Service request scheduling method, electronic device, storage medium and program product

Abstract

The application discloses a service request scheduling method applied to a management system, and the method comprises the following steps: receiving a first service access request sent by a user end; the first service access request comprises a first domain name, and the first service access request is used for accessing a service resource corresponding to the first domain name in a content distribution network (PCDN) based on a peer-to-peer network; searching the service resource corresponding to the first domain name in the PCDN to obtain a search result; if the search result indicates that the service resource does not exist in the PCDN, converting the first domain name into a second domain name; the second domain name is supported to be identified by the PCDN and a content distribution network (CDN); sending the second domain name to the user end; and the second domain name is used for instructing the user end to send a second service access request to the CDN based on the second domain name.

Description

Technical Field

[0001] This application relates to the field of distribution network technology, and in particular to a service request scheduling method, electronic device, storage medium, and program product. Background Technology

[0002] In related technologies, in order to solve the problems of high server load and high bandwidth consumption faced by centralized content delivery networks (CNDs), content providers have introduced peer-to-peer content delivery networks (PCDNs) to address these issues. However, when users access PCDNs and encounter situations where resources are not found, ensuring the continuity of user services and retrieving resources from the origin CDN network from the PCDN network become problems that need to be solved. Summary of the Invention

[0003] In view of this, embodiments of this application provide a service request scheduling method, an electronic device, a storage medium, and a program product.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides a service request scheduling method and an application management system. The method includes: receiving a first service access request sent by a user terminal; the first service access request includes a first domain name, which is used to access service resources corresponding to the first domain name in a PCDN; retrieving the service resources corresponding to the first domain name in the PCDN to obtain a search result; if the search result indicates that the service resources do not exist in the PCDN, converting the first domain name to a second domain name; the second domain name is recognizable by the PCDN and CDN; and sending the second domain name to the user terminal, which instructs the user terminal to send a second service access request to the CDN based on the second domain name.

[0006] In the above scheme, converting the first domain name into the second domain name includes: adding a customized domain name to the first domain name to obtain the second domain name; the customized domain name is determined by the PCDN and the CDN through negotiation.

[0007] In the above scheme, retrieving the business resources corresponding to the first domain name in PCDN includes: filtering resource nodes containing the business resources from the PCDN based on the keywords corresponding to the business resources; the keywords represent the attributes and / or category tags of the business resources; filtering out resource nodes that do not conform to preset filtering rules from the resource nodes containing the business resources; the preset filtering rules include resource nodes being accessible and / or the business resources within the resource nodes being complete.

[0008] In the above scheme, before retrieving the business resources corresponding to the first domain name in the PCDN, the method further includes: verifying the identity information of the user terminal to obtain a verification result; if the verification result indicates that the user terminal does not have permission to access the business resources corresponding to the first domain name, the first business access request is rejected.

[0009] This application provides a service request scheduling method applied to a user terminal. The method includes: sending a first service access request to a management system; the first service access request includes a first domain name; the first service access request is used to access the service resource corresponding to the first domain name in the PCDN; obtaining a second domain name sent by the management system when it detects that the service resource corresponding to the first domain name does not exist in the PCDN; the second domain name is obtained by conversion based on the first domain name, and the first domain name supports being recognized by the PCDN and CDN; and sending a second service access request to the CDN based on the second domain name.

[0010] In the above scheme, after sending the second service access request to the CDN based on the second domain name, the method further includes: obtaining the domain name resolution result of the second domain name sent by the CDN; the domain name resolution result includes the Internet Protocol IP address of the target resource node in the CDN where the service resource exists; and obtaining the service resource from the target resource node based on the IP address.

[0011] This application also provides an electronic device, including: a processor and a memory for storing a computer program that can run on the processor, wherein the processor, when running the computer program, executes the steps of the method applied in the management system described above.

[0012] This application also provides an electronic device, including: a processor and a memory for storing a computer program that can run on the processor, wherein the processor, when running the computer program, executes the steps of the method applied to the user terminal in the above-described scheme.

[0013] This application also provides a computer storage medium storing a computer program, which, when executed by a processor, implements the steps of the method described above.

[0014] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of a business request scheduling method applied to a management system.

[0015] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of a service request scheduling method applied to a user terminal.

[0016] This application embodiment receives a first service access request sent by a user terminal. The first service access request includes a first domain name and is used to access the service resources corresponding to the first domain name in the PCDN. The service resources corresponding to the first domain name are searched in the PCDN to obtain search results. If the search results indicate that the service resources do not exist in the PCDN, the first domain name is converted into a second domain name, which can be recognized by both the PCDN and CDN. The second domain name is sent to the user terminal, instructing the user terminal to send a second service access request to the CDN based on the second domain name. This application solves the problem of retrieving service resources from the PCDN network to the origin CDN network when the required service resources do not exist in the PCDN, thus ensuring the continuity of user services. Attached Figure Description

