Registry-Based Packet Routing Architecture for Power Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized routing master designs in electric power delivery systems experience bottlenecks and delays as more services are added, leading to inefficiencies in data communication between intelligent electronic devices.

Innovation Solution

Implementing a registry that distributes routing information among services, allowing them to communicate directly without relying on a central routing master, by maintaining a list of active services and packet types consumed and produced by each service.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a centralized routing master design is used to route packets between services, then routing management is simplified and centralized, but traffic congestion and packet delivery delays occur as more services are added

Engineering Contradiction:
Improverouting management complexityVSAvoidpacket delivery delay
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent segments the centralized routing function into distributed routing components. Each service maintains its own routing information and makes independent routing decisions, eliminating the single-point bottleneck of the centralized routing master. This segmentation allows parallel packet processing across multiple services, reducing delivery delays while maintaining manageable routing complexity through standardized routing data structures.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If more services are added to the electric power delivery system, then system functionality and monitoring capabilities are enhanced, but routing bottlenecks and processing delays increase

Engineering Contradiction:
Improvesystem functionalityVSAvoiddata communication efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements dynamic routing where each service can independently adapt its routing behavior based on current system conditions and service requirements. Routing information is maintained in a flexible format that allows services to dynamically adjust packet forwarding decisions, enabling the system to scale functionality without proportionally increasing routing overhead or delays.

Inventive Principle:
Principle #15Dynamics

3Reliability

If a centralized routing master processes all packet routing, then routing decisions are centralized and consistent, but processing capacity becomes a bottleneck as service volume increases

Engineering Contradiction:
Improverouting decision consistencyVSAvoidpacket processing speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent creates copies of routing information and distributes them to multiple services rather than having a single centralized routing master. Each service maintains a local copy of relevant routing data, enabling independent and simultaneous packet processing. This copying approach maintains routing consistency through standardized data structures while dramatically increasing overall packet processing speed through parallel execution across multiple services.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10951518B2Packet routing architecture using a registry
Publication Date: 2021.03.16 SCHWEITZER ENGINEERING LABORATORIES INC
  • US10951518B2 patent drawing
  • US10951518B2 patent drawing
  • US10951518B2 patent drawing

AI summary

The present disclosure relates to packet routing using a registry to communicate packets between a first service and a second service of an electronic device. The electronic device may have memory that includes a registry having a table of services with at least one memory address of the second service being associated with consuming at least one packet type. The electronic device may store, in the first service, the at least one memory address of the second service and the at least one packet type. The electronic device may produce, via the first service, at least one packet of the at least one packet type. The electronic device may provide the at least one packet to the at least one memory address associated with the second service to allow the second service to consume data of the at least one packet.