没有合适的资源?快使用搜索试试~ 我知道了~
资源推荐
资源详情
资源评论
AN10927
MIFARE and handling of UIDs
Rev. 2.0 — 01 September 2010
190720
Application note
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. 2010. All rights reserved.
Application note
PUBLIC
Rev. 2.0 — 01 September 2010
190720
2 of 18
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
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
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.
AN10927 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2010. All rights reserved.
Application note
PUBLIC
Rev. 2.0 — 01 September 2010
190720
3 of 18
NXP Semiconductors
AN10927
MIFARE and handling of UIDs
(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
AN10927 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2010. All rights reserved.
Application note
PUBLIC
Rev. 2.0 — 01 September 2010
190720
4 of 18
剩余17页未读,继续阅读
AndrewSoyal
- 粉丝: 0
- 资源: 1
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
- 1
- 2
前往页