PCDN service method, device, system and equipment

Abstract

The invention relates to the technical field of computer networks, and provides a PCDN service method, device, system and equipment, and the method comprises the steps: responding to a target resource application request sent by a client through a PCDN repeater when the client meets a specific service scene demand, querying a target PCDN terminal node where a target resource is located, and sending the target resource to the client through the PCDN repeater; and after the target resource downloading request is sent to the target PCDN terminal node, the target resource is acquired. According to the PCDN service method provided by the invention, under the limitation of a special service scene, the PCDN relay is newly added as a middle layer for directly serving with the client, the client request is scheduled to the PCDN relay for serving, the PCDN relay applies for target resource downloading from the PCDN terminal node, and the downloaded target resource is provided for the client, so that the service efficiency of the client is improved. The coverage range of the PCDN service is effectively expanded, and the resource acquisition efficiency and stability of the client in a complex network environment are improved.

Description

Technical Field

[0001] This application relates to the field of computer network technology, and in particular to a PCDN service method, apparatus, system and equipment. Background Technology

[0002] Bandwidth costs constitute a significant portion of expenses for internet companies, especially video-based companies. To save bandwidth and reduce investment, some internet companies have begun using a combination of Content Delivery Network (CDN) and Peer-to-Peer Network (P2P) for service distribution, specifically the Peer-to-Peer Content Delivery Network (PCDN) model. The PCDN service involves embedding software on home terminals, transforming them into content distribution nodes that provide content distribution services to external parties, achieving peer-to-peer content distribution. When a terminal node does not have the requested content, it then requests content from the CDN.

[0003] However, PCDN's server is a terminal node, which is often deployed on the user's home side. The number of terminals is huge, the Internet Protocol (IP) addresses are not fixed, the service range is limited, and it cannot directly provide services to clients with special service needs. Summary of the Invention

[0004] This application provides a PCDN service method, apparatus, system, and device to solve the problem in the prior art that PCDN terminal nodes cannot directly provide services to clients with special service scenario requirements.

[0005] Firstly, this application provides a PCDN service method applied to a PCDN server, the PCDN service method comprising: When the client meets the specific service scenario requirements, the IP address of the PCDN repeater is sent to the client; wherein, the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; In response to the target resource request sent by the client, the PCDN repeater queries the target PCDN terminal node where the target resource is located and obtains the Internet Protocol IP address of the target PCDN terminal node. The PCDN repeater initiates a target resource download request to the target PCDN terminal node based on the IP address of the target PCDN terminal node; After the target PCDN terminal node responds to the target resource download request, the PCDN repeater receives the target resource returned by the target PCDN terminal node and sends the target resource to the client.

[0006] In one embodiment, the PCDN server further includes a PCDN scheduling server; the PCDN service method further includes: When the client does not meet the requirements of a specific service scenario, the IP address of the PCDN scheduling server is sent to the client. In response to the target resource request sent by the client, the PCDN scheduling server queries the target PCDN terminal node where the target resource is located, obtains the IP address of the target PCDN terminal node, and sends the IP address of the target PCDN terminal node to the client. After the target PCDN terminal node receives the target resource download request sent by the client, the target PCDN terminal node responds to the target resource download request by sending the target resource to the client.

[0007] In one embodiment, whether the client meets the requirements of a specific service scenario or not is determined by the following method: In response to the target service domain name resolution request sent by the client's local domain name server; If the client has at least one service scenario requirement, such as needing free data service, needing cross-province service, or not supporting protocols that depend on PCDN scheduling, then the client is determined to meet the specific service scenario requirement. If the client does not have a service scenario requirement among at least one of the following: needing free data service, needing cross-province service, and not supporting protocols that PCDN scheduling depends on, then it is determined that the client does not meet the specific service scenario requirement.

[0008] Secondly, this application also provides a PCDN service method applied to a client, the PCDN service method comprising: When the client meets the specific service scenario requirements, it receives the IP address of the PCDN repeater sent by the PCDN server; wherein, the PCDN server includes the PCDN repeater and the PCDN terminal node, and the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; Based on the IP address of the PCDN repeater, a target resource request is sent to the PCDN repeater; After the PCDN repeater responds to the target resource request, it receives the target resource sent by the PCDN repeater.

[0009] In one embodiment, the PCDN service method further includes: The PCDN server also includes a PCDN scheduling server and PCDN terminal nodes; the PCDN service method further includes: When the client does not meet the requirements of a specific service scenario, the IP address of the PCDN scheduling server sent by the PCDN server is received. Based on the IP address of the PCDN scheduling server, a target resource request is sent to the PCDN scheduling server; After the PCDN scheduling server responds to the target resource request, it receives the IP address of the target PCDN terminal node where the target resource is located, sent by the PCDN scheduling server. Based on the IP address of the target PCDN terminal node, a target resource download request is sent to the target PCDN terminal node; After the target PCDN terminal node responds to the target resource request, the target resource sent by the target PCDN terminal node is received.

[0010] Thirdly, this application also provides a PCDN service device deployed on a PCDN server, wherein the PCDN server includes a PCDN repeater and a PCDN terminal node; the PCDN service device includes: The address sending module is used to send the IP address of the PCDN repeater to the client when the client meets the specific service scenario requirements; wherein, the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; The address query module is used by the PCDN repeater to query the target PCDN terminal node where the target resource is located in response to the target resource request sent by the client, and obtain the IP address of the target PCDN terminal node; The resource download request sending module is used by the PCDN repeater to initiate a target resource download request to the target PCDN terminal node based on the IP address of the target PCDN terminal node; The resource sending module is configured to, after the target PCDN terminal node responds to the target resource download request, receive the target resource returned by the target PCDN terminal node, and send the target resource to the client.

[0011] Fourthly, this application also provides a PCDN service device deployed on a client, the PCDN service device comprising: The address receiving module is used to receive the IP address of the PCDN repeater sent by the PCDN server when the client meets the specific service scenario requirements; wherein, the PCDN server includes the PCDN repeater and the PCDN terminal node, and the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; The resource download request sending module is used to send a target resource request to the PCDN repeater based on the IP address of the PCDN repeater; The resource receiving module is used to receive the target resource sent by the PCDN repeater after the PCDN repeater responds to the target resource request.

