# US 2008/0270490 A1 · System and Method for Replication, Integration, Consolidation and Mobilisation of Data

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

- Number: US 2008/0270490 A1
- Document ID: US20080270490A1
- Status: Published application
- Kind: A1
- Application number: 11/597,925
- Filed: 2005-05-27
- Published: 2008-10-30
- Earliest claimed: 2004-05-28
- Assignees: moxite GmbH
- Inventors: Roland Watterott; Justus Lorentz
- Web page: https://patentgrep.com/patent/US20080270490A1

## CPC

- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/25: Integrating or interfacing systems involving database management systems
- H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 67/55: Push-based network services
- 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)

## Abstract

The system for replication, integration, consolidation and mobilisation of data according to the present invention provides a flexible framework of functionally autonomous and distributable modules with the main advantage of scalability, to simplify data integration, produce an integration structure that can accommodate backend structural changes and can cope with highly distributed data sources. Also, it creates a framework for delivering highly accessible, secure data to a mobile environment with minimal transfer loads during sending and receiving and secure data on the mobile client devices. Added to this, making use of modern mobile connection types for delivering push content from and/or to a wide spectrum of devices.

## Claims

### Claim 1

A system for at least one of replication, integration, consolidation and mobilization of data, the system includes:
a Replication Server for managing the replication of data
(i) between at least two backend data sources, and/or
(ii) between at least one backend data source and at least one input/output device and/or
(iii) between at least two input/output devices,
a Data Connector for connecting to any type of structured data,
a Communications Server for access to and from said input/output devices over a communication link, and
a common administration.

### Claim 2 (depends on 1)

The system according to claim 1, wherein one or more of the following modules: Replication Server, Data Connector and Communications Server, may be implemented to function autonomously from the other modules.

### Claim 3 (depends on 1)

The system according to claim 1, wherein said Data Connector is adapted to communicate with at least one backend data source and at least one Replication Server, whereby said Data Connector is independently implemented from said Replication Server, so that flexibility and scalability is achieved for data traffic optimization.

### Claim 4 (depends on 1)

The system according to claim 1, wherein said Communications Server is adapted to communicate with at least one input/output device and at least one Replication Server, whereby said Communications Server is independently implemented from said Replication Server, so that flexibility and scalability is achieved for data traffic optimization.

### Claim 5 (depends on 1)

The system according to claim 1, wherein said system includes a plurality of Replication Servers and wherein said Data Connector is set up to communicate with at least two of said plurality of Replication Servers.

### Claim 6 (depends on 1)

The system according to claim 1, wherein said system includes a plurality of Replication Servers and wherein said Communications Server is set up to communicate with at least two of said plurality of Replication Servers.

### Claim 7 (depends on 1)

The system according to claim 1, wherein said Replication Server is adapted to communicate with at least one Data Connector and at least one Communications Server, whereby said Replication Server is independently implemented from said Data Connector and said Communications Server, so that flexibility and scalability is achieved for data traffic optimization.

### Claim 8 (depends on 1)

The system according to claim 1, wherein said system includes a plurality of Communications Servers and wherein said Replication Server is set up to communicate with at least two of said plurality of Communications Server.

### Claim 9 (depends on 1)

The system according to claim 1, wherein said system includes a plurality of input/output devices and wherein said Communications Server is set up to communicate with at least two of said plurality of input/output devices.

### Claim 10 (depends on 1)

The system according to claim 1, wherein at least one of said input/output devices is equipped with a client application or a mobile client application.

### Claim 11 (depends on 1)

The system according to claim 1, wherein at least a subset of said at least two input/output devices is equipped with a client application or a mobile client application.

### Claim 12 (depends on 10)

The system according to claim 10, wherein said client applications are formed by at least two different client applications.

### Claim 13 (depends on 1)

The system according to claim 1, wherein said communication link is formed by a wireless connection.

### Claim 14 (depends on 1)

The system according to claim 1, wherein said communication link is formed by a wire based connection.

### Claim 15 (depends on 1)

The system according to claim 1, wherein more than one instance is provided of one of said Replication Server, said Data Connector and said Communication Server.

### Claim 16 (depends on 15)

The system according to claim 15, wherein each instance features its own data storage for facilitating independent operation.

### Claim 17 (depends on 1)

The system according to claim 1, wherein said common administration is formed by one single administration unit.

### Claim 18 (depends on 1)

The system according to claim 1, wherein said common administration is divided into separate administration units with respect to predetermined field of responsibility by means of access rights.

### Claim 19 (depends on 1)

The system according to claim 1, wherein a common data structure is provided from said Data Connector, through said Replication Server, to said Communication Server, providing flexibility during integrations.

### Claim 20 (depends on 19)

The system according to claim 19, wherein said common data structure is configured to offer user level access rights control down to field level.

### Claim 21 (depends on 19)

The system according to claim 19, wherein said common data structure is configured to offer device level access rights control down to field level.

### Claim 22 (depends on 19)

The system according to one of the claims 19, wherein said common data structure is configured to offer connection type level access rights control down to field level.

### Claim 23 (depends on 1)

The system according to claim 1, wherein anyone of the modules, namely, said Data Connector and said Communication Server, may be implemented in any number of instances and be combined around one or more Replication Servers, to offer maximum cooperative distribution.

### Claim 24 (depends on 1)

The system according to claim 1, wherein at least one instance of said Replication Server, said Data Connector and said Communication Server, may be configured to initiate a push transaction to communicate data to a target module or stationary wire based device or mobile wireless device.

### Claim 25 (depends on 24)

The system according to claim 24, wherein the configuration for push transactions may be set to event-driven or time-based rules.

### Claim 26 (depends on 1)

The system according to claim 1, wherein said system is configured to utilize a field-driven data structure designed to address both replication and integration needs.

### Claim 27 (depends on 1)

The system according to claim 1, wherein said system is configured to manage version control over client applications.

### Claim 28 (depends on 1)

The system according to claim 1, wherein said system is configured to automatically distribute version updates.

### Claim 29 (depends on 1)

The system according to claim 1, wherein said system is configured to manage version control over its own modules, namely, Replication Server, Data Connector and Communication Server, in order to facilitate automated version updates in a distributed environment.

### Claim 30 (depends on 1)

The system according to claim 1, wherein said system is configured to manage dynamic template adjustments on the client application according to changes in data structures and/or access rights.

### Claim 31

A method for managing transmission of transactions between its individual modules, the method including the following steps:
upon receiving data, the receiving module first validates the access rights of the sending module;
for a legal connection the receiving module then collects the received data and verified transaction integrity;
the receiving module then decides on the destination module, checks availability of the destination module, logs on to this module; and
upon successful connection sends the transaction to the destination module.

### Claim 32 (depends on 31)

The method according to claim 31, further including the following step: after sending the transaction to the destination module, the sending module monitors the delivery status and resend the transaction if necessary.

### Claim 33

(canceled)

### Claim 34

(canceled)
