Operation and maintenance system, method and device and electronic equipment

Through the monitoring end, network proxy end and cloud platform of the operation and maintenance system, rapid automated processing and continuous monitoring of faults on the robot control end are realized, the problem of inefficient fault handling is solved, and the stability of industrial production is improved.

CN119057780AActive Publication Date: 2024-12-03HANGZHOU HIKROBOT TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202411238731.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-04
Publication Date
2024-12-03
Estimated Expiration
2044-09-04

AI Technical Summary

Technical Problem

The robot control terminal fault processing efficiency is low, resulting in delayed fault processing and affecting the stability of industrial production.

Method used

A kind of operation and maintenance system is designed, including a monitoring terminal, a network proxy terminal and a cloud platform. The monitoring terminal obtains operation and maintenance data and sends it to the cloud platform through the network proxy terminal. The cloud platform generates fault processing instructions and returns them to the robot control terminal for fault processing. , and provide upgrade files to improve system stability.

Benefits of technology

It realizes rapid and automated processing of faults on the robot control side, improves fault handling efficiency, and continuously monitors to prevent fault recurrence, improving the stability of industrial production.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119057780A_ABST
    Figure CN119057780A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides an operation and maintenance system, method and device and electronic equipment. The operation and maintenance system comprises a monitoring end, a network agent end and a cloud platform. The monitoring end is used for acquiring operation and maintenance data of a to-be-monitored robot control end and sending the operation and maintenance data to the cloud platform through the network agent end when it is determined that the robot control end is abnormal based on the operation and maintenance data; and the cloud platform is used for generating a fault processing instruction for performing fault processing on the robot control end under the condition of determining a fault of the robot control end based on the received operation and maintenance data, and sending the fault processing instruction to the robot control end through the network agent end, so that the robot control end performs fault processing according to the fault processing instruction. According to the scheme, the fault processing efficiency of the robot control end can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of robotics technology, and in particular to an operation and maintenance system, method, device and electronic equipment. Background Art

[0002] At present, in industrial production scenarios, robot systems can be used to replace manual labor in factories to perform tasks such as handling. The robot system can include multiple robots and robot control terminals; among them, the robot control terminal can be deployed in the local computer room of the factory to schedule the robot.

[0003] When a fault occurs at the robot control end, the operation and maintenance personnel need to rush to the site to troubleshoot the fault and collect information, and then feed back the collected information to the R&D personnel so that the R&D personnel can determine how to handle the fault. The R&D personnel will then feed back the fault handling method to the operation and maintenance personnel for on-site processing. It can be seen that the information transmission and processing operations in the process of troubleshooting the robot control end are relatively cumbersome. Often, the fault will not be handled until it has caused serious negative impacts, and the fault handling process will also interfere with the continued stable operation of industrial production. Therefore, the efficiency of fault handling is relatively low. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide an operation and maintenance system, method, device and electronic device to solve the problem of low efficiency of fault handling at the robot control end. The specific technical solution is as follows:

[0005] The embodiment of the present application first provides an operation and maintenance system, which includes: a monitoring terminal, a network agent terminal and a cloud platform; wherein:

[0006] The monitoring end is used to obtain operation and maintenance data of the robot control end to be monitored, and when it is determined that the robot control end is abnormal based on the operation and maintenance data, the monitoring end sends the operation and maintenance data to the cloud platform through the network agent end; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server;

[0007] The cloud platform is used to generate a fault handling instruction for handling the robot control end when it is determined that the robot control end has a fault based on the received operation and maintenance data, and send the fault handling instruction to the robot control end through the network agent end, so that the robot control end performs fault handling according to the fault handling instruction.

[0008] Optionally, the cloud platform is specifically used to generate a fault handling instruction for handling the first specified type of fault when it is determined that the fault of the robot control terminal belongs to the first specified type;

[0009] The cloud platform is further configured to, when it is determined that the fault of the robot control terminal does not belong to the first specified type, obtain reference data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal, and send the reference data to the operation and maintenance client, so that the operation and maintenance personnel can generate an upgrade file for processing the fault based on the reference data; and after receiving the upgrade file, send the upgrade file to the monitoring terminal through the network agent terminal;

[0010] The monitoring end is further used to receive the upgrade file and send the upgrade file to the robot control end, so that the robot control end is upgraded based on the upgrade file.

[0011] Optionally, the robot control terminal is upgraded in a rolling manner.

[0012] Optionally, the cloud platform is further used to receive robot operation status data uploaded by the robot to be monitored through the network agent;

[0013] When it is determined that the robot has failed based on the operation status data, a failure handling instruction for handling the failure of the robot is generated.

[0014] Optionally, the monitoring terminal is deployed in the server;

[0015] The monitoring end is also used to automatically shut down when it detects that the computing resources occupied by itself have reached a preset threshold;

[0016] Optionally, the system further includes: a monitoring management terminal, configured to perform at least one of the following steps:

[0017] When detecting that the monitoring terminal is shut down, restarting the monitoring terminal;

[0018] Receiving the program package of the monitoring terminal sent by the cloud platform through the network agent terminal to update the monitoring terminal deployed in the server;

[0019] The network agent receives the upgrade file for the robot control terminal sent by the cloud platform and sends it to the monitoring terminal, so that the monitoring terminal upgrades the robot control terminal based on the upgrade file.

[0020] Optionally, the monitoring end is further configured to, when determining that the robot control end is abnormal based on the operation and maintenance data, determine that the robot control end is abnormal before sending the operation and maintenance data to the cloud platform through the network agent end, for a plurality of operation status data at different times corresponding to the same operation state in the operation and maintenance data, if the plurality of operation status data meet a preset condition;

[0021] The preset conditions include at least one of the following:

[0022] The frequency of abnormalities indicated by the multiple operating status data is greater than a first threshold, the number of consecutive abnormalities indicated by the multiple operating status data is greater than a second threshold, and the duration of consecutive abnormalities indicated by the multiple operating status data is greater than a first duration.

[0023] Optionally, the network agent is deployed in a charging station of the robot.

[0024] The embodiment of the present application also provides an operation and maintenance method, which is applied to a monitoring end of an operation and maintenance system, wherein the operation and maintenance system further includes: a network agent end and a cloud platform; the method includes:

[0025] Acquire operation and maintenance data of the robot control terminal to be monitored; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server;

[0026] When it is determined that the robot control terminal is abnormal based on the operation and maintenance data, the operation and maintenance data is sent to the cloud platform through the network agent, so that the cloud platform determines that the robot control terminal is faulty based on the received operation and maintenance data; generates a fault handling instruction for handling the robot control terminal, and sends the fault handling instruction to the robot control terminal through the network agent, so that the robot control terminal performs fault handling according to the fault handling instruction.

[0027] Optionally, the method further comprises:

[0028] Receiving an upgrade file for processing the fault sent by the cloud platform; wherein the upgrade file is generated by an operation and maintenance personnel based on reference data; the reference data is data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal acquired by the cloud platform when it is determined that the fault of the robot control terminal does not belong to the first specified type;

[0029] The upgrade file is sent to the robot control end so that the robot control end is upgraded based on the upgrade file.

[0030] Optionally, the monitoring terminal is deployed in the server; the method further includes:

[0031] It will automatically shut down when it detects that the computing resources it occupies have reached the preset threshold.

[0032] Optionally, when the robot control terminal is determined to be abnormal through the operation and maintenance data, before sending the operation and maintenance data to the cloud platform through the network agent, the method further includes:

