Processing method and apparatus for back-to-source request of content delivery network, and device and medium

By introducing the source station server to the CDN to receive the source request and issue the access identifier, the problem that the CDN and the source station cannot converge during the domain name creation and adaptation process is solved, simplifying the process and reducing the difficulty of operation and maintenance.

WO2024235249A1PCT designated stage expired Publication Date: 2024-11-21BEIJING VOLCANO ENGINE TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/093312
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-18
Filing Date
2024-05-15
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In the content distribution network (CDN), different source stations cannot converge during the domain name creation and adaptation process, resulting in increased business complexity and operation and maintenance difficulties.

Method used

Receive the CDN server's return request through the source station server, decouple the CDN server with the service domain name, and uniformly send the access identifier of the source station access from the source station server to avoid the CDN server sending the source back request directly to the source station, thereby solving the problem of The problem of inconsistency in the creation and adaptation of domain names.

Benefits of technology

It reduces the complexity of the domain name creation process, realizes the convergence of business domain names, simplifies the decoupling of CDN servers and business domain names, and reduces the difficulty of operation and maintenance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024093312_21112024_PF_FP_ABST
    Figure CN2024093312_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed in the present disclosure are a processing method and apparatus for a back-to-source request of a content delivery network (CDN), and a device and a medium. The method comprises: receiving a back-to-source request carrying an access identifier, wherein the access identifier comprises a target acceleration domain name and a target service provider identifier; querying a target source station corresponding to the target acceleration domain name, and acquiring source station configuration information corresponding to the target source station; generating a target access identifier of the target source station on the basis of the source station configuration information; and sending the target access identifier to a target CDN server corresponding to the target service provider identifier, wherein the target CDN server acquires a target resource from the target source station according to the target access identifier.
Need to check novelty before this filing date? Find Prior Art

Description

Content distribution network back-to-origin request processing method, device, equipment and medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202310567586.9, entitled “Method, device, equipment and medium for processing content distribution network back-to-origin requests” filed on May 18, 2023, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates to the field of communication technologies, and in particular to a method, apparatus, device, and medium for processing a content distribution network back-to-origin request. Background Art

[0004] For current Internet businesses, if they need to continuously and efficiently configure the accelerated domain names of different Content Delivery Network (CDN) service providers in real time, they usually align the domain names with the CDN service providers to automatically create OpenAPIs. The general solution is to create domain names based on the minimum functional template domain name solution.

[0005] Summary of the Invention

[0006] The present disclosure provides a method, apparatus, device, and medium for processing a content distribution network back-to-origin request.

[0007] According to one aspect of an embodiment of the present disclosure, a method for processing a content delivery network back-to-origin request is provided. The method is applied to an origin server, which is in communication with multiple CDN servers. The method includes:

[0008] Receive a back-to-origin request carrying an access identifier, wherein the access identifier includes a target acceleration domain name and a target service provider identifier, the target acceleration domain name is generated by the target CDN server according to preset configuration information, and the target service provider identifier is the target service provider identifier of the target CDN server;

[0009] Query the target origin server corresponding to the target acceleration domain name and obtain the origin server configuration information corresponding to the target origin server;

[0010] Generate a target access identifier for the target source station based on the source station configuration information;

[0011] The target access identifier is sent to a target CDN server corresponding to the target service provider identifier, wherein the target CDN server obtains the target resource from the target source station according to the target access identifier.

[0012] According to another aspect of an embodiment of the present disclosure, a method for processing a content delivery network back-to-origin request is provided. The method is applied to a target CDN server, which is any server in communication with an origin server. The method includes:

[0013] Receiving a service request from a client, wherein the service request carries an original access identifier of a service to be accessed by the client;

[0014] In response to the service request, using the original access identifier to obtain service information of the service to be accessed, and generating a target acceleration domain name based on the service information and preset configuration information corresponding to the target CDN server;

[0015] Generate a back-to-origin request based on the target acceleration domain name and the target service provider identifier of the target CDN server, and send the back-to-origin request to the origin server;

[0016] Receive the target access identifier fed back by the source server based on the back-to-source request, and use the target access identifier to obtain the target resource from the target source server.

[0017] According to another aspect of an embodiment of the present disclosure, a device for processing a content distribution network back-to-origin request is provided, including:

[0018] A first receiving module is configured to receive a back-to-origin request carrying an access identifier, wherein the access identifier includes a target acceleration domain name and a target service provider identifier, wherein the target acceleration domain name is generated by a target CDN server according to preset configuration information, and the target service provider identifier is a target service provider identifier of the target CDN server;

[0019] A query module, configured to query the target origin server corresponding to the target acceleration domain name and obtain the origin server configuration information corresponding to the target origin server;

