Remote Control System Multicast Update Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing remote control systems face challenges in efficiently transmitting parameter change notifications across a network, leading to delayed reflections in controller displays and increased network bandwidth and CPU load, particularly when multiple controllers are involved.

Innovation Solution

The system employs a virtual current memory synchronized with the controlled device's memory, using unicast for change commands and multicast for update information, along with a synchronization data transmission mechanism that includes error correction to ensure reliable data transfer with reduced network load.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If notification is sent frequently and reliably using unicast to all controllers, then the reliability of parameter update transmission is improved, but the number of packets increases leading to increased network bandwidth consumption and CPU load

Engineering Contradiction:
Improvereliability of parameter update transmissionVSAvoidnumber of packets transmitted
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system segments the communication into two distinct types: unicast for requesting updates and multicast for broadcasting updates. This segmentation allows the system to use the most efficient communication method for each purpose, reducing overall network traffic while maintaining reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The controlled device acts as an intermediary that receives unicast requests from controllers and then proactively pushes update information to all controllers via multicast. This intermediary approach eliminates the need for multiple unicast transmissions from each controller to the controlled device, significantly reducing packet count while ensuring reliable delivery.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Quantity of substance

If notification is sent by broadcasting to all controllers, then the number of packets is reduced and network load is minimized, but the reliability of transmission cannot be guaranteed

Engineering Contradiction:
Improvenumber of packets transmittedVSAvoidarrival guarantee of notification
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system performs preliminary action by having the controller send a unicast request to the controlled device before the actual update transmission. This preliminary request establishes a reliable communication channel and triggers the controlled device to prepare and send the update information via multicast, ensuring both reliability and efficiency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback through the unicast request mechanism where the controller explicitly requests update information from the controlled device. This feedback loop ensures that updates are only transmitted when needed and that the transmission is initiated by a reliable request, combining the efficiency of multicast with the reliability of unicast confirmation.

Inventive Principle:
Principle #23Feedback

3Speed

If parameter updates are transmitted to all controllers immediately upon change, then the synchronization speed is improved, but the network bandwidth consumption and CPU load increase

Engineering Contradiction:
Improvesynchronization speed of parameter updatesVSAvoiddata amount transmitted
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The system uses periodic action by having the controlled device transmit update information in response to specific triggers (unicast requests) rather than continuously or immediately on every change. This periodic transmission based on demand maintains synchronization speed while significantly reducing the overall data amount transmitted across the network.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system changes the transmission parameter from continuous/immediate transmission to on-demand transmission triggered by unicast requests. This parameter change in the communication strategy maintains the speed of synchronization when needed while reducing unnecessary transmissions, thereby lowering network bandwidth consumption and CPU load.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8688252B2Remote control system and communication system
Publication Date: 2014.04.01 YAMAHA CORP
  • US8688252B2 patent drawing
  • US8688252B2 patent drawing
  • US8688252B2 patent drawing

AI summary

When a controlled device has changed the value of a parameter, the controlled device transmits the result of the change as updated information UPDATE to controllers by multicast, and aside from this, also transmits synchronization data SYNC in each synchronization period by multicast. Upon detecting a reception error of those data, the controller requests, from the controlled device, the information of the parameter which has been changed in one or more synchronization periods including and after the synchronization period subsequent to the last synchronization period in which the controller could normally receive all of the packets, and corrects the parameter value in the controller based on the current value of the changed parameter transmitted from the controlled device in response to the request.