Robot as a service

Robot as a service or robotics as a service (RaaS) is a cloud computing unit that facilitates the seamless integration of robot and embedded devices into Web and cloud computing environment. In terms of service-oriented architecture (SOA), a RaaS unit includes services for performing functionality, a service directory for discovery and publishing, and service clients for user's direct access.[1][2] The current RaaS implementation facilitates SOAP and RESTful communications between RaaS units and the other cloud computing units. Hardware support and standards are available to support RaaS implementation. Devices Profile for Web Services (DPWS) defines implementation constraints to enable secure Web Service messaging, discovery, description, and eventing on resource-constrained devices between Web services and devices.

RaaS can be considered a unit of the Internet of Things (IoT), Internet of Intelligent Things (IoIT) that deal with intelligent devices that have adequate computing capacity,[3] Cyber-physical system (CPS) that is a combination of a large computational and communication core and physical elements that can interact with the physical world,[4] and Autonomous decentralized system (ADS) whose components are designed to operate in a loosely coupled manner and data are shared through a content-oriented protocol.[5][6]

The more common usage of the term Robot as a Service (RaaS), is as a financial model for the purchase and use of a physical industrial or service robot. In a RaaS purchase contract, the buyer is paying for the use of the physical device through a subscription-based contract. RaaS is differentiated from a lease contract in that the original manufacturer continues to own the physical robotic device and carries the machine as an asset on its books. RaaS is becoming popular for many robotics equipment providers as the buyer can purchase the equipment through operating expense budgets rather than through a capital expenditure. The service contract for RaaS requires that the original manufacturer update and maintain the robot in good working order throughout the contract life. All parts and labor for preventative maintenance is also included in the RaaS contract. The original manufacturer may swap out the physical robot with another, equivalent machine at any time. In addition, the original manufacturer may provide remote service, via the Web, to remotely monitor, triage and repair, or recover the system. RaaS takes its name from the software as a service (SaaS) business model, popularized in the enterprise software market.

History

The initial design and implementation of applying service-oriented computing in embedded systems and robots was presented in the 49th IFIP 10.4 Workgroups meeting in February 2006.[7] In the initial design, a robot is the service client that looks up the service registry and consumes Web services on remote sites. Evolved from service-oriented robot, Robot as a Service is an all-in-one SOA unit, that is, the unit includes services for performing functionality, service directory for discovery and publishing, and applications for client’s direct access.[8] This all-in-one design gives the robot unit tools and capacity to be a self-contained cloud unit in the cloud computing environment. Based on RaaS concepts, a Visual IoT/Robotics Programming Language Environment (VIPLE) has been developed.

RaaS architecture

RaaS follows SOA and is a cloud computing unit. A RaaS unit acts as a service provider, a service broker, and as a service client:

  1. A RaaS cloud unit is a service provider: Each unit hosts a repository of preloaded services. A developer or a client can deploy new services into or remove service from a robot. The services can be used by this robot and can also be shared with other robots.
  2. A RaaS cloud contains a set of applications deployed: A developer or client can compose a new application (functionality) based on the services available in the unit and outside the unit.
  3. A RaaS unit is a service broker: a client can look up the services and applications available in the unit’s directory. A client can search and discover the applications and services deployed on the robot by browsing the directory. The services and applications can be organized in a hierarchy of classes to facilitate the discovery.

The main components of a RaaS unit and typical applications and services deployed. RaaS units are designed for the cloud computing environment. The services in RaaS will communicate with the drivers and other operating system components, which further communicate with the devices and other hardware components. The RaaS units can directly communicate with each other through Wi-Fi, if the wireless infrastructure is available or through ad hoc wireless network otherwise. The communication between RaaS and other services in the cloud are through standard service interface WSDL enabled by DPWS or RESTful service overall HTTP.

A few prototypes of RaaS have been implemented, which include both Web interface and physical devices.[9][10][11][12][13]

