Method and device for redirecting interconnection route of content delivery network and related equipment

Abstract

The invention provides a content distribution network interconnection route redirection method and device and related equipment, and relates to the technical field of computer networks and information, the method is applied to a content distribution network interconnection system, and the content distribution network interconnection system comprises a plurality of downstream content distribution networks. The method comprises the following steps: receiving a redirection request sent by a downstream content distribution network to be redirected; and sending a target service request to the target downstream content distribution network according to the redirection request, so that the target downstream content distribution network provides the target service. The present disclosure allows direct cooperation between downstream content delivery networks, and can reduce dependence on real-time scheduling of upstream content delivery networks.

Description

Background Art

[0002] A Content Delivery Network (CDN) improves access speed and reduces latency by deploying edge nodes globally and caching content closer to users. However, the coverage of a single CDN is usually limited by the geographical distribution of its infrastructure and resource allocation, making it difficult to achieve comprehensive global coverage. This means that in some regions, users may not receive ideal service quality. To address this issue, Content Delivery Network Interconnection (CDNI) emerged. CDNI enables multiple independent CDNs to interconnect and work together through standardized interfaces and mechanisms, thus expanding the coverage of content distribution and enhancing service availability and reliability. Through CDNI, content providers can utilize the combined resources of multiple CDNs to achieve broader content distribution and meet the needs of global users.

[0003] The CDNI architecture in related technologies is a mechanism where an upstream CDN coordinates multiple downstream CDNs for content services. Its core goal is that through CDNI between CDNs, an upstream CDN connects to the content service provider, and its CDN coverage can be extended to the coverage of other CDNs. In related technologies, the service scheduling of downstream CDNs requires unified decision-making by the upstream CDN. When a downstream CDN node needs to migrate services due to cache invalidation or performance degradation, the request must be rolled back to the upstream CDN for reallocation, which will cause the following problems:

[0004] 1) Increase the number of hops in the content service path, resulting in significant latency;

[0005] 2) The upstream CDN becomes a scheduling bottleneck, affecting the overall scalability of the system;

[0006] 3) Downstream CDNs cannot independently respond to temporary service emergencies and lack flexibility.

[0007] As Figure 1 shown, the existing CDNI service migration process is as follows:

[0008] 1) Service problems occur in downstream CDN1, triggering the migration process and initiating a redirect request to the client;

[0009] 2) The client receives the redirect request and initiates a service request to the upstream CDN according to the redirect signaling;

[0010] 3) The upstream CDN queries its own service capabilities or the service capabilities of other downstream CDNs, and redirects the client to the downstream CDN3 service through redirection. It can be seen that the process in the related art requires scheduling the service request back to the upstream CDN and then re-scheduling it by the upstream CDN.

[0011] It should be noted that the information disclosed in the above background art section is only used to enhance the understanding of the background of the present disclosure, and thus may include information that does not constitute the prior art known to those of ordinary skill in the art. Summary of the Invention

[0012] The present disclosure provides a redirection method, apparatus, and related devices for content delivery network interconnection routing, which at least to a certain extent reduce the dependence on real-time scheduling of the upstream CDN in the related art, and improve the service stability, response efficiency, and scalability of the edge CDN.

[0013] Other features and advantages of the present disclosure will become apparent through the following detailed description, or will be learned in part through the practice of the present disclosure.

[0014] According to one aspect of the present disclosure, there is provided a redirection method for content delivery network interconnection routing, characterized in that it is applied to a content delivery network interconnection system, the content delivery network interconnection system includes a plurality of downstream content delivery networks, and the method includes: receiving a redirection request sent by a downstream content delivery network to be redirected; sending a target service request to a target downstream content delivery network according to the redirection request, so that the target downstream content delivery network provides a target service.

[0015] In some exemplary embodiments of the present disclosure, based on the foregoing solution, the content delivery network interconnection system includes: an upstream content delivery network. Before receiving a redirection request sent by a downstream content delivery network to be redirected, the method further includes: determining a docking strategy between the upstream content delivery network and a plurality of downstream content delivery networks based on a content delivery network interconnection protocol, the content delivery network interconnection protocol being used to enable the upstream content delivery network to identify and connect to the downstream content delivery network; generating a core shared routing table according to the docking strategy, the core shared routing table being used to store network service configuration information of the upstream content delivery network and a plurality of downstream content delivery networks.

[0016] In some exemplary embodiments of the present disclosure, based on the foregoing solution, after generating the core shared routing table, the method further includes: generating an associated shared routing table corresponding to a plurality of downstream content delivery networks based on the network service configuration information of the plurality of downstream content delivery networks in the core shared routing table, wherein the associated shared routing table is associated with the core shared routing table and is configured to store relevant information generated based on the data records in the core shared routing table.

[0017] In some exemplary embodiments of the present disclosure, based on the foregoing solution, the redirection request is generated according to an associated shared routing table corresponding to the downstream content distribution network to be redirected.

[0018] In some exemplary embodiments of the present disclosure, based on the foregoing solution, after generating the core shared routing table according to the docking policy, the method further includes: when the downstream content distribution network changes, updating the core shared routing table; and according to the network service configuration information of the downstream content distribution network in the updated core shared routing table, updating the associated shared routing table corresponding to the downstream content distribution network.

[0019] In some exemplary embodiments of the present disclosure, based on the foregoing solution, before sending a target service request to a target downstream content distribution network according to the redirection request, the method further includes: controlling the verification between the downstream content distribution network to be redirected and the target downstream content distribution network through an asymmetric key signature.

[0020] In some exemplary embodiments of the present disclosure, based on the foregoing solution, the downstream content distribution network only reads the associated shared routing table.

