CN112235145B - Flow state detection method and device - Google Patents
Flow state detection method and device Download PDFInfo
- Publication number
- CN112235145B CN112235145B CN202011113863.1A CN202011113863A CN112235145B CN 112235145 B CN112235145 B CN 112235145B CN 202011113863 A CN202011113863 A CN 202011113863A CN 112235145 B CN112235145 B CN 112235145B
- Authority
- CN
- China
- Prior art keywords
- service
- detection
- routing
- execution plan
- configuration file
- 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/0876—Aspects of the degree of configuration automation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0876—Network utilisation, e.g. volume of load or congestion level
- H04L43/0888—Throughput
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Abstract
The application discloses a method and a device for detecting flow state, which relate to the technical field of communication networks, wherein the method comprises the following steps: acquiring a routing configuration file; analyzing a calling link according to the routing configuration file and generating a detection execution plan; acquiring detection results of all detection items according to the detection execution plan; and determining the flow state according to the detection result of each detection item in the detection execution plan. The problem of unable quick accurate location problem point among the prior art is solved, the effect that can improve the time of flow state detection investigation and shorten the investigation time to second level has been reached.
Description
Technical Field
The invention relates to the technical field of communication networks, in particular to a method and a device for detecting a flow state.
Background
In the micro service cluster environment based on the Istio service grid, the hop count of a traffic path is large, and the traffic path dynamically changes in real time along with the change of the service version and the node state. When the flow has a problem, it is difficult and bottleneck to locate the problem point quickly and accurately and solve the flow problem in time.
Disclosure of Invention
The invention aims to provide a flow state detection method and a flow state detection device, which are used for solving the problems in the prior art.
In order to achieve the purpose, the invention provides the following technical scheme:
according to a first aspect, an embodiment of the present invention provides a traffic status detection method, where the method includes:
acquiring a routing configuration file;
analyzing a calling link according to the routing configuration file and generating a detection execution plan;
acquiring detection results of all detection items according to the detection execution plan;
and determining the flow state according to the detection result of each detection item in the detection execution plan.
Optionally, the obtaining the routing configuration file includes:
analyzing an access website to obtain a host identity host in the access website;
and acquiring the routing configuration file at an entrance of the IstioIngressgateway according to the host identity host.
Optionally, analyzing the call link according to the routing configuration file, and generating a detection execution plan includes:
acquiring an access path and a service version of an accessed target service;
and determining the calling link according to the access path, the service version of the target service and the routing configuration file, and generating the detection execution plan.
Optionally, the determining the call link according to the access path, the service version of the target service, and the routing configuration file includes:
determining routing service and version information of a next hop in the routing configuration file according to the access path and the service version of the target service;
and analyzing according to the determined routing service of the next hop to obtain a complete service path and service nodes in the service path, and obtaining the call link.
Optionally, the analyzing to obtain a complete service path and a service node in the service path according to the determined next-hop routing service includes:
if the next-hop routing service is the API gateway, searching the next-hop service of the gateway route in a routing table of the API gateway, retrieving a corresponding routing configuration table according to the service name of the next-hop service, and further finding the target service to be accessed according to the service version of the target service and the access path;
and if the routing service of the next hop is the intermediate node, searching a corresponding routing configuration table according to the service name of the intermediate node, and further finding the target service to be accessed according to the service version of the target service and the access path.
Optionally, the obtaining, according to the detection execution plan, a detection result of each detection item includes:
determining each detection item of each step according to the detection execution plan;
and executing all the detection items of all the steps in parallel to obtain corresponding detection results.
Optionally, the detecting the execution plan includes sequentially probing at least one of ingress probing, gateway probing and service probing.
Optionally, the detection item includes at least one of service access detection, service status detection, Pod access detection, and configuration status detection.
Optionally, the detection event further includes a log detection event, and a detection result of the log detection event is an access log of the target service.
In a second aspect, a flow state detection device is provided, the device comprising:
the acquisition module is used for acquiring the routing configuration file;
the generating module is used for analyzing and calling a link according to the routing configuration file and generating a detection execution plan;
the acquisition module is further used for acquiring the detection result of each detection item according to the detection execution plan;
and the state determining module is used for determining the flow state according to the detection result of each detection item in the detection execution plan.
Obtaining a route configuration file; analyzing a calling link according to the routing configuration file and generating a detection execution plan; acquiring detection results of all detection items according to the detection execution plan; determining a flow state according to a detection result of each detection item in the detection execution plan; the flow state detection is converted into automatic detection, so that the problem point cannot be quickly and accurately positioned in the prior art is solved, and the effects of improving the flow state detection and troubleshooting time and shortening the troubleshooting time to the second level are achieved. Meanwhile, the work difficulty which can be completed by experienced personnel is reduced to the work which can be completed by any testing personnel, and the effect of reducing the work difficulty and threshold is achieved.
The foregoing description is only an overview of the technical solutions of the present invention, and in order to make the technical solutions of the present invention more clearly understood and to implement them in accordance with the contents of the description, the following detailed description is given with reference to the preferred embodiments of the present invention and the accompanying drawings.
Drawings
Fig. 1 is a flowchart of a method of detecting a traffic status according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of one possible implementation of flow detection in a detection execution plan according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a flow state detection device according to an embodiment of the present invention.
Detailed Description
The technical solutions of the present invention will be described clearly and completely with reference to the accompanying drawings, and it should be understood that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience of description and simplicity of description, but do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
In addition, the technical features involved in the different embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
First, to facilitate understanding, a brief description will be given of terms that may be referred to in this application. Wherein:
kubernetes: a containerization orchestration system.
Service: definition of a service in kubernets.
Pod: under the minimum definition of an instance under one Service in kubernets, one Service may have multiple Pod.
Referring to fig. 1, a flowchart of a method for detecting a traffic status according to an embodiment of the present application is shown, where as shown in fig. 1, the method includes:
optionally, this step may include:
firstly, analyzing an access website to obtain a host identity host in the access website;
when a user accesses a URL (uniform resource locator), the server parses the URL to obtain a host identifier host.
Secondly, the route configuration file at the entrance of the IstioIngressgateway is obtained according to the host identity host.
After the host is obtained through analysis, the routing configuration file at the entrance of the IstioIngressgateway can be obtained according to the host.
102, analyzing a calling link according to the routing configuration file and generating a detection execution plan;
the method comprises the following steps:
firstly, acquiring an access path and a service name of an accessed target service;
similar to the above-mentioned acquisition method of the host, after the server obtains the URL, the server may obtain the access path and the traffic label by analyzing the URL, and after the traffic label is obtained, the server may read and obtain the version information of the target service currently requested to be accessed according to the traffic label.
Secondly, determining the calling link according to the access path, the service name of the target service and the routing configuration file, and generating a detection execution plan.
Optionally, this step may include:
(1) determining routing service and version information of a next hop in the routing configuration file according to the access path and the service version of the target service;
(2) and analyzing according to the determined routing service of the next hop to obtain a complete service path and a service node in the service path, and obtaining the call link.
Optionally, if the determined next-hop routing service is an API gateway, searching a next-hop routing service of a gateway route in a routing table of the API gateway, retrieving a corresponding routing configuration table according to a service name of the next-hop routing service, and further finding the target service to be accessed according to the service version of the target service and the access path;
and searching a VirtualService routing configuration table corresponding to the service according to the service name, and finding the service version of the target service needing to be accessed according to the path and the trafficlabel.
And if the determined routing service of the next hop is the intermediate node, searching a corresponding routing configuration table according to the service name of the intermediate node, and further finding the target service to be accessed according to the service version of the target service and the access path.
That is, when the next-hop routing service is an intermediate node, the corresponding VirtualService routing configuration table can be retrieved according to the service plane name, and then the service version of the target service to be accessed is found.
After the service version of the target service to be accessed is found, a complete service path and each service node in the path can be obtained, and then a detection execution plan can be generated. Wherein, detecting the execution plan may include sequentially probing at least one of an ingress probe, a gateway probe, and a service probe, and the probing event includes at least one of a service access probe, a service status probe, a Pod access probe, and a configuration status probe. Wherein Pod is the minimum/simplest basic unit created or deployed for kubernets, and one Pod represents one running process on the cluster.
When the detection execution plan is generated, a preset execution template can be called, and the detection items in each step are defined in the execution template, so that the final detection execution plan is obtained. In practical implementation, an executor may be constructed for each step according to the execution template, for example, an ingress probe, a gateway probe, and a service probe are constructed. Of course, the order in the execution templates may also be adjusted or other functions may be extended as desired.
Assuming that the URL to be accessed is as the name, a possible route analysis process, after the URL is obtained, three steps of Istio route analysis, gateway route analysis and service route analysis are carried out. Wherein the Istio route analysis comprises: and analyzing the URL to obtain host, path and trafficlabel, obtaining a routing configuration file according to the host, searching in the routing configuration file according to the path and trafficlabel to obtain the next hop service of the gateway routing, and then performing gateway routing analysis. When the found next-hop service is the API gateway, the routing table of the API gateway can be found according to the host, the next-hop service of the gateway route is found in the routing table according to the path and the traffic label, and then the service route analysis is carried out. In the service routing analysis, a VirtualService routing configuration table corresponding to the service can be detected according to the service name in the host, and the service version needing to be accessed can be found in the routing configuration table according to the path and the traffic, for example, the found service is traffic-client, and the version is swzhou.
103, acquiring detection results of all detection items according to the detection execution plan;
after the detection execution plan is obtained, the detection result of each detection item can be obtained according to the detection execution plan. Optionally, when a plurality of probes are included, in order to increase the detection speed, each probe may be executed independently, that is, the ingress probe, the gateway probe, and the service probe may be executed in an independent co-routine, so that the overall detection speed is determined by the execution speed of the slowest step.
Referring to fig. 2, a possible schematic diagram of the system including an ingress probe, a gateway probe and a service probe together, and the probing events include a service access probe, a service status probe, a Pod access probe and a configuration status probe simultaneously is shown.
It should be added that the above is only exemplified by detecting the above matters, and in actual implementation, example log detection can be introduced according to requirements, so that a request access log can be obtained during traffic state detection, and the detection problem is more intuitively and conveniently exposed.
And 104, determining the flow state according to the detection result of each detection item in the detection execution plan.
After the test execution plan is executed, the flow state may be determined based on the probe results of each probe event in the test execution plan. In the step, the execution results of the detection items in each detector can be collected in a unified mode, and the subsequent result presenting and reading efficiency is improved.
One possible flow state detection method provided in an embodiment of the present application may include a parameter analysis stage, an execution stage, and an output stage. In the analysis stage, after the URL is obtained, the URL is analyzed to obtain a host, a path and a trafficlabel, and then the analysis stage is started. In the analysis stage, a complete calling link can be obtained through the Istio route analysis and the API gateway route analysis, a corresponding execution plan is generated, and then the execution stage is started. Wherein the execution plan comprises an ingress probe plan, a gateway probe plan and a service probe plan. In the execution stage, the probing may be performed sequentially by an ingress probe, a gateway probe, and a service probe, wherein a probe template may be loaded when generating a probe plan for each probe, and probe items in the probe template include at least one of service access probe, service state probe, Pod access probe, and configuration state probe. And after the detection plan is executed, entering an output stage and outputting the detection result of each detector.
In summary, by obtaining the routing configuration file; analyzing a calling link according to the routing configuration file and generating a detection execution plan; acquiring detection results of all detection items according to the detection execution plan; determining a flow state according to a detection result of each detection item in the detection execution plan; the flow state detection is converted into automatic detection, so that the problem point cannot be quickly and accurately positioned in the prior art is solved, and the effects of improving the flow state detection and troubleshooting time and shortening the troubleshooting time to the second level are achieved. Meanwhile, the difficulty of work which can be completed by experienced personnel is reduced to work which can be completed by any testing personnel, and the effect of reducing the difficulty and threshold of work is achieved.
Referring to fig. 3, a schematic structural diagram of a flow state detection device according to an embodiment of the present application is shown, and as shown in fig. 3, the flow state detection device may include:
an obtaining module 510, configured to obtain a routing configuration file;
a generating module 520, configured to analyze the call link according to the routing configuration file, and generate a detection execution plan;
the obtaining module 510 is further configured to obtain a detection result of each detection item according to the detection execution plan;
a state determining module 530, configured to determine a flow state according to a detection result of each of the detection items in the detection execution plan.
In summary, by obtaining the routing configuration file; analyzing a calling link according to the routing configuration file and generating a detection execution plan; acquiring detection results of all detection items according to the detection execution plan; determining a flow state according to a detection result of each detection item in the detection execution plan; the flow state detection is converted into automatic detection, so that the problem point cannot be quickly and accurately positioned in the prior art is solved, and the effects of improving the flow state detection and troubleshooting time and shortening the troubleshooting time to the second level are achieved. Meanwhile, the difficulty of work which can be completed by experienced personnel is reduced to work which can be completed by any testing personnel, and the effect of reducing the difficulty and threshold of work is achieved.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (8)
1. A method for detecting a traffic state, the method comprising:
acquiring a routing configuration file;
analyzing a calling link according to the routing configuration file and generating a detection execution plan;
acquiring detection results of all detection items according to the detection execution plan;
determining a flow state according to a detection result of each detection item in the detection execution plan;
analyzing a call link according to the routing configuration file and generating a detection execution plan, wherein the analyzing the call link according to the routing configuration file comprises:
acquiring an access path and a service version of an accessed target service;
determining the calling link according to the access path, the service version of the target service and the routing configuration file, and generating the detection execution plan;
wherein the determining the call link according to the access path, the service version of the target service, and the routing configuration file comprises:
determining routing service and version information of a next hop in the routing configuration file according to the access path and the service version of the target service;
and analyzing according to the determined routing service of the next hop to obtain a complete service path and a service node in the service path, and obtaining the call link.
2. The method of claim 1, wherein obtaining the routing profile comprises:
analyzing an access website to obtain a host identity host in the access website;
and acquiring the routing configuration file at an entrance of the IstioIngressgateway according to the host identity host.
3. The method of claim 1, wherein the analyzing the determined next-hop routing service to obtain a complete service path and service nodes in the service path comprises:
if the next-hop routing service is the API gateway, searching the next-hop service of the gateway route in a routing table of the API gateway, retrieving a corresponding routing configuration table according to the service name of the next-hop service, and further finding the target service to be accessed according to the service version of the target service and the access path;
and if the routing service of the next hop is the intermediate node, searching a corresponding routing configuration table according to the service name of the intermediate node, and further finding the target service to be accessed according to the service version of the target service and the access path.
4. The method according to claim 1, wherein the obtaining the probing result of each probing event according to the detection execution plan comprises:
determining each detection item of each step according to the detection execution plan;
and executing all the detection items of all the steps in parallel to obtain corresponding detection results.
5. The method of claim 1, wherein detecting the execution plan comprises probing at least one of an ingress probe, a gateway probe, and a service probe in sequence.
6. The method of claim 5, wherein the probe transaction comprises at least one of a service access probe, a service status probe, a Pod access probe, and a configuration status probe.
7. The method of claim 6,
the detection items also comprise log detection items, and the detection result of the log detection items is an access log of the target service.
8. A flow condition detection device, the device comprising:
the acquisition module is used for acquiring the routing configuration file;
the generating module is used for analyzing and calling a link according to the routing configuration file and generating a detection execution plan;
the acquisition module is further used for acquiring the detection result of each detection item according to the detection execution plan;
the state determining module is used for determining the flow state according to the detection result of each detection item in the detection execution plan;
the generation module is used for acquiring an access path and a service version of an accessed target service, determining the calling link according to the access path, the service version of the target service and the routing configuration file, and generating the detection execution plan; the generation module is used for determining the routing service and the version information of the next hop in the routing configuration file according to the access path and the service version of the target service; the generation module is used for analyzing and obtaining a complete service path and service nodes in the service path according to the determined routing service of the next hop, and obtaining the call link.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011113863.1A CN112235145B (en) | 2020-10-17 | 2020-10-17 | Flow state detection method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011113863.1A CN112235145B (en) | 2020-10-17 | 2020-10-17 | Flow state detection method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112235145A CN112235145A (en) | 2021-01-15 |
| CN112235145B true CN112235145B (en) | 2022-06-14 |
Family
ID=74117888
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011113863.1A Active CN112235145B (en) | 2020-10-17 | 2020-10-17 | Flow state detection method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112235145B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112311679B (en) * | 2020-10-28 | 2023-07-28 | 北京水滴科技集团有限公司 | State detection method, state detection device, electronic equipment and readable storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103442008A (en) * | 2013-08-29 | 2013-12-11 | 中国科学院计算技术研究所 | System and method for detecting routing security |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20100124713A (en) * | 2008-02-01 | 2010-11-29 | 톰슨 텔레콤 벨지움 | A method for routing traffic in a gateway |
| CN107483631B (en) * | 2017-09-19 | 2020-04-07 | 山东大学 | Method for controlling cache to realize mobile internet service access |
| US11489943B2 (en) * | 2019-02-13 | 2022-11-01 | Red Hat, Inc. | Automatic version routing among multiple instances of an application |
-
2020
- 2020-10-17 CN CN202011113863.1A patent/CN112235145B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103442008A (en) * | 2013-08-29 | 2013-12-11 | 中国科学院计算技术研究所 | System and method for detecting routing security |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112235145A (en) | 2021-01-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106874187B (en) | Code coverage rate collection method and device | |
| CN102684927B (en) | A kind of method and apparatus of patrolling and examining the network equipment | |
| CN104065528A (en) | Method And Apparatus For Analyzing And Verifying Functionality Of Multiple Network Devices | |
| CN110287696B (en) | Detection method, device and equipment for rebound shell process | |
| CN105677572B (en) | Based on self organizing maps model cloud software performance exception error diagnostic method and system | |
| CN112235145B (en) | Flow state detection method and device | |
| JP6060209B2 (en) | System and method for obtaining statistically effective analytical mean and analytical range of quality control substances | |
| CN112732563A (en) | Interface script test log extraction method and device, terminal and storage medium | |
| CN101252477B (en) | Determining method and analyzing apparatus of network fault root | |
| CN116719750B (en) | Software testing method and device, server equipment and storage medium | |
| CN102571495B (en) | Method and device for checking network topological structure for wire arrangement of printed circuit board | |
| CN104123397A (en) | Automatic test device and method for Web page | |
| CN106502901A (en) | Coverage rate detection method, device and equipment | |
| CN109218140A (en) | A kind of method of software definition deployment NFV network measuring system | |
| CN110858810A (en) | Network link state monitoring method, device, system and medium | |
| CN113364115A (en) | Power cable information comprehensive processing system and method | |
| CN108574957B (en) | Intelligent routing inspection server, routing inspection system and method for evolved packet core network equipment | |
| CN113238901B (en) | Multi-device automatic testing method and device, storage medium and computer device | |
| CN112311679B (en) | State detection method, state detection device, electronic equipment and readable storage medium | |
| CN112418622B (en) | Method for relatively positioning equipment for unknown electric meters in transformer area | |
| CN113868031A (en) | Method, device and system for testing performance consistency of hard disk | |
| CN114125864A (en) | MDT-based neighbor cell detection method and device | |
| CN111506507A (en) | Business service state detection method and device, electronic equipment and storage medium | |
| JP2008234232A (en) | Automatic test system, automatic test device, automatic test method and program | |
| CN112533233A (en) | Wireless network detection method, device and system based on user interaction |
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 |