Lora-based robot calling system, method, device and storage medium

CN116233318BActive Publication Date: 2024-11-01SHENZHEN PUDU TECH CO LTD

Patent Information

Application Number
CN202211616673.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-12-15
Publication Date
2024-11-01
Estimated Expiration
2042-12-15

AI Technical Summary

Technical Problem

[0003]在目前的餐饮机器人服务系统中,客人通过呼叫终端呼叫餐饮机器人前往客人所在位置来为客人进行服务,而呼叫终端与餐饮机器人之间普遍采用WiFi网络进行通信,所以数据传输对网络的依赖性比较高,一旦网络出现波动或者断网导致数据接收延时或丢失,数据传输的稳定性和准确性差,从而导致呼叫成功率低

Benefits of technology

[0054]上述基于lora的机器人呼叫系统、方法、计算机设备、计算机可读存储介质和计算机程序产品,通过搭建基于lora的机器人呼叫系统,以及基于自定义串行通信协议封装生成机器人呼叫请求,响应于机器人呼叫请求,确定目标机器人并生成控制指令控制目标机器人去往呼叫终端所在位置,提高了数据传输的准确性和稳定性,从而提高了呼叫成功率。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116233318B_ABST
    Figure CN116233318B_ABST
Patent Text Reader

Abstract

The present application relates to a robot calling system, method, device and storage medium based on Lora. The system includes: a Lora gateway, at least one calling terminal that establishes Lora communication with the Lora gateway, and a robot cluster; the calling terminal is used to generate a robot call request based on a custom serial communication protocol encapsulation, and send the robot call request to the Lora gateway; the Lora gateway is used to respond to the robot call request, determine the target robot from the robot cluster and send a control instruction to the target robot; the target robot is used to respond to the control instruction to go to the location of the calling terminal. By building a robot calling system based on Lora, and generating a robot call request based on a custom serial communication protocol encapsulation, responding to the robot call request, determining the target robot and generating a control instruction to control the target robot to the location of the calling terminal, the accuracy and stability of data transmission are improved, thereby improving the call success rate.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of robotics technology, and in particular to a Lora-based robot calling system, method, device and storage medium. Background Art

[0002] With the development of robotics technology, more and more industries are beginning to use robots, especially in the catering industry. In order to reduce labor costs and improve efficiency, robots are gradually being used to replace part of the labor.

[0003] In the current catering robot service system, guests use call terminals to call catering robots to go to their locations to provide services. The call terminals and catering robots generally use WiFi networks for communication, so data transmission is highly dependent on the network. Once the network fluctuates or is disconnected, causing data reception delays or loss, the stability and accuracy of data transmission are poor, resulting in a low call success rate. Summary of the invention

[0004] Based on this, it is necessary to provide a lora-based robot calling system, method, computer device, computer-readable storage medium and computer program product that can improve the call success rate in response to the above technical problems.

[0005] In a first aspect, the present application provides a robot calling system based on Lora, the calling system comprising: a Lora gateway, at least one calling terminal for establishing Lora communication with the Lora gateway, and a robot cluster;

[0006] The calling terminal is used to generate a robot call request based on a custom serial communication protocol encapsulation and send the robot call request to the lora gateway;

[0007] Lora gateway, used to respond to robot call requests, determine the target robot from the robot cluster and send control instructions to the target robot;

[0008] The target robot is used to go to the location of the calling terminal in response to the control instruction.

[0009] In some embodiments, the control instruction includes a unique identifier of the calling terminal, and the target robot is further used to:

[0010] Determining a map location of the calling terminal based on the unique identifier of the calling terminal;

[0011] Go to the location of the calling terminal based on the map location.

[0012] In some embodiments, the control instruction includes a map location of the calling terminal, and the target robot is further used to:

[0013] Go to the location of the calling terminal based on the map location;

[0014] Among them, the map location is determined by the lora gateway through the unique identifier of the calling terminal in the robot call request.

[0015] In some embodiments, the custom serial communication protocol has a custom session mode field; the target robot is also used to generate an arrival message based on the custom serial communication protocol encapsulation after arriving at the location of the calling terminal, and send the arrival message to the lora gateway; the arrival message is encapsulated with a second session mode identifier; the second session mode represented by the second session mode identifier is to send a response message without related data;

[0016] The lora gateway is also used to respond to the arrival message, send an arrival prompt instruction to the calling terminal, and return a response message without relevant data to the target robot based on the second session mode identifier;

[0017] The calling terminal is also used to output arrival prompt information in response to the arrival prompt instruction; the arrival prompt information is used to prompt that the target robot has arrived at the calling terminal.

[0018] In a second aspect, the present application also provides a calling method, which is applied to a lora gateway, and the method includes:

[0019] Obtain the robot call request generated by the calling terminal based on the custom serial communication protocol encapsulation;

[0020] In response to the robot call request, determining a target robot from the robot cluster;

[0021] A control instruction is sent to the target robot, so that the target robot responds to the control instruction and goes to the location of the calling terminal.

[0022] In some embodiments, in response to a robot call request, determining a target robot from a robot cluster includes:

[0023] Get the status information reported by the robot cluster;

[0024] Based on the state information, a robot whose state information is an idle state is determined from the robot cluster as a target robot.

[0025] In some embodiments, in response to a robot call request, determining a target robot from a robot cluster includes:

[0026] Obtain status and location information reported by the robot cluster;

[0027] Get the map location of the calling terminal;

[0028] Determine, based on the state information, a robot whose state information is an idle state from the robot cluster;

[0029] Based on the map position and position information of the calling terminal, a robot closest to the calling terminal is determined as a target robot from robots whose status information is an idle state.

[0030] In some embodiments, the custom serial communication protocol has a custom session mode field; the robot call request includes a first session mode identifier under the session mode field; the custom serial communication protocol also has a custom source address field; the robot call request also includes the address of the calling terminal under the source address field; after sending a control instruction to the target robot so that the target robot responds to the control instruction and goes to the location of the calling terminal, it also includes:

[0031] Based on the address of the calling terminal, call success response information matching the first session mode identifier is returned to the calling terminal.

[0032] In some embodiments, the first session mode represented by the first session mode identifier requires sending a response message carrying relevant data; the method further includes:

[0033] If there is no target robot in an idle state, call failure response information is returned to the calling terminal based on the first session mode identifier.

[0034] In some embodiments, the method further comprises:

[0035] Determine the state information of the target robot while the target robot is moving toward the location of the calling terminal;