[0033] For a plurality of operation status data at different times corresponding to the same operation status in the operation and maintenance data, if the plurality of operation status data meet a preset condition, determining that the robot control terminal is abnormal;

[0034] Wherein, the preset condition includes at least one of the following:

[0035] The frequency of abnormalities indicated by the multiple operating status data is greater than a first threshold, the number of consecutive abnormalities indicated by the multiple operating status data is greater than a second threshold, and the duration of consecutive abnormalities indicated by the multiple operating status data is greater than a first duration.

[0036] The embodiment of the present application also provides an operation and maintenance method, which is applied to a cloud platform of an operation and maintenance system, wherein the operation and maintenance system further includes: a network agent terminal and a monitoring terminal; the method includes:

[0037] Receive operation and maintenance data sent by the monitoring end when determining that the robot control end is abnormal; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server; and the operation and maintenance data is used by the monitoring end to determine whether the robot control end is abnormal;

[0038] In the case where it is determined that the robot control end has a fault based on the operation and maintenance data, generating a fault handling instruction for handling the fault of the robot control end;

[0039] The fault handling instruction is sent to the robot control end through the network agent end, so that the robot control end performs fault handling according to the fault handling instruction.

[0040] Optionally, the generating of a fault handling instruction for handling a fault on the robot control terminal includes:

[0041] generating a fault handling instruction for handling the first specified type of fault;

[0042] The method further comprises:

[0043] When it is determined that the fault of the robot control terminal does not belong to the first specified type, obtaining reference data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal;

[0044] Sending to the operation and maintenance client so that the operation and maintenance personnel can generate an upgrade file for handling the fault based on the reference data;

[0045] After receiving the upgrade file, the upgrade file is sent to the monitoring end through the network agent end; so that the monitoring end receives the upgrade file and sends the upgrade file to the robot control end, so that the robot control end is upgraded based on the upgrade file.

[0046] Optionally, the method further comprises:

[0047] Receiving robot operation status data uploaded by the robot to be monitored through the network agent;

[0048] When it is determined that the robot has failed based on the operation status data, a failure handling instruction for handling the failure of the robot is generated.

[0049] The embodiment of the present application also provides an operation and maintenance device, which is applied to a monitoring end of an operation and maintenance system, wherein the operation and maintenance system further includes: a network agent end and a cloud platform; the device includes:

[0050] An operation and maintenance data acquisition module, used to acquire operation and maintenance data of the robot control terminal to be monitored; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server;

[0051] An operation and maintenance data sending module is used to send the operation and maintenance data to the cloud platform through the network agent when it is determined that the robot control terminal is abnormal based on the operation and maintenance data, so that the cloud platform can generate a fault handling instruction for handling the robot control terminal when the robot control terminal is faulty based on the received operation and maintenance data, and send the fault handling instruction to the robot control terminal through the network agent, so that the robot control terminal can handle the fault according to the fault handling instruction.

[0052] Optionally, the device further comprises:

[0053] An upgrade file receiving module, used for receiving an upgrade file for processing a fault sent by the cloud platform; wherein the upgrade file is generated by an operation and maintenance personnel based on reference data; the reference data is data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal acquired by the cloud platform when it is determined that the fault of the robot control terminal does not belong to the first specified type;

[0054] The upgrade file upgrade module is used to send the upgrade file to the robot control end so that the robot control end is upgraded based on the upgrade file.

[0055] Optionally, the monitoring terminal is deployed in the server; the device further includes:

[0056] The automatic shutdown module is used to automatically shut down when it detects that the computing resources occupied by itself have reached a preset threshold.

[0057] Optionally, the device further comprises:

[0058] The abnormality determination module is used for, when the operation and maintenance data is sent and the robot control terminal is determined to be abnormal through the operation and maintenance data, before sending the operation and maintenance data to the cloud platform through the network agent, the method further includes:

[0059] For a plurality of operation status data at different times corresponding to the same operation status in the operation and maintenance data, if the plurality of operation status data meet a preset condition, determining that the robot control terminal is abnormal;

[0060] Wherein, the preset condition includes at least one of the following:

[0061] The frequency of abnormalities indicated by the multiple operating status data is greater than a first threshold, the number of consecutive abnormalities indicated by the multiple operating status data is greater than a second threshold, and the duration of consecutive abnormalities indicated by the multiple operating status data is greater than a first duration.

[0062] The embodiment of the present application also provides an operation and maintenance device, which is applied to a cloud platform of an operation and maintenance system, wherein the operation and maintenance system further includes: a network agent terminal and a monitoring terminal; the device includes:

[0063] An operation and maintenance data receiving module, used to receive the operation and maintenance data sent by the monitoring end when determining that the robot control end is abnormal; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server; and the operation and maintenance data is used by the monitoring end to determine whether the robot control end is abnormal;

[0064] A first instruction generation module is used to generate a fault handling instruction for handling the fault of the robot control end when it is determined that the robot control end is faulty based on the operation and maintenance data;

[0065] The instruction sending module is used to send the fault handling instruction to the robot control end through the network agent end, so that the robot control end performs fault handling according to the fault handling instruction.

[0066] Optionally, the first instruction generating module is specifically used to generate a fault handling instruction for handling the first specified type of fault;

[0067] The device also includes:

[0068] A reference data acquisition module, for obtaining reference data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal when it is determined that the fault of the robot control terminal does not belong to the first specified type, and sending the reference data to the operation and maintenance client, so that the operation and maintenance personnel can generate an upgrade file for handling the fault based on the reference data;

[0069] The upgrade file sending module is used to send the upgrade file to the monitoring end through the network agent end after receiving the upgrade file; so that the monitoring end receives the upgrade file and sends the upgrade file to the robot control end, so that the robot control end is upgraded based on the upgrade file.

[0070] Optionally, the device further comprises:

[0071] An operation status data receiving module, used for receiving the robot operation status data uploaded by the robot to be monitored through the network agent;

[0072] The second instruction generating module is used to generate a fault handling instruction for handling the fault of the robot when it is determined that the robot has a fault based on the running status data.

[0073] The present application also provides an electronic device, including:

[0074] Memory, used to store computer programs;

[0075] The processor is used to implement any of the above-mentioned operation and maintenance methods when executing the program stored in the memory.

[0076] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, any of the above-mentioned operation and maintenance methods is implemented.

[0077] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute any of the above-mentioned operation and maintenance methods.

[0078] Beneficial effects of the embodiments of the present application:

[0079] The robot operation and maintenance system provided in the embodiment of the present application includes: a monitoring end, a network agent end and a cloud platform; the monitoring end can obtain the operation and maintenance data of the robot control end to be monitored, and when it is determined that the robot control end is abnormal based on the operation and maintenance data, the monitoring end sends the operation and maintenance data to the cloud platform through the network agent end; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of middleware running in the server; the cloud platform can generate a fault handling instruction for the robot control end to handle the fault when it is determined that the robot control end is faulty based on the received operation and maintenance data, and send the fault handling instruction to the robot control end through the network agent end, so that the robot control end performs fault handling according to the fault handling instruction.

[0080] It can be seen that, through this solution, when a fault occurs at the robot control end, information can be automatically, quickly collected and transmitted without affecting the operation of the industrial production in the scene where the robot is located, thereby realizing rapid processing of the fault. Therefore, this solution improves the efficiency of fault processing at the robot control end. In addition, the operation and maintenance system provided by the embodiment of the present application can continuously monitor the robot control end, so that after the robot control end is processed for a fault, it can also continuously detect whether the processed fault occurs again, thereby realizing a closed loop of fault detection.

