1、BS ISO/IEC 29161:2016 Information technology Data structure Unique identification for the Internet of Things BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06BS ISO/IEC 29161:2016 BRITISH STANDARD National foreword This British Standard is the UK implementation of IS
2、O/IEC 29161:2016. The UK participation in its preparation was entrusted to Technical Committee IST/34, Automatic identification and data capture techniques. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include
3、 all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2016. Published by BSI Standards Limited 2016 ISBN 978 0 580 81274 3 ICS 35.040 Compliance with a British Standard cannot confer immunity from legal obligations. This Bri
4、tish Standard was published under the authority of the Standards Policy and Strategy Committee on 31 August 2016. Amendments issued since publication Date Text affectedBS ISO/IEC 29161:2016 Information technology Data structure Unique identification for the Internet of Things Technologies de linform
5、ation Structure de donnes Identification unique pour lInternet des Objets INTERNATIONAL STANDARD ISO/IEC 29161 Reference number ISO/IEC 29161:2016(E) First edition 2016-08-01 ISO/IEC 2016 BS ISO/IEC 29161:2016ii ISO/IEC 2016 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2016, Published in
6、 Switzerland All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can
7、 be requested from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC 29161:2016(E)BS ISO/IEC 29161:2
8、016ISO/IEC 29161:2016(E)Foreword iv Introduction v 1 Scope . 1 2 Normative references 1 3 Terms and definitions . 1 4 Abbreviated terms 1 5 Identification of an “entity” . 2 5.1 General . 2 5.2 Overview of the “IoT Network” . 3 6 Unambiguous wrapper for unique identifiers in IoT applications 4 6.1 O
9、verview 4 6.2 URN schemes suitable for identification in IoT systems 5 6.2.1 Instances of URN schemes . 5 6.2.2 Listing of existing URN schemes referenced by this International Standard 6 6.3 URI usage in IoT systems . 6 7 Use of unique identification 7 7.1 UI concept 7 7.2 UI encoding 7 Annex A (in
10、formative) URI usage with ISO/IEC JTC 1/SC 31 standards . 8 Annex B (informative) OID wrappers and sensor networks .10 Annex C (informative) Identification Schemes possible to use in Networks .12 Annex D (informative) Ontology of Identification .13 Bibliography .15 ISO/IEC 2016 All rights reserved i
11、ii Contents PageBS ISO/IEC 29161:2016ISO/IEC 29161:2016(E) Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate i
12、n the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and no
13、n-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. The procedures used to develop this document and those intended for its further maintenance are described in the I
14、SO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attention is drawn to the possibility
15、that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list o
16、f patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressions related to conformit y assessment, as well
17、as information about ISOs adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following URL: www.iso.org/iso/foreword.html. The committee responsible for this document is ISO/IEC JTC 1, Information technology, Subcommittee SC 31, Automatic iden
18、tification and data capture techniques. iv ISO/IEC 2016 All rights reservedBS ISO/IEC 29161:2016ISO/IEC 29161:2016(E) Introduction In applications of the Internet of Things (IoT), one “thing” can communicate with other “things” via the Internet. For that “thing” to communicate, it should possess an
19、identifier of “which” it is. The ISO/IEC 15459- series does a good job identifying how groups that have been assigned an issuing agency code can create a character-based system of unique identification. There is no shortage of claimants to provide that identifier. Each is understandable due to its o
20、rigins and the perspective from which it comes. The Internet is a network and groups such as the International Telecommunications Union (ITU) and the Internet Engineering Task Force (IETF) view this identifier as a mechanism to facilitate network routing. ITU- T X.668 | ISO/IEC 9834-9 and ITU- T X.6
21、60 | ISO/IEC 9834- 1 attempt to fill this need from a network perspective. From a network perspective, it is accepted that the identification of an entity must resolve to an IP address for contacting it, whether its domain name “hangs” from an OID root using an OID resolver, or from a more general D
22、NS node (which may end up as the same thing). However, not everything is viewed from the perspective of the network, nor necessarily should it so be viewed. The network is a transport mechanism and the entities themselves have historic identifiers, which have their genesis from supply chain applicat
23、ions and identification. Ultimately, the various forms of unique identification identified within this International Standard need to be combined in a single message in an unambiguous form. This International Standard provides a method enabling this combination in an unambiguous form. ISO/IEC 2016 A
24、ll rights reserved vBS ISO/IEC 29161:2016BS ISO/IEC 29161:2016Information technology Data structure Unique identification for the Internet of Things 1 Scope This International Standard establishes a unique identification scheme for the Internet of Things (IoT), based on existing and evolving data st
25、ructures. This International Standard specifies the common rules applicable for unique identification that are required to ensure full compatibility across different identities. The unique identification is a universal construct for any physical object, virtual object, or person. It is used in IoT i
26、nformation systems that need to track or otherwise refer to entities. It is intended for use with any IoT media. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the
27、edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. There are no normative references in this document. 3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/IEC 19762 and the fol
28、lowing apply. 3.1 coap constrained application protocol SOURCE: RFC 7252 3.2 entity any concrete or abstract thing of interest, including associations among things SOURCE: ISO/PAS 16917 Note 1 to entry: Information also provided in Annex D. 3.3 rest representational state transfer 4 Abbreviated term
29、s 2D 2 Dimensional AIDC Automatic Identification and Data Capture IC Integrated Circuit IoT Internet of Things INTERNATIONAL ST ANDARD ISO/IEC 29161:2016(E) ISO/IEC 2016 All rights reserved 1BS ISO/IEC 29161:2016ISO/IEC 29161:2016(E) IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6
30、MAC Media Access Control RF Radio Frequency RFID Radio Frequency Identification URI Uniform Resource Identifier URL Uniform Resource Locator URN Uniform Resource Name XMPP Extensible Messaging and Presence Protocol 5 Identification of an “entity” 5.1 General For the purpose of this International Sta
31、ndard, the term “thing” considers the following as synonyms; “item”, “object” and “entity”. A thing may be a person, object, or location; see also Annex D. When one considers the Internet of Things (IoT), the definition of the “thing” is most often coloured by the perspective of the person undertaki
32、ng the consideration. If one is coming from the world of sensors, the IoT is simply an expansion of a sensor network. If one is coming from the world of RFID, the IoT is simply an expansion of an RFID infrastructure. If one is coming from the world of geospatial data, the IoT is simply an expansion
33、of a location-based network. If one is coming from the world of telecommunications, the IoT is simply an expansion of a telecommunications network. In truth, all are correct. Figure 2 shows some of the possible iterations of “things” that would be possible to connect through the IoT, using various e
34、xisting communication interfaces. Of course, there are other possibilities and these iterations of IoT might actually be combined, e.g. a mobile phone reading a 2D symbol, an RF tag, or a wireless IC device. Figure 1 IoT everything possible being connected2 ISO/IEC 2016 All rights reservedBS ISO/IEC
35、 29161:2016ISO/IEC 29161:2016(E) A single transaction may need to capture several identities as it progresses from origin to destination (and return). For example, there may exist a need to capture, each time a transaction is recorded, the following: item identification; sensor identification; node
36、identification; gateway identification; target resource identification; location of data capture, if mobile; time of data capture; identification of the individual; As a virtual thing, software, or software content, ISO/IEC 8824-1:2015, 3.8.52 defines an “object” as A well-defined piece of informati
37、on, definition, or specification which requires a name in order to identify its use in an instance of communication. An object is an abstraction or simulation of physical things such as people (“people” are included in this definition of object only to be true to the quote, whereas this Internationa
38、l Standard discriminates between people, objects, and locations) and machines or intangible things such as events and processes that captures their characteristics and behaviour. Something you can do things to. An object has state, behaviour, and identity; the structure and behaviour of similar obje
39、cts are defined in their common class. 64 The following are properties that may characterize a thing: a) Identity: the property of an entity that distinguishes it from other entities; b) Type: describes the type of entity; c) Data: describes if and how persons, locations and/or other entities can be
40、 tied to the entity; d) Behaviour: describes the methods in the locations interface by which the location can be used. 5.2 Overview of the “IoT Network” The Internet of Things (IoT) network aims to enable almost everything to communicate with each other, being connected using various communication i
41、nterfaces and protocols like IPv4, IPv6, MAC addresses, CoAP/REST, XMPP, etc. Prerequisite for the IoT network is the possibility to tie various information to the right thing for a given purpose using unambiguous identities to which specified information is tied which is then exchanged using applic
42、ation defined protocols. ISO/IEC 2016 All rights reserved 3BS ISO/IEC 29161:2016ISO/IEC 29161:2016(E) Figure 2 Possible information exchange using IoT Figure 2 shows an example where the items positions in a minibar in a hotel room are defined and monitored using sensing techniques. When an item is
43、removed, it is automatically sensed and information is sent so it is registered as being removed. The item will then be added as purchased and the price added to the room bill, to be paid at check out. Received information will also trigger refilling of minibar with the removed item. The scenario ab
44、ove requires that everything is possible to be uniquely identified, for which this International Standard is to provide a method for adding a wrapper to already existing identification schemes. 6 Unambiguous wrapper for unique identifiers in IoT applications 6.1 Overview Each form of unique identifi
45、cation stands on its own within the context of applications within that specific identifications domain. When one travels outside of that closed system, an open system form of the identification is required. The nature of the Internet of Things (IoT) is for people and objects to communicate with one
46、 and the other. This means that the unique identification scheme will need to accommodate established forms of identification. For the purposes of this International Standard, the “unambiguous wrapper” for identifiers used in IoT communications shall be a Uniform Resource Identifier (URI) defined by
47、 IETF, in RFC 3986. URIs are traditionally classified as either a Uniform Resource Locator (URL, using a string starting with “http:/”) denoting a web resource, or a Uniform Resource Name (URN, using a string starting with “urn:”) as defined in RFC 2141. In both cases, the URI is a text string from
48、a limited subset of US ASCII (for maximum portability across systems). The URI syntax is organized hierarchically, with components listed in order of decreasing significance from left to right. Other structures were considered, but the URI structure is widely accepted and extensively used with today
49、s AIDC data carriers, while providing the flexibility of a broader implementation. This International Standard is primarily concerned with supporting the interoperable use of Identification schemes from different domains, using existing URNs as needed to provide this interoperability in an efficient manner. Although URLs will also be used extensively in IoT applications, no special treatment of them is required for interoperability, and so this International Standard
