RFIDEPCGEN2协议2_epcgen2协议

RFID

GEN2

需积分: 9 54 浏览量更新于2023-07-17 评论收藏 1.04MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源评论

资源推荐

EPCglobal

Tag Data Standards Version 1.4

Ratified on June 11, 2008

Disclaimer

EPCglobal Inc™ is providing this document as a service to interested industries.

This document was developed through a consensus process of interested parties.

Although efforts have been to assure that the document is correct, reliable, and

technically accurate, EPCglobal Inc. makes NO WARRANTY, EXPRESS OR

IMPLIED, THAT THIS DOCUMENT IS CORRECT, WILL NOT REQUIRE

MODIFICATION AS EXPERIENCE AND TECHNOLOGICAL ADVANCES DICTATE,

OR WILL BE SUITABLE FOR ANY PURPOSE OR WORKABLE IN ANY

APPLICATION, OR OTHERWISE. Use of this document is with the understanding

that EPCglobal Inc. has no liability for any claim to the contrary, or for any damage

or loss of any kind or nature.

20 permitted. Requests for permission to reproduce should be addressed to

21 epcglobal@epcglobalinc.org.

23 EPCglobal Inc.

is providing this document as a service to interested industries. This document

24 was developed through a consensus process of interested parties. Although efforts have been to

25 assure that the document is correct, reliable, and technically accurate, EPCglobal Inc. makes NO

26 WARRANTY, EXPRESS OR IMPLIED, THAT THIS DOCUMENT IS CORRECT, WILL NOT

27 REQUIRE MODIFICATION AS EXPERIENCE AND TECHNOLOGICAL ADVANCES DICTATE,

28 OR WILL BE SUITABLE FOR ANY PURPOSE OR WORKABLE IN ANY APPLICATION, OR

29 OTHERWISE. Use of this Document is with the understanding that EPCglobal Inc. has no liability

for any claim to the contrary, or for any damage or loss of any kind or nature

DOCUMENT HISTORY

Document Number:

™

Abstract

This document defines the EPC Tag Data Standards version 1.4. It applies to RFID tags

conforming to “EPC Radio-Frequency Identity Protocols Class-1 Generation-2 UHF RFID

Protocol for Communications at 860 MHz-960MHz Version 1.1.0” (“Gen2 Specification”).

Such tags will be referred to as “Gen 2 Tags” in the remainder of this document. These

standards define completely that portion of EPC tag data that is standardized, including how

that data is encoded on the EPC tag itself (i.e. the EPC Tag Encodings), as well as how it is

encoded for use in the information systems layers of the EPC Systems Network (i.e. the EPC

URI or Uniform Resource Identifier Encodings).

The EPC Tag Encodings include a Header field followed by one or more Value Fields. The

Header field defines the overall length and format of the Values Fields. The Value Fields

contain a unique EPC Identifier and a required Filter Value when the latter is judged to be

important to encode on the tag itself.

The EPC URI Encodings provide the means for applications software to process EPC Tag

Encodings either literally (i.e. at the bit level) or at various levels of semantic abstraction that

is independent of the tag variations. This document defines four categories of URI:

1. URIs for pure identities sometimes called “canonical forms.” These contain only the

unique information that identifies a specific physical object, location or organization,

and are independent of tag encodings.

2. URIs that represent specific tag encodings. These are used in software applications

where the encoding scheme is relevant, as when commanding software to write a tag.

3. URIs that represent patterns, or sets of EPCs. These are used when instructing

software how to filter tag data.

4. URIs that represent raw tag information, generally used only for error reporting

purposes.

Status of this document

This section describes the status of this document at the time of its publication. Other

documents may supersede this document. The latest status of this document series is

maintained at EPCglobal. See http://www.epcglobalinc.org/standards/tds/

. 72

On June 11

, the Recommended Specification was reviewed and ratified by the EPCglobal

Board. It is now a Ratified Standard and can be fully implemented and referenced.

Further comments or potential errata found pertaining to this document should be sent to the

EPCglobal Software Action Group’s Tag Data & Translation Standards Working Group at

the following mailing list: sag_tdts_wg@lists.epcglobalinc.org

. 79

™

81 Changes from Previous Versions

Version 1.4 82

100

101

102

103

104

105

106

107

108

109

110

111

This update to the Tag Data Standards provides support for two GS1 identities: The Global

Service Relation Number (GSRN) and the Global Document Type Identifier (GDTI).

Changes are as follows

1. Sections 2.1.2.6 (GSRN) and 2.1.2.7 (GDTI) describe the new Identity Types.

2. The Header Table 1 has three new entries: x2C for GSRN-96, x2D for GDTI-96 and

x3A for GDTI-113.

3. A new filter value of “100” has been added to the SGTIN filter Table in Section