[0021] According to another aspect of the present disclosure, there is also provided a redirection device for content distribution network interconnection routing, characterized in that it is applied to a content distribution network interconnection system, the content distribution network interconnection system includes a plurality of downstream content distribution networks, and the device includes: a redirection request receiving module, configured to receive a redirection request sent by a downstream content distribution network to be redirected; and a target service request sending module, configured to send a target service request to a target downstream content distribution network according to the redirection request, so that the target downstream content distribution network provides a target service.

[0022] According to yet another aspect of the present disclosure, there is also provided a redirection system for content distribution network interconnection routing, characterized in that it includes: a downstream content distribution network, configured to send a redirection request and receive a target service request; and a client, configured to receive a redirection request sent by a downstream content distribution network to be redirected, and send the target service request to a target downstream content distribution network according to the redirection request, so that the target downstream content distribution network provides a target service.

[0023] According to still another aspect of the present disclosure, there is also provided an electronic device, including: a processor; and a memory, configured to store executable instructions of the processor; wherein, the processor is configured to execute any one of the above-mentioned redirection methods for content distribution network interconnection routing by executing the executable instructions.

[0024] According to another aspect of the present disclosure, there is also provided a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned redirect method for content distribution network interconnection routing is implemented.

[0025] According to another aspect of the present disclosure, there is also provided a computer program product, including: a computer program or instruction, and when the computer program or instruction is executed by a processor, the above-mentioned redirect method for content distribution network interconnection routing is implemented.

[0026] In an embodiment of the present disclosure, a redirect method, device and related equipment for content distribution network interconnection routing are provided. The downstream content distribution network to be redirected sends a redirect request, and according to the redirect request, a target service request is sent to the target downstream content distribution network so that the target downstream content distribution network provides the target service. Compared with the related technology where the service scheduling of the downstream content distribution network needs to be uniformly decided by the upstream content distribution network, when the downstream content distribution network node needs to migrate services due to cache invalidation or performance degradation, the request must be rolled back to the upstream content distribution network for reallocation. The embodiment of the present disclosure breaks through the bottleneck of the traditional content distribution network interconnection relying on the upstream content distribution network. When a certain downstream content distribution network service is abnormal, the user request can be directly redirected by skipping the upstream content distribution network, greatly improving the migration efficiency and security.

[0027] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present disclosure, and are used together with the specification to explain the principles of the present disclosure. Obviously, the drawings in the following description are only some embodiments of the present disclosure, and those of ordinary skill in the art can obtain other drawings based on these drawings without creative efforts.

[0029] Figure 1 Showing a schematic diagram of content distribution network interconnection service migration in the related art;

[0030] Figure 2 Showing an exemplary application system architecture diagram of a redirect method for content distribution network interconnection routing in an embodiment of the present disclosure;

[0031] Figure 3 Showing a schematic diagram of a redirect method for content distribution network interconnection routing in an embodiment of the present disclosure;

[0032] Figure 4 Showing a schematic diagram of content distribution network interconnection service migration in an embodiment of the present disclosure;

[0033] Figure 5 Shows a schematic diagram of the generation and update process of a core SRT and an associated SRT in an embodiment of the present disclosure;

[0034] Figure 6 Shows a schematic diagram of a redirecting device for content delivery network interconnection routing in an embodiment of the present disclosure;

[0035] Figure 7 Shows a schematic diagram of a redirecting system for content delivery network interconnection routing in an embodiment of the present disclosure;

[0036] Figure 8 Shows a schematic diagram of an electronic device applying a redirecting method for content delivery network interconnection routing in an embodiment of the present disclosure. Detailed implementation manners

[0037] Example embodiments will now be described more fully with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0038] In addition, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of the embodiments of the present disclosure. However, those skilled in the art will realize that the technical solutions of the present disclosure can be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the present disclosure.

[0039] The flowcharts shown in the accompanying drawings are merely illustrative and not necessarily include all the contents and operations / steps, nor are they necessarily executed in the described order. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to the actual situation.

[0040] Figure 2 Shows an exemplary application system architecture diagram to which the redirecting method for content delivery network interconnection routing in an embodiment of the present disclosure can be applied. As Figure 2 shown, the system architecture can include a terminal device 201, a network 202, and a server 203.

[0041] The network 202 is a medium for providing a communication link between the terminal device 201 and the server 203, which can be a wired network or a wireless network.

[0042] Optionally, the above-mentioned wireless network or wired network uses standard communication technologies and / or protocols. The network is usually the Internet, but can also be any network, including but not limited to any combination of local area network (LAN), metropolitan area network (MAN), wide area network (WAN), mobile, wired or wireless network, private network or virtual private network). In some embodiments, technologies and / or formats including Hyper Text Mark-up Language (HTML), Extensible Markup Language (XML), etc. are used to represent the data exchanged through the network. In addition, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), Internet Protocol Security (IPsec), etc. can be used to encrypt all or some of the links. In other embodiments, customized and / or dedicated data communication technologies can also be used to replace or supplement the above data communication technologies.

[0043] The terminal device 201 can be various electronic devices, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, wearable devices, augmented reality devices, virtual reality devices, etc.

[0044] Optionally, the clients of the application programs installed in different terminal devices 201 are the same, or clients of the same type of application programs based on different operating systems. Depending on the different terminal platforms, the specific form of the client of the application program can also be different. For example, the client of the application program can be a mobile phone client, a PC client, etc.

[0045] The server 203 can be a server that provides various services, such as a back-end management server that supports the devices for the operations performed by users using the terminal device 201. The back-end management server can analyze and process data such as requests received, and feedback the processing results to the terminal device.

[0046] Optionally, the server can be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The terminal can be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited thereto. The terminal and the server can be directly or indirectly connected through wired or wireless communication methods, and this application does not make any restrictions here.

