ITU-T Y 2055-2011 Framework of object mapping using IPv6 in next generation networks (Study Group 13)《在下一代网络中使用IPv6的对象映射的结构 13号研究组》.pdf

《ITU-T Y 2055-2011 Framework of object mapping using IPv6 in next generation networks (Study Group 13)《在下一代网络中使用IPv6的对象映射的结构 13号研究组》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Y 2055-2011 Framework of object mapping using IPv6 in next generation networks (Study Group 13)《在下一代网络中使用IPv6的对象映射的结构 13号研究组》.pdf（26页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T Y.2055TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2011) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Frameworks and functional architecture models Framework of object

2、mapping using IPv6 in next generation networks Recommendation ITU-T Y.2055 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.299 Ne

3、twork 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 Architecture

4、, 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.1999

5、 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.2099Quality 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 Numbering, na

6、ming and addressing Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Smart ubiquitous networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 Future networks Y.3000Y.3099 For furthe

7、r details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.2055 (03/2011) i Recommendation ITU-T Y.2055 Framework of object mapping using IPv6 in next generation networks Summary Recommendation ITU-T Y.2055 specifies the basic concept and requirements of object mapping using IPv6 in

8、next generation networks (NGN) in order to provide networking capabilities to objects. This Recommendation also describes the mapping architecture, the relationship between identifiers and the relevant mechanisms for object mapping. History Edition Recommendation Approval Study Group 1.0 ITU-T Y.205

9、5 2011-03-16 13 Keywords IPv6, mapping, NGN, object. ii Rec. ITU-T Y.2055 (03/2011) 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 Stand

10、ardization 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), wh

11、ich 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 Resolution 1. In some areas of information technology which fall within

12、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 and a recognized operating agency. Compliance with this Recommendat

13、ion 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 met. The words “shall“ or some other obligatory language such as “

14、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 RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation

15、 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 Recommendation development process. As of the date of approval of

16、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 information and are therefore strongly urged to consult the TSB patent d

17、atabase at http:/www.itu.int/ITU-T/ipr/. ITU 2012 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.2055 (03/2011) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defin

18、ed elsewhere 2 3.2 Terms defined in this Recommendation . 3 4 Abbreviations and acronyms 3 5 Conventions 4 6 Overview of object mapping using IPv6 in NGN 4 6.1 Classification of identifiers for object identification and mapping 4 6.2 Basic concept of object mapping 5 6.3 Requirements for object mapp

19、ing using IPv6 6 7 Mapping architecture and relationship between identities . 7 7.1 Mapping architecture between identifiers 7 7.2 Mapping relationships between identifiers . 8 8 Mechanisms for object mapping . 10 8.1 ID bindings in NGN architecture . 10 8.2 Object mapping mechanism . 10 9 Security

20、considerations . 11 Appendix I Examples of mapping between host and object(s) . 12 1 Host = Object (one-to-one mapping) 12 2 Host Object (one-to-many mapping) . 12 Appendix II Network attachment control faction (NACF) functional architecture 13 Appendix III Information flows of explicit binding and

21、implicit binding 14 Appendix IV Examples for services using object mapping 16 Bibliography. 17 Rec. ITU-T Y.2055 (03/2011) 1 Recommendation ITU-T Y.2055 Framework of object mapping using IPv6 in next generation networks 1 Scope This Recommendation describes the requirements and the mechanisms for ob

22、ject mapping using IPv6 in next generation networks (NGNs). This Recommendation covers the following: Basic concept and requirements of object mapping using IPv6; Mapping architecture and relationships between identifiers; Mechanisms for object mapping using IPv6. This Recommendation does not intend

23、 to develop any specific protocols for object mapping. As many new types of devices (i.e., objects) are connected to networks, this Recommendation assumes that IPv6 plays a key role in object-to-object communications. The objective of this Recommendation is to provide guidelines for mapping of infor

24、mation on objects for providing end-to-end connectivity in IPv6-based NGN. 2 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

25、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 edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recomme

26、ndations 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 G.805 Recommendation ITU-T G.805 (2000), Generic functional architecture of transport networks. ITU-T X.800 Recommendation ITU-T

27、X.800 (1991), Security architecture for Open Systems Interconnection for CCITT applications. ITU-T X.811 Recommendation ITU-T X.811 (1995) | ISO/IEC 10181-2:1996, Information technology Open Systems Interconnection Security frameworks for open systems: Authentication framework. ITU-T Y.1540 Recommen

28、dation ITU-T Y.1540 (2011), Internet protocol data communication service IP packet transfer and availability performance parameters. ITU-T Y.2001 Recommendation ITU-T Y.2001 (2004), General overview of NGN. ITU-T Y.2002 Recommendation ITU-T Y.2002 (2009), Overview of ubiquitous networking and of its

29、 support in NGN. 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.2014 Recommendation ITU-T Y.20