[0017] Figure 1 A flowchart illustrating a service request scheduling method provided in an embodiment of this application;

[0018] Figure 2 A flowchart illustrating another service request scheduling method provided in this application embodiment;

[0019] Figure 3 A schematic diagram of the structure of a management system provided in an embodiment of this application;

[0020] Figure 4 A flowchart illustrating another service request scheduling method provided in this application embodiment;

[0021] Figure 5 This application provides a domain name conversion diagram as an embodiment.

[0022] Figure 6 This is another domain name conversion diagram provided in an embodiment of this application;

[0023] Figure 7 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0024] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0025] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

[0026] In traditional CDNs, content providers (such as websites and video platforms) store and distribute content by establishing distributed server nodes around the world. Users obtain content by communicating with the nearest server node, improving access speed and reliability. However, this centralized CDN model can face problems such as high server load and high bandwidth consumption, especially under large-scale user access, where these problems become increasingly severe.

[0027] PCDN addresses these issues by introducing peer-to-peer (P2P) networking technology. It incorporates end-user devices (such as computers and smartphones) into the distribution network, making them content distribution sources and relay nodes. When a user requests a resource, the PCDN system attempts to obtain the resource from other user devices with the same resource, rather than directly from a centralized server node.

[0028] In summary, PCDN integrates user devices into the content delivery network, providing efficient content delivery through resource sharing and collaboration among nodes. It reduces the load on centralized servers, improves resource access speed and availability, and better accommodates the demands of large-scale user access and popular content.

[0029] In related technologies, content providers have introduced PCDN to address the problems of high server load and large bandwidth consumption faced by centralized CDN. However, when users access the PCDN network, if they encounter a situation where the PCDN network does not hit a resource, how to ensure the continuity of user services and how to retrieve resources from the PCDN network back to the origin CDN network become problems that need to be solved.

[0030] One approach involves using a PCDN node proxy query during the origin pull process. This involves querying another PCDN node through a routing service node to obtain the target slice file. However, this method is only one way to obtain the target slice file and limits the service node to other PCDN nodes within the PCDN network. It fails to adequately consider how to ensure business continuity and establish origin pull mechanisms and methods when the target slice file is unavailable in the PCDN network.

[0031] In another approach, the client sends a resource scheduling request to the converged network resource scheduling system. The system then identifies the resources to be scheduled within the network service system and, based on resource access quality analysis, determines the network service system type and the resources to be scheduled in response to the client. The client then obtains the access result based on the resource information in the response message. This approach provides a method for the scheduling system to determine network and resource selection, but it does not provide a method for selecting and deciding on the network service system when there is no resource content in the PCDN network. Furthermore, the network service system corresponding to the open PCDN only provides a method for pulling resources to be scheduled from the CDN via HTTP, limiting the supported methods.

[0032] In another approach, a first-link coordination plugin and a second-link coordination plugin are deployed on the PCDN and CDN service nodes to establish two links between the user end and the PCDN and CDN service nodes. The user's business requests are accessed through a first sub-stream constructed by the first-link coordination plugin. If poor service quality occurs during this access, data transmission in the second link is achieved through message exchange between the first and second-link coordination plugins. This provides a user-end data flow guarantee mechanism, enabling real-time switching to the second link for data transmission when the service quality of the PCDN service node falls below the guarantee requirements. However, the simultaneous establishment of the first and second links increases the complexity of system interaction, places high demands on the real-time concurrency capabilities and resource consumption of the terminal and system, and has limited effectiveness in guaranteeing service quality.

[0033] To address the shortcomings of the aforementioned related technologies, this invention provides a service request scheduling method that can retrieve resources from the origin CDN network when resources are not found in the PCDN network. To illustrate the technical solution described in this invention, specific embodiments are provided below.

[0034] Figure 1 This is a flowchart illustrating a service request scheduling method provided in an embodiment of this application, as shown below. Figure 1 As shown, this method is applied to a management system and includes steps 101 to 104, wherein:

[0035] Step 101: Receive a first service access request sent by the user terminal; the first service access request includes a first domain name, and the first service access request is used to access the service resources corresponding to the first domain name in PCDN.

[0036] In some embodiments, when a user needs to obtain resources from the network, they can obtain them from PCDN, especially some popular resources. Based on the P2P sharing mode, the more users downloading resources at the same time, the faster the resource download speed will be. Moreover, obtaining resources through PCDN can greatly reduce the service pressure of CDN. Based on this, in this embodiment of the application, resources can be obtained from PCDN first, that is, the business access request is sent to PCDN.

[0037] In some embodiments, the management system may be a PCDN system, network management system, controller, data analysis system, operation and maintenance platform, or other systems or components with management and control functions, while the user terminal may be an electronic device such as a mobile phone, computer, or tablet computer. The first service access request sent by the user terminal may be an access request initiated by the user or an access request automatically initiated by an application in the electronic device when the user is performing other operations. Specifically, the first service access request may also include the user terminal's IP address, request time, number of requests, and identity information.