[0047] Those skilled in the art can know that Figure 2 the number of terminal devices, networks, and servers in [] is only illustrative. According to actual needs, there can be any number of terminal devices, networks, and servers. The embodiments of the present disclosure do not make any limitations in this regard.

[0048] Under the above system architecture, an embodiment of the present disclosure provides a method for redirecting content delivery network interconnection routing, and this method can be executed by any electronic device with computing and processing capabilities.

[0049] In some embodiments, the method for redirecting content delivery network interconnection routing provided in the embodiments of the present disclosure can be executed by the terminal device of the above system architecture; in other embodiments, the method for redirecting content delivery network interconnection routing provided in the embodiments of the present disclosure can be executed by the server in the above system architecture; in other embodiments, the method for redirecting content delivery network interconnection routing provided in the embodiments of the present disclosure can be implemented by the interaction between the terminal device and the server in the above system architecture.

[0050] For the convenience of subsequent understanding, the embodiments of the present disclosure will explain the professional terms designed below:

[0051] Content Delivery Network Interconnection: (Content Delivery Network Interconnection, CDNI) is a set of interfaces and mechanisms for connecting two or more independent content delivery networks (CDNs). Through CDNI, CDNs can work together to expand the service coverage, improve the service quality, reduce the infrastructure cost, and enhance the availability and elasticity of content delivery.

[0052] Shared Routing Table (SRT) is a structure used to coordinate service capabilities and routing information between the upstream CDN (which can be represented by UCDN) and the downstream CDN (which can be represented by DCDN). The core SRT is maintained by the UCDN and contains the service capabilities, load status, key information, etc. of each DCDN; the associated SRT is a read-only copy of the core SRT and is distributed to each DCDN node. When a certain DCDN service is abnormal, it can autonomously select other DCDNs for service migration based on the information in the associated SRT without the need for the UCDN to intervene in real time, thus achieving more efficient content distribution and stronger system resilience.

[0053] First, an embodiment of the present disclosure provides a mechanism that is compatible with the CDNI standard and allows direct collaboration between DCDNs, breaking through the bottleneck of traditional CDNI's dependence on the UCDN. A hierarchical SRT is designed to enable direct collaboration between DCDNs. The UCDN dynamically generates the core SRT (including service capabilities, key pool, URL conversion rules) and synchronizes the read-only associated SRT to each DCDN. When a certain DCDN service is abnormal, it can autonomously redirect requests to the optimal DCDN based on the service weights (such as load, latency) of the associated SRT and use the asymmetric key signature mechanism to complete token verification (encrypted with the issuer's private key and decrypted with the target's public key), realizing the collaboration of DCDNs without the need for the UCDN to intervene in real time. The embodiment of the present disclosure is compatible with the CDNi standard and can be applied to various scenarios such as the interconnection between traditional CDNs and edge CDNs, and CDN node disaster recovery, and has the value of large-scale deployment.

[0054] Figure 3 The following shows a schematic diagram of a redirection method for content distribution network interconnection routing in an embodiment of the present disclosure. This method is applied to a content distribution network interconnection system, which includes multiple downstream content distribution networks, and includes the following steps:

[0055] S302, receiving a redirection request sent by a downstream content distribution network to be redirected.

[0056] It should be noted that in the embodiments of the present disclosure, DCDN refers to a CDN node or system located close to the client in the network structure, which is responsible for directly providing services to users. Suppose a global video streaming company uses multiple CDNs to cover different geographical regions. A CDN dedicated to serving the Asian region can be considered a DCDN. Additionally, in the embodiments of the present disclosure, a redirect request is issued when a certain DCDN is unable to provide services to users due to high load, maintenance, or other reasons. In this case, the DCDN will send a redirect request to another more suitable DCDN, asking to direct the user's request to that DCDN. For example, if the DCDN in the Asian region detects that its server is running near full capacity, it can send a redirect request to another DCDN in the European region to ensure that users can continue to watch videos smoothly.

[0057] S304, send a target service request to the target downstream content delivery network according to the redirect request, so that the target downstream content delivery network provides the target service.

[0058] It should be noted that in the embodiments of the present disclosure, the target downstream content delivery network refers to a CDN that is currently processing a user request but needs to transfer this request to other DCDNs for some reason. Once the target DCDN is determined, the DCDN to be redirected will send a target service request to the target DCDN, informing it to be ready to receive and provide the target service corresponding to the user's needs.

[0059] In the redirect method for content delivery network interconnection routing provided in the embodiments of the present disclosure, first, receive a redirect request sent by the downstream content delivery network to be redirected; then, send a target service request to the target downstream content delivery network according to the redirect request, so that the target downstream content delivery network provides the target service. Compared with the related art where the service scheduling of the downstream content delivery network needs to be uniformly decided by the upstream content delivery network, when the downstream content delivery network node needs to migrate services due to cache invalidation or performance degradation, the request must be rolled back to the upstream content delivery network for reallocation. The embodiments of the present disclosure break through the bottleneck of the traditional content delivery network interconnection relying on the upstream content delivery network. When a certain downstream content delivery network has service anomalies, it can directly redirect the user request by skipping the upstream content delivery network, greatly improving the migration efficiency and security.