[0036] If the status information indicates that the target robot is forcibly occupied, forced occupation response processing is performed.

[0037] In some embodiments, the method further comprises:

[0038] After the target robot arrives at the location of the calling terminal, an arrival message generated and encapsulated based on a custom serial communication protocol is received by the target robot; the arrival message encapsulates a second session mode identifier; the second session mode represented by the second session mode identifier is to send a response message without related data;

[0039] In response to the arrival message, an arrival prompt instruction is generated to control the calling terminal to output arrival prompt information through the arrival prompt instruction, and return a response message without relevant data to the target robot based on the second session mode identifier; the arrival prompt information is used to prompt that the target robot has arrived at the calling terminal.

[0040] In a third aspect, the present application also provides another calling method, which is applied to a calling terminal, and the method includes:

[0041] A robot call request is generated based on the custom serial communication protocol encapsulation, and the robot call request is sent to the Lora gateway, so that the Lora gateway determines the target robot based on the robot call request and sends a control instruction to the target robot, so that the target robot responds to the control instruction and goes to the location of the calling terminal.

[0042] In a fourth aspect, the present application also provides another call control method, which is applied to a robot, and the method comprises:

[0043] Get the control command sent by the Lora gateway; the control command is generated by the Lora gateway based on the robot call request sent by the calling terminal;

[0044] The device moves to the location of the calling terminal in response to the control instruction.

[0045] In some embodiments, the control instruction includes a unique identifier of the calling terminal, and responding to the control instruction to go to the location of the calling terminal includes:

[0046] Determining a map location of the calling terminal based on the unique identifier of the calling terminal;

[0047] Go to the location of the calling terminal based on the map location; or

[0048] The control instruction includes a map location of the calling terminal, and in response to the control instruction, going to the location of the calling terminal includes:

[0049] Go to the location of the calling terminal based on the map location;

[0050] Among them, the map location is determined by the lora gateway through the unique identifier of the calling terminal in the robot call request.

[0051] In a fifth aspect, the present application further provides a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0052] In a sixth aspect, the present application further provides a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0053] In a seventh aspect, the present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0054] The above-mentioned Lora-based robot calling system, method, computer device, computer-readable storage medium and computer program product, by building a Lora-based robot calling system and generating a robot calling request based on a custom serial communication protocol encapsulation, responds to the robot calling request, determines the target robot and generates a control instruction to control the target robot to the location of the calling terminal, thereby improving the accuracy and stability of data transmission, thereby improving the call success rate. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 This is an architectural diagram of a robot calling system based on Lora in one embodiment;

[0056] Figure 2 A flowchart of a calling method in one embodiment;

[0057] Figure 3 A flowchart of a calling method in another embodiment;

[0058] Figure 4 A schematic diagram of a custom SLIP protocol format in one embodiment;

[0059] Figure 5 A flowchart of a calling method in another embodiment;

[0060] Figure 6 A flowchart of a calling method in another embodiment;

[0061] Figure 7 is a structural block diagram of a calling device in one embodiment;

[0062] Figure 8 is a structural block diagram of a calling device in another embodiment;

[0063] Fig. 9 is a structural block diagram of a calling device in another embodiment;

[0064] Fig.10 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0065] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0066] In some embodiments, Figure 1 As shown, a schematic diagram of the architecture of a robot calling system based on lora is provided. Figure 1The system includes a lora gateway 101, at least one calling terminal 102 that establishes lora communication with the lora gateway, and a robot cluster 103. The lora gateway 101 performs lora communication with the robots in the robot cluster 103 and the calling terminal 102 respectively. After receiving the robot call request, the lora gateway 101 determines the target robot 1031 from the robot cluster 103, and controls the target robot 1031 to go to the location of the calling terminal 102. It should be noted that the robot cluster 103 includes at least one robot.

[0067] The target robot 103 is a robot in the robot cluster 103 connected to the Lora gateway 101, and is used to go to the call terminal 102 to provide services. It can be understood that the call terminal 102, the robots in the robot cluster 103 and the Lora gateway 101 form a Lora local area network. Even if the network is disconnected or the network fluctuates, the data transmission between the call terminal 102, the robots in the robot cluster 103 and the Lora gateway 101 will not be disturbed, that is, the robots in the robot cluster 103 can respond to the robot call request in time, so that they can quickly reach the location of the call terminal 102, thereby improving the call success rate.

[0068] Optionally, compared with 4G, WIFI, etc., Lora LAN can achieve a longer transmission distance at the same power consumption, and it will not be affected by the environment such as the surge in mobile phone terminals or WIFI terminals that affects data transmission.

[0069] Exemplarily, the calling terminal 102 generates a robot call request based on a custom serial communication protocol encapsulation, and sends the robot call request to the lora gateway 101. In response to the robot call request, the lora gateway 101 determines a target robot 1031 from the robot cluster 103 and sends a control instruction to the target robot 1031. The target robot 1031 goes to the location of the calling terminal 102 in response to the control instruction.

[0070] Among them, the custom serial communication protocol is a custom serial communication protocol. It can be understood that the custom serial communication protocol can be a new custom serial communication protocol, or it can be obtained by custom modification based on the existing serial communication protocol. The data frames communicated between the robot, lora gateway and the call terminal can all be encapsulated using the custom serial communication protocol.

[0071] The above-mentioned Lora-based robot calling system, by building a Lora-based robot calling system and generating a robot calling request based on a custom serial communication protocol encapsulation, responds to the robot calling request, determines the target robot and generates a control instruction to control the target robot to the location of the calling terminal, thereby improving the accuracy and stability of data transmission, thereby improving the call success rate.

[0072] In some embodiments, the control instruction includes a unique identifier of the calling terminal, and the target robot 1031 is further used to: determine the map location of the calling terminal 102 based on the unique identifier of the calling terminal 102; and go to the location of the calling terminal 102 based on the map location.

[0073] The map location is the location of the calling terminal in the operating environment of the LoRa-based robot calling system. For example, if the operating environment is a restaurant, the location of the calling terminal in the map of the restaurant is the map location.

[0074] Exemplarily, the target robot 1031 determines the map location of the calling terminal 102 based on the correspondence between the unique identifier of the calling terminal 102 and the map location, and goes to the location of the calling terminal 102 based on the map location.

[0075] In an optional embodiment, the target robot 1031 pre-stores a map of the operating environment, which includes the map position of the calling terminal 102 in the operating environment (specifically including X, Y coordinates, and may also include angle information such as θ) and binding information of the unique identifier corresponding to the calling terminal 102.

