RFIDEPCGEN2协议1资源-CSDN文库

5星 · 超过95%的资源需积分: 49 83 浏览量 2009-07-21 17:47:02 上传评论收藏 4.18MB PDF 举报

### RFID EPC GEN2 协议详解 #### 一、协议概述 RFID EPC GEN2 协议是针对电子产品编码（Electronic Product Code, EPC）系统的射频识别（Radio Frequency Identification, RFID）标签与读写器之间通信的一个标准化协议。此标准由EPCglobal组织制定，并于2005年首次发布。RFID EPC GEN2协议旨在为不同制造商生产的RFID标签和读写器提供一个通用的操作平台，从而实现不同品牌设备之间的互操作性。 #### 二、文档结构与版权说明文档开头部分明确了文档的版权信息以及版本声明。文档标题为“Low Level Reader Protocol (LLRP), Version 1.0.1”，这表明该文档定义了低层读写器协议的版本1.0.1，并且包含了已经批准的固定错误更正内容。文档声明中提到，EPCglobal Inc. 提供该文档作为对感兴趣行业的服务，文档通过共识过程由利益相关方共同开发。尽管文档经过了仔细校验以确保其正确性和技术准确性，但EPCglobal Inc.并不保证文档完全无误，也不保证文档不会随着经验和技术进步而需要修改，或者在任何应用中都适用。文档使用需注意EPCglobal Inc.不承担任何法律责任，并明确规定了未经授权不得复制、修改或使用该文档。 #### 三、协议特点与应用场景 **1. 特点：** - **低层接口设计**：RFID EPC GEN2协议定义了一个低层接口，使得客户端能够控制RFID空气协议的操作时序并访问空气协议命令参数。 - **互操作性**：该协议支持不同制造商生产的RFID设备间的互操作，促进了供应链管理中的标准化。 - **灵活性**：协议设计考虑到了未来可能的技术进步和需求变化，具有较好的扩展性。 **2. 应用场景：** - **供应链管理**：RFID EPC GEN2协议广泛应用于物流和供应链管理中，通过自动化的物品追踪提高效率。 - **零售业**：零售商可以利用RFID技术进行库存管理，减少人工错误并提升顾客体验。 - **医疗保健**：在医疗领域，RFID可用于药品跟踪、患者识别等关键应用中，有助于提高医疗服务的安全性和效率。 - **资产管理**：企业和机构可通过RFID技术实现对资产的有效管理和监控，如跟踪办公设备的位置变化。 #### 四、关键技术要点 **1. 空气接口协议**：RFID EPC GEN2协议规定了标签与读写器之间的无线通信标准，包括数据传输格式、频率范围和调制方式等。 **2. 命令集**：定义了一系列基本命令，如读取、写入、锁定标签等，允许客户端通过这些命令对标签进行操作。 **3. 反碰撞机制**：为了解决多个标签同时响应读写器查询时产生的冲突问题，RFID EPC GEN2协议采用了先进的反碰撞算法，提高了系统整体性能。 **4. 安全特性**：包括数据加密、身份验证等安全措施，确保RFID系统的安全性。 #### 五、结论 RFID EPC GEN2协议作为一项重要的行业标准，对于推动RFID技术的应用和发展起到了关键作用。它不仅提高了RFID系统的互操作性和灵活性，还为众多行业提供了高效、可靠的数据采集解决方案。随着技术的不断进步和应用场景的扩展，RFID EPC GEN2协议将持续发挥其重要作用，并有可能在未来得到进一步的发展和完善。

资源详情

资源评论

Low Level Reader Protocol (LLRP), Version 1.0.1

Ratified Standard with Approved Fixed Errata

August 13, 2007

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.

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

epcglobal@epcglobalinc.org. 24

EPCglobal Inc.

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

document was developed through a consensus process of interested parties. Although efforts 27

have been to assure that the document is correct, reliable, and technically accurate, EPCglobal 28

Inc. makes NO WARRANTY, EXPRESS OR IMPLIED, THAT THIS DOCUMENT IS 29

CORRECT, WILL NOT REQUIRE MODIFICATION AS EXPERIENCE AND TECHNOLOGICAL 30

ADVANCES DICTATE, OR WILL BE SUITABLE FOR ANY PURPOSE OR WORKABLE IN 31

ANY APPLICATION, OR OTHERWISE. Use of this Document is with the understanding that 32

EPCglobal Inc. has no liability for any claim to the contrary, or for any damage or loss of any 33

kind or nature 34

Abstract 35

This document specifies an interface between RFID Readers and Clients. The interface

