Mobile Business Object Abstraction Layer for Data Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data access methods for mobile devices require frequent rewriting and redesign of objects when system components change, leading to compatibility issues and complexity in understanding relational synchronization technology, especially when dealing with diverse data sources like Web Services and Enterprise applications.
Innovation Solution
A flexible data abstraction methodology is implemented through defining a data source, synchronization methodology, and providing an abstraction layer for accessing data, which includes defining a Mobile Business Object (MBO) using metadata to facilitate transparent and efficient data access across multiple data sources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If objects are designed to access remote systems and store data in relational databases, then data access is abstracted in an object-oriented manner, but the objects require frequent rewriting and redesign when system components change
Solution Approach 1:
The patent introduces a synchronization object as an intermediary layer between mobile devices and enterprise data sources. This synchronization object abstracts the complexity of relational synchronization technology and provides a standardized interface for data access. When system components change, the synchronization object can be updated without requiring changes to the application logic, as it mediates all interactions between the application and the data source.
Solution Approach 2:
The synchronization object is designed as a universal component that can work with multiple types of data sources (relational databases, Web Services, Enterprise applications) through a standardized interface. This multi-functionality allows the same object structure to access different data sources without rewriting, resolving the compatibility issue when system components change.
2Reliability
If relational synchronization technology is implemented for data synchronization, then data consistency is maintained, but developers must understand the complexities of the synchronization technology
Solution Approach 1:
The synchronization object acts as an intermediary that encapsulates the complexity of relational synchronization technology. It provides a simplified, high-level interface for developers while handling the complex synchronization logic internally. This allows developers to maintain data consistency without needing to understand the underlying synchronization mechanisms.
Solution Approach 2:
The patent creates a local copy of enterprise data on mobile devices through the synchronization object. This copying mechanism maintains data consistency by replicating data from enterprise sources to local storage and managing updates bidirectionally, while the synchronization object handles all the complex coordination logic transparently.
3Adaptability or versatility
If multiple versions of objects are created to handle system component changes, then compatibility is maintained, but the number of objects increases and management becomes complex
Solution Approach 1:
The synchronization object serves as a stable intermediary layer that remains unchanged while system components evolve. Application objects interact with the synchronization object through a consistent interface, allowing the underlying data sources and synchronization mechanisms to change without creating multiple versions of application objects.
Solution Approach 2:
The synchronization object is designed as a universal, version-independent component that can adapt to different system configurations and data sources. This single universal object replaces the need for multiple version-specific objects, reducing complexity while maintaining compatibility.
4Ease of operation
If data access methods are designed for frequent connectivity, then data access is simplified, but mobile devices with occasional connectivity cannot efficiently access and synchronize data
Solution Approach 1:
The synchronization object is designed as a universal component that handles multiple connectivity patterns (frequent and occasional connectivity) through the same interface. It provides offline data access capabilities and automated synchronization when connectivity is available, allowing mobile devices with occasional connectivity to efficiently access and synchronize data without requiring frequent connectivity.
Data Source
AI summary
A system, method, and computer program product are provided for abstracting data in a remote data source. A method operates by defining the data source, defining a data synchronization methodology for communication with the data source, and providing an abstraction layer for accessing data in the data source. The abstraction layer implements the data synchronization methodology when data is accessed through the abstraction layer is presented.