Traitement en cours

Veuillez attendre...

Paramétrages

Paramétrages

Aller à Demande

1. WO2004059443 - SYSTEME ET PROCEDE DE MISE A JOUR DE DONNEES MOBILES ET DE LOGICIEL

Note: Texte fondé sur des processus automatiques de reconnaissance optique de caractères. Seule la version PDF a une valeur juridique

[ EN ]

CLAIMS
WE CLAIM:

1. A method of processing data that is shared between multiple enterprise data sources and a mobile client, the method comprising:
receiving a request from the mobile client for enterprise data used by a client application, wherein the client request includes metadata that identifies enterprise data sources for the requested data and that specifies a relational correspondence between the requested data;
retrieving the enterprise data from the enterprise data sources identified as containing the requested data;
converting the retrieved data into a relational format that defines the retrieved data from the enterprise data sources, in accordance with the relations specified by the metadata; and
storing the converted data in a relational data store in the mobile client.

2. A method as defined in claim 1 , wherein the metadata describes business processes that are executed by the client application.

3. A method as defined in claim 1 , wherein the metadata is received at the mobile client from an application server.

4. A method as defined in claim 3, wherein the mobile client requests the metadata during an initialization operation of the client
application.

5. A method as defined in claim 1 , wherein the metadata specifies a View into an enterprise data source that exposes the data schema of the enterprise data source so an application server can process data into and out of the enterprise data sources.

6. A method as defined in claim 5, wherein the metadata specifies conflict detection and resolution parameters that resolve data conflicts between the mobile client and multiple back end enterprise data sources.

7. A method as defined in claim 1 , wherein the mobile application includes multiple display pages and each display page is associated with metadata that specifies a flow to another display page, thereby comprising a business flow.

8. A method as defined in claim 1 , wherein the metadata specifies a business object layer of data that defines objects in a relational database format such that converted data from multiple enterprise data sources can be related together.

9. A method as defined in claim 1 , further including receiving upload data from the mobile client and determining a corresponding enterprise data source to which the upload data should be sent.

10. A method as defined in claim 9, further including applying conflict detection and resolution rules to determine if the upload data from the mobile client should be stored in the corresponding enterprise data source or if the upload data should be refused.

11. An application server that supports delivering data to mobile clients that can be shared between multiple enterprise data sources and multiple mobile clients, the application server comprising:
a data manager that receives a request for data from the mobile client, processes metadata in the client data request to determine the data to be retrieved and the enterprise data source from which the data is to be retrieved; and
one or more connectors that retrieve the data from the enterprise data sources and convert the retrieved data into a relational format that defines the retrieved data from the enterprise data sources, in accordance with the metadata contained in the received request, and that return the converted data to a relational data store on the mobile client.

12. An application server as defined in claim 11 , wherein the metadata describes business processes that are executed by the client application.

13. An application server as defined in claim 11 , wherein the metadata is received at the mobile client from an application server.

14. An application server as defined in claim 13, wherein the mobile client requests the metadata during an initialization operation of the client application.

15. An application server as defined in claim 11 , wherein the metadata specifies a view into an enterprise data source that exposes the data schema of the enterprise data source so an application server can process data into and out of the enterprise data sources.

16. An application server as defined in claim 15, wherein the metadata specifies conflict detection and resolution rules that resolve data conflicts between the mobile client and the enterprise data sources.

17. An application server as defined in claim 1 1 , wherein the mobile application includes multiple display pages and each display page is associated with metadata that specifies a flow to another display page, thereby comprising a business flow.

18. An application server as defined in claim 11 , wherein the metadata specifies a business object layer of data that defines objects in a relational database format such that converted data from multiple enterprise data sources can be related together.

19. An application server as defined in claim 11 , further including receiving upload data from the mobile client and determining a corresponding enterprise data source to which the upload data should be sent.

20. An application server as defined in claim 19, further including applying conflict rules to determine if the upload data from the mobile client should be stored in the corresponding enterprise data source or if the upload data should be refused.

21. A mobile client that processes data from multiple enterprise data sources over a mobile network, the mobile client comprising:
an application that performs data processing functions and generates requests for data;
a data manager that receives data requests from the application and generates a client data request including metadata that specifies enterprise data to be retrieved and specifies the enterprise data sources from which the data is to be retrieved, wherein the data manager transmits the client data requests over the mobile network; and
a relational datastore in which is stored enterprise data from responses to the client data requests, wherein the responses comprise the requested enterprise data from the enterprise data sources, converted to a relational format that relates the retrieved data from the enterprise data sources, in accordance with the metadata contained in the received request.

22. A mobile client as defined in claim 21 , wherein the metadata describes business processes that are executed by the client application.

23. A mobile client as defined in claim 21 , wherein the metadata is received at the mobile client from an application server.

24. A mobile client as defined in claim 23, wherein the mobile client requests the metadata during an initialization operation of the client application.

25. A mobile client as defined in claim 21 , wherein the metadata specifies a view into an enterprise data source that exposes the data schema of the enterprise data source so an application server can process data into and out of the enterprise data sources.

26. A mobile client as defined in claim 25, wherein the metadata specifies conflict detection and resolution rules that resolve data conflicts between the mobile client and the enterprise data sources.

27. A mobile client as defined in claim 21 , wherein the mobile application includes multiple display pages and each display page is associated with metadata that specifies a flow to another display page, thereby comprising a business flow.

28. A mobile client as defined in claim 21 , wherein the metadata specifies a business object layer of data that defines objects in a relational format such that converted data from multiple enterprise data sources can be related together.

29. A mobile client as defined in claim 21 , further including receiving upload data from the mobile client and determining a corresponding enterprise data source to which the upload data should be sent.

30. A mobile client as defined in claim 29, further including applying conflict rules to determine if the upload data from the mobile client should be stored in the corresponding enterprise data source or if the upload data should be refused.