[0076] When the target robot 1031 receives the unique identifier of the calling terminal 102 , it can determine the map location of the corresponding calling terminal 102 based on the unique identifier.

[0077] In the above embodiment, the location of the calling terminal is accurately located according to the correspondence between the unique identifier of the calling terminal and the map location.

[0078] In some embodiments, the control instruction includes the map location of the calling terminal 102, and the target robot 1031 is also used to: go to the location of the calling terminal 102 based on the map location; wherein the map location is determined by the lora gateway 101 through the unique identifier of the calling terminal 102 in the robot call request.

[0079] Exemplarily, after the lora gateway 101 receives the robot call request sent by the calling terminal 102, the map location of the calling terminal 102 is determined according to the correspondence between the unique identifier of the calling terminal 102 in the robot call request and the map location, and a control instruction including the map location is generated. After receiving the control instruction including the map location, the target robot 1031 goes to the location of the calling terminal 102 based on the map location.

[0080] In an optional embodiment, the lora gateway 101 may only include a gateway end, which is used to implement communication between the call terminal 102 and the robot cluster 103.

[0081] In an optional embodiment, the lora gateway 101 includes a gateway end and a cloud platform end.

[0082] In an optional embodiment, the gateway end and the cloud platform end can communicate with each other, wherein the gateway end is responsible for communicating with the calling terminal 102 , and the cloud platform end is responsible for communicating with the robot cluster 103 .

[0083] Optionally, the communication method between the gateway and the cloud platform is not limited.

[0084] In another optional embodiment, the gateway side may be used to implement communication between the call terminal 102 and the robot cluster 103, and the cloud platform side may be used to assist the gateway side in calculating relevant data.

[0085] For example, in an optional embodiment, the lora gateway 101 pre-stores a map of the corresponding operating environment, which includes the map position of the call terminal 102 in the operating environment (specifically including X, Y coordinates, and may also include angle information such as θ) and binding information of the unique identifier of the corresponding call terminal 102. When the lora gateway 101 receives the robot call request sent by the call terminal 102, the map position of the call terminal 102 is determined according to the correspondence between the unique identifier of the call terminal 102 in the robot call request and the map position, and the map position is sent to the target robot 1031 as part of the control instruction, so that after the target robot 1031 receives the control instruction including the map position, it goes to the location of the call terminal 102 based on the map position.

[0086] In an optional embodiment, the gateway may pre-store a map of the corresponding operating environment and perform calculations.

[0087] In other embodiments, the cloud platform may pre-store a map of the corresponding operating environment, and after obtaining the unique identifier of the calling terminal 102 from the gateway, calculate the map position of the calling terminal 102 corresponding to the unique identifier and send it to the gateway. The gateway then sends the map position as part of the control instruction to the target robot 1031, so that after the target robot 1031 receives the control instruction including the map position, it goes to the location of the calling terminal 102 based on the map position.

[0088] In some embodiments, the custom serial communication protocol has a custom session mode field; the target robot 1031 is also used to generate an arrival message based on the custom serial communication protocol encapsulation after arriving at the location of the calling terminal 102, and send the arrival message to the lora gateway 101; the arrival message is encapsulated with a second session mode identifier; the second session mode represented by the second session mode identifier is to send a response message without related data.

[0089] The lora gateway 102 is also used to respond to the arrival message, send an arrival prompt instruction to the calling terminal 102, and return a response message without relevant data to the target robot 1031 based on the second session mode identifier.

[0090] The calling terminal 102 is also used to output arrival prompt information in response to the arrival prompt instruction; the arrival prompt information indicates that the target robot 1031 has arrived at the calling terminal.

[0091] The session mode refers to the communication mode between the initiator and the requested party. The session mode can be set according to the application scenario and can be one or more.

[0092] It can be understood that a session mode field is defined in the custom serial communication protocol, and the data frame encapsulated by the custom serial communication protocol carries the session mode field. The data frame sent by the initiator of the session carries the session mode field, and the requested session party determines the session mode of the current session by identifying the session mode field in the data frame, so as to return the corresponding data frame. The session mode field is used to write information representing the session mode, that is, the session mode identifier. It can be understood that the session mode fields of different session modes are different, and based on different session mode fields, there can be a first session mode, a second session mode, a third session mode, a fourth session mode, and so on. The first session mode identifier refers to the session mode field used to write information representing the first session mode, and the second session mode identifier refers to the session mode field used to write information representing the second session mode.

[0093] It can be understood that the requested conversation party can determine that a data frame without relevant data needs to be returned to the conversation initiator by identifying the field corresponding to the second conversation mode in the received data frame. For example, the custom second conversation mode field in the custom serial communication protocol is 0x02. After the target robot arrives at the location of the calling terminal, the target robot sends an arrival prompt message to the Lora gateway. The conversation mode field of the data frame received by the Lora gateway is 0x02, which means that the Lora gateway needs to return a data frame without data to the target robot, indicating that the Lora gateway has learned that the target robot has arrived at the location of the calling terminal.

[0094] The arrival message refers to the message sent to the LoRa gateway when the target robot arrives at the calling terminal, which is used to indicate that the target robot has arrived at the calling terminal. The arrival message includes at least one of the calling terminal address, the arrival instruction and the current location information.

[0095] The arrival prompt command is a command sent by the lora gateway to prompt the calling terminal that the target robot has arrived at the calling terminal.

[0096] The arrival prompt information is a prompt information generated by the calling terminal when the target robot arrives at the location of the calling terminal, which is used to prompt that the target robot has arrived. The arrival prompt information includes at least one of a sound prompt and a light prompt. For example, the arrival prompt information can be a voice broadcast that the robot has arrived, or a light can be turned on to prompt that the robot has arrived, which is not limited in this embodiment.

[0097] In some embodiments, Figure 2 As shown, a flowchart of a calling method is provided, in which the method is applied to Figure 1 Taking the lora gateway 101 in the example as an example, the following steps are included:

[0098] Step 201: Obtain a robot call request generated by a calling terminal based on a custom serial communication protocol encapsulation.

[0099] For example, when a user needs to call a robot, he can use a calling terminal to perform a robot calling operation. The calling terminal can generate a robot calling request based on a custom serial communication protocol encapsulation in response to the robot calling operation, and send the robot calling request to the lora gateway.

[0100] In some embodiments, when the calling terminal generates a robot call request based on the custom serial communication protocol encapsulation, the first session mode identifier can be written into the session mode field of the custom serial communication protocol. Therefore, the robot call request will carry the first session mode identifier, that is, it is used to specify the use of the first session mode for communication. The lora gateway can extract the first session mode identifier from the obtained robot call request.

