CN110450189B - Abnormity processing method and device for robot - Google Patents
Abnormity processing method and device for robot Download PDFInfo
- Publication number
- CN110450189B CN110450189B CN201910670701.9A CN201910670701A CN110450189B CN 110450189 B CN110450189 B CN 110450189B CN 201910670701 A CN201910670701 A CN 201910670701A CN 110450189 B CN110450189 B CN 110450189B
- Authority
- CN
- China
- Prior art keywords
- abnormal
- robot
- abnormal event
- log
- detecting whether
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B25—HAND TOOLS; PORTABLE POWER-DRIVEN TOOLS; MANIPULATORS
- B25J—MANIPULATORS; CHAMBERS PROVIDED WITH MANIPULATION DEVICES
- B25J19/00—Accessories fitted to manipulators, e.g. for monitoring, for viewing; Safety devices combined with or specially adapted for use in connection with manipulators
- B25J19/0095—Means or methods for testing manipulators
Landscapes
- Engineering & Computer Science (AREA)
- Robotics (AREA)
- Mechanical Engineering (AREA)
- Manipulator (AREA)
Abstract
The application discloses an exception handling method and device for a robot. The method comprises the following steps: detecting whether an abnormal event exists in the running process of the robot; if the abnormal event exists, actively acquiring an abnormal log related to the abnormal event in a robot system log; and actively sending the abnormal log. The technical problem that abnormity can not be effectively solved in time is solved. The abnormal log is actively sent by the method and the system, so that the robot abnormity is timely and effectively solved.
Description
Technical Field
The application relates to the field of robots, in particular to an exception handling method and device for a robot.
Background
The robot may be implemented to include: delivering meals, explaining, guiding, patrolling and other tasks.
The inventor finds that if the robot generates an abnormal program in the process of executing a task, the abnormal program cannot be timely and effectively processed and solved.
Aiming at the problem that the abnormity in the related technology can not be effectively solved in time, an effective solution is not provided at present.
Disclosure of Invention
The main objective of the present application is to provide an exception handling method and apparatus for a robot, so as to solve the problem that an exception cannot be effectively solved in time.
In order to achieve the above object, according to one aspect of the present application, there is provided an abnormality processing method for a robot.
An exception handling method for a robot according to the present application includes: detecting whether an abnormal event exists in the running process of the robot; if the abnormal event exists, actively acquiring an abnormal log related to the abnormal event in a robot system log; and actively sending the abnormal log.
Further, detecting whether the robot has an abnormal event in the operation process includes any one or more of the following scenarios: detecting whether an abnormal event which does not normally execute a task exists in the running process of the robot; and detecting whether the robot has an abnormal event which is caused by the crash due to the abnormal logic of the running program in the running process.
Further, the detecting whether the robot has an abnormal event in the operation process includes any one or more of the following preset events: detecting whether a first preset abnormal event exists in the operation process of internal equipment of the robot; detecting whether a second preset abnormal event exists in the robot external equipment in the running process; and detecting whether a third preset abnormal event exists in the networking operation process of the robot.
Further, if there is an abnormal event, actively acquiring an abnormal log related to the abnormal event in a log of the robot system includes: if an abnormal event exists, judging the abnormal event type data; generating occurrence frequency data of the type of abnormal event according to the abnormal event type data; according to the occurrence frequency data, corresponding to the associated historical data; and actively acquiring an abnormal log related to historical data, frequency data and type data in the abnormal events in the robot system log.
Further, actively sending the exception log comprises: determining all abnormal logs to be sent; processing all the abnormal logs according to the highest priority to generate an abnormal log collection; and actively and immediately sending the abnormal log collection. In order to achieve the above object, according to another aspect of the present application, there is provided an abnormality processing apparatus for a robot.
An abnormality processing device for a robot according to the present application includes: the detection module is used for detecting whether the robot has an abnormal event in the running process; the active acquisition module is used for actively acquiring an abnormal log related to an abnormal event in a robot system log if the abnormal event exists; and the sending module is used for actively sending the abnormal log.
Further, the detection module comprises: detecting whether an abnormal event which does not normally execute a task exists in the running process of the robot; and detecting whether the robot has an abnormal event which is caused by the crash due to the abnormal logic of the running program in the running process.
Further, the detection module comprises: detecting whether a first preset abnormal event exists in the operation process of internal equipment of the robot; detecting whether a second preset abnormal event exists in the robot external equipment in the running process; and detecting whether a third preset abnormal event exists in the networking operation process of the robot.
Further, the active acquisition module includes: if an abnormal event exists, judging the abnormal event type data; generating occurrence frequency data of the type of abnormal event according to the abnormal event type data; according to the occurrence frequency data, corresponding to the associated historical data; and actively acquiring an abnormal log related to historical data, frequency data and type data in the abnormal events in the robot system log.
Further, the active acquisition module includes: if an abnormal event exists, judging the abnormal event type data; generating occurrence frequency data of the type of abnormal event according to the abnormal event type data; according to the occurrence frequency data, corresponding to the associated historical data; and actively acquiring an abnormal log related to historical data, frequency data and type data in the abnormal events in the robot system log.
In the method and the device for processing the robot exception in the embodiment of the application, a mode of detecting whether the robot has an exception event or not in the running process is adopted, and if the exception event exists, an exception log related to the exception event in a robot system log is actively acquired, so that the purpose of actively sending the exception log is achieved, the technical effect of timely and effectively solving the robot exception is achieved, and the technical problem that the exception cannot be effectively solved in time is solved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this application, serve to provide a further understanding of the application and to enable other features, objects, and advantages of the application to be more apparent. The drawings and their description illustrate the embodiments of the invention and do not limit it. In the drawings:
FIG. 1 is a schematic flow diagram of an exception handling method for a robot according to a first embodiment of the present application;
FIG. 2 is a schematic flow diagram of an exception handling method for a robot according to a second embodiment of the present application;
FIG. 3 is a schematic flow chart of an exception handling method for a robot according to a third embodiment of the present application;
FIG. 4 is a schematic flow chart of an exception handling method for a robot according to a fourth embodiment of the present application;
FIG. 5 is a schematic flow chart of an exception handling method for a robot according to a fifth embodiment of the present application;
fig. 6 is a schematic structural diagram of an exception handling device for a robot according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be used. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In this application, the terms "upper", "lower", "left", "right", "front", "rear", "top", "bottom", "inner", "outer", "middle", "vertical", "horizontal", "lateral", "longitudinal", and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings. These terms are used primarily to better describe the present application and its embodiments, and are not used to limit the indicated devices, elements or components to a particular orientation or to be constructed and operated in a particular orientation.
Moreover, some of the above terms may be used to indicate other meanings besides the orientation or positional relationship, for example, the term "on" may also be used to indicate some kind of attachment or connection relationship in some cases. The specific meaning of these terms in this application will be understood by those of ordinary skill in the art as appropriate.
Furthermore, the terms "mounted," "disposed," "provided," "connected," and "sleeved" are to be construed broadly. For example, it may be a fixed connection, a removable connection, or a unitary construction; can be a mechanical connection, or an electrical connection; may be directly connected, or indirectly connected through intervening media, or may be in internal communication between two devices, elements or components. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art as appropriate.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
As shown in fig. 1, the method includes steps S to S as follows:
step S102, detecting whether the robot has an abnormal event in the running process;
detecting whether the robot has an abnormal event in the normal operation process, such as the task execution process, wherein the abnormal event can be that the robot does not execute the task normally. The exception event may also cause an error in the execution logic of the robot when performing a task.
It should be noted that the manner of detecting an abnormal event is not limited in the embodiments of the present application as long as the abnormal event can be detected.
Step S104, if an abnormal event exists, actively acquiring an abnormal log related to the abnormal event in a robot system log;
through the abnormal event detection, if the abnormal event exists, all abnormal logs related to the abnormal event in the robot system logs are actively acquired. By configuring a computer program for detecting a preset abnormal event and actively acquiring an abnormal log related to the abnormal event on the robot, an active abnormal log acquisition operation can be performed on the robot.
It should be noted that the exception log related to the exception event may be related to the same exception time or may be related to multiple exception events, and is not specifically limited in the embodiments of the present application.
And step S106, actively sending the abnormal log.
And after the abnormal log is obtained, the abnormal log is actively sent on the robot. It should be noted that, when actively sending the abnormal log, the preset communication time between the robot and the server does not need to be considered, and as long as the abnormal log is detected and obtained, the abnormal log is actively sent on the robot.
From the above description, it can be seen that the following technical effects are achieved by the present application:
in the method and the device for processing the robot exception in the embodiment of the application, a mode of detecting whether the robot has an exception event or not in the running process is adopted, and if the exception event exists, an exception log related to the exception event in a robot system log is actively acquired, so that the purpose of actively sending the exception log is achieved, the technical effect of timely and effectively solving the robot exception is achieved, and the technical problem that the exception cannot be effectively solved in time is solved.
According to the embodiment of the present application, as a preferred embodiment in the present application, as shown in fig. 2, detecting whether there is an abnormal event in the operation process of the robot includes any one or more of the following scenarios:
step S202, detecting whether the robot has an abnormal event which does not normally execute the task in the running process;
step S204, detecting whether the robot has an abnormal event which is caused by the crash due to the abnormal logic of the running program in the running process.
Specifically, detecting whether the robot has an abnormal event which does not normally execute a task in the running process; if the abnormal events which do not normally execute the tasks exist, actively acquiring abnormal logs related to the abnormal events which do not normally execute the tasks in the robot system logs; and actively sending the abnormal log to a server.
Specifically, detecting whether an abnormal event which is caused by crash due to abnormal operation program logic exists in the operation process of the robot; if an abnormal event which causes the crash due to the abnormal logic of the running program exists, actively acquiring an abnormal log which is related to the abnormal event which causes the crash due to the abnormal logic of the running program in a robot system log; and actively sending the abnormal log to a server.
According to the embodiment of the present application, as a preferred embodiment in the present application, as shown in fig. 3, detecting whether there is an abnormal event in the operation process of the robot includes any one or more of the following preset events:
step S302, detecting whether a first preset abnormal event exists in the operation process of the internal equipment of the robot;
step S304, detecting whether a second preset abnormal event exists in the operation process of the robot external equipment;
and step S306, detecting whether a third preset abnormal event exists in the networking operation process of the robot.
Specifically, the detecting whether the robot internal device has the first preset abnormal event in the operation process refers to the preset abnormal event caused by the robot internal device.
The detecting whether the second preset abnormal event exists in the operation process of the robot external equipment refers to the preset abnormal event caused by the robot external equipment.
The detection of whether the third preset abnormal event exists in the networking operation process of the robot refers to the preset abnormal event caused by the networking operation process of the robot.
It should be noted that the preset exception event is configured in advance and can be detected by a computer program. In the embodiment of the present application, the above-described abnormal event is not particularly limited as long as the abnormal situation of the robot can be satisfied.
According to the embodiment of the present application, as shown in fig. 4, if there is an abnormal event, actively acquiring an abnormal log related to the abnormal event in a log of a robot system includes:
step S402, if an abnormal event exists, judging the abnormal event type data;
step S404, generating the occurrence frequency data of the type of abnormal event according to the abnormal event type data;
step S406, according to the occurrence frequency data, corresponding to the associated historical data;
step S408, actively acquiring an abnormal log related to historical data, frequency data and type data in the abnormal event in the robot system log.
Specifically, if the abnormal event exists on the robot, the abnormal event type data needs to be judged, and the occurrence frequency data of the abnormal event of the type is generated according to the abnormal event type data. For example, the frequency of the abnormal event a is 1 day and 2 times. Abnormal event B occurred at a frequency of 1 week 2 times. And correspondingly associating the historical data according to the occurrence frequency data. For example, the historical data C of the abnormal event a is associated, or the historical data D of the abnormal event B is associated.
And actively acquiring an abnormal log related to historical data, frequency data and type data in the abnormal events in a robot system log on the robot.
For the abnormal log, when the robot task is not normally executed or some program logic is abnormally crashed, the abnormal condition and the generation reason of the current robot are recorded and synchronously sent to the background.
According to the embodiment of the present application, as a preferred embodiment in the present application, as shown in fig. 5, actively sending the exception log includes:
step S502, determining all abnormal logs to be sent;
step S504, processing all the abnormal logs according to the highest priority to generate an abnormal log collection;
and step S506, actively and immediately sending the abnormal log collection.
Specifically, all the abnormal logs to be sent are determined, all the abnormal logs are processed according to the highest priority to generate an abnormal log collection, the abnormal log collection is obtained, and the robot can actively send the abnormal log collection in real time.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowcharts, in some cases, the steps illustrated or described may be performed in an order different than presented herein.
According to an embodiment of the present application, there is also provided an apparatus for implementing the above-described exception handling method for a robot, as shown in fig. 6, the apparatus including: the detection module 10 is used for detecting whether an abnormal event exists in the running process of the robot;
detecting whether the robot has an abnormal event in the normal operation process, such as the task execution process, wherein the abnormal event can be that the robot does not execute the task normally. The exception event may also cause an error in the execution logic of the robot when performing a task.
It should be noted that the manner of detecting an abnormal event is not limited in the embodiments of the present application as long as the abnormal event can be detected.
The active acquisition module 20 is configured to actively acquire an abnormal log related to an abnormal event in a log of the robot system if the abnormal event exists;
through the abnormal event detection, if the abnormal event exists, all abnormal logs related to the abnormal event in the robot system logs are actively acquired. By configuring a computer program for detecting a preset abnormal event and actively acquiring an abnormal log related to the abnormal event on the robot, an active abnormal log acquisition operation can be performed on the robot.
It should be noted that the exception log related to the exception event may be related to the same exception time or may be related to multiple exception events, and is not specifically limited in the embodiments of the present application.
And a sending module 30, configured to send the exception log actively.
And after the abnormal log is obtained, the abnormal log is actively sent on the robot. It should be noted that, when actively sending the abnormal log, the preset communication time between the robot and the server does not need to be considered, and as long as the abnormal log is detected and obtained, the abnormal log is actively sent on the robot.
From the above description, it can be seen that the following technical effects are achieved by the present application:
in the method and the device for processing the robot exception in the embodiment of the application, a mode of detecting whether the robot has an exception event or not in the running process is adopted, and if the exception event exists, an exception log related to the exception event in a robot system log is actively acquired, so that the purpose of actively sending the exception log is achieved, the technical effect of timely and effectively solving the robot exception is achieved, and the technical problem that the exception cannot be effectively solved in time is solved.
According to the embodiment of the application, as a preferred option in the embodiment, the detection module 10 is configured to detect whether an abnormal event that does not normally execute a task exists in the operation process of the robot; and detecting whether the robot has an abnormal event which is caused by the crash due to the abnormal logic of the running program in the running process.
Specifically, detecting whether the robot has an abnormal event which does not normally execute a task in the running process; if the abnormal events which do not normally execute the tasks exist, actively acquiring abnormal logs related to the abnormal events which do not normally execute the tasks in the robot system logs; and actively sending the abnormal log to a server.
Specifically, detecting whether an abnormal event which is caused by crash due to abnormal operation program logic exists in the operation process of the robot; if an abnormal event which causes the crash due to the abnormal logic of the running program exists, actively acquiring an abnormal log which is related to the abnormal event which causes the crash due to the abnormal logic of the running program in a robot system log; and actively sending the abnormal log to a server.
According to the embodiment of the application, the detection module 10 is used for detecting whether a first preset abnormal event exists in the operation process of the internal equipment of the robot; detecting whether a second preset abnormal event exists in the robot external equipment in the running process; and detecting whether a third preset abnormal event exists in the networking operation process of the robot.
Specifically, the detecting whether the robot internal device has the first preset abnormal event in the operation process refers to the preset abnormal event caused by the robot internal device.
The detecting whether the second preset abnormal event exists in the operation process of the robot external equipment refers to the preset abnormal event caused by the robot external equipment.
The detection of whether the third preset abnormal event exists in the networking operation process of the robot refers to the preset abnormal event caused by the networking operation process of the robot.
It should be noted that the preset exception event is configured in advance and can be detected by a computer program. In the embodiment of the present application, the above-described abnormal event is not particularly limited as long as the abnormal situation of the robot can be satisfied.
According to the embodiment of the present application, as in the embodiment of the present application, the active acquisition module 20 is configured to determine the abnormal event type data if an abnormal event exists; generating occurrence frequency data of the type of abnormal event according to the abnormal event type data; according to the occurrence frequency data, corresponding to the associated historical data; and actively acquiring an abnormal log related to historical data, frequency data and type data in the abnormal events in the robot system log.
Specifically, if the abnormal event exists on the robot, the abnormal event type data needs to be judged, and the occurrence frequency data of the abnormal event of the type is generated according to the abnormal event type data. For example, the frequency of the abnormal event a is 1 day and 2 times. Abnormal event B occurred at a frequency of 1 week 2 times. And correspondingly associating the historical data according to the occurrence frequency data. For example, the historical data C of the abnormal event a is associated, or the historical data D of the abnormal event B is associated.
And actively acquiring an abnormal log related to historical data, frequency data and type data in the abnormal events in a robot system log on the robot.
For the abnormal log, when the robot task is not normally executed or some program logic is abnormally crashed, the abnormal condition and the generation reason of the current robot are recorded and synchronously sent to the background.
According to the embodiment of the present application, as a preferred option in the embodiment, the active acquisition module 20 is configured to: determining all abnormal logs to be sent; processing all the abnormal logs according to the highest priority to generate an abnormal log collection; and actively and immediately sending the abnormal log collection.
Specifically, all the abnormal logs to be sent are determined, all the abnormal logs are processed according to the highest priority to generate an abnormal log collection, the abnormal log collection is obtained, and the robot can actively send the abnormal log collection in real time.
It will be apparent to those skilled in the art that the modules or steps of the present application described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and they may alternatively be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, or fabricated separately as individual integrated circuit modules, or fabricated as a single integrated circuit module from multiple modules or steps. Thus, the present application is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (7)
1. An exception handling method for a robot, comprising:
detecting whether an abnormal event exists in the running process of the robot;
if the abnormal event exists, actively acquiring an abnormal log related to the abnormal event in a robot system log;
actively sending the abnormal log;
if the abnormal event exists, actively acquiring an abnormal log related to the abnormal event in a robot system log comprises the following steps:
if an abnormal event exists, judging the abnormal event type data;
generating occurrence frequency data of the type of abnormal event according to the abnormal event type data;
according to the occurrence frequency data, corresponding to the associated historical data;
actively acquiring abnormal logs related to historical data, frequency data and type data in the abnormal events in the robot system logs;
for the abnormal log, when the robot task is not normally executed or some program logic is abnormally crashed, the abnormal condition and the generation reason of the current robot are recorded and synchronously sent to a background;
the actively sending the exception log comprises: and determining all abnormal logs to be sent, processing all the abnormal logs according to the highest priority to generate an abnormal log collection set, obtaining the abnormal log collection set, and actively sending the abnormal log collection set by the robot in real time.
2. The exception handling method according to claim 1, wherein detecting whether the robot has an exception event during operation comprises any one or more of the following scenarios:
detecting whether an abnormal event which does not normally execute a task exists in the running process of the robot;
and detecting whether the robot has an abnormal event which is caused by the crash due to the abnormal logic of the running program in the running process.
3. The exception handling method according to claim 1, wherein detecting whether the robot has an exception event during operation comprises any one or more of the following preset events:
detecting whether a first preset abnormal event exists in the operation process of internal equipment of the robot;
detecting whether a second preset abnormal event exists in the robot external equipment in the running process;
and detecting whether a third preset abnormal event exists in the networking operation process of the robot.
4. The exception handling method according to claim 1, wherein actively sending the exception log comprises:
determining all abnormal logs to be sent;
processing all the abnormal logs according to the highest priority to generate an abnormal log collection;
and actively and immediately sending the abnormal log collection.
5. An exception handling apparatus for a robot, comprising:
the detection module is used for detecting whether the robot has an abnormal event in the running process;
the active acquisition module is used for actively acquiring an abnormal log related to an abnormal event in a robot system log if the abnormal event exists;
the sending module is used for actively sending the abnormal log;
the active acquisition module is used for acquiring the data,
if an abnormal event exists, judging the abnormal event type data;
generating occurrence frequency data of the type of abnormal event according to the abnormal event type data;
according to the occurrence frequency data, corresponding to the associated historical data;
actively acquiring abnormal logs related to historical data, frequency data and type data in the abnormal events in the robot system logs;
for the abnormal log, when the robot task is not normally executed or some program logic is abnormally crashed, the abnormal condition and the generation reason of the current robot are recorded and synchronously sent to a background;
the actively sending the exception log comprises: and determining all abnormal logs to be sent, processing all the abnormal logs according to the highest priority to generate an abnormal log collection set, obtaining the abnormal log collection set, and actively sending the abnormal log collection set by the robot in real time.
6. The exception handling apparatus of claim 5, wherein the detection module is to,
detecting whether an abnormal event which does not normally execute a task exists in the running process of the robot;
and detecting whether the robot has an abnormal event which is caused by the crash due to the abnormal logic of the running program in the running process.
7. The exception handling apparatus of claim 5, wherein the detection module is to,
detecting whether a first preset abnormal event exists in the operation process of internal equipment of the robot;
detecting whether a second preset abnormal event exists in the robot external equipment in the running process;
and detecting whether a third preset abnormal event exists in the networking operation process of the robot.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910365401 | 2019-04-30 | ||
| CN201910365401X | 2019-04-30 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110450189A CN110450189A (en) | 2019-11-15 |
| CN110450189B true CN110450189B (en) | 2021-06-08 |
Family
ID=68483302
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910670701.9A Active CN110450189B (en) | 2019-04-30 | 2019-07-23 | Abnormity processing method and device for robot |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110450189B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111093124B (en) * | 2019-12-13 | 2022-02-18 | 苏州浪潮智能科技有限公司 | Abnormity positioning method and device, backbone network switch and readable storage medium |
| CN114851248B (en) * | 2022-05-27 | 2023-03-10 | 中迪机器人(盐城)有限公司 | Abnormity identification and coping processing system and method for clamping robot |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106201756A (en) * | 2016-07-12 | 2016-12-07 | 努比亚技术有限公司 | Log acquisition device, mobile terminal and method |
| CN106339303A (en) * | 2016-08-23 | 2017-01-18 | 浪潮电子信息产业股份有限公司 | Method for analyzing abnormity of running log |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9172670B1 (en) * | 2012-01-31 | 2015-10-27 | Google Inc. | Disaster-proof event data processing |
| CN104199766A (en) * | 2014-08-25 | 2014-12-10 | 广东欧珀移动通信有限公司 | Abnormal running monitoring method and device |
| US9626240B2 (en) * | 2014-09-25 | 2017-04-18 | Oracle International Corporation | Adaptive application logger |
-
2019
- 2019-07-23 CN CN201910670701.9A patent/CN110450189B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106201756A (en) * | 2016-07-12 | 2016-12-07 | 努比亚技术有限公司 | Log acquisition device, mobile terminal and method |
| CN106339303A (en) * | 2016-08-23 | 2017-01-18 | 浪潮电子信息产业股份有限公司 | Method for analyzing abnormity of running log |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110450189A (en) | 2019-11-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112162878B (en) | Database fault discovery method and device, electronic equipment and storage medium | |
| CN110213068B (en) | Message middleware monitoring method and related equipment | |
| CN103246574B (en) | The method of calibration of data accuracy and device | |
| CN109167681B (en) | State monitoring method and device | |
| US11381383B2 (en) | Methods and apparatuses for processing service using blockchain | |
| CN108845912B (en) | Service interface calls the alarm method of failure and calculates equipment | |
| CN110450189B (en) | Abnormity processing method and device for robot | |
| CN106685676B (en) | Node switching method and device | |
| CN112737800B (en) | Service node fault positioning method, call chain generating method and server | |
| US9529661B1 (en) | Optimal multi-core health monitor architecture | |
| CN107870948A (en) | Method for scheduling task and device | |
| CN111143167A (en) | Alarm merging method, device, equipment and storage medium for multiple platforms | |
| US20180026833A1 (en) | Alarm processing methods and devices | |
| EP3040936A1 (en) | Remote server | |
| CN109617750A (en) | A kind of service method for early warning and gateway | |
| US20160205011A1 (en) | Method and Device for Testing Link Performance, Logic Processor and Network Processor | |
| CN110618853B (en) | Detection method, device and equipment for zombie container | |
| CN110659147B (en) | Self-repairing method and system based on module self-checking behavior | |
| CN110405750A (en) | Motion control method and device of robot and robot | |
| CN110238878B (en) | Self-checking method and device for robot | |
| CN106094738A (en) | For running method and the automation equipment of automation equipment | |
| CN113391611B (en) | Early warning method, device and system for power environment monitoring system | |
| CN108600008A (en) | Server management method, server managing device and distributed system | |
| US10356010B2 (en) | Control device | |
| US10674337B2 (en) | Method and device for processing operation for device peripheral |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: Room 702, 7th floor, NO.67, Beisihuan West Road, Haidian District, Beijing 100089 Patentee after: Beijing Yunji Technology Co.,Ltd. Address before: Room 702, 7th floor, NO.67, Beisihuan West Road, Haidian District, Beijing 100089 Patentee before: BEIJING YUNJI TECHNOLOGY Co.,Ltd. |