[0020] A first generating module, configured to generate a target access identifier of the target source station based on the source station configuration information;

[0021] The sending module is configured to send the target access identifier to a target CDN server corresponding to the target service provider identifier, wherein the target CDN server obtains target resources from the target source station according to the target access identifier.

[0022] According to another aspect of an embodiment of the present disclosure, a device for processing a content distribution network back-to-origin request is provided, including:

[0023] A second receiving module is configured to receive a service request from a client, wherein the service request carries an original access identifier of a service to be accessed by the client;

[0024] A response module, configured to respond to the service request, obtain service information of the service to be accessed using the original access identifier, and generate a target acceleration domain name based on the service information and preset configuration information corresponding to the target CDN server;

[0025] A second generating module is configured to generate a back-to-origin request based on the target acceleration domain name and the target service provider identifier of the target CDN server, and send the back-to-origin request to the origin server;

[0026] The processing module is configured to receive a target access identifier fed back by the source server based on the back-to-source request, and obtain a target resource from a target source server using the target access identifier.

[0027] According to another aspect of an embodiment of the present disclosure, a storage medium is further provided. The storage medium includes a stored program, and the above steps are executed when the program is run.

[0028] According to another aspect of an embodiment of the present disclosure, an electronic device is also provided, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; wherein: the memory is used to store computer programs; and the processor is used to execute the steps in the above method by running the program stored in the memory.

[0029] The embodiment of the present disclosure further provides a computer program product comprising instructions, which, when executed on a computer, causes the computer to execute the steps in the above method.

[0030] The embodiment of the present disclosure further provides a computer program, which, when executed on a computer, enables the computer to execute the steps in the above method. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0033] FIG1 is a flowchart of a method for processing a content distribution network back-to-origin request provided by an embodiment of the present disclosure;

[0034] FIG2 is a flowchart of a method for processing a content distribution network back-to-origin request provided by another embodiment of the present disclosure;

[0035] FIG3 is a schematic diagram of a process for processing a back-to-origin request provided by an embodiment of the present disclosure;

[0036] FIG4 is a block diagram of a device for processing a content distribution network back-to-origin request provided by an embodiment of the present disclosure;

[0037] FIG5 is a block diagram of a device for processing a content distribution network back-to-origin request provided by another embodiment of the present disclosure;

[0038] FIG6 is a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0039] To make the purpose, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. The schematic embodiments of the present disclosure and their descriptions are used to explain the present disclosure and do not constitute an improper limitation of the present disclosure. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.

[0040] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another similar entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

[0041] The present disclosure provides a method, apparatus, device, and medium for processing a content distribution network (CDN) back-to-origin request. The method provided by the present disclosure can be applied to any desired electronic device, such as a server or terminal. For ease of description, these devices will be referred to as electronic devices.

[0042] Currently, for static domain name services such as images, downloads, and on-demand services, the corresponding source sites have global coverage. Therefore, every time an acceleration domain name is configured on the CDN side, the problem of accelerating domain name adaptation needs to be solved at the source site. Ultimately, the domain name creation business is complex and cannot be converged.

[0043] The above technical solution provided by the embodiment of the present disclosure has the following advantages compared with the related technology: the method provided by the embodiment of the present disclosure receives the back-to-source request of the CDN server through the source station server, decouples the CDN server from the business domain name, and does not require the CDN server to directly send the back-to-source request to the source station. Instead, the source station server uniformly issues an access identifier for accessing the source station to the CDN server, thereby solving the problem that different source stations cannot converge during the domain name creation and adaptation process.

[0044] According to one aspect of an embodiment of the present disclosure, a method embodiment of a method for processing a content distribution network back-to-origin request is provided. FIG1 is a flowchart of a method for processing a content distribution network back-to-origin request provided by an embodiment of the present disclosure. As shown in FIG1 , the method includes:

[0045] Step S11, receiving a back-to-source request carrying an access identifier, wherein the access identifier includes a target acceleration domain name and a target service provider identifier. The target acceleration domain name is generated by the target CDN server based on preset configuration information, and the target service provider identifier is the target service provider identifier of the target CDN server.

[0046] The method provided by the embodiments of the present disclosure is applied to an origin server, which is connected to multiple CDN servers. The origin server can be understood as the origin's 302 server. The 302 in 302 server represents a temporary transfer. Because the acceleration domain name carried in the return-to-origin request sent by the CDN server is temporarily replaced, the origin's 302 server is added to temporarily receive the return-to-origin request from the CDN server and return the corresponding origin's access identifier to the CDN server. This solves the problem of domain name creation services from different service origins not being able to converge.

