ITU-T Q 3030-2008 Signalling architecture for the NGN service control plane (Study Group 11)《NGN设施控制平面用信令结构》.pdf

1、 International Telecommunication Union ITU-T Q.3030TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (02/2008) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Network signalling and control functional architecture Signalling architecture for the NGN service control

2、 plane Recommendation ITU-T Q.3030 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 SERVICES IN THE ISDN Q.60Q.99 CLAUSES APPLICABLE TO ITU-T ST

3、ANDARD 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.849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.9

4、99 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 INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND IS

5、DN 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 signalling Q.3130Q.3179 Signalling and control requirements and

6、 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 applications Q.3700Q.3849 Testing for NGN networks Q.3900Q.3999 F

7、or further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3030 (02/2008) i Recommendation ITU-T Q.3030 Signalling architecture for the NGN service control plane Summary Recommendation ITU-T Q.3030 describes the overall signalling architecture for the NGN service control pla

8、ne including the functional entities, interfaces and protocols. Source Recommendation ITU-T Q.3030 was approved on 29 February 2008 by ITU-T Study Group 11 (2005-2008) under Recommendation ITU-T A.8 procedure. ii Rec. ITU-T Q.3030 (02/2008) FOREWORD The International Telecommunication Union (ITU) is

9、 the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing

10、Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.

11、 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 purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Ad

12、ministration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and c

13、ompliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendati

14、on is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claime

15、d Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommen

16、dation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, wi

17、thout the prior written permission of ITU. Rec. ITU-T Q.3030 (02/2008) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 1 4 Abbreviations and acronyms 1 5 Conventions 1 6 Service control functions 2 7 Service control architecture and interfaces. 2 7.1 Service control functional entities 4 7

18、.2 Reference points . 4 7.3 Reference points and interfaces description. 6 Appendix I 11 Bibliography. 12 Rec. ITU-T Q.3030 (02/2008) 1 Recommendation ITU-T Q.3030 Signalling architecture for the NGN service control plane 1 Scope This Recommendation describes the overall signalling architecture for

19、the NGN service control plane. It identifies the functional entities (FEs), interfaces, and protocols that are required to model the control plane of the next generation network. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this

20、 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; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent editi

21、on 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 Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T H.248.1 Recommendation IT

22、U-T H.248.1 (2005), Gateway control protocol: Version 3. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2006), Functional requirements and architecture of the NGN release 1. ITU-T Y.2021 Recommendation ITU-T Y.2021 (2006), IMS for Next Generation Networks. ITU-T Y.2031 Recommendation ITU-T Y.2031 (2006),

23、 PSTN/ISDN emulation architecture. 3 Definitions No new definitions are needed. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: HTTP HyperText Transfer Protocol MSCML Media Server Control Markup Language NGN Next Generation Network PIEA PSTN/ISDN emula

24、tion architecture SIP Session Initiation Protocol VoiceXML Voice eXtensible Markup Language All other relevant abbreviations are contained in the above references. 5 Conventions None. 6 Service control functions The service control functions include call/session control, resource control, registrati

25、on, and authentication and authorization functions at the service level for both mediated and non-mediated 2 Rec. ITU-T Q.3030 (02/2008) services. They may also include functions for controlling media resources, i.e., specialized resources and gateways at the service-signalling level. 7 Service cont

26、rol architecture and interfaces This clause describes the details of the signalling architecture for the NGN service control plane, including the functional entities, interfaces and protocols. This service control architecture supports SIP-based sessions and is independent of services. Figure 1 show

27、s the generalized NGN functional architecture as defined in ITU-T Y.2012. The service control functional entities are bordered (highlighted) in Figure 1. The signalling architecture for the NGN service control plane is based on the service control functions outlined in clause 6. 3 Rec. ITU-T Q.3030

28、(02/2008) Q.3030(08)_F01Scope of NGNT-6:Inter-connectionborder gateway FE:S-6: S. authenticationand authorization FES-8: Access GWcontrol FENACF RACFRGWCustomernetworkNGNterminalLegacyterminalANIApplicationsS-11: User signallinginterworking FEEnd-userFunctionS-3: Interrogating call session control F

29、ES-14: Media resource broker FET-17: Transportresource control FEAccess packet transport functionsT-5:AccessbordergatewayFES-1: Serving call session control FET-8:MediaresourceprocessingFET-12: T. userprofile FET-4: Accessrelay FES-2: Proxy call sessioncontrol FES-4: Subscriptionlocator FES-5: S. us

30、er profile FET-16: Policy decision FES-15: General services control FENGNUNIOther NGNRACFT-14: Access management FET-15: Home gatewayConfiguration FET-11:T. authentication Media/application bandwidth requirements for QoS control. Interfaces supporting any of the above reference points will use the D

31、iameter protocol as indicated in b-ITU-T Q.3301.1. 7.3.13 S-2 (P-CSC-FE) S-11 (USIW-FE) This reference point allows communication between a P-CSC-FE and USIW-FE. Interfaces supporting the above reference point will use the SIP protocol. 7.3.14 S-11 (USIW-FE) End user function Access to end user func

32、tions not supporting SIP is performed at this reference point, via the USIW-FE. 7.3.15 S-7 (IBC-FE) S-12 (NSIW-FE) This reference point allows communication between an IBC-FE and NSIW-FE. Interfaces supporting the above reference point will use the SIP protocol. 7.3.16 S-12 (NSIW-FE) Other NGN/IP mu