[0081] Of course, implementing any product or method of the present application does not necessarily require achieving all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0082] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0083] Figure 1 A schematic diagram of the structure of the operation and maintenance system provided in an embodiment of the present application;

[0084] Figure 2 A schematic diagram of the business architecture of the monitoring end in the operation and maintenance system provided in an embodiment of the present application;

[0085] Figure 3 A schematic diagram of a process involved in the operation and maintenance system provided in an embodiment of the present application;

[0086] Figure 4 A schematic diagram of a rolling upgrade in an embodiment of the present application;

[0087] Figure 5 A schematic diagram of a downlink network involved in the operation and maintenance system provided in an embodiment of the present application;

[0088] Figure 6 A schematic diagram of an uplink network involved in the operation and maintenance system provided in an embodiment of the present application;

[0089] Figure 7 A schematic diagram of the deployment architecture involved in the operation and maintenance system provided in the embodiment of the present application;

[0090] Figure 8 A flowchart of the operation and maintenance method provided in the embodiment of the present application;

[0091] Fig. 9 A flowchart of another operation and maintenance method provided in an embodiment of the present application;

[0092] Fig.10 A schematic diagram of the structure of the operation and maintenance device provided in an embodiment of the present application;

[0093] Fig.11 A schematic diagram of the structure of another operation and maintenance device provided in an embodiment of the present application;

[0094] Fig.12 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0095] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field based on the present application belong to the scope of protection of the present application.

[0096] In order to improve the efficiency of troubleshooting a robot control terminal, an embodiment of the present application provides an operation and maintenance system, which includes: a monitoring terminal, a network agent terminal and a cloud platform; wherein:

[0097] A monitoring terminal, used to obtain operation and maintenance data of a robot control terminal to be monitored, and when determining that the robot control terminal is abnormal based on the operation and maintenance data, send the operation and maintenance data to the cloud platform through a network proxy terminal; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of middleware running in the server;

[0098] The cloud platform is used to generate a fault handling instruction for handling the robot control end when a fault in the robot control end is determined based on the received operation and maintenance data, and send the fault handling instruction to the robot control end through the network agent end, so that the robot control end handles the fault according to the fault handling instruction.

[0099] Through this solution, when a fault occurs at the robot control end, information can be automatically, quickly collected and transmitted without affecting the operation of the industrial production in the scene where the robot is located, thereby realizing rapid processing of the fault. Therefore, this solution improves the efficiency of fault processing at the robot control end. In addition, the operation and maintenance system provided by the embodiment of the present application can continuously monitor the robot control end, so that after the robot control end is fault processed, it can also continuously detect whether the processed fault occurs again, realizing a closed loop of fault detection.

[0100] The operation and maintenance system provided in the embodiment of the present application is introduced below in conjunction with the accompanying drawings.

[0101] like Figure 1 As shown, the operation and maintenance system provided in the embodiment of the present application may include:

[0102] Monitoring terminal 101, network agent terminal 102 and cloud platform 103;

[0103] The operation and maintenance system proposed in the embodiment of the present application can be used to operate and maintain robot systems in scenarios such as industrial production.

[0104] The network agent 102 may be a wired network card or a wireless network card. In one implementation, the network agent 102 may be deployed in a charging station of the robot to improve the degree of integration. There may be multiple charging stations in a robot system.

[0105] The monitoring terminal 101 is used to obtain the operation and maintenance data of the robot control terminal to be monitored, and when the robot control terminal is determined to be abnormal based on the operation and maintenance data, the operation and maintenance data is sent to the cloud platform 103 through the network agent terminal 102; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of the server for controlling the robot, component operation status data of the robot business component running in the server, and middleware operation status data of the middleware running in the server;

[0106] The robot control terminal can be a server for controlling the robot, or a control program running in the server. The server can be installed with programs such as business components for executing various robot services, and can be deployed in a local computer room. In a robot system, multiple such servers can be included, so that load balancing can be achieved when receiving and processing robot control tasks.

[0107] The monitoring terminal 101 may be a program or device for monitoring the robot control terminal. In one implementation, the monitoring terminal 101 and the robot control terminal may be deployed in the same server. When a robot system includes multiple servers, the monitoring terminal 101 may be deployed in each server.

[0108] like Figure 2 As shown, the monitoring terminal 101 can detect the system-level operating status data of the server, that is, the parameters representing the overall operating status of the server, such as CPU occupancy, memory occupancy, disk usage, and thread information (for example, the number of threads used, the operating status of each process, etc.), handle information (for example, the number of handles used), etc. The thread information can be obtained by detecting the PID (process number).

[0109] For each robot business component running in the server, the monitoring end 101 can also detect the running status data of the robot business component (i.e., component running status data). Each robot business component can be a component in the robot control end for realizing a business function. The robot business components in the robot control end may include: iWMS (Intelligence Warehouse Management System), RCMS (Robot Condition Monitoring System), RCS (Robot Control System), WCS (Warehouse Control System), AMS (Automated Manufacturing Systems), etc.

[0110] For each business component, you can obtain the component running status data for the general basic detection items of the business component. General basic detection items, such as: occupied memory, occupied CPU, handle information (for example, the number of used handles), number of database connections, log backup information (for example, whether the log backup is successful), abnormal crash information (for example, the number of crashes), data migration task information (for example, whether the data migration is successful), etc.

[0111] In addition, according to different business characteristics, the number of unfinished tasks of the specified business component, whether the message sending queue is accumulated, whether the message receiving queue is accumulated, interface exception information (for example, the number of interface exceptions), internal processing time, etc. can also be detected for the specified business component.

[0112] The monitoring terminal 101 can also detect the middleware running status data of the middleware running in the server. The middleware can be a general middleware that supports the operation of various robot business components in the server, such as a database, a message middleware, etc. For the database, the configuration parameters, the computing resources occupied by the database, the amount of data in the database, SQL (Structured Query Language, database language), TOP SQL (the most time-consuming database query statement) time, etc. can be detected. For the middleware, the memory occupied, the CPU occupied, and other information can also be detected.

[0113] In addition, the user can also manage the detection items to be detected by the monitoring terminal 101 according to needs, that is, independently set the detection items to be detected, and perform routine configuration for the monitoring terminal 101, including configuring detection strategies, inference strategies, etc.

[0114] When the monitoring terminal 101 is deployed in a local server, the monitoring terminal 101 can use cgroups (controlgroups) to manage the computing resources occupied by itself, such as CPU resources, memory, etc., and automatically shut down when it detects that the computing resources occupied by itself reach a preset threshold, so as to minimize the impact of the monitoring terminal 101 on the server performance, thereby reducing the impact of the monitoring terminal 101 on the normal operation of the robot control terminal.

[0115] In one implementation, the monitoring terminal 101 may pre-set an abnormal condition for each parameter in the operation and maintenance data detected by the monitoring terminal 101. For example, the abnormal condition may be that the CPU occupancy rate in the system-level operation status data exceeds a preset threshold, or that the memory occupied by a business component exceeds a preset threshold, etc. Thus, the monitoring terminal 101 may confirm that the robot control terminal is abnormal when it is detected that any parameter in the operation and maintenance data meets the abnormal condition.

