Home

NFC Controller Interface Specification

1. SPI_INT SPI CLK IDLE I ACTIVE IDLE SPIMOSI me fase ae PEN ene mu SPL MISO TRISTATE l Oorl TRISTATE Figure 26 SPI Data Transfer from the DH to the NFCC with CRC If the slave does not assert SPI_INT in a timely fashion the master is allowed to deassert SPI_CSN and use the SPI bus to talk to a different peripheral This can happen if the slave is busy processing its FIFOs 11 3 2 2 Data Transfer from NFCC to DH The DirectRead command is used to transfer data from slave to the master Data can be transferred from the slave to the master in the following fashion e Slave asserts SPLINT e Master asserts SPI CSN e Master send 2 octet SPI header e Slave sends 2 octet SPI payload length e Slave sends SPI payload e Master deasserts SPI CSN Slave may deasserts SPI_INT at any time after step 2 Slave SHALL deasserts SPI_INT before step 6 SPI_CSN may be toggled deasserted and asserted in every 8 bit transfer If the Second Octet is equal to 0x00 the DirectRead header is sent as shown in the table below Table 92 SPI Header Coding NFCC to DH without CRC First Octet Second Octet Third Octet Fourth Octet Master 0x02 0x00 0x00 0x00 Slave 0x00 0x00 MSB Payload LSB Payload Length Length The payload length is defined in the same manner as above Figure 27 bellow illustrates the procedure to transfer data from NFCC to the DH NFC Controller Interface NCI Specification P
2. A Logical Connection is set up through negotiation between the NFCC and the DH as described in Section 4 4 The following is an overview of the Logical Connection concept Dynamic Logical Connection e The DH MAY create a Dynamic Logical Connection e The NFCC MAY reject an incoming connection request e An identifier Conn ID will be assigned by the NFCC to identify the Dynamic Logical Connection and this remains valid for the life of the Dynamic Logical Connection The Conn ID is released when the Dynamic Logical Connection is closed e The DH can close a Dynamic Logical Connection e Data can be transported only after the Dynamic Logical Connection has been successfully created e Both the DH and the NFCC SHALL ignore Data Packets with unassigned Conn IDs Static RF Connection e The Static RF Connection exists after NFCC Initialization without needing to be created using the connection Control Messages defined in Section 4 4 2 and is never closed e The Initial Number of Credits and Max Data Packet Payload Size of the Static RF Connection are re established by the NFCC each time it sends RF_INTF_ACTIVATED_NTF e The DH SHALL NOT send data over the Static RF Connection if there is no active RF Interface See Section 7 3 e If there is no active RF Interface both the DH and the NFCC SHALL ignore Data Packets with the Conn ID of the Static RF Connection NOTE All RF Interfaces included in this version of the specification use
3. e RF_DEACTIVATE_CMD RSP NTF Sleep_AF Mode Before sending the RF_DEACTIVATE_NTF to the DH the NFCC SHALL deselect the Remote NFC Endpoint by sending an NFC DEP Deselect Request DSL_REQ to the Remote NFC Endpoint as specified in DIGITAL When using this RF Interface the following deactivation cases described in Section 5 2 for RFST_LISTEN_ACTIVE SHALL NOT be allowed e RF_DEACTIVATE_CMD RSP NTF Sleep Mode 8 4 3 4 Failures during Data Exchange If an NFC DEP Timeout Error PROTOCOL EXCEPTION as defined in DIGITAL occurs the NFCC SHALL send the CORE INTERFACE ERROR NTF with the Status of RF TIMEOUT ERROR If an NFC DEP Transmission Error PROTOCOL EXCEPTION as defined in DIGITAL occurs the NFCC SHALL send the CORE INTERFACE ERROR NTF with the Status of RF_TRANSMISSION_ERROR If an NFC DEP Protocol Error PROTOCOL EXCEPTION as defined in DIGITAL occurs the NFCC SHALL send the CORE INTERFACE ERROR NTF with the Status of RF_PROTOCOL_ERROR 8 44 Listen side NFC DEP RF Interface Management The Listen side NFC DEP RF Interface MAY be used when the device operates as a NFC DEP Target in Peer Mode and the Remote NFC Endpoint supports NFC DEP based on NFC A or NFC F 8 4 4 1 Discovery Configuration The Discovery configuration parameters defined in the following tables are relevant depending on the NFC technology used in Discovery NFC A or NFC F as set by RF Technology and Mode in RF_DISCOVER_CMD They MAY be changed from defa
4. Figure 11 Format for Frame RF Interface NFC A for Transmission For NFC A Data Message SHALL NOT contain the parity bits used by Standard Frame When sending the RF Frames the NFCC SHALL insert the parity bits according to DIGITAL For NFC B Data Message SHALL NOT contain the start and stop bits used by the frame format When sending the RF Frames the NFCC SHALL insert the start and stop bits according to DIGITAL For Type 1 Tag Platform and when in Poll Mode the first octet of the Data Message SHALL consist of Ob as the most significant bit followed by the 7 bit Command Code The RF Frame format is defined in Section 8 4 of DIGITAL where EoD consists of CRC B1 and CRC_B2 NFC Controller Interface NCI Specification Page 93 RF Interfaces Data Packet Data Packet Header Payload Byte 1 Byte 2 Byte n CRC_B1 CRC_B2 RF Frame Payload EoD Data Figure 12 Format for Frame RF Interface NFC B for Transmission Data Packet Data Packet Header SoD Payload Su Byte 1 Byte 2 Byte n CRC_F1 CRC F2 rame Payload EoD Data Figure 13 Format for Frame RF Interface NFC F for Transmission 8 2 1 2 Data from RF to the DH For NFC A and NFC B the Data Message SHALL correspond to the Payload of the Data and Payload Format defined in DIGITAL Section 4 4 for NFC A and 5 4 for NFC B followed by a Status field of 1 octet For NFC F the Data Message SHALL correspond to the SoD and Payload of the Data and Payl
5. NOTE In case of a DEP RES frame the first Byte would be OxD5 and the second Byte 0x07 Data Packet Data Packet Header Payload pf e r A U e eo e a s U g K n d D eed 0x06 PFB DIDI NAD Transport Data Bytes Y N S 0x06 PFB DID NAD Transport Data Bytes Figure 19 Format for NFC DEP RF Interface for Transmission 8 4 12 Data from RF to the DH The NFCC SHALL transfer the Information PDU received within the Transport Data Bytes of one or a chained series of DEP_RES responses if the NFCC is an NFC DEP Initiator or DEP_REQ commands if the NFCC is an NFC DEP Target to the DH The last byte of the Transport Data Bytes of a DEP_RES or DEP_REQ frame not indicating chaining received by the NFCC from the Remote NFC Endpoint SHALL be the last octet of the Data Packet with the Packet Boundary Flag set to Ob Figure 20 illustrates the mapping between the Data Message format and the NFC DEP DEP_RES frame NOTE This figure shows the case where NCI Segmentation and Reassembly feature is not used However NFC DEP chaining is used where one Data Message is received by multiple DEP_RES frames from the Remote NFC Endpoint NOTE In case of a DEP_REQ frame the first Byte would be 0xD4 and the second Byte 0x06 NFC Controller Interface NCI Specification Page 109 RF Interfaces 0x07 PFB DID NAD Transport Data Bytes 7 d MEDE oxD5 0x07 DONA Transpor Data Bytes z frame A r
6. If Configuration Status is set to 0x01 in either CORE_RESET_RSP or CORE_RESET_NTF the NCI RF Configuration SHALL have been reset which includes e Removing all entries of the Listen Mode Routing Table e Reverting all Configuration Parameter to their default values NFC Controller Interface NCI Specification Page 35 NCI Core Control Messages e Erasing the RF Interface Mapping configuration If Configuration Status is set to 0x00 the NCI RF Configuration SHALL be the same as before the reset In this case the NFCC internal mapping of NFCEEs to NFCEE IDs SHALL also be unchanged as otherwise the Listen Mode Routing Table would be corrupted The NFCC MAY also reset itself without having received a CORE RESET CMD e g in the case of an internal error In these cases the NFCC SHALL inform the DH with the CORE_RESET_NTF The Reason code SHALL reflect the internal reset reason and the Configuration Status the status of the NCI RF Configuration 4 2 Initialization of NFCC These Control Messages are used to initialize the NFCC Table 8 Control Messages to Initialize the NFCC CORE_INIT_CMD Payload Field s Length Value Description Empty payload CORE INIT RSP Payload Field s Length Value Description Status 1 Octet See Table 94 NEFCC Features 4 Octets See Table 9 Number of Supported 1 Octet Number of Supported RF Interface fields to follow n RF Interfaces Supp
7. If an NFC DEP Protocol Error PROTOCOL EXCEPTION DIGITAL occurs the NFCC SHALL send the CORE_INTERFACE_ERROR_NTF with the Status of RF_PROTOCOL_ERROR When the DH receives the CORE_INTERFACE_ERROR_NTF the DH MAY initiate NFC DEP RF Interface deactivation or perform some other error handling procedure NFC Controller Interface NCI Specification Page 114 NFCEE Discovery and Mode Set 9 NFCEE Discovery and Mode Set 9 1 NFCEE ID The NFCC dynamically assigns IDs for NFCEES called NFCEE IDs The DH gets to know the ID values by performing NFCEE Discovery NFCEE IDs are valid until an NFCEE is removed from the NFCC An ID with a value of zero is referred to in this specification as a DH NFCEE ID and SHALL represent the DH NFCEE Table 84 NFCEE IDs Value Description 0 DH NFCEE ID a static ID representing the DH NFCEE 1 254 Dynamically assigned by the NFCC 255 RFU 9 2 NFCEE Discovery These Control Messages are used to discover whether one or more NFCEEs are connected to the NFCC Table 85 Control Messages for NFCEE Discovery NFCEE DISCOVER CMD Payload Field s Length Value Description Discovery Action 1 Octet 0x00 Disable discovery of NFCEE 0x01 Enable discovery of NFCEE 0x02 RFU OxFF NFCEE_DISCOVER_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 Number of NFCEEs 1 Octet 0 255 Indicates the nu
8. rorum NFC Controller Interface NCI Specification Technical Specification NFC Forum NCI 1 0 NFCForum TS NCI 1 0 2012 11 06 Contents RESTRICTIONS ON USE This specification is copyright 2011 2012 by the NFC Forum and was made available pursuant to a license agreement entered into between the recipient Licensee and NFC Forum Inc Licensor and may be used only by Licensee and in compliance with the terms of that license agreement License If you are not the Licensee you may read this Specification but are not authorized to implement or make any other use of this specification However you may obtain a copy of this Specification and implementation rights at the following page of Licensor s website http www nfc forum org specs spec_license after entering into and agreeing to such license terms as Licensor is then requiring On the date that this specification was downloaded by Licensee the non implementation terms of that license were as follows 1 LICENSE GRANT Licensor hereby grants Licensee the right without charge to copy for internal purposes only except with respect to the elements listed on Exhibit A and share this Specification with Licensee s members employees and to the extent related to Licensees use of this Specification consultants This license grant does not include the right to sublicense modify or create derivative works based upon any portion of the Specification except for the element
9. 2 Octets Description 0x0000 OxFFFF defines the Total Duration of the single discovery period in ms This time definition provides only a rough target value for the NFCC but NFCC may adjust the duration time due to the current limitation of active RF Protocols and hardware limitations Default NFCC decides CON_DEVICES_LIMIT 1 Octet As defined in ACTIVITY for the Collision Resolution Activity Default NFCC decides based on its capabilities NFC Controller Interface NCI Specification Page 68 RF Communication Configuration 6 2 RF Interface Mapping Configuration These Control Messages are used to configure the mapping between RF Protocols and RF Interfaces Table 42 Control Messages for RF Interface Mapping Configuration RF_DISCOVER_MAP_CMD Payload Field s Length Value Description Number of Mapping 1 Octet The number of Mapping Configuration fields to follow n Configurations Mapping 3 Octets RF Protocol 1 Octet See Table 98 SE Wien Mode 1 Octet See Table 43 RF Interface 1 Octet See Table 99 The value 0 NFCEE Direct RF Interface SHALL NOT be used RF_DISCOVER_MAP_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 Table 43 Value Field for Mode Bit Mask Description b7 b6 b5 b4 b3 b2 b1 b0 Octet0 0 0 0 0 IO 0 RFU X If set to 1b the RF Interface is mapped to the RF Pr
10. HCI Host Controller Interface HCP Host Controller Protocol ISO International Organization for Standardization MT Message Type NCI NFC Controller Interface NDEF NFC Data Exchange Format NFC Near Field Communication NFCC NFC Controller NFCEE NFC Execution Environment OID Opcode Identifier PBF Packet Boundary Flag RF Radio Frequency RFU Reserved for Future Use SAR Segmentation and Reassembly SDU Service Data Unit NFC Controller Interface NCI Specification Page 13 Introduction 1 10 Glossary Application ID AID Defined in ISO IEC 7816 4 this is a specific type of Dedicated File DF name which is used in a SELECT command to identify applications Battery Off State State where an internal battery or external power source is not available For example the battery is removed or empty so the Device Host DH is switched off The NFC Forum Device can only act in Listen Mode when the NFC Controller NFCC and certain NFC Execution Environments NFCEEs may be powered by a Remote NFC Device via magnetic coupling Command Message A request sent from the Device Host DH to the NFC Controller NFCC for action by the NFCC Connection Identifier Conn ID A unique 4 bit identifier for a Logical Connection Control Message A generic name when referring to a Command Response or Notification Message but not a Data Message NOTE The terms Command Response and Notification as used in th
11. If the NFCC supports the HCI Network it SHALL return one and only one NFCEE_DISCOVER_NTF with a Protocol type of HCI Access even if the HCI Network contains multiple NFCEEs NFC Controller Interface NCI Specification Page 118 NFCEE Discovery and Mode Set The NFCEE ID returned by the NFCC in the NFCEE_DISCOVER_NTF is used by the DH to address the HCI Network The following rules apply to the NFCEE_DISCOVER_NTF for an HCI Network e If NFCEE Status field has a value of 0x00 NFCEE connected and enabled the HCI Network is allowed to perform RF communication under the conditions given by the RF State Machine e Ifthe NFCEE Status field has a value of 0x01 NFCEE connected and disabled RF communication is not allowed This is typically due to a previous NFCEE MODE SET CMD sent to deactivate the HCI Network No Hardware Registration Identification SHALL be provided within NFCEE_DISCOVERY_NTF The Length of Hardware Registration Identification SHALL be set to 0 The Hardware Registration Identification information of the different hosts within the HCI Network can be received by HCP packets according ETSI_102622 e An NFCEE DISCOVER NTF that contains a Protocol type of HCI Access SHALL NOT contain any other additional Protocol 9 3 NFCEE Enabling and Disabling These Control Messages are used to enable or disable an NFCEE Table 88 Control Messages to Enable and Disable a Connected NFCEE NFCEE_M
12. OID values are defined along with the definition of the respective Control Messages described in Table 102 Payload Length L The Payload Length SHALL indicate the number of octets present in the payload The Payload Length field SHALL be an 8 bit field containing a value from 0 to 255 NFC Controller Interface NCI Specification Page 29 NCI Core Framework 3 4 3 Format of Data Packets The Data Packet structure is detailed in Figure 8 Packet Header 3 1 4 8 8 L bytes P MT Conn ID RFU Payload Length L Payload Octet 0 Octet 1 Octet 2 Octet 3 Octet 2 L Figure 8 Data Packet Structure Each Data Packet SHALL have a 3 octet Packet Header and MAY have additional Payload for carrying a Data Message or a segment of a Data Message NOTE In the case of an empty Data Message only the Packet Header is sent Message Type MT Refer to Table 2 for details of the MT field NOTE MT always contains 000b to indicate a Data Packet as defined in Table 2 Packet Boundary Flag PBF Refer to Table 3 for details of the PBF field Connection Identifier Conn ID The Connection Identifier Conn ID SHALL be used to indicate the previously setup Logical Connection to which this data belongs Refer to Section 4 4 for details on setting up a Logical Connection and the assignment of the Conn ID The Conn ID is a 4 bit field containing a value from 0 to 15 Payload Length L The Payload Length
13. The following Protocols can be mapped to this Interface see Section 6 2 PROTOCOL_ISO_DEP 8 3 1 Data Mapping between the DH and RF The DH and the NFCC SHALL only use the Static RF Connection for data communication with a Remote NFC Endpoint NCI Segmentation and Reassembly MAY be applied to Data Messages in either direction 8 3 1 1 Data from the DH to RF When receiving a Data Message from the DH the NFCC SHALL send the data contained in the Data Message as a Payload of an I Block or as multiple Payloads of a chained series of I Blocks to the Remote NFC Endpoint using the activated technology The last octet of the Data Packet with the Packet Boundary Flag set to Ob SHALL be the last byte of the Payload of an I Block not indicating chaining sent by the NFCC to the Remote NFC Endpoint Figure 17 illustrates the mapping between the Data Packet and the RF Frame when sending the frame to the Remote NFC Endpoint NFC Controller Interface NCI Specification Page 103 RF Interfaces NOTE This figure shows the case where NCI Segmentation and Reassembly feature is not used However ISO DEP chaining is used where one Data Message is sent with multiple I Blocks to the Remote NFC Endpoint Data Packet Data Packet Header Payload Pid PCB DID INF CRC_1 CRC 2 Payload Block TEE soD Paoa E0 dosoossos ISO DEP Block Block Figure 17 Format for ISO DEP RF Interface for Transmission 8 3 1 2 Data
14. a a o n Data Packet Data Packet Header Payload Figure 20 Format for NFC DEP RF Interface for Reception 8 4 2 NFC DEP RF Interface Configuration The behavior of the NFC DEP protocol MAY be configured using CORE SET CONFIG CMD indicating the following parameter Table 80 Specific Parameters for NFC DEP RF Interface ID Length Description NECDEP OP 1 Octet See Table 81 Default OxOF Table 81 NFC DEP Operation Parameter Bit Mask Description b7 b6 b5 b4 b3 b2 b1 b0 OctetO jO O 0 JO RFU X If set to 1b all PDUs indicating chaining MI bit set SHALL use the maximum number of Transport Data Bytes X If set to b1 Information PDU with no Transport Data Bytes SHALL NOT be sent X If set to 1b the NFC DEP Initiator SHALL use the ATTENTION command only as part of the error recovery procedure as described in DIGITAL X If set to 1b the NFC DEP Target SHALL NOT send RTOX requests This parameter SHALL only be configured when the NFCC is in RFST_IDLE state NFC Controller Interface NCI Specification Page 110 RF Interfaces Some settings are only relevant for NFC DEP Target or NFC DEP Initiator respectively The settings not matching the current role of the device SHALL be ignored NOTE These settings allow configuring the NFC DEP protocol to comply with the requirements stated in the NFC Forum Logical Link Contr
15. if the CORE SET CONFIG CMD contains either e the parameter LF T3T MAX e a parameter of type LF_T3T_IDENTIFIERS with a higher index than the value of LE TAT MAX NFC Controller Interface NCI Specification Page 65 RF Communication Configuration e aLF_T3T_IDENTIFIERS parameter with values for Octets 0 and 1 which are equal to Octet 0 and 1 of another LF_T3T_IDENTIFIERS parameters value The NFCC SHALL answer by sending CORE_GET_CONFIG_RSP with a Status of STATUS_REJECTED if the CORE GET CONFIG CMD contains e a parameter of type LF_T3T_IDENTIFIERS with a higher index than the value provided by LE TAT MAX NOTE If the value of LF T3T MAX is set to 0 the NFCC does not support generating SENSF responses for the Type 3 Tag Platform 6 1 9 Listen ISO DEP Parameters These parameters MAY be configured if listening for NFC A or NFC B Table 38 Discovery Configuration Parameters for Listen ISO DEP ID Length Description LI FWI 1 Octet Frame Waiting time Integer as defined in DIGITAL Default 4 LA_HIST_BY O n Historical Bytes only applicable for Type Octets 4A Tag as defined in DIGITAL Default empty do not send historical bytes LB_H_INFO_RESP O n Higher Layer Response field of the Octets ATTRIB response as defined in DIGITAL Default empty send ATTRIB response without Higher Layer Response field LI BIT RATE 1 Octet Maximum supported bit rate Default 0x00 106 Kbit s For valu
16. so communication from a DH to an NFCEE will only be possible if it is also supported by the protocols used between the NFCC and the NFCEE An addressing scheme for Remote NFC Endpoints The NCI Core uses Logical Connections to support communication between the DH and targets NFCEEs or Remote NFC Endpoints which are discovered by the NFCC Reset initialization and configuration of the NFCC Exception handling including Control Messages for indicating errors and rules for how to use them NFC Controller Interface NCI Specification Page 23 NCI Core Framework 3 2 NCI Control Messages Control Messages contain Commands Responses and Notifications They control the interaction between the DH and the NFCC See Figure 4 Command Response Notification Control Message Exchange Figure 4 Control Message Exchange A Command can be sent by the DH to instruct the NFCC to perform a specific action For each Command received the NFCC SHALL answer with a Response to acknowledge the receipt of the Command The Response MAY also indicate changes that the Command caused at the NFCC Notifications SHALL only be sent from the NFCC to the DH A Notification can be sent to deliver additional information related to a Command A Notification can also be sent independently of any Command or Response unless specified otherwise Control Messages are sent over the NCI as payload of Control Packets A Control Packet payload
17. the NFCC SHALL send RF_DISCOVER_NTF to the DH for each combination of Remote NFC Endpoint and RF Protocol detected during the RF Discovery Process e The NFCC SHALL assign a unique RF Discovery ID to each detected Remote NFC Endpoint The combination of RF Discovery ID and RF Protocol SHALL be unique across all RF_DISCOVER_NTFs sent within a series of RF Discovery Notifications The NFCC SHALL assign the same RF Discovery ID in all notifications send for a single Remote NFC Endpoint supporting multiple protocols NOTE If a Remote NFC Endpoint supports multiple protocols the NFCC uses the same RF Discovery ID for each Notification but different RF Protocol values If a Remote NFC Endpoint uses separate polling responses to indicate support of multiple protocols the NFCC can not know that the responses came from a single Remote NFC Endpoint In that case the NFCC assigns different RF Discovery ID e All assigned RF Discovery IDs are released when the RF State machine defined in Section 5 2 moves into state RFST_IDLE e The Notification Type field SHALL be set to 0 or 1 if the current RF_DISCOVER_NTF is the last notification being sent or set to 2 if there is another RF_DISCOVER_NTF to follow called series of RF Discovery Notifications NOTE Since RF_DISCOVER_NTF is only sent when there are multiple Remote NFC Endpoints in the field or if a Remote NFC Endpoint supports multiple RF Protocols the first notification sent after starting the RF
18. the NFCC may issue RF commands to deactivate the Remote NFC Endpoint before sending RF_DEACTIVATE_NTF When using the ISO DEP or NFC DEP RF interface and the NFCC detects an error during the RF communication it SHALL notify the DH sending CORE_INTERFACE_ERROR_NTF using the appropriate status out of RF_TRANSMISSION_ERROR RF_PROTOCOL_ERROR and RF_TIMEOUT_ERROR see Table 94 The state will then remain RFST_POLL_ACTIVE NFC Controller Interface NCI Specification Page 52 RF Communication 5 2 6 State RFST_LISTEN ACTIVE In this state the NFCC is activated in Listen Mode In this state an RF Interface is activated which allows the NFCC to communicate with a Remote NFC Endpoint as specified by the active RF Interface The NFCC SHALL accept and send Data Messages to or from the DH or NFCEE based on the routing tables NOTE By configuring the NFCC to send RF_NFCEE_ACTION_NTF notifications the DH will get informed if a decision is made by the NFCC based on the routing algorithm to route to a different NFCEE see 7 4 The local routing destination can change when using AID based routing see 6 3 1 if the Remote NFC Endpoint selects an AID where the corresponding application is hosted on a different NFCEE than the one previously selected Routing can also change if the NFC Forum Device appears to the Remote NFC Endpoint as not one but multiple endpoints and the Remote NFC Endpoint switches communication between these endpoints In this state
19. 48 Table 49 Table 50 Table 51 Table 52 Table 53 Table 54 Table 55 Table 56 Table 57 Table 58 Table 59 Table 60 Table 61 Table 62 Table 63 Table 64 Table 65 Table 66 Table 67 Table 68 Tables LB ADC FO valie Sinh EG GE Ge Bis E ca ONG iia ENE ieee 63 Discovery Configuration Parameters for Listen F oo eee ese ese ese ee ee ee ee Ge Ge 64 Supported Protocols for Listen F cece see se se se ee ee ee Ge Ge Ge GRA GRA Gee de 65 LF CON BITRE ValtieS EE OE RE AE OE EE EN 65 Discovery Configuration Parameters for Listen ISO DEP oo esse esse esse esse ee se ee se de ee 66 Discovery Configuration Parameters for Listen NFC DEP esse esse ee se ee se se ee ee see ee 67 Values for LN ATR RES CONBPIG esse see see se ese ee es ee ee ee Ge Ge Ge RA ee 67 Common Parameters for Discovery ConfiguratjOn esse esse esse esse es se ee Ge Ge Ge ee ee de 68 Control Messages for RF Interface Mapping Configuration eee sees see ses ee ee ee 69 Value Field fot SR SA OE RR AR IE EE E 69 Control Messages to Configure Listen Mode Routing esse esse es see se se Ge GR Ge 72 More field lS ER OR EE N OE RE ER eee 72 TLV Coding for Listen Mode Routing esse ese se se ee es ee ee ee Ge Ge Ge RA ee ee ee 72 Value Field for Technology based Routing eee esse esse es ee ee ee Ge Ge Ge GR RA ee ee 73 Value Field for Protocol based Routing esse sesse ese ee ee ee ee Ge Ge GR RA GR ek
20. 97 Bit Rates Bit Rate value Definition 0x00 NFC_BIT_RATE_106 106 Kbit s 0x01 NFC_BIT_RATE_212 212 Kbit s 0x02 NFC_BIT_RATE_424 424 Kbit s 0x03 NFC_BIT_RATE_848 848 Kbit s 0x04 NFC_BIT_RATE_1695 1695 Kbit s 0x05 NFC_BIT_RATE_3390 3390 Kbit s 0x06 NFC_BIT_RATE_6780 6780 Kbit s 0x07 0x7F RFU 0x80 0xFE For proprietary use OxFF RFU Common Tables Active communication mode and ISO IEC 15693 is currently not supported by the The allowed values for each technology SHALL be as defined in DIGITAL and ACTIVITY Table 98 RF Protocols RF Protocol value Definition 0x00 PROTOCOL_UNDETERMINED 0x01 PROTOCOL_T1T 0x02 PROTOCOL_T2T 0x03 PROTOCOL_T3T 0x04 PROTOCOL_ISO_DEP 0x05 PROTOCOL_NFC_DEP 0x06 0x7F RFU 0x80 0xFE For proprietary use OxFF RFU NOTE Type 4 Tag Platform is based on the ISO DEP Protocol NFC Controller Interface NCI Specification Page 138 Table 99 RF Interfaces RF Interface value Definition 0x00 NFCEE Direct RF Interface 0x01 Frame RF Interface 0x02 ISO DEP RF Interface 0x03 NFC DEP RF Interface 0x04 0x7F RFU 0x80 0xFE For proprietary use OxFF RFU Table 100 NFCEE Protocols Interfaces NFCEE Interface Definition Protocol value 0x00 APDU 0x01 HCI Access 0x02 Type 3 Tag Command Set 0x03 Transparent 0x04 0x7F RFU 0x80 0xFE For propri
21. Coding for RF NFCEE Discovery Reguest esse esse esse esse ee se ee se ee se ee ee de ee ee ee de 89 Value Field for NFCEE Discovery Request InformaHON eesees sesse esse ee se ee se se ee ee ee 89 Notification to Report an NFCEE Action esse see ese esse es se es se es se ee se ee Ge ee Ge Ge ee ee ee 89 NFC Controller Interface NCI Specification Page vii Tables Table 69 Trigger in NFCEE Action NotificaHON esse esse esse ese ese es se es se ee se ee ee Ge Ge GRA ee Ge de 90 Table 70 RF NFCEE ACTION configuration parameter sesse esse esse esse ee se ee se ee se de ee de ede eke dee 91 Table 71 Control Messages for RF Parameter Update ees esse esse ee ee ee Ge Ge Ge Ge ee 96 Table 72 TLV Coding for RF Communication Parameter ID esse esse esse ee se ee se Ge RA Ge ee 97 Table 73 NFC B Data Exchange Configuration Parameter esse esse esse esse ee se ee se ee Ge de Ge ee Ge ee 98 Table 74 Control Messages to Request the NFCC to send a Type 3 Tag Polling Command 99 Table 75 Pre activation states and the split of commands between NFCC amp DH ee 102 Table 76 Activation Parameters for NFC A ISO DEP Poll Mode cece esse esse esse esse ee se ee se ee 105 Table 77 Activation Parameters for NFC B ISO DEP Poll Mode esse esse es se esse ee se ee se ee 106 Table 78 Activation Parameters for NFC A ISO DEP Listen Mode sesse esse esse esse ee se ee se ee 107 Table 79 Activation Parameters for N
22. DH The state will then change to RFST DISCOVERY If the DH sends RF_DEACTIVATE_CMD Idle Mode the NFCC SHALL send RF_DEACTIVATE_RSP The state will then change to RFST_IDLE 5 3 RF Field Information This Notification is used to inform the DH about operating fields generated by Remote NFC Endpoints Table 20 Notification for RF Field information RF_FIELD_INFO_NTF Payload Field s Length Value Description RF Field Status 1 Octet See Table 21 Table 21 RF Field Status Bit Mask Description b7 b6 b5 b4 b3 b2 b1 bO Octet 0 O 0 JO JO JO JO JO RFU X 1b Operating field generated by Remote NFC Endpoint 0b No Operating field generated by Remote NFC Endpoint The DH can configure whether the NFCC is allowed to send RF Field Information Notifications by setting the following configuration parameter NFC Controller Interface NCI Specification Page 54 RF Communication Table 22 RF Field Information Configuration Parameter ID Length Value Description RF FIELD INFO 1 Octet 0x00 The NFCC is not allowed to send RF Field default Information Notifications to the DH 0x01 The NFCC is allowed to send RF Field Information Notifications to the DH 0x02 0xFF RFU If RF_FIELD_INFO is set to 0x01 the following rules apply The NFCC SHALL send RF_FIELD_INFO_NTF immediately if the RF_FIELD_INFO is set to 0x01 T
23. Description SENSF_REQ PARAMS 4 Octets Byte 2 5 of SENSF as defined in Section 6 6 1 of DIGITAL RF_T3T_POLLING_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 RF_T3T_POLLING_NTF Payload Field s Length Value Description Status 1 Octet See Table 94 Number of Responses 1 Octet The number of Response fields to follow n Response 1 n m 1 Length 1 Octet Length of following Octets SENSF_RES field m Allowed values SHALL be 0x10 or 0x12 Other values are RFU SENSF_RES m Byte 2 17 19 of SENSF_RES Octets Response as defined in DIGITAL The DH is allowed to use this Command only e ifin RFST_POLL_ACTIVE state and e if the activated RF Interface is the Poll side Frame RF Interface for PROTOCOL_T3T After receiving a RF_T3T_POLLING_CMD and if above conditions are met the NFCC SHALL answer with a RF_T3T_POLLING_RSP with a Status value of STATUS_OK and send a SENSF_REQ Command with Bytes 2 5 set as specified in the Command parameter to the RF field When the NFCC receives SENSF_RES response s from the Remote NFC Endpoint s the NFCC SHALL populate the corresponding parameters of a RF_T3T_POLLING_NTF and send it with Status set to STATUS_OK to the DH If no response is received the NFCC SHALL send a RF_T3T_POLLING_NTF with Status set to STATUS_FAILED and containing no other Payload Fields If above conditions are not met the NFCC SHA
24. Endpoint When an ATR RES is received from the Remote NEC Endpoint the NFCC SHALL forward the ATR RES to the DH within the Activation Parameters of the RF_INTF_ACTIVATED_NTF Based on the current bit rate and the configured PN NFC DEP SPEED value the NFCC determines whether to send a PSL_REQ before sending the RF_INTF_ACTIVATED_NTF If PSL_REQ is sent the values in the three Data Exchange parameters of the RF_INTF_ACTIVATED_NTF SHALL reflect the technology and bit rates set with the PSL_REQ otherwise they SHALL indicate the technology and bit rates used during the protocol activation The RF_INTF_ACTIVATED_NTF SHALL include the Activation Parameters defined in Table 82 NFC Controller Interface NCI Specification Page 111 RF Interfaces Table 82 Activation Parameters for NFC DEP Poll Mode Parameter Length Description ATR RES Response Length 1 Octet Length of ATR RES Command Parameter n ATR RES Response n Octets All Bytes of ATR RES Response starting from and including Byte 3 as defined in DIGITAL 8 4 3 3 Interface Deactivation Additional rules apply for the following deactivation cases described in Section 5 2 for RFST_POLL_ACTIVE e RF_DEACTIVATE_CMD RSP NTF dle Mode RF_DEACTIVATE_CMD RSP NTF Discovery Before sending the RF_DEACTIVATE_NTF to the DH the NFCC SHALL release the Remote NFC Endpoint by sending an NFC DEP Release Request RLS_REQ to the Remote NFC Endpoint as specified in DIGITAL
25. Endpoint via an active RF Interface Switched On State In this state the DH the NFCC and all connected NFCEEs are switched on and powered either by internal battery or external power source The NFC Forum device can act in both Poll and Listen Modes NCI is only applicable in Switched On state Switched Off State In this state the DH is switched off and the NFCC and all connected NFCEEs are powered either by internal battery or external power source The NFC Forum Device can only act in Listen Mode UICC A Smart Card that conforms to the specifications written and maintained by the TC ETSI Smart Card Platform It is a platform to resident applications e g USIM CSIM ISIM banking transport etc NFC Controller Interface NCI Specification Page 17 Introduction 1 11 Coding Conventions The following coding conventions apply in this document if not stated otherwise e Each octet is represented by bits bO to b7 where b7 is the most significant bit msb and bO the least significant bit sb In all representations the leftmost bit is the msb e All values greater than 1 octet are sent and received in Little Endian format e In representations of octet arrays each octet is numbered starting at 0 Octet numbered 0 is sent over the NCI Transport first This document uses the following notations for numbers e Values expressed in hexadecimal form are preceded by Ox e Values expressed in binary form are followed
26. IDLE state to the READY_F Sub state The NFC DEP configuration SHALL be used by the NFCC for this purpose Using the configuration for the Type 3 Tag Platform the DH can provide the information required by the Listen Mode state machine described in ACTIVITY for answering a SENSF_REQ Command in IDLE state or READY_F Sub state The Type 3 Tag Platform configuration SHALL be used by the NFCC for this purpose The Type 3 Tag Platform configuration uses a set of parameters whose names start with LF_T3T_IDENTIFIERS_and a following number This document refers to the trailing number as the index and uses the term LF_T3T_IDENTIFIERS without index to refer to the whole parameter set NFC Controller Interface NCI Specification Page 63 RF Communication Configuration Table 35 Discovery Configuration Parameters for Listen F ID Length Value Description LF_CON_BITR_F LF_PROTOCOL_TYPE LF_T3T_MAX 1 Octet 1 Octet 1 Octet Configures the bit rates to listen for as defined in ACTIVITY See Table 37 Default 110b listen for both speeds Protocols supported by the NFC Forum Device in Listen Mode for NFC F See Table 36 Default NFCC decides The NFCC SHALL set the default value corresponding to the protocols implemented on the NFCC 0 16 The maximum index of LF_T3T_IDENTIFIERS supported by the NFCC There is no default because this is a read only parameter The DH SHALL NOT attempt to write this para
27. MAY include flow control mechanisms However it is recommended to rely on the flow control built into the NCI protocol e Transport Mappings providing framing SHALL NOT forward Packets with a size smaller than 3 bytes to the NCI Core The following sub sections describe Transport Mappings for NCI It is not mandated to use any of the Transport Mapping defined on the following sub sections The device implementation MAY use a proprietary Transport Mapping that fulfills the above requirements even for transport layers where this specification contains a mapping 11 1 UART Transport NCI Frames SHALL be transmitted over the UART between an DH and an NFCC with no additional framing Since there is no additional framing the UART transport cannot introduce any errors otherwise the NCI messages stream may be unrecoverable So the UART connection SHALL be of a sufficiently high quality as to provide a reliable data transfer at the configured baud rate The NCI UART Transport SHOULD use the following settings for RS232 e 8 data bits e 1 stop bit e No parity e Automatic i e h w based RTS CTS Flow control The baud rate is manufacturer specific Flow control with RTS CTS is used to prevent temporary UART buffer overrun and is not intended to be used other than temporarily NCI has its own credit based logical flow control mechanism which is better suited to the different types of NCI data that flow across the transport If CTS is 1
28. Mode Routing RF SET LISTEN MODE ROUTING CMD Payload Field s Length Value Description More 1 Octet See Table 45 Number of Routing 1 Octet The number of Routing Entry fields to follow n Entries This Control Message SHALL be at least one Routing Entry Routing Entry X 2 Type 1 Octet One of the types defined in Table 46 1 n Octets Length 1 Octet The length of Value x Value x Octets Value of the Routing TLV RF_SET_LISTEN_MODE_ROUTING_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 Table 45 More field values Value Description 0x00 Last Message 0x01 More Message s to follow 0x02 RFU OxFF Table 46 TLV Coding for Listen Mode Routing Type Length Value 0x00 3 Octets Technology based routing entry value field coded according to Table 47 0x01 3 Octets Protocol based routing entry value field coded according to Table 48 0x02 2 n Octets AID based routing entry value field coded according to Table 49 0x03 0x9F RFU 0xA0 0xFF For proprietary use NFC Controller Interface NCI Specification Page 72 RF Communication Configuration Table 47 Value Field for Technology based Routing Payload Field s Length Value Description Route 1 Octet An NFCEE ID as defined in Table 84 Power State 1 Octet See Table 50 Technology 1 Octet A valid RF Technology as
29. NTF with a given NFCEE ID as discarded by the DH when the NFCEE with this NFCEE ID is disabled If the NFCEE uses the HCI Protocol as defined in ETSI_102622 the NFCC may determine the NFCEE RF Discovery requirements based on the opened pipes Otherwise the method the NFCC uses to find out the NFCEE s RF Discovery requirements is implementation specific The DH SHOULD take the NFCEE s request under consideration based on its own requirements and requests for other NFCEEs Therefore the action taken by the DH on receipt of this notification is implementation specific Table 65 Notification for NFCEE Discovery Request RF_NFCEE_DISCOVERY_REQ_NTF Length Value Description The number of information entries to follow n Information Entry Type 1 Octet One of the types defined in Table 66 1 n el Payload Field s Number Of Information Entries Length 1 Octet The length of Value x Value x Octets Value of the Information Entry NFC Controller Interface NCI Specification Page 88 RF Discovery Table 66 TLV Coding for RF NFCEE Discovery Reduest Type Length Value 0x00 3 Octets Information about the particular discovery request in this TLV is to be added to the list value field coded according to Table 67 0x01 3 Octets Information about the particular discovery request in this TLV is to be removed from the list value field coded according to T
30. Page 28 NCI Core Framework e Ifthe packet does not contain the last segment of a segmented Message the PBF SHALL be set to 1b See Section 3 5 for more details about Segmentation and Reassembly 3 4 2 Format of Control Packets The Control Packet structure is detailed in Figure 7 Packet Header A 3 1 4 MET 6 8 L bytes P R R MT 2 GID F F OID Payload Length L Payload UI U Octet 0 Octet 1 Octet 2 Octet 3 Octet 2 L Figure 7 Control Packet Structure Each Control Packet SHALL have a 3 octet Packet Header and MAY have additional payload for carrying a Control Message or a segment of Control Message NOTE In the case of an empty Control Message only the Packet Header is sent Message Type MT Refer to Table 2 for details of the MT field Packet Boundary Flag PBF Refer to Table 3 for details of the PBF field Group Identifier GID The NCI supports Commands Responses and Notifications that are categorized according their individual groups The Group Identifier GID indicates the categorization of the message and SHALL be a 4 bit field containing one of the values listed in Table 102 All GID values not defined in Table 102 are RFU Opcode Identifier OID The Opcode Identifier OID indicates the identification of the Control Message and SHALL be a 6 bit field that is a unique identification of a set of Command Response or Notification Messages within the group GID
31. Proprietary If any of the RF Communication parameters listed in Table 72 to be used for Data Exchange differ from those used during Device Activation the DH SHALL send the new values to the NFCC using an RF_PARAMETER_UPDATE_CMD Not all RF Communication parameter settings are permissible in all modes of operation the DH is responsible for ensuring values sent to the NFCC are correct There is no obligation for the NFCC to check whether a given parameter value is permitted The RF Technology and Mode parameter specifies the RF Technology and Mode that SHALL be used by the NFCC when transmitting and receiving Refer to DIGITAL for permitted values of RF Technology and Mode for a given RF Interface activation The Transmit Bit Rate parameter specifies the bit rate that SHALL be used by the NFCC when transmitting For a polling device this is the bit rate from poll to listen and for a listening device this is the bit rate from listen to poll Refer to DIGITAL for permitted values of bit rate for a given RF Interface activation The Receive Bit Rate parameter specifies the bit rate that SHALL be used by the NFCC when receiving For a polling device this is the bit rate from listen to poll and for a listening device this is the bit rate from poll to listen Refer to DIGITAL for permitted values of bit rate for a given RF Interface activation The NFC B Data Exchange Configuration parameter specifies a number of NFC B related values N
32. RF_DISCOVER_CMD RSP RF_INTF_ACTIVATED_NTF CORE_GENERIC_ERROR_NTF Listen Mode DISC_TG_ACT_FAILED or RF_DEACTIVATE_NTF DISCOVERY_TEAR_DOWN Discovery Link Loss RF_DEACTIVATE_NTF Discovery NFC B Bad AFI RF_DISCOVER_NTF Notification Type 2 RF_DEACTIVATE_CMD RSP NTF Discovery RF_DEACTIVATE_NTF Discovery Link_Loss RF_DEACTIVATE_NTF Discovery Endpoint Request RF DEACTIVATE CMDIRSPINTF Sleep Mode RF DEACTIVATE CMDIRSPINTF Slaap AF Mode RF_DEACTIVATE_NTF Sleep Mode Endpolnt Reguest RF_DEACTIVATE_NTF Sleep AF Mode Endpoint_Request RF NFCEE ACTION NTF RF DEACTIVATE CMDIRSP RFST_ LISTEN_SLEEP RF_DEACTIVATE_CMD RSP NTF Idle Mode RF_INTF_ACTIVATED_ NTF Listan Mode CORE_INTF_ERROR_NTF RF_xxx_ERROR RF DEACTIVATE CMDIRSP Figure 10 RF Communication State Machine Upon successful DH and NFCC initialization see Section 4 2 the RF Communication state machine SHALL be in RFST_IDLE state Before the first transition out of RFST_IDLE state the DH SHALL set the RF Communication Configuration as described in Section 6 For Poll Mode the RF Communication state machine relates to the Activities defined in ACTIVITY in the following way e Technology Detection is handled in RFST_DISCOVERY and RFST_W4_ALL_DISCOVERIES e Collision Resolution is handled in RFST_DISCOVERY and RFST_W4_HOST_SELECT NFC Controller Interface NCI Specification
33. Rae ke oie 30 3 5 Segmentation and Reassembly siese see se se ee ee ee ee Ge GR GRA RA AA ee ee ee 31 3 6 Logical ConTeCtONSE iss ss ES es ee be SE LE Gee ed eke ed ee dee RE Ee Ee ee 32 4 NCI Core Control Messages ccccccesseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeenees 34 AL Res tof ie SEE RR EE EE OE EO EE OE OE ED 34 4 2 Imtialization of NECC Le feces ei at ese edges oe lade ee ee bs eet sen ee ele ceased 36 4 3 NFCC Configuration casdias See Gee se y Shay abn ai Mawel nee 39 4 3 1 Setting the Configuration esse sesse se ee ee EE GRA RA Ge ee ee ee 39 43 2 Retrieve the Configuration sees sees see se Ge ee ee ee ee ee 40 4 4 Logical Connection Management iese ces se se se se ee ee ee ee Ge Ge Ge GR RA ee de 41 4 4 Destination Lype EES sexes SEE Ge eN E De ee Ee gee EE ee ESE Ge EER EE 41 4 4 2 Connection Cr ation iseer cisions een eid a DERS ee ge ten a eel a ES 42 4 4 3 Connection ClOSUrC cccccceeeceeeseceesseceeneeceeeeeeaeceeaaeceeaeeceeeeeaeeseaaeceeneeees 44 4 4 4 Connection Credit Management iese se se ee ee ee ee Ge Ge Ge GR GR ee ee 45 NFC Controller Interface NCI Specification Page ii Contents 45 Generne oi EE EE RE EN RO NN 46 4 6 Interface Brrr ius ee si ee E eels E EEE DE Ee eg ee DE De 46 5 RF Communication ss see RE SG Ou N Ede AG SE GE GE Ge ok Ke Ou OK KG dee 47 5 1 RE Interface Architecture sie GEE EL cots E EE SR OS E EEEE TES 47 9 2
34. StateMachifi ji desc oie ete ee ata ha ee SE Ee ia Re ge ee De Ee Ge 48 32 1 State REST IDEE MEES Ge Ge ee Ee de E De See GE se AE Pe Sue de Se Nee eee 50 52 2 State REST DISCOVERY its ep geeis dee deed oeste se ese Oe AES seges ees ei dese 50 523 State REST W4 ALL DISCOVERIES ou esse esse ee se ee se ee se ee ee ee ee ee ee ee 51 5 2 4 State RFST_W4_HOST_SELECT 0 occ esse esse ee se ee se ee se ee ee ee ee ee ee ee ee ee 51 3 255 State REST POLE ACTIVE Hs se Mae eee Ge ee ee ee ee 52 5 2 6 State REST LISTEN ACTIVE see sd ss ee see ede de ee be nee A A 53 32 7 state REST LISTEN SLEEP nose esse gese e ees SI Gee tsceus ook oe dee thes 53 5 3 RE Pield Information Ee ees see Ne ee be gee oe Ee elite ER cele alee 54 6 RF Communication Configuration ccccccesseesseeeeeeeeeeeeseeeseseeeeeeeeeees 56 6 1 Eonfiguration Parameters ser costes SE Ee Red EDE ae EE GEE tins Baie Se ese ee ee seed ED 56 6 1 1 Poll A Baraimeter sees be sees Ee tese eg Oes beg eek ef Dak se dees seg Re bep ge 56 6 12 Poll B Parameters sis ee Ses Ee be ee e ed ede be ee ee se bee ed ees 57 61 3 Poll F Parameters Ee Se N ee Ee ates tale GE Ee E he eee ee 58 6 1 4 Poll ISO DEP ParametersS isi se es se ee ee ee ee ke ee ed ee E ee Re de de ee ee ee 59 6 1 5 Poll NFC DEP Parameters iss sesse esse sees sed se se es ss ee ee see oi ge ds ee Re oi ed Se ee 60 GAG Listem AParamelers neinet EE EER ESE Ge EE N ee teen ea
35. The credit based flow control mechanism applies to Data Packets Each Data Packet that can contain either a complete Data Message or a segment of a Data Message requires one credit NFC Controller Interface NCI Specification Page 26 NCI Core Framework Flow control is configured per Logical Connection during connection establishment see Section 7 3 for Static RF Connection and Section 4 4 for Dynamic Logical Connection It may be enabled or disabled differently for each Logical Connection and with different parameters It is mandatory for the DH to support credit based flow control though it is optional for the NFCC to request the DH to use flow control Please refer to Section 4 4 4 regarding the normative rules for the credit based flow control mechanism 3 3 2 Exception Handling for Data Messages The rules in this section define the exception processing to be performed by a receiver of an erroneous Data Message In case of a Data Message with syntax error meaning that the coding of the Data Packet is not consistent with this specification e Ifthe receiver is the NFCC it SHALL send a CORE INTERFACE ERROR NTF message with a Status value of STATUS_SYNTAX_ERROR e If the receiver is the DH it SHALL ignore the Data Message NFC Controller Interface NCI Specification Page 27 NCI Core Framework 34 Packet Formats 3 4 1 Common Packet Header All Packets have a common header consisting of an MT field and a PBF field as
36. This is used to create a Dynamic Logical Connection for communicating with a Remote NFC Endpoint 0x03 NFCEE This is used to create a Dynamic Logical Connection for communicating with an NFCEE 0x04 OxCO RFU OXC1 OxFE Proprietary This is for proprietary use e g to create a Logical Connection between the DH and the NFCC for firmware update purposes OxFF RFU NFC Controller Interface NCI Specification Page 41 NCI Core Control Messages 4 4 2 Connection Creation These Control Messages are used when the DH creates a Dynamic Logical Connection to the NFCC Table 13 Control Messages for DH Connection Creation CORE_CONN_CREATE_CMD Payload Field s Length Value Description Destination Type 1 Octet See Table 12 Number of 1 Octet Based on the Destination Type of the connection the number Destination specific of Destination specific Parameter fields following n Parameters Destination specific m 2 Type 1 Octet Type of the Destination specific Parameter 0 n Octets Parameter See Table 15 Length 1 Octet Length of Value m Value m Value of the Destination specific Octets Parameter CORE_CONN_CREATE_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 Max Data Packet 1 Octet A number from 1 255 Payload Size Initial Number of 1 Octet See Table 14 Credits Conn ID 1 Octet The four
37. b3 b2 b1 Octet 0 0 0 0 RFU Discovery Configuration Mode This parameter informs the DH how the NFCC uses the RF Configuration provided by the DH if multiple NFCEESs exist in the NFC Forum Device If set to OOb the DH is the only entity that configures the NFCC If set to 01b the NFCC can receive configurations from the DH and other NFCEEs This implies that the NFCC can manage or merge multiple sets of RF configuration parameters Other values are RFU See Section 7 1 for more details on the use of this parameter Discovery Frequency configuration in RF_DISCOVER_CMD supported if the bit is set to 1b If set to Ob the Discovery Frequency value is ignored and the value of 0x01 SHALL be used by the NFCC Octet 1 RFU AID based routing Supported if the bit is set to 1b NFCC supports 7816 4 Command parsing of SELECT command Protocol based routing Supported if bit is set to 1b Technology based Routing Supported if the bit is set to 1b RFU Octet 2 Octet 3 RFU Switched Off state Supported if the bit is set to 1b Battery Off state Supported if the bit is set to 1b Octet 3 is reserved for proprietary capabilities NFC Controller Interface NCI Specification Page 38 NCI Core Control Messages If no routing type is supported in Octet 1 of the NFCC Features then the NFCC does not support Listen
38. be sent in states other than RFST POLL ACTIVE and RFST LISTEN ACTIVE Table 71 Control Messages for RF Parameter Update RF PARAMETER UPDATE CMD Payload Field s Length Value Description Number of 1 Octet The number of RF Communication Parameter fields to Parameters follow n RF x 2 ID 1 Octet The identifier of the RF Communication Octets Communication Parameter as defined Parameter 1 n in Table 72 Length 1 Octet The length of Value x Value x Octets Value of the RF Communication Parameter RF_PARAMETER_UPDATE_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 Number of 1 Octet The number of RF Communication Parameter ID fields to Parameters follow n Value SHALL be 0x00 and no Parameter IDs listed unless Status STATUS_INVALID_PARAM RF Communication 1 Octet The identifier of the invalid RF Communication Parameter Parameter ID 0 n See Table 72 for a list of IDs NFC Controller Interface NCI Specification Page 96 RF Interfaces Table 72 TLV Coding for RF Communication Parameter ID Type Length Value 0x00 1 Octet RF Technology and Mode coded as defined in Table 96 0x01 1 Octet Transmit Bit Rate coded as defined in Table 97 0x02 1 Octet Receive Bit Rate coded as defined in Table 97 0x03 1 Octet NFC B Data Exchange Configuration coded as defined in Table 73 0x04 0x7F RFU 0x80 0xFF
39. by a lower case b In this document the following rules apply for fields or values defined as Reserved for Future Use RFU e For an NCI message including fields with a subset of octets or bits defined as RFU the sender SHALL set these octets or bits to the value indicated in this document or to zero if no value is given e Foran NCI message including fields with a subset of octets or bits defined as RFU the receiver SHALL disregard these octets or bits and SHALL keep the same interpretation of any other field of the whole message unless explicitly stated otherwise For fields that could contain values that are defined as RFU the sender of an NCI message SHALL NOT set these fields to the RFU values If a parameter is defined as meaningless in certain conditions the message sender SHALL include the parameter but MAY set its value to any value The message receiver SHALL ignore the parameter value Values defined as Proprietary MAY be used by implementations for extensions that are out of scope of this specification In this document Control Messages are defined by using tables specifying the message parameters Control Messages SHALL be coded in the order and length as specified by the corresponding definition table first parameter being defined in the topmost table row The names of Parameters that can be present multiple times in a Control Message are followed by square brackets surrounding the number of times the paramet
40. contains a complete or a segment of a Control Message Both the DH and the NFCC SHALL be capable of supporting Control Messages with a payload of 255 octets which is the maximum size of any Control Message The maximum payload length of a Control Packet is also 255 octets The DH SHALL be capable of receiving Control Packets with 255 octet payloads However the NFCC MAY specify a smaller maximum Control Packet payload size defined by the parameter Max Control Packet Payload Size see Section 4 2 As a result Control Messages can be segmented into multiple Control Packets when sent over the NCI as described in Section 3 5 3 2 1 Flow Control for Control Messages The DH and NFCC are allowed to send a complete Control Message over the NCI in as many Packets as needed There is no Packet based flow control for Control Messages in NCI The following flow control rules apply to Control Messages e After sending a Command the DH SHALL NOT send another Command until it receives a Response for that Command Although the NCI Transport between the DH and NFCC is NFC Controller Interface NCI Specification Page 24 NCI Core Framework reliable as a precaution the DH MAY maintain a timer T to check for a Response If Request Th sgue expires without a Response being received it SHOULD be treated as an Exception and processed as in Section 3 2 2 The value of T SHOULD NOT be less than one second ESE is left up to implementations b
41. eke ESE Eed ek eo bee 61 GAT EisteniB Parameters steer des ei Ee Ee eed Gee ede Ee eN ESE Ee Se ee ede dy 62 61 8 Listen F Parameters ie EE ee N ss DEE Se Geek Ge Ee Ee He Ee Ee EE es Ee Eg Ge Ge Ge Ee ee 63 6 1 9 Listen ISO DEP Parameters uses sesse se esse ee ee ee ee ke ee se Ad ee ee Re de RA ee ee ee ge 66 6 1 10 Listen NFC DEP Parameters uie sees see see esse ese es se ee se ee ee ee Ge Ge Ge ee ee 67 GALL Common Parameters ss RE Ne ss ke EE EK an AE SR oe ko eek Ee aT eed 68 6 2 RF Interface Mapping Configuration se se es ee ee ee Ge GR GR RA ASe ee ee ee 69 6 3 Listen Mode Routing Configuration e sesse esse ese ee ee Ge Ge RA RA AA ee ee ee ee 70 6 3 1 Listen Mode Routing Table Design sesse se esse ee ee ee Ge GR GRA GR ee 70 6 3 2 Configure Listen Mode ROutiNg iese see se se se ee ee ee Ge Ge GR ee ee 72 6 3 3 Read Listen Mode Routing eee ee se ee ee ee ee ee Ge GR GR ee ee 75 ERE DIETAT a ON TE OE RT EE OS EE 76 AA Starting RE Discovery ie es ER aed EES EL eon eet Dee ee Oe Ne ge ee ES ee N ee Ge 76 1 2 Select Discovered Target ss ee EE EER Ee oe E ee EE ee aes 82 73 RF Interface Activation and DeactiVaHON ees sees ss sees ee ee se se de ee Ge ee Ge AA ee ee ee 82 7 3 1 RF Interface Activation Notification sesse esse se ss ses ee ee ee ee Ge AA ed ee ee 82 732 RE Interface Deactivation c cccsscesssscssecseesccceneccssesecesscconseesenssessnaecnaes 86 14 NECEE Discovery Reques
42. in scope NFC Execution Environment NFCEE An environment either built into the NFCC or connected to the NFCC where NFC applications are executed The NFCEE may be included in entities with various form factors some of which can be removable or replaceable NFC Radio Interface A contactless radio interface using NFC technology to communicate with a Remote NFC Endpoint NFC Controller Interface NCI Specification Page 15 Introduction NFC DEP Initiator The role of an NFC Forum Device reached when an NFC Forum Device in Poll Mode has gone through a number of Activities In this mode the NFC Forum Device communicates using the NFC DEP protocol NFC DEP Target The role of an NFC Forum Device reached when the NFC Forum Device in Listen Mode has gone through a number of Activities In this mode the NFC Forum Device communicates using the NFC DEP protocols NFCEE Discovery Process Functionality that allows detection of NFCEEs that are physically connected to the NFCC NFCEE Interface A logical entity on the NFCC that communicates with the DH on one side and an NFCEE on the other side NFCEE Protocol A protocol used in the communication between the NFCC and an NFCEE Notification Message Can only be sent by an NFCC to the DH It is sent asynchronously and typically contains informational parameters Packet A structure that is used to transmit a Message over the NCI Transport There are both Control Packets fo
43. least significant bits of the octet SHALL contain the Conn ID as defined in Table 4 The four most significant bits are RFU Table 14 Initial Number of Credits Value Description 0x00 OxFE Number of credits OxFF Data flow control is not used NFC Controller Interface NCI Specification Page 42 NCI Core Control Messages Table 15 Destination specific Parameters Type Length Value 0x00 2 Octets First octet An RF Discovery ID see Table 53 Second octet RF Protocol see Table 98 0x01 2 Octets First octet NFCEE ID as defined in Table 84 The value of 0x00 DH NFCEE ID SHALL NOT be used Second octet NFCEE Interface Protocol See Table 100 0x02 0x9F RFU OXAO OXEF For proprietary use To create a Logical Connection the DH sends the CORE CONN CREATE CMD to the NFCC and identifies the Destination Type see Section 4 4 1 to which this Logical Connection will apply The combination of Destination Type and Destination Specific Parameters SHALL uniquely identify a single destination for the Logical Connection If the Destination Type is 0x01 then no Destination specific Parameters are allowed If the Destination Type is that of a Remote NFC Endpoint 0x02 then only the Destination specific Parameter with Type 0x00 or proprietary parameters as defined in Table 15 SHALL be present NOTE This version of the specification does not actually use Dynamic Logi
44. listen and for a listening device this is the bit rate from listen to poll See Table 97 Data Exchange Receive 1 Octet Bit Rate that will be used for future Data Exchange in the Bit Rate receive direction For a polling device this is the bit rate from listen to poll and for a listening device this is the bit rate from poll to listen See Table 97 Length of Activation 1 Octet The length of Activation Parameters field to follow Parameters Activation Parameters O n Activation Parameters are defined in the RF Interface Octets section that corresponds to the RF Interface value If a proprietary interface is activated proprietary parameters MAY be used For a list of possible ISO DEP RF Interface Activation Parameters see Table 76 Table 77 Table 78 and Table 79 For a list of possible NFC DEP RF Interface Activation Parameters see Table 82 and Table 83 There are no Activation Parameters defined for the Frame RF Interface The RF Interface to be activated is selected based on the current RF Interface Mapping configuration see Section 6 2 or the parameter in the RF_DISCOVER_SELECT_CMD see Section 7 2 Depending on the selected RF Discovery ID and RF Protocol the NFCC performs protocol activation procedures before activating the RF Interface The protocol activation is described in each RF Interface section When all phases before RF Interface activation are performed successfully the NFCC SHALL sen
45. n Supporting Data n Octets Depends on Trigger NFC Controller Interface NCI Specification Page 89 RF Discovery The Trigger value indicates the type of trigger that has caused this notification to be sent as defined in Table 69 Table 69 Trigger in NFCEE Action Notification Trigger Description Supporting Data 0x00 ISO TIEC_7816 4 SELECT The AID in the SELECT command command with an AID 0x01 RF Protocol based routing The RF Protocol see Table 98 decision 0x02 RF Technology based routing The RF Technology see decision Table 95 0x03 0x0F RFU 0x10 Application initiation Application specific Could be an AID for an ISO IEC_7816 4 type application 0x11 0xFF RFU If RF_NFCEE_ACTION is set to 0x01 the following triggers apply e 0x00 this trigger SHALL be sent by the NFCC when the NFCC is capable of determining the Application Identifier of the accessed application In the case of ISO IEC_7816 4 SELECT commands applies to NFC Forum Tag Type 4 the Notification SHALL be sent for each such SELECT command received and the value of the Supporting Data SHALL contain the AID selected The NFCEE ID field SHALL identify the DH NFCEE or the NFCEE on which the corresponding application is hosted e 0x01 this trigger SHALL be sent when a routing decision is made based on the RF Protocol The Supporting Data SHALL contain the corresponding RF Protocol The ID field SHALL identify the DH NFCE
46. shown in Figure 6 3 1 bits P MT B Information F Octet 0 Octet 1 N Figure 6 NCI Core Packet Format Message Type MT The MT field indicates the contents of the Packet and SHALL be a 3 bit field containing one of the values listed in Table 2 The content of the Information field is dependent on the value of the MT field The receiver of an MT designated as RFU SHALL silently discard the packet Table 2 MT Values MT Description 000b Data Packet Section 3 4 3 001b Control Packet Command Message as a payload Section 3 4 2 010b Control Packet Response Message as a payload Section 3 4 2 011b Control Packet Notification Message as a payload Section 3 4 2 100b RFU 111b Packet Boundary Flag PBF The Packet Boundary Flag PBF is used for Segmentation and Reassembly and SHALL be a 1 bit field containing one of the values listed in Table 3 Table 3 PBF Values PBF Description Ob The Packet contains a complete Message or the Packet contains the last segment of a segmented Message 1b The Packet contains a segment of a Message which is not the last segment The following rules apply to the PBF flag in Packets e If the Packet contains a complete Message the PBF SHALL be set to Ob e If the Packet contains the last segment of a segmented Message the PBF SHALL be set to Ob NFC Controller Interface NCI Specification
47. the DH when the Frame RF Interface is used therefore for all RF Technologies the RF_INTF_ACTIVATED_NTF SHALL NOT contain any Activation Parameters 8 2 3 3 Interface Deactivation The deactivation cases for the Poll side Frame RF Interface are as described in Section 5 2 for RFST_POLL_ACTIVE 8 2 3 4 Failures during Data Exchange Even if there are any failures during data exchange the NFCC SHALL NOT send any CORE_INTERFACE_ERROR_NTF to the DH The DH itself identifies TRANSMISSION ERROR PROTOCOL ERROR or TIMEOUT ERROR in communication with the Remote NFC Endpoint The DH MAY deactivate the RF Interface when it identifies such errors 8 2 4 Listen side Frame RF Interface Management This Interface can be used if the NFC Forum Device is operating in Listen Mode Card Emulation Mode or Peer Mode NFC DEP Target 8 24 1 Discovery Configuration The Discovery configuration parameters defined in the following tables are relevant depending on the NFC technology used in Discovery RF Technology and Mode in RF_DISCOVER_CMD They MAY be changed from defaults by using the CORE_SET_CONFIG_CMD before moving to state RFST_DISCOVERY state NFC Controller Interface NCI Specification Page 100 RF Interfaces e Table 30 Discovery Configuration Parameters for Listen A e Table 32 Discovery Configuration Parameters for Listen B e Table 35 Discovery Configuration Parameters for Listen F e Table 38 Discovery Configuration Parameters for
48. the NFCC MAY be put to sleep mode by the DH sending RF_DEACTIVATE_CMD Sleep Mode or Sleep_AF Mode e g if ISO DEP or NFC DEP implementation on the DH use Frame RF Interface or by the Remote NFC Endpoint If the deactivation to sleep is successful the NFCC SHALL send REF DEACTIVATE NTF Sleep Mode or Sleep AF Mode DH Request or Endpoint Request to the DH The state will then change to RFST_LISTEN_SLEEP If the DH sends RF_DEACTIVATE_CMD Idle Mode the NFCC SHALL send RF_DEACTIVATE_RSP followed by RF_DEACTIVATE_NTF Idle DH Request upon successful deactivation The state will then change to RFST_IDLE On detection of remote RF field off the NFCC SHALL move to the NO REMOTE FIELD state in the Listen Mode State Machine defined in ACTIVITY and send RF_DEACTIVATE_NTF Discovery RF Link Loss to the DH The RF Communication state will then change to RFST_DISCOVERY When using the RF Frame Interface and the DH detects a command or an error during the RF communication which forces returning to the IDLE state as defined in the ACTIVITY Listen Mode state machine the DH SHALL send RF_DEACTIVATE_CMD Discovery to the NFCC which SHALL answer RF_DEACTIVATE_RSP followed by RF_DEACTIVATE_NTF Discovery DH Request The state will then change to RFST_DISCOVERY When using the NFC DEP RF interface and the NFCC detects a RLS_REQ command during the RF communication which forces it returning to the IDLE state as defined in the ACTIVITY Liste
49. the RF Communication parameters contained within the Command NOTE For NFC DEP RF Protocol the RF Communication parameters need to be aligned with the parameter values contained in the PSL_REQ and the update Command is issued after the PSL_REQ is received from the Remote NFC Endpoint but before the PSL_RES is sent The Status field in the RF_ PARAMETER UPDATE RSP indicates whether the setting of these RF Communication parameters was successful or not A Status of STATUS_OK SHALL indicate that all RF Communication parameters have been set to these new values within the NFCC If the DH tries to set a parameter which is not applicable for the NFCC the NFCC SHALL respond with an RF_PARAMETER_UPDATE_RSP with a Status field of STATUS_INVALID_PARAM and including one or more invalid RF Communication parameter ID s All other RF Communication parameters SHALL have been set to the new values within the NFCC 8 2 2 2 Request Type 3 Tag Polling In the RFST_POLL_ACTIVE state the SENSF command which is also part of the T3T command set cannot be handled by the DH over the Frame RF Interface therefore specific Commands are introduced for this case NFC Controller Interface NCI Specification Page 98 RF Interfaces The following Control Messages are used to request the NFCC to send a Type 3 Tag Polling Command Table 74 Control Messages to Request the NFCC to send a Type 3 Tag Polling Command RF_T3T_POLLING_CMD Payload Field s Length Value
50. the b1 of this field to 0 The bit at position X of LF_T3T_FLAGS determines whether the NFCC is allowed to send a SENSF_RES with the identifiers specified in LF_T3T_IDENTIFIERS with index X If the bit at position X is set to 0 the contents of LF_T3T_IDENTIFIERS with index X SHALL be ignored in the process to create responses to a SENSF_REQ if set to 1 they are enabled to be used in this process The bits having a higher number than the value of LF T3T MAX SHALL be ignored by the NFCC If LF_T3T_FLAGS is set to the default 0x0000 sending of SENSF_RES for Type 3 Tag platform is disabled Table 36 Supported Protocols for Listen F Bit Mask Description b7 b6 b5 b4 b3 b2 b1 b0 OctetO X X For proprietary use 0 JO JO JO 0 RFU X If set to 1b NFC DEP Protocol is supported by the NFC Forum Device in Listen Mode Table 37 LF CON BITR F Values Bit Mask Description b7 b6 b5 b4 b3 b2 b1 b0 Octet0 jo O O lO JO 0 RFU X If set to 1b listen for 424 kbps X If set to 1b listen for 212 kbps At least one of the bits b1 or b2 SHALL be set to 1b The Octets 0 and 1 of an LF_T3T_IDENTIFIERS value representing a Type 3 Tag Platform System Code SHALL NOT be configured to be equal to Octets 0 and 1 of any other LF_T3T_IDENTIFIERS value The NFCC SHALL answer by sending CORE_SET_CONFIG_RSP with a Status of STATUS_REJECTED
51. the mapping configuration is rejected the state of the RF Interface Mapping configuration in the NFCC SHALL be invalid As long as the table is invalid starting of the RF Discovery Process is not possible see Section 6 The DH SHALL only use RF Interface values that are supported by the NFCC The RF Interfaces supported by the NFCC are made known to the DH in the CORE INIT RSP 6 3 Listen Mode Routing Configuration If as part of the Discovery Process the DH wants the NFCC to enter Listen Mode and the NFCC has indicated support for listen mode routing the DH SHALL configure the Listen Mode Routing Table This is reguired to provide the NFCC the information on where to route received data when activated in Listen Mode If an NFCEE for which a routing entry exists becomes disabled the NFCC SHALL stop the routing to that NFCEE until the NFCEE is enabled again The corresponding routing entries SHALL be ignored for the time the NFCEE is disabled NOTE The DH should evaluate whether to reconfigure the Listen Mode Routing Table if an NFCEE is disabled for which protocol or technology based routing entries exist that can be handled by other NFCEEs If an NFCEE is removed then the corresponding NFCEE ID becomes invalid and the DH SHALL remove all Routing Entries for that NFCEE ID by reconfiguring the Listen Mode Routing Table 6 3 1 Listen Mode Routing Table Design The Listen Mode Routing Table consists of three types of routing entries Th
52. 1 Octet 0x00 default No bail out during Poll Mode in Discovery activity as defined in ACTIVITY 0x01 Bail out when NFC A Technology has been detected during Poll Mode in Discovery activity as defined in ACTIVITY 0x02 0xFF RFU NFC Controller Interface NCI Specification Page 56 RF Communication Configuration 6 1 2 Poll B Parameters Table 24 Discovery Configuration Parameters for Poll B ID Length Value Description PB_AFI 1 Octet variable Application family identifier as defined in DIGITAL Default 0x00 all application families DIGITAL mandates a value of 0x00 PB_BAIL_OUT 1 Octet 0x00 No bail out during Poll Mode default in Discovery activity as defined in ACTIVITY 0x01 Bail out when NFC B Technology has been detected during Poll Mode in Discovery activity as defined in ACTIVITY 0x02 0xFF RFU PB ATTRIB PARAMI 1 Octet variable The values and coding of this parameter SHALL be as defined in DIGITAL for Param 1 of the ATTRIB command There is no default because this is a read only parameter The DH SHALL NOT attempt to write this parameter PB SENSB REO PARAM 1 Octet variable Control of what is sent in the PARAM byte of an ALLB_REQ or SENSB_REQ as defined in DIGITAL See Table 25 Default 0x00 NOTE The information provided by PB ATTRIB PARAMI1 can be used by the DH to construct a valid ATTRIB command
53. 3 Technology based For each received frame from RF the NFCC SHALL follow the steps below until a route is found 1 Ifthe Listen side ISO DEP RF Interface is used and there is at least one AID based routing entry for the current power state then a Monitor for the SELECT command as defined in ISO IEC_7816 4 If a SELECT command is found for type AID match the AID in the routing table based on the current power state If matched route to that target including the SELECT command otherwise continue with step 1b b Ifitis the first APDU after ISO DEP activation continue with step 2 Otherwise route to the same target as the previous command 2 Check if there is a target configured in the routing table for the currently active protocol based on the current power state If yes route to the target If T3T check for and route to multiple targets otherwise continue with step 3 3 Check if there is target configured for the currently active NFC Technology based on the current power state If yes route to that target otherwise continue with step 4 4 If this step is reached no route was found for the received frame The NFCC handles the frame in an implementation specific manner NFC Controller Interface NCI Specification Page 71 6 3 2 Configure Listen Mode Routing RF Communication Configuration These Control Messages are used to configure the Listen Mode Routing Table Table 44 Control Messages to Configure Listen
54. CC SHALL respond with RF_GET_LISTEN_MODE_ROUTING_RSP with a Status indicating the failure reason and the RF_GET_LISTEN_MODE_ROUTING_NTF SHALL NOT be sent NFC Controller Interface NCI Specification Page 75 RF Discovery 7 RF Discovery This section describes the Control Messages reguired for moving through the state machine defined in Section 5 2 7 1 Starting RF Discovery RF Discovery Process is a periodic activity consisting of poll and listen cycles configured by different discovery configurations The TOTAL_DURATION configuration parameter in Table 41 specifies the duration of one discovery period Total Duration This parameter is used to define the length of listen or idle cycles The following rules are applied for the Total Duration parameter e If both Poll and Listen Modes are configured then Listen Duration length is Total Duration minus Poll Duration where Poll Duration is the time required to execute the Technology Detection Activity see ACTIVITY for the configured technologies when no Remote NFC Endpoint is detected e If only Poll Mode is configured then Idle Duration length is Total Duration minus Poll Duration e If only Listen Mode is configured then this parameter is not applicable e The NFCC MAY extend Total Duration if it is not long enough to cover the Configurations provided in the RF_DISCOVER_CMD NOTE ACTIVITY defines some limits to the length of polling for each technology but there m
55. CC sends the SEL RES indicating according to DIGITAL that the NFC Forum Device may support the Type 4A Tag Platform to the Remote NFC Endpoint The NFCC then receives the RATS command and sends the RATS response to the Remote NFC Endpoint The NFCC SHALL then send the RF_INTF_ACTIVATED_NTF to the DH to indicate that a Remote NFC Endpoint based on ISO DEP has been detected For NFC A the RF_INTF_ACTIVATED NTF SHALL include the Activation Parameters defined in Table 78 Table 78 Activation Parameters for NFC A ISO DEP Listen Mode Parameter Length Description RATS Command Param 1 Octet Byte 2 PARAM of the RATS Command as defined in DIGITAL For NFC B Following the anticollision sequence the NFCC sends the SENSB_RES indicating the NFC Forum Device may support the Type 4B Tag Platform bit 1 1b in the Protocol Type to the Remote NFC Endpoint The NFCC then receives the ATTRIB Command and sends the ATTRIB Response to the Remote NFC Endpoint The NFCC SHALL then send the RF_INTF_ACTIVATED_NTF to the DH to indicate that a Remote NFC Endpoint based on ISO DEP has been detected For NFC B the RF_INTF_ACTIVATED_NTF SHALL include the Activation Parameters defined in Table 79 NFC Controller Interface NCI Specification Page 107 RF Interfaces Table 79 Activation Parameters for NFC B ISO DEP Listen Mode Parameter Length Description ATTRIB Command Length 1 Octet Length of ATTRIB Comman
56. CI Specification Page 9 Introduction The DH higher layer software may contain one or more NFC Execution Environments or one or more NFC Execution Environments may be connected to the DH e g on an SD card All NFC Execution Environments on or connected to the DH are logically viewed as one entity called a DH NFCEE In addition one or more NFC Execution Environments may be integrated or connected to the NFCC These are referred to as NFCEEs The scope of NCI is to define the communication between the DH and the NFCC The communication between the NFCC and NFCEES is out of scope of this specification 1 3 Audience This document is intended for use by manufacturers targeting to implement NFC Controllers NFC Forum Devices or NFC protocol stacks 1 4 Applicable Documents or References ACTIVITY NFC Forum Activity Technical Specification Version 1 0 NFC Forum DIGITAL NFC Forum Digital Protocol Technical Specification Version 1 0 NFC Forum ISO TEC_14443 Identification cards Contactless integrated circuit cards Proximity cards Includes ISO IEC 14443 1 2008 Identification cards Contactless integrated circuit cards Proximity cards Part 1 Physical characteristics ISO IEC 14443 2 2010 Identification cards Contactless integrated circuit cards Proximity cards Part 2 Radio frequency power and signal balance ISO IEC 14443 3 2001 Identification cards Contactless integrated c
57. Command APDU o oo ee esse esse es see se Ge Ge GRA Ge ee ee ee ee ee Ge 122 Figure 22 Mapping of Response APDU e esse esse esse es see se Ge GR GR Ge Re ee ee ee ee ee Ge 123 Figure 23 Data Message Format for Type 3 Tag Command Set Interface ee esse es see 124 Figure 24 SPP Operation iss verge g chy yee ul HE ek Ke GRA GERED GE RA NE ee esata soe eg oe se Eko 128 Figure 25 SPI Data Transfer from the DH to the NFCC without CRC esse esse es see see se 129 Figure 26 SPI Data Transfer from the DH to the NFCC with CRC esse esse es see ee ee se 130 Figure 27 SPI Data Transfer from the NFCC to the DH without CRC esse esse es see see se 131 Figure 28 SPI Data Transfer from the NFCC to the DH with CRC esse esse se es ee ee 132 Figure 29 SPI Race Condition Teorienn teieni ee Se ee E Ge De de vs ed ee DE Ee Ee Pe ve dee see 132 Figure 30 SPI Race Condition 2 cise esse Se SEGE oe be costes Gee ESE Vee PES DnE Rek de Ge Se Ge ESE se Vse ee gee 133 NFC Controller Interface NCI Specification Page v Tables Tables Table AbbreviatlonS ss sfc EE EA GE EG GO oe Sedge ee EG sca eh oe ee 13 Table 2 MT Values sso ick eb ie se DE Mh ee eA Ge Ee Seal see Ee De ee ee Reh ies 28 Table 3 PBF EIE EER ER ER OE OE EE 28 Table SE SAID OE OE EE N N OE N EE N 33 Table 5 Control Messages to Reset the NECC ese esse ee se ee Ge GR GR RA GR Ge ee ee ee ee 34 Table6 NCE SG EE EE OE RE ER RE EE EE 34 Table 7 Confistration Status Es se E
58. Controller Interface NCI Specification Page 73 RF Communication Configuration The DH SHALL NOT try to configure routing of a specific type unless the NFCC has indicated support for routing that type in the NFCC Features sent in the CORE_INIT_RSP Also the DH SHALL NOT try to configure routing for a specific power state unless the NFCC has indicated support for that power state in the NFCC Features sent in the CORE_INIT_RSP On receipt of the RF_SET_LISTEN_MODE_ROUTING_CMD with a valid routing configuration the NFCC SHALL respond with the RF_SET_LISTEN_MODE_ROUTING_RSP with a Status of STATUS_OK In case of an error the NFCC SHALL respond with the RF_SET_LISTEN_MODE_ROUTING_RSP with a Status of STATUS_FAILED and the routing table SHALL be emptied Also if a new routing configuration is comprised of several Commands and any one of these Commands fail then the new routing configurations SHALL be ignored and the routing table SHALL be emptied After above failure cases the DH SHALL retry to configure the routing table until the NFCC accepts the routing table NOTE Failure in routing table configuration may lead to an empty routing table As the routing table can only be configured in RFST_IDLE state this can not happen during ongoing RF communication NFC Controller Interface NCI Specification Page 74 RF Communication Configuration 6 3 3 Read Listen Mode Routing These Control Messages are used by the DH to read the NFCC s Liste
59. DIGITAL Section 4 4 for NFC A and 5 4 for NFC B For NFC F the Data Message SHALL correspond to the SoD and Payload of the Data and Payload Format defined Section 6 4 of DIGITAL After receiving a Data Message the NFCC SHALL append the appropriate EoD and send the result in an RF Frame of the currently used technology to the Remote NFC Endpoint NOTE In addition to the formats in Sections 4 4 5 4 and 6 4 DIGITAL defines Data and Payload Formats for ISO DEP NFC DEP and the Tag Platforms Mapping those formats to the definitions above result in the following In case of ISO DEP the Data Message corresponds to the SoD and Payload of an ISO DEP Block defined in Section 13 1 In case of NFC DEP the Data Message corresponds to the SoD and Payload of the Data and Payload Format defined in Section 14 4 For Type 1 and Type 2 Tag Platform the Data Message includes only the Payload field of the applicable Data and Payload Format sections 8 4 and 9 4 For Type 3 Tag Platform the Data Message includes the SoD and Payload field of the Data and Payload Format defined in Section 10 4 Figure 11 Figure 12 and Figure 13 illustrate the mapping between the Data Message Format and the RF frame for each Frame RF Interface when sending the RF frame to the Remote NFC Endpoint NOTE These figures show the case where NCI Segmentation and Reassembly feature is not used Data Packet Data Packet Header Payload Byte 1 BEE Byen RF Frame Payload EoD
60. Discovery Process will always have the Notification Type set to 0x02 more notifications to follow e A value of 0x00 SHALL be used for the Notification Type if the NFCC has completed the collision resolution process and no further Remote NFC Endpoints have been identified A value of 1 SHALL be used if the NFCC has aborted the collision resolution process due to internal restrictions and therefore further Remote NFC Endpoints might not have been detected After receiving RF_DISCOVER_NTF with a Notification Type field set to 0x00 or 0x01 the DH SHALL either select the Remote NFC Endpoint by sending RF_DISCOVER_SELECT_CMD or stop the RF Discovery Process by sending RF_DEACTIVATE_CMD NFC Controller Interface NCI Specification Page 79 RF Discovery Table 54 Specific Parameters for NFC A Poll Mode Parameter Length Description SENS RES Response 2 Octets Defined in DIGITAL NFCID1 Length 1 Octet Length of NFCID1 Parameter If an NFC Forum Type 1 Tag is detected then no NFCID1 Parameter is available and the value of this parameter is set to 0x00 In all other cases NFCID1 Length value SHALL be either 0x04 0x07 or OxOA Other values are RFU NFCID1 0 4 7 or Defined in DIGITAL 10 Octets SEL_RES Response Length 1 Octets Length of SEL_RES Response Parameter If a NFC Forum Type 1 Tag is detected then no SEL_RES Response is available and the value of this parameter is set to 0x00 In all other cases the value of
61. E cus das Areva eae eee ei GE Ge se 35 Table 8 Control Messages to Initialize the NFCC esse esse ese se Ge Ge GR RA GR Ge ee ee ee ee 36 Table 9 NECC Features er EE n ee Ee ER Ve Ge GE ee Ge ei Pent Ge Re Ee Repack 38 Table 10 Control Messages for Setting Configuration Parameters i s sesse see see se ee ee ee ee 39 Table 11 Control Messages for Reading Current Configuration ses see see see se ee ee ee ee 40 Table 2 Destination Py pes EE Re GER De Ge os ge Se ee GESE ata seed E Taos AE DE Ge aniseed 41 Table 13 Control Messages for DH Connection Creation iese esse esse ee sede ss ee ek Se ee ee ee ee 42 Table 14 Initial Number of Credits esns toene se ee ee ee ee a Ge GRA GRA RA AA Re ee ee ee 42 Table 15 Destination specific Parameters sesse se see ee ee ee Ge Ge GR GRA RA Ge Ge ee ee ee ee 43 Table 16 Control Messages for Connection CloSure sesse esse see se Ge GR AG AR ee ee ee ee 44 Table 17 Control Messages for Connection Credit Management iese ses see se se ee ee ee ee 45 Table 18 Control Messages for Generic Error 0 0 ee esse esse es see ee ee Ge GR GRA RA GR AR ee ee ee ee 46 Table 19 Control Messages for Interface ErrOF iese esse esse esse ee see se ee Ge Ge GR RA GR AR ee ee ee ee 46 Table 20 Notification for RF Field information esse esse es see see se Ge GR GRA RA GR AR ee ee ee ee 54 Table 27 RE Field Status sie SE Ge EE Ee hatin EE VN ol ea ee ee dd 54 Table 22 RF Field Infor
62. E or the NFCEE the traffic is routed to e 0x02 this trigger SHALL be sent when a routing decision is made based on the RF Technology The Supporting Data SHALL contain the corresponding RF Technology The ID field SHALL identify the DH NFCEE or the NFCEE the traffic is routed to e 0x10 this trigger SHALL be sent if and when the NFCEE provides the information to the NFCC The manner in which the application on the NFCEE communicates with the NFCC to provide the information is outside the scope of this specification as is the content of the Supporting Data The ID field SHALL identify the NFCEE providing the information For all cases above a notification SHALL NOT be sent when the NFCEE ID is set to the value of 0x00 DH NFCEE ID The DH can configure whether the NFCC is allowed to send NFCEE Action notifications by setting the following configuration parameter NFC Controller Interface NCI Specification Page 90 RF Discovery Table 70 RF NFCEE ACTION configuration parameter ID Length Value Description REF NFCEE ACTION 1 Octet 0x00 The NFCC SHALL NOT send RF NFCEE Action notifications to the DH 0x01 The NFCC SHALL send RF NFCEE default Actions to the DH upon the triggers described in this section 0x02 0xFF RFU NFC Controller Interface NCI Specification Page 91 RF Interfaces 8 RF Interfaces 8 1 NFCEE Direct RF Interface The NFCEE Direct RF Interface is a pseudo interface t
63. FC B ISO DEP Listen Mode esse esse esse esse ee se ee se ee 108 Table 80 Specific Parameters for NFC DEP RF Interface esse sesse ese ese es se es se es se ee ee ee Ge 110 Table 81 NFC DEP Operation Parameter e esse esse esse esse ee se ee se ee eed ed ee ee ee ee ee ee ee ee ee Ge 110 Table 82 Activation Parameters for NFC DEP Poll Mode iese see ese ese esse es se es se ee se ee se ee se 112 Table 83 Activation Parameters for NFC DEP Listen Mode esse sesse esse esse es se ee se ee se ee se ee 113 Table 4NECEE DS ER ei Re GE Ee ee ee ee RR Ge ED AE Ee nets 115 Table 85 Control Messages for NFCEE Discovery cs ee sees se ee see ee ee ee ee ee ee ee ee ee Ge 115 Table 86 TLV Coding for NFCEE DiSCOVErY esse esse esse ee se ee se ee ee ee ee ee eke ee ee ee ee ee ee ee ee Ge 117 Table 87 Value Field for T3T Command Set Interface Supplementary Information 117 Table 88 Control Messages to Enable and Disable a Connected NFCEE ee ees se esse esse ee se ees 119 Fable 89 SPUmOdeSiisc20 scctehissekeeees iteeusshtaceast su Eeo E Eee EEEE EEEE ENa ER EEDE Ee n NOONE NANNE 127 Table 90 SPI Header Coding DH to NFCC without CRC ssssesssssssssssssessrssrrsseesseessersseessee 129 Table 91 SPI Header Coding DH to NFCC with CRC esse esse se es se ee ee ee Ge ee ee ee ee ee 129 Table 92 SPI Header Coding NFCC to DH without CRC ees esse sees se ee ee ee Ge ke ee ee ee ee 130 Table 93 SPI H
64. F_DEACTIVATE_NTF the NFCC SHALL stop sending any Data Messages related to the RF Interface Upon receipt of a RF_DEACTIVATE_NTF the DH SHALL NOT send any Data Messages related to the RF Interface After an RF Interface has been deactivated no further communication operations defined by the RF Interface including Data Messages SHALL be performed all remaining data in the NFCC and DH buffers that was exchanged in the context of the RF Interface SHALL be removed NFC Controller Interface NCI Specification Page 87 RF Discovery 7 4 NFCEE Discovery Request This notification informs the DH of changes to the list of RF Discovery tasks reguested on behalf of NFCEE s which are attached to the NFCC Information is sent in this notification as a list of TLVs as defined in Table 66 e If an attached NFCEE wishes to start using RF communication for a given combination of RF Protocol RF Technology and Mode a TLV is included in which the Type field is set to 0x00 and the value is set according to Table 67 e If an attached NFCEE wishes to stop using RF communication for a given combination of RF Protocol RF Technology and Mode a TLV is included in which the Type field is set to 0x01 and the value is set according to Table 67 This notification can be sent at any time after the first NFCEE Discovery has been run even if RF Discovery is already in progress The NFCC SHALL consider any previously transmitted RF_NFCEE_DISCOVERY_REQ
65. For Poll Mode one Remote NFC Endpoint must be selected if only one Remote NFC Endpoint is detected it is selected automatically and depending on the RF Interface to activate the NFCC may need to first establish one or more lower level protocol s before activating an RF interface In future extensions of NCI the NFCC may even have to start exchanging some data for instance to check if the remote NFC Endpoint stores NDEF compliant data before activating the RF Interface e For Listen Mode the NFCC may only have to be detected selected by a Remote NFC Endpoint before activating the RF interface Or it may need to first wait for the Remote NFC Endpoint to establish one or more lower level protocol s Section 8 describes dependencies and explains how the RF Interfaces are used 5 2 State Machine The NCI process for RF Communication is described using a state machine shown in Figure 10 It is entirely optional for any DH or NFCC to implement the state machine explicitly However all DH and NFCC implementations SHALL follow NCI behavior exactly as if they had implemented the state machine Each transition from one state to another is accompanied by an appropriate NCI Command Response or Notification so both the DH and NFCC can always unambiguously know the current RF Communication state The following Control Messages SHALL NOT be sent unless permitted by the rules of the state machine e RF DISCOVER CMD RF_DISCOVER_RSP RF_DISC
66. Forum logo in promoting member s products sold under the name of the member e The logo SHALL be printed in black or in color as illustrated on the Logo Page that is available from the NFC Forum at the address above The aspect ratio of the logo SHALL be maintained but the size MAY be varied Nothing MAY be added to or deleted from the logos e Since the NFC Forum name is a trademark of the Near Field Communication Forum the following statement SHALL be included in all published literature and advertising material in which the name or logo appears NFC Forum and the NFC Forum logo are trademarks of the Near Field Communication Forum 1 7 Intellectual Property This document conforms to the Intellectual Property guidelines specified in the NFC Forum s Intellectual Property Rights Policy as outlined in the NFC Forum Rules of Procedure These documents are available on the NFC Forum website 1 8 Special Word Usage The key words SHALL SHALL NOT SHOULD SHOULD NOT and MAY in this document are to be interpreted as described in RFC2119 1 9 Abbreviations The abbreviations as used in this document are defined in Table 1 NFC Controller Interface NCI Specification Page 12 Abbreviation Table 1 Abbreviations Description Introduction AID Application Identifier CRC Cyclic Redundancy Check DH Device Host GID Group Identifier
67. H 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 NFC Controller Interface NCI Specification Page 21 NCI Architecture 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 unlike RF Interface activation 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 NCI uses different Identifiers for Remote NFC Endpoints and NFCEEs These identifiers are dynamically assigned by the NFCC The DH gets to know them in the context of RF Discovery and NFCEE Discovery respectively The identifiers for Remote NFC Endpoints are called RF Discovery IDs They usually have a short lifetime as they are only valid for the time the DH wants to be able to communicate with the Remote NFC Endpoint In contrast the identifiers for NFCEES have a longer lifetime as NFCEEs usually are not frequently added to or removed from a device The identifiers for NFCEEs are called NFCEE IDs There is one re
68. LL send a RF_T3T_POLLING_RSP with a Status value of STATUS_SEMANTIC_ERROR In this case the NFCC SHALL NOT send a RF_T3T_POLLING_NTF NFC Controller Interface NCI Specification Page 99 RF Interfaces 8 2 3 Poll side Frame RF Interface Management This Interface can be used if the NFC Forum Device is operating in Poll Mode Reader Writer Mode or Peer Mode NFC DEP Initiator 8 2 3 1 Discovery Configuration The Discovery configuration parameters defined in the following tables are relevant depending on the NFC technology used in Discovery RF Technology and Mode in RF_DISCOVER_CMD They MAY be changed from defaults by using the CORE_SET_CONFIG_CMD before moving to state RFST_DISCOVERY e Table 23 Discovery Configuration Parameters for Poll A e Table 24 Discovery Configuration Parameters for Poll B e Table 26 Discovery Configuration Parameters for Poll F e Table 41 Common Parameters for Discovery Configuration 8 2 3 2 Discovery and Interface Activation To enable Poll Mode the DH sends the RF_DISCOVER_CMD to the NFCC containing at least one configuration for a Poll Mode RF Technology and Mode In the case where multiple Remote NFC Endpoints are detected and the DH has selected the NFC Endpoint to be used or in the case only a single Remote NFC Endpoint is detected then the NFCC sends an RF INTE ACTIVATED NTF to the DH to indicate that this Interface has been activated The protocol activation is fully under the control of
69. Listen ISO DEP Using this Interface the LI FWI parameter is only applicable for NFC B In the case of NFC Forum Type 4 Tag Emulation by the DH the DH sends the CORE_SET_CONFIG_CMD to configure the Listen A Parameters and or the Listen B Parameters as defined in Table 30 and Table 32 In the case of NFC Forum Type 3 Tag Emulation by the DH the DH sends the CORE_SET_CONFIG_CMD to configure the Listen F Parameters as defined in Table 35 The RF SET LISTEN MODE ROUTING CMD MAY be used to route the received data from the Remote NFC Endpoint to specific NFCEEs which will in this case include routing some or all received data to the DH for example if a NFC Forum Type 4 Tag is being emulated by an NFCEE on the DH 8 2 4 2 Discovery and Interface Activation To enable Listen Mode the DH sends the RF_DISCOVER_CMD to the NFCC containing at least one configuration for a Listen Mode RF Technology and Mode When the NFCC has based on the communication with the Remote NFC Endpoint see ACTIVITY determined whether to activate the Frame RF Interface the NFCC sends the RF INTE ACTIVATED NTF to the DH to indicate that this Interface has been activated to be used for communication with the specified Remote NFC Endpoint To provide the RF Protocol information in the RF_INTF_ACTIVATED_NTF the NFCC needs to recognize the corresponding protocol activation command for example ATTRIB RATS or ATR_REQ before activating the Frame RF Interface and forwardi
70. Mode Routing In that case the DH SHALL NOT use any Command defined in Section 6 3 4 3 NFCC Configuration 4 3 1 Setting the Configuration These Control Messages are used to set configuration parameters on the NFCC Table 10 Control Messages for Setting Configuration Parameters CORE_SET_CONFIG_CMD Payload Field s Length Value Description Number of 1 Octet The number of Parameter fields to follow n Parameters Parameter 1 n m 2 ID 1 Octet The identifier of the configuration parameter Octets See Table 101 for a list of IDs Len 1 Octet The length of Val m If Len is set to 0x00 then the Val field is omitted and the NFCC SHALL set the configuration parameter to its default value Val mOctets The value of the configuration parameter CORE_SET_CONFIG_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 Number of 1 Octet The number of Parameter ID fields to follow n Parameters Value SHALL be 0x00 and no Parameter IDs listed unless Status STATUS_INVALID_PARAM Parameter ID 1 Octet The identifier of the invalid configuration parameter 0 n See Table 101 for a list of IDs All configuration parameters within the NFCC are set to default values but the DH MAY use CORE_SET_CONFIG_CMD to change these values The NFCC responds with CORE_SET_CONFIG_RSP and the Status indicates whether the setting of these co
71. N EG Ge ER Red Ek Re ede N ka lS REUS dek N Ke 19 RAN COMPONENtS OE N EN N 19 EE Eo OR OE AE ER EE N 19 22 1 ou OE AR ER NE N EE HE detent ie 20 PAN Data ELE EE RE OE EO OU EE EE 20 N ee ME EE N EE N eee 21 224 RECommunCAHON Es Re ese i Pe Gee Ses GE ces aca Erge Se Se Me eke 21 225 NFCEE Communication iis siese ee Ese gegee Ke bees ees a e cote gee ee SeSe 21 DDO vldentifiers ER e ME EE RE Re AE RE EE N ee 22 22 1 NEC Cas Shated Resource sc ii STE Ee EE See a ee ee Se SR Ee ns ee ee ee ee ee 22 3 NGI Core Framework susse se GENE Ee SEG WK ee GE Ee we ee ke Ke GAN EG SEN KA Ee ei 23 EE oi RE OE EO N AE RE EE OD Ai 23 32 NCICoiitrol MesSafeS iss iss SA OER ee Gees sek AE gee Goedere ee ei 24 3 2 1 Flow Control for Control Message iese se se ee ee ee Ge Ge Ge Ge ee ee 24 3 2 2 Exception Handling for Control Messages esse esse esse es se ee se ee Se de Ge ee ee ee 25 3 32 NELData Messa ges ESE AR SEE EE Oe De EES Se AE SeSe EDE Ee Ee GENE ates 26 3 3 1 Flow Control for Data Packets sesse esse esse se Ge Ge GR Ge ee ee ee 26 3 3 2 Exception Handling for Data MessageS iese esse esse es se ee se ee se Ge Ge de Ge ee ee 27 34 Packet Formats es ee Se NET Ge Ge Be ee Ee Ee EG Geek ee We Ge ee Ee ee De Gee ee Ge be 28 3 4 1 Common Packet Headrest GRA GR ee Ge ee ee ee 28 3 4 2 Format of Control Packets iese ses see se se ee ee ee ee ee Ge Ge Ge GR ee ee 29 343 Format of Data Packets cestier inaenea eines che Be
72. NFCC decides the NFCC SHALL set the default value corresponding to the RF Interfaces implemented on the NFCC LA_NFCID1 4 7 or 10 NFCID1 as defined in DIGITAL Octets Default NFCC decides NFC Controller Interface NCI Specification Page 61 RF Communication Configuration Table 31 LA_SEL_INFO coding Bit Mask Description b7 b6 b5 b4 b3 b2 b1 bO Octet 0 X X X X X For proprietary use 0 Will be set by the NFCC independently of what is configured by DH X If set to 1b NFC DEP Protocol is supported by the NFC Forum Device in Listen Mode X If set to 1b ISO DEP Protocol is supported by the NFC Forum Device in Listen Mode 6 1 7 Listen B Parameters Table 32 Discovery Configuration Parameters for Listen B ID Length Description LB_SENSB_INFO 1 Octet Used to generate Byte 2 of Protocol Info within SENSB_RES according to DIGITAL See Table 33 Default NFCC decides The NFCC SHALL set the default value corresponding to the protocols implemented on the NFCC LB_NFCIDO 4 Octets NFCIDO as defined in DIGITAL Default NFCC decides LB APPLICATION DATA 4 Octets Application Data Bytes 6 9 of SENSB_RES as defined in DIGITAL Default All octets are set to 0x00 LB_SFGI 1 Octet Start Up Frame Guard Time as defined in DIGITAL Default NFCC decides LB_ADC_FO 1 Octet Byte 3 of Protocol Info within
73. ODE_SET_CMD Payload Field s Length Value Description NFCEE ID 1 Octet NFCEE ID as defined in Table 84 The value of 0x00 DH NFCEE ID SHALL NOT be used NFCEE Mode 1 Octet 0x00 Disable the connected NFCEE 0x01 Enable the connected NFCEE 0x02 RFU OxFF NFCEE_MODE_SET_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 To enable or disable an NFCEE the DH sends the NFCEE_ MODE SET CMD to the NFCC The NFCEE ID identifies the NFCEE on which the action should occur and the NFCEE Mode identifies whether that NFCEE should be enabled or disabled On completion of the necessary processing the NFCC indicates whether the action was successful or unsuccessful by sending the NFCEE_MODE_SET_RSP to the DH In a failure case the Status SHALL be set to STATUS_FAILED see Table 94 The NFCC SHALL NOT route communication to or from a disabled NFCEE This also includes any communication from a Remote NFC Endpoint or from another NFCEE routed via the NFCC NFC Controller Interface NCI Specification Page 119 NFCEE Discovery and Mode Set The NFCC SHALL only enable or disable a NFCEE when triggered by a NFCEE MODE SET CMD If the NFCEE is disabled by the DH with NECEE MODE SET CMD then Logical Connection to this NFCEE SHALL be closed implicitly without sending of a CORE CONN CLOSE CMD and corresponding NFCEE Interface SHALL be deactivated immediately 9 3 1 HCI Ne
74. OVER_NTF e RF DISCOVER SELECT CMD RF DISCOVER SELECT RSP e RF INTE ACTIVATED NTF e RF DEACTIVATE CMD RF DEACTIVATE RSP RF_DEACTIVATE_NTF e CORE INTERFACE ERROR NTF with a Conn ID of a Logical Connection that is used in the context of an RF Interface In addition the following Control Messages as specified in the corresponding sections can only be sent in certain states e RF NFCEE ACTION NTF see Section 7 5 e RF PARAMETER UPDATE CMD RSP see Section 8 2 2 1 NFC Controller Interface NCI Specification Page 48 RF Communication e RF_T3T_POLLING_CMD RSP NTF see Section 8 2 2 2 If the NFCC or DH receives a Control Message in a state where that Control Message is not allowed it SHALL treat this as a semantic error as defined in 3 2 2 Other Commands Responses and Notifications that are not explicitly forbidden by this specification MAY be exchanged in any state CORE_INTF_ERROR_NTF RF_DEACTIVATE_CMD RSP RF ox ERROR RF_DISCOVER_SELECT_CMD RSP RF_INTF_ACTIVATED_NTF Poll Mode RF_DEACTIVATE_CMD RSP NTF Sleep Made RF_DEACTIVATE_CMD RSPINTF Sleep_AF Mode RF_DEACTIVATE_CMD RSP NTF Idle Mode CORE_GENERIC_ERROR_NTF DISC_TG_ACT_FAILED RF_INTF_ACTIVATED_NTF RF DEACTIVATE CMDIRSPINTF Poll Mode Discovery RF_DISCOVER_NTF Notification Type 0 1 RF_DEACTIVATE_CMDIRSP RF_DISCOVER_NTF Notification Type 2 REST_W4_ ALL_DISGOVERIES
75. Page 49 RF Communication e Device Activation is handled in RFST_DISCOVERY RFST_W4_ALL_DISCOVERIES and RFST_W4_HOST_SELECT depending on the number of Remote NFC Endpoints discovered and the RF Interface mapping Depending on the RF Interface part of the Device Activation Activity is handled by the DH in RFST_POLL_ACTIVE e RF Data Exchange is handled in state RFST_POLL_ACTIVE e Depending on the RF Interface the Device Deactivation Activity is fully handled by the NFCC or split between the DH and the NFCC The DH is responsible for handling its part in RFST_POLL_ACTIVE The NFCC handles Device Deactivation when moving from state RFST_POLL_ACTIVE to either RFST_DISCOVERY RFST_IDLE or RFST_W4_HOST_SELECT The Listen Mode state machine defined in ACTIVITY is handled in states RFST_DISCOVERY RFST_LISTEN_ACTIVE and RFST_LISTEN_SLEEP The IDLE state defined in ACTIVITY is hosted inside the RFST_DISCOVERY NCI state 5 2 1 State RFST_IDLE Discovery related configuration defined in Sections 6 1 6 2 and 6 3 SHALL only be set while in this state NOTE Although CORE_SET_CONFIG_CMD may be sent in any state parameters that relate to RF Discovery may only be included in state RFST_IDLE The NFCC SHALL turn the RF field OFF in this state The greedy collection ACTIVITY is cleared in this state When the DH issues a valid RF_ DISCOVER _CMD Command and the NFCC returns RF_DISCOVER_RSP with status STATUS_OK the state is changed to RFST
76. RFACE_ACTIVATION_FAILED OxCl NFCEE_TRANSMISSION_ERROR OxC2 NFCEE_PROTOCOL_ERROR OxC3 NFCEE_TIMEOUT_ERROR OxC4 0xDF RFU Proprietary Status Codes OXEO OXEF For proprietary use NFC Controller Interface NCI Specification Page 136 Common Tables Table 95 RF Technologies RF Technology value Definition 0x00 NFC_RF_TECHNOLOGY_A 0x01 NFC_RF_TECHNOLOGY_B 0x02 NFC_RF_TECHNOLOGY_F 0x03 NFC REF TECHNOLOGY 15693 0x04 Ox7F RFU 0x80 0xFE For proprietary use OxFF RFU NOTE The RF Technology with value 0x03 NFC_RF_TECHNOLOGY_15693 is not covered by DIGITAL Table 96 RF Technology and Mode Value Description 0x00 NFC_A_PASSIVE_POLL_MODE 0x01 NFC_B_PASSIVE_POLL_MODE 0x02 NFC_F_PASSIVE_POLL_MODE 0x03 NFC_A_ACTIVE_POLL_MODE RFU 0x04 RFU 0x05 NFC_F_ACTIVE_POLL_MODE RFU 0x06 NFC_15693_PASSIVE_POLL_MODE RFU 0x07 Ox6F RFU 0x70 OX7F Reserved for Proprietary Technologies in Poll Mode 0x80 NFC_A_PASSIVE_LISTEN_MODE 0x81 NFC_B_PASSIVE_LISTEN_MODE 0x82 NFC_F_PASSIVE_LISTEN_MODE 0x83 NFC_A_ACTIVE_LISTEN_MODE RFU 0x84 RFU 0x85 NFC_F_ACTIVE_LISTEN_MODE RFU 0x86 NFC_15693_PASSIVE_LISTEN_MODE RFU 0x87 OxEF RFU OxFO OxFF Reserved for Proprietary Technologies in Listen Mode NFC Controller Interface NCI Specification Page 137 NOTE NFC Forum Table
77. RFU CORE_RESET_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 NCI Version 1 Octet See Table 6 Configuration 1 Octet See Table 7 Status CORE RESET NTF Payload Field s Length Value Description Reason Code 1 Octet 0x00 Unspecified reason Ox01 Ox9F RFU OxAO OxFF For proprietary use Configuration 1 Octet See Table 7 Status Table 6 NCI Version NCI Version Identifier Definition 0x10 NCI Version 1 0 Other values RFU NFC Controller Interface NCI Specification Page 34 NCI Core Control Messages Table 7 Configuration Status Value Definition 0x00 NCI RF Configuration has been kept 0x01 NCI RF Configuration has been reset 0x02 0xFF RFU The NCI Version parameter SHALL be encoded as an 8 bit field consisting of two 4 bit unsigned values representing the major and minor release levels of this specification The most significant 4 bits SHALL denote the major release level The least significant 4 bits SHALL denote the minor release level of this specification The DH SHALL continue the communication if it supports the major version reported by the NFCC and it SHALL NOT use Commands RFU values or RFU fields from a greater minor version than reported by the NFCC The CORE_RESET_CMD is issued by the DH to reset the NFCC This Command MAY be issued anytime following power up of the NFCC After a reset the NCI initialization as described in Section 4 2 SHALL be per
78. RS_2 0x41 LF_T3T_IDENTIFIERS_3 0x42 LF_T3T_IDENTIFIERS_4 0x43 LF_T3T_IDENTIFIERS_5 0x44 LF_T3T_IDENTIFIERS_6 0x45 LF_T3T_IDENTIFIERS_7 0x46 LF_T3T_IDENTIFIERS_8 0x47 LF_T3T_IDENTIFIERS_9 0x48 LF_T3T_IDENTIFIERS_10 0x49 LF_T3T_IDENTIFIERS_11 Ox4A LF_T3T_IDENTIFIERS_12 Ox4B LF_T3T_IDENTIFIERS_13 Ox4C LF_T3T_IDENTIFIERS_14 0x4D LF T3T IDENTIFIERS 15 Ox4E LF_T3T_IDENTIFIERS_16 Ox4F LF_PROTOCOL_TYPE 0x50 LF_T3T_PMM 0x51 LF_T3T_MAX 0x52 LF_T3T_FLAGS 0x53 LF_CON_BITR_F 0x54 LF_ADV_FEAT 0x55 NFC Controller Interface NCI Specification Page 141 Parameter Name Tag RFU 0x56 0x57 Listen Mode ISO DEP Discovery Parameters LI FWI 0x58 LA_HIST_BY 0x59 LB_H_INFO_RESP OxSA LI BIT RATE Ox5B RFU OxS5C Ox5F Listen Mode NFC DEP Discovery Parameters LN_WT 0x60 LN_ATR_RES_GEN_BYTES 0x61 LN_ATR_RES_CONFIG 0x62 RFU 0x63 0x7F Other Parameters RF_FIELD_INFO 0x80 RF_NFCEE_ACTION 0x81 NFCDEP_OP 0x82 RFU 0x83 0x9F Reserved for Proprietary Use Reserved 0xA0 0xFE Reserved for Extension RFU OxFF NFC Controller Interface NCI Specification Common Tables Page 142 Common Tables Table 102 GID and OID Definitions GID OID NCI Core 0000b 0000b 0001b Message Name CORE_RESET_CMD CORE_RESET_RSP CORE_RESET_NTF CORE_INIT_CMD CORE_INIT_RSP 0010b CORE_SET_CONFIG_CMD CORE_SET_CONFIG_RSP 0011b 0100b CORE_GET_CONFIG_CMD CORE_GE
79. Remote NFC Endpoints or with local NFCEEs Some NCI modules are mandatory parts of an NCI implementation others are optional There can also be dependencies between NCI modules in the sense that a module may only be useful if there are other modules implemented as well For example all modules that deal with communication with a Remote NFC Endpoint the RF Interface modules depend on the RF Discovery to be present NCI modules D wn o 2 ses using of sesde mr a NES LL LL QO cc cc NCI Core Transport Transport Transport Mapping Mapping C Mapping Transport Transport Transport Figure 2 NCI Components 2 2 Concepts This section outlines the basic concepts used in NCI NFC Controller Interface NCI Specification Page 19 NCI Architecture NFC Forum Device DH 7 282 ale NCI 22 2 SEE g slee slee 5 eE eg by as N NFGC kecet poosi NFCEE oll is is 12 io PEE ac Remote NFC Endpoint Figure 3 NCI concepts 2 2 1 Control Messages A DH uses NCI Control Messages to control and configure an NFCC Control Messages consist of Commands Responses and Notifications Commands are only allowed to be sent in the direction from DH to NFCC and Responses and Notifications are only allowed to be sent in the other direction Control Messages ar
80. SENSB_RES according DIGITAL See Table 34 Default 0x05 NFC Controller Interface NCI Specification Page 62 RF Communication Configuration Table 33 LB_SENSB_INFO values Bit Mask Description b7 b6 b5 b4 b3 b2 b1 bO Octet0 X X For proprietary use O IO JO O JO RFU X If set to 1b ISO DEP Protocol is supported by the NFC Forum Device in Listen Mode Table 34 LB_ADC_FO values Bit Mask Description b7 b6 b5 b4 b3 b2 b1 bO Octet 0 O JO JO 0 Will be set by the NFCC independently of 0 what is configured by DH X X b3 and b4 of ADC Coding field of SENSB_RES Byte 12 as defined in DIGITAL X If set to 1b DID MAY be used otherwise it SHALL NOT be used 6 1 8 Listen F Parameters The NFC F listen configuration supports the configuration for the NFC Forum Type 3 Tag Platform as well as for NFC DEP Target functionality The DH may configure none one or both of these capabilities The names of configuration parameters in Table 35 which are only relevant for the Type 3 Tag Platform start with the prefix LF_T3T_ The other parameters are relevant to configure the NFC DEP functionality Using the configuration for the NFC DEP functionality the DH can provide the information required by the Listen Mode state machine described in ACTIVITY for moving from the
81. SO IEC_14443 Listen Mode The mode of an NFC Forum Device where it does not generate a carrier In this mode the NFC Forum Device listens for the RF field of another device Logical Connection A communication channel between the Device Host DH and the NFC Controller NFCC that is used for data communication towards either the NFCC itself an NFCEE or a Remote NFC Endpoint Message A generic term for a Command Response Notification or Data object communicated between the DH and NFCC NCI The logical interface between a Device Host DH and an NFC Controller NFCC NCI Core Defines the basic NCI functionality required between the Device Host DH and NFC Controller NFCC NCI Transport The physical connection e g SPI I2C UART USB etc and any associated link level protocol between the DH and NFCC Each supported NCI Transport has a Transport Mapping which defines the characteristics of the NCI Transport An NCI Transport provides the ability to reliably transfer data without intimate knowledge of the data being transferred The NCI specification defines multiple Transport Mappings NFC Controller NFCC The logical entity responsible for the transmission of data over the NFC Radio Interface The NFC Controller has a connection to the Device Host DH and may have connections to additional NFC Execution Environments NFCEEs Those connections are out of scope of this specification but the impacts to the NCI are
82. State RFST_POLL_ACTIVE In this state the NFCC device is activated in Poll Mode The NFCC SHALL keep the RF field ON while in this state In this state an RF Interface is activated which allows the NFCC to communicate with a Remote NFC Endpoint The NFCC SHALL accept and send Data Messages to or from the DH as specified by the active RF Interface In this state the DH MAY send RF_DEACTIVATE_CMD Sleep Mode or Sleep_AF Mode to deactivate communication with the Remote NFC Endpoint Depending on the activated interface and protocol the NFCC will issue RF commands to put the Remote NFC Endpoint into sleep state The NFCC internally marks the state of that particular RF Discovery ID device as sleeping and SHALL send RF_DEACTIVATE_RSP followed by RF_DEACTIVATE_NTF Sleep Mode or Sleep_AF Mode DH Request upon successful completion The state will change to RFST_W4_HOST_SELECT If the DH sends RF_DEACTIVATE_CMD Idle Mode the NFCC SHALL send RF_DEACTIVATE_RSP followed by RF_DEACTIVATE_NTF Idle Mode DH Request upon successful deactivation The state will then change to RFST_IDLE If the DH sends REF DEACTIVATE CMD Discovery the NFCC SHALL send RF_DEACTIVATE_RSP followed by RF_DEACTIVATE_NTF Discovery DH Request upon successful deactivation The state will then change to RFST_DISCOVERY where the NFCC SHALL either restart or continue the Polling discovery activity In both cases above depending on the activated interface and protocol
83. T_CONFIG_RSP CORE_CONN_CREATE_CMD CORE CONN CREATE RSP 0101b CORE_CONN_CLOSE_CMD CORE_CONN_CLOSE_RSP 0110b CORE_CONN_CREDITS_NTF O111b CORE_GENERIC_ERROR_NTF 1000b CORE_INTERFACE_ERROR_NTF 1001b 1111b RFU RF Management 0000b 0001b RF_DISCOVER_MAP_CMD RF_DISCOVER_MAP_RSP 0001b RF_SET_LISTEN_MODE_ROUTING_CMD RF_SET_LISTEN_MODE_ROUTING_RSP 0010b RF_GET_LISTEN_MODE_ROUTING_CMD RF_GET_LISTEN_MODE_ROUTING_RSP RF_GET_LISTEN_MODE_ROUTING_NTF 0011b RF_DISCOVER_CMD RF_DISCOVER_RSP RF_DISCOVER_NTF 0100b RF DISCOVER SELECT CMD RF DISCOVER SELECT RSP 0101b RF_INTF_ACTIVATED_NTF 0110b RF_DEACTIVATE_CMD RF_DEACTIVATE_RSP RF_DEACTIVATE_NTF O111b RF_FIELD_INFO_NTF NFC Controller Interface NCI Specification Page 143 GID OID 1000b Message Name RF_T3T_POLLING_CMD RF_T3T_POLLING_RSP RF_T3T_POLLING_NTF Common Tables 1001b RF_NFCEE_ACTION_NTF 1010b RF_NFCEE_DISCOVERY_REQ NTF 1011b RF_PARAMETER_UPDATE_CMD RF_PARAMETER_UPDATE_RSP 1100b 1111b RFU NFCEE Management 0010b 0000b NFCEE_DISCOVER_CMD NFCEE_DISCOVER_RSP NFCEE_DISCOVER_NTF 0001b NFCEE_MODE_SET_CMD NFCEE_MODE_SET_RSP Proprietary 1111 0010b 1111b RFU NOTE An implementation using proprietary Notifications should take into account that any DH not supporting those proprieta
84. _DISCOVERY 5 2 2 State RFST_DISCOVERY In this state the NFCC stays in Poll Mode and or Listen Mode based on the discovery configuration until at least one Remote NFC Endpoint is detected or the RF Discovery Process is stopped by the DH The parameters and duty cycle for Poll Mode and Listen Mode are as configured by the DH The NFCC is expected to start filling up the greedy collection ACTIVITY in this state If discovered by a Remote NFC Endpoint in Listen mode once the Remote NFC Endpoint has established any underlying protocol s needed by the configured RF Interface the NFCC SHALL send RF_INTF_ACTIVATED_NTF Listen Mode to the DH and the state is changed to RFST_LISTEN_ACTIVE While polling if the NFCC discovers more than one Remote NFC Endpoint or a Remote NFC Endpoint that supports more than one RF Protocol it SHALL start sending RF DISCOVER NTF messages to the DH At this point the state is changed to RFST_W4_ALL_DISCOVERIES NFC Controller Interface NCI Specification Page 50 RF Communication While polling if the NFCC discovers just one Remote NFC Endpoint that supports just one Protocol the NFCC SHALL try to automatically activate it The NFCC SHALL first establish any underlying protocol s with the Remote NFC Endpoint that are needed by the configured RF Interface On completion the NFCC SHALL activate the RF Interface and send RF INTE ACTIVATED NTF Poll Mode to the DH At this point the state is changed t
85. able 67 0x02 0x7F RFU 0x80 0xFF For proprietary use Table 67 Value Field for NFCEE Discovery Request Information Payload Field s Length Value Description NFCEE 1 Octet An NFCEE ID as defined in Table 84 RF Technology 1 Octet An RF Technology and Mode as defined in and Mode Table 96 RF Protocol 1 Octet An RF Protocol as defined in Table 98 7 5 RF NFCEE Action RF NFCEE Action is the mechanism used to indicate that an action involving one of the NFCEEs in the device has occurred that may be of interest to the DH Actions could be routing decisions made by the NFCC or the availability of application level information about a transaction with a Remote NFC Endpoint For example this indication could provide a mechanism for a User Interface application on the DH to perform any application specific behaviors based on the knowledge that a specific NFCEE or application on an NFCEE has been accessed by a Remote NFC Endpoint For example the User Interface application could display branding and or request an action from a consumer This notification SHALL NOT be sent in states other than RFST_LISTEN_ACTIVE Table 68 Notification to Report an NFCEE Action RF_NFCEE_ACTION_NTF Payload Field s Length Value Description NFCEE ID 1 Octet An NFCEE ID as defined in Table 84 Trigger 1 Octet See Table 69 Supporting Data Length 1 Octet The length of Supporting Data field to follow
86. ad length is the length of the whole NCI packet inclusive of the NCI header Since the NCI packet can be as long as 258 octets we need a 2 octet payload length field Figure 25 illustrates the above procedure to transfer data from the DH to the NFCC J SPI_CSN SPLINT SPL CLK IDLE ACTIVE IDLE SPI_MOSI IDLE es es ie ae SPL MISO TRISTATE y Oorl TRISTATE Figure 25 SPI Data Transfer from the DH to the NFCC without CRC If the second octet is equal to 0x01 the DirectWrite header is sent as shown in the table below and 2 octet CRC SHALL follow the Payload CRC SHALL be a CRC 16 CCITT using the polynomial x16 x12 x5 1 calculated for all octets of Header and Payload The initial value SHALL be FFFFh The first CRC octet transmitted SHALL be the MSB The master SHALL send ACK if the CRC is correct when receiving data from the slave The master SHALL send NAK if the CRC is not correct when receiving data from the slave Table 91 SPI Header Coding DH to NFCC with CRC First Octet Second Octet Third Octet Fourth Octet Master 0x01 0x01 b8 NAK if set to lb LSB b7 ACK if set to 1b Payload b6 b1 MSB engm Payload Length Slave 0x00 0x00 0x00 0x00 Figure 26 illustrates the procedure to transfer data from the DH to the NFCC when the Second Octet is equal to 0x01 NFC Controller Interface NCI Specification Page 129 Transport Mappings SPI CSN
87. age 130 Transport Mappings SPI CSN SPI INT SPI CLK IDLE ACTIVE IDLE SPL MOSI IDLE FEE y Oorl IDLE Y V Length DirectRead SPI_MISO TRISTATE A Oorl Ges Payload TRISTATE Figure 27 SPI Data Transfer from the NFCC to the DH without CRC If the second octet is equal to 0x01 the DirectRead header is sent as shown in the table below and 2 octet CRC SHALL follow the Payload The CRC SHALL be the same as defined in Section 11 3 2 1 The slave SHALL send ACK if the CRC is correct when receiving data from the master The slave SHALL send NAK if the CRC is not correct when receiving data from the master Table 93 SPI Header Coding NFCC to DH with CRC b6 b1 MSB Payload Length First Octet Second Octet Third Octet Fourth Octet Master 0x02 0x01 0x00 0x00 Slave 0x00 0x00 b8 NAK if set to 1b LSB Payload b7 ACK if set to 1b Length Figure 28 illustrates the procedure to transfer data from NFCC to the DH when Second Octet is equal to 0x01 NFC Controller Interface NCI Specification Page 131 Transport Mappings SPI CSN SPI_INT T SPI_CLK IDLE ACTIVE IDLE SPIMOSI DLE Disa je SPI_MISO TRISTATE oorl om ek TRISTATE Figure 28 SPI Data Transfer from the NFCC to the DH with CRC If the master does not assert SPI_CSN in a timely fashion the slave is allowed to deassert SPI_INT This can happen if the mas
88. ates the mapping between Response APDU and the Data Packets to be sent to the DH NFC Controller Interface NCI Specification Page 122 NFCEE Interfaces APDU Data Field Swi SW2 Data Packet Data Packet Header Payload Data Packet Header Payload Figure 22 Mapping of Response APDU 10 1 2 Failures during Data Exchange If the NFCEE fails to respond to an APDU command within the appropriate time the NFCC SHALL send a CORE_INTERFACE ERROR NTF with the Status set to NFCEE_TIMEOUT_ERROR If the data received from the DH is not formatted correctly that is is less than 4 octets in length or for example the value provided for Lc in the Command Header does not match the length of the data field the NFCC SHALL send a CORE_INTERFACE_ERROR_NTF with the Status set to NFCEE_PROTOCOL_ERROR 10 2 HCI Access NFCEE Interface The HCI Access Interface is used by the DH to communicate with NFCEEs connected to the NFCC and supporting HCI according to ETSI_102622 The NFCC SHALL support the HCI Access Interface if one or more NFCEEs are connected to NFCC using HCI NOTE ETSI_102622 uses different terms to those used in this specification Terminal used in ETSI_102622 corresponds to DH in this specification CLF used in ETSI_102622 corresponds to NFCC in this specification Host controller according ETSI_102622 is implemented by the NFCC UICC is a specific implementation of an NFCEE having also a link with DH via t
89. ay be NFCC implementation specific variations Also the minimum length of listening for each technology may vary per implementation Thus the DH may not know the exact minimum value to be used for Total Duration If the Discovery Configuration Mode in Octet 0 of the NFCC Features as returned in CORE_INIT_RSP is set to 00b the DH is responsible for defining not just the configuration parameters but the Listen Mode Routing Table and the RF Technology and Mode list in the RF_DISCOVER_CMD The NFCC is unable to modify these items so the entire process of RF Discovery is as defined by the DH If the Discovery Configuration Mode in Octet 0 of the NFCC Features as returned in CORE_INIT_RSP is set to 01b the DH may choose to set configuration parameters Listen Mode Routing Table and the RF Technology and Mode list in the RF_DISCOVER_CMD for its own purposes However the NFCC may modify any or all of these items to suit its own RF Discovery needs If the DH has no needs for RF Discovery the RF Technology and Mode list in RF DISCOVER CMD may be empty and the NFCC may use just its own values The following Control Messages are used to initiate the RF Discovery Process NFC Controller Interface NCI Specification Page 76 RF Discovery Table 52 Control Messages to Start Discovery RF_DISCOVER_CMD Payload Field s Length Value Description Number of 1 Octet The number of Configuration f
90. back data For testing purposes the DH can enable the loopback mode by creating a Logical Connection with Destination Type value 0x01 After the successful creation of the Logical Connection the DH MAY send Data Messages over that connection and the NFCC SHALL loopback the same Data Messages to the DH Flow control and segmentation amp reassembly mechanisms apply also for the loopback connection NOTE Data Messages can be segmented differently when returning them to the DH NFC Controller Interface NCI Specification Page 134 Exhibit A A ExhibitA Exhibit A is left blank intentionally NFC Controller Interface NCI Specification Page 135 Common Tables B Common Tables Table 94 Status Codes Status Code Description Generic Status Codes 0x00 STATUS_OK 0x01 STATUS_REJECTED 0x02 STATUS_RF_FRAME_CORRUPTED 0x03 STATUS_FAILED 0x04 STATUS_NOT_INITIALIZED 0x05 STATUS_SYNTAX_ERROR 0x06 STATUS_SEMANTIC_ERROR 0x07 0x08 RFU 0x09 STATUS_INVALID_PARAM OXOA STATUS MESSAGE SIZE EXCEEDED OxOB Ox9F RFU RF Discovery Specific Status Codes OxAO DISCOVERY_ALREADY_STARTED OxAl DISCOVERY_TARGET_ACTIVATION_FAILED OxA2 DISCOVERY_TEAR_DOWN OxA3 0xAF RFU RF Interface Specific Status Codes OxBO RF_TRANSMISSION_ERROR OxB1 RF_PROTOCOL_ERROR OxB2 RF_TIMEOUT_ERROR OXB3 OXBE RFU NFCEE Interface Specific Status Codes OxCO NFCEE_INTE
91. cal Connections for communication with Remote NFC Endpoints If the Destination Type is that of an NFCEE 0x03 then only the Destination specific Parameter with Type 0x01 or proprietary parameters as defined in Table 15 SHALL be present After receipt of a CON CREATE CMD the NFCC must determine whether to accept the request and if so continue with the actual creation of the Logical Connection The NFCC SHALL respond with a CORE_CONN_CREATE_RSP where the Status SHALL indicate whether the Logical Connection has been established STATUS_OK or failed In failure case and if no different Status value is specified for the concrete case the Status value SHALL be STATUS_REJECTED NOTE For example NFCEE Interface activation Section 10 defines a specific Status value for the NFCEE Interface activation failure If the Logical Connection has been established the Conn ID SHALL indicate the Connection Identifier for this Logical Connection The CORE_CONN_CREATE_RSP SHALL contain the actual Conn ID used for the Logical Connection If data flow control is requested by the NFCC the NFCC also indicates the Initial Number of Credits that the NFCC has allocated for this connection s receive path If data flow control is not requested the NFCC SHALL set the parameter value for Initial Number of Credits to OxFF NFC Controller Interface NCI Specification Page 43 NCI Core Control Messages 4 4 3 Connection Closure These Control Messages are u
92. cal Specification Version 1 1 NFC Forum MANU Register of IC manufacturers ISO IEC JTC1 SC17 Standing Document 5 RFC2119 Key words for use in RFCs to Indicate Requirement Levels RFC 2119 S Bradner March 1997 Internet Engineering Task Force T3TOP NFC Forum Type 3 Tag Operation Specification Version 1 0 NFC Forum 1 5 Administration The NFC Forum NFC Controller Interface NCI Specification is an open specification supported by the Near Field Communication Forum Inc located at 401 Edgewater Place Suite 600 Wakefield MA 01880 Tel 1 781 876 8955 Fax 1 781 610 9864 NFC Controller Interface NCI Specification Page 11 Introduction http www nfc forum org The NFC Forum Inc maintains this specification Comments errors and other feedback can be submitted at http www nfc forum org apps group_public add_comment php document_id 13436 1 6 Name and Logo Usage The Near Field Communication Forum s policy regarding the use of the trademarks NFC Forum and the NFC Forum logo is as follows e Any company MAY claim compatibility with NFC Forum specifications whether a member of the NFC Forum or not e Permission to use the NFC Forum logos is automatically granted to designated members only as stipulated on the most recent Membership Privileges document during the period of time for which their membership dues are paid e Member s distributors and sales representatives MAY use the NFC
93. ce activation The assigned NFCEE ID remains valid until the NFCEE is removed or the NFCC is reset with a Configuration Status of 0x01 Once NFCEE Discovery Process has been enabled the NFCC SHALL notify the DH of any detectable removals and or reconnections of NFCEEs through the NFCEE_DISCOVER_NTF If a NFCEE_DISCOVER_NTF is sent to notify that a new NFCEE has been connected to the NFCC the initial state of this NFCEE SHALL be connected and disabled NFCEE Status value set to 0x01 If the NFCEE Status is set to 0x02 NFCEE removed the Number of Protocol Information Entries SHALL be 0 If the NFCEE Discovery Process fails then NFCEE_DISCOVER_RSP SHALL be sent with Status of STATUS_FAILED see Table 94 In the failure case the Number of NFCEEs SHALL be 0 If the NFCC detects that an NFCEE is removed then the Logical Connection to this NFCEE SHALL be closed implicitly and the corresponding NFCEE Interface Protocol SHALL be deactivated immediately In case NFCEE Discovery is enabled a NFCEE_DISCOVER_NTF is sent To disable the sending of NFCEE_DISCOVER_NTF the DH SHALL send the NFCEE_DISCOVER_CMD with Discovery Action is set to 0x00 The NFCC SHALL respond by sending a NFCEE_DISCOVER_RSP with a Status set to STATUS_OK and the Number of NFCEEs parameter SHALL be ignored by DH 9 2 1 HCl Network Specific Handling The HCI Network as specified ETSI 102622 is treated logically by the NCI Specification as one virtual NFCEE
94. credits to send the whole Data Message the DH is allowed to send as many Data Packets as number of credits available When the DH wants to send a Data Packet on a Logical Connection and flow control is enabled the DH SHALL check that the NFCC_Credits_Avail variable for that connection is greater than 0 If so the DH SHALL reduce the NFCC_Credits_Avail by 1 and transfer the Data Packet over the Logical Connection The DH SHALL NOT send any Data Packet on a connection when the corresponding NFCC_Credits_Avail is 0 If the NFCC receives a Data Packet that was subject to credit based flow control it needs to tell the DH when the buffer is again available for use It does this by sending CORE CONN CREDITS NTF When the DH receives this Notification it SHALL add the credits to variable NFCC_Credits_Avail for the appropriate Logical Connection s The DH SHALL set the NFCC_Credits_Avail variable to the initial value on the following scenarios e A Dynamic Logical Connection is created See Sections 4 4 2 e For the Static RF Connection if an RF Interface Activated Notification is received see Section 7 3 1 NFC Controller Interface NCI Specification Page 45 NCI Core Control Messages 4 5 Generic Error This Notification is used to inform the DH about a generic error situation Table 18 Control Messages for Generic Error CORE GENERIC ERROR NTF Payload Field s Length Value Description Status 1 Octet See Tabl
95. d Parameter n ATTRIB Command n Octets All Bytes of the ATTRIB Command as defined in DIGITAL starting from and including Byte 2 8 3 3 3 Interface Deactivation Additional rules apply for the following deactivation cases described in Section 5 2 for RFST LISTEN ACTIVE e RF DEACTIVATE NTF SIeep Mode Endpoint Request After sending an S DESELECT response block to the Remote NFC Endpoint the NECC SHALL send the RF_DEACTIVATE_NTF When using this RF Interface the following deactivation cases described in Section 5 2 for RFST LISTEN ACTIVE SHALL NOT be allowed e RF _DEACTIVATE_NTF Discovery Endpoint Reguest e RF DEACTIVATE NTF Sleep AF Mode Endpoint Request e RF DEACTIVATE CMD RSP NTFE Seep AF Mode e RF DEACTIVATE CMD RSP NTF Sleep Mode 8 3 3 4 Failures during Data Exchange If an ISO DEP Protocol Error PROTOCOL EXCEPTION as defined in DIGITAL occurs the NFCC SHALL send the CORE INTERFACE ERROR NTF with the Status of RF PROTOCOL ERROR When the DH receives the CORE INTERFACE ERROR NTE the DH MAY initiate ISO DEP RF Interface deactivation or perform some other error handling procedure 8 4 NFC DEP RF Interface Both the Poll side and Listen side NFC DEP RF Interfaces provide access to the Transport Data Bytes of the NFC DEP frames exchanged between the NFC Forum Device and a Remote NFC Endpoint Using this interface the DH does not need to have any knowledge related to the NFC DEP frame format ho
96. d RF_INTF_ACTIVATED_NTF with information about the activated RF Interface RF Interface field After the NFCC sends RF_INTF_ACTIVATED_NTF the Static RF Connection may be used The Max Data Packet Payload Size and Initial Number of Credits parameters of the RF INTE ACTIVATED NTE apply to the Static RF Connection NOTE The NFCC may choose any permitted values for Max Data Packet Payload Size and Initial Number of Credits when activating an RF Interface regardless of any values that may have been used in previous activations The Data Exchange RF Technology and Mode Data Exchange Transmit Bit Rate and Data Exchange Receive Bit Rate parameters inform the DH about the RF Technology and Bit Rates used in the further data exchange with the Remote NFC Endpoint NFC Controller Interface NCI Specification Page 84 RF Discovery RF INTE ACTIVATED NTF can include Activation Parameters Activation Parameters depend on the RF Interface field Each RF Interface section defines the parameters to be included Other parameters in the RF INTE ACTIVATED NTF are the same as in the RF DISCOVER NTE The RF Discovery ID value communicated in an RF INTE ACTIVATED NTF SHALL be valid until the state is changed to RFST_IDLE NFC Controller Interface NCI Specification Page 85 RF Discovery 7 3 2 RF Interface Deactivation These Control Messages are used to deactivate an active RF Interface to stop communication between the DH or NFCEE with a Remot
97. de 73 Value Field for AlD based Routing esse see se se se ee ee ee ee Ge Ge Ge GR GR ek ee 73 Value Field for Power State iese ses se se E ee ee Ge Ge GR GR E ee 73 Control Messages to Read the NFCC s Listen Mode Routing sees sees ses ee se de 75 Control Messages to Start DisCOVETY iese sees see se ee Ge Se ee ee ee ee Ge Ge GRA GR ee ee 77 RE Discovery Dis SR SS Ee GE eta eves ee lesen eee eae eden 78 Specific Parameters for NFC A Poll Mode esse ss ee se ee se Ge GR GR Ge Ge ee ee 80 Specific Parameters for NFC A Listen Mode esse esse es see se Ge RA ee ee ee 80 Specific Parameters for NFC B Poll Mode esse esse see se Ge GR ee Ge ee ee 80 Specific Parameters for NFC B Listen Mode iese esse es see se se GR AA ee ee ee 80 Specific Parameters for NFC F Poll Mode o00 cece eesceesecseecssecesecnaecnseceseeeseeeseeeseeeees 81 Specific Parameters for NFC F Listen Mode ees esse ee see se ee Ge GR GR ee Ge ee ee 81 Control Messages to select a Discovered Target sesse ee ee ee Ge Ge RA Ge ee 82 Notification for RF Interface activation esse sesse see se ee ee ee ee ee Ge Ge Ge RA ee 83 Control Messages for RF Interface Deactivation esse sesse esse es ee ee Ge Ge RA GR ed 86 Deactivation TYDPERKE Ek RE N ee EE ba dete ne ee Ons ee Pe Sek VER e ee 86 Deactivation MES N N OE RR EE N OE 87 Notification for NFCEE Discovery Reguest esse esse esse esse esse ee se ee se ee se de se ee ee de ee ee de 88 TLV
98. defined in Table 95 Table 48 Value Field for Protocol based Routing Payload Field s Length Value Description Route 1 Octet An NFCEE ID as defined in Table 84 Power State 1 Octet See Table 50 Protocol 1 Octet A valid RF Protocol as defined in Table 98 Table 49 Value Field for AID based Routing Payload Field s Length Value Description Route 1 Octet An NFCEE ID as defined in Table 84 Power State 1 Octet See Table 50 AID 5 16 Octets Application Identifier Table 50 Value Field for Power State Bit Mask Description b7 b6 b5 b4 b3 b2 b1 b0 O IO JO JO JO RFU X Battery off X Switched off X Switched on When configuration of the NFCC for Listen Mode communication is necessary the DH SHALL always send the complete Listen Mode Routing Table The NFCC uses the More field to determine if it has received all the Commands necessary to configure the routing The new routing SHALL only become effective following receipt of all configuration information The DH SHALL keep the total size of the routing configuration information smaller than the Max Routing Table Size indicated during Initialization see Section 4 2 All parameters except More and Number of Routing Entries are included in the calculation to determine if the routing configuration size exceeds the Max Routing Table Size NFC
99. e 94 This Notification is used in error situations when the error can not be notified using an error status in a Response Message This Notification SHALL NOT be used to report error scenarios related to NFCEE or RF Interface communication using Logical Connections To notify a generic error situation the NFCC SHALL send CORE_GENERIC_ERROR_NTF to the DH with the Status code identifying the error case 4 6 Interface Error These Control Messages are used to inform the DH about an RF or NFCEE Interface communication specific error situation Table 19 Control Messages for Interface Error CORE_INTERFACE_ERROR_NTF Payload Field s Length Value Description Status 1 Octet See Table 94 Conn ID 1 Octet The identifier of the Logical Connection where the error occurred The four least significant bits of the octet SHALL contain the Conn ID as defined in Table 4 The four most significant bits are RFU This Notification is used in error situations when the error can not be notified using an error status in a Response Message This Notifcation SHALL only be used to notify error scenarios related to NFCEE or RF Interface communication using Logical Connections To notify a Logical Connection or RF NFCEE Interface specific error situation the NFCC SHALL send CORE_INTERFACE_ERROR_NTF to the DH with the Status code identifying the error and the affected Conn ID NFC Controller Interface NCI Specificati
100. e DH subject to flow control or the NFCC at any time once a Logical Connection has been created The DH SHALL be capable of supporting any Data Message size sent by the NFCC it is assumed that DH is able to handle any data received either from a local NFCEE or Remote NFC Endpoint At any time the maximum data size the NFCC is able to receive for a Logical Connection is defined by the Max Data Packet Payload Size announced during RF Interface activation in a case of Static RF Connection see Section 7 3 or during Dynamic Logical Connection see Section 4 4 times the number of unused credits given by the NFCC for that connection The maximum payload of a Data Packet is 255 octets The DH SHALL be capable of receiving Data Packets with 255 octet payloads However the NFCC MAY specify a smaller maximum Data Packet payload size on a Logical Connection basis The DH SHALL NOT send Data Packets with a payload length exceeding the Max Data Packet Payload Size that was announced during creation of the corresponding Logical Connection Data Messages can be segmented as described in Section 3 5 3 3 1 Flow Control for Data Packets A credit based Data flow control mechanism is defined for data sent from the DH to the NFCC and MAY be invoked by the NFCC to eliminate buffer overflow conditions It is assumed that the DH has sufficient buffering to handle all data sent from the NFCC so credit based flow control is not supported in that direction
101. e EE GE EE be se ee re Ge RE DS ge deeg 124 10 4 Transparent NFCEE Interface cc esse ee se se ee se ee es se ee ee ee Ge ee de se de ee ee Ge ge de Ge ee ee ee 124 10 4 1 Di do GEUTE EE EE EE EE EE pete 125 11 Transport Mapping esessss iets see eN Ge Ak ke GR Re ie ER Ge ke ek Gee de Re ge AE 126 TEI UART Transport si sr se ease EE ee aie ee ER ie Ge Ee eN 126 112 DE TratisPOEL sees ie es di BE Abe ER adi oe GER ee EE gee eg ee GR Dee Ul ee Se sete 127 11 3 Half Duplex SPI Transport i sssekse erts ess bis geb gee er ge etskee Nee AEE ede edge beg ede 127 11 31 Physical EERS DE EE RD RE DS ER EED tel 127 11 32 Data Tranter Ese itn Ee GEE eee SEEK Shed Maen pees eee 128 12 POSTING RR N OE 134 12 1 Local oopback Mod ieke esse Eer Ego ee be ede eg laces be ee be ge ee Dee EE Ge eo 134 A Exhibit EE EE EE N 135 B COMMON Table ER EER RR RD Oe RD GE N EE ODE ee ee ee ee es 136 Ci REVISION HIStOFV sesse esse GR eN Ne EE Oe N Ge dee eN Ge Ne NG Ge ese SG eN GR Gee eN 145 NFC Controller Interface NCI Specification Page iv Figures Figures Figure NGELSEOpe RE EE GES EO ER PG RE GR GE GE ee ee geed 9 Fisure 2 NCI Component Aves Ee EE ee ek eh Al se Ge Ge N eg ESE AE ies 19 Figure AE Eed EE ME ER ER NE AE EE 20 Figure 4 Control Message Exchange esse ese esse esse es se es se ee ee ee nani GR Ge ee ee ee ee 24 Figure DELER EXc hange 2sx N EE EE EE EE N 26 Figure 6 NCI Gore Packet Format sis sei ees ie
102. e NFC Endpoint or to stop the Discovery process Table 62 Control Messages for RF Interface Deactivation RF_DEACTIVATE_CMD Payload Field s Length Value Description Deactivation Type 1 Octet See Table 63 RF_DEACTIVATE_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 RF_DEACTIVATE_NTF Payload Field s Length Value Description Deactivation Type 1 Octet See Table 63 Deactivation 1 Octet See Table 64 Reason Table 63 Deactivation Types Deactivation Type Description 0x00 Idle Mode 0x01 Sleep Mode 0x02 Sleep_AF Mode 0x03 Discovery 0x04 OxFF RFU NOTE Sleep Mode and Sleep_AF Mode refer to the sleep states of Listen Mode state machine defined in ACTIVITY Depending on the technology Sleep Mode refers to SLEEP_A for NFC A SLEEP_B for NFC B or IDLE for NFC F Sleep_AF refers to the SLEEP_AF state NFC Controller Interface NCI Specification Page 86 RF Discovery Table 64 Deactivation Reasons Deactivation Reason Description 0x00 DH_Request 0x01 Endpoint_Request 0x02 RF Link Loss 0x03 NFC B_Bad_AFI 0x04 OxFF RFU The RF State Machine in Section 5 2 specifies for each state the possible deactivation cases The following rules apply in addition to the definitions in Section 5 2 For the RF_DEACTIVATE_CMD the Deactivation Type values Sleep Mode a
103. e NFCC SHALL receive all relevant Data Packets and combine the Command APDU data from all Data Packets prior to sending the Command APDU to the NFCEE Figure 21 illustrates the mapping between the Data Packet s and the Command APDU to be sent to the NFCEE Data Packet Data Packet Header Payload Data Packet Header Payload eo APDU Data Field Figure 21 Mapping of Command APDU REFS wes ce The following is the structure of the Command APDU in the Data Message and is dependent on the case of the command For Case 1 CLA INSI P1 P2 For Case 2 CLA INSI P1 P2 Le For Case 3 CLA INS P1 P2 Le Data Field For Case 4 CLA INS P1 P2 Le Data Field Le It is the responsibility of the NFCC to correctly map these to the protocol used between the NFCC and the NFCEE In the case that T 0 is being used as this protocol it is the responsibility of the NFCC to manage the 0x6Cxx and 0x61xx status words and these status words are not sent from the NFCC to the DH In these cases the NFCC SHALL transfer the full response 10 1 1 2 Format for Data Messages sent from NFCC to DH The NFCC SHALL retrieve the complete APDU Response from the NFCEE and handle it as a Data Message and send it to the DH in one or more Data Packets If the retrieved APDU Response s from an NFCEE does not fit within a single Data Packet the NFCEE SHALL split the APDU Response across multiple Data Packets Figure 22 illustr
104. e coding refer to Table 97 Depending on the capabilities of NFCC the NFCC MAY reduce the maximum supported bit rate reported to the RF reader NFC Controller Interface NCI Specification Page 66 RF Communication Configuration 6 1 10 Listen NFC DEP Parameters These parameters MAY be configured if listening for NFC A and or NFC F Table 39 Discovery Configuration Parameters for Listen NFC DEP ID Length Value Description LN_WT 1 Octet Waiting Time defined in DIGITAL Default Target value for WT max as defined in DIGITAL LN_ATR_RES_GEN_BYTES 0 n Octets General Bytes in ATR_RES as defined in DIGITAL Default empty no General Bytes SHALL be sent in ATR RES LN_ATR_RES_CONFIG 1 Octet Used to generate the Optional parameters PP in ATR RES See Table 40 Default 0x30 NFCC indicates a maximum payload size of 254 bytes Table 40 Values for LN ATR RES CONFIG Bit Mask Description b7 b6 b5 b4 b3 b2 b1 bO Octet 00 0 0 10 RFU X X Will be set by the NFCC independently of what is configured by DH X X Value for LR as defined in DIGITAL Default 11b NOTE Need to be set to 11b for LLCP NFC Controller Interface NCI Specification Page 67 6 1 11 Common Parameters RF Communication Configuration Table 41 Common Parameters for Discovery Configuration ID TOTAL_DURATION Length
105. e gained in exchange for the loss of bandwidth These are more important as the intended clock rate far exceeds the NCI bandwidth requirement The transport mechanism has the capability to send a maximum sized NCI packet in a single SPI frame The following Data Transfer sections define two modes of operation acknowledged and unacknowledged Which mode is used is determined by the Second Octet In the acknowledged mode a CRC is following the Payload and the receiver sends an positive acknowledge for correctly received payloads or a negative acknowledge for erroneous payloads 11 3 2 1 Data Transfer from DH to NFCC The master SHALL use the DirectWrite command to send data to a slave The master can initiate a data transfer in the following fashion e Master asserts SPI CSN e Slave asserts SPLINT e Master sends 2 byte DirectWrite header followed by 2 byte SPI payload length parameter e Master sends SPI payload e Slave deasserts SPLINT e Master deasserts SPI CSN SPI_CSN may be toggled deasserted and asserted in every 8 bit transfer If the Second Octet is equal to 0x00 the DirectWrite header is sent as shown in the table below NFC Controller Interface NCI Specification Page 128 Table 90 SPI Header Coding DH to NFCC without CRC Transport Mappings First Octet Second Octet Third Octet Fourth Octet Master 0x01 0x00 MSB Payload LSB Payload Length Length Slave 0x00 0x00 0x00 0x00 The Paylo
106. e transmitted in NCI Control Packets and NCI supports segmentation of Control Messages into multiple Packets The NCI Core defines a basic set of Control Messages e g for setting and retrieving of NFCC configuration parameters Additional Control Messages can be defined by NCI Modules 2 2 2 Data Messages Data Messages are used to transport data to either a Remote NFC Endpoint named RF Communication in NCI or to an NFCEE named NFCEE Communication NCI defines Data Packets enabling the segmentation of Data Messages into multiple Packets Data Messages can only be exchanged in the context of a Logical Connection As a result a Logical Connection must be established before any Data Messages can be sent One Logical Connection the Static RF Connection is always established during initialization of NCI The Static RF Connection is dedicated to be used for RF Communication Additional Logical Connections can be created for RF and or NFCEE Communication Logical Connections provide flow control for Data Messages in the direction from DH to NFCC NFC Controller Interface NCI Specification Page 20 NCI Architecture 2 2 3 Interfaces An NCI Module may contain one Interface An Interface defines how a DH can communicate via NCI with a Remote NFC Endpoint or NFCEE Each Interface is defined to support specific protocols and can only be used for those protocols the majority of Interfaces support exactly one protocol NCI defines two type
107. eader Coding NFCC to DH with CRC sesse esse se ss see ee ee Ge Re ee ee ee 131 Table 94 Status Ok EE EK RE OR EE N N 136 Table 95 RE Technologies is ae ig Se oe SE RS Se ti Re EE ge doch DEE etal EO ee Ke Se EE se eed 137 Table 96 RF Technology and Mode esse sketse eed ese be ee GE bee R EEE doek DE GR ee beken ek kg ede 137 able 97 Bit Rates ES SE GE Ee EK EE Ee RS bettie Be RE Ee ee ies ee ede 138 Table 98 RE Protooolsti ie ER ee EE ee EEE ee EE ge ee ge Ee ee ents 138 Table 99 RF Intertaces EE AR RE OR EO OE E OE EN 139 Table 100 NFCEE Protocols Interfaces iese esse esse ee se ee se ee sede see eke ee ee ee ee ee Ge ee ee ee Ge ee Ged 139 Table 101 Configuration Parameter Tags 00 esse es see see se GR SA GR ee ee ee ee ee ee Ge Ge 140 Table 102 GID and OID Definition sesse ee se Ge GR Ge ee ee ee ee ee ee Ge 143 Table 103 Revision HISLOTVE iss sers ek ee ee ee sege ig er Ge gen beg babe koe beg este gee Ek Sober AS nege ee de 145 NFC Controller Interface NCI Specification Page viii 1 Introduction Introduction This document specifies a communication protocol called the NFC Controller Interface NCI between an NFC Controller NFCC and a Device Host DH 1 1 Objectives NCI is defined to meet the following requirements NCI is defined to be independent of a specific transport layer a physical connection and any associated link protocol Transport Mappings define the details on how to run NCI on top
108. ees sede DEE se gese RS Ge ks ek sege ke Ee Dee ee Se be ge be Fee 28 Figure 7 Control Packet Stricture ss ier ee ESE EE REEL eae eee emi ie 29 Figure 8 Data Packet Structur ir EE RE dees oe DEE Ese De Ge eek eg ee Ge Ee ed ee 30 Figute 9 REF Interface Architecture ss it aes SE e Ee see egg ee E Ee ee el iis 47 Figure 10 RF Communication State Machine sesse esse es see se ee Ge Ge GR RA GR AR ee ee ee 49 Figure 11 Format for Frame RF Interface NFC A for Transmission sesse esse sees se see se ee ee 93 Figure 12 Format for Frame RF Interface NFC B for TransmisSiON sesse esse sees se see se ee ee 94 Figure 13 Format for Frame RF Interface NFC F for Transmission sesse esse se es se se ee se ee ee 94 Figure 14 Format for Frame RF Interface NFC A for Reception ses see see se se se ee ee 95 Figure 15 Format for Frame RF Interface NFC B for Reception sees see see se ee ee ee ee 95 Figure 16 Format for Frame RF Interface NFC F for Reception cece see se se se ee ee 95 Figure 17 Format for ISO DEP RF Interface for TransmisStON esse ese esse esse esse es se es ee ee Ge 104 Figure 18 Format for ISO DEP RF Interface for Reception esse esse ese ese ese es ee ee ee ee 104 Figure 19 Format for NFC DEP RF Interface for TransmiSSION esse esse esse esse esse es se es se ee ee Ge 109 Figure 20 Format for NFC DEP RF Interface for Reception see ese esse esse es se es se ee ee ee Ge 110 Figure 21 Mapping of
109. er is to be included This information is expressed by an index range e g 1 10 The upper bound of this range can be a variable defined by another parameter The parameter instances SHALL follow each other sequentially The corresponding parameter length indicates the length of a single parameter instance not the length of the complete parameter set NFC Controller Interface NCI Specification Page 18 NCI Architecture 2 NCI Architecture This section outlines some of the basic concepts used in NCI It is an informal introduction to the documentation and normative statements later in this document 2 1 Components NCI can be split into the following logical components NCI Core The NCI Core defines the basic functionality of the communication between a Device Host DH and an NFC Controller NFCC This enables Control Message Command Response and Notification and Data Message exchange between an NFCC and a DH Transport Mappings Transport Mappings define how the NCI messaging is mapped to an underlying NCI Transport which is a physical connection and optional associated protocol between the DH and the NFCC Each Transport Mapping is associated with a specific NCI Transport NCI modules NCI modules build on top of the functionality provided by the NCI Core Each module provides a well defined functionality to the DH NCI modules provide the functionality to configure the NFCC and to discover and communicate with
110. ese are e AID based routing entries e Protocol based routing entries e Technology based routing entries AID based routing is only possible if the NFCC terminates the ISO DEP protocol and understands at least the SELECT command defined in ISO IEC_7816 4 The DH knows if the NFCC supports this from the NFCC capabilities returned in the CORE_INIT_RSP NFC Controller Interface NCI Specification Page 70 RF Communication Configuration Each AID SHALL be unique in the NFCC s routing table For each protocol value except for the T3T protocol and proprietary protocols there SHALL be at most one protocol based route be configured for each supported Power State Switched On Switched Off and Battery Off For T3T protocol as the Remote NFC Endpoint can manage responses from multiple NFCEEs the DH MAY configure more than one NFCEE ID for each supported Power State In this case data received from the Remote NFC Endpoint will be forwarded to all configured NFCEE IDs if the NFCC cannot find the route for it The corresponding rules for routing entries for proprietary protocols are out of scope of this specification NOTE Transitions between Power States are implementation specific issues thus out of scope of this specification For each technology there SHALL be at most one technology based route configured for each supported Power State The order of searching through the routing table SHALL be 1 AID based 2 Protocol based and
111. et by RF Technology and Mode in REF DISCOVER CMD They MAY be changed from defaults by using the CORE SET CONFIG CMD before moving to state RFST DISCOVERY e Table 23 Discovery Configuration Parameters for Poll A e Table 24 Discovery Configuration Parameters for Poll B e Table 27 Discovery Configuration Parameters for ISO DEP 8 3 2 2 Discovery and Interface Activation To enable Poll Mode for ISO DEP the DH sends the RF_DISCOVER_CMD to the NFCC containing configurations with RF Technology and Mode values of NFC_A_PASSIVE_POLL_MODE and or NFC_B_PASSTIVE_POLL_MODE When the NFCC is ready to exchange data that is after receiving a response to the protocol activation command from the Remote NFC Endpoint it sends the RF_INTF_ACTIVATED NTEFE to the DH to indicate that this Interface has been activated to be used with the specified Remote NFC Endpoint Detailed ISO DEP RF Interface activation handling in the NFCC For NFC A Following the anticollision sequence if the Remote NFC Endpoint supports ISO DEP Protocol the NFCC sends the RATS Command to the Remote NFC Endpoint and after receiving the RATS response the NFCC SHALL send the RF_INTF_ACTIVATED_NTF to the DH to indicate a Remote NFC Endpoint based on ISO DEP has been activated For NFC A the RF_INTF_ACTIVATED NTF SHALL include the Activation Parameters defined in Table 76 Table 76 Activation Parameters for NFC A ISO DEP Poll Mode Parameter Length Descr
112. etary use OxFF RFU NFC Controller Interface NCI Specification Common Tables Page 139 Table 101 Configuration Parameter Tags Parameter Name Tag Common Discovery Parameters TOTAL DURATION 0x00 CON_DEVICES_LIMIT 0x01 RFU 0x02 0x07 Poll Mode NFC A Discovery Parame ters PA_BAIL_OUT 0x08 RFU 0x09 0x0F Poll Mode NFC B Discovery Parameters PB_AFI 0x10 PB_BAIL_OUT 0x11 PB_ATTRIB_PARAM1 0x12 PB_SENSB_REQ_PARAM 0x13 RFU 0x14 0x17 Poll Mode NFC F Discovery Parameters PF_BIT_RATE 0x18 PF_RC_CODE 0x19 RFU 0x1A 0x1F Poll Mode ISO DEP Discovery Parameters PB_H_INFO 0x20 PI_BIT_RATE 0x21 PA_ADV_FEAT 0x22 RFU 0x23 0x27 Poll Mode NFC DEP Discovery Parameters PN_NFC_DEP_SPEED 0x28 PN_ATR_REQ_GEN_BYTES 0x29 PN_ATR_REQ_CONFIG 0x2A RFU 0x2B 0x2F Listen Mode NFC A Discovery Parameters LA_BIT_FRAME_SDD 0x30 LA_PLATFORM_CONFIG 0x31 LA_SEL_INFO 0x32 NFC Controller Interface NCD Specification Common Tables Page 140 Common Tables Parameter Name Tag LA_NFCID1 0x33 RFU 0x34 0x37 Listen Mode NFC B Discovery Parameters LB_SENSB_INFO 0x38 LB_NFCIDO 0x39 LB_APPLICATION_DATA Ox3A LB_SFGI 0x3B LB_ADC_FO 0x3C RFU 0x3D 0x3F Listen Mode NFC F Discovery Parameters LF_T3T_IDENTIFIERS_1 0x40 LF_T3T_IDENTIFIE
113. eters for Listen B Except parameter LB_SFGI which SHALL be configured by the NFCC when using this Interface NFC Controller Interface NCI Specification Page 106 RF Interfaces e Table 38 Discovery Configuration Parameters for Listen ISO DEP To use this Interface at least one of the Parameters LA_SEL_INFO and LB_SENSB_INFO SHALL be configured to indicate ISO DEP support In the case of Type 4 Tag Emulation being hosted on the DH the DH sends the CORE_SET_CONFIG_CMD to configure the Listen A Parameters and or the Listen B Parameters defined in Table 30 and Table 32 and to set the Selected Interface to ISO DEP The DH MAY send the RF_SET_LISTEN_MODE_ROUTING_CMD to set the routing information on the NFCC which will route the received data to the specific NFCEEs and in this case to the DH 8 3 3 2 Discovery and Interface Activation To enable Listen Mode for ISO DEP the DH sends the RF_DISCOVER_CMD to the NFCC containing configurations with RF Technology and Mode values of NFC_A_PASSIVE_LISTEN_MODE and or NFC_B_PASSIVE_LISTEN_MODE When the NFCC is ready to exchange data with the DH that is after receiving protocol activation command from the Remote NFC Endpoint it sends the RF INTE ACTIVATED NTF to the DH to indicate that this Interface has been activated to be used with the specified Remote NFC Endpoint Detailed ISO DEP RF Interface activation handling in the NFCC For NFC A Following the anticollision sequence the NF
114. field indicates the number of Payload octets present The Payload Length field is an 8 bit field containing a value from 0 to 255 NFC Controller Interface NCI Specification Page 30 NCI Core Framework 3 5 Segmentation and Reassembly The Segmentation and Reassembly functionality SHALL be supported by both the DH and the NFCC Segmentation and Reassembly of Messages SHALL be performed independently for Control Packets and Data Packets of each Logical Connection Any NCI Transport Mapping is allowed to define a fixed Maximum Transmission Unit MTU size in octets If such a Mapping is defined and used then if either DH or NFCC needs to transmit a Message either Control or Data Message that would generate a Packet including Packet Header larger than the MTU the Segmentation and Reassembly SAR feature SHALL be used on the Message The following rules apply to segmenting Control Messages e For each segment of a Control Message the header of the Control Packet SHALL contain the same MT GID and OID values e From DH to NFCC The Segmentation and Reassembly feature SHALL be used when sending a Command Message from the DH to the NFCC that would generate a Control Packet with a payload larger than the Max Control Packet Payload Size reported by the NFCC at initialization see Section 4 2 Each segment of a Command Message except for the last SHALL contain a payload with the length of Max Control Packet Payload Size e F
115. figuration esse esse esse esse es se ee ee ee ee ed 110 8 4 3 Poll side NFC DEP RF Interface Management iese ese esse ee se se ee ee ee ee eke de 111 8 4 4 Listen side NFC DEP RF Interface Management iese es sees se ee se ee ee ee ee ee 112 9 NFCEE Discovery and Mode Set uses esse ee ee EE ER EER Gee RR RR RE RE EER Ee ee ee 115 ME ie oo N ELE EE OE EE 115 92 NEEEE Discovery ie te ese ese eNE SE Ed De ee teed dines E ENGER GED SIR Ge Re De Deeg ae deep ee dis 115 92 1 HCI Network Specific Handling eee esse esse es se es ee Ge Ge GR GR GR ee ee 118 9 3 NFCEE Enabling and Disabling ee esse ee se ee se ee ee ee ee ee ede ee ee ee se ee se ee se ee ee se ee se 119 9 3 1 HCI Network Specific Handling esse esse esse ee se ee se ee Ge ed Gee ee ee ee ee 120 10 NFCEE lntertaces es ii ses oe N oe soe oe eeu dee Ee oe Nee se Gegee Ge 121 EED vy pidO del d od ia SA AE MR OE HR EE HE ER ENE 121 MEEN Pi do OER IE OK EE RE N EE N 121 10 1 2 Failures during Data Exchange esse esse esse esse ee see Ge Ge GR SA Se ee ee ee ee 123 10 2 HELAccess NFCEE Interfac ie esse Ede s eN sl ge Pe GES ese De Deed se Ged len ss Ge e ee Ged 123 10 2 1 NFCEE Interface Activation and DeactVaHON sesse ses see ese ese ese ese ee 123 10 22 Data Exchange is et ee oc bee ee RE ed coe ge ee oe Ee Ee Ge ee ee ee 124 10 3 Type 3 Tag Command Set NFCEE Interface oe see ese ese esse ee se es se ee ee ee Ge 124 10 3 1 Data Exchang ss EDS se e
116. formed On completion of the reset procedure the NFCC SHALL send a CORE_RESET_RSP informing the DH that the NFCC has been reset The Status SHALL be STATUS_OK The CORE_RESET_CMD allows defining different reset types using the Reset Type parameter The Configuration Status parameters in CORE_RESET_RSP and CORE RESET NTF inform the DH about the status of the NCI RF configuration after the reset NOTE This allows different NFCC implementations Some NFCCs may have persistent memory for the NCI RF Configuration and therefore do not require the DH to re configure after a reset Others may not have persistent memory for the NCI RF Configuration The DH can force a reset of the configuration by using the Reset Type parameter The DH knows based on the Configuration Status value whether it needs to configure the NFCC after the reset or not If Reset Type has been set to 0x00 the Configuration Status in CORE_RESET_RSP SHALL be set to either 0x00 or 0x01 If Reset Type has been set to 0x01 the Configuration Status in CORE_RESET_RSP SHALL be set to 0x01 For all Configuration Status values all data in Buffers used for NCI Data and Control Packet exchange SHALL be deleted and the Buffer SHALL be freed In this context NCI RF Configuration SHALL comprise e The Listen Mode Routing Table see Section 6 3 e All Configuration Parameters see Table 101 for a list of Configuration Parameters e RF Interface Mapping configuration see Section 6 2
117. from RF to the DH The NFCC SHALL transfer the Payload of received I Blocks to the DH The Payload of an ISO DEP I Block not indicating chaining or the combined Payload of a chained series of ISO DEP I Blocks SHALL be sent as one Data Message The last byte of the Payload of an I Block not indicating chaining received by the NFCC from the Remote NFC Endpoint SHALL be the last octet of the Data Packet with Packet Boundary Flag set to Ob Figure 18 illustrates the mapping between the NCI Data Message format and the ISO DEP I blocks for the ISO DEP RF Interface NOTE This figure shows the case where NCI Segmentation and Reassembly feature is not used However ISO DEP chaining is used where one Data Message is received by multiple I Blocks from the Remote NFC Endpoint eae O DEP sp Payload FO d ww zy EE CD INF oe lose Se bo o Med er Ge eo o od o eo Data Packet EE Packet Header Payload Figure 18 Format for ISO DEP RF Interface for Reception 8 3 2 Poll side ISO DEP RF Interface Management The Poll side ISO DEP RF Interface MAY be used for Reader Writer Mode when the Remote NFC Endpoint supports ISO DEP based on NFC A or NFC B NFC Controller Interface NCI Specification Page 104 RF Interfaces 8 3 2 1 Discovery Configuration The Discovery configuration parameters defined in the following tables are relevant depending on the NFC technology used in Discovery NFC A or NFC B as s
118. g all data from buffers related to the closed Logical Connection setting NFCC_Credits_Avail to initial value and releasing the Conn ID for later use NOTE The DH should make sure that the last Data Message has arrived at the NFCC before sending the CORE CONN CLOSE CMD The NFCC should attempt to send any pending data to a Remote NFC Endpoint or NFCEE even though the corresponding connection is being closed NFC Controller Interface NCI Specification Page 44 NCI Core Control Messages 4 4 4 Connection Credit Management These Control Messages are used to manage the credits on a Logical Connection that uses credit based flow control Table 17 Control Messages for Connection Credit Management CORE CONN CREDITS NTF Payload Field s Length Value Description Number of Entries 1 Octet Number of Entry fields to follow n Entry 1 n 2 Octet Conn ID 1 Octet The identifier of the Logical Connection for which credits are given The four least significant bits of the octet SHALL contain the Conn ID as defined in Table 4 The four most significant bits are RFU Credits 1 Octet The number of credits given For each Logical Connection the DH stores the initial credits value received as part of the connection setup Initial Number of Credits parameter in a variable namely NFCC Credits Avail which is used to track the number of Data Packets that can be sent to the NFCC NOTE If there are not enough
119. g state of the Listen Mode state machine defined in ACTIVITY e SLEEP AF when NFC A or NFC F is the technology currently in use If the currently used technology is NFC B the NFCC SHALL respond with a RF_DEACTIVATE_RSP with Status set to STATUS_REJECTED not send a RF DEACTIVATE NTF and keep the Frame RF Interface activated e RF_DEACTIVATE_NTF Sleep Mode Endpoint Request After receiving a SLP_REQ or sending a SLPB_RES the NFCC SHALL send the DEACTIVATE_NTF When using this RF Interface the following deactivation cases described in Section 5 2 for RFST_LISTEN_ACTIVE SHALL NOT be allowed e RF _DEACTIVATE_NTF Discovery Endpoint_Request e RF DEACTIVATE NTF Sleep AF Mode Endpoint Request 8 2 4 4 Failures during Data Exchange Even if there are any failures during data exchange the NFCC SHALL NOT send any CORE_INTERFACE_ERROR_NTF to the DH The DH itself identifies TRANSMISSION ERROR and PROTOCOL ERROR in communication with the Remote NFC Endpoint from the Data in the Data Packet The DH MAY deactivate the RF Interface when it identifies such errors 8 3 ISO DEP RF Interface Both the Poll side and Listen side ISO DEP RF Interface provides access to the Payload of the ISO DEP I Blocks exchanged between the NFC Forum Device and a Remote NFC Endpoint Using this interface the DH need not have any knowledge about ISO DEP block format however any higher layer protocol e g based on 7816 APDU exchange must be handled on the DH
120. hat is used when the NFCC in state RFST DISCOVERY can determine that the RF communication has to be routed to an NFCEE One example for such a case is if an NFCEE is directly coupled to the RF e g when the NFC Wired Interface see SO IEC_28361 is used The NFCEE Direct RF Interface does not enable NCI Data Message exchange between the DH and the NFCC and as a consequence no communication between the DH and the Remote NFC Endpoint Therefore this RF Interface does not define a Data Mapping or Discovery Configuration The NFCEE Direct RF Interface can not be mapped to an RF Protocol The following sections apply for Poll Mode and Listen Mode 8 1 1 Discovery and Interface Activation When the DH has enabled an NFCEE is in state RFST_DISOVERY and determines that the RF communication has to be routed to an NFCEE it sends an RF INTE ACTIVATED NTF to the DH to indicate that this Interface has been activated 8 1 2 Interface Deactivation Using this interface deactivation cases with Deactivation Types Sleep Mode or Sleep_AF Mode SHALL NOT be allowed 8 2 Frame RF Interface Both the Poll side and Listen side Frame RF Interfaces provide access to the Payload of the RF frames exchanged between the NFC Forum device and a Remote NFC Endpoint The RF frame formats are technology dependent Any higher layer protocols for example ISO DEP or NFC DEP must be handled on the DH In addition when using Frame RF Interface the activation
121. he HCI Access Interface 10 2 1 NFCEE Interface Activation and Deactivation If the DH has received a NFCEE_DISCOVER_NTF indicating HCI Access see Table 100 in the Supported NFCEE Protocol parameter the DH MAY activate this NFCEE Interface by opening a Logical Connection using the NFCEE ID specified in the NFCEE_DISCOVER_NTEFE and using HCI Access as the protocol When the HCI Access NFCEE Interface is activated and if the HCI Network is already enabled then the Host Controller SHALL send EVT HOT PLUG as described within ETSI 102622 to the hosts within the HCI Network to make them aware that the Terminal Host is available When the HCI Access NFCEE Interface is deactivated by closing the Logical Connection to the HCI Access NFCEE Interface the hosts within the HCI Network SHALL be made aware by EVT_HOT_PLUG that the Terminal Host has disappeared NFC Controller Interface NCI Specification Page 123 NFCEE Interfaces 10 2 2 Data Exchange The payload of the Data Packets sent on the Logical Connection SHALL be valid HCP packets as defined within ETSI_102622 Each Data Packet SHALL contain a single HCP packet NCI Segmentation and Reassembly SHALL NOT be applied to Data Messages in either direction The HCI fragmentation mechanism is used if required 10 3 Type 3 Tag Command Set NFCEE Interface The Type 3 Tag Command Interface is used by the DH to communicate with NFCEEs connected to the NFCC by exchanging Type 3 Tag Co
122. he value of the RF Specific Parameters Octets Technology and Mode See Table 54 for NFC A Poll Mode See Table 56 for NFC B Poll Mode See Table 58 for NFC F Poll Mode Proprietary parameters if the value of RF Technology and Mode is reserved for a proprietary technology Notification Type 1 Octet 0 Last Notification 1 Last Notification due to NFCC reaching it s resource limit 2 More Notification to follow 3 255 RFU Table 53 RF Discovery ID Value Description 0 RFU 1 254 Dynamically assigned by the NFCC 255 RFU The DH requests that the NFCC starts Discovery activity by sending the RF_DISCOVER_CMD The parameters RF Technology and Mode and Discovery Frequency are provided by the DH to configure the manner in which the NFCC performs the RF Discovery Process If the parameters are acceptable for the NFCC the NFCC SHALL return the RF_DISCOVER_RSP with a Status of STATUS_OK and will start the RF Discovery Process accordingly In the case where the RF Communication State Machine is not in the state RFST_IDLE the NFCC SHALL return RF_DISCOVER_RSP with a Status of DISCOVERY_ALREADY_STARTED In this error case the current ongoing RF Discovery Process SHALL continue without any changes NFC Controller Interface NCI Specification Page 78 RF Discovery In Poll Mode if there are multiple Remote NFC Endpoints detected or if a Remote NEC Endpoint supports multiple RF Protocols
123. his allows the DH to retrieve the current RF field status If an operating field from a Remote NFC Endpoint has been detected bit 0 of RF Field Status is set to 1b and if not specified differently by the used Transport Mapping the NFCC SHALL send RF_FIELD_INFO_NTF Transport Mappings MAY restrict the sending of RF FIELD INFO NTF if the transport requires time to become operational after detecting an external field and if the DH can use the start of this transport activation as an indication of the presence of an external field Transport Mappings SHALL NOT restrict the sending of RF_FIELD_INFO_NTF for any other reason If the loss of an operating field from a Remote NFC Endpoint has been detected bit 0 of RF Field Status is set to Ob the NFCC SHALL send RF_FIELD_INFO_NTF If RF_FIELD_INFO is set to 0x00 the NFCC SHALL NOT send RF_FIELD_INFO_NTF notifications NFC Controller Interface NCI Specification Page 55 RF Communication Configuration 6 RF Communication Configuration Before starting the actual RF Discovery Process by moving to the RFST_DISCOVERY state described in Section 5 2 the DH SHALL have first configured e Any non default Poll Mode and Listen Mode parameters e The mapping between protocols and interfaces e Any CE routing that is needed The above steps need to be followed before the first time the RF Discovery Process is started and after that only when something changes They are described in detail in the foll
124. hnology and Mode for the collection of the RF Technology Specific Parameters below See Table 96 Max Data Packet 1 Octet Max Data Packet Payload Size the NFCC can receive for the Payload Size Static RF Connection A number from 1 255 Initial Number of 1 Octet Initial Number of Credits given by the NFCC to the DH for Credits the Static RF Connection as defined in Table 14 Length of RF 1 Octet The length of RF Technology Specific Parameters field to Technology Specific follow Parameters RF Technology Specific 0 n One of the below tables depending on the value of the RF Parameters Octets Technology and Mode Depends on RF Technology and Mode See Table 54 for NFC A Poll Mode See Table 55 for NFC A Listen Mode See Table 56 for NFC B Poll Mode See Table 57 for NFC B Listen Mode See Table 58 for NFC F Poll Mode See Table 59 for NFC F Listen Mode Proprietary parameters if the value of RF Technology and Mode is reserved for a proprietary technology NFC Controller Interface NCI Specification Page 83 RF Discovery RF INTF ACTIVATED NTF Payload Field s Length Value Description Data Exchange RF 1 Octet RF Technology and Mode that will be used for future Data Technology and Mode Exchange See Table 96 Data Exchange 1 Octet Bit rate that will be used for future Data Exchange in the Transmit Bit Rate transmit direction For a polling device this is the bit rate from poll to
125. ields to follow n Configurations n can be 0 if the RF Discovery is enabled for NFCEE s only e g in response to a RF_NFCEE_DISCOVERY_REQ NTF and an NFCEE s providing configuration settings directly to the NFCC If n is 0 this Command contains no Configuration fields Configuration 2 Octets RF 1 Octet RF Technology and Mode of the local 0 n Technology device See Table 96 and Mode Discovery 1 Octet 0x00 RFU EE aaa 0x01 RF Technology and Mode will be executed in every discovery period 0x02 These values are allowed for Poll OXOA Mode RF Technology and Mode values This value specifies how often the Poll period of the specific RF Technology will be executed For example a value of 10 indicates that this Polling will be executed in every 10 discovery period OxOB RFU OxFF RF_DISCOVER_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 NFC Controller Interface NCI Specification Page 77 RF Discovery RF_DISCOVER_NTF Payload Field s Length Value Description RF Discovery ID 1 Octet See Table 53 RF Protocol 1 Octet RF Protocol supported by the Remote NFC Endpoint See Table 98 RF Technology and 1 Octet RF Technology and Mode of the local device See Table 96 Mode Length of RF 1 Octet The length of RF Technology Specific Parameters field to Technology Specific follow Parameters RF Technology O n One of the below tables depending on t
126. ion by the NFCC Unless otherwise specified the NFCC SHALL send a Response with a Status value of STATUS_SEMANTIC_ERROR and no additional fields The NFCC SHALL respond to an unknown Command unknown GID or OID with a Response having the same GID and OID as the Command followed by a Status field with the value of STATUS_SYNTAX_ERROR and no additional fields The DH SHALL ignore any unknown Response or Notification unknown GID or OID If the NFCC cannot perform the action requested in a valid Command the NFCC SHALL inform the DH using a Response with one of the Status field values defined in Table 94 Allowed Status values are specified for each Response Reasons for not being able to perform a Command could be buffer overflow limited processing power limited resources etc If a Response for a corresponding Command is not received by the DH within the time set for T Heads the DH MAY resend the Command or send another Command NFC Controller Interface NCI Specification Page 25 NCI Core Framework 3 3 NCI Data Messages Data Messages are used to exchange data over Logical Connections between a DH and NFCC target NFCEE or Remote NFC Endpoint See Figure 5 DH NFCC Data Data Data Message Exchange Figure 5 Data Exchange Data Messages are sent over the NCI Transport as payloads of Data Packets A Data Packet payload contains a complete or a segment of a Data Message Data Messages can be sent by either th
127. iption RATS Response Length 1 Octet Length of RATS Response Parameter n RATS Response n Octets All Bytes of the RATS Response as defined in DIGITAL starting from and including Byte 2 For NFC B Following the anticollision sequence if the Remote NFC Endpoint supports ISO DEP Protocol the NFCC sends the ATTRIB command to the Remote NFC Endpoint and following receipt of the ATTRIB response the NFCC SHALL send the RF_INTF_ACTIVATED_NTF to the DH to indicate a Remote NFC Endpoint based on ISO DEP has been activated For NFC B the RF_INTF_ACTIVATED_NTF SHALL include the Activation Parameters defined in Table 77 NFC Controller Interface NCI Specification Page 105 RF Interfaces Table 77 Activation Parameters for NFC B ISO DEP Poll Mode Parameter Length Description ATTRIB Response Length 1 Octet Length of ATTRIB Response Parameter n ATTRIB Response n Octets ATTRIB Response as defined in DIGITAL 8 3 2 3 Interface Deactivation Additional rules apply for the following deactivation cases described in Section 5 2 for RFST_POLL_ACTIVE e RF_DEACTIVATE_CMD RSP NTF dle Mode RF_DEACTIVATE_CMD RSP NTF Discovery RF_DEACTIVATE_CMD RSP NTF Sleep Mode Before sending the RF DEACTIVATE NTF to the DH the NFCC SHALL de activate the Remote NFC Endpoint according to the De activation rules for ISO DEP specified in DIGITAL When using this RF Interface the following deactivation cases described in Secti
128. ircuit cards Proximity cards Part 3 Initialization and anticollision ISO TEC_14443 3 2001 Amd 1 Identification cards Contactless integrated circuit s cards Proximity cards Part 3 Initialization and Anti collision 1 February 2001 with Amendment 1 Bit rates of fc 64 fc 32 and fc 16 15 June 2005 Amendment 3 Handling of reserved fields and values 22 March 2006 and Corrigendum 1 Amendment 1 Corrigendum 29 August 2006 ISO IEC 14443 4 2008 Identification cards Contactless integrated circuit cards Proximity cards Part 4 Transmission protocol ISO IEC NFC Controller Interface NCI Specification Page 10 Introduction ETSI 102622 ETSI TS 102 622 Smart Cards UICC Contactless Front end CLF Interface Host Controller Interface HCI Release 10 2011 ETSI ISO IEC_78 16 3 ISO IEC 7816 3 Identification cards Integrated circuit cards Part 3 Cards with contacts Electrical interface and transmission protocols ISO IEC ISO IEC_78 16 4 ISO IEC 7816 4 Identification cards Integrated circuit cards Organization security and commands for interchange 2005 ISO IEC ISO IEC_28361 ISO IEC 28361 Information technology Telecommunications and information exchange between systems Near Field Communication Wired Interface NFC WI 2007 ISO IEC MT PC bus specification and user manual Rev 03 June 2007 NXP LLCP NFC Logical Link Control Protocol LLCP Techni
129. is document are intended to mean the same as Command Message Response Message and Notification Message Cyclic Redundancy Check CRC A checksum appended within the data segment before transmission and verified afterward by the recipient to detect Transmission Errors Data Message A message containing a data carried over a Logical Connection Destination Type Identifies an entity NFCC NFCEE or Remote NFC Endpoint for which a Dynamic Logical Connection is intended Device Host DH An Execution Environment responsible for the overall management of the NFC Forum Device and any peripherals This includes the management e g initialization configuration power management etc of the NFC Controller peripheral DH NFCEE An environment residing on or connected to the DH where NFC applications are executed There is logically only one DH NFCEE but it may be composed of more than one environment for example applications on the DH and applications on a peripheral connected to the DH The manner in which the DH manages the DH NFCEE is implementation specific NFC Controller Interface NCI Specification Page 14 Introduction Dynamic Logical Connection A Logical Connection that is created and closed dynamically as needed HCI Network A Network as described within ETSI 102622 consisting of a host controller and one or more hosts ISO DEP Protocol Half duplex block transmission protocol defined in I
130. is section describes the supported NFCEE Interfaces Unless defined otherwise all NFCEE Interfaces are optional The DH learns which NFCEE Interfaces are supported by an NFCEE during NFCEE Discovery Process see Section 9 1 The Supported NFCEE Protocol parameter field s in NFCEE_DISCOVER_NTF identifies the supported NFCEE Protocol s The DH SHALL only initiate NFCEE Interface activation for an NFCEE Protocol that was reported during the NFCEE Discovery Process NFCEE Interface activation and deactivation is performed automatically when creating or closing a Logical Connection to an NFCEE see Section 4 4 There are no specific Control Messages for NFCEE Interface activation or deactivation The combination of NFCEE ID and NFCEE Protocol as reported in the NFCEE_DISCOVER_NTF used during connection creation uniquely identifies a specific NFCEE Interface to be activated In case of an error during NFCEE Interface activation the NFCC SHALL set the Status in the CORE_CONN_CREATE_RSP to NFCEE_INTERFACE_ACTIVATION_FAILED There MAY be multiple simultaneous active NFCEE Interfaces but there SHALL be only one active NFCEE Interface for each NFCEE This means that for each NFCEE only one Logical Connection is allowed between the DH and one NFCEE An NECEE Interface SHALL be deactivated when the corresponding Logical Connection is closed The DH MAY initiate connection closure by using the Conn ID used for the NFCEE Interface see de
131. l Bytes SHALL be sent in ATR REO PN ATR REO CONFIG 1 Octet Configuration to be used in the Optional Parameters PP within ATR REO See Table 29 Default 0x30 NFC Controller Interface NCI Specification Page 60 RF Communication Configuration Table 29 Values for PN ATR REG CONFIG Bit Mask Description b7 b6 b5 b4 b3 b2 b1 b0 Octet0 jO 0 0 0 0 REU X If set to 1b the DID MAY be used otherwise DID SHALL NOT be used NOTE Needs to be 0b for LLCP X IX Value for LR as defined in DIGITAL NOTE Needs to be always set to 11b for LLCP 6 1 6 Listen A Parameters Table 30 Discovery Configuration Parameters for Listen A ID Length Description LA_BIT_FRAME SDD 1 Octet Bit Frame SDD value to be sent in Byte 1 of SENS_RES This is a 5 bit value that SHALL be contained in the 5 least significant bits of the octet Default NFCC decides the NFCC SHALL set the value as defined in DIGITAL LA PLATFORM CONFIG 1 Octet Platform Configuration value to be sent in Byte 2 of SENS RES This is a 4 bit value that SHALL be contained in the 4 least significant bits of the octet Default NFCC decides the NFCC SHALL set the value as defined in DIGITAL LA_SEL_INFO 1 Octet This value is used to generate SEL_RES according DIGITAL Bits set in this field SHALL be set in the SEL_RES sent by the NFCC See Table 31 Default
132. ld coding is out of scope of this document and can be defined by each NFCEE manufacturer 0x01 ATR Bytes ATR information contains the transmission parameters such as T 0 and T 1 which are supported by the NFCEE It also carries all the necessary information that MAY be required by the DH such as Data transmission rate Mask Version number NFCEE Serial number NFCEE hardware parameters etc The format of ATR is defined in SO IEC_7816 3 specification 0x02 9 169 T3T Command Set Interface Supplementary Information The T3T Command Set Interface Supplementary Information MAY be present when one of the Supported NFCEE Protocol parameters contains the value Type 3 Tag Command Set It SHALL NOT be present otherwise If the T3T Command Set Interface Supplementary Information is present it SHALL contain the PMm and Number of Entries field as outlined in Table 87 If the value for Number of Entries is larger than 0 it SHALL be followed by the corresponding number of Entries Each Entry SHALL consist of the System Code and Idm fields as defined in Table 87 0x03 0x9F RFU 0xA0 0xFF For proprietary use Table 87 Value Field for T3T Command Set Interface Supplementary Information Payload Field s Length Value Description PMm 8 Octets PMn as defined in T3TOP Number of Entries 1 Octets The number of Entries to follow n An entry System Code n consists of System Code and Idm parame
133. mation Configuration Parameter iese esse esse ee se se ee Sk Ge ee ee ee ee 55 Table 23 Discovery Configuration Parameters for Poll Ao eee sees see see se ee ee Ge ee ee ee ee 56 Table 24 Discovery Configuration Parameters for Poll Bow esse ses se ee ek Ge ee ee ee ee 57 Table 25 Values for PB SENSB REO PARAM ese esse esse ee se ee se ee ee ee ee ee ede eke ese ee ee ee ee 58 Table 26 Discovery Configuration Parameters for Poll Fu sees esse ee sees ese ee ee ee ee ee ee ee 58 Table 27 Discovery Configuration Parameters for ISO DEP iese eee sees see see ee ee ee ee ee 59 Table 28 Discovery Configuration Parameters for Poll NEC DEP ees see see esse ese esse es se ese 60 Table 29 Values for PN ATR REO CONFIG roccie se de Ge de a ee ek Ge ee ee ee ee 61 Table 30 Discovery Configuration Parameters for Listen Au ee sees see see ee ee Ge ee ee ee ee 61 Table 31 LA SEL INEBO Coding i sites ks ee Ge ees Se SP ee eatin ge GEK SEERDE Bee Dee ke BEE De ge goe DA Ve dese 62 Table 32 Discovery Configuration Parameters for Listen B i esse see se se ee GR ee ee ee 62 Table 33 LB SENSB INFO valueS esse se ee ee ee ee ee ee ee ee ee ee ee ER ee ee ee ee ee ee ee TEE ee ee ee ee ee ee ee ee ee ee ee 63 NFC Controller Interface NCI Specification Page vi Table 34 Table 35 Table 36 Table 37 Table 38 Table 39 Table 40 Table 41 Table 42 Table 43 Table 44 Table 45 Table 46 Table 47 Table
134. mber of 1 Octet The number of Parameter fields to follow n Parameters Parameter 1 n m 2 ID 1 Octet The identifier of the configuration parameter Octets See Table 101 for a list of IDs Len 1 Octet Length of Val m If Len 0x00 then Val field is omitted Val mOctets Value of the configuration parameter The DH MAY use CORE_GET_CONFIG_CMD to retrieve the current configuration parameters of the NFCC If the NFCC is able to respond with all requested parameters the NFCC SHALL respond with the CORE_GET_CONFIG_RSP with a Status of STATUS_OK NOTE In the STATUS OK case parameter values can be empty and therefore have a Len of 0x00 and no Val field e g if the default value of the parameter is empty If the DH tries to retrieve any parameter s that are not available in the NFCC the NFCC SHALL respond with a CORE_GET_CONFIG_RSP with a Status field of STATUS_INVALID_PARAM containing each unavailable Parameter ID with a Parameter Len field of value zero In this case the CORE_GET_CONFIG_RSP SHALL NOT include any parameter s that are available on the NFCC NOTE This failure case STATUS INVALID PARAM is intended for when the DH tries to retrieve a Parameter that is not supported at all by the NFCC NFC Controller Interface NCI Specification Page 40 NCI Core Control Messages NOTE After receiving the list of unavailable Parameters the DH can assume that the other Parameters req
135. mber of NFCEEs connected to the NFCEE NFC Controller Interface NCI Specification Page 115 NFCEE Discovery and Mode Set NFCEE DISCOVER NTF Payload Field s Length Value Description NFCEE ID 1 Octet An NFCEE ID as defined in Table 84 The value of 0x00 DH NFCEE ID SHALL NOT be used NEFCEE Status 1 Octet 0x00 NFCEE connected and enabled 0x01 NFCEE connected and disabled 0x02 NFCEE removed 0x03 RFU OxFF Number of Protocol 1 Octet The number of Supported NFCEE Protocol fields to follow Information Entries n Supported NFCEE n Octet See Table 100 Protocols 0 n Number of NFCEE 1 Octet Number of NFCEE Information TLV fields to follow m Information TLVs NFCEE Information X 2 Type 1 Octet The Type of the NFCEE Information TLVIO m Octets TLV See Table 86 Length 1 Octet The length of Value x Value x Octets The Value of the NFCEE Information TLV NFC Controller Interface NCI Specification Page 116 NFCEE Discovery and Mode Set Table 86 TLV Coding for NFCEE Discovery Type Length Value 0x00 Hardware Registration Identification The Hardware Registration Identification can be used by the DH to validate that any communication between the DH and an NFCEE only occurs with a valid NFCEE It can be used by the NFC upper layer protocols or a DH application to enable security for communicating with NFCEES The value fie
136. meter 17 255 RFU LF_T3T_IDENTIFIERS_1 10 Octets LF_T3T_IDENTIFIERS_2 10 Octets LF_T3T_IDENTIFIERS_16 10 Octets For each identifier Octet 0 and Octet 1 indicate the System Code of a Type 3 Tag Emulation occurring on the DH Octet 2 Octet 9 indicates NFCID2 for the Type 3 Tag Platform Default Octet 0 and 1 SHALL be set to OxFF Octet 2 SHALL be set to 0x02 Octet 3 SHALL be set to OxFE Octets 4 9 SHALL be set to 0x00 LF_T3T_PMM 8 Octets PADO PAD1 MRTI_check MRTI_update and PAD2 of SENSF_RES as defined in DIGITAL Default all octets set to OxFF LF_T3T_FLAGS 2 Octets A bit field indicating which LF_T3TIDENTIFIERS are enabled in the process to create responses to a SENSF_REQ Detailed definitions as defined below Default 0x0000 LF_ADV_FEAT NFC Controller Interface NCI Specification 1 Octet 0x00 The NFCC SHALL NOT include RD default bytes in its SENSF_RES if it receives a SENSF_REQ with RC set to 0x02 The NFCC MAY include RD bytes in its SENSF_RES if it receives a SENSF_REQ with RC set to 0x02 0x01 0x02 OxFF RFU Page 64 RF Communication Configuration If the DH is interested in NFC DEP based communication it SHALL set the b1 of LF_PROTOCOL_TYPE to 1 which will enables the generation of SENSF_RES indicating NFC DEP capabilities as a response to a SENSF_REQ having a System Code of FFFFh Otherwise the DH SHALL set
137. mmand has to be managed by the DH and if configured accordingly the NFCC SHALL activate the Frame RF Interface e In any other case the NFCC SHALL not activate the Frame RF Interface The protocol activation is fully under the control of the DH when the Frame RF Interface is used therefore for all RF Technologies the RF_INTF_ACTIVATED_NTF SHALL NOT contain any Activation Parameters NOTE Multiple SENSF_RES responses may be sent from one or more of the NFCEEs connected to the NFCC In this case the NFCC has to assign a time slot to each SENSF_RES response prior to sending them to the Remote NFC Endpoint The NECC sends the RF_INTF_ACTIVATED_NTF corresponding to the RF Protocol indicated by the RF Frame received after sending SENSF_RES responses to the Remote NFC Endpoint 8 2 4 3 Interface Deactivation Additional rules apply for the following deactivation cases described in Section 5 2 for RFST_LISTEN_ACTIVE e RF_DEACTIVATE_CMD RSP NTF Sleep Mode Before sending the REF DEACTIVATE NTF the NFCC SHALL move to the following state of the Listen Mode state machine defined in ACTIVITY e SLEEP A when NFC A is the technology currently in use e SLEEP B when NFC B is the technology currently in use e IDLE when NFC F is the technology currently in use e RF DEACTIVATE CMD RSP NTE SIeep AF Mode NFC Controller Interface NCI Specification Page 102 RF Interfaces Before sending the RF DEACTIVATE NTF the NFCC SHALL move to the followin
138. mmands and Responses as defined in T3TOP 10 3 1 Data Exchange The payload of the Data Messages sent on the Logical Connection SHALL be Type 3 Tag Commands and Responses as defined in T3TOP preceded by a 1 octet length field Data Messages MAY be segmented into multiple Data Packets when sent over the NCI The length field value SHALL equal the length of the Type 3 Tag Command or Response plus one Type 3 Tag Commands SHALL only be sent in the direction of DH to NFCC Type 3 Tag Responses SHALL only be sent in the direction of NFCC to DH Figure 23 illustrate the mapping between the Data Packet Format and the Type 3 Tag Command Set Format when no segmentation is applied Data Packet Data Packet Header Payload LEN Byte 1 Byte 2 Byte 3 Byte n oe TEN eye Bye 2 Byte 3 By Command Set CMD Format RSP CMD RSP Parameters Code Figure 23 Data Message Format for Type 3 Tag Command Set Interface 10 3 1 1 Polling Command and Response If a SENSF_REQ is sent by the DH to the NFCEE it SHALL be coded as defined in the Section 6 5 of DIGITAL and SHALL have a TSN value of 0x00 The DH SHOULD choose a larger value for ATPoll as defined in DIGITAL to accommodate a potential longer transmission time of the SENS_RES from the NFCEE to the DH compared to the RF communication 10 4 Transparent NFCEE Interface The Transparent Interface is used by the DH to communicate with NFCEEs connected to the NFCC by exchanging data
139. n Mode Routing Table Table 51 Control Messages to Read the NFCC s Listen Mode Routing RF GET LISTEN MODE ROUTING CMD Payload Field s Length Value Description Empty Payload RF GET LISTEN MODE ROUTING RSP Payload Field s Length Value Description Status 1 Octet See Table 94 RF_GET_LISTEN_MODE_ROUTING_NTF Payload Field s Length Value Description More 1 Octet See Table 45 Number of Routing 1 Octet The number of Routing Entry fields to follow n Entries If the Listen Mode Routing Table is empty the value of this field is 0x00 and there are no Routing Entries following Routing Entry X 2 Type 1 Octet One of the types defined in Table 46 0 n Octets Length 1 Octet The length of Value x Value x Octets Value of the Routing TLV To retrieve the current routing information from the NFCC the DH sends the RF_GET_LISTEN_MODE_ROUTING_CMD to the NFCC The NFCC SHOULD respond with the RF_GET_LISTEN_MODE_ROUTING_RSP with a Status of STATUS_OK followed by one or more RF_GET_LISTEN_MODE_ROUTING_NTF s containing the current routing information All but the last RF GET LISTEN MODE ROUTING _NTF SHALL have the More Parameter set to 1 The last REF GET LISTEN MODE ROUTING NTF SHALL have the More Parameter set to 0 Routing Entry fields will only be present if the value of Number of Routing Entries is greater than Zero In case of an error the NF
140. n Mode state machine the DH SHALL send RF_DEACTIVATE_NTF Discovery Endpoint_Request to the DH The state will then change to RFST_DISCOVERY When using the ISO DEP or NFC DEP RF interface and the NFCC detects an error during the RF communication which does not require returning to the IDLE state as defined in the ACTIVITY Listen Mode state machine the NFCC SHALL send CORE INTERFACE ERROR NTF using the appropriate status out of RF_TRANSMISSION_ERROR RF_PROTOCOL_ERROR and RF_TIMEOUT_ERROR see table 88 The state will then remain RFST_LISTEN_ACTIVE 5 2 7 State RFST LISTEN SLEEP In this state the NFCC is not supposed to respond to any RF commands until it gets a valid RF wake up command for details refer DIGITAL NFC Controller Interface NCI Specification Page 53 RF Communication If the NFCC receives a valid RF wake up command s followed by successful activation procedure the NFCC SHALL send RF_INTF_ACTIVATED_NTF Listen mode to the DH At that point the state is changed back to RFST_LISTEN_ACTIVE On detection of remote RF field off the NFCC SHALL send RF DEACTIVATE_NTF Discovery RF Link Loss to the DH The RF Communication state will then change to RFST_DISCOVERY For NFC B Technology when the NFCC detects a command during the RF communication which forces returning to the IDLE state as defined in the ACTIVITY Listen Mode state machine the NFCC SHALL send RF_DEACTIVATE_NTF Discovery NFC B Bad AFD to the
141. nd Sleep AF Mode are not allowed for all RF Interfaces Each RF Interface specifies whether it supports these deactivation cases If an RF_DEACTIVATE_CMD with Deactivation Type set to Sleep Mode or Sleep AF Mode is received when using an RF Interface where those values are not allowed the NFCC SHALL send RF_DEACTIVATE_RSP with a Status of STATUS_REJECTED The NFCC SHALL NOT send RF_DEACTIVATE_NTF in this case If the Deactivation Type in the RF_DEACTIVATE_CMD was set to Sleep Mode or Sleep AF Mode and there was an error in executing the protocol deactivation procedures defined by the RF Interface the RF DEACTIVATE NTF SHALL have the Deactivation Type set to Idle Mode and the state SHALL change to RFST_IDLE In all other cases and if not defined otherwise in the corresponding interface section the value of the Deactivation Type parameter of the RF_DEACTIVATE_NTF SHALL be the same as in the RF_ DEACTIVATE CMD If the RF_DEACTIVATE_NTF is send following a RF DEACTIVATE CMD RSP the Deactivation Reason SHALL be set to DH Request If the activated RF Interface defines that the NFCC has to perform protocol deactivation procedures the NFCC SHALL perform those deactivation procedures before sending the RF_DEACTIVATE_NTF Prior to sending an RF_DEACTIVATE_NTF the NFCC SHOULD send all data pending to be sent to the Remote NFC Endpoint and send all completely received Data Messages to the DH After sending a R
142. nfiguration parameters was successful or not A Status of STATUS_OK SHALL indicate that all configuration parameters have been set to these new values within the NFCC If the DH tries to set a parameter that is not applicable for the NFCC the NFCC SHALL respond with a CORE_SET_CONFIG_RSP with a Status field of STATUS_INVALID_PARAM and including one or more invalid Parameter ID s All other configuration parameters SHALL have been set to the new values within the NFCC NFC Controller Interface NCI Specification Page 39 NCI Core Control Messages Based on the maximum size of the payload of a Control Message and on the length of the Payload Fields in CORE GET CONFIG RSP the maximum length of a parameter is limited to 251 octets The parameter length fields Parameter Len n SHALL be set to a value between 0x00 and OxFB The values OxFC OxFF are RFU 4 3 2 Retrieve the Configuration These Control Messages are used by the DH to retrieve current configuration parameters of the NFCC Table 11 Control Messages for Reading Current Configuration CORE_GET_CONFIG_CMD Payload Field s Length Value Description Number of 1 Octet The number of Parameter ID fields to follow n Parameters Parameter ID 1 Octet The identifier of the configuration parameter 1 n See Table 101 for a list of IDs CORE_GET_CONFIG_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 Nu
143. ng the command to the DH If the NFCC has not determined which protocol is being activated the RF Protocol value SHALL be PROTOCOL_UNDETERMINED There are five different states in the Listen state machine defined in ACTIVITY from which the NFCC may activate the Frame RF Interface These five pre activation states are listed in the Table 75 Once in one of these pre activation states some commands received from the remote NFC Endpoint are managed by the NFCC others are forwarded to and then managed by the DH Table 75 details which commands the NFCC handles when using the Frame RF Interface in Listen Mode Any other commands are forwarded to the DH NFC Controller Interface NCI Specification Page 101 RF Interfaces Table 75 Pre activation states and the split of commands between NFCC amp DH Technology Pre activation state Commands handled by the NFCC NFC A ACTIVE_A amp SENS_REQ ACTIVE_A ALL_REQ SLP_REQ SDD_REQ SEL_REQ Command with Transmission Error as defined in DIGITAL e g CRC errors Parity errors NFC B READY_B_DECL SENSB_REQ ALLB_REQ SLPB_REQ Command with Transmission Error as defined in DIGITAL e g CRC errors NEC F IDLE amp READY F SENSF_REQ Command with Transmission Error as defined in DIGITAL e g CRC errors When the NFCC receives a command while it is in one of these pre activation states e based on the information in Table 75 if the co
144. ngth SHALL be 0x00 and Local NFCID2 field is not present Other values are RFU Local NFCID2 0 or 8 NFCID2 generated by the Local NFCC for Octets NFEC DEP Protocol Available for Frame RF Interface NFC Controller Interface NCI Specification Page 81 RF Discovery 7 2 Select Discovered Target These Control Messages are used to select an RF Discovery ID and RF Protocol identifying a Remote NFC Endpoint as reported by a previous RF_DISCOVER_NTF and the RF Interface to use for communicating with the Remote NFC Endpoint which might differ from the one defined in the RF_DISCOVER_MAP_CMD Table 60 Control Messages to select a Discovered Target RF_DISCOVER_SELECT_CMD Payload Field s Length Value Description RF Discovery ID 1 Octet See Table 53 RF Protocol 1 Octet See Table 98 RF Interface 1 Octet See Table 99 The value 0x00 NFCEE Direct RF Interface SHALL NOT be used RF_DISCOVER_SELECT_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 The DH SHALL send RF_DISCOVER_SELECT_CMD to the NFCC to inform the NFCC which RF Discovery ID RF Protocol and RF Interface are to be used for subsequent communication In case the RF Discovery ID RF Protocol or RF Interface is not valid the NFCC SHALL respond with RF_DISCOVER_SELECT_RSP with a Status of STATUS_REJECTED Otherwise the NFCC SHALL respond with RF_DISCOVER_SELECT_RSP with a Status of STATUS_OK Af
145. o RFST_POLL_ACTIVE If the protocol activation is not successful the NFCC SHALL send CORE_GENERIC_ERROR_NTF to the DH with status DISCOVERY_TARGET_ACTIVATION_FAILED and stay in RFST_DISCOVERY In this state the NFCC MAY detect a command during the RF communication which forces it to come back to the IDLE state as defined in the ACTIVITY Listen Mode state machine If the RF Protocol deactivation is completed the NFCC SHALL send CORE_GENERIC_ERROR_NTF DISCOVERY_TEAR DOWN and the state will remain RFST_DISCOVERY NOTE RF Protocol deactivation while in state RFST_DISCOVERY can happen if during protocol activation in Listen Mode a teardown command is received e g an NFC DEP RLS_REQ when waiting for a potential PSL_REQ If the DH sends RF_DEACTIVATE_CMD the NFCC SHALL ignore the Deactivation Type parameter stop the RF Discovery Process and send RF_DEACTIVATE_RSP The state will then change to RFST_IDLE 5 2 3 State RFST_W4_ALL_DISCOVERIES In this state the NFCC has discovered more than one Remote NFC Endpoint or a Remote NFC Endpoint that supports more than one RF Protocol while polling The NFCC SHOULD keep the RF field ON while in this state Discover notifications with Notification type set to 2 SHALL NOT change the state When the NFCC sends the last RF_DISCOVER_NTF Notification Type not equal to 2 to the DH the state is changed to RFST_W4_HOST_SELECT If the DH sends RF_DEACTIVATE_CMD the NFCC SHALL ignore the Deac
146. oad Format defined Section 6 4 of DIGITAL followed by a Status field of 1 octet After receiving an RF frame the NFCC SHALL check and remove the EoD and send the result in a Data Message to the DH NOTE The information in the Note of 8 2 1 1 applies also for the Data Messages send to the DH except that the Status field is added to each Data Message In case of an error the Data Message MAY consist of only a part of the Payload of the received RF frame but SHALL include the trailing Status field A Data Message consisting of only the Status field is a valid message If the RF frame was received correctly the NFCC SHALL set the Status field of Data Message to a value of STATUS OK If the NFCC detected an error when receiving the RF frame the NFCC SHALL set the Status field of the Data Message to a value of STATUS_RF_FRAME_CORRUPTED see Table 94 Figure 14 Figure 15 and Figure 16 illustrate the mapping of the RF frame received from the Remote NFC Endpoint to the Data Message format to be sent to the DH for each Technology NOTE These figures show the case where NCI Segmentation and Reassembly feature is not used NFC Controller Interface NCI Specification Page 94 RF Interfaces Data RF Frame Payload BET Byte 2 Byen Data Packet Data Packet Header Payload p s 254 octets at maximum 1 octet Figure 14 Format for Frame RF Interface NFC A for Reception For NFC A Data Message SHALL NOT contain the parity bits pre
147. of different NCI Transport layers NCI is specified to accommodate different levels of functionality in the NFCC with regard to RF communications Different levels of functionality imply different splits of the NFC Forum protocol stack between the NFCC and the DH To achieve this NCI specifies RF Interfaces each of which can be communicated with a DH and each of which interfaces to a defined functional block implemented on the NFCC An NCI implementation on an NFCC will be tailored to include the RF Interfaces that match the functionalities of the NFCC NCI provides features to allow DH to NFCEE communication NCI therefore includes methods to discover and enumerate connected NFCEEs and the NFCEE Interfaces they support and to establish connections between DH and NFCEE Interfaces NCI also contains definitions of the data formats that can be exchanged over a connection to NFCEE Interfaces NCI is specified to be extensible to allow future extensions and vendor specific functionality 1 2 Scope The following figure outlines a typical architecture of an NFC Forum Device Device Host NFC Controller DH NFCEE RF Higher layer drivers software NFCEE NCI NCI l link ODE NCI driver firmware Transport Transport NFCEE Layer Layer eee layer firmware firmware ier E NCI Scope Physical connections Figure 1 NCI Scope The NFCC is connected to the Device Host which is the main application processor in the Device NFC Controller Interface N
148. of the RF Interface does not always coincide with the completion of Device Activation For ISO DEP Protocol the RATS or ATTRIB commands responses are not handled by the NFCC but must be handled by the DH and are sent over NCI as the Payload of Data Messages The same is true for ATR_REQ RES and PSL_REQ RES when activating NFC DEP Protocol All Protocols defined in Table 98 can be mapped to this Interface see Section 6 2 8 2 1 Data Mapping between the DH and RF The DH and the NFCC SHALL only use the Static RF Connection for data communication with a Remote NFC Endpoint The DH MAY send a Data Message to the NFCC according to Section 8 2 1 1 The NFCC SHALL populate an RF frame of the currently used Technology with this data and send the RF frame to the Remote NFC Endpoint When the NFCC receives an RF frame from the Remote NFC Endpoint then the NFCC SHALL extract the Payload from the RF frame and send it as Payload of a Data Message to the DH according to Section 8 2 1 2 NCI Segmentation and Reassembly MAY be applied to Data Messages in either direction NFC Controller Interface NCI Specification Page 92 RF Interfaces The format of the Data within the Data message used for the Frame RF Interface NFC A NFC B NFC F differs depending on the transmission direction of the message 8 2 1 1 Data from the DH to RF For NFC A and NFC B the Data Message SHALL correspond to the Payload of the Data and Payload Format defined in
149. ol Protocol LLCP for the NFC DEP protocol binding 8 4 3 Poll side NFC DEP RF Interface Management The Poll side NFC DEP RF Interface MAY be used when the device operates as an NFC DEP Initiator when in Peer Mode and the Remote NFC Endpoint supports NFC DEP based on NFC A or NFC F 8 4 3 1 Discovery Configuration The Discovery configuration parameters defined in the following tables are relevant depending on the NFC technology used in Discovery NFC A or NFC F as set by RF Technology and Mode in RF_DISCOVER_CMD They MAY be changed from defaults by using the CORE_SET_CONFIG_CMD before moving to state RFST_DISCOVERY e Table 23 Discovery Configuration Parameters for Poll A e Table 26 Discovery Configuration Parameters for Poll F e Table 28 Discovery Configuration Parameters for Poll NFC DEP 8 4 3 2 Discovery and Interface Activation To enable Poll Mode for NFC DEP the DH sends the RF_DISCOVER_CMD to the NFCC containing configurations with RF Technology and Mode values of NFC_A_PASSIVE_POLL_MODE and or NFC F PASSIVE POLL MODE When the NFCC is ready to exchange data that is after successful protocol activation it SHALL send the RF_INTF_ACTIVATED_NTF to the DH to indicate that the NFC DEP protocol has been activated as follows Following the anticollision sequence if the Remote NFC Endpoint supports NFC DEP Protocol the NFCC sends an ATR_REQ with PN ATR REO GEN BYTES configured during Discovery Configuration to the Remote NFC
150. ol that is used to communicate with the Remote NFC Endpoint During RF Discovery configuration the DH must configure a mapping that associates an RF Interface for each RF Protocol If only a single Remote NFC Endpoint is detected during one discovery cycle the RF Interface for this Endpoint is automatically activated If there are multiple Remote NFC Endpoints detected in Poll Mode the DH can select the Endpoint it wants to communicate with This selection also triggers activation of the mapped Interface After an RF Interface has been activated the DH can communicate with the Remote NFC Endpoint using the activated RF Interface An activated RF Interface can be deactivated by either the DH or the NFCC e g on behalf of the Remote NFC Endpoint However each RF Interface can define which of those methods are allowed There are different deactivation options depending on which part of the protocol stack is executed on the DH For example if a protocol command to tear down the communication is handled on the DH the DH will deactivate the RF Interface If such a command is handled on the NFCC the NFCC will deactivate the Interface This specification describes the possible Control Message sequences for RF Communication in the form of a state machine 2 2 5 NFCEE Communication The 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 D
151. on 5 2 for RFST_LISTEN_ACTIVE SHALL NOT be allowed e RF_DEACTIVATE_CMD RSP NTF Sleep_AF Mode 8 3 2 4 Failures during Data Exchange If an ISO DEP Timeout Error PROTOCOL EXCEPTION occurs the NFCC SHALL send the CORE INTERFACE ERROR NTFE with the Status of RF_TIMEOUT_ERROR If an ISO DEP Transmission Error PROTOCOL EXCEPTION occurs the NFCC SHALL send the CORE INTERFACE ERROR_NTF with the Status of RF_TRANSMISSION_ERROR If an ISO DEP Protocol Error PROTOCOL EXCEPTION occurs the NFCC SHALL send the CORE INTERFACE ERROR NTF with the Status of RF PROTOCOL ERROR 8 3 3 Listen side ISO DEP RF Interface Management This Listen side ISO DEP RF Interface MAY be used for Card Emulation Mode when the Remote NFC Endpoint uses ISO DEP based on NFC A or NFC B In Listen Mode if the NFCC receives an I Block from the Remote NFC Endpoint with an empty Payload as part of the presence check mechanism defined in ISO IEC 14443 the NFCC SHALL respond with an I Block and not forward the received I Block to the DH 8 3 3 1 Discovery Configuration The Discovery configuration parameters defined in the following tables are relevant depending on the NFC technology used in Discovery NFC A or NFC B as set by RF Technology and Mode in RF_DISCOVER_CMD They MAY be changed from defaults by using the CORE_SET_CONFIG_CMD before moving to state RFST_DISCOVERY e Table 30 Discovery Configuration Parameters for Listen A e Table 32 Discovery Configuration Param
152. on Page 46 RF Communication 5 RF Communication Communication with a Remote NFC Endpoint is performed by the use of RF Interfaces RF Interfaces are logical entities on the NFCC which allow the DH to use specific layers in the protocol stack implemented on the NFCC The DH can only communicate with a Remote NFC Endpoint via an RF Interface that has been activated during the Discovery process Section 5 1 gives an overview about the available RF Interfaces Section 5 2 defines the NCI state machine for RF Communication Section 5 3 defines a mechanism to get information about an external RF field 5 1 RF Interface Architecture All data exchanged between the DH and a Remote NFC Endpoint flows through an RF Interface designated as the Active RF Interface Figure 9 shows an overview of the RF Interfaces NFC R W M i C RAN Mode 1 NFG Peer Mode Interfaces NFC CE Mode Interfaces Interfaces i LLCP High Interface i NDEF Access IF LLCP High R W NDEF i LLCP Low Interface l Tag 4 LLCP Low Tag ISO DEP IF NFC DEP Interface ISO DEP IF is ISO DEP NFC DEP NFC DEP ISO DEP Poll side Poll side Listen side Listen side Poll Side Frame Interface Listen Side Frame Interface RF Frame Poll side Initiator RF Frame Listen side Target Figure 9 RF Interface Architecture NOTE The NDEF Access LLCP High and LLCP Low RF Interfaces do not exi
153. only the Static RF Connection However Dynamic Logical Connections may be used by RF Interfaces included in future versions of this specification The Conn ID has a range of 0 to 15 see Table 4 The Conn ID of 0 is reserved for the Static RF Connection used for RF communication which exists following NFCC Initialization but that is not available for use unless an RF Interface is activated Each RF Interface defines whether the Static RF Connection is used and whether Dynamic Logical Connections are permitted NFC Controller Interface NCI Specification Page 32 NCI Core Framework Table 4 Conn ID Conn ID Description 0000b Static RF Connection between the DH and a Remote NFC Endpoint 0001b Dynamically assigned by the NFCC 1111b NFC Controller Interface NCI Specification Page 33 NCI Core Control Messages 4 NCI Core Control Messages Following are the descriptions of the Commands Responses and Notifications that are part of the NCI Core 4 1 Reset of NFCC These Control Messages are used to reset the NFCC Table 5 Control Messages to Reset the NFCC CORE_RESET_CMD Payload Field s Length Value Description Reset Type 1 Octet 0x00 Keep Configuration Reset the NFCC and keep the NCI RF Configuration if supported 0x01 Reset Configuration Reset the NFCC including the NCI RF Configuration 0x02 OxFF
154. or value coding refer to Table 97 Depending on the capabilities of NFCC the NFCC MAY adjust a lower bit rate than specified by this field even if a higher bit rate would be supported by the Remote NFC Endpoint PA_ADV_FEAT 1 Octet 0x00 The NFCC SHALL NOT indicate default support for advanced protocol features in the RATS command as defined in DIGITAL 0x01 The NFCC SHALL indicate support for advanced protocol features in the RATS command as defined in DIGITAL 0x02 0xFF RFU NFC Controller Interface NCI Specification Page 59 RF Communication Configuration 6 1 5 Poll NFC DEP Parameters Those parameters MAY be configured if polling for NFC A and or NFC F or P2P Active Table 28 Discovery Configuration Parameters for Poll NFC DEP ID Length Value Description PN_NFC_DEP_SPEED 1 Octet 0x00 Highest Available Bit Default Rates The NFCC SHOULD use the highest supported Bit Rates for Data Exchange The NFCC is responsible for determining the highest Bit Rate available for Data Exchange If the Bit Rate change is possible a PSL_REQ is sent by the NFCC 0x01 Maintain the Bit Rates The NFCC SHALL use the same bit rates for Data Exchange as were used for Device Activation even if higher bit rates are supported This means that a PSL_REQ is not sent by the NFCC 0x02 RFU OxFF PN ATR REO GEN BYTES 0 n Octets General Bytes for ATR REO Default empty no Genera
155. orted RF 1 Octet See Table 99 Interface 1 n NOTE If supported the pseudo interface NFCEE Direct RF Interface has to be reported as well Max Logical 1 Octet 0x00 OXOE Maximum number of Dynamic Logical Connections Connections supported by the NFCC OxOF OxFF RFU Max Routing Table 2 Octets Indicates the maximum amount of data in Octets that are Size possible in a routing configuration see Section 6 3 If Listen Mode Routing is not supported then the value SHALL be 0x0000 Max Control Packet 1 Octet Indicates the maximum payload length of a NCI Control Payload Size Packet that the NFCC is able to receive Valid range is 32 to 255 NOTE All Control Messages exchanged prior to this have a length that is smaller than 32 octets Max Size for Large 2 Octets The maximum size in octets for the sum of the sizes of Parameters PB_H_INFO and LB_H_INFO_RESP parameter values NFC Controller Interface NCI Specification Page 36 NCI Core Control Messages CORE INIT RSP Payload Field s Length Value Description Manufacturer ID 1 Octet IC Manufacturer ID as defined in MANU If this information is not available the NFCC SHALL return 0x00 Manufacturer Specific 4 Octets This field contains NFCC manufacturer specific information Information like chip version firmware version etc encoded in a manufacturer specific mode If this information is not available or if the Manufacturer ID is set
156. orted on the C transport 11 3 Half Duplex SPI Transport 11 3 1 Physical NCI control and data messages are transmitted over SPI The DH SHALL be the master of the communication The communication SHALL use standard SPI signal lines i e SPI_CSN SPI CLK SPI MOSI and SPI MISO In addition to attain flow control there SHALL be an additional SPI_INT signal line which SHALL be driven by the slave The clock rate negotiation is manufacturer specific and is out of scope of this document The data sent through the transport is assumed to be in Little Endian format 11 3 1 1 SPI Modes SPI can be operated in one of the four modes described below The mode selection procedure is manufacturer specific and is out of scope of this document Table 89 SPI modes SPI mode CPOL CPHA 0 0 0 1 0 1 2 1 0 1 1 NFC Controller Interface NCI Specification Page 127 Transport Mappings SCK CYCLE FOR REFERENCE Mode 0 scx CPoL g Mode 2 SCK CPOL 1 MOSI FROM MASTER MISO FROM SLAVE SS TO SLAVE h SCK CYCLE 7 FOR REFERENCE Mode 1 SCK CPOL 0 Mode 3 SCK CPOL 1 MOSI FROM MASTER MISO 22 FROMSLAVE IIT SS TO SLAVE Figure 24 SPI Operation 11 3 2 Data Transfer This proposal reduces the full duplex nature of the Generic SPI transport to a half duplex interface Packet framing and flow control mechanisms ar
157. ot all values are relevant to a given operating mode Values that are relevant to the current RF Communication State SHALL be used by the NFCC as defined in DIGITAL during subsequent Data Exchange They consist of Minimum TRO Minimum TR1 Minimum TR2 Suppression of SoS and Suppression of EoS The format of the octet is defined below NFC Controller Interface NCI Specification Page 97 RF Interfaces Table 73 NFC B Data Exchange Configuration Parameter Bit Mask Description b7 b6 b5 b4 b3 b2 b1 b0 OctetO X X Minimum TRO as defined in DIGITAL X X Minimum TRI as defined in DIGITAL X Suppression of EoS as defined in DIGITAL X Suppression of SoS as defined in DIGITAL X X Minimum TR2 as defined in DIGITAL On receipt of the RF PARAMETER UPDATE CMD Command e if the NFCC is in state REST POLL ACTIVE it SHALL update the RF Communication parameters contained within the Command before responding with an RE PARAMETER UPDATE RSP NOTE For NFC DEP RF Protocol the RF Communication parameters need to be aligned with the parameter values contained in the PSL_REQ and the update Command is issued after the PSL_RES is received from the Remote NFC Endpoint but before the first DEP_REQ is sent e if the NFCC is in state RFST_LISTEN_ACTIVE it SHALL respond with an REF PARAMETER UPDATE RSP and then SHALL wait until it has sent the next RF Frame before updating
158. otocol in Listen Mode X Ifsetto 1b the RF Interface is mapped to the RF Protocol in Poll Mode At least one of the bits bO or bl SHALL be set to 1b A Mapping Configuration defines the RF Interface which SHALL be used for the communication from the DH to a Remote NFC Endpoint using the specified RF Protocol and Mode when the NFCC autonomously transfers to the RFST_POLL_ACTIVE or RFST_LISTEN_ACTIVE states NFC Controller Interface NCI Specification Page 69 RF Communication Configuration If the DH initiates the transfer to the RFST_POLL_ACTIVE state by sending an RF_DISCOVER_SELECT_CMD the DH SHALL specify the interface to use as a parameter to the RF_DISCOVER_SELECT_CMD which overruless any values which may be in the RF Interface Mapping configuration Only one RF Interface SHALL be mapped to each RF Protocol To perform RF Interface mapping the DH SHALL send a RF_DISCOVER_MAP_CMD to the NFCC The NFCC SHALL set the RF Interface for all RF Protocols Modes not included in the RF DISCOVER MAP CMD to the value Frame RF Interface If the NFCC accepts the RF Interface mapping configuration it SHALL respond using a RF_DISCOVER_MAP_RSP with a Status of STATUS OK If the RF Interface mapping is invalid the NFCC SHALL reject the mapping configuration by sending a RF DISCOVER MAP RSP with a Status of STATUS_REJECTED In this case the DH MAY attempt an alternative configuration If
159. owing sections 6 1 Configuration Parameters These are configuration parameters related to discovery The Commands used to set and get these parameters are specified in Section 4 3 The sub sections below describe all configurable RF Discovery parameters Table 101 contains a list of all parameters with their Parameter Tags All parameters have default values so the DH is not required to configure any RF Discovery parameter Also some parameters are relevant only for either Listen or Poll Mode or only to specific RF Interface s These parameters are described in the corresponding RF Interface sections If the DH has changed any parameter the DH MAY reset the parameter back to its default value by sending a CORE_SET_CONFIG_CMD with a Parameter field containing the ID of the parameter a length of 0x00 and no value field If the DH retrieves a Parameter whose current value is a default defined by the NFCC the NFCC SHALL send the actual value of the parameter as set by the NFCC In the particular case where the NFCC combines configuration parameters from the DH and some NFCEEs as reported in CORE_INIT_RSP see Table 9 the NFCC may modify the configuration parameters set by the DH before they are visible on the RF or read back by the DH The way they are modified is out of the scope of this document 6 1 1 Poll A Parameters Table 23 Discovery Configuration Parameters for Poll A ID Length Value Description PA BAIL OUT
160. r transporting Control Messages and Data Packets for transporting Data Messages Poll Mode The mode of an NFC Forum Device when it generates a carrier and probes polls for other devices Response Message Sent by the NFCC for each Command Message received from the DH The Response Message may contain status information pertaining to the results of the Command Message Remote NFC Endpoint Refers to a remote device card or tag connected wirelessly over the NFC Radio Interface to the local NFC Forum Device RF Discovery Process Functionality that allows detection of a Remote NFC Endpoint and detection by a Remote NFC Endpoint The DH can configure the RF Discovery Process which then runs autonomously within the NFCC NFC Controller Interface NCI Specification Page 16 Introduction RF Interface Logical entities that may contain some protocol logic e g an ISO DEP RF Interface or an NFC DEP RF Interface or may be a transparent conduit e g a Frame RF Interface The DH can only communicate with a Remote NFC Endpoint via an RF Interface designated as the Active RF Interface The NFCC contains multiple RF Interfaces RF Protocol A protocol used in the communication between the NFCC and a Remote NFC Endpoint Static RF Connection A Logical Connection with a fixed Connection Identifier that always exists after NFCC initialization and is never closed It is used by the DH to communicate with a Remote NFC
161. rom NFCC to DH When an NFCC sends a Control Message to the DH regardless of the length it MAY segment the Control Message into smaller Control Packets if needed for internal optimization purposes The following rules apply to segmenting Data Messages e For each segment of a Data Message the header of the Data Packet SHALL contain the same MT and Conn ID e From DH to NFCC If a Data Message payload size exceeds the Max Data Packet Payload Size of the connection then the Segmentation and Reassembly feature SHALL be used on the Data Message e From NFCC to DH When an NFCC sends a Data Message to the DH regardless of the payload length it MAY segment the Data Message into smaller Data Packets for any internal reason for example for transmission buffer optimization NFC Controller Interface NCI Specification Page 31 NCI Core Framework 3 6 Logical Connections Logical Connections are used to exchange Data Messages between the DH and the NFCC Logical Connections provide a common context for related Data Messages Depending on the information exchanged during Logical Connection establishment the NFCC can be the endpoint of the Data communication or it has to forward the Payload of the Data Messages to or from a Remote NFC Endpoint or NFCEE the later two being the main use cases for Logical Connections NOTE The communication method between the NFCC and the Remote Endpoint or between the NFCC and an NFCEE is out of scope of NCI
162. ry extensions will silently discard the Notifications NFC Controller Interface NCI Specification Page 144 Revision History C Revision History The following table outlines the revision history of NFC Controller Interface NCI Specification Table 103 Revision History Document Revision and Status Change Notice Supersedes Name Release Date NFC Controller Version 1 Final None Interface NCI November 2012 Specification NFC Controller Interface NCI Specification Page 145
163. s either a PSL_REQ or a first command It SHALL then forward the ATR_REQ and the updated data rate and technology information to the DH within the Activation Parameters of the RF_INTF_ACTIVATED_NTF For NFC A and NFC F the RF_INTF_ACTIVATED_ NTF SHALL include the Activation Parameters defined in Table 83 Table 83 Activation Parameters for NFC DEP Listen Mode Parameter Length Description ATR_REQ Command 1 Octet Length of ATR_REQ Command Parameter n Length ATR_REQ Command n Octets All Bytes of the ATR_REQ Command as defined in DIGITAL starting from and including Byte 3 8 4 4 3 Interface Deactivation Additional rules apply for the following deactivation cases described in Section 5 2 for RFST_LISTEN_ACTIVE e RF DEACTIVATE NTF Sleep AF Mode Endpoint Request After sending a Deselect response DSL_RES to the Remote NFC Endpoint the NFCC SHALL send the DEACTIVATE_NTF e RF DEACTIVATE NTF Discovery Endpoint_Request After sending a Release response RLS_RES to the Remote NFC Endpoint the NFCC SHALL send the DEACTIVATE_NTF NFC Controller Interface NCI Specification Page 113 RF Interfaces When using this RF Interface the following deactivation cases described in Section 5 2 for RFST LISTEN ACTIVE SHALL NOT be allowed e RF DEACTIVATE NTF SIeep Mode Endpoint Request e RF_DEACTIVATE_CMD RSP NTF Sleep Mode e RF_DEACTIVATE_CMD RSP NTF Sleep_AF Mode 8 4 4 4 Failures during Data Exchange
164. s listed in Exhibit A 2 NO WARRANTIES THE SPECIFICATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE ACCURACY COMPLETENESS AND NONINFRINGEMENT OF THIRD PARTY RIGHTS IN NO EVENT SHALL LICENSOR ITS MEMBERS OR ITS CONTRIBUTORS BE LIABLE FOR ANY CLAIM OR ANY DIRECT SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE DATA OR PROFITS WHETHER IN AN ACTION OF CONTRACT NEGLIGENCE OR OTHER TORTIOUS ACTION ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE SPECIFICATION 3 THIRD PARTY RIGHTS Without limiting the generality of Section 2 above LICENSOR ASSUMES NO RESPONSIBILITY TO COMPILE CONFIRM UPDATE OR MAKE PUBLIC ANY THIRD PARTY ASSERTIONS OF PATENT OR OTHER INTELLECTUAL PROPERTY RIGHTS THAT MIGHT NOW OR IN THE FUTURE BE INFRINGED BY AN IMPLEMENTATION OF THE SPECIFICATION IN ITS CURRENT OR IN ANY FUTURE FORM IF ANY SUCH RIGHTS ARE DESCRIBED ON THE SPECIFICATION LICENSOR TAKES NO POSITION AS TO THE VALIDITY OR INVALIDITY OF SUCH ASSERTIONS OR THAT ALL SUCH ASSERTIONS THAT HAVE OR MAY BE MADE ARE SO LISTED 4 TERMINATION OF LICENSE In the event of a breach of this Agreement by Licensee or any of its employees or members Licensor shall give Licensee written notice and an opportunity to cure If the breach is not cured within thirty 30 days after wri
165. s of Interfaces RF Interfaces and NFCEE Interfaces Protocols used to communicate with a Remote NFC Endpoint are called RF Protocols Protocols used to communicate with an NFCEE are called NFCEE Protocols An NFCEE Interface has a one to one relationship to an NFCEE Protocol whereas there might be multiple RF Interfaces for one RF Protocol The later allows NCI to support different splits of the protocol implementation between the NFCC and DH An NCI implementation on an NFCC should include those RF Interfaces that match the functionality implemented on the NFCC Interfaces must be activated before they can be used and they must be deactivated when they are no longer used An Interface can define its own configuration parameters and Control Messages but most importantly it must define how the payload of a Data Message maps to the payload of the respective RF or NFCEE Protocol and in the case of RF Communication whether the Static RF Connection and or Dynamic Logical Connections are used to exchange those Data Messages between the DH and the NFCC 2 2 4 RF Communication RF Communication is started by configuring and running the RF Discovery process The RF Discovery is an NCI module that discovers and enumerates Remote NFC Endpoints For each Remote NFC Endpoint the RF Discovery Process provides the DH with the information about the Remote NFC Endpoint gathered during the RF Discovery Process One part of this information is the RF Protoc
166. sed to close a Dynamic Logical Connection Table 16 Control Messages for Connection Closure CORE CONN CLOSE CMD Payload Field s Length Value Description Conn ID 1 Octet The identifier of the connection to be closed The four least significant bits of the octet SHALL contain the Conn ID as defined in Table 4 The four most significant bits are RFU CORE_CONN_CLOSE_RSP Payload Field s Length Value Description Status 1 Octet See Table 94 To close a Logical Connection the DH sends the CORE CONN CLOSE CMD to the NFCC indicating the Conn ID to be closed On receiving a CORE_CONN_CLOSE_CMD for an existing connection the NFCC SHALL accept the connection closure request by sending a CORE_CONN_CLOSE_RSP with a Status of STATUS_OK and the Logical Connection is closed If there is no connection associated to the Conn ID in the CORE CONN CLOSE CMD the NFCC SHALL reject the connection closure request by sending a CORE CONN CLOSE RSP with a Status of STATUS_REJECTED When a DH receives this status it should assume that the Conn ID is unknown and therefore the connection no longer exists on the NFCC and SHOULD proceed as in a normal closing The DH SHALL clean up all resources associated with the Conn ID after it sends the CORE_CONN_CLOSE_CMD The NFCC SHALL clean up all resources associated with the Conn ID after receiving the CORE_CONN_CLOSE_CMD NOTE Clean up all resources means deletin
167. sent in the Standard Frame and Bit Oriented Frame When receiving RF Frames the NFCC SHALL check and remove these parity bits according to DIGITAL For NFC B Data Message SHALL NOT contain the start and stop bits used by NFC B frame format When receiving the RF Frames the NFCC SHALL remove the start and stop bits according to DIGITAL For Type 1 Tag Platform the RF Frame format is defined in Section 8 4 of DIGITAL where EoD consists of CRC_B1 and CRC_B2 For Type 2 Tag Platform when the NFCC in Poll Mode receives 4 bit ACK or NACK RF Frames from the Remote NFC Endpoint the NFCC SHALL populate these 4 bits to the lower order bits of the first and only payload octet while each higher order bit is set to Ob Data RF Frame Payload EoD Byte 1 Byte 2 Byte n CRC_B1 CRC_B2 Payload i i 254 octets at maximum 1 octet Data Packet Data Packet Header Figure 15 Format for Frame RF Interface NFC B for Reception Data RF Frame Payload Byte 1 Byte 2 Byte n CRC_F1 CRC_F2 Data Packet Data Packet Header SoD Payload Figure 16 Format for Frame RF Interface NFC F for Reception NFC Controller Interface NCI Specification Page 95 RF Interfaces 8 2 2 Frame RF Interface specific Control Messages 8 2 2 1 RF Communication Parameter Update These Control Messages are used to update RF Communication parameters once the Frame RF Interface has been activated The REF PARAMETER UPDATE CMD SHALL NOT
168. served and static NFCEE ID value 0 which represents the DH NFCEE Logical Connections take a third type of identifier Destination Type as a first parameter to identify the destination for the data Depending on the Destination Type there can be a second parameter for identifying the data destination For example if the Destination Type is Remote NFC Endpoint the second parameter will be an RF Discovery ID 2 2 7 NFCC as Shared Resource The 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 For example they might 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 as to 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
169. st in the NCI specification version 1 0 They are anticipated to be added in a future version The following should be noted e The ISO DEP RF Interface is applicable for both Reader Writer Mode and Card Emulation Mode e Specific to the Frame RF Interface e The Poll Side Frame RF Interface is applicable for both Reader Writer Mode and the NFC DEP Initiator side of the Peer Mode e Listen Side Frame RF Interface is applicable for both Card Emulation Mode and the NFC DEP Target side of the Peer Mode An RF Interface is automatically activated by the NFCC in the following cases e When in Poll Mode a single Remote NFC Endpoint supporting a single protocol has been discovered NFC Controller Interface NCI Specification Page 47 RF Communication e In Listen Mode the NFCC has been discovered selected by a Remote NFC Endpoint In both cases the RF Interface to activate is determined by the current mapping between RF Protocols and RF Interfaces that can be configured using the RF_DISCOVER_MAP_CMD Command defined in Section 6 2 If in Poll Mode multiple Remote NFC Endpoints or a Remote NFC Endpoint supporting more than one RF Protocol have been discovered the DH has to select a Remote NFC Endpoint and RF Protocol using the RF_DISCOVER_SELECT_CMD Command After receipt of this Command the NFCC activates the RF Interface specified in the RF_DISCOVER_SELECT_CMD Command The activation of an RF Interface depends on the Mode e
170. t s seis 08 si eene Seer eel chic ee dood eed ke te eee 88 AD RE NECEBsA CH Oni itc c3 EO RE NE EE Ie 89 8 RF MTC ie N OE N EE EN 92 8 1 NEBCEE Direct RF Interface ss ceca iii Kees de Ge ee Ge Wes DE Gee GR Veg SE ee ee ee 92 8 1 1 Discovery and Interface Activation iese ese se es se ee ee Se Ge RA GRA RA ee ee 92 8 1 2 Interface Deactivation eee esse n ee AR AA AA AR ee RA E ee ee 92 6 2 Frame RE Interfata se seges ae Ese cous AE GRA Re ese eke Be See VEG ee ESE ER eek bede eek Gee dees d 92 82 1 Data Mapping between the DH and RF eee sees see ee ee ee Se ee ee ee 92 8 2 2 Frame RF Interface specific Control MessageS esse ses see se se se ee ee 96 8 2 3 Poll side Frame RF Interface Management eee see se Ge Ge Ge ee ee 100 82 4 Listen side Frame RF Interface Management esse ese esse ee see se ee ee ee ee 100 NFC Controller Interface NCI Specification Page iii Contents 8 3 JISO DEP RE Interfaces oz se se see hn tela al eee 103 8 3 1 Data Mapping between the DH and RP eee sesse es ee ee ee ee Ge Ge 103 8 3 2 Poll side ISO DEP RF Interface Management ee esse esse esse ee se ee se ee se 104 8 3 3 Listen side ISO DEP RF Interface Management iese esse esse ee se ee se se 106 84 NEC DEP RF Interfaces uas Ee Ne Gee sn Ede ede Se ee Ge Re De E Se Ee ee Ee Ve Eg ee ee EE Ge se gee ie 108 8 4 1 Data Mapping between the DH and REF ee ese ese es ee ee ee Ge Ge 108 84 2 NFC DEP RF Interface Con
171. tails in Section 4 4 3 In case of unrecoverable transmission errors of a message between the NFCC and the NFCEE the NFCC SHALL send a CORE_INTERFACE_ERROR_NTF with the Status set to NFCEE_TRANSMISSION_ERROR 10 1 APDU NFCEE Interface 10 1 1 Data Exchange This communication will be the sending and receiving of APDU command response pairs using short messages lengths as described in Section 12 of ISO IEC_7816 3 That is L and L are coded on one byte The DH MAY send a Data Message to the NFCC according to Section 10 1 1 1 The NFCC will extract and send the Command APDU data contained in the payload of the Data Message s to the NFCEE When the NFCC receives Response APDU data from the NFCEE the NFCC SHALL populate the payload of a Data Message with the Response APDU and send the Data Message to the DH according to Section 10 1 1 2 NCI Segmentation and Reassembly MAY be applied to Data Messages in either direction The NFCC is responsible for managing the variances necessary for the communication and receipt of Command and Response APDUs between itself and the NFCEE and this SHALL be transparent to the DH and NCI NFC Controller Interface NCI Specification Page 121 NFCEE Interfaces 10 1 1 1 Format for Data Messages sent from DH to NFCC When receiving a Data Message from the DH the NFCC SHALL send the Data Message i e Command APDU to the NFCEE If a single Command APDU is split across multiple Data Packets th
172. ter is busy processing its FIFOs 11 3 2 3 Race Condition Since this is a half duplex interface there is a possibility that both master DH and slave NFCC would want to send data at the same time In such a race condition the master would deassert the SPI CSN at the same time as the slave would deassert the SPI_INT In such a situation the 2 octet header sent by the master determines the transaction type A consequence of this is that the slave SHALL only deassert SPI_INT when it is capable of receiving a maximum sized Direct Write command The two figures below illustrate such a scenario SPI_CSN SPLINT foo I SPI_CLK IDLE ACTIVE IDLE DirectWrite J Length y DirectWrite SPI_MOSI IDLE i od Mee Payload IDLE SPI_MISO TRISTATE Oorl TRISTATE Figure 29 SPI Race Condition 1 NFC Controller Interface NCI Specification Page 132 SPI CSN SPI_INT SPI_CLK SPI MOSI SPI_MISO Transport Mappings IDLE ACTIVE IDLE DirectRead V IDLE i A A bytes A Oorl A IDLE Length DirectRead TRISTATE Oorl 2 bytes Payload TRISTATE Figure 30 SPI Race Condition 2 NFC Controller Interface NCI Specification Page 133 Testing 12 Testing The Commands Responses and Notifications in this section provide mechanisms to facilitate testing 12 1 Local Loopback Mode The local loopback mode is used to verify that the NFCC can receive and loop
173. ter that the NFCC SHALL perform activation for the RF Protocol depending on the RF Technology or RF Interface associated with the parameters of the RF_DISCOVER_SELECT_CMD The specified RF Interface parameter value is only valid for the following RF Interface activation and does not cause any change to the RF Interface Mapping configuration see Section 6 2 7 3 RF Interface Activation and Deactivation The NFCC can activate an RF Interface either in RFST_DISCOVERY or RFST_W4_HOST_SELECT state by sending RF_INTF_ACTIVATED_NTF The RF_INTF_ACTIVATED_NTF SHALL cause the RF communication state to change to either RFST_POLL_ACTIVE or RFST_LISTEN_ACTIVE as described in Section 5 2 At most one RF Interface SHALL be active at any time 7 3 1 RF Interface Activation Notification This Notification is used by the NFCC to inform the DH that a specific RF Interface has been activated NFC Controller Interface NCI Specification Page 82 RF Discovery Table 61 Notification for RF Interface activation RF INTF ACTIVATED NTF Payload Field s Length Value Description RF Discovery ID 1 Octet See Table 53 RF Interface 1 Octet See Table 99 If this contains a value of 0x00 NFCEE Direct RF Interface then all following parameters SHALL contain a value of 0 and SHALL be ignored RF Protocol 1 Octet See Table 98 Activation RF 1 Octet RF Technology and Mode of the local device that were used Tec
174. ters Allowed values SHALL be from 0x00 to 0x10 Other values are RFU 2 Octets System Code as defined in T3TOP Idm n 8 Octets Idm as defined in T3TOP To discover whether one or more NFCEEs are connected to the NFCC the NFCEE_DISCOVER_CMD is sent by the DH to the NFCC with the Discovery Action of 0x01 NFC Controller Interface NCI Specification Page 117 NFCEE Discovery and Mode Set On receipt of the NFCEE DISCOVER CMD the NFCC SHALL respond to the DH with the NFCEE_DISCOVER_RSP with a Status of STATUS OK and a Number of NFCEEs indicating how many NFCEEs are connected to the NFCC a value of 0x00 indicates no connected NFCEEs 0x01 indicates 1 connected NFCEE etc If there is at least one NFCEE connected to the NFCC for each connected NFCEE the NFCC SHALL send a NFCEE_DISCOVER_NTF to the DH indicating the following e The unique NFCEE ID assigned by the NFCC to the NFCEE e The current NFCEE Status e Each NFCEE Protocol supported by the NFCEE e Zero or more NFCEE Information Records to provide additional information on the NFCEE NOTE NFCEE Protocols and NFCEE Interfaces have one to one mapping and values for these are defined in the common NOTE Table 100 If an NFCEE supports certain NFCEE Protocol s reported with NFCEE DISCOVER NTF then one of supported protocols may be used for communication between the DH and the NFCEE A creation of that communication channel is called NFCEE Interfa
175. the SEL_RES Response Length SHALL be 0x01 Other values are RFU SEL_RES Response 0 1 Octet Defined in DIGITAL Table 55 Specific Parameters for NFC A Listen Mode No parameters are currently defined Table 56 Specific Parameters for NFC B Poll Mode Parameter Length Description SENSB_RES Response 1 Octet Length of SENSB_RES Response Parameter Length Allowed values SHALL be OXOB and Ox0C Other values are RFU SENSB_RES Response 11 or 12 Byte 2 Byte 12 or 13 of SENSB_RES as Octets defined in DIGITAL Table 57 Specific Parameters for NFC B Listen Mode Parameter Length Description No parameters are currently defined NFC Controller Interface NCI Specification Page 80 RF Discovery Table 58 Specific Parameters for NFC F Poll Mode Parameter Length Description Bit Rate 1 Octet 1 212 kbps 2 424 kbps 0 and 3 to 255 RFU SENSF_RES Response 1 Octet Length of SENSF_RES Response Parameter Length Allowed values SHALL be 0x10 and 0x12 Other values are RFU SENSF_RES Response 16 or 18 Byte 2 Byte 17 or 19 of SENSE RES as Octets defined in DIGITAL Table 59 Specific Parameters for NFC F Listen Mode Parameter Length Description Local NFCID2 Length 1 Octet Length of Local NFCID2 Parameter If NFCID2 is available then Local NFCID2 Length SHALL be 0x08 If NFCID2 is not available then Local NFCID2 Le
176. then the DH NFCC is allowed to send If CTS is 0 then the DH NFCC is not allowed to send The RS232 signals SHOULD be connected in a null modem fashion i e the local TXD SHOULD be connected to the remote RXD and the local RTS SHOULD be connected to the remote CTS and vice versa NFC Controller Interface NCI Specification Page 126 Transport Mappings 11 2 12C Transport NCI Frames SHALL be transmitted over the C I2C between a DH and an NFCC with no additional framing Since there is no additional framing the I C transport cannot introduce any errors otherwise the NCI messages stream may be unrecoverable So the PC connection SHALL be of a sufficiently high quality as to provide a reliable data transfer at the configured transfer rate The DH SHOULD operate as a bus master and MAY also be able operate as a bus slave if addressed by another bus master The NFCC MAY operate as either bus master or slave In the latter case out of band means SHOULD be provided in order for the NFCC to request the DH to initiate a data transfer as a bus master However if out of band method is not available the DH SHALL poll frequently the NFCC Polling frequency is implementation specific The I2C transport SHOULD support standard up to 100kbps and Fast Speed mode up to 400kbps and MAY support Fast Mode Plus up to 1 Mbit s and High Speed mode up to 3 4Mbit s Additionally 10 bit addressing mode and clock stretching MAY be supp
177. tivation Type parameter stop the RF Discovery Process and send RF_DEACTIVATE_RSP The state will then change to RFST_IDLE 5 2 4 State RFST WA HOST SELECT The NFCC SHOULD keep the RF field ON while in this state In this state the NFCC has its greedy collection intact and is waiting for the DH to select one of the Remote NFC Endpoints from the greedy collection ACTIVITY to activate The greedy collection ACTIVITY may contain Remote NFC Endpoints that are in sleep state When the DH sends RF_DISCOVER_SELECT_CMD with a valid RF Discovery ID RF Protocol and RF Interface the NFCC SHALL try to activate the associated Remote NFC Endpoint depending on the state of the Remote NFC Endpoint The NFCC SHALL first establish any underlying protocol s with the Remote NFC Endpoint that are needed by the configured RF Interface On completion the NFCC SHALL activate the RF Interface and send RF INTE ACTIVATED NTF Poll Mode to the DH At this point the state is changed to RFST_POLL_ACTIVE NFC Controller Interface NCI Specification Page 51 RF Communication If the activation was not successful the NFCC SHALL send CORE GENERIC ERROR NTF to the DH with a Status of DISCOVERY_TARGET_ACTIVATION_FAILED and the state will remain as RFST_W4_HOST_SELECT If the DH sends RF_DEACTIVATE_CMD the NFCC SHALL ignore the Deactivation Type parameter stop the RF Discovery Process and send RF_DEACTIVATE_RSP The state will then change to RFST_IDLE 5 2 5
178. 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 if 7816 4 APDU commands are used on top of ISO DEP In addition NCI enables the DH to get informed if communication between an NFCEE and a Remote NFC Endpoint occurs NFC Controller Interface NCI Specification Page 22 NCI Core Framework 3 NCI Core Framework 3 1 Overview The NCI Core includes the following required functionality Packet formats to transmit Commands Responses Notification and Data Messages over NCI Definition of the Commands Responses and Notifications used for different operations as described in Section 4 between a Device Host and an NFC Controller Some subsequent sections in this specification define additional Commands Responses and Notifications that are not part of the NCI Core A flow control mechanism for Command Response Message exchange A Logical Connection concept for Data Messages A credit based flow control mechanism for Data Messages sent from the DH to the NFCC Segmentation and reassembly for Control and Data Messages An addressing scheme for NFC Execution Environments NFCEE The NCI Core supports communication between the DH and NFCEEs connected to the NFCC NOTE NCI only covers the link between a DH and an NFCC
179. to 0x00 the NFCC SHALL return all octets containing 0x00 The CORE INIT CMD is used by the DH to initialize the NFCC This Command SHALL be issued following indication that the NFCC has been successfully reset see Section 4 1 and at no other time On execution of the Command the NFCC SHALL send a CORE INIT RSP to inform the DH that the NFCC has executed the Command If the initialization was successful the Status SHALL be STATUS_OK If the NFCC is unable to execute the Command the Status SHALL be set to STATUS_FAILED see Table 94 and the other parameters of the CORE_INIT_RSP SHALL be ignored by the DH No other Command that is defined in this specification except for CORE_RESET_CMD or CORE INIT CMD SHALL be sent prior to the NFCC being successfully initialized Prior to initialization if the DH knows the manufacturer ID of the NFCC by some means outside the scope of NCI then proprietary Commands MAY be sent but otherwise they SHALL NOT be sent Following successful initialization proprietary Commands MAY be sent by the DH and proprietary Responses and Notifications MAY be sent by the NFCC After sending a CORE_INIT_CMD the DH SHALL discard any information that may have been previously provided by the NFCC concerning discovery requests from NFCEE s NFC Controller Interface NCI Specification Page 37 NCI Core Control Messages Table 9 NFCC Features Bit Mask Description b7 b6 b5 b4
180. tten notice or if the breach is of a nature that cannot be cured then Licensor may immediately or thereafter terminate the licenses granted in this Agreement 5 MISCELLANEOUS All notices required under this Agreement shall be in writing and shall be deemed effective five days from deposit in the mails Notices and correspondence to the NFC Forum address as it appears below This Agreement shall be construed and interpreted under the internal laws of the United States and the Commonwealth of Massachusetts without giving effect to its principles of conflict of law NFC Forum Inc 401 Edgewater Place Suite 600 Wakefield MA USA 01880 NFC Controller Interface NCI Specification Page i Contents Contents 1 TRO CUCU ON sesse Se es n ei ee ge Ge ek oo Ne ee ae WE GN US Ge EA Eed 9 LE ee RE ME AE OE RE OE AE ER EL ENG 9 L2 Oo N EE ER EE ON OE RE EI 9 1 3 AUGIENCEs EE EE eee ER aa N ee ee a ede Ee Ge Ve ee Ee Ge ee 10 1 4 Applicable Documents or References esse ses see se se ee ee ee ee Ge Ge GR ee ee 10 ESE Gie ie ee AI EE N AE N OE ER tt Gaede E TREENER EEEE 11 16 Narhe and logoUsage ESE GE e ED eg Ee ea teen De EE eee eee 12 1 77 Intellectual vide AO RE OR ER RE EER ER nee 12 1 87 Special Word USage si EER MS ee oe SE dele Lieto BE NG Gees 12 ER Vrees Ee ME EO EK e iea a 12 1 10 oa N EE N EE EE RE EE dete 14 1AL Codines Conventions re n eeaeee N OE EE OE EG 18 2 NCI Architecture sies sesse see es Ke ed RE
181. twork Specific Handling To enable or disable the HCI Network the DH SHALL send NFCEE_MODE_SET_CMD with the NFCEE ID set to that of the HCI Network If the NFCEE Mode field of the NFCEE_ MODE SET CMD is set to Enable the connected NFCEE the HCI Network is allowed to perform RF communication Therefore if they were not already activated the communication interfaces to the hosts of the HCI Network SHALL be activated If the HCI Access NFCEE Interface is already enabled while receiving the NFCEE MODE SET CMD the NFCC SHALL activate all communication interfaces to the hosts in the HCI Network some of these interfaces may have been deactivated before e g for power consumption reasons If the NFCEE Mode field of the NFCEE_ MODE SET CMD is set to Disable the connected NFCEE the HCI Network is not allowed to perform any further RF communication Therefore it MAY be no longer necessary to keep the communication interfaces to the hosts within the HCI Network activated Before disabling the HCI Network if the HCI Access NFCEE Interface was activated the DH SHALL deactivate it as described in Section 10 2 1 The enabled disabled state of the HCI Network SHALL be persistent in the NFCC including while the DH is switched off until a new NFCEE_MODE_SET_CMD is sent by the DH This includes across a reset and initialization of the NFCC NFC Controller Interface NCI Specification Page 120 NFCEE Interfaces 10 NFCEE Interfaces Th
182. uested in the CORE GET CONFIG CMD are available and the DH may initiate another CORE GET CONFIG CMD to retrieve those Parameters If CORE GET CONFIG RSP message payload size with all requested parameters would exceed the maximum Control Message payload size 255 octets then the NFCC SHALL only send the limited set of parameters that will not exceed the maximum payload size In this case the Status field SHALL have a value of STATUS MESSAGE SIZE EXCEEDED The DH MAY retrieve any unreturned parameters by sending another CORE_GET_CONFIG_CMD requesting only those specific IDs If both of these conditions happen 1 the DH tries to retrieve unavailable Parameters and 2 Response would exceed maximum Control Message payload size then case 1 has higher priority i e the NFCC SHALL return a status of STATUS_INVALID_PARAM to the DH 4 4 Logical Connection Management 4 4 1 Destination Type Destination Types are used during Logical Connection creation They identify the type of an entity in the system NFCC NFCEE or Remote NFC Endpoint Destination Types may also identify specific functionality within an entity like the loop back function within the NFCC Valid Destination Types are defined in Table 12 Table 12 Destination Types Destination Type Description 0x00 RFU 0x01 NECC Loop back This is used to create a Logical Connection between the DH and the NECC for loop back mode See Section 12 1 0x02 Remote NFC Endpoint
183. ults by using the CORE_SET_CONFIG_CMD before moving to state RFST_DISCOVERY NFC Controller Interface NCI Specification Page 112 RF Interfaces e Table 30 Discovery Configuration Parameters for Listen A The parameter LA_HIST_BY is not applicable when using this Interface e Table 39 Discovery Configuration Parameters for Listen NFC DEP When using this Interface the DH SHALL configure the parameters LA_SEL_INFO see Table 30 and LF_PROTOCOL_TYPE see Table 35 to indicate NFC DEP support When using this Interface the parameter LF CON BITR F SHALL be configured by the NFCC to the value 0x06 The NFCC SHALL reject any other configuration for this parameter as long as this Interface is mapped to the NFC DEP protocol 8 4 4 2 Discovery and Interface Activation To enable Listen Mode for NFC DEP the DH sends the RF_DISCOVER_CMD to the NFCC containing configurations with RF Technology and Mode values of NFC_A_PASSIVE_LISTEN_MODE and or NFC_F_PASSIVE_LISTEN_MODE When the NFCC is ready to exchange data with the DH that is after successful protocol activation it SHALL send the RF_INTF_ACTIVATED_NTF to the DH to indicate that the NFC DEP protocol has been activated as follows Following the anticollision sequence and when an ATR_REQ has been received from the Remote NFC Endpoint the NFCC SHALL send an ATR_RES to the Remote NFC Endpoint with LN_ATR_RES_GEN_BYTES configured during Discovery Configuration but then wait until it receive
184. ut e After sending a Command the DH SHALL be able to receive a Response e After sending a Response the NFCC SHALL be ready to receive the next Command from the DH e The DH SHALL be able to receive a Notification from the NFCC at any time 3 2 2 Exception Handling for Control Messages The rules in this section define the exception processing to be performed by a receiver of an erroneous Control Message Any Command received by the DH SHALL be ignored Any Response or Notification received by the NFCC SHALL be ignored In the case of a Control Message with syntax errors meaning that the coding of the Control Packet is not consistent with this specification and where the receiver can still determine the type of the Control Message e Ifthe Control Message is a Command the NFCC SHALL ignore the content of the Command and send a Response with the same GID and OID as in the Command and with a Status value STATUS_SYNTAX_ERROR The Response SHALL NOT contain any additional fields e Ifthe Control Message is a Response the DH SHALL ignore the content of the Response and is free to send another Command e Ifthe Control Message is a Notification the DH SHALL ignore the Notification In case of a Control Message with a semantic error meaning that a Control Message with valid syntax is received when it is not expected e Anunexpected Response or Notification SHALL be ignored by the DH e Anunexpected Command SHALL NOT cause any act
185. wever any higher layer protocol e g LLCP exchange must be handled on the DH The following Protocols can be mapped to this Interface see Section 6 2 PROTOCOL_NFC_DEP 8 4 1 Data Mapping between the DH and RF The DH and the NFCC SHALL only use the Static RF Connection for data communication with a Remote NFC Endpoint NCI Segmentation and Reassembly MAY be applied to Data Messages in either direction NFC Controller Interface NCI Specification Page 108 RF Interfaces 8 4 1 1 Data from the DH to RF When receiving a Data Message from the DH the NFCC SHALL send the payload data contained in the Data Message as an information PDU transferred within the Transport Data Bytes of one or a chained series of DEP_REQ commands if the NFCC is an NFC DEP Initiator or DEP_RES responses if the NFCC is an NFC DEP Target to the Remote NFC Endpoint using the activated technology The last octet of a Data Packet with Packet Boundary Flag set to Ob SHALL be the last byte of the Transport Data Bytes of the DEP_REQ or DEP_RES frame not indicating chaining sent by the NFCC to the Remote NFC Endpoint Figure 19 illustrates the mapping between the Data Packet and the NFC DEP DEP REO frame when sending a frame to the Remote NFC Endpoint NOTE This figure shows the case where NCI Segmentation and Reassembly feature is not used However NFC DEP chaining is used where one Data Message is sent with multiple DEP_REQ frames to the Remote NFC Endpoint
186. when using the Frame RF Interface NFC Controller Interface NCI Specification Page 57 RF Communication Configuration Table 25 Values for PB SENSB REG PARAM Bit Mask Description b7 b6 b5 b4 b3 b2 b1 b0 Octet0 O JO RFU X If set to 1b the NFCC SHALL indicate support for advanced features in an ALLB_REQ or SENSB_REQ otherwise it SHALL NOT indicate support X If set to 1b the NFCC SHALL indicate support for extended SENSB RES in an ALLB_REQ or SENSB_REQ otherwise it SHALL NOT indicate support O JO JO JO Will be set by the NFCC independently of what is configured by DH 6 1 3 Poll F Parameters Table 26 Discovery Configuration Parameters for Poll F ID Length Value Description PF_BIT_RATE 1 Octet 1 2 The initial bit rate Value coding refer to Table 97 Default 0x01 PF_RC_CODE 1 Octet 0 2 Value of RC to use in SENSF_REQ as defined in DIGITAL Default 0x00 NFC Controller Interface NCI Specification Page 58 RF Communication Configuration 6 1 4 Poll ISO DEP Parameters Table 27 Discovery Configuration Parameters for ISO DEP ID Length Value Description PB_H_INFO O n Octets Higher layer INF field of the ATTRIB Command as defined in DIGITAL Default empty NFCC will send ATTRIB Command without Higher Layer INF field PI BIT RATE 1 Octet 0 3 Maximum allowed bit rate Default 0x00 106 Kbit s F
187. which is not understood by the NFCC but just passed without modification NFC Controller Interface NCI Specification Page 124 NFCEE Interfaces 10 4 1 Data Exchange The DH MAY send Data Messages on such a connection to the NFCC for transmission to the NFCEE The NFCC SHALL extract and forward the payload of the Data Messages in the appropriate message format directly to the NFCEE without any modification When the NFCC receives a message from the NFCEE the NFCC SHALL extract the data from the message populate it to the payload of a Data Message and send the Data Message to the DH on the relevant connection The mechanism used to transmit such data between the NFCC and the NFCEE is implementation specific The NFCC is responsible for managing the variances necessary for the communication between itself and the NFCEE and this SHALL be transparent to the DH and NCI NCI Segmentation and Reassembly MAY be applied to Data Messages in either direction NFC Controller Interface NCI Specification Page 125 Transport Mappings 11 Transport Mappings The NCI Core design is intended to be independent of any specific underlying transport layer or its speed The following are reguirements for any underlying Transport Mapping e Transport Mappings SHALL provide means to transport Data and Control Packets in both directions between the DH and NFCC e Transport Mappings SHALL provide a reliable data transfer e Transport Mappings

NFC Controller Interface Specification

Contents

Download Pdf Manuals

Related Search

Related Contents