Abstract: The techniques provide a wireless communication carrier with the ability to directly initiate a subscription management service to perform profile state changes with respect to eSIM profile states that are maintained by the subscription management service. A profile transition request is received from an entity at an eSIM management platform. The profile transition request includes a profile state change for an eSIM profile from a first profile state to a second profile state. The requested profile state change is validated using a validation table of permissible profile state changes that is common to the eSIM management platform and the subscription management service. The profile transition request is sent to the subscription management service in response to the validation of the profile state change.

Abstract: A download order message is received from a business support function of a wireless communication carrier. The download order message is for initiating a preparation of an unpopulated eSIM profile for downloading to an EUICC on a user device. The unpopulated eSIM profile is an eSIM profile that lacks pre-populated profile metadata. A metadata provision value is extracted from the download order message. The metadata provision value is compared to a mapping table that maps profile metadata provision values to corresponding combinations of one or more metadata element values. Accordingly, a combination of one or more profile metadata element values for the unpopulated eSIM profile is identified based on the comparison of the metadata provision value to the mapping table. The combination of one or more profile metadata element values is then populated into the unpopulated eSIM profile to generate a populated eSIM profile.

Abstract: The disclosed system provides for machine-to-machine routing of messages (e.g., text messages, binary information, etc.) between devices (e.g., external applications, IoT devices, etc.) using non-routable identifiers. The systems and methods publish an application programming interface (API) configured to receive (non-routable) identification information of a target device from an external application (e.g., an IoT Service Provider) that calls the API, determines whether a target device associated with the identification information is a subscriber of a telecommunications service provider that provides telecommunications plans to subscribers of the telecommunications service provider, verifies that the external application is authorized to transmit messages to the target device, and translates the non-routable identification information to a mapped device address that can be used to determine a location of the target device so that the message can be delivered to the target device.

Abstract: A request to initiate a performance of an operation on an embedded subscriber identity module (eSIM) profile stored in an embedded universal integrated circuit card (eUICC) of a machine-to-machine (M2M) device is sent from a backend service of a wireless communication carrier to a subscription management service. A callback message is then received at the backend service from the subscription management service indicating that the operation is performed on the eSIM profile, in which the callback message including an eUICC identifier (ID) of the eUICC or an Integrated Circuit Card identifier (ICCID) of the eSIM profile. A profile state entry of the eSIM profile is locate via the backend service in an eSIM profile state database. The profile state entry of the eSIM profile is then updated via the backend service in the eSIM profile state database with an updated profile state of the eSIM profile after the operation.

Abstract: One or more consumer Embedded Subscriber Identity Module (eSIM) profiles that are provided by at least one eSIM profile vendor may be received at a subscription management service of a wireless communication carrier. The one or more consumer eSIM profiles are loaded into a Subscription Manager Data Preparation Plus (SM-DP+) profile data store of the subscription management service, each consumer eSIM profile for deployment to an eUICC in a consumer device. At least one corresponding Integrated Circuit Card identifier (ICCID) of the one or more consumer eSIM profiles as loaded into the SM-DP+ data store is then sent via the subscription management service to an eSIM profile management platform of the wireless communication carrier using a service data feed, in which the eSIM profile management platform provides a central interface for a plurality of entities to perform actions with respect to multiple eSIM profiles and multiple eUICC Identifiers (EIDs).

Abstract: The disclosed system provides for machine-to-machine routing of messages (e.g., text messages, binary information, etc.) between devices (e.g., external applications, IoT devices, etc.) using non-routable identifiers. The systems and methods publish an application programming interface (API) configured to receive (non-routable) identification information of a target device from an external application (e.g., an IoT Service Provider) that calls the API, determines whether a target device associated with the identification information is a subscriber of a telecommunications service provider that provides telecommunications plans to subscribers of the telecommunications service provider, verifies that the external application is authorized to transmit messages to the target device, and translates the non-routable identification information to a mapped device address that can be used to determine a location of the target device so that the message can be delivered to the target device.

Abstract: The techniques provide a wireless communication carrier with the ability to directly initiate a subscription management service to perform profile state changes with respect to eSIM profile states that are maintained by the subscription management service. A profile transition request is received from an entity at an eSIM management platform. The profile transition request includes a profile state change for an eSIM profile from a first profile state to a second profile state. The requested profile state change is validated using a validation table of permissible profile state changes that is common to the eSIM management platform and the subscription management service. The profile transition request is sent to the subscription management service in response to the validation of the profile state change.

