XML Meta Element for Non-IP OTA Protocol Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems lack a unified method for over-the-air (OTA) device management, making it difficult for network service providers to manage mobile devices and services using a single mechanism, as existing standards such as OMA DM, IOTA-HCM, IS-683, and proprietary protocols do not adequately address the need for integrated management.
Innovation Solution
A method and system that use an end-to-end IP protocol to accommodate non-IP OTA protocols by encapsulating non-IP protocol content in XML messages with a 'Meta' element, enabling the integration of different OTA protocols and providing a unified mechanism for managing mobile devices and services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple separate OTA management standards (OMA DM, IOTA-HCM, IS-683, proprietary protocols) are used to manage different mobile devices and services, then each standard can be optimized for specific device types or service requirements, but the overall system complexity increases and network service providers cannot use a single unified mechanism for device management
Solution Approach 1:
The patent applies universality by creating a unified OTA management protocol that can handle multiple device types and service requirements through a single mechanism. The protocol uses XML as a universal data representation format and incorporates a meta-element structure that can encapsulate different protocol-specific parameters, allowing one protocol to serve multiple functions across heterogeneous networks and device types.
Solution Approach 2:
The patent implements nesting by embedding protocol-specific content within a universal XML framework. The meta-element acts as a container that holds protocol-specific parameters and data structures, allowing the unified protocol to accommodate legacy and new features without requiring separate management systems for each protocol type.
2Ease of manufacture
If legacy non-IP OTA protocols are integrated with new IP-based protocols, then backward compatibility is maintained and existing components can be reused, but the system must handle multiple protocol formats simultaneously
Solution Approach 1:
The patent uses XML as an intermediary layer between legacy non-IP protocols and new IP-based protocols. The meta-element structure serves as a mediator that translates and encapsulates protocol-specific data into a universal format, allowing seamless integration of legacy and new protocols without requiring direct compatibility between them.
Solution Approach 2:
The patent applies parameter changes by modifying the data representation format of legacy protocols through XML encoding. The meta-element structure changes the parameters of protocol-specific data to fit within the universal XML framework, enabling legacy protocols to operate within the IP-based ecosystem without fundamental redesign.
3Device complexity
If a unified OTA management protocol is implemented to simplify device management, then system complexity is reduced and a single mechanism can be used for all devices, but the protocol must be designed to accommodate diverse and evolving device requirements
Solution Approach 1:
The patent implements dynamics through the flexible XML structure and meta-element configuration system. The protocol can dynamically adapt to diverse device requirements by configuring the meta-element with appropriate data types and structures, allowing the same unified protocol to serve different device types without requiring rigid predefined configurations for each.
Data Source
AI summary
Disclosed herein is a method, a system, a network node and a computer program executable by a data processor or data processors to accommodate a non-IP OTA protocol using an end-to-end IP protocol. The method includes receiving a message from a non-IP entity; using a markup language, such as XML, for message and content representation, where in an XML message non-IP protocol content is identified using an XML ‘Meta’ element, where the Meta element describes the content type as ‘non-IP protocol name’ and sending the XML message. The step of using XML preferably includes encapsulating received content in an XML message and using the XML Meta element to enable a receiver of the XML message to extract the content. The message received from the non-IP entity may be an IS-683 message.