Robot lifecycle management method, device, terminal and storage medium

Abstract

Embodiments of the present invention disclose a robot lifecycle management method, device, terminal, and storage medium. This method, applied to a cloud server, includes: obtaining tracking data reported by a robot when it triggers a preset tracking event; determining the robot's current state based on the tracking data; and updating the robot's lifecycle data based on the current state. This allows the cloud server to effectively track the robot's entire lifecycle, monitor and protect the robot's lifecycle, and proactively provide timely services to users, creating a virtuous cycle.

Description

Technical Field

[0001] The present invention relates to the field of robots, and in particular to a robot lifecycle management method, device, terminal and storage medium. Background Art

[0002] In existing technologies, the monitoring of the robot's life cycle is mainly carried out during production. After the robot is sold to the user, there is no quality and status monitoring of the robot in use. As a result, the manufacturer cannot quickly locate the problem when the robot has a problem, nor can it respond to the user in a timely and rapid manner. Summary of the Invention

[0003] In view of this, the present application provides a robot lifecycle management method, which is applied to a cloud server, including:

[0004] Get the tracking data reported when the robot triggers the preset tracking event;

[0005] Determine the current state of the robot according to the tracking data;

[0006] The life cycle data of the robot is updated based on the current state.

[0007] Furthermore, the buried point data includes the triggered buried point event and the buried point data when the buried point event is triggered;

[0008] Determining the current state of the robot according to the tracking data includes:

[0009] Determine whether the triggered tracking event has a preceding tracking event.

[0010] If the result is yes, then determine whether the status of the preceding tracking event is normal.

[0011] If the judgment result is normal, the current state of the robot is determined based on the buried point data.

[0012] Furthermore, it also includes: if the status of the previous embedded point event is abnormal, the preset warning process is executed.

[0013] Furthermore, when the preceding buried point event status fails to pass, the current status is judged to be illegal, and the current status is changed to the preceding buried point event status.

[0014] Furthermore, the present application also provides a robot lifecycle management method, which is applied to a robot and includes:

[0015] If the robot triggers a preset tracking event, it obtains the tracking data related to the tracking event;

[0016] Uploading the tracking data to the cloud server;

[0017] Obtaining status data fed back by the cloud server;

[0018] The life cycle data of the robot is updated based on the status data.

[0019] Furthermore, the lifecycle data includes all the buried events;

[0020] The updating of the life cycle data of the robot based on the status data includes:

[0021] The triggered tracking event is determined based on the current life cycle data. If the cloud server determines that the tracking event is normal, the tracking event is deleted from the life cycle data.

[0022] Furthermore, the present application provides a robot lifecycle management device, which is applied to a cloud server and includes:

[0023] The acquisition module is used to obtain the tracking data reported when the robot triggers the preset tracking event;

[0024] An analysis module, configured to determine the current state of the robot based on the tracking data;

[0025] An updating module is used to update the life cycle data of the robot based on the current state.

[0026] Furthermore, an embodiment of the present application also provides a robot lifecycle management device, applied to a robot, comprising:

[0027] The information acquisition module is used to obtain the tracking data related to the tracking event if the robot triggers the preset tracking event;

[0028] A communication module is used to upload the tracking data to the cloud server and obtain the status data fed back by the cloud server;

[0029] An updating module is used to update the life cycle data of the robot based on the status data.

[0030] Furthermore, an embodiment of the present application also provides a terminal device, including a processor and a memory, wherein the memory stores a computer program, and when the computer program runs on the processor, it executes the robot lifecycle management method described in the above embodiment.

[0031] Furthermore, an embodiment of the present application also provides a readable storage medium storing a computer program, which executes the robot lifecycle management method described in the above embodiment when running on a processor.

[0032] The present invention provides a robot lifecycle management method, which is applied to a cloud server. The method obtains tracking data reported by a robot when it triggers a preset tracking event; determines the robot's current state based on the tracking data; and updates the robot's lifecycle data based on the current state. This allows the cloud server to effectively track and monitor the robot's lifecycle, protect it, and proactively provide timely services to users, creating a virtuous cycle. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solution of the present invention, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only illustrate certain embodiments of the present invention and should not be regarded as limiting the scope of protection of the present invention. In each of the drawings, similar components are numbered similarly.