[0101] Step 202: In response to the robot call request, determine a target robot from the robot cluster.

[0102] Exemplarily, the lora gateway responds to the robot call request and determines a target robot from a robot cluster based on at least one of location information and status information.

[0103] The position information is the real-time position information of the robot. The status information is used to indicate whether the target robot is in an idle state. If optional, its status information specifically includes an idle state and an occupied state. Its occupied state can be an overall state, and can also include sub-states such as delivering food, returning dishes, and summoning, which are not limited here.

[0104] In an optional embodiment, the robot may report its own position information and status information at a preset frequency.

[0105] In an optional embodiment, the Lora gateway can send inquiries to at least one robot at a preset frequency and obtain the location information and status information reported by the robot. Or when the Lora gateway needs to determine the location information and status information of the robot, it sends a temporary inquiry to at least one robot and obtains the location information and status information reported by the robot.

[0106] In an optional embodiment, the lora gateway may only include a gateway end, which is used to implement communication between the call terminal and the robot cluster.

[0107] In an optional embodiment, the lora gateway includes a gateway end and a cloud platform end.

[0108] In an optional embodiment, the gateway end and the cloud platform end can communicate with each other, wherein the gateway end is responsible for communicating with the calling terminal 102, and the cloud platform end is responsible for communicating with the robot cluster.

[0109] Optionally, the communication method between the gateway and the cloud platform is not limited.

[0110] In another optional embodiment, the gateway side may be used to implement communication between the calling terminal and the robot cluster 103, and the cloud platform side may be used to assist the gateway side in calculating relevant data.

[0111] In an optional embodiment, the lora gateway responds to the robot call request and determines the target robot from the robot cluster based on at least one of the location information and the state information. Specifically, the gateway side determines the target robot from the robot cluster based on at least one of the location information and the state information. Alternatively, the cloud platform side determines the target robot from the robot cluster based on at least one of the location information and the state information, which is not limited here.

[0112] Step 203: Send a control instruction to the target robot, so that the target robot responds to the control instruction and goes to the location of the calling terminal.

[0113] Exemplarily, when the lora gateway finds the target robot, it sends a control instruction to the target robot. The target robot responds to the control instruction to switch the state information to the occupied state, and goes to the location of the calling terminal according to the control instruction.

[0114] In some embodiments, after sending a control instruction to the target robot so that the target robot responds to the control instruction and goes to the location of the calling terminal, the lora gateway determines that the current session mode is the first session mode based on the session mode field in the received robot call request, and returns a data frame matching the first session mode to the calling terminal, and the data frame carries call success response information.

[0115] Among them, the call success response information is the response information used to characterize the success of the call. It can be understood that after the robot call is successful, the lora gateway can return a corresponding data frame to the calling terminal, and the data frame carries the call success response information, so that the calling terminal knows that the robot call is successful.

[0116] It should be noted that the content of the returned call success response information will be different for different session modes. In this embodiment, the robot call request carries the first session mode identifier, which specifies that the session mode for responding to the robot call request is the first session mode. After the lora gateway successfully calls the robot, it can generate matching call success response information according to the first session mode.

[0117] In the above calling method, by building a robot calling system based on Lora and generating a robot calling request based on a custom serial communication protocol encapsulation, in response to the robot calling request, the target robot is determined and a control instruction is generated to control the target robot to the location of the calling terminal, thereby improving the accuracy and stability of data transmission and thus improving the call success rate.

[0118] In some embodiments, the first session mode represented by the first session mode identifier requires sending a response message carrying relevant data; the method also includes: if there is no target robot in an idle state, then based on the first session mode identifier, returning a call failure response message to the calling terminal.

[0119] It can be understood that the requested conversation party can determine that the data frame carrying relevant data needs to be returned to the conversation initiator by identifying the field corresponding to the first conversation mode in the received data frame. For example, the custom first conversation mode field in the custom serial communication protocol is 0x01. In a conversation in which the robot inquires about the connection status from the Lora gateway (there are four modes of connection status, namely 0x00 unregistered, 0x01 registered, 0x02 logged in, and 0x03 disconnected), the conversation mode field in the data frame received by the Lora gateway is 0x01. Then the data frame carrying relevant data returned by the Lora gateway to the robot refers to the data frame carrying the connection status information.

[0120] Among them, the call failure response information is the response information used to characterize the call failure. It can be understood that after the robot call fails, that is, when there is no target robot, the lora gateway can return the corresponding data frame to the calling terminal, which carries the call success or failure response information, so that the calling terminal knows that the robot call has failed.

[0121] For example, when the LoRa gateway receives a robot call request, it finds that all robots connected to the LoRa gateway are occupied, that is, there is no idle robot. At this time, based on the first session mode identifier, it determines that the current session mode is the first session mode, and returns a corresponding data frame to the calling terminal, which carries call failure response information.

[0122] In this embodiment, call failure response information is returned to the calling terminal through the first session mode identifier, and the calling terminal is notified of the call status in time to avoid the calling terminal from making a long call and causing a waste of resources.

[0123] In some embodiments, the custom serial communication protocol has a custom session mode field; the robot call request includes a first session mode identifier under the session mode field; the custom serial communication protocol also has a custom source address field; the robot call request also includes the address of the calling terminal under the source address field; after sending a control instruction to the target robot so that the target robot responds to the control instruction and goes to the location of the calling terminal, it also includes: based on the address of the calling terminal, returning a call success response information matching the first session mode identifier to the calling terminal.

[0124] Among them, the source address field refers to the source address field in the data frame encapsulated in the custom serial communication protocol, that is, the address field of the initiator of the conversation. In order to distinguish whether the initiator of the conversation is the lora gateway, the robot or the calling terminal, the addresses of the three should be different. It can be understood that the requested conversation party can know the address of the initiator of the conversation by identifying the source address field in the data frame, so as to accurately return the corresponding data frame. For example, the lora gateway address field is 0x00, the calling terminal address field is 0x01, and the robot address field is 0x02. In a conversation, the source address field in the data frame received by the lora gateway is 0x02, which means that the initiator of the conversation is a robot. Based on the source address field, the lora gateway returns the corresponding data frame to the robot.

[0125] In this embodiment, by determining the source address field, accurate data transmission can be achieved and the call success rate can be improved.

