Abstract: A mobile network gateway receives, from a user equipment device (UE), a session request for a session between the UE and an application hosted by a hosting device, where the session request includes an application identifier (ID) associated with the application. The mobile network gateway identifies a network slice of a mobile network based on the application ID and an ID associated with the UE, and retrieves a security profile from memory based on the application ID and the identified network slice. The mobile network gateway establishes a secure tunnel between the gateway and the hosting device using the retrieved security profile, and forwards data units associated with the requested session between the UE and the hosting device via the secure tunnel.

Abstract: One or more computing devices, systems, and/or methods for data fragmentation and reconstruction are provided. Random number generation information, indicating a number of fragments into which data stored by a client device is to be fragmented, is received. The data is fragmented according to the number of fragments as a set of fragments. Authentication data is incorporated with the set of fragments. A set of entities capable of storing the set of fragments with the authentication data is identified. The set of fragments with the authentication data are stored across the set of entities.

Abstract: An improved cellular network architecture enables the provisioning of mobile profiles on devices lacking bootstrap profiles. A mobile device transmits an attach request that includes a pre-configured mobile country code (MCC) and mobile network code (MNC) uniquely associated with an emergency data session. The mobile device is then null-authenticated with a subscriber database, and an emergency data session is established, the emergency data session allowing traffic to a mobile profile manager. The mobile device can then download a mobile profile from the mobile profile using the emergency data session. Thus, a mobile device does not require a provisioning profile to download a full (or provisioning) mobile profile from a cellular network as in existing solutions.

Abstract: A first user device may provide, to a provisioning device, a request for a subscriber identity module (SIM) swap that causes provisioning data to be provided to a first SIM card of the first user device and from a second SIM card of a second user device. The first user device may generate a first encrypted token based on a first identifier associated with the first SIM card. The first user device may provide, to the provisioning device, the first encrypted token and a user identifier. The first user device may selectively receive the provisioning data when the first encrypted token matches a second encrypted token generated by the second user device based on a second identifier associated with the second SIM card, or receive a message indicating that the first user device cannot be provisioned, when the first encrypted token fails to match the second encrypted token.

Abstract: A user device may invoke, for a user associated with an unavailable user device, a guest mode, and may connect the user device with a network device based on invoking the guest mode. The user device may provide credentials of the user and a secure input of the user to the network device based on invoking the guest mode, and may receive an identity service and an emergency service for the user when the secure input is authenticated by the network device. The user device may associate, via the identity service, the user with the user device to enable the user to utilize the emergency service, and may provide, via the emergency service, one or more emergency notifications. The user device may receive an indication of the user exiting the guest mode, and may remove the credentials of the user from a memory based on the indication.

Abstract: A mobile network gateway receives, from a user equipment device (UE), a session request for a session between the UE and an application hosted by a hosting device, where the session request includes an application identifier (ID) associated with the application. The mobile network gateway identifies a network slice of a mobile network based on the application ID and an ID associated with the UE, and retrieves a security profile from memory based on the application ID and the identified network slice. The mobile network gateway establishes a secure tunnel between the gateway and the hosting device using the retrieved security profile, and forwards data units associated with the requested session between the UE and the hosting device via the secure tunnel.

Abstract: A device within a small cell may establish a first secure communication channel between the device and a network device based on a first type of encryption. The device within the small cell may transmit data between the small cell and a core network via the first secure communication channel. The device within the small cell may receive information associated with a second type of encryption, wherein the second type of encryption is different from the first type of encryption. The device within the small cell may terminate the first secure communication channel. The device within the small cell may establish a second secure communication channel between the device and the network device based on the information associated with the second type of encryption. The device within the small cell may transmit further data between the small cell and the core network via the second secure communication channel.

Abstract: Communicating via near field communication (NFC) between a reader and an application on an NFC-enabled device. The device receives, from a reader, a selection of an application identifier (AID) proxy of the device. The proxy receives, from the reader, a query (including domain name) directed to the availability of an application on the device. The proxy determines whether the domain name corresponds to an AID of an application on the device by reference to a data store relating each domain name of each application to a corresponding AID. When the domain determined to correspond to an AID of an application on the device, the device transmits a response to the reader indicating the AID corresponding to the domain name. The device receives, from the reader, selection of the transmitted AID. The application corresponding to selected AID communicates with the reader in an NFC application protocol data unit communication session.

Abstract: Communicating via near field communication (NFC) between a reader and an application on an NFC-enabled device. The device receives, from a reader, a selection of an application identifier (AID) proxy of the device. The proxy receives, from the reader, a query (including domain name) directed to the availability of an application on the device. The proxy determines whether the domain name corresponds to an AID of an application on the device by reference to a data store relating each domain name of each application to a corresponding AID. When the domain determined to correspond to an AID of an application on the device, the device transmits a response to the reader indicating the AID corresponding to the domain name. The device receives, from the reader, selection of the transmitted AID. The application corresponding to selected AID communicates with the reader in an NFC application protocol data unit communication session.

Abstract: Communicating via near field communication (NFC) between a reader and an application on an NFC-enabled device. The device receives, from a reader, a selection of an application identifier (AID) proxy of the device. The proxy receives, from the reader, a query (including domain name) directed to the availability of an application on the device. The proxy determines whether the domain name corresponds to an AID of an application on the device by reference to a data store relating each domain name of each application to a corresponding AID. When the domain determined to correspond to an AID of an application on the device, the device transmits a response to the reader indicating the AID corresponding to the domain name. The device receives, from the reader, selection of the transmitted AID. The application corresponding to selected AID communicates with the reader in an NFC application protocol data unit communication session.

Abstract: Communicating via near field communication (NFC) between a reader and an application on an NFC-enabled device. The device receives, from a reader, a selection of an application identifier (AID) proxy of the device. The proxy receives, from the reader, a query (including domain name) directed to the availability of an application on the device. The proxy determines whether the domain name corresponds to an AID of an application on the device by reference to a data store relating each domain name of each application to a corresponding AID. When the domain determined to correspond to an AID of an application on the device, the device transmits a response to the reader indicating the AID corresponding to the domain name. The device receives, from the reader, selection of the transmitted AID. The application corresponding to selected AID communicates with the reader in an NFC application protocol data unit communication session.