[0034] Figure 1 A schematic diagram of a robot lifecycle management method according to an embodiment of the present application is shown;

[0035] Figure 2 A schematic diagram of a process flow of another robot lifecycle management method according to an embodiment of the present application is shown;

[0036] Figure 3 A schematic diagram of a robot lifecycle management device according to an embodiment of the present application is shown;

[0037] Figure 4 A schematic diagram of another robot lifecycle management device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0038] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments.

[0039] The components of the embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the figures is not intended to limit the scope of the claimed invention, but rather merely represents selected embodiments of the present invention. All other embodiments derived by those skilled in the art based on the embodiments of the present invention without inventive effort are intended to be within the scope of protection of the present invention.

[0040] Hereinafter, the terms "including", "having" and their cognates, which may be used in various embodiments of the present invention, are intended only to indicate specific features, numbers, steps, operations, elements, components or combinations of the foregoing items, and should not be understood as first excluding the existence of one or more other features, numbers, steps, operations, elements, components or combinations of the foregoing items or the possibility of adding one or more features, numbers, steps, operations, elements, components or combinations of the foregoing items.

[0041] Furthermore, the terms “first,” “second,” “third,” etc., are merely used for distinguishing descriptions and are not to be understood as indicating or implying relative importance.

[0042] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by those skilled in the art to which the various embodiments of the present invention pertain. The terms (such as those defined in generally used dictionaries) will be interpreted as having the same meaning as in the context of the relevant technical field and will not be interpreted as having an idealized meaning or an overly formal meaning unless clearly defined in the various embodiments of the present invention.

[0043] Next, the robot lifecycle management method of the present application is explained with specific embodiments.

[0044] Example 1

[0045] This embodiment is a robot life cycle management method executed by a cloud server, which includes the following steps: Figure 1 The flowchart shown.

[0046] Step S100, obtaining the tracking data reported by the robot when triggering the preset tracking event.

[0047] A robot's life cycle begins when it is assembled and ready to run. This life cycle consists of a series of events, such as testing, walking, raising hands, dancing, writing, and other specific actions. Some of these events can reflect the current state of the robot and whether the current life cycle of the robot is legal. These events are preset tracking events. When the robot triggers these tracking events, it reports the data generated by executing these tracking events to the cloud server.

[0048] Specifically, these preset tracking events include one or more of testing, activation, self-test, power on, power off, daily behavior, firmware upgrade, accessory replacement, repair and return.

[0049] Step S200, determining the current state of the robot based on the tracking data.

[0050] When the cloud server obtains the data generated when executing these tracking events, it can analyze this data to determine the current state of the robot. The status is determined by determining the life cycle to which the current tracking event belongs, whether the current life cycle is legal, and whether the robot reflected by the data is normal. It will first determine whether there is a preceding tracking event for the triggered tracking event. The so-called preceding tracking event refers to a definition based on the order of life. Specifically, the life cycle of a robot includes, in order: testing, shipping, activation, daily use, repair and return, and termination. Testing is the performance of the robot before it leaves the factory. There are no preceding events for testing. When the test is completed and the robot needs to be shipped, the cloud will detect whether the test has been covered during the test step. If so, the robot can be shipped; otherwise, it cannot be shipped.

[0051] For tracking events in the activation lifecycle, the preceding event is the outbound event. If the current action is to activate the robot, but no outbound action has been performed, the preceding outbound action is abnormal. This indicates that the robot may have been stolen and not legally acquired by the user. Therefore, the current activation behavior is considered abnormal, the activation operation is rejected, and the preset warning process is initiated. The current state is changed to the preceding tracking event state.

[0052] When the robot is in the life cycle of daily use, it means that it has entered the user's home and started to accept the user's commands to perform corresponding actions. At this time, it will feedback the execution data when performing operations such as dancing, telling stories, cleaning, etc., and then feed these execution data back to the cloud. The cloud uses the data to determine whether the robot is operating normally. If it is normal, it will continue to cycle the life cycle of daily use. If one is found, it will enter the repair and return, or even terminate the state.