[0012] Fifthly, this application also provides a service system, including: a client, a PCDN server, and a CDN server, wherein the PCDN server includes a PCDN repeater and a PCDN terminal node; The client is used to: send a target service domain name resolution request to the CDN server; The CDN server is configured to: respond to the target service domain name resolution request sent by the client to the CDN server; if the target service domain name has enabled PCDN distribution service, send the target service domain name resolution request to the client to the PCDN server. The client is configured to: receive a target service domain name resolution request sent by the CDN server to the PCDN server, and send a target service domain name resolution request to the PCDN server. The PCDN server is configured to: respond to a target service domain name resolution request sent by the client to the PCDN server, determine that the client meets the specific service scenario requirements, and send the IP address of the PCDN repeater to the client; wherein, the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; The client is configured to: receive the IP address of the PCDN repeater sent by the PCDN server, and send a target resource request to the PCDN repeater based on the IP address of the PCDN repeater; The PCDN server is configured to: respond to a target resource request sent by the client, query the target PCDN terminal node where the target resource is located, and obtain the IP address of the target PCDN terminal node; based on the IP address of the target PCDN terminal node, the PCDN repeater initiates a target resource download request to the target PCDN terminal node; after the target PCDN terminal node responds to the target resource download request, the PCDN repeater receives the target resource returned by the target PCDN terminal node and sends the target resource to the client; The client is configured to: receive the target resource sent by the PCDN repeater after the PCDN repeater responds to the target resource request.

[0013] Sixthly, this application provides an electronic device, the electronic device including a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of any of the PCDN service methods described above.

[0014] In a seventh aspect, this application also provides a non-transitory computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the PCDN service methods described above.

[0015] Eighthly, this application also provides a computer program product comprising a computer program that can be stored on a non-transitory computer-readable storage medium, and which, when executed by the processor, implements the steps of any of the PCDN service methods described above.

[0016] The PCDN service method, apparatus, system, and equipment provided in this application, under the limitation of scenarios where PCDN terminal nodes cannot directly provide services to clients, add a PCDN repeater as an intermediate layer for direct service with clients. The PCDN repeater schedules the client's target resource request to the PCDN repeater for service, and then requests the target resource from the PCDN terminal node to download the target resource and provides the downloaded target resource to the client. This effectively expands the coverage of PCDN services and improves the efficiency and stability of resource acquisition for clients in complex network environments. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating the traditional PCDN service method provided in this application.

[0019] Figure 2 This is a flowchart illustrating the PCDN service method based on a PCDN repeater provided in this application.

[0020] Figure 3 This is one of the flowcharts illustrating the PCDN service method applied to the PCDN server provided in this application.

[0021] Figure 4 This is a schematic diagram of the overall process of the PCDN service method provided in this application.

[0022] Figure 5 This is a schematic diagram of the architecture that integrates CDN and PCDN provided in this application.

[0023] Figure 6 This is the second flowchart of the PCDN service method applied to the PCDN server provided in this application.

[0024] Figure 7 This is a schematic diagram illustrating the logic for determining the next scheduling direction of the request provided in this application.

[0025] Figure 8 This is one of the flowcharts illustrating the PCDN service method applied to the client provided in this application.

[0026] Figure 9 This is the second flowchart of the PCDN service method applied to the client provided in this application.

[0027] Figure 10 This is one of the structural schematic diagrams of the PCDN service device provided in this application.

[0028] Figure 11 This is the second structural schematic diagram of the PCDN service device provided in this application.

[0029] Figure 12 This is a schematic diagram of the structure of the electronic device provided in this application. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0031] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein.

[0032] To address the problem that existing PCDN terminal nodes cannot directly provide services to clients with special service needs, this application proposes a new system architecture, which adds a PCDN repeater to the original architecture.

[0033] PCDN repeaters are responsible for aggregating the output streams from PCDN terminal nodes, enabling clients to request resources and providing resource services to clients. They can support various special service scenarios, including those where PCDN terminal nodes cannot directly provide services.

[0034] PCDN terminal nodes are responsible for content caching and providing the required content to clients and PCDN repeaters.

[0035] Each PCDN terminal node is equipped with a communication module that communicates with the PCDN repeater. The two maintain a long-term communication link, ensuring efficient resource transmission. Therefore, the PCDN repeater can efficiently retrieve cached content from each PCDN terminal node and forward this content to the client, providing resource services to the client.

[0036] In traditional PCDN service models, PCDN terminal nodes are deployed on the user's home side. Due to limitations imposed by home firewalls and home gateway configurations, the proportion of terminals that can provide external services through PCDN is not high. By maintaining a persistent connection between the PCDN repeater and the PCDN terminal nodes, there is no need for the terminals to actively open ports. This avoids service restrictions imposed by factors such as home firewalls and home gateway settings, ensuring that PCDN terminal nodes can stably provide resources to the PCDN repeater.

[0037] In addition, the PCDN repeater makes full use of PCDN's terminal storage, storing hot resources on the PCDN service terminal and obtaining resources from the backend through a proxy, thus reducing its own disk read pressure. It also distributes some business processing logic (such as access control authentication, formatted log output, etc.) to the backend PCDN terminal for processing, utilizing the terminal's computing power, reducing the CPU and other hardware overhead of the proxy server itself, saving server resources, and greatly improving server performance, thereby enhancing bandwidth service capabilities.

[0038] Figure 1 This is a flowchart illustrating the traditional PCDN service method provided in this application. The client initiates a DNS resolution request to the PCDN authoritative Domain Name Server (DNS) at the PCDN dispatcher to obtain the access address of the target resource. After resolution by the PCDN authoritative DNS, it returns the Internet Protocol (IP) address of the dispatcher server to the client via a 302 redirect, guiding the client into the resource dispatch process. Based on the returned IP address, the client sends a Hypertext Transfer Protocol (HTTP) request to the 302 dispatcher server to request the target resource. The 302 dispatcher server queries the PCDN terminal node (such as an edge node like a set-top box) that stores the target resource and returns its IP address to the client. The client uses the IP address of the PCDN terminal node to directly initiate an HTTP request to that node to obtain the target resource. The PCDN terminal node responds to the request, transmitting the target resource to the client, completing content distribution.

[0039] The entire process is guided by authoritative DNS and allocated PCDN terminal nodes by a 302 scheduling server, enabling direct resource interaction between the client and edge nodes, and improving content distribution efficiency and network experience by utilizing distributed nodes.