[0038] In some embodiments, the first domain name is the original domain name in the first service access request sent by the user terminal, and the first service access request is used to access the service resources corresponding to the first domain name in PCDN.

[0039] Step 102: Retrieve the business resources corresponding to the first domain name in the PCDN to obtain the retrieval results.

[0040] In some embodiments, the management system may first identify the business resources corresponding to the first domain name, specifically including identifying the content attributes such as the name, type, tags, and description of the business resources, and then search and filter them from PCDN based on these content attributes to obtain search results.

[0041] In some embodiments, the management system can manage existing resources on the PCDN, including but not limited to setting attributes such as the resource's region, name, type, tag, description, etc., to provide different resource classification and filtering options, so as to quickly filter the business resources requested by the user.

[0042] In some embodiments, the requested business resources can also be retrieved by searching the metadata of business resources in the PCDN. Specifically, metadata can be used to indicate the storage location, historical data, resource search, file records, and other functions of the resources. The metadata can be used as a directory of resources in the PCDN, and the requested business resources can be found based on the resource directory. At the same time, the metadata can also be used to determine the background information of the resource's content, instructions, status, and other relevant characteristics. Further searches can be performed based on this feature to verify the availability and integrity of the resources, filter out incomplete or unavailable resources, and improve the reliability of the resources provided to users.

[0043] Step 103: If the search result indicates that the business resource does not exist in the PCDN, the first domain name is converted into a second domain name; the second domain name can be recognized by the PCDN and CDN.

[0044] In some embodiments, the search results may indicate whether the requested service resource exists in the PCDN, or whether there are available nodes in the PCDN to provide the requested service resource. Here, an available node may mean that the node is accessible and / or that the service resource in the node is fully accessible. When the search results indicate that the requested service resource does not exist in the PCDN, it may mean that none of the nodes in the PCDN contain the requested service resource, or that the nodes containing the service resource are inaccessible or the service resource is incomplete.

[0045] In some embodiments, when a user cannot obtain the requested service resource from PCDN, it needs to retrieve the service resource from CDN. This requires converting the first domain name in the first service access request sent by the user into a second domain name that can be recognized by both PCDN and CDN, ensuring the user can continue to access the service resource and guaranteeing the continuity of service access. Converting the first domain name to the second domain name can involve changing the format, content, or other aspects of the domain name so that both CDN and PCDN can recognize the converted domain name. For example, if the first domain name is http(s): / / xyz*.cmmobile.com / uri, and the corresponding service resource is not found in PCDN, the domain name needs to be converted. This conversion supports both Hypertext Transfer Protocol (HTTP) and Hypertext Transfer Protocol Secure (HTTPS) requests. A custom domain name, such as pcdn.cmmobile.com, is added to the first domain name to obtain the second domain name http(s): / / pcdn.cmmobile.com / xyz*.cmmobile.com / uri.

[0046] In some embodiments, when the first domain name http(s): / / xyz*.cmmobile.com / uri is converted to http(s): / / IP / xyz*.cmmobile.com / uri, the user terminal selects the PCDN network, which provides services and accesses the terminal cache node in the PCDN to obtain resources. Alternatively, when the first domain name is converted to http(s): / / pcdn.cmmobile.com / xyz*.cmmobile.com / uri, the user terminal accesses the CDN network, which provides services and accesses the edge node in the CDN network to restore the domain name and obtain resources.

[0047] It should be noted that if the first domain name is not converted, the CDN will not be able to recognize the first domain name, making it difficult to obtain resources from the CDN based on the first domain name.

[0048] Step 104: Send the second domain name to the user terminal; the second domain name is used to instruct the user terminal to send a second service access request to the CDN based on the second domain name.

[0049] In some embodiments, after the domain name conversion is completed, the converted second domain name needs to be sent to the user terminal, which then initiates a service access request to the CDN based on the second domain name, i.e., the second service access request. The composition type of the content in the second service access request can be the same as that in the first service access request, and the domain name included in the second service access request is the second domain name.

[0050] In some embodiments, a second domain name and search results may be sent to the user simultaneously to inform the user that the requested service resources cannot be obtained in the PCDN. The user may then send a second service access request to the CDN to obtain the requested service resources.

[0051] This application embodiment receives a first service access request sent by a user terminal. The first service access request includes a first domain name and is used to access the service resources corresponding to the first domain name in the PCDN. The service resources corresponding to the first domain name are searched in the PCDN to obtain search results. If the search results indicate that the service resources do not exist in the PCDN, the first domain name is converted into a second domain name, which can be recognized by both the PCDN and CDN. The second domain name is sent to the user terminal, instructing the user terminal to send a second service access request to the CDN based on the second domain name. This application solves the problem of retrieving service resources from the PCDN network to the origin CDN network when the required service resources do not exist in the PCDN, thus ensuring the continuity of user services.

