EPC Tag Data Standard: Gen 2 RFID标签内存内容规范

需积分: 10 89 浏览量更新于2024-07-16 收藏 2.87MB PDF 举报

"GS1_EPC_TDS_i1_10.pdf" 是关于EPC (Electronic Product Code) 标签数据标准的文档，该标准详细定义了电子产品代码及其在Gen 2 RFID标签上的内存内容。文档涵盖了EPC的规格，包括在EPCglobal架构的不同层次上的表示以及与GS1键和其他现有代码的对应关系。此外，它还规定了存储在Gen 2 RFID标签上的数据，如EPC、用户内存数据、控制信息和标签制造信息。 EPC（电子产品代码）是RFID（无线频率识别）系统中用于唯一标识物体的一种编码体系。此标准的Release 1.10版本于2017年3月被批准，由多个组织和个人共同编辑和贡献，包括GS1 Global Office、Ken Traub Consulting LLC、USTRANSCOM (DoD)、GS1 US、GS1 Switzerland、GS1全球办公室、GS1 Netherlands和GS1 Germany等。 EPC Tag Data Standard的核心内容可以分为两个主要部分： 1. **电子产品代码（Electronic Product Code）的规范**：EPC是一个在全球范围内通用的、唯一的数字标识符，用于识别物理对象。它在EPCglobal架构的不同层级上具有不同的表示形式，确保在供应链的各个阶段都能准确无误地识别物品。EPC还与GS1键和其他现有的编码系统兼容，例如条形码，以支持跨行业的互操作性。 2. **Gen 2 RFID标签的数据规格**：这部分规定了Gen 2 RFID标签上的内存结构和数据内容。Gen 2是RFID技术的一个重要标准，提供更高的数据容量和更灵活的操作特性。标签内存包括： - **EPC**：这是标签的主要部分，存储着物品的唯一标识。 - **用户内存**：用户可以自定义这部分内存，通常用于存储额外的物品信息，如生产日期、批号或定制的业务数据。 - **控制信息**：这些信息可能包括访问权限、读写控制和安全特征，以保护数据免受未经授权的访问或篡改。 - **标签制造信息**：这些数据包含关于标签本身的元信息，如制造商标识、芯片类型和序列号，有助于跟踪和管理标签。这个标准对于实现高效、安全的RFID系统至关重要，它确保了不同供应商的标签和阅读器之间的互操作性，并提供了统一的数据结构，以便在供应链管理、库存控制、物流追踪等多个领域实现自动化和信息化。通过遵循EPC Tag Data Standard，企业可以利用RFID技术提高效率、减少错误，并增强对供应链透明度的掌控。

EPC Tag Data Standard

Section 7.9 specifies the Pure Identity Pattern URI, which is a syntax for representing sets of 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-specific forms of the

EPC as well as other data apart from the EPC that may be stored on Gen 2 RFID 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 bank of 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 capture process by providing hints about

what kind of object the tag is affixed to. Control information is not part of the EPC, and does

comprise any part of the unique identity of a tagged 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 may be other tags present, such as reading a pallet tag in the presence of

a large number of item-level tags, and “attribute bits” (Section

11 ) that provide additional special

attribute information such as alerting to the presence of hazardous material. The same “attribute

bits” are available regardless of what kind of EPC is used, whereas the available “filter values” are

different depending on the type of EPC (and with certain types of EPCs, no filter value is available at

all).

Section 12 specifies the “tag” Uniform Resource Identifiers, which is a compact string representation

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 in Sections

10 and 11 . In the “tag” URI, the

EPC content of the EPC memory bank is represented in a form similar to the Pure Identity EPC URI.

Unlike the Pure Identity EPC URI, however, the “tag” URI also includes the control information

content of the EPC memory bank. The “tag” URI form is recommended for use in capture

applications that need to read control information in order to capture data correctly, or that need to

write the full contents of the EPC memory bank. “Tag” URIs are used in the Application Level 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 of related RFID

tags based on their EPC content, such as all tags containing EPCs for a given range of serial

numbers for a given trade item.

Sections 14 and 14.5.1.2 specify the contents of the EPC memory bank of a Gen 2 RFID tag at the

bit level. Section 14 specifies how to translate between the “tag” URI and the EPC Binary Encoding.

The binary encoding is a bit-level representation of what is actually stored on the tag, and is also

what is carried via the Low Level Reader Protocol (LLRP) interface. Section

14.5.1.2 specifies how

