CN115361264A - Node management method, device, node, system and storage medium - Google Patents
Node management method, device, node, system and storage medium Download PDFInfo
- Publication number
- CN115361264A CN115361264A CN202210997409.XA CN202210997409A CN115361264A CN 115361264 A CN115361264 A CN 115361264A CN 202210997409 A CN202210997409 A CN 202210997409A CN 115361264 A CN115361264 A CN 115361264A
- Authority
- CN
- China
- Prior art keywords
- node
- target
- monitoring management
- management port
- request information
- 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.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 261
- 238000012544 monitoring process Methods 0.000 claims abstract description 271
- 230000004044 response Effects 0.000 claims abstract description 121
- 238000000034 method Methods 0.000 claims abstract description 30
- 238000004458 analytical method Methods 0.000 claims description 14
- 238000012423 maintenance Methods 0.000 claims description 14
- 238000013507 mapping Methods 0.000 claims description 9
- 238000012217 deletion Methods 0.000 claims description 7
- 230000037430 deletion Effects 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 6
- 238000004891 communication Methods 0.000 description 21
- 238000010586 diagram Methods 0.000 description 12
- 230000005540 biological transmission Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000013144 data compression Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
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/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
- H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
- H04L41/028—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP] for synchronisation between service call and response
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention discloses a node management method, a node management device, a node management system and a storage medium. The method comprises the following steps: for each node, receiving request information through a configured target monitoring management port; forwarding the request information to a unified monitoring platform, and receiving response information corresponding to the request information through the target monitoring management port, wherein the response information is generated by the unified monitoring platform according to the request information; and determining a target node according to the node identification ID in the response information, and managing the target node according to the response information. By using the method, the efficiency of node management can be improved.
Description
Technical Field
The embodiments of the present invention relate to the field of communications technologies, and in particular, to a node management method, apparatus, node, system, and storage medium.
Background
With the rapid development of information technology, related applications based on data processing can be deployed on multiple nodes to facilitate synchronous processing and distribution of data, wherein the multiple nodes may be in different network environments. In this case, because direct communication management is not allowed for network security among nodes in different network environments, operation and maintenance personnel cannot uniformly monitor and manage each node and related applications deployed on each node, so that a large amount of workload is brought to the operation and maintenance personnel, and the efficiency of node management is reduced.
Therefore, how to improve the efficiency of node management is a technical problem to be solved urgently at present.
Disclosure of Invention
The embodiment of the invention provides a node management method, a node management device, a node management system and a storage medium, which are used for improving the efficiency of node management.
In a first aspect, an embodiment of the present invention provides a node management method, including:
for each node, receiving request information through a configured target monitoring management port;
forwarding the request information to a unified monitoring platform, and receiving response information corresponding to the request information through the target monitoring management port, wherein the response information is generated by the unified monitoring platform according to the request information;
and determining a target node according to the node identification (Identity, ID) in the response information, and managing the target node according to the response information.
In a second aspect, an embodiment of the present invention further provides a node management apparatus, including:
the receiving module is used for receiving request information through the configured target monitoring management port aiming at each node;
the forwarding module is used for forwarding the request information to a unified monitoring platform and receiving response information corresponding to the request information through the target monitoring management port, wherein the response information is generated by the unified monitoring platform according to the request information;
and the management module is used for determining a target node according to the node ID in the response information and managing the target node according to the response information.
In a third aspect, an embodiment of the present invention further provides a node, including:
one or more processors;
storage means for storing one or more programs;
the one or more programs are executed by the one or more processors, so that the one or more processors implement the node management method provided by the embodiment of the invention.
In a fourth aspect, an embodiment of the present invention further provides a node management system, including: a monitoring management platform and a plurality of nodes provided by the embodiment of the invention;
wherein at least two of said nodes are cascaded.
In a fifth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the node management method provided in the embodiment of the present invention.
The embodiment of the invention provides a node management method, a node management device, a node management system and a storage medium, and the method comprises the steps of firstly receiving request information through a configured target monitoring management port aiming at each node; then, the request information is forwarded to a unified monitoring platform, response information corresponding to the request information is received through a target monitoring management port, and the response information is generated by the unified monitoring platform according to the request information; and finally, determining the target node according to the node ID in the response information, and managing the target node according to the response information. By utilizing the technical scheme, the efficiency of node management can be improved.
Drawings
Fig. 1 is a schematic flowchart of a node management method according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a node management method according to a second embodiment of the present invention;
fig. 3 is a schematic diagram illustrating an implementation of a node management system according to a second embodiment of the present invention;
fig. 4 is a schematic diagram illustrating an implementation of a node management method according to a second embodiment of the present invention;
fig. 5 is a schematic diagram illustrating an implementation of parsing response information according to a second embodiment of the present invention;
fig. 6 is a schematic structural diagram of a node management apparatus according to a third embodiment of the present invention;
fig. 7 is a schematic structural diagram of a node according to a fourth embodiment of the present invention;
fig. 8 is a schematic diagram of a node management system according to a sixth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently, or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but could have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like. In addition, the embodiments and features of the embodiments in the present invention may be combined with each other without conflict.
The term "include" and variations thereof as used herein are intended to be open-ended, i.e., "including but not limited to". The term "based on" is "based at least in part on". The term "one embodiment" means "at least one embodiment".
It should be noted that the terms "first", "second", etc. mentioned in the present invention are only used for distinguishing the corresponding contents, and are not used for limiting the order or interdependence relationship.
It is noted that references to "a", "an", and "the" modifications in the present invention are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that reference to "one or more" unless the context clearly dictates otherwise.
Example one
Fig. 1 is a schematic flowchart of a node management method according to an embodiment of the present invention, where the method is applicable to a case where different nodes are managed in a unified manner, and the method may be executed by a node management apparatus, where the apparatus may be implemented by software and/or hardware and is generally integrated on a node, and in this embodiment, the node includes but is not limited to: desktop computers, notebook computers, servers and the like.
As shown in fig. 1, a node management method provided in an embodiment of the present invention includes the following steps:
and S110, receiving request information through the configured target monitoring management port aiming at each node.
In this embodiment, the target monitoring management port may refer to a port configured for performing communication between nodes corresponding to each node, that is, one node may be configured with one target monitoring management port. It can be understood that, the communication port and the Internet Protocol (IP) address are associated with each other, for example, each node corresponds to an IP address, and when communicating between nodes, the IP address needs to be obtained to find the corresponding node, on this basis, the communication port is needed to realize when the node wants to access an application program, and different application programs can correspond to different communication ports; that is, after connecting to a corresponding node through an IP address, access to the corresponding application on the node can be located through the communication port.
The request information may refer to information including node configuration information, node state information, and node request information. The node configuration information may refer to relevant configuration information when the node is registered, and may include, for example, information such as a registration authentication user name, a registration authentication password, a node name, a node address, a superior gateway address, a communication port, a communication protocol, and a system version. The node state information may refer to information associated with a current operating state of the node, and may include information such as a memory state of the node, a Central Processing Unit (CPU) state, an application process state, a received data size of the node, data update time, data compression rate, a transmitted data size, a data transmission speed, and data Processing time. The node request information may refer to information associated with a node requesting registration to the unified monitoring management platform, and may include information such as a node ID, a node version number, a node application version, and the like.
The unified monitoring management platform can be regarded as a system platform deployed for unified monitoring and management of all nodes. A port for receiving the request information of each node (that is, a monitoring management port configured by the unified monitoring platform) may be provided on the unified monitoring management platform, and the received request information may also be displayed to a user (such as an operation and maintenance person), so that the user may know the state of each node.
For each node, the request information can be received through a target monitoring management port configured by the node. It will be appreciated that for network security, nodes between different network segments (i.e., across network segments) are not allowed to communicate directly, and therefore a target supervisory management port may be provided for communication. The target monitoring management port corresponding to each node may be determined according to the network environment configuration to which each node belongs, and the network environment configuration may refer to a communication network segment configuration in which the node is located.
For example, if the network environment configuration to which a certain node belongs is consistent with the network environment to which the unified monitoring platform belongs (i.e., belongs to the same network segment), the target monitoring management port configured by the node may be set as the monitoring management port configured by the unified monitoring platform; if the network environment configuration to which a certain node belongs is not consistent with the network environment configuration to which the unified monitoring platform belongs (i.e. belongs to a cross-network segment), the target monitoring management port configured by the node can be set as the monitoring management port configured by the upper node of the node. It should be noted that the IP address is associated with the communication port, so that when a certain node configures a target monitoring management port, the IP address may also be configured correspondingly, for example, if the target monitoring management port configured for the certain node is a monitoring management port configured for the unified monitoring platform, the IP address configuration for the node may be an IP address configured for the unified monitoring platform; similarly, if the target monitoring management port configured for a certain node is the monitoring management port configured for the upper node of the node, the IP address configuration of the node may be the IP address configured for the upper node of the node.
Optionally, the request information includes request information corresponding to the node or request information corresponding to a subordinate node of the node;
after receiving the request information through the configured target monitoring management port, the method further comprises the following steps: and if the request information is the request information corresponding to the subordinate node of the node, recording the mapping relation between the node ID in the request information and the subordinate connection in a local cache queue of the node, wherein the subordinate connection is the connection between the target monitoring management port of the node and the local port of the subordinate node of the node.
For each node, the request information may include the request information submitted by the node, and may also include the request information submitted by a node subordinate to the node. After the node receives the request information through the configured target monitoring management port, if the request information is the request information correspondingly submitted by the subordinate node of the node, the mapping relationship between the node ID and the subordinate connection included in the request information may be recorded in the local cache queue of the node to be used for positioning and forwarding of the response information subsequently.
It can be understood that, if the request information is the request information correspondingly submitted by the subordinate node of the node, it may indicate that the target monitoring management port configured by the subordinate node of the node is the target monitoring management port corresponding to the node, and on this basis, the subordinate node of the node may submit the request information to the correspondingly configured target monitoring management port (i.e., the target monitoring management port corresponding to the node) through the local port, so that the subordinate connection may refer to the connection between the target monitoring management port of the node and the local port of the subordinate node of the node; it can also be understood that when a subordinate node of the node submits a request message to the node, a long connection, that is, a subordinate connection, is established between a local port corresponding to the subordinate node and the configured target monitoring management port. Correspondingly, if the request information is the request information correspondingly submitted by the node, it can be understood that no lower level connection exists, and the response information corresponding to the request information can be directly received at the local of the node.
S120, the request information is forwarded to a unified monitoring platform, response information corresponding to the request information is received through the target monitoring management port, and the response information is generated by the unified monitoring platform according to the request information.
In this embodiment, for each node, the received request information is forwarded to the unified monitoring platform, and the response information corresponding to the request information is received through the corresponding target monitoring management port. The response information may be generated by the unified monitoring and management platform according to the corresponding request information, for example, the response information may include information generated according to the request information, such as updating the node configuration, updating the node application, and making a decision as to whether the node can be registered in the unified management platform. The updating of the node configuration may be response information generated by relevant operation and maintenance personnel modifying the corresponding node configuration of the node based on the node configuration information in the request information, and the decision on whether the node can be registered in the unified management platform may be response information generated according to information such as a node ID in the current request information and information such as a node list allowing registration preset in the unified monitoring platform by the relevant operation and maintenance personnel. It should be noted that, if no node modification or request node registration is found according to the request information, the response information may be null, that is, no modification or management is performed on the corresponding node.
Optionally, forwarding the request information to the unified monitoring platform includes: if the target monitoring management port is a first monitoring management port corresponding to the unified monitoring platform, forwarding the request information to the unified monitoring platform through the target monitoring management port; and if the target monitoring management port is a second monitoring management port corresponding to a superior node of the node, sequentially forwarding the request information through the target monitoring management ports corresponding to the superior nodes cascaded with the node, wherein the target monitoring management port corresponding to the last-stage node is a first monitoring management port.
If the target monitoring management port of the node is the first monitoring management port corresponding to the unified monitoring platform (the first monitoring management port can be understood as the monitoring management port configured corresponding to the unified monitoring platform), the request information can be directly forwarded to the unified monitoring platform through the target monitoring management port (that is, only when the target monitoring management port corresponding to the node is the first monitoring management port, the unified monitoring platform can be allowed to be accessed and communicated with the unified monitoring platform).
If the target monitoring management port of the node is a second monitoring management port corresponding to a higher node of the node (the second monitoring management port can be understood as a target monitoring management port configured corresponding to the higher node of the node), the request information may be forwarded sequentially through the target monitoring management ports corresponding to the higher nodes in cascade connection with the node, where the target monitoring management port corresponding to the last node is the first monitoring management port. That is, the node forwards the request information to the upper node in cascade connection with the node through the corresponding target monitoring management port, and if the target monitoring management port corresponding to the upper node is not the first monitoring management port (at this time, it indicates that the target monitoring management port cannot be directly communicated with the unified monitoring platform), the upper node continues to forward the request information to the upper node in cascade connection with the node on the basis, and so on until the target monitoring management port corresponding to the forwarded node is the first monitoring management port.
S130, determining a target node according to the node ID in the response information, and managing the target node according to the response information.
In this embodiment, the target node may refer to a node that originally submits the request information, and thus, for each node, the target node may include the node or a node subordinate to the node, since the request information may be correspondingly submitted by the node or the node subordinate.
Optionally, the target node includes the node or a subordinate node of the node; determining a target node according to the node ID in the request information, comprising: searching whether a subordinate connection matched with the node ID exists in a local cache queue of the node according to the node ID in the response message; if yes, determining the target node as a subordinate node of the node; otherwise, determining the target node as the node.
For each node, determining whether a target node may be a node according to the node ID in the response information, and searching whether a lower-level connection matching the node ID exists from a local cache queue of the node according to the node ID information included in the response information, where if the lower-level connection exists, it may be indicated that request information corresponding to the response information is possibly submitted by a lower-level node of the node, that is, the target node is the lower-level node of the node; if the request information does not exist, it can be shown that the request information corresponding to the response information may be submitted by the node itself, that is, the target node is the node.
On the basis, if the target node is the node, the target node can be managed according to the received response information; if the target node is a subordinate node of the node, the node can forward the response information to a local port of the corresponding subordinate node through the target monitoring management port, and on the basis, the subordinate node can perform corresponding node management according to the received response information.
Optionally, managing the target node according to the response information includes: analyzing the response information according to the type of the set response information; managing the target node according to the analysis result;
the set type of the response message may refer to a classification type of a preset response message, and may include, for example, node configuration update, node program upgrade, node message advertisement, node deletion, node maintenance, and the like. A node configuration update may be understood as updating the current configuration information of the node. A node program upgrade may be understood as an upgrade to an associated application program deployed on a node. The node message announcement may be understood as a message notification issued by the unified monitoring platform, where the content of the message notification is not limited, and may include, for example, a notification of a management result of a relevant operation and maintenance worker on a certain application program, a notification of relevant configuration modification on a node, and the like; the node may also present the content of the message notification. Node deletion may be understood as the deletion of relevant configurations that the node is allowed to access the unified monitoring platform. Node preservation is understood to mean that the node remains unchanged for all settings present.
After receiving the response information, analyzing the response information according to the type of the set response information, and on the basis, managing the target node according to the analysis result, for example, if the analysis result of the response information is node deletion, automatically deleting the configuration information associated with the target node allowed to access the unified monitoring platform; if the analysis result of the response information is the node configuration update, the current node configuration of the target node can be automatically updated according to the new node configuration information contained in the response information, and the like.
It should be noted that, in an embodiment, when the unified monitoring platform generates the response information according to the request information, if the application program on the node needs to be upgraded, the response information may include an application program upgrade package downloaded from the unified monitoring platform; on the basis, after receiving the response information, the target node can directly update according to the application program upgrading packet in the response information so as to replace the current node application program. The method for obtaining the application upgrade package is not limited, and may be set according to actual requirements.
The node management method provided by the embodiment of the invention comprises the steps of firstly receiving request information through a configured target monitoring management port aiming at each node; then, the request information is forwarded to a unified monitoring platform, response information corresponding to the request information is received through a target monitoring management port, and the response information is generated by the unified monitoring platform according to the request information; and finally, determining the target node according to the node ID in the response information, and managing the target node according to the response information. By the method, the efficiency of node management can be improved.
Example two
Fig. 2 is a flowchart illustrating a node management method according to a second embodiment of the present invention, where the second embodiment is further detailed based on the foregoing embodiments. It should be noted that technical details that are not described in detail in the present embodiment may be referred to any of the above embodiments.
As shown in fig. 2, a node management method provided in the second embodiment of the present invention includes the following steps:
s210, aiming at each node, determining a corresponding target monitoring management port according to the network environment configuration to which the node belongs.
In this embodiment, the network environment configurations to which each node belongs may be different, and in order that nodes configured in different network environments may communicate with each other, for each node, a corresponding target monitoring management port may be determined according to the network environment configuration to which the node belongs, so as to perform corresponding communication through the target monitoring management port.
Optionally, the target monitoring management port includes a first monitoring management port corresponding to the unified monitoring platform or a second monitoring management port corresponding to a superior node of the node; for each node, determining a corresponding target monitoring management port according to the network environment configuration to which the node belongs, including: if the network environment configuration of the node is consistent with the network environment configuration of the unified monitoring platform, the target monitoring management port corresponding to the node is a first monitoring management port corresponding to the unified monitoring platform; if the network environment configuration of the node is inconsistent with the network environment configuration of the unified monitoring platform, the target monitoring management port corresponding to the node is a second monitoring management port corresponding to a superior node of the node.
The configurable target monitoring management port can be a first monitoring management port corresponding to the unified monitoring platform; for the node with inconsistent configuration with the network environment to which the unified monitoring platform belongs, for cross-network-segment communication, the configurable target monitoring management port may be a second monitoring management port corresponding to a superior node of the node.
And S220, receiving the request information through the configured target monitoring management port.
In this embodiment, for each node, request information is received through the configured target monitoring management port, where the request information may include request information corresponding to the node or request information corresponding to a lower node of the node. After receiving the request information through the configured target monitoring management port, if the request information is the request information corresponding to the subordinate node of the node, the mapping relationship between the node ID in the request information and the subordinate connection may be recorded in the local cache queue of the node.
And S230, forwarding the request information to the unified monitoring platform, and receiving response information corresponding to the request information through the target monitoring management port, wherein the response information is generated by the unified monitoring platform according to the request information.
In this embodiment, if the target monitoring management port is a first monitoring management port corresponding to the unified monitoring platform, the request information may be forwarded to the unified monitoring platform through the target monitoring management port; if the target monitoring management port is a second monitoring management port corresponding to a superior node of the node, the request information can be forwarded sequentially through the target monitoring management ports corresponding to the superior nodes cascaded with the node, wherein the target monitoring management port corresponding to the last-stage node is a first monitoring management port.
S240, determining the target node according to the node ID in the response information, and managing the target node according to the response information.
In this embodiment, the target node is determined according to the node ID in the response message, and the target node may include the node or a node lower than the node. Specifically, according to the node ID in the response message, it may be searched from the local cache queue of the node whether a lower link matching the node ID exists; if yes, determining that the target node is a lower node of the node; otherwise, the target node may be determined to be the node itself. On the basis, the response information can be analyzed according to the set response information type, and the target node is managed according to the analysis result.
In the node management method provided by the second embodiment of the present invention, by configuring a corresponding target monitoring management port for each node, transmission of request information and corresponding response information is realized through the monitoring management port on this basis, and automatic management of the node can be realized according to the response information, so that efficiency and accuracy of node management are improved.
In one embodiment, with the rapid development of information technology and the acceleration of exchange quotations, various file quotations are gradually replaced by streaming data transmission. Related enterprises such as securities, futures, funds and the like have higher and higher requirements on market data transmission, so that the traditional market file mapping sharing mode is changed into the market data real-time synchronization and distribution mode through market distribution software. The common market distribution software belongs to a client and server deployment mode, for example, an enterprise headquarter receives market from a trading exchange gateway, and distributes the market to related sub-departments below the headquarter through a market distribution software server. The headquarter and the sub-departments may belong to a network environment of a cross-network segment, different network environments are not allowed to be directly communicated based on network security requirements, and generally, a fortress machine deploys a quotation software sub-node, that is, the quotation software is deployed on nodes corresponding to the headquarter and each sub-department, and then quotation data is forwarded to each terminal node (a sub-network may refer to the network environment to which the sub-department belongs) in a sub-network (the terminal node may be understood as a node corresponding to each terminal under the sub-department). Based on the deployment architecture, the difficulties of monitoring and managing the cross-network-segment nodes and the deployed market distribution software thereof are encountered, and especially for the application program upgrade of the market distribution node software, a large amount of workload is brought to related operation and maintenance personnel due to the lack of uniform monitoring and management. In order to solve the difficulty of operation and maintenance management of the nodes across network segments, the present embodiment provides a method for unified monitoring management of the nodes across network segments.
A method for unified monitoring management of nodes comprises the following steps:
the method comprises the following steps: and deploying a unified monitoring platform, and providing a node registration and state collection interface (namely a first monitoring management port corresponding to the same monitoring platform), wherein a node request meeting interface specifications and authentication requirements can be registered to the current platform. And displaying the corresponding detailed node information according to the node registration information and the related state information (namely the request information).
Step two: each node is configured with a corresponding monitoring management IP address and port (i.e. a target monitoring management port and an IP address associated therewith), the monitoring management IP address and port may be an IP address and a first monitoring management port corresponding to a unified monitoring platform, or an IP address and a target monitoring management port corresponding to a higher-level node of the node, the node submits request information to the corresponding target monitoring management port, the request information may include status information of the node, and the status information may be periodically uploaded to the corresponding target monitoring management port.
Step three: each node can provide a target monitoring management port as an agent monitoring management port, and the target monitoring management port is used for a scene that subordinate nodes of the node cannot access the unified monitoring platform. And waiting for the access of the subordinate node, then receiving the request information by the target monitoring management port of the node, forwarding the request information to the unified monitoring platform, and simultaneously recording the mapping relation between the node ID in the request information and the subordinate connection in the local cache queue of the node. Receiving response information corresponding to the request information through the target monitoring management port, finding the subordinate connection according to the mapping relation recorded in the local cache queue and the node ID in the response information, forwarding the response information to the node corresponding to the subordinate connection (namely, the node can be understood as the target node), analyzing the response information according to the set type of the response information, and managing the target node according to the analysis result.
Step four: if the node does not match the subordinate connection matched with the node ID in the response information in the record of the local cache queue after receiving the response information from the target monitoring management port, the node can indicate that the response information is the response information corresponding to the node. The node starts analysis processing, and the answer information is analyzed according to the set answer information type so as to manage the target node according to the analysis result.
In this embodiment, for each node, through the setting of the target monitoring management port, request information of a lower node may be collected and forwarded to the unified monitoring platform, and on this basis, response information issued from the unified monitoring management platform may also be received through the target monitoring management port. In addition, the target monitoring management port is arranged, so that each subordinate node of the cross-network segment does not need to open a special port for monitoring and managing the unified monitoring platform, the target monitoring management port corresponding to the superior node is configured to realize communication with the unified monitoring platform, and automatic monitoring and management of the cross-network segment nodes are realized, so that errors or omission of operation and maintenance personnel during manual node management operation are avoided, the efficiency of node management is improved, human resources are saved, and the efficiency and accuracy of automatic operation and maintenance are improved.
Fig. 3 is a schematic diagram illustrating an implementation of a node management system according to a second embodiment of the present invention. As shown in fig. 3, the distribution and transmission of market data are taken as an example, and include a gateway (which may refer to a gateway to which a node providing the initial market data belongs), a master node (which may refer to a node directly connected to the gateway for communication, such as a node corresponding to a head office of an enterprise), a child node (which may refer to a node corresponding to each sub-department below the head office), and a terminal node (which may refer to each terminal below the head office or a node corresponding to each terminal below each sub-department). And the main node receives the market information from the gateway and distributes the market information to the sub-nodes or the terminal nodes connected with the sub-nodes. Meanwhile, the child nodes can continue to cascade and forward the market data to the terminal nodes of the subordinate level of the child nodes. In fig. 3, the gateway, the master node, the terminal nodes connected to the master node, and the unified monitoring platform are deployed in a headquarter network environment, and the child nodes are deployed on the bastion machine, wherein the bastion machine is a dual-network card machine, and can receive market data from the master node and access the unified monitoring platform, so that the master node, the terminal nodes connected to the master node, and the child nodes deployed on the bastion machine can also access the unified monitoring platform. The terminal nodes at the downstream of the sub-nodes are deployed in an independent network environment different from the headquarter network environment, can receive market data from the sub-nodes, but cannot access the headquarter main node and the unified monitoring and management platform.
On the basis of the above embodiment, the transmission direction of the market data may be that the gateway sends the market data to the master node, the master node distributes the market data to the child nodes and the partial terminal nodes connected to the child nodes, and the child nodes distribute the market data to the terminal nodes downstream of the child nodes. The request information can be collected in a mode that a main node, part of terminal nodes and sub-nodes which belong to the same network environment with the unified monitoring platform can directly send state information to the unified monitoring platform through a configured target monitoring management port (namely, a first monitoring management port); and part of the terminal nodes which do not belong to the same network environment with the unified monitoring platform can send request information to a target monitoring management port of the upper node (namely, a target monitoring management port corresponding to the child node), and the child node forwards the request information to the unified monitoring platform. On the basis, the unified monitoring management platform can display and monitor the detailed information of each node in real time according to the collected request information.
Fig. 4 is a schematic diagram illustrating an implementation of a node management method according to a second embodiment of the present invention. As shown in fig. 4, first, for each node, the node listens to a corresponding target monitoring management port, waits for a connection of a lower node of the node, and receives request information of the lower node. The node can also record the mapping relation between the node ID in the request information and the subordinate connection to the local cache queue. The node then forwards the received request message to the configured target monitoring management port (which now also includes the configured IP address associated with the target monitoring management port), and waits to receive an acknowledgement message. After receiving the response information, searching the matched subordinate connection in the local cache queue according to the node ID in the response information, if no matched subordinate connection exists, indicating that the current response information corresponds to the node, analyzing the response information by the node according to the type of the response information, and managing the node according to the analysis result. And if the lower level connection is matched, forwarding the response information to a node (namely the target node) corresponding to the lower level connection so as to complete the management of the target node according to the response information.
Fig. 5 is a schematic diagram illustrating an implementation of parsing response information according to a second embodiment of the present invention. As shown in fig. 5, the target node receives the response message, and performs judgment and analysis on the response message according to the set response message type, where the analysis result may include node configuration update, node program upgrade, node message advertisement, node deletion, and node maintenance.
EXAMPLE III
Fig. 6 is a schematic structural diagram of a node management apparatus according to a third embodiment of the present invention, where the node management apparatus may be implemented by software and/or hardware. As shown in fig. 6, the apparatus includes: a receiving module 310, a forwarding module 320, and a management module 330;
the receiving module 310 is configured to receive, for each node, request information through a configured target monitoring management port;
a forwarding module 320, configured to forward the request information to a unified monitoring platform, and receive response information corresponding to the request information through the target monitoring management port, where the response information is generated by the unified monitoring platform according to the request information;
and the management module 330 is configured to determine a target node according to the node ID in the response information, and manage the target node according to the response information.
In this embodiment, the apparatus first receives, through the receiving module 310, request information for each node through a configured target monitoring management port; then, the request information is forwarded to the unified monitoring platform through the forwarding module 320, and the response information corresponding to the request information is received through the target monitoring management port, and the response information is generated by the unified monitoring platform according to the request information; finally, the management module 330 determines the target node according to the node ID in the response message, and manages the target node according to the response message. By using the device, the efficiency of node management can be improved.
Optionally, the apparatus further comprises:
and the port determining module is used for determining a corresponding target monitoring management port according to the network environment configuration of each node before the configured target monitoring management port receives the request information.
Optionally, the target monitoring management port includes a first monitoring management port corresponding to the unified monitoring platform or a second monitoring management port corresponding to a higher-level node of the node;
the port determination module specifically includes:
a first port determining unit, configured to determine that a target monitoring management port corresponding to the node is a first monitoring management port corresponding to the unified monitoring platform if the network environment configuration to which the node belongs is consistent with the network environment configuration to which the unified monitoring platform belongs;
and the second port determining unit is used for determining that the target monitoring management port corresponding to the node is a second monitoring management port corresponding to a superior node of the node if the network environment configuration to which the node belongs is inconsistent with the network environment configuration to which the unified monitoring platform belongs.
Optionally, the forwarding module 320 specifically includes:
the first forwarding unit is configured to forward the request information to the unified monitoring platform through the target monitoring management port if the target monitoring management port is a first monitoring management port corresponding to the unified monitoring platform;
and the second forwarding unit is used for forwarding the request information sequentially through the target monitoring management ports corresponding to the upper nodes in cascade connection with the node if the target monitoring management port is a second monitoring management port corresponding to the upper node of the node, wherein the target monitoring management port corresponding to the last-stage node is the first monitoring management port.
Optionally, the request information includes request information corresponding to the node or request information corresponding to a lower node of the node;
the device further comprises:
a recording module, configured to record, after receiving request information through the configured target monitoring management port, a mapping relationship between a node ID in the request information and a subordinate connection in a local cache queue of the node if the request information is request information corresponding to a subordinate node of the node, where the subordinate connection is a connection between the target monitoring management port of the node and a local port of the subordinate node of the node.
Optionally, the target node includes the node or a subordinate node of the node;
the management module 330 specifically includes:
the searching unit is used for searching whether lower-level connection matched with the node ID exists in a local cache queue of the node according to the node ID in the response information;
a first node determining unit, configured to determine that a target node is a subordinate node of the node if a subordinate connection matching the node ID exists;
and the first node determining unit is used for determining the target node as the node if the lower-level connection matched with the node ID does not exist.
Optionally, the management module 330 specifically further includes:
the analysis unit is used for analyzing the response information according to the set response information type;
the management unit is used for managing the target node according to the analysis result;
the setting response information type comprises node configuration updating, node program upgrading, node message announcement, node deletion and node maintenance.
The node management device can execute the node management method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
Example four
Fig. 7 is a schematic structural diagram of a node according to a fourth embodiment of the present invention. As shown in fig. 7, a node according to the fourth embodiment of the present invention includes: a storage device 42 and one or more processors 41; the number of the processors 41 in the node may be one or more, and one processor 41 is taken as an example in fig. 4; storage 42 is used to store one or more programs; the one or more programs are executed by the one or more processors 41, so that the one or more processors 41 implement the node management method according to any one of the embodiments of the present invention.
The node may further comprise: a communication device 43, an input device 44 and an output device 45.
The processor 41, the storage means 42, the communication means 43, the input means 44 and the output means 45 in the node may be connected by a bus or other means, as exemplified by a bus connection in fig. 7.
The storage device 42 in the node is used as a computer-readable storage medium for storing one or more programs, which may be software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the node management method according to one or two embodiments of the present invention (for example, the modules in the node management device shown in fig. 6 include a receiving module 310, a forwarding module 320, and a management module 330). The processor 41 executes various functional applications and data processing of the node by executing software programs, instructions and modules stored in the storage device 42, that is, implements the node management method in the above method embodiment.
The storage device 42 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the node, and the like. Further, the storage 42 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, storage 42 may further include memory located remotely from processor 41, which may be connected to the nodes over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The communication means 43 may comprise a receiver and a transmitter. The communication device 43 is configured to perform information transmission and reception communication in accordance with control of the processor 41.
The input device 44 is operable to receive entered numeric or character information and to generate key signal inputs relating to user settings and function control of the node. The output device 45 may include a display device such as a display screen.
And, when the one or more programs included in the above-mentioned node are executed by the one or more processors 41, the programs perform the following operations: for each node, receiving request information through a configured target monitoring management port; forwarding the request information to a unified monitoring platform, and receiving response information corresponding to the request information through the target monitoring management port, wherein the response information is generated by the unified monitoring platform according to the request information; and determining a target node according to the node ID in the response information, and managing the target node according to the response information.
EXAMPLE five
An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program is used, when executed by a processor, to execute a node management method, where the method includes: for each node, receiving request information through a configured target monitoring management port; forwarding the request information to a unified monitoring platform, and receiving response information corresponding to the request information through the target monitoring management port, wherein the response information is generated by the unified monitoring platform according to the request information; determining a target node according to the node ID in the response information, and managing the target node according to the response information
Optionally, the program, when executed by the processor, may be further configured to perform the node management method according to any embodiment of the present invention.
Computer storage media for embodiments of the present invention may take the form of any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. 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 (a non-exhaustive list) of the computer readable storage medium would include the following: 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), a flash Memory, an optical fiber, a portable CD-ROM, an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. 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.
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 a variety of forms, including, but not limited to: an electromagnetic signal, an optical signal, or any suitable combination of the foregoing. 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, or Radio Frequency (RF), etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
EXAMPLE six
Fig. 8 is a schematic diagram of a node management system according to a sixth embodiment of the present invention. As shown in fig. 8, the node management system includes: a unified monitoring platform 510, and a plurality of nodes 520 as provided by embodiments of the present invention;
wherein at least two nodes 520 are cascaded.
For each node 520, receiving request information through the configured target monitoring management port;
forwarding the request information to the unified monitoring platform 510, and receiving response information corresponding to the request information through the target monitoring management port, where the response information is generated by the unified monitoring platform 510 according to the request information;
and determining a target node according to the node ID in the response information, and managing the target node according to the response information.
The node management system provided by the sixth embodiment can be used for executing the node management method provided by any of the above embodiments, and has corresponding functions and beneficial effects.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A node management method, the method comprising:
for each node, receiving request information through a configured target monitoring management port;
forwarding the request information to a unified monitoring platform, and receiving response information corresponding to the request information through the target monitoring management port, wherein the response information is generated by the unified monitoring platform according to the request information;
and determining a target node according to the node identification ID in the response information, and managing the target node according to the response information.
2. The method of claim 1, further comprising, prior to receiving the request message via the configured target monitoring management port:
and aiming at each node, determining a corresponding target monitoring management port according to the network environment configuration to which the node belongs.
3. The method according to claim 2, wherein the target monitoring management port includes a first monitoring management port corresponding to a unified monitoring platform or a second monitoring management port corresponding to a superior node of the node;
the determining, for each node, a corresponding target monitoring management port according to the network environment configuration to which the node belongs includes:
if the network environment configuration to which the node belongs is consistent with the network environment configuration to which the unified monitoring platform belongs, the target monitoring management port corresponding to the node is a first monitoring management port corresponding to the unified monitoring platform;
if the network environment configuration of the node is inconsistent with the network environment configuration of the unified monitoring platform, the target monitoring management port corresponding to the node is a second monitoring management port corresponding to a superior node of the node.
4. The method of claim 3, wherein forwarding the request message to the unified monitoring platform comprises:
if the target monitoring management port is a first monitoring management port corresponding to the unified monitoring platform, forwarding the request information to the unified monitoring platform through the target monitoring management port;
and if the target monitoring management port is a second monitoring management port corresponding to a superior node of the node, sequentially forwarding the request information through the target monitoring management ports corresponding to the superior nodes which are in cascade connection with the node, wherein the target monitoring management port corresponding to the last-stage node is a first monitoring management port.
5. The method according to claim 1, wherein the request information comprises request information corresponding to the node or request information corresponding to a subordinate node of the node;
after receiving the request information through the configured target monitoring management port, the method further comprises the following steps:
if the request information is the request information corresponding to the subordinate node of the node, recording the mapping relation between the node ID in the request information and the subordinate connection in a local cache queue of the node, wherein the subordinate connection is the connection between the target monitoring management port of the node and the local port of the subordinate node of the node.
6. The method of claim 5, wherein the target node comprises the node or a subordinate node of the node;
the determining a target node according to the node ID in the response message includes:
according to the node ID in the response message, searching whether a lower-level connection matched with the node ID exists in a local cache queue of the node;
if yes, determining the target node as a subordinate node of the node; otherwise, determining the target node as the node.
7. The method of claim 1, wherein the managing the target node according to the response information comprises:
analyzing the response information according to the type of the set response information;
managing the target node according to the analysis result;
the setting response information type comprises node configuration updating, node program upgrading, node message announcement, node deletion and node maintenance.
8. A node, comprising:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the node management method of any of claims 1-7.
9. A node management system, comprising: a unified monitoring platform, and a plurality of nodes according to claim 8;
wherein at least two of said nodes are cascaded.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the node management method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210997409.XA CN115361264B (en) | 2022-08-19 | 2022-08-19 | Node management method, device, node, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210997409.XA CN115361264B (en) | 2022-08-19 | 2022-08-19 | Node management method, device, node, system and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115361264A true CN115361264A (en) | 2022-11-18 |
| CN115361264B CN115361264B (en) | 2024-01-30 |
Family
ID=84001801
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210997409.XA Active CN115361264B (en) | 2022-08-19 | 2022-08-19 | Node management method, device, node, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115361264B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104753968A (en) * | 2013-12-25 | 2015-07-01 | 中国电信股份有限公司 | Cloud computing cross-region multiple data centers and dispatching management method thereof |
| CN107438016A (en) * | 2017-07-28 | 2017-12-05 | 深圳市万网博通科技有限公司 | Network management, equipment, system and storage medium |
| CN110191007A (en) * | 2019-06-27 | 2019-08-30 | 广州虎牙科技有限公司 | Node administration method, system and computer readable storage medium |
| KR20210060364A (en) * | 2019-11-18 | 2021-05-26 | 주식회사 위즈온텍 | Edge server system supporting hybrid cloud |
| CN113127437A (en) * | 2019-12-31 | 2021-07-16 | 阿里巴巴集团控股有限公司 | File system management method, cloud system, device, electronic equipment and storage medium |
| CN113423088A (en) * | 2021-06-18 | 2021-09-21 | 安徽星云互联科技有限责任公司 | Information distribution method, device, equipment, system and storage medium |
| CN113452600A (en) * | 2021-06-10 | 2021-09-28 | 绿盟科技集团股份有限公司 | Cross-region message communication method and device, electronic equipment and storage medium |
| CN114500527A (en) * | 2021-12-27 | 2022-05-13 | 天翼云科技有限公司 | Out-of-band management system and method for edge device |
| CN115801894A (en) * | 2022-11-15 | 2023-03-14 | 阿里巴巴（中国）有限公司 | Communication service system, method and device for realizing communication service and storage medium |
-
2022
- 2022-08-19 CN CN202210997409.XA patent/CN115361264B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104753968A (en) * | 2013-12-25 | 2015-07-01 | 中国电信股份有限公司 | Cloud computing cross-region multiple data centers and dispatching management method thereof |
| CN107438016A (en) * | 2017-07-28 | 2017-12-05 | 深圳市万网博通科技有限公司 | Network management, equipment, system and storage medium |
| CN110191007A (en) * | 2019-06-27 | 2019-08-30 | 广州虎牙科技有限公司 | Node administration method, system and computer readable storage medium |
| KR20210060364A (en) * | 2019-11-18 | 2021-05-26 | 주식회사 위즈온텍 | Edge server system supporting hybrid cloud |
| CN113127437A (en) * | 2019-12-31 | 2021-07-16 | 阿里巴巴集团控股有限公司 | File system management method, cloud system, device, electronic equipment and storage medium |
| CN113452600A (en) * | 2021-06-10 | 2021-09-28 | 绿盟科技集团股份有限公司 | Cross-region message communication method and device, electronic equipment and storage medium |
| CN113423088A (en) * | 2021-06-18 | 2021-09-21 | 安徽星云互联科技有限责任公司 | Information distribution method, device, equipment, system and storage medium |
| CN114500527A (en) * | 2021-12-27 | 2022-05-13 | 天翼云科技有限公司 | Out-of-band management system and method for edge device |
| CN115801894A (en) * | 2022-11-15 | 2023-03-14 | 阿里巴巴（中国）有限公司 | Communication service system, method and device for realizing communication service and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115361264B (en) | 2024-01-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220263727A1 (en) | Systems and methods for enhanced monitoring of a distributed computing system | |
| US11716669B2 (en) | Internet of things service routing method | |
| CN101371237B (en) | Performing message payload processing functions in a network element on behalf of an application | |
| US8554980B2 (en) | Triggered notification | |
| CN111258627B (en) | Interface document generation method and device | |
| US20200213262A1 (en) | System and method for automating actions in distributed computing | |
| CN110636127B (en) | Communication processing method and system between information data | |
| CN112988485A (en) | Simulation test method and device for power Internet of things equipment | |
| CN110011875A (en) | Dial testing method, device, equipment and computer readable storage medium | |
| CN115114044A (en) | Message pushing method, device, equipment and medium | |
| CN104219280B (en) | A kind of intelligent use data transmission channel | |
| CN113242317B (en) | Addressing route synchronization method and related device for alliance chain supervision system | |
| CN115361264B (en) | Node management method, device, node, system and storage medium | |
| CN112445861A (en) | Information processing method, device, system and storage medium | |
| CN113553206B (en) | Data event execution method and device, electronic equipment and computer readable medium | |
| CN111756836B (en) | Information sending method and device based on event management model | |
| CN113472846B (en) | Message processing method, device, equipment and computer readable storage medium | |
| CN112367296B (en) | Service control method and device | |
| CN104462235A (en) | Internet of Things general event service mechanism based on Restful Web Service | |
| CN110430098B (en) | Data processing system | |
| CN107124293B (en) | Protocol management method and system of distributed network system | |
| US11799982B2 (en) | Message push method, apparatus, device and medium | |
| CN117880329B (en) | Multi-gateway access method for Internet of things equipment | |
| CN112367298B (en) | Service control method and device | |
| CN109818768B (en) | Physical facility management system, PNF network management system and method |
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 |