Abstract: Methods, systems, computer-readable media, and apparatuses for providing anti-rollback protection in a device which has no internal non-volatile memory are presented. One embodiment is a device for providing anti-rollback protection. The device may obtain a firmware version number associated with a first firmware installation for the device, wherein the device is implemented on a substrate that includes no non-volatile memory. The device may obtain a lowest acceptable firmware version number, wherein the lowest acceptable firmware version number is stored in a secure element environment, wherein the secure element environment utilizes memory separated from the substrate. The device may compare the firmware version number and the lowest acceptable firmware version number, wherein if the firmware version number is less than the lowest acceptable firmware version number, then disallow the first firmware installation.

Abstract: Aspects disclosed herein relate to improving technology detection and collision resolution among multiple NFC devices using a NFC type-A RF technology. In one example, a communications device is equipped to determine that a first device sensing response message includes one or more collisions, identify a first remote NFC device of the plurality of remote NFC devices by performing collision resolution on the first device sensing response message, transmit a sleep request message to the first remote NFC device that prohibits the first remote NFC device from responding to a first device sensing request message and the first device sensing request message, receive a second device sensing response message that includes collisions among the plurality of remote NFC devices, and identify a second remote NFC device of the plurality of remote NFC devices by performing collision resolution on the second device sensing response message.

Abstract: Aspects disclosed herein relate to partitioning LLCP responsibilities between the NFCC and DH. In an example, with a NFC device a DH maybe configured to establish a LLCP link with a remote NFC endpoint through a NFCC, and partition LLCP related responsibilities between the DH and the NFCC when the NFCC is operable for LLCP split communications. Further, the NFCC may be operable to receive a PDU from a remote NFC endpoint, determine whether the received PDU is a SYMM PDU or a link deactivation PDU, and communicate the received PDU to a DH upon a determination that the received PDU is not a SYMM PDU or a link deactivation PDU.

Abstract: Disclosed are methods, apparatus, systems, computer program products, and other implementations, including a method that includes determining a source from which routing table information is to be obtained based, at least in part, on location data indicating the source, and receiving configuration information from a device host (DH). The method also includes removing DH-based routing table information included in the configuration information in response to the location data indicating that a near-field communication controller (NFCC) is configured to receive the routing table information from one or more secure computing environments or from the DH, and obtaining secure routing table information from at least one of the one or more secure computing environments.

Abstract: Aspects relate to improving reporting NFC RF technology usage in activation and data exchange for NFC devices. For example, with a near field communication (NFC) device, a NFCC may be configured to obtain a first radio frequency (RF) technology and mode value, a second RF technology and mode value, and one or more RF specific parameters associated with a NFC device during an activation phase of a communication link using a first NFC RF technology. The one or more RF specific parameters may be based on the first RF technology and mode value. Further, the NFCC may be configured to configure communications to be supported by a second NFC RF technology for use during a data exchange phase of the communication link. The second NFC RF technology may be based on the second RF technology and mode value.

Abstract: Aspects relate to improved mechanisms for updating parameter values for communications between a DH and a remote NFC endpoint. In one example, a DH associated with a NFC device may be configured to determine that one or more parameter values included in a parameter selection request message are different than one or more corresponding parameter values used during discovery of a remote NFC endpoint using a frame RF interface, and communicate the parameter values to a NFC Controller using a parameter update message. A NFCC associated with a NFC device may be configured to receive, using a NFC-DEP interface, a parameter selection request message including one or more parameters, determine to implement one or more parameter changes based on the received one or more parameters, and communicate an activation message to a DH indicating values to which the NFC Controller changed the one or more parameter values.

Abstract: Aspects relate to improving reporting NFC RF technology usage in activation and data exchange for NFC devices. For example, with a near field communication (NFC) device a NFCC may be configured to obtain a first radio frequency (RF) technology and mode value, a second RF technology and mode value, and one or more RF specific parameters associated with a NFC device during an activation phase of a communication link using a first NFC RF technology. The one or more RF specific parameters and the first NFC RF technology may be based on the first RF technology and mode value. Further, the NFCC may be configured to configure communications to be supported by a second NFC RF technology for use during a data exchange phase of the communication link. The second NFC RF technology may be based on the second RF technology and mode value.