3.5.1.

4. The Encoding and Decoding procedures for the GRAI-96 and GRAI-170 have been

changed in sections 3.8.1.1, 3.8.1.2, 3.8.2.1 and 3.8.2.2 to eliminate a leading 0 that

has been encoded as a filler 0 character in the GRAI. This leading “0” is not part of

the GRAI in the GS1 General Specifications.

5. Changes from a value “168-126” to a value of “168-148” in table 22 in section 3.9.2

and the GIAI Summary table in Appendix A have been made to correct an error in

version 1.3.1.

6. Section 3.10 is the detailed definition and encoding and decoding procedures for the

Global Service Relation Number (GSRN).

7. Section 3.11 is the detailed definition and encoding and decoding procedures for the

Global Document Type Identifier (GDTI).

8. Section 4 has been updated to include the URI forms for the new identities.

9. Section 5 has been updated to include the translations for the new identities

10. Appendix A and B have been updated with new tables for the new identities

11. References to EAN.UCC have been changed to GS1 throughout the document.

12. The Sunset date of July 1, 2009 for 64 bit Header values has been added.

13. Deleted Appendix B which was the bit allocation table because it is too

implementation specific for this TDTS document. This table, if needed, will be

published by EPCglobal.

Version 1.3.1

112

113

114

115

116

This update to the Tag Data Standards provides errata changes found since Version 1.3 was

published. Changes are as follows

™

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

1. In section 3.8.2.2 GRAI-170 Decoding Procedure, the bit numbering has been

corrected. For instance “00110111 b

162

161

…b

“ has been corrected to read

“00110111 b

161

160

…b

“ and so forth throughout the section.

2. The GIAI-202 Table 23 and the Associated Summary Table in Appendix A did not

add up to a total of 188 bits for each Company Prefix/Individual Asset Reference

which is what the encoding/decoding procedure expects. The Individual Asset

Reference Bits column has been changed so each row adds to 188 bits. For example,

for Partition value 0 the Individual Asset Reference bits value “126” was changed to

“148”.

3. An addition error in the Appendix B table, SGLN-195 row, has been corrected. The

Total bits required column was changed from 333 to 336.

4. A typographical error in line three of the section 3.8.1.1 GRAI-96 Encoding

Procedure has been corrected. The formula “15 <= K 3 <= 0” was replaced with

“15 <= K <= 30”.

5. In Section 5.4 (Gen 2 Tag EPC Memory into Tag or Raw URI) step 8 line 4 a

missing dot (.) character after the value of A has been corrected.

6. The arrows in Appendix B between the Bar Code symbol and the SGTIN-96 have

been adjusted to reflect the connections between the Company Prefix, Item Reference

and Serial Number.

Version 1.3 137

138

139

140

141

142

143

144

145

146

147

148

149

150

This Tag Data Standards Version 1.3 is aimed for use in Gen 2 Tags, whereas the previous

Version 1.1, was aimed for use in UHF Class 1 Generation 1 tags. Version 1.3 maintains

compatibility with version 1.1 in the identity level. In other words, this version will continue

to support the GS1 system and DoD identity types.

However, in Version 1.3, there are significant changes to prior versions, including:

1. The deprecation of 64 bit encodings.

2. The elimination of tiered header rules.

3. The encoding of EPC to fit the structure of Gen 2 Tags

4. The addition of the Extension Component to the SGLN

5. Addition of SGTIN-198, SGLN-195, GRAI-170, GIAI-202 and corresponding

changes in URI expression for alpha-numeric serial number encoding.

剩余119页未读，继续阅读

zpxfzp

粉丝: 4
资源: 4

会员权益专享

RFID EPC GEN2 协议2

评论0

会员权益专享

最新资源

RFID EPC GEN2 协议2

评论0

ISO18000-6C(EPC Gen2) V2.0.1最新版协议

Epc GEN2 国际标准协议

EPC标准协议(中文版).doc

RFID EPC GEN2 协议4

新的EPC RFID协议的研究及性能评估

"易卡支付：基于EPC Global RFID协议的安全性能评估与新协议研究

epc gen2 协议中文

epc class-1 gen2 uhf rfid v2.0.1协议

SO 18000-6 又有几种呢

讨论RFID的主要安全协议，说明各类协议i的优缺点

超高频rfid读写器仿真

matlab rfid

nxp ucode dna 指令集

android uhf 开发

ISO/IEC 18000-63 ISO/IEC 18000-6B ISO/IEC 18000-6C有什么区别

impinj 读写器这些模式autoset dense reader ，autoset static ，max throughput，hybrid mode的区别

impinj r2000底层开发

seuic UHFReader

ISO18000-6C(EPC Global Gen2) V2.0.1 新版协议

会员权益专享

最新资源