An offline docking method and device between a docking robot and a driverless vehicle

Abstract

The application relates to the technical field of robots, and provides an offline connection method and device between a connection robot and an unmanned vehicle. The method is applied to the connection robot and comprises the following steps: determining server exception information; determining a to-be-completed connection task according to the server exception information; the to-be-completed connection task comprises a task time, a task location and a task content; determining a target unmanned vehicle according to the task location; moving to the vicinity of the target unmanned vehicle and initiating a short-distance communication connection with the target unmanned vehicle; and performing connection with the target unmanned vehicle according to the task content within the task time. The application can complete the to-be-completed connection task remaining before server exception in the case of server exception. The application avoids the influence of network failure on the connection work of the connection robot and the unmanned vehicle, so that the connection robot and the unmanned vehicle can still normally connect in the offline state.

Description

Technical Field

[0001] This application relates to the field of robotics technology, and in particular to an offline connection method and apparatus for connecting a robot and an unmanned vehicle. Background Technology

[0002] With the booming development of the internet economy, advanced technologies such as automation and information are increasingly being applied in smart logistics warehousing centers. Among them, the cooperative transportation between unmanned vehicles and shuttle robots is currently a relatively advanced coordination method in smart logistics transportation.

[0003] The coordination between the autonomous vehicle and the shuttle robot is achieved through the transfer of the cargo compartment. The cargo compartment is a universal component that can be detachably attached to either the autonomous vehicle or the shuttle robot. The shuttle robot docking process is realized by transferring the cargo compartment from the autonomous vehicle to the shuttle robot.

[0004] In existing technologies, the shuttle robot and the unmanned vehicle are connected to the system server, which then obtains information and sends instructions to the shuttle robot or the unmanned vehicle to perform the shuttle operation.

[0005] However, due to the influence of the actual working environment, when a network failure occurs and the system server cannot be connected, how to ensure the smooth connection between the shuttle robot and the unmanned vehicle is an urgent problem to be solved. Summary of the Invention

[0006] In view of this, embodiments of this application provide an offline connection method and apparatus between a shuttle robot and an unmanned vehicle to solve the problem in the prior art where the shuttle robot and the unmanned vehicle cannot connect smoothly when the network fails to connect to the system server.

[0007] A first aspect of this application provides an offline shuttle method between a shuttle robot and an unmanned vehicle, the method being applied to the shuttle robot and including:

[0008] Determine server error information;

[0009] The pending connection tasks are determined based on the server error information; the pending connection tasks include the task time, task location, and task content.

[0010] Determine the target unmanned vehicle based on the mission location;

[0011] Move to the vicinity of the target unmanned vehicle and initiate a short-range communication connection with the target unmanned vehicle;

[0012] Within the mission time, connect with the target unmanned vehicle according to the mission requirements.

[0013] A second aspect of this application provides an offline shuttle device for connecting a robot and an unmanned vehicle, comprising:

[0014] Server anomaly information determination module: used to determine server anomaly information;

[0015] Pending Connection Task Determination Module: Used to determine pending connection tasks based on server error information; pending connection tasks include task time, task location, and task content;

[0016] Target Unmanned Vehicle Determination Module: Used to determine the target unmanned vehicle based on the mission location;

[0017] Connection module: Used to move to the vicinity of the target unmanned vehicle and initiate a short-range communication connection with the target unmanned vehicle;

[0018] Shuttle module: Used to shuttle to the target unmanned vehicle according to the task content within the task time.

[0019] A third aspect of this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described method.

[0020] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the above-described method.

[0021] The beneficial effects of this application's embodiments compared to existing technologies are as follows: In the event of a server malfunction, the shuttle robot can determine the target unmanned vehicle based on the pending shuttle task, move to the vicinity of the target unmanned vehicle, and initiate a short-range communication connection with it, thereby completing the remaining pending shuttle task before the server malfunction. This avoids network failures affecting the shuttle robot and unmanned vehicle's shuttle operation, ensuring normal shuttle operation even when offline. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a schematic diagram illustrating an application scenario of this application embodiment;

