Intelligent IoT Security System

Through the server-side management of the robot charging queue of the intelligent IoT security system, the problem of the lack of overall coordination and control of security robots when the power is low is solved, and effective coverage and security guarantees for community patrol tasks are achieved.

CN113162146BActive Publication Date: 2025-06-17KAISA PROPERTY MANAGEMENT (SHENZHEN) CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202110312751.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-03-24
Publication Date
2025-06-17
Estimated Expiration
2041-03-24

AI Technical Summary

Technical Problem

Existing security robots charge themselves when the battery is low, but lack overall coordination and control, resulting in a gap in community patrol tasks, affecting community safety.

Method used

Design an intelligent IoT security system to manage the robot queue and charging queue through the server side, receive charging requests from the security robot, and decide whether to allow charging or waiting in line according to the set control logic to ensure the overall coordinated control of the charging process.

Benefits of technology

It effectively avoids the large gaps in security robots during work, ensures the safety of the community, and ensures continuous security by notifying human patrols when most robots are charged.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113162146B_ABST
    Figure CN113162146B_ABST
Patent Text Reader

Abstract

The present invention relates to an intelligent Internet of Things security system and method, including: creating and managing a robot queue, and creating and managing a robot charging queue; receiving a charging request from any security robot connected to the server side, where the charging request carries the robot ID and the current remaining battery level of the security robot; making a decision according to the control logic to determine whether the security robot is to charge or queue up for waiting; when sending an instruction for the security robot to wait for charging or allowing charging, sending the waiting charging or charging information of the security robot, as well as the current remaining battery level, to the corresponding mobile terminal. The present invention can be applied in the field of community security patrol, and overall coordinated control is achieved for the charging processes of multiple security robots performing security patrol tasks therein, avoiding large gaps in the work of the security robots. When most security robots are charging, it will also notify the mobile terminal of the personnel, thereby ensuring community security.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of property security management, and in particular to an intelligent Internet of Things security system. Background Art

[0002] Property management is an activity in which an operation and a property service enterprise repair, maintain, and manage a house and its supporting facilities and equipment and related sites in accordance with the agreement of a property service contract, and maintain the environmental hygiene and related order within the property management area. At present, in property management, service enterprises have been able to provide various comprehensive services for community residents.

[0003] Property security management is a conventional service provided by a property service enterprise to community residents. Property security management refers to the management behavior in which a property service enterprise takes various measures and means to ensure the personal and property safety of community owners and maintain the normal living and working order. Property security management includes two aspects: "prevention" and "protection". "Prevention" is to prevent disasters and harmful accidents from occurring, and "protection" is to carry out emergency treatment of the accidents that occur through various measures. Security patrol is a basic task that property security personnel must perform to prevent and properly handle accidents.

[0004] Traditional security patrols are completed by relying on manpower. With the soaring of labor costs and the development of intelligent technologies, more and more security robots have joined the work of community patrols. For example, some more advanced communities can use multiple security robots to divide areas for patrols to achieve full coverage of the community. These robots usually rely on rechargeable batteries to provide power. In the case of low battery power, these robots can charge themselves.

[0005] The inventor of the present invention found in the research that most of the existing security robots charge themselves when the battery power is low, and there is no overall coordinated control method. When most or all of the security robots charge themselves, it will cause a gap in the community patrol task, which will pose a hidden danger to the community's security.

[0006] Therefore, it is necessary to improve this. Summary of the Invention

[0007] In view of this, in response to the above problems, the present invention provides an intelligent Internet of Things security system, which can be applied in the field of community security patrols, and realizes overall coordinated control of the charging processes of multiple security robots performing security patrol tasks, avoiding large gaps in the work of security robots. When most security robots are charging, it will also notify the mobile terminals of personnel, and temporarily replace robot patrols with manual patrols to ensure community security.

[0008] To achieve the above object, the present invention provides the following technical solutions:

[0009] An embodiment of the present invention provides a charging control method for a security robot, which is applicable to a server side and includes:

[0010] Create and manage a robot queuing queue, and create and manage a robot charging queue;

