CN112671836A - Method for accelerating user request based on CDN technology - Google Patents
Method for accelerating user request based on CDN technology Download PDFInfo
- Publication number
- CN112671836A CN112671836A CN202011418272.5A CN202011418272A CN112671836A CN 112671836 A CN112671836 A CN 112671836A CN 202011418272 A CN202011418272 A CN 202011418272A CN 112671836 A CN112671836 A CN 112671836A
- Authority
- CN
- China
- Prior art keywords
- cdn
- remote
- load balancing
- content
- resource
- 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
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to the technical field of computers, in particular to a method for accelerating user requests based on a CDN technology, which comprises the following steps: and (3) access request: a client initiates a content URL access request, and a remote website server closest to a user requests a remote website DNS server to perform domain name resolution on URL access corresponding to the content of the user URL access request; load balancing: the remote website DNS server transfers the domain name resolution right to a remote CDN special DNS server, and then the remote CDN special DNS server transfers a corresponding access request to a remote CDN global load balancing system; the invention can enable the user to obtain the required content nearby, relieve the condition of network congestion delay, improve the response speed of the user for accessing the website, realize the purpose of reducing the response time for accessing the dynamic content of the internet and the total network flow by distributing the internet application program code to the CDN edge nodes at the edge of the network, and improve the utilization rate of the computing resources of the computer equipment.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method for accelerating user requests based on a CDN technology.
Background
The CDN is also called a Content Delivery Network, and a basic idea of the CDN is to place node servers at various places in a Network to form a layer of intelligent virtual Network on the existing internet basis through the node servers, so as to avoid possible speed bottlenecks and unstable Network links on the internet, and make Content transmission faster and more stable.
In a traditional access mode, users directly face a server accessing a target website, but when the number of accessing users is large, network access delay is easily caused, response speed of network access is affected, only static content can be cached, a large amount of computing resources are idle, and the resource utilization rate is low.
SUMMARY OF THE PATENT FOR INVENTION
The invention aims to provide a method for accelerating user requests based on a CDN technology, which solves the problems that when the number of access users is large, network access delay is easily caused, the response speed of network access is influenced, only static content can be cached, a large amount of computing resources are idle, and the resource utilization rate is low.
In order to achieve the purpose, the invention provides the following technical scheme: a method for accelerating user request based on CDN technology comprises the following steps:
step 1: and (3) access request: a client initiates a content URL access request, and a remote website server closest to a user requests a remote website DNS server to perform domain name resolution on URL access corresponding to the content of the user URL access request;
step 2: load balancing: the remote website DNS server transfers the domain name resolution right to a remote CDN special DNS server, then the remote CDN special DNS server transfers the corresponding access request to a remote CDN global load balancing system, and then the remote CDN global load balancing system transfers the corresponding access request to a remote CDN regional load balancing system;
and step 3: request target URL points to resource: the remote CDN regional load balancing system feeds back an IP address corresponding to the CDN edge computing server through a remote CDN special DNS server, and then requests a resource pointed by a target URL (uniform resource locator) to the CDN edge computing server according to the IP address corresponding to the CDN edge computing server;
and 4, step 4: judging dynamic and static states: judging whether the resource is dynamic content according to the resource pointed by the target URL requested by the CDN edge computing server, if so, requesting a Docker mirror image containing a resource program and a database from a Docker warehouse, downloading the Docker mirror image of the database, starting a Docker container, executing the program in the Docker mirror image of the database, generating dynamic content corresponding to the program, and feeding back the dynamic content to the client;
and 5: static content query: if the local cache is not dynamic content, the static content is inquired, whether the local cache has the cache of the resource is judged, if yes, the cached resource is immediately taken and fed back to the client, and if not, the cached resource is taken from the data center and fed back to the client.
Preferably, in step 1, the developed program for generating dynamic content is uploaded to a Docker warehouse in advance and deployed to a data center.
Preferably, in step 2, in the domain name resolution process of the local DNS system, the CDN-dedicated DNS server is a CDN-dedicated DNS server to which the CNAME points.
Preferably, in step 2, the DNS server dedicated for the CDN feeds back an IP address of one device in the CDN global load balancing system, and initiates a content URL access request to the corresponding device according to the IP address.
Preferably, in step 2, the device in the CDN global load balancing system selects a CDN regional load balancing system closest to the client according to the IP address of the client and the request content URL of the client, and then selects one regional load balancing device from the CDN regional load balancing system.
Preferably, in step 3, the DNS server dedicated to the CDN resolves the domain name to the IP address of the CDN edge computing server closest to the user according to the location information of the user location.
Preferably, in step 5, the suffix name of the dynamic content is jsp, php, action or do, and the suffix name of the static content is jpg, png, js or html.
Compared with the prior art, the invention has the following beneficial effects:
the invention can enable the user to obtain the required content nearby, relieve the condition of network congestion delay, improve the response speed of the user for accessing the website, realize the purpose of reducing the response time for accessing the dynamic content of the internet and the total network flow by distributing the internet application program code to the CDN edge nodes at the edge of the network, and improve the utilization rate of the computing resources of the computer equipment.
Drawings
FIG. 1 is a flow chart of the inventive patent architecture;
fig. 2 is a schematic diagram of the patent structure of the invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the patent of the invention without any inventive work belong to the protection scope of the patent of the invention.
Referring to fig. 1-2, a method for accelerating a user request based on a CDN technique includes the following steps:
step 1: and (3) access request: a client initiates a content URL access request, and a remote website server closest to a user requests a remote website DNS server to perform domain name resolution on URL access corresponding to the content of the user URL access request;
step 2: load balancing: the remote website DNS server transfers the domain name resolution right to a remote CDN special DNS server, then the remote CDN special DNS server transfers the corresponding access request to a remote CDN global load balancing system, and then the remote CDN global load balancing system transfers the corresponding access request to a remote CDN regional load balancing system;
and step 3: request target URL points to resource: the remote CDN regional load balancing system feeds back an IP address corresponding to the CDN edge computing server through a remote CDN special DNS server, and then requests a resource pointed by a target URL (uniform resource locator) to the CDN edge computing server according to the IP address corresponding to the CDN edge computing server;
and 4, step 4: judging dynamic and static states: judging whether the resource is dynamic content according to the resource pointed by the target URL requested by the CDN edge computing server, if so, requesting a Docker mirror image containing a resource program and a database from a Docker warehouse, downloading the Docker mirror image of the database, starting a Docker container, executing the program in the Docker mirror image of the database, generating dynamic content corresponding to the program, and feeding back the dynamic content to the client;
and 5: static content query: if the local cache is not dynamic content, the static content is inquired, whether the local cache has the cache of the resource is judged, if yes, the cached resource is immediately taken and fed back to the client, and if not, the cached resource is taken from the data center and fed back to the client.
The first embodiment is as follows:
and (3) access request: a client initiates a content URL access request, and a remote website server closest to a user requests a remote website DNS server to perform domain name resolution on URL access corresponding to the content of the user URL access request; load balancing: the remote website DNS server transfers the domain name resolution right to a remote CDN special DNS server, then the remote CDN special DNS server transfers the corresponding access request to a remote CDN global load balancing system, and then the remote CDN global load balancing system transfers the corresponding access request to a remote CDN regional load balancing system; request target URL points to resource: the remote CDN regional load balancing system feeds back an IP address corresponding to the CDN edge computing server through a remote CDN special DNS server, and then requests a resource pointed by a target URL (uniform resource locator) to the CDN edge computing server according to the IP address corresponding to the CDN edge computing server; judging dynamic and static states: judging whether the resource is dynamic content according to the resource pointed by the target URL requested by the CDN edge computing server, if so, requesting a Docker mirror image containing a resource program and a database from a Docker warehouse, downloading the Docker mirror image of the database, starting a Docker container, executing the program in the Docker mirror image of the database, generating dynamic content corresponding to the program, and feeding back the dynamic content to the client; static content query: if the local cache is not dynamic content, the static content is inquired, whether the local cache has the cache of the resource is judged, if yes, the cached resource is immediately taken and fed back to the client, and if not, the cached resource is taken from the data center and fed back to the client.
Example two:
in the first embodiment, the following steps are added:
in step 1, the developed program for generating dynamic content is uploaded to a Docker warehouse in advance and is deployed to a data center, so that the work of subsequent programs is facilitated.
And (3) access request: a client initiates a content URL access request, and a remote website server closest to a user requests a remote website DNS server to perform domain name resolution on URL access corresponding to the content of the user URL access request; load balancing: the remote website DNS server transfers the domain name resolution right to a remote CDN special DNS server, then the remote CDN special DNS server transfers the corresponding access request to a remote CDN global load balancing system, and then the remote CDN global load balancing system transfers the corresponding access request to a remote CDN regional load balancing system; request target URL points to resource: the remote CDN regional load balancing system feeds back an IP address corresponding to the CDN edge computing server through a remote CDN special DNS server, and then requests a resource pointed by a target URL (uniform resource locator) to the CDN edge computing server according to the IP address corresponding to the CDN edge computing server; judging dynamic and static states: judging whether the resource is dynamic content according to the resource pointed by the target URL requested by the CDN edge computing server, if so, requesting a Docker mirror image containing a resource program and a database from a Docker warehouse, downloading the Docker mirror image of the database, starting a Docker container, executing the program in the Docker mirror image of the database, generating dynamic content corresponding to the program, and feeding back the dynamic content to the client; static content query: if the local cache is not dynamic content, the static content is inquired, whether the local cache has the cache of the resource is judged, if yes, the cached resource is immediately taken and fed back to the client, and if not, the cached resource is taken from the data center and fed back to the client.
Example three:
in the second embodiment, the following steps are added:
in step 2, in the domain name resolution process of the local DNS system, the CDN-dedicated DNS server is a CDN-dedicated DNS server to which the CNAME points, and provides assistance for domain name resolution.
And (3) access request: a client initiates a content URL access request, and a remote website server closest to a user requests a remote website DNS server to perform domain name resolution on URL access corresponding to the content of the user URL access request; load balancing: the remote website DNS server transfers the domain name resolution right to a remote CDN special DNS server, then the remote CDN special DNS server transfers the corresponding access request to a remote CDN global load balancing system, and then the remote CDN global load balancing system transfers the corresponding access request to a remote CDN regional load balancing system; request target URL points to resource: the remote CDN regional load balancing system feeds back an IP address corresponding to the CDN edge computing server through a remote CDN special DNS server, and then requests a resource pointed by a target URL (uniform resource locator) to the CDN edge computing server according to the IP address corresponding to the CDN edge computing server; judging dynamic and static states: judging whether the resource is dynamic content according to the resource pointed by the target URL requested by the CDN edge computing server, if so, requesting a Docker mirror image containing a resource program and a database from a Docker warehouse, downloading the Docker mirror image of the database, starting a Docker container, executing the program in the Docker mirror image of the database, generating dynamic content corresponding to the program, and feeding back the dynamic content to the client; static content query: if the local cache is not dynamic content, the static content is inquired, whether the local cache has the cache of the resource is judged, if yes, the cached resource is immediately taken and fed back to the client, and if not, the cached resource is taken from the data center and fed back to the client.
Example four:
in the third embodiment, the following steps are added:
in step 2, the special DNS server for the CDN feeds back an IP address of one device in the CDN global load balancing system, and initiates a content URL access request to the corresponding device according to the IP address, the device in the CDN global load balancing system selects a CDN regional load balancing system closest to the client according to the IP address of the client and the request content URL of the client, and then selects one regional load balancing device from the CDN regional load balancing system, thereby facilitating balancing access traffic of each user.
And (3) access request: a client initiates a content URL access request, and a remote website server closest to a user requests a remote website DNS server to perform domain name resolution on URL access corresponding to the content of the user URL access request; load balancing: the remote website DNS server transfers the domain name resolution right to a remote CDN special DNS server, then the remote CDN special DNS server transfers the corresponding access request to a remote CDN global load balancing system, and then the remote CDN global load balancing system transfers the corresponding access request to a remote CDN regional load balancing system; request target URL points to resource: the remote CDN regional load balancing system feeds back an IP address corresponding to the CDN edge computing server through a remote CDN special DNS server, and then requests a resource pointed by a target URL (uniform resource locator) to the CDN edge computing server according to the IP address corresponding to the CDN edge computing server; judging dynamic and static states: judging whether the resource is dynamic content according to the resource pointed by the target URL requested by the CDN edge computing server, if so, requesting a Docker mirror image containing a resource program and a database from a Docker warehouse, downloading the Docker mirror image of the database, starting a Docker container, executing the program in the Docker mirror image of the database, generating dynamic content corresponding to the program, and feeding back the dynamic content to the client; static content query: if the local cache is not dynamic content, the static content is inquired, whether the local cache has the cache of the resource is judged, if yes, the cached resource is immediately taken and fed back to the client, and if not, the cached resource is taken from the data center and fed back to the client.
Example five:
in the fourth example, the following steps were added:
in step 3, the special DNS server for the CDN resolves the domain name to the IP address of the CDN edge computing server closest to the user according to the location information of the user location, which facilitates the access of the user.
And (3) access request: a client initiates a content URL access request, and a remote website server closest to a user requests a remote website DNS server to perform domain name resolution on URL access corresponding to the content of the user URL access request; load balancing: the remote website DNS server transfers the domain name resolution right to a remote CDN special DNS server, then the remote CDN special DNS server transfers the corresponding access request to a remote CDN global load balancing system, and then the remote CDN global load balancing system transfers the corresponding access request to a remote CDN regional load balancing system; request target URL points to resource: the remote CDN regional load balancing system feeds back an IP address corresponding to the CDN edge computing server through a remote CDN special DNS server, and then requests a resource pointed by a target URL (uniform resource locator) to the CDN edge computing server according to the IP address corresponding to the CDN edge computing server; judging dynamic and static states: judging whether the resource is dynamic content according to the resource pointed by the target URL requested by the CDN edge computing server, if so, requesting a Docker mirror image containing a resource program and a database from a Docker warehouse, downloading the Docker mirror image of the database, starting a Docker container, executing the program in the Docker mirror image of the database, generating dynamic content corresponding to the program, and feeding back the dynamic content to the client; static content query: if the local cache is not dynamic content, the static content is inquired, whether the local cache has the cache of the resource is judged, if yes, the cached resource is immediately taken and fed back to the client, and if not, the cached resource is taken from the data center and fed back to the client.
Example six:
in the fifth example, the following steps were added:
in step 5, the dynamic content is given a suffix name of jsp, php, action or do, and the static content is given a suffix name of jpg, png, js or html, thereby providing acceleration to the user's request.
And (3) access request: a client initiates a content URL access request, and a remote website server closest to a user requests a remote website DNS server to perform domain name resolution on URL access corresponding to the content of the user URL access request; load balancing: the remote website DNS server transfers the domain name resolution right to a remote CDN special DNS server, then the remote CDN special DNS server transfers the corresponding access request to a remote CDN global load balancing system, and then the remote CDN global load balancing system transfers the corresponding access request to a remote CDN regional load balancing system; request target URL points to resource: the remote CDN regional load balancing system feeds back an IP address corresponding to the CDN edge computing server through a remote CDN special DNS server, and then requests a resource pointed by a target URL (uniform resource locator) to the CDN edge computing server according to the IP address corresponding to the CDN edge computing server; judging dynamic and static states: judging whether the resource is dynamic content according to the resource pointed by the target URL requested by the CDN edge computing server, if so, requesting a Docker mirror image containing a resource program and a database from a Docker warehouse, downloading the Docker mirror image of the database, starting a Docker container, executing the program in the Docker mirror image of the database, generating dynamic content corresponding to the program, and feeding back the dynamic content to the client; static content query: if the local cache is not dynamic content, the static content is inquired, whether the local cache has the cache of the resource is judged, if yes, the cached resource is immediately taken and fed back to the client, and if not, the cached resource is taken from the data center and fed back to the client.
Although embodiments of the present patent have been shown and described, it will be appreciated by those skilled in the art that changes, modifications, substitutions and alterations can be made in these embodiments without departing from the principles and spirit of the present patent, the scope of which is defined in the appended claims and their equivalents.
Claims (7)
1. A method for accelerating user request based on CDN technology is characterized in that: the method comprises the following steps:
step 1: and (3) access request: a client initiates a content URL access request, and a remote website server closest to a user requests a remote website DNS server to perform domain name resolution on URL access corresponding to the content of the user URL access request;
step 2: load balancing: the remote website DNS server transfers the domain name resolution right to a remote CDN special DNS server, then the remote CDN special DNS server transfers the corresponding access request to a remote CDN global load balancing system, and then the remote CDN global load balancing system transfers the corresponding access request to a remote CDN regional load balancing system;
and step 3: request target URL points to resource: the remote CDN regional load balancing system feeds back an IP address corresponding to the CDN edge computing server through a remote CDN special DNS server, and then requests a resource pointed by a target URL (uniform resource locator) to the CDN edge computing server according to the IP address corresponding to the CDN edge computing server;
and 4, step 4: judging dynamic and static states: judging whether the resource is dynamic content according to the resource pointed by the target URL requested by the CDN edge computing server, if so, requesting a Docker mirror image containing a resource program and a database from a Docker warehouse, downloading the Docker mirror image of the database, starting a Docker container, executing the program in the Docker mirror image of the database, generating dynamic content corresponding to the program, and feeding back the dynamic content to the client;
and 5: static content query: if the local cache is not dynamic content, the static content is inquired, whether the local cache has the cache of the resource is judged, if yes, the cached resource is immediately taken and fed back to the client, and if not, the cached resource is taken from the data center and fed back to the client.
2. The method for accelerating user requests based on CDN technology as recited in claim 1, wherein: in step 1, the developed program for generating the dynamic content is uploaded to a Docker warehouse in advance and is deployed to a data center.
3. The method for accelerating user requests based on CDN technology as recited in claim 1, wherein: in step 2, in the domain name resolution process of the local DNS system, the CDN-dedicated DNS server is a CDN-dedicated DNS server to which the CNAME points.
4. The method for accelerating user requests based on CDN technology as recited in claim 1, wherein: in step 2, the special DNS server for the CDN feeds back an IP address of one device in the CDN global load balancing system, and initiates a content URL access request to the corresponding device according to the IP address.
5. The method for accelerating user requests based on CDN technology as recited in claim 1, wherein: in step 2, the device in the CDN global load balancing system selects a CDN regional load balancing system closest to the client according to the IP address of the client and the request content URL of the client, and then selects one regional load balancing device from the CDN regional load balancing system.
6. The method for accelerating user requests based on CDN technology as recited in claim 1, wherein: in step 3, the special DNS server for the CDN resolves the domain name to the IP address of the CDN edge computing server closest to the user according to the location information of the user location.
7. The method for accelerating user requests based on CDN technology as recited in claim 1, wherein: in step 5, the suffix name of the dynamic content is jsp, php, action or do, and the suffix name of the static content is jpg, png, js or html.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011418272.5A CN112671836A (en) | 2020-12-07 | 2020-12-07 | Method for accelerating user request based on CDN technology |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011418272.5A CN112671836A (en) | 2020-12-07 | 2020-12-07 | Method for accelerating user request based on CDN technology |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112671836A true CN112671836A (en) | 2021-04-16 |
Family
ID=75401329
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011418272.5A Pending CN112671836A (en) | 2020-12-07 | 2020-12-07 | Method for accelerating user request based on CDN technology |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112671836A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113037878A (en) * | 2021-05-26 | 2021-06-25 | 北京拓课网络科技有限公司 | CDN data access method, system and electronic equipment |
| CN113301184A (en) * | 2021-07-08 | 2021-08-24 | 凌锐蓝信科技(北京)有限公司 | Remote access method, device, computer equipment and storage medium |
| CN114172912A (en) * | 2021-11-01 | 2022-03-11 | 北京中合谷投资有限公司 | Networking method of hybrid distributed network |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107105029A (en) * | 2017-04-18 | 2017-08-29 | 北京友普信息技术有限公司 | A kind of CDN dynamic contents accelerated method and system based on Docker technologies |
| CN108076142A (en) * | 2017-11-28 | 2018-05-25 | 郑州云海信息技术有限公司 | A kind of method and system for accelerating user's request based on CDN technologies |
-
2020
- 2020-12-07 CN CN202011418272.5A patent/CN112671836A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107105029A (en) * | 2017-04-18 | 2017-08-29 | 北京友普信息技术有限公司 | A kind of CDN dynamic contents accelerated method and system based on Docker technologies |
| CN108076142A (en) * | 2017-11-28 | 2018-05-25 | 郑州云海信息技术有限公司 | A kind of method and system for accelerating user's request based on CDN technologies |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113037878A (en) * | 2021-05-26 | 2021-06-25 | 北京拓课网络科技有限公司 | CDN data access method, system and electronic equipment |
| CN113037878B (en) * | 2021-05-26 | 2021-08-17 | 北京拓课网络科技有限公司 | CDN data access method, system and electronic equipment |
| CN113301184A (en) * | 2021-07-08 | 2021-08-24 | 凌锐蓝信科技(北京)有限公司 | Remote access method, device, computer equipment and storage medium |
| CN114172912A (en) * | 2021-11-01 | 2022-03-11 | 北京中合谷投资有限公司 | Networking method of hybrid distributed network |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11108729B2 (en) | Managing request routing information utilizing client identifiers | |
| US10404790B2 (en) | HTTP scheduling system and method of content delivery network | |
| US20210297365A1 (en) | Request routing based on class | |
| US11632353B2 (en) | Delegating DNS records to additional providers | |
| CN112671836A (en) | Method for accelerating user request based on CDN technology | |
| US9160703B2 (en) | Request routing management based on network components | |
| US9549038B1 (en) | Cacheable resource location selection | |
| US8577992B1 (en) | Request routing management based on network components | |
| US20070073829A1 (en) | Partitioning data across servers | |
| TWI657682B (en) | Method and system for realizing precise dispatch request on content distribution network (CDN) | |
| US10958501B1 (en) | Request routing information based on client IP groupings | |
| US9588854B2 (en) | Systems and methods for a secondary website with mirrored content for automatic failover | |
| US20060059246A1 (en) | System and method for connection optimization | |
| CN103347089A (en) | Method and device for separating and accelerating dynamic resources and static resources of website | |
| US10764355B2 (en) | Network address resolution | |
| US20050097185A1 (en) | Localization link system | |
| US10735528B1 (en) | Geographic relocation of content source in a content delivery network | |
| EP3066577B1 (en) | Content node selection using network performance profiles | |
| US10075553B1 (en) | Systems and methods for automatically rewriting network page code | |
| CN103347087A (en) | Structuring P2P and UDDI service registering and searching method and system | |
| US20030225859A1 (en) | Request mapping for load balancing | |
| CN115883657A (en) | Cloud disk service accelerated scheduling method and system | |
| Tang et al. | Minimal cost replication of dynamic web contents under flat update delivery | |
| KR20120137350A (en) | Utilizing resources of a peer-to-peer computer environment | |
| KR100313847B1 (en) | Internet service apparatus and method using bookmark |
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: 20210416 |