CDN scheduling method, access device, CDN scheduler and storage medium

The CDN scheduling method improves CDN scheduling accuracy and user device access speed by using CDN edge node identifiers to identify and allocate CDN edge nodes, addressing the inaccuracies and slow responses caused by IP address uncertainties.

CN113949740BActive Publication Date: 2024-12-10ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010612513.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-06-29
Publication Date
2024-12-10
Estimated Expiration
2040-06-29

AI Technical Summary

Technical Problem

CDN schedulers face challenges in accurately obtaining user device IP addresses due to security risks and network fluctuations, leading to reduced scheduling accuracy and slow response times when accessing network content.

Method used

A CDN scheduling method that uses a CDN edge node identifier instead of IP addresses, allowing for precise identification and allocation of CDN edge nodes, improving scheduling accuracy and response speed by confirming the corresponding CDN edge node through the CDN edge node identifier.

Benefits of technology

Enhances CDN scheduling accuracy and user device access speed by utilizing CDN edge node identifiers, ensuring faster and more reliable content delivery.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113949740B_ABST
    Figure CN113949740B_ABST
Patent Text Reader

Abstract

The present invention discloses a CDN scheduling method, access device, CDN scheduler and storage medium. The CDN scheduling method receives a request message from a user equipment UE, obtains a CDN edge node identifier, the CDN edge node identifier is used to confirm the CDN edge node corresponding to the UE, adds the CDN edge node identifier to the request message, and sends the request message to the CDN scheduler, so that the CDN scheduler allocates the corresponding CDN edge node to the UE according to the CDN edge node identifier, and adds the CDN edge node identifier used to confirm the CDN edge node corresponding to the UE to the request message of the UE, so that after receiving the request message, the CDN scheduler can quickly confirm the CDN edge node corresponding to the UE according to the CDN edge node identifier, and then perform CDN scheduling. Compared with the method of using the UE IP address for CDN scheduling, the CDN scheduling accuracy can be improved and the response speed of user equipment access can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a CDN scheduling method, access equipment, a CDN scheduler and a storage medium. Background Art

[0002] CDN (Content Delivery Network) is a new type of network content service system that relies on CDN edge nodes deployed in various places and is scheduled through a CDN scheduler, allowing users to obtain the required content from the nearest CDN edge node, reducing network congestion, improving the response speed and hit rate of user access, and solving network congestion.

[0003] At present, CDN schedulers generally implement scheduling based on the IP address of the user device. However, in actual situations, due to security risks, it is difficult for the CDN scheduler to accurately obtain the IP address of the user device. When the network fluctuates, the IP address of the user device obtained by the CDN scheduler will have a large error, resulting in reduced accuracy of CDN scheduling. User devices are prone to slow response when accessing network content. Summary of the invention

[0004] The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

[0005] The embodiments of the present invention provide a CDN scheduling method, an access device, a CDN scheduler and a storage medium, which can improve the accuracy of CDN scheduling and improve the response speed of user device access.

[0006] In a first aspect, an embodiment of the present invention provides a content delivery network CDN scheduling method, comprising:

[0007] Receiving a request message from a user equipment UE;

[0008] Obtaining a CDN edge node identifier, where the CDN edge node identifier is used to identify a CDN edge node corresponding to the UE;

[0009] The CDN edge node identifier is added to the request message, and the request message is sent to the CDN scheduler, so that the CDN scheduler allocates a corresponding CDN edge node to the UE according to the CDN edge node identifier.

[0010] In a second aspect, an embodiment of the present invention further provides a CDN scheduling method, including:

[0011] Receive a request message, where the request message carries a CDN edge node identifier;

[0012] Confirming the CDN edge node corresponding to the UE according to the CDN edge node identifier;

[0013] The CDN edge node is allocated to the UE.

[0014] In a third aspect, an embodiment of the present invention further provides an access device, comprising at least one processor and a memory for communicating with the at least one processor; the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the CDN scheduling method as described in the first aspect.

[0015] In a fourth aspect, an embodiment of the present invention further provides a CDN scheduler, comprising at least one processor and a memory for communicating with the at least one processor; the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the CDN scheduling method as described in the second aspect.

[0016] In a fifth aspect, an embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the CDN scheduling method described in the first aspect or the second aspect.

