Client programming for mobile client

• US 20060030292A1
• Filed: 05/04/2005
• Published: 02/09/2006
• Est. Priority Date: 05/20/2004
• Status: Abandoned Application

• Current Assignee: BEA Systems Incorporated (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Bosworth, Adam, Eskafi, Farokh H., Bosworth, Alexander, Khesin, Alexander, Lloyd, Alexander, Lucas, Terry, Burdon, Richard, Ong, Ken
• Application Number:
  US11/121,770
• Publication Number:
  US 20060030292A1
• Time in Patent Office: Days
• US Class Current: 455/408
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/8358 Query translation
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 88/02 Terminal devices

Abstract

Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a metadata description of the mobile application'"'"'s anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.

Claims

1. A mobile unit comprising:

a local cache of data nodes, and

an occasionally-connected data model defining node types and the relations between nodes, wherein the mobile unit uses the data nodes and the occasionally-connected data model to produce an application which is displayed at the mobile unit.

2. The mobile unit of claim 1, further comprising a template for producing a interface for the data nodes at the mobile unit.

3. The mobile unit of claim 2, wherein the template is an XHTML template.

4. The mobile unit of claim 2, wherein the template uses Spath expressions.

5. The mobile unit of claim 2, wherein the template can access a current position in the occasionally-connected data model.

6. The mobile unit of claim 2, wherein the template does not modify the occasionally-connected data model.

7. The mobile unit of claim 2, wherein the template can invoke actions.

8. The mobile unit of claim 7, wherein the actions can modify data nodes.

9. The mobile unit of claim 1, further comprising actions that allow the modification of the data nodes.

10. The mobile unit of claim 9, wherein the actions allow the modification of the data nodes without a connection to a server.

14. The mobile unit of claim 9, wherein the actions allow the modification of the data nodes without a connection to a server.

15. The mobile unit of claim 9, wherein the actions are XScript functions.

11. A mobile unit comprising:

a local cache of data nodes,

an occasionally-connected data model defining node types and the relations between nodes; and

actions that allow modification of the data nodes.

12. The mobile unit of claim 11, wherein a template can invoke the actions.

13. The mobile unit of claim 12, wherein the template produces a interface for the data nodes at the mobile unit.

16. A mobile unit comprising:

memory storing an occasionally-connected data model; and

a local cache of data modes as defined by the occasionally-connected data model, the data nodes including primary keys and synchronization states.

17. The mobile unit of claim 16, wherein in at least one of the data nodes includes at least one secondary key.

18. The mobile unit of claim 16, wherein the synchronization state is used to synchronize the data nodes with an occasionally-connected application server.

19. The mobile unit of claims 16, wherein the occasionally-connected data model includes at least one XML schema for the data nodes.