Wireless Application UI Data Mapping Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing software applications for wireless devices is complex due to resource constraints and the need for platform-specific native applications, which are not platform-independent and require extensive coding and multiple versions for different devices.
Innovation Solution
A system and method for managing the user interface of wireless devices through direct mapping between application data domains and UI screens, using atomic data and screen component definitions in a structured definition language like XML, enabling dynamic and interactive screens with reduced resource consumption and simplified development.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If native applications are developed for each device platform, then application performance and device optimization are improved, but device complexity and development time increase due to requiring multiple versions
Solution Approach 1:
The patent implements a universal application architecture where a single application written in Java can run across multiple device platforms (wireless phones, PDAs, personal computers) through the use of abstract data components and screen components that are platform-independent, eliminating the need to develop separate native applications for each platform while maintaining optimized performance
2Adaptability or versatility
If explicit coding is used to map screen elements to data components, then customization and control are improved, but development complexity and time increase
Solution Approach 1:
The patent implements automatic mapping between screen components and data components through the use of metadata-driven configuration. The system automatically generates the mapping relationships based on component definitions and metadata, eliminating the need for manual explicit coding while maintaining full customization capability through configurable parameters and metadata attributes
3Loss of information
If data is requested from Web Service for each screen display, then data freshness is improved, but resource consumption and response time worsen due to repeated requests
Solution Approach 1:
The patent implements data caching mechanisms where data is retrieved from Web Services in advance and stored locally in the application. The cached data is then reused for subsequent screen displays, reducing the frequency of Web Service requests while maintaining data freshness through selective updates based on metadata-defined refresh criteria
4Reliability
If application size is increased to include all device-specific optimizations, then application performance on specific platforms is improved, but memory resources and device storage are taxed
Solution Approach 1:
The patent employs a compact universal application design where platform-specific optimizations are achieved through configuration and metadata rather than duplicating entire application versions. The single Java-based application footprint remains small while achieving native-like performance on each platform through the abstract component architecture and runtime adaptation
Data Source
AI summary
A system and method for generating a screen element, based on a data object, of a component application is disclosed. The component application includes a data component having a data field definition and a screen component having a screen element definition. A mapping manager identifies a mapping present in the screen component. The mapping specifies dynamic relationships between the screen component and the data component by an identifier, and for selecting the data component mapped by the mapping according to the mapping identifier. The mapping manager maintains dynamic integrity and automatically synchronizes changes between the screen component and the corresponding data component. A data manager obtains a data object field value corresponding to the data field definition of the mapped data component; and a presentation manager generates a screen element from the screen element definition to include the data object field value.