[0047] Specifically, when performing a back-to-origin operation, the CDN server no longer needs to directly return to the service origin site, but instead returns to the origin site's 302 server. This reduces the complexity of the domain name creation process and decouples the CDN server from the service domain name. The CDN server no longer needs to directly return to the service origin site, thus reducing the difficulty of service operation and maintenance as service domain names expand.

[0048] In the disclosed embodiment, a CDN server receives a service request from a client. The service request carries the Uniform Resource Locator (URL) of the service the client is currently accessing. Based on the URL, the CDN server performs a back-to-source operation. Specifically, the server configures a target acceleration domain name using preset configuration information and service information of the service being accessed. The preset configuration information is pre-configured on the CDN server by the origin server and includes authentication parameters, the origin server's server address, and so on. After the target CDN server configures the target acceleration domain name, it generates a back-to-source request using the target acceleration domain name and its own server identifier, and sends the back-to-source request to the origin server.

[0049] In the disclosed embodiment, the origin server receives a back-to-origin request and extracts the target acceleration domain name and target service provider identifier from the back-to-origin request. It then uses the CDN server corresponding to the target service provider identifier as the target CDN server. The origin server then analyzes the target acceleration domain name and ultimately returns an access identifier to the CDN server, which uses the access identifier to retrieve the corresponding resources.

[0050] Step S12: query the target origin server corresponding to the target acceleration domain name, and obtain the origin server configuration information corresponding to the target origin server.

[0051] In the embodiment of the present disclosure, before querying the target origin server corresponding to the target acceleration domain name, the method further includes the following steps A1-A2:

[0052] Step A1: Check whether the target acceleration domain name carries signature information.

[0053] Step A2: If the target acceleration domain name carries signature information, determine whether the target acceleration domain name supports authenticated access, verify the signature information, and obtain a verification result.

[0054] In the embodiment of the present disclosure, after the source station server obtains the target acceleration domain name, it will detect whether the target acceleration domain name carries signature information. If the target acceleration domain name carries signature information, it means that the target acceleration domain name needs to support authenticated access. At this time, the source station server needs to verify the signature information.

[0055] As an example, the verification process can be as follows: the origin server obtains the public key of the target CDN server and then uses the public key to decrypt the signature information to obtain the decrypted signature information. The decrypted signature information is then encrypted and calculated using the same encryption algorithm as the target CDN server. The calculated result is then verified against the signature information to obtain a verification result. If the calculated result and the signature information are consistent, the verification result is passed. If the calculated result and the signature information are inconsistent, the verification result is failed.

[0056] In the embodiment of the present disclosure, if the target acceleration domain name does not carry signature information, it means that the target acceleration domain name does not need to be authenticated and can be directly returned to the corresponding source station.

[0057] In the embodiment of the present disclosure, querying the target origin server corresponding to the target acceleration domain name and obtaining the origin server configuration information corresponding to the target origin server includes the following steps B1-B2:

[0058] Step B1: If the verification result is passed, obtain the target scheduling rule that matches the target acceleration domain name, and use the source station indicated by the target scheduling rule as the target source station.

[0059] In the disclosed embodiment, if the verification result is passed, multiple scheduling rules currently configured in the origin server are obtained. Scheduling rules include, but are not limited to, those set based on different CDN service providers or business types. Based on these, the fields carried by the target acceleration domain name are matched with the current scheduling rules, the matching scheduling rule is determined as the target scheduling rule, and the origin indicated by the target scheduling rule is used as the target origin.

[0060] As an example, the current scheduling rules include: CDN-01—source station K, CDN-02—source station M, CDN-03—source station N. The service provider field carried by the target acceleration domain name is "CDN-02". At this time, it can be determined that the hit scheduling rule is "CDN-02—source station M", and source station M is the target source station.

[0061] Step B2: Read the source station configuration information corresponding to the target source station, where the source station configuration information includes: authentication algorithm, authentication parameters, source station address corresponding to the target source station, and back-to-source host.

[0062] In the disclosed embodiment, after the origin server determines the target origin to which the CDN server will return, it reads the origin configuration information corresponding to the target origin. This configuration information includes the authentication algorithm, authentication parameters, the origin address corresponding to the target origin, and the return-to-origin host. The authentication parameters are specific information relied upon by the origin server for checksum calculations, and the return-to-origin host is the domain name address that the CDN server needs to access for return-to-origin operations. Furthermore, different origins for different services have different configured authentication algorithms.

[0063] Step S13: Generate a target access identifier of the target source station based on the source station configuration information.

[0064] In the disclosed embodiment, after obtaining the source station configuration information, the origin server uses the source station configuration information to generate a target access identifier. Specifically, the origin server uses an authentication algorithm to sign the authentication parameters, the source station address corresponding to the target source station, and the back-to-source host to generate a URL that can access the target source station, namely the target access identifier. The authentication algorithm can be: ToS V1 Sign, OSS MBuckt, OBS Sign, etc.

[0065] Step S14: sending the target access identifier to the target CDN server corresponding to the target service provider identifier, wherein the target CDN server obtains the target resource from the target origin station according to the target access identifier.

[0066] In the embodiment of the present disclosure, after generating a target access identifier, the origin server sends the target access identifier to the target CDN server. The target CDN server initiates an access request to the target origin server based on the target access identifier to obtain the corresponding target resource.

[0067] The method provided by the embodiment of the present disclosure receives the back-to-origin request from the CDN server through the origin server, decoupling the CDN server from the business domain name. There is no need for the CDN server to send the back-to-origin request directly to the origin server. Instead, the origin server uniformly issues an access identifier for accessing the origin server to the CDN server, thereby solving the problem that different origin servers cannot converge during the domain name creation and adaptation process.

[0068] FIG2 is a flowchart of a method for processing a content distribution network back-to-origin request provided by an embodiment of the present disclosure. As shown in FIG2 , the method may include the following steps:

[0069] Step S21: receiving a service request from a client, wherein the service request carries an original access identifier of a service to be accessed by the client.

[0070] The method provided by the embodiment of the present disclosure is applied to the target CDN server, which is any server that is communicatively connected to the source server. When a user wants to access the resources of a certain service, a service request can be sent through the client. Specifically, the client first obtains the current attribution information, then determines the service to be accessed, and obtains the original domain name of the service to be accessed, for example: the client's current service to be accessed is X, and the original domain name is X-aaa-com. Finally, an original access identifier (Uniform Resource Locator, abbreviated URL) is generated based on the original domain name and the attribution information, and the original access identifier is carried in the service request and sent to the target CDN server. The service to be accessed can be a video service, a picture service, a music service, and so on.

[0071] In the disclosed embodiment, after receiving a service request from a client, the target CDN server can extract the original access identifier from the service request. It then uses the original access identifier to obtain service information for the service to be accessed, and rewrites the original access identifier with the service information to generate a target acceleration domain name for back-to-source.

[0072] Step S22: In response to the service request, the service information of the service to be accessed is obtained using the original access identifier, and a target acceleration domain name is generated based on the service information and preset configuration information corresponding to the target CDN server.

[0073] In the embodiment of the present disclosure, the target CDN server responds to the service request and obtains service information of the service to be accessed using the original access identifier. The service information includes: service type, service key, etc.

[0074] It should be noted that using the original access identifier to obtain business information can, on the one hand, determine whether the business being accessed meets the origin server's back-to-source requirements. On the other hand, if the origin server's back-to-source requirements are met, the business information can be used to configure the acceleration domain name.

[0075] In the embodiment of the present disclosure, generating a target acceleration domain name based on business information and preset configuration information corresponding to the target CDN server includes the following steps C1-C3:

[0076] Step C1: Use the service information to detect whether the service to be accessed meets the domain name creation rule of the source server, and obtain a detection result.

[0077] In the disclosed embodiment, the target CDN server is configured with multiple service types currently supported by the origin server for accelerated domain name creation. Based on this, the service type in the service information is used to determine whether the service to be accessed matches the service type stored on the target CDN server, and whether the service information requires authenticated access, thereby obtaining a detection result. Specifically, this includes the following situations:

[0078] (1) If the service type in the service information matches any of the service types stored in the target CDN server, and the service information requires authentication access, the detection result is: the service to be accessed supports access to the origin server and carries an authentication access identifier.

[0079] (2) If the service type in the service information matches any of the service types stored in the target CDN server, and the service information does not require authentication access, the detection result is: the service to be accessed supports access to the origin server and does not carry an authentication access identifier.

[0080] (3) If the service type in the service information does not match the service type stored in the target CDN server, the detection result is: the service to be accessed does not support access to the origin server.

[0081] In the embodiment of the present disclosure, if the detection result shows that the service to be accessed supports access to the source server and carries an authentication access identifier, or if the detection result shows that the service to be accessed supports access to the source server and does not carry an authentication access identifier, the current process can be continued. If access to the source server is not supported, the current process is terminated.

[0082] Step C2: Obtain a target domain name creation template corresponding to the detection result, wherein the target domain name creation template includes multiple configuration items.

[0083] In an embodiment of the present disclosure, obtaining a target domain name creation template corresponding to the detection result includes: when the detection result shows that the service to be accessed supports access to the source server and does not carry an authentication access identifier, using the original domain name creation template as the target domain name creation template.

