1、 ATIS-0300096 RFID Guideline for Product, Product Package and Transport Unit Tagging June 2008 Copyright 2008 by the Alliance for Telecommunications Industry Solutions, Inc. All rights reserved. The RFID Guideline for Product, Product Package and Transport Unit Tagging, dated June 2008, is copyright
2、ed, published and distributed by ATIS on behalf of the Automatic Identification and Data Capture Committee (AIDC). Except as expressly permitted, no part of this publication may be reproduced or distributed in any form, including electronic media or otherwise, without the prior express written permi
3、ssion of ATIS. Participants in the AIDC and other parties are hereby authorized to reproduce this document and distribute it within their own business organizations for business purposes, provided that this notice continues to appear in the reproduced documentation. Resale is prohibited. For orderin
4、g information, please contact: ATIS 1200 G Street N.W., Suite 500 Washington, DC 20005 (202) 628-6380 aidcatis.org A complete listing of AIDC Documents is available on the ATIS Web Site at: http:/www.atis.org/bcsc/publisheddocs.asp. 2 ATIS is the leading technical planning and standards development
5、organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More than 200 companies actively formulate standards in ATIS Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and
6、 Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platforms and Emerging Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Networked Car,
7、 IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and
8、 a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the American National Standards Institute (ANSI). For more information, please visit www.atis.org. - - The Automatic Identification and Data Capture Committee (AIDC) provides an open forum to establish guidel
9、ines for common shipping labels, product marking labels, product changes and software issuance standards. These common guidelines simplify the receiving, shipping, transportation and tracing of telecommunications products through company and industry business processes and the global supply chain Th
10、is document is maintained under the direction of ATIS and the AIDC. Suggestions for improvement of this document are welcome. They should be sent to the Alliance for Telecommunications Industry Solutions, AIDC Staff, 1200 G Street NW, Suite 500, Washington, DC 20005. All changes to this document sha
11、ll be made through the AIDC issue resolution process and adopted by the AIDC as set forth in the ATIS Operating Procedures. - Notice of Disclaimer Provide or reference equipment with specific equipment attributes, features and technical information. Note 2: The CLEI Code does qualify as an Equipment
12、 Identifier (EI) Mandatory: when used in defining data elements. The data element with mandatory designation is required. Optional: when used in defining data elements. The data element with optional designation is not required and may or may not be included. Unique RF tag identifier (UID): Unique i
13、dentification of the RFID tag as defined in ISO/IEC 15963. Unique Item Identifier (UII): Equivalent to Unique Serial Identification (USI) as used in this and other BCSC documents. Unique Serial Identification (USI): Unique serial identification consists of two segments, the manufacturer identificati
14、on segment and the serial number segment. The combination of these two segments ensures uniqueness within a company. To make the USI globally unique, the manufacturer identification segment includes an Issuing Agency Code (IAC - per ISO/IEC 15459-2) with the IAC-assigned code for the manufacturer/su
15、pplier/company. This is the standard approach as specified in ISO/IEC 15459-4 and ANS MH10.8.7 standards. ISO/IEC 15459 refers to the unique serial identification for an item as the Unique Item Identifier (UII). 10 2 Issues related to the use of RFID 2.1 Frequency Issues The frequencies specified in
16、 this guideline have not been tested in a telecommunications environment. The frequency requirements are based on international standards. This guideline recommends that companies planning to implement these requirements initiate rigorous testing in a central office and other telecommunications envi
17、ronment to ensure compatibility and minimize or eliminate interference with existing equipment. Use of RFID at UHF (860-960MHz) could have negative impact on the functionality of both RFID components and telecommunication equipment when used in areas where GSM/UMTS operates at 880-960MHz, if not tes
18、ted thoroughly. Other frequencies specified in the international standards may also affect the functionality of both RFID components and telecommunication equipment. Any RFID frequency plan for usage should be thoroughly tested in a telecommunications environment. 2.2 Tag Format Issues This guidelin
19、e recommends tag formatting per the appropriate section of the ISO/IEC 18000-n standard for the frequency of the tag being used. In the Protocol Control (PC) bits, bit 17HEX shall be set to 1 for ISO tags. If EPC tags are required and permitted by trading partner agreement, the rules for EPC will ap
20、ply, as specified EPCglobal Tag Data Standard. 2.3 Tag Size This document does not specify a particular tag size. The optimum tag size depends on available tags and user applications. Therefore, users should consider the minimum needed content depending on the task and applications. 3 Tag Layout Fig
21、ure 3-1 provides the logical memory map for an RFID tag (per ISO/IEC 18000). 11 Figure 3-1 Memory Map 3.1 Tag memory banks Tag memory shall be logically separated into four distinct banks, each of which may comprise one or more memory words. The memory banks are defined in the subsections that follo
22、w. 3.1.1 Reserved memory Reserved memory shall contain the kill and access passwords. See ISO 17366 for additional information. 3.1.2 UII memory UII memory shall contain a CRC-16 (Cyclic Redundancy Check1) at memory addresses 00HEX to 0FHEX, (which is calculated/verified within the RFID hardware tha
23、t writes/reads the tag), Protocol-Control (PC) bits at memory addresses 10HEX to 1FHEX, and a code, i.e., a UII, that identifies the object to which the tag is or will be attached beginning at address 20HEX. The specific detail for encoding the UII is provided in sections 4.2, 5.2, 6.2 and 7.2 for e
24、ach tag type. The PC is subdivided into an UII length field in memory locations 10HEX to 14HEX, RFU bits in memory locations 15HEX to 16HEX, an ISO/EPC bit in memory location 17HEX, and a Numbering System Identifier (NSI) in memory locations 18HEX to 1FHEX. The CRC-16, PC, and UII shall be stored Mo
25、st Significant Bit (MSB) first (the UIIs MSB is stored in location 20HEX). Table 3.1-1: Protocol Control Bits Protocol Control Bits run from 10HEX 1FHEX 0/1 0/1 0/1 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F Length indicator User Mem XPC EPC / ISO Application Family Identifier (AFI) / Numbering
26、 System Identifier (NSI) Bits 10HEX 14HEX: The length of the (PC + UII) that a Tag backscatters, in words: 000002: One word (addresses 10HEX to 1FHEX in UII memory). 000012: Two words (addresses 10HEX to 2FHEX in UII memory). 000102: Three words (addresses 10HEX to 3FHEX in UII memory). 111112: 32 w
27、ords (addresses 10HEX to 20FHEX in UII memory). Bit 15HEX: Indicates that User Memory (Bank 11) is used (value = 1) or not used (value = 0). Bit 16HEX: Shall be set to “0” if there are no extension of the PC bits and shall be set to “1” if the PC bits are extended by an additional 16 bits. NOTE: If
28、a Tag implements XPC bits then PC Bit 16HEX SHALL be the logical OR of the XPC bits contents. The Tag computes this logical OR, and maps the result into PC bit 16HEX, at power up. Readers can select on this bit, and Tags will backscatter it. _ 1 A method for detecting errors in the received data by
29、grouping the bytes of data into a block and calculating the CRC. This is usually done by the data link protocol and the calculated CRC is appended to the end of the data link layer frame. Although the calculation may be done by software, it is usually performed by hardware which is much simpler than
30、 the software approach. The RFID tag will have this inherent capability. 12 NOTE: The XPC will be logically located at word 32 of UII memory. If a reader wants to select on the XPC bits, then it issues a Select command targeting this memory location. Bit 17HEX: For encoding a tag in ISO/IEC 15961 fo
31、rmat using AFI in Bits 18HEX 1FHEX, this bit shall be set to “1”. This shall be the preferred method for the telecommunication industry. If the user needs to encode an EPC tag, this bit is set to “0”. Bits 18HEX 1FHEX: A numbering system identifier (NSI) whose default value is 000000002 and which ma
32、y include an AFI (Application Family Identifier) as defined in ISO/IEC 15961 (when encoding the tag pursuant to ISO standards). The MSB of the NSI is stored in memory location 18h. When Bit 17HEX is set to “1”, using an AFI, then the following shall apply for product/package, shipments and returnabl
33、e transport items: The AFI is followed by the application subfamily (ASF) per Annex B, ISO/IEC 15961:2004 (E). 13 Table 3.1-2: Numbering System Identifier Description Decimal AFI Decimal ASF Hex Binary Product/package 10 1 A1 10100001 Transport units (shipments) 10 2 A2 10100010 Returnable Transport
34、 Items 10 3 A3 10100011 3.1.3 TID memory TID memory shall contain an 8-bit ISO/IEC 15963 allocation class (AC) identifier at memory locations 00HEX to 07HEX. There are five (5) classes of UID (Unique RF tag identifier) issuers defined as shown in Table 3.1-3. Table 3.1-3: Classes of unique identifie
35、rs issuers AC Value Class UID issuer identifier size Serial Number size Registration authority (of “UID issuer Registration Number”) 11100000 7816-6 8 bits 48 bits APACS (ISO/IEC 7816-6 registration authority) 11100001 14816 per NEN per NEN NEN (ISO 14816 registration authority) 11100010 GS1 per GS1
36、 per GS1 GS1 000xxxxx INCITS 256 per ANS INCITS 256 per ANS INCITS 256 ANSI ASC INCITS T6 11100011 to 11101111 RFU N/A N/A Reserved for future use by ISO TID memory shall contain sufficient identifying information above 07HEX for an Interrogator to uniquely identify the custom commands and/or option
37、al features that a tag supports. (See section 6 of ISO/IEC 15963). This memory content information is encoded by the tag manufacturer. For EPC tags whose ISO/IEC 15963 allocation class identifier is 111000102, this identifying information shall comprise a 12-bit Tag mask-designer identifier at memor
38、y locations 08HEX to 13HEX and a 12-bit Tag model number at memory locations 14HEX to 1FHEX. NOTE: The reader should contact EPCGlobal for information on encoding EPC tags. See the References section for EPCGlobal contact information. For ISO/IEC 15459-4 tags whose ISO/IEC 15963 allocation class ide
39、ntifier is 111001112, this identifying information shall comprise a 12-bit Tag mask-designer identifier at memory locations 08HEX to 13HEX and a 12-bit Tag model number at memory locations 14HEX to 1FHEX. For ISO/IEC 15459-4 tags operating conformant to ISO/IEC 18000, Part 3, Mode 3 and whose ISO/IE
40、C 15963 allocation class identifier is 000101002, this identifying information shall comprise a 12-bit Tag mask-designer identifier at memory locations 08HEX to 13HEX and a 12-bit Tag model number at memory locations 14HEX to 1FHEX. For ISO/IEC 15459-5 tags operating conformant to ISO/IEC 18000, Par
41、t 6, Type C and whose ISO/IEC 15963 allocation class identifier is 000100112, this identifying information shall comprise a 12-bit Tag mask-designer 14 identifier at memory locations 08HEX to 13HEX and a 12-bit Tag model number at memory locations 14HEX to 1FHEX. Tags may contain Tag- and vendor-spe
42、cific data (for example, a Tag serial number) in TID memory above 1FHEX. For ISO/IEC 15459-5 tags operating conformant to ISO/IEC 18000, Part 3, Mode 3 and whose ISO/IEC 15963 allocation class identifier is 000101002, this identifying information shall comprise a 12-bit Tag mask-designer identifier
43、at memory locations 08HEX to 13HEX and a 12-bit Tag model number at memory locations 14HEX to 1FHEX. Tags may contain Tag- and vendor-specific data (for example, a Tag serial number) in TID memory above 1FHEX. For ISO/IEC 15459-5 tags operating conformant to ISO/IEC 18000, Part 7 and whose ISO/IEC 1
44、5963 allocation class identifier is 000100012, this identifying information shall comprise a 8-bit Tag mask-designer identifier at memory locations 08HEX to 0FHEX and a 32-bit Tag serial number at memory locations 16HEX to 1FHEX. For ISO/IEC 15459-5 tags operating conformant to ISO/IEC 18000, Part 2
45、, Type A and whose ISO/IEC 15963 allocation class identifier is 111000002, this identifying information shall comprise a 8-bit Tag manufacturer identification at memory locations 08HEX to 15HEX and a 48-bit Tag serial number at memory locations 16HEX to 3FHEX. Tags may contain Tag- and vendor-specif
46、ic data (for example, a Tag serial number) in TID memory above 1FHEX. 3.1.4 User memory User memory allows user-specific data storage. The memory organization is user-defined and specific information on tags can be found in individual sections 4.3, 5.3, 6.3 and 7.3 below. 15 4 Product tags See Secti
47、on 2 for frequency issues related to RFID tags on products. Studies in process during the development of this guideline indicate that RFID on telecommunications products is one of the automatic data capture technologies that may provide significant value, especially for maintenance and repair of the
48、se products. Other technologies, i.e. Management Information Base (MIB) and product identity markings, can be used for identification of telecommunications equipment that is installed and operating. Although implementation of RFID product tagging may not be implemented across the industry for many years, this section provides guidelines for the specification of the tag content in a standard, industry accepted format for those manufacturers, suppliers and service providers, including repair and maintenance providers, that find the use of RFID beneficial in their operations and in the
