URI Resolution for Device Management Node Addressing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current device management technologies face challenges in efficiently designating and resolving addresses for nodes, particularly when managing objects with the same management object identifier (MOID), unnamed nodes, and multiple addresses using a single node address, due to limitations in existing addressing schemes such as absolute, relative, and virtual URI methods.
Innovation Solution
A method and device for resolving uniform resource identifiers (URIs) that utilize a management object identifier (MOID) and management object instance identifier (MIID) to uniquely identify specific nodes within a device management tree, allowing for efficient designation of management object instances, unnamed nodes, and multiple addresses using a single node address through the use of instance URIs, MOID URIs, URIs using x-names, and URIs with wildcards.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional URI addressing schemes (absolute, relative, virtual) are used to designate nodes in device management, then basic node identification is possible, but efficient designation of management object instances with the same MOID, unnamed nodes, and multiple addresses using a single address cannot be achieved
Solution Approach 1:
The URI is segmented into distinct components: scheme, MOID, MIID, and path segments. Each component serves a specific function in node identification, allowing the system to efficiently designate specific nodes, unnamed nodes, and multiple addresses while maintaining a structured and manageable addressing scheme that reduces overall complexity
Solution Approach 2:
The instance URI scheme serves multiple functions: it can designate specific management object instances by MOID and MIID, address unnamed nodes using wildcard patterns, and represent multiple addresses through a single unified URI structure. This multi-functional capability eliminates the need for separate addressing mechanisms for different node types
2Productivity
If a single address is used to designate multiple nodes, then addressing efficiency is improved, but ambiguity in node identification occurs
Solution Approach 1:
The URI incorporates optional path segments that provide local differentiation within the hierarchical structure. While the MOID and MIID components can identify groups of nodes efficiently, the path segments (e.g., /segment1/segment2/leaf) add local specificity to precisely identify individual nodes within those groups, eliminating ambiguity while maintaining addressing efficiency
3Adaptability or versatility
If wildcard patterns are used to address unnamed nodes, then designation flexibility is improved, but precision in identifying specific nodes deteriorates
Solution Approach 1:
The URI scheme supports dynamic patterns using wildcards (e.g., * for any single segment, ** for any number of segments) that adapt to the actual node structure in the management information tree. This allows flexible designation of unnamed nodes while maintaining precision by matching the dynamic structure of the managed devices, resolving the contradiction between flexibility and precision
Data Source
AI summary
The present invention relates to a method for resolving, for device management, a uniform resource identifier (URI) indicating a particular node and an apparatus therefor, the method comprising the steps of: finding one or more MO instances in accordance with a management object identifier (MOID) and MO instance information comprised in the URI; and finding the particular node within the one or more MO instances by means of a path, comprised in the URI, from the MO instance root node to the particular node, wherein if the MO instance information comprises a management object instance identifier (MIID), then the step for finding one or more MO instances comprises finding a unique MO instance having the MOID and MIID, and, if an MO instance having the MOID and MIID does not exist or exists in multiples, then returning an error.