[0040] Figure 2 This is a flowchart illustrating the PCDN service method based on a PCDN repeater provided in this application. The client initiates a DNS resolution request to the authoritative PCDN DNS of the PCDN scheduling system. The authoritative PCDN DNS returns the IP address of the PCDN repeater to the client. Based on the obtained IP address, the client initiates an HTTP request to the PCDN repeater to retrieve the target resource. The PCDN repeater retrieves file fragments in parallel from multiple PCDN terminal nodes, concatenates and integrates the fragments, and finally provides the complete resource to the client.

[0041] The entire process guides the client to the PCDN repeater through the PCDN authoritative DNS, and then the PCDN repeater obtains the target from the PCDN terminal node. As an intermediary, the PCDN repeater enables effective resource interaction between the client and the PCDN terminal node, further optimizing the content distribution process and improving the user's network experience.

[0042] The PCDN service method proposed in this application allows for flexible switching of service modes based on different user needs. When users meet special needs, a PCDN service method based on PCDN repeaters can be used; when users do not meet special needs, a traditional PCDN service method can be used. This enables flexible configuration of service methods and improves user experience.

[0043] This application presents the following embodiments, which are described below in conjunction with... Figures 1-9 This application provides a detailed description of the PCDN service method.

[0044] This application provides a PCDN service method applied to a PCDN server, wherein the method is executed by the controller of the PCDN server as the execution subject. Figure 3 This is one of the flowcharts illustrating the PCDN service method applied to the PCDN server provided in this application. Figure 4 This is a schematic diagram of the overall process of the PCDN service method provided in this application.

[0045] The PCDN server includes PCDN repeaters and PCDN terminal nodes, such as Figure 3 As shown, the PCDN service method includes the following steps: Step 310: When the client meets the specific service scenario requirements, send the IP address of the PCDN repeater to the client; wherein, the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; Step 320: In response to the target resource request sent by the client, the PCDN repeater queries the target PCDN terminal node where the target resource is located and obtains the Internet Protocol IP address of the target PCDN terminal node; Step 330: The PCDN repeater initiates a target resource download request to the target PCDN terminal node based on the IP address of the target PCDN terminal node; Step 340: After the target PCDN terminal node responds to the target resource download request, the PCDN repeater receives the target resource returned by the target PCDN terminal node and sends the target resource to the client.

[0046] Specifically, when a client wants to obtain a target resource (e.g., https: / / a.com / demo.ts), it initiates a DNS resolution request for the target service domain name (a.com), which is recursively routed from the local DNS to the CDN converged scheduling server in the CDN server.

[0047] The CDN's converged scheduling server needs to determine whether the client's content delivery service is provided by CDN or PCDN based on the DNS resolution request sent by the client. It then determines whether the target service domain name (a.com) in the DNS resolution request is eligible for PCDN distribution services.

[0048] If the domain name does not have content distribution services enabled, then the CDN will be responsible for content distribution. The target CDN edge node storing the target resource will be queried, and its IP address will be returned to the client. The client will then initiate an HTTP request (http: / / a.com / demo.ts) to that node based on its IP address. The node will respond to the HTTP request and return the target resource to the client.

[0049] If the domain name has enabled content distribution services, then it is confirmed that PCDN provides content distribution services. In this case, the PCDN server returns the CNAME of the authoritative DNS of PCDN: a.com.pcdn.com. CNAME is a canonical domain name redirection mechanism used to instruct the client to re-initiate a DNS resolution request for the new domain name.

[0050] After receiving the CNAME from the PCDN authoritative DNS, the client's local DNS will initiate a DNS resolution request for a.com.pcdn.com to the PCDN authoritative DNS. Based on this request, the PCDN authoritative DNS will determine whether the client currently meets the requirements of the specific service scenario.

[0051] When a client meets the specific service requirements, the PCDN authoritative DNS will return the IP address of the PCDN repeater to the client, directing the client to the PCDN repeater, which will then provide the target resource to the client. This process avoids the client directly initiating requests to the PCDN terminal node; instead, it uses the repeater as an intermediary to achieve efficient resource distribution and transmission.

[0052] After receiving the IP address of the PCDN repeater, the client sends a target resource request to the PCDN repeater. Upon receiving the request, the PCDN repeater queries the target PCDN terminal node where the target resource is located and obtains the IP address of that node.

[0053] The PCDN repeater initiates a download request for the target resource (https: / / a.com / demo.ts) to the target PCDN terminal node based on the node's IP address. The target PCDN terminal node responds to the download request by returning the target resource to the PCDN repeater.

[0054] After the PCDN repeater receives the target resource returned by the target PCDN terminal node and completes the download, it forwards the target resource to the client, thus completing the entire agile resource acquisition process.

[0055] Figure 5 This application provides a schematic diagram of an architecture integrating CDN and PCDN. Its core purpose is to achieve more efficient content distribution by coordinating the resource scheduling of both networks. When a service domain has enabled but not yet enabled PCDN distribution services, content distribution is achieved by utilizing the network resources of the CDN server; conversely, when the service domain has enabled PCDN distribution services, content distribution is achieved by utilizing the network resources of the PCDN server. Furthermore, if the PCDN endpoint does not have the required content, it can retrieve the content from the CDN edge node or origin server via an origin request, cache it, and then distribute it to the user. This integrated architecture can flexibly select the optimal content distribution path based on the actual service status and resource distribution.

[0056] The PCDN service method provided in this application, under the limitation of scenarios where PCDN terminal nodes cannot directly provide services to clients, adds a PCDN repeater as an intermediate layer for direct service with clients. The PCDN repeater schedules the client's target resource request to the PCDN repeater for service, and then requests the target resource from the PCDN terminal node to download the target resource, and provides the downloaded target resource to the client. This effectively expands the coverage of PCDN services and improves the efficiency and stability of resource acquisition for clients in complex network environments.

[0057] This application also provides a PCDN service method applied to a PCDN server, wherein the method is executed by the controller of the PCDN server as the execution subject. Figure 6 This is the second flowchart illustrating the PCDN service method applied to the PCDN server provided in this application. Figure 4 This is a schematic diagram of the overall process of the PCDN service method provided in this application.

[0058] The PCDN server also includes a PCDN scheduling server, such as Figure 6 As shown, the PCDN service method includes the following steps: Step 610: When the client does not meet the requirements of a specific service scenario, send the IP address of the PCDN scheduling server to the client; Step 620: In response to the target resource request sent by the client, the PCDN scheduling server queries the target PCDN terminal node where the target resource is located, obtains the IP address of the target PCDN terminal node, and sends the IP address of the target PCDN terminal node to the client. Step 630: After the target PCDN terminal node receives the target resource download request sent by the client, the target PCDN terminal node responds to the target resource download request by sending the target resource to the client.