[0126] In some embodiments, in response to a robot call request, determining a target robot from a robot cluster includes: obtaining status information reported by the robot cluster; and determining, based on the status information, a robot from the robot cluster whose status information is an idle state as the target robot.

[0127] The state information includes but is not limited to any one of an idle state, an occupied state and a forced occupied state.

[0128] It can be understood that the idle state indicates that the robot is not occupied, the occupied state indicates that the robot is occupied, and the forced occupied state indicates that the robot encounters an emergency situation while heading to the location of the calling terminal, such as the robot suddenly shutting down, encountering an obstacle and being unable to move, etc.

[0129] Exemplarily, when the lora gateway receives a robot call request, it obtains status information reported by the connected robot cluster, where the status information includes any one of an idle state, an occupied state, and a forced occupied state. Based on the status information, the robot with an idle state is determined from the robot cluster as the target robot.

[0130] In some embodiments, determining a robot in an idle state from the robot cluster as a target robot based on the state information includes: if there is only one robot in an idle state, then the robot is the target robot. If multiple robots in an idle state are found, then the target robot is determined according to the position information.

[0131] In the above embodiment, the target robot in an idle state is determined through state information, so that the target robot can go to the location of the calling terminal in time, thereby improving the call success rate.

[0132] In some embodiments, in response to a robot call request, a target robot is determined from a robot cluster, including: obtaining status information and location information reported by the robot cluster; obtaining a map location of a calling terminal; determining a robot whose status information is an idle state from the robot cluster based on the status information; and determining, from the robots whose status information is an idle state, a robot closest to the calling terminal as a target robot based on the map location and location information of the calling terminal.

[0133] Exemplarily, the lora gateway obtains the status information and location information reported by the robot cluster, as well as the map location of the calling terminal. When the number of robots whose status information is idle is determined to be at least two from the robot cluster based on the status information, the robot closest to the calling terminal is determined as the target robot from the robots whose status information is idle based on the map location and location information of the calling terminal.

[0134] It should be noted that being closest to the calling terminal may mean that the straight-line distance between the robot and the calling terminal is the shortest, or that the actual path between the robot and the calling terminal is the shortest, or that the map-planned path between the robot and the calling terminal is the shortest, which is not limited in this embodiment.

[0135] In the above embodiment, when there are at least two robots in an idle state, by determining the robot closest to the calling terminal as the target robot, it can be ensured that the target robot quickly reaches the calling terminal and the calling time is shortened.

[0136] In some embodiments, after the target robot arrives at the location of the calling terminal, an arrival message encapsulated based on a custom serial communication protocol is received from the target robot; the arrival message encapsulates a second session mode identifier; the second session mode represented by the second session mode identifier is to send a response message without relevant data; in response to the arrival message, the calling terminal is controlled to output an arrival prompt message, and based on the second session mode identifier, a response message without relevant data is returned to the target robot; the arrival prompt message indicates that the robot has arrived at the calling terminal.

[0137] Exemplarily, after the target robot arrives at the calling terminal, an arrival message is generated based on the custom serial communication protocol encapsulation and sent to the Lora gateway. After receiving the arrival message, the Lora gateway sends an arrival prompt instruction to the calling terminal to prompt the robot that it has arrived. The calling terminal outputs the arrival prompt information in response to the arrival prompt instruction.

[0138] In this embodiment, the second session identifier is used to determine that the session mode between the robot call request recipient and the robot is the second session mode, and data is accurately transmitted, thereby ensuring the reliability of data transmission. At the same time, when the target robot arrives at the location of the calling terminal, the calling terminal outputs arrival prompt information to prompt that the target robot has arrived, so as to prompt the user that the target robot has arrived.

[0139] In some embodiments, when a one-way message encapsulated based on a custom serial communication protocol and carrying a third session mode identifier is received, no response processing is performed on the received one-way message; wherein the third session mode represented by the third session mode identifier does not require a response.

[0140] Among them, a one-way message refers to a message sent in one direction, that is, the sender is only responsible for sending the message and does not wait for a response.

[0141] It can be understood that one-way messages are determined according to the conversation scenario. For example, in the conversation scenario, the robot sends heartbeat data to the Lora gateway, the robot reports location information and status information to the Lora gateway, etc. The message sent by the robot is a one-way message, and the recipient does not need to respond.

[0142] The third session mode identifier refers to the information representing the third session mode written in the session mode field.

[0143] It can be understood that the requested conversation party can determine that a data frame without relevant data needs to be returned to the conversation initiator by identifying the field corresponding to the third conversation mode in the received data frame. For example, the custom third conversation mode field in the custom serial communication protocol is 0x03. During a conversation, when the robot sends heartbeat data to the Lora gateway at regular intervals, the heartbeat data is used to indicate that the robot is online. If the conversation mode field of the data frame received by the Lora gateway is 0x03, it means that the Lora gateway does not need to respond to the received data frame.

[0144] In this embodiment, the conversation mode between the lora gateway and the robot is determined to be the third conversation mode through the third conversation identifier, and data is accurately transmitted, thereby ensuring the reliability of data transmission.

[0145] In some embodiments, while the target robot is heading toward the location of the calling terminal, the state information of the target robot is determined; if the state information indicates that the target robot is forcibly occupied, forced occupation response processing is performed.

[0146] Among them, the forced occupation response processing refers to the processing performed when the state information of the target robot is in the forced occupation state.

[0147] Exemplarily, the target robot runs out of power and shuts down while heading to the location of the calling terminal. At this time, the target robot will switch its status information to the forced occupation state before shutting down. After the Lora gateway determines that the status information of the target robot is in the forced occupation state, it will perform forced occupation response processing. For example, the Lora gateway may send a call failure message to the calling terminal, and the calling terminal may display the call failure. Alternatively, the Lora gateway may reacquire the status information of all connected robots, find the robot that is closest to the calling terminal and is in an idle state as the target robot, and control the target robot to go to the location of the calling terminal.

[0148] In this embodiment, by determining the status information of the target robot in the process of going to the calling terminal, when the status information of the target robot is a forced occupation state, the calling terminal can be promptly notified of the call failure or a new robot can be rearranged to go to the calling terminal, thereby improving the call success rate.

[0149] In another embodiment, Figure 3 As shown, another calling method is provided, which specifically includes the following steps:

[0150] S301. The calling terminal generates a robot call request by encapsulating based on a custom serial communication protocol; the custom serial communication protocol has a custom session mode field; the robot call request includes a first session mode identifier under the session mode field.

[0151] S302. The lora gateway responds to the robot call request and determines from the robot cluster a robot whose status information is idle and closest to the calling terminal as a target robot.