[0052] In some embodiments, converting the first domain name to the second domain name includes:

[0053] A custom domain name is added to the first domain name to obtain the second domain name; the custom domain name is determined by the PCDN and the CDN through negotiation.

[0054] In some embodiments, a first domain name can be converted to a second domain name by adding a custom domain name to the first domain name. For example, if the first domain name is http(s): / / xyz*.cmmobile.com / uri, the converted second domain name is http(s): / / pcdn.cmmobile.com / xyz*.cmmobile.com / uri, where pcdn.cmmobile.com is the added custom domain name. This domain name is determined through negotiation between PCDN and CDN, and is recognized by both. After the second domain name is received and recognized by CDN or PCDN, it can be restored to the first domain name to determine the business resources corresponding to the first domain name.

[0055] In some embodiments, the generated second domain name can be stored, and when another user requests the service resource again, the corresponding second domain name can be directly called to return to the user.

[0056] Based on the above embodiments, by converting the first domain name in the first service access request sent by the user terminal, a second domain name that can be recognized and restored by both CDN and PCDN is obtained. In the case that the service resources required by the user do not exist in PCDN, the service resources can be obtained from the origin CDN network from the PCDN network, thus ensuring the continuity of user services.

[0057] In some embodiments, retrieving the business resources corresponding to the first domain name in the PCDN includes:

[0058] Based on the keywords corresponding to the business resources, resource nodes containing the business resources are filtered from the PCDN; the keywords represent the attributes and / or category tags of the business resources.

[0059] Remove resource nodes that do not meet the preset filtering rules from the resource nodes that contain the business resources; the preset filtering rules include whether the resource node is accessible and / or whether the business resources within the resource node are complete.

[0060] In some embodiments, resource nodes containing the requested service resource can be filtered from the PCDN using keywords of the service resource requested by the user. Specifically, when storing resources in the PCDN, resources are classified according to attributes and labeled with corresponding tags or identifiers. The management system can identify the service resource requested by the user, obtain the corresponding category or tag, and match it in the PCDN to filter out the service resources in the PCDN that are requested by the user.

[0061] In some embodiments, after filtering out some resource nodes that have business resources requested by users, an availability check is performed on these resource nodes. Specifically, the filtering can be based on preset filtering rules, including filtering out inaccessible resource nodes, resource nodes with insufficient resource availability, and resource nodes with incomplete resources.

[0062] Based on the above embodiments, by filtering resource nodes in PCDN, it can be ensured that the resources obtained by the user are reliable and valid when the requested business resources exist in the resource nodes.

[0063] In some embodiments, before retrieving the business resources corresponding to the first domain name in the PCDN, the method further includes:

[0064] The user's identity information is verified to obtain the verification result;

[0065] If the verification result indicates that the user does not have permission to access the business resources corresponding to the first domain name, the first business access request is rejected.

[0066] In some embodiments, the management system may also verify the user's identity before responding to the user's business access request. Specifically, it may verify the user's identity information such as the user's identity identifier and access permissions, and reject the user's business access request if the user does not have the permission to access the corresponding resource.

[0067] In some embodiments, the user's historical access requests can also be recorded to form an access record for that user. Based on the access record, the user's access behavior can be monitored and analyzed to determine whether the user's access behavior is abnormal. If an abnormality is detected, the user's access action can be stopped.

[0068] Based on the above embodiments, by verifying the identity information of the user terminal that issues the service request, the data security of CDN and PCDN is protected, and malicious access behavior and attacks are avoided.

[0069] Figure 2 This is a flowchart illustrating a service request scheduling method provided in an embodiment of this application, as shown below. Figure 2 As shown, this method is applied to the user terminal and includes steps 201 to 203, wherein:

[0070] Step 201: Send a first service access request to the management system; the first service access request includes a first domain name; the first service access request is used to access the service resources corresponding to the first domain name in the PCDN.

[0071] In some embodiments, when a user needs to access certain resources or requires corresponding resource support during an operation, the user sends a first business access request to the management system. The first business access request includes a first domain name and may also include the user's identity information, access time, number of accesses, etc. Preferably, the first business access request can be used to access the business resources corresponding to the first domain name in the PCDN.

[0072] Step 202: Obtain the second domain name sent by the management system when it detects that the business resource corresponding to the first domain name does not exist in the PCDN; the second domain name is obtained based on the conversion of the first domain name, and the first domain name can be recognized by the PCDN and CDN.

[0073] In some embodiments, when the requested service resource does not exist in the PCDN, the client will receive a second domain name returned by the management system. The client can then initiate another service access request based on the second domain name, which can be recognized by both the PCDN and CDN.