[0017] An embodiment of the present invention includes: receiving a request message from a user equipment UE, obtaining a CDN edge node identifier, wherein the CDN edge node identifier is used to confirm the CDN edge node corresponding to the UE, adding the CDN edge node identifier to the request message, and sending the request message to a CDN scheduler, so that the CDN scheduler allocates the corresponding CDN edge node to the UE according to the CDN edge node identifier, and by adding the CDN edge node identifier used to confirm the CDN edge node corresponding to the UE to the request message of the UE, the CDN scheduler can quickly confirm the CDN edge node corresponding to the UE according to the CDN edge node identifier after receiving the request message, and then perform CDN scheduling. Compared with the method of performing CDN scheduling using the IP address of the UE, the accuracy of CDN scheduling can be improved, and the response speed of user equipment access can be improved.

[0018] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings are used to provide a further understanding of the technical solution of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the technical solution of the present invention and do not constitute a limitation on the technical solution of the present invention.

[0020] Figure 1 It is a schematic diagram of CDN scheduling in the prior art provided by an embodiment of the present invention;

[0021] Figure 2 This is a CDN scheduling networking diagram provided by an embodiment of the present invention;

[0022] Figure 3 is a flow chart of a CDN scheduling method applied to an access device provided by an embodiment of the present invention;

[0023] Figure 4 It is a schematic diagram of the message structure of a TCP message provided by an embodiment of the present invention;

[0024] Figure 5 is a flow chart of a CDN scheduling method applied to a CDN scheduler provided by an embodiment of the present invention;

[0025] Figure 6 It is a flowchart of specific steps for allocating a CDN edge node to a UE provided by an embodiment of the present invention;

[0026] Figure 7 is a flow chart of a specific example of a CDN scheduling method provided by an embodiment of the present invention;

[0027] Figure 8 It is a flow chart of a set-top box acquiring a video stream when the OLT determines through a distribution table that there is an IP address of a CDN edge node corresponding to the set-top box, provided by another embodiment of the present invention;

[0028] Fig. 9 is a structural diagram of an access device provided by an embodiment of the present invention;

[0029] Fig.10 It is a structural diagram of a CDN scheduler provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0031] It should be understood that in the description of the embodiments of the present invention, the meaning of multiple (or multiple) is more than two, greater than, less than, and exceeding are understood to exclude the number itself, and above, below, and within are understood to include the number itself. If there is a description of "first", "second", etc., it is only used for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

[0032] At present, CDN schedulers generally implement scheduling based on the IP address of the user device. One situation is that there is a CDN edge node nearby the user device, but it is difficult for the scheduler to accurately obtain the IP address of the user device, which leads to reduced accuracy of CDN scheduling. The user device is prone to slow response when accessing network content.

[0033] Another situation is that the user device does not have a nearby CDN edge node. Figure 1 , is a schematic diagram of CDN scheduling in the prior art provided by an embodiment of the present invention, wherein the UE sends a request message to the CDN scheduler, and after confirmation, the scheduler returns a 302 response to the user equipment, instructing the user equipment to obtain the video stream from the CDN upper node. However, when the user equipment is far away from the CDN upper node, a slow response speed may also occur when accessing network content.

[0034] User equipment UE is a device that can be installed with various communication applications or has communication functions, such as smart phones, tablet computers, PCs, various wearable devices (earphones, watches, etc.), vehicle-mounted devices, and set-top boxes.

[0035] Based on this, the embodiments of the present invention provide a CDN scheduling method, an access device, a CDN scheduler and a storage medium, which can improve the accuracy of CDN scheduling and improve the response speed of user device access.

[0036] Reference Figure 2 , is a CDN scheduling networking diagram provided by an embodiment of the present invention, in which the CDN edge node is deployed on the access device OLT, the OLT is connected to the CDN scheduler through the broadband access server, the CDN edge node is connected to the CDN upper node, the UE sends a scheduling request to the CDN scheduler through the OLT, the CDN scheduler sends a scheduling indication to the UE through the OLT, and the UE accesses the corresponding CDN edge node according to the scheduling indication. Figure 1 The CDN scheduling network diagram is shown below. The principle of the CDN scheduling method according to the embodiment of the present invention is described in detail below.