[0152] S303, lora gateway sends control instructions to the target robot.

[0153] S304. The lora gateway returns call success response information matching the first session mode identifier to the calling terminal.

[0154] In some embodiments, if there is no target robot in an idle state, call failure response information is returned to the calling terminal based on the first session mode identifier.

[0155] S305. The control instruction includes a unique identifier of the calling terminal; the target robot determines the map location of the calling terminal based on the unique identifier of the calling terminal; and moves to the location of the calling terminal based on the map location.

[0156] Furthermore, when the target robot is heading to the location of the calling terminal, the Lora gateway determines the status information of the target robot; if the status information indicates that the target robot is forcibly occupied, a call failure message can be sent to the calling terminal. Alternatively, the Lora gateway can re-acquire the status information of all connected robots, find the robot that is closest to the calling terminal and is in an idle state as the target robot, and control the target robot to go to the location of the calling terminal.

[0157] In some embodiments, the control instruction includes a map location of the calling terminal; the target robot goes to the location of the calling terminal based on the map location, wherein the map location is determined by the lora gateway through the unique identifier of the calling terminal in the robot call request.

[0158] S306. The target robot goes to the location of the calling terminal, switches the status information to the occupied state, and after arriving at the location of the calling terminal, generates an arrival message based on the custom serial communication protocol encapsulation, and sends the arrival message to the lora gateway.

[0159] S307. The lora gateway sends an arrival prompt instruction to the calling terminal in response to the arrival message; the arrival message is encapsulated with a second session mode identifier; the second session mode represented by the second session mode identifier is to send a response message without related data.

[0160] S308. The lora gateway returns a response message without relevant data to the target robot based on the second session mode identifier.

[0161] S309. The calling terminal outputs arrival prompt information in response to the arrival prompt instruction; the arrival prompt information is used to prompt that the target robot has arrived at the calling terminal.

[0162] In this embodiment, the session mode field in the robot call request is encapsulated through a custom serial communication protocol, and call success response information matching the first session mode identifier is returned to the caller based on the first session mode field, thereby improving the accuracy and stability of data transmission; in the process of the robot going to the location of the calling terminal, when the status information of the target robot is a forced occupied state, timely response and processing are performed, thereby improving the call success rate.

[0163] In some embodiments, the custom serial communication protocol may be a custom protocol based on SLIP (Serial Line Internet Protocol), that is, the custom serial communication protocol of the present application is obtained by custom modification on the SLIP protocol, which may also be called a custom SLIP protocol format.

[0164] In some embodiments, reference Figure 4, provides a custom SLIP protocol format. The specific description and instructions for the SLIP protocol format are as follows:

[0165] Two END characters. Each data frame starts and stops with an END character.

[0166] Frame Number: When two parties are talking, the frame number will automatically increase by 1 after each successful frame transmission. If the transmission fails after 3 attempts, the frame number will automatically increase by 1 when a new frame is transmitted next time. When the frame number value accumulates to 255, it will start to accumulate from 0 again, and the cycle will repeat. If the data frame is a response frame, the frame number is the number of the last received non-response frame, that is, only the last non-response frame will be responded to.

[0167] SRC (address of the initiator, i.e. source address field) and DEST (address of the requested party), that is, in each session, the data frame carries the addresses of the initiator and the requested party. For example, the address of the lora gateway is defined as 0x00, the address of the calling terminal is 0x01, and the address of the robot is 0x10. When the SRC in a data frame is 0x00 and the DEST is 0x10, it can be determined that the data frame is a data frame sent by the lora gateway to the robot.

[0168] Type (session mode field), that is, the conversation mode between the initiator and the requested party is determined by confirming the Type field. For example, it can be agreed that the initiator is Party A and the requested party is Party B. There is no master-slave distinction between the two parties. The master and the slave are distinguished only in a single conversation. The initiator of the conversation is the master (Party A) and the requested party is the slave (Party B).

[0169] In some embodiments, there may be three types of conversation modes between Party A and Party B. The first conversation mode: Party A initiates a conversation, and Party B responds with relevant data; the second conversation mode: Party A initiates a conversation, and Party B responds without relevant data; the third conversation mode: Party A initiates a conversation, and Party B does not need to respond. In this embodiment, the conversation modes may include, but are not limited to, the first conversation mode, the second conversation mode, and the third conversation mode. Exemplarily, the sender's Type field can be set to 0x01, which is used by the sender to read and query relevant information of the receiver, and the receiver must respond with relevant data; 0x02, which is used by the sender to set, modify, and notify the receiver, and the receiver must respond with relevant data; 0x03, which is used by the sender to set, modify, and notify the receiver, and the receiver does not need to respond with relevant data; the receiver's Type field can be set to 0x10, which is used to indicate that the receiver carries relevant data in the response frame to the received data frame with the Type field of 0x01 or 0x02; 0x20, the receiver only responds to the received data frame with the Type field of 0x03 without relevant data; 0x05, the receiver does not respond to the received data frame with the Type field of 0x05, which is mainly used for real-time data transmission, transparent transmission, broadcast communication, etc.

[0170] ID (business scenario), that is, the ID field is used to determine the session scenario in which the initiating party and the requested party are in; illustratively, the ID field can be set according to the application scenario. For example, when the ID is 0x02, it indicates that the initiating party and the requested party are querying the connection status; when the ID is 0x20, it indicates that the initiating party and the requested party are transparently transmitting data; when the ID is 0x03, it indicates that the initiating party and the requested party are sending heartbeat data.

[0171] PayloadLength (data payload area size) is used to characterize the size of user data transmitted in a data frame; illustratively, it is used to characterize the size of Data0....DataN actually transmitted.

[0172] Data0....DataN (0 to N data) represents the data actually transmitted.

[0173] Checksum is used to check whether data is transmitted incorrectly. The verification principle is: (FrameNumber+SRC+DEST+Type+ID+PayloadLength+DATA0+…DATAn)^0xFF. When replacement characters appear in the frame content, the checksum must be calculated using the original data.

[0174] In this embodiment, the data frames in the session are encapsulated by customizing the SLIP protocol format, thereby ensuring the accuracy and stability of data transmission.

[0175] In some embodiments, Figure 5 As shown, another calling method is provided, which is described by taking the method applied to the calling terminal 102 as an example, and includes the following steps:

[0176] Step 501: Generate a robot call request based on a custom serial communication protocol encapsulation.