[0116] After the monitoring terminal 101 determines that the robot control terminal is abnormal, the operation and maintenance data can be sent to the cloud platform 103 through the network agent terminal 102. The operation and maintenance data sent can be all the operation and maintenance data currently obtained by the monitoring terminal 101, or it can be the operation and maintenance data associated with the abnormality. For example, for a business component, if it is detected that there is a parameter in the component operation status data of the business component that meets the preset condition, that is, it is determined that the business component is abnormal, then all the operation and maintenance data currently obtained for the business component can be sent to the cloud platform.

[0117] The operation and maintenance data acquired by the monitoring terminal 101 may be data generated within a time period. The monitoring terminal 101 may also periodically acquire the generated operation and maintenance data, and after acquiring the operation and maintenance data each time, determine whether the robot control terminal is abnormal based on the operation and maintenance data, and then when determining that the robot control terminal is abnormal, send the operation and maintenance data acquired this time, or data associated with the abnormality in the operation and maintenance data acquired this time to the cloud platform 103.

[0118] In one implementation, the monitoring terminal 101 may first generate an event including the operation and maintenance data to be sent, and then send the event to the cloud platform 103 .

[0119] The cloud platform 103 is used to generate a fault handling instruction for handling the robot control end when a fault in the robot control end is determined based on the received operation and maintenance data, and send the fault handling instruction to the robot control end through the network agent 102 so that the robot control end performs fault handling according to the fault handling instruction.

[0120] In one implementation, the cloud platform 103 can determine the fault corresponding to the acquired operation and maintenance data according to the correspondence between the preset operation and maintenance data set and the fault set. And the fault set can include an item of no fault, which is used to indicate that the robot control end has no fault, that is, when it is determined that the item corresponding to the acquired operation and maintenance data is no fault, it is determined that the robot control end has no fault.

[0121] In another implementation, the operation and maintenance data can also be input into a pre-trained fault detection model to obtain a result representing the fault type output by the fault detection model. The fault detection model can be a neural network model trained using sample operation and maintenance data and labels representing the fault type corresponding to the sample operation and maintenance data.

[0122] The cloud platform 103 may pre-set processing strategies for different fault types, so that after the cloud platform 103 determines the fault type of the robot control end, it may generate a fault handling instruction according to the corresponding processing strategy.

[0123] For example, when the fault type is determined to be: a business component has a large memory leak, the CPU usage is too high, or other resource out-of-bounds faults that affect the overall stability of the robot control end, the generated fault handling instructions can be used to instruct the business component to be shut down or restarted.

[0124] If the fault type is determined to be: too much database data, too long SQL delay, etc., the generated fault handling instruction can be used to instruct the migration of data in the database. If the fault type is determined to be: data migration failure, etc., the generated fault handling instruction can be used to instruct the data to be migrated to be migrated again.

[0125] When the fault type is determined to be: system process pseudo-death of the robot control end, system process deadlock of the robot control end, etc., the generated fault handling instructions can be used to instruct the robot control end to retain the data snapshot and restart, and restore data according to the data snapshot after restarting.

[0126] If the robot control end is in a virtual machine environment such as virtualization or containerization, the fault type may include insufficient system resources, that is, insufficient computing resources of the virtual machine used by the robot control end. In this case, the generated fault handling instructions can be used to indicate the computing resources occupied by the robot control end expansion.

[0127] When the fault type is determined to be: the robot control end processing takes too long and the processing capacity is insufficient, the generated fault processing instruction can be used to instruct the robot control end to expand the service node, that is, to enable an idle server for robot control.

[0128] After generating the fault handling instruction, the cloud platform 103 can send the fault handling instruction to the robot control terminal through the network agent terminal 102, so that the robot control terminal performs fault handling according to the fault handling instruction, thereby realizing the ability of the operation and maintenance system to automatically handle faults. The fault handling instruction can be first sent by the cloud platform 103 to the monitoring terminal 101 through the network agent terminal 102, and then the monitoring terminal 101 sends the fault handling instruction to the robot control terminal.

[0129] In one implementation, the cloud platform 103 may also be used to receive robot operation status data uploaded by the robot to be monitored through the network agent 102, and generate a fault handling instruction for handling the robot fault when a robot fault is determined based on the operation status data. The robot operation status data may include information at the robot device level: for example, power, temperature, posture, etc., and may also include the robot's CPU occupancy rate, memory occupancy rate, program error, etc.

[0130] The robot can monitor the running status based on its own alarm module and upload the running status data. The robot can also generate events containing the robot running status data, and then send the generated events to the cloud platform 103.

[0131] The robot can interact with the cloud platform 103 directly through the network agent 102, or the monitoring terminal 101 can first obtain the robot's operating status data, and the monitoring terminal 101 sends the operating status data to the cloud platform 103 through the network agent 102, and then the monitoring terminal 101 receives the fault handling instructions generated by the cloud platform 103 for handling the robot's faults, and forwards them to the robot.

[0132] The manner in which the cloud platform 103 generates fault handling instructions for handling a robot fault may be similar to the manner in which the fault handling instructions for handling a robot control terminal are generated as described above, and will not be described in detail here.

[0133] In this embodiment, when a fault occurs at the robot control end, information can be automatically, quickly collected and transmitted without affecting the operation of the industrial production in the scene where the robot is located, thereby realizing rapid processing of the fault. Therefore, this solution improves the efficiency of fault processing at the robot control end. In addition, the operation and maintenance system provided in the embodiment of the present application can continuously monitor the robot control end, so that after the robot control end is fault processed, it can also continuously detect whether the processed fault occurs again, realizing a closed loop of fault detection.

[0134] In another embodiment of the present application, the cloud platform 103 is specifically used to generate a fault handling instruction for handling the first specified type of fault when it is determined that the fault of the robot control terminal belongs to the first specified type;

[0135] The first specified type may be a fault type for which a corresponding fault handling strategy is pre-recorded in the cloud platform 103. In this case, the cloud platform 103 may directly generate a fault handling instruction for handling the first specified type of fault.

[0136] The cloud platform 103 is further configured to, when it is determined that the fault of the robot control terminal does not belong to the first specified type, obtain reference data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal, and send the reference data to the operation and maintenance client, so that the operation and maintenance personnel can generate an upgrade file for processing the fault based on the reference data; and after receiving the upgrade file, send the upgrade file to the monitoring terminal 101 through the network agent terminal;

[0137] When it is determined that the fault of the robot control end does not belong to the first specified type, it indicates that the processing strategy preset in the cloud platform 103 cannot process the fault. In this case, the log data of the robot control end and / or the reference data associated with the operation and maintenance data in the dump data can be obtained, wherein the dump data (dump) refers to: dumping the data generated in the memory when the program is running in the computer to other storage media to obtain data, for example, when a program has an error or crashes, the data in the memory when the program is running can be dumped into a file to facilitate subsequent search for the cause of the problem, and the data dumped in this process is the dump data.

[0138] Specifically, the reference data can be obtained by the monitoring terminal 101 from the storage device of the robot control terminal, and then sent to the cloud platform 103, so that the cloud platform 103 can obtain the reference data. The reference data can be log data and / or dump data generated within a specified time period before the fault occurs.

[0139] After obtaining the reference data, the cloud platform 103 can send the reference data to the operation and maintenance personnel through the operation and maintenance client, so that the operation and maintenance personnel can perform fault analysis based on the reference data, determine the cause of the fault, and then generate an upgrade file for handling the fault. The operation and maintenance client can be a client such as a communication program, enterprise office software, and enterprise office system.

