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 User data for Mobile AIDC services BS ISO/IEC 29175:2012National foreword This British Standard is the UK impl
2、ementation of ISO/IEC 29175: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 not pu
3、rport 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 81102 9 ICS 35.040 Compliance with a British Standard cannot confer immunity from legal obliga
4、tions. 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 29175:2012 Reference number ISO/IEC 29175:2012(E) ISO/IEC 2012INTERNATIONAL S
5、TANDARD ISO/IEC 29175 First edition 2012-04-01Information technology Mobile item identification and management User data for Mobile AIDC services Technologies de linformation Gestion et identification dlment mobile Donnes dutilisateur pour services AIDC mobiles BS ISO/IEC 29175:2012ISO/IEC 29175:201
6、2(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 ISO at the
7、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 29175:2012ISO/IEC 2917
8、5:2012(E) ISO/IEC 2012 All rights reserved iiiContents Page Foreword iv 1 Scope 1 2 Normative references 1 3 Terms and definitions . 2 4 Abbreviated terms . 2 5 User Data Identifier 2 5.1 General . 2 5.2 Identifier for user data. 2 5.3 RF tag for user data . 3 5.3.1 ISO/IEC 29143 and ISO/IEC 18000-6
9、3 air interface requirements . 3 5.3.2 ISO/IEC 29143 and ISO/IEC 18000-63 memory architecture for user data . 3 5.3.3 DSFID of user data for ISO/IEC 15962 . 4 5.3.4 Preparing object identifier for user data identifier . 5 5.3.5 Encoding of user data . 5 5.4 ISO/IEC 15434-applied ORM for user data 5
10、5.4.1 ISO/IEC 15434 envelope structure for user data 5 5.4.2 Header data and format trailer for user data 6 Annex A (informative) Examples of the final arcs for ASC MH10 Data Identifiers for an RF tag 8 Annex B (informative) Example of QR Code Encoding ASC MH10 Data Identifiers. 9 Bibliography 10 BS
11、 ISO/IEC 29175:2012ISO/IEC 29175: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 or
12、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, go
13、vernmental 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 Directives,
14、 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 natio
15、nal 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 shall not be held responsible for identifying any or all such patent rights. ISO/IEC 29175 was prepared by Joint Technical Committee ISO/IEC JTC 1, Inf
16、ormation technology, Subcommittee SC 31, Automatic identification and data capture techniques. BS ISO/IEC 29175:2012INTERNATIONAL STANDARD ISO/IEC 29175:2012(E) ISO/IEC 2012 All rights reserved 1Information technology Mobile item identification and management User data for Mobile AIDC services 1 Sco
17、pe This International Standard provides identification of user data for the purpose of encoding and identifying user data in Mobile AIDC services using ISO/IEC 29143 radio frequency (RF) tags; ISO/IEC 18000-63 RF tags, and ISO/IEC 15434-applied optically readable media such as linear bar codes and t
18、wo-dimensional symbols. 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 edition of the referenced document (including any amendments) applies. IS
19、O/IEC 15434, Information technology Automatic identification and data capture techniques Syntax for high-capacity ADC media ISO/IEC 15961-2, Information technology Radio frequency identification (RFID) for item management Data protocol Part 2: Registration of RFID data constructs ISO/IEC 15962, Info
20、rmation technology Radio frequency identification (RFID) for item management Data protocol: data encoding rules and logical memory functions ISO/IEC 18000-6, Information technology Radio frequency identification for item management Part 6: Parameters for air interface communications at 860 MHz to 96
21、0 MHz ISO/IEC 19762 (all parts), Information technology Automatic identification and data capture (AIDC) techniques Harmonized vocabulary ISO/IEC 29143, Information technology Automatic identification and data capture techniques Air interface specification for Mobile RFID interrogators ISO/IEC TR 29
22、172, Information technology Mobile item identification and management Reference architecture for Mobile AIDC services ISO/IEC 29174-1, Information technology UII scheme and encoding format for Mobile AIDC services Part 1: Identifier scheme for multimedia information access triggered by tag-based ide
23、ntification 1ANSI MH10.8.2, Data Identifier and Application Identifier Standard 1To be published. BS ISO/IEC 29175:2012ISO/IEC 29175:2012(E) 2 ISO/IEC 2012 All rights reserved3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/IEC 19762, ISO/IEC 29172 an
24、d the following apply. 3.1 UII resolution process of converting unique item identifier (UII) into its associated information 4 Abbreviated terms DI data identifier MII mobile item identifier ODS object directory service OID object identifier ORM optically readable media UII unique item identifier UM
25、I user-memory indicator 5 User Data Identifier 5.1 General In typical Mobile AIDC services, information is provided through specific network communications, called UII resolution. Once a Mobile AIDC terminal reads an identifier from the data carrier, information associated with the identifier can be
26、 acquired through the network by UII resolution. According to ISO/IEC 29172, the typical procedures for Mobile AIDC services are as follows: - The Mobile AIDC terminal reads an MII from the data carrier and sends an MII resolution request to ODS. - ODS then resolves the MII to the locations of the i
27、nformation associated with the MII and sends an MII resolution response to the Mobile AIDC terminal. - The Mobile AIDC terminal then requests an AIDC service from the selected location. The concept of MII (ISO/IEC 29174-1), explained in ISO/IEC 29172, is included within UII. As explained above, the
28、MII resolution occurs prior to getting information about the tagged object or the targeted service. However, it may be useful that user is able to get the information such as the object name, and the product/service name from RF tag or ORM without network communication. MII shall be as defined in IS
29、O/IEC 29174-1. This information is called user data in this International Standard, and user data can be helpful. For example, when UIIs from multiple items are read simultaneously by the Mobile AIDC terminal the user can select the targeted item using user data. 5.2 Identifier for user data Identif
30、iers for user data shall follow ASC MH10 Data Identifiers, which are given in ANSI MH10.8.2 and ISO/IEC 15418. BS ISO/IEC 29175:2012ISO/IEC 29175:2012(E) ISO/IEC 2012 All rights reserved 3ASC MH10 Data Identifiers may be used with any alphanumeric data carrier and are designed to ensure cross-indust
31、ry commonality of the Data Identifiers used in automatic identification technologies. ASC MH10 Data Identifiers have a format of one alphabetic character alone, or one alphabetic character prefixed by one, two or three numeric characters. Some ASC MH10 Data Identifiers may incorporate format definit
32、ions. The American National Standards Institute (ANSI) has designated ANSI MH10.8.2 as a “Continuous Maintenance” standard available at: http:/www.autoid.org/ANSI_MH10/ansi_mh10sc8_wg2.htm A full list of ASC MH10 Data Identifiers from the last full publication is available from: Customer Service Mat
33、erial Handling Industry 8720 Red Oak Blvd., Suite 201 Charlotte, NC 28217-3992 USA (V): +1 704/522-8644 (F): +1 704/522-7826 (U1): http:/www.mhia.org/ (U2): http:/www.mhia.org/vango/Core/orders/category.aspx?catid=52 There are alternative identifiers to meet the use case addressed by this Internatio
34、nal Standard, including those of GS1. Those interested in this technique are encouraged to contact GS1 for further information. 5.3 RF tag for user data 5.3.1 ISO/IEC 29143 and ISO/IEC 18000-63 air interface requirements RF tags compliant to this International Standard shall use the air interface de
35、scribed in ISO/IEC 18000-63 and ISO/IEC 29143. 5.3.2 ISO/IEC 29143 and ISO/IEC 18000-63 memory architecture for user data User data for ISO/IEC 29143 and ISO/IEC 18000-63 shall be stored at Memory Bank “11 2 ” (User memory) and shall follow ISO/IEC 15961-1 and ISO/IEC 15962. To indicate that user da
36、ta resides in MB11, the User- memory indicator (UMI, bit 0x15 of MB01) is set to a “1”. BS ISO/IEC 29175:2012ISO/IEC 29175:2012(E) 4 ISO/IEC 2012 All rights reservedFigure 1 ISO/IEC 29143 and 18000-63, Type C, Memory structure 5.3.3 DSFID of user data for ISO/IEC 15962 When user data is stored in Us
37、er memory, User memory locations 0x00 to 0x07 shall be the DSFID as defined in ISO/IEC 15962. The encoding of user data to User Memory locations above 0x07 shall conform to ISO/IEC 15962. 5.3.3.1 Access Method ISO/IEC 15961-1 defines Access Methods incorporated into the ISO/IEC 15962 Access Methods
38、as shown in Table 1. Access Methods for user data can be chosen from Table 1. Table 1 Assigned and Reserved Access Methods 15961 integer code 15962 DSFID bit code Name Description 0 00 No-Directory This structure supports the contiguous abutting of all the Data- Sets 1 01 Directory The data is encod
39、ed exactly as for No-Directory but the RFID tag supports an additional directory, which is first read to point to the address of the relevant object identifier. BS ISO/IEC 29175:2012ISO/IEC 29175:2012(E) ISO/IEC 2012 All rights reserved 515961 integer code 15962 DSFID bit code Name Description 2 10
40、Packed-Objects This is an integrated compaction and encoding scheme that formats data in an indexed structure as defined by the Application administrator (see ISO/IEC 15961-2) 3 11 Tag-Data-Profile This is an integrated compaction and encoding scheme for a fixed set of data elements, each of a defin
41、ed length 4-15 00-11 Reserved for future revisions of ISO/IEC 15962 5.3.3.2 Data-Format Data Formats shall be limited to those identified in ISO/IEC 15961-2. As explained in clause 5.2, ASC MH10 Data Identifiers shall be used to identify data fields for user data. According to ISO/IEC 15961-2, Data
42、Format “13” is one of the Data Formats assigned to ASC MH10 Data Identifiers. Table 2 Data-Format for user data Data Format (Decimal) Assigned Organisation or Function Root-OID Comments 13 ANSI-DI-Mapping Table 1 0 15961 13 This data format enables ANS MH10 Data Identifiers to be used as the Relativ
43、e-OID in an Object Identifier structure in a more efficient encoding manner than data format 10. The current mapping table is available at: http:/www.autoid.org/ANSI_MH10/ansi_mh10sc8_w g2.htm The root-OID shall be 1 0 15961 13 and shall not be encoded on the RF tag because the DSFID Data Format “13
44、” implies this. Each user data object is encoded on the RF tag using a RELATIVE-OID, representing a data element according to the rules of the ASC MH10 Data Identifiers standard. 5.3.4 Preparing object identifier for user data identifier To prepare the object identifier for user data, alphanumeric A
45、SC MH10 Data Identifiers should be converted to the final arc of the root-OID 1 0 15961 13. Data-Format 13 to Relative-OID mapping table is available at: http:/www.autoid.org/ANSI_MH10/ansi_mh10sc8_wg2.htm The final component of the object identifier for ASC MH10 Data Identifiers is derived by mappi
46、ng table. Examples are given in Annex A. 5.3.5 Encoding of user data The encoding of user data to User memory locations above 0x07 shall conform to ISO/IEC 15962. 5.4 ISO/IEC 15434-applied ORM for user data 5.4.1 ISO/IEC 15434 envelope structure for user data User data for ORM shall be encoded in ac
47、cordance with ISO/IEC 15434 envelope structure. BS ISO/IEC 29175:2012ISO/IEC 29175:2012(E) 6 ISO/IEC 2012 All rights reservedFigure 2 Envelope structure of ISO/IEC 15434 ISO/IEC 15434 defines a transfer structure, syntax, and coding of messages and data formats for use with high capacity AIDC media.
48、 To allow multiple data Formats to be contained within a data stream, a two level structure of enveloping is employed. The outermost layer of the message is a Message Envelope that defines the beginning and end of the message. Within the Message Envelope are one or more Format Envelopes that contain
49、 the data (See Figure 2). 5.4.2 Header data and format trailer for user data Header data and format trailer for each format are defined in Table 3. Table 3 ISO/IEC 15434 header data and trailers Format Indicator Variable Header Data Format Trailer Format Description 00 Reserved for future use 01 G S vv R STransportation 02 Complete EDI message / transaction 03 vvvrrr F S G S U SR SStructured data using ANSI ASC X12 Segments BS ISO/IEC 29175:2012