this binary encoding is combined with attribute 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.

Section 17 specifies the binary encoding of the User memory bank of Gen 2 RFID Tags.

4 The Electronic Product Code: A universal identifier for

physical objects

The Electronic Product Code is designed to facilitate business processes and applications that need

to manipulate visibility data – data about observations of physical objects. The EPC is a universal

identifier that provides a unique identity for any physical object. The EPC is designed to be unique

across all physical objects in the world, over all time, and across all categories of physical objects. It

is expressly intended for use by business applications that need to track all categories of physical

objects, whatever they may be.

By contrast, nine GS1 identification keys defined in the GS1 General Specifications [GS1GS17.0] can

identify categories of objects (GTIN), unique objects (SSCC, GLN, GIAI, GSRN, CPID), or a hybrid

(GRAI, GDTI, GCN) that may identify either categories or unique objects depending on the absence

or presence of a serial number. (Two other keys, GINC and GSIN, identify logical groupings, not

physical objects.) The GTIN, as the only category identification key, requires a separate serial

number to uniquely identify an object but that serial number is not considered part of the

identification key.

EPC Tag Data Standard

There is a well-defined correspondence between EPCs and GS1 keys. This allows any physical object

that is already identified by a GS1 key (or GS1 key + serial number combination) to be used in an

EPC context where any category of physical object may be observed. Likewise, it allows EPC data

captured in a broad visibility context to be correlated with other business data that is specific to the

category of object involved and which uses GS1 keys.

The remainder of this section elaborates on these points.

4.1 The need for a universal identifier: an example

The following example illustrates how visibility data arises, and the role the EPC plays as a unique

identifier for any physical object. In this example, there is a storage room in a hospital that holds

radioactive samples, among other things. The hospital safety officer needs to track what things have

been in the storage room and for how long, in order to ensure that exposure is kept within

acceptable limits. Each physical object that might enter the storage room is given a unique

Electronic Product Code, which is encoded onto an RFID Tag affixed to the object. An RFID reader

positioned at the storage room door generates visibility data as objects enter and exit the room, as

illustrated below.

Figure 4-1 Example Visibility Data Stream

As the illustration shows, the data stream of interest to the safety officer is a series of events, each

identifying a specific physical object and when it entered or exited the room. The unique EPC for

each object is an identifier that may be used to drive the business process. In this example, the EPC

(in Pure Identity EPC URI form) would be a primary key of a database that tracks the accumulated

exposure for each physical object; each entry/exit event pair for a given object would be used to

update the accumulated exposure database.

This example illustrates how the EPC is a single, universal identifier for any physical object. The

items being tracked here include all kinds of things: trade items, reusable transports, fixed assets,

service relations, documents, among others that might occur. By using the EPC, the application can

use a single identifier to refer to any physical object, and it is not necessary to make a special case

for each category of thing.

Visibility Data Stream at Storage Room Entrance

Time

In /

Out

EPC

Comment

8:23am

urn:epc:id:sgtin:0614141.012345.62852

10cc Syringe #62852

(trade item)

8:52am

urn:epc:id:grai:0614141.54321.2528

Pharma Tote #2528

(reusable transport)

8:59am

urn:epc:id:sgtin:0614141.012345.1542

10cc Syringe #1542

(trade item)

9:02am

Out

urn:epc:id:giai:0614141.17320508

Infusion Pump #52 (fixed

asset)

9:32am

urn:epc:id:gsrn:0614141.0000010253

Nurse Jones (service

relation)

9:42am

Out

urn:epc:id:gsrn:0614141.0000010253

Nurse Jones (service

relation)

9:52am

urn:epc:id:gdti:0614141.00001.1618034

Patient Smith’s chart

(document)

RFID Reader

Hospital

Storage Room

EPC Tag Data Standard

4.2 Use of identifiers in a Business Data Context

Generally speaking, an identifier is a member of set (or “namespace”) of strings (names), such that

each identifier is associated with a specific thing or concept in the real world. Identifiers are used

within information systems to refer to the real world thing or concept in question. An identifier may

occur in an electronic record or file, in a database, in an electronic message, or any other data

context. In any given context, the producer and consumer must agree on which namespace of

identifiers is to be used; within that context, any identifier belonging to that namespace may be

used.

The keys defined in the GS1 General Specifications [GS1GS17.0] are each a namespace of

identifiers for a particular category of real-world entity. For example, the Global Returnable Asset