[0037] Reference Figure 3 The embodiment of the present invention provides a CDN scheduling method, which is applied to an access device, wherein for Figure 2For the CDN scheduling networking diagram shown, the access device is the OLT accessed by the UE. In fact, in other networking architectures, the access device can also be a PON or other device. The CDN scheduling method includes but is not limited to the following steps 301 to 303:

[0038] Step 301: receiving a request message from a UE;

[0039] In one embodiment, the content of the request message in the UE may be video on demand. For example, taking the UE as a personal computer as an example, before the UE performs video on demand, the UE may first obtain an IP address through PPPOE dial-up or DHCP to connect to the Internet, and then perform video on demand. Before the video is played on demand, a handshake connection is first performed with the CDN scheduler through a request message. After the connection is confirmed, the CDN scheduler will subsequently perform CDN scheduling on the UE and allocate a suitable CDN edge node to the UE.

[0040] In one embodiment, the UE may perform a TCP handshake connection with the CDN, that is, the request message may be a TCP message.

[0041] Step 302: Obtain a CDN edge node identifier, where the CDN edge node identifier is used to identify the CDN edge node corresponding to the UE;

[0042] In one embodiment, the CDN edge node identifier is used to confirm the CDN edge node corresponding to the UE, that is, the CDN edge node to which the UE should be assigned can be obtained through the CDN edge identifier, without performing CDN scheduling according to the IP address of the UE.

[0043] Step 303: Add the CDN edge node identifier to the request message, and send the request message to the CDN scheduler, so that the CDN scheduler allocates the corresponding CDN edge node to the UE according to the CDN edge node identifier.

[0044] In one embodiment, when the request message is a TCP message, when the CDN edge node identifier is added to the request message, the CDN edge node identifier may be filled in the extension field of the TCP message. Figure 4 , the extended field may be the Urgent point field of the TCP message. It is understandable that the extended field is not limited to the UrgentPointer field, and other reserved fields of the TCP message may also be used according to actual conditions.

[0045] By adding the CDN edge node identifier used to confirm the CDN edge node corresponding to the UE to the UE's request message, the CDN scheduler can quickly confirm the CDN edge node corresponding to the UE according to the CDN edge node identifier after receiving the request message, and then perform CDN scheduling. Compared with the method of using the UE's IP address for CDN scheduling, the accuracy of CDN scheduling can be improved, and the response speed of user device access can be improved. Figure 2 As shown, if the UE does not send a scheduling request including a CDN edge node identifier to the OLT, it can only obtain the corresponding service content from the CDN upper node, or perform CDN scheduling through a scheduling algorithm in the prior art.

[0046] In one embodiment, the above-mentioned CDN edge node identifier can be an IP address of the CDN edge node. Based on this, in the above-mentioned step 302, the CDN edge node identifier is obtained. Specifically, the CDN edge node identifier of the first CDN edge node corresponding to the UE can be obtained according to the preset CDN edge node allocation information. At this time, the CDN edge node identifier of the first CDN edge node is the first IP address of the first CDN edge node.

[0047] Exemplarily, the allocation information of the preset CDN edge node can be an allocation table between the preset CDN edge node and the UE, and the allocation table stores the correspondence between the first CDN edge node and the UE. For example, UE1, UE2 and UE3 correspond to the first CDN edge node. When the request message is sent by UE1, the CDN edge node corresponding to UE1 can be found through the allocation table. The IP address of the first CDN edge node is identified, and therefore the first CDN edge node should be allocated to UE1. It can be understood that in actual networking, the number of UEs can be large, and the number of CDN edge nodes can also be large. The embodiments of the present invention are only exemplary.

[0048] In one embodiment, when the allocation table between the CDN edge node and the UE is preset, the allocation relationship can be determined according to the positional relationship between the UE and the CDN edge node during network planning. For example, when the UE is a set-top box, the allocation can be made according to the installation address of the set-top box and the address of the CDN edge node, and the first CDN edge node closest to the set-top box is selected to correspond to it; or, the allocation can be made according to the address of the OLT connected to the UE and the address of the CDN edge node during network planning, and the first CDN edge node closest to the OLT is selected to correspond to it; or, the network operator can plan the specific allocation relationship according to the actual situation, and the embodiment of the present invention does not limit it.

[0049] In one embodiment, the CDN edge node identifier may also be information that can uniquely identify the CDN edge node, such as a MAC address of the CDN edge node.