[0024] Figure 2This is a flowchart illustrating an offline connection method between a shuttle robot and an unmanned vehicle provided in an embodiment of this application;

[0025] Figure 3 This is a schematic diagram of an offline connection device between a shuttle robot and an unmanned vehicle provided in an embodiment of this application;

[0026] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0027] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0028] With the booming development of the internet economy, advanced technologies such as automation and information are increasingly being applied in smart logistics warehousing centers. Among them, the cooperative transportation between unmanned vehicles and shuttle robots is currently a relatively advanced coordination method in smart logistics transportation.

[0029] Autonomous vehicles (AVVs) are a type of robotics technology. AVVs are generally driverless vehicles that move between two fixed locations. Shuttle robots, on the other hand, may have more dispersed and specific routes, such as package delivery. An AVV with a large capacity can carry all the packages and travel between a distribution center and a specific residential area. A shuttle robot can then be responsible for delivering packages to each gate of that residential area. This delivery operation requires a shuttle process between the AVV and the shuttle robot. This shuttle process can be achieved by transferring the cargo compartment between the AVV and the shuttle robot.

[0030] The primary scenario for the shuttle robots and unmanned vehicles described in this application is cargo transportation. Unmanned vehicles can provide pickup and delivery services in urban environments such as enclosed office buildings, campuses, and other locations with concentrated orders. Their excellent flexibility and convenient operation will significantly improve delivery efficiency. Their high carrying capacity is beneficial for transporting large quantities of goods. Shuttle robots are highly flexible due to their small size and diverse functions, allowing them to easily navigate complex and varied transportation scenarios.

[0031] The coordination between the autonomous vehicle and the shuttle robot is achieved through the transfer of the cargo compartment. The cargo compartment is a universal component that can be detachably attached to either the autonomous vehicle or the shuttle robot. The shuttle robot docking process is realized by transferring the cargo compartment from the autonomous vehicle to the shuttle robot.

[0032] In existing technologies, the shuttle robot and the unmanned vehicle are connected to the system server, which then obtains information and sends instructions to the shuttle robot or the unmanned vehicle to perform the shuttle operation.

[0033] However, due to the influence of actual working environments, such as when the shuttle robot or unmanned vehicle moves to an area where the network is blocked, and a network failure occurs that prevents it from connecting to the system server, ensuring a smooth connection for the shuttle robot and unmanned vehicle is an urgent problem to be solved.

[0034] In view of the problems in the prior art, this disclosure provides a novel offline shuttle method and apparatus for shuttle robots and unmanned vehicles. In the event of a server malfunction, the shuttle robot can determine the target unmanned vehicle based on the shuttle task to be completed, move to the vicinity of the target unmanned vehicle, and initiate a short-range communication connection with the target unmanned vehicle, thereby completing the remaining shuttle task before the server malfunction. This avoids the shuttle robot and unmanned vehicle from being affected by network failures, allowing the shuttle robot and unmanned vehicle to continue to connect normally even when offline.

[0035] The following describes in detail, with reference to the accompanying drawings, an offline connection method and apparatus for connecting a shuttle robot and an unmanned vehicle according to an embodiment of this application.

[0036] Figure 1 This is a schematic diagram illustrating an application scenario according to an embodiment of this application. The application scenario may include terminal devices 101, 102, and 103, a network 104, a shuttle robot 105, and an unmanned vehicle 106.

[0037] Terminal devices 101, 102, and 103 can be hardware or software. When terminal devices 101, 102, and 103 are hardware, they can be various electronic devices with displays that support communication with server 104, including but not limited to smartphones, tablets, laptops, and desktop computers. When terminal devices 101, 102, and 103 are software, they can be installed in the aforementioned electronic devices. Terminal devices 101, 102, and 103 can be implemented as multiple software programs or software modules, or as a single software program or software module; this application embodiment does not impose any limitations on this. Furthermore, various applications can be installed on terminal devices 101, 102, and 103, such as data processing applications, instant messaging tools, social platform software, search applications, shopping applications, etc.

[0038] Network 104 can be a wired network using coaxial cable, twisted pair, and fiber optic connection, or it can be a wireless network that enables interconnection of various communication devices without wiring, such as Bluetooth, Near Field Communication (NFC), and Infrared. This application embodiment does not limit this.