[0053] Step S300: updating the life cycle data of the robot based on the current state.

[0054] If it is judged that its previous behavior is normal, such as the outbound behavior is normal, it means that it is outbound normally, so the activation operation can be performed. After the cloud executes the activation of the robot, the current robot's life cycle data is updated in the cloud, so that the robot can execute the events after activation, which belong to the daily use life cycle.

[0055] If during the life cycle of daily use, the feedback data is found to be abnormal, which means that the robot has an abnormality, it will actively warn the user. For example, if it is a software abnormality, the user will be reminded that updates and software repair operations are required, and the user will be guided to repair it. If it is a hardware abnormality, the user will be reminded that they need to seek after-sales service.

[0056] Furthermore, updating lifecycle data also updates whether preset tracking events have been triggered. As mentioned in the previous example, the lifecycle is linear, and each event is essentially preceded by a pre-event. These pre-events are irreversible. For example, if a product has been shipped, activated, and sold to a user, it is impossible to activate or ship it again, nor is it possible for the customer to perform testing operations. Therefore, these pre-events that have been triggered are marked as triggered, and the status of the triggered event is updated. The updated data is returned to the robot, so the robot does not return data from the triggered event.

[0057] Example 2

[0058] This embodiment is a robot life cycle management method executed by a robot, which includes the following steps: Figure 2 The flowchart shown.

[0059] Step S400: If the robot triggers a preset tracking event, the tracking data related to the tracking event is obtained;

[0060] When the robot receives the user's instruction to execute the tracking event, it automatically records the tracking data related to the tracking event. The tracking data can be logs or other forms of similar poems.

[0061] Step S500: Upload the tracking data to the cloud server and obtain status data fed back by the cloud server.

[0062] Upload the data to the cloud server, let the cloud server judge the status of the robot, and then the cloud server will feedback the status data of the robot.

[0063] Step S600: updating the life cycle data of the robot based on the status data.

[0064] Based on the status data fed back from the cloud, the robot's own life cycle data is updated. In addition to the current life cycle and robot status, the life cycle data also includes preset tracking point data.

[0065] When the life cycle of the robot is executed step by step from the test, the tracking events in the previous life cycle will not be executed again in theory. For example, if it has reached the life cycle of daily use, it is impossible to activate or ship it out of the warehouse, or even some tracking events in the testing phase. Therefore, there is no need to upload data for these events, and they can be directly classified as exceptions locally. Therefore, as the life cycle of the robot progresses, the tracking events can be updated in real time. For example, by judging whether the triggered tracking events are normal, if they are normal, it means that the life cycle will continue to advance, and the tracking events can be deleted from the life cycle data, or by judging the current valid life cycle, the tracking events before the life cycle are classified as invalid events, and the tracking events in the current life cycle and subsequent life cycles are classified as valid events, so as to upload tracking data in a targeted manner.

[0066] The present application also provides a robot life cycle management device, which is applied to a cloud server, such as Figure 3 As shown, it includes: an acquisition module 10, an analysis module 20 and an update module 30.

[0067] The acquisition module 10 is used to obtain the tracking data reported when the robot triggers a preset tracking event.

[0068] The analysis module 20 is used to determine the current state of the robot based on the buried data.

[0069] The updating module 30 is configured to update the life cycle data of the robot based on the current state.

[0070] Furthermore, the embodiment of the present application also provides a robot life cycle management device, which is applied to a robot and includes an information acquisition module 40, a communication module 50 and an update module 60. Figure 4 shown.

[0071] The information acquisition module 40 is used to obtain the tracking data related to the tracking event if the robot triggers a preset tracking event;

[0072] The communication module 50 is used to upload the tracking data to the cloud server and obtain the status data fed back by the cloud server;

[0073] The updating module 60 is configured to update the life cycle data of the robot based on the status data.