Abstract: A command is sent for a machine-to-machine (M2M) device to perform an operation on an embedded subscriber identity module (eSIM) profile stored in an embedded universal integrated circuit card (eUICC) of the M2M device. The operation is request by a backend service of a wireless communication carrier. A confirmation message is then received from the M2M device indicating that the operation on the eSIM profile is performed. Accordingly, a callback message is sent to the backend service of the wireless communication carrier indicating that the operation is performed. The callback message includes an eUICC identifier (ID) of the eUICC or an Integrated Circuit Card identifier (ICCID) of the eSIM profile. The eUICC ID or the ICCID is used by the backend service to locate a profile state entry of the eSIM profile in an eSIM profile state database for update with a profile state of the eSIM profile.

Abstract: Service data feeds that indicate multiple Embedded Subscriber Identity Module (eSIM) profiles provided by one or more eSIM profile vendor are loaded into one or more profile data stores of a subscription management service may be received from the subscription management service. The profile data stores may include a Subscription Manager Data Preparation (SM-DP) profile data store or a Subscription Manager Data Preparation Plus (SM-DP+) profile data store. A request is then received from an entity to perform an action with respect to a particular eSIM profile that has a specific Integrated Circuit Card identifier (ICCID). The request is forwarded to the subscription management service in response to determining that the specific ICCID matches an ICCID of an eSIM profile that is indicated by a service data feed as being loaded into a profile data store of the subscription management service. Accordingly, the subscription management service may implement the action with respect to the particular eSIM profile.

Abstract: A notification is received from a user device indicating that an embedded subscriber identity module (eSIM) profile is deleted from an embedded universal integrated circuit card (eUICC) of the user device, in which the eUICC has a particular eUICC identifier (ID). The profile state of the eSIM profile is transitioned from a state of in use to a state of suspended. A billing function is then notified that the eSIM profile is deleted from the eUICC of the user device and the suspended state of the eSIM profile. If the billing function determines that the eSIM profile is active for billing a subscriber for telecommunication services, the profile state of the eSIM profile is transitioned from suspended to released for reuse solely by the eUICC with the particular eUICC ID. However, if the billing function determines that the eSIM profile is inactive, the profile state of the eSIM profile is transitioned from suspended to available for use by any eUICC.

Abstract: The pairing of an entity solely to a single subscription management service may simplify the deployment of an Embedded Subscriber Identity Module (eSIM) profile management platform. The pairing includes selecting a subscription management service as a sole provider of eSIM profile management to an entity. The subscription management service may be provided by one or more subscription managers that execute on one or more computing devices, the one or more subscription managers including at least one of a Subscription Manager Data Preparation (SM-DP) or a Subscription Manager Secure Routing (SM-SR). Subsequently, the entity is mapped solely to the subscription management service to configure the eSIM management platform to route profile management communications for the entity between the entity and the subscription management service.

Abstract: This disclosure describes a local profile assistant (LPA) client hosted application that connects to an LPA interface module hosted in the core network and that exposes SIM profile management functionality. When end users are able to obtain validation of a secure connection, the end users can request for modification of their eSIM settings and profiles locally using the LPA client and via the LPA interface module to receive the modification over the air. Additionally, local eSIM management can be enabled by providing an open application programming interface (API) on the server in the core network, wherein the API would operate in concert with the LPA client.

Abstract: The pairing of an entity solely to a single subscription management service may simplify the deployment of an Embedded Subscriber Identity Module (eSIM) profile management platform. The pairing includes selecting a subscription management service as a sole provider of eSIM profile management to an entity. The subscription management service may be provided by one or more subscription managers that execute on one or more computing devices, the one or more subscription managers including at least one of a Subscription Manager Data Preparation (SM-DP) or a Subscription Manager Secure Routing (SM-SR). Subsequently, the entity is mapped solely to the subscription management service to configure the eSIM management platform to route profile management communications for the entity between the entity and the subscription management service.