[0074] In some embodiments, the client may also receive a search result sent by the management system, indicating that the requested service resource does not exist in the PCDN. In this case, the client may temporarily stop sending service requests to the PCDN.

[0075] In some embodiments, when multiple clients simultaneously request the same resource from the CDN, the client that obtains the resource first can share the resource with other clients. In this case, other clients can obtain the requested resource from the PCDN through the second domain name.

[0076] Based on the above embodiments, when the resource requested by the user does not exist in the PCDN, the user will receive a second domain name issued by the management system. Since the second domain name can be recognized by the CDN and PCDN, the user is allowed to re-initiate the service access request and obtain the resource through the PCDN and / or CDN.

[0077] Step 203: Send a second service access request to the CDN based on the second domain name.

[0078] In some embodiments, after obtaining the second domain name, the user terminal generates a second service access request based on the second domain name, sends the second service access request to the CDN, and retrieves service resources from the PCDN network back to the origin CDN network, thus ensuring the continuity of user services.

[0079] In some embodiments, after the PCDN obtains the resource requested by the user through origin pull, the user can also send a second service request to the PCDN to obtain the service resource. It should be noted that when both the PCDN and CDN can provide the resource requested by the user, the service access request sent by the user can be directed to a resource node with better service quality based on a converged CDN scheduling strategy.

[0080] Based on the above embodiments, when the requested service resources are not available in the PCDN, the user will receive a second domain name that can be recognized by both the PCDN and CDN. The user can then send a second service request based on the second domain name to obtain service resources from the CDN. This solves the problem of obtaining service resources from the PCDN network back to the CDN network when the required service resources are not available in the PCDN, thus ensuring the continuity of user services.

[0081] Figure 3 A schematic diagram of the structure of a management system provided in an embodiment of this application is shown below. Figure 3 As shown, the management system includes:

[0082] The PCDN converged scheduling and control component mainly consists of four parts: a service access processing module, a content resource retrieval module, a scheduling policy management module, and a domain name conversion processing module. As a functional component of the management system, this component needs to interact with the PCDN network resource management system and network elements in the CDN system to collaboratively complete the optimization of the entire service's seamless integration and converged scheduling.

[0083] The PCDN network resource management system is used to maintain the PCDN node topology and PCDN node status.

[0084] The PCDN converged scheduling and control component includes:

[0085] The Business Access Control module is used for authenticating and verifying user requests. It verifies user identity information, ensuring that only authorized users can access resources and services in the PCDN or CDN system. By verifying user identity, this module determines whether the user has the necessary permissions. It controls access to user business access requests. Based on the user's identity and permission level, it determines whether the user is authorized to access specific resources or perform specific operations. Through fine-grained access control, it ensures that only authorized users can access specific content or perform specific operations. The Business Access Control module is responsible for implementing the system's security policies. It can perform security filtering and inspection of user requests to prevent malicious access and attacks. This module can detect and block potential security threats, protecting the data security of the PCDN and CDN systems and user terminals. When receiving user business access requests, the Business Access Control module is responsible for recording relevant request information and performing auditing and logging. This facilitates subsequent system management and troubleshooting, and also helps in monitoring and analyzing user behavior.

[0086] The Content Resource Retrieval Module is used to retrieve content resources from the PCDN Network Resource Management System through an interface with the PCDN system to obtain available content resource information. This module is responsible for retrieving metadata about content resources within the PCDN system. By setting attributes such as resource ownership region, name, type, tags, and description, the module provides different resource classification and filtering options, enabling users to more accurately find the resources they need and offering efficient resource search and retrieval functions. During content resource retrieval, the PCDN Network Resource Management System performs a resource availability check. This check verifies whether the node or server hosting the resource is accessible, as well as the resource's availability and integrity. The availability check filters out unavailable or incomplete resources, ensuring that the resources retrieved by the Content Resource Retrieval Module are reliable and valid.

[0087] The scheduling policy management module provides scheduling policy management functions. For different services carried by the PCDN network, the scheduling control management module supports various basic scheduling policies, including those based on user IP address ranges, geographical proximity, content distribution, Quality of Service (QoS), Communication Provider (CP) level, and node health. It also supports composite scheduling policies formed by combining multiple basic scheduling policies to schedule services to different levels of service nodes.

[0088] Domain Name Conversion Processing Module: This module performs domain name conversion operations within the PCDN converged scheduling control module. Its main function is to convert the domain name during service connection between the PCDN and CDN networks under converged scheduling. It translates the network connection (uniform resource location, URL) address carried in user service requests so that both the PCDN and CDN networks can jointly identify the converted URL address and perform resource scheduling and access operations based on it.

[0089] Specifically, the above module can achieve the following steps:

[0090] 1. Receiving User Business Requests: The domain name conversion processing module receives user business requests from the business access control module. These requests contain the URL address that needs to be accessed.

