11.08.2015 Views

GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

30093010301130123013301430153016301730183019302030213022302330243025302630273028302930303031303230333034303530363037303830393040304130423043304430453046304730482. Otherwise, apply the procedure of Section 12.3.3 to the <strong>EPC</strong> <strong>Tag</strong> URI from Step 1 toobtain a Pure Identity <strong>EPC</strong> URI. This is the final result.15.2.4 Decoding of Control InformationThis procedure is used as a subroutine by the decoding procedures in Sections 15.2.1and 15.2.2. It calculates a string that is inserted immediately following theurn:epc:tag: or urn:epc:raw: prefix, containing the values of all non-zerocontrol information fields (apart from the filter value). If all such fields are zero, thisprocedure returns an empty string, in which case nothing additional is inserted after theurn:epc:tag: or urn:epc:raw: prefix.Given: The contents of the <strong>EPC</strong> Memory Bank of a Gen 2 tagProcedure:1. If bit 17 h is zero, extract bits 18 h – 1F h and consider them to be an unsigned integer A.If A is non-zero, append the string [att=xAA] (square brackets included) to CF,where AA is the value of A as a two-digit hexadecimal numeral.2. If bit 15 h is non-zero, append the string [umi=1] (square brackets included) to CF.3. If bit 16 h is non-zero, extract bits 210 h – 21F h and consider them to be an unsignedinteger X. If X is non-zero, append the string [xpc=xXXXX] (square bracketsincluded) to CF, where XXXX is the value of X as a four-digit hexadecimal numeral.Note that in the Gen 2 air interface, bits 210 h – 21F h are inserted into thebackscattered inventory data immediately following bit 1F h , when bit 16 h is non-zero.See [UHFC1G2].4. Return the resulting string (which may be empty).16 <strong>Tag</strong> Identification (TID) Memory Bank ContentsTo conform to this specification, the <strong>Tag</strong> Identification memory bank (bank 10) SHALLcontain an 8 bit ISO/IEC 15963 allocation class identifier of E2 h at memory locations 00 hto 07 h . TID memory locations 08 h to 13 h SHALL contain a 12 bit <strong>Tag</strong> mask designeridentifier (MDID) obtainable from <strong>EPC</strong>global. TID memory locations 14 h to 1F h SHALLcontain a 12-bit vendor-defined <strong>Tag</strong> model number (TMN) as described below.<strong>EPC</strong>global will assign two MDIDs to each mask designer, one with bit 08 h equal to oneand one with bit 08 h equal to zero. Readers and applications that are not configured tohandle the extended TID will treat both of these numbers as a 12 bit MDID. Readers andapplications that are configured to handle the extended TID will recognize the TIDmemory location 08 h as the Extended <strong>Tag</strong> Identification bit. The value of this bitindicates the format of the rest of the TID. A value of zero indicates a short TID in whichthe values beyond address 1F h are not defined. A value of one indicates an Extended <strong>Tag</strong>Identification (XTID) in which the memory locations beyond 1F h contain additional dataas specified in Section 16.2.The <strong>Tag</strong> model number (TMN) may be assigned any value by the holder of a givenMDID. However, [UHFC1G2] states “TID memory locations above 07 h shall be definedCopyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 116 of 218

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!