30、14 (2010), Network attachment control functions in next generation networks. ITU-T Y.2015 Recommendation ITU-T Y.2015 (2009), General requirements for ID/locator separation in NGN. 2 Rec. ITU-T Y.2055 (03/2011) ITU-T Y.2051 Recommendation ITU-T Y.2051 (2008), General overview of IPv6-based NGN. ITU-

31、T Y.2091 Recommendation ITU-T Y.2091 (2008), Terms and definitions for Next Generation Networks. ITU-T Y.2701 Recommendation ITU-T Y.2701 (2007), Security requirements for NGN release 1. ITU-T Y.2702 Recommendation ITU-T Y.2702 (2008), Authentication and authorization requirements for NGN release 1.

32、 ITU-T Y.2720 Recommendation ITU-T Y.2720 (2009), NGN identity management framework. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 address ITU-T Y.2091: An address is the identifier for a specific termination point and is used for rou

33、ting to this termination point. 3.1.2 authentication ITU-T X.811: Authentication provides assurance of the claimed identity of an entity. 3.1.3 authorization ITU-T X.800: The granting of rights, which includes the granting of access based on access rights. 3.1.4 binding ITU-T G.805: A direct relatio

34、nship between a “transport processing function“ or “transport entity“ and another “transport processing function“ or “transport entity“ which represents the static connectivity that cannot be directly modified by management action. 3.1.5 context ITU-T Y.2002: The information that can be used to char

35、acterize the environment of a user. NOTE Context information may include where the user is, what resources (devices, access points, noise level, bandwidth, etc.) are near the user, at what time the user is moving, interaction history between person and objects, etc. According to specific application

36、s, context information can be updated. 3.1.6 host ITU-T Y.1540: A computer that communicates using the Internet protocols. A host implements routing functions (i.e., it operates at the IP layer) and may implement additional functions including higher layer protocols (e.g., TCP in a source or destina

37、tion host) and lower layer protocols (e.g., ATM). 3.1.7 identifier 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/applications, or oth

38、er 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.8 identit

39、y ITU-T Y.2720: Information about an entity that is sufficient to identify that entity in a particular context. 3.1.9 ID/LOC separation ITU-T Y.2015: ID/LOC separation is decoupling the semantic of IP address into the semantics of node IDs and LOCs. Distinct namespaces are used for node IDs and LOCs

40、 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 LOCs due to mobility and multi-homing. Rec. ITU-T Y.2055 (03/2011) 3 NOTE In t

41、he context of this Recommendation, a completely new namespace for node IDs can optionally be created that would leave the IP address space more or less intact for LOCs, allowing routing technologies to be developed independently of end-host mobility and end-host multi-homing implications. 3.1.10 obj

42、ect ITU-T Y.2002: An intrinsic representation of an entity that is described at an appropriate level of abstraction in terms of its attributes and functions. NOTE 1 An object is characterized by its behaviour. An object is distinct from any other object. An object interacts with its environment incl

43、uding other objects at its interaction points. An object is informally said to perform functions and offer services (an object which makes a function available is said to offer a service). For modelling purposes, these functions and services are specified in terms of the behaviour of the object and

44、of its interfaces. An object can perform more than one function. A function can be performed by the cooperation of several objects. NOTE 2 Objects include terminal devices (e.g., used by a person to access the network such as mobile phones, Personal computers, etc.), remote monitoring devices (e.g.,

45、 cameras, sensors, etc.), information devices (e.g., content delivery server), products, contents, and resources. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 mapping: A technique for forming associations between logical and physical interfaces. 3.2

46、.2 object mapping: The process which an object identifier (object ID) is associated with an identifier (e.g., IPv6 address). 3.2.3 object ID: The identifier which identifies an object. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AM-FE Access Manage

47、ment Functional Entity AR-FE Access Relay Functional Entity ATM Asynchronous Transfer Mode DHCP Dynamic Host Configuration Protocol DNS Domain Name System EPC Electronic Product Code EUI Extended Unique Identifier GW Gateway ID Identifier IdM Identity Management IP Internet Protocol IT Information T

48、echnology LOC Locator MAC Medium Access Control NACF Network Attachment Control Function NAC-FE Network Access Configuration Functional Entity NGN Next Generation Network PoA Point of Attachment RA Router Advertisement RACF Resource Admission Control Function 4 Rec. ITU-T Y.2055 (03/2011) RS Router

49、Solicitation SCF Service Control function SCM Supply Chain Management TCP Transmission Control Protocol TLM-FE Transport Location Management Functional Entity URI Uniform Resource Identifier URL Uniform Resource Locator 5 Conventions In this Recommendation, the keyword “NGN“ indicates “IPv6-based NGN“ as per ITU-T Y.2051. In clause 6.3: The keywords “is required to“ indicate a requirement which must be strictly followed and from which no deviation is permitted, if