Abstract: The disclosed system provides for machine-to-machine routing of messages (e.g., text messages, binary information, etc.) between devices (e.g., external applications, IoT devices, etc.) using non-routable identifiers. The systems and methods publish an application programming interface (API) configured to receive (non-routable) identification information of a target device from an external application (e.g., an IoT Service Provider) that calls the API, determines whether a target device associated with the identification information is a subscriber of a telecommunications service provider that provides telecommunications plans to subscribers of the telecommunications service provider, verifies that the external application is authorized to transmit messages to the target device, and translates the non-routable identification information to a mapped device address that can be used to determine a location of the target device so that the message can be delivered to the target device.

Abstract: An on-boarding management entity may be implemented to manage interconnectivity among various enterprise entities and various subscription managers. A subscription manager identifier associated with each of the subscription managers may be used to map different enterprise entities to specific or range of subscription managers. In the event of additions or replacements of subscription managers, a business logic may be employed via a rules engine in order to internally map a subscription manager identifier of the desired subscription manager to the respective subscription manager. The business logic can also be employed to map and relay callbacks and notifications received from the subscription managers to respective enterprise entities.

Abstract: A command is sent for a machine-to-machine (M2M) device to perform an operation on an embedded subscriber identity module (eSIM) profile stored in an embedded universal integrated circuit card (eUICC) of the M2M device. The operation is request by a backend service of a wireless communication carrier. A confirmation message is then received from the M2M device indicating that the operation on the eSIM profile is performed. Accordingly, a callback message is sent to the backend service of the wireless communication carrier indicating that the operation is performed. The callback message includes an eUICC identifier (ID) of the eUICC or an Integrated Circuit Card identifier (ICCID) of the eSIM profile. The eUICC ID or the ICCID is used by the backend service to locate a profile state entry of the eSIM profile in an eSIM profile state database for update with a profile state of the eSIM profile.

Abstract: A notification is received from a user device indicating that an embedded subscriber identity module (eSIM) profile is deleted from an embedded universal integrated circuit card (eUICC) of the user device, in which the eUICC has a particular eUICC identifier (ID). The profile state of the eSIM profile is transitioned from a state of in use to a state of suspended. A billing function is then notified that the eSIM profile is deleted from the eUICC of the user device and the suspended state of the eSIM profile. If the billing function determines that the eSIM profile is active for billing a subscriber for telecommunication services, the profile state of the eSIM profile is transitioned from suspended to released for reuse solely by the eUICC with the particular eUICC ID. However, if the billing function determines that the eSIM profile is inactive, the profile state of the eSIM profile is transitioned from suspended to available for use by any eUICC.

Abstract: Service data feeds that indicate multiple Embedded Subscriber Identity Module (eSIM) profiles provided by one or more eSIM profile vendor are loaded into one or more profile data stores of a subscription management service may be received from the subscription management service. The profile data stores may include a Subscription Manager Data Preparation (SM-DP) profile data store or a Subscription Manager Data Preparation Plus (SM-DP+) profile data store. A request is then received from an entity to perform an action with respect to a particular eSIM profile that has a specific Integrated Circuit Card identifier (ICCID). The request is forwarded to the subscription management service in response to determining that the specific ICCID matches an ICCID of an eSIM profile that is indicated by a service data feed as being loaded into a profile data store of the subscription management service. Accordingly, the subscription management service may implement the action with respect to the particular eSIM profile.

Abstract: A download order message is received from a business support function of a wireless communication carrier. The download order message is for initiating a preparation of an unpopulated eSIM profile for downloading to an EUICC on a user device. The unpopulated eSIM profile is an eSIM profile that lacks pre-populated profile metadata. A metadata provision value is extracted from the download order message. The metadata provision value is compared to a mapping table that maps profile metadata provision values to corresponding combinations of one or more metadata element values. Accordingly, a combination of one or more profile metadata element values for the unpopulated eSIM profile is identified based on the comparison of the metadata provision value to the mapping table. The combination of one or more profile metadata element values is then populated into the unpopulated eSIM profile to generate a populated eSIM profile.

Abstract: A device associated with a subscriber database of a telecommunication network described herein is configured to receive a Send Routing Information for Short Message (SRI-SM) message from a messaging center. The device then determines whether a user device specified by the SRI-SM message is associated with an Internet Protocol (IP) Multimedia Subsystem (IMS) registration. In response to determining that the user device is associated with an IMS registration, the device sends the SRI-SM message to an IP Short Message Gateway (IP-SM-GW). In response to determining that the user device is not associated with an IMS registration, the device processes the SRI-SM message and responds to the messaging center based on the processing.