[0060] In some embodiments, the content distribution network interconnection system in the embodiments of the present disclosure includes: an upstream content distribution network. Before receiving a redirection request sent by a downstream content distribution network to be redirected, the redirection method of the content distribution network interconnection routing in the embodiments of the present disclosure further includes: determining a docking strategy between the upstream content distribution network and multiple downstream content distribution networks based on a content distribution network interconnection protocol, where the content distribution network interconnection protocol is used to enable the upstream content distribution network to identify and connect to the downstream content distribution network; generating a core shared routing table according to the docking strategy, and the core shared routing table is used to store network service configuration information of the upstream content distribution network and multiple downstream content distribution networks. Specifically, through the core shared routing table, the UCDN can identify the service capabilities and status of each DCDN (such as geographical coverage, load conditions, cache hit rate, etc.), so as to dynamically select the optimal content distribution path according to the current network conditions, which helps to reduce latency and improve content delivery speed. Moreover, based on the information in the SRT, the UCDN can more reasonably allocate traffic to different DCDNs, avoid overloading of a single node, and ensure the stability and reliability of the overall system. In addition, the SRT in the embodiments of the present disclosure not only includes basic service configuration information, but also can store a key pool and content identifier conversion rules. For example, when transmitting sensitive data, the information can be protected by keys provided by quantum encryption technology; it should be noted that in some embodiments, the network service configuration information in the embodiments of the present disclosure includes information such as CDN service capabilities, metadata, key pools, and service request uniform resource locator (URL) rules of each CDN.

[0061] In some embodiments, the embodiments of the present disclosure form a hierarchical shared routing table structure with the core SRT and the associated SRT. Specifically, the UCDN maintains the core SRT, records the service capabilities, load status, protocol support, key pool, and content identifier conversion rules of all CDN nodes; each DCDN node holds a read-only copy of the associated SRT, and can decide whether to initiate service migration to other DCDNs based on this.

[0062] In some embodiments, the core SRT data structure in the embodiments of the present disclosure includes: CDN identifier, service capabilities, content delivery network interconnection policy, and key pool. Specifically, the CDN identifier in the embodiments of the present disclosure is used to uniquely identify each CDN (e.g., CDN-ID). The service capabilities in the embodiments of the present disclosure include: Geographic coverage (Footprint): The geographical regions supported by the CDN (e.g., countries, cities); Load status: The current load (e.g., CPU usage rate, bandwidth utilization rate); Cache hit rate: The hit rate of content caching, reflecting content availability; Latency performance: The average delivery latency of the CDN (e.g., calculated based on historical data); Supported protocols: The content delivery protocols supported (such as HTTP / 2, QUIC). The content delivery network interconnection policy in the embodiments of the present disclosure includes: Content delivery policy: For example, geographical restrictions, access control policies; Content identifier definition: The content identifier of the CDN service (URL composition and parameter definition). The key pool in the embodiments of the present disclosure includes: The public key of the DCDN.

[0063] In some embodiments, the associated SRT data structure in the embodiments of the present disclosure includes: CDN identifier, service route identifier, service route weight, content identifier conversion, and key pool. Specifically, the CDN identifier in the embodiments of the present disclosure is used to uniquely identify each CDN. The service route identifier in the embodiments of the present disclosure is used to uniquely identify each service, including CDN-ID and service capability ID (HTTP2, QUIC, etc.). The service route weight in the embodiments of the present disclosure is the service weight corresponding to each collaborating CDN (which can be represented by a Cost value), and the DCDN determines which CDN (UCDN or other DCDN) to redirect the service to according to this value. The content identifier conversion in the embodiments of the present disclosure is a regular expression for converting the content service identifier, which can convert the original service URL into the corresponding URL of the target CDN. The key pool in the embodiments of the present disclosure includes the public keys of each CDN.

[0064] In some embodiments, after the core shared routing table is generated in the embodiments of the present disclosure, the method for redirecting content distribution network interconnection routing in the embodiments of the present disclosure further includes: generating associated shared routing tables corresponding to multiple downstream content distribution networks based on the network service configuration information of the multiple downstream content distribution networks in the core shared routing table, where the associated shared routing tables are associated with the core shared routing table and are configured to store relevant information generated based on the data records in the core shared routing table. Specifically, each DCDN in the embodiments of the present disclosure can have a dedicated associated shared routing table customized for it according to its own characteristics and service requirements, enabling the DCDN to more accurately manage and optimize its internal resource allocation and service strategies without relying on a general core SRT. Moreover, since the associated SRT is relevant information generated based on the data records in the core SRT, it usually only contains the part related to this DCDN, reducing the amount of data to be queried and processed and helping to speed up the decision-making process. Additionally, if a certain DCDN fails or becomes unavailable, other DCDNs can identify alternative service providers by checking their own associated SRTs, ensuring continuous provision of high-quality services even when local network problems occur.

[0065] In some embodiments, as Figure 4 shown, the device applying the method for redirecting content distribution network interconnection routing in the embodiments of the present disclosure needs to have a UCDN and a DCDN. Among them, the UCDN includes UCDN nodes and a core SRT, and the DCDN includes DCDN nodes and an associated SRT. More specifically, the core SRT is used to store information such as CDN service capabilities, metadata, key pools, and service request URL rules of each CDN; the UCDN manages the core SRT and generates and periodically updates the associated SRTs of each DCDN according to the core SRT and the docking strategy between the UCDN and the DCDN; the associated SRT is used to store routing information and serve as the service capabilities and metadata of the DCDN; the DCDN manages the associated SRT and migrates services to other DCDNs when the service quality cannot be met; the corresponding DCDN should be able to check whether it can provide corresponding services through its own associated SRT according to the migrated service request.

[0066] In some embodiments, as Figure 4As shown, the redirect request in the embodiments of the present disclosure is generated according to the associated shared routing table corresponding to the downstream content distribution network to be redirected. Specifically, in the embodiments of the present disclosure, a core SRT is set on the UCDN, and an associated SRT is set on each DCDN. The DCDN can directly redirect user requests to other DCDNs through the associated SRT. It should be noted that the SRT does not change the relationship between the UCDN and the DCDN that are interconnected by the existing content distribution network, but can directly redirect user requests by skipping the UCDN, greatly improving the migration efficiency and security.

