Modular distributed mobile data applications

• US 7,877,682 B2
• Filed: 04/11/2007
• Issued: 01/25/2011
• Est. Priority Date: 12/04/2000
• Status: Expired due to Fees

• Current Assignee: William Charles Aegerter
• Original Assignee: William Charles Aegerter
• Inventors: Aegerter, William Charles
• Primary Examiner(s): Hong; Stephen S
• Assistant Examiner(s): Patel; Manglesh M
• Application Number:
  US11/734,182
• Publication Number:
  US 20070220089A1
• Time in Patent Office: 1,385 Days
• Field of Search: 715234-239, 715/200
• US Class Current: 715/237
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems

Abstract

Computer-implemented system and methods for deploying a distributed client-server system, enabling developers to rapidly create and deploy read-write distributed data interfaces for host database systems. The disclosed system is especially advantageous for mobile clients as connection to the server environment can be intermittent without unduly impeding local (disconnected) operations. One important aspect of the invention is an incremental process for executing an application servo in a client device. This process includes building and incrementally maintaining a logical context tree in which each node expresses a complete current state of the execution process.

Claims

1. A distributed mobile computing system for intermittently networked devices, the system comprising:

a servo for execution on a mobile computing device having a user interface and having at least intermittent communication with a server environment, the execution of the servo to realize a predetermined function on the mobile computing device, the servo defined in a predetermined servo description language (SDL) and configured to be stored in local storage on the mobile computing device, the servo comprising;

a declaration of data storage on the mobile computing device, the declaration including or referencing a schema, and

a declaration of a view, the declaration including a transformation rule mapping a schema component to an abstract interface object or concrete interface object;

an interpreter to execute the servo on the mobile computing device to realize the predetermined function by interacting with data and schema in local storage and interacting with a concrete interface object or an abstract interface object to enforce the mapping declared in the transformation rule of the servo;

a synchronizer on the mobile computing device to interact with a server-side synchronizer to synchronize data, schemata, and servos stored in local storage of the mobile computing device with server-side replica storage during periods of network connectivity; and

a server environment including;

storage on a non-transitory computer-readable storage medium for data, schemata, and at least one servo;

replica storage of the local storage on the mobile computing device, wherein the replica storage is on a non-transitory computer-readable storage medium; and

a synchronizer to interact with the synchronizer on the mobile computing device to synchronize data, schemata, and servos stored in local storage of the mobile computing device with the replica storage.

2. A distributed mobile computing system according to claim 1, wherein the servo is declared using a standard XSLT vocabulary extended so as to include the view declaration element.

3. A distributed mobile computing system according to claim 1, wherein the servo further includes one or more elements that include the declaration of data storage on the mobile computing device, and wherein the declaration of data storage includes a declaration of a persistent storage tree.

4. A distributed mobile computing system according to claim 3, wherein the declaration of data storage on the mobile computing device includes a name attribute for defining a locally scoped name for the corresponding storage tree.

5. A distributed mobile computing system according to claim 4, wherein the declaration of data storage on the mobile computing device includes identification of a predetermined storage schema to which the corresponding storage tree conforms.

6. A distributed mobile computing system according to claim 5, wherein the declaration of data storage on the mobile computing device includes at least one attribute directed to specification of a lifetime, an update policy or a destruction policy associated with the corresponding storage tree.

7. A distributed mobile computing system according to claim 5, wherein the predetermined storage schema is defined in an extensible markup language (XML).

8. A distributed mobile computing system according to claim 5, wherein the predetermined storage schema is defined within the servo.

9. A distributed mobile computing system according to claim 5, wherein the predetermined storage schema is defined by an XML schema definition.

10. A distributed mobile computing system according to claim 5, including an opportunity element to realize automatic extension of the servo through opportunity-based linking of an interface component representing an instance of a schema fragment to a template wherein the template specifies at least one of a transformation rule, a transaction handling rule and an interface object specification.

11. A distributed mobile computing system according to claim 5, wherein the servo is declared using a standard XSLT vocabulary extended so as to include the declaration of data storage on the mobile computing device.

12. A computing platform for distributed mobile applications comprising a computer-implemented server environment for interaction with a mobile client machine over a potentially intermittent communication channel, the server environment including:

a messaging service for managing potentially intermittent communication between the client machine and the server environment;

a location broker component for locating a database associated with an identifier contained in a request communicated from the client machine;

a session manager service for managing an interactive session with the client machine;

an interpreter instance for processing a request assigned to it in a current session;

storage on a non-transitory computer-readable storage medium for at least one servo, data and schema;

replica storage of a local storage on the client machine, wherein the replica storage is on a non-transitory computer-readable storage medium, and wherein data and schema in the local storage on the client machine are used and manipulated by an interpreter on the client machine that executes a servo to realize a predetermined function;

a synchronizer to interact with a synchronizer on the client machine to synchronize data, schemata, and servos stored in local storage of the client machine with the replica storage; and

a registry for managing meta data associated with servos and schemata;

wherein both the servo and the data are expressed in a markup language.

13. A computing platform according to claim 12 wherein the stored servo is declared in a servo definition language (SDL) defined by a schema that references the XSL vocabulary;

and the SDL includes a means for discovering a session environment; and

wherein the session environment includes indicia (attributes) of a physical location of the mobile client machine, identification of the mobile client hardware, and current status of the communication channel.

14. A computing platform according to claim 12 wherein the SDL defines a storage declaration instruction, and application data is available for reference in the SDL as a named input tree using a name defined in a storage declaration instruction in the servo.

15. A computing platform according to claim 14 wherein the SDL defines the following types of rules:

application data schema;

transformation rules;

transaction handling rules; and

interface object specifications.

16. A computing platform according to claim 15 wherein the SDL further defines opportunity rules to realize automatic extension a servo through opportunity-based linking of an interface component representing an instance of a schema fragment to a template.

17. A computing platform according to claim 15 wherein the SDL further defines opportunity rules to realize automatic integration of multiple servos through opportunity-based linking of an interface component representing an instance of a schema fragment to a template.

18. A computing platform according to claim 16 wherein the SDL specifies at least one of a transformation rule, a transaction handling rule and an interface object specification.

19. A computing platform according to claim 16 wherein the SDL further includes a view element for selecting a group of transformation rules to define at least a part of an output interface.

20. A computing platform according to claim 19 wherein the server environment further includes a schema translator for translating data from one schema to another.

21. A computing platform according to claim 19 wherein the registry includes at least one of the following kinds of metadata:

a schema public identifier with the corresponding schema representation;

a schema translator with a corresponding directed pair of schema public identifiers including flags for whether the translation loses information; and

a datasource public identifier with corresponding datasource declaration.