[0140] The way in which the cloud platform 103 handles robot failures can be similar to the above. For example, when it is determined that the robot failure does not belong to the specified type, reference data associated with the operation and maintenance data in the robot's log data and / or dump data can be obtained, so that the operation and maintenance personnel can also generate a robot upgrade file for handling the robot failure based on the reference data for the robot. The cloud platform 103 then receives the robot upgrade file and sends the robot upgrade file to the robot through the network agent 102 to upgrade the robot.

[0141] For example, a processing flow of an embodiment of the present application can be as follows: Figure 3As shown, first, the cloud platform 103 collects and summarizes the events containing operation and maintenance data of the robot and the robot control end, and stores them persistently in the cloud platform 103. The cloud platform 103 performs fault detection and fault diagnosis based on the operation and maintenance data, and then automatically collects the log data and dump data of the robot control end, and generates a fault handling instruction to send to the robot control end to perform pre-processing of the fault. At the same time, the cloud platform 103 can also notify the operation and maintenance personnel of the occurrence of a fault by phone or by sending voice or text messages through the enterprise office software, and can also push the message of the occurrence of the fault to the enterprise office system, so that the enterprise office system notifies the customer problem handling system to generate a customer problem ticket waiting for the task work order. In the cloud platform 103, different judgment conditions, alarm levels, alarm strategies, and alarm push methods can be flexibly configured for different fault types. The cloud platform 103 can also generate a fault diagnosis report at any time or periodically as needed, and the fault diagnosis report can contain information obtained by classifying and counting the faults that occurred in the robot and the robot control end within a time period. Furthermore, the information in the fault diagnosis report can also be used to further optimize the training of the above-mentioned fault detection model to improve the accuracy of the fault detection model detection.

[0142] In this embodiment, the cloud platform 103 used for operating and maintaining the robot and the robot control terminal can also be called an alarm monitoring center. One cloud platform 103 can be used to operate and maintain multiple robot systems.

[0143] The operation and maintenance personnel develop an upgrade file to handle the fault, and finally upload the developed upgrade file as a product to the enterprise office system. The upgrade file can be a program installation package, and then the enterprise office system pushes the upgrade file to the cloud platform 103, and the cloud platform 103 sends the upgrade file to the monitoring terminal 101. The monitoring terminal 101 can install the upgrade file when the robot or robot control terminal meets the upgrade conditions, for example, when the robot or robot control terminal is idle, to upgrade the program of the robot or robot control terminal. Afterwards, the monitoring terminal 101 and the cloud platform 103 can also detect whether the upgrade is successful, and continue to detect whether the same fault occurs again.

[0144] The monitoring end 101 is also used to receive the upgrade file and send the upgrade file to the robot control end, so that the robot control end is upgraded based on the upgrade file.

[0145] In one implementation, the robot control terminal can be upgraded in a grayscale release or rolling upgrade manner. For example, a rolling upgrade can be performed as follows: Figure 4As shown in the figure: before the upgrade, 100% of the task traffic to be processed by the robot control end is processed by instance 1 and instance 2 in version V1 before the upgrade. After installing the upgrade file to obtain the upgraded version V2, 5% of the task traffic can be first allocated to instance 1 in the upgraded version V2 for processing. After the operation reaches the preset time, the task traffic allocated to instance 1 of version V2 can be increased to 30%. After continuing to run for a period of time, if there is no abnormality in the operation, the task traffic allocated to instance 1 of version V2 will continue to be increased to 50%, and instance 1 in version V1 will no longer be allocated task traffic. After running for a period of time, 70% of the task traffic will be allocated to instance 1 and instance 2 of version V2. If the operation is stable, the task traffic can finally be no longer allocated to version V1, and 100% of the task traffic will be allocated to instance 1 and instance 2 of version V2 to complete the upgrade.

[0146] In this embodiment, the efficiency of troubleshooting the robot control terminal is improved. Furthermore, the cloud platform obtains reference data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal, and sends it to the operation and maintenance client, so that the operation and maintenance personnel can generate an upgrade file for troubleshooting based on the reference data; and after receiving the upgrade file, send the upgrade file to the monitoring terminal through the network agent; the monitoring terminal receives the upgrade file and sends the upgrade file to the robot control terminal, so that the robot control terminal is upgraded based on the upgrade file, so that when the fault cannot be automatically handled, the operation and maintenance personnel can develop an upgrade file for troubleshooting, and then obtain the upgrade file to automatically upgrade the robot control terminal to solve the fault.

[0147] In another embodiment of the present application, the monitoring end 101 is further used to determine that the robot control end is abnormal based on the operation and maintenance data, before sending the operation and maintenance data to the cloud platform 103 through the network agent end 102, for the operation state data corresponding to the same operation state in the operation and maintenance data at multiple different times, if the multiple operation state data meet the preset conditions, determine that the robot control end is abnormal;

[0148] One operating state in the operation and maintenance data corresponds to each parameter to be monitored by the monitoring terminal 101 .

[0149] The precondition includes at least one of the following:

[0150] The first item is that the frequency of the multiple operating status data indicating anomalies is greater than the first threshold; that is, within a specified time period, the number of multiple operating status data indicating anomalies obtained for the same operating status is greater than the first threshold. The monitoring terminal 101 can periodically obtain the operating status data corresponding to the same operating status in the operation and maintenance data, and determine whether the operating status data indicates anomalies after each acquisition. For example, the system-level memory usage rate can be periodically obtained. After each acquisition, if the memory usage rate obtained this time is greater than the preset threshold, it is determined that the memory usage rate indicates anomalies.

[0151] The second item is that the number of times the multiple running status data indicate continuous abnormalities is greater than a second threshold; that is, for the same running status, the multiple running status data obtained continuously all indicate abnormalities.

[0152] The third item is that the duration of continuous abnormality in the multiple operating status data is greater than the first duration. When the operating status data obtained by the monitoring terminal 101 for a certain operating status indicates abnormality for the first time, the time of obtaining the operating status data can be recorded as the abnormality occurrence time. If each subsequent acquisition of the operating status data corresponding to the operating status is abnormal, and the time interval between the time of the most recent acquisition of the operating status and the abnormality occurrence time reaches the first duration, it can be determined that the robot control terminal is abnormal.

[0153] In one implementation, the operation and maintenance system may further include: a monitoring management terminal, configured to perform at least one of the following steps:

[0154] When it is detected that the monitoring terminal 101 is shut down, restart the monitoring terminal 101;

[0155] Receiving the program package of the monitoring terminal 101 sent by the cloud platform 103 through the network agent terminal 102 to update the monitoring terminal 101 deployed in the server;

[0156] The network agent 102 receives the upgrade file for the robot control terminal sent by the cloud platform 103 and sends it to the monitoring terminal 101, so that the monitoring terminal 101 upgrades the robot control terminal based on the upgrade file.

[0157] The monitoring management terminal can be deployed in a server for controlling the robot, or it can be an independent device. The monitoring management terminal can be used to receive files with large data volumes sent by the cloud platform 103, including program packages of the monitoring terminal 101 and upgrade files of the robot control terminal, so that the monitoring terminal 101 can be initially installed and subsequently upgraded, and the received upgrade files can be sent to the monitoring terminal 101, so that the monitoring terminal 101 can upgrade the robot control terminal based on the upgrade files.