[0067] In some embodiments, as Figure 4 shown, after the embodiments of the present disclosure generate the core shared routing table according to the docking policy, the method for redirecting the content distribution network interconnection routing in the embodiments of the present disclosure further includes: when the downstream content distribution network changes, updating the core shared routing table; and updating the associated shared routing table corresponding to the downstream content distribution network according to the network service configuration information of the downstream content distribution network in the updated core shared routing table. Specifically, when changes occur in the service capabilities, load status, protocol support, etc. of the DCDN, timely updating of the core SRT and the associated SRT can ensure that all relevant parties obtain the latest and accurate information, avoiding incorrect decisions or inefficient operations caused by outdated information; moreover, dynamically adjusting the core SRT and the associated SRT to reflect the latest network conditions and service requirements enables the entire CDN system to quickly adapt to changes; in addition, the core SRT and the associated SRT not only contain basic service configuration information, but may also involve security-related information such as key pools and content identifier conversion rules, which is crucial for maintaining secure communication between DCDNs. Especially when dealing with sensitive data, timely updating of the core SRT and the associated SRT ensures that all participating parties use the latest and correct security parameters.

[0068] In some embodiments, as Figure 5 shown, the generation and update process of the core SRT and the associated SRT in the embodiments of the present disclosure includes:

[0069] S502, the DCDN reports its service capabilities through the content distribution network interconnection protocol.

[0070] S504, after the UCDN receives the service capabilities of the DCDN, it updates the corresponding entry of the core SRT.

[0071] S506, the UCDN calculates the service weight of the corresponding entry of the associated SRT of the DCDN

[0072] S508, the UCDN updates the associated SRT of the DCDN.

[0073] In some embodiments, the generation and update of the core SRT and the associated SRT in the embodiments of the present disclosure are provided by the UCDN docking content provider and determine which DCDN specifically provides the target service. The embodiments of the present disclosure do not change the docking logic of the content delivery network interconnection protocol. The generation and update of the associated SRT are both determined by the core SRT; the DCDN can directly determine the service redirection corresponding DCDN from the associated SRT table without going through the UCDN for transit again.

[0074] In some embodiments, before the content delivery network interconnection route redirection method in the embodiments of the present disclosure sends a target service request to the target downstream content delivery network according to a redirection request, it further includes: controlling the verification between the downstream content delivery network to be redirected and the target downstream content delivery network through an asymmetric key signature. Specifically, the asymmetric key signature uses a pair of keys - a public key and a private key. The issuer uses its private key to sign the data (such as the token in the redirection request), and the receiver uses the public key of the issuer to verify the validity of the signature, ensuring that only the entity with the correct private key can generate a valid signature, thereby preventing the forgery or tampering of the redirection request. Even if the data transmitted in the network is intercepted, the attacker cannot forge a legitimate redirection request because they do not have the corresponding private key; secondly, each DCDN has its own public key and private key pair. During the redirection process, the DCDN to be redirected uses its private key to sign a token containing key information (such as the issuing CDN-ID, target CDN-ID, URL hash value, expiration time, etc.). The target DCDN can use the public key of the DCDN to be redirected to verify the token and confirm that it indeed comes from the specified DCDN rather than an imposter, ensuring the authenticity and integrity of the redirection request; in addition, since each DCDN has an independent key pair and can obtain the public keys of other DCDNs through public channels, there is no need to rely on a third-party authority for identity verification. This decentralized trust model enables DCDNs to directly establish a secure connection and complete the necessary verification without the real-time intervention of the UCDN.

[0075] In some embodiments, taking the migration process of the DCDN1 service to the DCDN2 service as an example, the migration in the embodiments of the present disclosure mainly includes: the DCDN1 migration URL and token generation process and the DCDN2 migration URL and token verification process. Specifically, the DCDN1 migration URL and token generation process includes:

[0076] 1). Selection of the redirected target CDN:

[0077] When DCDN1 detects poor service quality, it queries its own associated SRT, and through querying the service route, selects DCDN2 with the lowest Cost value as the target CDN.

[0078] 2) Migration URL Generation:

[0079] Convert the original service URL to the corresponding URL of DCDN2 through the regular expression of content service identifier conversion.

[0080] 3) Token Construction:

[0081] The token includes the following parameters: issued CDN-ID, target CDN-ID, hash value of the migration URL, expiration time; Token signature: Sign the token using the private key of dCDN1 to generate the final token.

[0082] In some embodiments, the DCDN2 migration URL and token verification process in the embodiments of the present disclosure includes:

[0083] 1) Issuer Public Key Acquisition:

[0084] Obtain from the service request that the request source is DCDN1, and extract the public key of DCDN1 from the CDN public key pool associated with SRT;

[0085] 2) Token Verification:

[0086] DCDN2 decrypts the token using the DCDN1 public key and checks the field integrity and timeliness (whether it has expired);

[0087] 3) Provide Service:

[0088] If the token verification passes, provide the service.

[0089] In some embodiments, the DCDN1 migration URL and token generation process and the DCDN2 migration URL and token verification process in the embodiments of the present disclosure can completely remove the real-time participation of UCDN in the process of generating security tokens, and realize direct cooperation between DCDNs through the key information and policies preset by the associated SRT, achieving decentralized trust; although the core SRT is still managed and updated by UCDN, the policy data (public key, routing) is regularly synchronized to the associated SRT, which can support offline verification and realize dynamic policy synchronization; in addition, the process of generating security tokens and the whole process of key verification do not depend on the online interaction of UCDN, realizing decentralized permission verification.

