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 Y.2616 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2014) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Packet-based Networks Interworkin
2、g mechanisms in public packet telecom data networks Recommendation ITU-T Y.2616 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.2
3、99 Network aspects Y.300Y.399 Interfaces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Archite
4、cture, access, network capabilities and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y
5、.1999 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Enhance
6、ments to NGN Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.350
7、0Y.3999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.2616 (08/2014) i Recommendation ITU-T Y.2616 Interworking mechanisms in public packet telecom data networks Summary Constituting a hierarchical packet data network which can meet requirements of future packe
8、t based networks (FPBN), public packet telecom data networks (PTDN) provide efficient interworking mechanisms with other packet data networks (PDN), e.g., IP networks and other PTDNs. Recommendation ITU-T Y.2616 illustrates five typical PTDN interworking scenarios and relevant interworking framework
9、s, interworking mechanisms and corresponding interworking procedures on the data plane, control plane and management plane. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.2616 2014-08-29 13 11.1002/1000/12282 Keywords PTDN, interworking mechanism, interworking framework,
10、data plane, control plane, management plane. _ * 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.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.2616 (08/2014) FOREWORD The
11、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-T) is a permanent organ of ITU. ITU-T is responsible for studying technica
12、l, 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 years, establishes the topics for study by the ITU-T study groups which, in
13、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 necessary standards are prepared on a collaborative basis with ISO and IEC. N
14、OTE 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. However, the Recommendation may contain certain mandatory provisions (to ensure
15、, 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 equivalents are used to express requirements. The use of such words does n
16、ot 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 a claimed Intellectual Property Right. ITU takes no position concerning th
17、e 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 had not received notice of intellectual property, protected by patents, w
18、hich 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.int/ITU-T/ipr/. ITU 2014 All rights reserved. No part of this publication
19、 may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.2616 (08/2014) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 1 4 Abbreviations and acronyms 2 5 Co
20、nventions 2 6 Interworking scenarios 2 6.1 Interworking between two peer PTDNs . 2 6.2 PTDNs interworking across another PTDN . 3 6.3 PTDNs interworking via an IP network (or other PDN) 3 6.4 Interworking of two IP networks (IP islands) via a PTDN 3 6.5 Interworking between a PTDN and a PDN 3 7 Two
21、peer interworking PTDNs 3 7.1 Interworking requirements . 4 7.2 Data plane interworking . 4 7.3 Control plane interworking . 4 7.4 Management plane interworking 5 7.5 OAM interworking . 5 8 Interworking across a PTDN 5 8.1 Interworking requirements . 6 8.2 Data plane interworking . 6 8.3 Control pla
22、ne interworking . 6 8.4 Management plane interworking 7 8.5 OAM interworking . 7 9 PTDNs interworking via an IP network (or other PDN) 7 9.1 Interworking requirements . 7 9.2 Data plane interworking . 7 9.3 Control plane interworking . 8 9.4 Management plane interworking 8 9.5 OAM interworking . 8 1
23、0 Two IP networks (IP islands) interworking via a PTDN 8 10.1 Interworking requirements . 9 10.2 Data plane interworking . 9 10.3 Control plane interworking . 9 10.4 Management plane interworking 9 10.5 OAM interworking . 9 iv Rec. ITU-T Y.2616 (08/2014) Page 11 Interworking of a PTDN and a PDN 9 12
24、 Security considerations . 10 Bibliography. 12 Rec. ITU-T Y.2616 (08/2014) 1 Recommendation ITU-T Y.2616 Interworking mechanisms in public packet telecom data networks 1 Scope This Recommendation defines the interworking scenarios, interworking frameworks, interworking mechanisms and corresponding i
25、nterworking procedures on the data plane, control plane and management plane as well as interworking security considerations relating to public packet telecom data networks (PTDNs). 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in t
26、his 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 ed
27、ition 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 Y.1401 Recommendation
28、ITU-T Y.1401 (2008), Principles of interworking. ITU-T Y.2011 Recommendation ITU-T Y.2011 (2004), General principles and general reference model for Next Generation Networks. ITU-T Y.2615 Recommendation ITU-T Y.2615 (2012), Routing mechanisms in public packet telecommunication data networks. 3 Defin
29、itions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 control plane ITU-T Y.2011: The set of functions that controls the operation of entities in the stratum or layer under consideration, plus the functions required to support this control. 3.1.2 da
30、ta plane ITU-T Y.2011: The set of functions used to transfer data in the stratum or layer under consideration. 3.1.3 interworking ITU-T Y.1401: The term “interworking“ is used to express interactions between networks, between end systems, or between parts thereof, with the aim of providing a functio
31、nal entity capable of supporting an end-to-end communication. 3.1.4 interworking function ITU-T Y.1401: These functions are referred to in the interworking definition, which include the conversion between protocols and the mapping of one protocol to another. The functionality required between networ
32、ks can be separated from the functionality, if any, required in end system. 3.1.5 management plane ITU-T Y.2011: The set of functions used to manage entities in the stratum or layer under consideration, plus the functions required to support this management. 3.2 Terms defined in this Recommendation
33、None. 2 Rec. ITU-T Y.2616 (08/2014) 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: ED Edge Device ID Identifier IP Internet Protocol IWF Interworking Function MC Multicast McID Multicast Identifier NMS Network Management System NNI Network to Network
34、Interface OAM Operation, Administration and Maintenance PDN Packet Data Network PTDN Public packet Telecom Data Network QoS Quality of Service VPN Virtual Private Network VPNID Virtual Private Network Identifier 5 Conventions In this Recommendation, the following conventions are used: The keywords “
35、is required to“ and “are required to“ indicate a requirement or requirements which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. The keywords “is recommended to“ indicate a requirement which is recommended but which is not
36、absolutely required. Thus this requirement need not be present to claim conformance. The keywords “can optionally“ 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 t
37、he option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor can optionally provide the feature and still claim conformance with the specification. 6 Interworking scenarios 6.1 Interworking between two peer PTDNs In the scenario shown in F
38、igure 6-1, two peer PTDNs that belong to different operators need to interwork with each other and the interworking process is limited to these two PTDNs. Y . 2 6 1 6 ( 1 4 ) _ F 6 - 1P T D N - A P T D N - BI W FFigure 6-1 Interworking between two peer PTDNs Rec. ITU-T Y.2616 (08/2014) 3 6.2 PTDNs i
39、nterworking across another PTDN In the scenario shown in Figure 6-2, two PTDNs that belong to different operators (or different private networks) interwork with each other across a third PTDN. Y . 2 6 1 6 ( 1 4 ) _ F 6 - 2P T D N - A P T D N - C P T D N - BI W F I W FFigure 6-2 PTDNs interworking ac
40、ross another PTDN 6.3 PTDNs interworking via an IP network (or other PDN) In the scenario shown in Figure 6-3, two separated PTDNs interwork via an IP network (or other PDN). The IP network (or other PDN) provides a kind of tunnel mechanism between two PTDNs. The data packets from the sending PTDN a
41、re encapsulated in an IP network (or other PDN) tunnel, they are then sent to the receiving PTDN and are de-capsulated at the border of the receiving PTDN. Y . 2 6 1 6 ( 1 4 ) _ F 6 - 3P T D N - A IP n e t w o r k( t h e r P D N )o r o P T D N - BI W F I W FFigure 6-3 PTDNs interworking via an IP ne
42、twork (or other PDN) 6.4 Interworking of two IP networks (IP islands) via a PTDN In the scenario shown in Figure 6-4, two separated IP networks (or other PDNs) interwork via a PTDN that provides a kind of tunnel mechanism between the two IP networks (or other PDNs). The data packets from the sending
43、 IP network (or other PDN) are encapsulated in a PTDN tunnel, they are then sent to the receiving IP network (or other PDN) and are then de-capsulated at the border of the receiving IP network (or other PDN). Y . 2 6 1 6 ( 1 4 ) _ F 6 - 4I P - A P T D N I P - BED EDFigure 6-4 Interworking of two sep
44、arated IP networks (or other PDNs) via a PTDN 6.5 Interworking between a PTDN and a PDN The interworking scenario shown in Figure 6-5 involves service interworking between the service terminals of an IP network (or other PDN) and the service terminals of a PTDN. P T D N P D NI W FP T D N t e r m i n
45、 a l s P D N t e r m i n a l sY . 2 6 1 6 ( 1 4 ) _ F 6 - 5 Figure 6-5 Service interworking between a PTDN and a PDN 7 Two peer interworking PTDNs Figure 7-1 provides a general framework of two peer PTDNs interworking. 4 Rec. ITU-T Y.2616 (08/2014) Y . 2 6 1 6 ( 1 4 ) _ F 7 - 1E n du s e r 1 P T D N
46、 -AIW FA B P T D N -B E n du s e r 2N e t w o rk -BN e t w o rk -AFigure 7-1 Two peer PTDNs interworking framework In this figure, IWF indicates the interworking function module. All data need to traverse the IWF module when two peer PTDNs that belong to different operators (or private networks) int
47、erwork with each other. An interworking function module comprises a data plane, a control plane and a management plane. 7.1 Interworking requirements When two peer PTDNs are interworking, the following interworking requirements apply: Routing information is required to be exchanged between PTDN-A an
48、d PTDN-B. The QoS guarantee mechanisms of PTDN-A and PTDN-B are required to be supported in the IWF module. Each PTDN has its own independent virtual network management mechanism and virtual private network identifier (VPNID) assignment mechanism. The VPN is required to be terminated on the IWF modu
49、le and the VPNID is required to be translated on the IWF module. Each PTDN has its own independent multicast management mechanism and multicast identifier or McID assignment mechanism. The multicast is required to be terminated in the IWF and the McID is required to be translated by the IWF. If network alarm information needs to be transferred, relevant alarm parameters are required to be translated via the IWF based on the local PTDN alarm management mechanism. If the network