Dependability, including reliability and security are critical in RaaS design. Collaborating RaaS units can be scheduled for redundant execution, backing up each other’s operations. The redundant design can also address the instruction-level attack such as code injection and Return Oriented Programming (ROP) attacks. As the redundant RaaS units are independent of each other, instruction-level gadget programming is likely to generate different sequences in different devices. These differences in behaviors can be detected by the collaboration among the RaaS units. The major challenge in designing RaaS is to deal with the diversity of the networks, applications, and the environments or end users. In cloud computing, the network and communication protocols are limited to a few standards such WSDL, SOAP, HTTP, and RESTful architecture. In RaaS, HTTP, SOAP, and WSDL standards and robotics applications are the main design considerations.

Applications

RaaS can be used anywhere SOA, cloud computing, IoT, CPS, and ADS are used. One the application in computer science education. RaaS uses existing services to compose different applications at workflow level, which significantly reduce the learning curve of robotics programming.[14][15]

See also

References
  1. Yinong Chen, Zhihui Du, and Marcos Garcia-Acosta, M., "Robot as a Service in Cloud Computing", In Proceedings of the Fifth IEEE International Symposium on Service Oriented System Engineering (SOSE), Nanjing, June, 2010, pp. 151–158.
  2. Yinong Chen, H. Hu, "Internet of Intelligent Things and Robot as a Service", Simulation Modelling Practice and Theory, Volume 34, May 2013, Pages 159–171.
  3. Pranav Mehta, CTO, Intel Intelligent Systems Group: “Internet of Things and the Infrastructure”, Intel Embedded Research and Education Summit, February 2012, http://embedded.communities.intel.com/servlet/JiveServlet/downloadBody/7156-102-1-2402/Internet-of-Things-and-the-Infrastructure.pdf.
  4. Ragunathan (Raj) Rajkumar, Insup Lee, Lui Sha, and John Stankovic, “Cyber Physical Systems: The Next Computing Revolution”, 47th Design Automation Conference (DAC 2010), CPS Demystified Session, Anaheim, CA, June 17, 2010.
  5. Kinji Mori, Concept-Oriented Research and Development in Information Technology, Wiley Series in Systems Engineering and Management, 2014.
  6. M.B. Remy, M.B. Blake, Distributed Service-Oriented Robotics, IEEE Internet Computing, Volume:15 , Issue: 2, pp. 70–74, 2011.
  7. Yinong Chen, "Service-Oriented Computing in Recomposable Embedded Systems", Joint IARP/IEEE-RAS/EURON/IFIP 10.4 Workshop on Dependability in Robotics and Autonomous Systems, Tucson, AZ, February 15–19, 2006, http://webhost.laas.fr/TSF/IFIPWG/Workshops&Meetings/49/workshop/04%20chen.pdf
  8. Yinong Chen, Zhihui Du, and Marcos Garcia-Acosta, M., "Robot as a Service in Cloud Computing", In Proceedings of the Fifth IEEE International Symposium on Service Oriented System Engineering (SOSE), Nanjing, June, 2010, pp. 151–158.
  9. Yinong Chen, "Service-Oriented Computing in Recomposable Embedded Systems", Joint IARP/IEEE-RAS/EURON/IFIP 10.4 Workshop on Dependability in Robotics and Autonomous Systems, Tucson, AZ, February 15–19, 2006, http://webhost.laas.fr/TSF/IFIPWG/Workshops&Meetings/49/workshop/04%20chen.pdf
  10. Intel Autobot Web Service, 2012, http://venus.eas.asu.edu/WSRepository/RaaS/main/
  11. RaaS online programming environment, 2013, http://venus.eas.asu.edu/WSRepository/eRobotic/
  12. Zhihui Du, Weiqiang Yang, Yinong Chen, Xin Sun, Xiaoying Wang, and Chen Xu, "Design of a Robot Cloud Center", in 10th International Symposium on Autonomous Decentralized Systems (ISADS), Tokyo, March 2011, pp. 269–275.
  13. Robotics as a service implemented into robot, 2016, http://www.digitaltrends.com/cool-tech/qihan-sanbot/
  14. Yinong Chen, Zhizheng Zhou, "Service-Oriented Computing and Software Integration in Computing Curriculum", IPDPS Workshops 2014, pp. 1091–1098.
  15. Yinong Chen, Zhizheng Zhou, "Robot as a Service in Computing Curriculum”, 12th International Symposium on Autonomous Decentralized Systems (ISADS), Taichung, March 2015.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.