[0074] Furthermore, an embodiment of the present application also provides a terminal device, including a processor and a memory, wherein the memory stores a computer program, and when the computer program runs on the processor, it executes the robot lifecycle management method described in the above embodiment.

[0075] Furthermore, an embodiment of the present application also provides a readable storage medium storing a computer program, which executes the robot lifecycle management method described in the above embodiment when running on a processor.

[0076] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and structure diagrams in the accompanying drawings show the possible architectures, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and the module, program segment or a part of the code contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in an alternative implementation, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the structure diagram and / or flowchart, and the combination of boxes in the structure diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or can be implemented using a combination of dedicated hardware and computer instructions.

[0077] In addition, the functional modules or units in the various embodiments of the present invention may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0078] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a smart phone, a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0079] The above description is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed by the present invention, which should be covered by the scope of protection of the present invention.

Claims

1. A robot life cycle management method, characterized in that: Applied to cloud servers, including: Get the tracking data reported when the robot triggers the preset tracking event; Determine the current state of the robot according to the tracking data; The life cycle data of the robot is updated based on the current state, including: determining a triggered buried event based on the current life cycle data, and if the buried event is normal, deleting the buried event from the life cycle data; the buried data includes the triggered buried event and the buried data when the buried event is triggered; The lifecycle data includes all the embedded events; Determining the current state of the robot according to the tracking data includes: Determine whether the triggered tracking event has a preceding tracking event. If the result is yes, then determine whether the status of the preceding tracking event is normal. If the status of the preceding tracking event is determined to be normal, the current status of the robot is determined based on the tracking data.

2. The method according to claim 1, wherein Also includes: If the status of the preceding tracking event is abnormal, the preset warning process will be executed.

3. The robot life cycle management method according to claim 2, characterized in that: When the preceding embedding event status fails, the current status is determined to be illegal, and the current status is changed to the preceding embedding event status.

4. A robot life cycle management method, characterized in that: Applications in robots include: If the robot triggers a preset tracking event, it obtains the tracking data related to the tracking event; Upload the tracking data to the cloud server and obtain the status data fed back by the cloud server; Based on the status data, updating the life cycle data of the robot; The lifecycle data includes all the embedded events; The updating of the life cycle data of the robot based on the status data includes: The triggered tracking event is determined based on the current life cycle data. If the cloud server determines that the tracking event is normal, the tracking event is deleted from the life cycle data.

5. A robot life cycle management device, characterized in that: Applied to cloud servers, including: The acquisition module is used to obtain the tracking data reported when the robot triggers the preset tracking event; An analysis module, configured to determine the current state of the robot based on the tracking data; An updating module, configured to update the life cycle data of the robot based on the current state; The lifecycle data includes all the embedded events; The updating of the life cycle data of the robot based on the current state includes: Determine a triggered tracking event based on the current lifecycle data, and if the tracking event is normal, delete the tracking event from the lifecycle data; The buried point data includes the triggered buried point event and the buried point data when the buried point event is triggered; Determining the current state of the robot according to the tracking data includes: Determine whether the triggered tracking event has a preceding tracking event. If the result is yes, then determine whether the status of the preceding tracking event is normal. If the judgment result is normal, the current state of the robot is determined based on the buried point data.

6. A robot life cycle management device, characterized in that: Applications in robots include: The information acquisition module is used to obtain the tracking data related to the tracking event if the robot triggers the preset tracking event; A communication module is used to upload the tracking data to the cloud server and obtain the status data fed back by the cloud server; An updating module, configured to update the life cycle data of the robot based on the status data; The lifecycle data includes all the embedded events; The updating of the life cycle data of the robot based on the status data includes: The triggered tracking event is determined based on the current life cycle data. If the cloud server determines that the tracking event is normal, the tracking event is deleted from the life cycle data.

7. A terminal device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a computer program, and when the computer program is run on the processor, the method for managing the robot life cycle as claimed in any one of claims 1 to 3 or claim 4 is executed.

8. A readable storage medium, characterized in that: The device stores a computer program, which, when running on a processor, executes the robot lifecycle management method described in any one of claims 1 to 3 or claim 4.

Images