Robot service management system and method thereof

Abstract

A robot service management system includes a service sending / receiving module, a dispatching module, a robot group, a monitoring module, a storage module, and a credential module. The service sending / receiving module receives and sends task information. The dispatching module is connected to the service sending / receiving module. The dispatching module generates dispatch information based on the task information. The robot group is wirelessly connected to the dispatching module. The robot group executes the dispatch information. The monitoring module is wirelessly connected to the robot group. The monitoring module obtains monitoring information based on status signals from the robot group. The storage module is connected to the dispatching module and the monitoring module, and is used to store the dispatch information and the monitoring information. The credential module is connected to the storage module and wirelessly connected to the robot group. The credential module obtains credential information based on the dispatch information and the monitoring information, wherein the robot group includes at least one robot. Each robot includes a communication module, a sensing device, a control module, and a mobility device. The control module is connected to the communication module, the sensing device, and the mobility device. The control module, communication module, and sensing device are located within the mobile device. The control module receives entry information via the communication module, receives an elevator image captured by the sensing device in response to the entry information, analyzes the elevator image to identify the internal space of the elevator, and drives the mobile device based on the internal space.

Description

Robot Service Management System and Its Method This case is about a service management system, especially a robot service management system and its method. Accommodation providers formulate different forms of service processes according to different service types. Generally speaking, the service process sequentially includes filling out a service operation requirement form, preparing service information products, preparing service equipment, the process of service operations, and the acceptance of service operations. However, the service processes of various departments such as the management department, housekeeping department, and catering department are independent of each other and not centrally managed, resulting in waste of service resources and affecting the overall service efficiency. Moreover, accommodation operators cannot fully grasp the completion status and effectiveness of each service task. In some embodiments, a robot service management system includes a service receiving and sending module, a dispatching module, a robot group, a monitoring module, a storage module, and a certificate module. The service receiving and sending module is used to receive and send a task information. The dispatching module is connected to the service receiving and sending module and is used to generate a dispatching information according to the task information. The robot group is wirelessly connected to the dispatching module and is used to execute the dispatching information. The monitoring module is connected to the robot group. The monitoring module is used to receive at least one status signal from the robot group and obtain a monitoring information according to the status signal of the robot group. The storage module is connected to the dispatching module and the monitoring module and is used to store the dispatching information and the monitoring information. The certificate module is connected to the dispatching module and is wirelessly connected to the robot group. The certificate module is used to obtain a certificate information according to the dispatching information and the monitoring information, where the robot group includes at least one robot. The robot includes a communication module, a sensing device, a control module, and a mobile device. The control module is connected to the communication module, the sensing device, and the mobile device. The control module, the communication module, and the sensing device are located in the mobile device, and the control module receives an incoming information via the communication module, responds to the incoming information to receive an elevator image captured by the sensing device, analyzes the elevator image to identify the internal space of the elevator, and drives the mobile device according to the internal space. In some embodiments, the task information includes an item data and a location data, the dispatching information includes a route data, and the dispatching module is further used to generate the route data according to the item data, the location data, and a first map information. In some embodiments, the robot group includes a plurality of robots, the monitoring information includes the current status information of the plurality of robots, the current status information of each robot includes an idle data, and the dispatching module is further used to transmit the dispatching information to a selected robot among at least one robot according to the idle data of each robot. In some embodiments, the robot group includes a plurality of robots, the monitoring information includes the current status information of the plurality of robots, the current status information of each robot includes an idle data and a power data, and the dispatching module is further configured to transmit dispatching information to a selected robot among at least one robot according to the project data, the location data, and the idle data and power data of each robot. In some embodiments, the robot group includes at least one robot, the monitoring information includes the current status information of the plurality of robots, the current status information of each robot includes an idle data, a power data, and a location data, and the dispatching module is further configured to transmit dispatching information to a selected robot among at least one robot according to the project data, the location data, and the idle data, power data, and location data of each robot. In some embodiments, the dispatching information includes: a project data, the robot includes a communication module, a control module, and a mobile device, the control module is connected to the communication module and the mobile device, the control module and the communication module are located on the mobile device, and the control module is further configured to generate an arrival data after completing the project data, transmit the arrival data to the monitoring module via the communication module, and drive the mobile device to return to a starting location. In some embodiments, the certificate information includes a completion certificate and an abnormal certificate. When the robot arrives at the starting location, the control module is further configured to generate a return data and transmit the return data to the certificate module via the communication module, and the certificate module confirms whether the dispatching information and the arrival data of the robot exist when receiving the return data of any robot, generates a completion certificate in response to the existence of the dispatching information and the arrival data of the same robot, and generates an abnormal certificate in response to the non-existence of the arrival data of the same robot. In some embodiments, the dispatching information includes a first map information; the robot includes a communication module, a control module, a storage module, and a mobile device, the control module is connected to the communication module, the storage module, and the mobile device, the control module, the communication module, and the storage module are located on the mobile device, the storage module stores a second map information, and the control module is further configured to download the first map information via the communication module and update the second map information with the first map information. In some embodiments, the second map information includes a charging location data; the robot further includes a power supply module, the power supply module is connected to the control module and is located on the mobile device, the power supply module stores a remaining power and provides the power required for the operation of the robot with the remaining power, and the control module drives the mobile device according to the charging location data in response to the remaining power being lower than or equal to a threshold. In some embodiments, the dispatch information includes a disinfection data; a robot in the robot group includes a disinfection device, a communication module, a control module, and a mobile device. The control module is connected to the communication module, the disinfection device, and the mobile device. The control module, the communication module, and the disinfection device are located on the mobile device, and the control module receives the dispatch information via the communication module and controls the disinfection device according to the disinfection data. In some embodiments, a robot service management method stores at least one monitoring information of at least one robot, obtains a task information, generates a dispatch information according to the task information, and transmits the dispatch information to a selected robot among at least one robot according to the monitoring information of each robot. The robot service management method includes receiving at least one status signal from at least one robot, relative to the monitoring information of the robot; updating the monitoring information of the robot relative to the status signal of each robot; and obtaining a certificate information relative to the dispatch information and the monitoring information. In some embodiments, the transmitting step selects one from the at least one robot as the selected robot according to an idle data of the monitoring information, an item data, and a location data of the dispatch information; and transmits the dispatch information to the selected robot. In some embodiments, the transmitting step includes selecting one from the at least one robot as the selected robot according to an idle data and a power data of the monitoring information, an item data, and a location data of the dispatch information, and transmitting the dispatch information to the selected robot. In some embodiments, the transmitting step includes selecting one from the at least one robot as the selected robot according to an idle data, a power data, and a location data of the monitoring information, an item data, and a location data of the dispatch information, and transmitting the dispatch information to the selected robot. In some embodiments, it further includes receiving a return data from any one of the robots; wherein, the obtaining step is executed in response to the return data, and the obtaining step includes checking the dispatch information and the monitoring information in response to the return data; generating a completion certificate when the dispatch information of the robot that sends the return data exists and there is an arrival data of the robot that sends the return data in the monitoring information; and generating an abnormal certificate when the dispatch information of the robot that sends the return data exists and there is no arrival data in the monitoring information. In some embodiments, it further includes the selected robot executing the dispatch information, and the selected robot transmits the arrival data and returns to a starting location when completing an item data of the dispatch information; the selected robot transmits the return data when arriving at the starting location; receiving and recording an arrival data from the selected robot in the certificate information. In summary, the robot service management system and method of any embodiment can effectively integrate task information, link monitoring information of the service process, effectively grasp the completion degree of task information, and improve overall efficiency. In some embodiments, the robot service management system and method can also select a suitable robot according to the idle state of the robot, the amount of power, and the length of the moving path to execute the dispatch information. The robot can move to different floors to execute the dispatch information, control the robot to perform disinfection, or any combination thereof. Please refer to FIG. 1. A robot service management system includes a system main body 10 and a robot group 30. Among them, the system main body 10 includes a service receiving and sending module 110, a dispatch module 120, a monitoring module 140, a credential module 150, and a storage module 160. The robot service management system is applicable to provide and manage a service. Among them, the applicable services can be, for example, hotel services, catering services, or tour guide services, etc. The service receiving and sending module 110 is connected to the dispatch module 120. The dispatch module 120, the monitoring module 140, and the credential module 150 are connected to the storage module 160. The dispatch module 120 and the monitoring module 140 are wirelessly connected to the robot group 30. Please refer to FIGS. 1 and 2. The robot group 30 is composed of one or more robots 31. The storage module 160 stores a monitoring information (step S110). Here, the monitoring information records the current various states of each robot 31 (hereinafter referred to as the current state). Specifically, the monitoring information includes the current state information of each robot 31. The service receiving and sending module 110 is used to receive and send a task information (step S120). Among them, this task information corresponds to a service demand. In other words, a task information represents a work task, and by executing this work task, the corresponding service demand can be provided. Therefore, this task information includes an item data for indicating the task content of this work task, a time data for indicating the time when this work task needs to be executed, and a location data for indicating the completion location of this work task. In some embodiments, taking hotel service as an example, if the task information represents a work task for providing the service demand of cleaning room 301 and providing mineral water at 8:00 in the morning, the item data included in this task information is "clean the room and provide mineral water", the time data for executing the task included in this task information is "8:00 in the morning", and the location data for executing the task included in this task information is "room 301". In addition, the task information can also represent the work task of delivering room supplies, the work task of disinfecting the hotel gym, or the work task of greeting guests in the hotel lobby. The dispatching module 120 is used to generate a dispatching information according to the task information (step S130). Each dispatching information includes corresponding task information, an identification data for indicating the robot 31 that executes this execution task, and a route data for indicating the movement route when performing this execution task. In other words, each dispatching information includes item data, location data, time data, identification data, and route data. In some embodiments, the dispatching module 120 also stores the generated dispatching information in the storage module 160. Please refer to FIGS. 1 and 2. Moreover, the dispatching module 120 also assigns (transmits) the dispatching information to a certain robot 31 (hereinafter referred to as the selected robot 31a) in the robot group 30 according to the monitoring information (step S140, i.e., the transmission step), so that the selected robot 31a executes the dispatching information to provide the service requirements corresponding to this execution task (step S150). In some embodiments, the system main body 10 of the robot service management system may further include a network module 170, and the dispatching module 120 is connected to the network module 170. The dispatching module 120 communicates with any robot 31 in the robot group 30 through the network module 170, so that the dispatching module 120 can transmit the dispatching information to the assigned selected robot 31a via a network 20. Please refer to FIGS. 1 and 2. The monitoring module 140 receives status signals from each robot 31 (step S160), and then updates the monitoring information correspondingly according to the received status signals (step S170). Among them, the status signal can be a current status signal. Specifically, the monitoring module 140 receives the current status signals of all the robots 31 in the robot group 30 at a fixed period or an unfixed period, and then forms the current status information of each robot 31 according to the received current status signals, and updates the current status information of this robot 31 in the monitoring information with the formed current status information of each robot 31. In other words, the monitoring module 140 monitors the current status of all the robots 31 at any time and updates the monitoring information accordingly. In some embodiments, the system main body 10 of the robot service management system may further include a network module 170, and the monitoring module 140 is connected to the network module 170. The monitoring module 140 communicates with any robot 31 in the robot group 30 through the network module 170, so that the monitoring module 140 can receive the status signals from each robot 31 via the network 20. Please refer to FIGS. 1 and 2. The credential module 150 obtains a credential information according to the dispatch information and the monitoring information (step S180). In some embodiments, during the execution of the dispatch information by the selected robot 31a, the selected robot 31a reports its working status to the robot service management system. Specifically, the selected robot 31a sends a working status signal to the monitoring module 140 via the network 20. At this time, the monitoring module 140 forms the working status information of this robot 31 according to the received working status signal, and stores the formed working status information in the storage module 160. In other words, the status signal can also be a working status signal. The monitoring information also includes the working status information of each robot 31. Herein, the monitoring module 140 monitors the working status of the selected robot 31a at any time and updates the monitoring information accordingly. After the selected robot 31a completes the dispatch information, the credential module 150 can determine whether the generated credential information is a completion credential or an abnormal credential by verifying the monitoring information in the storage module 160. Please refer to FIG. 1. In some embodiments, the service transceiver module 110 can be connected to the execution management system 40 of each execution unit in a wired or wireless manner, and receives task information from the execution management system 40 (an example of step S120). In other words, the system main body 10 of the robot service management system can further include a network module 170, and the service transceiver module 110 is connected to the network module 170. The robot service management system communicates with the execution management system 40 of each execution unit through the network module 170, so that the service transceiver module 110 can receive the task information sent from the execution management system 40 via the network 20. In some embodiments, the execution management system 40 of each execution unit can receive the data of the service requirements needed by the service recipient (such as task items, task time, task location, or a combination thereof) through the user interface 130 (such as a keyboard and a mouse, or a touch screen, etc.), and form task information accordingly. Then, the execution management system 40 transmits the task information to the robot service management system via the network 20, so that the robot 31 can provide service requirements to the service recipient according to this task information. In some embodiments, taking hotel service as an example, the execution unit can be, for example, the front desk, the management department, the food and beverage department, or the housekeeping department, etc. Please refer to FIG. 1. In some embodiments, the system main body 10 of the robot service management system can further include a user interface 130. The service transceiver module 110 is connected to the user interface 130. Herein, the user interface 130 can provide the user to input the service requirements needed by the service recipient. In other words, the service transceiver module 110 can receive various data of the service requirements needed by the service recipient through the user interface 130 and form task information accordingly (another example of step S120). In some embodiments, the format of the task information may be a structured data format, an unstructured data format, or a combination thereof. Among them, the structured data format includes data in a structured form in an application information system, such as data in a relational database. Please refer to FIG. 1. In some embodiments, the service transceiver module 110 is further connected to the storage module 160. The service transceiver module 110 stores the obtained task information in the storage module 160 and instantaneously updates the task information newly added by each execution management system 40 in the robot service management system for future access and verification. In some embodiments, the task information in the unstructured data format may be, for example, sequential text digital data in the JSON (JavaScript Object Notation) data exchange format. Please refer to FIG. 1. In some embodiments, the dispatch information sent by the dispatch module 120 to the robot 31 can be encrypted using an asymmetric encryption algorithm. In other words, in the signal received by the robot 31 from the dispatch module 120, in addition to the dispatch information, there is also a hash value (hereinafter referred to as the first hash value) obtained by operating on the dispatch information using the asymmetric encryption algorithm. Therefore, after receiving the wireless signal, the robot 31 first operates on the dispatch information using the same asymmetric encryption algorithm to obtain another hash value (hereinafter referred to as the second hash value) and checks whether the second hash value is the same as the first hash value to determine whether the received dispatch information can be adopted. Here, when the encrypted hash value is the same as the original hash value, the robot 31 determines that the dispatch information has not been tampered with. Among them, the asymmetric encryption algorithm may be, for example, algorithms such as RSA, ElGamal, Elliptic Curve Cryptosystems (ECC), or Diffie–Hellman key exchange. Please refer to FIGS. 1 and 2. In some embodiments, the current state of the robot 31 may include its own state and movement state. The own state may be, for example, the remaining power (i.e., the power remaining in the robot 31 currently), the life of each lamp tube, the movement speed, the presence or absence of storage space, or any combination thereof. The movement state may be, for example, the current position, the floor where it is located, whether it takes the elevator, or any combination thereof. Specifically, the current state information of each robot 31 includes idle data for indicating whether this robot 31 is currently working or idle, power data for indicating the amount of remaining power of this robot 31, and position data for indicating the position where this robot 31 is currently located. In some embodiments, the current state signal carries one or more types of data such as idle data, power data, position data, or any combination thereof. Therefore, when the monitoring module 140 receives the current state signal from any robot 31 (an example of step S160), the monitoring module 140 reads one or more types of data carried in the current state signal and correspondingly updates the same type of data of this robot 31 stored in the storage module 160 (an example of step S160). Please refer to FIGS. 1 and 3. In some embodiments, the robot 31 may include a moving device 311, a communication module 312, a power module 313, and a control module 314. The control module 314 is connected to the drive circuit 311b of the moving device 311, the communication module 312, and the power module 313. The communication module 312, the power module 313, and the control module 314 are located within the housing 311a of the moving device 311. The control module 314 is used to control the moving device 311, the communication module 312, and the power module 313. The power module 313 stores an amount of power and is used to supply the power required for the operation of the robot 31 with this amount of power, that is, to supply power to each component of the robot 31 that needs to be powered (such as the moving device 311, the communication module 312, and the control module 314, etc.). The control module 314 can be wirelessly connected to the monitoring module 140 and the dispatching module 120 via the communication module 312, and then receive the dispatching information sent by the dispatching module 120 and send the status signal (i.e., the current state signal and / or the working state signal) to the monitoring module 140 via the network 20, that is, the robot 31 communicates with the system main body 10. The moving device 311 enables the robot 31 to move at a traveling speed. Specifically, when the control module 314 executes the dispatching information, the control module 314 enables the drive circuit 311b of the moving device 311 to drive the moving mechanism 311c of the moving device 311. Here, the moving mechanism 311c moves relative to the ground, thus causing the robot 31 to move on the ground. And, the control module 314 also controls the moving mechanism 311c of the moving device 311 according to the dispatching information, so that the robot 31 moves along the route indicated by the route data. Please refer to FIGS. 1 and 3. In some embodiments, the robot 31 may further include a positioning module 315. The positioning module 315 is located within the mobile device 311 and is connected to the control module 314. The positioning module 315 generates position data based on the position of the robot 31. For example, the position data may include planar data (such as longitude and latitude) representing the planar position of the robot 31 and altitude data (such as floor or altitude) representing the relative vertical altitude of the robot 31. Among them, the altitude data corresponds to a floor data. Please refer to FIGS. 1 and 3. In some embodiments, when the robot 31 is to send a current status signal, the control module 314 obtains position data from the positioning module 315, obtains power consumption data from the power module 313, generates a current status signal based on the obtained position data and power consumption data, and sends it to the monitoring module 140 via the communication module 312. Please refer to FIGS. 1 and 2. In some embodiments, a map information (hereinafter referred to as the first map information) may also be stored in the storage module 160. In an example of step S130, the dispatching module 120 may generate a route data based on the item data and location data of the task information, the position data of each robot 31 in the monitoring information, and the first map information. Specifically, the dispatching module 120 may obtain the location data and item data from the task information, obtain the position data from the current status information of the selected robot 31a in the monitoring information, and calculate, according to the item data, the route in the first map information from the location represented by the position data to the location represented by the location data and the route from the location represented by the location data back to the starting location, that is, obtain the route data. Among them, the starting location may be the location represented by the position data, or other specified locations. In some embodiments, taking hotel service as an example, the map information includes the floor plans of all floors of the hotel. The route data is the traveling route for the robot 31 to move from its current location (i.e., the position data) to the location where the work task is to be performed (i.e., the location data). In some embodiments, the dispatching module 120 confirms whether there is an intermediate location according to the item data. This intermediate location refers to a location that needs to be passed through before reaching the location represented by the location data, such as a spare parts location for collecting spare parts, a location for changing altitude data, or a work storage location for collecting cleaning tools, etc. If there is an intermediate location, the dispatching module 120 calculates the route in the first map information from the location represented by the position data through the intermediate location to the location represented by the location data and the route from the location represented by the location data back to the starting location, that is, obtains the route data. Otherwise, the dispatching module 120 calculates the route in the first map information from the location represented by the position data to the location represented by the location data and the route from the location represented by the location data back to the starting location, that is, obtains the route data. Please refer to FIGS. 1 and 3. When the selected robot 31a executes the dispatch information, the control module 314 continuously obtains position data from the positioning module 315 and controls the movement mechanism 311c to adjust the direction according to the obtained position data and the route data in the dispatch information, so that the selected robot 31a advances along the route indicated by the route data. For example, when the item data represents the delivery of housekeeping supplies, the route data represents the route of the selected robot 31a from its current location (i.e., the position data) to the supply location where the selected robot 31a can obtain the supplies, and the route of the selected robot 31a moving from the supply location to the location where the work task is to be performed (i.e., the location data). In some embodiments, the positioning module 315 can be implemented by a Global Positioning System (GPS) or an inertial sensor. In some embodiments, the positioning module 315 can also calculate the position data by an algorithm based on wireless signals (such as Wi-Fi signals, Bluetooth signals, or Ultra-Wideband (UWB), etc.) obtained by the communication module 312 or images collected by the sensing module. Here, the algorithms applicable to calculating the position data are well-known to those skilled in the art, so they will not be elaborated further. Please refer to FIGS. 1 and 3. In some embodiments, whenever the selected robot 31a starts to execute the dispatch information, the control module 314 of the selected robot 31a generates idle data representing being at work and sends a current status signal with this idle data to the monitoring module 140 via the communication module 312, so that the monitoring module 140 updates the idle data (i.e., the monitoring information) of the current status information of this selected robot 31a in the storage module 160 accordingly. And when entering the idle state (such as when the selected robot 31a completes the work task or returns to the starting location), the selected robot 31a generates idle data representing being idle and sends a current status signal with this idle data to the monitoring module 140 via the communication module 312, so that the monitoring module 140 updates the idle data (i.e., the monitoring information) of the current status information of this selected robot 31a in the storage module 160 accordingly. In this way, the robot service management system can grasp whether each robot 31 is currently in an idle state or in a state of executing dispatch information (i.e., at work) based on the idle data of each robot 31 in the monitoring information. Please refer to FIGS. 1 and 2. In an exemplary embodiment of step S140, the dispatch module 120 selects one idle robot 31 from the robot group 30 as the selected robot 31a according to the idle data of each robot 31 in the monitoring information, and transmits the dispatch information to this selected robot 31a via the network module 170. Based on this, it can be avoided that the robot 31 receiving the dispatch information cannot immediately execute the received dispatch information because it is executing another dispatch information, thereby improving the overall work efficiency of the robot group 30. Please refer to FIGS. 1 and 2. In another exemplary embodiment of step S140, the dispatching module 120 may also select a suitable robot 31 from the robot group 30 as the selected robot 31a according to the idle data and power data of each robot 31 in the task information and the monitoring information, and transmit the dispatching information to the selected robot 31a. Specifically, the dispatching module 120 estimates the power consumption (hereinafter referred to as the estimated power) required for the robot 31 to execute the dispatching information based on the item data and the route data in the task information. Then, based on this estimated power, the power data and the idle data of each robot 31 in the monitoring information, the dispatching module 120 selects one of the robots 31 in the idle state and with the remaining power greater than or equal to the estimated power from the robot group 30 as the selected robot 31a, and transmits the dispatching information to this selected robot 31 via the network module 170. Herein, this route data may be a route from a starting location to the location where the work task is executed, and the starting location may be the location where the idle robot 31 in the robot group 30 is located. Therefore, it can be avoided that the selected robot 31 fails to effectively complete the task due to insufficient power. For example, it can be avoided that the robot 31 stops on the road due to power exhaustion during the execution of the dispatching information or first diverts to a charging location for charging, thus delaying the completion of the task. Specifically, during the process of selecting a suitable robot 31, the dispatching module 120 selects a robot 31 with sufficient power as the selected robot 31a from the plurality of robots in the idle state according to the plurality of idle data and the plurality of power data, and transmits the dispatching information to the selected robot 31a. In some embodiments, the dispatching module 120 determines the estimated power according to the dispatching information, and then selects a matching robot 31 as the selected robot 31a from one or more robots 31 in the idle state based on the estimated power and the power data of all the robots 31. Please refer to FIGS. 1 and 2. In another exemplary embodiment of step S140, the dispatching module 120 may further select a suitable robot 31 as the selected robot 31a according to the idle data, power data, and location data of each robot 31 in the task information and the monitoring information, and transmit the dispatching information to the selected robot 31a. Herein, the dispatching module 120 determines the length of the path that each robot 31 moves when executing the dispatching information according to the location data and project data of the task information and the location data of each robot 31. Therefore, in addition to determining the selected robot 31 according to the idle state and power state of each robot 31, the dispatching module 120 further determines the selected robot 31 according to the length of the path that the robot 31 moves when executing the dispatching information, so as to improve the overall working efficiency of the robot group 30. Specifically, the dispatching module 120 selects the robots 31 in the idle state from the robot group 30 according to the idle data and power data of each robot 31. The dispatching module 120 then calculates the path (hereinafter referred to as the task path, that is, the shortest route from the location represented by the location data to the location represented by the location data, and whether this shortest route passes through the intermediate location depends on the project data) that each idle robot 31 moves when executing the dispatching information and the estimated power required for moving along the corresponding task path by using the location data of each idle robot 31 and the location data and project data of the task information. Then, the dispatching module 120 selects the robot 31 with the shortest corresponding task path as the selected robot 31a from the robots 31 in the idle state and with the remaining power matching the estimated power, that is, transmits the dispatching information to the robot 31 that is in the idle state, has sufficient remaining power, and has the shortest corresponding task path. Please refer to FIG. 1. In some embodiments, the monitoring module 140 can also be used to monitor electronic devices outside the robot service management system, such as elevators, electric doors, escalators, or any combination thereof. The location data includes a height data (hereinafter referred to as the first height data) and a plane data (hereinafter referred to as the first plane data), and the location data includes another height data (hereinafter referred to as the second height data) and another plane data (hereinafter referred to as the second plane data). Assume that the first height data does not match the second height data. For example: the floors represented by the first height data are different from the floors represented by the second height data. The route data of the dispatching information includes an intermediate location. Hereinafter, the intermediate location is taken as the first elevator door as an example. Please refer to FIG. 1. During the process of executing the dispatch information, the selected robot 31a generates a call signal at the first elevator door and transmits the call signal to the monitoring module 140. The call signal includes position data representing the location of the selected robot 31a, and this position data includes a height data (hereinafter referred to as the third height data) representing the floor where the selected robot 31a is located and a plane data (hereinafter referred to as the third plane data) representing the plane position (i.e., the midway position) where the selected robot 31a is located. The monitoring module 140 knows the floor and plane position of the selected robot 31a based on the call signal and the floor data. Specifically, the monitoring module 140 can obtain the third height data and the third plane data from the call signal, control a first elevator corresponding to the third plane data to the floor corresponding to the third height data, and send an entry command back to the selected robot 31a after the first elevator arrives at the floor corresponding to the third height data. After the selected robot 31a executes the entry command, it enters the first elevator. When the first elevator moves to the floor represented by the second height data, the first elevator sends a arrival signal to the monitoring module 140. After receiving the arrival signal, the monitoring module 140 sends a continuation command to the selected robot 31a, causing the moving device 311 of the selected robot 31a to respond to the continuation command, leave the first elevator, and continue to move along the route data. Therefore, when the robot 31 needs to go to different height data to perform work tasks, the selected robot 31a can change its height, thereby effectively completing the work tasks. Please refer to FIGS. 1 to 4. In some embodiments, one or more robots 31 in the robot group 30 may have a sensing device 316. For dispatch information where the first height data does not match the second height data, the dispatch module 120 will select a robot 31 with a sensing device 316 as the selected robot 31a. In other words, the robot 31 may further include a sensing device 316. The sensing device 316 is located inside the moving device 311 and its lens is embedded in the housing 311a of the moving device 311. The sensing device 316 is connected to the control module 314 and powered by the power module 313. The control module 314 receives the entry command via the communication module 312, responds to the entry command to receive an elevator image captured by the sensing device 316, performs image analysis of the elevator image to identify the internal space of the first elevator, and drives the moving device 311 to move the selected robot 31a from the entrance of the first elevator to inside the first elevator when the identified internal space is sufficient for the selected robot 31a to enter. Specifically, before the selected robot 31a enters the first elevator, the control module 314 will first use the elevator image captured by the sensing device 316 to determine whether the remaining space inside the first elevator is sufficient for the selected robot 31a to enter. Once the control module 314 determines that it can enter, the control module 314 will control the moving device 311 to move forward, enabling the selected robot 31a to enter the first elevator for boarding. Please refer to FIGS. 1 to 4. In some embodiments, when the control module 314 determines that the remaining space is insufficient for the selected robot 31a to enter, the control module 314 controls the mobile device 311 to stop moving, so that the selected robot 31a remains stationary in place and does not enter the first elevator. Then, the control module 314 issues another call signal (hereinafter referred to as a re-call signal) to the monitoring module 140 and the dispatching module 120. The monitoring module 140 controls another elevator corresponding to the third plane data (hereinafter referred to as the second elevator) to move to the floor corresponding to the third height data according to the re-call signal. The dispatching module 120 generates and transmits a transfer route data to the control module 314 according to the re-call signal, the third plane data, and the plane position of the second elevator. The control module 314 receives the transfer route data via the communication module 312 and controls the mobile device 311 to move to the location of the second elevator according to the transfer route information. Among them, at the entrance of the second elevator, the selected robot 31a determines whether to enter the second elevator in the same way as it determines whether to enter the first elevator. In some embodiments, during the execution of the dispatching information, the control module 314 can determine whether to continue to execute this dispatching information (i.e., re-transmit the call signal) when it encounters the situation of being unable to enter the elevator again according to the number of times the call signal is sent. Please refer to FIGS. 1 to 4. In some embodiments, when the control module 314 determines that the remaining space is insufficient for the selected robot 31a to enter, the control module 314 can decide not to continue to execute the dispatching information, and control the mobile device 311 to move so that the selected robot 31a returns to the starting point. In some embodiments, the call signal may further include an event data. This event data represents an event of an external electronic device to be called, such as calling an elevator. Please refer to FIGS. 1 to 4. In some embodiments, the dispatching information includes: an item data. The control module 314 is further used to generate an arrival data after completing the item data, and drive the mobile device 311 to move to the starting point. Here, the control module 314 transmits a working status signal with this arrival data to the monitoring module 140 via the communication module 312. The monitoring module 140 then records this arrival data in the working status information of the selected robot 31a in the monitoring information. In some embodiments, the starting point can be a preset gathering location of the robot group 30, the location where the selected robot 31a starts to execute the dispatching information, the location of the idle robot 31, or the charging location where the robot 31 charges. After the selected robot 31a executes the dispatching information or the dispatching information cannot be completed, it moves to the starting point. And, when arriving at the starting point, the control module 314 generates a return data and transmits the return data to the credential module 150 via the communication module 312. Please refer to FIGS. 1, 2 and 3. In some embodiments, the certificate information includes a completion certificate and an abnormal certificate. When the certificate module 150 receives the return data of any robot 31, it confirms whether the dispatch information and arrival data of the robot 31 exist (i.e., whether they are stored in the storage module 160). A completion certificate is generated in response to the existence of the dispatch information and arrival data of the same robot 31 (i.e., the robot 31 that sends the return data), and an abnormal certificate is generated in response to the non-existence of the arrival data of the same robot 31. Therefore, the abnormal certificate indicates that an abnormality occurred during the execution of the dispatch task by the robot 31 and it could not be successfully completed. In addition, the abnormal certificate will record various reasons for the failure to complete the task for relevant personnel to adjust the relevant work processes based on the abnormal certificate in the future. Please refer to FIGS. 1 to 4. In some embodiments, each robot 31 may further include a storage module 317. The storage module 317 is located inside the housing 311a of the mobile device 311 and is connected to the control module 314. The storage module 317 stores a map information (hereinafter referred to as the second map information). The control module 314 further downloads the first map information from the system main body 10 via the communication module 312 and updates the second map information with the first map information. Specifically, the dispatch module 120 may transmit the first map information simultaneously when the first map is updated or when the dispatch information is transmitted. When the control module 314 of the selected robot 31a receives the first map information, it will determine whether there is a difference between the first map information and the second map information. When the control module 314 determines that there is a difference, it means that the second map information needs to be updated. The control module 314 then updates the second map information with the first map information downloaded from the dispatch module 120. Conversely, if there is no difference, the control module 314 directly discards the received first map information. Please refer to FIGS. 1 and 3. In some embodiments, the first map information transmitted by the dispatch module 120 to the robot 31 can be encrypted using an asymmetric encryption algorithm. In other words, in the signal received by the control module 314 from the dispatch module 120, in addition to the first map information, there is also a hash value (hereinafter referred to as the third hash value) obtained by operating on the first map information using the asymmetric encryption algorithm. Before updating the second map information, the control module 314 will first determine whether the first map information comes from a legitimate source based on the third hash value, that is, whether the third hash value is correct, to avoid updating incorrect map information. Specifically, the control module 314 first operates on the received first map information using the same asymmetric encryption algorithm to obtain another hash value (hereinafter referred to as the fourth hash value) and confirms whether the third hash value is the same as the fourth hash value, so as to determine whether the received first map information can be adopted. If they are the same, then the first map information can be adopted, that is, it comes from a legitimate source. Conversely, if they are different, then the first map information cannot be adopted, that is, it comes from an illegitimate source. Please refer to FIGS. 1 to 4. In some embodiments, the second map information includes a charging location data representing a charging location. Herein, when the remaining power is lower than or equal to a threshold, the control module 314 drives the mobile device 311 to move to the charging location according to the charging point data, so that the robot 31 moves to the charging location for charging. Please refer to FIGS. 1, 2, 5 and 6. In some embodiments, the item data of the dispatch information may be a disinfection data. The robot group 30 may have one or more robots 31 including a disinfection device 318. Specifically, the robot 31 with the disinfection device 318 is the disinfection robot 31b. For the dispatch information with the disinfection data, the dispatch module 120 selects an idle disinfection robot 31b from the robot group 30 as the selected robot 31a. Therefore, when the control module 314 receives this dispatch information via the communication module 312, it controls the disinfection device 318 to perform disinfection according to the disinfection data therein. In some embodiments, the disinfection device 318 is (for example but not limited to) a disinfection spray device or an ultraviolet light device. The disinfection spray device sprays the disinfectant liquid (such as alcohol) in a mist form. Please refer to FIG. 5. In some embodiments, the disinfection device 318 may include a plurality of UVC lamp tubes 318a and a driving circuit 318b. The plurality of UVC lamp tubes 318a are located on the mobile device 311. Each UVC lamp tube 318a is used to emit an ultraviolet light. The driving circuit 318b is connected to the plurality of UVC lamp tubes 318a and is located on the mobile device 311. The driving circuit 318b is used to drive the plurality of UVC lamp tubes 318a. The control module 314 is connected to the mobile device 311, the communication module 312 and the driving circuit 318b. The control module 314 is located on the mobile device 311 and is used to receive the dispatch information via the communication module 312. The control module 314 enables the mobile device 311 and the driving circuit 318b according to the dispatch information. Please refer to FIGS. 1 to 4. For example, taking hotel service as an example, assume that the position of the idle robot 31 is on the first floor of the hotel, the spare parts are located in the basement of the hotel, and the task information is that room 601 needs mineral water. After the service transceiver module 110 receives the task information (step S120), it will transmit the task information to the dispatching module 120. The dispatching module 120 generates dispatching information according to the task information (step S130). The dispatching module 120 obtains monitoring information from the monitoring module 140 (step S110). The dispatching module 120 selects a suitable robot 31 as the selected robot 31a from the robot group 30 according to the information in the monitoring information (such as idle data, power data, and position data), and transmits the delivery information to the selected robot 31a (step S140). The selected robot 31a executes the dispatching information and moves to the location represented by the position data to perform the work task. During the process of the selected robot 31a executing the dispatching information, if it needs to move to different floors to execute the dispatching information, the selected robot 31a will first move to the first elevator and then send a call signal to the monitoring module 140. After receiving the call signal, the monitoring module 140 will control the first elevator to move to the floor where the selected robot 31a is located. When the first elevator moves to the floor where the robot 31 is located, the first elevator will send an arrival signal to the monitoring module 140. After receiving the arrival signal, the monitoring module 140 will send an entry command to the selected robot 31a to command the selected robot 31a to enter the first elevator. When the first elevator arrives at the floor represented by the location data, the first elevator will send an arrival information to the monitoring module 140. After receiving the arrival information, the monitoring module 140 will send a continue command to the selected robot 31a, so that the moving device 311 of the selected robot 31a responds to the continue command, leaves the first elevator, and continues to move along the route data. Before the selected robot 31a enters the first elevator, the sensing device 316 obtains the elevator image of the first elevator. When the control module 314 determines that the space in the first elevator is sufficient for the selected robot 31a to enter according to the elevator image, the control module 314 drives the moving device 311 to act, so that the selected robot 31a moves from the entrance of the first elevator to the inside of the first elevator. When the control module 314 determines that the space in the first elevator is not sufficient for the selected robot 31a to enter according to the elevator image, the control module 314 will control the moving device 311 to stop, so that the selected robot 31a stops in place and does not enter the first elevator. The control module 314 will send a re-call information to the monitoring module 140 and the dispatching module 120. After receiving the re-call information, the monitoring module 140 will control the second elevator to move to the floor where the selected robot 31a is located. The dispatching module 120 generates and returns a transfer route data to the control module 314 according to the re-call signal, the third plane data, and the plane position of the second elevator. The control module 314 receives the transfer route data via the communication module 312 and controls the moving device 311 to move to the location of the second elevator according to the transfer route information.When the selected robot 31a generates arrival data after completing the project data and drives the mobile device 311 to move to the starting location. Here, the control module 314 will transmit a working status signal with the arrival data to the monitoring module 140 via the communication module 312. When the monitoring module 140 receives the working status signal and the robot 31 arrives at the starting location, when it arrives at the starting location, the control module 314 will generate a return data and transmit the return data to the certificate module 150 via the communication module 312. When the certificate module 150 receives the return data, if the dispatch information and the arrival information exist, the certificate module 150 will generate a completion certificate. On the contrary, if the arrival data does not exist, the certificate module 150 will generate an abnormal certificate (step S180). During the process of the control module 314 executing the dispatch information, the control module 314 will obtain position data from the positioning module 315, obtain power data from the power module 313, generate a current status signal from the obtained position data and power data and send it to the monitoring module 140 via the communication module 312. So that the monitoring module 140 obtains the current status signal of the selected robot 31a (step S160). Then the monitoring module 140 updates the monitoring information according to the received current status signal (step S170). In this way, the entire robot service management is completed. Please refer to FIG. 1. In some embodiments, the system main body 10 can be one or more computer hosts, or one or more servers. Among them, the service transceiver module 110, the dispatch module 120, the user interface 130, and the certificate module 150 can be implemented by one or more processors. In some embodiments, the storage module 160 and the storage module 317 can be implemented by one or more memories, one or more hard disk drives, or one or more solid-state drives respectively. In some embodiments, the network module 170 can be implemented by a communication chip, a transceiver, or a circuit that supports wireless LAN (WLAN), Wireless Broadband (Wibro), Worldwide Interoperability for Microwave Access (Wimax), High-Speed Downlink Packet Access (HSDPA), or other types of Wireless Wide Area Network (WWAN) communication technologies. In some embodiments, the moving mechanism 311c of the mobile device 311 has a motor and a wheel set or a belt set connected to the motor. The drive circuit 311b of the mobile device 311 applies a voltage to the motor, and the motor rotates the wheel set or the belt set, thereby driving the robot 31 to move forward. In some embodiments, the control module 314 can be implemented by one or more processors. In some embodiments, the power module 313 includes a storage battery and a charge and discharge circuit connected to the storage battery. In some embodiments, the communication module 312 may be implemented by a communication chip, transceiver, circuit, 4G network, 5G network that supports wireless LAN (WLAN), wireless broadband (Wibro), worldwide interoperability for microwave access (Wimax), high-speed downlink packet access (HSDPA), or other types of wireless wide area network (WWAN) communication technologies. In some embodiments, the sensing device 316 may be implemented by a lidar, an ultrasonic, a camera, or a video camera. In summary, the robot service management system and method according to any embodiment can effectively integrate task information, link monitoring information of the service process, effectively grasp the completion degree of task information, and improve overall efficiency. In some embodiments, the robot service management system and method can also select a suitable robot according to the idle state, battery level, and path length of the robot to execute dispatch information, the robot can move to different floors to execute dispatch information, control the robot to perform disinfection, or any combination thereof. Although the technical content of this case has been disclosed as above in various embodiments, however, it is not intended to limit the protection scope of this case. Any person with ordinary knowledge in the field to which this case belongs, without departing from the spirit of this case, any changes or modifications made shall fall within the scope of protection of this case. Therefore, the protection scope of this case shall be subject to the content of the patent application scope. 10: System main body 110: Service transceiver module 120: Dispatch module 130: User interface 140: Monitoring module 150: Credential module 160: Storage module 170: Network module 20: Network 30: Robot group 31: Robot 31a: Selected robot 31b: Disinfection robot 311: Mobile device 311a: Housing 311b: Drive circuit 311c: Moving mechanism 312: Communication module 313: Power module 314: Control module 315: Positioning module 316: Sensing device 317: Storage module 318: Disinfection device 318a: UVC lamp tube 318b: Drive circuit 40: Execution management system S110~S180: Steps FIG. 1 is a functional block diagram of a robot service management system according to an embodiment. FIG. 2 is a flowchart of a robot service management method according to an embodiment. FIG. 3 is a schematic diagram of the functional blocks of a robot according to an embodiment. FIG. 4 is a schematic diagram of a robot according to an embodiment. FIG. 5 is a schematic diagram of the functional blocks of a robot according to an embodiment. FIG. 6 is a schematic diagram of a disinfection robot according to an embodiment. 10: System main body 110: Service transceiver module 120: Dispatch module 130: User interface 140: Monitoring module 150: Certificate module 160: Storage module 170: Network module 20: Network 30: Robot group 31: Robot 31a: Selected robot 31b: Disinfection robot 40: Execution management system