[0050] In one embodiment, the CDN edge node identifier of the first CDN edge node corresponding to the UE can be obtained according to the preset allocation information of the CDN edge node in at least the following four ways:

[0051] The first method is to obtain the correspondence between the UE preset locally and the first CDN edge node, and obtain the CDN edge node identifier of the first CDN edge node corresponding to the UE according to the correspondence. Taking the access device as OLT as an example, when the OLT receives the request message from the UE, it obtains the correspondence between the UE preset locally and the first CDN edge node. The correspondence has been explained above, and it can be a distribution table between the preset CDN edge node and the UE. The CDN edge node identifier of the corresponding first CDN edge node is obtained through the distribution table, which can be matched by the UE identifier of the UE. The UE identifier can be a serial number, MAC address, and other information that can uniquely identify the UE, depending on which one is used as the UE identifier when the distribution table is preset. In this way, the distribution table between the CDN edge node and the UE is stored locally in the OLT, and obtaining the CDN edge node identifier of the corresponding first CDN edge node according to the UE is also completed locally in the OLT.

[0052] The second method is to obtain the correspondence between the UE preset in the cloud server and the first CDN edge node, and obtain the CDN edge node identifier of the first CDN edge node corresponding to the UE according to the correspondence. Also, taking the access device as OLT as an example, when the OLT receives the request message of the UE, it obtains the correspondence between the UE preset in the cloud server and the first CDN edge node. The correspondence has been explained above, and it can be a preset allocation table between the CDN edge node and the UE, and the CDN edge node identifier of the corresponding first CDN edge node is obtained through the allocation table. It can also be matched through the UE identifier of the UE. The UE identifier can be a serial number, MAC address, and other information that can uniquely identify the UE, depending on which one is used as the UE identifier when the allocation table is preset. In this method, the allocation table between the CDN edge node and the UE is stored in the cloud server, and the OLT first obtains the allocation table from the cloud server, and then obtains the CDN edge node identifier of the corresponding first CDN edge node locally according to the UE. Compared with the first method, this method can save the local storage space of the OLT.

[0053] The third method is to send the UE identifier of the UE to the cloud server, and obtain the CDN edge node identifier of the first CDN edge node corresponding to the UE identifier from the cloud server. Similar to the second method, the allocation table between the CDN edge node and the UE is stored in the cloud server. The difference between this method and the second method is that in this method, obtaining the CDN edge node identifier of the corresponding first CDN edge node according to the UE is also completed on the cloud server, that is, the OLT directly obtains the CDN edge node identifier of the corresponding first CDN edge node from the cloud server. Compared with the second method, since obtaining the CDN edge node identifier of the corresponding first CDN edge node according to the UE is also completed on the cloud server, the resources of the OLT can be saved.

[0054] The fourth method is to obtain the correspondence between the access device accessed by the preset UE and the first CDN edge node, and obtain the CDN edge node identifier of the first CDN edge node corresponding to the access device. Different from the above three methods, the allocation table in this method stores the correspondence between the access device accessed by the UE and the first CDN edge node, that is, all UEs accessing the same OLT correspond to the first CDN edge node. The advantage of this method is that the corresponding relationship between the UE and the first CDN edge node is established through the access device, which can simplify the allocation table of the correspondence between the UE and the first CDN edge node. It can be understood that this method mainly changes the content of the allocation table. When using this method, the above three methods can also be referred to. For example, the allocation table of the first method is stored locally, and the matching first CDN edge node is also locally; the allocation table of the second method is stored in the cloud server, and the matching first CDN edge node is locally; the allocation table in the third method is stored in the cloud server, and the matching first CDN edge node is also in the cloud server.

[0055] In one embodiment, the CDN edge node identifier may also be the second IP address of the access device to which the UE is connected. Based on this, in the step 302 above, the CDN edge node identifier is obtained. Specifically, the second IP address of the access device to which the UE is connected may be obtained, and the second IP address is used as the CDN edge node identifier.

[0056] Among them, since the second IP address of the access device accessed by the UE is generally fixed and can be obtained through network topology and other methods, the CDN edge node corresponding to the UE is confirmed based on the second IP address of the access device accessed by the UE. Compared with the existing method of CDN scheduling through the UE's IP address, it can also improve the accuracy of CDN scheduling and improve the response speed of user device access.

