MOBILE APPLICATIONS

• US 20090300656A1
• Filed: 09/18/2007
• Published: 12/03/2009
• Est. Priority Date: 09/22/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Lloyd, Alexander, Lucas, Terry Leonard, Bosworth, Adam, Eskafi, Farokh H., Bosworth, Alexander, Khesin, Alexander, Burdon, Richard, Ong, Ken
• Granted Patent: US 8,645,973 B2
• Time in Patent Office: Days
• US Class Current: 719/320
• CPC Class Codes: G06F 12/0875 with dedicated cache, e.g. instruction or stack
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

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 application adapted to run on a mobile browser at a mobile device;

the mobile application comprising;

a controller program file;

a set of presentation templates; and

metadata files that describe the applications data model.

2. The mobile application of claim 1, wherein the controller file contains action scripts.

3. The mobile application of claim 2, wherein the scripts are written in ECMAscript for XML.

4. The mobile application of claim 2, wherein the action scripts are invoked by user actions.

5. The mobile application of claim 2, wherein the action script returns the name of a template to load.

6. The mobile application of claim 2, wherein a begin action script is automatically executed.

7. The mobile application of claim 1, wherein templates define layout.

8. The mobile application of claim 1, wherein templates include expressions.

9. The mobile application of claim 8, wherein the expressions are evaluated when a user clicks an element.

10. The mobile application of claim 9, wherein the controller action is called when the expression is evaluated.

11. The mobile application of claim 1, wherein the metadata files define an object model that references local cached data.

12. The mobile application of claim 2, wherein action scripts can modify data, modify a template and cause navigation.

13. The mobile application of claim 1, wherein data is defined in data nodes that can be locally cached.

14. The mobile application of claim 2, wherein the controller file further includes function scripts.