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.3404 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2016) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Service and session control protocols Signalling requirements for NGN rea
2、l-time multimedia services supporting IPv6 transition Recommendation ITU-T Q.3404 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 T
3、HE 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.849 DIGI
4、TAL 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 INDEPENDEN
5、T CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN Q.3000Q.3709 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.313
6、0Q.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.3616 Service and session co
7、ntrol protocols supplementary services based on SIP-IMS Q.3617Q.3639 NGN applications Q.3700Q.3709 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN Q.3710Q.3899 TESTING SPECIFICATIONS Q.3900Q.4099 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3404 (08/2016) i Reco
8、mmendation ITU-T Q.3404 Signalling requirements for NGN real-time multimedia services supporting IPv6 transition Summary Recommendation ITU-T Q.3404 describes the IPv6 transition technologies which could be applied in a next generation network (NGN) environment. The signalling requirements supportin
9、g NGN real-time multimedia services in Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) mixed network are specified. Three mechanisms for IPv6 transition are introduced in this Recommendation including dual stack, translation and tunnelling. History Edition Recommendation Ap
10、proval Study Group Unique ID* 1.0 ITU-T Q.3404 2016-08-29 11 11.1002/1000/12987 Keywords IPv6, multimedia services, NGN. * 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 example, http:/handle.i
11、tu.int/11.1002/1000/11830-en. ii Rec. ITU-T Q.3404 (08/2016) 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 Standardization Sector (ITU-
12、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 meets every four ye
13、ars, 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 purview, the nec
14、essary 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 voluntary. Howev
15、er, 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“ and the negative
16、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 involve the use of
17、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 Recommendation, ITU
18、 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 at http:/www.itu
19、.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.3404 (08/2016) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Te
20、rms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Architecture for NGN multimedia services supporting IPv6 transition . 2 7 Signalling requirements for dual stack . 3 8 Signalling requirements for translation 3 8.1 General requirements 3 8.2 Scenario 1: UE using
21、 IPv6 and NGN core using IPv4 . 4 8.3 Scenario 2: UE using IPv4 and NGN core using IPv6 . 4 8.4 Scenario 3: NGN core using IPv6 and other IP-based network using IPv4 . 5 8.5 Scenario 4: NGN core using IPv4 and other IP-based networks using IPv6 . 6 9 Signalling requirements for tunnelling . 7 9.1 Ov
22、erviews . 7 9.2 Scenario1: 4over6 tunnel connecting IPv4 NGN core networks 7 9.3 Scenario 2: 6over4 tunnel connection IPv6 NGN core networks . 8 Rec. ITU-T Q.3404 (08/2016) 1 Recommendation ITU-T Q.3404 Signalling requirements for NGN real-time multimedia services supporting IPv6 transition 1 Scope
23、This Recommendation describes the IPv6 transition technologies which could be applied in a next generation network (NGN) environment. The signalling requirements supporting NGN real-time multimedia services in Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) mixed network ar
24、e specified. Three mechanisms for IPv6 transition are described in this Recommendation including dual stack, translation and tunnelling. The security issues introduced by IPv6 transition is out of scope of this Recommendation. 2 References The following ITU-T Recommendations and other references con
25、tain 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; users of this Recommendation are therefore encouraged to investigate t
26、he 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 Recommendation does not give it, as a stand-alone document, the status of a
27、 Recommendation. ITU-T Y.2011 Recommendation ITU-T Y.2011 (2004), General principles and general reference model for Next Generation Networks. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2010), Functional requirements and architecture of next generation networks. ITU-T Y.2701 Recommendation ITU-T Y.27
28、01 (2007), Security requirements for NGN release 1. IETF RFC 5565 IETF RFC 5565 (2009), Softwire Mesh Framework. IETF RFC 5747 IETF RFC 5747 (2010), 4over6 Transit Solution Using IP Encapsulation and MP-BGP Extensions. IETF RFC 5969 IETF RFC 5969 (2010), IPv6 Rapid Deployment on IPv4 Infrastructures
29、 (6rd) - Protocol Specification. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 NGN service stratum ITU-T Y.2011: That part of the NGN which provides the user functions that transfer service-related data and the functions that control
30、and manage service resources and network services to enable user services and applications. 3.1.2 NGN transport stratum ITU-T Y.2011: That part of the NGN which provides the user functions that transfer data and the functions that control and manage transport resources to carry such data between ter
31、minating entities. 3.2 Terms defined in this Recommendation None. 2 Rec. ITU-T Q.3404 (08/2016) 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: ABG-FE Access Border Gateway Functional Entity ALG Application Level Gateway IBC-FE Interconnection Border G
32、ateway Control Functional Entity IBG-FE Interconnection Border Gateway Functional Entity IP Internet Protocol ISDN Integrated Services Digital Network NACF Network Attachment Control Functions NAT Network Address Translation NAT-PT Network Address Translation Protocol Translation NNI Network to Netw
33、ork Interface NSIW-FE Network Signalling Interworking Functional Entity P-CSC-FE Proxy Call Session Control Functional Entity PSTN Public Switched Telephone Network RACF Resource and Admission Control Functions S-CSC-FE Serving Call Session Control Functional Entity SCTP Stream Control Transmission
34、Protocol SDP Session Description Protocol SIP Session Initiation Protocol TCP Transmission Control Protocol UDP User Datagram Protocol UE User Equipment UNI User to Network Interface 5 Conventions In this Recommendation: The keywords “is required to“ indicate a requirement which must be strictly fol
35、lowed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. The keywords “is recommended“ indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. The keywords “can o
36、ptionally“ indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendors implementation must provide the option, and the feature can be optionally enabled by the network operator/service provider. Rather, i
37、t means the vendor may optionally provide the feature and still claim conformance with this Recommendation. 6 Architecture for NGN multimedia services supporting IPv6 transition The architecture of NGN multimedia services supporting IPv6 transition is depicted in Figure 6-1. Rec. ITU-T Q.3404 (08/20
38、16) 3 T e r m i n a l E q u i p m e n t T r ans p or t S t r at u mS e r vi c e S t r at u mN G N c or e UNI NNIFigure 6-1 Architecture for NGN multimedia services supporting IPv6 transition In order to reduce the interworking complexity, all functional entities in the NGN core network (e.g., proxy
39、call session control functional entity (P-CSC-FE), serving call session control functional entity (S-CSC-FE), access border gateway functional entity (ABG-FE) should use the same version of internet protocol as far as possible. Accordingly, IP protocol transition is only required on user to network
40、interface (UNI) and network to network interface (NNI) within both control plane and media plane in NGN service stratum and NGN transport stratum. Three IPv6 transition mechanisms are introduced in this Recommendation to support NGN real-time multimedia services, including dual stack, translation an
41、d tunnelling as specified in clause 7, clause 8 and clause 9 respectively. 7 Signalling requirements for dual stack In order to support dual stack transition, all functional entities inside an NGN core network are required to support IPv4 and IPv6 simultaneously. At the edge of an NGN core network,
42、the functional entities connected to user equipment (UEs) or other IP-based networks should have the capability to adapt the same IP version as that which is used by the connected entities (UEs and/or other IP-based networks) both at the signalling level and media level. 8 Signalling requirements fo
43、r translation 8.1 General requirements Network address translation (NAT)/network address translation protocol translation (NAT-PT) functions are required to be processed in the border of the IPv4 and IPv6 network for translation transition. The IPv4 address of the traffic from the IPv4 network to th
44、e IPv6 network shall be translated into IPv6 address in the border gateway, and vice versa. As an interconnecting node, the border gateway shall support dual stack. The border gateway shall also implement application level gateway (ALG) function which provides the application level translation for s
45、pecific protocols (e.g., session initiation protocol (SIP) and session description protocol (SDP). The border gateway shall be located in the border of networks using different protocols. Referring to NGN architecture defined in ITU-T Y.2012, the functions of border gateway could be implemented in A
46、BG-FE, interconnection border gateway functional entity (IBG-FE)， P-CSC-FE and interconnection border gateway control functional entity (IBC-FE). 4 Rec. ITU-T Q.3404 (08/2016) Considering IPv6 transition using translation mechanism, there are four specific scenarios: 1) Scenario 1: UE using IPv6 and
47、 NGN core using IPv4; 2) Scenario 2: UE using IPv4 and NGN core using IPv6; 3) Scenario 3: NGN core using IPv6 and other IP-based network using IPv4; 4) Scenario 4: NGN core using IPv4 and other IP-based network using IPv6. 8.2 Scenario 1: UE using IPv6 and NGN core using IPv4 Figure 8-1 Scenario 1:
48、 UE using IPv6 and NGN core using IPv4 In the scenario of UE using IPv6 and NGN core using IPv4 shown in Figure 8-1, P-CSC-FE and ABG-FE act as a border gateway within the control plane and the user plane (media plane) respectively. P-CSC-FE implements ALG function which provides the application lev
49、el translation for SIP and SDP. It requests address mapping information based on the address binding information provided by the resource and admission control functions (RACF), and then modifies the addresses and/or ports contained in the SIP and SDP message bodies. The function and procedure of RACF refers to ITU-T Y.2701. ABG-FE implements NAT/NAT-PT function under the control of the network attachment control functions (NACF) and RACF. A globally unique IPv4 address, dynamically allocated from an IPv4 addres
