没有合适的资源?快使用搜索试试~ 我知道了~
温馨提示
试读
21页
This document shows the use of UIDs in contactless smartcard systems. It indicates recommendations about the Random ID, mixed use of 4 byte and 7 byte UIDs in the same system, and it describes the options how to upgrade 4 byte UID systems to accept 7 byte UID smart cards.
资源推荐
资源详情
资源评论
AN10927
MIFARE and handling of UIDs
Rev. 3.1 — 02 October 2013
190731
Application note
COMPANY PUBLIC
Document information
Info
Content
Keywords
Single Size UID, Double Size UID, 4 Byte UID, 7 Byte UID, SNR, NUID,
FNUID, ONUID
Abstract
This document shows the use of UIDs in contactless smartcard systems.
It indicates recommendations about the Random ID, mixed use of 4 byte
and 7 byte UIDs in the same system, and it describes the options how to
upgrade 4 byte UID systems to accept 7 byte UID smart cards.
NXP Semiconductors
AN10927
MIFARE and handling of UIDs
AN10927
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2013. All rights reserved.
Application note
COMPANY PUBLIC
Rev. 3.1 — 02 October 2013
190731
2 of 21
Contact information
For additional information, please visit:
http://www.nxp.com
For sales office addresses, please send an email to:
salesaddresses@nxp.com
Revision history
Rev
Date
Description
3.1
20131002
Typos corrected in Cascade Level 3 (Section 2)
Ultralight EV1 and MIFARE4Mobile added in Table 3 (Section 2.4)
UID with shortcut for MIFARE from mobile added (Section 3.1.2)
CLRC663, CRC630, CLRC631, PR601, PRH601 added in
Annex A
Annex C (Source code to derive NUID out of a Double Size UID) added
3.0
20110804
MIFARE Classic next generation added.
2.0
20100901
Bit order corrected (Section 3.2.2), 7 byte MF1 ICS x0 added in Table 4 (Section 3.2.5),
Table 3 updated (Section 2.4)
1.0
20100519
Initial version
NXP Semiconductors
AN10927
MIFARE and handling of UIDs
AN10927
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2013. All rights reserved.
Application note
COMPANY PUBLIC
Rev. 3.1 — 02 October 2013
190731
3 of 21
1. Introduction
This document shows the use of UIDs in contactless smartcard systems. It indicates
recommendations about the use of Random ID, the mixed use of 4 byte (single size) and
7 byte (double size) UIDs in the same system, and it describes the options how to
upgrade 4 byte UID systems to use 7 byte UID smart cards.
Note: A UID is not a “serial number”, but a unique identifier. There is no recommendation
how to turn the array of bytes into an integer.
Note: “UID” is a common expression, defined in the ISO/IEC 14443-3. In some case the
UID is even not unique (like RID or NUID, see below).
Note: The 4 byte UID is called “Single Size UID”, too. The 7 byte UID is called “Double
Size UID”, too. The 10 byte UID is called “Triple Size UID”, too.
2. MIFARE and ISO/IEC 14443 UIDs
In this section the use of UIDs according to the ISO/IEC 14443 is described. Fig 1 shows
the three different UID sizes defined in ISO/IEC 14443-3 as they are used during the
anti-collision and selection procedure.
UID0 UID1 UID2 UID3
UID0 UID1
UID2 UID3CT UID4
UID5 UID6
UID3 UID4 UID5
UID6
CT
UID7 UID8 UID9
4 byte UID
7 byte UID
10 byte UID
Cascade Level 1 Cascade Level 2
Cascade Level 3
BCC
BCCBCC
UID0
UID1 UID2CT BCC BCC BCC
(1) BCC = Block Check Character, it is calculated as exclusive-or over the 4 previous bytes.
(2) CT = Cascade Tag, to indicate a following cascade level.
Fig 1. UIDs according to ISO/IEC 14443
Fig 2 shows the Anticollision sequence, which is a mandatory part of the card activation
sequence. It automatically selects a single PICC with 4 byte UID (= Single Size UID),
7 byte UID (= Double Size UID) or 10 byte UID (= Triple Size UID).
Cascade Level 1
In the Cascade Level 1 the PCD sends the Anticollision command CL1 (0x93) and the
PICC returns
• either the 4 byte UID (UID0...UID4) and one byte BCC,
• or a Cascade Tag (CT) followed by the first 3 byte of the UID (UID0...UID2) and one
byte BCC.
The CT (0x88) indicates that the UID is not yet complete, and another Cascade Level
has to follow.
NXP Semiconductors
AN10927
MIFARE and handling of UIDs
AN10927
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2013. All rights reserved.
Application note
COMPANY PUBLIC
Rev. 3.1 — 02 October 2013
190731
4 of 21
(3) CT = Cascade Tag
(4) CL = Cascade Level
Fig 2. Anticollision sequence
Note: The UID0 byte of a 4 byte UID must not be 0x88.
The CL1 then must be selected, using the Select command CL1 (0x93). The PICC
returns its SAK CL1, which indicates
• whether the UID is complete or not, and (if so),
− the type of card (for details refer to
[1] and [2]), and
− whether the card supports T=CL.
Cascade Level 2
If the UID is not yet complete, the PCD continues with an Anticollision CL2 command
(0x95), and the PICC returns
• either the last 4 bytes of the Double Size UID (UID3...UID6) and one byte BCC,
• or a Cascade Tag (CT) followed by the next 3 bytes of the Triple Size UID
(UID3...UID5) and one byte BCC.
The CT (0x88) indicates that the UID is not yet complete, and another Cascade Level
has to follow.
Note: The UID3 byte of a 7 byte or 10 byte UID must not be 0x88.
The CL2 then must be selected, using the Select command CL2 (0x95). The PICC
returns its SAK CL2, which indicates
• whether the UID is complete or not, and (if so),
− the type of card (refer to
[1] and [2]), and
NXP Semiconductors
AN10927
MIFARE and handling of UIDs
AN10927
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2013. All rights reserved.
Application note
COMPANY PUBLIC
Rev. 3.1 — 02 October 2013
190731
5 of 21
− whether the card supports T=CL.
Cascade Level 3
If the UID is not yet complete, the PCD continues with an Anticollision CL3 command
(0x97), and the PICC returns
• the last 4 bytes of the Triple Size UID (UID6...UID9) and one byte BCC.
The CL3 then must be selected, using the Select command CL3 (0x97). The PICC
returns its SAK CL3, which indicates
• the type of card (refer to [1] and [2]), and
• whether the card supports T=CL.
2.1 Single Size UID
The single size UID contains 4 bytes. As shown in Table 1, the value of the UID0 byte
defines how those 4 bytes shall be interpreted.
Table 1. Assignment of Single Size UIDs
POR = Power on reset
UID0 [Hex]
Definition
Range
08
RID: UID1, UID2 and UID3 are dynamically generated
during or after each Power-On-Reset (POR).
appr. 16 million
x0... x7
Proprietary use (i.e. used for MIFARE)
appr. 2.1 billion
18…78, 98…E8
Proprietary use (i.e. used for MIFARE)
appr. 218 million
x9...xE
Proprietary use (i.e. used for MIFARE)
appr. 1.6 billion
xF
Fixed number, non-unique
appr. 268 million
88
Cascade Tag
-
F8
RFU
-
Note: Single Size UIDs do not have a manufacturer code.
Note: The use of Single Size UIDs (unique ones) might end soon, since the number of
usable IDs is limited to approximately 3.7 billion pieces only.
2.1.1 Random ID (RID)
A single size UID with UID0 = 0x08 indicates a Random Identifier. The Random ID (RID)
is dynamically generated, when the PICC powers up. Deselecting a PICC does not reset
the RID, but a field reset does.
Note: RID is always limited to 4 bytes.
Note: Depending on the PICC implementation, a UID (i.e. Double Size UID) may be
retrieved from the card by proprietary means after the PICC is selected with its RID.
剩余20页未读,继续阅读
资源评论
- wxlainiyy2018-12-25资料不错,非常好,帮助非常大
- 阿杰与西门吹雪2018-12-17对学习mifare卡处理7字节的方式很有用处,不错的资料。
- qq_233359272020-08-11好东西啊啊啊啊
- newdible2014-09-29非常有用的资料,谢谢分享。目前正在研究mifare1系统如何处理7字节的UID问题
onlineit
- 粉丝: 5
- 资源: 24
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- 《基于51单片机和DS18B20的温度检测和报警系统,可设置报警温度上下限,输出温度采用数码管显示 》+源代码+设计资料
- ESP8266WIFI系统工作原理图.schdoc
- C语言《基于STM32的测量温度与压力的数据处理设计 》+源代码+设计资料
- ApkTool,安卓逆向工具
- prompt技术资料AI资料.zip
- 基于NeRF方法实现校园内真实拍摄场景的三维重建和web端实时渲染源码.zip
- HCIA-Data Center Facility V2.0.zip
- 物联网场景下的协同通信技术.pptx
- 大语言模型的微调和推理baichuan7B, chatglm2-6B, Qwen-7B-chat源码.zip
- 环境光谱特征数据库系统的建设.docx
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功