Dynamic Data Binding for Mobile Business Objects
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional mobile applications face challenges in quickly developing dynamic data binding from remote data stores due to coding and deployment complexities, making it difficult to efficiently bind and modify data structures on mobile devices.
Innovation Solution
A method and system that dynamically bind data from a remote data store to a mobile application by defining a metadata source referencing a mobile business object, allowing attribute binding and subsequent dynamic changes to the binding while the application is executing, with a metadata source containing subscription criteria for data transfer between components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional mobile applications use traditional coding approaches for data binding, then data binding functionality can be achieved, but development time and complexity increase significantly
Solution Approach 1:
The patent introduces a metadata source as an intermediary component that mediates between the mobile application and remote data stores. This metadata source contains binding definitions that automatically configure data connections, eliminating the need for developers to manually code complex binding logic and reducing both development time and coding complexity.
Solution Approach 2:
The patent uses metadata templates that can be copied and reused across different applications. These templates contain pre-defined binding configurations that can be instantiated without re-coding, allowing rapid development while maintaining consistent data binding patterns across multiple applications.
2Adaptability or versatility
If applications dynamically modify data binding at runtime, then adaptability improves, but system stability and execution continuity may be compromised
Solution Approach 1:
The patent implements dynamic binding by allowing the metadata source to be updated at runtime without restarting the application. The binding definitions can be modified to adapt to changing data structures or requirements while the application continues executing, achieving both adaptability and stability through controlled metadata updates rather than structural changes.
Solution Approach 2:
The patent prepares binding configurations in advance within the metadata source before runtime execution. When dynamic changes are needed, the system updates existing metadata bindings rather than creating new connections during execution, which maintains execution stability while enabling adaptability through pre-planned modification mechanisms.
3Adaptability or versatility
If applications bind to multiple remote data stores, then data access versatility improves, but deployment complexity and maintenance difficulty increase
Solution Approach 1:
The patent creates a universal metadata source framework that can bind to multiple types of remote data stores through a single unified interface. This multi-functional metadata source handles different data store protocols and structures through standardized binding definitions, allowing applications to access various data sources without deploying separate binding mechanisms for each type.
Solution Approach 2:
The patent segments the data binding functionality into separate, manageable metadata definitions that can be independently configured for each data store connection. This segmentation allows developers to deploy and maintain individual binding configurations separately, reducing overall deployment complexity while enabling connections to multiple data stores through composed metadata sources.
Data Source
AI summary
Systems, methods and computer program products for dynamically binding data from a remote data source in a container-based mobile application are described herein. The method includes the steps of: 1) defining a metadata source that references both a mobile business object (MBO) and the mobile application, the MBO being connected to the remote data store; 2) binding an attribute from the MBO to the mobile application using the metadata source; and 3) changing, dynamically, the binding of the attribute while the mobile application is executing.