Method of representing and processing complex branching logic for mobile applications

• US 8,126,924 B1
• Filed: 07/21/2008
• Issued: 02/28/2012
• Est. Priority Date: 07/20/2007
• Status: Expired due to Fees

• Current Assignee: Countermind, LLC
• Original Assignee: Countermind
• Inventors: Herin, Paul M.
• Primary Examiner(s): Fleurantin, Jean B
• Application Number:
  US12/176,992
• Time in Patent Office: 1,317 Days
• Field of Search: 707600- 81, 717/137, 725/62, 725/63, 702/182, 702/183, 702/188, 700/108, 455/432.1, 455/432.2
• US Class Current: 707/791
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/0633 Workflow analysis
• CPC Class Codes: G06Q 10/103 Workflow collaboration or project management

Abstract

A system is provided for efficiently defining and navigating through complex workflow structures for mobile unit applications. In one embodiment, the system (100) includes business platforms (101), a mobility server (102), an application descriptor generator (103) and mobile units (104). The business platforms (101) may be existing data systems of a business entity. The mobility server (102) handles communications between the business systems (101) and the mobile units (104). The application descriptor generator (103) creates application descriptors that define the functionality of an application running on a client (108) of the mobile unit (104). This functionality may include complex branching logic. In this manner, applications can be rapidly deployed and readily adapted to meet the needs of a business entity.

Claims

1. A method for use in controlling operation of a mobile unit, said mobile unit being associated with a mobility server operative for disseminating application descriptors that describe a functionality of an application for execution at one or more mobile units, said method comprising the steps of:

providing a client, resident on a mobile unit, for receiving an application descriptor from said mobility server and, responsive to receipt of said application descriptor, establishing said application having said functionality, wherein said functionality is described by said application descriptor;

establishing with said client a root form list, of one or more forms, defining the default process flow structure for navigating through said application, said root form list having a data content, including associated data structures, defined by said application descriptor; and

establishing with said client a child form list, of one or more forms, defining an alternative process flow structure for navigating through said application, said child form list having a data content, including said associated data structures, defined by said application descriptor;

wherein said client is responsive to said application descriptor to establish said root form list such that said root form list has a data content that is independent of a linking relationship for accessing said child form list as defined by said application descriptor.

2. A method as set forth in claim 1, wherein said client is responsive to said application descriptor to allow multiple parent forms to link to said child form list and a data content of said child form list varies depending on which said parent form links to said child form list, wherein said linking is defined in the application descriptor.

3. A method as set forth in claim 1, wherein said client is responsive to said application descriptor to allow a parent form to have multiple links creating multiple child form lists, each of said multiple child form lists having a content defined by said application descriptor.

4. A method as set forth in claim 1, wherein said client is further responsive to said application descriptor for linking said child form list to said root form list.

5. A method as set forth in claim 1, wherein said client is responsive to said application descriptor to establish one or more detail links from a component to multiple detail form lists, where said detail form lists describe detail information of said component and the data content of each said detail form list varies depending on each said detail link.

6. A method as set forth in claim 5, further comprising the steps of using said root form list and a series of child form lists and said detail form lists defined by said application descriptor to receive and store input data, and issuing a response, to said mobility server, including said input data, wherein said response further includes metadata, related to said default and alternative process flow structures, describing said input data.

7. A method as set forth in claim 6, wherein said response is stored in persistive memory in said device prior to issuing to said mobility server.

8. A method as set forth in claim 6, wherein said input data determines said alternative process flow structure that varies from said default process flow structure, based on said application descriptor.

9. A method as set forth in claim 1, further compromising the steps:

navigating from a first form to a second form, wherein said first and second form are in different groups.