[0039] The shuttle robot 105 can be a mobile robot with cargo carrying function, or a robot with navigation, recognition and near-field communication functions.

[0040] The unmanned vehicle 106 can be an autonomous, cargo-carrying intelligent mobile device, or a vehicle with near-field communication capabilities. It loads and transports goods by attaching multiple cargo compartments. These cargo compartments can move between the unmanned vehicle 106 and the shuttle robot 105, thus enabling shuttle operations between the two.

[0041] The shuttle robot 105 can establish a communication connection with the unmanned vehicle 106 via network 104 through terminal devices 101, 102, and 103 to receive or send information, etc. Alternatively, the shuttle robot 105 can directly establish a communication connection with the unmanned vehicle 106 via network 104. Specifically, the shuttle robot 105 determines server anomaly information; the shuttle robot 105 determines the shuttle task to be completed based on the server anomaly information; the shuttle task to be completed includes the task time, task location, and task content; the shuttle robot 105 determines the target unmanned vehicle based on the task location; moves to the vicinity of the target unmanned vehicle and initiates a short-range communication connection with the target unmanned vehicle; the shuttle robot 105 connects with the target unmanned vehicle according to the task content within the task time.

[0042] It should be noted that the specific types, quantities, and combinations of terminal devices 101, 102, and 103 and network 104 can be adjusted according to the actual needs of the application scenario, and this application embodiment does not impose any restrictions on this.

[0043] Figure 2 This is a flowchart illustrating an offline connection method between a shuttle robot and an unmanned vehicle provided in an embodiment of this application. Figure 2 The offline connection method between the shuttle robot and the unmanned vehicle can be provided by Figure 1 The shuttle robot 105 performs the operation. For example... Figure 2 As shown, the offline connection method between the shuttle robot and the unmanned vehicle includes:

[0044] S201, Determine server error information;

[0045] S202, Determine the connection task to be completed based on the server error information; the connection task to be completed includes the task time, task location and task content;

[0046] S203, determine the target unmanned vehicle based on the mission location;

[0047] S204, move to the vicinity of the target unmanned vehicle and initiate a short-range communication connection with the target unmanned vehicle;

[0048] S205, within the mission time, will connect with the target unmanned vehicle according to the mission content.

[0049] Specifically, in this embodiment, the unmanned vehicle (UAV) is a type of intelligent mobile robot used for loading goods. The docking robot is a robot used to dock with the UAV and unload goods. Typically, the UAV's cargo carrier is a cargo hold, and the UAV can have several cargo holds. The cargo hold is adapted to both the UAV and the docking robot. The docking robot moves to the bottom of the cargo hold and uses an operating component to unload the cargo hold from the UAV and place it on the docking robot. Each docking robot can dock with one cargo hold at a time, and the cargo holds can be transferred between the UAV and the docking robot to complete the docking. The server refers to a server that uniformly acquires information and then sends instructions to the docking robot or UAV. It receives and analyzes requests sent by terminal devices with which it has established communication connections, generates processing results, and then sends instructions to the docking robot or UAV based on the processing results. Determining server anomaly information means determining anomaly information indicating that the server cannot provide normal service. For example, server malfunctions or problems with the equipment or network in the data center; improper user operations after login causing server errors; malicious attacks or computer virus infections on the server; and the movement of connecting robots or unmanned vehicles to areas with poor network signals can all cause server abnormalities, meaning the inability to connect to the server.

[0050] Furthermore, based on the server anomaly information, pending shuttle tasks are determined. These tasks include the task time, task location, and task content. Pending shuttle tasks refer to the shuttle operations that the shuttle robot and the unmanned vehicle were conducting before the server anomaly occurred. When the server anomaly occurred, the task was interrupted, and the remaining unfinished tasks are the pending shuttle tasks. Pending shuttle tasks generally consist of task time, task location, and task content. Task time refers to the time when the shuttle robot and the unmanned vehicle will shuttle. Task location refers to the location where the shuttle robot shuttles with the unmanned vehicle. Task content refers to which cargo compartment on the unmanned vehicle the shuttle robot will shuttle with, or the specific number of cargo compartments to shuttle, etc.