[0091] 2. System Content Resource Retrieval: Based on the content resource scheduling policy set in the scheduling policy management module, the content resource retrieval module searches for resource information in the PCDN to determine whether the requested resource information exists in the network.

[0092] 3. Customized Domain Name Conversion: When no content resources are found in PCDN, the domain name portion of the URL is converted according to the pre-defined domain name conversion rules of the domain name conversion processing module. This involves negotiation with PCDN and CDN to determine the result of the domain name conversion.

[0093] 4. Business Resource Scheduling: The converted URL address is used for PCDN converged scheduling to enable users to access and obtain requested resources. This solves key issues such as optimal edge node selection, URL address restoration, and content resource retrieval when resources are retrieved from the origin CDN network after a PCDN network miss.

[0094] Figure 4 This is a flowchart illustrating a service request scheduling method provided in an embodiment of this application.

[0095] Here, we take the user's requested business domain name as xyz*.cmmobile.com as an example. The shared origin CDN domain name negotiated between PCDN and CDN is pcdn.cmmobile.com. This shared origin CDN domain name must have CDN network distribution capabilities, such as... Figure 4 As shown.

[0096] 1. The user initiates access to the original business domain name.

[0097] The user initiates access to the business domain xyz*.cmmobile.com.

[0098] 2. Search for content resource information to determine whether the resource in the PCDN network is matched.

[0099] The service access control module in the PCDN converged scheduling and control component forwards service domain name access requests to the content resource retrieval module. The content resource retrieval module then uses the scheduling policy configured in the scheduling policy management module of the PCDN system to retrieve content resource information and determine whether the resource in the PCDN network is matched.

[0100] 3. PCDN network access failed to reach the resource.

[0101] After performing content retrieval based on the scheduling strategy, it was determined that the PCDN network did not hit the access resource.

[0102] 4. If the accessed resource is not found, forward it to the address translation processing module for processing.

[0103] The content resource retrieval module forwards the business domain name xyz*.cmmobile.com accessed by the user to the domain name conversion processing module, along with the resource retrieval results within the PCDN system, i.e., the resource information corresponding to the user's business access domain name that was not found in the PCDN network.

[0104] 5. The address conversion processing module converts the original business domain name and adds a customized domain name.

[0105] The domain name conversion processing module converts the business domain name based on the received access business domain name information and the PCDN system search results. It supports the conversion of HTTP / HTTPS request domain names, and can convert the user's request http(s): / / xyz*.cmmobile.com / uri message into http(s): / / pcdn.cmmobile.cmmobile.com / xyz*.cmmobile.com / uri.

[0106] 6. Redirect the response to the new business domain after conversion.

[0107] Respond to the user's request for a business domain name and return the converted domain name http(s): / / pcdn.cmmobile.com / xyz*.cmmobile.com / uri to the requesting user via redirection.

[0108] 7. Initiate a Domain Name System (DNS) request using the new domain name.

[0109] The user re-initiates a DNS request based on the new domain name information. Since the pcdn.cmmobile.com domain name has already been configured for service acceleration in the CDN network, the DNS queries the CDN network's scheduling center via the domain name. The CDN network's scheduling center then uses the domain name, IP address, and other information to find the most suitable CDN edge node IP address to provide the service and responds with the resolution result to the requesting user. This demonstrates the advantages of domain name conversion, solving both the problem of simultaneously supporting HTTP and HTTPS business requests and scheduling origin pulls, and also resolving the issue of reselecting the optimal CDN edge node through DNS resolution when pulling back to the origin CDN network. This is more advantageous than adding an IP address to the business domain name requested by the user, because adding an IP address is not suitable for HTTPS redirection and can only select a fixed CDN edge node to provide service during the process of scheduling back to the origin CDN from PCDN.

[0110] 8. Initiate a request to access the domain name resources of the new business.

[0111] Based on the IP address resolved from the pcdn.cmmobile.com domain, the user sends an HTTP(s): / / pcdn.cmmobile.com / xyz*.cmmobile.com / uri service request to the CDN edge node, initiating a service resource access request.

[0112] 9. The new business domain name is restored to the original business domain name.

[0113] The CDN edge node receives the business domain name request message http(s): / / pcdn.cmmobile.com / xyz*.cmmobile.com / uri, and removes the negotiated shared origin CDN domain name information pcdn.cmmobile.com carried in the business domain name request message. The CDN edge node then searches to see if the content resource requested by http(s): / / xyz*.cmmobile.com / uri is matched.

[0114] 10. If the target domain is not found, the business resources will be obtained from the CDN content center using the restored original business domain.

[0115] If the CDN edge node does not match the user's business domain name request content, it will initiate a content resource request to the CDN content center. When making the request, it will use the business domain name http(s): / / xyz*.cmmobile.com / uri after deleting the negotiated shared origin CDN domain name information to request the CDN content center.