[0059] Specifically, after receiving the CNAME from the PCDN authoritative DNS, the client's local DNS will initiate a DNS resolution request for a.com.pcdn.com to the PCDN authoritative DNS. Based on this request, the PCDN authoritative DNS will determine whether the client currently meets the requirements of the specific service scenario.

[0060] If the client does not meet the requirements of a specific service scenario, it is assumed that the request can be served directly by the PCDN terminal node. The PCDN authoritative DNS returns the IP address of the PCDN scheduling server to the client's local DNS, and the local DNS recursively returns the IP address to the client.

[0061] The client sends a target resource request (https: / / a.com / demo.ts) to the PCDN scheduling server based on the IP address. After receiving the request, the PCDN scheduling server queries the target PCDN terminal node where the target resource is located, obtains the IP address of the node, and returns the IP address to the client.

[0062] After receiving the IP address of the target PCDN endpoint, the client sends a target resource download request (https: / / a.com / demo.ts) to the target PCDN endpoint. The target PCDN endpoint responds to the download request and sends the target resource to the client, thus completing the entire agile resource acquisition process.

[0063] In this embodiment, when the client does not meet the requirements of a specific service scenario, the PCDN scheduling server directly guides the client to establish a connection with the target PCDN terminal node, thereby achieving rapid resource distribution, reducing unnecessary intermediate steps, and further optimizing the content distribution path.

[0064] The two embodiments listed above can dynamically adjust service strategies according to the actual needs of the client, enabling the entire PCDN service system to more intelligently cope with complex and ever-changing network environments and provide users with a smoother and more efficient content distribution experience.

[0065] To address the specific needs of a client scenario, an embodiment is proposed, wherein whether the client meets or does not meet the specific service scenario requirements is determined in the following way: In response to the target service domain name resolution request sent by the client's local domain name server; If the client has at least one service scenario requirement, such as needing free data service, needing cross-province service, or not supporting protocols that depend on PCDN scheduling, then the client is determined to meet the specific service scenario requirement. If the client does not have a service scenario requirement among at least one of the following: needing free data service, needing cross-province service, and not supporting protocols that PCDN scheduling depends on, then it is determined that the client does not meet the specific service scenario requirement.

[0066] Specifically, the following process can be referred to Figure 7 , Figure 7 This is a schematic diagram illustrating the logic for determining the next scheduling direction of the request provided in this application.

[0067] Traditional PCDN service methods have several service defects, such as difficulty in supporting client-side free data services, inability to adapt to scenarios where clients do not support HTTP 302, and difficulty in supporting cross-province services for clients.

[0068] PCDN struggles to support free data services for customers: PCDN's server is a terminal node, often deployed on the user's home side. The number of terminals is huge and their IP addresses are not fixed, making it difficult to achieve free data service through the Layer 3 free data service method (i.e., identifying the range of server-side IP addresses). In addition, PCDN generally uses the HTTP 302 scheduling method to find the terminal service node where the corresponding resource is located. During the scheduling process, the client's domain name will be rewritten, so it is also difficult to support Layer 7 free data service.

[0069] PCDN cannot adapt to scenarios where the client does not support HTTP 302: In order to find the terminal node where the resource is located, PCDN generally uses the HTTP 302 scheduling method to schedule the user's request to the specific terminal node where the resource is located. This requires the client to support HTTP 302. If it cannot support it, the service cannot be provided.

[0070] PCDN has difficulty supporting cross-provincial services: Currently, operators have adopted a cross-provincial settlement model, which only allows cross-provincial services for service nodes with fixed systems and fixed IP address ranges such as IDC and CDN. PCDN terminals have a huge number of terminals and their IP addresses are not fixed, so they are generally subject to cross-provincial settlement by operators, which increases operating costs.

[0071] To address the specific service requirements of the aforementioned clients, a new PCDN repeater is added. This repeater supports the needs of clients using PCDN services, such as data-free service and cross-province service. It also adapts to scenarios where clients do not support HTTP 302, improving terminal availability and providing service solutions. In the PCDN service method of this application, the service mode can be quickly switched according to different client needs.

[0072] For example, a PCDN relay service solution combined with direct PCDN terminal node service can be adopted. For clients that do not require data-free service, support the HTTP 302 protocol, only require local province service, and have low bandwidth demands, the direct PCDN terminal node service mode can be used. For clients outside the province, mobile data users, or those that do not support HTTP 302, a relay service solution with flexible configuration can be used.