[0177] Step 502: Send a robot call request to the Lora gateway, so that the Lora gateway determines the target robot based on the robot call request, and sends a control instruction to the target robot, so that the target robot responds to the control instruction and goes to the location of the calling terminal.

[0178] In some embodiments, the method further comprises: outputting arrival prompt information in response to an arrival prompt instruction. The arrival prompt instruction is generated by the lora gateway in response to an arrival message generated based on a custom serial communication protocol encapsulation and sent by the target robot after the target robot arrives at the location of the calling terminal.

[0179] In some embodiments, Figure 6 As shown, another calling method is provided, which is described by taking the method applied to the target robot 1031 as an example, and includes the following steps:

[0180] Step 601, obtain the control instruction sent by the Lora gateway; the control instruction is generated by the Lora gateway based on the robot call request sent by the calling terminal.

[0181] Step 602: Go to the location of the calling terminal in response to the control instruction.

[0182] In some embodiments, the control instruction includes a unique identifier of the calling terminal; the method further includes: determining a map location of the calling terminal based on the unique identifier of the calling terminal; and traveling to a location of the calling terminal based on the map location.

[0183] In some embodiments, the control instruction includes a map location of the calling terminal; the method also includes: going to the location of the calling terminal based on the map location; wherein the map location is determined by the lora gateway through the unique identifier of the calling terminal in the robot call request.

[0184] In some embodiments, the method also includes: after arriving at the location of the calling terminal, generating an arrival message based on a custom serial communication protocol encapsulation, and sending the arrival message to the lora gateway; the arrival message is encapsulated with a second session mode identifier; the second session mode represented by the second session mode identifier is to send a response message without related data.

[0185] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least one partial step in the flowcharts involved in the above embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least one part of the steps or stages in other steps.

[0186] Based on the same inventive concept, the embodiment of the present application also provides a calling device for implementing the calling method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more calling device embodiments provided below can refer to the limitations on the calling method above, and will not be repeated here.

[0187] In some embodiments, Figure 7 As shown, a calling device is provided, including: a first acquisition module 701, a determination module 702 and a control module 703, wherein:

[0188] The first acquisition module 701 is used to acquire a robot call request generated by a calling terminal based on a custom serial communication protocol encapsulation.

[0189] The determination module 702 is used to determine a target robot from a robot cluster in response to a robot call request.

[0190] The control module 703 is used to send a control instruction to the target robot, so that the target robot responds to the control instruction and goes to the location of the calling terminal.

[0191] In some embodiments, the determination module 702 is specifically used to obtain status information reported by the robot cluster; based on the status information, determine from the robot cluster a robot with idle status information as the target robot.

[0192] In some embodiments, the determination module 702 is specifically used to obtain status information and location information reported by the robot cluster; obtain the map location of the calling terminal; determine the robot whose status information is an idle state from the robot cluster based on the status information; based on the map location and location information of the calling terminal, determine the robot closest to the calling terminal from the robots whose status information is an idle state as the target robot.

[0193] In some embodiments, the custom serial communication protocol has a custom session mode field; the robot call request includes a first session mode identifier under the session mode field; the custom serial communication protocol also has a custom source address field; the robot call request also includes the address of the calling terminal under the source address field; after sending a control instruction to the target robot so that the target robot responds to the control instruction and goes to the location of the calling terminal, the control module 703 is specifically used to return a call success response information matching the first session mode identifier to the calling terminal based on the address of the calling terminal.

[0194] In some embodiments, the first session mode represented by the first session mode identifier requires sending a response message carrying relevant data; the control module 703 is also used to return a call failure response message to the calling terminal based on the first session mode identifier if there is no target robot in an idle state.

[0195] In some embodiments, the determination module 702 is further used to determine the state information of the target robot while the target robot is heading toward the location of the calling terminal; if the state information indicates that the target robot is forcibly occupied, forced occupation response processing is performed.

[0196] In some embodiments, the determination module 702 is also used to receive an arrival message generated based on a custom serial communication protocol encapsulation and sent by the target robot after the target robot arrives at the location of the calling terminal; the arrival message is encapsulated with a second session mode identifier; the second session mode represented by the second session mode identifier is to send a response message without relevant data; in response to the arrival message, an arrival prompt instruction is generated to control the calling terminal to output the arrival prompt information through the arrival prompt instruction, and return the response information without relevant data to the target robot based on the second session mode identifier; the arrival prompt information is used to prompt that the target robot has arrived at the calling terminal.

[0197] In some embodiments, Figure 8 As shown, another calling device is provided, including: a first generating module 801 and a sending module 802, wherein:

[0198] The first generating module 801 is used to generate a robot call request based on a custom serial communication protocol encapsulation.

[0199] The sending module 802 is used to send a robot call request to the Lora gateway, so that the Lora gateway determines the target robot based on the robot call request and sends a control instruction to the target robot so that the target robot responds to the control instruction and goes to the location of the calling terminal.

[0200] In some embodiments, the device further comprises a prompt module for outputting arrival prompt information in response to an arrival prompt instruction. The arrival prompt instruction is generated by the lora gateway in response to an arrival message generated based on a custom serial communication protocol encapsulation and sent by the target robot after the target robot arrives at the location of the call terminal.

[0201] In some embodiments, Fig. 9 As shown, another calling device is provided, including: a second acquisition module 901 and a response module 902, wherein:

[0202] The second acquisition module 901 is used to obtain the control instruction sent by the Lora gateway; the control instruction is generated by the Lora gateway based on the robot call request sent by the calling terminal.

[0203] The response module 902 is used to respond to the control instruction and go to the location of the calling terminal.

[0204] In some embodiments, the control instruction includes a map location of the calling terminal; the response module 902 is specifically used to go to the location of the calling terminal based on the map location; wherein the map location is determined by the lora gateway through the unique identifier of the calling terminal in the robot call request.

[0205] In some embodiments, the control instruction includes a unique identifier of the calling terminal; the response module 902 is specifically used to determine the map location of the calling terminal based on the unique identifier of the calling terminal; and go to the location of the calling terminal based on the map location.

[0206] In some embodiments, the device also includes a second generation module, which is used to generate an arrival message based on a custom serial communication protocol encapsulation after arriving at the location of the calling terminal, and send the arrival message to the lora gateway; the arrival message is encapsulated with a second session mode identifier; the second session mode represented by the second session mode identifier is to send a response message without related data.

[0207] Each module in the above-mentioned calling device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0208] In some embodiments, a computer device is provided, which may be a gateway, a robot or a call terminal, and its internal structure diagram may be as follows: Fig.10As shown. The computer device includes a processor, a memory and a communication interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a calling method is implemented.

