9. RoboEarth Cloud Engine
• Motivation
Execution
Onboard
data size [bits]
Cloud
Execution
allowed delay [ms]
• What exactly is the RoboEarth Cloud Engine ?
• It is a PaaS with a clone-based model
Roboticists solve the essentially same tasks over and over and over again – no reuse!!
Our solution: Away from INDIVIDUAL solutions towards COMMON solutionsRobots can share experience
Map of world wide human knowledge exchange over internet
I hope the video gave some motivation. And here is a different way to look at the motivation. Let’s project all robotic applications into this space spanned by the I/O data size and allowed delay. The red line whose gradient is the data rate separates applications that can run on board and on the cloud. And the good news is mobile communication guys are doing . They try to do rendering on the cloud for mobile games. For us robotisists this means redline getting steeper and making more applications cloud executables.Enough with motivation.Before going into more detail let me first define what exactly it is. It is platform as a service with a clone based model + A PaaS because we allow users to deploy their own applications and use it. To see what we mean by a clone based model let’s move onto the next slide
Why clone based ? Because every physical robot has a system level clone ( or a computational instance ) on the cloud. In addition to that the system level clones can be tightly interconnected. Two extreams of usageNow let’s look at the different parts. Let me start with the green box, which is the system level clone. It is implemented using a linux container (a light weight virtualization) Cool aspects of the container: You can peacefully sleep at night while allowing others to run their programs on your servers. You can control CPU usage, disk I/O, network traffic. And what is inside ? Re_comm_nodeApp Engine Manager All the magic happens: Several processes running with different privilegesI manages the contanersIt functionas as the software router that are capable of streaming data in memory/cpu efficient Now the communication with the robot. We made this parts very very modular so that users can have their own protocol. By default we are providing websockets based one