[0051] Furthermore, the target autonomous vehicle is determined based on the task location. As mentioned above, the task location refers to where the shuttle robot will connect with the autonomous vehicle. The task location is the target location for the connection. There may be several autonomous vehicles around the shuttle robot, and the target autonomous vehicle to perform the connection task needs to be selected from these vehicles. Generally, a task location can correspond to one autonomous vehicle, and the task location and target autonomous vehicle are linked in the system information. The target autonomous vehicle pre-defined before the server malfunction can be selected through the task location.

[0052] Furthermore, it moves to the vicinity of the target unmanned vehicle and initiates a short-range communication connection with the target unmanned vehicle.

[0053] Once the target unmanned vehicle (UAV) is identified, the shuttle robot activates the positioning device on the UAV and moves to its vicinity by tracking the device. When a communication range is reached, a short-range communication connection is established with the UAV. A short-range communication connection refers to the transmission of information via radio waves over a relatively short distance. By establishing this connection, the UAV and the shuttle robot can share connection information prior to the server malfunction, mitigating the impact of task interruption caused by the server failure.

[0054] Furthermore, within the task timeframe, the shuttle robot connects with the target autonomous vehicle according to the task requirements. After establishing a connection with the target autonomous vehicle, the shuttle robot and the target autonomous vehicle re-establish their association. The shuttle task to be completed is then re-sent to the target autonomous vehicle. This allows the shuttle robot to connect with the target autonomous vehicle according to the task requirements within the task timeframe.

[0055] According to the technical solution provided in this disclosure, in the event of a server malfunction, the shuttle robot can determine the target unmanned vehicle based on the shuttle task to be completed, move to the vicinity of the target unmanned vehicle, and initiate a short-range communication connection with the target unmanned vehicle, thereby completing the remaining shuttle task before the server malfunction. This avoids the shuttle robot and unmanned vehicle from being affected by network failures, allowing the shuttle robot and unmanned vehicle to continue to connect normally even when offline.

[0056] In some embodiments, determining server error information includes:

[0057] Determine the network signal strength connected to the server;

[0058] Determine server anomaly information based on network signal strength.

[0059] Specifically, the shuttle robot connects to the server, acting as a receiver to receive instructions from the server. Therefore, testing tools or software built into the shuttle robot can be used to analyze the server's network quality and bandwidth by detecting packet loss rates, maximum and minimum values ​​between the server and the shuttle robot, thereby determining the network signal strength. The strength of the network signal is then used to identify server anomalies. For example, no network signal may indicate a damaged or malfunctioning server, or the shuttle robot may be located in an area without network coverage; a weak network signal may indicate the shuttle robot is located inside an elevator, or the server is in a China Telecom area using a China Unicom line, which will definitely affect its connection.

[0060] In some embodiments, determining the connection task to be completed based on server error information includes:

[0061] Determine the server's log information at the time of the anomaly based on the server anomaly information;

[0062] The pending connection tasks are determined based on the log information.

[0063] Specifically, server log information consists of one or more log files automatically created and maintained by the server, containing a list of activities performed by the server. These activities can include access records, error logs, security events, system events, and so on. When a server malfunctions, the error log at the time of the malfunction can be determined based on the server malfunction information. The error log reveals the server's access details, including access time, access source, and access type. Combining this information, the instructions received by the connection robot when accessing the server can be determined. In other words, the connection tasks assigned to the connection robot by the server at that time, including time, location, and content, can be identified. All this log information can then be used to determine the connection tasks to be completed.

[0064] In some embodiments, each autonomous vehicle has a specific identification code, and determining the target autonomous vehicle based on the mission location includes:

[0065] Determine the target identifier code that matches the mission location;

[0066] The target unmanned vehicle is identified based on the target identifier code.