[0011] Receive a charging request from any security robot connected to the server side, where the charging request carries the robot ID and the current remaining power of the security robot;

[0012] Make a decision according to the following control logic to determine whether the security robot is to charge or queue up and wait:

[0013] If the current remaining power does not exceed the first threshold, move the robot ID of the security robot into the robot charging queue and send an instruction to allow charging to the security robot;

[0014] If the current remaining power exceeds the first threshold but does not exceed the second threshold, move the robot ID of the security robot into the robot queuing queue, send an instruction to wait for charging to the security robot, and further count the number of robots in the robot charging queue in real time until the number of robots is lower than the first ratio of the total number of security robots, then send an instruction to allow charging to the security robot, move the robot ID out of the robot queuing queue, and move it into the robot charging queue;

[0015] If the current remaining power exceeds the second threshold but does not exceed the third threshold, move the robot ID of the security robot into the robot queuing queue, send an instruction to wait for charging to the security robot, and further count the number of robots in the robot charging queue in real time until the number of robots is lower than the second ratio of the total number of security robots, then send an instruction to allow charging to the security robot, move the robot ID out of the robot queuing queue, and move it into the robot charging queue;

[0016] The first threshold is lower than the second threshold, and the second threshold is lower than the third threshold; the first ratio is higher than the second ratio;

[0017] The method further includes:

[0018] When sending an instruction to wait for charging or allow charging to the security robot, send the waiting charging or charging information of the security robot and the current remaining power to the mobile terminal corresponding to the robot ID.

[0019] In one embodiment of the present invention, the method further includes the step of adjusting the robot queuing queue in real time, specifically:

[0020] When a new robot ID is moved into the robot queuing queue, obtain the remaining power of all security robots in the current robot queuing queue, assign a high priority to the security robots with low power, and the security robots with high priority preferentially obtain the instruction to allow charging.

[0021] In one embodiment of the present invention, the method further includes: obtaining the current power of the security robots in the robot charging queue in real time. When the current power of any security robot reaches the fourth threshold, send an instruction to stop charging to the security robot, and the fourth threshold is higher than the third threshold.

[0022] In one embodiment of the present invention, the method further includes: when sending an instruction to allow charging to the security robot, navigate the security robot to the charging pile closest to the security robot.

[0023] In one embodiment of the present invention, the first threshold is 20%, the second threshold is 40%, the third threshold is 60%, the fourth threshold is 85% to 100%, the first ratio is 50%, and the second ratio is 25%.

[0024] Another aspect of the embodiments of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the method as described above is implemented.

[0025] Another aspect of the embodiments of the present invention further provides a security robot charging control method, which is applicable to the security robot side and includes:

[0026] Obtain the current remaining power of the security robot in real time;

[0027] Whenever the current remaining power is lower than the first threshold, the second threshold or the third threshold, send a charging request to the server side. The charging request carries the robot ID and the current remaining power of the security robot for the server side to make a decision. The first threshold is lower than the second threshold, and the second threshold is lower than the third threshold;

[0028] Receive the instruction to allow charging or the instruction to queue and wait sent by the server side.

[0029] In one embodiment of the present invention, the method further includes:

[0030] After receiving the instruction to allow charging sent by the server side, the security robot performs self-navigation or receives navigation from the server side and moves to the nearest charging pile for charging.

[0031] In one embodiment of the present invention, the method further includes:

[0032] While the security robot is charging, the current battery level is sent to the server in real time until the current battery level is higher than the fourth threshold. Then, the security robot receives the instruction to stop charging from the server, leaves the charging pile, and resumes the security patrol task.

[0033] Another aspect of the embodiments of the present invention further provides an intelligent Internet of Things security system, including a server, N security robots, X charging piles with positioning functions, and Y mobile terminals; any one of the security robots, any one of the charging piles, and any one of the mobile terminals are connected to the server, where N, X, and Y are all positive integers, and both X and Y do not exceed N;

[0034] The server is used to create and manage the robot queue and the robot charging queue, and is also used to receive the charging request of any security robot connected to the server. The charging request carries the robot ID and the current remaining battery level of the security robot, and is used to make a decision according to the control logic to determine whether the security robot is to charge or queue up and wait;