[0057] Reference Figure 5The embodiment of the present invention provides a CDN scheduling method, which is applied to a CDN scheduler. The CDN scheduling method includes but is not limited to the following steps 501 to 503:

[0058] Step 501: receiving a request message, where the request message carries a CDN edge node identifier;

[0059] Step 502: confirming the CDN edge node corresponding to the UE according to the CDN edge node identifier;

[0060] Step 503: Allocate the CDN edge node to the UE.

[0061] After receiving the request message carrying the CDN edge node identifier, the CDN scheduler quickly confirms the CDN edge node corresponding to the UE based on the CDN edge node identifier, and then performs CDN scheduling. Compared with the method of using the UE's IP address for CDN scheduling, this can improve the accuracy of CDN scheduling and increase the response speed of user device access.

[0062] In one embodiment, when the CDN edge node identifier is the IP address of the CDN edge node, taking the first CDN edge node as an example, that is, when the CDN edge node identifier is the first IP address of the first CDN edge node, in the above step 402, the CDN edge node corresponding to the UE is confirmed according to the CDN edge node identifier, and specifically, the first CDN edge node corresponding to the UE can be confirmed using the CDN edge node identifier according to the preset CDN edge node allocation information. The preset CDN edge node allocation information has been explained above and will not be repeated here.

[0063] Similarly, the CDN scheduler uses the CDN edge node identifier to confirm the first CDN edge node corresponding to the UE. There can also be four ways. For example, the allocation table of the first method is stored locally, and the corresponding first CDN edge node is also locally; the allocation table of the second method is stored in the cloud server, and the corresponding first CDN edge node is locally; the allocation table in the third method is stored in the cloud server, and the corresponding first CDN edge node is also in the cloud server; the fourth method is to confirm the first CDN edge node through the correspondence between the access device accessed by the UE and the first CDN edge node; the detailed explanation has been given above and will not be repeated here.

[0064] In one embodiment, referring to Figure 6 In the above step 503, allocating a CDN edge node to the UE may specifically include the following steps 601 to 604:

[0065] Step 601: Query the load of the first CDN edge node;

[0066] Step 602: Determine whether the load of the first CDN edge node is lower than a preset threshold. If so, jump to step 503; otherwise, jump to step 504;

[0067] Step 603: Allocate the first CDN edge node to the UE, and end the process;

[0068] Step 604: Allocate the second CDN edge node closest to the first CDN edge node to the UE, and end the process.

[0069] Among them, by judging whether the load of the first CDN edge node is lower than the preset threshold, it is ensured that the UE can have a better user experience after CDN scheduling. When the load of the first CDN edge node is high, allocating the first CDN edge node to the UE may cause the UE to freeze when using the service due to congestion problems, and even affect the use of other UEs accessing the first CDN edge node. Exemplarily, the preset threshold can be 70%, 75%, 80%, etc. It can be understood that the preset threshold can be set according to the actual situation, and the embodiment of the present invention does not limit it.

[0070] In one embodiment, if the load of the second CDN edge node closest to the first CDN edge node is also less than a preset threshold, another CDN edge node that is next closest to the first CDN edge node may be selected again, and so on, until the load meets the requirement.

[0071] In one embodiment, in the above step 504, the second CDN edge node closest to the first CDN edge node is allocated to the UE. Specifically, the second CDN edge node closest to the first CDN edge node can be determined according to the network topology, and the second CDN edge node can be allocated to the UE. For example, the routing path between the first CDN edge node and other CDN edge nodes can be obtained through the network topology, and the second CDN edge node with the shortest routing path to the first CDN edge node is found.

[0072] In one embodiment, in the above step 504, the second CDN edge node closest to the first CDN edge node is allocated to the UE. Specifically, the second CDN edge node closest to the first CDN edge node can be determined based on the geographical location, and the second CDN edge node can be allocated to the UE. For example, the physical distance between the first CDN edge node and other CDN edge nodes can be obtained through the actual address of the first CDN edge node, and the second CDN edge node with the shortest physical distance to the first CDN edge node is found.

[0073] In one embodiment, when the CDN edge node identifier is the second IP address of the access device to which the UE accesses, for example, the second IP address of the OLT to which the UE accesses, in the above step 402, the CDN edge node corresponding to the UE is confirmed according to the CDN edge node identifier, and specifically, the third CDN edge node closest to the access device can also be confirmed according to the second IP address.

