Movatterモバイル変換


[0]ホーム

URL:


CN112070456B - Method for issuing task, terminal equipment, robot and storage medium - Google Patents

Method for issuing task, terminal equipment, robot and storage medium
Download PDF

Info

Publication number
CN112070456B
CN112070456BCN202010763563.1ACN202010763563ACN112070456BCN 112070456 BCN112070456 BCN 112070456BCN 202010763563 ACN202010763563 ACN 202010763563ACN 112070456 BCN112070456 BCN 112070456B
Authority
CN
China
Prior art keywords
task
inspection
robot
patrol
identity
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010763563.1A
Other languages
Chinese (zh)
Other versions
CN112070456A (en
Inventor
黄高波
阳柳郴
李珍珠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Ubtech Technology Co ltd
Original Assignee
Shenzhen Ubtech Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Ubtech Technology Co ltdfiledCriticalShenzhen Ubtech Technology Co ltd
Priority to CN202010763563.1ApriorityCriticalpatent/CN112070456B/en
Publication of CN112070456ApublicationCriticalpatent/CN112070456A/en
Application grantedgrantedCritical
Publication of CN112070456BpublicationCriticalpatent/CN112070456B/en
Activelegal-statusCriticalCurrent
Anticipated expirationlegal-statusCritical

Links

Classifications

Landscapes

Abstract

The application is applicable to the technical field of robots, and provides a task issuing method, terminal equipment, a robot and a storage medium, wherein the task issuing method comprises the following steps: the terminal equipment receives the inspection content input by the user, generates an inspection task according to the inspection content, corresponds to the first identity, acquires a second identity sent by the robot if the existence of the robot in wired communication with the terminal equipment is detected, sends the inspection content corresponding to the inspection task to the robot if the first identity is consistent with the second identity and the inspection task is detected to be a task to be issued, stores the inspection task if the existence of the robot in wired communication with the terminal equipment is detected, and can meet the requirement of the user for issuing the task to the robot at any time, thereby improving user experience.

Description

Method for issuing task, terminal equipment, robot and storage medium
Technical Field
The application belongs to the technical field of robots, and particularly relates to a task issuing method, terminal equipment, a robot and a storage medium.
Background
With the development of robot technology, robots are applied to more and more fields, for example, robots can perform inspection according to inspection tasks issued by terminal devices. For some patrol tasks with high confidentiality requirements, the patrol tasks can be issued only under the condition that the robot and the terminal equipment are in wired communication. Because the robot is in a mobile state most of the time and can not perform wired communication with the terminal equipment in the mobile state, the robot is in an unconnected state most of the time. If a user needs to issue a task to the robot through the terminal equipment, the task can be executed after the robot is required to execute the current task and the terminal equipment is in wired communication, and the task cannot be issued to the robot at any time, so that the user experience is poor.
Disclosure of Invention
In view of this, the embodiments of the present application provide a method, a terminal device, a robot, and a storage medium for issuing tasks, which can meet the requirement that a user issues tasks to the robot at any time, thereby improving user experience.
A first aspect of an embodiment of the present application provides a method for issuing a task, where the method for issuing a task is executed in a terminal device, and the method for issuing a task includes:
receiving inspection content input by a user, and generating an inspection task according to the inspection content, wherein the inspection task corresponds to a first identity identifier;
if the robot in wired communication with the terminal equipment is detected, acquiring a second identity sent by the robot;
if the first identity identifier is consistent with the second identity identifier and the inspection task is detected to be a task to be issued, sending inspection content corresponding to the inspection task to the robot;
and if the robot which is in wired communication with the terminal equipment is detected to be absent, storing the inspection task.
In a possible implementation manner of the first aspect, the detecting that the patrol task is a task to be issued includes:
acquiring a synchronous identifier corresponding to the inspection task;
and if the synchronous identifier is the first identifier, determining that the inspection task is a task to be issued.
In a possible implementation manner of the first aspect, after the sending, to the robot, patrol content corresponding to the patrol task, the method for issuing a task further includes:
and if receiving the information of successful reception sent by the robot, updating the synchronous identifier to a second identifier.
In a possible implementation manner of the first aspect, the inspection content includes inspection parameters and inspection time information, and the inspection parameters include: patrol position, patrol object and shooting parameters.
In a possible implementation manner of the first aspect, before the storing the inspection task, the method for issuing the task further includes:
determining the task type of the inspection task;
correspondingly, if the robot which is in wired communication with the terminal equipment is detected to be not present, storing the patrol task, including:
and if the fact that the robot in wired communication with the terminal equipment does not exist is detected, and the task type is the first task type, storing the inspection task. A second aspect of the embodiments of the present application provides a method for issuing a task, where the method for issuing a task is performed on a robot, and the method for issuing a task includes:
after establishing wired communication with terminal equipment, sending a second identity of the robot to the terminal equipment;
and acquiring the patrol content which is sent by the terminal equipment and corresponds to the patrol task, wherein the patrol task is a task to be issued, the patrol task corresponds to a first identity, and the first identity is consistent with the second identity.
In a possible implementation manner of the second aspect, after the acquiring the patrol content corresponding to the patrol task and sent by the terminal device, the method for issuing the patrol task further includes:
and planning a patrol path according to the patrol content.
A third aspect of the embodiments of the present application provides an apparatus for issuing a task, including:
the receiving module is used for receiving the patrol content input by the user, generating a patrol task according to the patrol content, and the patrol task corresponds to the first identity identifier;
the first acquisition module is used for acquiring a second identity sent by the robot if the robot in wired communication with the terminal equipment is detected;
the first sending module is used for sending the inspection content corresponding to the inspection task to the robot if the first identity identifier is consistent with the second identity identifier and the inspection task is detected to be a task to be issued;
and the storage module is used for storing the patrol task if the robot which is in wired communication with the terminal equipment is detected to be absent.
In a possible implementation manner of the third aspect, the first sending module is further configured to:
acquiring a synchronous identifier corresponding to the inspection task;
and if the synchronous identifier is the first identifier, determining that the inspection task is a task to be issued.
In a possible implementation manner of the third aspect, the first sending module is further configured to:
and if receiving the information of successful reception sent by the robot, updating the synchronous identifier to a second identifier.
In a possible implementation manner of the third aspect, the inspection content includes inspection parameters and inspection time information, and the inspection parameters include: patrol position, patrol object and shooting parameters.
In a possible implementation manner of the third aspect, the device for issuing a task further includes a determining module, where the determining module is configured to determine a task type of the inspection task;
correspondingly, the storage module is specifically configured to:
and if the fact that the robot in wired communication with the terminal equipment does not exist is detected, and the task type is the first task type, storing the inspection task.
A fourth aspect of the present application provides an apparatus for issuing a task, including:
the second sending module is used for sending a second identity mark of the robot to the terminal equipment after the wired communication is established with the terminal equipment;
the second acquisition module is used for acquiring the patrol content corresponding to the patrol task, which is sent by the terminal equipment, wherein the patrol task is a task to be issued, the patrol task corresponds to a first identity, and the first identity is consistent with the second identity.
In a possible implementation manner of the fourth aspect, the second obtaining module is further configured to:
and planning a patrol path according to the patrol content.
A fifth aspect of the embodiments of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the method for issuing tasks according to the first aspect described above when executing the computer program.
A sixth aspect of the embodiments of the present application provides a robot, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the method for issuing tasks according to the second aspect.
A seventh aspect of the embodiments of the present application provides a computer readable storage medium storing a computer program, which when executed by a processor implements a method for issuing a task as described in the first aspect or a method for issuing a task as described in the second aspect.
A fifth aspect of the embodiments of the present application provides a computer program product, which when run on a terminal device, causes the terminal device to perform the method for issuing a task described in the first aspect or the method for issuing a task described in the second aspect.
Compared with the prior art, the embodiment of the application has the beneficial effects that: after the inspection content input by the user is received, the terminal equipment generates an inspection task according to the inspection content input by the user, and ensures that the inspection task corresponds to the first identity. Then, if the terminal equipment detects that the robot in wired communication with the terminal equipment exists, acquiring a second identity of the robot, and if the terminal equipment judges that the first identity is consistent with the second identity, detecting that the patrol task is a task to be issued, and sending patrol content corresponding to the patrol task to the robot; and if the robot which is in wired communication with the terminal equipment is detected to be absent, storing the inspection task. Therefore, whether or not a robot in wired communication with the terminal device exists, the user can generate a patrol task to be sent to the robot through the terminal device, namely, the user can issue the task to the robot at any time. In addition, if the inspection task is generated when the robot does not have wired communication with the terminal equipment, once the robot corresponding to the inspection task is detected to have wired communication with the terminal equipment, the terminal equipment can issue the inspection task, so that the time for the robot to wait for the inspection task to generate is reduced, the robot can respond to the inspection task faster, and the user experience is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments or the prior art will be briefly described below.
Fig. 1 is a architecture diagram of a task issuing system to which a task issuing method provided in an embodiment of the present application is applicable;
FIG. 2 is a block diagram of a system for issuing tasks provided by an embodiment of the present application;
FIG. 3 is a flow chart of a method for issuing tasks according to an embodiment of the present disclosure;
FIG. 4 is a flow chart of a method for issuing tasks according to another embodiment of the present application;
fig. 5 is a schematic diagram of a terminal device provided in an embodiment of the present application;
fig. 6 is a schematic view of a robot provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to illustrate the technical solutions described in the present application, the following description is made by specific examples.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
In addition, in the description of the present application, the terms "first," "second," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.
The following describes a method for issuing tasks provided in the embodiments of the present application.
As shown in fig. 1, fig. 1 is a architecture of a task issuing system, which is applicable to the task issuing method provided in the embodiment of the present application, and the system includes a terminal device 100 and a robot 200. The terminal device 100 and the robot 200 can perform wired communication.
The terminal device 100 may be a computing device such as a desktop computer, a notebook computer, a palm computer, and a cloud server.
As shown in fig. 2, the terminal device 100 includes a patrol task generating module 10, a patrol task synchronizing module 20, a first network communication module 30, and a first wired network connector 40, and the robot 200 includes a second wired network connector 50, a second network communication module 60, and a patrol task performing module 70.
The terminal device 100 stores a first database, where the first database includes inspection parameters, each set of inspection parameters corresponds to one inspection point, and the inspection parameters include position information of the inspection point, an inspection object at the inspection point, and a shooting parameter at the inspection point. The user selects the inspection parameters from the database and sets inspection time information, and the inspection task generating module 10 generates an inspection task according to the inspection parameters and the inspection time information, and stores the generated inspection task in the first database on the terminal device 100. The inspection task generating module 10 is further configured to obtain a first identity (such as a first identity input by a user, or the user selects the first identity from an existing identity list), and associate the inspection task with the first identity. Wherein the first identity is used to uniquely identify the robot.
The robot 200 is connected to the first wired network connector 40 of the terminal device 100 through the second wired network connector 50 at a preset time so as to be in wired communication with the terminal device 100. When the inspection task synchronization module 20 detects that the robot 200 is in wired communication with the terminal device 100, the second identity sent by the second network communication module 60 is acquired through the first network communication module 30. The inspection task synchronization module is further configured to verify whether the first identity identifier is consistent with the second identity identifier, detect whether an inspection task that needs to be synchronized to the robot 200 exists if the first identity identifier is consistent with the second identity identifier, and send inspection parameters and inspection time information corresponding to the inspection task to the second network communication module 60 through the first network communication module 30 if the inspection task that needs to be synchronized to the robot 200 exists. The second network communication module 60 is configured to store the received inspection parameters and inspection time information to a second database on the robot 200, and the inspection task execution module 70 is configured to execute an inspection task according to the inspection parameters and the inspection time information stored in the second database.
The following describes a method for issuing a task according to the embodiment of the present application according to the system for issuing a task shown in fig. 1 and fig. 2.
Fig. 3 shows an implementation flow of a method for issuing a task according to an embodiment of the present application, where a flow execution body of the embodiment may be a terminal device. The process is detailed as follows:
s101: and receiving the inspection content input by the user, and generating an inspection task according to the inspection content, wherein the inspection task corresponds to the first identity identifier.
The inspection content comprises inspection parameters and inspection time information, and the inspection parameters comprise inspection positions, inspection objects and shooting parameters. The inspection position is coordinate information of an inspection point, for example, coordinates of the inspection point on a preset map. The inspection object is an action required to be executed by the robot at an inspection point, such as LED indicator lamp shooting, door handle identification, cabinet temperature identification and the like. The shooting parameters comprise an identification of a shooting camera, the height of a lifting rod where the camera used for shooting is located, a shooting position, a scaling factor during shooting, a camera focal length, an up-down pitch angle, a left-right deflection angle and the like of a cradle head. The inspection parameters can be stored in the first database of the terminal equipment in advance, or set by a user, and each group of inspection parameters corresponds to one inspection point.
The inspection time information comprises the time of single execution of inspection tasks and inspection types, and the inspection types can be single inspection, daily cycle inspection, weekly cycle inspection and the like.
After the terminal equipment acquires the inspection parameters and the inspection time information, an inspection task is generated, and the generated inspection task is stored in a first database and is associated with the acquired first identity. The first identity identifier may be a MAC address or serial number information of the robot, etc., and is used for uniquely identifying the robot.
In one possible implementation manner, after the terminal device generates the inspection task, a synchronization identifier is added to the inspection task, where the synchronization identifier is used to identify whether the inspection task has been issued to the robot. The initial value of the synchronization identifier is a first identifier, such as false.
S102: and if the robot in wired communication with the terminal equipment is detected, acquiring a second identity sent by the robot.
The second identity identifier may be a MAC address or serial number information of the robot, and the second identity identifier is used for uniquely identifying the robot.
The terminal equipment can acquire the second identity through a wired communication mode, and can acquire the second identity through a wireless communication mode.
S103: and if the first identity identifier is consistent with the second identity identifier and the inspection task is detected to be a task to be issued, sending inspection content corresponding to the inspection task to the robot.
Specifically, when the terminal equipment detects that the first identity identifier is consistent with the second identity identifier, acquiring all the inspection tasks corresponding to the first identity identifier and the synchronous identifiers corresponding to the inspection tasks, and judging whether the inspection tasks are issued to the robot according to the synchronous identifiers. If the synchronous identifier is the first synchronous identifier, the fact that the inspection task corresponding to the synchronous identifier is not issued to the robot is indicated, the inspection task is used as a task to be issued, and inspection content corresponding to the task to be issued is sent to the robot.
After sending the patrol content corresponding to the patrol task, if receiving a message of successful receipt sent by the robot, the terminal device indicates that the patrol task is successfully issued, and updates the synchronous identifier corresponding to the patrol task which is successfully sent to a second identifier, for example true, so that the patrol task is identified as an issued task, and the robot is prevented from repeatedly issuing the patrol task when the robot is in wired communication with the terminal device again.
Correspondingly, if the terminal equipment detects that the first identity identifier is inconsistent with the second identity identifier, or the inspection task is determined to be the issued task according to the synchronous identifier, the inspection task is stored in the first database, and the robot waits for establishing wired communication with the terminal equipment.
S104: and if the robot which is in wired communication with the terminal equipment is detected to be absent, storing the inspection task.
Specifically, after the terminal device generates the inspection task according to the inspection content input by the user, if no robot in wired communication with the terminal device exists, the terminal device stores the inspection task in the first database, and when the robot corresponding to the inspection task is in wired communication with the terminal device, the terminal device can issue the inspection task to the robot.
In the embodiment of the application, after receiving the inspection content input by the user, the terminal device generates the inspection task according to the inspection content input by the user, and ensures that the inspection task corresponds to the first identity identifier. Then, if the terminal equipment detects that the robot in wired communication with the terminal equipment exists, acquiring a second identity of the robot, and if the terminal equipment judges that the first identity is consistent with the second identity, detecting that the patrol task is a task to be issued, and sending patrol content corresponding to the patrol task to the robot; and if the robot which is in wired communication with the terminal equipment is detected to be absent, storing the inspection task. Therefore, whether or not a robot in wired communication with the terminal device exists, the user can generate a patrol task to be sent to the robot through the terminal device, namely, the user can issue the task to the robot at any time. In addition, if the inspection task is generated when the robot does not have wired communication with the terminal equipment, once the robot corresponding to the inspection task is detected to have wired communication with the terminal equipment, the terminal equipment can issue the inspection task, so that the time for the robot to wait for the inspection task to generate is reduced, the robot can respond to the inspection task faster, and the user experience is improved.
In one possible implementation, before storing the inspection task, the terminal device determines the task type of the inspection task according to the inspection object or the inspection location. The task types comprise a first task type and a second task type, wherein the first task type is a task type with higher confidentiality, namely a task type which is required to be sent through a wired communication mode, and the second task type is a task type with lower confidentiality, namely a task type which is capable of being sent through a wireless communication mode. For example, if the terminal device detects that the inspection object corresponding to the inspection task is a preset inspection object or detects that the inspection position corresponding to the inspection task is a preset inspection position, it is determined that the task type of the inspection task is the first task type. After determining that the task type of the inspection task is the first task type, if no robot in wired communication with the terminal equipment exists, storing the current inspection task. Similarly, when the terminal device determines that the task type of the inspection task is the second task type, after the inspection task is generated, the inspection task can be sent to the corresponding robot in a wireless communication mode, so that the corresponding inspection task sending mode can be determined according to the task type, and the task issuing efficiency is improved.
Fig. 4 shows an implementation flow of a method for issuing a task according to another embodiment of the present application, where the flow execution body of the present embodiment may be a robot. The process is detailed as follows:
s201: after establishing wired communication with the terminal equipment, the second identity of the robot is sent to the terminal equipment.
Specifically, the robot establishes wired communication with the robot at a preset time, where the preset time may be a time when the robot performs a current task, or may be a preset time.
S202: and acquiring the patrol content which is sent by the terminal equipment and corresponds to the patrol task, wherein the patrol task is a task to be issued, the patrol task corresponds to a first identity, and the first identity is consistent with the second identity.
Specifically, a patrol task corresponding to the first identity is stored on the terminal equipment, after the robot sends the second identity to the terminal equipment, the terminal equipment sends patrol contents corresponding to the patrol task to the robot when detecting that the first identity is consistent with the second identity and the patrol task is a task to be issued, the robot stores the patrol contents in the second database, and the patrol task is executed according to the patrol contents.
In one possible implementation, the inspection content includes inspection parameters and inspection time information, and the inspection parameters include inspection positions, inspection objects and photographing parameters. And the robot plans the inspection path according to the inspection position and the inspection time information, and sequentially executes the inspection tasks according to the planned inspection path.
In the above embodiment, after the robot establishes wired communication with the terminal device, the terminal device sends the second identity of the robot to the terminal device, and the terminal device can issue the inspection task to the robot according to the second identity, and the inspection task stored on the terminal device can be stored by the user at any time, so that the user can issue the task to the robot at any time, the time for waiting for the robot is reduced, and the user experience is improved.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not limit the implementation process of the embodiment of the present application in any way.
Based on the same inventive concept, the application also provides a terminal device. Fig. 5 is a schematic diagram of a terminal device provided in an embodiment of the present application. As shown in fig. 5, the terminal device of this embodiment includes: a processor 11, a memory 12, and a computer program 13 stored in the memory 12 and executable on the processor 11. The steps of the above-described method embodiment of issuing tasks performed on the terminal device, such as steps S101 to S104 shown in fig. 3, are implemented when the processor 11 executes the computer program 13.
By way of example, the computer program 13 may be divided into one or more modules/units, which are stored in the memory 12 and executed by the processor 11 to complete the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions for describing the execution of the computer program 13 in the terminal device.
It will be appreciated by those skilled in the art that fig. 5 is merely an example of a terminal device and is not meant to be limiting, and that more or fewer components than shown may be included, or certain components may be combined, or different components may be included, for example, the terminal device may also include input and output devices, network access devices, buses, etc.
The processor 11 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 12 may be an internal storage unit of the terminal device, such as a hard disk or a memory of the terminal device. The memory 12 may also be an external storage device of the terminal device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the terminal device. Further, the memory 12 may also include both an internal storage unit and an external storage device of the terminal device. The memory 12 is used for storing the computer program as well as other programs and data required by the terminal device. The memory 12 may also be used to temporarily store data that has been output or is to be output.
The application also provides a robot. Fig. 6 is a schematic view of a robot provided in an embodiment of the present application. As shown in fig. 6, the robot of this embodiment includes: a processor 21, a memory 22 and a computer program 23 stored in said memory 22 and executable on said processor 21. The steps of the method embodiment of the task issuing performed on the robot described above, such as steps S201 to S202 shown in fig. 4, are implemented when the processor 21 executes the computer program 23.
The computer program 23 may, for example, be split into one or more modules/units, which are stored in the memory 22 and executed by the processor 21 to complete the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing a specific function for describing the execution of the computer program 23 in the robot.
It will be appreciated by those skilled in the art that fig. 6 is merely an example of a robot and is not limiting of the robot, and may include more or fewer components than shown, or may combine certain components, or different components, e.g., the robot may also include input and output devices, network access devices, buses, etc.
The processor 21 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 22 may be an internal storage unit of the robot, such as a hard disk or a memory of the robot. The memory 22 may also be an external storage device of the robot, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card) or the like, which are provided on the robot. Further, the memory 22 may also include both an internal memory unit and an external memory device of the robot. The memory 22 is used for storing the computer program as well as other programs and data required by the robot. The memory 22 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other manners. For example, the apparatus/terminal device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each method embodiment described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims (8)