[0035] The server is further used to send the waiting-to-charge or charging information of the security robot, as well as the current remaining battery level, to the mobile terminal corresponding to the robot ID;

[0036] Any one of the security robots is used to obtain the current remaining battery level of the security robot in real time. Whenever the current remaining battery level is lower than the first threshold, the second threshold, or the third threshold, a charging request is sent to the server. The charging request carries the robot ID and the current remaining battery level of the security robot for the server to make a decision. The first threshold is lower than the second threshold, and the second threshold is lower than the third threshold; the security robot is further used to receive the instruction to allow charging or the instruction to queue up and wait sent by the server.

[0037] The security robot charging control method, intelligent IoT security system, electronic device, and storage medium provided by the above embodiments of the present invention can create and manage a robot queue and a robot charging queue. When the battery level of a security robot is low, it can receive a charging request from the security robot, determine whether the security robot should charge or queue up according to the set control logic, send corresponding control instructions to the security robot, and also send the information to the mobile terminal corresponding to the security robot. In this way, in the field of community security patrol, the charging process of multiple security robots performing security patrol tasks can be coordinated as a whole, avoiding large gaps in the work of security robots. When most security robots are charging, it will also notify the mobile terminal of the personnel, and temporarily replace robot patrol with manual patrol to ensure community security. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 FIG. 6 is a schematic structural diagram and an application scenario diagram of an intelligent IoT security system provided by an embodiment of the present invention;

[0039] Figure 2 FIG. 10 is a schematic flowchart of a security robot charging control method provided by an embodiment of the present invention;

[0040] Figure 3 FIG. 14 is a schematic flowchart of a security robot charging control method provided by another embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0041] In order to make the above objects, features, and advantages of the present invention more obvious and understandable, the technical solutions of the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts belong to the scope of protection of the present invention.

[0042] In the description herein, it should be understood that the orientation or positional relationships such as "upper", "lower", "left", "right", etc. are only for the convenience of description and simplification of operations, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and thus should not be construed as a limitation of the present invention. In addition, the terms "first" and "second" are only used for descriptive distinction and have no special meaning.

[0043] In the description of this specification, the description referring to terms such as "one embodiment" and "example" means that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example.

[0044] Embodiment 1

[0045] See Figure 1 , which is a schematic structural diagram and an application scenario diagram of an intelligent Internet of Things security system provided by Embodiment 1 of the present invention.

[0046] The intelligent Internet of Things security system in this embodiment is applied to the scenario of property security patrol in a community. As is well known, with the increase in labor costs, more and more advanced communities have used security robots for patrol. These security robots are equipped with batteries to provide electrical energy for their patrol work. In the case where the battery power of the security robot is low, the security robot needs to be charged. In addition, this community is also equipped with a certain number of security guards to perform manual patrols and handle emergencies.

[0047] See Figure 1 , the intelligent Internet of Things security system in this embodiment includes a server side, security robots, charging piles, and mobile terminals.

[0048] Specifically, the server side in this embodiment can be, but is not limited to, set in the computer room of the security guard room. The server side includes necessary information receiving, transmitting, and processing devices, such as servers, computers, monitors, and various other control devices. The server side can be connected to all the security robots, charging piles, and mobile terminals equipped by each security guard in this community through various forms of networks.

[0049] The security robots in this embodiment have the function of self - movement. For example, they can be wheeled security robots or other types such as tracked security robots. According to the security patrol requirements of the community, the security robots can perform various forms of security patrols, such as security patrols for personal and property safety, fire patrols, etc. The security robots need to be equipped with various detection sensors, such as cameras, infrared detectors, etc. The security robots also need to be equipped with wireless network communication modules so that they can connect to and communicate with the server side. The security robots are powered by their own storage batteries. Each security robot can perform security patrols within a certain area range in the community according to the task customization. Through the coordinated cooperation of multiple security robots, the comprehensive coverage of community patrols can be achieved. The number of security robots in this embodiment can be represented by N. Generally speaking, a smaller community can use 4 security robots to achieve full coverage, while a large community needs about 8 security robots to be competent for the patrol task.