[0209] Those skilled in the art will understand that Fig.10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0210] In some embodiments, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0211] In some embodiments, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0212] In some embodiments, a computer program product is provided, including a computer program, which implements the steps in the above-mentioned method embodiments when executed by a processor.

[0213] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0214] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0215] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A robot calling system based on lora, characterized in that: The calling system includes: a lora gateway, at least one calling terminal establishing lora communication with the lora gateway, and a robot cluster; The calling terminal is used to generate a robot call request based on a custom serial communication protocol encapsulation and send the robot call request to the lora gateway; the custom serial communication protocol has a custom session mode field; The lora gateway is used to respond to the robot call request, determine the target robot from the robot cluster and send a control instruction to the target robot; The target robot is used to respond to the control instruction and go to the location of the calling terminal; The target robot is also used to, after arriving at the location of the calling terminal, generate an arrival message based on the custom serial communication protocol encapsulation, and send the arrival message to the lora gateway; the arrival message is encapsulated with a second session mode identifier under the session mode field; the second session mode represented by the second session mode identifier is to send a response message without related data; The lora gateway is also used to respond to the arrival message, send an arrival prompt instruction to the calling terminal, and return a response message without relevant data to the target robot based on the second session mode identifier; The calling terminal is further used to output arrival prompt information in response to the arrival prompt instruction; the arrival prompt information is used to prompt that the target robot has arrived at the calling terminal; The lora gateway is also used to determine the status information of the target robot during the process of the target robot going to the location of the calling terminal; If the state information indicates that the target robot is forcibly occupied, a forced occupation response process is performed; wherein the forced occupation response process refers to the process performed when the state information of the target robot is in a forced occupation state.

2. The lora-based robot calling system according to claim 1 is characterized in that: The control instruction includes the unique identifier of the calling terminal, and the target robot is further used for: Determining a map location of the calling terminal based on the unique identifier of the calling terminal; Go to the location of the calling terminal based on the map location.

3. The lora-based robot calling system according to claim 1, characterized in that: The control instruction includes the map location of the calling terminal, and the target robot is further used for: Go to the location of the calling terminal based on the map location; Among them, the map location is determined by the lora gateway through the unique identifier of the calling terminal in the robot call request.

4. A calling method, characterized in that: Applied to lora gateway, the method includes: Obtaining a robot call request generated by a calling terminal based on a custom serial communication protocol encapsulation; the custom serial communication protocol has a custom session mode field; In response to the robot call request, determining a target robot from a robot cluster; Sending a control instruction to the target robot so that the target robot responds to the control instruction and goes to the location of the calling terminal; After the target robot arrives at the location of the calling terminal, an arrival message generated and encapsulated based on a custom serial communication protocol is received from the target robot; the arrival message encapsulates a second session mode identifier under the session mode field; the second session mode represented by the second session mode identifier is to send a response message without related data; In response to the arrival message, an arrival prompt instruction is generated, so as to control the calling terminal to output arrival prompt information through the arrival prompt instruction, and return a response message without relevant data to the target robot based on the second session mode identifier; the arrival prompt information is used to prompt that the target robot has arrived at the calling terminal; Determining the state information of the target robot during the process of the target robot moving toward the location of the calling terminal; If the state information indicates that the target robot is forcibly occupied, a forced occupation response process is performed; wherein the forced occupation response process refers to the process performed when the state information of the target robot is in a forced occupation state.

5. The calling method according to claim 4, characterized in that: The step of determining a target robot from a robot cluster in response to the robot call request comprises: Get the status information reported by the robot cluster; Based on the state information, a robot whose state information is an idle state is determined from the robot cluster as a target robot.

6. The calling method according to claim 4, characterized in that: The step of determining a target robot from a robot cluster in response to the robot call request comprises: Obtain status and location information reported by the robot cluster; Obtaining a map location of the calling terminal; Determine, from the robot cluster, a robot whose status information is an idle state based on the status information; Based on the map position of the calling terminal and the position information, a robot closest to the calling terminal is determined as a target robot from the robots whose status information is an idle state.

7. The method according to claim 4, characterized in that The custom serial communication protocol has a custom session mode field; the robot call request includes a first session mode identifier under the session mode field; the custom serial communication protocol also has a custom source address field; the robot call request also includes the address of the calling terminal under the source address field; After sending a control instruction to the target robot so that the target robot responds to the control instruction and goes to the location of the calling terminal, the method further includes: Based on the address of the calling terminal, call success response information matching the first session mode identifier is returned to the calling terminal.

8. The method according to claim 7, characterized in that The first session mode represented by the first session mode identifier is that a response message carrying relevant data needs to be sent; the method further includes: If there is no target robot in an idle state, call failure response information is returned to the calling terminal based on the first session mode identifier.

9. A calling method, characterized in that: Applied to a calling terminal, the method comprises: A robot call request is generated based on a custom serial communication protocol encapsulation, and the robot call request is sent to a lora gateway, so that the lora gateway determines a target robot based on the robot call request, and sends a control instruction to the target robot, so that the lora gateway executes the calling method as claimed in claim 4.

10. A calling method, characterized in that: Applied to a robot, the method comprises: Obtaining a control instruction sent by a lora gateway; the control instruction is generated by the lora gateway based on a robot call request sent by a calling terminal; wherein the control instruction includes a unique identifier of the calling terminal, and the step of responding to the control instruction and going to the location of the calling terminal includes: Determining a map location of the calling terminal based on the unique identifier of the calling terminal; Go to the location of the calling terminal based on the map location; or The control instruction includes a map location of the calling terminal, and the step of responding to the control instruction and proceeding to the location of the calling terminal includes: Go to the location of the calling terminal based on the map location; Wherein, the map location is determined by the lora gateway through the unique identifier of the calling terminal in the robot call request; the lora gateway executes the calling method as claimed in claim 4; In response to the control instruction, the calling terminal goes to the location of the calling terminal.

11. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 4 to 10 are implemented.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 4 to 10 are implemented.

Citation Information

Patent Citations

  • A moving method and device

    CN109202896A

  • Hotel meal delivery method, device and equipment based on robot and storage medium

    CN112356022A

  • Robot calling system

    CN212096360U

  • Watch pager system based on LoRa communication

    CN214481287U

  • Serving system using robot and operation method thereof

    US20200070344A1

Cited By

  • Robot calling system based on LORA, and method, device and storage medium

    EP4637128A1