CN114466031B - CDN system node configuration method, device, equipment and storage medium - Google Patents
CDN system node configuration method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114466031B CN114466031B CN202111613397.8A CN202111613397A CN114466031B CN 114466031 B CN114466031 B CN 114466031B CN 202111613397 A CN202111613397 A CN 202111613397A CN 114466031 B CN114466031 B CN 114466031B
- Authority
- CN
- China
- Prior art keywords
- node
- cdn
- configuration
- address
- resource request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- 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/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- 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/04—Network management architectures or arrangements
- H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a CDN system node configuration method, a device, equipment and a storage medium, wherein the method comprises the following steps: determining the node type currently corresponding to the CDN node according to the received resource request; the configuration files corresponding to the node types are read from the local, wherein each CDN node in the CDN system is provided with the configuration files corresponding to all the node types; and analyzing the read configuration file, and configuring the CDN node. The method and the device solve the technical problem that the node configuration efficiency of the CDN system in the prior art is relatively low.
Description
Technical Field
The present application relates to the field of CDN technologies, and in particular, to a method, an apparatus, a device, and a storage medium for configuring a node of a CDN system.
Background
The full name of CDN is Content Delivery Network, the content delivery network. The method aims at adding a new network architecture layer into the existing Internet, releasing the content of the server of the original site to the server of the edge node closest to the network of the user, enabling the user to obtain the required content nearby, solving the congestion condition of the Internet, improving the speed of the user accessing the server of the source site, accelerating the user to acquire the resources of the server of the source site, reducing the load of the server of the corresponding source site, enabling the server of the edge node to receive a large number of requests of all clients, and reducing the source returning quantity through the server of the edge node.
The CDN is used for accelerating the resources acquired by users, reducing the load of a content source station, enabling the edge nodes to bear a large number of acceleration channels, enabling the disk space to be limited, generally increasing the nodes of the middle layer to conduct transfer, reducing the source return rate, enabling the nodes of the middle layer with good network to be connected with the source station when the source is returned, and improving the response rate.
The inventor finds that for CDN nodes of different levels, the configuration contents of the corresponding configuration items are different, for example, an edge node needs to be configured with a burglar chain and a video drag function, and an outermost node needs to be configured with functions of source return timeout time, retry times, source return authentication and the like, wherein the outermost node is a node directly connected with a source station server. Since the amount of bandwidth of different CDN nodes varies from customer to customer, it is often necessary to add or subtract intermediate levels to adjust the network topology of the CDN. However, it is difficult to perform unified configuration on each node in the CDN, manual cooperation is required to perform on each node one by one, configuration work is complicated, and configuration efficiency is relatively low.
Disclosure of Invention
In view of the above, the present application provides a method, an apparatus, a device and a storage medium for configuring CDN system nodes, so as to solve the technical problem in the prior art that the CDN system node configuration efficiency is relatively low.
In a first aspect, an embodiment of the present application provides a CDN system node configuration method, applied to a CDN node, where the method includes the following steps:
determining the node type currently corresponding to the CDN node according to the received resource request;
the configuration files corresponding to the node types are read from the local, wherein each CDN node in the CDN system is provided with the configuration files corresponding to all the node types;
and analyzing the read configuration file, and configuring the CDN node.
In one embodiment, the determining, according to the received resource request, the node type currently corresponding to the CDN node includes:
acquiring domain name information in the resource request, and inquiring an IP address in the domain name information, which corresponds to providing service for the CDN node;
judging whether the resource request carries a hierarchy identification or not, and judging whether the IP address is a source station IP address or not, wherein the hierarchy identification is used for representing the hierarchy of a node at the upper layer;
and determining the node type currently corresponding to the CDN node according to the judging result.
In one embodiment, the node type includes: the configuration files corresponding to the edge nodes are edge configuration files, the configuration files corresponding to the middle layer nodes are middle layer configuration files, and the configuration files corresponding to the outermost layer nodes are source station configuration files.
In one embodiment, the determining, according to the determination result, a node type currently corresponding to the CDN node includes:
if the IP address is not the IP address of the source station and the resource request does not carry the hierarchical identifier, determining the CDN node as an edge node;
if the IP address is not the IP address of the source station and the resource request carries the hierarchical identifier, determining the CDN node as an intermediate layer node;
and if the IP address is the IP address of the source station and the resource request carries the hierarchical identifier, determining the CDN node as the outermost node.
In one embodiment, the determining whether the IP address is a source station IP address includes:
initiating DNS inquiry to obtain corresponding SRV record information;
and judging whether the IP address is the IP address of the source station according to the SRV record information.
In one embodiment, if the CDN node is an edge node, a hierarchy identifier is added to the resource request, and then the resource request is sent to a next-tier node.
In one embodiment, if the CDN node is an intermediate node, after determining a next node, the hierarchy identifier in the resource request is updated, and then the resource request is sent to the next node.
In a second aspect, an embodiment of the present application provides a CDN system node configuration apparatus, applied to a CDN node, where the apparatus includes:
the receiving module is used for determining the node type currently corresponding to the CDN node according to the received resource request;
the reading module is used for locally reading configuration files corresponding to the node types, wherein each CDN node in the CDN system is provided with the configuration files corresponding to all the node types;
and the configuration module is used for analyzing the read configuration file and configuring the CDN node.
In a third aspect, an embodiment of the present application provides a computer apparatus, including: the CDN system node configuration method according to any one of the first aspect is realized by the processor through executing the computer instructions.
In a fourth aspect, an embodiment of the present application provides a non-transitory computer readable storage medium storing computer instructions that, when executed by a processor, implement the CDN system node configuration method of any one of the first aspects.
The CDN system node configuration method, device, equipment and storage medium provided by the embodiment of the application have at least the following beneficial effects:
according to the CDN system node configuration method, device, equipment and storage medium provided by the embodiment of the application, the configuration files of all node types are stored for each node, and which type of configuration file is used is determined according to the resource request. Or each node is stored with configuration files of all levels, and decides which level of configuration file to use according to the resource request. The node does not need to know which position in the system architecture is in, and the scheduling system decides the positioning information so as to determine whether each node corresponds to a source needing to be returned. If the source is not needed and the node is not an edge node, the node can be determined to be a middle layer node, and the middle layer configuration file is correspondingly used for configuring the node. And if the source is needed to be returned, correspondingly loading the source returning configuration file for configuration. And if the node is an edge node, correspondingly loading the edge configuration file for configuration. And determining the node type according to the received resource request, so as to select and load the corresponding configuration file for configuration. Therefore, unified configuration of all nodes is realized, the configuration process is simplified, and the configuration efficiency is improved. When the intermediate level needs to be added, the number of layers of the intermediate level can be quickly increased without changing any configuration. When the intermediate layer node is required to be released to be set as an edge node, the performance of the node can be quickly changed, so that the configuration efficiency is improved. On the whole, the system is convenient for unified management, and global configuration is rapidly carried out so as to rapidly meet different requirements, improve the application efficiency and improve the overall performance of the CDN system.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present application, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a CDN system node configuration method according to an embodiment of the present application;
fig. 2 is a flowchart of another CDN system node configuration method according to an embodiment of the present application;
fig. 3 is a network topology diagram of a CDN node according to an embodiment of the present application;
fig. 4 is a block diagram of a CDN system node configuration device according to an embodiment of the present application;
fig. 5 is a block diagram of a CDN system node configuration computer device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made apparent and fully in view of the accompanying drawings, in which some, but not all embodiments of the application are shown. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In addition, the technical features of the different embodiments of the present application described below may be combined with each other as long as they do not collide with each other.
While the processes described below include a plurality of operations that occur in a particular order, it should be understood that the processes may include additional or fewer operations, which may be performed in sequence or in parallel.
Example 1
Referring to fig. 1, an embodiment of the present application provides a CDN system node configuration method, applied to CDN nodes, including the following steps:
step S101, determining the node type currently corresponding to the CDN node according to the received resource request;
step S102, a configuration file corresponding to the node type is read locally, wherein each CDN node in the CDN system is provided with configuration files corresponding to all node types;
step S103, analyzing the read configuration file, and configuring the CDN node.
In the foregoing embodiment, specifically, all CDN nodes in the CDN system are provided with configuration files corresponding to all node types. The node types can be divided into an edge node type, a middle layer node type and an outermost layer node type, and configuration files corresponding to all the node types are an edge configuration file, a middle layer configuration file and a source station configuration file. Each CDN node in the CDN system stores configuration files of all levels, determines the node type corresponding to the CDN node currently according to the received resource request, and reads and selects the configuration files corresponding to the node type. Illustratively, if the bandwidth demand of the customer is high, then nodes of intermediate tiers should be added to enhance the customer's high load requests. By reading the configuration file corresponding to the node type for configuration, the configuration content on each node of the intermediate level is not required to be configured and changed, so that the addition of the nodes of the intermediate level can be completed.
By storing configuration files of all node types for each node, it is decided which type of configuration file to use according to the resource request. Or each node is stored with configuration files of all levels, and decides which level of configuration file to use according to the resource request. The node does not need to know which position in the system architecture is in, and the scheduling system decides the positioning information so as to determine whether each node corresponds to a source needing to be returned. If the source is not needed and the node is not an edge node, the node can be determined to be a middle layer node, and the middle layer configuration file is correspondingly used for configuring the node. And if the source is needed to be returned, correspondingly loading the source returning configuration file for configuration. And if the node is an edge node, correspondingly loading the edge configuration file for configuration. And determining the node type according to the received resource request, so as to select and load the corresponding configuration file for configuration. Therefore, unified configuration of all nodes is realized, the configuration process is simplified, and the configuration efficiency is improved. When the intermediate level needs to be added, the number of layers of the intermediate level can be quickly increased without changing any configuration. When the intermediate layer node is required to be released to be set as an edge node, the performance of the node can be quickly changed, so that the configuration efficiency is improved. On the whole, the system is convenient for unified management, and global configuration is rapidly carried out so as to rapidly meet different requirements, improve the application efficiency and improve the overall performance of the CDN system.
In one embodiment, referring to fig. 2, the determining, according to the received resource request, the node type currently corresponding to the CDN node includes:
step S1011, obtaining domain name information in the resource request, and inquiring an IP address in the domain name information, which corresponds to providing service for the CDN node;
step S1012, judging whether the resource request carries a hierarchy identification and judging whether the IP address is a source station IP address, wherein the hierarchy identification is used for representing the hierarchy of a node at the upper layer;
step S1013, determining a node type currently corresponding to the CDN node according to the determination result.
In the above embodiment, specifically, domain name information in the resource request is obtained, and whether the domain name information carries a hierarchy identifier is determined, where the hierarchy identifier is used to represent a hierarchy of a node in a previous layer. In other words, in the CDN system, when the previous node sends the resource request to the corresponding next node, the node will carry the level identifier of the previous node, where the level identifier may be understood as the node identifier, and by determining whether the resource request carries the level identifier, it may be determined whether the current corresponding node type is an edge node. Specifically, if the received resource request does not have the corresponding hierarchical identifier, it can be determined that the sender of the current resource request corresponds to the client; if the received resource request carries the hierarchical identifier, it can be determined that the sender of the received resource request is a node of the CDN system, not a client. Therefore, if the corresponding hierarchical identifier does not exist in the resource request, determining that the receiving node of the current resource request is an edge node, correspondingly selecting and reading the configuration file of the edge node type, analyzing the configuration file of the edge node type, and configuring the edge node.
In the foregoing embodiment, specifically, domain name information in the resource request is obtained, and an IP address corresponding to the service provided to the CDN node in the domain name information is queried. And (3) obtaining corresponding SRV record information by initiating DNS inquiry, wherein the SRV record information maps the service name to the name of the server providing the service. In other words, the IP corresponding to the server that provides the service to the CDN node may be obtained by locating the resource distance. Illustratively, if the server providing the service to the CDN node is a next-tier node, correspondingly obtaining an IP of the next-tier node; and if the server providing the service for the CDN node is a source station server, correspondingly obtaining the IP of the source station. By determining whether the IP address providing service to the CDN node is the source IP address, it may be determined whether the CDN node is an outermost node. If the IP address providing service for the CDN node is the source station IP address, determining the CDN node as the outermost node, and further selecting a configuration file corresponding to the type of the outermost node to configure the CDN node.
In summary, in the foregoing embodiment, by determining whether the resource request carries a hierarchical identifier, and determining whether an IP address corresponding to the service provided to the CDN node in domain name information in the resource request is a source IP address, a node type currently corresponding to the CDN node is determined according to a determination result. The number of layers of the middle hierarchy can be rapidly increased without any change to the application program or any configuration.
In one embodiment, the node type includes: the configuration files corresponding to the edge nodes are edge configuration files, the configuration files corresponding to the middle layer nodes are middle layer configuration files, and the configuration files corresponding to the outermost layer nodes are source station configuration files.
In the above embodiment, specifically, the corresponding configuration content in the edge configuration file is not limited to: a hotlink and a video drag function. The corresponding configuration content in the source station configuration file includes, but is not limited to: back source timeout time, number of retries, and back source authentication. By storing configuration files corresponding to all node types in each node, each node can locally read the corresponding configuration files according to the configuration requirements corresponding to the node, so that the configuration files are analyzed and node configuration is carried out. The independent configuration of each node is avoided, so that the CDN system configuration is unified. The configuration of all nodes is the same, facilitating easy management of configuration information. Further, the configuration information is distinguished from the acceleration domain name granularity, so that the configuration information under the acceleration domain name directory is easier to manage and configure.
In one embodiment, the determining, according to the determination result, a node type currently corresponding to the CDN node includes:
if the IP address is not the IP address of the source station and the resource request does not carry the hierarchical identifier, determining the CDN node as an edge node;
if the IP address is not the IP address of the source station and the resource request carries the hierarchical identifier, determining the CDN node as an intermediate layer node;
and if the IP address is the IP address of the source station and the resource request carries the hierarchical identifier, determining the CDN node as the outermost node.
In one embodiment, the determining whether the IP address is a source station IP address includes:
a) Initiating DNS inquiry to obtain corresponding SRV record information;
b) And judging whether the IP address is the IP address of the source station according to the SRV record information.
In the above embodiment, specifically, by initiating a DNS query, corresponding SRV record information is obtained, where the SRV record information maps a service name to a server name that provides the service. In other words, the IP corresponding to the server that provides the service to the CDN node may be obtained by locating the resource distance. Illustratively, if the server providing the service to the CDN node is a next-tier node, correspondingly obtaining an IP of the next-tier node; and if the server providing the service for the CDN node is a source station server, correspondingly obtaining the IP of the source station. By determining whether the IP address providing service to the CDN node is the source IP address, it may be determined whether the CDN node is an outermost node. If the IP address providing service for the CDN node is the source station IP address, determining the CDN node as the outermost node, and further selecting a configuration file corresponding to the type of the outermost node to configure the CDN node.
In one embodiment, if the CDN node is an edge node, a hierarchy identifier is added to the resource request, and then the resource request is sent to a next-tier node.
In one embodiment, if the CDN node is an intermediate node, after determining a next node, the hierarchy identifier in the resource request is updated, and then the resource request is sent to the next node.
Referring to fig. 3, a preferred example is illustrated below to further illustrate the present application. In the CDN system shown in the figure, four nodes are present in total, namely a first node, a second node, a third node and a fourth node from left to right.
The first node receives the request sent by the client, determines that the source request does not carry the hierarchy identification, and determines that the IP of the server providing the service to the first node is the IP of the second node and is not the IP of the source station. Therefore, if the first node is determined to be the edge node, the edge configuration file is read from the local of the first node, the edge configuration file is parsed, the first node is configured, and the first node is configured as the edge node. The edge node adds a hierarchy identification in the resource request and then sends the resource request to the next level node. I.e. the edge node will actively add the header of X-level 0 to send to the second node.
The second node receives the request carrying the level identifier sent by the edge node, determines that the source request carries the level identifier X-level:0, and determines that the IP of the server providing service for the second node is the IP of the third node and is not the IP of the source station. Therefore, if the second node is determined to be a parent node, the middle layer configuration file is read from the local area of the second node, the middle layer configuration file is analyzed, the second node is configured, and the second node is configured as the middle layer node. After determining the next-layer node, the middle-layer node updates the hierarchical identifier in the resource request and then sends the resource request to the next-layer node. I.e. a layer of parent nodes will actively update the header of X-level 1 to send to the third node.
And the third node receives the request carrying the level identifier sent by the edge node, determines that the source request carries the level identifier 1, and determines that the IP of the server providing the service for the third node is the IP of the fourth node and is not the IP of the source station. Therefore, if the third node is determined to be the two-layer father node, the middle layer configuration file is read from the local of the third node, the middle layer configuration file is analyzed, the third node is configured, and the third node is configured as the middle layer node. After determining the next two-layer node, the middle-layer node updates the hierarchical identifier in the resource request and then sends the resource request to the next two-layer node. I.e. the parent node of the two layers will actively update the header of the X-level 2 to be sent to the fourth node.
The fourth node receives the request carrying the level identifier sent by the edge node, determines that the source request carries the level identifier 2, and determines that the IP of the server providing the service for the fourth node is the IP of the source station. Therefore, if the fourth node is determined to be the three-layer father node and the outermost node, the source station configuration file is read from the local of the fourth node, the source station configuration file is analyzed, the fourth node is configured as the outermost node, and the outermost node returns to the source to acquire the source station resource.
When judging the IP of the service provided by each server, the server obtains corresponding SRV record information by initiating a DNS query DNS system and judges whether the IP address is the IP address of the source station according to the SRV record information, namely, whether the return needs to return to the source is determined.
All nodes contain 3 levels of configuration files, namely an edge configuration file, a middle layer configuration file and a source station configuration file, when each node is configured, no change is needed to be carried out on an application program, and the configuration file is used for loading by the level identification carried in a resource request and corresponding SRV record information obtained by initiating a DNS (Domain name System) query DNS system. The number of layers of the intermediate hierarchy can be rapidly increased without changing any configuration. The node does not need to know which position in the architecture the node is located in, and the corresponding SRV record information obtained by initiating the DNS to inquire the DNS system obtains whether the IP address for providing service for the node is the IP address of the source station, so as to judge whether to use the source-returning configuration file. Judging the carried level identification information, if the level identification information does not exist, correspondingly considering the level identification information as an edge node, and correspondingly loading an edge configuration file for configuration. And updating the corresponding layer identification every time the upper layer node is returned. For determining whether to select to load an edge profile or a middle tier profile.
Example 2
Referring to fig. 4, an embodiment of the present application provides a CDN system node configuration device, which is applied to CDN nodes, and includes the following modules:
a receiving module 41, configured to determine a node type currently corresponding to the CDN node according to the received resource request;
a reading module 42, configured to locally read configuration files corresponding to the node types, where each CDN node in the CDN system is provided with configuration files corresponding to all node types;
and the configuration module 43 is configured to analyze the read configuration file and perform configuration of the CDN node.
The CDN system node configuration device provided in the embodiment of the present application may be used in the CDN system node configuration method performed in the foregoing embodiment 1, and relevant details refer to the foregoing method embodiment, and the implementation principle and technical effects are similar and are not repeated herein.
It should be noted that: in the CDN system node configuration device provided in the foregoing embodiment, only the division of the functional modules is used for illustration when the CDN system node configuration is performed, and in practical application, the functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the CDN system node configuration device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the CDN system node configuration device and the CDN system node configuration method embodiment provided in the foregoing embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiment, which is not described herein again.
Example 3
The embodiment of the application also provides computer equipment, which can be computing equipment such as desktop computers, notebook computers, palm computers, cloud servers and the like. As shown in fig. 5, the device may include, but is not limited to, a processor and a memory, where the processor and memory may be connected by a bus or other means.
The processor may be a central processing unit (Central Processing Unit, CPU) or other general purpose processor, digital signal processor (Digital Signal Processor, DSP), graphics processor (Graphics Processing Unit, GPU), embedded Neural network processor (Neural-network Processing Unit, NPU) or other special purpose deep learning coprocessor, application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or any combination thereof.
The memory, as a non-transitory computer readable storage medium, may be used to store a non-transitory software program, a non-transitory computer executable program, and a module, such as a program instruction/module corresponding to a CDN system node configuration method in an embodiment of the present application. The processor executes various functional applications and data processing of the processor by running non-transitory software programs, instructions and modules stored in the memory, that is, implements the CDN system node configuration method in method embodiment 1 described above.
The memory may include a memory program area and a memory data area, wherein the memory program area may store an operating system, at least one application program required for a function; the storage data area may store data created by the processor, etc. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory may optionally include memory located remotely from the processor, the remote memory being connectable to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The one or more modules are stored in the memory that, when executed by the processor, perform the CDN system node configuration method described above.
The embodiment of the application also provides a non-transitory computer readable storage medium, which stores computer executable instructions, and the computer executable instructions can execute the CDN system node configuration method in any of the method embodiments. Wherein the non-transitory computer readable storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a Flash Memory (Flash Memory), a Hard Disk (HDD), a Solid State Drive (SSD), or the like; the non-transitory computer readable storage medium may also include a combination of the above types of memory.
It will be appreciated by those skilled in the art that embodiments of the application may be provided as methods, apparatus, computer devices, or non-transitory computer readable storage media, all of which may relate to or comprise a computer program product.
Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The technical features of the above-described embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above-described embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
It will be apparent that the examples described above represent only a few embodiments of the present application, which are described in more detail and detail, but are not to be construed as limiting the scope of the application. It should be noted that other variations or modifications in the above description can be made by those of ordinary skill in the art without departing from the spirit of the application. It is not necessary here nor is it exhaustive of all embodiments. While still being apparent from variations or modifications that may be made by those skilled in the art are within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.
Claims (9)
1. A CDN system node configuration method, applied to CDN nodes, comprising the steps of:
determining a node type currently corresponding to the CDN node according to the received resource request, wherein the node type comprises: edge nodes, middle layer nodes and outermost layer nodes;
the configuration files corresponding to the node types are read from the local, wherein each CDN node in the CDN system is provided with the configuration files corresponding to all the node types;
analyzing the read configuration file and configuring the CDN node;
the determining the node type currently corresponding to the CDN node according to the received resource request includes:
acquiring domain name information in the resource request, and inquiring an IP address in the domain name information, which corresponds to providing service for the CDN node;
judging whether the resource request carries a hierarchy identification or not, and judging whether the IP address is a source station IP address or not, wherein the hierarchy identification is used for representing the hierarchy of a node at the upper layer;
and determining the node type currently corresponding to the CDN node according to the judging result.
2. The CDN system node configuration method of claim 1, wherein the configuration file corresponding to the edge node is an edge configuration file, the configuration file corresponding to the middle tier node is a middle tier configuration file, and the configuration file corresponding to the outermost tier node is a source configuration file.
3. The CDN system node configuration method of claim 2, wherein determining the node type currently corresponding to the CDN node according to the determination result includes:
if the IP address is not the IP address of the source station and the resource request does not carry the hierarchical identifier, determining the CDN node as an edge node;
if the IP address is not the IP address of the source station and the resource request carries the hierarchical identifier, determining the CDN node as an intermediate layer node;
and if the IP address is the IP address of the source station and the resource request carries the hierarchical identifier, determining the CDN node as the outermost node.
4. The CDN system node configuration method of claim 1, wherein the determining whether the IP address is a source IP address comprises:
initiating DNS inquiry to obtain corresponding SRV record information;
and judging whether the IP address is the IP address of the source station according to the SRV record information.
5. The CDN system node configuration method of claim 1, wherein,
if the CDN node is an edge node, adding a hierarchical identifier in the resource request, and then sending the resource request to a next-layer node.
6. The CDN system node configuration method of claim 1, wherein,
if the CDN node is the middle layer node, after the next layer node is determined, updating the level identifier in the resource request, and then sending the resource request to the next layer node.
7. A CDN system node configuration device, applied to a CDN node, comprising:
the receiving module is configured to determine, according to the received resource request, a node type currently corresponding to the CDN node, where the node type includes: the receiving module is specifically configured to obtain domain name information in the resource request, and query an IP address in the domain name information, which corresponds to providing service for the CDN node; judging whether the resource request carries a hierarchy identification or not, and judging whether the IP address is a source station IP address or not, wherein the hierarchy identification is used for representing the hierarchy of a node at the upper layer; determining the node type currently corresponding to the CDN node according to the judging result;
the reading module is used for locally reading configuration files corresponding to the node types, wherein each CDN node in the CDN system is provided with the configuration files corresponding to all the node types;
and the configuration module is used for analyzing the read configuration file and configuring the CDN node.
8. A computer device, comprising: the system node configuration method of the CDN system according to any one of claims 1 to 6, comprising a memory and a processor, the memory and the processor being communicatively connected to each other, the memory having stored therein computer instructions, the processor executing the computer instructions.
9. A non-transitory computer readable storage medium storing computer instructions that, when executed by a processor, implement the CDN system node configuration method of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111613397.8A CN114466031B (en) | 2021-12-27 | 2021-12-27 | CDN system node configuration method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111613397.8A CN114466031B (en) | 2021-12-27 | 2021-12-27 | CDN system node configuration method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114466031A CN114466031A (en) | 2022-05-10 |
| CN114466031B true CN114466031B (en) | 2023-10-10 |
Family
ID=81406911
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111613397.8A Active CN114466031B (en) | 2021-12-27 | 2021-12-27 | CDN system node configuration method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114466031B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115225490A (en) * | 2022-07-20 | 2022-10-21 | 天翼云科技有限公司 | Gateway configuration method and device and electronic equipment |
| CN118413574A (en) * | 2024-06-28 | 2024-07-30 | 北京火山引擎科技有限公司 | Request processing method, device, equipment and medium based on content distribution network |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103684870A (en) * | 2013-12-25 | 2014-03-26 | 乐视网信息技术（北京）股份有限公司 | Method and system for obtaining bandwidth flow of CDN (Content Delivery Network) |
| CN105847398A (en) * | 2016-04-25 | 2016-08-10 | 乐视控股（北京）有限公司 | Business scheduling method, scheduling server and business server |
| CN109039696A (en) * | 2018-06-08 | 2018-12-18 | 网宿科技股份有限公司 | A kind of CDN node, CDN node restorative procedure and node repair system |
| CN110311983A (en) * | 2019-07-09 | 2019-10-08 | 北京字节跳动网络技术有限公司 | Processing method, device, system, electronic equipment and the storage medium of service request |
| CN111371585A (en) * | 2018-12-26 | 2020-07-03 | 北京奇虎科技有限公司 | Configuration method and device for CDN node |
| CN111935195A (en) * | 2020-10-13 | 2020-11-13 | 北京志翔科技股份有限公司 | Distributed system management method, device, storage medium and distributed management system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107517228B (en) * | 2016-06-15 | 2021-03-05 | 阿里巴巴集团控股有限公司 | Dynamic acceleration method and device in content distribution network |
-
2021
- 2021-12-27 CN CN202111613397.8A patent/CN114466031B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103684870A (en) * | 2013-12-25 | 2014-03-26 | 乐视网信息技术（北京）股份有限公司 | Method and system for obtaining bandwidth flow of CDN (Content Delivery Network) |
| CN105847398A (en) * | 2016-04-25 | 2016-08-10 | 乐视控股（北京）有限公司 | Business scheduling method, scheduling server and business server |
| CN109039696A (en) * | 2018-06-08 | 2018-12-18 | 网宿科技股份有限公司 | A kind of CDN node, CDN node restorative procedure and node repair system |
| CN111371585A (en) * | 2018-12-26 | 2020-07-03 | 北京奇虎科技有限公司 | Configuration method and device for CDN node |
| CN110311983A (en) * | 2019-07-09 | 2019-10-08 | 北京字节跳动网络技术有限公司 | Processing method, device, system, electronic equipment and the storage medium of service request |
| CN111935195A (en) * | 2020-10-13 | 2020-11-13 | 北京志翔科技股份有限公司 | Distributed system management method, device, storage medium and distributed management system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114466031A (en) | 2022-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10700963B2 (en) | Locating service endpoints from a service registry | |
| US8713182B2 (en) | Selection of a suitable node to host a virtual machine in an environment containing a large number of nodes | |
| EP2901308B1 (en) | Load distribution in data networks | |
| US20200364608A1 (en) | Communicating in a federated learning environment | |
| US9858124B1 (en) | Dynamic management of data stream processing | |
| CN114466031B (en) | CDN system node configuration method, device, equipment and storage medium | |
| US9888065B2 (en) | Defragmenting clusters with reserved resources | |
| US20100235509A1 (en) | Method, Equipment and System for Resource Acquisition | |
| US20140101300A1 (en) | Method and apparatus for automated deployment of geographically distributed applications within a cloud | |
| US10158709B1 (en) | Identifying data store requests for asynchronous processing | |
| CN101741907A (en) | Method and system for balancing server load and main server | |
| US10986065B1 (en) | Cell-based distributed service architecture with dynamic cell assignment | |
| US11063992B1 (en) | Network-based media processing (NBMP) workflow management through 5G framework for live uplink streaming (FLUS) control | |
| CN109783564A (en) | Support the distributed caching method and equipment of multinode | |
| US8180857B2 (en) | Method for downloading file in parallel | |
| US20230344781A1 (en) | Grouping resource metadata tags | |
| CN110347656B (en) | Method and device for managing requests in file storage system | |
| CA2567798A1 (en) | Method, system and program product for storing downloadable content on a plurality of enterprise storage system (ess) cells | |
| US11093493B1 (en) | Dynamically switching between query and scan for optimizing table reads | |
| US11579915B2 (en) | Computing node identifier-based request allocation | |
| CN109960695B (en) | Management method and device for database in cloud computing system | |
| KR20060117149A (en) | File distribution method and system based on p2p technology | |
| CN103609074A (en) | Application specific WEB request routing | |
| JP2008509467A (en) | Method, system and computer program for managing database records by attributes located in a plurality of databases | |
| WO2024032653A1 (en) | Reducing network overhead |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |