CN111814178A - Data callback fusing protection method for third-party application - Google Patents
Data callback fusing protection method for third-party application Download PDFInfo
- Publication number
- CN111814178A CN111814178A CN202010606816.4A CN202010606816A CN111814178A CN 111814178 A CN111814178 A CN 111814178A CN 202010606816 A CN202010606816 A CN 202010606816A CN 111814178 A CN111814178 A CN 111814178A
- Authority
- CN
- China
- Prior art keywords
- callback
- party application
- fusing
- time
- data
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6272—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database by registering files or documents with a third party
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6281—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database at program execution time, where the protection is within the operating system
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Bioethics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Databases & Information Systems (AREA)
- Retry When Errors Occur (AREA)
Abstract
The invention discloses a data callback fusing protection method for third-party application, which can realize a fusing protection function for the granularity of the third-party application without using a uniform registration center, namely, after a callback platform finds that the third-party application A is unavailable, data callback cannot be performed on the third-party application A within a period of time, but data callback of other healthy third-party applications cannot be influenced, so that the waste of callback resources is avoided. The situation that the whole callback system is dragged down due to the unavailability of the application A is prevented.
Description
Technical Field
The invention relates to the technical field of internet and internet of things, in particular to a data callback fusing protection method for third-party application.
Background
In the application of the internet of things, a large number of scenes of data callback to third-party applications exist, and because the states of the third-party applications are unknown, a fuse is generally required to be used for protecting resources of a callback platform, so that the phenomenon that when a certain third-party application is unavailable, excessive callback resources are consumed, and the whole callback service platform is dragged down is prevented. At present, the mainstream fuse in the industry is represented by Hystrix, and fusing protection of service granularity is realized based on a micro-service management framework; i.e. which service is not available, is fuse protected for this service, but the disadvantage is that the called service has to be required to be registered uniformly in a registry (e.g. Eureka, Zookeeper, etc.). For a data callback scene of a third-party application, the third-party application cannot be required to be registered in a unified registration center, so that the traditional fusing protection method cannot meet the requirements of the service scene.
Disclosure of Invention
The invention aims to solve the problems and provides a data callback fusing protection method for third-party application.
After the communication and coordination between the callback platform and the third-party application service party, the callback platform party independently maintains the basic information of the third-party application to the third-party application callback information state table of the third-party application. Specifically, the elements such as appId, callback address url, fuse state, failure times, breaker _ time and the like of the third-party application to be called back are respectively stored in a database, a cache or a readable and writable file system according to the granularity of the third-party application, so that the call-back platform can conveniently read and modify the elements. When data needs to be called back to a third-party application, the third-party application and the third-party application appId to which the call-back data belongs are found according to the call-back data, a call-back state information record corresponding to the application is found from a call-back information state table according to the appId, and whether the third-party application is called back or not is comprehensively determined according to the recorded fuse state, failure times and break time. And if the third-party application is called back, updating the fusing state, the failure times and the break time of the fuse according to the success or failure of the calling-back result, so as to determine whether the third-party application is called back or not when the data is called back next time. Finally, the purpose of the third-party application granularity fusing protection is achieved on the premise that the third-party application is not uniformly registered in the registration center.
The invention realizes the purpose through the following technical scheme:
a data callback fusing protection method for third-party application comprises the following steps:
s1, determining an interface of the callback platform, which needs to perform data callback on the third-party application, between the callback platform side and the third-party application service side, and recording the third-party application and the callback address url corresponding to the interface;
s2 initializing the static application information of the callback information state table;
s3 initializing the blown dynamic element of the callback information state table; to represent the concept that no fusing initially occurs, the initialization operation is set as follows: initializing a fusing state to be that the fuse is closed, initializing a callback failure number value to be 0, and initializing breaker _ time to be null or null; wherein break _ time represents the moment when the fusing occurs;
s4, storing the appId, callback address url, fuse state, failure times and break _ time of the third-party application to be called back into a database, a cache or a readable and writable file system, so as to ensure that the callback platform can conveniently read and modify the elements;
s5, when data needs to call back the third-party application, finding the third-party application to which the call-back data belongs according to the call-back data; for example, finding the attributive application A according to the callback data A; in a software system, mapping the callback data A to appId _ A, and finding a callback state information record A corresponding to the application A from a callback information state table through the appId _ A;
the s6 callback platform determines whether to perform data callback on the third-party application according to the fuse state, the failure frequency and other elements in the record A; according to whether the callback result is successful, the failure times of the record A are modified, and the fusing state of the fuse is converted;
s7 when there is a new callback, the steps of s1-s6 are repeated.
Further, the step s2 specifically includes:
s2.1, summarizing the third-party applications needing to be called back, and distributing a unique identifier, which can be appId, for each third-party application; if the third-party application A corresponds to the appId _ A, the third-party application B corresponds to the appId _ B, and so on;
s2.2 associates an application callback address url for each third party application's appId.
Further, in the step s6, the following steps are specifically performed:
s6.1, when data A is recalled and the fuse corresponding to A is recorded to be in a fusing off state, directly recalling the data to a third-party application A; according to the success or failure of the callback result, the method is divided into the following two substeps:
s6.1.1, if the third-party application A is called back successfully, the fuse state and the failure times of the record A are not modified;
s6.1.2, if the third-party application A is called back to fail, adding 1 to the failure times of recording A; the callback platform needs to set a maximum failure time threshold value max _ error allowed by callback in advance, if the error time is greater than the threshold value max _ error, the fuse is modified to be in a fusing open state, and the fusing time break _ time _ A _1 is saved;
s6.2 when the data A is recalled and the fuse state of the corresponding record A is fusing and opened, the callback platform needs to set a fusing time range in advance; according to the current time, breaker _ time and fusing time, the relationship among the three is divided into the following two conditions:
s6.2.1 if the condition is satisfied: if the current time-breaker _ time _ A _1 is smaller than the fusing time, the third-party application is not called back, so that the waste of calling back resources is reduced;
s6.2.2 if the condition is satisfied: if the current time-breaker _ time _ A _1 is larger than the fusing time, trying to call back the third-party application, and if the call-back is successful, resetting the recorded failure times of A and modifying the fuse into a fusing off state; if the callback fails, only the break _ time recorded in the record A is updated to be the latest break _ time _ A _2 at the current moment, and the rest parameters are not processed.
The invention has the beneficial effects that:
according to the data callback fusing protection method for the third-party application, the fusing protection function can be realized for the granularity of the third-party application without using a uniform registration center, namely after the callback platform finds that the third-party application A is unavailable, data callback cannot be performed on the third-party application A within a period of time, but data callback of other healthy third-party applications cannot be influenced, so that the waste of callback resources is avoided. The situation that the whole callback system is dragged down due to the unavailability of the application A is prevented.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the embodiments or the drawings needed to be practical in the prior art description, and obviously, the drawings in the following description are only some embodiments of the embodiments, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic diagram of the fuse and callback information states of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without any inventive step, are within the scope of the present invention.
The core of the invention is a fuse and callback information state table: the fuse determines whether to call back the third-party application or not; the callback information state table maintains static application information and dynamic fusing elements of the third-party application.
The static application information comprises a unique identifier of the third-party application and a callback address url of the third-party application. Generally, before the actual data callback occurs, the callback platform side and the third-party application service side negotiate to determine the actual data callback. These two pieces of information are generally not modified if the third party application is not changed. The dynamic element comprises a fuse state corresponding to the third-party application and failure times of the callback platform for requesting the third-party data.
In any embodiment, as shown in fig. 1, a method for callback fusing and protecting data for a third-party application of the present invention includes:
s1, determining an interface of the callback platform, which needs to perform data callback on the third-party application, between the callback platform side and the third-party application service side, and recording the third-party application and the callback address url corresponding to the interface;
s2 initializing the static application information of the callback information state table;
s2.1, summarizing the third-party applications needing to be called back, and allocating a unique identifier to each third-party application, wherein the unique identifier can be but is not limited to appId; for example, the third-party application A corresponds to the appId _ A, the third-party application B corresponds to the appId _ B, and so on;
s2.2 associating an application callback address url with the appId of each third-party application;
s3 initializing the blown dynamic element of the callback information state table; to represent the concept that no fusing initially occurs, the following initialization operations are specified: initializing a fusing state to be that the fuse is closed, initializing a callback failure number value to be 0, and initializing breaker _ time to be null or null; wherein break _ time represents the moment when the fusing occurs;
s4, uniformly storing the appId, callback address url, fuse state, failure times, breaker _ time and other elements of the third-party application to be called back into a database, a cache or a readable and writable file system, so as to ensure that the callback platform can conveniently read and modify the elements; the stored information element sets are collectively called as a callback information state table;
s5, when data needs to call back a third-party application, first finding the third-party application to which the call-back data belongs according to the call-back data, for example, finding the application a to which the call-back data belongs according to the call-back data a; generally, in a software system, mapping the callback data A to appId _ A, and finding a callback state information record A corresponding to an application A from a callback information state table through appId _ A;
the s6 callback platform determines whether to perform data callback on the third-party application according to the fuse state, the failure frequency and other elements in the record A; according to whether the callback result is successful, the failure times of the record A are modified, and the fusing state of the fuse is converted, which is specifically as follows:
s6.1, when data A is recalled and the fuse corresponding to A is recorded to be in a fusing off state, directly recalling the data to a third-party application A; according to the success or failure of the callback result, the method is divided into the following two substeps:
s6.1.1, if the third-party application A is called back successfully, the fuse state and the failure times of the record A are not modified;
s6.1.2, if the third-party application A is called back to fail, adding 1 to the failure times of recording A; the callback platform needs to set a maximum failure time threshold value max _ error allowed by callback in advance, if the error time is greater than the threshold value max _ error, the fuse is modified to be in a fusing open state, and the fusing time break _ time _ A _1 is saved;
s6.2 when the data A is recalled and the fuse state of the corresponding record A is fusing and opened, the callback platform needs to set a fusing time range in advance; according to the current time, breaker _ time (fusing occurrence time) and fusing time (fusing time length), the relationship between the three is divided into the following two conditions:
s6.2.1 if the condition is satisfied: if the current time-breaker _ time _ A _1 is smaller than the fusing time, the third-party application is not called back, so that the waste of calling back resources is reduced;
s6.2.2 if the condition is satisfied: if the current time-breaker _ time _ A _1 is larger than the fusing time, trying to call back the third-party application, and if the call-back is successful, resetting the recorded failure times of A and modifying the fuse into a fusing off state; if the callback fails, only updating the breaker _ time recorded in the record A to be the breaker _ time _ A _2 at the current latest moment, and not processing other parameters;
s7 when there is a new callback, the steps of s1-s6 are repeated.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions 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. It should be noted that the various technical features described in the above embodiments can be combined in any suitable manner without contradiction, and the invention is not described in any way for the possible combinations in order to avoid unnecessary repetition. In addition, any combination of the various embodiments of the present invention is also possible, and the same should be considered as the disclosure of the present invention as long as it does not depart from the spirit of the present invention.
Claims (3)
1. A data callback fusing protection method for third-party application is characterized by comprising the following steps:
s1, determining an interface of the callback platform, which needs to perform data callback on the third-party application, between the callback platform side and the third-party application service side, and recording the third-party application and the callback address url corresponding to the interface;
s2 initializing the static application information of the callback information state table;
s3 initializing the blown dynamic element of the callback information state table; to represent the concept that no fusing initially occurs, the initialization operation is set as follows: initializing a fusing state to be that the fuse is closed, initializing a callback failure number value to be 0, and initializing breaker _ time to be null or null; wherein break _ time represents the moment when the fusing occurs;
s4, storing the appId, callback address url, fuse state, failure times and break _ time of the third-party application to be called back into a database, a cache or a readable and writable file system, so as to ensure that the callback platform can conveniently read and modify the elements;
s5, when data needs to call back the third-party application, finding the third-party application to which the call-back data belongs according to the call-back data; for example, finding the attributive application A according to the callback data A; in a software system, mapping the callback data A to appId _ A, and finding a callback state information record A corresponding to the application A from a callback information state table through the appId _ A;
the s6 callback platform determines whether to perform data callback on the third-party application according to the fuse state, the failure frequency and other elements in the record A; according to whether the callback result is successful, the failure times of the record A are modified, and the fusing state of the fuse is converted;
s7 when there is a new callback, the steps of s1-s6 are repeated.
2. The method for callback fusing protection of data to a third party application as claimed in claim 1, wherein the step s2 specifically comprises:
s2.1, summarizing the third-party applications needing to be called back, and distributing a unique identifier, which can be appId, for each third-party application; if the third-party application A corresponds to the appId _ A, the third-party application B corresponds to the appId _ B, and so on;
s2.2 associates an application callback address url for each third party application's appId.
3. The method for callback fusing protection of data to a third party application as claimed in claim 1, wherein in step s6, the following is specifically performed:
s6.1, when data A is recalled and the fuse corresponding to A is recorded to be in a fusing off state, directly recalling the data to a third-party application A; according to the success or failure of the callback result, the method is divided into the following two substeps:
s6.1.1, if the third-party application A is called back successfully, the fuse state and the failure times of the record A are not modified;
s6.1.2, if the third-party application A is called back to fail, adding 1 to the failure times of recording A; the callback platform needs to set a maximum failure time threshold value max _ error allowed by callback in advance, if the error time is greater than the threshold value max _ error, the fuse is modified to be in a fusing open state, and the fusing time break _ time _ A _1 is saved;
s6.2 when the data A is recalled and the fuse state of the corresponding record A is fusing and opened, the callback platform needs to set a fusing time range in advance; according to the current time, breaker _ time and fusing time, the relationship among the three is divided into the following two conditions:
s6.2.1 if the condition is satisfied: if the current time-breaker _ time _ A _1 is smaller than the fusing time, the third-party application is not called back, so that the waste of calling back resources is reduced;
s6.2.2 if the condition is satisfied: if the current time-breaker _ time _ A _1 is larger than the fusing time, trying to call back the third-party application, and if the call-back is successful, resetting the recorded failure times of A and modifying the fuse into a fusing off state; if the callback fails, only the break _ time recorded in the record A is updated to be the latest break _ time _ A _2 at the current moment, and the rest parameters are not processed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010606816.4A CN111814178A (en) | 2020-06-29 | 2020-06-29 | Data callback fusing protection method for third-party application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010606816.4A CN111814178A (en) | 2020-06-29 | 2020-06-29 | Data callback fusing protection method for third-party application |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111814178A true CN111814178A (en) | 2020-10-23 |
Family
ID=72855589
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010606816.4A Pending CN111814178A (en) | 2020-06-29 | 2020-06-29 | Data callback fusing protection method for third-party application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111814178A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114327832A (en) * | 2021-12-30 | 2022-04-12 | 胜斗士(上海)科技技术发展有限公司 | Callback processing method and platform, device, storage medium and program product |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080320259A1 (en) * | 2007-06-21 | 2008-12-25 | Garg Vijay K | Method for Providing Fault Tolerance to Multiple Servers |
| CN106776099A (en) * | 2017-01-11 | 2017-05-31 | 北京皮尔布莱尼软件有限公司 | One kind service fusing shielding system and method |
| CN107608812A (en) * | 2017-09-08 | 2018-01-19 | 北京奇艺世纪科技有限公司 | A kind of blowout method and server |
| CN108111467A (en) * | 2016-11-24 | 2018-06-01 | 华为技术有限公司 | Identity identifying method and equipment and system |
| CN108681476A (en) * | 2018-05-08 | 2018-10-19 | 广州品唯软件有限公司 | A kind of automatic blowout method of physical layer interface and device |
| CN109240765A (en) * | 2018-08-28 | 2019-01-18 | 中国联合网络通信集团有限公司 | Blowout method, device, equipment and the computer readable storage medium of Service Source |
| CN110399178A (en) * | 2019-06-14 | 2019-11-01 | 五八有限公司 | A kind of call method of third party's service, device, electronic equipment and storage medium |
| CN110580234A (en) * | 2019-08-22 | 2019-12-17 | 广州易起行信息技术有限公司 | Fusing method suitable for micro server and external system |
| CN110737567A (en) * | 2019-10-17 | 2020-01-31 | 吉旗（成都）科技有限公司 | Server-side interface fusing method and device based on cache |
| CN111078453A (en) * | 2019-12-17 | 2020-04-28 | 深圳前海环融联易信息科技服务有限公司 | Method and device for automatically fusing and recovering micro-service, computer equipment and storage medium |
| CN111324477A (en) * | 2020-02-03 | 2020-06-23 | 北京同邦卓益科技有限公司 | Processing method and device for distributed fusing |
-
2020
- 2020-06-29 CN CN202010606816.4A patent/CN111814178A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080320259A1 (en) * | 2007-06-21 | 2008-12-25 | Garg Vijay K | Method for Providing Fault Tolerance to Multiple Servers |
| CN108111467A (en) * | 2016-11-24 | 2018-06-01 | 华为技术有限公司 | Identity identifying method and equipment and system |
| CN106776099A (en) * | 2017-01-11 | 2017-05-31 | 北京皮尔布莱尼软件有限公司 | One kind service fusing shielding system and method |
| CN107608812A (en) * | 2017-09-08 | 2018-01-19 | 北京奇艺世纪科技有限公司 | A kind of blowout method and server |
| CN108681476A (en) * | 2018-05-08 | 2018-10-19 | 广州品唯软件有限公司 | A kind of automatic blowout method of physical layer interface and device |
| CN109240765A (en) * | 2018-08-28 | 2019-01-18 | 中国联合网络通信集团有限公司 | Blowout method, device, equipment and the computer readable storage medium of Service Source |
| CN110399178A (en) * | 2019-06-14 | 2019-11-01 | 五八有限公司 | A kind of call method of third party's service, device, electronic equipment and storage medium |
| CN110580234A (en) * | 2019-08-22 | 2019-12-17 | 广州易起行信息技术有限公司 | Fusing method suitable for micro server and external system |
| CN110737567A (en) * | 2019-10-17 | 2020-01-31 | 吉旗（成都）科技有限公司 | Server-side interface fusing method and device based on cache |
| CN111078453A (en) * | 2019-12-17 | 2020-04-28 | 深圳前海环融联易信息科技服务有限公司 | Method and device for automatically fusing and recovering micro-service, computer equipment and storage medium |
| CN111324477A (en) * | 2020-02-03 | 2020-06-23 | 北京同邦卓益科技有限公司 | Processing method and device for distributed fusing |
Non-Patent Citations (1)
| Title |
|---|
| 黄强文 等: ""基于Spring Cloud和Docker的分布式微服务架构设计"", 《微型电脑应用》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114327832A (en) * | 2021-12-30 | 2022-04-12 | 胜斗士(上海)科技技术发展有限公司 | Callback processing method and platform, device, storage medium and program product |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10511506B2 (en) | Method and device for managing virtualized network function | |
| CN112003961A (en) | A resource exposure method, system, device and medium in kubernetes | |
| CN112114894B (en) | Process processing method, device and electronic device based on Activiti process engine | |
| CN106331065A (en) | Proxy application for host system with service container and system | |
| US9830333B1 (en) | Deterministic data replication with conflict resolution | |
| CN114900449B (en) | Resource information management method, system and device | |
| EP3703337A1 (en) | Mobile edge host-machine service notification method and apparatus | |
| CN116542668A (en) | Block chain-based data processing method, equipment and readable storage medium | |
| CN116341508A (en) | Dynamic configuration method, device, computer equipment and storage medium of message template | |
| CN119487499A (en) | Communication system node with multiple modules and shared memory | |
| CN115567388A (en) | Network slice configuration automatic update method, system, device and storage medium | |
| CN114880013A (en) | A method and device for processing configuration information of a business process | |
| CN111814178A (en) | Data callback fusing protection method for third-party application | |
| CN100559778C (en) | Method and system for interfacing to application components | |
| CN113472687B (en) | Data processing method and device | |
| US20010018678A1 (en) | Caching mechanism to optimize a bidding process used to select resources and services | |
| CN115914405B (en) | Service processing method and device | |
| CN113515458B (en) | Method and system for reducing test environment resource consumption based on Envoy plug-in | |
| CN115361440B (en) | Method and device for updating endpoint resources of multiple Kubernetes clusters and electronic equipment | |
| CN109033134A (en) | A kind of message treatment method, device, storage medium and computer equipment | |
| CN115794396A (en) | Resource allocation method, system and electronic equipment | |
| CN115276777B (en) | TDMA networking parameter management method based on data abstract and time stamp | |
| CN109104321B (en) | Method for improving Web _ HDFS availability under Hadoop dual-computer cluster | |
| CN116319239B (en) | Service calling method, device, computer equipment and storage medium | |
| CN114173007B (en) | A communication method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201023 |