[0090] In some embodiments, when the present disclosure's embodiments detect insufficient service quality in the DCDN, they select a target DCDN based on metrics such as the "service weight (Cost value)" in the associated SRT, construct a redirect URL, and generate a service migration request. More specifically, to be compatible with the existing content delivery network interconnection strategy, the UCDN needs to dynamically calculate the associated SRT of each DCDN based on the data in the core SRT. When calculating the corresponding service weight, it is necessary to first screen the DCDNs that meet the content delivery network interconnection strategy, and then calculate the service weight (Cost value) based on factors such as resource availability among the eligible DCDNs. The specific calculation process includes: policy screening and resource evaluation.

[0091] In some embodiments, the policy screening in the present disclosure's embodiments is that the UCDN checks one by one whether each DCDN meets the following conditions according to the docking policy recorded in the core SRT. The DCDNs that do not meet the conditions will be excluded. The conditions include: Geographic coverage matching: The geographic coverage (Footprint) of the DCDN must cover the area where the user is located to meet the geographic restriction policy of content delivery network interconnection. If not, it will be directly excluded; Protocol support: The DCDN must support the protocol requested by the client (such as HTTP / 2, QUIC). If not, it will be directly excluded; Access control policy: The DCDN must comply with the access control rules defined in the core SRT (such as the black and white lists for content delivery). If not, it will be directly excluded. Only the DCDNs that pass the above policy screening can enter the subsequent service weight calculation stage.

[0092] In some embodiments, the resource evaluation in the present disclosure's embodiments is to calculate the service weight by comprehensively considering the following resource availability factors among the DCDNs that meet the content delivery network interconnection strategy: Load status: According to the current load of the DCDN recorded in the core SRT (such as CPU usage rate, bandwidth utilization rate), the lower the load, the smaller the service weight and the higher the priority; Cache hit rate: Reflects the content availability of the DCDN. The higher the cache hit rate, the more the content can be directly provided and the lower the service weight; Latency performance: Based on the historical average distribution latency of the DCDN recorded in the core SRT, the lower the latency, the smaller the service weight.

[0093] In some embodiments, the present disclosure's embodiments ensure the efficiency and policy compliance of service migration through policy screening and resource evaluation.

[0094] In some embodiments, the downstream content delivery network in the embodiments of the present disclosure only reads and associates and shares a routing table. Specifically, by restricting the modification permission of the DCDN to the associated SRT, it is ensured that all service configuration information is uniformly maintained and updated by the UCDN, avoiding data inconsistency problems caused by decentralized management or misoperations, and ensuring that the information stored in the associated SRT is always the latest and accurate; secondly, read-only access reduces potential security risks, prevents malicious tampering with routing policies or other important configurations, and protects the integrity of user data and services; in addition, the centralized management and update of the associated SRT by the UCDN reduces the complexity of multi-node synchronization and coordination in a distributed environment. One only needs to focus on the maintenance of the core SRT without worrying about whether the local configuration on each DCDN is correct, which not only saves time and resources but also reduces the possibility of errors and improves the operation and maintenance efficiency.

[0095] In some embodiments, the embodiments of the present disclosure enable direct cooperation between DCDNs through a hierarchical SRT structure and an autonomous redirection mechanism, skipping the transit of the UCDN, reducing the number of hops and latency of service migration, significantly improving the efficiency of content delivery, and enhancing service efficiency and elasticity; moreover, the decentralized design enhances system elasticity, and the DCDN can quickly respond to sudden service exceptions (such as load surges or node failures) to ensure service continuity; in addition, the service weight calculation strictly follows the content delivery network interconnection policy (such as geographical restrictions, protocol support), ensuring seamless compatibility with the existing content delivery network interconnection architecture, and at the same time, eliminating unqualified DCDNs through a screening mechanism to improve the success rate of migration and policy compliance.

[0096] Based on the same inventive concept, embodiments of the present disclosure also provide a redirection device for content delivery network interconnection routing, as described in the following embodiments. Since the principle of solving problems in this device embodiment is similar to that of the above method embodiment, the implementation of this device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be elaborated.

[0097] Figure 6 The following shows a schematic diagram of a redirection device for content delivery network interconnection routing in the embodiments of the present disclosure. This device is applied to a content delivery network interconnection system, which includes multiple downstream content delivery networks. The device includes:

[0098] A redirection request receiving module 601, configured to receive a redirection request sent by a downstream content delivery network to be redirected;

[0099] A target service request sending module 602, configured to send a target service request to a target downstream content delivery network according to the redirection request, so that the target downstream content delivery network provides the target service.

[0100] In an embodiment of the present disclosure, a redirecting device for content distribution network interconnection routing is provided. The redirecting device receives a redirect request sent by a downstream content distribution network to be redirected through a redirect request receiving module, and sends a target service request to a target downstream content distribution network according to the redirect request through a target service request sending module, so that the target downstream content distribution network provides a target service. Compared with the related art, in which the service scheduling of the downstream content distribution network needs to be uniformly decided by the upstream content distribution network, when the service of a downstream content distribution network node needs to be migrated due to cache invalidation or performance degradation, the request must be rolled back to the upstream content distribution network for reallocation. The embodiment of the present disclosure breaks through the bottleneck of the traditional content distribution network interconnection that depends on the upstream content distribution network. When the service of a certain downstream content distribution network is abnormal, the user request can be directly redirected by skipping the upstream content distribution network, greatly improving the migration efficiency and security.

[0101] In some embodiments, the content distribution network interconnection system in the embodiment of the present disclosure includes: an upstream content distribution network. The redirecting device for content distribution network interconnection routing in the embodiment of the present disclosure further includes: a docking policy determination module, configured to determine a docking policy between the upstream content distribution network and multiple downstream content distribution networks based on a content distribution network interconnection protocol before receiving a redirect request sent by a downstream content distribution network to be redirected. The content distribution network interconnection protocol is used to enable the upstream content distribution network to identify and connect to the downstream content distribution network; a core shared routing table generation module, configured to generate a core shared routing table according to the docking policy. The core shared routing table is used to store the network service configuration information of the upstream content distribution network and multiple downstream content distribution networks.

