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.3034 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2015) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Future networks Architecture for interworking of heterogen
2、eous component networks in ID/locator split-based future networks Recommendation ITU-T Y.3034 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 middl
3、eware Y.200Y.299 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.1100
4、Y.1199 Architecture, 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 ov
5、er NGN Y.1900Y.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.2250
6、Y.2299 Enhancements 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 C
7、OMPUTING Y.3500Y.3999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.3034 (06/2015) i Recommendation ITU-T Y.3034 Architecture for interworking of heterogeneous component networks in ID/locator split-based future networks Summary Recommendation ITU-T Y.3034 spec
8、ifies the architecture for interworking of heterogeneous component networks in ID/locator split-based future networks. It describes the functions of the different architectural components such as the host, gateway and ID/locator mapping server. It also lists the advantages and challenges of the arch
9、itecture. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.3034 2015-06-13 13 11.1002/1000/12521 Keywords Heterogeneous network, ID/locator split-based future networks, interworking. _ * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field o
10、f 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.3034 (06/2015) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and
11、 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 Recommendations on them with a view to standardizing telecommunications on a worldwide bas
12、is. 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. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resol
13、ution 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 “Administration“ is used for conciseness to indicate both a telecommunication administration
14、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 compliance with the Recommendation is achieved when all of these mandatory provisions are
15、 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 Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the poss
16、ibility 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 claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the
17、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 Recommendation. However, implementers are cautioned that this may not represent the latest inform
18、ation and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2015 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 Y.3034 (06/2015) iii Table of Conte
19、nts Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 3 4 Abbreviations and acronyms 4 5 Conventions 4 6 Overview of interworking heterogeneous networks in future networks 4 7 Heterogeneous component network environment 5 8 Con
20、figuration of ID/locator split-based future networks 7 8.1 Host function 8 8.2 Gateway function 9 8.3 Router function . 10 8.4 ID/locator mapping server function 11 9 Architecture for interworking of heterogeneous network protocols . 11 10 Advantages and challenges . 12 10.1 Advantages . 12 10.2 Cha
21、llenges 13 11 Environmental considerations 13 12 Security considerations . 14 Bibliography. 15 Rec. ITU-T Y.3034 (06/2015) 1 Recommendation ITU-T Y.3034 Architecture for interworking of heterogeneous component networks in ID/locator split-based future networks 1 Scope The scope of this Recommendatio
22、n includes the following items: Overview of the functional components of the ID/locator split-based future network architecture relevant to interworking of heterogeneous component networks; Architecture for interworking of heterogeneous component networks in ID/locator split-based future networks. 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, editions indicated were valid. All Recommendations and other references are subject to revision; us
24、ers 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 published regularly. The reference to a document within this Recomme
25、ndation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Y.2015 Recommendation ITU-T Y.2015 (2009), General requirements for ID/locator separation in NGN. ITU-T Y.2022 Recommendation ITU-T Y.2022 (2011), Functional architecture for the support of host-based separati
26、on of node identifiers and routing locators in next generation networks. ITU-T Y.2057 Recommendation ITU-T Y.2057 (2011), Framework of node identifier and locator separation in IPv6-based next generation networks. ITU-T Y.3001 Recommendation ITU-T Y.3001 (2011), Future networks: Objectives and desig
27、n goals. ITU-T Y.3011 Recommendation ITU-T Y.3011 (2012), Framework of network virtualization for future networks. ITU-T Y.3031 Recommendation ITU-T Y.3031 (2012), Identification framework in future networks. ITU-T Y.3032 Recommendation ITU-T Y.3032 (2014), Configurations of node identifiers and the
28、ir mapping with locators in future networks. ITU-T Y.3033 Recommendation ITU-T Y.3033 (2014), Framework of data aware networking for future networks. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 access border gateway b-ITU-T Y.2091:
29、A packet gateway between an access network and a core network. 2 Rec. ITU-T Y.3034 (06/2015) 3.1.2 address b-ITU-T Y.2091: An address is the identifier for a specific termination point and is used for routing to this termination point. 3.1.3 component network ITU-T Y.3001: A single homogeneous netwo
30、rk which, by itself, may not provide a single end-to-end global telecommunication infrastructure. 3.1.4 future network (FN) ITU-T Y.3001: A network able to provide services, capabilities, and facilities difficult to provide using existing network technologies. A future network is either: a) A new co
31、mponent network or an enhanced version of an existing one, or b) A heterogeneous collection of new component networks or of new and existing component networks that is operated as a single network. 3.1.5 gateway b-ITU-T Y.2261: A unit that interconnects different networks and performs the necessary
32、translation between the protocols used in these networks. 3.1.6 identifier b-ITU-T Y.2091: An identifier is a series of digits, characters and symbols or any other form of data used to identify subscriber(s), user(s), network element(s), function(s), network entity(ies) providing services/applicatio
33、ns, or other entities (e.g., physical or logical objects). Identifiers can be used for registration or authorization. They can be either public to all networks, shared between a limited number of networks or private to a specific network (private IDs are normally not disclosed to third parties). 3.1
34、.7 ID/locator mapping ITU-T Y.2015: ID/LOC mapping is an association between a node ID and one or more LOCs. NOTE 1 A single node ID or several node IDs can be associated with many LOCs associated with a single terminal. The node ID to LOC mapping can have the one-to-one, one-to-many, or many-to-one
35、 relationship. NOTE 2 ID/LOC mapping is also called ID/LOC binding. 3.1.8 ID/locator mapping function ITU-T Y.2015: An ID/LOC mapping function gets mapping information from an ID/LOC mapping storage function and uses the corresponding node ID and/or LOC in packet headers. The ID/LOC mapping function
36、 works in a close correlation with the transport user profile associated with the transport control function. 3.1.9 ID/locator mapping storage function ITU-T Y.2015: An ID/LOC mapping storage function stores the mapping of NGN identifiers, node IDs and LOCs. This function also updates mapping inform
37、ation, as well as provides mapping information to other functions on request. The mapping storage function can be physically located in an NGN terminal or with other NGN components. 3.1.10 ID/locator separation ITU-T Y.2015: ID/LOC separation is decoupling the semantic of IP address into the semanti
38、cs of node IDs and LOCs. Distinct namespaces are used for node IDs and LOCs so that they can evolve independently. LOCs are associated with the IP layer whereas node IDs are associated with upper layers in such a way that ongoing communication sessions or services shall not be broken by changing LOC
39、s due to mobility and multi-homing. NOTE In this Recommendation, ID/locator separation and ID/locator split are used interchangeably. 3.1.11 interworking b-ITU-T Y.1401: The term “interworking“ is used to express interactions between networks, between end systems, or between parts thereof, with the
40、aim of providing a functional entity capable of supporting an end-to-end communication. The interactions required to provide a functional entity rely on functions and on the means to select these functions. 3.1.12 locator (LOC) ITU-T Y.2015: A locator is the network-layer topological name for an int
41、erface or a set of interfaces. LOCs are carried in the IP address fields as packets traverse the network. NOTE IP addresses can gradually become pure LOCs. However, on the contrary, it cannot be said that a LOC is an IP address. An IP address may associate with the IP layer as well as upper layer pr
42、otocols (such as TCP and HTTP), whereas a LOC will associate with only the IP layer and be used in IP address fields. Rec. ITU-T Y.3034 (06/2015) 3 3.1.13 name b-ITU-T Y.2091: A name is the identifier of an entity (e.g., subscriber, network element) that may be resolved/translated into an address. 3
43、.1.14 network address translation b-ITU-T Y.2111: The operation by which IP addresses are translated (mapped) from one address domain to another address domain. 3.1.15 network address port translation (NAPT) b-ITU-T Y.2111: The operation by which IP addresses and transport or port identifiers such a
44、s TCP and UDP port numbers are translated (i.e., mapped) from one address domain to another address domain. 3.1.16 node ID ITU-T Y.2015: A node ID is an identifier used at the transport and higher layers to identify the node as well as the endpoint of a communication session. A node ID is independen
45、t of the node location as well as the network to which the node is attached so that the node ID is not required to change even when the node changes its network connectivity by physically moving or simply activating another interface. The node IDs should be used at the transport and higher layers fo
46、r replacing the conventional use of IP addresses at these layers. A node may have more than one node ID in use. NOTE Unless otherwise specified, the term “ID“ used in this Recommendation represents a node ID. 3.1.17 node name ITU-T Y.3032: A node name is a string of alphanumeric characters and symbo
47、ls that is used to uniquely identify the node. A node name, which may have variable length, is usually configured in such a way that it would be easier to be read and remembered by humans. NOTE Node names may also consist of human non-readable bit strings. 3.1.18 session b-ITU-T Y.2091: A temporary
48、telecommunications relationship among a group of objects in the service stratum that is assigned to collectively fulfil a task for a period of time. A session has a state that may change during its lifetime. Session-based telecommunications may, but need not be, assisted by intermediaries (see media
49、ted services). Session-based telecommunications can be one-to-one, one-to-many, many-to-one, or many-to-many. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 access component network: A component network that provides connectivity to user terminals is called an access component network. The access component network collects data traffic generated from the user terminals connected to it or delivers data traffic
