Software Component ID Allocation via DCinfo Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The OMA DM method lacks a standardized approach for correctly identifying and managing software components, leading to ambiguity when multiple Deployed Components (DCs) exist within a software package, causing issues for the DM server in performing subsequent management tasks.
Innovation Solution
A method and system where the DM server generates and transmits a download package with metadata or a new node (DCinfo) containing ID and file information for each software component, allowing the DM client to allocate unique IDs to each component, enabling the DM server to correctly identify and manage software components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the mobile device allocates an ID to each Deployed Component (DC) locally, then the device can manage software components autonomously, but the DM server becomes unaware of the DC IDs and cannot perform subsequent management tasks
Solution Approach 1:
The patent applies preliminary action by having the DM server pre-allocate DC IDs to software components before downloading them to the mobile device. The server generates and transmits DC information objects containing these pre-assigned IDs, ensuring that both the server and device share the same ID space from the outset. This eliminates the information loss problem while maintaining automated management, as the server retains knowledge of all DC IDs it has allocated.
2Adaptability or versatility
If multiple DCs exist within a software package with different ID, name, and version values, then the software package can be more versatile, but it becomes ambiguous how to determine the ID, name, and version values for each DC
Solution Approach 1:
The patent introduces an intermediary DC information object that serves as a bridge between the software package and individual DCs. This object contains structured information about each DC including its ID, name, version, and file path. By using this intermediary data structure, the system can handle multiple DCs with different values without ambiguity, as the DC information object explicitly defines the relationship between the software package and its constituent components.
3Adaptability or versatility
If the OMA DM specification does not define how name and version values are specified, then the specification remains flexible and adaptable, but implementation becomes inconsistent and ambiguous
Solution Approach 1:
The patent applies parameter changes by explicitly defining the name and version parameters within the DC information object structure. Instead of leaving these parameters undefined in the specification, the patent provides concrete guidance on how they should be determined and stored. This maintains the flexibility of the overall OMA DM framework while adding precision to specific implementation details, ensuring consistent behavior across different systems.
Data Source
AI summary
A method for allocating an identifier (ID) of a software component is disclosed. The method includes generating information on software components by a Device Management (DM) server, generating a download package including the information on software components by the DM server, transmitting the download package from the DM server to a DM client, executing the download package by the DM client, and allocating an ID to each software component based on the information on software components if the download package is executed by the DM client.