CN113904909B - Network environment change self-adaption method and system of distributed agent management system - Google Patents
Network environment change self-adaption method and system of distributed agent management system Download PDFInfo
- Publication number
- CN113904909B CN113904909B CN202111457115.XA CN202111457115A CN113904909B CN 113904909 B CN113904909 B CN 113904909B CN 202111457115 A CN202111457115 A CN 202111457115A CN 113904909 B CN113904909 B CN 113904909B
- Authority
- CN
- China
- Prior art keywords
- node
- main node
- master
- broadcast
- configuration
- 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/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
-
- 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/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- 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/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0846—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on copy from other elements
-
- 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/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
-
- 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/12—Discovery or management of network topologies
-
- 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/30—Decision processes by autonomous network management units using voting and bidding
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a network environment change self-adaptive method of a distributed agent management system, which comprises the following steps: the working steps of the main node are as follows: when the network environment changes, the main node corrects the local configuration and sends a broadcast with the main node information to each slave node at regular time; monitoring other broadcasts, and if the main node broadcast with a higher version number is found, automatically switching the main node into a slave node; the working steps of the slave node are as follows: the configuration is updated along with the change of the information of the main node; entering a main node discovery step when the connection with the main node is unavailable for exceeding the preset time; a main node discovery step: the slave node circularly monitors the broadcast until receiving the broadcast of the master node and successfully connecting with the master node, and then updates the configuration. The self-adaptive method of the invention can automatically adapt to the change of network IP addresses and the like when the network environment changes, thereby improving the reliability of the system and reducing the burden of managers.
Description
Technical Field
The invention relates to the field of seat management, in particular to a network environment change self-adaption method and a network environment change self-adaption system of a distributed seat management system.
Background
For a general distributed system, in order to improve reliability, each service of the distributed system has a plurality of redundant nodes. When a node is abnormal (such as IP address changes), other redundant nodes can still provide service.
However, for the distributed seat management system, each node has respective purposes, and redundant nodes are not designed. When the IP address of the node changes (if the router is replaced, the IP of all the nodes changes, or the IP address obtained from the DHCP is outdated due to long-time off-line restarting, a new IP address is obtained again), because of no redundant node, the node is damaged, the system reliability is poor, and an administrator needs to reconfigure networking. Especially, when the whole network environment changes, the IP addresses of all nodes are changed, and the recovery operation is quite complicated.
The system stability of the distributed seat management system is reduced, the workload of an administrator is increased, and the maintenance cost is increased.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provide a network environment change self-adaption method of a distributed agent management system, which can automatically adapt to changes of network IP addresses and the like when the network environment changes, thereby improving the reliability of the system and reducing the burden of managers.
It is another object of the present invention to provide a network environment change adaptive system of a distributed agent management system.
The purpose of the invention is realized by the following technical scheme:
the network environment change self-adaptive method of the distributed agent management system comprises the following steps:
the working steps of the main node are as follows: when the network environment changes, the main node corrects the local configuration and sends a broadcast with the main node information to each slave node at regular time; monitoring other broadcasts, and if the main node broadcast with a higher version number is found, automatically switching the main node into a slave node;
the working steps of the slave node are as follows: the configuration is updated along with the change of the information of the main node; entering a main node discovery step when the connection with the main node is unavailable for exceeding the preset time;
a main node discovery step: the slave node circularly monitors the broadcast until receiving the broadcast of the master node and successfully connecting with the master node, and then updates the configuration.
The master node starts to monitor the broadcast of other master nodes by calling a master discovery module.
If the host node is found to be the host node with a higher version number, the host node is switched to the slave node by calling a network management module NetworkManager, and a synchronous configuration module SyncClient is called to connect a new host node.
The current master node is switched into a slave node by calling a network management module NetworkManager, and the specific steps are as follows: firstly, stopping UDP broadcast of a main node, and then establishing TCP connection with a new main node; if the connection is successful, synchronizing the configuration of the new main node; if TCP connections from the slave node still exist at the moment, a command is sent to inform the slave node of switching to a new master node; if the connection fails, a reconnection is attempted until the connection is successful.
The working steps of the main node further comprise: when the main node is started, it firstly detects whether the local IP is consistent with the configuration, if so, the configuration is updated.
The broadcast with the master node information is a UDP broadcast.
The working steps of the slave node are as follows:
(1) calling a synchronous configuration module Syncclient to connect with a main node;
(2) if the connection with the main node is successful, synchronous configuration is started, local information is sent to the main node to be checked at regular time, and the main node updates the configuration if the received node IP address is inconsistent with the configuration; the local information comprises a configuration version number and an IP address; (3) attempting reconnection when the connection fails or is disconnected;
(4) if the reconnection still fails after the preset time is exceeded, informing a network management module NetworkManager to process the abnormity of the main node;
(5) the network management module network manager calls a master discovery module Masterdiscover to start monitoring master node broadcast;
(6) when the master node discovery module Masterdiscover receives the broadcast of the master node, the master node discovery module informs the synchronous configuration module SyncClient to connect a new master node;
(7) if the connection with the new main node fails, returning to the step (5) to continue monitoring;
(8) if the new main node is successfully connected, synchronous configuration is started, and the node is recovered to be normal.
In the step (5), the master discovery module MasterDiscover starts to monitor the UDP broadcast, receives the UDP broadcast packet, and after interpreting and checking, determines that the broadcast packet is from the master node, and then enters the step (6) to process.
The preset time is one minute.
The other purpose of the invention is realized by the following technical scheme:
a network environment change adaptive system for a distributed agent management system, comprising: the system comprises a network management module, a main node broadcasting module, a main node discovery module and a slave node synchronous configuration module; the main node broadcasting module is responsible for sending UDP broadcast of the main node at regular time; the main node discovery module is responsible for monitoring a UDP broadcast port and handing received other main node broadcasts to the network management module for processing; the slave node synchronous configuration module is responsible for synchronous configuration of the slave master node and periodically sends network information of the slave node to the master node for inspection; the network management module is responsible for managing the modules.
Compared with the prior art, the invention has the following advantages and beneficial effects:
the invention provides a network change self-adaptive scheme, enhances the system reliability, does not need a specially-assigned person for management, and greatly lightens the burden of an administrator.
Drawings
FIG. 1 is a block diagram of network change adaptation according to the present invention.
Fig. 2 is a sequence diagram of the operation flow of the master node of the present invention.
Fig. 3 is a sequence diagram of the slave node operation flow of the present invention.
Detailed Description
The present invention will be described in further detail with reference to examples and drawings, but the present invention is not limited thereto.
As shown in fig. 1, the network environment change adaptive system of the distributed agent management system of this embodiment includes a network management module NetworkManager, a master broadcast module masterbroker, a master discovery module MasterDiscover, and a slave synchronization configuration module SyncClient.
The operation of these modules differs between master and slave nodes.
A distributed agent management system only has one main node, and the rest are slave nodes. Only the master node has the authority of writing configuration, and the slave nodes can only be synchronously configured from the master node. When the network environment changes, the main node is responsible for correcting the configuration of the local computer; the slave node needs to find a new IP address of the master node first, and then can send a request to the master node to modify the configuration.
The master broadcast module of the master broadcast module is responsible for sending the UDP broadcast of the master node in a timing mode. The master discovery module MasterDiscover is responsible for monitoring the UDP broadcast port and handing the received other master node broadcasts to the network management module NetworkManager for processing. The slave node synchronous configuration module Syncclient is responsible for synchronous configuration of the slave node and the master node and periodically sends local network information to the master node for checking. The network management module NetworkManager is responsible for managing the modules.
As shown in fig. 2, the operation flow of the master node includes the following steps:
(1) start timing UDP broadcast: calling a master broadcasting module to start to send UDP broadcast of the master node at regular time;
(2) start listening to UDP broadcast port: calling a master discover module to start monitoring UDP broadcast of other master nodes;
when a certain router or switch in a distributed system fails, the network is split into 2 local area networks; at this time, if the administrator designates a new master node in the local area network without the master node, the cluster brain split is exceeded (i.e. 2 local area networks all have respective master nodes). When a local area network is reconstructed after the network is repaired, the problem of 2 main nodes occurs;
(3) receiving another master node broadcast: the master node discovery module Masterdiscover receives the broadcast of other master nodes;
(4) checking the version number of the main node: judging whether the version number is higher than that of the local computer or not;
(5) if the version number of the local computer is lower than that of the main node, the local computer is switched to the slave node: if the master node is found to be the master node with a higher version number, the network management module network manager is called to be switched to be the slave node;
(6) calling a synchronous configuration module Syncclient to connect the new host node;
(7) if the master node with the lower version number is found, a command is sent to inform the master node of switching to the slave node.
The main node is switched into the slave node, and the adopted technical means are as follows: firstly, stopping UDP broadcast of a main node, and then establishing TCP connection with a new main node; if the connection is successful, synchronizing the configuration of the new main node; at this point if there are more TCP connections from the slave node, a command is sent to inform them to switch to the new master node. If the connection fails, a reconnection is attempted until the connection is successful. The method for calling the SyncClient to connect the new host node specifically comprises the following steps: disconnecting the current connection and establishing a TCP connection with a new main node; if the connection function is adopted, the configuration of the new main node is synchronized; if the connection fails, a reconnection is attempted until the connection is successful.
As shown in fig. 3, the operation flow of the slave node includes the following steps:
(1) connecting a main node: calling a synchronous configuration module Syncclient to connect with a main node;
(2) if the connection is successful, the local information is sent to the main node to check: if the connection with the main node is successful, synchronous configuration is started, local information (configuration version number, IP address and the like) is sent to the main node at regular time for checking, and the main node finds that the IP address of the received node is inconsistent with the configuration, the configuration is updated;
(3) and if the connection is disconnected, the reconnection is tried: attempting reconnection when the connection fails or is disconnected;
(4) if the reconnect timeout fails, the master node is notified of the exception: if the reconnection still fails after 60 seconds, the network management module is informed to process the exception of the main node;
(5) starting to monitor the broadcast port of the main node: the network management module network manager calls a master discovery module Masterdiscover to start monitoring master node broadcast;
the method starts to monitor UDP broadcast, after receiving UDP broadcast packet, after interpretation and verification, the broadcast packet is confirmed to be from the main node, and then the step (6) is carried out for processing;
(6) receiving the broadcast of the main node: when the master node discovery module Masterdiscover receives the master node broadcast;
(7) connecting a new main node: informing a synchronous configuration module Syncclient to connect a new main node;
(8) if the connection with the new main node fails, returning to the step (5) to continue monitoring;
(9) if the new main node is successfully connected, synchronous configuration is started, and the node is recovered to be normal.
The above embodiments are preferred embodiments of the present invention, but the present invention is not limited to the above embodiments, and any other changes, modifications, substitutions, combinations, and simplifications which do not depart from the spirit and principle of the present invention should be construed as equivalents thereof, and all such changes, modifications, substitutions, combinations, and simplifications are intended to be included in the scope of the present invention.
Claims (9)
1. The network environment change self-adaption method of the distributed agent management system is characterized by comprising the following steps:
the working steps of the main node are as follows: when the network environment changes, the main node corrects the local configuration and sends a broadcast with the main node information to each slave node at regular time; monitoring other broadcasts, and if the main node broadcast with a higher version number is found, automatically switching the main node into a slave node;
the working steps of the slave node are as follows: the configuration is updated along with the change of the information of the main node; entering a main node discovery step when the connection with the main node is unavailable for exceeding the preset time;
the slave node needs to find a new IP address of the master node first, and can send a request to the master node to correct configuration;
the working steps of the slave node are as follows:
(1) calling a synchronous configuration module Syncclient to connect with a main node;
(2) if the connection with the main node is successful, synchronous configuration is started, local information is sent to the main node to be checked at regular time, and the main node updates the configuration if the received node IP address is inconsistent with the configuration; the local information comprises a configuration version number and an IP address;
attempting reconnection when the connection fails or is disconnected;
(4) if the reconnection still fails after the preset time is exceeded, informing a network management module NetworkManager to process the abnormity of the main node;
(5) the network management module network manager calls a master discovery module Masterdiscover to start monitoring master node broadcast;
(6) when the master node discovery module Masterdiscover receives the broadcast of the master node, the master node discovery module informs the synchronous configuration module SyncClient to connect a new master node;
(7) if the connection with the new main node fails, returning to the step (5) to continue monitoring;
(8) if the new main node is successfully connected, synchronous configuration is started, and the node is recovered to be normal;
a main node discovery step: the slave node circularly monitors the broadcast until receiving the broadcast of the master node and successfully connecting with the master node, and then updates the configuration.
2. The adaptive method for network environment change of the distributed agent management system according to claim 1, wherein the master node starts to monitor the broadcast of other master nodes by calling a master discovery module MasterDiscover.
3. The adaptive network environment change method of a distributed agent management system according to claim 1, wherein if the host node is found to have a higher version number, the current host node is switched to a slave node by calling a network management module NetworkManager, and a synchronization configuration module SyncClient is called to connect a new host node.
4. The adaptive method for network environment change of the distributed agent management system according to claim 3, wherein the current master node is switched to the slave node by calling a network management module, NetworkManager, and the specific steps are as follows: firstly, stopping UDP broadcast of a main node, and then establishing TCP connection with a new main node; if the connection is successful, synchronizing the configuration of the new main node; if TCP connections from the slave node still exist at the moment, a command is sent to inform the slave node of switching to a new master node; if the connection fails, a reconnection is attempted until the connection is successful.
5. The network environment change adaptive method of the distributed agent management system according to claim 1, wherein the working step of the master node further comprises: when the main node is started, it firstly detects whether the local IP is consistent with the configuration, if so, the configuration is updated.
6. The adaptive method for network environment change of distributed agent management system according to claim 1, wherein the broadcast with master node information is UDP broadcast.
7. The adaptive method for network environment change of a distributed agent management system according to claim 1, wherein in step (5), the master discovery module MasterDiscover starts to monitor UDP broadcast, receives a UDP broadcast packet, and after interpretation and verification, determines that the broadcast packet is from the master node, and then proceeds to step (6) for processing.
8. The adaptive method for network environment change of the distributed agent management system according to claim 1, wherein the preset time is one minute.
9. A network environment change adaptation system for a distributed agent management system implementing the method of any one of claims 1 to 8, comprising: the system comprises a network management module, a main node broadcasting module, a main node discovery module and a slave node synchronous configuration module; the main node broadcasting module is responsible for sending UDP broadcast of the main node at regular time; the main node discovery module is responsible for monitoring a UDP broadcast port and handing received other main node broadcasts to the network management module for processing; the slave node synchronous configuration module is responsible for synchronous configuration of the slave master node and periodically sends network information of the slave node to the master node for inspection; the network management module is responsible for managing the modules.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111457115.XA CN113904909B (en) | 2021-12-02 | 2021-12-02 | Network environment change self-adaption method and system of distributed agent management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111457115.XA CN113904909B (en) | 2021-12-02 | 2021-12-02 | Network environment change self-adaption method and system of distributed agent management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113904909A CN113904909A (en) | 2022-01-07 |
| CN113904909B true CN113904909B (en) | 2022-03-11 |
Family
ID=79195347
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111457115.XA Active CN113904909B (en) | 2021-12-02 | 2021-12-02 | Network environment change self-adaption method and system of distributed agent management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113904909B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114844591A (en) * | 2022-05-12 | 2022-08-02 | 北京领为军融科技有限公司 | Multi-node synchronization method for air combat flight simulator |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101499949A (en) * | 2008-02-01 | 2009-08-05 | 杭州华三通信技术有限公司 | Failure recovery processing method in intersected ring network, node and intersected ring network |
| CN106789132A (en) * | 2016-12-30 | 2017-05-31 | 中国民航信息网络股份有限公司 | The transmission method of data, apparatus and system |
| CN108228812A (en) * | 2017-12-29 | 2018-06-29 | 北京奇虎科技有限公司 | Adaptive host node switching method and device |
| CN112087343A (en) * | 2020-09-22 | 2020-12-15 | 广州合易威视信息科技有限公司 | Networking and communication method of seat management system |
| CN113489601A (en) * | 2021-06-11 | 2021-10-08 | 海南视联通信技术有限公司 | Anti-destruction method and device based on video networking autonomous cloud network architecture |
| CN113660121A (en) * | 2021-08-13 | 2021-11-16 | 杭州安恒信息技术股份有限公司 | Information management method and device based on distributed system and computer storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112367198B (en) * | 2020-10-30 | 2022-07-01 | 新华三大数据技术有限公司 | Main/standby node switching method and device |
| CN112532436B (en) * | 2020-11-23 | 2024-05-28 | 京东科技控股股份有限公司 | Block chain node state conversion method and block chain system |
-
2021
- 2021-12-02 CN CN202111457115.XA patent/CN113904909B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101499949A (en) * | 2008-02-01 | 2009-08-05 | 杭州华三通信技术有限公司 | Failure recovery processing method in intersected ring network, node and intersected ring network |
| CN106789132A (en) * | 2016-12-30 | 2017-05-31 | 中国民航信息网络股份有限公司 | The transmission method of data, apparatus and system |
| CN108228812A (en) * | 2017-12-29 | 2018-06-29 | 北京奇虎科技有限公司 | Adaptive host node switching method and device |
| CN112087343A (en) * | 2020-09-22 | 2020-12-15 | 广州合易威视信息科技有限公司 | Networking and communication method of seat management system |
| CN113489601A (en) * | 2021-06-11 | 2021-10-08 | 海南视联通信技术有限公司 | Anti-destruction method and device based on video networking autonomous cloud network architecture |
| CN113660121A (en) * | 2021-08-13 | 2021-11-16 | 杭州安恒信息技术股份有限公司 | Information management method and device based on distributed system and computer storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113904909A (en) | 2022-01-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106685818B (en) | Message feedback method and device | |
| US6148410A (en) | Fault tolerant recoverable TCP/IP connection router | |
| US9722875B2 (en) | Master device, slave device, and methods thereof | |
| CN102404146B (en) | Master-slave switching method, network device and DHCP server | |
| CN105119822A (en) | Backup group management method and system based on VRRP (Virtual Router Redundancy Protocol) | |
| CN113904909B (en) | Network environment change self-adaption method and system of distributed agent management system | |
| CN110958176A (en) | System and method for controlling uninterrupted routing during switching of main and standby control planes | |
| CN111371680B (en) | Route management method, device, equipment and storage medium for dual-computer hot standby | |
| CN108964984B (en) | Seamless switching method for redundant channel of power system main station and sub station communication | |
| JP4967674B2 (en) | Media service system, media service device, and LAN redundancy method used therefor | |
| CN113114800B (en) | Resource processing method and device | |
| CA2789794C (en) | Method and system for emergency switching | |
| US11432172B2 (en) | Channel establishment method and base station | |
| US20180270108A1 (en) | Enhanced performance of a telecommunications network comprising at least one group of pooled mobility management entities | |
| JP4465300B2 (en) | Redundant configuration apparatus and redundant configuration method | |
| CN104702422A (en) | Method, device and system for realizing high availability of communication equipment | |
| CN110890989A (en) | Channel connection method and device | |
| KR101401006B1 (en) | Method and appratus for performing software upgrade in high availability system | |
| US20070150613A1 (en) | Method for substitute switching of spatially separated switching systems | |
| CN114189547B (en) | SSL tunnel fast switching method under cluster | |
| CN111209145A (en) | Virtual machine disaster tolerance-based service self-healing method, equipment and storage medium | |
| CN117834394A (en) | Automatic hot standby switching method, device and system for dual-computer application server | |
| CN115190040B (en) | High-availability realization method and device for virtual machine | |
| US11575570B2 (en) | Communication apparatus, redundant communication system, and communication control method | |
| CN113395188B (en) | Method and system for determining working state of server |
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 |