OTA MIDP Provisioning for Non-MIDlet Applications on CDC Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile computing environments cannot use the Over the Air (OTA) Mobile Information Device Profile (MIDP) to provision non-MIDlet applications, such as Xlets and applets, to Connected Device Configuration (CDC) devices, limiting the ability to deliver content to these devices.
Innovation Solution
A method and system that prefixes an identifier for non-MIDlet applications to imply a MIDlet application, allowing them to be delivered through the OTA/MIDP protocol, using a server and client configuration to manage and classify these applications as Xlets or applets, enabling their provisioning to CDC-enabled devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the OTA/MIDP protocol is used to provision applications, then MIDlet applications can be delivered to CLDC/MIDP devices, but non-MIDlet applications (Xlets and applets) cannot be provisioned to CDC devices
Solution Approach 1:
The patent introduces a descriptor file as an intermediary component that bridges the gap between the MIDP protocol and non-MIDlet applications. The descriptor file contains metadata that identifies the application type (Xlet or applet) and provides configuration information, allowing the existing MIDP provisioning infrastructure to handle CDC devices without modifying the core protocol. This intermediary layer enables compatibility while maintaining protocol integrity.
Solution Approach 2:
The patent changes the parameter representation by introducing a new descriptor format that includes application type identification and configuration parameters. Instead of modifying the MIDP protocol itself, the solution changes the data structure parameters in the descriptor file to accommodate different application types, enabling the same protocol to provision multiple application formats to different device configurations.
2Ease of manufacture
If the OTA/MIDP infrastructure is used for provisioning, then existing provisioning servers can serve CLDC devices, but CDC devices cannot receive non-MIDlet applications through the same infrastructure
Solution Approach 1:
The patent makes the descriptor file structure universal by designing it to handle multiple application types (MIDlets, Xlets, and applets) through a common format. The descriptor includes flexible fields that can represent different application characteristics, allowing a single provisioning infrastructure to serve multiple device configurations and application types without requiring separate systems for each.
Solution Approach 2:
The descriptor file acts as a mediator between the provisioning server and diverse application types. It translates the needs of different application formats into a standardized representation that the existing MIDP infrastructure can process, enabling CDC devices to receive non-MIDlet applications through the same provisioning channel used for MIDlets.
3Adaptability or versatility
If non-MIDlet applications are provisioned to CDC devices, then content delivery capability is expanded, but the provisioning system must handle additional application types and interfaces
Solution Approach 1:
The patent segments the application provisioning process into distinct components: the descriptor file for metadata, the application binary for execution, and the provisioning protocol for delivery. By separating the identification (descriptor) from the execution (binary), the system can handle multiple application types through a unified mechanism, reducing the complexity of managing diverse application formats within the provisioning system.
Data Source
AI summary
A method for delivering a non-MIDlet application to a device associated with a connected device configuration (CDC) through an over the air (OTA) mobile information device profile (MIDP) protocol is provided. The method initiates with prefixing an identifier for the non-MIDlet application, wherein the identifier is configured to imply a MIDlet application. The method includes requesting the non-MIDlet application and determining a type of the non-MIDlet application. Then, the non-MIDlet application is managed with an interface application associated with the type of the application. A system and device configured to download a non-MIDlet application through a mobile information device profile (MIDP) are provided.