Identifier (GRAI) is a key that is used to identify returnable assets, such as plastic totes and pallet

skids. The set of GRAI codes can be thought of as identifiers for the members of the set “all

returnable assets.” A GRAI code may be used in a context where only returnable assets are

expected; e.g., in a rental agreement from a moving services company that rents returnable plastic

crates to customers to pack during a move. This is illustrated below.

Figure 4-2 Illustration of GRAI Identifier Namespace

The upper part of the figure illustrates the GRAI identifier namespace. The lower part of the figure

shows how a GRAI might be used in the context of a rental agreement, where only a GRAI is

expected.

GRAI = 0614141000234AB23 (100 liter tote #AB23)

GRAI = 0614141000517XY67 (500 liter tote #XY67)

GRAI = 0614141000234AB24 (100 liter tote #AB24)

GRAIs: All returnable

assets

<Items>

…

Establishes the context as returnable assets

Therefore, any GRAI could go

here (and nothing else)

EPC Tag Data Standard

Figure 4-3 Illustration of EPC Identifier Namespace

In contrast, the EPC namespace is a space of identifiers for any physical object. The set of EPCs can

be thought of as identifiers for the members of the set “all physical objects.” EPCs are used in

contexts where any type of physical object may appear, such as in the set of observations arising in

the hospital storage room example above. Note that the EPC URI as illustrated in Figure 4-3

includes strings such as sgtin, grai, and so on as part of the EPC URI identifier. This is in

contrast to GS1 Keys, where no such indication is part of the key itself; instead, this is indicated

outside of the key, such as in the XML element name

<grai> in the example in Figure 4-2 in the

Application Identifier (AI) that accompanies a GS1 key in a GS1 element string.

4.3 Relationship between EPCs and GS1 keys

There is a well-defined relationship between EPCs and GS1 keys. For each GS1 key that denotes an

individual physical object, there is a corresponding EPC, including both an EPC URI and a binary

encoding for use in RFID tags. In addition, each GS1 key that denotes a class or grouping of

physical objects has a corresponding URI form. These correspondences are formally defined by

conversion rules specified in Section 7

, which define how to map a GS1 key to the corresponding

EPC value and vice versa. The well-defined correspondence between GS1 keys and EPCs allows for

seamless migration of data between GS1 key and EPC contexts as necessary.

EPCs:

All physical objects

EPC =

urn:epc:id:sgtin:0614141.012345.62852

(

10cc Syringe #62852 – trade item)

EPC =

urn:epc:id:grai:0614141.54321.2528

(Pharma Tote #2528 – reusable asset)

<epc>urn:epc:id:sgtin:0614141.012345.62852</epc>

…

Establishes the context as all physical objects

Therefore, any EPC could go here

剩余199页未读，继续阅读

jrdshhw

粉丝: 0
资源: 8

EPC Tag Data Standard: Gen 2 RFID标签内存内容规范

USB_driver.rar_TDS510-B_tds510_tds510 driver_tds510 驱动_tds510驱动

''' Firmware : JXTC104Q Serial number : S6KLNE0RC50859 Model : Micron_5300_MTFDDAK480TDS Model : SAMSUNG MZ7L3480HCHQ-00B7C ''' 正则匹配的方法法，同时可以匹配取出Model 中的Micron_5300_MTFDDAK480TDS 和 MZ7L3480HCHQ-00B7C

[''' Array : 0 Vendor : ATA Model : SAMSUNG MZ7L3480HCHQ-00B Firmware : JXTC104Q''', ''' Array : 1 Vendor : ATA Model : Micron_5300_MTFDDAK480TDS Firmware : D3MU001'''] python正则匹配Model那行，返回['MZ7L3480HCHQ-00B','Micron_5300_MTFDDAK480TDS']

soap_call___tds__GetCapabilities(&soap, endpoint, NULL, &req, &rep);

调用soap_call___tds__GetDeviceInformation函数需要加入什么头文件

‘SAMSUNG MZ7L3480HCHQ-00B7C’ ‘Micron_5300_MTFDDAK480TDS’ 如果字符串中有空格，则空格分隔取最后的内容，没有空格的原字符串，原值返回

stm32 TDS c文件 h文件代码

tds传感器ADC转换代码

使用gSOAP生成ONVIF框架代码

最新资源

soap_call_tdsGetCapabilities(&soap, endpoint, NULL, &req, &rep);

调用soap_call_tdsGetDeviceInformation函数需要加入什么头文件