[0084] In the disclosed embodiment, if the detection result indicates that the service being accessed supports access to the origin server and does not carry an authentication access identifier, this indicates that the service being accessed does not require a signature when returning to the origin. In this case, the original domain name creation template can be directly used as the target domain name creation template. The original domain name creation template is as follows: {service type abbreviation}{CDN service provider identifier}{service provider product type abbreviation}-{service service key}-{service service key2}-{origin site address}.{secondary domain name}.

[0085] In an embodiment of the present disclosure, obtaining a target domain name creation template corresponding to the detection result includes: when the detection result is that the service to be accessed supports access to the source server and carries an authentication access identifier, using the authentication access identifier to generate signature information, and carrying the signature information in the original domain name creation template to obtain the target domain name creation template.

[0086] In the embodiment of the present disclosure, if the detection result shows that the service to be accessed supports access to the source server and carries an authentication access identifier, it means that the service to be accessed requires a signature when returning to the source. At this time, the authentication access identifier can be used directly to generate signature information, and the signature information can be carried in the original domain name creation template to obtain the domain name creation template: {service type abbreviation}{CDN service provider identifier}{service provider product type abbreviation}{business service key}-{business service key2}-sign-{source site address}.{secondary domain name}.

[0087] It should be noted that the business type abbreviation can be: p (for image business), v (for video business), etc. The service provider product type abbreviation can be used to distinguish the different product types of the service provider. For example, for service provider K, the general product type of this service provider can use the default value of empty. For example, the product type abbreviation of service provider J is "j". Business service key / key2 is the business information customized when applying for a domain name for the business, and sign indicates whether the accelerated domain name supports authenticated access. The source site address indicates the different back-to-source addresses that the CDN server needs to configure. For example, sg represents the standard image source site address of region A, p-9j-sg.xxxxxxx.com, etc., where 9 is the CDN service provider identifier of service provider J, and j is the service provider product type abbreviation of service provider J.

[0088] Step C3: Obtain the data content corresponding to each configuration item and write the data content into the target domain name creation template to obtain the target acceleration domain name.

[0089] In the disclosed embodiment, after obtaining the target domain name configuration template, the data content of configuration items such as {business type abbreviation}, {business service key}, and {business service key2} can be obtained from the business information. The data content of configuration items such as {CDN service provider identifier}, {service provider product type abbreviation}, and {origin site address} can be obtained from the preset configuration information of the target CDN server. The obtained data content is written into the target domain name creation template to obtain the target acceleration domain name.

[0090] In addition, non-authenticated acceleration domains (i.e., acceleration domains without a signature) under the same second-level domain name and placed in the same property share the cache by default. Authenticated acceleration domains (i.e., acceleration domains with a signature) under the same second-level domain name and placed in the same property share the cache by default. Authenticated and non-authenticated domains do not share the cache.

[0091] For example, for an unauthenticated image service using the SG standard origin server of service provider H, the acceleration domain name is: p16h-test-demo.test.com, where 16 is the CDN provider identifier of service provider H and h is the abbreviation of the service provider product type of service provider H.

[0092] It's important to note that to provide static domain caching, you can require that unauthenticated and authenticated domains under the same second-level domain be placed in separate properties. Initially, the CDN provider can create the first business second-level domain. The business side simply needs to determine whether a corresponding property exists. If so, place it in the property; otherwise, manually configure it. Later, automated creation of the first property will complete the closed loop.

[0093] The domain name creation method provided by the embodiment of the present disclosure realizes automatic domain name creation based on whether the business needs to configure authentication and the global distribution of the source station, and no longer needs to manually configure the domain name. At the same time, the timeliness of domain name creation is shortened from the original N days to minutes. Therefore, by providing a standardized accelerated domain name configuration template, not only the efficiency of domain name configuration is improved, but also the concretization of business domain names is realized, that is, the characteristics of the domain name can be known through the configuration items of the domain name, such as the source station address, CDN service provider, whether it has authentication, etc.

[0094] Step S23: Generate a back-to-origin request based on the target acceleration domain name and the target service provider identifier of the target CDN server, and send the back-to-origin request to the origin server.

[0095] In the disclosed embodiment, the target CDN server generates an access identifier based on the configured target acceleration domain name (x-cdn-host) and the target service provider identifier (x-cdn-vendor) of the target CDN server, adds the access identifier to the back-to-origin request, and sends it to the origin server. After receiving the back-to-origin request, the origin server extracts the target acceleration domain name and target service provider identifier from the back-to-origin request. The origin server then analyzes the target acceleration domain name and ultimately feeds the access identifier back to the CDN server.

[0096] Step S24: receiving the target access identifier fed back by the source server based on the back-to-source request, and using the target access identifier to obtain the target resource from the target source server.

