Provisioning multi-provider secure subscriber identification module services
Disclosed herein are techniques associated with an embedded subscriber identification module (eSIM) service. A first request message, including a plan identifier for a service plan, is received from a client device. A target service provider module corresponding to the service provider system is identified based on the plan identifier. The module is a dedicated data structure stored in an intermediary system. An order creation request signal is provided to complete an order for the plan. After receiving a subscription creation confirmation, an order completion status is received. An indication of the completed order is posted to a subscription change topic to cause an event handler to provide an updated order status signal.
1 . A method, comprising:
receiving, by a provider management component provided by a processor that executes instructions stored in a memory of an intermediary system and from a client device, a first request message associated with an embedded subscriber identification module (eSIM) service, the first request message including a plan identifier associated with a service plan offered by a service provider system,
identifying, by the provider management component and based on the plan identifier, a target service provider module corresponding to the service provider system, wherein the target service provider module comprises a dedicated data structure, stored in the intermediary system, comprising at least one of a database table associated with the service provider system, an asynchronous event queue associated with the service provider system, or a set of workflow logic components associated with the service provider system;
providing, by the provider management component via the target service provider module, an order creation request signal to request completion of an order corresponding to the service plan;
receiving, by the target service provider module from the service provider system, a subscription creation confirmation signal indicative of creation, by the service provider system, of a subscription associated with the service plan;
receiving, by the provider management component from the target service provider module, an order completion status signal based on the subscription creation confirmation signal; and
posting, by the provider management component to a subscription change topic of an asynchronous event queue managed by an event handler component of the intermediary system, an indication of completion of the order to cause the event handler component to provide an updated order status signal to the client device.
2 . The method of claim 1 , wherein receiving the first request message comprises receiving the first request message via an application programming interface (API) of the intermediary system.
3 . The method of claim 2 , wherein the first request message is generated by the client device subsequent to a processing of a payment event by a payment component of the intermediary system.
4 . The method of claim 1 , wherein the dedicated data structure of the target service provider module comprises the database table associated with the service provider system, the method comprising:
persisting, by the target service provider module and subsequent to receiving the subscription creation confirmation signal, an indication of the order in the database table associated with the service provider system.
5 . The method of claim 1 , wherein the target service provider module is one of a plurality of service provider modules stored in a data store of the intermediary system, and wherein each service provider module of the plurality of service provider modules corresponds to a different service provider system of a plurality of service provider systems.
6 . The method of claim 1 , wherein the provider management component comprises a hypertext transfer protocol (HTTP) server, the method comprising:
receiving, by the HTTP server, one or more webhook events from the service provider system, wherein the one or more webhook events include at least one asynchronous notification corresponding to a change in a status of the subscription; and
proxying, by the HTTP server, the one or more webhook events to a dedicated endpoint of the target service provider module to cause the target service provider module to process the change in the status of the subscription.
7 . The method of claim 1 , comprising:
transmitting, from the provider management component to a plurality of service provider systems, a plurality of asynchronous requests for product information; and
receiving, at the provider management component and based on the plurality of asynchronous requests, a plurality of asynchronous responses indicative of a plurality of sets of product information, wherein each set of product information of the plurality of sets of product information is associated with a corresponding service provider system of the plurality of service provider systems.
8 . The method of claim 7 , comprising:
aggregating, by the provider management component, the product information into a single aggregated set of product information; and
providing the single aggregated set of product information to the client device.
9 . The method of claim 8 , comprising:
providing the single aggregated set of product information to an application programming interface (API) of the intermediary system to cause the API to map the single aggregated set of product information to a set of available service plans associated with the plurality of service provider systems.
10 . A system, comprising:
one or more memories; and
one or more processors communicatively coupled with the one or more memories, the one or more processors configured to execute instructions stored in the one or more memories to cause the system to:
receive, by a provider management component of the system and from a client device, a first request message associated with an embedded subscriber identification module (eSIM) service, the first request message including a plan identifier associated with a service plan offered by a service provider system;
identify, by the provider management component and based on the plan identifier, a target service provider module corresponding to the service provider system, wherein the target service provider module comprises a dedicated data structure, stored in the system, comprising at least one of a database table associated with the service provider system, an asynchronous event queue associated with the service provider system, or a set of workflow logic components associated with the service provider system;
provide, by the provider management component via the target service provider module, an order creation request signal to request completion of an order corresponding to the service plan;
receive, by the target service provider module from the service provider system, a subscription creation confirmation signal indicative of creation, by the service provider system, of a subscription associated with the service plan;
receive, by the provider management component from the target service provider module, an order completion status signal based on the subscription creation confirmation signal; and
post, by the provider management component to a subscription change topic of an asynchronous event queue managed by an event handler component of the system, an indication of a completion of the order to cause the event handler component to provide an updated order status signal to the client device.
11 . The system of claim 10 , wherein the one or more processors are configured to execute the instructions to cause the system to:
receive, by a hypertext transfer protocol (HTTP) server of the provider management component and at a first dedicated endpoint corresponding to the target service provider module, a callback event from the service provider system; and
authenticate the callback event using a first authorization operation unique to the first dedicated endpoint, wherein the first authorization operation is different from a second authorization operation associated with a second service provider module stored in the system.
12 . The system of claim 11 , wherein the one or more processors are configured to execute the instructions to cause the system to:
route, based on a successful authentication, the callback event to the target service provider module for processing.
13 . The system of claim 12 , wherein the callback event includes a data payload having a data structure unique to the service provider system, and wherein, to process the callback event, the one or more processors are configured to execute the instructions to cause the system to:
process the data payload using a set of workflow logic components of the target service provider module.
14 . The system of claim 11 , wherein the callback event comprises an asynchronous notification indicating a change in a status of a subscription associated with the service plan.
15 . The system of claim 10 , wherein, to receive the first request message, the one or more processors are configured to execute the instructions to cause the system to:
publish, by an application programming interface (API) of the system and based on a successful payment processing event, the first request message to an order creation topic of the asynchronous event queue associated with the service provider system.
16 . The system of claim 15 , wherein, to receive the first request message, the one or more processors are configured to execute the instructions to cause the system to:
consume, by the provider management component, the first request message from the order creation topic of the asynchronous event queue associated with the service provider system.
17 . One or more non-transitory computer-readable media storing instructions operable to cause one or more processors to perform operations comprising:
receiving, by a provider management component of an intermediary system and from a client device, a first request message associated with an embedded subscriber identification module (eSIM) service, the first request message including a plan identifier associated with a service plan offered by a service provider system;
identifying, by the provider management component and based on the plan identifier, a target service provider module corresponding to the service provider system, wherein the target service provider module comprises a dedicated data structure, stored in the intermediary system, comprising at least one of a database table associated with the service provider system, an asynchronous event queue associated with the service provider system, or a set of workflow logic components associated with the service provider system;
providing, by the provider management component via the target service provider module, an order creation request signal to request completion of an order corresponding to the service plan;
receiving, by the target service provider module from the service provider system, a subscription creation confirmation signal indicative of creation, by the service provider system, of a subscription associated with the service plan;
receiving, by the provider management component from the target service provider module, an order completion status signal based on the subscription creation confirmation signal; and
posting, by the provider management component to a subscription change topic of an asynchronous event queue managed by an event handler component of the intermediary system, an indication of a completion of the order to cause the event handler component to provide an updated order status signal to the client device.
18 . The one or more non-transitory computer-readable media of claim 17 , the operations comprising:
determining, by the provider management component, that providing the order creation request signal resulted in an error; and
publishing, by an application programming interface (API) and based on the error, a message to a retry topic of the asynchronous event queue associated with the service service provider module to facilitate a subsequent attempt to provide the order creation request signal.
19 . The one or more non-transitory computer-readable media of claim 18 , the operations comprising:
consuming, by the provider management component, the message from the retry topic; and
re-providing, by the provider management component via the target service provider module, the order creation request signal to the service provider system.
20 . The one or more non-transitory computer-readable media of claim 17 , the operations comprising:
generating a secure communication based on applying, by the intermediary system, a security service to data traffic generated using the eSIM service.