Method of handling a data request

• US 20030028620A1
• Filed: 06/20/2001
• Published: 02/06/2003
• Est. Priority Date: 06/20/2001
• Status: Abandoned Application

• Current Assignee: Navarsoft Limited
• Original Assignee: Navarsoft Limited
• Inventors: Timmermann, Andreas, Woelfel, Ludger, Kuschke, Michael
• Application Number:
  US09/884,448
• Publication Number:
  US 20030028620A1
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

A method of handling a data request by exporting data from at least one database to at least one receiver via an intermediary server, the intermediary server comprising at least one database adapter and a memory buffer for temporary storage of data, the method including the steps of transmitting a data request to the database, retrieving the data from the database and assigning it with a unique ID, transmitting the data and the unique ID to the intermediary server, passing the data through the database adapter to transform the data into receiver readable format and transmitting the transformed data and unique ID number to the receiver when the receiver is next enabled to receive the data. There is furthermore provided a computer implemented system for accessing databases operated by independent electronic processing devices.

Claims

1. A method of handling a data request by exporting data from at least one database to at least one receiver via an intermediary server, the intermediary server comprising at least one database adapter and a memory buffer for temporary storage of data, the method comprising the steps of:

(a) transmitting the data request from the intermediary server to the database;

(b) retrieving the requested data from the database;

(c) assigning to the data a unique ID number;

(d) transmitting the requested data and unique ID number to the intermediary server;

(e) passing the requested data through the relevant database adapter to transform the data into receiver readable format and storing the transformed data and unique ID number in the memory buffer; and

(f) transmitting the transformed data and unique ID number to the receiver when the receiver is next enabled to receive the data.

2. A method of handling a data request as claimed in claim 1, in which the unique ID number identifies the database from which the data came.

3. A method of handling a data request as claimed in claim 1, in which the unique ID number contains a destination address.

4. A method of handling a data request as claimed in claim 1, in which the data is requested from the database at predetermined intervals by the server.

5. A method of handling a data request as claimed in claim 1 in which the data request originates at the receiver before passing through the intermediary server.

6. A method of handling a data request as claimed in claim 5 in which the data is requested from the database at predetermined intervals.

7. A method of handling a data request as claimed in claim 1, in which the database will transmit only the updated data of data that has already been given a unique ID number.

8. A method of handling a data request as claimed in claim 1, in which the data at the receiver may be altered and retransmitted back to the database with the same unique ID number via the intermediary server.

9. A method of handling a data request as claimed in claim 8, in which the data to be retransmitted back to the database is stored on the memory buffer of the intermediary server until an update request is received from the database.

10. A method of handling a data request as claimed in claim 8, in which only that data that has changed is retransmitted back to the database.

11. A method of handling a data request as claimed in claim 8, in which the data received by the database is compared with the existing data and the existing data is updated accordingly.

12. A method of handling a data request as claimed in claim 8, in which the data is retransmitted back to the database at predetermined intervals.

13. A method of handling a data request as claimed in claim 1, in which the database will transmit any data that has changed to the intermediary server so that the receivers may receive the updated data when the receiver is next enabled to receive the data.

14. A method of handling a data request as claimed in claim 13, in which the data is automatically sent to the intermediary server when the data in the database changes.

15. A method of handling a data request as claimed in claim 13, in which the data is sent from the database to the intermediary server at predetermined intervals.

16. A method of handling a data request as claimed in claim 1, in which the data from more than one database may be linked so that a request for one piece of data will also generate a request for all lined pieces of data.

17. A method of handling a data request as claimed in claim 1, in which two or more receivers may be linked into a common group so that data transmitted to one of these receivers will be transmitted to all of those receivers in that group.

18. A method of handling a data request as claimed in claim 17, in which the receivers of a common group are all updated at predetermined intervals.

19. A method of handling a data request as claimed in claim 17, in which the receivers of a common group are all updated when the data in the database changes.

20. A method of handling a data request as claimed in claim 1, in which data that is transferred is not deleted from the transmitting memory until a transmission successful message is received from the recipient.

21. A method of handling a data request as claimed in claim 1, in which the data transfers that are unsuccessful will generate a data transfer incomplete message.

32. A computer program comprising program instructions for causing a computer to perform the method of claim 1.

33. A computer program as claimed in claim 32 embodied on a record medium.

34. A computer program as claimed in claim 32 embodied on a carrier signal.

22. A method of handling a data request by exporting data from at least one database to at least one receiver via an intermediary server, the intermediary server comprising at least one database adapter and a memory buffer for temporary storage of data, the method comprising the steps of:

(a) transmitting the data request from the intermediary server to the database;

(b) retrieving the requested data from the database;

(c) assigning the data with a unique ID number;

(d) transmitting the requested data and unique ID number to the intermediary server;

(e) passing the requested data through the relevant database adapter to transform the data into receiver readable format and storing the transformed data and unique ID number in the memory buffer;

(f) transmitting the transformed data and unique ID number to the receiver when the receiver is next enabled to receive the data, and on the data in the database being changed by the addition of updated data;

(g) exporting the updated data to the intermediary server,

(h) storing the updated data with the same ID in the memory buffer; and

(i) transmitting the updated data to the receiver when the receiver is next enabled whereby the receiver then stored the updated data.

23. A method of handling a data request as claimed in claim 22, in which the data is requested from the database at predetermined intervals by the server.

24. A method of handling a data request as claimed in claim 22, in which the data request originated at the receiver before passing through the intermediary server.

25. A method of handling a data request as claimed in claim 22, in which the data at the receiver may be altered and retransmitted back to the database with the same unique ID number via the intermediary server.

26. A method of handling a data request as claimed in claim 25, in which the data to be retransmitted back to the database is stored on the memory buffer of the intermediary server until an update request is received from the database.

27. A method of handling a data request data as claimed in claim 22, in which data that is transferred is not deleted from the memory of the transmitter until a transmission successful message is received from the recipient.

35. A computer program comprising program instructions for causing a computer to perform the method of claim 22.

36. A computer program as claimed in claim 35 embodied on a record medium.

37. A computer program as claimed in claim 35 embodied on a carrier signal.

28. A computer implemented system for accessing databases operated by independent electronic processing devices comprising:

(a) a plurality of receivers;

(b) an intermediary server;

(c) a communications network connecting the processing devices and the server and the receivers and the server, at least the receivers and the server being only intermittently connected;

(d) translation means in the server to accept data from the database and convert the accepted data into a format suitable for transmission to the receiver;

(e) means to assign a unique ID to data in a database on accepting data from the database;

(f) a storage buffer for the ID and converted data; and

(g) means on the receiver being enabled to communicate with the server, downloading the data and ID to the receiver.

29. A computer implemented system as claimed in claim 28, in which the intermediary server is provided with means to request data from the database at predetermined intervals.

30. A computer implemented system as claimed in claim 28, in which the receiver is provided with means to request data from the databases at predetermined intervals.

31. A computer implemented system as claimed in claim 28, in which the receiver is provided with means to alter the data and means to retransmit the altered data to the intermediary server.