OMA DM Relative URI Addressing for Unique Management Object Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The OMA DM protocol's relative URI addressing mechanism is inadequate for specifying unique management objects in management trees, especially when multiple objects have the same attribute values or when there are no leaf nodes directly under the root node, leading to ambiguity and inability to manage specific nodes effectively.
Innovation Solution
Modifying the conventional relative URI by adding attribute conditions or a time condition to the first part, allowing for the specification of multiple attribute values or time sequences, enabling the identification of unique management objects within the management tree.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the conventional relative URI with single attribute condition is used, then the addressing is simple, but it cannot uniquely specify management objects when multiple objects have the same attribute values
Solution Approach 1:
The URI syntax is segmented into multiple distinct components: URI parameter for sub-tree specification, MOID for object identification, multiple attribute conditions for unique identification, and time condition for temporal differentiation. This segmentation allows each component to serve a specific function, enabling unique identification of management objects while maintaining clear syntax structure.
Solution Approach 2:
The patent adds a time dimension to the URI addressing mechanism by introducing time conditions. This transforms the identification from a static single-attribute model to a dynamic multi-dimensional model that includes temporal information, enabling unique identification even when attribute values are identical across multiple objects.
2Measurement precision
If multiple attribute conditions are added to specify unique management objects, then the identification accuracy improves, but the URI syntax becomes more complex
Solution Approach 1:
The extended URI syntax is designed to be universal and adaptable. It can function with a single attribute condition for simple cases or with multiple attribute conditions and time conditions for complex identification needs. This multi-functionality allows the same syntax structure to handle both simple and complex identification scenarios without requiring different addressing mechanisms.
Solution Approach 2:
The URI syntax is made dynamic by allowing the inclusion of one or more attribute conditions and time conditions based on the specific identification needs. The syntax structure adapts to the complexity of the identification task, being simple when one condition suffices and more comprehensive when multiple conditions are required for unique identification.
3Adaptability or versatility
If the conventional relative URI is used, then the addressing mechanism is simple, but it fails when there are no leaf nodes directly under the root node
Solution Approach 1:
The patent performs preliminary action by specifying the path from the root node to the target management object through the URI parameter and MOID combination. This preliminary path specification ensures that even when no leaf nodes exist directly under the root node, the addressing mechanism can still locate the target object by establishing the path in advance through intermediate nodes.
Solution Approach 2:
The patent introduces intermediate nodes as mediators in the path from root to target. When no leaf nodes exist directly under the root node, these intermediate nodes serve as mediators to bridge the gap, allowing the URI mechanism to successfully address management objects in various tree structures including those with only intermediate nodes.
Data Source
AI summary
A method for addressing a management object in a management tree of a device management (DM) client and an associated DM system are disclosed to solve the issues encountered in the relative universal resource identifier (URI) addressing of the OMA DM protocol. The method comprises receiving a relative URI including a first part from a DM server, and identifying a root node of the management object according to the first part. The first part comprises a URI parameter for specifying a root node of a sub-tree of the management tree for finding the management object, a management object identifier, and a plurality of attribute conditions for specifying values of a plurality of leaf nodes directly under the root node of the management object.