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: 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: 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: A method, an apparatus, and a computer program product for wireless communication are provided in connection with providing efficient SE functionality. In one example, a communications device includes a SE which includes a processor, RAM, and NVM, and secured and unsecured components. The SE may be equipped to receive a request to access a function that is accessible through information stored in the SE, retrieve a first portion of the information associated with the function that is stored in the secured component, obtain a second portion of the information associated with the function that is stored in the unsecured component, and facilitate access to the function using the first retrieved portion of the information to enable access to the second obtained portion of the information. In an aspect, the secured component may include the processor and the RAM, and the unsecured component may include substantially all of the NVM.

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: An operating system, comprising a first component including a first protocol stack configured to process data packets of a first type, wherein the first component is initialized independently of other components in the operating system, a second component including a second protocol stack configured to process data packets of a second type, wherein the second component is initialized independently of the other components in the operating system, and a third component configured to receive data packets of the first type and the second type and direct the data packets of the first type to the first component and the data packets of the second type to the second component.

Abstract: An operating system, comprising a first component including a first protocol stack configured to process data packets of a first type, wherein the first component is initialized independently of other components in the operating system, a second component including a second protocol stack configured to process data packets of a second type, wherein the second component is initialized independently of the other components in the operating system, and a third component configured to receive data packets of the first type and the second type and direct the data packets of the first type to the first component and the data packets of the second type to the second component.