Automated Address Assignment for Cascading Interconnected Units

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing master-slave systems with interconnected units face challenges in efficiently addressing and configuring units, especially in larger systems with geographically dispersed units, leading to costly and time-consuming configuration and maintenance, as well as issues with address collisions and manual dipswitch settings.

Innovation Solution

A method where a controlling unit performs a system start-up procedure by transmitting requests to identify units and their cascading ports, assigning unique addresses, and recording them, allowing for automated configuration without prior software configuration, enabling 'plug and play' capability and avoiding address collisions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual dipswitch settings are used for address assignment, then unique addressing is achieved, but configuration time and cost increase significantly

Engineering Contradiction:
Improveaddressing accuracyVSAvoidconfiguration time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system enables automated address assignment where the controlling unit automatically detects connected units and assigns addresses without requiring manual dipswitch configuration. The unit responds to identification requests with its type information, and the controller autonomously calculates and assigns unique addresses based on the unit type and connection topology.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements preliminary address assignment during system startup before normal operation begins. The controlling unit performs address assignment as part of the initialization sequence, ensuring all units have valid addresses before the system becomes operational, thereby eliminating post-installation configuration needs.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If fixed address assignment per unit type is used, then addressing is simplified, but scalability to multiple units of the same type is limited

Engineering Contradiction:
Improveaddressing complexityVSAvoidsystem scalability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The address space is segmented into two parts: a unit type identifier (first address part) and a unique instance identifier (second address part). This segmentation allows multiple units of the same type to be distinguished by their instance identifiers while maintaining simple type-based classification, enabling both simplified addressing and unlimited scalability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from one-dimensional fixed addressing to two-dimensional addressing by adding the instance identifier dimension. Units are first categorized by type (first dimension) and then distinguished by instance number (second dimension), allowing systematic expansion while maintaining addressing simplicity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Measurement precision

If Ethernet/MAC addressing is used, then unique addressing is guaranteed, but system cost and complexity increase

Engineering Contradiction:
Improveaddressing uniquenessVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent employs a simplified addressing scheme that uses basic data link layer protocols instead of complex Ethernet/MAC addressing. The address structure uses straightforward type identifiers and instance numbers rather than hierarchical MAC addresses, reducing protocol complexity and implementation cost while maintaining sufficient uniqueness for master-slave systems.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

4Adaptability or versatility

If cascading ports are added for system expansion, then scalability improves, but address collision risk increases

Engineering Contradiction:
Improvesystem scalabilityVSAvoidaddressing reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements a feedback mechanism where the controlling unit sends identification requests to detected units and processes their responses to verify address uniqueness. The unit responds with its type information, and the controller uses this feedback to calculate and assign addresses that are guaranteed to be unique within the cascaded topology, preventing address collisions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3357219B1Addressing in a system of interconnected units
Publication Date: 2020.06.03 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3357219B1 patent drawingFigure 1
  • EP3357219B1 patent drawingFigure 2
  • EP3357219B1 patent drawingFigure 3~5

AI summary

A controlling unit (101) retrieves information regarding system (100) interconnect topology and assigns unique address to all connected units (102,103,104,105) without the need for any prior configuration. An added unit with cascading ports will be able to use the address assignment that enables the controller (101) to avoid address collisions between connected units. In short, the disclosure provides the system (100) of interconnected units with a "plug and play" capability