[0116] 11. The CDN content center completes resource acquisition.

[0117] The CDN content center is responsible for performing operations such as content querying, retrieval, response, and returning to the original content site.

[0118] 12. Business resources that respond to user requests.

[0119] The CDN content center responds to user requests for content resources from CDN edge nodes.

[0120] 13. Return the requested business resources to the user.

[0121] CDN edge nodes return the content resource information requested by the user to the user's client.

[0122] In some embodiments, domain name conversion is performed on unsuccessful resource requests. The converted new domain name can be processed and restored by both the PCDN network and the CDN network. The newly generated business domain name guides the user to select the final access network. Figure 5 This application provides a domain name conversion illustration, such as... Figure 5 As shown, when the business domain name requested by the user, http(s): / / xyz*.cmmobile.com / uri, is converted to http(s): / / IP / xyz*.cmmobile.com / uri, the user terminal selects the PCDN network, which provides services and accesses the PCDN system's terminal cache node to obtain resources. Figure 6 This application provides a domain name conversion illustration, such as... Figure 6 As shown, when the uri is converted from http(s): / / xyz*.cmmobile.com / uri to http(s): / / pcdn.cmmobile.com / xyz*.cmmobile.com / uri, the user accesses the CDN network, which provides services, accesses the edge nodes in the CDN network to restore the domain name, and obtains resources.

[0123] Based on the above embodiments, a content resource fusion scheduling component based on the PCDN network processes user service requests and, according to resource retrieval in the PCDN network, converts the requested service domain name according to the shared origin domain name format agreed upon by the PCDN and CDN networks. By adding the agreed shared origin domain name information to the original service domain name of the user request, the problem of content resource traffic continuing in the CDN network when there are no resources hit in the PCDN network can be solved. Simultaneously, during the service process, it solves the problems of not being able to change the domain name to the IP address in HTTPS origin requests, restoring the domain name address for new service domain name requests, and dynamically selecting the optimal CDN edge node during the origin CDN process.

[0124] This application also provides a service request scheduling device for use in a management system. This device corresponds to the service request scheduling method described above, and the steps in the service request scheduling method embodiment are also fully applicable to this device embodiment.

[0125] The device includes:

[0126] The first receiving module is used to receive a first service access request sent by the user terminal; the first service access request includes a first domain name, and the first service access request is used to access the service resources corresponding to the first domain name in PCDN.

[0127] The first processing module is used to retrieve the business resources corresponding to the first domain name in the PCDN and obtain the retrieval results.

[0128] The first processing module is further configured to convert the first domain name into a second domain name if the search result indicates that the business resource does not exist in the PCDN; the second domain name is supported by the PCDN and CDN.

[0129] The first sending module is used to send the second domain name to the user terminal; the second domain name is used to instruct the user terminal to send a second service access request to the CDN based on the second domain name.

[0130] The first processing module is further configured to add a custom domain name to the first domain name to obtain the second domain name; the custom domain name is determined by the PCDN and the CDN through negotiation.

[0131] The first processing module is further configured to filter out resource nodes containing the business resource from the PCDN based on the keywords corresponding to the business resource; the keywords represent the attributes and / or category tags of the business resource; and filter out resource nodes that do not conform to preset filtering rules from the resource nodes containing the business resource; the preset filtering rules include resource nodes being accessible and / or the business resources within the resource nodes being complete.

[0132] The device further includes a verification module, used to verify the identity information of the user terminal and obtain a verification result; if the verification result indicates that the user terminal does not have permission to access the business resources corresponding to the first domain name, the first business access request is rejected.

[0133] This application also provides a service request scheduling device for use on a user terminal. This device corresponds to the service request scheduling method described above, and the steps in the service request scheduling method embodiment are also fully applicable to this device embodiment.

[0134] The device includes:

[0135] The second sending module is used to send a first service access request to the management system; the first service access request includes a first domain name; the first service access request is used to access the service resources corresponding to the first domain name in the PCDN.

[0136] The second receiving module is used to obtain the second domain name sent by the management system when it detects that the business resource corresponding to the first domain name does not exist in the PCDN; the second domain name is obtained by conversion based on the first domain name, and the first domain name can be recognized by the PCDN and CDN.

[0137] The second sending module is also used to send a second service access request to the CDN based on the second domain name.

[0138] The second receiving module is further configured to obtain the domain name resolution result of the second domain name sent by the CDN; the domain name resolution result includes the IP address of the target resource node in the CDN where the service resource exists; and obtain the service resource from the target resource node based on the IP address.

[0139] In practical applications, the aforementioned first receiving module, first sending module, first processing module, and verification module can be implemented by a processor in a service request scheduling device used in a management system. Similarly, the aforementioned second receiving module and second sending module can be implemented by a processor in a service request scheduling device used in a user terminal. Of course, the processor needs to run a computer program stored in memory to perform its functions.