[0050] The charging pile in this embodiment can charge the security robot. The charging pile itself has a positioning device for positioning. The charging pile is also connected to the server side for the server side to navigate the robot so that it can navigate to the nearest charging pile that is not occupied by a charged robot. Of course, the security robot can also navigate based on its own navigation module. The number of charging piles in this embodiment can be represented by X. Generally, the value of X can be set to be equal to the value of N. To save costs, the value of X can also be lower than the value of N.

[0051] The mobile terminal in this embodiment is the mobile terminal equipped for the community security personnel, which can be but is not limited to a mobile phone. Usually, the mobile terminal of one security guard can correspond to at least one security patrol robot. When all the security patrol robots corresponding to the mobile terminal are charging, it is necessary to switch from security robot patrol to manual patrol to ensure the safety of the community. Here, the number of mobile terminals is represented by Y. Generally, the value of Y is less than the value of N to save labor costs.

[0052] Specifically, the intelligent IoT security system in this embodiment includes a server side, N security robots, X charging piles with positioning functions, and Y mobile terminals; any one of the security robots, any one of the charging piles, and any one of the mobile terminals are connected to the server side. N, X, and Y are all positive integers, and both X and Y do not exceed N;

[0053] The server side is used to create and manage the robot queue and the robot charging queue, and is also used to receive the charging request of any security robot connected to the server side. The charging request carries the robot ID and the current remaining power of the security robot, and is used to make a decision according to the control logic to determine whether the security robot is to charge or queue up and wait;

[0054] The server side is also used to send the information that the security robot is waiting to charge or is charging, as well as the current remaining power to the mobile terminal corresponding to the robot ID;

[0055] Any one of the security robots is used to obtain the current remaining power of the security robot in real time. Whenever the current remaining power is lower than the first threshold, the second threshold, or the third threshold, it sends a charging request to the server side. The charging request carries the robot ID and the current remaining power of the security robot for the server side to make a decision. The first threshold is lower than the second threshold, and the second threshold is lower than the third threshold; the security robot is also used to receive the instruction to allow charging or the instruction to queue up and wait sent by the server side.

[0056] Embodiment Two

[0057] In Embodiment 2, a security robot charging control method is provided, specifically as follows Figure 2 The security robot charging control method provided in this embodiment is applicable to the server side.

[0058] Such as Figure 2 The security robot charging control method in this embodiment includes:

[0059] Step 201: Create and manage a robot queuing queue and create and manage a robot charging queue.

[0060] Step 202: Receive a charging request from any security robot connected to the server side.

[0061] Specifically, the charging request in this step carries the robot ID and the current remaining power of the security robot.

[0062] Step 203: Make a decision according to the control logic to determine whether the security robot is to charge or queue up and wait.

[0063] The specific control logic of this step is as follows: If the current remaining power does not exceed the first threshold, move the robot ID of the security robot into the robot charging queue and send an instruction to allow charging to the security robot; if the current remaining power exceeds the first threshold but does not exceed the second threshold, move the robot ID of the security robot into the robot queuing queue, send an instruction to wait for charging to the security robot, and further count the number of robots in the robot charging queue in real time until the number of robots is lower than the first ratio of the total number of security robots, then send an instruction to allow charging to the security robot, move the robot ID out of the robot queuing queue, and move it into the robot charging queue; if the current remaining power exceeds the second threshold but does not exceed the third threshold, move the robot ID of the security robot into the robot queuing queue, send an instruction to wait for charging to the security robot, and further count the number of robots in the robot charging queue in real time until the number of robots is lower than the second ratio of the total number of security robots, then send an instruction to allow charging to the security robot, move the robot ID out of the robot queuing queue, and move it into the robot charging queue. In this control logic, the first threshold is lower than the second threshold, and the second threshold is lower than the third threshold; the first ratio is higher than the second ratio. In an application scenario, the first threshold is 20%, the second threshold is 40%, the third threshold is 60%, the first ratio is 50%, and the second ratio is 25%.