[0158] like Figure 5As shown, a downlink data network involved in the operation and maintenance system provided in this embodiment may include: a cloud platform 103, a network agent terminal 102, a robot, a monitoring and management terminal and an operation and maintenance application; the operation and maintenance application is an application used to operate and maintain the robot and the robot control system, and may include the monitoring terminal 101 in the embodiment of the present application; the operation and maintenance application and the monitoring and management terminal can communicate through the local loopback address 127.0.0.1.

[0159] In an uplink data network involved in the operation and maintenance system provided in this embodiment, such as Figure 6 As shown, the robot and the operation and maintenance application directly upload the operation status data to the cloud platform 103 through the network agent. Since the amount of data is small, the monitoring and management end does not need to be involved, so the monitoring and management end may not be included in the uplink data network.

[0160] The monitoring management end and the monitoring end 101 can transmit different data through different links, which can avoid mutual influence and improve the operation efficiency of the operation and maintenance system.

[0161] In this embodiment, the efficiency of troubleshooting the robot control terminal is improved. Furthermore, the monitoring terminal determines that the robot control terminal is abnormal when multiple operating status data meet preset conditions, rather than considering the robot control terminal abnormal every time the acquired operating status data indicates an abnormality. This can avoid frequently sending operation and maintenance data to the cloud platform, and the cloud platform does not need to frequently perform fault judgments, thereby reducing the occupation of computing resources.

[0162] In one embodiment of the present application, a deployment architecture diagram of the operation and maintenance system can be as follows: Figure 7 As shown: the monitoring management end can communicate with the monitoring end 101 through the HTTP (Hypertext Transfer Protocol) protocol, and the monitoring end 101 communicates with the cloud platform 103 through HTTPS (Hypertext Transfer Protocol Secure) and the network agent 102. The monitoring end 101 can be deployed in the same server as the robot control end. The robot can also exchange information with the cloud platform 103 through the network agent 102. The cloud platform 103 can also send messages to the communication software to notify the operation and maintenance personnel of the failure; the cloud platform 103 can also interact with the enterprise office and R&D management system, and push the failure message to the enterprise office system, so that the enterprise office system notifies the customer problem handling system to generate a customer problem ticket waiting for the task work order, and receives the upgrade file uploaded by the enterprise office system.

[0163] In this embodiment, when a fault occurs at the robot control end, information can be automatically, quickly collected and transmitted without affecting the operation of the industrial production in the scene where the robot is located, thereby realizing rapid processing of the fault. Therefore, this solution improves the efficiency of fault processing at the robot control end. In addition, the operation and maintenance system provided in the embodiment of the present application can continuously monitor the robot control end, so that after the robot control end is fault processed, it can also continuously detect whether the processed fault occurs again, realizing a closed loop of fault detection. The whole process has a high degree of automation and intelligence, which can greatly improve operation and maintenance, and timely detect and handle faults.

[0164] The embodiment of the present application also provides an operation and maintenance method, which is applied to the monitoring end of the operation and maintenance system, and the operation and maintenance system also includes: a network agent end and a cloud platform; Figure 8 As shown, the method includes:

[0165] S801, obtaining operation and maintenance data of a robot control terminal to be monitored; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server;

[0166] S802, when it is determined that the robot control terminal is abnormal based on the operation and maintenance data, the operation and maintenance data is sent to the cloud platform through the network agent, so that the cloud platform determines that the robot control terminal is faulty based on the received operation and maintenance data; generates a fault handling instruction for handling the robot control terminal, and sends the fault handling instruction to the robot control terminal through the network agent, so that the robot control terminal handles the fault according to the fault handling instruction.

[0167] Optionally, the method further comprises:

[0168] Receiving an upgrade file for processing the fault sent by the cloud platform; wherein the upgrade file is generated by the operation and maintenance personnel based on the reference data; the reference data is data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal acquired by the cloud platform when it is determined that the fault of the robot control terminal does not belong to the first specified type;

[0169] Send the upgrade file to the robot control end so that the robot control end is upgraded based on the upgrade file.

[0170] Optionally, the monitoring end is deployed in a server; the method further includes:

[0171] It will automatically shut down when it detects that the computing resources it occupies have reached the preset threshold.

[0172] Optionally, when it is determined through the operation and maintenance data that the robot control terminal is abnormal, before sending the operation and maintenance data to the cloud platform through the network agent terminal, the method further includes:

[0173] For multiple operation status data at different times corresponding to the same operation status in the operation and maintenance data, if the multiple operation status data meet the preset conditions, it is determined that the robot control end is abnormal;

[0174] The preconditions include at least one of the following:

[0175] The frequency of abnormalities indicated by the multiple operating status data is greater than a first threshold, the number of consecutive abnormalities indicated by the multiple operating status data is greater than a second threshold, and the duration of consecutive abnormalities indicated by the multiple operating status data is greater than a first duration.

[0176] The embodiment of the present application also provides an operation and maintenance method, which is applied to a cloud platform of an operation and maintenance system. The operation and maintenance system further includes: a network agent terminal and a monitoring terminal; Fig. 9 As shown, the method includes:

[0177] S901, receiving operation and maintenance data sent by the monitoring end when determining that the robot control end is abnormal; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server; and the operation and maintenance data is used by the monitoring end to determine whether the robot control end is abnormal;

[0178] S902, when it is determined based on the operation and maintenance data that the robot control end has a fault, generating a fault handling instruction for handling the fault of the robot control end;

[0179] S903, sending a fault handling instruction to the robot control end through the network agent end, so that the robot control end performs fault handling according to the fault handling instruction.

[0180] Optionally, the above-mentioned generating a fault handling instruction for handling a fault on the robot control end includes:

[0181] generating a fault handling instruction for handling a fault of a first specified type;

[0182] The method further includes:

[0183] When it is determined that the fault of the robot control terminal does not belong to the first specified type, obtaining reference data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal;

[0184] Send it to the operation and maintenance client so that the operation and maintenance personnel can generate an upgrade file for handling the fault based on the reference data;

[0185] After receiving the upgrade file, the upgrade file is sent to the monitoring end through the network agent end; so that the monitoring end receives the upgrade file and sends the upgrade file to the robot control end, so that the robot control end is upgraded based on the upgrade file.

[0186] Optionally, the method further comprises:

[0187] Receive robot operation status data uploaded by the robot to be monitored through the network agent;

[0188] When a robot failure is determined based on the operation status data, a failure handling instruction for handling the failure of the robot is generated.

[0189] The embodiment of the present application also provides an operation and maintenance device, which is applied to the monitoring end of the operation and maintenance system. The operation and maintenance system also includes: a network agent end and a cloud platform; Fig.10 As shown, the device comprises:

[0190] The operation and maintenance data acquisition module 1001 is used to acquire the operation and maintenance data of the robot control terminal to be monitored; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server;

[0191] The operation and maintenance data sending module 1002 is used to send the operation and maintenance data to the cloud platform through the network agent when it is determined that the robot control terminal is abnormal based on the operation and maintenance data, so that the cloud platform can generate a fault handling instruction for handling the robot control terminal when the robot control terminal is faulty based on the received operation and maintenance data, and send the fault handling instruction to the robot control terminal through the network agent, so that the robot control terminal can handle the fault according to the fault handling instruction.

[0192] Optionally, the device further comprises:

