Abstract: A method, a device, and a non-transitory storage medium are described in which a security service of end device profiles is provided. The service may include obtaining a profile for a card of an end device from a third party device in which the profile includes first and second executables. For example, the first and second executables may each include a subscriber identification module. The first executable may initialize and subsequently perform a switching procedure that enables the second executable to replace the use of the first executable. The first executable may also generate a key that can be used to provision the second executable on the end device.

Abstract: A user equipment (UE) may receive, from a certificate authority, a first onboarding identifier associated with a private key stored on the UE. The UE may transmit, to a wireless network, an attach request based on the first onboarding identifier. The UE may receive, from the wireless network, a signaling message that includes a second onboarding identifier, wherein the signaling message may be encrypted with a public key paired with the private key stored on the UE. The UE may decrypt the signaling message using the private key stored on the UE to obtain the second onboarding identifier. The UE may obtain a permanent identifier from a Remote SIM Provisioning platform based on the UE completing an authentication procedure using an authentication response obtained from the decrypted signaling message. The UE may then connect to the wireless network using the permanent identifier.

Abstract: A user equipment (UE) may receive, from a certificate authority, a first onboarding identifier associated with a private key stored on the UE. The UE may transmit, to a wireless network, an attach request based on the first onboarding identifier. The UE may receive, from the wireless network, a signaling message that includes a second onboarding identifier, wherein the signaling message may be encrypted with a public key paired with the private key stored on the UE. The UE may decrypt the signaling message using the private key stored on the UE to obtain the second onboarding identifier. The UE may obtain a permanent identifier from a Remote SIM Provisioning platform based on the UE completing an authentication procedure using an authentication response obtained from the decrypted signaling message. The UE may then connect to the wireless network using the permanent identifier.

Abstract: A user equipment (UE) may receive, from a certificate authority, a first onboarding identifier associated with a private key stored on the UE. The UE may transmit, to a wireless network, an attach request based on the first onboarding identifier. The UE may receive, from the wireless network, a signaling message that includes a second onboarding identifier, wherein the signaling message may be encrypted with a public key paired with the private key stored on the UE. The UE may decrypt the signaling message using the private key stored on the UE to obtain the second onboarding identifier. The UE may obtain a permanent identifier from a Remote SIM Provisioning platform based on the UE completing an authentication procedure using an authentication response obtained from the decrypted signaling message. The UE may then connect to the wireless network using the permanent identifier.

Abstract: Requests for location fix for a mobile device, received from one or more Location Based Service (LBS) applications are queued in a queue in the mobile device. Based on information in a first queued request, the mobile device runs a location engine in a first fix mode to obtain a location fix for the mobile device, for a response to the first request. While the location engine is running to obtain the fix for the response to the first request, the mobile device analyzes information in a second queued request, to determine a second fix mode for response to the second request. Based on a comparison of the first and second fix modes, the mobile device may change the information in the second request to correspond to the first fix mode, before output of the second request from the queue to the location engine.

Abstract: Requests for location fix for a mobile device, received from one or more Location Based Service (LBS) applications are queued in a queue in the mobile device. Based on information in a first queued request, the mobile device runs a location engine in a first fix mode to obtain a location fix for the mobile device, for a response to the first request. While the location engine is running to obtain the fix for the response to the first request, the mobile device analyzes information in a second queued request, to determine a second fix mode for response to the second request. Based on a comparison of the first and second fix modes, the mobile device may change the information in the second request to correspond to the first fix mode, before output of the second request from the queue to the location engine.

Abstract: Requests for location fix for a mobile device are received from one or more Location Based Service (LBS) applications. The received requests are queued in a First In First Out (FIFO) queue in the mobile device. Based on information in a first request out of the FIFO queue, the mobile device runs a location engine in a first fix mode to obtain a fix on the location of the mobile device for a response to the first request. While the location engine is running to obtain the fix for the response to the first request, the mobile device analyzes information in a second request in the FIFO queue, to determine a second fix mode for response to the second request. Based on a comparison of the second fix mode to the first fix mode, the mobile device may change the information in the second request to correspond to the first fix mode, before output of the second request from the FIFO queue to the location engine.