Claims

1. A robot service management system, comprising: A service transceiver module is used to receive and send task information; A dispatch module, connected to the service transceiver module, is used to generate dispatch information based on the task information; a robot group, wirelessly connected to the dispatch module, is used to execute the dispatch information; a monitoring module, wirelessly connected to the robot group, is used to receive at least one status signal from the robot group and form monitoring information based on the at least one status signal; a storage module, connected to the dispatch module and the monitoring module, is used to store the dispatch information and the monitoring information; and a credential module, connected to the storage module and wirelessly connected to the robot group, is used to obtain credential information based on the dispatch information and the monitoring information. The robot group includes at least one robot, which includes a communication module, a sensing device, a control module, and a moving device. The control module connects the communication module, the sensing device, and the moving device. The control module, the communication module, and the sensing device are located inside the moving device. The control module receives entry information through the communication module, receives an elevator image captured by the sensing device in response to the entry information, analyzes the elevator image to identify an interior space of the elevator, and drives the moving device according to the interior space.

2. The robot service management system as described in claim 1, wherein the task information includes project information and location information, the dispatch information includes route information, and the dispatch module is further used to generate the route information based on the project information, the location information, and a first map information.

3. The robot service management system as described in claim 2, wherein the robot group includes a plurality of robots, the monitoring information includes current status information of the plurality of robots, the current status information of each robot includes idle data, and the dispatch module is further configured to transmit dispatch information to a selected robot among the at least one robot based on the idle data of each robot.