[0193] An upgrade file receiving module, used for receiving an upgrade file for processing a fault sent by the cloud platform; wherein the upgrade file is generated by an operation and maintenance personnel based on reference data; the reference data is data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal acquired by the cloud platform when it is determined that the fault of the robot control terminal does not belong to the first specified type;

[0194] The upgrade file upgrade module is used to send the upgrade file to the robot control end so that the robot control end is upgraded based on the upgrade file.

[0195] Optionally, the monitoring terminal is deployed in the server; the device further includes:

[0196] The automatic shutdown module is used to automatically shut down when it detects that the computing resources occupied by itself have reached a preset threshold.

[0197] Optionally, the device further comprises:

[0198] The abnormality determination module is used for, when the operation and maintenance data is sent and the robot control terminal is determined to be abnormal through the operation and maintenance data, before sending the operation and maintenance data to the cloud platform through the network agent, the method further includes:

[0199] For a plurality of operation status data at different times corresponding to the same operation status in the operation and maintenance data, if the plurality of operation status data meet a preset condition, determining that the robot control terminal is abnormal;

[0200] The preset conditions include at least one of the following:

[0201] The frequency of abnormalities indicated by the multiple operating status data is greater than a first threshold, the number of consecutive abnormalities indicated by the multiple operating status data is greater than a second threshold, and the duration of consecutive abnormalities indicated by the multiple operating status data is greater than a first duration.

[0202] The embodiment of the present application also provides an operation and maintenance device, which is applied to a cloud platform of an operation and maintenance system. The operation and maintenance system also includes: a network agent terminal and a monitoring terminal; Fig.11 As shown, the device comprises:

[0203] The operation and maintenance data receiving module 1101 is used to receive the operation and maintenance data sent by the monitoring end when determining that the robot control end is abnormal; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server; and the operation and maintenance data is used by the monitoring end to determine whether the robot control end is abnormal;

[0204] A first instruction generating module 1102 is used to generate a fault handling instruction for handling the fault of the robot control end when it is determined that the robot control end is faulty based on the operation and maintenance data;

[0205] The instruction sending module 1103 is used to send the fault handling instruction to the robot control end through the network agent end, so that the robot control end performs fault handling according to the fault handling instruction.

[0206] Optionally, the first instruction generating module is specifically used to generate a fault handling instruction for handling the first specified type of fault;

[0207] The device also includes:

[0208] A reference data acquisition module, for obtaining reference data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal when it is determined that the fault of the robot control terminal does not belong to the first specified type, and sending the reference data to the operation and maintenance client, so that the operation and maintenance personnel can generate an upgrade file for handling the fault based on the reference data;

[0209] The upgrade file sending module is used to send the upgrade file to the monitoring end through the network agent end after receiving the upgrade file; so that the monitoring end receives the upgrade file and sends the upgrade file to the robot control end, so that the robot control end is upgraded based on the upgrade file.

[0210] Optionally, the device further comprises:

[0211] An operation status data receiving module, used for receiving the robot operation status data uploaded by the robot to be monitored through the network agent;

[0212] The second instruction generating module is used to generate a fault handling instruction for handling the fault of the robot when it is determined that the robot has a fault based on the running status data.

[0213] The present application also provides an electronic device, such as Fig.12 As shown, including:

[0214] Memory 1201, used for storing computer programs;

[0215] The processor 1202 is used to implement the steps of any of the above-mentioned operation and maintenance methods when executing the program stored in the memory 1201.

[0216] Furthermore, the electronic device may further include a communication bus and / or a communication interface, and the processor 1202, the communication interface, and the memory 1201 communicate with each other via the communication bus.

[0217] The communication bus mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0218] The communication interface is used for communication between the above electronic device and other devices.

[0219] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0220] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0221] In another embodiment provided in the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned operation and maintenance methods are implemented.

[0222] In another embodiment provided in the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute the operation and maintenance method described in any one of the above embodiments.

[0223] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a solid-state hard disk (SSD), etc.

[0224] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0225] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the method embodiment, since it is basically similar to the system embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the system embodiment.

[0226] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. An operation and maintenance system, characterized in that: The operation and maintenance system includes: a monitoring terminal, a network agent terminal and a cloud platform; wherein: The monitoring end is used to obtain operation and maintenance data of the robot control end to be monitored, and when it is determined that the robot control end is abnormal based on the operation and maintenance data, the monitoring end sends the operation and maintenance data to the cloud platform through the network agent end; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server; The cloud platform is used to generate a fault handling instruction for handling the robot control end when it is determined that the robot control end has a fault based on the received operation and maintenance data, and send the fault handling instruction to the robot control end through the network agent end, so that the robot control end performs fault handling according to the fault handling instruction.

2. The system according to claim 1, wherein the cloud platform is specifically configured to generate a fault handling instruction for handling the fault of the first specified type when it is determined that the fault of the robot control end belongs to the first specified type; The cloud platform is further configured to, when it is determined that the fault of the robot control terminal does not belong to the first specified type, obtain reference data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal, and send the reference data to the operation and maintenance client, so that the operation and maintenance personnel can generate an upgrade file for processing the fault based on the reference data; and after receiving the upgrade file, send the upgrade file to the monitoring terminal through the network agent terminal; The monitoring end is further used to receive the upgrade file and send the upgrade file to the robot control end, so that the robot control end is upgraded based on the upgrade file.

3. The system according to claim 2, characterized in that The robot control terminal is upgraded in a rolling upgrade manner.

4. The system according to claim 1, characterized in that The cloud platform is also used to receive robot operation status data uploaded by the robot to be monitored through the network agent; When it is determined that the robot has failed based on the operation status data, a failure handling instruction for handling the failure of the robot is generated.

5. The system according to claim 1, characterized in that The monitoring terminal is deployed in the server; The monitoring end is also used to automatically shut down when it detects that the computing resources occupied by itself have reached a preset threshold.

6. The system according to claim 5, characterized in that The system further includes: a monitoring management terminal, configured to perform at least one of the following steps: When detecting that the monitoring terminal is shut down, restarting the monitoring terminal; Receiving the program package of the monitoring terminal sent by the cloud platform through the network agent terminal to update the monitoring terminal deployed in the server; The network agent receives the upgrade file for the robot control terminal sent by the cloud platform and sends it to the monitoring terminal, so that the monitoring terminal upgrades the robot control terminal based on the upgrade file.

7. The system according to claim 1, characterized in that The monitoring end is further configured to, when determining that the robot control end is abnormal based on the operation and maintenance data, determine that the robot control end is abnormal before sending the operation and maintenance data to the cloud platform through the network agent end, for a plurality of operation status data at different times corresponding to the same operation state in the operation and maintenance data, if the plurality of operation status data meet a preset condition; Wherein, the preset condition includes at least one of the following: The frequency of abnormalities indicated by the multiple operating status data is greater than a first threshold, the number of consecutive abnormalities indicated by the multiple operating status data is greater than a second threshold, and the duration of consecutive abnormalities indicated by the multiple operating status data is greater than a first duration.

8. The system according to any one of claims 1 to 6, characterized in that: The network agent is deployed in the charging pile of the robot.

9. An operation and maintenance method, characterized in that: The monitoring end is applied to the operation and maintenance system, and the operation and maintenance system also includes: a network agent end and a cloud platform; the method includes: Acquire operation and maintenance data of the robot control terminal to be monitored; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server; When it is determined that the robot control terminal is abnormal based on the operation and maintenance data, the operation and maintenance data is sent to the cloud platform through the network agent, so that the cloud platform determines that the robot control terminal is faulty based on the received operation and maintenance data; generates a fault handling instruction for handling the robot control terminal, and sends the fault handling instruction to the robot control terminal through the network agent, so that the robot control terminal performs fault handling according to the fault handling instruction.