[0067] Specifically, an identification code is a code used to uniquely identify a specific entity within a certain type of data, based on element classification. In this embodiment, the identification code can be a string of numbers, letters, or a combination of both. During the shuttle task, the task location is associated with the target identification code of the target autonomous vehicle. Determining the task location also determines the target identification code that matches it. The target identification code is a specific identifier for the target autonomous vehicle, thus allowing for its identification.

[0068] In some embodiments, moving to the vicinity of the target autonomous vehicle and initiating a short-range communication connection with the target autonomous vehicle includes:

[0069] Move to the vicinity of the target unmanned vehicle, pair with the target unmanned vehicle based on the target identification code, and establish a short-range communication connection;

[0070] This short-range communication connectivity includes Wi-Fi, Wi-Fi, Bluetooth, UWB, RFID, or NFC.

[0071] Specifically, once the target unmanned vehicle (UAV) is identified, the shuttle robot can activate the positioning device on the target UAV and move to its vicinity by tracking the positioning device. The target identification code can serve as the authorization password for pairing the shuttle robot with the target UAV. When a communication range is reached, a short-range communication connection is initiated with the target UAV. A short-range communication connection refers to a connection where the sending and receiving parties transmit information via radio waves over a relatively short distance. Generally, the shuttle robot and the target UAV can establish a short-range communication connection through the following methods.

[0072] With Wi-Fi, when both the shuttle robot and the target unmanned vehicle are located in an area around the access point, they share a common local area network, enabling effective communication and transmission.

[0073] ZigBee is primarily used for short-range communication between various electronic devices. The name ZigBee comes from the communication method bees use for survival and development. Bees dance in a zigzag pattern to share the location, distance, and direction of newly discovered food. ZigBee can be considered a sibling of the Bluetooth family. This family uses the 2.4GHz frequency band and employs frequency hopping technology. However, ZigBee is simpler and slower than Bluetooth, with lower power consumption and cost. Its basic data rate is 250kb / s, which can be reduced to 28kb / s, extending the transmission range to 134m and achieving higher reliability.

[0074] Bluetooth is a technology that establishes a universal short-range wireless interface for communication between fixed or mobile devices. It uses the globally common 2.4GHz ISM band and offers a transmission rate of 1Mbps and a transmission distance of 10m.

[0075] Ultra-wideband (UWB) is a wireless carrier communication technology. Because it uses nanosecond-level non-sinusoidal narrow pulses instead of sinusoidal carriers to transmit data, UWB can transmit signals with a very wide bandwidth. Using low-power pulses, it can transmit data over a very wide spectrum and utilize spectrum resources without causing significant interference to traditional narrowband wireless communication systems.

[0076] Radio Frequency Identification (RFID) is a type of automatic identification technology that uses wireless radio frequency for non-contact two-way data communication. It uses wireless radio frequency to read and write recording media (electronic tags or RFID cards) to achieve the purpose of identifying targets and exchanging data.

[0077] Near Field Communication (NFC) uses two-way identification and connection. It operates within a frequency range of 13.56MHz and a distance of 20cm. Initially a combination of remote control identification and networking technology, NFC has evolved into a wireless connectivity technology. By combining all identification applications and services on a single device, NFC solves the problem of storing multiple passwords, ensuring data security. Using NFC, wireless interconnection and the exchange of data and services can be achieved between multiple devices (e.g., digital cameras, PDAs, set-top boxes, computers, mobile phones, etc.).

[0078] In some embodiments, docking with the target unmanned vehicle according to the task content within the task time includes:

[0079] Sharing connection information with the target unmanned vehicle based on short-range communication connection;

[0080] The target driverless vehicle determines its docking permissions based on the docking information;

[0081] According to the docking authority, dock with the target unmanned vehicle within the task time and in accordance with the task content.

[0082] Specifically, after the shuttle robot initiates a short-range communication connection with the target unmanned vehicle (UAV), it can share shuttle information with the target UAV. This shuttle information includes the time, location, and content of the shuttle connection. In other words, the shuttle robot's pending shuttle tasks correspond to the shuttle information. Based on this shuttle information, the target UAV can determine what tasks it still needs to complete before losing connection with the server. According to this shuttle information, the target UAV can determine its shuttle permissions. Shutdown permissions refer to the scope and extent of the shuttle robot's connection with the target UAV. That is, the shuttle permissions ensure that the target UAV's original tasks, time, and content remain unchanged. Finally, the shuttle robot, based on its shuttle permissions, shuttles with the target UAV within the task time and according to the task content.