Abstract: The present application presents example data routing methods and apparatuses for reducing the amount of nonvolatile memory required to store secure element application locations associated with a near-field communications device. For example, the present disclosure presents a method of communication routing in a near-field communication device, which can include receiving, at a near-field communications controller (NFCC), a routing request message (e.g. from a requesting device), wherein the routing request message includes an original application identifier (AID) associated with an application. The example method may also include generating a compressed AID by applying a hash function to the original AID, reading an entry corresponding to the compressed AID in a routing data structure, wherein the entry contains one or more secure element pointers associated with one or more secure elements, and querying at least one of the secure elements to determine whether each contains the application.

Abstract: Methods, systems, computer-readable media, and apparatuses for providing anti-rollback protection in a device which has no internal non-volatile memory are presented. One embodiment comprises of a device for providing anti-rollback protection. The device may obtain a firmware version number associated with a first firmware installation for the device, wherein the device is implemented on a substrate that includes no non-volatile memory. The device may obtain a lowest acceptable firmware version number, wherein the lowest acceptable firmware version number is stored in a secure element environment, wherein the secure element environment utilizes memory separated from the substrate.

Abstract: Disclosed are methods, apparatus, systems, computer program products, and other implementations, including a method that includes determining a source from which routing table information is to be obtained based, at least in part, on location data indicating the source, and receiving configuration information from a device host (DH). The method also includes removing DH-based routing table information included in the configuration information in response to the location data indicating that a near-field communication controller (NFCC) is configured to receive the routing table information from one or more secure computing environments or from the DH, and obtaining secure routing table information from at least one of the one or more secure computing environments.

Abstract: Various aspects include methods and devices for aggregating a number of micro-payment transactions within a secure memory of a purchaser's computing device to enable completion of micropayment electronic commerce transactions with reduce the number of fund transfers and verification messages. Transactions in which a purchaser pays a micropayment (i.e., <$1.00) are aggregated over time in a purchaser's computing device. Eventually accumulated transaction information is downloaded to a trusted payment authority for settlement. The trusted payment authority pays the merchant for all aggregated transactions in a single funds transfer. Transactions among many purchasers may also be aggregated into a single funds transfer. By aggregating micropayments within the purchaser's computing device, the amount of money involved in transactions processed through the payment authority can become large enough to justify the transactions costs of exchanging money between the purchaser and various merchants.

Abstract: Aspects disclosed herein relate to providing improved mechanisms for updating parameter values for communications between a DH and a remote NFC endpoint. In one example, a DH associated with a NFC device may be configured to determine that one or more parameter values included in a parameter selection request message are different than one or more corresponding parameter values used during discovery of a remote NFC endpoint using a frame RF interface, and communicate the parameter values to a NFC Controller using a parameter update message. In another example, a NFCC associated with a NFC device may be configured to receive, using a NFC-DEP interface, a parameter selection request message including one or more parameters, determine to implement one or more parameter changes based on the received one or more parameters, and communicate an activation message to a DH indicating values to which the NFC Controller changed the one or more parameter values.

Abstract: Aspects relate to improving reporting NFC RF technology usage in activation and data exchange for NFC devices. For example, with a near field communication (NFC) device a NFCC may be configured to obtain a first radio frequency (RF) technology and mode value, a second RF technology and mode value, and one or more RF specific parameters associated with a NFC device during an activation phase of a communication link using a first NFC RF technology. The one or more RF specific parameters and the first NFC RF technology may be based on the first RF technology and mode value. Further, the NFCC may be configured to configure communications to be supported by a second NFC RF technology for use during a data exchange phase of the communication link. The second NFC RF technology may be based on the second RF technology and mode value.