Cloud Robot Fleet Coordination Using Leader Heartbeats

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing robotic systems face inefficiencies in task distribution and management as they lack a centralized coordination mechanism, leading to redundant efforts and communication failures when multiple robots attempt to assign tasks without a leader, especially in large fleets.

Innovation Solution

A system where a fleet of robotic devices communicates with a server that maintains a list of active devices and tasks, allowing a leader robotic device to assign tasks based on device capabilities and heartbeats, ensuring efficient task distribution and fault tolerance by replacing the leader if it becomes inactive.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a centralized coordination mechanism is introduced to manage task distribution among robotic devices, then task management efficiency and system coordination improve, but device complexity and communication infrastructure requirements increase

Engineering Contradiction:
Improvetask management efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

A cloud server acts as an intermediary between robotic devices, maintaining centralized lists of active devices and tasks. The server coordinates task assignment by receiving heartbeat signals from robots, determining which robots are active, and distributing tasks accordingly, thereby improving coordination without requiring direct peer-to-peer communication infrastructure between robots

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If multiple robotic devices attempt to assign tasks without a designated leader, then device autonomy is maintained, but communication failures and redundant efforts occur

Engineering Contradiction:
Improvedevice autonomyVSAvoidcommunication reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The cloud server provides multiple functions: maintaining the list of active robotic devices, receiving heartbeat signals, determining device activity status, and assigning tasks. This multi-functional centralized system ensures reliable coordination while allowing individual robots to maintain operational autonomy within the coordinated framework

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

3Productivity

If a leader robotic device is designated to distribute tasks, then task assignment efficiency improves, but system vulnerability to leader failure increases

Engineering Contradiction:
Improvetask assignment efficiencyVSAvoidsystem reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

Robotic devices send periodic heartbeat signals to the cloud server, providing feedback on their active status. The server uses this feedback to determine which devices are available for task assignment and can identify when a leader device has failed, enabling dynamic task redistribution to maintain system reliability

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20240295880A1Robot Collaboration via Cloud Server
Publication Date: 2024.09.05 GDM HOLDING LLC
  • US20240295880A1 patent drawing
  • US20240295880A1 patent drawing
  • US20240295880A1 patent drawing

AI summary

A method includes receiving, by a robotic device, an indication that the robotic device was elected to be a leader robotic device by a plurality of robotic devices and receiving an indication of a new task in a remotely stored list of tasks. The method further includes determining, based on a remotely stored list of robotic devices, an additional robotic device to assign the new task. The remotely stored list of robotic devices comprises an entry for each respective robotic device of the plurality of robotic devices associating the respective robotic device with an identifier and a heartbeat. The method additionally includes assigning the new task to the additional robotic device based on the additional robotic device having an active heartbeat. Assigning the new task to the additional robotic device comprises associating the new task with the additional robotic device in the remotely stored list of tasks to cause the additional robotic device to carry out the new task.