NFC Forum Type 2 Tag 操作规范详解

NFC

需积分: 5 42 浏览量更新于2024-06-22 收藏 482KB PDF 举报

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

领优惠券(最高得80元）

"Type 2 Tag Operation Specification - NFC Forum TM Type2TagOperation 技术规范，版本1.2，2014-03-27" NFC（近场通信）是一种短距离无线通信技术，它允许设备在非常近的距离内交换数据。"Type 2 Tag Operation Specification" 是NFC Forum制定的一份技术文档，详细规定了Type 2标签的操作规范。Type 2标签是NFC技术中常见的非接触式智能卡类型之一，常用于各种应用场景，如支付、信息读取、身份验证等。这份规范的主要内容可能包括以下方面： 1. **协议栈结构**：Type 2标签操作规范会描述NFC协议栈的基本结构，包括物理层、数据链路层和应用层的交互机制。 2. **命令集**：规范详细定义了对Type 2标签进行读写操作的命令集，如初始化、读块、写块、锁定块等。这些命令使得设备能够与Type 2标签进行有效的通信。 3. **数据存储**：Type 2标签通常采用EEPROM（电可擦可编程只读存储器）作为数据存储介质，规范会详细说明其存储结构，包括块大小、内存布局以及错误校验机制。 4. **安全机制**：规范可能会涵盖如何实现数据的安全性，例如通过区块锁定防止未经授权的修改，以及可能的加密和认证过程。 5. **兼容性和互操作性**：NFC Forum的目标是确保不同厂商的产品之间可以无缝协作，因此这份规范将强调设备间的兼容性和互操作性标准。 6. **实施指导**：对于开发者和制造商，规范会提供实施建议和注意事项，以帮助他们正确地设计和制造符合Type 2 Tag Operation规范的NFC设备和标签。 7. **版权和许可**：文档指出只有获得NFC Forum许可的接收者才能使用该规范，并且必须遵循许可协议的条款。未授权的用户只能阅读，不能实施或使用规范中的内容。 8. **更新和获取方式**：有兴趣的个人或公司可以通过NFC Forum的官方网站获取最新版本的规范及实施权利，但需同意当时的许可条款。理解并遵循"Type 2 Tag Operation Specification"对于开发和设计NFC Type 2标签系统至关重要，它为实现可靠、安全且符合行业标准的NFC应用提供了基础框架。

资源详情

资源推荐

Memory Structure and Management

Type 2 Tag Operation Page 5

Byte Number

UID / Internal

Internal0

Internal1

Internal2

Internal3

Serial Number

Internal / Lock

Internal4

Internal5

Internal6

Internal7

Internal8

Internal9

Lock0

Lock1

Data0

Data1

Data2

Data3

Data4

Data5

Data6

Data7

Data8

Data9

Data10

Data11

Block

Data

CC0

CC1

CC2

CC3

Data

Figure 1: Static Memory Structure

2.1.1 Internal Bytes

These bytes are reserved for manufacturing use.

[RQ_T2T_MEM_001] The NFC Forum Device SHALL NOT use internal bytes to store

information data.

2.1.2 Static Lock bytes

The bits of byte 2 and 3 of block 2 represent the field-programmable read-only locking

mechanism called “static lock bytes”. Depending on the value of the bits of the static lock bytes,

two configurations are possible:

• All bits are set to 0b, and the CC area and the data area of the tag can be read and written.

• All bits are set to 1b, and the CC area and the data area of the tag can only be read.

The locking bits are set to 1b via a standard write command to block 2 (BNo = 2). For more

details, see Section 5.2.

[RQ_T2T_MEM_002] To set all static lock bits to 1b, the NFC Forum Device SHALL set Bytes

Lock0 and Lock1 to FFh using the WRITE command to change the value of Block 2. Bytes

internal8 and Internal9 of Block2 can be set to any value.

This process is irreversible: if one bit of the lock bytes is set to 1b, it cannot be changed back to

0b.

2.1.3 Capability Container

The Capability Container (CC) manages the information of the Type 2 Tag Platform. The four

bytes of block 3 contain the CC. See Section 6.1 for a detailed description of the CC.

Memory Structure and Management

Type 2 Tag Operation Page 7

NOTE Dynamic lock bytes and reserved bytes might be located at any byte address in

between or at the end of the data areas starting from block 16. A more detailed

example of dynamic memory structure is shown in Appendix C.2.

Compared to the static memory structure, the dynamic memory structure might contain optional

configuration information to describe details of dynamic lock bits and to identify reserved

memory areas in the data area using the Lock Control TLV and the Memory Control TLV (see

Section 2.3).

A more detailed example of Dynamic Memory Layout can be found in Appendix C.2. This

example includes also Memory Control TLV, Lock Control TLV and Dynamic Lock Bytes.

2.2.1 Reserved Bytes

The reserved bytes belong to reserved memory areas.

[RQ_T2T_MEM_004] The NFC Forum Device SHALL ignore and jump over the reserved

bytes during read and write operations. Reserved bytes are identified by one or more Memory

Control TLV blocks (see Section 2.3.3).

2.2.2 Static and Dynamic Lock Bits

A tag with a dynamic memory structure contains two kinds of lock bits:

• Static lock bits as specified in Section 2.1.2

• Dynamic lock bits described below in this section

The dynamic lock bits are called “dynamic” because their position(s) inside the tag can change.

This is in contrast to the static lock bytes because their position is fixed (see Section 2.1.2).

Lock areas are only needed on Type 2 Tag Platform that allows the transition from

READ/WRITE state to READ-ONLY state (see Section 6.4.4).

[RQ_T2T_MEM_005] The NFC Forum Device SHALL ignore and jump over the bytes that

belong to lock areas during read operations of NFC Forum data inside Type 2 Tag Platform in

READ-ONLY state (see Section 6.3).

The default settings of the dynamic lock bits are:

• The position of the dynamic lock bits starts from the first byte after the data area (see

Section 2.2.3 and Figure 2). The bytes that contain the dynamic lock bits are called “dynamic

lock bytes”.

• The number of dynamic lock bits is equal to data area size minus 48 (in bytes) divided by 8.

If the division result is not an integer, the number of lock bytes is equal to the closest integer

that is bigger than the division result. That is:

 

8)48( −= zeDataAreaSiitsnamicLockBNumberOfDy

The number of dynamic lock bytes is equal to:





64)48( −= zeDataAreaSiytesnamicLockBNumberOfDy

[RQ_T2T_MEM_006] When the number of the dynamic lock bits is not a multiple of 8, the last

dynamic lock byte is partially filled with these bits. In this byte, the dynamic lock bits are located

starting from the lsb to the msb. The part of the byte that does not contain dynamic lock bits is

filled with reserved bits that the NFC Forum Device SHALL always set to 0b.

剩余56页未读，继续阅读

txf123

粉丝: 21
资源: 14

会员权益专享

NFC Forum Type 2 Tag 操作规范详解

NFC Forum Type 2 Tag

NFC Forum Type 1 Tag Operation Specification 1.2.pdf

NFC Forum Type 1 Tag Operation Specification

type Tag struct { ID int64 // tag的主键 Name string } type Operation struct { Add []Tag // 新增的tag Del []Tag // 删除的tag }

uniapp怎么给uni-tag动态赋值type

Can't determine type for tag

父级的点击事件，如何排除分类按钮区域 {{ item.title }} <el-tag v-for="type in item.typeList" :key="type" type="info" style="margin-left: 2px"> {{ type }} </el-tag>

<el-tag :type="item.type" effect="dark"> {{ item.status}}</el-tag> item.status等于0离网等于1空闲等于2占用怎么写

cannot convert ‘ipp_tag_e’ to ‘ipp_t*’ {aka ‘_ipp_s*’} 153 | response = cupsDoRequest(CUPS_HTTP_DEFAULT, "localhost:631", ippNewRequest(IPP_OP_GET_JOB_ATTRIBUTES), ippAddInteger(IPP_TAG_OPERATION, IPP_TAG_JOB, IPP_TAG_INTEGER, "job-id", job_id), NULL);

会员权益专享

最新资源

父级的点击事件，如何排除分类按钮区域

{{ item.title }}

<el-tag v-for="type in item.typeList" :key="type" type="info" style="margin-left: 2px"> {{ type }} </el-tag>

cannot convert ‘ipp_tag_e’ to ‘ipp_t’ {aka ‘_ipp_s’} 153 | response = cupsDoRequest(CUPS_HTTP_DEFAULT, "localhost:631", ippNewRequest(IPP_OP_GET_JOB_ATTRIBUTES), ippAddInteger(IPP_TAG_OPERATION, IPP_TAG_JOB, IPP_TAG_INTEGER, "job-id", job_id), NULL);