4. The robot service management system as described in claim 2, wherein the robot group includes a plurality of robots, the monitoring information includes current status information of the plurality of robots, the current status information of each robot includes idle data and battery data, and the dispatch module is further configured to transmit the dispatch information to a selected robot among the at least one robot based on the project data, the location data and the idle data and battery data of each robot.

5. The robot service management system as described in claim 2, wherein the monitoring information includes current status information of the plurality of robots, the current status information of each robot includes idle data, battery data and location data, and the dispatch module is further configured to transmit the dispatch information to a selected robot among the at least one robot based on the project data, the location data and the idle data, battery data and location data of each robot.

6. The robot service management system as described in claim 2, wherein the dispatch information includes: The project data indicates that the robot includes a communication module, a control module, and a mobile device. The control module connects the communication module and the mobile device, and the control module and the communication module are located on the mobile device. Furthermore, the control module is used to generate arrival data after completing the project data, transmit the arrival data to the monitoring module via the communication module, and drive the mobile device to return to a starting point.

7. The robot service management system as described in claim 6, wherein the credential information includes a completion credential and an exception credential, and when the robot arrives at the starting location, the control module further generates return data and transmits the return data to the credential module via the communication module, and the credential module, upon receiving the return data from any robot, confirms whether the robot's dispatch information and arrival data exist, generates the completion credential if the same robot's dispatch information and arrival data exist, and generates the exception credential if the same robot's arrival data does not exist.