[0102] In some embodiments, the redirecting device for content distribution network interconnection routing in the embodiment of the present disclosure further includes: an associated shared routing table generation module, configured to generate an associated shared routing table corresponding to multiple downstream content distribution networks based on the network service configuration information of the multiple downstream content distribution networks in the core shared routing table after generating the core shared routing table. The associated shared routing table is associated with the core shared routing table and is configured to store relevant information generated based on the data records in the core shared routing table.

[0103] In some embodiments, the redirect request in the embodiment of the present disclosure is generated according to the associated shared routing table corresponding to the downstream content distribution network to be redirected.

[0104] In some embodiments, the redirecting device for content delivery network interconnection routing in the embodiments of the present disclosure further includes: a core shared routing table update module, configured to update the core shared routing table when a downstream content delivery network changes after generating the core shared routing table according to the docking policy; an associated shared routing table update module, configured to update the associated shared routing table corresponding to the downstream content delivery network according to the network service configuration information of the downstream content delivery network in the updated core shared routing table.

[0105] In some embodiments, the redirecting device for content delivery network interconnection routing in the embodiments of the present disclosure further includes: a verification module, configured to control the verification between the downstream content delivery network to be redirected and the target downstream content delivery network to be completed through asymmetric key signature before sending a target service request to the target downstream content delivery network according to the redirect request.

[0106] In some embodiments, the downstream content delivery network in the embodiments of the present disclosure has a read-only associated shared routing table.

[0107] Based on the same inventive concept, an embodiment of the present disclosure further provides a redirecting system for content delivery network interconnection routing, as shown in the following embodiments. Since the principle of solving problems in this system embodiment is similar to that of the above method embodiment, the implementation of this system embodiment can refer to the implementation of the above method embodiment, and repeated parts will not be described again.

[0108] A schematic diagram of a redirecting system for content delivery network interconnection routing in an embodiment of the present disclosure, the system includes:

[0109] A downstream content delivery network, configured to send a redirect request and receive a target service request;

[0110] A client, configured to receive a redirect request sent by the downstream content delivery network to be redirected, and send a target service request to the target downstream content delivery network according to the redirect request, so that the target downstream content delivery network provides a target service.

[0111] In some embodiments, as Figure 7 shown, in the embodiments of the present disclosure, a core SRT is set on the UCDN, and an associated SRT is set on each DCDN. The DCDN can directly redirect user requests to other DCDNs through the associated SRT. The SRT does not change the relationship between the UCDN and the DCDN in the existing content delivery network interconnection, but can directly redirect user requests by skipping the UCDN, greatly improving the migration efficiency and security.

[0112] Those skilled in the art can understand that various aspects of the present disclosure can be implemented as a system, a method, or a program product. Therefore, various aspects of the present disclosure can be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software aspects, which can be collectively referred to as "circuitry", "module", or "system" here.

[0113] Based on the same inventive concept, an electronic device is further provided in an embodiment of the present disclosure. The electronic device includes: a processor; and a memory for storing executable instructions of the processor; wherein, the processor is configured to execute the content distribution network interconnection routing redirection method of any one of the above via executing the executable instructions. Since the principle of solving problems in this embodiment of the electronic device is similar to that of the above method embodiment, the implementation of this embodiment of the electronic device can refer to the implementation of the above method embodiment, and the repeated parts will not be elaborated.

[0114] Hereinafter, reference is made to Figure 8 describe the electronic device 800 according to this embodiment of the present disclosure. Figure 8 The illustrated electronic device 800 is merely an example and should not impose any limitation on the functions and usage scope of the embodiments of the present disclosure.

[0115] As Figure 8 shown, the electronic device 800 is presented in the form of a general-purpose computing device. The components of the electronic device 800 may include but are not limited to: at least one of the above processing units 801, at least one of the above storage units 802, and a bus 803 connecting different system components (including the storage unit 802 and the processing unit 801).

[0116] Among them, the storage unit stores program code, and the program code can be executed by the processing unit 801, so that the processing unit 801 executes the steps according to various exemplary embodiments of the present disclosure described in the above "Exemplary Method" section of this specification.

[0117] In some embodiments, when the electronic device is used to control, for example, the content distribution network interconnection routing redirection method of the present disclosure above, the processing unit 801 may execute the following steps of the above method embodiment:

[0118] Receive a redirection request sent by a downstream content distribution network to be redirected; send a target service request to a target downstream content distribution network according to the redirection request, so that the target downstream content distribution network provides a target service.

[0119] The storage unit 802 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 8021 and / or a cache storage unit 8022, and may further include a read-only storage unit (ROM) 8023.

[0120] The storage unit 802 may also include a program / utilities 8024 having a set (at least one) of program modules 8025. Such program modules 8025 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment.

[0121] The bus 803 may represent one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus structures.

[0122] The electronic device 800 may also communicate with one or more external devices 804 (such as a keyboard, a pointing device, a Bluetooth device, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 800, and / or may communicate with any device that enables the electronic device 800 to communicate with one or more other computing devices (such as a router, a modem, etc.). Such communication may be carried out through an input / output (I / O) interface 805. Moreover, the electronic device 800 may also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 806. As shown in the figure, the network adapter 806 communicates with other modules of the electronic device 800 through the bus 803. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0123] Through the description of the above embodiments, those skilled in the art can easily understand that the example embodiments described herein can be implemented by software, or can be implemented by a combination of software and necessary hardware. Therefore, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

[0124] Based on the same inventive concept, embodiments of the present disclosure also provide a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the content distribution network interconnection routing redirection method of any one of the above. Since the principle of solving problems in the computer-readable storage medium embodiment is similar to that of the above method embodiment, the implementation of the computer-readable storage medium embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be elaborated.

