US 12,067,000 B2
Methods and systems to process asynchronous transactions at a management system
Pablo Medeiros Dominguez, Redmond, WA (US); Mirmd Hasan, Bellevue, WA (US); James Latham, Redmond, WA (US); and Joshua Ogden, Overland Park, KS (US)
Assigned to T-Mobile Innovations LLC, Overland Park, KS (US)
Filed by T-Mobile Innovations LLC, Overland Park, KS (US)
Filed on May 26, 2022, as Appl. No. 17/825,919.
Prior Publication US 2023/0385272 A1, Nov. 30, 2023
Int. Cl. G06F 16/23 (2019.01); G06Q 30/04 (2012.01)
CPC G06F 16/2379 (2019.01) [G06Q 30/04 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A method performed by a system comprising consolidated subscriber data in communication with a plurality of provisioning middlewares to provision transactions asynchronously, wherein the method comprises:
receiving, by a provisioning application at the system from a first provisioning middleware, an add instruction to add a new account to a subscriber database at the system, wherein the add instruction indicates a line identifier and a first source identifier, wherein the line identifier identifies a line activated by the new account, wherein the first source identifier identifies a first carrier billing system from which the first provisioning middleware received a request to add the new account, and wherein the first provisioning middleware is communicatively coupled to the first carrier billing system;
determining, by the provisioning application, an existing account indexed by the line identifier that is present at the subscriber database after receiving the add instruction;
when the existing account indexed by the line identifier is present at the subscriber database:
deleting, by the provisioning application, the existing account from the subscriber database; and
adding, by the provisioning application, the new account associated with the line identifier at the subscriber database, wherein the new account indicates the first source identifier, and wherein the first source identifier stored with the line identifier at the subscriber database is used to determine whether to perform or discard a received delete or update instruction;
receiving, by the provisioning application from a second provisioning middleware, a delete instruction to delete the existing account from the subscriber database at the system, wherein the delete instruction indicates the line identifier, and wherein a second carrier billing system is the only billing system coupled to the second provisioning middleware;
determining, by the provisioning application, from a memory, a second source identifier identifying the second carrier billing system from which the second provisioning middleware received a request to delete the existing account;
determining, by the provisioning application, whether the second source identifier in the delete instruction matches the first source identifier stored in association with the new account that has been recently added to the subscriber database;
discarding the delete instruction when the second source identifier in the delete instruction does not match the first source identifier stored in association with the new account; and
transmitting, via an application programming interface, a response to a provisioning request device indicating a success of deleting the existing account.