[0074] In one embodiment, the third CDN edge node corresponding to the access device is confirmed based on the second IP address, and the third CDN edge node corresponding to the second IP address can be allocated based on the IP range where the second IP address is located and the correspondence between the IP range and the CDN edge node in the previous network planning. Exemplarily, the second IP address can be the management IP address of the access device.

[0075] In one embodiment, the third CDN edge node corresponding to the access device is confirmed according to the second IP address, and the third CDN edge node corresponding to the second IP address can also be allocated according to the second IP address using a scheduling algorithm.

[0076] The following is an actual example to illustrate the CDN scheduling method of the embodiment of the present invention. The user UE is an example of a set-top box. Figure 7 , specifically including the following steps 701 to 710:

[0077] Step 701: OLT receives a TCP scheduling request message from a set-top box;

[0078] Step 702: The OLT determines whether there is an IP address of a CDN edge node corresponding to the set-top box through the allocation table. If there is an IP address of a CDN edge node corresponding to the set-top box locally, the process jumps to step 703; otherwise, the process jumps to step 704;

[0079] Step 703: The OLT fills the IP address of the CDN edge node corresponding to the set-top box into the Urgrent Point field in the TCP scheduling request message, and adaptively modifies the TCP Checksum field in the IP header, sends the TCP scheduling request message to the CDN scheduler, and jumps to step 705;

[0080] Step 704: the OLT obtains its own management IP address, fills the management IP address of the OLT into the Urgrent Pointer field in the TCP scheduling request message, and adaptively modifies the TCP Checksum field in the IP header, sends the TCP scheduling request message to the CDN scheduler, and jumps to step 705;

[0081] Step 705: The CDN scheduler receives the TCP scheduling request message and extracts the IP address in the Urgrent Pointer field;

[0082] Step 706: The CDN scheduler determines whether the IP address is the IP address of a CDN edge node. If so, jump to step 707; otherwise, jump to step 708;

[0083] Step 707: The CDN scheduler confirms the CDN edge node corresponding to the set-top box according to the IP address of the CDN edge node, and jumps to step 710;

[0084] Step 708: The CDN scheduler determines whether the IP address is the management IP address of the OLT. If so, jump to step 709; otherwise, jump to step 713;

[0085] Step 709: The CDN scheduler confirms the CDN edge node corresponding to the set-top box according to the IP range of the management IP address of the OLT and the correspondence between the IP range and the CDN edge node in the previous network planning;

[0086] Step 710: The CDN scheduler determines whether the load of the CDN edge node is lower than a preset threshold. If so, jump to step 711; otherwise, jump to step 712;

[0087] Step 711: The CDN scheduler allocates the CDN edge node to the set-top box to complete CDN scheduling;

[0088] Step 712: The CDN scheduler allocates another CDN edge node that is closest to the CDN edge node to the set-top box, completing CDN scheduling;

[0089] Step 713: The CDN scheduler performs CDN scheduling according to the IP address of the set-top box.

[0090] In the above steps 701 to 713, after receiving the TCP scheduling request message from the set-top box, the OLT first determines whether there is an IP address of the CDN edge node corresponding to the set-top box, and then chooses to fill in the IP address of the CDN edge node or its own management IP address into the TCP scheduling request message; after receiving the TCP scheduling request message filled with the IP address of the CDN edge node or the management IP address of the OLT itself, the CDN scheduler confirms whether the IP address is the IP address of a CDN edge node or the management IP address of the OLT, and then selects the corresponding scheduling method. Compared with the method of using the UE's IP address for CDN scheduling, the accuracy of CDN scheduling can be improved, the response speed of user equipment access can be improved, and the stability and reliability of scheduling can be effectively improved.

[0091] In step 713, if the CDN scheduler cannot confirm that the IP address is the IP address of a CDN edge node or the management IP address of the OLT, CDN scheduling can only be performed based on the IP address of the set-top box to at least ensure the success of this scheduling.

[0092] Reference Figure 8 , Figure 8 The process of a set-top box obtaining a video stream when the OLT determines through the allocation table that there is an IP address of a CDN edge node corresponding to the set-top box is shown. In one embodiment, after the CDN scheduler allocates the corresponding CDN edge node to the set-top box, if the CDN edge node does not have the corresponding content of the service request, the CDN edge node can obtain the corresponding content from its CDN upper node and then provide it to the set-top box.

