Publish-Subscribe Data Sharing for Embedded Service Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Embedded devices face limitations in processing capability and memory due to restricted program and data sizes, making it difficult to execute services without pre-designating a connection destination for service provision from another device via a network.

Innovation Solution

An information processing system utilizing a publish/subscribe type data communication method, such as DDS, allows information processing devices to share data without designating a transmission destination, enabling automatic detection and addition/deletion of devices and distributing services among devices with varying processing capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If connection destination is designated in advance for service provision, then service execution is reliable, but setup requires manual configuration and increases complexity

Engineering Contradiction:
Improveservice execution reliabilityVSAvoidconnection setting complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables devices to automatically discover and select service providers without manual configuration. The information processing device autonomously receives service execution requests, publishes them to the network, and automatically selects connection destinations based on published service information, eliminating the need for manual connection settings while maintaining reliable service execution

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Service providers publish their service information and capabilities to the network in advance. This preliminary publication of service metadata allows requesting devices to automatically discover and select appropriate service providers without manual configuration, resolving the contradiction between reliability and setup complexity

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If service execution request is published to the network without designating transmission destination, then automatic device detection is enabled, but data transmission efficiency may be reduced

Engineering Contradiction:
Improveautomatic device detection capabilityVSAvoiddata transmission efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system introduces a publish/subscribe mechanism as an intermediary layer between service requesters and providers. Service requests are published to the network where they are automatically routed to appropriate subscribers (service providers) based on service type matching. This intermediary approach enables automatic device detection while maintaining transmission efficiency through targeted delivery rather than broadcast to all devices

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The network communication is segmented into service publication channels organized by service type. Instead of a single broadcast channel, the system divides communication into multiple specialized channels, allowing efficient routing of service requests to relevant providers while enabling automatic device detection within each service category

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3872624B1Information processing device, information processing system, and information processing method
Publication Date: 2023.01.04 TOSHIBA TEC KK
  • EP3872624B1 patent drawingFigure 1~2
  • EP3872624B1 patent drawingFigure 3
  • EP3872624B1 patent drawingFigure 4

AI summary

According to one embodiment, the information processing device shares shared data with another information processing device by exchanging the shared data that does not designate a transmission destination with the other information processing device. The information processing device includes a reception unit, an execution unit, and a publication unit. The reception unit receives first shared data including a first parameter and an execution request for requesting the execution of a first service using the first parameter. The execution unit outputs a first execution result by executing the first service according to the first shared data. The publication unit publishes second shared data including the first execution result.