ROS Data Synchronization for Persistent Calibration Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Robot Operating System (ROS) lacks a robust data persisting mechanism, leading to data inconsistency and abnormal system conditions due to the inflexibility of existing solutions that do not automatically notify programming nodes of updated calibration data, which is crucial for driverless vehicles.

Innovation Solution

A method and apparatus for synchronizing data in ROS by detecting operations on data transmission between communication processes, determining if the data are persistent, and transmitting change messages to other processes to maintain data consistency, utilizing a detecting unit, determining unit, and transmitting unit to set and manage data persistency flags and registration information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data are written into a hard disk in the form of a file, then data can be persisted, but the robot operating system cannot automatically notify programming nodes of updates, resulting in data inconsistency

Engineering Contradiction:
Improvedata consistencyVSAvoidautomatic notification capability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements a feedback mechanism where the system monitors file system events (create, modify, delete operations) and automatically notifies subscribed programming nodes when persistent data changes. This feedback loop ensures all nodes receive real-time updates about data changes, maintaining data consistency across the system without manual intervention.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary component (data synchronization mechanism) that sits between the file system and programming nodes. This intermediary monitors file operations, determines which data are persistent, and selectively notifies relevant nodes, thereby automating the notification process while maintaining data consistency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a data synchronization mechanism is implemented, then data consistency is maintained, but system complexity increases

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a self-service mechanism where programming nodes automatically register their data interests with the synchronization system. The system then autonomously monitors file operations and selectively notifies only those nodes subscribed to specific data types, reducing the need for complex centralized control while maintaining data consistency.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent segments the data synchronization mechanism into modular components: file operation monitoring, persistence determination, node subscription management, and selective notification. This segmentation allows each component to handle specific tasks independently, reducing overall system complexity while ensuring comprehensive data consistency.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11126639B2Method and apparatus for synchronizing data in a robot operating system
Publication Date: 2021.09.21 BEIJING BAIDU NETCOM SCI & TECH CO LTD
  • US11126639B2 patent drawing
  • US11126639B2 patent drawing
  • US11126639B2 patent drawing

AI summary

This present application discloses a method and apparatus for synchronizing data in a robot operating system. A specific implementation of the method includes: detecting an operation on data being transmitted between communication processes, wherein the operation includes at least one of updating the data, deleting the data, and storing the data; determining whether the data are persistent data, in response to positively detecting an operation on the data being transmitted between the communication processes; and transmitting a change message of the data to communication processes other than the communication processes in response to positively determining that the data are persistent data. In the embodiment, the persistent data may always remain consistent across the communication processes.