Logical Node Device Mapping for Configuration Change Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing device management systems face challenges in consistently managing devices over time, especially when devices are updated or relocated, as they often rely on device identification or location information as keys, making it difficult to associate pre-update and post-update devices or track changes in device locations.
Innovation Solution
A device configuration management apparatus that uses logical nodes as keys, associating them with locations and devices, and manages information using a relational data model, allowing for updates and changes in device and location associations, enabling consistent management even with device replacements or relocations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If device identification information is used as a key to manage device information, then individual device management is achieved, but it becomes difficult to associate pre-update and post-update devices when devices are replaced
Solution Approach 1:
The patent introduces location information as an intermediary key that mediates between device identification and physical placement. By using location information (e.g., facility name, installation position) as the primary key and device identification information as an associated attribute, the system enables continuous tracking of devices at specific locations even when individual devices are replaced. This resolves the contradiction by maintaining management consistency through location while allowing device updates.
Solution Approach 2:
The patent shifts the management dimension from device-centric (using device ID as key) to location-centric (using installation position as key). This dimensional change allows the system to manage devices based on where they are installed rather than what specific device is installed, enabling seamless device replacement while maintaining location-based management consistency.
2Ease of operation
If location information is used as a key to manage device information, then location-based management is achieved, but it becomes difficult to track device identification changes over time
Solution Approach 1:
The patent merges location information and device identification information into a unified management structure. The location information serves as the primary key for management operations, while device identification information is stored as an associated attribute. This combination enables both location-based management operations and tracking of device identification changes over time, as the system maintains the relationship between locations and devices through the unified data structure.
Solution Approach 2:
The patent implements feedback mechanisms that track changes in device identification information associated with specific locations. When device identification changes occur, the system records these changes while maintaining the location-based management structure, providing feedback on device updates without disrupting location-based operations.
3Measurement precision
If device identification information is used as a key, then individual device tracking is enabled, but device replacements disrupt the management process
Solution Approach 1:
The patent uses location information as a stable intermediary that remains constant during device replacements. While device identification information may change when devices are replaced, the location information serves as a stable anchor that maintains the management structure. This resolves the contradiction by decoupling the stability requirement from device identification and anchoring it to location information instead.
4Adaptability or versatility
If location information is used as a key, then device relocations are simplified, but association between devices and specific installations is lost
Solution Approach 1:
The patent combines location information (for relocation flexibility) with device identification information (for specific installation association) in a unified management structure. The location serves as the primary key enabling flexible relocation operations, while device identification is maintained as an associated attribute ensuring reliable device-location associations. This merging approach resolves the contradiction by enabling both relocation flexibility and association reliability simultaneously.
Data Source
Figure 1
Figure 2
Figure 3~5
AI summary
A device configuration management apparatus includes a logical node information storage storing logical node information about a logical node that can be associated with a particular device and a particular location, the logical node information including for each of logical nodes a device ID for identifying the particular device and location information which is information for identifying the location, a network information storage storing network information as a set of information about an edge connecting two logical nodes, and a node update processer configured to perform processing for updating at least one of the device ID and the location information with regard to the particular logical node in the logical node information stored in the logical node information storage.