CN108933695B - Method and apparatus for processing information - Google Patents
Method and apparatus for processing information Download PDFInfo
- Publication number
- CN108933695B CN108933695B CN201810660506.3A CN201810660506A CN108933695B CN 108933695 B CN108933695 B CN 108933695B CN 201810660506 A CN201810660506 A CN 201810660506A CN 108933695 B CN108933695 B CN 108933695B
- Authority
- CN
- China
- Prior art keywords
- abnormal
- call chain
- target
- request
- determining
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the application discloses a method and a device for processing information. One embodiment of the method comprises: acquiring an abnormal operation log corresponding to the target abnormal request, wherein the abnormal operation log comprises a preset hierarchy number; connecting the obtained abnormal operation logs based on the hierarchy number to generate at least one calling chain; determining an abnormal request belonging to a preset historical time period in the target abnormal request as a candidate abnormal request, and acquiring an operation log set corresponding to the candidate abnormal request; for a call chain in at least one call chain, determining the number of abnormal operation logs in the call chain, which are included in an operation log set of a candidate abnormal request, and determining the number of times of abnormity of the call chain for the candidate abnormal request based on the determined number; based on the determined number of times, a target call chain is determined. This embodiment improves the efficiency of information processing.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to a method and a device for processing information.
Background
Large-scale distributed systems are usually composed of many subsystems or modules, and when a request initiated by a user arrives at the system, the request needs to be processed through different modules and returned to the user. Therefore, some modules may have problems and may affect the stability of the whole system.
Currently, the localization tracking of the module with problems usually adopts a manual analysis mode.
Disclosure of Invention
The embodiment of the application provides a method and a device for processing information.
In a first aspect, an embodiment of the present application provides a method for processing information, where the method includes: acquiring an abnormal operation log corresponding to the target abnormal request, wherein the abnormal operation log comprises a preset hierarchy number, and the hierarchy number is used for representing the hierarchy relation among the abnormal operation logs; connecting the obtained abnormal operation logs based on the hierarchy number to generate at least one calling chain; determining an abnormal request belonging to a preset historical time period in the target abnormal request as a candidate abnormal request, and acquiring an operation log set corresponding to the candidate abnormal request; for a call chain in at least one call chain, determining the number of abnormal operation logs in the call chain, which are included in an operation log set of a candidate abnormal request, and determining the number of times of abnormity of the call chain for the candidate abnormal request based on the determined number; based on the determined number of times, a target call chain is determined.
In some embodiments, after determining the target call chain, the method further comprises: determining an abnormal operation log located at the tail stage of a target call chain; and determining the operation corresponding to the determined abnormal operation log as a target operation.
In some embodiments, after determining the operation corresponding to the determined abnormal operation log as the target operation, the method further includes: in response to determining that the target operation is a call operation, determining a network protocol address for performing the call operation; in response to determining that the network protocol addresses for performing the call operation include at least two, dividing the target call chain into at least two target sub-call chains based on the at least two network protocol addresses; determining the times of abnormity of each target sub-call chain aiming at the candidate abnormal requests, and generating result information used for indicating the abnormal reasons of the target abnormal requests based on the determined times of abnormity of the target sub-call chains.
In some embodiments, the method further comprises: and in response to determining that the target operation is not a call operation, determining an abnormal operation log corresponding to the target operation as result information indicating an abnormal reason of the target abnormal request.
In some embodiments, concatenating the obtained abnormal operation logs based on the hierarchy number, generating at least one call chain, includes: based on the hierarchy number, sequentially connecting the acquired abnormal operation logs to generate at least one initial call chain; for an initial call chain in at least one initial call chain, determining whether the initial call chain comprises a missing operation log based on a preset call chain; in response to determining that the initial call chain includes a missing oplog, obtaining the oplog that the initial call chain misses, and supplementing the obtained oplog into the initial call chain, obtaining a call chain.
In a second aspect, an embodiment of the present application provides an apparatus for processing information, the apparatus including: the log obtaining unit is configured to obtain an abnormal operation log corresponding to the target abnormal request, wherein the abnormal operation log comprises preset hierarchy numbers, and the hierarchy numbers are used for representing the hierarchy relation among the abnormal operation logs; a log connection unit configured to connect the acquired abnormal operation logs based on the hierarchy number, and generate at least one call chain; the request determining unit is configured to determine an abnormal request which belongs to a preset historical time period in the target abnormal requests as a candidate abnormal request, and acquire an operation log set corresponding to the candidate abnormal request; a number determination unit configured to determine, for a call chain of at least one call chain, the number of abnormal operation logs in the call chain included in an operation log set of a candidate abnormal request, and determine, based on the determined number, the number of times an abnormality occurs in the call chain for the candidate abnormal request; a call chain determination unit configured to determine a target call chain based on the determined number of times.
In some embodiments, the apparatus further comprises: a log determining unit configured to determine an abnormal operation log located at a tail stage of a target call chain; an operation determination unit configured to determine an operation corresponding to the determined abnormal operation log as a target operation.
In some embodiments, the apparatus further comprises: an address determination unit configured to determine a network protocol address for performing a call operation in response to determining that the target operation is the call operation; a call chain dividing unit configured to divide the target call chain into at least two target sub-call chains based on at least two network protocol addresses in response to determining that the network protocol addresses for performing the call operation include at least two; and the information generation unit is configured to determine the times of abnormity of each target sub-call chain aiming at the candidate abnormity request, and generate result information used for indicating the abnormity reason of the target abnormity request based on the determined times of abnormity of the target sub-call chain.
In some embodiments, the apparatus further comprises: an information determination unit configured to determine, in response to determining that the target operation is not the call operation, an abnormal operation log corresponding to the target operation as result information indicating an abnormal cause of the target abnormal request.
In some embodiments, the log connection unit includes: the log connection module is configured to sequentially connect the acquired abnormal operation logs based on the hierarchy number to generate at least one initial call chain; a log padding module configured to determine, for an initial call chain of the at least one initial call chain, whether the initial call chain includes a missing operation log based on a preset call chain; in response to determining that the initial call chain includes a missing oplog, obtaining the oplog that the initial call chain misses, and supplementing the obtained oplog into the initial call chain, obtaining a call chain.
In a third aspect, an embodiment of the present application provides a server, including: one or more processors; a storage device having one or more programs stored thereon which, when executed by one or more processors, cause the one or more processors to implement the method of any of the embodiments of the method for processing information described above.
In a fourth aspect, the present application provides a computer-readable medium, on which a computer program is stored, which when executed by a processor implements the method of any of the above-described methods for processing information.
The method and the device for processing information provided by the embodiment of the application, by obtaining the abnormal operation log corresponding to the target abnormal request, wherein the abnormal operation log comprises a preset hierarchy number, the hierarchy number is used for representing the hierarchy relation among the abnormal operation logs, then connecting the obtained abnormal operation logs based on the hierarchy number to generate at least one calling chain, determining the abnormal request in the target abnormal request within a preset historical time period as a candidate abnormal request, obtaining the operation log set corresponding to the candidate abnormal request, determining the number of abnormal operation logs in the calling chain included in the operation log set of the candidate abnormal request for the calling chain in the at least one calling chain, and determining the number of times of abnormality of the calling chain for the candidate abnormal request based on the determined number, and determining the target call chain based on the determined times, so that the analysis and the processing of the abnormal reason of the abnormal request are realized through the abnormal operation log corresponding to the abnormal request, and the information processing efficiency is improved.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture diagram in which one embodiment of the present application may be applied;
FIG. 2 is a flow diagram for one embodiment of a method for processing information according to the present application;
FIG. 3 is a schematic diagram of an application scenario of a method for processing information according to the present application;
FIG. 4 is a flow diagram of yet another embodiment of a method for processing information according to the present application;
FIG. 5 is a schematic block diagram illustrating one embodiment of an apparatus for processing information according to the present application;
FIG. 6 is a schematic block diagram of a computer system suitable for use in implementing a server according to embodiments of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
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.
Fig. 1 shows an exemplary system architecture 100 to which embodiments of the method for processing information or the apparatus for processing information of the present application may be applied.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have various communication client applications installed thereon, such as a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.
The terminal apparatuses 101, 102, and 103 may be hardware or software. When the terminal devices 101, 102, and 103 are hardware, they may be various electronic devices with information interaction function, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, mpeg Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer IV, mpeg Audio Layer 4), laptop portable computers, desktop computers, and so on. When the terminal apparatuses 101, 102, 103 are software, they can be installed in the electronic apparatuses listed above. It may be implemented as multiple pieces of software or software modules (e.g., multiple pieces of software or software modules to provide distributed services) or as a single piece of software or software module. And is not particularly limited herein.
The server 105 may be a server that provides various services, such as an information processing server that processes a target abnormality request initiated by the terminal apparatuses 101, 102, 103. The information processing server may analyze and perform other processing on the received data such as the exception request, and obtain a processing result (e.g., a target call chain).
It should be noted that the method for processing information provided in the embodiment of the present application is generally performed by the server 105, and accordingly, the apparatus for processing information is generally disposed in the server 105.
The server may be hardware or software. When the server is hardware, it may be implemented as a distributed server cluster formed by multiple servers, or may be implemented as a single server. When the server is software, it may be implemented as multiple pieces of software or software modules (e.g., multiple pieces of software or software modules used to provide distributed services), or as a single piece of software or software module. And is not particularly limited herein.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. In particular, in the case where data used in processing information does not need to be acquired from a remote place, the above system architecture may not include a network and a terminal device, but only a server.
With continued reference to FIG. 2, a flow 200 of one embodiment of a method for processing information in accordance with the present application is shown. The method for processing information comprises the following steps:
In this embodiment, an execution subject (for example, a server shown in fig. 1) of the method for processing information may obtain an abnormal operation log corresponding to the target abnormal request from a local or communication-connected electronic device (for example, a terminal device shown in fig. 1) through a wired connection manner or a wireless connection manner.
The target exception request is an exception request for determining an exception cause of the target exception request, and the target exception request may be a certain type of request initiated by a user, such as a posting request, an uploading request, and the like. The abnormal request is a request for which a preset operation for responding to the request is not normally performed. Here, an operation that cannot be normally performed is determined as an abnormal operation. When the execution main body or other electronic devices execute abnormal operations, an abnormal operation log is generated, wherein the abnormal operation log comprises an abnormal identifier used for representing log abnormality, and further, the execution main body can acquire the abnormal operation log corresponding to the target abnormal request based on the abnormal identifier. The obtained abnormal operation log may be all or part of the abnormal operation log corresponding to the target abnormal request stored in advance. The anomaly identification may be an identification preset by a technician.
In the present embodiment, the abnormal operation log includes a hierarchy number set in advance. The hierarchical number can be represented in various forms, such as numbers, characters or symbols, and can be used for representing the hierarchical relationship among the abnormal operation logs. It can be understood that the hierarchical relationship between the operation logs can be used to characterize the execution sequence of the operations corresponding to the operation logs.
And step 202, connecting the obtained abnormal operation logs based on the hierarchy number to generate at least one calling chain.
In this embodiment, the execution subject may connect the obtained abnormal operation logs based on the hierarchy number to generate at least one call chain. Specifically, the abnormal operation log obtained by the execution main body may include one or at least two. Here, it is to be understood that, when only one abnormal operation log is included in the abnormal operation log acquired by the execution main body, the abnormal operation log may be directly determined as a call chain.
In this embodiment, the call chain may be used to characterize an execution sequence of the abnormal operation corresponding to the included abnormal operation log. Specifically, for each call chain in at least one call chain, the abnormal operation corresponding to the abnormal operation log located at the first level of the call chain is executed in preference to the abnormal operation corresponding to other abnormal operation logs; and the abnormal operation corresponding to the abnormal operation log at the tail stage of the calling chain is lagged behind the abnormal operation corresponding to other abnormal operation logs. Here, the first level of the call chain is the lowest level (corresponding to the first executed operation) and the last level of the call chain is the highest level (corresponding to the last executed operation).
It should be noted that a call chain may correspond to a separate module in the distributed system. Oplogs belonging to the same call chain may include the same call chain identification. Wherein the call chain identification may be predetermined by a technician.
In this embodiment, the execution main body may first connect the obtained abnormal operation logs based on the hierarchy number to generate at least one initial call chain, and then may directly determine the generated at least one initial call chain as the at least one call chain, or may process each generated initial call chain and determine the processed at least one initial call chain as the at least one call chain.
It can be understood that, when the obtained abnormal operation logs have different hierarchy numbers, the execution main body may directly connect the obtained abnormal operation logs based on the hierarchy numbers to generate a call chain; when the obtained abnormal operation logs include at least two abnormal operation logs with the same hierarchy number, the execution main body may first determine, based on a preset calling chain identifier, a calling chain to which the abnormal operation logs with the same hierarchy number belong, and then connect the abnormal operation logs belonging to the same calling chain based on the hierarchy number, respectively, to obtain at least two calling chains.
As an example, the obtained abnormal operation log includes A, B, C, D. The level numbers of the abnormal operation logs are respectively a (level 1), B (level 1), C (level 2) and D (level 2), the abnormal operation log a and the abnormal operation log C have the same calling chain identifier, and the abnormal operation log B and the abnormal operation log D have the same calling chain identifier. Here, the smaller the value of the hierarchy number, the lower the token hierarchy (i.e., the operation corresponding thereto is preferentially performed). Based on the hierarchy number and the call chain identification, the execution body may generate the following two initial call chains: A-C; B-D. Furthermore, the execution body may directly determine the two generated initial call chains as the two call chains, or may separately process the two generated initial call chains and determine the two processed initial call chains as the two call chains.
In some optional implementations of this embodiment, the executing body may further generate at least one call chain by: first, the execution subject may sequentially connect the obtained abnormal operation logs based on the hierarchy number to generate at least one initial call chain. Then, for an initial call chain of the at least one initial call chain, the execution main body may determine whether the initial call chain includes a missing operation log based on a preset call chain, obtain the missing operation log of the initial call chain in response to determining that the initial call chain includes the missing operation log, and add the obtained operation log into the initial call chain to obtain the call chain. Wherein, the missing operation log is a non-abnormal operation log. The preset call chain may be a call chain preset by a technician and used as a comparison template, and the preset call chain may include all operation logs corresponding to corresponding modules of the distributed system.
In this embodiment, the execution subject may determine an exception request belonging to a preset historical time period in the target exception request as a candidate exception request, and obtain an operation log set corresponding to the candidate exception request. The preset historical time period may be a time period preset by a technician. The abnormal request belonging to the preset historical time period is the abnormal request initiated in the preset historical time period. Here, the exception request initiated within the preset historical time period in the target exception request may include at least one time, that is, the candidate exception request may include at least one time. Correspondingly, the operation log set corresponding to the obtained candidate exception request may include at least one group of operation logs, and each group of operation logs corresponds to one candidate exception request. It should be noted that the acquired operation log set may include an abnormal operation log and a non-abnormal operation log.
In this embodiment, for a call chain in at least one call chain, the execution main body may determine the number of abnormal operation logs in the call chain included in the operation log set of the candidate exception request, and determine the number of times of exception occurrence of the call chain for the candidate exception request based on the determined number.
It is to be understood that, for each candidate exception request, the execution subject may determine the call chain causing the exception of the candidate exception request by determining the source of the exception operation log included in the group of operation logs corresponding to the candidate exception request.
In this embodiment, the execution main body may determine, by various methods, the number of times that each call chain in the at least one call chain has an exception for a candidate exception request within a preset historical time period, based on an exception operation log included in an operation log set of the candidate exception request.
Specifically, as an example, for a call chain in at least one call chain, the execution subject may determine, by the following steps, a number of times that an exception occurs in the call chain for a candidate exception request: first, the execution subject may select an abnormal operation log as a reference object from the abnormal operation logs included in the call chain. Then, the execution subject may determine the number of the reference objects included in the operation log set of the candidate exception request, and further determine the determined number as the number of times that the exception occurs in the call chain. It should be noted that the execution main body may randomly select the abnormal operation log as the reference object, or may select the abnormal operation log as the reference object according to a manner preset by a technician (for example, select the abnormal operation log located at the first stage of the call chain).
Optionally, the execution main body may further determine, for the candidate exception request, the number of times that the call chain is abnormal, by: first, the execution subject may determine the number of abnormal operation logs included in the call chain, and determine the number as the first number. Then, the execution subject may determine the number of abnormal operation logs in the call chain included in the operation log set of the candidate abnormal request, and determine the number as the second number. Finally, the execution main body may perform quotient calculation on the quantity value of the second quantity and the quantity value of the first quantity, and determine a quotient calculation result as the number of times of occurrence of the exception in the call chain for the candidate exception operation.
Based on the determined number of times, a target call chain is determined, step 205.
In this embodiment, the execution subject may determine the target call chain based on the number of times determined in step 204. The target call chain may be a call chain that plays a main role in an exception condition of the target exception request in the at least one call chain (i.e., the exception of the target call chain is a main cause of an exception of the target exception request).
In this embodiment, the execution subject may determine the target call chain by various methods based on the determined number of times that each call chain is abnormal. Specifically, as an example, the execution subject may directly determine, as a target call chain, a call chain with the largest number of times of occurrence of an exception in the at least one call chain; or, the execution main body may respectively perform quotient calculation on the number of times that the determined call chains are abnormal and the number of times that the candidate abnormal request is in the preset time period, obtain an influence coefficient for representing the degree of influence of each call chain on the candidate abnormal request, and further determine the call chain corresponding to the maximum influence coefficient as the target call chain.
With continued reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the method for processing information according to the present embodiment. In the application scenario of fig. 3, server 301 may first determine that the target exception request is an anomalous posted request 302. Then, the server 301 may obtain an abnormal operation log corresponding to the abnormal posting request 302, including a database call log 303, a content audit log 304, and a content upload log 305, where the abnormal operation log may include a preset level number, and the level number may be used to represent a level relationship between the abnormal operation logs. Next, the server 301 may connect the database call log 303, the content audit log 304, and the content upload log 305 based on the hierarchy number, and generate a call chain 306 and a call chain 307; then, the server 301 may determine, as the candidate exception request 308, a request belonging to a historical time period from 5/2017 to 5/6/2017 in the exception posted request 302, and obtain an operation log set 309 corresponding to the candidate exception request 308; next, for the call chain 306 and the call chain 307, the server 301 may determine the number, specifically, the number 310 and the number 311, of the abnormal operation logs in each call chain included in the operation log set 309 of the candidate abnormal request, respectively, and the server 301 may determine the number 312 of times of abnormality occurrence of the call chain 306 and the number 313 of times of abnormality occurrence of the call chain 307 for the candidate abnormal request 308 based on the determined number 310 and the number 311. Finally, the server 301 may determine the target call chain 314 based on the determined times 312 and 313.
The method provided by the above embodiment of the present application, by obtaining an abnormal operation log corresponding to a target abnormal request, where the abnormal operation log includes a preset hierarchy number, and then connecting the obtained abnormal operation logs based on the hierarchy number, generating at least one call chain, determining an abnormal request in the target abnormal request that belongs to a preset historical time period as a candidate abnormal request, and obtaining an operation log set corresponding to the candidate abnormal request, for a call chain in the at least one call chain, determining the number of abnormal operation logs in the call chain included in the operation log set of the candidate abnormal request, and determining the number of times of abnormality occurrence of the candidate abnormal request for the candidate abnormal request based on the determined number, determining the target call chain based on the determined number of times, so as to request the corresponding abnormal operation log through the abnormal request, the analysis and processing of the abnormal reason aiming at the abnormal request are realized, and the information processing efficiency is improved.
With further reference to FIG. 4, a flow 400 of yet another embodiment of a method for processing information is shown. The flow 400 of the method for processing information includes the steps of:
In this embodiment, an execution subject (for example, a server shown in fig. 1) of the method for processing information may obtain an abnormal operation log corresponding to the target abnormal request from a local or communication-connected electronic device (for example, a terminal device shown in fig. 1) through a wired connection manner or a wireless connection manner.
And 402, connecting the acquired abnormal operation logs based on the hierarchy number to generate at least one calling chain.
In this embodiment, the execution subject may connect the obtained abnormal operation logs based on the hierarchy number to generate at least one call chain.
In this embodiment, the execution subject may determine an exception request belonging to a preset historical time period in the target exception request as a candidate exception request, and obtain an operation log set corresponding to the candidate exception request.
In this embodiment, for a call chain in at least one call chain, the execution main body may determine the number of abnormal operation logs in the call chain included in the operation log set of the candidate exception request, and determine the number of times of exception occurrence of the call chain for the candidate exception request based on the determined number.
Based on the determined number of times, a target call chain is determined, step 405.
In this embodiment, the execution principal may determine the target call chain based on the number of times determined in step 404. The target call chain may be a call chain that plays a main role in an exception condition of the target exception request in the at least one call chain (i.e., the exception of the target call chain is a main cause of an exception of the target exception request).
At step 406, an abnormal oplog at the tail level of the target call chain is determined.
In this embodiment, based on the target call chain determined in step 405, the execution subject may determine an abnormal operation log located at the tail stage of the target call chain.
For example, the target call chain may be "a-C", and the execution subject may determine that the abnormal operation log located at the tail stage of the target call chain is "C".
In this embodiment, based on the abnormal operation log determined in step 406, the execution subject may determine the operation corresponding to the determined abnormal operation log as the target operation. The target operation may be an operation that plays a main role in an abnormal situation of the target abnormal request in an operation for responding to the target abnormal request (i.e., the abnormality of the target operation is a main cause of the abnormality of the target abnormal request).
In some optional implementation manners of this embodiment, after determining the operation corresponding to the determined abnormal operation log as the target operation, the execution main body may further perform the following steps: first, the execution body may determine a network protocol address for executing the call operation in response to determining that the target operation is the call operation. Then, the executing body may divide the target call chain into at least two target sub-call chains based on the at least two network protocol addresses in response to determining that the network protocol addresses for executing the call operation include at least two. Then, the execution main body may determine the number of times that each target sub-call chain is abnormal for the candidate abnormal request, and generate result information indicating the reason of the abnormality of the target abnormal request based on the determined number of times that the target sub-call chain is abnormal. Wherein the result information may include, but is not limited to, at least one of: numbers, words, symbols, pictures.
In this implementation, the execution subject may divide the target call chain into at least two target sub-call chains. Specifically, as an example, the target call chain is "A-C". Wherein "C" corresponds to a call operation, specifically calling network protocol address C1Corresponding electronic device and network protocol address C2The corresponding electronic device, further, the execution subject can divide the target call chain "A-C" into the target sub call chain "A-C1"and" A-C2”。
As a specific implementation manner, the execution subject may generate result information indicating an exception reason of the target exception request by the following steps based on the determined number of times that the target sub-call chain has an exception: first, the execution main body may determine whether the number of times of occurrence of the exception of each target sub-call chain is greater than a preset number of times. And in response to the fact that the number of times of abnormity of a certain target sub-call chain is larger than the preset number of times, determining the abnormity of the electronic equipment to which the network protocol address corresponding to the target sub-call chain belongs as the abnormity reason of the target abnormity request. Finally, the execution subject may generate result information for characterizing an anomaly of the electronic device to which the network protocol address corresponding to the target sub-call chain belongs.
As another specific implementation manner, in response to determining that the number of times of occurrence of the exception of the at least two target sub-call chains is less than or equal to a preset number, the execution main body may generate result information indicating an exception reason of the target exception request based on an error code in an operation log corresponding to the target operation. It should be noted that the abnormal operation log of the abnormal call operation may include an error code, and the error code may be used to characterize an abnormal reason of the abnormal call operation. The abnormal reasons may include connection failure, failure to acquire data, request parameter error, etc. Here, the correspondence relationship between the error code and the cause of the abnormality may be set in advance by a technician.
In some optional implementation manners of this embodiment, in response to determining that the target operation is not a call operation, the execution main body may further determine, as result information indicating an exception reason of the target exception request, an exception operation log corresponding to the target operation.
As can be seen from fig. 4, the flow 400 of the method for processing information in the present embodiment highlights the step of determining the target operation compared to the corresponding embodiment of fig. 2. Therefore, the scheme described in the embodiment can refine the reason causing the target abnormal request abnormality based on the abnormal operation log included in the call chain, thereby realizing more comprehensive information processing.
With further reference to fig. 5, as an implementation of the methods shown in the above-mentioned figures, the present application provides an embodiment of an apparatus for processing information, which corresponds to the method embodiment shown in fig. 2, and which is particularly applicable in various electronic devices.
As shown in fig. 5, the apparatus 500 for processing information of the present embodiment includes: a log acquisition unit 501, a log connection unit 502, a request determination unit 503, a number of times determination unit 504, and a call chain determination unit 505. The log obtaining unit 501 is configured to obtain an abnormal operation log corresponding to a target abnormal request, where the abnormal operation log includes a preset hierarchy number, and the hierarchy number is used to represent a hierarchical relationship between the abnormal operation logs; the log connection unit 502 is configured to connect the acquired abnormal operation logs based on the hierarchy number, generating at least one call chain; the request determining unit 503 is configured to determine an exception request belonging to a preset historical time period in the target exception requests as a candidate exception request, and obtain an operation log set corresponding to the candidate exception request; the number-of-times determining unit 504 is configured to determine, for a call chain of the at least one call chain, the number of abnormal operation logs in the call chain included in the operation log set of the candidate exception request, and determine, based on the determined number, the number of times that the exception occurs in the call chain for the candidate exception request; the call chain determination unit 505 is configured to determine a target call chain based on the determined number of times.
In this embodiment, the log obtaining unit 501 of the apparatus 500 for processing information may obtain the abnormal operation log corresponding to the target abnormal request from a local or communication-connected electronic device (e.g., the terminal device shown in fig. 1) through a wired connection manner or a wireless connection manner.
The target abnormal request is an abnormal request for determining the reason of the abnormality, and the target abnormal request may be a certain type of request initiated by a user. The abnormal request is a request for which a preset operation for responding to the request is not normally performed. Here, an operation that cannot be normally performed is determined as an abnormal operation. When the execution main body or other electronic devices execute abnormal operations, an abnormal operation log is generated, wherein the abnormal operation log comprises an abnormal identifier used for representing log abnormality, and further, the execution main body can acquire the abnormal operation log corresponding to the target abnormal request based on the abnormal identifier. The obtained abnormal operation log may be all or part of the abnormal operation log corresponding to the target abnormal request stored in advance. The anomaly identification may be an identification preset by a technician.
In the present embodiment, the abnormal operation log includes a hierarchy number set in advance. The hierarchical number may be represented in various forms, and may be used to characterize the hierarchical relationship between the abnormal operation logs. It can be understood that the hierarchical relationship between the operation logs can be used to characterize the execution sequence of the operations corresponding to the operation logs.
In this embodiment, the log connection unit 502 may connect the acquired abnormal operation logs based on the hierarchy number to generate at least one call chain. The call chain can be used for characterizing the execution sequence of the abnormal operation corresponding to the included abnormal operation log. Specifically, for each call chain in at least one call chain, the abnormal operation corresponding to the abnormal operation log located at the first level of the call chain is executed in preference to the abnormal operation corresponding to other abnormal operation logs; and the abnormal operation corresponding to the abnormal operation log at the tail stage of the calling chain is lagged behind the abnormal operation corresponding to other abnormal operation logs. Here, the first level of the call chain is the lowest level (corresponding to the first executed operation) and the last level of the call chain is the highest level (corresponding to the last executed operation).
It should be noted that a call chain may correspond to a separate module in the distributed system. Oplogs belonging to the same call chain may include the same call chain identification. Wherein the call chain identification may be predetermined by a technician.
In this embodiment, the request determining unit 503 may determine an exception request belonging to a preset history time period in the target exception request as a candidate exception request, and acquire an operation log set corresponding to the candidate exception request. The preset historical time period may be a time period preset by a technician. The abnormal request belonging to the preset historical time period is the abnormal request initiated in the preset historical time period. Here, the exception request initiated within the preset historical time period in the target exception request may include at least one time, that is, the candidate exception request may include at least one time. Correspondingly, the operation log set corresponding to the obtained candidate exception request may include at least one group of operation logs, and each group of operation logs corresponds to one candidate exception request. It should be noted that the acquired operation log set may include an abnormal operation log and a non-abnormal operation log.
In this embodiment, for a call chain of at least one call chain, the number-of-times determining unit 504 may determine the number of abnormal operation logs in the call chain included in the operation log set of the candidate exception request, and determine the number of times that the exception occurs in the call chain for the candidate exception request based on the determined number.
In the present embodiment, based on the number of times determined by the number-of-times determining unit 504, the call chain determining unit 505 may determine the target call chain. The target call chain may be a call chain that plays a main role in an exception condition of the target exception request in the at least one call chain (i.e., the exception of the target call chain is a main cause of an exception of the target exception request).
In some optional implementations of this embodiment, the apparatus 500 may further include: a log determining unit (not shown in the figure) configured to determine an abnormal operation log located at a tail stage of the target call chain; an operation determination unit (not shown in the figure) configured to determine an operation corresponding to the determined abnormal operation log as a target operation.
In some optional implementations of this embodiment, the apparatus 500 may further include: an address determination unit (not shown in the figure) configured to determine a network protocol address for performing a call operation in response to determining that the target operation is the call operation; a call chain dividing unit (not shown in the figure) configured to divide the target call chain into at least two target sub-call chains based on at least two network protocol addresses in response to determining that the network protocol addresses for performing the call operation include at least two; and an information generating unit (not shown in the figure) configured to determine the number of times that each target sub-call chain is abnormal for the candidate abnormal request, and generate result information indicating the abnormal reason of the target abnormal request based on the determined number of times that the target sub-call chain is abnormal.
In some optional implementations of this embodiment, the apparatus 500 may further include: and an information determination unit (not shown in the figure) configured to determine, in response to a determination that the target operation is not the call operation, an abnormal operation log corresponding to the target operation as result information indicating an abnormal cause of the target abnormal request.
In some optional implementations of this embodiment, the log connection unit 502 may include: a log connection module (not shown in the figure) configured to sequentially connect the obtained abnormal operation logs based on the hierarchy number to generate at least one initial call chain; a log padding module (not shown in the figure) configured to determine, for an initial call chain of the at least one initial call chain, whether the initial call chain includes a missing operation log based on a preset call chain; in response to determining that the initial call chain includes a missing oplog, obtaining the oplog that the initial call chain misses, and supplementing the obtained oplog into the initial call chain, obtaining a call chain.
The apparatus 500 provided by the above-mentioned embodiment of the present application acquires, by the log acquiring unit 501, an abnormal operation log corresponding to a target abnormal request, where the abnormal operation log includes a preset hierarchy number, the log connecting unit 502 connects the acquired abnormal operation logs based on the hierarchy number to generate at least one call chain, the request determining unit 503 determines an abnormal request in the target abnormal request that belongs to a preset history time period as a candidate abnormal request, and acquires an operation log set corresponding to the candidate abnormal request, the number determining unit 504 determines, for a call chain in the at least one call chain, the number of abnormal operation logs in the call chain included in the operation log set of the candidate abnormal request, and determines, based on the determined number, the number of times of occurrence of an abnormality in the candidate abnormal request for the call chain, the call chain determining unit 505 determines the target call chain based on the determined number of times, so that analysis and processing of an abnormal reason for the abnormal request are realized through the abnormal operation log corresponding to the abnormal request, and the efficiency of information processing is improved.
Referring now to FIG. 6, shown is a block diagram of a computer system 600 suitable for use in implementing a server according to embodiments of the present application. The server shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU)601 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the system 600 are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted in the storage section 608 as necessary.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The computer program performs the above-described functions defined in the method of the present application when executed by a Central Processing Unit (CPU) 601. It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a log obtaining unit, a log connecting unit, a request determining unit, a number determining unit, and a call chain determining unit. The names of these units do not in some cases constitute a limitation on the unit itself, and for example, the log obtaining unit may also be described as a "unit that obtains an abnormal operation log corresponding to the target abnormal request".
As another aspect, the present application also provides a computer-readable medium, which may be contained in the server described in the above embodiments; or may exist separately and not be assembled into the server. The computer readable medium carries one or more programs which, when executed by the server, cause the server to: acquiring an abnormal operation log corresponding to the target abnormal request, wherein the abnormal operation log comprises a preset hierarchy number, and the hierarchy number is used for representing the hierarchy relation among the abnormal operation logs; connecting the obtained abnormal operation logs based on the hierarchy number to generate at least one calling chain; determining an abnormal request belonging to a preset historical time period in the target abnormal request as a candidate abnormal request, and acquiring an operation log set corresponding to the candidate abnormal request; for a call chain in at least one call chain, determining the number of abnormal operation logs in the call chain, which are included in an operation log set of a candidate abnormal request, and determining the number of times of abnormity of the call chain for the candidate abnormal request based on the determined number; based on the determined number of times, a target call chain is determined.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (12)
1. A method for processing information, comprising:
acquiring an abnormal operation log corresponding to a target abnormal request, wherein the abnormal operation log comprises a preset hierarchy number, and the hierarchy number is used for representing the hierarchy relation among the abnormal operation logs;
connecting the obtained abnormal operation logs based on the hierarchy number to generate at least one calling chain;
determining an abnormal request belonging to a preset historical time period in the target abnormal request as a candidate abnormal request, and acquiring an operation log set corresponding to the candidate abnormal request;
for a call chain in the at least one call chain, determining the number of abnormal operation logs in the call chain, which are included in an operation log set of a candidate abnormal request, and determining the number of times of abnormity of the call chain for the candidate abnormal request based on the determined number;
based on the determined number of times, a target call chain is determined.
2. The method of claim 1, wherein after the determining a target call chain, the method further comprises:
determining an abnormal operation log located at a tail stage of the target call chain, wherein the tail stage corresponds to a last executed operation;
and determining the operation corresponding to the determined abnormal operation log as a target operation.
3. The method of claim 2, wherein after determining the operation corresponding to the determined abnormal operation log as a target operation, the method further comprises:
in response to determining that the target operation is a call operation, determining a network protocol address for performing the call operation;
in response to determining that the network protocol addresses for performing the call operation include at least two, dividing the target call chain into at least two target sub-call chains based on the at least two network protocol addresses;
determining the times of abnormity of each target sub-call chain aiming at the candidate abnormity request, and generating result information used for indicating the abnormity reason of the target abnormity request based on the determined times of abnormity of the target sub-call chain.
4. The method of claim 2, wherein the method further comprises:
and in response to determining that the target operation is not a call operation, determining an abnormal operation log corresponding to the target operation as result information indicating an abnormal reason of the target abnormal request.
5. The method according to one of claims 1 to 4, wherein the concatenating the obtained abnormal operation logs based on the hierarchy number to generate at least one call chain comprises:
based on the hierarchy number, sequentially connecting the acquired abnormal operation logs to generate at least one initial call chain;
for an initial call chain in the at least one initial call chain, determining whether the initial call chain comprises a missing operation log based on a preset call chain; in response to determining that the initial call chain includes a missing oplog, obtaining the oplog that the initial call chain misses, and supplementing the obtained oplog into the initial call chain, obtaining a call chain.
6. An apparatus for processing information, comprising:
the log obtaining unit is configured to obtain an abnormal operation log corresponding to a target abnormal request, wherein the abnormal operation log comprises preset hierarchy numbers, and the hierarchy numbers are used for representing the hierarchy relation among the abnormal operation logs;
a log connection unit configured to connect the acquired abnormal operation logs based on the hierarchy number, and generate at least one call chain;
the request determining unit is configured to determine an abnormal request which belongs to a preset historical time period in the target abnormal requests as a candidate abnormal request, and acquire an operation log set corresponding to the candidate abnormal request;
a number determination unit configured to determine, for a call chain of the at least one call chain, a number of abnormal operation logs in the call chain included in an operation log set of a candidate abnormal request, and determine, based on the determined number, a number of times an abnormality occurs in the call chain for the candidate abnormal request;
a call chain determination unit configured to determine a target call chain based on the determined number of times.
7. The apparatus of claim 6, wherein the apparatus further comprises:
a log determining unit configured to determine an abnormal operation log located at a tail stage of the target call chain, wherein the tail stage corresponds to a last executed operation;
an operation determination unit configured to determine an operation corresponding to the determined abnormal operation log as a target operation.
8. The apparatus of claim 7, wherein the apparatus further comprises:
an address determination unit configured to determine a network protocol address for performing the call operation in response to determining that the target operation is a call operation;
a call chain dividing unit configured to divide the target call chain into at least two target sub-call chains based on at least two network protocol addresses in response to determining that the network protocol addresses for performing the call operation include at least two;
an information generating unit configured to determine the number of times each target sub-call chain is abnormal for the candidate abnormal request, and generate result information indicating the reason of abnormality of the target abnormal request based on the determined number of times each target sub-call chain is abnormal.
9. The apparatus of claim 7, wherein the apparatus further comprises:
an information determination unit configured to determine, in response to determining that the target operation is not a call operation, an abnormal operation log corresponding to the target operation as result information indicating an abnormal cause of the target abnormal request.
10. The apparatus according to one of claims 6-9, wherein the log connection unit comprises:
the log connection module is configured to sequentially connect the acquired abnormal operation logs based on the hierarchy number to generate at least one initial call chain;
a log padding module configured to determine, for an initial call chain of the at least one initial call chain, whether the initial call chain includes a missing operation log based on a preset call chain; in response to determining that the initial call chain includes a missing oplog, obtaining the oplog that the initial call chain misses, and supplementing the obtained oplog into the initial call chain, obtaining a call chain.
11. A server, comprising:
one or more processors;
a storage device having one or more programs stored thereon,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-5.
12. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810660506.3A CN108933695B (en) | 2018-06-25 | 2018-06-25 | Method and apparatus for processing information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810660506.3A CN108933695B (en) | 2018-06-25 | 2018-06-25 | Method and apparatus for processing information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108933695A CN108933695A (en) | 2018-12-04 |
| CN108933695B true CN108933695B (en) | 2021-05-25 |
Family
ID=64446981
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810660506.3A Active CN108933695B (en) | 2018-06-25 | 2018-06-25 | Method and apparatus for processing information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108933695B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109933508B (en) * | 2019-03-25 | 2023-02-24 | 北京百度网讯科技有限公司 | Method and apparatus for transmitting information |
| CN110223173A (en) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Trade link abnormality eliminating method and relevant device |
| CN110647447B (en) * | 2019-08-01 | 2023-04-14 | 百度时代网络技术（北京）有限公司 | Abnormal instance detection method, device, equipment and medium for distributed system |
| CN111143304B (en) * | 2019-11-20 | 2023-09-29 | 杭州端点网络科技有限公司 | Micro-service system exception log analysis method based on request link |
| CN112882854B (en) * | 2019-11-29 | 2024-06-11 | 阿里巴巴集团控股有限公司 | Method and device for processing request exception |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9203740B2 (en) * | 2013-07-18 | 2015-12-01 | Globalfoundries Inc. | Automated network fault location |
| CN105721187B (en) * | 2014-12-03 | 2018-12-07 | 中国移动通信集团江苏有限公司 | A kind of traffic failure diagnostic method and device |
| CN105591821B (en) * | 2016-01-06 | 2020-06-30 | 北京京东尚科信息技术有限公司 | Monitoring system and service system |
| CN105978723A (en) * | 2016-05-11 | 2016-09-28 | 广州唯品会信息科技有限公司 | Network information management method and device |
| CN106294132B (en) * | 2016-07-29 | 2019-02-01 | 深圳创维－Rgb电子有限公司 | A kind of method and device managing log |
| CN107071084B (en) * | 2017-04-01 | 2019-07-26 | 北京神州绿盟信息安全科技股份有限公司 | A kind of evaluation method and device of DNS |
-
2018
- 2018-06-25 CN CN201810660506.3A patent/CN108933695B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN108933695A (en) | 2018-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108933695B (en) | Method and apparatus for processing information | |
| CN108880931B (en) | Method and apparatus for outputting information | |
| CN111368013B (en) | Unified identification method, system, equipment and storage medium based on multiple accounts | |
| CN109901987B (en) | Method and device for generating test data | |
| CN109359194B (en) | Method and apparatus for predicting information categories | |
| CN109614327B (en) | Method and apparatus for outputting information | |
| CN108011949B (en) | Method and apparatus for acquiring data | |
| CN110737655B (en) | Method and device for reporting data | |
| CN109885564B (en) | Method and apparatus for transmitting information | |
| CN112947919A (en) | Method and device for constructing service model and processing service request | |
| CN113822745A (en) | Article display method and device | |
| CN107229565B (en) | Test method and device | |
| CN109597819B (en) | Method and apparatus for updating a database | |
| CN113157911A (en) | Service verification method and device | |
| CN108933802B (en) | Method and apparatus for monitoring operation | |
| CN108804442B (en) | Serial number generation method and device | |
| CN115454956A (en) | Log generation method and device, electronic equipment and storage medium | |
| CN111460273B (en) | Information pushing method and device | |
| CN109889402B (en) | Method and apparatus for generating information | |
| CN109308299B (en) | Method and apparatus for searching information | |
| CN114428815A (en) | Data storage method and device, electronic equipment and computer readable medium | |
| CN108898446B (en) | Method and apparatus for outputting information | |
| CN111414566A (en) | Method and device for pushing information | |
| WO2020078049A1 (en) | User information processing method and device, server, and readable medium | |
| CN108287792B (en) | Method and apparatus for outputting information |
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 |