Decentralized Service Data Point Architecture for Intelligent Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing intelligent network systems require a central instance, such as an intelligent router, which can lead to a single point of failure and are not scalable for distributed data storage and retrieval applications like storage area networks and factory automation networks.

Innovation Solution

A service data point (SDP) architecture where each node can act as an entry point for data requests, using broadcast messages to query other nodes for data, eliminating the need for a central router and allowing for scalable and decentralized data storage and retrieval without a central or replicated register.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a central instance (intelligent router) is used to route requests from SCP to SDPs, then request routing is achieved, but a single point of failure is created and scalability is limited

Engineering Contradiction:
Improvesystem reliabilityVSAvoidcentralized architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the centralized routing function into distributed components. Each SDP node maintains its own routing information and can independently respond to information requests from SCPs. The routing function is divided among multiple nodes rather than concentrated in a single intelligent router, eliminating the single point of failure while maintaining routing capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of having a central router direct requests to specific SDPs, the patent inverts the approach by allowing any SDP node to receive requests and then broadcast queries to find the required data. The request flow is reversed: rather than central routing pushing requests to the right destination, any node can pull requests and distribute queries peer-to-peer to locate data.

Inventive Principle:
Principle #13The other way round (Inversion)

2Adaptability or versatility

If a central instance is used for data storage and retrieval, then data access is centralized, but scalability for distributed applications is hindered

Engineering Contradiction:
Improveadaptability to distributed applicationsVSAvoidconfiguration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Each SDP node is designed to be universal and multi-functional. Any node can receive information requests from SCPs, perform local database queries, broadcast queries to other nodes, receive responses, and return results to SCPs. This universal capability across all nodes enables the system to adapt to various distributed applications including SANs and factory automation networks without requiring specialized configuration.

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

Solution Approach 2:

The system implements self-service through automatic broadcast querying and response collection. When a node receives an information request it cannot fulfill locally, it automatically broadcasts a query message to all other nodes and collects responses. This self-service mechanism eliminates the need for external configuration or central management intervention, reducing configuration complexity while enabling distributed data access.

Inventive Principle:
Principle #25Self-service

3Reliability

If broadcast messages are used to query other nodes, then data retrieval is achieved without central router, but network traffic increases

Engineering Contradiction:
Improveavoidance of single point of failureVSAvoidnetwork traffic overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies partial action by broadcasting queries only when necessary. Nodes first attempt local database queries before broadcasting to other nodes. Additionally, broadcast queries are sent only to the extent needed - when local data is insufficient - rather than continuously or excessively. This partial broadcasting approach maintains reliability through distributed querying while minimizing unnecessary network traffic overhead.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP2207363B1Electronic apparatus, intelligent network and intelligent network implemented data processing method
Publication Date: 2012.10.31 ORGA SYST GMBH
  • EP2207363B1 patent drawingFigure 1
  • EP2207363B1 patent drawingFigure 2
  • EP2207363B1 patent drawingFigure 3

AI summary

The present invention relates to an electronic apparatus, such as a service data point for an intelligent network, the service data point (110) comprising a plurality of nodes (1, 2, 3, ..., i) being coupled by a network (114), each node of the plurality of nodes comprising: - means (130) for receiving an information request (124) from a service control point (106) of the intelligent network, the information request carrying an identifier of at least one subscriber (116, 118) of the intelligent network, - a database (132) for storing subscriber data, - information retrieval means (134) for querying the database using the identifier, - broadcast means (136) for sending a broadcast message (138) to all other nodes of the plurality of nodes of the service data point, the broadcast message carrying the identifier of the at least one subscriber.