[0064] Further, the server is also responsible for adjusting the robot queue. Specifically, when a new robot ID is moved into the robot queue, the remaining battery levels of all security robots in the current robot queue are obtained, and the security robots with low battery levels are given high priorities, and the security robots with high priorities are given the instruction to charge first.

[0065] After the server sends the instruction to allow charging to the robot, in some cases where the battery level of a security robot is too low, it is also necessary to navigate the security robot to the charging pile closest to the security robot.

[0066] In this step, while the security robot is charging, the current battery level of the security robot in the robot charging queue is obtained in real time. When the current battery level of any security robot reaches the fourth threshold, an instruction to stop charging is sent to the security robot. The fourth threshold in this step is higher than the third threshold. Generally, the value range of the fourth threshold is 85% to 100%. When the patrol task of the security robot is heavy, the value of the fourth threshold can be lowered, and when the task is not much, the security robot can be fully charged.

[0067] Step 204, when sending the instruction to wait for charging or allow charging to the security robot, the waiting for charging or charging information of the security robot, as well as the current remaining battery level, are sent to the mobile terminal corresponding to the robot ID.

[0068] This step provides the possibility of switching between robot patrol and manual patrol. When all the robots corresponding to the mobile terminal are charging, manual charging is required.

[0069] As for when a certain security robot is charging, the remaining security robots in the working state need to re-customize the patrol area and tasks, which will not be elaborated in detail in this application.

[0070] Embodiment III

[0071] Figure 3 It is a security robot charging control method provided by an embodiment of the present invention. The method in this embodiment is applicable to the security robot side.

[0072] Specifically, the method provided in this embodiment includes:

[0073] Step 301, obtain the current remaining battery level of the security robot in real time.

[0074] Step 302, whenever the current remaining battery level is lower than the first threshold, the second threshold or the third threshold, a charging request is sent to the server.

[0075] Specifically, in this step, the charging request carries the robot ID of the security robot and the current remaining power. The security robot sends a charging request to the server for the server to make a decision. Here, the first threshold is lower than the second threshold, and the second threshold is lower than the third threshold. Generally speaking, the first threshold is 20%, the second threshold is 40%, and the third threshold is 60%.

[0076] Step 303: Receive the instruction to allow charging or the instruction to queue up and wait sent by the server.

[0077] Step 304: After receiving the instruction to allow charging sent by the server, the security robot performs self-navigation or receives navigation from the server and moves to the nearest charging pile for charging.

[0078] Step 305: While the security robot is charging, it sends the current power to the server in real time until the current power is higher than the fourth threshold. Then it receives the instruction to stop charging sent by the server, leaves the charging pile, and resumes the security patrol task.

[0079] In summary, the security robot charging control method, intelligent IoT security system, electronic device, and storage medium provided in the above embodiments of the present invention can create and manage the robot queue and the robot charging queue. When the power of the security robot is low, it can receive the charging request of the security robot, determine whether the security robot is to charge or queue up and wait according to the set control logic, and send the corresponding control instruction to the security robot. At the same time, the information is also sent to the mobile terminal corresponding to the security robot. In this way, in the field of community security patrol, the charging process of multiple security robots performing security patrol tasks can be coordinated as a whole, avoiding a large gap in the work of the security robots. When most security robots are charging, it will also notify the mobile terminal of the personnel, and temporarily replace the robot patrol with manual patrol to ensure community security.

[0080] In addition, it should be understood that although this specification is described according to the embodiments, not every embodiment only contains an independent technical solution. This narrative way of the specification is only for clarity. Those skilled in the art should regard the specification as a whole, and the technical solutions in each embodiment can also be appropriately combined to form other embodiments that can be understood by those skilled in the art.

[0081] In summary, the above-described embodiments merely represent several implementation manners of the present invention. Their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of the present invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present invention, several modifications and improvements can still be made, and these all fall within the protection scope of the present invention. Therefore, the protection scope of the present invention patent shall be subject to the appended claims. As mentioned above, the present invention can also have more improvements. Without departing from the principle of the present device, several improvements and refinements should also be regarded as within the protection scope of the present invention.

Claims

