CN115150258A - CDN node configuration method, system and storage medium - Google Patents
CDN node configuration method, system and storage medium Download PDFInfo
- Publication number
- CN115150258A CN115150258A CN202110340286.8A CN202110340286A CN115150258A CN 115150258 A CN115150258 A CN 115150258A CN 202110340286 A CN202110340286 A CN 202110340286A CN 115150258 A CN115150258 A CN 115150258A
- Authority
- CN
- China
- Prior art keywords
- node
- cdn
- cdn node
- request
- transit
- 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
- 238000000034 method Methods 0.000 title claims abstract description 33
- 230000006870 function Effects 0.000 claims description 34
- 238000012546 transfer Methods 0.000 claims description 7
- 230000000694 effects Effects 0.000 claims description 6
- 238000012545 processing Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 235000008694 Humulus lupulus Nutrition 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
- H04L63/126—Applying verification of the received information the source of the received data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1031—Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
Abstract
The disclosure relates to a CDN node configuration method, system and storage medium. The CDN node configuration method comprises the following steps: the CDN node receives a request for acquiring the content; the CDN node judges whether the request is from the inside of a CDN network or from a user side by authenticating the request; if the request is from a user side, the function of the CDN node as the edge node is effective and the function of the CDN node as the transit node is not effective, and if the request is from a node in a CDN network, the function of the CDN node as the edge node is not effective and the function of the CDN node as the transit node is effective; and the CDN node initiates a scheduling request to a scheduling system to acquire the information of the node or the source station which the CDN node should respond to.
Description
Technical Field
The present disclosure relates generally to CDN node configuration methods, systems, and storage media, and more particularly to CDN node configuration unifying methods, systems, and storage media.
Background
A large number of edge nodes exist in a CDN (Content Delivery Network), and CDN manufacturers may add transit nodes to reduce back sources and perform back source link optimization. The edge nodes and the transit nodes are positioned differently and have different processing logics, so that different configurations need to be customized according to the node hierarchy.
The edge node and the transit node are located at different topological structure positions in the CDN, and the configuration of each node is not uniform. For example, the hotlink protection function configuration only needs to be effective at the edge node on the user access side, and the CDN internal transit node does not need to be effective. If the transit node is also active, then the requests that may come from inside may be considered illegal. And if the function is rewritten like a Uniform Resource Locator (URL), the function only needs to be deployed to the true back-source node, and does not need to be deployed to the edge node. If the edge node is also rewritten and the transfer source node is also rewritten, there may be a case of rewriting many times, and the return source URL does not meet the customer requirement.
Due to the inconsistent configuration of edge nodes and transit nodes, the nodes are not free to be multiplexed in different levels of the topology. For example, if edge nodes are used to mediate back to the source, the access will be in error.
On the other hand, when the CDN topology changes, for example, when a transit level is increased or decreased, a large number of nodes need to be deployed, a large number of configurations need to be modified, and the upper layer to which the node returns is known by configuring the cache node, which requires a large number of modifications, resulting in poor timeliness and a large risk.
Disclosure of Invention
An object of an embodiment of the present disclosure is to provide a CDN node configuration method, system, and storage medium, which can perform scheduling to select a node in a full network range when a node fails, without considering a level of the node, and without redeploying configuration, so as to achieve the purpose of fast scheduling.
Another object of the embodiments of the present disclosure is to provide a CDN node configuration method, system and storage medium, where when a domain bandwidth exceeds a load of a certain transit node, an edge node that has cached the domain name may be added to a transit, and a transit node that has not cached the domain name is not required to be added, so that a hit rate may be increased, and a source return amount may be reduced.
According to an aspect of the present disclosure, a CDN node configuration method is provided, including the following steps: the CDN node receives a request for obtaining the content; the CDN node judges whether the request originates from the inside of a CDN network or from a user side by authenticating the request; if the request is from a user side, the function of the CDN node as the edge node is effective and the function of the CDN node as the transit node is not effective, and if the request is from a node in the CDN network, the function of the CDN node as the edge node is not effective and the function of the CDN node as the transit node is effective; and the CDN node initiates a scheduling request to a scheduling system to acquire upper node or source station information which the CDN node should return.
According to another aspect of the present disclosure, there is provided a CDN node configuration system, including: a memory having instructions stored thereon; and a processor configured to execute instructions stored on the memory to perform the CDN node configuration method.
According to yet another aspect of the present disclosure, there is provided a computer-readable storage medium comprising computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the CDN node configuration method described above.
According to the CDN node configuration method, the CDN node configuration system and the storage medium, when a node fails, the node can be selected by scheduling in the whole network range without considering the level of the node and without redeploying the configuration, and the aim of rapid scheduling is fulfilled. And when the domain name bandwidth exceeds the load of a certain transfer node, the edge node which caches the domain name can be added into the transfer, and the transfer node which does not cache the domain name is not required to be added, so that the hit rate can be increased, and the source return quantity can be reduced.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
The present disclosure may be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which:
fig. 1 is a CDN architecture diagram showing a CDN network structure of embodiment 1.
Fig. 2 is a flowchart illustrating a CDN node configuration method in the CDN network according to embodiment 1.
Fig. 3 is a flowchart illustrating a CDN node configuration method in the CDN network according to embodiment 2.
Fig. 4 is a flowchart illustrating a CDN node configuration method in the CDN network according to embodiment 3.
FIG. 5 illustrates an exemplary configuration of a computing device 1200 capable of implementing embodiments in accordance with the present disclosure.
Detailed Description
The following detailed description is made with reference to the accompanying drawings and is provided to assist in a comprehensive understanding of various exemplary embodiments of the disclosure. The following description includes various details to aid understanding, but these details are to be regarded as examples only and are not intended to limit the disclosure, which is defined by the appended claims and their equivalents. The words and phrases used in the following description are intended only to provide a clear and consistent understanding of the disclosure. In addition, descriptions of well-known structures, functions, and configurations may be omitted for clarity and conciseness. Those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the spirit and scope of the disclosure.
(embodiment mode 1)
Fig. 1 is a CDN architecture diagram showing a CDN network structure of the present embodiment. As shown in fig. 1, the CDN network according to the present embodiment includes CDN nodes, a scheduling system, and a configuration system. The CDN node comprises an edge node and a transit node which are connected with the user side. The CDN node serving as the transit node may be a transit node inside the CDN network, or may be a transit node of the last layer. And the transfer node of the last layer is connected with the source station. One CDN node may function as an edge node according to the situation, or may function as a transit node inside the CDN network or a transit node of the last layer.
Next, a CDN node configuration method in the CDN network according to the present embodiment is described with reference to a flowchart of fig. 2.
First, in step S11, the CDN node receives a request to acquire content. In this case, the CDN node may be an edge node or a transit node.
Then, in step S12, the CDN node authenticates the request, and determines whether the request originates from inside the CDN network or from the user side. The way in which the request is authenticated may be the way in which the encrypted request header is verified.
If the request originates from the user side, the function of the CDN node as an edge node is validated and the function as a transit node is not validated in step S13. For example, the user-side functions such as the hotlink requirement, the hotlink request, and the requirement for 302 hops function as edge nodes.
If the request originates from a node inside the CDN network, the function of the CDN node as an edge node is not validated and the function as a transit node is validated in step S14. For example, some functions of the user side, such as the anti-hotlinking function request, 302 response, etc., are not effective, and the requirements, such as URL caching, etc., which are not related to the user side need to be effective. Whether the function is effective or not is partly derived from software defaults and partly configured according to requirements.
Then, in step S15, the CDN node issues a scheduling request to the scheduling system, and obtains information of an upper node or a source station to which the CDN node should respond. For example, a CDN node functioning as an edge node issues a scheduling request, and the scheduling system responds to the edge node.
If a certain CDN node fails, the scheduling system can perform scheduling in the whole CDN network range including the edge node and the transit node to select a substitute CDN node, the level of the node is not required to be considered, the redeployment configuration is not required, and the purpose of rapid scheduling can be achieved.
If the domain bandwidth of a certain CDN node functioning as a transit node exceeds the load threshold of the transit node, the edge node that has cached the domain name may be added to the transit without adding a transit node that has not cached the domain name, which may increase the hit rate and reduce the amount of backlogs.
According to the embodiment, the relay node can be used as the edge node when the edge node needs to be added, the edge node can be used as the relay node when the relay node needs to be added, the configuration of the node does not need to be modified, and the CDN node can be flexibly used.
(embodiment mode 2)
Fig. 3 is a flowchart illustrating a CDN node configuration method in the CDN network according to the present embodiment. In the present embodiment, a CDN node configuration method in a case where a CDN node issues a scheduling request is mainly described.
As shown in fig. 3, first, in step S21, the CDN node determines whether or not it has a cache of the content requested to be acquired, and if so, directly gives the cached content (step S22).
If the CDN node does not have a cache of the content requested to be obtained, the CDN node needs to pull the file back to the upper layer, the CDN node requests the scheduling system to return an upper node domain name or an IP address (step S23), and the scheduling system returns an upper node domain name or an IP address (step S24). For example, the scheduling system returns the customer back to the source domain name or the domain name of the call back relay.
In step S25, the CDN node distinguishes whether the dispatch return is a source return or a return transit node according to the upper node domain name or the IP address returned by the dispatch system. For example, a node differentiates whether a dispatch return requires a return to source or return to transit (internal node) based on a domain name suffix.
If the domain name or the IP address of the upper node returned by the scheduling system indicates direct back-to-source, the back-to-source related function of the CDN node is in effect (step S26), for example, the functions of URL back-to-source rewriting, back-to-source addition request header, and the like are in effect. Then, the CDN node issues a request to the source station (step S27).
If the upper node domain name or IP address returned by the scheduling system indicates that an internal transfer node is visited, the CDN node adds information related to authentication of the internal node to the request, and invalidates a function related to origin returning of the CDN node (step S28), for example, adds information related to authentication of the internal node at the head of the request, which is convenient for another node to authenticate, and the internal node may be used to perform security operations such as authentication, URL rewriting, etc. takes effect and the origin returning request head does not take effect. Then, the CDN node issues a request to the upper-layer transit node (step S29).
According to this embodiment, in addition to the technical effects of embodiment 1, the CDN nodes can be further flexibly configured by validating or invalidating the back-source related function of the node, and the configuration of the node does not need to be modified.
(embodiment mode 3)
Fig. 4 is a flowchart illustrating a CDN node configuration method in the CDN network according to the present embodiment. In the present embodiment, a description will be given mainly of a process performed when the scheduling system receives a scheduling request.
As shown in fig. 4, first, in step S31, the scheduling system receives a scheduling request from a CDN node, and obtains a domain name requested by the scheduling request and an IP address of the CDN node.
In step S32, the scheduling system obtains a transit or source return configuration matching the domain name requested by the scheduling request and the IP address of the CDN node. For example, the scheduling system finds the transit framework and source-back related configuration used by the domain name through the domain name.
In step S33, the scheduling system calculates the role of the upper layer (e.g., back to source or back to upper node) by using the matching algorithm according to the obtained transit or back to source configuration.
In step S34, the scheduling system determines whether the CDN node needs to go back to the source according to the role of going back to the upper layer. If the CDN node needs to return to the source (step S34: yes), the domain name or IP address of the source station is returned (step S35), otherwise, the domain name or IP address of the upper node is returned (step S36).
According to the embodiment of the disclosure, the CDN node can distinguish a user request, an internal request, a back-to-source request, a back-to-internal request, and a response in each direction. And the CDN node does not need to know the position of the CDN node in the framework, and the CDN node can enable corresponding functions to be effective according to the corresponding address returned to the upper layer provided by the scheduling system.
(embodiment mode 4)
Embodiment 4 mainly describes a CDN node configuration system and a computer-readable storage medium. The CDN node configuration system may include a memory and a processor. The processor may be configured to execute instructions stored on the memory to perform the CDN node configuration method recited in the various embodiments above.
Included in a computer-readable storage medium are computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the CDN node configuration method recited in the various embodiments above.
FIG. 5 illustrates an exemplary configuration of a computing device 1200 capable of implementing embodiments in accordance with the present disclosure.
As shown in fig. 5, computing device 1200 may include one or more elements that may be connected to or communicate with bus 1202 via one or more interfaces. The bus 1202 may include, but is not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus. Computing device 1200 may include, for example, one or more processors 1204, one or more input devices 1206, and one or more output devices 1208. The one or more processors 1204 may be any kind of processor and may include, but are not limited to, one or more general-purpose processors or special-purpose processors (such as special-purpose processing chips). The processor 1204 may be configured to implement the CDN node configuration method described in each of the above embodiments, for example. Input device 1206 may be any type of input device capable of inputting information to a computing device and may include, but is not limited to, a mouse, a keyboard, a touch screen, a microphone, and/or a remote control. Output device 1208 can be any type of device capable of presenting information and can include, but is not limited to, a display, speakers, a video/audio output terminal, a vibrator, and/or a printer.
The subject matter of the present disclosure is provided as examples of apparatus, systems, methods, and programs for performing the features described in the present disclosure. However, other features or variations are contemplated in addition to the above-described features. It is contemplated that the implementation of the components and functions of the present disclosure may be accomplished with any emerging technology that may replace the technology of any of the implementations described above.
Additionally, the above description provides examples, and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For example, features described with respect to certain embodiments may be combined in other embodiments.
In addition, in the description of the present disclosure, the terms "first," "second," "third," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or order.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multi-task processing and parallel processing may be advantageous.
Claims (7)
1. A CDN node configuration method comprises the following steps:
the CDN node receives a request for acquiring the content;
the CDN node judges whether the request originates from the inside of a CDN network or from a user side by authenticating the request;
if the request is from a user side, the function of the CDN node as the edge node is effective and the function of the CDN node as the transit node is not effective, and if the request is from a node in a CDN network, the function of the CDN node as the edge node is not effective and the function of the CDN node as the transit node is effective; and
and the CDN node initiates a scheduling request to a scheduling system to obtain information of an upper node or a source station which the CDN node should respond to.
2. The CDN node configuration method of claim 1 wherein,
in the case where the CDN node itself has a cache of the content requested for retrieval, the cache content is given directly,
under the condition that the CDN node does not have a cache of the content requested to be obtained, the CDN node requests a scheduling system to return an upper node domain name or an IP address, and distinguishes whether to return to a source or a return to a transit node according to the upper node domain name or the IP address returned by the scheduling system,
and if the domain name or the IP address of the upper node returned by the scheduling system represents direct source returning, the source returning related function of the CDN node takes effect, and the request is sent to the source station, and if the domain name or the IP address of the upper node returned by the scheduling system represents an access transfer node, the CDN node adds information related to internal node authentication to the request, so that the source returning related function of the CDN node is invalid, and the request is sent to the upper node.
3. The CDN node configuration method of claim 2, further comprising the steps of:
the scheduling system receives a scheduling request from the CDN node, and acquires a domain name requested by the scheduling request and an IP address of the CDN node;
the scheduling system acquires a transit or return-to-source configuration matched with the domain name requested by the scheduling request and the IP address of the CDN node;
the dispatching system calculates the role of the return upper layer by using a matching algorithm according to the transit or return source configuration; and
and if the CDN node needs to return to the source according to the role of the upper layer, returning the domain name or the IP address of the source station, otherwise, returning the domain name or the IP address of the upper layer node.
4. The CDN node configuration method of any of claims 1 to 3 wherein:
and if the CDN node fails, the scheduling system performs scheduling in a whole network range including the edge node and the transit node to select a substitute CDN node.
5. The CDN node configuration method of any of claims 1 to 3 wherein:
and if the domain name bandwidth of the CDN node which functions as the transit node exceeds the load threshold of the transit node, the edge node which caches the domain name functions as the transit node.
6. A CDN node configuration system, comprising:
a memory having instructions stored thereon; and
a processor configured to execute instructions stored on the memory to perform the CDN node configuration method of any of claims 1 to 5.
7. A computer-readable storage medium comprising computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the CDN node configuration method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110340286.8A CN115150258A (en) | 2021-03-30 | 2021-03-30 | CDN node configuration method, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110340286.8A CN115150258A (en) | 2021-03-30 | 2021-03-30 | CDN node configuration method, system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115150258A true CN115150258A (en) | 2022-10-04 |
Family
ID=83404467
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110340286.8A Pending CN115150258A (en) | 2021-03-30 | 2021-03-30 | CDN node configuration method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115150258A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101252588A (en) * | 2008-02-22 | 2008-08-27 | 蓝汛网络科技（北京）有限公司 | Apparatus, system and method for distributing stream medium content |
| CN104660700A (en) * | 2015-03-03 | 2015-05-27 | 网宿科技股份有限公司 | Method and system of CDN (content distribution network) |
| CN106790519A (en) * | 2016-12-19 | 2017-05-31 | 中国联合网络通信集团有限公司 | Service scheduling method and fringe node |
| CN107317879A (en) * | 2017-08-02 | 2017-11-03 | 网宿科技股份有限公司 | The distribution method and system of a kind of user's request |
| CN110266741A (en) * | 2018-03-12 | 2019-09-20 | 贵州白山云科技股份有限公司 | Client traffic automatic scheduling method and device in a kind of content distributing network |
| CN112153160A (en) * | 2020-09-30 | 2020-12-29 | 北京金山云网络技术有限公司 | Access request processing method and device and electronic equipment |
| CN112202631A (en) * | 2020-09-17 | 2021-01-08 | 北京金山云网络技术有限公司 | Resource access method, device and system, electronic equipment and storage medium |
-
2021
- 2021-03-30 CN CN202110340286.8A patent/CN115150258A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101252588A (en) * | 2008-02-22 | 2008-08-27 | 蓝汛网络科技（北京）有限公司 | Apparatus, system and method for distributing stream medium content |
| CN104660700A (en) * | 2015-03-03 | 2015-05-27 | 网宿科技股份有限公司 | Method and system of CDN (content distribution network) |
| CN106790519A (en) * | 2016-12-19 | 2017-05-31 | 中国联合网络通信集团有限公司 | Service scheduling method and fringe node |
| CN107317879A (en) * | 2017-08-02 | 2017-11-03 | 网宿科技股份有限公司 | The distribution method and system of a kind of user's request |
| CN110266741A (en) * | 2018-03-12 | 2019-09-20 | 贵州白山云科技股份有限公司 | Client traffic automatic scheduling method and device in a kind of content distributing network |
| CN112202631A (en) * | 2020-09-17 | 2021-01-08 | 北京金山云网络技术有限公司 | Resource access method, device and system, electronic equipment and storage medium |
| CN112153160A (en) * | 2020-09-30 | 2020-12-29 | 北京金山云网络技术有限公司 | Access request processing method and device and electronic equipment |
Non-Patent Citations (1)
| Title |
|---|
| 蔡宁;: "CDN边缘节点部署位置下沉的研究", 电信工程技术与标准化, no. 10, 15 October 2015 (2015-10-15) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220276910A1 (en) | Dynamically integrating a client application with third-party services | |
| US9807080B2 (en) | Method and apparatus for providing authentication session sharing | |
| US9237207B2 (en) | Device, system and method for providing distributed online services | |
| US10574771B2 (en) | Methods and systems for rewriting scripts to redirect web requests | |
| US11792179B2 (en) | Computer readable storage media for legacy integration and methods and systems for utilizing same | |
| WO2020228038A1 (en) | Domain name processing method, apparatus, electronic device, and storage medium | |
| US20170094507A1 (en) | Wireless application protocol gateway | |
| US11582229B2 (en) | Systems and methods of application single sign on | |
| CN104756080A (en) | Augmenting capabilities of a host device | |
| CN114257440B (en) | Network function service discovery method, system and storage medium | |
| CN115150258A (en) | CDN node configuration method, system and storage medium | |
| US9794255B2 (en) | Communication terminal and communication processing method | |
| CN106790458B (en) | Cross-local area network Memcache data sharing method and system | |
| CN113641966B (en) | Application integration method, system, equipment and medium | |
| US11683686B2 (en) | Method for authentication, user terminal and authentication server for executing the same | |
| JP7033944B2 (en) | Login support program, login support method, information processing terminal, and login support system | |
| CN116186723A (en) | Authority control system, method, equipment, medium and product | |
| CN115842673A (en) | Method and device for updating local authority information of client | |
| KR20140092065A (en) | User device, method of communicating using the same and computer-readable recording medium |
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 |