[0140] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the apparatus can be divided into different program modules to complete all or part of the processing described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and will not be described again here.

[0141] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiments of this application, the embodiments of this application also provide an electronic device. Figure 7 This is a schematic diagram of the hardware composition structure of an electronic device provided in an embodiment of this application, such as... Figure 7 As shown, the electronic device includes:

[0142] The communication interface 701 enables information exchange with other devices, such as network devices.

[0143] The processor 702 is connected to the communication interface 701 to enable information interaction with other devices and to execute the methods provided by one or more of the above-mentioned technical solutions when running a computer program. The computer program is stored in the memory 703.

[0144] Of course, in practical applications, the various components in an electronic device are coupled together through a bus system 704. It can be understood that the bus system 704 is used to realize the connection and communication between these components. In addition to the data bus, the bus system also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, in... Figure 7 The general designated all buses as Bus System 704.

[0145] The memory 703 in this embodiment is used to store various types of data to support the operation of the computer device. Examples of such data include any computer program used to operate on the electronic device.

[0146] It is understood that memory 703 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0147] The methods disclosed in the embodiments of this application can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in memory. The processor reads the program from the memory and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0148] Optionally, when the processor 702 executes the program, it implements the corresponding processes implemented by the computer device in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0149] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a first memory storing a computer program, which can be executed by a processor of a computer device to complete the steps described in the aforementioned method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0150] In the several embodiments provided in this application, it should be understood that the disclosed apparatus, computer devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components may be combined, or integrated into another system, or some features may be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0151] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0152] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0153] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0154] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0155] In an exemplary embodiment, this application also provides a computer program product, including a computer program that can be executed by a processor 702 of an electronic device to complete the steps described in the business request scheduling method applied to a management system according to this application embodiment.

[0156] In an exemplary embodiment, this application also provides a computer program product, including a computer program that can be executed by a processor 702 of an electronic device to complete the steps described in the service request scheduling method applied to a user terminal according to the embodiments of this application.

[0157] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0158] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0159] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A business request scheduling method, applied to a management system, characterized in that, The method includes: Receive a first service access request sent by the user terminal; the first service access request includes a first domain name, and the first service access request is used to access the service resources corresponding to the first domain name in the content delivery network PCDN based on a peer-to-peer network; Retrieve the business resources corresponding to the first domain name in the PCDN to obtain the retrieval results; If the search results indicate that the service resource does not exist in the PCDN, the first domain name is converted to the second domain name; the second domain name can be recognized by the PCDN and the content delivery network CDN. The second domain name is sent to the user terminal; the second domain name is used to instruct the user terminal to send a second service access request to the CDN based on the second domain name. The step of converting the first domain name to the second domain name includes: A custom domain name is added to the first domain name to obtain the second domain name; the custom domain name is determined by the PCDN and the CDN through negotiation.

2. The method according to claim 1, characterized in that, The step of retrieving the business resources corresponding to the first domain name in PCDN includes: Based on the keywords corresponding to the business resources, resource nodes containing the business resources are filtered from the PCDN; the keywords represent the attributes and / or category tags of the business resources. Remove resource nodes that do not meet the preset filtering rules from the resource nodes that contain the business resources; the preset filtering rules include whether the resource node is accessible and / or whether the business resources within the resource node are complete.

3. The method according to claim 1, characterized in that, Before retrieving the business resources corresponding to the first domain name in the PCDN, the method further includes: The user's identity information is verified to obtain the verification result; If the verification result indicates that the user does not have permission to access the business resources corresponding to the first domain name, the first business access request is rejected.

4. A service request scheduling method, applied to the user end, characterized in that, The method includes: A first service access request is sent to the management system; the first service access request includes a first domain name; the first service access request is used to access the service resources corresponding to the first domain name in the PCDN. The system obtains a second domain name sent when it detects that the business resource corresponding to the first domain name does not exist in the PCDN; the second domain name is obtained by the system adding a customized domain name conversion determined by the PCDN and CDN to the first domain name, and the second domain name can be recognized by the PCDN and the CDN; A second service access request is sent to the CDN based on the second domain name.

5. The method according to claim 4, characterized in that, After sending the second service access request to the CDN based on the second domain name, the method further includes: Obtain the domain name resolution result of the second domain name sent by the CDN; the domain name resolution result includes the Internet Protocol IP address of the target resource node in the CDN where the business resource exists; Based on the IP address, the service resources are obtained from the target resource node.

6. An electronic device, characterized in that, include: A processor and memory for storing computer programs that can run on the processor, wherein, The processor, when running a computer program, performs the steps of the method according to any one of claims 1 to 3, or the steps of the method according to any one of claims 4 to 5.

7. A computer storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

8. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 3.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 4 to 5.

Images