[0083] In some embodiments, where the method is applied to an autonomous vehicle, the method further includes:

[0084] Determine server error information;

[0085] Identify the target shuttle robot based on server anomaly information;

[0086] Move to the vicinity of the target shuttle robot and initiate a short-range communication connection with the target shuttle robot;

[0087] Connecting with the target robot is based on short-range communication.

[0088] Specifically, since unmanned vehicles are also a type of intelligent mobile cargo robot, their cargo compartments are interchangeable between unmanned vehicles and shuttle robots. Therefore, the shuttle process is bidirectional. This offline shuttle method can also be bidirectional. Unlike the previous embodiment, the execution entity in this embodiment is the unmanned vehicle. By determining server anomaly information, the target shuttle robot is identified based on this information. The vehicle moves to the vicinity of the target shuttle robot and initiates a short-range communication connection, then shuttles with the target shuttle robot based on this short-range communication connection. This completes the remaining shuttle tasks before the server anomaly. This avoids network failures affecting the shuttle operation of the unmanned vehicle and the shuttle robot, allowing the shuttle robot or unmanned vehicle to continue shuttleing normally even when offline.

[0089] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0090] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0091] Figure 3 This is a schematic diagram of an offline connection device between a shuttle robot and an unmanned vehicle provided in an embodiment of this application. Figure 3 As shown, the offline connection device between the shuttle robot and the unmanned vehicle includes:

[0092] The server exception information determination module 301 is configured to determine server exception information.

[0093] The pending connection task determination module 302 is configured to determine pending connection tasks based on server error information; the pending connection tasks include task time, task location and task content;

[0094] The target unmanned vehicle determination module 303 is configured to determine the target unmanned vehicle based on the mission location;

[0095] The connection module 304 is configured to move to the vicinity of the target unmanned vehicle and initiate a short-range communication connection with the target unmanned vehicle.

[0096] The docking module 305 is configured to dock with the target unmanned vehicle according to the task content within the task time.

[0097] In some embodiments, Figure 3 The server anomaly information determination module 301 includes:

[0098] Determine the network signal strength connected to the server;

[0099] Determine server anomaly information based on network signal strength.

[0100] In some embodiments, Figure 3 The pending connection task determination module 302 includes:

[0101] Determine the server's log information at the time of the anomaly based on the server anomaly information;

[0102] The pending connection tasks are determined based on the log information.

[0103] In some embodiments, each autonomous vehicle has a specific identification code. Figure 3 The target unmanned vehicle determination module 303 includes:

[0104] Determine the target identifier code that matches the mission location;

[0105] The target unmanned vehicle is identified based on the target identifier code.

[0106] In some embodiments, Figure 3 The connection module 304 includes:

[0107] Move to the vicinity of the target unmanned vehicle, pair with the target unmanned vehicle based on the target identification code, and establish a short-range communication connection;

[0108] This short-range communication connectivity includes Wi-Fi, Wi-Fi, Bluetooth, UWB, RFID, or NFC.

[0109] In some embodiments, Figure 3 The connection module 305 includes:

[0110] Sharing connection information with the target unmanned vehicle based on short-range communication connection;

[0111] The target driverless vehicle determines its docking permissions based on the docking information;

[0112] According to the docking authority, dock with the target unmanned vehicle within the task time and in accordance with the task content.

[0113] In some embodiments, the method is applied to autonomous vehicles. Figure 3 The connection module 305 also includes:

[0114] Determine server error information;

[0115] Identify the target shuttle robot based on server anomaly information;

[0116] Move to the vicinity of the target shuttle robot and initiate a short-range communication connection with the target shuttle robot;

[0117] Connecting with the target robot is based on short-range communication.