8. The robot service management system as described in claim 1, wherein the dispatch information includes a first map information; the robot includes the communication module, the control module, another storage module, and the mobile device, the control module connects the communication module, the other storage module, and the mobile device, the control module, the communication module, and the other storage module are located on the mobile device, the other storage module stores a second map information, and the control module is further used to download the first map information via the communication module and update the second map information with the first map information.

9. The robot service management system as described in claim 8, wherein the second map information includes charging location data; the robot further includes a power supply module connected to the control module and located on the mobile device, the power supply module stores a remaining power and provides the power required for the operation of the robot with the remaining power, and the control module drives the mobile device according to the charging location data when the remaining power is lower than or equal to a threshold.

10. The robot service management system as described in claim 1, wherein the dispatch information includes cleaning data; the robot in the robot group includes a cleaning device, the communication module, the control module, and the mobile device, the control module connects the communication module, the cleaning device, and the mobile device, the control module, the communication module, and the cleaning device are located on the mobile device, and the control module receives the dispatch information via the communication module and controls the cleaning device according to the cleaning data.

11. A robot service management method, comprising: storing at least one monitoring information of at least one robot; obtaining task information; generating dispatch information based on the task information; and transmitting the dispatch information to a selected robot among the at least one robot based on the monitoring information of each robot, the robot service management method comprising: Receive at least one status signal from at least one of the robots, relative to the monitoring information of the robot; Update the monitoring information of the robot relative to the status signal of each robot; obtain credential information relative to the dispatch information and the monitoring information; in response to an entry command, capture an elevator image of an elevator; analyze the elevator image to identify an interior space of the elevator; and drive the selected robot based on the interior space.

