CN110868338A - Early warning monitoring method - Google Patents
Early warning monitoring method Download PDFInfo
- Publication number
- CN110868338A CN110868338A CN201911145765.3A CN201911145765A CN110868338A CN 110868338 A CN110868338 A CN 110868338A CN 201911145765 A CN201911145765 A CN 201911145765A CN 110868338 A CN110868338 A CN 110868338A
- Authority
- CN
- China
- Prior art keywords
- module
- event
- data
- early warning
- rule
- 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
Images
Classifications
-
- 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/50—Testing arrangements
-
- 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/04—Processing captured monitoring data, e.g. for logfile generation
-
- 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/10—Active monitoring, e.g. heartbeat, ping or trace-route
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Data Mining & Analysis (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides an early warning monitoring method, which is based on an early warning monitoring system, and the system comprises a calculation module, a rule module and a bus module; the method comprises the steps of setting an early warning event, an early warning rule and/or a rule set; monitoring the bus module, and acquiring related data to perform rule judgment and perform related early warning operation; the bus module receives data and realizes the flow of communication between the modules; and (3) carrying out a persistence processing flow on the data circulating in the bus module. The invention utilizes event stream to communicate, has low requirement on the coupling between modules and realizes the automation of the early-warning monitoring process.
Description
Technical Field
The invention belongs to the technical field of monitoring, and particularly relates to an early warning monitoring method.
Background
In the context of big data, some larger companies monitor business data, and further develop a series of monitoring platforms. The existing monitoring platform has the following disadvantages:
1. data communication between components is protocol-based, and the coupling between components is high.
2. Most of the methods only support data offline calculation and have poor expansibility.
3. The existing scheme only supports simple early warning.
4. The operation of service personnel is complicated, the script needs to be operated manually, and the operability is poor.
5. Different business early warnings have different logics, and the later maintenance cost is extremely high.
If a set of efficient, perfect, highly available and extensible monitoring and early warning solution can be designed to solve the problems, the method has strong practical value and wide market prospect.
Disclosure of Invention
In order to solve the problems, the invention discloses an early warning monitoring method, which is based on an early warning monitoring system, wherein the system comprises a calculation module, a rule module and a bus module; the method comprises the following steps:
the business party selects the early warning event, the early warning rule and/or the flow of the rule set in the rule module;
the calculation module monitors the bus module and acquires the relevant data of the early warning event to carry out the processes of data calculation, task creation and task management;
the rule module monitors the bus module, acquires related data to judge rules and perform related early warning operation;
the bus module receives the service data issued by the external monitored service end and the related information issued by the rest modules, and realizes the communication flow among the rest modules;
and the data persistence module is used for carrying out persistence processing on the data circulated in the bus module.
Further, the system also comprises an event module, and when the rule module does not have the early warning event required by the business party, the method also comprises the step that the business party customizes the flow of the early warning event through the event module.
Further, the flow of the service side customizing the early warning event through the event module specifically comprises:
the method comprises the following steps: a service party creates a self-defined early warning event, which comprises determining an event definition, an event and data dependency relationship definition and an event completion rule definition, and sets metadata of the self-defined event, wherein the metadata is stored in an event module;
step two: the event module issues the relevant information created by the user-defined early warning event to the bus module and synchronizes to the persistence module.
Furthermore, the self-defined early warning event comprises a control event and a data event.
Further, the process of monitoring the bus module by the computing module, acquiring early warning related data, performing data computation and task creation specifically comprises the following steps:
the method comprises the following steps: the calculation module monitors the bus module, and when relevant information created by the user-defined early warning event is monitored, a generation script of relevant data is acquired;
step two: the computing module starts a task to compute related data and generates a corresponding task according to a computing result;
step three: the calculation result is returned to the bus module and synchronized to the data persistence module.
Further, the calculation module starts a task to calculate the related data of the early warning event, and in the step of generating the corresponding task according to the calculation result, the calculation module performs real-time calculation or off-line calculation on the related data and generates an off-line task or a real-time task according to the calculation result.
Further, the offline calculation is to perform batch calculation on the data in a specified time period before the predetermined time point at the predetermined time point.
Further, when the rule module does not have the rule and/or rule set required by the business party, the method further comprises the step that the business party customizes the rule and/or rule set through a rule configuration interface provided by the rule module.
Further, the bus module employs a message queue.
Further, the data persistence module adopts one or more of MySQ, HBase, Hive, Spark, ES and Kylin.
The invention has the beneficial effects that:
1. the invention adopts a communication mechanism based on event stream, the communication among all the components is based on an event bus, and the coupling is low.
2. And off-line calculation and real-time calculation of data are supported, and further delay monitoring early warning and real-time early warning are supported.
3. The invention realizes full process automation, including configuration of early warning information, data extraction, data layering, data storage and data early warning.
4. The invention has high expansibility, can effectively integrate all service early warnings and has low later maintenance cost.
Drawings
Fig. 1 is a block schematic diagram of a system on which the present invention is based.
Detailed Description
The design concept of the invention is as follows: the method is based on an early warning monitoring system, the system comprises a calculation module, a rule module and a bus module, communication among all components is based on an event bus, the coupling requirement is low, and automation of an early warning monitoring process is realized.
The system on which the invention is based will first be described in detail with reference to fig. 1.
The system comprises an event module, a calculation module, a rule module and a bus module. The following are introduced separately:
firstly, the method comprises the following steps: event module
The event module is configured to: and an event configuration interface is arranged for a service party to configure a self-defined early warning event, and the self-defined early warning event is issued to the bus module. The self-defined early warning events are divided into control type events (namely protocols) and data type events (namely examples).
Specifically, the event module also provides 3 main functions of permission isolation, event self-service operation and metadata management.
a. And (4) permission isolation:
1. a tenant mechanism is employed. The tenant mechanism virtually partitions the data and configuration of the event module, so that each tenant (namely a business side) can use a single instance, and each tenant can individually configure the leased instance according to the requirement of the tenant.
2. And a permission isolation measure is provided, and data sources and events which can be operated by different tenants are configured in advance by a platform administrator.
b. Self-service operation of self-defined event setting
And when the service side considers that the conventional early warning event can not meet the requirement and needs to be defined by users, event definition, event and data dependency relationship definition and event completion rule definition are carried out in an event configuration interface set by an event module by self.
When self-defined event self-service operation is carried out, the event module issues an 'event creation' message on the bus module, and the computing module can monitor the message. The destruction of events is performed without the need for pre-warning.
c. Metadata management
The event module provides metadata management capability for customizing the whole life cycle of the early warning event, metadata persistence capability (storing configuration information metadata into a relational database through a persistence module), metadata version snapshot capability (backing the event to a specific version), maintenance of mapping relation between the event and specific implementation thereof, support of control type events (namely protocols) and data type events (namely instances), and support of corresponding event and data dependency relation definition of a business party.
Second, calculating module
The computing module includes a task manager configured to: and monitoring an event data bus, acquiring a generation script corresponding to the custom early warning data after monitoring the event creation message, and then starting a task to calculate related data.
The calculation is divided into off-line calculation and real-time calculation. The off-line calculation adopts the technical means that the batch calculation is carried out on the data in the appointed time period before the preset time point at the preset time point through a HIVE module, a YARN module and an HDFS module of the HADOOP and through a task scheduling system. In the present embodiment, the off-line calculation is a calculation of data before the morning zero point of the day. The function of off-line calculation supports delay early warning. Offline task generation supports manual creation of timed tasks, addition to a data platform scheduling system for data dependency management and unified scheduling execution. The data platform scheduling system may employ existing tools, such as HERA,
and the real-time task generation support is to create a new real-time task according to the generation specification based on the event content. The calculated data is sent back to the event bus, and is subjected to persistence processing, monitoring is performed by the rule module, and rule hit refreshing is performed. The calculation processing of the early warning data event comprises the steps of generating an offline task and a real-time task by utilizing data.
The task manager monitors the control protocol events meeting the conditions through a daemon process, and performs task global management according to the control protocol events, such as 'creation event', 'destruction event' and the like. The creation event is a task that the computing module monitors an event bus to acquire a rule of an early warning event so as to establish an offline or real-time task (namely, a task created by a YARN cluster of the HADOOP), and the destruction event is to destroy the task in the HADOOP cluster.
If the event is accompanied by the task generated by the data (namely the data event), an 'offline task' or a 'real-time task' is newly established according to the configuration information in the early warning data event.
And standardizing data sources, output forms and the like of the offline tasks and the real-time tasks according to the metadata information.
Rule module
The rules module is configured to: the system is provided with a rule configuration interface, a user can select a predefined early warning data event and can customize a monitoring rule or a monitoring rule set to form a customized rule event. The custom rule event is published to an event bus. The rule module also monitors the bus module, carries out rule judgment on the obtained early warning data event and carries out corresponding early warning operation according to the judgment result. The early warning operation comprises grading early warning, on-duty early warning and time interval early warning. The meaning of the grading early warning is as follows: different early warning levels are set according to different employee levels and corresponding alarm severity levels, such as CTO level early warning, general supervision level early warning, general level communication early warning and the like.
The meaning of the on-duty early warning is as follows: the company can set the on-duty personnel every day, and the early warning information every day can be sent to the on-duty personnel;
the meaning of the time interval early warning is as follows: forewarning according to the grade time interval of forewarning, for example: the ordinary early warning is only the notification from eight early points to eight late points, and the severe early warning is performed in the whole time period.
The self-defined monitoring rule comprises a rule definition, a rule threshold value setting and a rule disposal action setting. The rule handling action settings include, but are not limited to, mail alerts, nail alerts, phone alerts, and generation of new events.
The custom rule set is a logical operation of the monitoring rules (and, or, not, etc.).
The rule module also supports the enabling, suspending of rules, rule sets.
The following exemplary rules may specifically include the following:
1. monitoring a name;
2. monitoring the object: such as city, media, channel, account, plan, unit, keyword, creative, search term;
3. monitoring range: account, channel, keyword type (including consumption-thread amount, daily average show amount-daily average click rate, thread cost-thread amount);
4. monitoring indexes: such as: exposure amount, click amount, consumption, exposure amount, consumption amount, clue cost, user rate, jump rate, abnormal keyword state, non-approved passing, too low search amount, and newly added or removed keywords.
5. Alarm threshold value: the method comprises upper limit reminding and lower limit reminding. If, the upper bound is reminded to: present day display amount > average over the past N days; the lower limit reminder is: present day display < average over the past N days. Can also set alarm information receiver
The rules module also supports the following functions:
1. metadata management capabilities that support the entire lifecycle of a rule, rule set.
2. The self-defined adding capability to the rule base, the knowledge base and the fact base is provided.
3. Providing metadata persistence capabilities.
4. Metadata version snapshot capability is provided that can roll back rules to a particular version.
5. If a rule handles an action as "generating a new event," then the mapping between the new event and its specific implementation needs to be maintained.
Bus module
The bus module is configured to receive service data issued by an external monitored service end and events, data and messages issued by the other modules, and the received service data, the events, the data and the messages are taken as circulation channels of the bus module to decouple the other modules and realize communication among the modules.
The bus module may be any message communication mechanism, if message queues are employed, the RabbitMQ, Kafka, etc. tools may be used.
Data persistence module
The module is mainly used for persisting events, rules, batch calculation data results, real-time calculation results and the like. The adopted infrastructure can be one or a combination of several of MySQL, HBase, Hive, Spark, ES, Kylin and other tools.
The early warning monitoring method of the present invention is explained below. The method is based on the early warning monitoring system and comprises the following processes:
the first process is as follows: and the business party selects the flow of the early warning event, the early warning rule and/or the rule set in the rule module.
And a second process: and the calculation module monitors the bus module and acquires the relevant data of the early warning event to perform the processes of data calculation, task creation and task management.
The second process specifically comprises the following steps:
the method comprises the following steps: and the calculation module monitors the bus module, and acquires a generation script of related data when monitoring related information created by the user-defined early warning event.
Step two: and the computing module starts the task to compute the related data and generates a corresponding task according to the computed result. The calculation of the calculation module is real-time calculation or off-line calculation, and an off-line task or a real-time task is generated according to a calculation result.
Step three: the calculation result is returned to the bus module and synchronized to the data persistence module.
And a third process: the rule module monitors the bus module, acquires related data to judge rules and perform related early warning operation;
and (4) a fourth process: the bus module receives the service data issued by the external monitored service end and the related information issued by the rest modules, and realizes the communication flow among the rest modules;
and a fifth process: and the data persistence module is used for carrying out persistence processing on the data circulated in the bus module.
The present embodiment does not limit the execution sequence of the above-mentioned flows, and the flows may be performed concurrently.
Preferably, when the rule module does not have the pre-warning event required by the service party, the method further includes the step that the service party self-defines the pre-warning event through an event configuration interface provided by the event module, and the method specifically includes the following steps:
the method comprises the following steps: a service party creates a self-defined early warning event, which comprises determining an event definition, an event and data dependency relationship definition and an event completion rule definition, and sets metadata of the self-defined event, wherein the metadata is stored in an event module;
step two: the event module issues the relevant information created by the user-defined early warning event to the bus module and synchronizes to the persistence module.
The self-defined early warning event comprises a control event and a data event.
Preferably, when the rule module does not have the rule and/or rule set required by the business party, the method further comprises the flow of customizing the rule and/or rule set through a rule configuration interface provided by the rule module by the business party.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited to the above embodiments, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present invention, and all those persons skilled in the art should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (10)
1. The early warning monitoring method is characterized in that the method is based on an early warning monitoring system, and the system comprises a calculation module, a rule module and a bus module; the method comprises the following steps:
the business party selects the early warning event, the early warning rule and/or the flow of the rule set in the rule module;
the calculation module monitors the bus module and acquires the relevant data of the early warning event to carry out the processes of data calculation, task creation and task management;
the rule module monitors the bus module, acquires related data to judge rules and perform related early warning operation;
the bus module receives the service data issued by the external monitored service end and the related information issued by the rest modules, and realizes the communication flow among the rest modules;
and the data persistence module is used for carrying out persistence processing on the data circulated in the bus module.
2. The warning monitoring method of claim 1, wherein the warning monitoring system further comprises an event module, and when the rule module does not have the warning event required by the service party, the method further comprises the step that the service party customizes the warning event through an event configuration interface provided by the event module.
3. The warning monitoring method of claim 2, wherein the flow of the self-defining warning event through the event configuration interface provided by the event module by the service party is specifically as follows:
the method comprises the following steps: a service party creates a self-defined early warning event, which comprises determining an event definition, an event and data dependency relationship definition and an event completion rule definition, and sets metadata of the self-defined event, wherein the metadata is stored in an event module;
step two: the event module issues the relevant information created by the user-defined early warning event to the bus module and synchronizes to the persistence module.
4. The warning monitoring method of claim 2, wherein the custom warning event includes both control type events and data type events.
5. The early warning monitoring method according to claim 2, wherein the process of monitoring the bus module by the computing module, acquiring early warning related data, performing data computation and task creation specifically comprises the following steps:
the method comprises the following steps: the calculation module monitors the bus module, and when relevant information created by the user-defined early warning event is monitored, a generation script of relevant data is acquired;
step two: the computing module starts a task to compute related data and generates a corresponding task according to a computing result;
step three: the calculation result is returned to the bus module and synchronized to the data persistence module.
6. The warning monitoring method of claim 5, wherein the computing module starts a task to perform the computation of the related data of the warning event, and in the step of generating the corresponding task according to the computation result, the computing module performs real-time computation or off-line computation on the related data, and generates an off-line task or a real-time task according to the computation result.
7. The warning monitoring method of claim 6, wherein the offline calculation is a batch calculation of data at a predetermined point in time and within a specified period of time prior to the predetermined point in time.
8. The warning monitoring method of claim 1, wherein when the rules and/or rule sets required by the business party are not available in the rule module, the method further comprises the business party customizing the flow of the warning rules and/or rule sets through a rule configuration interface provided by the rule module.
9. The warning monitoring method of claim 1, wherein the bus module employs a message queue.
10. The warning monitoring method as claimed in claim 1, wherein the data persistence module employs one or more of MySQ, HBase, Hive, Spark, ES, and Kylin.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911145765.3A CN110868338B (en) | 2019-11-21 | 2019-11-21 | Early warning monitoring method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911145765.3A CN110868338B (en) | 2019-11-21 | 2019-11-21 | Early warning monitoring method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110868338A true CN110868338A (en) | 2020-03-06 |
| CN110868338B CN110868338B (en) | 2021-05-25 |
Family
ID=69655275
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911145765.3A Expired - Fee Related CN110868338B (en) | 2019-11-21 | 2019-11-21 | Early warning monitoring method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110868338B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111508214A (en) * | 2020-04-22 | 2020-08-07 | 杭州电子科技大学 | Alarm control method and control equipment |
| CN115174351A (en) * | 2022-07-07 | 2022-10-11 | 深圳市积加跨境网络科技有限公司 | E-commerce operation early warning data generation method |
| CN116483822A (en) * | 2023-06-21 | 2023-07-25 | 建信金融科技有限责任公司 | Service data early warning method, device, computer equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110149744A1 (en) * | 2009-12-18 | 2011-06-23 | Vonage Network Llc | Method and apparatus for directing the installation of voip devices |
| CN104317624A (en) * | 2014-11-04 | 2015-01-28 | 南京联创科技集团股份有限公司 | Plug-in processing based data assembling method |
| CN104410512A (en) * | 2014-10-28 | 2015-03-11 | 国云科技股份有限公司 | Resource monitoring alarm framework suitable for cloud computation and method thereof |
| CN105717887A (en) * | 2014-12-05 | 2016-06-29 | 克拉玛依红有软件有限责任公司 | Oil gas processing station intelligent early warning system based on Internet of things sensing data |
-
2019
- 2019-11-21 CN CN201911145765.3A patent/CN110868338B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110149744A1 (en) * | 2009-12-18 | 2011-06-23 | Vonage Network Llc | Method and apparatus for directing the installation of voip devices |
| CN104410512A (en) * | 2014-10-28 | 2015-03-11 | 国云科技股份有限公司 | Resource monitoring alarm framework suitable for cloud computation and method thereof |
| CN104317624A (en) * | 2014-11-04 | 2015-01-28 | 南京联创科技集团股份有限公司 | Plug-in processing based data assembling method |
| CN105717887A (en) * | 2014-12-05 | 2016-06-29 | 克拉玛依红有软件有限责任公司 | Oil gas processing station intelligent early warning system based on Internet of things sensing data |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111508214A (en) * | 2020-04-22 | 2020-08-07 | 杭州电子科技大学 | Alarm control method and control equipment |
| CN111508214B (en) * | 2020-04-22 | 2022-04-22 | 杭州电子科技大学 | Alarm control method and control equipment |
| CN115174351A (en) * | 2022-07-07 | 2022-10-11 | 深圳市积加跨境网络科技有限公司 | E-commerce operation early warning data generation method |
| CN116483822A (en) * | 2023-06-21 | 2023-07-25 | 建信金融科技有限责任公司 | Service data early warning method, device, computer equipment and storage medium |
| CN116483822B (en) * | 2023-06-21 | 2023-09-26 | 建信金融科技有限责任公司 | Service data early warning method, device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110868338B (en) | 2021-05-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110868338B (en) | Early warning monitoring method | |
| US11277483B2 (en) | Assessing user activity using dynamic windowed forecasting on historical usage | |
| CN104065741B (en) | Data collecting system and collecting method | |
| CN107786616A (en) | Main frame intelligent monitor system based on high in the clouds | |
| CN106960292A (en) | A kind of operation flow monitoring system and method applied to Utilities Electric Co. | |
| CN114925045B (en) | PaaS platform for big data integration and management | |
| CN114443435A (en) | Container micro-service oriented performance monitoring alarm method and alarm system | |
| CN112015753B (en) | Monitoring system and method suitable for containerized deployment of open source cloud platform | |
| CN110221947A (en) | Warning information method for inspecting, system, computer installation and readable storage medium storing program for executing | |
| CN111754123A (en) | Data monitoring method and device, computer equipment and storage medium | |
| CN115860729A (en) | IT operation and maintenance integrated management system | |
| US10331484B2 (en) | Distributed data platform resource allocator | |
| CN111625410B (en) | Information processing method, apparatus, and computer storage medium | |
| CN109067000A (en) | One kind matching electricity consumption intelligence load monitoring system | |
| CN103986607A (en) | Voice-sound-light alarm monitoring system for intelligent data center | |
| CN109840141A (en) | Thread control method, device, electronic equipment and storage medium based on cloud monitoring | |
| CN109582531A (en) | Monitoring method, device and the electronic equipment of power distribution unit | |
| CN110796341B (en) | Distributed batch processing method and device for collecting cases and electronic equipment | |
| CN112016813A (en) | Method for monitoring power supply and utilization service state of directional important power customer | |
| CN109858807A (en) | A kind of method and system of enterprise operation monitoring | |
| CN105493443A (en) | Social networking information consumption gap resolution | |
| CN109635560A (en) | Offshore platform generalized information management system | |
| CN110855527A (en) | Early warning monitoring system | |
| CN107145427A (en) | A kind of method and system of automatic classification monitoring application service daily record | |
| CN108154343B (en) | Emergency processing method and system for enterprise-level information system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210825 Address after: 100000 1025, floor 1, No. 1, Kaifa Road, Shangdi Information Industry base, Haidian District, Beijing Patentee after: Beijing tulayan Technology Co.,Ltd. Address before: 100089 08a01, block D, 8 / F, No. a 28, information road, Haidian District, Beijing Patentee before: Beijing Gaoyin Technology Co.,Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20210525 Termination date: 20211121 |