1、 International Telecommunication Union ITU-T Y.2016TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2009) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Frameworks and functional architecture models Functional requireme
2、nts and architecture of the NGN for applications and services using tag-based identification Recommendation ITU-T Y.2016 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Servi
3、ces, applications and middleware 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 Servi
4、ces and applications Y.1100Y.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 Ch
5、arging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 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
6、and networks in NGN Y.2250Y.2299 Numbering, naming and addressing Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Future networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 For
7、 further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.2016 (08/2009) i Recommendation ITU-T Y.2016 Functional requirements and architecture of the NGN for applications and services using tag-based identification Summary Recommendation ITU-T Y.2016 includes functional requ
8、irements and architecture of the NGN for the support of applications and services using tag-based identification. This Recommendation is based on the capabilities defined in Recommendation ITU-T Y.2213. Source Recommendation ITU-T Y.2016 was approved on 22 August 2009 by ITU-T Study Group 13 (2009-2
9、012) under Recommendation ITU-T A.8 procedures. Keywords ID tag, ID terminal, frameworks, functional architecture, identifier, RFID, tag-based identification. ii Rec. ITU-T Y.2016 (08/2009) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field
10、 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 Recommendations on them with a view to standardizin
11、g 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. The approval of ITU-T Recommendations is covered b
12、y 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 “Administration“ is used for conciseness to indicate b
13、oth 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 compliance with the Recommendation is achieved when
14、 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 Recommendation is required of any party. INTELLECTUAL PROPERTY
15、 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 claimed Intellectual Property Rights, whether asserted b
16、y 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 Recommendation. However, implementers are cautioned that t
17、his 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 2010 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. IT
18、U-T Y.2016 (08/2009) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 Functional requirements and functions of the NGN for applications and services using tag-based
19、identification . 4 6.1 NGN functional requirements 4 6.2 Functional architecture model 5 6.3 Functions to support applications and services using tag-based identification . 6 7 Functional architecture of the NGN for applications and services using tag-based identification . 9 7.1 Transport processin
20、g functional entities . 9 7.2 Transport control functional entities 10 7.3 Service control functional entities 10 7.4 Application support functions and service support functions 10 8 Security . 11 Appendix I Analysis of service requirements and network capabilities defined in ITU-T Y.2213 12 I.1 NGN
21、 service requirements of tag-based identification applications and services . 12 I.2 Non-NGN high level service requirements of tag-based identification applications and services 13 I.3 NGN requirements supported by extensions or additions of NGN Release 1 capabilities . 14 I.4 NGN requirements supp
22、orted by existing NGN Release 1 capabilities . 14 I.5 Non-NGN high level service requirements supported by NGN Release 1 capabilities 15 Appendix II High-level reference architecture of ID-based applications and services in the NGN 16 Appendix III Use-case example of applications using tag-based ide
23、ntification in the NGN 17 Appendix IV Traceability mechanism and referential information flows 19 IV.1 Traceability mechanism 19 IV.2 Information flows . 19 Bibliography. 21 Rec. ITU-T Y.2016 (08/2009) 1 Recommendation ITU-T Y.2016 Functional requirements and architecture of the NGN for applications
24、 and services using tag-based identification 1 Scope This Recommendation based on ITU-T Y.2012 covers extended features in order to support applications and services using tag-based identification in NGN. This Recommendation describes functional requirements, functional architecture and functional e
25、ntities in order to support the NGN service requirements and capabilities defined in ITU-T Y.2213. This Recommendation covers: Support of capabilities defined in ITU-T Y.2213 from an architectural viewpoint; Functional requirements of the NGN architecture to support applications and services using t
26、ag-based identification; Functional architecture and entities extensions for applications and services using tag-based identification in NGN. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this
27、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 edition of the Recommendations and other r
28、eferences 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 X.668 Recommendation ITU-T X.668 (2008) | ISO/IEC 9834-9:2008,
29、 Information technology Open Systems Interconnection Procedures for the operation of OSI Registration Authorities: Registration of object identifier arcs for applications and services using tag-based identification. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2006), Functional requirements and archite
30、cture of the NGN release 1. ITU-T Y.2213 Recommendation ITU-T Y.2213 (2008), NGN service requirements and capabilities for network aspects of applications and services using tag-based identification. ITU-T Y.2701 Recommendation ITU-T Y.2701 (2007), Security requirements for NGN release 1. 3 Definiti
31、ons 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 associated information ITU-T Y.2213: The information which is associated with an identifier. NOTE Example associated information instances are URL, URN, IP address, E.164 number, etc. 2 Rec. ITU-T Y
32、.2016 (08/2009) 3.1.2 forward identifier resolution ITU-T Y.2213: A function to resolve an identifier into an associated information. 3.1.3 ID tag ITU-T Y.2213: A physical object which stores one or more identifiers and optionally application data such as name, title, price, address, etc. NOTE It ma
33、y have a communication capability with an ID terminal depending on implementations. 3.1.4 ID terminal ITU-T Y.2213: A device with a data reading and optional writing capability which reads (and optionally writes) identifier(s) and optionally application data from/into an ID tag. NOTE The data readin
34、g (and optionally writing) capability depends on implementations. 3.1.5 identifier resolution ITU-T Y.2213: A function to resolve an identifier into associated information (see “Forward identifier resolution“) and vice versa (see “Reverse identifier resolution“). 3.1.6 reference point ITU-T Y.2012:
35、A conceptual point at the conjunction of two non-overlapping functional entities that can be used to identify the type of information passing between these functional entities. NOTE A reference point may or may not correspond to one or more physical interfaces between pieces of equipment. 3.1.7 reve
36、rse identifier resolution (or backward identifier resolution) ITU-T Y.2213: A function to resolve an associated information into a corresponding identifier. It is the reverse operation of the forward identifier resolution. 3.1.8 tag-based identification ITU-T Y.2213: The process of specifically iden
37、tifying a physical or logical object from other physical or logical objects by using identifiers stored on an ID tag. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 functional architecture: A set of functional entities used to describe the structure o
38、f an NGN. These functional entities are separated by reference points, and thus, they define the distribution of functions. The functional entities can be used to describe a set of reference configurations. These reference configurations identify which reference points are visible at the boundaries
39、of equipment implementations and between administrative domains. 3.2.2 functional entity: An entity that comprises a specific set of functions at a given location. Functional entities are logical concepts, while groupings of functional entities are used to describe practical and physical implementat
40、ions. 3.2.3 identifier: 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 other entities (e.g., physical or logical objects). Identifi
41、ers can be used for registration or authorization. NOTE Identifier can be either public to all networks, shared between a limited number of networks or private to a specific network (private identifiers are normally not disclosed to third parties). 4 Abbreviations and acronyms This Recommendation us
42、es the following abbreviations: ABG-FE Access Border Gateway Functional Entity AN-FE Access Node Functional Entity ANI Application Network Interface Rec. ITU-T Y.2016 (08/2009) 3 APL-SCM-FE Application Service Coordination Manager Functional Entity AS-FE Application Support Functional Entity B2B Bus
43、iness-to-Business B2C Business-to-Customer DB Data Base DNS Domain Name System EN-FE Edge Node Functional Entity FE Functional Entity IBG-FE Interconnection Border Gateway Functional Entity ID Identification IP Internet Protocol IRI Internationalized Resource Identifier LDAP Lightweight Directory Ac
44、cess Protocol NACF Network Attachment Control Functions NGN Next Generation Network NNI Network Node Interface OID Object Identifier PD-FE Policy Decision Functional Entity PII Personally Identifiable Information RACF Resource and Admission Control Functions RFID Radio Frequency Identification SAA-F
45、E Service Authentication and Authorization Functional Entity SUP-FE Service User Profile Functional Entity TRC-FE Transport Resource Control Functional Entity TTI Tag to Terminal Interface UNI User Network Interface URI Uniform Resource Identifier URL Uniform Resource Locator URN Uniform Resource Na
46、me XNI Any Network Interface 5 Conventions None. 4 Rec. ITU-T Y.2016 (08/2009) 6 Functional requirements and functions of the NGN for applications and services using tag-based identification 6.1 NGN functional requirements ITU-T Y.2012 describes the NGN architectural functions to support NGN Release
47、 1 services. In order to support applications and services using tag-based identification, NGN functions are required to be extended. Clause 8.1 of ITU-T Y.2213 requires that the following capabilities be supported by extension of the existing capabilities of NGN: Multi-identifier interpretation; Id
48、entifier resolution; Privacy management; Content distribution control; Device management; Profile management: User profile; Device profile. Quality of Service. In addition, the following capabilities are supported by the existing capabilities of NGN (see clause 8.2 of ITU-T Y.2213): Service quality
49、control; Location management. Appendix I of ITU-T Y.2213 also identifies non-NGN high-level service requirements which will not affect the existing functional capabilities of the NGN. Based upon the analysis of ITU-T Y.2213 service requirements and network capabilities (see Appendix I for further details), the following list can be supported by NGN functions and end-user functions. General requirements for identifiers: Identifiers validation suppo