[0073] After receiving a DNS resolution request from a client, the PCDN authoritative DNS will obtain key parameters from the client, such as the service domain name, client IP address, and client User-Agent (the browser / application identifier of the user's device, including information such as device type and system version), and determine the next scheduling direction based on these key parameters.

[0074] Based on the client's User-Agent, determine if the client supports HTTP 302. If the client does not support HTTP 302, directly route to path one, which uses the PCDN relay service. The resolved result is the PCDN relay IP address, and the service is forwarded through the relay node. If the client supports HTTP 302, proceed to the next logical step.

[0075] Based on the client's IP address, determine whether the client is located within the province where the service is located. If the client is not within the province, it will still be routed to path one, i.e., using the PCDN relay service scheme and forwarding via the repeater's IP address. If the client is within the province, proceed to the next logical step.

[0076] Based on the service domain name, determine whether the domain name belongs to the data-free service, meaning that users do not consume their own data when accessing it, which is usually provided by the operator and the service provider. If the domain name does not belong to the data-free service, it is routed to path two, which uses the PCDN terminal direct service solution. The resolution result is the IP address of the PCDN H scheduling server, and the user directly connects to the terminal node to obtain the service. If the domain name belongs to the data-free service, proceed to the next logical judgment.

[0077] Based on the client's IP address, determine whether the client is using a mobile network (2G / 3G / 4G / 5G). If the client is using a mobile network, route 1 is used, employing the PCDN relay service scheme and forwarding via the repeater's IP address. If the client is not using a mobile network, route 2 is used, employing the PCDN direct terminal service scheme and obtaining service through a direct terminal connection.

[0078] This application embodiment effectively solves the service defects of traditional PCDN services in scenarios such as free data usage support, cross-province service adaptation, and HTTP 302 protocol compatibility through the above-mentioned scheduling judgment logic and flexible service mode switching mechanism.

[0079] This application also provides a PCDN service method applied to a client, wherein the method is executed by the client's controller as the execution entity. Figure 8 This is one of the flowcharts illustrating the PCDN service method applied to the client provided in this application. Figure 4 This is a schematic diagram of the overall process of the PCDN service method provided in this application.

[0080] like Figure 8 As shown, the PCDN service method includes the following steps: Step 810: When the client meets the specific service scenario requirements, receive the IP address of the PCDN repeater sent by the PCDN server; wherein, the PCDN server includes the PCDN repeater and the PCDN terminal node, and the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; Step 820: Send a target resource request to the PCDN repeater based on the PCDN repeater's IP address; Step 830: After the PCDN repeater responds to the target resource request, receive the target resource sent by the PCDN repeater.

[0081] Specifically, when a client wants to obtain a target resource (e.g., https: / / a.com / demo.ts), it initiates a DNS resolution request for the target service domain name (a.com), which is recursively routed from the local DNS to the CDN converged scheduling server in the CDN server.

[0082] The CDN's converged scheduling server needs to determine whether the client's content delivery service is provided by CDN or PCDN based on the DNS resolution request sent by the client. It then determines whether the target service domain name (a.com) in the DNS resolution request is eligible for PCDN distribution services.

[0083] If the domain name does not have content distribution services enabled, then the CDN will be responsible for content distribution. The target CDN edge node storing the target resource will be queried, and its IP address will be returned to the client. The client will then initiate an HTTP request (http: / / a.com / demo.ts) to that node based on its IP address. The node will respond to the HTTP request and return the target resource to the client.

[0084] If the domain name has enabled content distribution services, then it is confirmed that PCDN provides content distribution services. In this case, the PCDN server returns the CNAME of the authoritative DNS of PCDN: a.com.pcdn.com. CNAME is a canonical domain name redirection mechanism used to instruct the client to re-initiate a DNS resolution request for the new domain name.

[0085] After receiving the CNAME from the PCDN authoritative DNS, the client's local DNS will initiate a DNS resolution request for a.com.pcdn.com to the PCDN authoritative DNS. Based on this request, the PCDN authoritative DNS will determine whether the client currently meets the requirements of the specific service scenario.

[0086] When a client meets the specific service requirements, the PCDN authoritative DNS will return the IP address of the PCDN repeater to the client, directing the client to the PCDN repeater, which will then provide the target resource to the client. This process avoids the client directly initiating requests to the PCDN terminal node; instead, it uses the repeater as an intermediary to achieve efficient resource distribution and transmission.

[0087] After receiving the IP address of the PCDN repeater, the client sends a target resource request to the PCDN repeater. Upon receiving the request, the PCDN repeater queries the target PCDN terminal node where the target resource is located and obtains the IP address of that node.

[0088] The PCDN repeater initiates an HTTP request to download the target resource (https: / / a.com / demo.ts) to the target PCDN terminal node based on the node's IP address. The target PCDN terminal node responds to the download request by returning the target resource to the PCDN repeater.

[0089] After the PCDN repeater receives the target resource returned by the target PCDN terminal node and completes the download, it forwards the target resource to the client, thus completing the entire agile resource acquisition process.

[0090] Figure 5This application provides a schematic diagram of an architecture integrating CDN and PCDN. Its core purpose is to achieve more efficient content distribution by coordinating the resource scheduling of both networks. When a service domain has enabled but not yet enabled PCDN distribution services, content distribution is achieved by utilizing the network resources of the CDN server; conversely, when the service domain has enabled PCDN distribution services, content distribution is achieved by utilizing the network resources of the PCDN server. Furthermore, if the PCDN endpoint does not have the required content, it can retrieve the content from the CDN edge node or origin server via an origin request, cache it, and then distribute it to the user. This integrated architecture can flexibly select the optimal content distribution path based on the actual service status and resource distribution.

[0091] The PCDN service method provided in this application, under the limitation of scenarios where PCDN terminal nodes cannot directly provide services to clients, adds a PCDN repeater as an intermediate layer for direct service with clients. The PCDN repeater schedules the client's target resource request to the PCDN repeater for service, and then requests the target resource from the PCDN terminal node to download the target resource, and provides the downloaded target resource to the client. This effectively expands the coverage of PCDN services and improves the efficiency and stability of resource acquisition for clients in complex network environments.

[0092] This application also provides a PCDN service method applied to a client, wherein the method is executed by the client's controller as the execution entity. Figure 9 This is the second flowchart of the PCDN service method applied to the client provided in this application. Figure 4 This is a schematic diagram of the overall process of the PCDN service method provided in this application.

[0093] The PCDN server also includes a PCDN scheduling server, such as Figure 9 As shown, the PCDN service method includes the following steps: Step 910: When the client does not meet the requirements of a specific service scenario, receive the IP address of the PCDN scheduling server sent by the PCDN server. Step 920: Send a target resource request to the PCDN scheduling server based on the IP address of the PCDN scheduling server; Step 930: After the PCDN scheduling server responds to the target resource request, receive the IP address of the target PCDN terminal node where the target resource is located, sent by the PCDN scheduling server. Step 940: Based on the IP address of the target PCDN terminal node, send a target resource download request to the target PCDN terminal node; Step 950: After the target PCDN terminal node responds to the target resource request, receive the target resource sent by the target PCDN terminal node.

[0094] Specifically, after receiving the CNAME from the PCDN authoritative DNS, the client's local DNS will initiate a DNS resolution request for a.com.pcdn.com to the PCDN authoritative DNS. Based on this request, the PCDN authoritative DNS will determine whether the client currently meets the requirements of the specific service scenario.

[0095] If the client does not meet the requirements of a specific service scenario, it is assumed that the request can be served directly by the PCDN terminal node. The PCDN authoritative DNS returns the IP address of the PCDN scheduling server to the client's local DNS, and the local DNS recursively returns the IP address to the client.

[0096] The client sends a target resource request (https: / / a.com / demo.ts) to the PCDN scheduling server based on the IP address. After receiving the request, the PCDN scheduling server queries the target PCDN terminal node where the target resource is located, obtains the IP address of the node, and returns the IP address to the client.

[0097] After receiving the IP address of the target PCDN endpoint, the client sends a target resource download request (https: / / a.com / demo.ts) to the target PCDN endpoint. The target PCDN endpoint responds to the download request and sends the target resource to the client, thus completing the entire agile resource acquisition process.

[0098] In this embodiment, when the client does not meet the requirements of a specific service scenario, the PCDN scheduling server directly guides the client to establish a connection with the target PCDN terminal node, thereby achieving rapid resource distribution, reducing unnecessary intermediate steps, and further optimizing the content distribution path.

[0099] The two embodiments listed above can dynamically adjust service strategies according to the actual needs of the client, enabling the entire PCDN service system to more intelligently cope with complex and ever-changing network environments and provide users with a smoother and more efficient content distribution experience.

[0100] In summary, all the above embodiments, and Figure 4 The complete flowchart is shown below, which describes the entire process of PCDN service.

[0101] When a client wants to obtain a target resource (e.g., https: / / a.com / demo.ts), it initiates a DNS resolution request for the target service domain name (a.com), which is recursively routed from the local NDS to the CDN converged scheduling server in the CDN server.

[0102] The CDN's converged scheduling server needs to determine whether the client's content delivery service is provided by CDN or PCDN based on the DNS resolution request sent by the client. It then determines whether the target service domain name (a.com) in the DNS resolution request is eligible for PCDN distribution services.

[0103] If the domain name does not have content distribution services enabled, then the CDN will be responsible for content distribution. The target CDN edge node storing the target resource will be queried, and its IP address will be returned to the client. The client will then initiate an HTTP request (http: / / a.com / demo.ts) to that node based on its IP address. The node will respond to the HTTP request and return the target resource to the client.

[0104] If the domain name has enabled content distribution services, and it is confirmed that PCDN provides content distribution services, then the PCDN authoritative DNS CNAME of a.com.pcdn.com will be returned to the client.

[0105] After receiving the CNAME from the PCDN authoritative DNS, the client's local DNS will initiate a DNS resolution request for a.com.pcdn.com to the PCDN authoritative DNS. Based on this request, the PCDN authoritative DNS will determine whether the client currently meets the requirements of the specific service scenario.

[0106] When a client meets the specific service scenario requirements, the PCDN authoritative DNS will return the IP address of the PCDN repeater to the client, directing the client to the PCDN repeater, which will then be responsible for providing the target resources to the client.

[0107] After receiving the IP address of the PCDN repeater, the client sends a target resource request to the PCDN repeater. Upon receiving the request, the PCDN repeater queries the target PCDN terminal node where the target resource is located and obtains the IP address of that node.

[0108] The PCDN repeater initiates an HTTP request to download the target resource (https: / / a.com / demo.ts) to the target PCDN terminal node based on the node's IP address. The target PCDN terminal node responds to the download request by returning the target resource to the PCDN repeater.

[0109] After the PCDN repeater receives the target resource returned by the target PCDN terminal node and completes the download, it forwards the target resource to the client, thus completing the entire agile resource acquisition process.

[0110] If the client does not meet the requirements of a specific service scenario, it is assumed that the request can be served directly by the PCDN terminal node. The PCDN authoritative DNS returns the IP address of the PCDN scheduling server to the client's local DNS, and the local DNS recursively returns the IP address to the client.

[0111] The client sends a target resource request (https: / / a.com / demo.ts) to the PCDN scheduling server based on the IP address. After receiving the request, the PCDN scheduling server queries the target PCDN terminal node where the target resource is located, obtains the IP address of the node, and returns the IP address to the client.

[0112] After receiving the IP address of the target PCDN endpoint, the client sends a target resource download request (https: / / a.com / demo.ts) to the target PCDN endpoint. The target PCDN endpoint responds to the download request and sends the target resource to the client, thus completing the entire agile resource acquisition process.

[0113] The PCDN service apparatus provided in this application is described below. The PCDN service apparatus described below can be referred to in correspondence with the PCDN service method described above.

[0114] Figure 10 This is one of the structural schematic diagrams of the PCDN service device provided in this application. For example... Figure 10 As shown, the PCDN service device is deployed on the PCDN server and includes an address sending module 1010, an address query module 1020, a resource download request sending module 1030, and a resource sending module 1040. The address sending module 1010 is used to send the IP address of the PCDN repeater to the client when the client meets the specific service scenario requirements; wherein, the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; The address query module 1020 is used by the PCDN repeater to query the target PCDN terminal node where the target resource is located in response to the target resource request sent by the client, and obtain the IP address of the target PCDN terminal node. The resource download request sending module 1030 is used for the PCDN repeater to initiate a target resource download request to the target PCDN terminal node based on the IP address of the target PCDN terminal node; The resource sending module 1040 is used to receive the target resource returned by the target PCDN terminal node after the target PCDN terminal node responds to the target resource download request, and send the target resource to the client.

[0115] In one embodiment, the PCDN service apparatus is further configured to: When the client does not meet the requirements of a specific service scenario, the IP address of the PCDN scheduling server is sent to the client. In response to the target resource request sent by the client, the PCDN scheduling server queries the target PCDN terminal node where the target resource is located, obtains the IP address of the target PCDN terminal node, and sends the IP address of the target PCDN terminal node to the client. After the target PCDN terminal node receives the target resource download request sent by the client, the target PCDN terminal node responds to the target resource download request by sending the target resource to the client.

[0116] In one embodiment, the PCDN service apparatus is further configured to: In response to the target service domain name resolution request sent by the client's local domain name server; If the client has at least one service scenario requirement, such as needing free data service, needing cross-province service, or not supporting protocols that depend on PCDN scheduling, then the client is determined to meet the specific service scenario requirement. If the client does not have a service scenario requirement among at least one of the following: needing free data service, needing cross-province service, and not supporting protocols that PCDN scheduling depends on, then it is determined that the client does not meet the specific service scenario requirement.

[0117] Figure 11 This is the second structural schematic diagram of the PCDN service device provided in this application. Figure 11 As shown, the PCDN service device is deployed on the client side and includes an address receiving module 1110, a resource download request sending module 1120, and a resource receiving module 1130. Address receiving module 1110 is used to receive the IP address of the PCDN repeater sent by the PCDN server when the client meets the specific service scenario requirements; wherein, the PCDN server includes the PCDN repeater and the PCDN terminal node, and the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; The resource download request sending module 1120 is used to send a target resource request to the PCDN repeater based on the IP address of the PCDN repeater; The resource receiving module 1130 is used to receive the target resource sent by the PCDN repeater after the PCDN repeater responds to the target resource request.

[0118] In one embodiment, the PCDN server further includes a PCDN scheduling server and a PCDN terminal node; the PCDN service device is also used for: When the client does not meet the requirements of a specific service scenario, the IP address of the PCDN scheduling server sent by the PCDN server is received. Based on the IP address of the PCDN scheduling server, a target resource request is sent to the PCDN scheduling server; After the PCDN scheduling server responds to the target resource request, it receives the IP address of the target PCDN terminal node where the target resource is located, sent by the PCDN scheduling server. Based on the IP address of the target PCDN terminal node, a target resource download request is sent to the target PCDN terminal node; After the target PCDN terminal node responds to the target resource request, the target resource sent by the target PCDN terminal node is received.

[0119] The service system provided in this application is described below, and the service system described below can be referred to in correspondence with the PCDN service method described above. This application provides a service system, which includes: a client, a PCDN server, and a CDN server, wherein the PCDN server includes a PCDN repeater and a PCDN terminal node; The client is used to: send a target service domain name resolution request to the CDN server; The CDN server is configured to: respond to the target service domain name resolution request sent by the client to the CDN server; if the target service domain name has enabled PCDN distribution service, send the target service domain name resolution request to the client to the PCDN server. The client is configured to: receive a target service domain name resolution request sent by the CDN server to the PCDN server, and send a target service domain name resolution request to the PCDN server. The PCDN server is configured to: respond to a target service domain name resolution request sent by the client to the PCDN server, determine that the client meets the specific service scenario requirements, and send the IP address of the PCDN repeater to the client; wherein, the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; The client is configured to: receive the IP address of the PCDN repeater sent by the PCDN server, and send a target resource request to the PCDN repeater based on the IP address of the PCDN repeater; The PCDN server is configured to: respond to a target resource request sent by the client, query the target PCDN terminal node where the target resource is located, and obtain the IP address of the target PCDN terminal node; based on the IP address of the target PCDN terminal node, the PCDN repeater initiates a target resource download request to the target PCDN terminal node; after the target PCDN terminal node responds to the target resource download request, the PCDN repeater receives the target resource returned by the target PCDN terminal node and sends the target resource to the client; The client is configured to: receive the target resource sent by the PCDN repeater after the PCDN repeater responds to the target resource request.

[0120] Figure 12 This is a schematic diagram of the structure of the electronic device provided in this application, such as... Figure 12As shown, the electronic device may include: a processor 1210, a communications interface 1220, a memory 1230, and a communication bus 1240, wherein the processor 1210, the communications interface 1220, and the memory 1230 communicate with each other through the communication bus 1240. The processor 1210 can invoke logical instructions in the memory 1230 to execute a PCDN service method, which includes: sending the IP address of the PCDN repeater to the client when the client meets a specific service scenario requirement; wherein the specific service scenario requirement is used to indicate that the PCDN terminal node cannot directly provide services to the client; the PCDN repeater responds to the target resource request sent by the client, queries the target PCDN terminal node where the target resource is located, and obtains the Internet Protocol IP address of the target PCDN terminal node; the PCDN repeater initiates a target resource download request to the target PCDN terminal node based on the IP address of the target PCDN terminal node; after the target PCDN terminal node responds to the target resource download request, the PCDN repeater receives the target resource returned by the target PCDN terminal node and sends the target resource to the client. Alternatively, when the client meets the specific service scenario requirements, it receives the IP address of the PCDN repeater sent by the PCDN server; wherein the PCDN server includes the PCDN repeater and PCDN terminal nodes, and the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; based on the IP address of the PCDN repeater, it sends a target resource request to the PCDN repeater; after the PCDN repeater responds to the target resource request, it receives the target resource sent by the PCDN repeater.

[0121] Furthermore, the logical instructions in the aforementioned memory 1230 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, 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 steps 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 USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0122] On the other hand, this application also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions, and when the program instructions are executed by a computer, the computer can execute the PCDN service method provided in the above embodiments. The method includes: when a client meets a specific service scenario requirement, sending the IP address of the PCDN repeater to the client; wherein the specific service scenario requirement is used to characterize that the PCDN terminal node cannot directly provide services to the client; the PCDN repeater responds to the target resource request sent by the client, queries the target PCDN terminal node where the target resource is located, and obtains the Internet Protocol IP address of the target PCDN terminal node; the PCDN repeater initiates a target resource download request to the target PCDN terminal node based on the IP address of the target PCDN terminal node; after the target PCDN terminal node responds to the target resource download request, the PCDN repeater receives the target resource returned by the target PCDN terminal node and sends the target resource to the client. Alternatively, when the client meets the specific service scenario requirements, it receives the IP address of the PCDN repeater sent by the PCDN server; wherein the PCDN server includes the PCDN repeater and PCDN terminal nodes, and the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; based on the IP address of the PCDN repeater, it sends a target resource request to the PCDN repeater; after the PCDN repeater responds to the target resource request, it receives the target resource sent by the PCDN repeater.

