1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Q.3051 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2015) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN network signalling and control functional architecture Signalling archite
2、cture for the control plane of distributed service networking Recommendation ITU-T Q.3051 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVI
3、CES IN THE ISDN Q.60Q.99 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119 SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 Q.120Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.
4、849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER IN
5、DEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN Q.3000Q.3999 General Q.3000Q.3029 Network signalling and control functional architecture Q.3030Q.3099 Network data organization within the NGN Q.3100Q.3129 Bearer control signalin
6、g Q.3130Q.3179 Signalling and control requirements and protocols to support attachment in NGN environments Q.3200Q.3249 Resource control protocols Q.3300Q.3369 Service and session control protocols Q.3400Q.3499 Service and session control protocols supplementary services Q.3600Q.3649 NGN application
7、s Q.3700Q.3849 Testing for next generation networks Q.3900Q.3999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3051 (06/2015) i Recommendation ITU-T Q.3051 Signalling architecture for the control plane of distributed service networking Summary Recommendation IT
8、U-T Q.3051 describes the overall signalling architecture for the control plane of distributed service networking. It identifies the functions, physical entities (PEs), interfaces and protocols that will model the control plane for distributed service networking (DSN). History Edition Recommendation
9、Approval Study Group Unique ID* 1.0 ITU-T Q.3051 2015-06-13 11 11.1002/1000/12491 Keywords Control plane, DSN, signalling architecture. _ * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For exampl
10、e, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Q.3051 (06/2015) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardiza
11、tion Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which me
12、ets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts
13、 purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is
14、 voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“
15、and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation may in
16、volve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Re
17、commendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database
18、 at http:/www.itu.int/ITU-T/ipr/. ITU 2016 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Q.3051 (06/2015) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined e
19、lsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Control architecture and functions 2 6.1 Functions 3 6.2 Reference points . 4 7 Physical entities and interfaces in DSN architecture 6 7.1 PEs and interfaces for content services over DSN . 6 7.2
20、 PEs and interfaces when deploying MMTel service over DSN . 7 8 Protocols used for interfaces . 8 8.1 Protocols used for interfaces when deploying content services over DSN 8 8.2 Protocols used for interfaces when deploying MMTel service over DSN . 9 9 Security considerations . 9 Rec. ITU-T Q.3051 (
21、06/2015) 1 Recommendation ITU-T Q.3051 Signalling architecture for the control plane of distributed service networking 1 Scope This Recommendation provides signalling architecture for control plane of distributed service networking (DSN). Based on the functional architecture and the service provisio
22、ning in DSN, it specifies the mapping of functions into PEs and the mapping of reference points to interfaces in DSN architecture when deploying content service and multimedia telephony (MMTel) service over DSN. It also describes the protocols used for interfaces and security considerations, etc. 2
23、References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision;
24、 users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Reco
25、mmendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Q.1741.6 Recommendation ITU-T Q.1741.6 (2009), IMT-2000 references to Release 8 of GSM- evolved UMTS core network. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2010), Functional requirements and architecture o
26、f next generation networks. ITU-T Y.2080 Recommendation ITU-T Y.2080 (2012), Functional architecture for distributed service networking. ITU-T Y.2206 Recommendation ITU-T Y.2206 (2010), Requirements for distributed service networking capabilities. IETF RFC 768 IETF RFC 768 (1980), User Datagram Prot
27、ocol. IETF RFC 2326 IETF RFC 2326 (1998), Real Time Streaming Protocol (RTSP). IETF RFC 2616 IETF RFC 2616 (1999), Hypertext Transfer Protocol HTTP/1.1. IETF RFC 3550 IETF RFC 3550 (2003), RTP: A Transport Protocol for Real-Time Applications. IETF RFC 4825 IETF RFC 4825 (2007), The Extensible Markup
28、 Language (XML) Configuration Access Protocol (XCAP). IETF RFC 6940 IETF RFC 6940 (2014), REsource LOcation And Discovery (RELOAD) Base Protocol. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 distributed service networking (DSN) ITU-T
29、 Y.2206: An overlay networking which provides distributed and manageable capabilities to support various multimedia services and applications. 2 Rec. ITU-T Q.3051 (06/2015) 3.1.2 functional entity ITU-T Y.2012: An entity that comprises an indivisible set of specific functions. Functional entities ar
30、e logical concepts, while groupings of functional entities are used to describe practical, physical implementations. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AF Application Function CDF Content Deli
31、very Function CSAF Content Service Application Function DHT Distributed Hash Table DSN Distributed Service Networking EF End-user Function HTTP Hypertext Transfer Protocol ID Identification MMTel Multimedia Telephony NEF Node Enrolment Function PE Physical Entity RELOAD Resource Location And Discove
32、ry RF Relay Function RLF Resource Location Function RTP Real-time Transport Protocol RTSP Real Time Streaming Protocol SCF Service Control Function SIP Session Initiation Protocol TOCF Traffic Optimization Control Function UDP User Datagram Protocol UE User Equipment 5 Conventions None. 6 Control ar
33、chitecture and functions This clause summarizes the DSN functional architecture as described in ITU-T Y.2080, see Figure 6-1. Rec. ITU-T Q.3051 (06/2015) 3 Figure 6-1 DSN functional architecture 6.1 Functions 6.1.1 Node enrolment functions (NEFs) The NEF allocates a globally unique node identificati
34、on (ID) to each enrolling DSN node, provides bootstrap information for a DSN node to join to the distributed hash table (DHT)-based DSN network, and maintains the node profile. 6.1.2 Resource location functions (RLFs) The RLF maintains resource-related information and finds the required resources wh
35、en inquired. 6.1.3 Relay functions (RFs) The RF relays particular application traffic for DSN nodes to achieve NAT/firewall traversal and QoS improvement. 6.1.4 Content delivery functions (CDFs) The CDF stores, processes and delivers content to DSN nodes or user equipment (UE). 6.1.5 Traffic optimiz
36、ation control functions (TOCFs) The TOCF monitors and analyses network information, and provides guidance to DSN nodes in order to make the delivery and distribution of application traffic in the DSN network more efficient and cost-effective. 6.1.6 Management functions (MFs) The MFs inherit the MF f
37、unctions defined in ITU-T Y.2012, which include fault management, configuration management, accounting management, performance management, security management functions, etc. 6.1.7 Service control functions (SCFs) In DSN, the SCF defined in the NGN architecture ITU-T Y.2012 is reused for service con
38、trol. 4 Rec. ITU-T Q.3051 (06/2015) 6.1.8 End-user functions (EFs) The EF is a function of DSN UE, which supports access to a DSN network and services. 6.1.9 Content service application functions (CSAFs) The CSAF is an application function (AF) responsible in the DSN functional architecture for the
39、provision of content-related services to the EF. The functions are described in detail in ITU-T Y.2080. 6.2 Reference points 6.2.1 Reference point C1 The C1 reference point is between NEF and RLF. C1 is used by RLF to request the enrolment of a DSN node in which the RLF resides in the DHT-based DSN
40、network. C1 is used by NEF to provide configuration and bootstrap information to the RLF regarding a DSN node that newly joins the DHT based overlay in DSN network. 6.2.2 Reference point C2 The C2 reference point is between RLFs. C2 is used to exchange the information that constructs and maintains t
41、he DHT based overlay in a DSN network. C2 is also used to forward resource location requests or resource location update requests to RLFs. 6.2.3 Reference point C3 The C3 reference point is between RLF and CDF. C3 is used by CDF: to register content to RLFs; to request RLF for content location infor
42、mation; to report to RLF the status of a node in which the CDF resides. The status information includes: CPU usage, memory usage, disk usage, network interface usage, etc.; to report event related information to RLF, for instance, the event may be that the load of the node in which CDF resides reach
43、ed threshold; to report content related information to RLF, for instance, the content availability or content popularity, etc. 6.2.4 Reference point C4 The C4 reference point is between RF and RLF. C4 is used by RF to register the relay node in which it resides to RLF. C4 is used by RF to report the
44、 status of the node in which it resides to RLF, the status information includes: CPU usage, memory usage, disk usage, network interface usage, etc. C4 is used by RF to report event related information to RLF, for instance, the event may be that the load of the node in which RF resides reached thresh
45、old. C4 is used by RF to report the QoS measurement message to RLF. C4 is used by RLF to reserve resources on RF. Rec. ITU-T Q.3051 (06/2015) 5 6.2.5 Reference point C5 The C5 reference point is between TOCF and RLF. C5 is used by RLF to enquire TOCF about network information and to request traffic
46、optimization results from TOCF. 6.2.6 Reference point C6 The C6 reference point is between EF and SCF. C6 is used to exchange service control related information between EF and SCF. For instance, registration information or service request information. 6.2.7 Reference point C7 The C7 reference point
47、 is between RLF and SCF. C7 is used by SCF to request resource location from RLFs. 6.2.8 Reference point C8 The C8 reference point is between RLF and EF. C8 is used by EF to request resource location from RLF. 6.2.9 Reference point C9 The C9 reference point is between EF and CDF. C9 is used by EF to
48、 query a buffer map and request content from CDF. 6.2.10 Reference point C10 The C10 reference point is between CDFs. C10 is used by CDF to query a buffer map and request content from another CDF. 6.2.11 Reference point A1 The A1 reference point is between EF and CSAF. A1 is used by EF for accessing
49、 content services and requesting content location. 6.2.12 Reference point A2 The A2 reference point is between SCF and CSAF. A2 is used for user authentication and authorization. 6.2.13 Reference point A3 The A3 reference point is between CSAF and RLF. A3 is used by CSAF to request RLF for the available content node. 6.2.14 Reference point A4 The A4 reference point is between AF and TOCF. A4 is used by AF to query and subscribe the specific traffic related information. 6.2.15 Refere
copyright@ 2008-2019 麦多课文库（www.mydoc123.com）网站版权所有
备案/许可证编号：苏ICP备17064731号-1