GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537Information Services (EPCIS) specification, and is also available as an output from theApplication Level Events (ALE) interface.Section 7 specifies the correspondence between Pure Identity EPC URIs as defined inSection 6 and bar code element strings as defined in the GS1 General Specifications.Section 8 specifies the Pure Identity Pattern URI, which is a syntax for representing setsof related EPCs, such as all EPCs for a given trade item regardless of serial number.The remaining sections address topics that are specific to RFID, including RFID-specificforms of the EPC as well as other data apart from the EPC that may be stored on Gen 2RFID tags.Section 9 provides general information about the memory structure of Gen 2 RFID Tags.Sections 10 and 11 specify “control” information that is stored in the EPC memory bankof Gen 2 tags along with a binary-encoded form of the EPC (EPC Binary Encoding).Control information is used by RFID data capture applications to guide the data captureprocess by providing hints about what kind of object the tag is affixed to. Controlinformation is not part of the EPC, and does comprise any part of the unique identity of atagged object. There are two kinds of control information specified: the “filter value”(Section 10) that makes it easier to read desired tags in an environment where there maybe other tags present, such as reading a pallet tag in the presence of a large number ofitem-level tags, and “attribute bits” (Section 11) that provide additional special attributeinformation such as alerting to the presence of hazardous material. The same “attributebits” are available regardless of what kind of EPC is used, whereas the available “filtervalues” are different depending on the type of EPC (and with certain types of EPCs, nofilter value is available at all).Section 12 specifies the “tag” Uniform Resource Identifiers, which is a compact stringrepresentation for the entire data content of the EPC memory bank of Gen 2 RFID Tags.This data content includes the EPC together with “control” information as defined inSections 10 and 11. In the “tag” URI, the EPC content of the EPC memory bank isrepresented in a form similar to the Pure Identity EPC URI. Unlike the Pure IdentityEPC URI, however, the “tag” URI also includes the control information content of theEPC memory bank. The “tag” URI form is recommended for use in capture applicationsthat need to read control information in order to capture data correctly, or that need towrite the full contents of the EPC memory bank. “Tag” URIs are used in the ApplicationLevel Events (ALE) interface, both as an input (when writing tags) and as an output(when reading tags).Section 13 specifies the EPC Tag Pattern URI, which is a syntax for representing sets ofrelated RFID tags based on their EPC content, such as all tags containing EPCs for agiven range of serial numbers for a given trade item.Sections 14 and 14.5.10 specify the contents of the EPC memory bank of a Gen 2 RFIDtag at the bit level. Section 14 specifies how to translate between the the “tag” URI andthe EPC Binary Encoding. The binary encoding is a bit-level representation of what isactually stored on the tag, and is also what is carried via the Low Level Reader Protocol(LLRP) interface. Section 14.5.10 specifies how this binary encoding is combined withattribute bits and other control information in the EPC memory bank.Section 16 specifies the binary encoding of the TID memory bank of Gen 2 RFID Tags.Copyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 18 of 218