CN114466031A - 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
- CN114466031A CN114466031A CN202111613397.8A CN202111613397A CN114466031A CN 114466031 A CN114466031 A CN 114466031A CN 202111613397 A CN202111613397 A CN 202111613397A CN 114466031 A CN114466031 A CN 114466031A
- 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.)
- Granted
Links
Images
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 invention provides a CDN system node configuration method, a device, equipment and a storage medium, wherein the method comprises the following steps: determining a node type currently corresponding to the CDN node according to the received resource request; reading configuration files corresponding to the node types 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 technical problem that CDN system node configuration efficiency is relatively low in the prior art is solved.
Description
Technical Field
The present invention relates to the field of CDN technologies, and in particular, to a CDN system node configuration method, apparatus, device, and storage medium.
Background
The CDN is called a Content Delivery Network, i.e., a Content Delivery Network. The method aims to add a new network architecture in the existing Internet, distribute the content of a server of an original site to a server of an edge node closest to a network of a user, enable the user to obtain required content nearby, solve the Internet network congestion condition, improve the speed of accessing the server of the source site by the user, accelerate the user to obtain the resource of the server of the source site, reduce the load of the server corresponding to the source site, and enable the server of the edge node to receive the requests of various clients in large batch and reduce the amount of returned sources through the server of the edge node.
The CDN network is used for accelerating resources obtained by users and reducing the load of a content source station, edge nodes can bear a large number of acceleration channels, the disk space is limited, nodes in a middle layer are generally increased for transfer, the source return rate is reduced, the middle layer nodes of the network can be connected with the source station better when the source returns, and the response rate is improved.
The inventor finds that, for CDN nodes of different levels, the content configured by corresponding configuration items is different, for example, an edge node needs to configure a hotlink protection function and a video pull function, and an outermost node needs to configure a back source timeout time, retry times, back source authentication, and the like, where the outermost node is a node directly connected to a source station server. Because the bandwidth amounts of different customers to different CDN nodes are different, it is often necessary to increase or decrease intermediate levels to adjust the network topology of the CDN. However, it is difficult to configure each node in the CDN uniformly, and manual cooperation needs to be performed on each node one by one, which is tedious in configuration work and relatively low in configuration efficiency.
Disclosure of Invention
In view of this, the present invention provides a CDN system node configuration method, apparatus, device, and storage medium, 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 invention provides a CDN system node configuration method, which is applied to a CDN node, and the method includes the following steps:
determining a node type currently corresponding to the CDN node according to the received resource request;
reading configuration files corresponding to the node types 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, a node type currently corresponding to the CDN node includes:
acquiring domain name information in the resource request, and inquiring an IP address which correspondingly provides service for the CDN node in the domain name information;
judging whether the resource request carries a hierarchy identifier and judging whether the IP address is a source station IP address, wherein the hierarchy identifier is used for representing the hierarchy of a node on the upper layer;
and determining the node type currently corresponding to the CDN node according to the judgment result.
In one embodiment, the node types include: the node comprises edge nodes, middle layer nodes and outermost layer nodes, wherein configuration files corresponding to the edge nodes are edge configuration files, configuration files corresponding to the middle layer nodes are middle layer configuration files, and configuration files corresponding to the outermost layer nodes are source station configuration files.
In an 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 source station IP address and the resource request does not carry a hierarchical identifier, determining that the CDN node is an edge node;
if the IP address is not the source station IP address and the resource request carries a hierarchy identifier, determining that the CDN node is an intermediate layer node;
and if the IP address is a source station IP address and the resource request carries a hierarchy identifier, determining that the CDN node is an outermost layer node.
In one embodiment, the determining whether the IP address is a source station IP address includes:
initiating DNS query to obtain corresponding SRV record information;
and judging whether the IP address is the IP address of the source station or not according to the SRV record information.
In one embodiment, if the CDN node is an edge node, a tier 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 hierarchical 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 invention provides a CDN system node configuration device, which is applied to a CDN node, and the device includes the following modules:
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 nodes.
In a third aspect, an embodiment of the present invention provides a computer device, including: the CDN system node configuration method comprises a memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions, so as to implement the CDN system node configuration method according to any one of the first aspect.
In a fourth aspect, an embodiment of the present invention provides a non-transitory computer-readable storage medium storing computer instructions, which when executed by a processor, implement the CDN system node configuration method of any one of the first aspect.
The CDN system node configuration method, the device, the equipment and the storage medium provided by the embodiment of the invention at least have the following beneficial effects:
according to the CDN system node configuration method, device, equipment and storage medium provided by the embodiment of the invention, the configuration files of all node types are stored for each node, and the type of the configuration file is determined to be used according to the resource request. Or storing the configuration files of all levels for each node, and determining which level of the configuration files are used according to the resource request. The nodes do not need to know the position of the nodes in the system architecture, and the scheduling system determines the positioning information so as to determine whether each node corresponds to the source needing to be returned. If the source return is not needed and the node is not an edge node, the node can be determined to be a middle layer node, and the node is configured by using a middle layer configuration file correspondingly. And if the source return is needed, the source return configuration file is correspondingly loaded for configuration. And if the node is an edge node, configuring corresponding to the loading edge configuration file. And determining the node type according to the received resource request, so as to select and load the corresponding configuration file for configuration. Therefore, the unified configuration of all the nodes is realized, the configuration process is simplified, and the configuration efficiency is improved. When the intermediate level needs to be increased, the number of layers of the intermediate level can be rapidly increased without changing any configuration. When the intermediate layer node needs to be released and set as the edge node, the performance of the node can be changed rapidly to improve the configuration efficiency. On the whole, be convenient for unified management, carry out global configuration fast to satisfy different demands fast, improve and be suitable for efficiency, improved CDN system wholeness ability.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of a CDN system node configuration method according to an embodiment of the present invention;
fig. 2 is a flowchart of another CDN system node configuration method according to an embodiment of the present invention;
fig. 3 is a network topology diagram of a CDN node according to an embodiment of the present invention;
fig. 4 is a block diagram of a CDN system node configuration device according to an embodiment of the present invention;
fig. 5 is a block diagram of a CDN system node configuration computer device according to an embodiment of the present invention.
Detailed Description
The technical solutions of the present invention will be described clearly and completely with reference to the accompanying drawings, and it should be understood that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In addition, the technical features involved in the different embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
Although the processes described below include multiple operations that occur in a particular order, it should be clearly understood that the processes may include more or fewer operations that are performed sequentially or in parallel.
Example 1
Referring to fig. 1, an embodiment of the present invention provides a CDN system node configuration method, which is applied to a CDN node, and the method includes the following steps:
step S101, determining a node type currently corresponding to the CDN node according to the received resource request;
step S102, reading configuration files corresponding to the node types from the local, wherein each CDN node in the CDN system is provided with the configuration files corresponding to all the node types;
and step S103, analyzing the read configuration file, and configuring the CDN nodes.
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, an intermediate layer node type and an outermost layer node type, and the configuration files corresponding to all the node types are edge configuration files, intermediate layer configuration files and source station configuration files. Each CDN node in the CDN system stores configuration files of all levels, determines the current node type corresponding to the CDN node according to the received resource request, and reads and selects the configuration files corresponding to the node type. For example, if the bandwidth demand of the client is high, it should be necessary to add nodes in the middle hierarchy to increase the high load request of the client. By reading the configuration file corresponding to the node type for configuration, the addition of the nodes of the middle level can be completed without changing the configuration content on each node of the middle level.
By storing configuration files of all node types for each node, the type of configuration file to be used is determined according to the resource request. Or storing the configuration files of all levels for each node, and determining which level of the configuration files are used according to the resource request. The nodes do not need to know the position of the nodes in the system architecture, and the scheduling system determines the positioning information so as to determine whether each node corresponds to the source needing to be returned. If the source return is not needed and the node is not an edge node, the node can be determined to be a middle layer node, and the node is configured by using a middle layer configuration file correspondingly. And if the source return is needed, the source return configuration file is correspondingly loaded for configuration. And if the node is an edge node, configuring corresponding to the loading edge configuration file. And determining the node type according to the received resource request, so as to select and load the corresponding configuration file for configuration. Therefore, the unified configuration of all the nodes is realized, the configuration process is simplified, and the configuration efficiency is improved. When the intermediate level needs to be increased, the number of layers of the intermediate level can be rapidly increased without changing any configuration. When the intermediate layer node needs to be released and set as the edge node, the performance of the node can be changed rapidly to improve the configuration efficiency. On the whole, be convenient for unified management, carry out global configuration fast to satisfy different demands fast, improve and be suitable for efficiency, improved CDN system wholeness ability.
In an embodiment, referring to fig. 2, the determining a node type currently corresponding to the CDN node according to the received resource request includes:
step S1011, obtaining domain name information in the resource request, and querying an IP address corresponding to a service provided to the CDN node in the domain name information;
step S1012, determining whether the resource request carries a level identifier, and determining whether the IP address is a source station IP address, where the level identifier is used to indicate a level of a previous node;
and S1013, determining a node type currently corresponding to the CDN node according to the judgment result.
In the foregoing embodiment, specifically, the domain name information in the resource request is obtained, and whether the domain name information carries a hierarchical identifier is determined, where the hierarchical identifier is used to indicate a hierarchical level of a previous node. In other words, in the CDN system, when a previous node sends a resource request to a corresponding next node, the previous node carries a level identifier of the previous node, where the level identifier may also be understood as a 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 a corresponding level identifier, it can be determined that the sender of the current resource request corresponds to the client; if the received resource request carries the tier identifier, it may be determined that a sender of the received resource request is a node of the CDN system instead of the client. Therefore, if it is determined that the corresponding hierarchical identifier does not exist in the resource request, it is determined that the receiving node of the current resource request is an edge node, and the configuration file of the edge node type is correspondingly selected and read and analyzed, so as to perform configuration of the edge node.
In the foregoing embodiment, specifically, the domain name information in the resource request is obtained, and an IP address corresponding to a service provided to the CDN node in the domain name information is queried. By initiating a DNS query, corresponding SRV record information is obtained, which maps the service name to the name of the server providing the service. In other words, the IP corresponding to the server providing the service to the CDN node can be obtained by locating the resource distance. Exemplarily, if a server providing service to the CDN node is a next-layer node, an IP of the next-layer node is correspondingly obtained; and if the server providing the service to the CDN node is a source station server, correspondingly obtaining the IP of the source station. By judging whether the IP address providing service to the CDN node is a source station IP address, it can be judged whether the CDN node is an outermost node. If the IP address providing service for the CDN node is the source station IP address, the CDN node is determined to be the outermost node, and then a configuration file corresponding to the type of the outermost node can be selected to configure the CDN node.
In summary, in the above 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 the domain name information in the resource request is a source station 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 increased quickly without changing any application program or any configuration.
In one embodiment, the node types include: the node comprises edge nodes, middle layer nodes and outermost layer nodes, wherein configuration files corresponding to the edge nodes are edge configuration files, configuration files corresponding to the middle layer nodes are middle layer configuration files, and 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: anti-theft chain and video dragging functions. The corresponding configuration content in the source station configuration file includes but is not limited to: a back source timeout time, a number of retries and a back source authentication. By storing the configuration files corresponding to all node types in each node, each node can read the corresponding configuration files from the local according to the configuration requirements corresponding to the node, so that the configuration files are analyzed, and the node configuration is carried out. And the independent configuration of each node is avoided, so that the configuration of the CDN system is unified. The configuration of all nodes is the same, facilitating easy management of configuration information. Furthermore, 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 an 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 source station IP address and the resource request does not carry a hierarchical identifier, determining that the CDN node is an edge node;
if the IP address is not the source station IP address and the resource request carries a hierarchy identifier, determining that the CDN node is an intermediate layer node;
and if the IP address is a source station IP address and the resource request carries a hierarchy identifier, determining that the CDN node is an outermost layer node.
In one embodiment, the determining whether the IP address is a source station IP address includes:
a) initiating DNS query to obtain corresponding SRV record information;
b) and judging whether the IP address is the IP address of the source station or not according to the SRV record information.
In the above embodiment, specifically, by initiating a DNS query, corresponding SRV record information is obtained, and the SRV record information maps a service name to a server name providing the service. In other words, the IP corresponding to the server providing the service to the CDN node can be obtained by locating the resource distance. Exemplarily, if a server providing service to the CDN node is a next-layer node, an IP of the next-layer node is correspondingly obtained; and if the server providing the service to the CDN node is a source station server, correspondingly obtaining the IP of the source station. By judging whether the IP address providing service to the CDN node is a source station IP address, it can be judged whether the CDN node is an outermost node. If the IP address providing service for the CDN node is the source station IP address, the CDN node is determined to be the outermost node, and then a configuration file corresponding to the type of the outermost node can be selected to configure the CDN node.
In one embodiment, if the CDN node is an edge node, a tier 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 hierarchical identifier in the resource request is updated, and then the resource request is sent to the next node.
Referring now to fig. 3, a preferred example is illustrated for further explanation of the present application. In the CDN system shown in the drawing, there are four nodes in total, and from left to right, there are a first node, a second node, a third node, and a fourth node, respectively.
The first node receives a request sent by a client, determines that a source request does not carry a hierarchical identifier, and determines that the IP of a server providing service to the first node is the IP of a second node and is not the IP of a source station. Therefore, if the first node is determined to be an edge node, the edge configuration file is read from the local of the first node, the edge configuration file is analyzed, the first node is configured, and the first node is configured to be the edge node. The edge node adds a level identifier to the resource request and then sends the resource request to the next level node. Namely, the edge node can actively add the head of X-level:0 and send the head to the second node.
The second node receives a request carrying the hierarchy identifier sent by the edge node, determines that the source request carries the hierarchy identifier X-level:0, and determines that the IP of the server providing service to 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 layer of father node, the middle layer configuration file is read from the local part of the second node, the middle layer configuration file is analyzed, the second node is configured, and the second node is configured to be a middle layer node. After determining the next-layer node, the intermediate-layer node updates the level identifier in the resource request, and then sends the resource request to the next-layer node. Namely, the head of the X-level:1 is actively updated by one layer of father nodes and is sent to the third node.
The third node receives a request which is sent by the edge node and carries the hierarchical identifier, determines that the source request carries the hierarchical identifier level:1, and determines that the IP of the server providing 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 a second-layer father node, the middle-layer configuration file is read from the local part of the third node, the middle-layer configuration file is analyzed, the third node is configured, and the third node is configured to be a middle-layer node. After determining the next two-layer node, the intermediate layer node updates the level identifier in the resource request, and then sends the resource request to the next two-layer node. Namely, the second-layer father node can actively update the head of the X-level:2 and send the head to the fourth node.
And the fourth node receives a request carrying the hierarchy identifier sent by the edge node, determines that the source request carries the hierarchy identifier level:2, and determines that the IP of the server providing service for the fourth node is the IP of the source station. Therefore, if the fourth node is determined to be a three-layer father node and an 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 to be the outermost node, and the outermost node returns to the source to acquire the source station resources.
When each IP provides service, a DNS is initiated to inquire the DNS to obtain corresponding SRV record information, and whether the IP address is the IP address of the source station or not is judged according to the SRV record information, namely whether the return needs to return to the source is determined.
All nodes respectively 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, an application program does not need to be changed, and the level identification carried in a resource request and corresponding SRV record information obtained by initiating a DNS query DNS system determine which configuration file is loaded and used. The number of layers of the middle hierarchy can be increased quickly without any configuration change. The node does not need to know the position of the node in the architecture, and whether the IP address providing service for the node is the IP address of the source station or not is obtained by initiating the corresponding SRV record information obtained by a DNS inquiry DNS system, so that whether the source return configuration file is used or not is judged. And judging the carried hierarchy identification information, if the hierarchy identification information does not exist, correspondingly considering the hierarchy 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 returns. For determining whether to select to load the edge configuration file or the middle tier configuration file.
Example 2
Referring to fig. 4, an embodiment of the present invention provides a CDN system node configuration device, which is applied to a CDN node, and the device includes the following modules:
a receiving module 41, configured to determine, according to the received resource request, a node type currently corresponding to the CDN node;
a reading module 42, configured to read a configuration file corresponding to the node type from a local location, where each CDN node in the CDN system is provided with configuration files corresponding to all node types;
and a configuration module 43, 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 embodiment 1, and for details, reference is made to the above method embodiment, which is similar in implementation principle and technical effect and is not described herein again.
It should be noted that: the CDN system node configuration device provided in the foregoing embodiment is only illustrated by dividing the functional modules when performing CDN system node configuration, and in practical applications, the function allocation may be completed by different functional modules as needed, that is, an internal structure of the CDN system node configuration device is divided into different functional modules to complete all or part of the functions described above. In addition, the CDN system node configuration device provided in the foregoing embodiment and the CDN system node configuration method embodiment belong to the same concept, and details of a specific implementation process thereof are referred to in the method embodiment and are not described here again.
Example 3
The embodiment of the invention also provides computer equipment which can be computing equipment such as a desktop computer, a notebook computer, a palm computer, a cloud server and the like. As shown in fig. 5, the device may include, but is not limited to, a processor and a memory, wherein the processor and the memory may be connected by a bus or other means.
The Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), a Graphics Processing Unit (GPU), an embedded Neural Network Processor (NPU), other dedicated deep learning coprocessor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like, or a combination thereof.
The memory, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the CDN system node configuration method in the embodiment of the present invention. The processor executes various functional applications and data processing of the processor by running the non-transitory software program, instructions and modules stored in the memory, that is, the CDN system node configuration method in embodiment 1 of the foregoing method is implemented.
The memory may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created by the processor, and the like. Further, the memory may include high speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory optionally includes memory located remotely from the processor, and such remote memory may be coupled to the processor via 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 and, when executed by the processor, perform the CDN system node configuration method described above.
An embodiment of the present invention further provides a non-transitory computer-readable storage medium, where a computer-executable instruction is stored in the non-transitory computer-readable storage medium, and the computer-executable instruction may execute the CDN system node configuration method in any of the above method embodiments. The non-transitory computer readable storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, abbreviated as HDD), a Solid-State Drive (SSD), or the like; the non-transitory computer readable storage medium may also include a combination of memories of the above kind.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, apparatus, computer device or non-transitory computer readable storage medium, all relating to or including a computer program product.
Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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 embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
Obviously, the above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that various changes and modifications to the above description could be made by those skilled in the art without departing from the spirit of the present application. And are neither required nor exhaustive of all embodiments. And obvious variations or modifications therefrom are within the scope of the invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A CDN system node configuration method is applied to CDN nodes and is characterized by comprising the following steps:
determining a node type currently corresponding to the CDN node according to the received resource request;
reading configuration files corresponding to the node types 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.
2. The CDN system node configuration method of claim 1, wherein the determining a 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 which correspondingly provides service for the CDN node in the domain name information;
judging whether the resource request carries a hierarchy identifier and judging whether the IP address is a source station IP address, wherein the hierarchy identifier is used for representing the hierarchy of a node on the upper layer;
and determining the node type currently corresponding to the CDN node according to the judgment result.
3. The CDN system node configuration method of claim 2 wherein the node types comprise: the node comprises edge nodes, middle layer nodes and outermost layer nodes, wherein configuration files corresponding to the edge nodes are edge configuration files, configuration files corresponding to the middle layer nodes are middle layer configuration files, and configuration files corresponding to the outermost layer nodes are source station configuration files.
4. The CDN system node configuration method of claim 3, wherein the determining a node type currently corresponding to the CDN node according to the determination result includes:
if the IP address is not the source station IP address and the resource request does not carry a hierarchical identifier, determining that the CDN node is an edge node;
if the IP address is not the source station IP address and the resource request carries a hierarchy identifier, determining that the CDN node is an intermediate layer node;
and if the IP address is the source station IP address and the resource request carries the layer identification, determining that the CDN node is the outermost layer node.
5. The CDN system node configuration method of claim 2, wherein the determining whether the IP address is a source station IP address comprises:
initiating DNS query to obtain corresponding SRV record information;
and judging whether the IP address is the IP address of the source station or not according to the SRV record information.
6. The CDN system node configuration method of claim 2 wherein,
and if the CDN node is an edge node, adding a hierarchy identifier in the resource request, and then sending the resource request to a next-layer node.
7. The CDN system node configuration method of claim 2 wherein,
if the CDN node is a middle layer node, after a next layer node is determined, the hierarchy identification in the resource request is updated, and then the resource request is sent to the next layer node.
8. A CDN system node configuration device is applied to a CDN node, and comprises the following modules:
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 nodes.
9. A computer device, 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 to perform the CDN system node configuration method of any one of claims 1-7.
10. A non-transitory computer readable storage medium storing computer instructions which, when executed by a processor, implement the CDN system node configuration method of any one of claims 1-7.
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 true CN114466031A (en) | 2022-05-10 |
| CN114466031B 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) |
Cited By (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 (7)
| 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 |
| US20170366409A1 (en) * | 2016-06-15 | 2017-12-21 | Alibaba Group Holding Limited | Dynamic Acceleration in Content Delivery Network |
| 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 |
-
2021
- 2021-12-27 CN CN202111613397.8A patent/CN114466031B/en active Active
Patent Citations (7)
| 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 |
| US20170366409A1 (en) * | 2016-06-15 | 2017-12-21 | Alibaba Group Holding Limited | Dynamic Acceleration in Content Delivery Network |
| 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 |
Cited By (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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114466031B (en) | 2023-10-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10805363B2 (en) | Method, device and system for pushing file | |
| US8713182B2 (en) | Selection of a suitable node to host a virtual machine in an environment containing a large number of nodes | |
| US10291696B2 (en) | Peer-to-peer architecture for processing big data | |
| EP2901308B1 (en) | Load distribution in data networks | |
| CN106487850B (en) | The methods, devices and systems of mirror image are obtained under a kind of cloud environment | |
| US9052962B2 (en) | Distributed storage of data in a cloud storage system | |
| US8037025B2 (en) | Method and approach to hosting versioned web services | |
| US9888065B2 (en) | Defragmenting clusters with reserved resources | |
| US20140101300A1 (en) | Method and apparatus for automated deployment of geographically distributed applications within a cloud | |
| US10187255B2 (en) | Centralized configuration data in a distributed file system | |
| US9037618B2 (en) | Distributed, unified file system operations | |
| CN114466031B (en) | CDN system node configuration method, device, equipment and storage medium | |
| EP2235651A2 (en) | Distributed indexing of file content | |
| US10986065B1 (en) | Cell-based distributed service architecture with dynamic cell assignment | |
| US11003658B2 (en) | Selectively retrieving data from remote share nothing computer clusters | |
| CN106302640A (en) | Data request processing method and device | |
| US20140359213A1 (en) | Differencing disk improved deployment of virtual machines | |
| CN109783564A (en) | Support the distributed caching method and equipment of multinode | |
| US10664170B2 (en) | Partial storage of large files in distinct storage systems | |
| CN114610680A (en) | Method, device and equipment for managing metadata of distributed file system and storage medium | |
| CN114731297B (en) | Ad hoc network group for message restriction for computing device peer matching | |
| CN110347656B (en) | Method and device for managing requests in file storage system | |
| CN114830105A (en) | Data reading method and terminal | |
| CN114661246B (en) | Storage control method and device | |
| CN109960695B (en) | Management method and device for database in cloud computing system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |