Modular applications for mobile data system

Abstract

Operating sequences of a mobile data integration system include operational modules, also called transportable applications (“TransApps”), that are self contained and capable of being linked together with other operating sequences and TransApps. Each operational module can accept input data and can generate output data. The input data can be received from other modules, or from the application user, or from enterprise data sources. The output data can be provided to other modules, or to the application server (for enterprise data sources), or can be provided for display on the mobile computing device itself. Modules can be defined for the purpose of particular problem solutions, and such problem solution modules can be reused during other application design efforts. This supports reuse of earlier solutions to problems.

Description

REFERENCE TO PRIORITY DOCUMENTS [0001] This application claims benefit of priority of: co-pending U.S. Provisional Patent Application Ser. No. 60 / 664,121 entitled “Data Management for Mobile Data System”, by Robert O'Farrell et al., filed Mar. 21, 2005; co-pending U.S. Provisional Patent Application Ser. No. 60 / 664,088 entitled “Modular Applications for Mobile Data System”, by Robert Loughan, filed Mar. 21, 2005; co-pending U.S. Provisional Patent Application Ser. No. 60 / 664,122 entitled “Adapter Architecture for Mobile Data System”, by Robert O'Farrell et al., filed Mar. 21, 2005; and co-pending U.S. Provisional Patent Application Ser. No. 60 / 667,816 entitled “Modular Applications Management for Mobile Data System”, by Robert O'Farrell et al., filed Apr. 1, 2005. Priority of the respective filing dates is hereby claimed, and the disclosures of these Provisional Patent Applications are hereby incorporated by reference.COPYRIGHT NOTICE [0002] A portion of the disclosure of this paten...

AI Technical Summary

Benefits of technology

[0014] In accordance with the invention, operating sequences of the mobile data integration system are supported such that such operating sequences comprise operational modules, also called transportable applications (“TransApps”), that are self contained and capable of being linked together with other operating sequences and TransApps. Each operational module can accept input data and can generate output data. The input data can be received from other modules, or from the application user, or from enterprise data sources. The output data can be provided to other modules, or to the application server (for enterprise data sources), or can be provided for display on the mobile computing device itself. In this way, modules can be defined for the purpose of particular problem solutions, and such problem solution modules can be reused during other application design efforts. In this way, earlier solutions to problems can be utilized over and over again, and the knowledge and experience gained from a user community can be exploited for greater leverage, thereby increasing the efficiency of mobile data integration systems.

Problems solved by technology

Although many companies have realized significant savings and efficiencies from deploying such systems, it is also true that many organizations find the systems burdensome to implement and difficult to integrate with existing legacy data systems.

One important impediment to greater adoption of CRM and ERP systems that employ such mobile devices involve integration with other data in the enterprise.

Enterprise data integration issues can arise because mobile applications often come in proprietary, closed architectures that impede integration with other data systems of the enterprise.

The interim store, however, creates data update and conflict issues of its own.

Images