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.

16.2.2 50 h -5F h Serial Number Segment [15:0]40 h -4F h Serial Number Segment [31:16]30 h -3F h Serial Number Segment [47:32]16.2.1 20 h -2F h XTID Header Segment [15:0]16.1 and16.210 h -1F h TAG MDID[3:0] TAG MODEL NUMBER[11:0]00 h -0F h E2 h TAG MDID[11:4]311731183119312031213122312331243125312631273128312931303131Table 42. The Extended <strong>Tag</strong> Identification (XTID) format for the TID memory bank. Note thatthe table above is fully filled in and that the actual amount of memory used, presence of asegment, and address location of a segment depends on the XTID Header.16.2.1 XTID HeaderThe XTID header is shown in Table 43. It contains defined and reserved for future use(RFU) bits. The extended header bit and RFU bits ( bits 9 through 0) shall be set to zeroto comply with this version of the specification. Bits 15 through 13 of the XTID headerword indicate the presence and size of serialization on the tag. If they are set to zero thenthere is no serialization in the XTID. If they are not zero then there is a tag serial numberimmediately following the header. The optional features currently in bits 12 through 10are handled differently. A zero indicates the reader needs to perform a database look upor that the tag does not support the optional feature. A one indicates that the tag supportsthe optional feature and that the XTID contains the segment describing this feature.Note that the contents of the XTID header uniquely determine the overall length of theXTID as well as the starting address for each included XTID segment.BitPositionin WordField0 Extended HeaderPresentDescriptionIf non-zero, specifies that additional XTID header bitsare present beyond the 16 XTID header bits specifiedherein. This provides a mechanism to extend the XTIDin future versions of the <strong>EPC</strong> <strong>Tag</strong> <strong>Data</strong> <strong>Standard</strong>. Thisbit SHALL be set to zero to comply with this version ofthe <strong>EPC</strong> <strong>Tag</strong> <strong>Data</strong> <strong>Standard</strong>.If zero, specifies that the XTID header only contains the16 bits defined herein.9 – 1 RFU Reserved for future use. These bits SHALL be zero tocomply with this version of the <strong>EPC</strong> <strong>Tag</strong> <strong>Data</strong> <strong>Standard</strong>10 User Memoryand Block PermaLock SegmentPresentIf non-zero, specifies that the XTID includes the UserMemory and Block PermaLock segment specified inSection 16.2.5.If zero, specifies that the XTID does not include the UserMemory and Block PermaLock words.Copyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 119 of 218

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

Saved successfully!

Ooh no, something went wrong!