CN111343031B - Method and device for determining network fault - Google Patents
Method and device for determining network fault Download PDFInfo
- Publication number
- CN111343031B CN111343031B CN202010247690.6A CN202010247690A CN111343031B CN 111343031 B CN111343031 B CN 111343031B CN 202010247690 A CN202010247690 A CN 202010247690A CN 111343031 B CN111343031 B CN 111343031B
- Authority
- CN
- China
- Prior art keywords
- path
- path detection
- detection message
- information
- syslog
- 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
Abstract
The present disclosure provides a method and a device for determining a network fault, wherein the method includes: generating a path detection message, wherein the path detection message comprises first node information and tail node information of a path to be detected; sending the path detection message to the head node; receiving a system log syslog sent by a network node, wherein the syslog comprises path information of the path detection message received by the network node; and determining that the path to be detected has a fault according to the path information included in the syslog fed back by the network node. According to the method and the device, the path information passed by the path detection message is sent through the system log syslog, so that for equipment (a controller or a server provided with network management software) receiving the path information, an openflow protocol does not need to be configured, and the compatibility of the system is enhanced.
Description
Technical Field
The present disclosure relates to network communication technologies, and in particular, to a method and an apparatus for determining a network fault.
Background
With the advance of human beings to the internet era, the network scale becomes more and more huge and more important, and the problem of quickly troubleshooting the network becomes more and more critical, and the method becomes more and more urgent for operation and maintenance personnel to quickly troubleshoot fault occurrence points.
In the existing technology for troubleshooting network failures, a path detection message based on an openflow protocol is generally sent to a controller through a network node, and the controller determines an actual transmission path of the message and determines whether a failure exists based on a result of the path detection message.
It can be seen that the prior art requires that the controller must be configured with an openflow protocol stack.
Disclosure of Invention
The disclosure provides a method for determining a network fault, which is used for solving the problem of protocol incompatibility possibly caused by the fact that a controller needs to configure an openflow protocol stack in the prior art.
A first aspect of the present disclosure provides a method for determining a network fault, where the method includes:
generating a path detection message, wherein the path detection message comprises first node information and tail node information of a path to be detected;
sending the path detection message to the head node;
receiving a system log syslog sent by a network node, wherein the syslog comprises path information of the path detection message received by the network node; wherein the path information includes: an entry index identifier of the path detection message, a sequence identifier of the path detection message, and an identifier of the forwarding times of the path detection message;
and determining that the path to be detected has a fault according to the path information included in the syslog fed back by the network node.
Optionally, the method further includes: and issuing a flow table to a network node through a netconf protocol, wherein the flow table comprises a matching item and an action item, the matching item comprises identification information of a path detection message, and the action item comprises path information of the path detection message sent through a system log syslog.
Optionally, the method further includes:
and issuing a plurality of path detection messages aiming at the same path to be detected, and determining network topology information according to different paths passed by the plurality of path detection messages.
The second aspect of the present disclosure also provides a method for determining a network fault, which is applied to a network node in a network, and the method includes:
when the received message is identified to be a path detection message;
determining the path information of the path detection message;
the path information of the path detection message is sent to a controller through a system log syslog;
and forwarding the path detection message to the next hop network equipment.
Optionally, before receiving the path detection packet, the method further includes:
the method comprises the steps of receiving a flow table issued by a controller through a netconf protocol, wherein the flow table comprises a matching item and an action item, the matching item comprises identification information of a path detection message, and the action item comprises path information of the path detection message sent through a system log syslog.
A third aspect of the present disclosure is directed to an apparatus for determining a network failure, the apparatus comprising:
the system comprises a generating module, a detecting module and a processing module, wherein the generating module is used for generating a path detection message which comprises first node information and tail node information of a path to be detected;
a sending module, configured to send the path detection packet to the head node;
the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving a system log syslog sent by a network node, and the syslog comprises path information of the path detection message received by the network node; wherein the path information includes: an entry index identifier of the path detection message, a sequence identifier of the path detection message, and an identifier of the forwarding times of the path detection message;
the determining module is used for determining that the path to be detected has a fault according to the path information included in the syslog fed back by the network node, and the sending module is also used for sending a flow table to the network node through a netconf protocol, wherein the flow table comprises a matching item and an action item, the matching item comprises identification information of a path detection message, and the action item comprises the path information of the path detection message sent through a system log syslog.
Optionally, the sending module is further configured to issue multiple path detection messages for the same path to be detected, and determine network topology information according to different paths through which the multiple path detection messages pass.
The fourth aspect of the present disclosure also provides an apparatus for determining a network fault, including:
the identification module is used for determining the path information of the path detection message when identifying that the received message is the path detection message;
the uploading module is used for uploading the path information of the path detection message to the controller through a system log syslog;
and the forwarding module is used for forwarding the path detection message to the next hop network equipment.
Optionally, the apparatus further includes a receiving module, where the receiving module is configured to receive the path detection packet, and is configured to receive a flow table issued by a controller through a netconf protocol before receiving the path detection packet, where the flow table includes a matching item and an action item, the matching item includes identification information of the path detection packet, and the action item includes path information of the path detection packet sent through a system log syslog.
According to the method and the device, the path information passed by the path detection message is sent through the system log syslog, so that for equipment (a controller or a server provided with network management software) receiving the path information, an openflow protocol does not need to be configured, and the compatibility of the system is enhanced.
Drawings
FIG. 1 is a flowchart of a method provided in accordance with an embodiment of the present invention;
FIG. 2 is a flowchart of a method provided in a second embodiment of the present invention;
FIG. 3 is a diagram illustrating a structure of an apparatus according to a third embodiment of the present invention;
fig. 4 is a structural diagram of an apparatus according to a fourth embodiment of the present invention.
Detailed Description
Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers can indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
In the prior art, if network management software is installed in a controller or exists independently in the controller, the network management software is used as an independent component, and if a transmission path of a message is to be determined to troubleshoot a fault and the like, an openflow protocol must be configured, which easily causes a problem in the compatibility of the system.
In order to solve the above problem, the present disclosure provides a method for determining a network fault, in which path information passed by a path probe message is sent through a system log syslog, so that for a device (a controller or a server installed with network management software) receiving the path information, an openflow protocol does not need to be configured, and compatibility of the system is enhanced.
Example one
In order to better describe the determination method of network failure provided by the present disclosure, the present disclosure is illustrated with a specific example.
Fig. 1 is a flowchart of a method for determining a network fault according to the present disclosure, where the method for determining a network fault may be applied to a controller or a server installed with network management software (referred to as network management software), where the network management software may be used to draw a network topology, monitor a network, and the like. Specifically, as shown in fig. 1, the method includes:
the path detection message may adopt a format of a path detection message in the prior art, for example, the path detection message includes a source IP address, a destination IP address, a sequence identifier, and the like. Since there are multiple path detection possibilities, the sequence identifier is used to identify the number of path detections, so as to avoid confusion of multiple path detections. The source IP address and the destination IP address are respectively used for indicating a head node and a tail node of the path to be detected.
And 204, sending the path detection message to the head node.
In an alternative embodiment, the required head node may be determined by querying a Management Information Base MIB (Management Information Base, abbreviated as MIB), for example, by determining a network node supporting the netconf protocol as the head node.
Specifically, the entry index identifier of the path probing packet may be used to determine the physical link information of the network node. The number of times of forwarding the path detection packet may be used to represent the number of network nodes to which the path detection packet is forwarded, for example, 1 may be added to the number of times of forwarding the path detection packet per node, and certainly, the number of network devices to be passed through in the detection path is fixed, for example, a path to be detected needs to pass through 10 network nodes, and the default number of times of forwarding the packet may be initially 10, and 1 is subtracted per device to be passed through.
And step 208, determining a fault node according to the path information included in the syslog fed back by the network node.
Theoretically, if the network nodes work normally, each network node on the path to be detected sends syslog to the controller; and if the tail node of the path to be detected sends the path information of the syslog not including the path information of the path detection message to the syslog, determining that the path to be detected has a fault.
In an alternative embodiment, after determining that the path to be detected has a fault, the controller may determine the faulty node according to the path information included in the syslog fed back by the network node and the pre-collected network topology information. The controller receives the message of the syslog and determines a unique uplink and a network node according to the IP address and the interface index ID of the path detection message and the pre-collected network topology information, and the physical connection condition of the network equipment in the path to be detected can be completely determined by transmitting the syslog on the network nodes of one node of the equipment.
In this disclosure, the network topology may also be determined according to the path detection message, for example, the controller may issue multiple path detection messages for the same path to be detected, and determine the network topology information according to different paths through which the multiple path detection messages pass.
Generally, the controller may only indicate a head node and a tail node in the path detection message, but does not designate other intermediate network nodes through which the path to be detected passes, and may, for the case that an equivalent path exists, send a plurality of path detection messages to perform detection, and after sufficient times of detection, acquire different paths through which the path detection messages pass, thereby determining or updating network topology information.
If the controller is not configured with the openflow protocol and the network node supports the openflow protocol, in order to indicate the network node to send the path information of the path detection message through the syslog, the controller may send a flow table to the network node through the netconf protocol, where the sent flow table includes a matching item and an action item, the matching item includes identification information of the path detection message, and the action item includes the path information of the path detection message sent through the system log syslog. The identification information of the path detection message is used for indicating that the message is the path detection message so as to distinguish the path detection message from other data messages or protocol messages.
Certainly, when the controller is not configured with the openflow protocol and the network node does not support the openflow protocol (or may support the openflow protocol), the controller may instruct the network node to send the path information through the syslog when receiving the path detection packet by issuing a configuration or code instruction to the network node.
In the method for determining the network fault, the controller receives the path information through which the path detection message passes through the system log syslog, so that the controller does not need to configure an openflow protocol, and the compatibility of the system is enhanced.
Example two
Corresponding to the method for determining a network fault in the first embodiment, the network node provided in this embodiment may further perform the following method, and fig. 2 is a flowchart of the method for determining a network fault in the second embodiment of the present disclosure, and as shown in fig. 2, the method includes:
The network node may determine that the received packet is a path detection packet according to the identifier of the path detection packet.
The entry index identifier may be determined based on the entry receiving the path probe packet. After the network node adds 1 to or subtracts 1 from the path detection message forwarding frequency, the network node fills path information such as the entry index identifier, the path detection message forwarding frequency and the like into syslog.
The network node does not affect the forwarding of the path probing message while sending the syslog, and the execution sequence of step 306 and step 304 is not limited.
If the openflow protocol is not configured in the controller and the network node supports the openflow protocol, before the network node receives the path detection message in step, the flow table issued by the controller through the netconf protocol may be received, where the flow table includes a matching item and an action item, the matching item includes identification information of the path detection message, and the action item includes path information of the path detection message sent through the system log syslog.
The flow table in this embodiment is the same as the flow table in the first embodiment, and is not described herein again.
In the method for determining the network fault, the network node sends the path information through which the path detection message passes through the system log syslog, so that the controller does not need to configure an openflow protocol, and the compatibility of the system is enhanced.
EXAMPLE III
The present disclosure also provides a device for determining a network fault, where the device is configured to execute the method provided in the first embodiment, and fig. 3 is a schematic structural diagram of a device for determining a network fault provided in the third embodiment of the present disclosure, and as shown in fig. 3, the device includes:
a generating module 401, configured to generate a path detection message, where the path detection message includes first node information and last node information of a path to be detected;
a sending module 402, configured to send the path detection packet to the head node;
a receiving module 403, configured to receive a system log syslog sent by a network node, where the syslog includes path information of the path detection packet received by the network node; wherein the path information includes: an entry index identifier of the path detection message, a sequence identifier of the path detection message, and an identifier of the forwarding times of the path detection message;
a determining module 404, configured to determine that a path to be detected has a fault according to path information included in the syslog fed back by the network node.
Optionally, the sending module 402 is further configured to issue a flow table to the network node through a netconf protocol, where the flow table includes a matching item and an action item, the matching item includes identification information of the path detection packet, and the action item includes path information of the path detection packet sent through a system log syslog.
Optionally, the sending module 402 is further configured to issue multiple path detection messages for the same path to be detected, and determine network topology information according to different paths through which the multiple path detection messages pass.
According to the device for determining the network fault, the path information passed by the path detection message is received through the system log syslog, so that the device does not need to be configured with an openflow protocol, and the compatibility of the system is enhanced.
Example four
Corresponding to the method provided by the second embodiment, the present disclosure further provides a device for determining a network fault, fig. 4 is a schematic structural diagram of the device for determining a network fault provided by the third embodiment of the present disclosure, and as shown in fig. 4, the device includes:
an identifying module 501, configured to determine path information of a received packet when the received packet is identified as a path detection packet;
a sending module 502, configured to send the path information of the path detection packet to a controller through a system log syslog;
a forwarding module 503, configured to forward the path detection packet to the next hop network device.
Optionally, the apparatus further includes a receiving module (not shown in the figure), where the receiving module is configured to receive the path detection packet, and is configured to receive a flow table issued by a controller through a netconf protocol before receiving the path detection packet, where the flow table includes a matching item and an action item, the matching item includes identification information of the path detection packet, and the action item includes path information of the path detection packet sent through a system log syslog.
In the device for determining a network fault provided by the embodiment of the present disclosure, a network node sends a system log syslog to path information through which a path detection message passes through an uploading module 502, so that a controller does not need to configure an openflow protocol, and the compatibility of a system is enhanced.
Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.
In the embodiments provided in the present disclosure, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to embodiments of the present disclosure. 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.
In addition, functional modules in the embodiments of the present disclosure may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solution of the present disclosure or portions thereof that contribute to the prior art in essence can be embodied in the form of a software product, which is stored in a readable storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present disclosure. And the aforementioned readable storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only exemplary of the present disclosure and should not be taken as limiting the disclosure, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (10)
1. A method for determining a network failure, the method comprising:
generating a path detection message, wherein the path detection message comprises first node information and tail node information of a path to be detected;
sending the path detection message to the head node;
receiving a system log syslog sent by a network node, wherein the syslog comprises path information of the path detection message received by the network node; wherein the path information includes: an entry index identifier of the path detection message, a sequence identifier of the path detection message, and an identifier of the forwarding times of the path detection message;
and determining that the path to be detected has a fault according to the path information included in the syslog fed back by the network node.
2. The method of claim 1, further comprising:
the method comprises the steps of issuing a flow table to a network node through a configuration management netconf protocol, wherein the flow table comprises a matching item and an action item, the matching item comprises identification information of a path detection message, and the action item comprises path information of the path detection message sent through a system log syslog.
3. The method according to claim 1 or 2, characterized in that the method further comprises:
and issuing a plurality of path detection messages aiming at the same path to be detected, and determining network topology information according to different paths passed by the plurality of path detection messages.
4. A method for determining network failure is applied to a network node in a network, and is characterized in that the method comprises the following steps:
when the received message is identified to be a path detection message;
determining the path information of the path detection message;
the path information of the path detection message is sent to a controller through a system log syslog;
and forwarding the path detection message to the next hop network equipment.
5. The method of claim 4, wherein prior to receiving the path probe packet, the method further comprises:
the method comprises the steps of receiving a flow table issued by a controller through a netconf protocol, wherein the flow table comprises a matching item and an action item, the matching item comprises identification information of a path detection message, and the action item comprises path information of the path detection message sent through a system log syslog.
6. An apparatus for determining a network failure, the apparatus comprising:
the system comprises a generating module, a detecting module and a processing module, wherein the generating module is used for generating a path detection message which comprises first node information and tail node information of a path to be detected;
a sending module, configured to send the path detection packet to the head node;
the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving a system log syslog sent by a network node, and the syslog comprises path information of the path detection message received by the network node; wherein the path information includes: an entry index identifier of the path detection message, a sequence identifier of the path detection message, and an identifier of the forwarding times of the path detection message;
and the determining module is used for determining that the path to be detected has a fault according to the path information in the syslog fed back by the network node.
7. The apparatus of claim 6,
the sending module is further configured to issue a flow table to the network node through a netconf protocol, where the flow table includes a matching item and an action item, the matching item includes identification information of the path detection packet, and the action item includes path information of the path detection packet sent through a system log syslog.
8. The apparatus according to claim 6 or 7,
the sending module is further configured to issue multiple path detection messages for the same path to be detected, and determine network topology information according to different paths through which the multiple path detection messages pass.
9. An apparatus for determining a network failure, the apparatus comprising:
the identification module is used for determining the path information of the path detection message when identifying that the received message is the path detection message;
the uploading module is used for uploading the path information of the path detection message to the controller through a system log syslog;
and the forwarding module is used for forwarding the path detection message to the next hop network equipment.
10. The apparatus according to claim 9, further comprising a receiving module, configured to receive the path probe packet, and configured to receive, before receiving the path probe packet, a flow table issued by a controller through a netconf protocol, where the flow table includes a matching item and an action item, the matching item includes identification information of the path probe packet, and the action item includes path information of the path probe packet sent through a system log syslog.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010247690.6A CN111343031B (en) | 2020-03-31 | 2020-03-31 | Method and device for determining network fault |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010247690.6A CN111343031B (en) | 2020-03-31 | 2020-03-31 | Method and device for determining network fault |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111343031A CN111343031A (en) | 2020-06-26 |
| CN111343031B true CN111343031B (en) | 2022-02-22 |
Family
ID=71184511
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010247690.6A Active CN111343031B (en) | 2020-03-31 | 2020-03-31 | Method and device for determining network fault |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111343031B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112653721A (en) * | 2020-08-21 | 2021-04-13 | 广州市昇博电子科技有限公司 | Distributed network transmission and control method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103001811A (en) * | 2012-12-31 | 2013-03-27 | 北京启明星辰信息技术股份有限公司 | Method and device for fault locating |
| CN103401726A (en) * | 2013-07-19 | 2013-11-20 | 华为技术有限公司 | Network path detecting method, device and system |
| CN104796298A (en) * | 2014-01-22 | 2015-07-22 | 杭州华三通信技术有限公司 | SDN (Software Defined Network) network fault analyzing method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6990111B2 (en) * | 2001-05-31 | 2006-01-24 | Agilent Technologies, Inc. | Adaptive path discovery process for routing data packets in a multinode network |
-
2020
- 2020-03-31 CN CN202010247690.6A patent/CN111343031B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103001811A (en) * | 2012-12-31 | 2013-03-27 | 北京启明星辰信息技术股份有限公司 | Method and device for fault locating |
| CN103401726A (en) * | 2013-07-19 | 2013-11-20 | 华为技术有限公司 | Network path detecting method, device and system |
| CN104796298A (en) * | 2014-01-22 | 2015-07-22 | 杭州华三通信技术有限公司 | SDN (Software Defined Network) network fault analyzing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111343031A (en) | 2020-06-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107171883B (en) | Method, device and equipment for detecting forwarding table | |
| CN108111432B (en) | Message forwarding method and device | |
| US7995574B2 (en) | Detection of forwarding problems for external prefixes | |
| US20070140126A1 (en) | Method and system for originating connectivity fault management (CFM) frames on non-CFM aware switches | |
| JP2019129408A (en) | Failure detection method, node device, and communication system | |
| CN106789625B (en) | Loop detection method and device | |
| US8976681B2 (en) | Network system, network management server, and OAM test method | |
| CN109981323B (en) | Method and network equipment for detecting multicast path state of data link layer | |
| US20100094994A1 (en) | Network structure information acquiring method and device | |
| CN103078791A (en) | Method, device and system for processing operation, administration and maintenance (OAM) message | |
| CN112291116A (en) | Link fault detection method and device and network equipment | |
| JP5949035B2 (en) | Network device setting device, setting system, setting method and setting program | |
| CN110650041A (en) | IPRAN network fault positioning method and device | |
| EP3811216A1 (en) | Method and system for assessing network resource failures using passive shared risk resource groups | |
| KR101318156B1 (en) | Method for protection switching in ethernet ring network | |
| CN111343031B (en) | Method and device for determining network fault | |
| CN113114525A (en) | Routing detection method and network equipment | |
| CN108400900B (en) | Message detection, configuration, forwarding and statistical method and device, controller and system | |
| EP2129042A1 (en) | A multicast network system, node and a method for detecting a fault of a multicast network link | |
| WO2020010906A1 (en) | Method and device for operating system (os) batch installation, and network device | |
| CN105610594B (en) | Service chain fault diagnosis method and device | |
| CN110691012B (en) | Message processing method and tester | |
| WO2011124178A2 (en) | Fault detection method, route node and system | |
| KR20120004461A (en) | Method and apparatus for fault-resilient multicast and unicast in transport networks | |
| CN109412851B (en) | Link layer path detection method, device and system |
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 |