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
- 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.
<strong>EPC</strong> EncodingScheme Name(includes length)Filter value<strong>EPC</strong> <strong>Tag</strong> URIurn:epc:tag:[att=x01][xpc=x0004]:sgtin-96:3.0614141.112345.400Control fields(optional)<strong>EPC</strong> Raw URI, toggle=0urn:epc:raw:[att=x01][xpc=x0004]:96.x0123456890ABCDEF01234567ExplicitLength<strong>EPC</strong> Raw URI, toggle=1urn:epc:raw:[umi=1][xpc=x0004]:64.x31.x0123456890ABCDEF1810181118121813181418151816181718181819182018211822182318241825182618271828182918301831Application FamilyIdentifier (AFI)Figure 17.Illustration of <strong>EPC</strong> <strong>Tag</strong> URI and <strong>EPC</strong> Raw URIThe first form in the figure, the <strong>EPC</strong> <strong>Tag</strong> URI, is used for a valid <strong>EPC</strong>. It resembles thePure Identity <strong>EPC</strong> URI, with the addition of optional control information fields asspecified in Section 12.2.2 and a (non-optional) filter value. The <strong>EPC</strong> scheme name(sgtin-96 in the example above) specifies a particular binary encoding scheme, and soit includes the length of the encoding. This is in contrast to the Pure Identity <strong>EPC</strong> URIwhich identifies an <strong>EPC</strong> scheme but not a specific binary encoding (e.g., sgtin but notspecifically sgtin-96).The <strong>EPC</strong> Raw URI illustrated by the second example in the figure can be used wheneverthe toggle bit (bit 17 h ) is zero, but is typically only used if the first form cannot (that is, ifthe contents of the <strong>EPC</strong> bank cannot be decoded according to Section 14.4). It specifiesthe contents of bit 20 h onward as a single hexadecimal numeral. The number of bits inthis numeral is determined by the “length” field in the <strong>EPC</strong> bank of the tag (bits 10 h –14 h ). (The grammar in Section 12.4 includes a variant of this form in which the contentsare specified as a decimal numeral. This form is deprecated.)The <strong>EPC</strong> Raw URI illustrated by the third example in the figure is used when the togglebit (bit 17 h ) is one. It is similar to the second form, but with an additional field betweenthe length and payload that reports the value of the AFI field (bits 18 h – 1F h ) as ahexadecimal numeral.Each of these forms is fully defined by the encoding and decoding procedures specifiedin Section 14.5.10.Copyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 67 of 218
Change language