OMO ElectronicOMO Electronic
Expand menu
Hello, Sign inMy Account
0 Cart

NT4H1321G0DUD/062V

P1-P3P4-P6P7-P9P10-P12P13-P15P16-P16
NXP Semiconductors
NT4H1321
NTAG 413 DNA Secure Unique NFC Message for direct access to web services
NT4H1321_SDS All information provided in this document is subject to legal disclaimers. © NXP B.V. 2017. All rights reserved.
Product short data sheet Rev. 3.2 — 12 October 2017
COMPANY PUBLIC 400232 7 / 16
8 Functional description
8.1 File system
The file system is according to NFC Forum-TS-Type-4-Tag_2.0 NFC [5]. The application
structure, see Figure 3 of NTAG 413 DNA is fixed and optimized to fulfil the requirements
of the generic and secure NFC applications. In the single application, there is a set of
keys and different access link to those keys can be provided by file settings. Note in the
file setting "CC" stands for change configuration whearas the 32-byte file is called CC
(Capability Container) file
aaa-026094
Change key
AES 128
3 Keys
# 0, # 1, # 2
#E - Free
#F - Never
0
Com.
Plain
R
E
W
CC File (0xE103)
32-byte
Content: CC data
0
R&W
0
CC
0
Com.
Plain
R
E
CMAC
- -
W
E
R&W
E
CC Ctr
0
NDEF Application
ISO/IEC 7816 AID (DF Name) = 0xD2760000850101
NDEF File (0xE104)
128-byte
Empty NDEF message
Figure 3. NDEF Application with default setting
8.1.1 Keys
There are three AES 128-bit keys (key number 0, 1, 2) together with key number
"E" (means free) and key number "F" (means never). By default these 3-keys can be
changed after authentication with key number 0.
8.1.2 CC file
The capability container (CC) file is initialized with the following data field:
"000F20010000FF0406E104008000000000000000000000000000000000000000"
present in "INITIALIZED" state. Date structure of the CC file is explained in [5]. It can
be updated by authenticating with key number 0. The default access right is set as in
Figure 3, write (w), Read &Write (R&W) and change key can be set to any other value or
"F" to make this file read only. To be NDEF complaint the read (R) access shall remain
free (E). One-byte CC file ID is 0x01, is to be used as file number/ ID for the commands
with class byte 0x90, if required.
8.1.3 NDEF file
The NDEF file has an empty NDEF message at delivery. Any NDEF message according
to [5] can be written freely in this file. The write access can be changed to any key or to
never by authentication with the key number 0. For the NDEF file, the CMAC key and Ctr
NXP Semiconductors
NT4H1321
NTAG 413 DNA Secure Unique NFC Message for direct access to web services
NT4H1321_SDS All information provided in this document is subject to legal disclaimers. © NXP B.V. 2017. All rights reserved.
Product short data sheet Rev. 3.2 — 12 October 2017
COMPANY PUBLIC 400232 8 / 16
read key need to be defined at NDEF personalization. At delivery no keys are defined
there and hence the mirroring of UID, NFCCtr, or CMAC are not activated. One-byte
NDEF file ID is 0x02, is to be used as file number/ ID for the commands with class byte
0x90, wherever required
8.2 Communication protocol
NTAG 413 DNA uses ISO/IEC7816-4 [7] type standard APDUs for command-response
pair.
aaa-026096
to PCD
Response data field
to PICCLe
SW1 SW2
CLA INS P1 P2 Lc Command data field
Figure 4. NTAG 413 DNA command response pair
Table 4. Command response pair
Field Description Length
Class byte (CLA) 1
Instruction (INS) 1
Command header
Parameters (P1,P2) 2
Lc field Length of command data field (Lc), absent if no data
field.
1
Command data field Absent if no data Lc
Le field Expected response length. 1
Response data field Response data if any, absent if no response data up to Le
Response trailer status byte (SW1SW2) 2
The field length and presence might vary for different commands, refer to the specific
command description.
8.3 Communication modes
NTAG 413 DNA uses plain communication according to NFC Type 4 Tag operation. But
it also allows encrypted and CMACed communication (especially for write) in case it is
required to update the NDEF (re) personalization in field.
NTAG 413 DNA supports three communication modes. As shown in the following
Table 5, the different communication modes are represented by two bits. This
representation is used at several places in the document.
Table 5. Supported communication modes
Communication mode Bit
representation
Explanation
CommMode.Plain X0 No protection: message is transmitted in clear
CommMode.MAC 01 MAC protection for integrity and authenticity
NXP Semiconductors
NT4H1321
NTAG 413 DNA Secure Unique NFC Message for direct access to web services
NT4H1321_SDS All information provided in this document is subject to legal disclaimers. © NXP B.V. 2017. All rights reserved.
Product short data sheet Rev. 3.2 — 12 October 2017
COMPANY PUBLIC 400232 9 / 16
Communication mode Bit
representation
Explanation
CommMode.Full 11 Full protection for integrity, authenticity and
confidentiality
The communication mode defines the level of security for the communication between
PCD and PICC.
At application and PICC level, the communication mode is defined by the command itself,
as specified in the following table 7. The specified communication mode is applied if
there is an active authentication regardless of whether this authentication is required by
the command or not.
At file level, the communication mode is defined by the file. The specified communication
mode is applied if there is an active authentication. Note however that, under an
active authentication, if the only valid access condition for a certain access right is free
access (0xE), CommMode.Plain is to be applied. The commands for authentication
and changing keys have their own secure messaging rules, as indicated by N/A (not
applicable) in Table 6. If there is no active authentication, the command and response
are sent in plain (or the command is rejected in the case an authentication is required).
Table 6. Overview of expected command Communication Mode for secure messaging
Command Communication mode
Cmd.AuthenticateFirst N/A (command specific)
Cmd.AuthenticateNonFirst N/A (command specific)
Cmd.ChangeFileSetting CommMode.Full
Cmd.ChangeKey N/A (command specific)
Cmd.ReadNFCCounter CommMode.Full
Cmd.GetFileSetting CommMode.MAC
Cmd.GetKeyVersion CommMode.MAC
Cmd.GetVersion CommMode.MAC
Cmd.ReadData CommMode of targeted file.
Cmd.SetConfiguration CommMode.Full
Cmd.WriteData CommMode of targeted file.
9 Supported commands and APDUs
Table 7. NTAG413 DNA APDUs
Command C-APDU (hex) R-APDU
INS CLA INS P1 P2 Lc Data Le Data SW1
SW2
Cmd.SELECT 00 A4 XX XX XX Data to send XX response 9000
Cmd.READ BINARY 00 B0 XX XX - - XX response 9000
Cmd.UPDATE BINARY 00 D6 XX XX XX Data to write - - 9000
Cmd.AuthenticateFirst 90 71 00 00 XX Reference
data
00 Data 9100
Cmd.AuthenticateNonFirst 90 77 00 00 XX Data 00 Data 9100
Cmd.ChangeFileSetting 90 5F 00 00 XX Data 00 Data 9100
P1-P3P4-P6P7-P9P10-P12P13-P15P16-P16

NT4H1321G0DUD/062V

Mfr. #:
Buy NT4H1321G0DUD/062V
Manufacturer:
NXP Semiconductors
Description:
RFID Transponders CLHW
Lifecycle:
New from this manufacturer.
Delivery:
DHL FedEx Ups TNT EMS
Payment:
T/T Paypal Visa MoneyGram Western Union

Products related to this Datasheet