CN202010763563.1A2020-07-312020-07-31Method for issuing task, terminal equipment, robot and storage mediumActiveCN112070456B (en)

Priority Applications (1)

Application NumberPriority DateFiling DateTitle
CN202010763563.1ACN112070456B (en)2020-07-312020-07-31Method for issuing task, terminal equipment, robot and storage medium

Applications Claiming Priority (1)

Application NumberPriority DateFiling DateTitle
CN202010763563.1ACN112070456B (en)2020-07-312020-07-31Method for issuing task, terminal equipment, robot and storage medium

Publications (2)

Publication NumberPublication Date
CN112070456A CN112070456A (en)2020-12-11
CN112070456Btrue CN112070456B (en)2023-12-29

Family

ID=73656673

Family Applications (1)

Application NumberTitlePriority DateFiling Date
CN202010763563.1AActiveCN112070456B (en)2020-07-312020-07-31Method for issuing task, terminal equipment, robot and storage medium

Country Status (1)

CountryLink
CN (1)CN112070456B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
CN112835694A (en)*2021-01-252021-05-25广东建邦计算机软件股份有限公司 Inspection task processing method, device, computer equipment and storage medium
CN113762779A (en)*2021-09-092021-12-07苏州光格科技股份有限公司Data processing method and device for determining inspection task of track robot and robot
CN116107829A (en)*2022-01-242023-05-12漳州立达信光电子科技有限公司 Detection method, device, detection equipment and storage medium of equipment running state
CN117687655B (en)*2023-08-282024-07-23广州信邦智能装备股份有限公司Patrol robot upgrading management method, patrol robot and medium program

