Network Component Commissioning via Automatic Address Assignment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current networked systems face inefficiencies and errors in addressing and commissioning components, particularly during deployment, maintenance, and replacement, due to manual processes and limitations in addressing mechanisms, which can lead to incorrect integration and maintenance issues.

Innovation Solution

A computer-implemented method and association file server that automatically associate commissioning files with components in a networked environment using unique network identifiers and dynamic addressing, eliminating the need for manual address assignment and ensuring components are updated with the latest commissioning files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual address assignment is used, then devices can be addressed in the network, but the process is tedious and prone to human error

Engineering Contradiction:
Improveaddressing accuracyVSAvoidaddress assignment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service through automatic address assignment where the addressing server autonomously assigns addresses to devices without manual intervention. The server receives device identifiers, automatically generates appropriate addresses, and configures them on devices, eliminating the need for personnel to manually adjust mechanical switches and reducing both time and errors.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces mechanical address assignment methods (manual adjustment of mechanical switches) with an electronic automated system. The addressing server uses electronic communication to assign and configure addresses on devices, substituting the mechanical switch-based approach with a software-driven solution that is faster and more reliable.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If fixed static addresses are assigned, then devices can be identified, but the process requires manual server access and is tedious

Engineering Contradiction:
Improvedevice identificationVSAvoidaddress assignment operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system enables self-service through automatic address assignment where the addressing server autonomously assigns addresses to devices without manual intervention. The server receives device identifiers, automatically generates appropriate addresses, and configures them on devices, eliminating the need for personnel to manually access the server and providing addresses.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The addressing server acts as an intermediary between device identification and address configuration. It receives device identifiers, processes them through automatic assignment algorithms, and mediates the connection between device hardware and network addressing, eliminating the need for direct manual server access.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If components are replaced manually, then replacement can occur, but commissioning files may not be updated and integration errors occur

Engineering Contradiction:
Improvecomponent replacementVSAvoidintegration accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements feedback through automatic detection and verification. When a device is replaced or added, the addressing server automatically detects the change, verifies the device identifier, and confirms proper address assignment and commissioning file configuration. This feedback loop ensures integration accuracy without manual verification.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by pre-configuring commissioning files and address assignments before devices are actually deployed or replaced. The addressing server prepares the appropriate configuration data in advance, so when a device is installed or replaced, the commissioning process is already prepared and can be automatically applied, ensuring reliability.

Inventive Principle:
Principle #10Preliminary action

4Quantity of substance

If the system supports more devices, then network capacity increases, but addressing mechanisms become insufficient

Engineering Contradiction:
Improvenumber of devicesVSAvoidaddressing mechanism
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent implements dynamic addressing where the addressing server can automatically generate and assign addresses from a pool of available addresses, and dynamically adjust address allocations as devices are added or removed. This dynamic approach allows the system to scale to support more devices without requiring a fixed, complex addressing scheme.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The addressing server provides universal functionality by handling multiple tasks: receiving device identifiers, generating addresses, configuring devices, managing commissioning files, and detecting device changes. This multi-functional approach consolidates what would otherwise require multiple separate mechanisms into a single system that can support a large number of devices.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP2580889B1Device commissioning and replacement
Publication Date: 2016.01.27 SCHNEIDER ELECTRIC USA INC
  • EP2580889B1 patent drawingFigure 1
  • EP2580889B1 patent drawingFigure 2
  • EP2580889B1 patent drawingFigure 3a

AI summary

Systems and methods for associating commissioning files with components in a networked environment are provided. In one embodiment, a unique network identifier of a system component, such as a MAC address, and a network address, such as an IPv4 address may stored in an association file to link components on a network layout map to specific commissioning files. The network address may have a lease configured to infinity or to a power cycle of a component on the network. Further aspects relate to detecting if a system component has been replaced with another component. The detection may determine whether the new component has a unique network identifier not located in a association file. A user input may indicate whether the component is new or a replacement. If the new component is a replacement for another component, the unique network identifier of the first system component may be received and recorded.