1. A charging control method for a security robot, applicable to the server side, characterized in that, Including: Creating and managing a robot queuing queue, and creating and managing a robot charging queue; Receiving a charging request of any security robot connected to the server side, where the charging request carries the robot ID and the current remaining battery level of the security robot; Making a decision according to the following control logic to determine whether the security robot is to charge or queue up and wait: If the current remaining battery level does not exceed the first threshold, move the robot ID of the security robot into the robot charging queue, and send an instruction allowing charging to the security robot; If the current remaining battery level exceeds the first threshold but does not exceed the second threshold, move the robot ID of the security robot into the robot queuing queue, send an instruction to wait for charging to the security robot, and further count the number of robots in the robot charging queue in real time. Only when the number of robots is lower than the first proportion of the total number of security robots, send an instruction allowing charging to the security robot, move the robot ID out of the robot queuing queue, and move it into the robot charging queue; If the current remaining battery level exceeds the second threshold but does not exceed the third threshold, move the robot ID of the security robot into the robot queuing queue, send an instruction to wait for charging to the security robot, and further count the number of robots in the robot charging queue in real time. Only when the number of robots is lower than the second proportion of the total number of security robots, send an instruction allowing charging to the security robot, move the robot ID out of the robot queuing queue, and move it into the robot charging queue; The above-mentioned first threshold is lower than the second threshold, and the second threshold is lower than the third threshold; the first proportion is higher than the second proportion; The method further includes: When sending an instruction to wait for charging or allowing charging to the security robot, sending the information that the security robot is waiting for charging or allowing charging, as well as the current remaining battery level, to the mobile terminal corresponding to the robot ID.

2. The charging control method for a security robot according to claim 1, characterized in that, The method further includes the step of adjusting the robot queuing queue in real time, specifically: When a new robot ID is moved into the robot queuing queue, obtain the remaining battery levels of all security robots in the current robot queuing queue, and assign a high priority to the security robots with low battery levels. The security robots with high priority obtain the instruction allowing charging first.

3. The charging control method for a security robot according to claim 2, characterized in that, The method further includes: obtaining the current battery level of the security robot in the robot charging queue in real time. When the current battery level of any security robot reaches the fourth threshold, send an instruction to stop charging to the security robot, and the fourth threshold is higher than the third threshold.

4. The charging control method for a security robot according to claim 3, characterized in that, The method further includes: when sending an instruction allowing charging to the security robot, navigating the security robot to the charging pile closest to the security robot.

5. The charging control method for a security robot according to claim 4, characterized in that, The first threshold is 20%, the second threshold is 40%, the third threshold is 60%, the fourth threshold is 85% to 100%, the first proportion is 50%, and the second proportion is 25%.

6. A computer-readable storage medium, on which a computer program is stored, characterized in that, When the computer program is executed by a processor, it implements the method according to any one of claims 1 to 5.

7. An intelligent Internet of Things security system, characterized in that, It includes a server, N security robots, X charging piles with positioning functions, and Y mobile terminals; any one of the security robots, any one of the charging piles, and any one of the mobile terminals are connected to the server, where N, X, and Y are all positive integers, and both X and Y do not exceed N; The server controls the N security robots by using the security robot charging control method according to any one of claims 1-5; The server is used to create and manage a robot queue and a robot charging queue, and is also used to receive a charging request from any security robot connected to the server. The charging request carries the robot ID and the current remaining power of the security robot, and is used to make a decision according to the control logic to determine whether the security robot is to charge or queue up; it is also used to send the information that the security robot is waiting to charge or is allowed to charge, as well as the current remaining power, to the mobile terminal corresponding to the robot ID; Any one of the security robots is used to obtain the current remaining power of the security robot in real time. Whenever the current remaining power is lower than the first threshold, the second threshold, or the third threshold, it sends a charging request to the server. The charging request carries the robot ID and the current remaining power of the security robot for the server to make a decision. The first threshold is lower than the second threshold, and the second threshold is lower than the third threshold; the security robot is also used to receive an instruction to allow charging or an instruction to queue up sent by the server.

Citation Information

Patent Citations

  • Automatic multirobot charging scheduling method

    CN107154664A