BS ISO IEC 29178-2012 Information technology Mobile item identification and management Service broker for Mobile AIDC services《信息技术 移动物品识别和管理 移动自动识别和数据采集(AIDC)服务项目用服务代理》.pdf

《BS ISO IEC 29178-2012 Information technology Mobile item identification and management Service broker for Mobile AIDC services《信息技术 移动物品识别和管理 移动自动识别和数据采集(AIDC)服务项目用服务代理》.pdf》由会员分享，可在线阅读，更多相关《BS ISO IEC 29178-2012 Information technology Mobile item identification and management Service broker for Mobile AIDC services《信息技术 移动物品识别和管理 移动自动识别和数据采集(AIDC)服务项目用服务代理》.pdf（20页珍藏版）》请在麦多课文档分享上搜索。

1、raising standards worldwide NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW BSI Standards Publication Information technology Mobile item identification and management Service broker for Mobile AIDC services BS ISO/IEC 29178:2012National foreword This British Standard is the UK

2、 implementation of ISO/IEC 29178:2012. 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 n

3、ot purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2012 Published by BSI Standards Limited 2012 ISBN 978 0 580 81103 6 ICS 35.040 Compliance with a British Standard cannot confer immunity from legal o

4、bligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 November 2012. Amendments issued since publication Amd. No. Date Text affected BRITISH STANDARD BS ISO/IEC 29178:2012 Reference number ISO/IEC 29178:2012(E) ISO/IEC 2012INTERNATIO

5、NAL STANDARD ISO/IEC 29178 First edition 2012-05-01Information technology Mobile item identification and management Service broker for Mobile AIDC services Technologies de linformation Gestion et identification dlment mobile Courtier en service pour services AIDC mobiles BS ISO/IEC 29178:2012ISO/IEC