10. The method according to claim 9, characterized in that The method further comprises: Receiving an upgrade file for processing the fault sent by the cloud platform; wherein the upgrade file is generated by an operation and maintenance personnel based on reference data; the reference data is data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal acquired by the cloud platform when it is determined that the fault of the robot control terminal does not belong to the first specified type; The upgrade file is sent to the robot control end so that the robot control end is upgraded based on the upgrade file.

11. The method according to claim 9, characterized in that The monitoring terminal is deployed in the server; the method further includes: It will automatically shut down when it detects that the computing resources it occupies have reached the preset threshold.

12. The method according to claim 9, characterized in that When the robot control terminal is determined to be abnormal through the operation and maintenance data, before sending the operation and maintenance data to the cloud platform through the network agent, the method further includes: For a plurality of operation status data at different times corresponding to the same operation status in the operation and maintenance data, if the plurality of operation status data meet a preset condition, determining that the robot control terminal is abnormal; The preset conditions include at least one of the following: The frequency of abnormalities indicated by the multiple operating status data is greater than a first threshold, the number of consecutive abnormalities indicated by the multiple operating status data is greater than a second threshold, and the duration of consecutive abnormalities indicated by the multiple operating status data is greater than a first duration.

13. An operation and maintenance method, characterized in that: A cloud platform applied to an operation and maintenance system, wherein the operation and maintenance system further comprises: a network agent terminal and a monitoring terminal; and the method comprises: Receive operation and maintenance data sent by the monitoring end when determining that the robot control end is abnormal; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server; and the operation and maintenance data is used by the monitoring end to determine whether the robot control end is abnormal; In the case where it is determined that the robot control end has a fault based on the operation and maintenance data, generating a fault handling instruction for handling the fault of the robot control end; The fault handling instruction is sent to the robot control end through the network agent end, so that the robot control end performs fault handling according to the fault handling instruction.

14. The method according to claim 13, characterized in that The generating of a fault handling instruction for handling a fault on the robot control terminal comprises: generating a fault handling instruction for handling the first specified type of fault; The method further comprises: When it is determined that the fault of the robot control terminal does not belong to the first specified type, obtaining reference data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal, and sending the reference data to the operation and maintenance client, so that the operation and maintenance personnel can generate an upgrade file for handling the fault based on the reference data; After receiving the upgrade file, the upgrade file is sent to the monitoring end through the network agent end; so that the monitoring end receives the upgrade file and sends the upgrade file to the robot control end, so that the robot control end is upgraded based on the upgrade file.

15. The method according to claim 13, characterized in that The method further comprises: Receiving robot operation status data uploaded by the robot to be monitored through the network agent; When it is determined that the robot has failed based on the operation status data, a failure handling instruction for handling the failure of the robot is generated.

16. An operation and maintenance device, characterized in that: The monitoring end is applied to the operation and maintenance system, and the operation and maintenance system also includes: a network agent end and a cloud platform; the device includes: An operation and maintenance data acquisition module, used to acquire operation and maintenance data of the robot control terminal to be monitored; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server; An operation and maintenance data sending module is used to send the operation and maintenance data to the cloud platform through the network agent when it is determined that the robot control terminal is abnormal based on the operation and maintenance data, so that the cloud platform can generate a fault handling instruction for handling the robot control terminal when the robot control terminal is faulty based on the received operation and maintenance data, and send the fault handling instruction to the robot control terminal through the network agent, so that the robot control terminal can handle the fault according to the fault handling instruction.

17. The device according to claim 16, characterized in that The device also includes: An upgrade file receiving module, used for receiving an upgrade file for processing a fault sent by the cloud platform; wherein the upgrade file is generated by an operation and maintenance personnel based on reference data; the reference data is data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal acquired by the cloud platform when it is determined that the fault of the robot control terminal does not belong to the first specified type; An upgrade file upgrade module, used for sending the upgrade file to the robot control terminal, so that the robot control terminal is upgraded based on the upgrade file; The monitoring terminal is deployed in the server; the device also includes: An automatic shutdown module is used to automatically shut down when it detects that the computing resources occupied by itself have reached a preset threshold; The device also includes: The abnormality determination module is used for, when the operation and maintenance data is sent and the robot control terminal is determined to be abnormal through the operation and maintenance data, before sending the operation and maintenance data to the cloud platform through the network agent, the method further includes: For a plurality of operation status data at different times corresponding to the same operation status in the operation and maintenance data, if the plurality of operation status data meet a preset condition, determining that the robot control terminal is abnormal; The preset conditions include at least one of the following: The frequency of abnormalities indicated by the multiple operating status data is greater than a first threshold, the number of consecutive abnormalities indicated by the multiple operating status data is greater than a second threshold, and the duration of consecutive abnormalities indicated by the multiple operating status data is greater than a first duration.

18. An operation and maintenance device, characterized in that: A cloud platform applied to an operation and maintenance system, wherein the operation and maintenance system further comprises: a network agent terminal and a monitoring terminal; and the device comprises: An operation and maintenance data receiving module, used to receive the operation and maintenance data sent by the monitoring end when determining that the robot control end is abnormal; wherein the operation and maintenance data includes at least one of the following: system-level operation status data of a server for controlling the robot, component operation status data of a robot business component running in the server, and middleware operation status data of a middleware running in the server; and the operation and maintenance data is used by the monitoring end to determine whether the robot control end is abnormal; An instruction generation module, for generating a fault handling instruction for handling the fault of the robot control end when it is determined that the robot control end has a fault based on the operation and maintenance data; The instruction sending module is used to send the fault handling instruction to the robot control end through the network agent end, so that the robot control end performs fault handling according to the fault handling instruction.

19. The device according to claim 18, characterized in that The first instruction generating module is specifically used to generate a fault handling instruction for handling the first specified type of fault; The device also includes: A reference data acquisition module, for obtaining reference data associated with the operation and maintenance data in the log data and / or dump data of the robot control terminal when it is determined that the fault of the robot control terminal does not belong to the first specified type, and sending the reference data to the operation and maintenance client, so that the operation and maintenance personnel can generate an upgrade file for handling the fault based on the reference data; An upgrade file sending module is used to send the upgrade file to the monitoring end through the network agent end after receiving the upgrade file, so that the monitoring end receives the upgrade file and sends the upgrade file to the robot control end, so that the robot control end is upgraded based on the upgrade file; The device also includes: An operation status data receiving module, used for receiving the robot operation status data uploaded by the robot to be monitored through the network agent; The second instruction generating module is used to generate a fault handling instruction for handling the fault of the robot when it is determined that the robot has a fault based on the running status data.

20. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, for implementing the method described in any one of claims 9-12 or 13-15 when executing a program stored in a memory.

21. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any one of claims 9-12 or 13-15 is implemented.

Citation Information

Patent Citations

  • Robot-based data center infrastructure management system

    CN110231061A

  • Cloud power distribution room robot intelligent operation and maintenance duty management system

    CN112055089A

  • Mobile robot remote monitoring system and method

    CN115239240A

  • Operation and maintenance information processing method and related device

    CN116009506A

  • Remote controllable smart take-out robot central control system through network

    KR1020160034272A