[0123] In another aspect, this application also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program is implemented to perform the PCDN service method provided in the above embodiments. The method includes: when a client meets a specific service scenario requirement, sending the IP address of the PCDN repeater to the client; wherein the specific service scenario requirement is used to characterize that the PCDN terminal node cannot directly provide services to the client; the PCDN repeater responds to a target resource request sent by the client, queries the target PCDN terminal node where the target resource is located, and obtains the Internet Protocol IP address of the target PCDN terminal node; the PCDN repeater initiates a target resource download request to the target PCDN terminal node based on the IP address of the target PCDN terminal node; after the target PCDN terminal node responds to the target resource download request, the PCDN repeater receives the target resource returned by the target PCDN terminal node and sends the target resource to the client. Alternatively, when the client meets the specific service scenario requirements, it receives the IP address of the PCDN repeater sent by the PCDN server; wherein the PCDN server includes the PCDN repeater and PCDN terminal nodes, and the specific service scenario requirements are used to indicate that the PCDN terminal node cannot directly provide services to the client; based on the IP address of the PCDN repeater, it sends a target resource request to the PCDN repeater; after the PCDN repeater responds to the target resource request, it receives the target resource sent by the PCDN repeater.

[0124] The device embodiments described above are merely illustrative. The units described 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 modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0125] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0126] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A PCDN service method, characterized by, The PCDN server includes a PCDN relay and a PCDN terminal node. The PCDN service method includes: When the client meets a specific service scenario requirement, the IP address of the PCDN relay is sent to the client; wherein the specific service scenario requirement is used to represent that the PCDN terminal node cannot directly provide services to the client; The PCDN relay queries a target PCDN terminal node where a target resource is located in response to a target resource application request sent by the client, and obtains an Internet Protocol (IP) address of the target PCDN terminal node; The PCDN relay initiates a target resource download request to the target PCDN terminal node based on the IP address of the target PCDN terminal node; After the target PCDN terminal node responds to the target resource download request, the PCDN relay receives the target resource returned by the target PCDN terminal node and sends the target resource to the client.

