# US 8,280,353 B2 · System for the centralized storage of wireless customer information

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,280,353 B2
- Document ID: US8280353B2
- Status: Granted
- Kind: B2
- Application number: 12/910,235
- Filed: 2010-10-22
- Published: 2011-04-21
- Granted: 2012-10-02
- Earliest claimed: 2001-11-16
- Assignees: AT&T Intellectual Property I, L.P.
- Inventors: David Patron; Erez Yarkoni; John Ervin Lewis
- Web page: https://patentgrep.com/patent/US8280353B2

## CPC

- G06Q 20/102: {Bill distribution or payments}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/275: {Synchronous replication}
- 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)}
- H04L 41/5064: {Customer relationship management}
- H04L 43/0817: by checking functioning
- H04L 45/04: {Interdomain routing, e.g. hierarchical routing}
- H04L 45/308: {Route determination based on user's profile, e.g. premium users}
- H04L 47/2408: for supporting different services, e.g. a differentiated services [DiffServ] type of service
- H04L 51/212: using filtering or selective blocking
- H04L 51/56: Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
- H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
- H04L 67/306: User profiles
- H04L 67/63: Routing a service request depending on the request content or context
- H04L 69/329: in the application layer [OSI layer 7]
- H04W 8/18: Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04L 51/066: Format adaptation, e.g. format conversion or compression
- H04L 51/23: Reliability checks, e.g. acknowledgments or fault reporting
- H04L 51/234: for tracking messages
- H04L 51/58: Message adaptation for wireless communication
- H04L 69/085: specially adapted for interworking of IP-based networks with other networks
- H04W 4/12: Messaging; Mailboxes; Announcements
- 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
- H04W 40/246: {Connectivity information discovery}
- H04W 40/248: {Connectivity information update}
- H04W 88/16: Gateway arrangements
- H04W 88/184: {Messaging devices, e.g. message centre}
- H04W 92/02: Inter-networking arrangements
- H04W 92/06: between gateways and public network devices
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## 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

### Claim 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.

### Claim 2 (depends on 1)

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

### Claim 3 (depends on 1)

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.

### Claim 4 (depends on 3)

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

### Claim 5 (depends on 1)

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.

### Claim 6 (depends on 5)

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

### Claim 7 (depends on 1)

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

### Claim 8 (depends on 1)

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.

### Claim 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.

### Claim 10 (depends on 9)

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

### Claim 11 (depends on 9)

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.

### Claim 12 (depends on 11)

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.

### Claim 13 (depends on 12)

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.

### Claim 14 (depends on 13)

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.

### Claim 15 (depends on 9)

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.

### Claim 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.

### Claim 17 (depends on 16)

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

### Claim 18 (depends on 16)

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.

### Claim 19 (depends on 18)

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.

### Claim 20 (depends on 19)

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.