12. The robot service management method as described in claim 11, wherein the transmission step includes: Based on idle data from the monitoring information, project data from the dispatch information, and location data from the dispatch information, one of the at least one robots is selected as the selected robot; and the dispatch information is transmitted to the selected robot.

13. The robot service management method as described in claim 11, wherein the transmission step includes: Based on idle data and power data from the monitoring information, and project data and location data from the dispatch information, one of the at least one robots is selected as the selected robot; and the dispatch information is transmitted to the selected robot.

14. The robot service management method as described in claim 11, wherein the transmission step includes: Based on idle data, power data, and location data from the monitoring information, and item data and location data from the dispatch information, one of the at least one robots is selected as the selected robot; and the dispatch information is transmitted to the selected robot.

15. The robot service management method as described in claim 11 further includes: Receive a return data from any of the robots; wherein the obtaining step is performed in response to the return data, and the obtaining step includes: checking the dispatch information and the monitoring information in response to the return data; generating a completion certificate when the dispatch information of the robot that sent the return data exists and the monitoring information contains arrival data of the robot that sent the return data; and generating an exception certificate when the dispatch information of the robot that sent the return data exists and the monitoring information does not contain the arrival data.

16. The robot service management method as described in claim 15 further includes: The selected robot executes the dispatch information, and when the selected robot completes a project of the dispatch information, it sends back the arrival information and returns to a starting point; the selected robot sends back the return information when it arrives at the starting point; and receives and records the arrival information from the selected robot in the credentials information.

Images