protocol is called low-level because it provides control of RFID air protocol operation

timing and access to air protocol command parameters. The design of this interface

recognizes that in some RFID systems, there is a requirement for explicit knowledge of

RFID air protocols and the ability to control Readers that implement RFID air protocol

communications. It also recognizes that coupling control to the physical layers of an

RFID infrastructure may be useful for the purpose of mitigating RFID interference.

Audience for this document

The target audience for this specification includes:

RFID Network Infrastructure vendors

Reader vendors

EPC Middleware vendors

System integrators

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 www.epcglobalinc.org for more information.

This draft fixes errata in version 1.0 of LLRP that was ratified on April 12, 2007. A

summary of the fixed errata is contained in the table below. Note that Section and Line

numbers referenced are per version 1 of LLRP. Line numbers may be slightly different in

this version 1.0.1.

Comments on this document should be sent to the EPCglobal Software Action Group

Reader Operations Working Group mailing list at

sag_readerop@epclinklist.epcglobalinc.org. 59

60 Fixed Errata

Section# Line # Description Disposition

16.2.3.4.1 2921 It should be a generic UHF

RFModeTable Parameter (1-n)

with Notes under the parameter

that for C1G2 it is

UHFC1G2RFModeTable

Replace with UHF RFMode Table

Parameter (1-n)

15.2.1.3.1.1 2402 No length field Remove the length field from the

abstract

15.2.1.2.1.1.1 2309 No length field Remove the length field from the

abstract

9.2.1.1 1269 Range of Rx sensitivity 0-128 (relative to max sensitivity)

16.1.2 2593 C1G2LLRPCapabilities should be

replaced by

AirProtocolLLRPCapabilities

Parameter (0-1)

Replace with

AirProtocolLLRPCapabilties

Parameter (0-1)

9.2.4.1.2.1 1336 This is followed by a list of the

frequencies (in Khz) in hop table

order. The position of a frequency

in the list is its ChannelIndex.

(These are used by the hopping

event parameter)

This is followed by a list of the

frequencies (in Khz) in hop table

order. The one-based position of a

frequency in the list is its

ChannelIndex (i.e. the first

frequency is referred to as

ChannelIndex 1)

9.2.4.1.2.2 1343 This parameter carries the fixed

frequency list that can be used by

the Reader. The position of a

frequency in the list is its

ChannelIndex.

This parameter carries the fixed

frequency list that can be used by

the Reader. The one-based

position of a frequency in the list is

its ChannelIndex (i.e. the first

frequency is refered to as

ChannelIndex 1…)

12.2.6.2,

13.2.3.8,

13.2.6.2

1825,

2013,

2105

TheseChannelIndexes are used

by the RfTransmitter Parameter ,

Channel Index Parameter,

HoppingEventParameter

Possibly denote in these usages

that they are 1-based

11.1.3 1552 Delete access spec does not allow

0 like all other access spec

commands. This is believed to be

an errata

Possibly add zero to mean all

access specs, as in other access

spec commands.

16.2.7.1 3088 Custom parameter is 0-1. All

others are 0-N. This is believed to

be an errata

Extend this to 0-N to correct errata

16 2535,

2538

Encoding example:: message

length is 32 bits, but shown as 16

bits and 32-bit messageID is not

shown

Correct figures to match

documentation

14.2.2,

16.2.8.1

2215,

3270

The abstract

LLRPStatusParameter contains a

field called statusCode. The

binding references the same field

as ErrorCode

Correct binding section to match

abstract

16.4 3480 In 16.4, table 5,

"ReaderSensitivityTableEntry"

should be

ReceiveSensitivyTableElement

Change ReaderSensitivity to

ReceiveSensitivity

10.2.1,

16.2.4.1

1452,

2947

In 10.2.1, the field "Current State"

is listed as the last element of the

ROSpec Parameter, the binding

lists the same field as the 4th last

element.

Change position of "Current State"

field in abstract ROSpec

Parameter

16.4 3742 ReadEventNotification Change to

ReaderEventNotification

8.2 1194 Possible Values 0-255 Remove possible values.

Changed to unsigned integer

6.1 717 An AISpec binds a stop trigger and

a set of antennas to a set of

InventoryParameterSpecs and is

identified by a spec Identifier

Change the spec Identifyer to a

"one-based index called the

SpecIndex"

Contents 62

100

101

102

103

104

INDEX OF FIGURES................................................................................................................................13

INDEX OF TABLES.................................................................................................................................. 14

1 (INFORMATIVE) GLOSSARY...................................................................................................... 15