2. The PCDN service method of claim 1, wherein, The PCDN server further includes a PCDN scheduling server. The PCDN service method further includes: When the client does not meet a specific service scenario requirement, the IP address of the PCDN scheduling server is sent to the client; The PCDN scheduling server queries a target PCDN terminal node where a target resource is located in response to a target resource application request sent by the client, obtains an IP address of the target PCDN terminal node, and sends the IP address of the target PCDN terminal node to the client; After the target PCDN terminal node receives a target resource download request sent by the client, the target PCDN terminal node sends the target resource to the client in response to the target resource download request.

3. The PCDN service method of claim 2, wherein, The determination of whether the client meets a specific service scenario requirement or the client does not meet a specific service scenario requirement is made in the following manner: In response to a target service domain name resolution request sent by a local domain name server of the client; If the client has at least one service scenario requirement of requiring free flow service, requiring cross-province service, and not supporting PCDN scheduling dependency, it is determined that the client meets a specific service scenario requirement; If the client does not have at least one service scenario requirement of requiring free flow service, requiring cross-province service, and not supporting PCDN scheduling dependency, it is determined that the client does not meet a specific service scenario requirement.

4. A PCDN service method, characterized by, The PCDN service method applied to a client includes: When the client meets a specific service scenario requirement, the IP address of the PCDN relay sent by the PCDN server is received; wherein the PCDN server includes the PCDN relay and a PCDN terminal node, and the specific service scenario requirement is used to represent that the PCDN terminal node cannot directly provide services to the client; A target resource application request is sent to the PCDN relay based on the IP address of the PCDN relay; After the PCDN relay responds to the target resource application request, the target resource sent by the PCDN relay is received.