[0097] In an embodiment of the present disclosure, obtaining a target resource from a target source station using a target access identifier includes the following steps: generating an access request based on the target access identifier; sending the access request to a source station cache so that the source station cache uses the target access identifier to determine a target access policy, and accessing the target source station according to the target access policy to obtain the target resource.

[0098] In the disclosed embodiment, after the target CDN server generates an access request based on the target access identifier, it first sends the access request to the source station cache. The source station cache uses the target access identifier to determine the resource type of the resource to be accessed, and determines the target access policy based on the resource type. For example, if the resource type is an external network public resource type, the target access policy can be direct access. Or if the resource type is a non-external network public resource type, the target access policy is to verify the target access identifier, and access is allowed after the verification is passed. Finally, the target source station is accessed according to the target access policy to obtain the target resource.

[0099] In the embodiment of the present disclosure, the process of verifying the target access identifier includes: the source station cache verifies the signature information in the target access identifier. After the signature information is verified, the source station cache re-signs the target access identifier according to the pre-negotiated signature algorithm and independent authentication parameters. At this time, the re-signed target access identifier is sent to the storage gateway. After the storage gateway verifies the signature, it finally determines that non-external network public resources can be accessed.

[0100] The method provided by the embodiment of the present disclosure utilizes the source site cache to further determine the resource type of the resource to be accessed by the target access identifier, thereby determining its final target access policy. If it is a non-external network public resource type, it needs to be re-signed and the signature verified to ensure the security of access.

[0101] FIG3 is a schematic diagram of a back-to-origin request processing process provided by an embodiment of the present disclosure. As shown in FIG3 , the process includes the following steps:

[0102] Step 1: The client sends a service request to the CDN server, wherein the service request carries the original access identifier of the service to be accessed by the client.

[0103] In step 2, the CDN server receives and responds to the service request, obtains the service information of the service to be accessed using the original access identifier, and generates a target acceleration domain name based on the service information and the preset configuration information corresponding to the target CDN server.

[0104] In step 3, the CDN server generates an access identifier based on the target acceleration domain name and the target service provider identifier of the target CDN server, adds the access identifier to the back-to-origin request, and sends it to the origin server.

[0105] In step 4, the origin server receives the back-to-origin request and extracts the access identifier that carries the target acceleration domain name and the target service provider identifier from the back-to-origin request.

[0106] Step 5: The origin server queries the target origin server corresponding to the target acceleration domain name and obtains the origin server configuration information corresponding to the target origin server.

[0107] In step 6, the origin server generates a target access identifier of the target origin based on the origin configuration information, and sends the target access identifier to the CDN server.

[0108] In step 7, the CDN server generates an access request based on the target access identifier; sends the access request to the origin cache, so that the origin cache uses the target access identifier to determine the target access policy, and accesses the target origin to obtain the target resource according to the target access policy.

[0109] Figure 4 is a block diagram of a device for processing a content distribution network back-to-source request provided by an embodiment of the present disclosure. The device can be implemented as part or all of an electronic device through software, hardware, or a combination of both. As shown in Figure 4, the device includes:

[0110] A first receiving module 41 is configured to receive a back-to-origin request carrying an access identifier, wherein the access identifier includes a target acceleration domain name and a target service provider identifier. The target acceleration domain name is generated by a target CDN server based on preset configuration information, and the target service provider identifier is the target service provider identifier of the target CDN server.

[0111] Query module 42, used to query the target origin server corresponding to the target acceleration domain name and obtain the origin server configuration information corresponding to the target origin server;

[0112] A first generating module 43 is configured to generate a target access identifier of a target source station based on the source station configuration information;

[0113] The sending module 44 is configured to send the target access identifier to the target CDN server corresponding to the target service provider identifier, wherein the target CDN server obtains the target resource from the target origin station according to the target access identifier.

[0114] In an embodiment of the present disclosure, the processing device for content distribution network back-to-source requests also includes: a detection module for detecting whether the target acceleration domain name carries signature information; if the target acceleration domain name carries signature information, determining that the target acceleration domain name supports authenticated access, and verifying the signature information to obtain a verification result.

[0115] In the embodiment of the present disclosure, the query module 42 is used to obtain the target scheduling rule matched by the target acceleration domain name when the verification result is passed, and use the source station indicated by the target scheduling rule as the target source station; read the source station configuration information corresponding to the target source station, wherein the source station configuration information includes: authentication algorithm, authentication parameters, source station address corresponding to the target source station, and return to the source host.

[0116] Figure 5 is a block diagram of a device for processing a content distribution network back-to-source request provided by an embodiment of the present disclosure. The device can be implemented as part or all of an electronic device through software, hardware, or a combination of both. As shown in Figure 5, the device includes:

