System for the centralized storage of wireless customer information

• US 8,280,353 B2
• Filed: 10/22/2010
• Issued: 10/02/2012
• Est. Priority Date: 11/16/2001
• Status: Expired due to Fees

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Lewis, John Ervin, Patron, David, Yarkoni, Erez
• Primary Examiner(s): RAMPURIA, SHARAD K
• Application Number:
  US12/910,235
• Publication Number:
  US 20110092153A1
• Time in Patent Office: 711 Days
• Field of Search: 455405-408, 455/435.1, 4554121-4122, 4554141-4144
• US Class Current: 455/412.1
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: H04L 12/2856 Access arrangements, e.g. Internet access asynchronous transfer mode networks H04L12/5601; broadband local area networks H04L12/2801; optical access or distribution networks H04Q11/0067; access to open networks H04L12/5691; digital subscriber line end-user equipment and bit-level processing of data on a PSTN-based network H04M11/00; home network gateways H04L12/2834; wireless access networks H04W
• CPC Class Codes: H04L 41/5064 Customer relationship management
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/308 Route determination based on user's profile, e.g. premium users
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 51/234 for tracking messages
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/085 : specially adapted for interworking of IP-based networks with other networks
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/18 : Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 40/246 : Connectivity information discovery
• CPC Class Codes: H04W 40/248 : Connectivity information update
• CPC Class Codes: H04W 8/18 : Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 88/16 : Gateway arrangements
• CPC Class Codes: H04W 88/184 : Messaging devices, e.g. message centre
• CPC Class Codes: H04W 92/02 : Inter-networking arrangements
• CPC Class Codes: H04W 92/06 : between gateways and public network devices

Abstract

A system for storing subscriber information in a centralized location includes a processor, memory coupled to the processor, and a data storage device coupled to the processor. The data storage device includes a subscriber profile portion for storing personal information about a subscriber. The subscriber profile portion includes a subscriber identification portion for storing an identification string. The subscriber profile portion is associated with an account type portion for storing account information, a portal portion for storing portal information, and an account status portion for storing account status information. The data storage device further includes a subscription portion for storing subscription information. The subscription portion is associated with a device portion for storing device information, a services portion for storing services information, and a mobile subscription portion for storing mobile subscription information.

Claims

1. A system for collecting and distributing information within a wireless messaging infrastructure, the system comprising:

a scalable data storage device having a subscriber profile portion and a subscription portion;

a database business logic in communication with the scalable data storage device;

a backbone transport system in communication with the database business logic;

a backbone integration transport in communication with the backbone transport system;

a replica database business logic in communication with the backbone integration transport; and

a replica database in communication with the replica database business logic;

wherein the database business logic reads a bulk load data from the scalable data storage device, creates a data abstract file from the bulk load data, and announces availability of the bulk load data to the replica database;

wherein the replica database business logic retrieves the bulk load data from the scalable storage device, and loads the bulk load data into the replica database.

2. The system in claim 1, wherein the replica database is a network data distributor database.

3. The system in claim 1, further comprising a second replica database including at least a portion of the information stored in the scalable storage device.

4. The system in claim 3, wherein the second replica database is a routing and validations database.

5. The system in claim 1, wherein the scalable data storage device further comprises a state portion for storing state information and a country portion for storing country information.

6. The system in claim 5, wherein the subscriber profile portion is associated with the state portion and the country portion.

7. The system in claim 1, further comprising a provisioning system in communication with the database business logic and the backbone transport system.

8. The system in claim 1, further comprising a network database business logic adaptor in communication with the backbone transport system and the backbone integration system.

9. A method of collecting and distributing information within a wireless messaging infrastructure, the method comprising:

reading a bulk load data from a scalable data storage device having a subscriber profile portion and a subscription portion;

announcing availability of the bulk load data to a first replica database;

retrieving the bulk load data from the scalable storage device;

loading the bulk load data into the first replica database.

10. The method in claim 9, further comprising creating a data abstract file from the bulk load data.

11. The method in claim 9, further comprising:

announcing availability of the bulk load data to a second replica database;

retrieving the bulk load data from one of the scalable data storage device and the first replica database; and

loading the bulk load data onto the second replica database.

12. The method in claim 11, further comprising:

registering a new subscriber through an activation channel;

announcing availability of a new subscriber data to the first replica database;

retrieving the new subscriber data from the scalable data storage device; and

updating the first replica database with the new subscriber data.

13. The method in claim 12, further comprising:

announcing a new subscriber data to the second replica database;

retrieving the new subscriber data from one of the scalable data storage device and the first replica database; and

updating the second replica database with the new subscriber data.

14. The method in claim 13, wherein the announcing availability of the bulk load data to the first replica database further comprises sending the announcement through a backbone integration transport.

15. The method in claim 9, wherein the data abstract file represents one of all and a portion of the data subject to the bulk load operation.

16. A method of collecting and distributing information within a wireless messaging infrastructure, the method comprising:

reading a bulk load data from a scalable data storage device having a subscriber profile portion which stores a plurality of subscriber profiles, and a subscription portion which stores a plurality of mobile subscription information;

announcing availability of the bulk load data to a first replica database;

sending the bulk load data from the scalable storage device to the first replica database.

17. The method of claim 16, further comprising creating a data abstract file from the bulk load data.

18. The method in claim 16, further comprising:

announcing availability of the bulk load data to a second replica database; and

sending the bulk load data from one of the scalable data storage device and the first replica database to the second replica database.

19. The method in claim 18, further comprising:

registering a new subscriber through an activation channel;

announcing availability of a new subscriber data to the first replica database; and

updating the first replica database with the new subscriber data from the scalable data storage device.

20. The method in claim 19, wherein the announcing availability of the bulk load data to the first replica database further comprises sending the announcement through a backbone integration transport.