EBIF Application Conversion for Web-Enabled Device Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
EBIF applications are limited to specific devices, restricting their interactive capabilities on non-compatible devices such as web-enabled devices like smartphones and tablets.
Innovation Solution
An EBIF-compatible system acts as an intermediary, converting EBIF applications to web formats like XML or HTML, enabling execution on web-enabled devices by processing user interactions and generating graphical interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If EBIF applications are transmitted directly to receiving devices, then device compatibility is maintained, but the reach to more devices and users is limited
Solution Approach 1:
The patent introduces an EBIF-compatible system as an intermediary between the EBIF application source and web-enabled devices. This intermediary converts EBIF applications into web-compatible formats (HTML, XML, JavaScript) so that web-enabled devices can execute them without requiring native EBIF compatibility. This resolves the contradiction by maintaining EBIF compatibility for the intermediary while enabling broader device reach through web standards.
2Adaptability or versatility
If EBIF applications are converted to web formats for broader device support, then device reach is improved, but conversion complexity is introduced
Solution Approach 1:
The EBIF-compatible system serves as a mediator that handles the conversion from EBIF to web formats. By centralizing this conversion function in a dedicated system, the complexity is contained and managed, while the end user experiences simplified access to applications on their web-enabled devices without needing to understand or manage the conversion process.
Solution Approach 2:
The system changes the format parameters of the application data from EBIF binary format to web-compatible text-based formats (HTML, XML, JavaScript). This parameter transformation enables the same application to be executed on diverse web-enabled devices while managing conversion complexity through standardized format mappings.
3Ease of operation
If user input is converted back to EBIF format for execution, then interactivity is enhanced, but processing time increases
Solution Approach 1:
The EBIF-compatible system acts as an intermediary that handles the bidirectional conversion between web formats and EBIF format for user interactions. This centralized conversion approach optimizes processing by maintaining efficient conversion routines and caching mechanisms, reducing the time penalty while preserving full interactivity.
Data Source
AI summary
A system may receive application data in a client-incompatible format and convert at least a portion of the application data into an alternate client-compatible format. In one example, the incompatible format may comprise Enhanced Binary Interchange Format (EBIF) while a client-compatible format may include a web format such as JavaScript, XML or HTML. Interactions (e.g., commands and user input) associated with the application may be received and converted. The interactions may then be processed using the application.