[0117] The second receiving module 51 is configured to receive a service request from a client, wherein the service request carries an original access identifier of a service to be accessed by the client;

[0118] The response module 52 is configured to respond to the service request, obtain service information of the service to be accessed using the original access identifier, and generate a target acceleration domain name based on the service information and preset configuration information corresponding to the target CDN server;

[0119] The second generating module 53 is used to generate a back-to-origin request based on the target acceleration domain name and the target service provider identifier of the target CDN server, and send the back-to-origin request to the origin server;

[0120] The processing module 54 is configured to receive a target access identifier fed back by the origin server based on the back-to-origin request, and obtain target resources from the target origin server using the target access identifier.

[0121] In the embodiment of the present disclosure, the generation module 53 is used to use business information to detect whether the business to be accessed meets the domain name creation rules of the source station server to obtain a detection result; obtain a target domain name creation template corresponding to the detection result, wherein the target domain name creation template includes multiple configuration items; obtain the data content corresponding to each configuration item, and write the data content into the target domain name creation template to obtain the target acceleration domain name.

[0122] In the embodiment of the present disclosure, the generating module 53 is specifically configured to use the original domain name creation template as the target domain name creation template when the detection result shows that the service to be accessed supports access to the source server and does not carry the authentication access identifier;

[0123] The generation module 53 is specifically used to generate signature information using the authentication access identifier when the detection result shows that the service to be accessed supports access to the source server and carries the authentication access identifier, and carry the signature information to the original domain name creation template to obtain the target domain name creation template.

[0124] In an embodiment of the present disclosure, the processing module 54 is used to generate an access request based on the target access identifier; send the access request to the source station cache, so that the source station cache uses the target access identifier to determine the target access policy, and access the target source station according to the target access policy to obtain the target resource.

[0125] An embodiment of the present disclosure also provides an electronic device, as shown in Figure 6, which may include: a processor 1501, a communication interface 1502, a memory 1503 and a communication bus 1504, wherein the processor 1501, the communication interface 1502, and the memory 1503 communicate with each other through the communication bus 1504.

[0126] Memory 1503, used for storing computer programs;

[0127] The processor 1501 is configured to implement the steps of the above embodiment by executing the computer program stored in the memory 1503 .

[0128] The communication bus mentioned in the terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.

[0129] The communication interface is used for communication between the above terminal and other devices.

[0130] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage. Alternatively, the memory may be at least one storage device located away from the processor.

[0131] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

[0132] In another embodiment provided by the present disclosure, a non-transitory computer-readable storage medium is also provided, which stores instructions. When the computer-readable storage medium is executed, the computer executes the method for processing a content distribution network back-to-source request described in any of the above embodiments.

[0133] In another embodiment provided by the present disclosure, a computer program product including instructions is further provided. When the instructions are executed on a computer, the computer executes the method for processing a content distribution network back-to-origin request described in any of the above embodiments.

[0134] In another embodiment provided by the present disclosure, a computer program is further provided. When the computer is executed, the computer executes the method for processing a content distribution network back-to-origin request described in any of the above embodiments.

[0135] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present disclosure is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive).

[0136] The above description is only a preferred embodiment of the present disclosure and is not intended to limit the scope of protection of the present disclosure. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present disclosure are included in the scope of protection of the present disclosure.

[0137] The foregoing description is intended only to provide specific embodiments of the present disclosure, intended to enable those skilled in the art to understand and implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not to be limited to the embodiments shown herein, but is to be construed in the broadest manner consistent with the principles and novel features claimed herein.

Claims

1. A method for processing a content distribution network back-to-source request, wherein: The method is applied to an origin server, the origin server is in communication connection with a plurality of CDN servers, and the method comprises: Receive a back-to-source request carrying an access identifier, wherein the access identifier includes a target acceleration domain name and a target service provider identifier, the target acceleration domain name is generated by a target CDN server according to preset configuration information, and the target service provider identifier is a target service provider identifier of the target CDN server; Query the target source station corresponding to the target acceleration domain name, and obtain the source station configuration information corresponding to the target source station; Generate a target access identifier of the target source station based on the source station configuration information; The target access identifier is sent to a target CDN server corresponding to the target service provider identifier, wherein the target CDN server obtains the target resource from the target source station according to the target access identifier.

2. The method according to claim 1, wherein: Before querying the target source station corresponding to the target acceleration domain name, the method further includes: Detect whether the target acceleration domain name carries signature information; In the case where the target acceleration domain name carries the signature information, it is determined that the target acceleration domain name supports authentication access, and the signature information is verified to obtain a verification result.

