User's Manual
Table Of Contents
- 1. Introduction
- The PN7150 architecture overview
- 2. NCI Overview
- 3. DH interface
- 5. Initialization & Operation configuration
- 6. Reader/Writer Mode
- 6.1 T1T, T2T, MIFARE Ultralight, MIFARE Classic and MIFARE Plus tags
- 6.1.1 Access through the [NCI] Frame RF Interface
- 6.1.2 [PN7150-NCI] extension: TAG-CMD Interface
- 6.1.3 [PN7150-NCI] extension: Payload structure of the TAG-CMD RF Interface
- 6.1.4 [PN7150-NCI] extension: REQs & RSPs rules
- 6.1.5 [PN7150-NCI] extension: List of REQs & RSPs
- 6.1.6 [PN7150-NCI] extension: raw data exchange REQs & RSPs
- 6.1.7 [PN7150-NCI] extension: T2T & MFU REQs & RSPs
- 6.1.8 [PN7150-NCI] extension: MIFARE Classic REQs & RSPs
- 6.1.9 Access through the TAG-CMD RF Interface
- 6.2 T3T tag
- 6.3 T4T & ISO-DEP Tags/Cards
- 6.3.1 Access through the Frame RF Interface
- 6.3.2 Access through the ISO-DEP RF Interface
- 6.3.3 [PN7150-NCI] extension: Presence check Command/Response
- 6.3.4 [PN7150-NCI] extension: S-Block Command/Response
- 6.3.5 [PN7150-NCI] extension: WTX notification
- 6.3.6 [PN7150-NCI] extension: Higher bit rates in Poll NFC-A & NFC-B
- 6.4 [PN7150-NCI] extension: 15693 & I-Code tags
- 6.5 [PN7150-NCI] extension: KOVIO tags
- 6.1 T1T, T2T, MIFARE Ultralight, MIFARE Classic and MIFARE Plus tags
- 7. Card Emulation Mode
- 8. P2P Initiator & Target Mode
- 9. RF Discovery Management
- 9.1 RF Discovery functionalities
- 9.2 NFC FORUM Profile as defined in [NCI]
- 9.3 [PN7150-NCI] extension: additional technologies not yet supported by the NFC FORUM
- 9.4 [PN7150-NCI] extension: Low Power Card Detector (LPCD) Mode
- 9.5 [PN7150-NCI] extension: EMVCo Profile in Poll & Listen Modes
- 9.6 [PN7150-NCI] extension: Power optimization
- 10. Configurations
- 11. Test Mode
- 12. PN7150 Practical approach
U
M10936
P
N7150 User Manual
UM
10936 All information provided in this document is subject to legal disclaimers.
U
ser manual
CO
MPANY PUBLIC
Rev. 2.0 — 6 November 2020
348120
14 of 127
2.
2.5 NFCEE Communication
T
he DH can learn about the NFCEEs connected to the NFCC by using the NFCEE
Discovery module. During NFCEE Discovery the NFCC assigns an identifier for each
NFCEE. When the DH wants to communicate with an NFCEE, it needs to open a Logical
Connection to the NFCEE using the corresponding identifier and specifying the NFCEE
Protocol to be used.
Opening a Logical Connection to an NFCEE automatically activates the NFCEE Interface
associated to the protocol specified. As there is always a one-to-one relationship between
an NFCEE Protocol and Interface, there is no mapping step required (different as for the
RF Communication).
After the Interface has been activated, the DH can communicate with the NFCEE using
the activated Interface.
Closing the connection to an NFCEE Interface deactivates that NFCEE Interface.
NCI also includes functionality to allow the DH to enable or disable the communication
between an NFCEE and the NFCC.
2.2.6 Identifiers
T
he NFCC might only be used by the DH but also by the NFCEEs in the device (in such a
case the NFCC is a shared resource). NFCEEs differ in the way they are connected to the
NFCC and the protocol used on such a link determines how an NFCEE can use the NFCC.
For example, some protocols allow the NFCEE to provide its own configuration for RF
parameters to the NFCC (similar to the NCI Configuration Parameters for RF Discovery)
in other cases the NFCEE might not provide such information.
NFCCs can have different implementation in how they deal with multiple configurations
from DH and NFCEEs. They might for example switch between those configurations so
that only one is active at a time or they might attempt to merge the different configurations.
During initialization NCI provides information for the DH whether the configuration it
provides is the only one or if the NFCC supports configuration by NFCEEs as well.
NCI includes a module, called Listen Mode Routing, with which the DH can define where
to route received data when the device has been activated in Listen Mode. The Listen
Mode Routing allows the DH to maintain a routing table on the NFCC. Routing can be done
based on the technology or protocol of the incoming traffic or based on application
identifiers in case [7816-4] APDU commands are used on top of ISO-DEP.
In case of PN7150 the only route is the DH-NFCEE, therefore no Listen Mode Routing
programming supported.
In addition, NCI enables the DH to get informed if communication between an NFCEE and
a Remote NFC Endpoint occurs.