[0118] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0119] Figure 4 This is a schematic diagram of the electronic device 4 provided in an embodiment of this application. Figure 4 As shown, the electronic device 4 of this embodiment includes: a processor 401, a memory 402, and a computer program 403 stored in the memory 402 and executable on the processor 401. When the processor 401 executes the computer program 403, it implements the steps in the various method embodiments described above. Alternatively, when the processor 401 executes the computer program 403, it implements the functions of each module / unit in the various device embodiments described above.

[0120] Electronic device 4 can be a desktop computer, laptop, handheld computer, cloud server, or other electronic device. Electronic device 4 may include, but is not limited to, processor 401 and memory 402. Those skilled in the art will understand that... Figure 4 This is merely an example of electronic device 4 and does not constitute a limitation on electronic device 4. It may include more or fewer components than shown, or different components.

[0121] The processor 401 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0122] The memory 402 can be an internal storage unit of the electronic device 4, such as a hard disk or RAM of the electronic device 4. The memory 402 can also be an external storage device of the electronic device 4, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, Flash Card, etc., equipped on the electronic device 4. The memory 402 can also include both internal and external storage units of the electronic device 4. The memory 402 is used to store computer programs and other programs and data required by the electronic device.

[0123] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0124] If an integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program may include computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added to or subtracted according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0125] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. An offline shuttle method between a shuttle robot and an unmanned vehicle, characterized in that, The method is applied to a shuttle robot, and the method includes: Determine server error information; The pending connection task is determined based on the server anomaly information; the pending connection task includes the task time, task location, and task content; The target unmanned vehicle is determined based on the mission location; Move to the vicinity of the target unmanned vehicle and initiate a short-range communication connection with the target unmanned vehicle; Within the specified task time, the vehicle shall connect with the target unmanned vehicle in accordance with the specified task content. The step of determining the connection task to be completed based on the server anomaly information includes: The server's log information at the time of the anomaly is determined based on the server anomaly information; The connection tasks to be completed are determined based on the log information.

2. The method according to claim 1, characterized in that, The information used to determine server anomalies includes: Determine the network signal strength connected to the server; The server anomaly information is determined based on the network signal strength.

3. The method according to claim 1, characterized in that, Each of the unmanned vehicles has a specific identification code, and determining the target unmanned vehicle based on the mission location includes: Determine the target identifier code that matches the mission location; The target unmanned vehicle is identified based on the target identification code.

4. The method according to claim 3, characterized in that, The step of moving to the vicinity of the target unmanned vehicle and initiating a short-range communication connection with the target unmanned vehicle includes: Move to the vicinity of the target unmanned vehicle, pair with the target unmanned vehicle based on the target identification code, and establish the short-range communication connection; The short-range communication connection includes Wi-Fi, Wi-Fi, Bluetooth, ultra-wideband, RFID, or NFC.

5. The method according to claim 4, characterized in that, The step of connecting with the target unmanned vehicle according to the task content within the task time includes: Based on the short-range communication connection, the shuttle information is shared with the target unmanned vehicle; The target unmanned vehicle determines its docking permission based on the docking information; According to the connection permission, the vehicle shall connect with the target unmanned vehicle within the specified task time according to the task content.

6. The method according to any one of claims 1 to 5, characterized in that, If the method is applied to an autonomous vehicle, then the method further includes: Determine server error information; The target shuttle robot is determined based on the server anomaly information; Move to the vicinity of the target shuttle robot and initiate a short-range communication connection with the target shuttle robot; Connecting with the target shuttle robot based on the short-range communication connection.

7. An offline shuttle device for connecting a robot and an unmanned vehicle, characterized in that, include: Server anomaly information determination module: used to determine server anomaly information; Pending connection task determination module: used to determine pending connection tasks based on the server anomaly information; the pending connection tasks include task time, task location and task content; Target unmanned vehicle determination module: used to determine the target unmanned vehicle based on the mission location; Connection module: used to move to the vicinity of the target unmanned vehicle and initiate a short-range communication connection with the target unmanned vehicle; The docking module is used to dock with the target unmanned vehicle according to the task content within the task time. The module for determining pending connection tasks is specifically used to: determine the server's log information when an anomaly occurs based on the server anomaly information; and determine the pending connection tasks based on the log information.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 6.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 6.

Images