3. The method according to claim 2, wherein: The querying of the target source station corresponding to the target acceleration domain name and obtaining the source station configuration information corresponding to the target source station includes: If the verification result is that the verification is passed, the target scheduling rule matched by the target acceleration domain name is obtained, and the source station indicated by the target scheduling rule is used as the target source station; Read the source station configuration information corresponding to the target source station, wherein the source station configuration information includes: an authentication algorithm, authentication parameters, a source station address corresponding to the target source station, and a back-to-source host.

4. A method for processing a content distribution network back-to-source request, wherein: The method is applied to a target CDN server, where the target CDN server is any server that is in communication connection with the source server, and the method includes: Receiving a service request from a client, wherein the service request carries an original access identifier of a service to be accessed by the client; In response to the service request, using the original access identifier to obtain service information of the service to be accessed, and generating a target acceleration domain name based on the service information and preset configuration information corresponding to the target CDN server; Generate a back-to-origin request based on the target acceleration domain name and the target service provider identifier of the target CDN server, and send the back-to-origin request to the origin server; Receive the target access identifier fed back by the source station server based on the back-to-source request, and use the target access identifier to obtain the target resource from the target source station.

5. The method according to claim 4, wherein: The generating a target acceleration domain name based on the business information and preset configuration information corresponding to the target CDN server includes: Using the service information, detecting whether the service to be accessed satisfies the domain name creation rule of the source server, and obtaining a detection result; Obtaining a target domain name creation template corresponding to the detection result, wherein the target domain name creation template includes multiple configuration items; The data content corresponding to each of the configuration items is obtained, and the data content is written into the target domain name creation template to obtain the target acceleration domain name.

6. The method according to claim 5, wherein: The step of obtaining a target domain name corresponding to the detection result and creating a template includes: When the detection result shows that the service to be accessed supports access to the source server and does not carry an authentication access identifier, the original domain name creation template is used as the target domain name creation template; When the detection result shows that the service to be accessed supports access to the source server and carries an authentication access identifier, signature information is generated using the authentication access identifier, and the signature information is carried in the original domain name creation template to obtain the target domain name creation template.

7. The method according to any one of claims 4 to 6, wherein: The acquiring the target resource from the target source station by using the target access identifier includes: generating an access request based on the target access identifier; The access request is sent to the source station cache, so that the source station cache uses the target access identifier to determine the target access policy, and accesses the target source station to obtain the target resource according to the target access policy.

8. A device for processing a content distribution network back-to-source request, comprising: A first receiving module is used to receive a back-to-source request carrying an access identifier, wherein the access identifier includes a target acceleration domain name and a target service provider identifier, the target acceleration domain name is generated by a target CDN server according to preset configuration information, and the target service provider identifier is a target service provider identifier of the target CDN server; A query module, used to query the target source station corresponding to the target acceleration domain name, and obtain the source station configuration information corresponding to the target source station; A first generating module, configured to generate a target access identifier of the target source station based on the source station configuration information; A sending module is used to send the target access identifier to the target CDN server corresponding to the target service provider identifier, wherein the target CDN server obtains the target resource from the target source station according to the target access identifier. source.

9. A device for processing a content distribution network back-to-source request, comprising: A second receiving module is used to receive a service request from a client, wherein the service request carries an original access identifier of a service to be accessed by the client; A response module, configured to respond to the service request, obtain service information of the service to be accessed using the original access identifier, and generate a target acceleration domain name based on the service information and preset configuration information corresponding to the target CDN server; A second generating module is used to generate a back-to-origin request based on the target acceleration domain name and the target service provider identifier of the target CDN server, and send the back-to-origin request to the origin server; The processing module is used to receive the target access identifier fed back by the source station server based on the back-to-source request, and use the target access identifier to obtain the target resource from the target source station.

10. A storage medium comprising a stored program, wherein: When the program is executed, the method according to any one of claims 1 to 7 is executed.

11. An electronic device comprising a processor, a communication interface, a memory and a communication bus, wherein: The processor, the communication interface, and the memory communicate with each other via a communication bus; wherein: Memory, used to store computer programs; A processor, configured to execute the method according to any one of claims 1 to 7 by running a program stored in a memory.

12. A computer program product comprising instructions, which, when executed on a computer, cause the computer to execute the method according to any one of claims 1 to 7.

13. A computer program, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 7.

Citation Information

Patent Citations

  • CDN (Content Delivery Network) system and network source returning method thereof

    CN107995314A

  • Access request processing method, edge server and storage medium

    CN115277809A

  • Resource acquisition method and device, equipment and storage medium

    CN115695580A

  • Content delivery network back-to-source request processing method and device, equipment and medium

    CN116527632A

  • Resource acquisition method and system based on block chain network, storage medium, and computer device

    WO2019196825A1