6、 29178:2012(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either I

7、SO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2012 All rights reservedBS ISO/IEC 29178:2012IS

8、O/IEC 29178:2012(E) ISO/IEC 2012 All rights reserved iiiContents Page Foreword iv Introduction . v 1 Scope 1 2 Normative references 1 3 Terms and definitions . 1 4 Symbols (and abbreviated terms) 2 5 Overview of Mobile AIDC service architecture . 2 5.1 Generic architecture 2 5.2 Service broker-assis

9、ted architecture 3 6 Functions of service broker . 5 6.1 MII recognition . 5 6.2 MII resolution . 5 6.3 Service control . 5 7 Interfaces for service broker 6 7.1 Mobile AIDC terminal Service broker . 6 7.2 Service broker ODS 9 7.3 Service broker ORS 9 Annex A (informative) Example of interfaces . 10

10、 BS ISO/IEC 29178:2012ISO/IEC 29178:2012(E) iv ISO/IEC 2012 All rights reservedForeword 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

11、or IEC participate in 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,

12、 governmental and non-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. International Standards are drafted in accordance with the rules given in the ISO/IEC Directiv

13、es, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the na

14、tional bodies casting a vote. Attention is drawn to the possibility 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. ISO/IEC 29178 was prepared by Joint Technical Committee ISO/IEC

15、 JTC 1, Information technology, Subcommittee SC 31, Automatic identification and data capture techniques. BS ISO/IEC 29178:2012ISO/IEC 29178:2012(E) ISO/IEC 2012 All rights reserved vIntroduction Mobile AIDC is a version of the AIDC technology that is combined with mobile communications. A Mobile AI

16、DC terminal is a mobile phone that has one or more types of embedded AIDC device functions. It accesses AIDC media (e.g., labels, tags, etc.) information in the same manner as existing AIDC devices. In a typical Mobile AIDC service architecture, Mobile AIDC terminal gets the location information of

17、information content which is associated with Mobile Item Identifier (MII) stored in AIDC media through MII resolution process with Object Directory Service (ODS) directly. The information content provided by content provider may not be guaranteed to be adequate to the Mobile AIDC terminal in terms o

18、f capabilities of terminal or service policy of service provider. If the information content is not suitable to the Mobile AIDC terminal, the information content cannot be used in the Mobile AIDC terminal. For preventing this situation, a service broker can be applied optionally to a typical Mobile

19、AIDC service architecture to enforce service policies on Mobile AIDC information content. By a service broker, MII recognition and resolution related functions are performed in a service broker, which improves the functionality and efficiency over a Mobile AIDC terminal that includes these functions

20、. This International Standard specifies the functions of a service broker and the interface between Mobile AIDC terminals and a service broker. There are alternative techniques to meet the use case addressed by this International Standard. One of those techniques is to use EPC and ONS. Further infor

21、mation on this technique can be obtained from GS1. BS ISO/IEC 29178:2012INTERNATIONAL STANDARD ISO/IEC 29178:2012(E) ISO/IEC 2012 All rights reserved 1Information technology Mobile item identification and management Service broker for Mobile AIDC services 1 Scope This International Standard defines

22、the functions of a service broker supporting service control, MII recognition and MII resolution related functions in Mobile AIDC service architecture that uses MII (ISO/IEC 29174) as an identifier. For the use of a service broker by a Mobile AIDC terminal, definition is required of the interface be

23、tween a terminal and a service broker. This International Standard describes that interface. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edit

24、ion of the referenced document (including any amendments) applies. ISO/IEC 19762 (all parts), Information technology Automatic identification and data capture (AIDC) techniques Harmonized vocabulary ISO/IEC 18000-6, Information technology Radio frequency identification for item management Part 6: Pa

25、rameters for air interface communications at 860 MHz to 960 MHz ISO/IEC 29143, Information technology Automatic identification and data capture techniques Air interface specification for Mobile RFID interrogators ISO/IEC 29168-1, Information technology Open systems interconnection Object identifier

26、resolution system (ORS) ISO/IEC 29172, Information technology Mobile item identification and management Reference architecture for Mobile AIDC services ISO/IEC 29174 (all parts), Information technology UII scheme and encoding format for Mobile AIDC services ISO/IEC 29177, Information technology Auto

27、matic identification and data capture technique Identifier resolution protocol for multimedia information access triggered by tag-based identification 3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/IEC 19762, ISO/IEC 29168-1, ISO/IEC 29172, ISO/IEC

28、29174, ISO/IEC 29177, and the following apply. 3.1 MII recognition process that recognizes the type of the MII stored in an RFID tag or in a bar code or two-dimensional symbol on a label BS ISO/IEC 29178:2012ISO/IEC 29178:2012(E) 2 ISO/IEC 2012 All rights reserved3.2 MII resolution process of conver

29、ting an MII into its associated information by means of Object Directory Service (ODS) 4 Symbols (and abbreviated terms) AIDC Automatic Identification and Data Capture DNS Domain Name System DSFID Data Storage Format Identifier FQDN Fully Qualified Domain Name MII Mobile Item Identifier NAPTR Naming

30、 Authority Pointer ODS Object Directory Service OID Object Identifier ORM Optically Readable Media ORS Object identifier Resolution System URL Uniform Resource Locator XML Extensible Markup Language 5 Overview of Mobile AIDC service architecture 5.1 Generic architecture According to ISO/IEC 29172, g

31、eneric service architecture can be illustrated as Figure 1. An RFID tag or ORM can be attached to a physical object and one or more Mobile AIDC device(s) are built into the Mobile AIDC terminal. A content provider maintains the information content associated with the object. ODS manages the access i

32、nformation to retrieve the information content identified by the MII where the access information is usually represented as a URI. Figure 1 Generic service architecture BS ISO/IEC 29178:2012ISO/IEC 29178:2012(E) ISO/IEC 2012 All rights reserved 3Figure 2 shows the service procedures based on generic

33、 service architecture. The Mobile AIDC terminal reads the Mobile Item Identifier (MII) which is defined as ISO/IEC 29174 from the data carrier and performs MII recognition. For the purposes of this document, the term MII is intended to mean the unique item identifier that appears on Memory Bank “01

34、2 ” of RFID tag conforming to ISO/IEC 29143 or ISO/IEC 18000-6C or encoded in optically readable media as a serialized item. The MII appears in an RFID tag as the content of Memory Bank “01 2 ” and in ORM traditionally shown with a data identifier of “25S”. Once the MII is recognized in the Mobile A

35、IDC terminal, the Mobile AIDC terminal sends an MII resolution request to the Object Directory Service (ODS). The ODS performs MII resolution and returns an MII resolution result. MII resolution protocol is defined in ISO/IEC 29177 and the detailed MII resolution protocol follows ISO/IEC 29177. This

36、 MII resolution result includes the locations of the associated information of the MII that the Mobile AIDC terminal read from the data carrier. The Mobile AIDC terminal then chooses the associated information from the results. Figure 2 Generic service procedure In this service procedure, informatio

37、n content that Mobile AIDC terminal tries to access can be uncontrolled service. This means that the target content may not be adequate to the Mobile AIDC terminal in terms of capabilities of terminal or service policy of service provider. In that case, the Mobile AIDC terminal cannot use the chosen

38、 service. 5.2 Service broker-assisted architecture As explained in 4.1, a Mobile AIDC terminal is required to send the MII resolution request directly to ODS and get MII resolution result from ODS. In this case, service control such as service filtering is not applied to information content because

39、the Mobile AIDC terminal acquires the location of information content directly from ODS. For providing service control and simplicity of Mobile AIDC terminals functions, MII recognition and MII resolution related functions are performed in a service broker. In a service broker-assisted architecture,

40、 the Mobile AIDC terminal has only to read the MII from the data carrier and pass the MII to a service broker. Then a service broker performs the MII recognition and the MII resolution. Figure 3 below depicts a service broker-assisted Mobile AIDC service architecture. BS ISO/IEC 29178:2012ISO/IEC 29

41、178:2012(E) 4 ISO/IEC 2012 All rights reservedFigure 3 Service broker-assisted architecture In a service broker-assisted architecture, a Mobile AIDC terminal is connected to a service broker. A service broker processes the MII recognition and sends the MII resolution request to ODS. Multiple service

42、 brokers may exist and the selection of service broker depends on the users preference. Figure 4 Service broker-assisted service procedures (in case of HTTP as an access protocol to contents server) BS ISO/IEC 29178:2012ISO/IEC 29178:2012(E) ISO/IEC 2012 All rights reserved 5In Figure 4, the Mobile

43、AIDC terminal reads the MII from the data carrier and passes the MII to a service broker using the interface in clause 7.1.1. A service broker recognizes the MII and sends MII resolution request to ODS using the interface in clause 6.2.2. ODS performs the MII resolution process and returns the MII r

44、esolution result with the interface in clause 6.2.3. This MII resolution result includes the locations of the associated information of the MII including the access protocol to the locations. However, if a service broker fails to recognize the OID for MII or OID for other identifier schemes, a servi

45、ce broker sends the OID resolution request to ORS using the interface in clause 7.3.1 for resolving the OID which is defined in ISO/IEC 29168-1. ISO/IEC 29168-1 describes OID resolution process as follows: The general OID resolution process uses the DNS and DNS resource records. It involves an inter

46、action between the application and an ORS client to retrieve information (specified by that application) from the DNS system. The general OID resolution process normally returns a URL for a document, a canonical OID-IRI or a DNS name, but there is no restriction on what could be returned. This is us

47、ually followed by an application-specific OID resolution process, where the application uses the information obtained from the general resolution process to obtain the final information required by the application. A service broker can enforce service policy on resolution result such as filtering an

48、d modify the resolution result according to service policies. A service broker transfers the MII resolution result using the interface in clause 6.1.3 to the Mobile AIDC terminal. 6 Functions of service broker 6.1 MII recognition A service broker recognizes the MII according to ISO/IEC 29174. This M

49、II is delivered from the Mobile AIDC terminal using SERVICE-REQUEST interface. In case that a service broker fails to recognize the OID for MII or OID for other identifier schemes, a service broker cannot recognize the MII. In this case, a service broker sends the OID resolution request using interface defined in clause 7.3.1 to ORS which is defined in ISO/IEC 29168-1. 6.2 MII resolution For MII resolution, a service broker creates the MII resolution request and sends the reques