2 INTRODUCTION............................................................................................................................. 18

3 ROLE WITHIN THE EPCGLOBAL NETWORK ARCHITECTURE...................................... 19

4 TERMINOLOGY AND TYPOGRAPHICAL CONVENTIONS................................................. 21

5 OVERVIEW OF LLRP.................................................................................................................... 21

5.1 TYPICAL LLRP TIMELINE .......................................................................................................... 22

6 LLRP OPERATION......................................................................................................................... 23

6.1 INVENTORY, RF SURVEY AND ACCESS OPERATIONS ................................................................. 23

6.1.1 Operation Triggers............................................................................................................... 32

6.1.1.1 Summary.................................................................................................................................... 32

6.1.1.2 Reader Operation Triggers......................................................................................................... 33

6.1.1.3 Access Operation Triggers......................................................................................................... 34

6.2 REPORTING, EVENT NOTIFICATION AND KEEPALIVES................................................................ 34

7 MESSAGES, PARAMETERS AND FIELDS................................................................................ 35

7.1 OVERVIEW ................................................................................................................................. 35

7.1.1 Formatting Conventions....................................................................................................... 35

7.1.2 Messages............................................................................................................................... 36

7.1.3 Parameters ........................................................................................................................... 37

7.1.3.1 General Parameters .................................................................................................................... 37

7.1.3.1.1 Timestamp............................................................................................................................ 37

7.1.3.1.1.1 UTCTimestamp Parameter............................................................................................. 37

7.1.3.1.1.2 Uptime Parameter........................................................................................................... 37

7.1.4 Fields.................................................................................................................................... 38

7.1.5 Functional Grouping............................................................................................................ 38

7.1.6 LLRP Messages and Actions ................................................................................................ 40

8 CUSTOM EXTENSION .................................................................................................................. 41

8.1 CUSTOM_MESSAGE.............................................................................................................. 42

8.2 CUSTOM PARAMETER................................................................................................................. 42

8.3 CUSTOM EXTENSION IN COMMANDS.......................................................................................... 42

8.4 CUSTOM EXTENSION IN INDIVIDUAL LLRP PARAMETERS ......................................................... 43

8.5 ALLOWABLE PARAMETER EXTENSION....................................................................................... 43

9 READER DEVICE CAPABILITIES.............................................................................................. 43

9.1 MESSAGES ................................................................................................................................. 44

9.1.1 GET_READER_CAPABILITIES .......................................................................................... 44

9.1.2 GET_READER_CAPABILITIES_RESPONSE ..................................................................... 44

9.2 PARAMETERS ............................................................................................................................. 45

9.2.1 GeneralDeviceCapabilities Parameter................................................................................. 45

9.2.1.1 ReceiveSensitivityTableEntry Parameter................................................................................... 45

9.2.1.2 PerAntennaReceiveSensitivityRange Parameter........................................................................ 46

9.2.1.3 PerAntennaAirProtocol Parameter............................................................................................. 46

剩余193页未读，继续阅读

评论收藏

内容反馈

mtea

2018-01-03

谢谢啦，资源棒棒的

RFID EPC GEN2 协议1

评论2

最新资源

RFID EPC GEN2 协议1

评论2

最新资源

相关推荐

RFID EPC GEN2 协议2

EPC 协议--EPC_Class1_Gen2_UHF_RFID_Protocol

Epc GEN2 国际标准协议

EPC-Gen2（ ISO.IEC 18000-6C协议(全中文版)）

EPC Gen2 中文版.pdf

符合EPC 1类第2代标准的RFID的高效所有权转移协议

EPC Class-1 Gen2 UHF RFID V2.0.1最新版协议

RFID国际标准—EPC & GEN2

面向EPC Gen2标准的RFID标签分组多位隙并行识别协议

EpcGen2.rar_6c_RFID UHF_UHF EPC_gen2_rfid协议

论文研究-EPCglobal Class 1 Gen 2标准的RFID高效双向认证协议.pdf

RFID通信协议

EPCglobalClass1Gen2标准的RFID高效双向认证协议.pdf

一种基于ECC的RFID认证协议

RFID EPC GEN2 协议3

RFID EPC Gen2技术问答

Q&A：RFID EPC Gen2区块和命令技术问答

EPC Gen2 英文版

RFID EPC码协议文档

RFID技术与标准协定，epc

GS1-EPC-Gen2v2-UHF-AirInterface_i21_r_2018-09-04.pdf

EPC C1G2 协议

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

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

EPC-C1G2(18000-6C)协议

GEN2协议CRC工具