Citations (10)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
CN102280826A (en)*2011-07-302011-12-14山东鲁能智能技术有限公司Intelligent robot inspection system and intelligent robot inspection method for transformer station
CN103325153A (en)*2013-06-172013-09-25深圳市共济科技有限公司 A kind of inspection method and inspection system
CN108320347A (en)*2018-01-082018-07-24浙江立石机器人技术有限公司A kind of robot method for inspecting
CN108416866A (en)*2017-02-092018-08-17中国移动通信有限公司研究院 Method and device for processing inspection tasks
CN108737550A (en)*2018-05-252018-11-02山东鲁能智能技术有限公司A kind of robot interface's device and robot based on robot centralized control system
CN109543992A (en)*2018-11-192019-03-29华能国际电力股份有限公司上安电厂Intelligent polling method, device, intelligent terminal and server
CN109818416A (en)*2017-11-222019-05-28杨娜A kind of multi-functional transformer station intelligent robot inspection system
CN109962836A (en)*2017-12-252019-07-02深圳市优必选科技有限公司 A robot control method, server and robot
CN110196594A (en)*2019-05-242019-09-03北京海益同展信息科技有限公司Computer room inspection control method, device, equipment and storage medium
CN110794837A (en)*2019-10-312020-02-14上海玖道信息科技股份有限公司Intelligent inspection equipment system based on robot

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
CN107291078B (en)*2017-06-062019-11-08歌尔股份有限公司A kind of dispatching method and device of service robot

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
CN102280826A (en)*2011-07-302011-12-14山东鲁能智能技术有限公司Intelligent robot inspection system and intelligent robot inspection method for transformer station
CN103325153A (en)*2013-06-172013-09-25深圳市共济科技有限公司 A kind of inspection method and inspection system
CN108416866A (en)*2017-02-092018-08-17中国移动通信有限公司研究院 Method and device for processing inspection tasks
CN109818416A (en)*2017-11-222019-05-28杨娜A kind of multi-functional transformer station intelligent robot inspection system
CN109962836A (en)*2017-12-252019-07-02深圳市优必选科技有限公司 A robot control method, server and robot
CN108320347A (en)*2018-01-082018-07-24浙江立石机器人技术有限公司A kind of robot method for inspecting
CN108737550A (en)*2018-05-252018-11-02山东鲁能智能技术有限公司A kind of robot interface's device and robot based on robot centralized control system
CN109543992A (en)*2018-11-192019-03-29华能国际电力股份有限公司上安电厂Intelligent polling method, device, intelligent terminal and server
CN110196594A (en)*2019-05-242019-09-03北京海益同展信息科技有限公司Computer room inspection control method, device, equipment and storage medium
CN110794837A (en)*2019-10-312020-02-14上海玖道信息科技股份有限公司Intelligent inspection equipment system based on robot

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
变电站智能机器人巡检任务规划;钱金菊;王柯;王锐;彭向阳;;广东电力(02);全文*
智能机器人巡检系统在综合管廊中的应用研究;谢军;吴晓维;汪胜;;电气自动化(02);全文*

