1、 International Telecommunication Union ITU-T Y.2213TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (09/2008) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Service aspects: Service capabilities and service architecture NGN
2、 service requirements and capabilities for network aspects of applications and services using tag-based identification Recommendation ITU-T Y.2213 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTUR
3、E General Y.100Y.199 Services, 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
4、General Y.1000Y.1099 Services 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 m
5、aintenance Y.1700Y.1799 Charging Y.1800Y.1899 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
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 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 For further details, please refer to the list of ITU-T Recommendations. Rec.
7、 ITU-T Y.2213 (09/2008) i Recommendation ITU-T Y.2213 NGN service requirements and capabilities for network aspects of applications and services using tag-based identification Summary Recommendation ITU-T Y.2213 describes high-level service requirements and NGN capability requirements needed to supp
8、ort applications and services using tag-based identification. Several examples of applications and services using tag-based identification are also described with scenarios. The scope of this Recommendation is limited to applications and services using tag-based identification and they are distingui
9、shed by the following three mandatory elements: ID tag, ID terminal and identifier. Source Recommendation ITU-T Y.2213 was approved on 12 September 2008 by ITU-T Study Group 13 (2005-2008) under Recommendation ITU-T A.8 procedure. Keywords Bar code, capabilities, capability requirements, ID tag, ID
10、terminal, identifier, identifier resolution, RFID, service requirements and tag-based identification. ii Rec. ITU-T Y.2213 (09/2008) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication tec
11、hnologies (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 basis. The World Tele
12、communication 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 Resolution 1. In some a
13、reas 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 and a recognized o
14、perating 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 met. The words “sh
15、all“ 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 RIGHTS ITU draws attention to the possibility that the p
16、ractice 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 Recommendation dev
17、elopment 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 information and are ther
18、efore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2009 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.2213 (09/2008) iii CONTENTS Page 1 Scope 1 2 Refere
19、nces. 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation. 2 4 Abbreviations and acronyms 3 5 Conventions 4 6 Tag-based identification applications and services description and high-level reference service architecture . 4 6.1 Basic characteristics of tag-based i
20、dentification applications and services . 4 6.2 Impact of tag-based identification applications and services on the network. 5 6.3 Reference service architecture model. 5 7 Service requirements of tag-based identification applications and services 6 7.1 Multi-identifier interpretation requirements.
21、6 7.2 Identifier resolution 6 7.3 ID terminal and ID tag management 7 7.4 Content distribution control 7 7.5 Privacy management 7 7.6 Location-based services support. 8 7.7 Service quality control 8 7.8 Application transaction and traffic requirements . 8 8 NGN capabilities for tag-based identificat
22、ion applications and services . 8 8.1 Requirements for extensions or additions to NGN release 1 capabilities 9 8.2 Requirements supported by existing NGN release 1 capabilities 10 Appendix I Non-NGN high-level service requirements . 11 I.1 General requirements for identifiers. 11 I.2 Requirements fo
23、r identification of identifier schemes . 11 I.3 Requirements related to application data encoding 11 I.4 Requirements for identification service interworking 12 I.5 Requirements for location information management. 12 I.6 Requirements related to management of application mobility. 12 I.7 Requirement
24、s related to traceability. 12 I.8 Requirements related to identifier filtering 13 Appendix II Classification of tag-based identification applications and services 14 II.1 Overview of tag-based identification applications and services 14 II.2 Classification of tag-based identification applications an
25、d services 15 II.3 Examples of tag-based identification applications and services 15 iv Rec. ITU-T Y.2213 (09/2008) Page II.4 Evaluation of tag-based identification applications and services. 16 Appendix III Example scenarios of tag-based identification applications and services. 20 III.1 Closed-dom
26、ain tag-based identification applications and services 20 III.2 B2B tag-based identification applications and services . 21 III.3 B2C tag-based identification applications and services . 22 III.4 B2B2C tag-based identification applications and services 23 III.5 C2C tag-based identification applicati
27、ons and services . 24 Bibliography 25 Rec. ITU-T Y.2213 (09/2008) v Introduction Numerous applications have already incorporated identifiers to support differentiated services, where identifiers are mainly used for logical identification. Emerging applications, whose examples are described in Append
28、ices II and III, require also that logical identification be associated with physical objects. This Recommendation expects that a relationship between physical and logical objects is maintained and assumes that applications and services using tag-based identification are based on such a relationship
29、. This relationship makes a wide variety of business opportunities available: for example, passport numbers may be applied to physical objects for identification and each physical object, i.e., passport, may be associated with a logical object such as a text content, application program, mobile exec
30、utable code, or data record. Applications and services using tag-based identification adopted and deployed widely in various business fields have used identifiers as a means for identifying physical and logical objects. Consequently, their market volume is being expanded dramatically. In addition to
31、 use cases of identifier in business fields, physical and logical objects with an identifier can enable applications and services using tag-based identification in consumer fields as well. Existing applications and services using tag-based identification have been exploited in business-to-business (
32、B2B) fields, but currently they are expanding to business-to-consumer (B2C) and business-to-business-to-consumer (B2B2C) fields as shown in clause II.3. Both B2B and B2C/B2B2C tag-based identification applications and services basically have similar service requirements. Additionally, B2C/B2B2C-spec
33、ific service requirements and related challenges for NGN are also examined in this Recommendation, such as privacy management, identifier resolution, management, etc. Identifier information in such applications and services using tag-based identification works as the key information used to retrieve
34、 related contents, execute certain application programs, point to a specific information resource, make an association with a specific object, and so on. The identification feature supporting hyperlink-like access will enable NGN applications and services to be performed and provided to consumers in
35、 easier and more convenient ways. For example, consumers do not have to type a URL in a phone user interface because the tag-based identification supports that automatically. Since a number of applications and services using tag-based identification are expected to be deployed widely in NGN, the NGN
36、 architecture framework and the NGN functional entities have to support them. Rec. ITU-T Y.2213 (09/2008) 1 Recommendation ITU-T Y.2213 NGN service requirements and capabilities for network aspects of applications and services using tag-based identification 1 Scope This Recommendation covers extensi
37、ons to NGN release 1 capabilities in order to support tag-based identification applications and services in the NGN environment and builds upon b-ITU-T Y.Sup1 and ITU-T Y.2201. The scope of this Recommendation is limited to tag-based identification applications and services distinguished by the foll
38、owing three mandatory elements: ID tag, ID terminal and Identifier. These applications and/or services use identifiers only read from ID tags by ID terminals. This Recommendation covers: description and scope of tag-based identification applications and services with some example scenarios; high-lev
39、el service requirements of tag-based identification applications and services; and extended or new NGN capabilities based on the high-level service requirements. Functional requirements and related NGN architecture extensions for support of the described capabilities are out of scope of this Recomme
40、ndation. 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 were valid. All Recommendations and other references are subject t
41、o 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 Recommendations is regularly published. The reference to a document withi
42、n 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, Information technology Open Systems Interconnection Procedures for the operation of OSI Registration Authorities: Registration of ob
43、ject identifier arcs for applications and services using tag-based identification. ITU-T Y.2201 Recommendation ITU-T Y.2201 (2007), NGN release 1 requirements. ITU-T Y.2701 Recommendation ITU-T Y.2701 (2007), Security requirements for NGN release 1. 3 Definitions 3.1 Terms defined elsewhere This Rec
44、ommendation uses the following terms defined elsewhere: 3.1.1 application network interface (ANI) b-ITU-T Y.2012: Interface which provides a channel for interactions and exchanges between applications and NGN elements. The ANI offers capabilities and resources needed for realization of applications.
45、 3.1.2 end user b-ITU-T M.3050.1: The actual user of the products or services offered by the enterprise. The end user consumes the product or service. 2 Rec. ITU-T Y.2213 (09/2008) 3.1.3 identifier b-ITU-T Y.2091: A series of digits, characters and symbols or any other form of data used to identify
46、subscriber(s), user(s), network element(s), function(s), network entity(ies) providing services/applications, or other entities (e.g., physical or logical objects). Identifiers can be used for registration or authorization. NOTE Identifiers can be either public to all networks, shared between a limi
47、ted number of networks or private to a specific network (private identifiers are normally not disclosed to third parties). 3.1.4 name b-ITU-T Y.2091: The identifier of an entity (e.g., subscriber, network element) that may be resolved/translated into an address. 3.1.5 service b-ITU-T Z.100: A set of
48、 functions and facilities offered to a user by a provider. 3.1.6 user b-ITU-T Y.2091: It can be an end user, a person, a subscriber, a system, an equipment, a terminal (e.g., FAX, PC), a (functional) entity, a process, an application, a provider, or a corporate network. 3.2 Terms defined in this Rec
49、ommendation This Recommendation defines the following terms: 3.2.1 associated information: The information which is associated with an identifier. NOTE Example associated information instances are URL, URN, IP address, E.164 number, etc. 3.2.2 B2B tag-based identification applications and services: This term refers to tag-based identification applications and services based on business relationships which involve exchanges of identification information between business partners. 3.2.3 B2B2C tag-based identification appli
