GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

313231333134313531363137313831393140314131423143BitPositionin WordField11 BlockWrite andBlockEraseSegment Present12 OptionalCommandSupport SegmentPresentDescriptionIf non-zero, specifies that the XTID includes theBlockWrite and BlockErase segment specified inSection 16.2.4.If zero, specifies that the XTID does not include theBlockWrite and BlockErase words.If non-zero, specifies that the XTID includes the OptionalCommand Support segment specified in Section 16.2.3.If zero, specifies that the XTID does not include theOptional Command Support word.13 – 15 Serialization If non-zero, specifies that the XTID includes a uniqueserial number, whose length in bits is 48 + 16(N – 1),where N is the value of this field.If zero, specifies that the XTID does not include a uniqueserial number.Table 43. The XTID header16.2.2 XTID SerializationThe length of the XTID serialization is specified in the XTID header. The managingentity specified by the tag mask designer ID is responsible for assigning unique serialnumbers for each tag model number. The length of the serial number uses the followingalgorithm:0: Indicates no serialization1-7: Length in bits = 48 + ((Value-1) * 16)16.2.3 Optional Command Support SegmentIf bit twelve is set in the XTID header then the following word is added to the XTID. Bitfields that are left as zero indicate that the tag does not support that feature. Thedescription of the features is as follows.BitPosition inSegmentFieldDescription4 – 0 Max EPC Size This five bit field shall indicate the maximum size thatcan be programmed into the first five bits of the PC.5 Recom Support If this bit is set the tag supports recommissioning asspecified in [UHFC1G2].6 Access If this bit is set the it indicates that the tag supports theaccess command.Copyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 120 of 218