[0125] More specific examples of the computer-readable storage medium in the present disclosure may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above.

[0126] In the present disclosure, the computer-readable storage medium may include a data signal propagated in a baseband or as part of a carrier wave, in which the readable program code is carried. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The readable signal medium may also be any readable medium other than the readable storage medium, and the readable medium may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0127] Optionally, the program code contained on the computer-readable storage medium may be transmitted by any suitable medium, including but not limited to wireless, wired, optical fiber cable, RF, etc., or any suitable combination of the above.

[0128] In specific implementation, the program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages. The programming languages include object-oriented programming languages - such as Java, C++, etc., and also include conventional procedural programming languages - such as the "C" language or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, executed as an independent software package, partially on the user computing device and partially on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (for example, by using an Internet service provider to connect through the Internet).

[0129] Based on the same inventive concept, embodiments of the present disclosure also provide a computer program product, including: a computer program or instruction, which when executed by a processor implements the content distribution network interconnection routing redirection method in any one of the above method embodiments. Since the principle of solving problems in this computer program product embodiment is similar to that of the above method embodiments, the implementation of this computer program product embodiment can refer to the implementation of the above method embodiments, and the repeated parts will not be elaborated again.

[0130] It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more of the above-described modules or units can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0131] In addition, although the steps of the methods in the present disclosure are described in a specific order in the drawings, this does not require or imply that these steps must be executed in that specific order, or that all the steps shown must be executed to achieve the desired result. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step for execution, and / or one step may be decomposed into multiple steps for execution, etc.

[0132] Through the description of the above embodiments, those skilled in the art can easily understand that the exemplary embodiments described herein can be implemented by software, or by a combination of software and necessary hardware. Therefore, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

[0133] After considering the specification and practicing the invention disclosed herein, those skilled in the art will readily conceive of other embodiments of the present disclosure. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure, which follow the general principles of the present disclosure and include known common general knowledge or conventional technical means in the technical field not disclosed in the present disclosure. The specification and examples are only regarded as exemplary, and the true scope and spirit of the present disclosure are pointed out by the appended claims.

Claims

1. A redirect method for content distribution network interconnection routing, characterized in that, Applied to a content delivery network interconnection system, the content delivery network interconnection system includes a plurality of downstream content delivery networks, and the method includes: Receiving a redirection request sent by a downstream content delivery network to be redirected; Sending a target service request to a target downstream content delivery network according to the redirection request, so that the target downstream content delivery network provides a target service.

2. The redirect method for content distribution network interconnection routing according to claim 1, characterized in that The content delivery network interconnection system includes: an upstream content delivery network. Before receiving a redirection request sent by a downstream content delivery network to be redirected, the method further includes: Based on a content delivery network interconnection protocol, determining a docking strategy between the upstream content delivery network and a plurality of downstream content delivery networks, where the content delivery network interconnection protocol is used to enable the upstream content delivery network to identify and connect to the downstream content delivery network; Generating a core shared routing table according to the docking strategy, where the core shared routing table is used to store network service configuration information of the upstream content delivery network and a plurality of downstream content delivery networks.

3. The redirect method for content distribution network interconnection routing according to claim 2, characterized in that, After generating the core shared routing table, the method further includes: Generating associated shared routing tables corresponding to a plurality of downstream content delivery networks based on the network service configuration information of the plurality of downstream content delivery networks in the core shared routing table, where the associated shared routing tables are associated with the core shared routing table and are configured to store relevant information generated according to data records in the core shared routing table.

4. The redirect method for content distribution network interconnection routing according to claim 3, characterized in that The redirection request is generated according to the associated shared routing table corresponding to the downstream content delivery network to be redirected.

5. The redirect method for content distribution network interconnection routing according to claim 3, characterized in that After generating the core shared routing table according to the docking strategy, the method further includes: Updating the core shared routing table when the downstream content delivery network changes; Updating the associated shared routing table corresponding to the downstream content delivery network according to the network service configuration information of the downstream content delivery network in the updated core shared routing table.

6. The redirect method for content distribution network interconnection routing according to claim 1, characterized in that, Before sending a target service request to a target downstream content delivery network according to the redirection request, the method further includes: Controlling the verification between the downstream content delivery network to be redirected and the target downstream content delivery network through an asymmetric key signature.

7. The redirect method for content distribution network interconnection routing according to claim 3, characterized in that, The downstream content delivery network only reads the associated shared routing table.

8. A redirect device for content distribution network interconnection routing, characterized in that, Applied to a content delivery network interconnection system, the content delivery network interconnection system includes a plurality of downstream content delivery networks, and the device includes: A redirection request receiving module, configured to receive a redirection request sent by a downstream content delivery network to be redirected; A target service request sending module, configured to send a target service request to a target downstream content delivery network according to the redirection request, so that the target downstream content delivery network provides a target service.

9. A redirect system for content distribution network interconnection routing, characterized in that, Including: A downstream content delivery network, configured to send a redirection request and receive a target service request; A client, configured to receive a redirection request sent by a downstream content delivery network to be redirected, and send the target service request to a target downstream content delivery network according to the redirection request, so that the target downstream content delivery network provides a target service.

10. An electronic device, characterized in that, Including: A processor; And A memory for storing executable instructions of the processor; Wherein, the processor is configured to execute the redirect method of the content distribution network interconnection routing according to any one of claims 1 to 7 by executing the executable instructions.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the redirect method of the content distribution network interconnection routing according to any one of claims 1 to 7.

12. A computer program product, comprising: A computer program or instruction, characterized in that when the computer program or instruction is executed by a processor, it implements the redirect method of the content distribution network interconnection routing according to any one of claims 1 to 7.

Images