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.4805 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2017) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Internet of things and s
2、mart cities and communities Identification and security Identifier service requirements for the interoperability of smart city applications Recommendation ITU-T Y.4805 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF T
3、HINGS AND SMART CITIES GLOBAL INFORMATION INFRASTRUCTURE 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
4、.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS 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
5、Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over 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 an
6、d service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.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 Genera
7、lized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Y.4000Y.4049 Definitions and terminologies Y.4050Y.4099 Requirements and use cases Y.4100Y.4249 Infrastructure
8、, connectivity and networks Y.4250Y.4399 Frameworks, architectures and protocols Y.4400Y.4549 Services, applications, computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 Evaluation and assessment Y.4900Y.4999 For furt
9、her details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.4805 (08/2017) i Recommendation ITU-T Y.4805 Identifier service requirements for the interoperability of smart city applications Summary Recommendation ITU-T Y.4805 specifies a set of requirements for identifier services in
10、 smart city applications with a view to ensure that such systems are interoperable and secure. This set of requirements may additionally serve as guidelines for developing new identifier services for smart cities. It includes security features for service integrity and data confidentiality. The Reco
11、mmendation defines a full list of identifier service requirements, including security requirements, for the identifier service. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.4805 2017-08-22 20 11.1002/1000/13267 Keywords Data confidentiality, identifier, service integrit
12、y, smart city. * 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.4805 (08/2017) FOREWORD The International Telecommunication
13、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 technical, operating and tariff question
14、s 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 turn, produce Recommendations on
15、 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. NOTE In this Recommendation, the
16、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, e.g., interoperability or appl
17、icability) 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 not suggest that compliance with
18、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 the evidence, validity or applicab
19、ility 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, which may be required to implemen
20、t 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 2017 All rights reserved. No part of this publication may be reproduced, by any means
21、 whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.4805 (08/2017) 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 Conventions 2 6 Identifier service
22、s for smart city applications . 2 6.1 Service model . 2 6.2 Data model 3 6.3 Operation model . 3 7 Requirements for identifier services in smart city applications 3 7.1 General identifier service requirements 3 7.2 General security requirements 4 7.3 Requirements related to the service model . 5 7.4
23、 Requirements of data model . 6 7.5 Requirements of operation model 7 Bibliography. 8 Rec. ITU-T Y.4805 (08/2017) 1 Recommendation ITU-T Y.4805 Identifier service requirements for the interoperability of smart city applications 1 Scope This Recommendation specifies a set of requirements for identifi
24、er services in smart city applications with a view to ensure that such systems are interoperable and secure. This set of requirements may additionally serve as guidelines for developing new identifier services for smart cities. The Recommendation includes security features for service integrity and
25、data confidentiality. The Recommendation defines a full list of identifier service requirements, including security requirements, for the identifier service. 2 References None. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 application
26、 b-ITU-T Y.2261: A structured set of capabilities, which provide value-added functionality supported by one or more services, which may be supported by an API interface. 3.1.2 identifier b-ITU-T Y.2091: An identifier is a series of digits, characters and symbols or any other form of data used to ide
27、ntify 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. They can be either public to all networks, shared between a limited nu
28、mber of networks or private to a specific network (private IDs are normally not disclosed to third parties). 3.1.3 identifier resolution b-ITU-T Y.4108: A function to resolve an identifier into associated information and vice versa. 3.1.4 Internet of things (IoT) b-ITU-T Y.4000: A global infrastruct
29、ure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on existing and evolving interoperable information and communication technologies. NOTE 1 Through the exploitation of identification, data capture, processing and communication capabili
30、ties, the IoT makes full use of things to offer services to all kinds of applications, whilst ensuring that security and privacy requirements are fulfilled. NOTE 2 From a broader perspective, the IoT can be perceived as a vision with technological and societal implications. 3.1.5 interoperability b-
31、ITU-T Y.101: The ability of two or more systems or applications to exchange information and to mutually use the information that has been exchanged. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 identifier administration: The ability to carry out fun
32、ctions to support life-cycle management of identifiers and identifier attributes. These functions include the registration of new identifiers, the removal of existing identifier, the amendment and update of any information 2 Rec. ITU-T Y.4805 (08/2017) associated with the identifier and any other re
33、lated administrative functions as defined within a specific identifier scheme as per definition 3.1.2 above. 3.2.2 identifier service: A network information service operated over the Internet which carries out identifier resolution as per definition 3.1.3 and identifier administration as per definit
34、ion 3.2.1 above. 3.2.3 root service of identifier service: A root service is the key component at the apex of a hierarchical identifier or naming service. For example, DNS defines its root service as the collection of root name servers and data at the apex of the Internet naming system. 4 Abbreviati
35、ons and acronyms This Recommendation uses the following abbreviations and acronyms: ID Identifier IoT Internet of Things TTL Time-To-Live UTF-8 8-bit Unicode Transformation Format 5 Conventions The keywords “is required to“ indicate a requirement which must be strictly followed and from which no dev
36、iation is permitted if conformance to this Recommendation is to be claimed. The keywords “is recommended“ indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance. The keywords “can optionally“ indicate an option
37、al requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendors implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optiona
38、lly provide the feature and still claim conformance with the specification. In this Recommendation and its annexes, the words shall, shall not, should, and may sometimes appear, in which case they are to be interpreted, respectively, as is required to, is prohibited from, is recommended, and can opt
39、ionally. The appearance of such phrases or keywords in an appendix or in material explicitly marked as informative are to be interpreted as having no normative intent. 6 Identifier services for smart city applications Identifier (ID) services for smart city applications are discussed in terms of its
40、 service, data and operation models. The service model explores the service structure of the identifier service to better support smart city applications, including its service components and the relationship among these components. The data model defines necessary data structure that will be needed
41、 to support identifier attributes in smart city applications, as well as to security and management operations upon identifiers and identifier attributes. The operation model discusses essential operations that should be provided by the identifier service, as well as crucial features to allow cohesi
42、ve, transparent and trustworthy operations among different identifier service components, as appropriate. 6.1 Service model The identifier service for smart city applications must support applications operated from different cities, and managed by different organizations and/or service providers. A
43、distributed service model can enable such identifier service. Rec. ITU-T Y.4805 (08/2017) 3 The service model of the identifier service refers to the service structure of the identifier service, in terms of its service components, under a distributed networking environment. The identifier service fo
44、r smart city applications may consist of many service components, where each one is managed by different organizations and/or service providers. Each component of the identifier service may be responsible for a local domain of identifiers used in smart city applications. These service components mus
45、t work cooperatively to allow identification of any smart city entity in terms of a global unique identifier, and to allow resolution and real-time update of information associated with the identifier. On the other hand, a service component of the identifier service may be operated and managed by in
46、dividual organizations independently from others. Any disruption of one component should not disrupt the service from other components. Administration of identifier and identifier information may be performed by an individual identifier service component, without reliance on the others. 6.2 Data mod
47、el The data model of the identifier service refers to data structures necessary to support resolution and administration of its identifiers. The data structure should be flexible enough to support existing smart city applications, and to allow backward compatibility. An identifier in the smart city
48、identifier service not only provides identification of the smart city entity, but also serves as a reference to information associated to the identified subject. The data model of the identifier service should define a data structure that allows all data types to be associated with the identifier. I
49、t should also define common mechanisms that allow trust and/or credentials to be established over the information associated with the identifier, so that users can validate the information as needed. 6.3 Operation model The operation model of the identifier service refers to the essential operations that should be provided by the identifier service to support smart city applications, as well as how these operations should be carried out by the identifier service. The operation model should also define crucial features t
