# US 2006/0136485 A1 · Dynamic selection or modification of data management patterns

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

- Number: US 2006/0136485 A1
- Document ID: US20060136485A1
- Status: Published application
- Kind: A1
- Application number: 11/281,268
- Filed: 2005-11-16
- Published: 2006-06-22
- Earliest claimed: 2004-11-16
- Inventors: Peter Yared; Jeffrey Norton
- Web page: https://patentgrep.com/patent/US20060136485A1

## CPC

- 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
- G06F 16/24552: {Database cache management}
- H04W 4/60: Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods are presented that enable the dynamic selection or modification of data management patterns (such as for caching or updating data). A deployment document describes how to manage data used by the application, including which caching patterns (and parameters) and which updating patterns should be used. In this way, a data management pattern can be specified for a particular application (and for a particular data type or data structure within an application), rather than a system-wide configuration option. The deployment document can be modified at any time up until the application starts being executed. A set of business policies and/or technical rules determines whether and how an application's deployment document should be modified. The policies and rules can take into account the application's run-time context, such as the type of transaction, the user involved, and the size and the longevity of the data needed and generated.

## Claims

### Claim 1

(canceled)

### Claim 2

A system for managing data used by an application executing on a first node, comprising:
a local data store;
an interface to a network data store;
an interface to a second node;
a set of instructions that indicates how the data is to be managed; and
a data management module configured to manage the data based on the set of instructions.

### Claim 3 (depends on 2)

The system of claim 2, wherein the set of instructions further indicates how a particular data type is to be managed, and wherein the data management module is further configured to manage the particular data type based on the set of instructions.

### Claim 4 (depends on 2)

The system of claim 2, wherein the set of instructions further indicates how a particular data structure is to be managed, and wherein the data management module is further configured to manage the particular data structure based on the set of instructions.

### Claim 5 (depends on 2)

The system of claim 2, wherein the set of instructions is associated with the application.

### Claim 6 (depends on 2)

The system of claim 2, wherein the set of instructions includes extensible Markup Language.

### Claim 7 (depends on 2)

The system of claim 2, wherein the set of instructions includes an extensible Markup Language Schema document.

### Claim 8 (depends on 2)

The system of claim 2, wherein the first node includes a Linux operating system.

### Claim 9 (depends on 2)

The system of claim 2, wherein the first node includes a HyperText Transfer Protocol server.

### Claim 10 (depends on 2)

The system of claim 2, wherein the local data store includes a database.

### Claim 11 (depends on 2)

The system of claim 2, wherein the network data store includes a database.

### Claim 12

A system for managing data used by an application executing on a first node, comprising:
a local data store;
an interface to a network data store;
an interface to a second node;
a set of instructions that indicates how the local data store is to be populated; and
a data management module configured to populate the local data store based on the set of instructions.

### Claim 13 (depends on 12)

The system of claim 12, wherein the set of instructions further indicates that the local data store is to be populated on demand.

### Claim 14 (depends on 12)

The system of claim 12, wherein the set of instructions further indicates that the local data store is to be populated on a schedule.

### Claim 15

A system for managing data used by an application executing on a first node, comprising:
a local data store;
an interface to a network data store;
an interface to a second node;
a set of instructions that indicates how the data is to be obtained, if the data is not present in the local data store; and
a data management module configured to obtain the data, if the data is not located in the local data store, based on the set of instructions.

### Claim 16 (depends on 15)

The system of claim 15, wherein the set of instructions further indicates that the data is to be obtained using the interface to the network data store.

### Claim 17 (depends on 15)

The system of claim 15, wherein the set of instructions further indicates that the data is to be obtained using the interface to the second node.

### Claim 18

A system for managing data used by an application executing on a first node, comprising:
a local data store;
an interface to a network data store;
an interface to a second node;
a set of instructions that indicates how data in the local data store is to be updated; and
a data management module configured to update data in the local data store based on the set of instructions.

### Claim 19 (depends on 18)

The system of claim 18, wherein the set of instructions further indicates that data in the local data store is to be sent using the interface to the network data store.

### Claim 20 (depends on 18)

The system of claim 18, wherein the set of instructions further indicates that data in the local data store is to be sent using the interface to the second node.

### Claim 21

A computer-readable medium comprising instructions for managing data used by an application executing on a first node, comprising:
a local data store;
an interface to a network data store;
an interface to a second node;
a set of instructions that indicates how the data is to be managed; and
a data management module configured to manage the data based on the set of instructions.