33、ltimedia networks Interconnection with other NGN/IP multimedia networks supporting b-ITU-T H.323 or a non-compatible version of SIP is performed at this reference point, via the NSIW-FE. 7.3.17 S-7 (IBC-FE) T-6 (IBG-FE) This reference point is used by the IBC-FE to control the IBG-FE, e.g., to reque

34、st network address translation information. Interfaces supporting the above reference point will use the H.248 protocol. 7.3.18 S-8 (AGC-FE) T-1 (AMG-FE) This reference point is used by the AGC-FE to control the AMG-FE in case of supporting PSTN/ISDN services. Interfaces supporting the above referen

35、ce point will use the H.248 protocol. 7.3.19 S-7 (IBC-FE) Other NGN/IP multimedia networks This reference point is an IP interface between an IBC-FE and other NGN/IP multimedia networks. This reference point is used for call/session control with another IP network using SIP. Interfaces supporting th

36、e above reference point will use the SIP protocol. 7.3.20 S-10 (BGC-FE) S-10 (BGC-FE) S-10 (BGC-FE) Other NGN/IP multimedia networks These reference points allow a BGC-FE to exchange the call/session signalling with another BGC-FE in the same or another network, possibly via an IBC-FE. Interfaces su

37、pporting any of the above reference points will use the SIP protocol. 7.3.21 S-1 (S-CSC-FE) S-8 (AGC-FE) S-3 (I-CSC-FE) S-8 (AGC-FE) These reference points allow the communication and forwarding of call/session control signalling between an AGC-FE and S-CSC-FE/I-CSC-FE. Interfaces supporting any of

38、the above reference points will use the SIP protocol. Rec. ITU-T Q.3030 (02/2008) 9 7.3.22 S-9 (MGC-FE) S-13 (MRC-FE) Interfaces supporting any of the above reference points will use the SIP protocol. 7.3.23 S-13 (MRC-FE) S-10 (BGC-FE) Interfaces supporting any of the above reference points will use

39、 the SIP protocol. 7.3.24 S-2 (P-CSC-FE) T-13 (TLM-FE) This reference point enables a P-CSCF to obtain location information from the TLM-FE of the network attachment control functions (NACFs). Interfaces supporting the above reference point will use the Diameter (*) protocol *Whether other protocols

40、 may also be used need to be discussed as ITU-T has not agreed on a protocol for this reference point so far. 7.3.25 S-9 (MGC-FE) T-9 (SG-FE) This reference point enables the MGC-FE to exchange SS7 signalling information over IP with the SG-FE, according to the SIGTRAN architecture. 7.3.26 A-S1: S-1

41、4 (MRB-FE) ASF/SSF This reference point is used for MRB-FE to assign specific media server resources (i.e., MRC-FE and MRP-FE) to incoming calls at the request of service applications of the ASF/SSF. Interfaces supporting the above reference point could use SIP, HTTP, SOAP. 7.3.27 A-S4: S-1 (S-CSC-F

42、E) ASF/SSF This reference point supports the interactions between the S-CSC-FE and ASF/SSF in order to provide various session-based application services. ASF/SSF may interact with the AGC-FE through the S-CSC-FE to provide access to the applications required to support the legacy terminal users. In

43、terfaces supporting the above reference point will use SIP. 7.3.28 A-S5: S-6 (SAA-FE) ASF/SSF This reference point allows the ASF/SSF to query the SAA-FE the status of authentication, authorization, and accounting of users/terminals while it provides services. Interfaces supporting the above referen

44、ce point will use the Diameter (*) protocol. *Whether other protocols may also be used need to be discussed as ITU-T has not agreed on a protocol for this reference point so far. 7.3.29 A-S6: S-4 (SL-FE), S-5 (SUP-FE) ASF/SSF This reference point allows the ASF/SSF to query subscribers service profi

45、le and/or on the terminal capability information directly from SUP-FE, or indirectly from SUP-FE through SL-FE in case of multiple SUP-FEs. Interfaces supporting the above reference point will use the Diameter (*) protocol. * Whether other protocols may also be used need to be discussed as ITU-T has

46、 not agreed on a protocol for this reference point so far. 7.3.30 S-13 (MRC-FE) Application support function (ASF) This reference point enables the MRC-FE to interact with the ASF for enhanced services information, e.g., announcement. 10 Rec. ITU-T Q.3030 (02/2008) There are multiple protocols/langu

47、ages and modes of transport options for interfaces supporting this reference point. A particular network providers service types, equipment, traffic volumes, resource sharing strategies, etc., would determine the particular S-13 (MRC-FE) ASF interface best options for that network. More than one con

48、trol protocol/language can be used for the interactive media functionality. Example control protocols/languages for this interface include SIP, HTTP, voice extensible markup language (VoiceXML) and media server control markup language (MSCML). Rec. ITU-T Q.3030 (02/2008) 11 Appendix I (This appendix

49、 does not form an integral part of this Recommendation) The purpose of this appendix is to highlight the relationship between reference points (as defined in various architecture Recommendations) and candidate protocols potentially for use in interfaces supporting these reference points. Table I.1 shows the interface mapping tables between ASF/SSF and SCF. It also includes candidate protocols. Table I.1 Correspondence among reference points of Y.2012, Y.2021, and Y.2031 Y.2012 Y.2021 and Y.2031 (IMS