[0093] It should also be understood that the various implementations provided in the embodiments of the present invention can be combined arbitrarily to achieve different technical effects.

[0094] Fig. 9 The embodiment of the present invention provides an access device 900 provided by the embodiment of the present invention. The access device 900 includes: a memory 901, a processor 902, and a computer program stored in the memory 901 and executable on the processor 902. When the computer program is executed, it is used to execute the above CDN scheduling method.

[0095] The processor 902 and the memory 901 may be connected via a bus or other means.

[0096] The memory 901 is a non-transient computer-readable storage medium that can be used to store non-transient software programs and non-transient computer executable programs, such as the CDN scheduling method described in the embodiment of the present invention. The processor 902 implements the above-mentioned CDN scheduling method by running the non-transient software programs and instructions stored in the memory 901.

[0097] The memory 901 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store and execute the above-mentioned CDN scheduling method. In addition, the memory 901 may include a high-speed random access memory 901, and may also include a non-volatile memory 901, such as at least one disk memory 901 piece, a flash memory device or other non-volatile solid-state memory 901 piece. In some embodiments, the memory 901 may optionally include a memory 901 remotely arranged relative to the processor 902, and these remote memories 901 may be connected to the access device 900 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0098] The non-transient software programs and instructions required to implement the above CDN scheduling method are stored in the memory 901. When executed by one or more processors 902, the above CDN scheduling method is executed, for example, Figure 3 Method steps 301 to 303 in.

[0099] Fig.10 The CDN scheduler 1000 provided by the embodiment of the present invention is shown. The CDN scheduler 1000 includes: a memory 1001, a processor 1002, and a computer program stored in the memory 1001 and executable on the processor 1002. When the computer program is executed, it is used to execute the above CDN scheduling method.

[0100] The processor 1002 and the memory 1001 may be connected via a bus or other means.

[0101] The memory 1001 is a non-transient computer-readable storage medium that can be used to store non-transient software programs and non-transient computer executable programs, such as the CDN scheduling method described in the embodiment of the present invention. The processor 1002 implements the above-mentioned CDN scheduling method by running the non-transient software programs and instructions stored in the memory 1001.

[0102] The memory 1001 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store and execute the above-mentioned CDN scheduling method. In addition, the memory 1001 may include a high-speed random access memory 1001, and may also include a non-volatile memory 1001, such as at least one disk memory 1001, a flash memory device or other non-volatile solid-state memory 1001. In some embodiments, the memory 1001 may optionally include a memory 1001 remotely arranged relative to the processor 1002, and these remote memories 1001 may be connected to the CDN scheduler 1000 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0103] The non-transient software programs and instructions required to implement the above CDN scheduling method are stored in the memory 1001. When executed by one or more processors 1002, the above CDN scheduling method is executed, for example, Figure 5 Steps 501 to 503 of the method, Figure 6 Method steps 601 to 604.

[0104] The embodiment of the present invention further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the above-mentioned CDN scheduling method.

[0105] In one embodiment, the computer-readable storage medium stores computer-executable instructions, which are executed by one or more control processors 1002, for example, by one processor 1002 in the CDN scheduler 1000, so that the one or more processors 1002 can execute the CDN scheduling method, for example, Figure 3 Steps 301 to 303 of the method, Figure 5 Steps 501 to 503 of the method, Figure 6 Steps 601 to 604 of the method, Figure 7 Method steps 701 to 713 in.

[0106] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0107] It will be appreciated by those skilled in the art that all or some of the steps and systems in the disclosed method above may be implemented as software, firmware, hardware and appropriate combinations thereof. Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or may be implemented as hardware, or may be implemented as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or a non-transitory medium) and a communication medium (or a temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory 1001 technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, magnetic tape, disk storage or other magnetic storage device, or any other medium that may be used to store desired information and may be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically include computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0108] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above-mentioned implementation mode. Technical personnel familiar with the field can also make various equivalent deformations or substitutions under the shared conditions without violating the spirit of the present invention. These equivalent deformations or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. A content distribution network CDN scheduling method, include: Receiving a request message from a user equipment UE; Determine whether there is a CDN edge node identifier corresponding to the UE; If there is a CDN edge node identifier corresponding to the UE, obtain the CDN edge node identifier corresponding to the UE, and add the CDN edge node identifier to the request message; and sending the request message to a CDN scheduler, so that the CDN scheduler allocates a corresponding CDN edge node to the UE according to the CDN edge node identifier; If there is no CDN edge node identifier corresponding to the UE, obtain the management IP address of the access device to which the UE is connected, and fill the management IP address into the request message; And the request message is sent to the CDN scheduler, so that the CDN scheduler allocates the corresponding CDN edge node to the UE according to the management IP address.