5. The PCDN service method of claim 4, wherein, The PCDN server further comprises a PCDN scheduling server and a PCDN terminal node; The PCDN service method further comprises: When the client does not meet the specific service scenario requirement, the IP address of the PCDN scheduling server sent by the PCDN server is received; Based on the IP address of the PCDN scheduling server, a target resource application request is sent to the PCDN scheduling server; After the PCDN scheduling server responds to the target resource application request, the IP address of a target PCDN terminal node where the target resource is located is received, which is sent by the PCDN scheduling server; Based on the IP address of the target PCDN terminal node, a target resource download request is sent to the target PCDN terminal node; After the target PCDN terminal node responds to the target resource application request, the target resource sent by the target PCDN terminal node is received.

6. A PCDN service apparatus characterized by comprising: The PCDN service device is deployed in a PCDN server, and the PCDN server comprises a PCDN relay and a PCDN terminal node; The PCDN service device comprises: An address sending module is configured to send the IP address of the PCDN relay to the client when the client meets a specific service scenario requirement; wherein the specific service scenario requirement is used to represent that the PCDN terminal node cannot directly provide services to the client; An address query module is configured to query a target PCDN terminal node where a target resource is located, and obtain the IP address of the target PCDN terminal node, in response to the target resource application request sent by the client; A resource download request sending module is configured to initiate a target resource download request to the target PCDN terminal node based on the IP address of the target PCDN terminal node; A resource sending module is configured to receive the target resource returned by the target PCDN terminal node, and send the target resource to the client, after the target PCDN terminal node responds to the target resource download request.

7. A PCDN service apparatus characterized by comprising: The PCDN service device is deployed in a client, and the PCDN service device comprises: An address receiving module is configured to receive the IP address of the PCDN relay sent by the PCDN server when the client meets a specific service scenario requirement; wherein the PCDN server comprises the PCDN relay and a PCDN terminal node, and the specific service scenario requirement is used to represent that the PCDN terminal node cannot directly provide services to the client; A resource download request sending module is configured to send a target resource application request to the PCDN relay based on the IP address of the PCDN relay; A resource receiving module is configured to receive the target resource sent by the PCDN relay after the PCDN relay responds to the target resource application request.

8. A service system characterized by comprising: The service system comprises a client, a PCDN server and a CDN server, the PCDN server comprises a PCDN relay and a PCDN terminal node; The client is configured to send a target service domain name resolution request directed to the CDN server to the CDN server; The CDN server is configured to, in response to the target service domain name resolution request directed to the CDN server sent by the client, send a target service domain name resolution request directed to the PCDN server to the client if the target service domain name opens a PCDN distribution service; The client is configured to receive the target service domain name resolution request directed to the PCDN server sent by the CDN server, and send a target service domain name resolution request directed to the PCDN server to the PCDN server; The PCDN server is configured to, in response to the target service domain name resolution request directed to the PCDN server sent by the client, determine that the client meets a specific service scenario requirement, and send an IP address of the PCDN relay to the client; wherein the specific service scenario requirement is used to represent that the PCDN terminal node cannot directly provide services to the client; The client is configured to receive the IP address of the PCDN relay sent by the PCDN server, and send a target resource application request to the PCDN relay based on the IP address of the PCDN relay; The PCDN server is configured to: the PCDN relay, in response to the target resource application request sent by the client, queries a target PCDN terminal node where a target resource is located, obtains an IP address of the target PCDN terminal node, initiates a target resource download request to the target PCDN terminal node based on the IP address of the target PCDN terminal node, and after the target PCDN terminal node responds to the target resource download request, receives the target resource returned by the target PCDN terminal node, and sends the target resource to the client; The client is configured to receive the target resource sent by the PCDN relay after the PCDN relay responds to the target resource application request.

9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein, The processor executes the computer program to implement the steps of the PCDN service method according to any one of claims 1 to 5.

10. A non-transitory computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the PCDN service method according to any one of claims 1 to 5.

11. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the PCDN service method according to any one of claims 1 to 5.

Images