Also Published As

Publication numberPublication date
CN112070456A (en)2020-12-11

Similar Documents

PublicationPublication DateTitle
CN112070456B (en)Method for issuing task, terminal equipment, robot and storage medium
CN110856126B (en)Information reporting and receiving method, terminal equipment and storage medium
CN111221742B (en)Test case updating method and device, storage medium and server
CN110633977A (en)Payment exception processing method and device and terminal equipment
CN110875850A (en)Firmware upgrading method and system, readable storage medium and terminal equipment
CN112996020B (en)Bluetooth-based automatic test method and device and Bluetooth test terminal
US10614621B2 (en)Method and apparatus for presenting information
CN110611876A (en)Indoor asset management method, device and system
CN111737564A (en)Information query method, device, equipment and medium
CN110516471A (en)Product promotion method and relevant device based on information security
KR20220068913A (en)Automated shopping cart
CN110290166A (en)Across company-data exchange method, system, device and readable storage medium storing program for executing
CN115457656A (en) Method, device, equipment and storage medium for determining operation duration
CN110825756A (en)Data synchronization method, device, storage medium and equipment
CN111770208A (en)Control method and device for Internet of things equipment
CN112543121B (en)Multi-device group control method, electronic device and computer readable storage medium
CN112508467B (en)Method and device for order delivery
CN112306041A (en)Vehicle configuration information writing method and device and electronic equipment
CN113886302B (en) Method, device, terminal device and storage medium for obtaining serial port number of application device
CN112751799A (en)Verification method and device based on picture verification code
CN110765392A (en)Data loading method and device, storage medium and terminal
CN119484637A (en) A data acquisition system, method and related equipment
CN110212258B (en)BMS engineering installation configuration method and device and terminal equipment
CN116841579A (en)Optical storage and charging equipment upgrading method and system, electronic equipment and readable storage medium
CN104812066A (en)Method and device for identifying and positioning faults and server

Legal Events

DateCodeTitleDescription
PB01Publication
PB01Publication
SE01Entry into force of request for substantive examination
SE01Entry into force of request for substantive examination
GR01Patent grant
GR01Patent grant

[8]ページ先頭

©2009-2025 Movatter.jp