2. The CDN scheduling method according to claim 1, It is characterized in that The obtaining of the CDN edge node identifier corresponding to the UE includes: According to the preset allocation information of the CDN edge node, a CDN edge node identifier of a first CDN edge node corresponding to the UE is acquired.

3. The CDN scheduling method according to claim 2, It is characterized in that The acquiring, according to the preset allocation information of the CDN edge node, the CDN edge node identifier of the first CDN edge node corresponding to the UE comprises one of the following: Acquire a correspondence relationship between the UE and the first CDN edge node preset locally, and acquire a CDN edge node identifier of the first CDN edge node corresponding to the UE according to the correspondence relationship; Acquire a correspondence between the UE and a first CDN edge node preset in a cloud server, and acquire a CDN edge node identifier of the first CDN edge node corresponding to the UE according to the correspondence; Sending the UE identifier of the UE to the cloud server, and obtaining the CDN edge node identifier of the first CDN edge node corresponding to the UE identifier from the cloud server; A preset correspondence between an access device accessed by the UE and a first CDN edge node is obtained, and a CDN edge node identifier of the first CDN edge node corresponding to the access device is obtained.

4. The CDN scheduling method according to claim 3, Features: The CDN edge node identifier is a first Internet Protocol IP address of the first CDN edge node.

5. The CDN scheduling method according to any one of claims 1 to 4, Features: The request message is a TCP message, and the CDN edge node identifier is configured in an extension field of the TCP message.

6. A CDN scheduling method, include: Receive a request message, where the request message carries a CDN edge node identifier; Determine the type of the CDN edge node identifier; If the type of the CDN edge node identifier is a CDN edge node identifier of a certain CDN edge node, confirming a first CDN edge node corresponding to the UE according to the CDN edge node identifier; If the type of the CDN edge node identifier is the management IP address of the access device, the CDN edge node corresponding to the UE is confirmed according to the IP range of the management IP address of the access device and the correspondence between the IP range and the CDN edge node in the previous network planning; The CDN edge node is allocated to the UE.

7. The CDN scheduling method according to claim 6, It is characterized in that The confirming the first CDN edge node corresponding to the UE according to the CDN edge node identifier includes: According to the preset allocation information of the CDN edge node, the first CDN edge node corresponding to the UE is confirmed by using the CDN edge node identifier.

8. The CDN scheduling method according to claim 6, It is characterized in that The allocating the CDN edge node to the UE includes: Query the load of the first CDN edge node; When the load of the first CDN edge node is lower than a preset threshold, the first CDN edge node is allocated to the UE.

9. The CDN scheduling method according to claim 8, It is characterized in that include: When the load of the first CDN edge node is higher than the preset threshold, a second CDN edge node which is closest to the first CDN edge node is allocated to the UE.

10. The CDN scheduling method according to claim 9, It is characterized in that The allocating to the UE the second CDN edge node which is closest to the first CDN edge node comprises one of the following: Determine a second CDN edge node that is closest to the first CDN edge node according to the network topology, and allocate the second CDN edge node to the UE; A second CDN edge node that is closest to the first CDN edge node is determined according to the geographical location, and the second CDN edge node is allocated to the UE.

11. The CDN scheduling method according to claim 6, It is characterized in that The CDN edge node identifier is a second IP address of an access device accessed by the UE, and the step of confirming the CDN edge node corresponding to the UE according to the CDN edge node identifier includes: A third CDN edge node corresponding to the access device is confirmed according to the second IP address.

12. An access device, Features: At least one processor and a memory for communicating with the at least one processor; the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the CDN scheduling method as described in any one of claims 1 to 5.

13. A CDN scheduler, Features: at least one processor and a memory for communicatively coupling with the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the CDN scheduling method according to any one of claims 6 to 11.