WO2011157173A2 - 路由决策方法、内容分发装置和内容分发网络互连系统 - Google Patents

路由决策方法、内容分发装置和内容分发网络互连系统 Download PDF

Info

Publication number
WO2011157173A2
WO2011157173A2 PCT/CN2011/075300 CN2011075300W WO2011157173A2 WO 2011157173 A2 WO2011157173 A2 WO 2011157173A2 CN 2011075300 W CN2011075300 W CN 2011075300W WO 2011157173 A2 WO2011157173 A2 WO 2011157173A2
Authority
WO
WIPO (PCT)
Prior art keywords
cdn
total
service
current
concurrent
Prior art date
Application number
PCT/CN2011/075300
Other languages
English (en)
French (fr)
Other versions
WO2011157173A3 (zh
Inventor
和晓艳
李金成
王敬
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2011/075300 priority Critical patent/WO2011157173A2/zh
Priority to CN201180000966.XA priority patent/CN102257777B/zh
Publication of WO2011157173A2 publication Critical patent/WO2011157173A2/zh
Publication of WO2011157173A3 publication Critical patent/WO2011157173A3/zh
Priority to US14/095,265 priority patent/US9602378B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/12—Shortest path evaluation
    • H04L45/125—Shortest path evaluation based on throughput or bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1029—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers using data related to the state of servers by a load balancer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/16—Analogue secrecy systems; Analogue subscription systems
    • H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
    • H04N7/17309—Transmission or handling of upstream communications
    • H04N7/17327—Transmission or handling of upstream communications with deferred transmission or handling of upstream communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/16—Analogue secrecy systems; Analogue subscription systems
    • H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
    • H04N7/17309—Transmission or handling of upstream communications
    • H04N7/17336—Handling of requests in head-ends

Definitions

  • Routing decision method for Routing decision method, content distribution device, and content distribution network interconnection system
  • Embodiments of the present invention relate to the field of information technology, and in particular, to a routing decision method, a content distribution apparatus, and a content distribution network interconnection system. Background technique
  • the Content Delivery Network is a layer of network built on the existing Internet.
  • the Content Provider (CP) publishes content to the "edge" of the network closest to the user based on the CDN, so that users can obtain the required content nearby, thereby alleviating backbone congestion and improving response speed.
  • CP tends to sign up with a CDN service provider instead of signing up with multiple CDN service providers. Since any single CDN service provider has limited network coverage and users are dispersed in different regions of the world, it is necessary to interconnect the networks of different CDN service providers to achieve wider use of each other's networks. The coverage area, thus delivering the content of its contracted CP to more end users.
  • CDNs deployed by CDN service providers in different regions can be interconnected via the Internet to form a CDN interconnection system.
  • CDN interconnection system There are usually multiple CDNs in the CDN interconnection system that can serve the same user. These CDNs are interconnected and are the same user who can provide services.
  • DCDN Downstream CDN
  • UCDN Upstream CDN
  • the upstream CDN receives the user request
  • the upstream CDN forwards the user request directly to a downstream CDN that is closer to the user.
  • the upstream CDN forwards the user request to other downstream CDNs that are closer to the user; such repeated attempts are made so that the user can obtain the desired content in the vicinity.
  • the prior art upstream CDN repeats the routing request for the user request to be forwarded.
  • Embodiments of the present invention provide a route decision method, a content distribution apparatus, and a content distribution network interconnection system, which are used to improve routing decision efficiency of an upstream CDN in a content distribution network interconnection system.
  • the embodiment of the invention provides a routing decision method, including:
  • the total service threshold is set by the downstream CDN, and the downstream CDN can be the upstream CDN.
  • the embodiment of the invention further provides another routing decision method, including:
  • the embodiment of the invention further provides a content distribution device, and the content distribution device, as the upstream CDN, includes:
  • a receiving module configured to receive a notification message sent by the downstream CDN, where the notification message is used to determine a determining module, configured to determine the current total service quantity according to the notification message;
  • the embodiment of the present invention further provides another content distribution apparatus, and the content distribution apparatus, as the downstream CDN, includes:
  • a generating module configured to generate a notification message, where the notification message is used to determine that the downstream CDN is a current service total serving service provided by an upstream CDN connected thereto;
  • a sending module configured to send the notification message to the upstream CDN, so that the upstream CDN refers to the current total service quantity, and performs a routing decision on the user request to be forwarded.
  • An embodiment of the present invention further provides a content distribution network interconnection system, including: a first CDN, and a second CDN, respectively, the interconnected upstream CDN and the downstream CDN.
  • the upstream CDN determines, according to the notification message sent by the downstream CDN connected thereto, the current service total amount of the downstream CDN serving the upstream CDN connected thereto, and according to the current service.
  • the downstream CDN that is set by the downstream CDN is the total service threshold that the upstream CDN can provide, and the routing decision is made for the user request to be forwarded, which reduces the probability of forwarding the user request to the downstream CDN that cannot provide the service. Therefore, the accuracy of selecting a downstream CDN for the user to be forwarded is improved, thereby improving routing decision efficiency.
  • FIG. 1 is a flowchart of a route decision method according to Embodiment 1 of the present invention.
  • FIG. 2 is a schematic structural diagram of a CDN interconnection system provided by an application scenario according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a route decision method according to Embodiment 2 of the present invention.
  • FIG. 4 is a schematic diagram of a logical interface model for interworking between upstream and downstream CDNs in an application scenario according to an embodiment of the present invention
  • FIG. 5 is a signaling interaction diagram of a route decision method according to Embodiment 3 of the present invention
  • FIG. 6 is a signaling interaction diagram of a route decision method according to Embodiment 4 of the present invention
  • FIG. 7 is a signaling interaction diagram of a route decision method according to Embodiment 5 of the present invention
  • FIG. 8 is a schematic structural diagram of a content distribution apparatus according to Embodiment 6 of the present invention.
  • FIG. 9 is a schematic structural diagram of a content distribution apparatus according to Embodiment 7 of the present invention.
  • FIG. 10 is a schematic structural diagram of a CDN interconnection system according to Embodiment 8 of the present invention. detailed description
  • FIG. 1 is a flowchart of a route decision method according to Embodiment 1 of the present invention.
  • the execution body of this embodiment may be an upstream CDN in the CDN interconnection system.
  • the routing decision method provided in this embodiment includes:
  • Step 11 Receive a notification message sent by the downstream CDN, where the notification message is used to determine the current service total amount of the downstream CDN serving the upstream CDN connected thereto.
  • Step 12 Determine the current total service quantity according to the notification message.
  • FIG. 2 is a schematic structural diagram of a CDN interconnection system provided by an application scenario according to an embodiment of the present invention.
  • the 11th CDN is interconnected with the 21st CDN, and the 21st CDN and the 31st CDN are interconnected, and the 3 CDNs can serve the user A.
  • the 11th CDN is the downstream CDN with respect to the 21st CDN, and is the downstream CDN interconnected thereto; and the 21st CDN is the upstream CDN with respect to the 11th CDN, And is the upstream CDN interconnected with it.
  • the 11th CDN and the 21st CDN are downstream CDNs respectively with respect to the 31st CDN; 11 CDN and 21st CDN are upstream CDNs; and 21st CDN is a downstream CDN interconnected with the 31st CDN, and 31CDN is an upstream CDN interconnected with the 21st CDN; and so on.
  • the upstream CDN and the downstream CDN described below in the embodiments of the present invention unless otherwise specified, the upstream CDN and the downstream CDN are interconnected, and will not be described below.
  • the system shown in FIG. 2 is only an example, and should not be construed as limiting the technical solutions of the embodiments of the present invention.
  • the upstream CDN determines that the current implementation of the total service is not limited.
  • the upstream CDN may perform statistics and record.
  • the downstream CDN may report and report, and the corresponding CDN records or refreshes the corresponding result. The following two methods are explained separately:
  • Method 1 The upstream CDN itself performs statistics and records.
  • the foregoing notification message may include: reference information used to collect the current total service amount.
  • the upstream CDN can count and record the current total service amount based on the reference information.
  • the reference information may include: identification information, and start indication information or end indication information.
  • the start indication information indicates that: the downstream CDN provides a service for the user that is forwarded by the upstream CDN, and the end indication information indicates that the user request forwarded by the downstream CDN for the upstream CDN ends.
  • the user provides the service.
  • the identifier information includes: a CDN identifier of the downstream CDN, or a forwarding identifier allocated by the upstream CDN to the downstream CDN according to the forwarded user request; the current total service volume includes: a current total number of concurrent requests, the present invention
  • the current total number of concurrent requests described in the embodiment is: The total number of user requests that the downstream CDN currently receives the upstream CDN forwarding.
  • the upstream CDN may perform an add operation or an action on the start indication information for the current concurrent total number of the currently recorded CDNs corresponding to the identifier information.
  • the end indication information performs a decrement operation and refreshes the corresponding result that has been recorded.
  • the reference information may also include: the foregoing identification information and a single traffic, where the single traffic is a user request that the downstream CDN forwards the user for the upstream CDN, and provides traffic for the user; the current service
  • the total amount includes the current concurrent total traffic.
  • the current concurrent total traffic according to the embodiment of the present invention is: the current CDN currently received by the downstream CDN. The sum of the traffic requested by the user.
  • the upstream CDN may perform an operation of increasing or decreasing the single traffic for the current concurrent total traffic of the downstream CDN corresponding to the identifier information, and refresh the current Record the corresponding result.
  • the reference information may further include: a type of protocol used by the downstream CDN to provide a service for the user for a user request currently forwarded by the upstream CDN; and the service total threshold may further include: The current concurrent total request threshold value of the protocol type and/or the current concurrent total traffic threshold.
  • the reference information may further include: a domain name of a content provider of the content requested by the user currently forwarded by the upstream CDN; the service total threshold may further include: the current concurrent content corresponding to each content provider domain name The total number of request thresholds and/or the current concurrent total flow threshold. Then, when the upstream CDN counts the current total number of concurrent requests, the upstream CDN may classify and count the current total number of concurrent requests and/or the current concurrent total traffic according to the protocol type and/or the domain name of the content provider.
  • Method 2 The downstream CDN statistics are up and up. 3 ⁇ 4, the corresponding result is recorded or refreshed by the upstream CDN.
  • the notification message may include: identifier information and the current total service volume; the identifier information includes: a CDN identifier of the downstream CDN, or the upstream CDN is the downstream according to the forwarded user request.
  • the upstream CDN records or refreshes the corresponding result corresponding to the identifier information according to the current total service carried in the notification message.
  • Step 13 Perform routing decision on the user request to be forwarded according to the current service total and the total service threshold; the total service threshold is set by the downstream CDN, and the downstream CDN can be The upper limit of the service provided by the upstream CDN.
  • the current total service amount determined by the upstream CDN may include: the current CDN serving the current concurrent total number of requests and/or the current concurrent total traffic served by the upstream CDN, and may further include: according to the protocol type or content The domain name of the provider, the current total number of concurrent requests for the statistic, and/or the current concurrent total traffic.
  • the service total threshold may include one or a combination of the following: a concurrent total request threshold; a concurrent total traffic threshold; a concurrent total request threshold for each protocol type and/or a concurrent total traffic threshold Value; the total number of concurrent requests for each content provider domain name and/or the concurrent total traffic threshold.
  • the total service threshold can be pre-configured on the upstream CDN.
  • the service total threshold value may be carried in the notification message, and reported by the downstream CDN to the upstream CDN, so that the downstream CDN notifies the upstream CDN in time after the service total threshold value is changed, thereby improving application flexibility.
  • the upstream CDN receives the user request, if there is a downstream CDN in the system that is close to the user requesting the corresponding user, the current CDN and the total service threshold of the downstream CDN recorded by the latest record are used for routing. decision making.
  • the upstream CDN receives the user request, if there is a downstream CDN in the system that is close to the user requesting the corresponding user, the current CDN and the total service threshold of the downstream CDN recorded by the latest record are used for routing. decision making.
  • the upstream CDN may record the current record itself.
  • the total number of concurrent requests is compared with the total number of concurrent request thresholds. If the current total number of concurrent requests is less than the total number of concurrent requests, the user request is forwarded to the downstream CDN; otherwise, The user request is forwarded to the downstream CDN.
  • the upstream CDN may record the current concurrent total traffic recorded by itself. Comparing with the concurrent total traffic threshold, if the current concurrent total traffic is less than the concurrent total traffic threshold, forwarding the user request to the downstream CDN. If the current concurrent total traffic is greater than or equal to the concurrent total traffic threshold, the user request is not forwarded to the downstream CDN.
  • the upstream CDN may provide services for the user corresponding to the user request, and may also select other forwarding paths for the user request.
  • the upstream CDN may perform statistics or classification statistics on the current total number of concurrent requests and the current concurrent total traffic, and perform routing decisions on the routing requests to be forwarded by referring to the statistics to improve routing decisions. Accuracy, thus improving the efficiency of routing decisions.
  • the upstream CDN determines, according to the notification message sent by the downstream CDN, the upstream CDN is the current service total of the service provided by the upstream CDN connected thereto, and according to the current service total.
  • the downstream CDN that is set by the downstream CDN is a total service threshold value that can be provided by the upstream CDN, and performs routing decisions on the user request to be forwarded, and reduces The probability of forwarding the user request to the downstream CDN that cannot provide the service improves the accuracy of selecting the downstream CDN for the user to be forwarded, thereby improving the routing decision efficiency.
  • FIG. 3 is a flowchart of a route decision method according to Embodiment 2 of the present invention.
  • the execution subject of this embodiment may be a downstream CDN in the CDN interconnection system.
  • the routing decision method provided in this embodiment includes:
  • Step 31 Generate a notification message for determining the current total amount of service that the downstream CDN provides for the upstream CDN to which it is connected.
  • the type of the notification message is not limited, and the information carried by the information may include: reference information used to count the total amount of the current service; or, the identification information and the total amount of the current service that have been counted.
  • the technical solutions corresponding to the two different types of parameters carried in the notification message are respectively described as follows: Mode 1: The notification message includes: reference information used to collect the current total service amount.
  • the reference message may include: identification information, and at least one of the following information: start indication information, end indication information, single traffic.
  • the identifier information may include: a CDN identifier of the downstream CDN, or a forwarding identifier allocated by the upstream CDN to the downstream CDN according to the forwarded user request.
  • the start indication information indicates that: the downstream CDN starts to provide services for the user for the user request forwarded by the upstream CDN.
  • the ending indication information indicates that the downstream CDN ends the user request for the upstream CDN, and ends providing services for the user.
  • the single traffic is: the downstream CDN provides traffic for the user for the user request currently forwarded by the upstream CDN.
  • the reference information may further include at least one of the following information: a type of protocol used by the downstream CDN for a user request currently forwarded by the upstream CDN, and a user request for the user to be served by the upstream CDN; The domain name of the content provider that requested the content.
  • the notification message includes: identifier information and the total amount of the current service that has been counted.
  • the identifier information may include: a CDN identifier of the downstream CDN, or a forwarding identifier assigned by the upstream CDN to the downstream CDN according to the forwarded user request.
  • the method further includes: counting the downstream CDN The current total service.
  • the current total service amount may include: a current total number of concurrent requests, and/or, a current concurrent total traffic.
  • the method for the downstream CDN to count the total number of concurrent requests may include: the downstream CDN performs a user operation on the upstream CDN, and when the service is started for the user, performs an operation on the current total number of concurrent requests that are currently recorded, and refreshes the current The corresponding result is recorded; the downstream CDN forwards the user request for the upstream CDN, and when the service is provided to the user, performs a minus 1 operation on the current total number of concurrent requests that have been recorded, and refreshes the corresponding result that has been recorded.
  • the method for collecting the current concurrent total traffic by the downstream CDN may include: when the downstream CDN requests the user to be served by the upstream CDN to start providing services to the user, performing an operation of adding a single traffic to the currently recorded total concurrent total traffic, and refreshing Corresponding result currently recorded; when the downstream CDN provides service to the user for the end of the user request forwarded by the upstream CDN, the operation of reducing the single traffic is performed on the currently recorded total concurrent traffic, and the corresponding recorded current is refreshed. result.
  • the single-time traffic is a user request that is currently forwarded by the upstream CDN, and provides traffic for the user.
  • the type of the protocol used by the user may be provided according to the user request that is currently forwarded by the upstream CDN, and/or the requested content.
  • the domain name of the content provider, the statistics of the current total number of concurrent requests and/or the current total concurrent traffic may be provided according to the user request that is currently forwarded by the upstream CDN, and/or the requested content.
  • the generated notification message may also include: a service total threshold.
  • the service total threshold includes one or any combination of the following: concurrent total request threshold; concurrent total traffic threshold; concurrent total request threshold and/or concurrent total traffic of each protocol type Threshold; the total number of concurrent requests for each content provider domain name and/or the concurrent total traffic threshold.
  • Step 32 Send the notification message to the upstream CDN, so that the upstream CDN refers to the current total service volume, and performs routing decision on the user request to be forwarded.
  • the downstream CDN may choose to meet certain conditions, generate a notification message and send it to the upstream CDN.
  • the timing can be specifically as follows: Timing 1: The time at which the downstream CDN initiates or ends the service to the user for the user request forwarded by the upstream CDN.
  • Timing 1 The time at which the downstream CDN initiates or ends the service to the user for the user request forwarded by the upstream CDN.
  • Timing 2 The preset time period is the preset time of each preset time.
  • the downstream CDN can perform real-time statistics on the current total service amount at the timing, and report the statistical results at the timing of the second timing, which is beneficial to improve the overall performance of the system.
  • the upstream CDN receives the notification message sent by the downstream CDN, determines the current total service quantity according to the notification message, and refers to the current service total quantity, and implements a routing decision for the user request to be forwarded.
  • the description of the examples will not be repeated here.
  • the downstream CDN is generated and sent to the upstream CDN, and includes reference information for collecting the current total service volume, or a notification that includes the identification information and the total amount of the current service that has been counted.
  • the message is forwarded so that the upstream CDN can refer to the current total service amount and perform routing decisions on the user request to be forwarded, thereby improving the accuracy of the upstream CDN to select the downstream CDN for the user to be forwarded, thereby improving the routing decision efficiency.
  • FIG. 4 is a schematic diagram of a logical interface model for interworking between upstream and downstream CDNs in an application scenario according to an embodiment of the present invention. Between the pair of interworking CDNs consisting of the upstream CDN and the downstream CDN, the following interface communication can be used and the definitions of the interfaces are as follows:
  • Interworking Configuration Interface An interface on which the upstream CDN sends a command to the downstream CDN to invalidate the content.
  • the routing protocol (Request Routing Protocol): The upstream CDN forwards the user request to the downstream CDN through the interface; the downstream CDN reports the information required for the routing decision through the interface, and reports the notification message and the like according to the embodiment of the present invention.
  • Metadata Protocol Through this interface, the interworking upstream and downstream CDNs exchange some content distribution policy information, content area information, such as the content is not allowed to be delivered in certain areas, The available time window information of the content, etc.
  • Logging Protocol Through the interface, the upstream and downstream CDNs exchange log information, such as the downstream CDN, report the upstream CDN to the upstream CDN for a certain period of time, instead of the upstream CDN to deliver the content of the traffic to the user. .
  • the interworking upstream and downstream CDNs also include: a delivery node (Delivery Node, DN for short): the interworking upstream and downstream CDNs request related content through the DN interaction user.
  • Delivery Node Delivery Node
  • CDNA and CDNB constitute a pair of interconnected CDNs, and the CDNA is the upstream CDN of the CDNB, and the CDNB is the downstream CDN of the CDNA; the CDNA is far from the user terminal A, The content provider is contracted and is closer to the origin server (Source Server). The CDNB is closer to the user terminal A and farther away from the original server (Origin Server).
  • the CDNA may include: a CDNA routing interface module (CDNA&RR) and a content delivery node (CDNA DN); the CDNB may include: a CDNB routing interface module (CDNB&RR) and a content delivery node (CDNB DN).
  • CDNB&RR CDNB routing interface module
  • CDNB DN content delivery node
  • FIG. 5 is a signaling interaction diagram of a route decision method according to Embodiment 3 of the present invention.
  • the upstream CDN that is, CDNA
  • the downstream CDN that is, the notification message sent by the CDNB.
  • the routing decision method provided in this embodiment includes: Step 51: A domain name server (DNS) sent by the end user (Eend User) to the user equipment (User Equipment, UE for short) to the CDNA&RR Query request (DNS FQDNA).
  • DNS domain name server
  • Step 52 CDNA&RR judges that the UE is served by the CDNB through the user location and other information.
  • CDNA&RR returns its IP address to
  • Step 53 The UE sends an HTTP request (HTTP URLa) to the IP address returned in step 52.
  • the current total service volume of the CDNB is: the current total number of concurrent requests of the CDNB and the current total concurrent traffic.
  • the total service threshold is specifically the total concurrent request threshold and the concurrent total traffic threshold, and the 'J, CDNA&RR
  • Step 55 CDNA&RR returns the URL address (URLb) of CDNB&RR to the UE to notify
  • the UE establishes a connection with the CDNB according to the URL address.
  • Step 56 The UE sends a DNS query request (DNS FQDNB) to the CDNB&RR ⁇ .
  • DNS FQDNB DNS query request
  • Step 57 The CDNB&RR selects a node CDNB DN that is the final delivery content of the UE based on the UE location information, the domain name of the CP requesting the content requested, and returns the IP address of the CDNB DN to the UE.
  • Step 58 The UE sends an HTTP request (HTTP URLb) to the CDNB DN.
  • Step 59 After receiving the HTTP content request, the CDNB DN finds that it does not have the content required by the request, and sends a DNS query request (DNS FQDNA) to CDNA&RR ⁇ .
  • DNS FQDNA DNS query request
  • Step 510 CDNA&RR selects the content delivery node, CDNA DN, and returns the IP address of the CDNA DN to the CDNB DN.
  • Step 511 The CDNB DN sends an HTTP request (HTTP URLa) to the CDNA DN for requesting the content required by the UE for the current user request.
  • HTTP URLa HTTP request
  • Step 512 If the content of the user request of the UE is not saved by the CDDNA DN, the content (Data) required by the UE for the current user request is obtained from the original server of the CP.
  • Step 515 Generate a notification message (Notify) when the CDNB DN starts to deliver the content to the UE for the current user request forwarded by the CDNA, which is referred to as a first notification message, and is sent to the CDNB&RR via CDNB&RR.
  • a notification message Notify
  • the CDNA&RR sends the first notification message.
  • step 515 can be performed in parallel with step 514.
  • the first notification message may carry: CDN's CDN identity, start service indication information, and single traffic.
  • the first notification message may also carry at least one of the following information: a type of protocol used by the CDNB to deliver the content to the UE for the current user request forwarded by the CDDNA, such as HTTP, RTP, etc.; the CDNB forwards the user request for the CDNA
  • the domain name of the CP of the content delivered to the UE such as "video.sina.com”.
  • the first notification message may further carry at least one of the following information: a concurrent total request threshold set by the CDNB administrator, a total traffic threshold, a total concurrent request threshold of each protocol type, and Concurrent total traffic threshold, concurrent total request threshold and concurrent total traffic threshold for each content provider domain name.
  • the RTP concurrent total request threshold is 8
  • the HTTP concurrent total request threshold is 20
  • the concurrent total request threshold is 100
  • the concurrent total traffic threshold is 500M
  • the RTP delivery occupies the total concurrent.
  • the traffic threshold is 100M
  • the concurrent total traffic threshold occupied by HTTP delivery is 300M.
  • Step 516 The CDNA&RR receives the first notification message, and records and records the current total service volume of the CDNB according to the first notification message, such as counting the user request that the CDNB forwards for the CDNA, the current total number of concurrent requests for providing the service, and the current concurrent total traffic. And refresh the corresponding results that have been recorded.
  • the CDNA&RR may search for the current total number of concurrent requests and the current concurrent total traffic of the CDN corresponding to the CDN identifier carried in the first notification message, and the current indication information carried in the notification message, for the recorded current
  • the concurrent total number of requests is performed by adding 1 and the single-traffic traffic carried in the first notification message is performed, and the operation of increasing the single-time traffic is performed on the recorded current concurrent total traffic, and the local corresponding recording result is refreshed.
  • CDNA&RR can also be classified according to the protocol type and domain name information carried in the first notification message. Count the current concurrent total requests of CDNB and the current concurrent total traffic. For example: CDNA&RR statistics get CDNB's current total number of concurrent requests is 5, of which 3 are delivered using RSTP protocol type, 2 are delivered using RTP protocol type; 3 are concurrent requests delivered using RSTP protocol type, 2 are The content published by "sina”, one is published by "youtube”, and the corresponding total traffic is classified and counted.
  • Step 517 Generate a notification message (Notify), which is referred to as a second notification message, and send the second notification message to the CDDNA&RR via the CDNB&RR when the CDNB DN forwards the content (Data) to the UE. .
  • Notify a notification message
  • Step 517 Generate a notification message (Notify), which is referred to as a second notification message, and send the second notification message to the CDDNA&RR via the CDNB&RR when the CDNB DN forwards the content (Data) to the UE.
  • the second notification message may carry: a CDN identifier of the CDNB, an end service indication information, and a single traffic.
  • the second notification message may also carry at least one of the following information: a type of protocol used by the CDNB to deliver the content to the UE for the current user request forwarded by the CDDNA, such as HTTP, RTP, etc.; the CDNB forwards the user for the CDNA Request, the domain name of the CP of the content delivered to the UE, such as "video.sina.com".
  • Step 518 The CDNA&RR receives the second notification message, and records and records the current total service volume of the CDNB according to the second notification message, that is, the user request for the CDNB to be forwarded by the CDNB, the current total number of concurrent requests for providing the service, and the current total number of concurrent requests. Traffic, and refresh the corresponding results that have been logged.
  • the CDNA&RR may search for the current total number of concurrent requests and the current total concurrent traffic of the CDN corresponding to the CDN identifier carried in the second notification message, and the ending indication information carried in the second notification message, in the locally recorded data. And performing a decrease operation on the number of the current total concurrent requests that are recorded locally, and performing the operation of reducing the single traffic on the recorded current concurrent total traffic according to the single traffic carried in the second notification message, and refreshing the local The corresponding result has been recorded.
  • the corresponding categorical statistics are also subjected to a corresponding decrease or decrease of the single flow operation, and the corresponding result recorded locally is refreshed.
  • the CDNB sends a notification message to the CDNA, where the notification message carries reference information required for determining the current concurrent total number of requests for the CDNB to provide services for the CDNA and the current concurrent total traffic, according to which the CDNB refers.
  • Information statistics and refresh the corresponding local records As a result, the routing decision is made according to the latest result of the local record, and the probability of forwarding the user request to the downstream CDN that cannot provide the service is reduced, and the accuracy of the routing decision is improved, thereby improving the routing decision efficiency.
  • FIG. 6 is a signaling interaction diagram of a route decision method according to Embodiment 4 of the present invention.
  • the downstream CDN, CDNB collects the current total service amount of the upstream CDN, that is, the CDNA service, and reports it to the CDNA.
  • the routing decision method provided in this embodiment includes: Step 61-Step 614: Similar to Step 51-Step 514, and details are not described herein again.
  • Step 615 The CDNB DN re-counts the current total service amount when the user request for forwarding the CDNA starts to deliver the content to the UE.
  • step 615 can be performed in parallel with step 614.
  • the current total service volume of the CDNB may include: CDNB's current total concurrent requests and concurrent total traffic.
  • CDNB&RR can perform an additional 1 operation on the locally recorded total number of concurrent requests serving the CDC to serve the locally recorded CDNA.
  • the current concurrent total traffic performs an operation of increasing the single traffic and refreshes the corresponding result that has been recorded locally.
  • the protocol type the current total number of concurrent requests and the current total concurrent traffic are classified and counted. For example: If the content delivery protocol type is HTTP, the CDNB adds 1 to the total number of HTTP concurrent total requests currently serving the CDNA, and increases the total HTTP concurrent traffic currently serving the CDNA by a single traffic.
  • the CDNB can also determine the domain name of the content provider of the content delivered this time, and classify the current total number of concurrent requests and the current total concurrent traffic according to the domain name. For example, if the content provider's domain name for this delivery is "Youtube", CDNB will add 1 to the current total number of concurrent requests for the content provider domain name "Youtube” that is currently serving the CDC, and will now give “Youtube” The current concurrent total traffic of the service is incrementally operated, and the increased amount is the amount of traffic that the CDNB needs to deliver for this content.
  • Step 616 The CDNB DN generates a notification message (Notify), which is referred to herein as a third notification message.
  • the third notification message is sent to the CDDNA&RR via the CDNB&RR.
  • the third notification message may carry: the CDN identifier of the CDNB, the current total number of concurrent requests of the CDNB, and the current total concurrent traffic.
  • the third notification message may also carry:
  • the CDNB sorts and counts the current total number of concurrent requests and the current total concurrent traffic according to the protocol type or the domain name of the CP.
  • the third notification message may also carry at least one of the following information: a concurrent total request threshold set by the CDNB administrator, a total traffic threshold, a total concurrent request threshold of each protocol type, and a total concurrent Traffic threshold, the total number of concurrent requests for each content provider domain name and the total concurrent traffic threshold.
  • a concurrent total request threshold set by the CDNB administrator a total traffic threshold, a total concurrent request threshold of each protocol type, and a total concurrent Traffic threshold, the total number of concurrent requests for each content provider domain name and the total concurrent traffic threshold.
  • the total number of concurrent requests is 500
  • the total concurrent traffic threshold is 1000M
  • the total number of concurrent RTP requests is 100 and its concurrent total traffic threshold is 200M
  • the content provider domain name is "Youtube”.
  • the total concurrent request threshold is 400 and its concurrent total traffic threshold is 800M.
  • Step 617 After receiving the third notification message, the CDNA&RR extracts the corresponding information and refreshes the corresponding result of the local record. After the next time the user requests, the routing decision in step 64 is performed again according to the extracted information.
  • the information extracted by the CDNA&RR from the third notification message may include: the current concurrent total number of requests obtained by the CDNB statistics and the current concurrent total traffic; and may also include at least one of the following information: the current total number of concurrent requests of each type and the current Concurrent total traffic, concurrent total request threshold, concurrent total traffic threshold, concurrent total request thresholds and concurrent total traffic thresholds.
  • Step 618 The CDNB DN re-counts the current total service amount when the user request for forwarding the CDNA ends the delivery of the content to the UE.
  • the CDNB DN When the CDNB DN senses that it has delivered the content to the UE, it can perform a decrement operation on the current concurrent total request that the CDNB has recorded locally, and perform a operation of reducing the single traffic on the locally recorded current concurrent total traffic. After that, the CDNB refreshes the corresponding results that have been recorded locally.
  • the CDNB can also perform classification and statistics according to the type of protocol used to deliver the content to the UE and the domain name of the CP of the content, and refresh the corresponding result recorded locally.
  • the fourth notification message may carry: a CDN identifier of the CDNB, a current total number of concurrent requests of the CDNB, and a current total concurrent traffic.
  • the fourth notification message may also carry:
  • the CDNB sorts and counts the current total number of concurrent requests and the current total concurrent traffic according to the protocol type or the domain name of the CP.
  • Step 620 After receiving the fourth notification message, the CDNA&RR extracts the corresponding information and refreshes the corresponding result recorded locally. After the next user request comes, the routing decision in step 64 is performed again according to the extracted information.
  • the CDNB sends a notification message including its own real-time statistical result to the CDNA, so that the CDNA extracts the statistical result from the notification message and refreshes the corresponding result of the local record.
  • CDNA can make routing decisions based on the latest results recorded locally, and reduce the probability of forwarding user requests to downstream CDNs that cannot provide services, improving the accuracy of routing decisions, and improving routing decision efficiency.
  • the CDNB which is still in the downstream CDN, still collects the current total number of concurrent requests and the current total traffic for the upstream CDN, but does not send a notification message to the upstream CDN after each statistic, that is, the steps in this embodiment are not executed. 616 and step 619; Instead, the CDNB periodically sends a statistical result to the upstream CDN at a preset time corresponding to the long-term full time, and the statistical result may be carried in the notification message.
  • the duration of the timing may be the upstream CDN, that is, the CDNA designation, or the downstream CDN, set by the administrator of the CDNB, and the like.
  • the CDNA After receiving the notification message periodically sent by the CDNB, the CDNA extracts the information carried in the notification message and refreshes the corresponding result recorded locally. Since the downstream CDN, CDNB, uses the timed reporting method to notify the upstream CDN or CDNA, the signaling interaction between the CDNA and the CDNB is reduced, and the signaling overhead is saved, thereby improving the overall performance of the system.
  • FIG. 7 is a signaling interaction diagram of a route decision method according to Embodiment 5 of the present invention.
  • the CDN that is, the CDNA
  • the identification information is the forwarding identifier.
  • the routing decision method provided in this embodiment includes:
  • Step 71 The end user (Eend User) sends a DNS query request (DNS FQDNA) to the CDNA&RR through the UE.
  • DNS FQDNA DNS query request
  • Step 72 The CDNA&RR determines that the UE is served by the CDNB by using the information such as the location of the user, and determines that the user request is forwarded to the CDNB for processing. Therefore, the CDNA allocates a forwarding identifier to the CDNB according to the user request that is forwarded, and Record the correspondence between the forwarding identifier and the CDNB.
  • Step 73 CDNA&RR returns the alias CNAME of the CDNB to the UE, and the address of the server responsible for resolving the alias, that is, the address of CDNB&RR, and returns to the forwarding identifier assigned in step 72.
  • Step 74 The UE sends a DNS query request (DNS CNAME of CDNB) to the CDNB&RR.
  • Step 76 The UE sends an HTTP request (HTTP URLb) to the CDNB DN, where the request further carries the forwarding identifier assigned in step 72.
  • HTTP URLb HTTP request
  • Step 77-Step 712 Similar to Step 59-Step 514, and details are not described herein again.
  • Step 713 A notification message (Notify) is generated when the current user request forwarded by the CDNB DN for the CDNA starts to deliver the content to the UE, here referred to as a fifth notification message, and the fifth notification message is sent to the CDNA&RR via the CDNB&RR.
  • Notify is generated when the current user request forwarded by the CDNB DN for the CDNA starts to deliver the content to the UE, here referred to as a fifth notification message, and the fifth notification message is sent to the CDNA&RR via the CDNB&RR.
  • step 713 can be performed in parallel with step 712.
  • the fifth notification message may carry: a forwarding identifier and a start service indication information; and may carry at least one of the following information: a single traffic; a protocol used by the CDNB to deliver the content to the UE for the current user request forwarded by the CDDNA Type, such as HTTP, RTP, etc.; CDNB for CDNA forwarding This user request, the domain name of the CP of the content delivered to the UE, such as "video.sina.com". Further, the first notification message may further carry at least one of the following information: a concurrent total request threshold set by the CDNB administrator, a total flow threshold, and a total concurrent request threshold of each protocol type. And concurrent total traffic thresholds, concurrent total request thresholds and concurrent total traffic thresholds for each content provider domain name.
  • the total number of concurrent requests is 500, the total concurrent traffic threshold is 1000M, the total number of concurrent RTP requests is 100 and its concurrent total traffic threshold is 200M, and the content provider domain name is "Youtube”.
  • the total concurrent request threshold is 400 and its concurrent total traffic threshold is 800M.
  • Step 714 After the CDNA receives the fifth notification message, according to the forwarding identifier index in the fifth notification message to the current total service volume of the locally recorded CDNB, and according to other reference information carried in the fifth notification message, the current service of the CDNB is counted. Total, and refresh the corresponding results of the local record.
  • the current total service volume includes the current total number of concurrent requests and the current total concurrent traffic.
  • the CDNA&RR may perform an operation of adding 1 to the current total number of concurrent requests, and performing an increase on the recorded current total traffic according to the single traffic carried in the fifth notification message, for the start indication information carried in the notification message.
  • the single flow operation and refresh the local corresponding record result.
  • the CDNA&RR can also classify the current concurrent total number of requests and the current concurrent total traffic of the CDNB according to the protocol type and domain name information carried in the fifth notification message.
  • Step 715 When the CDNB DN ends delivering its required content (Data) to the UE, the UE notifies the CDNB DN that the content delivery is over.
  • Step 716 When the CDNB DN senses that the content delivery ends, a notification message (Notify), here referred to as a sixth notification message, is sent, and the sixth notification is sent to the CDNA&RR via the CDNB&RR.
  • a notification message here referred to as a sixth notification message
  • the information that can be carried by the sixth notification message corresponds to the information that can be carried by the fifth notification message described in step 713.
  • the sixth notification message may carry: the forwarding identifier and the ending service indication information that are allocated in step 72, and may further carry at least one of the following information: a single traffic; the CDNB forwards the user request for the CDNA, to the UE The type of protocol used to deliver the content, such as HTTP, RTP, etc.; CDNB forwards the user's request for the CDNA, the domain name of the CP of the content delivered to the UE, such as "video.sina.com,, etc.
  • Step 717 After the CDNA receives the sixth notification message, according to the forwarding identifier in the sixth notification message, the current service total amount of the locally recorded CDNB, and according to other reference information carried in the sixth notification message, the current CDNB is counted. Total service, and refresh the corresponding results of the local record.
  • the CDNA&RR may perform a decrement operation on the locally recorded total concurrent total number of requests, and a recorded total concurrent total traffic according to the single traffic carried in the sixth notification message, for the end indication information carried in the sixth notification message.
  • the operation of reducing the single flow is performed, and the corresponding result recorded locally is refreshed.
  • the corresponding classification statistics are also subjected to corresponding operations of reducing or decreasing the single flow, and refreshing the corresponding results recorded locally.
  • the CDNA judges whether the current total service amount is less than the service total threshold, and if so, forwards the user request to the CDNB; otherwise, the user request is not forwarded to the CDNB.
  • the CDNB sends a sixth notification message carrying reference information for counting the current total service volume of the CDNB to the CDNA, where the sixth notification message carries the CDNA allocated according to the forwarded user request for the CDNB.
  • the CDNA forwarding the identifier, so that the CDNA indexes the statistics to the locally recorded CDNB according to the forwarding identifier, and periodically counts and refreshes the corresponding result of the local record according to other reference information.
  • CDNA can make routing decisions based on the latest results of local records, and reduce the probability of forwarding user requests to downstream CDNs that cannot provide services, improving the accuracy of routing decisions, and improving routing decision efficiency.
  • FIG. 8 is a schematic structural diagram of a content distribution apparatus according to Embodiment 6 of the present invention.
  • the content distribution device shown in FIG. 8 can be used as an upstream CDN, and specifically includes: a receiving module 81, a determining module 82, and a decision module 83.
  • the receiving module 81 is configured to receive a notification message sent by the downstream CDN, where the notification message is used to determine that the downstream CDN is a current service total serving service provided by the upstream CDN connected thereto;
  • the upstream CDN is the content distribution device described in this embodiment.
  • the determining module 82 is configured to determine the current total service quantity according to the notification message.
  • the decision module 83 is configured to perform routing decision on the user request to be forwarded according to the current service total and the total service threshold; the total service threshold is set by the downstream CDN, and the downstream CDN can The upper limit for providing services to the upstream CDN.
  • the content distribution apparatus provided in this embodiment, that is, the specific implementation manner of determining the current total service volume by the upstream CDN is not limited, and may include, for example,: the upstream CDN itself performs statistics and records; or, the downstream CDN statistics are up and down, by the upstream CDN. Record or refresh the results.
  • the upstream CDN itself performs statistics and records
  • the downstream CDN statistics are up and down, by the upstream CDN. Record or refresh the results.
  • Method 1 The upstream CDN itself performs statistics and records.
  • the foregoing notification message may include: reference information used to collect the current total service amount.
  • the determining module 82 is specifically configured to count and record the current total service quantity according to the reference information.
  • the reference information may include: identification information, and start indication information or end indication information, where the start indication information indicates: the downstream CDN starts to provide a service for the user for the user request forwarded by the upstream CDN;
  • the information indicates that: the downstream CDN provides a service to the user for the user request of the upstream CDN, and the identifier information includes: the CDN identifier of the downstream CDN, or the upstream CDN is the user request according to the forwarding
  • the forwarding identifier of the downstream CDN allocation the current total service volume includes: a current total number of concurrent requests; the total service threshold includes: a total number of concurrent request thresholds.
  • the determining module 82 is specifically configured to perform, for the current indication number of the current concurrent total CDN corresponding to the identifier information, perform an add operation or an end indication for the start indication information.
  • the information is decremented by 1 and the corresponding result that has been recorded is refreshed.
  • the reference information may include: identifier information and a single traffic, where the identifier information includes: a CDN identifier of the downstream CDN, or the upstream CDN is the downstream CDN according to the forwarded user request.
  • the allocated forwarding identifier is a traffic that is used by the downstream CDN for the user currently forwarded by the upstream CDN to provide services for the user;
  • the current total service volume includes current concurrent total traffic;
  • the total threshold includes: Concurrent total flow threshold.
  • the determining module 82 is specifically configured to perform an operation of increasing or decreasing the single traffic, and refreshing the currently recorded operation, for the current concurrent total traffic of the downstream CDN that is currently recorded and corresponding to the identification information. The corresponding result.
  • the reference information may further include: a type of protocol used by the downstream CDN to provide a service for a user that is currently forwarded by the upstream CDN; and the total service threshold includes: The concurrent total request threshold value and/or the concurrent total traffic threshold value; correspondingly, the determining module 82 is further configured to classify the current concurrent total request number and/or the current concurrent total traffic according to the protocol type.
  • the reference information may further include: a domain name of a content provider of the content requested by the user currently forwarded by the upstream CDN; the total service threshold value further includes: concurrency corresponding to each content provider domain name The total number of request thresholds and/or the total concurrent traffic thresholds; correspondingly, the determining module 82 is further configured to categorize the current total number of concurrent requests and/or the current total concurrent traffic according to the domain name of the content provider. .
  • Method 2 The downstream CDN counts and reports, and the content distribution device, that is, the upstream CDN records or refreshes the corresponding result.
  • the notification message may include: identifier information and the current total service volume; the identifier information includes: a CDN identifier of the downstream CDN, or the upstream CDN is the downstream CDN according to the forwarded user request.
  • the assigned forwarding ID corresponds to the determining module 82 to record or refresh the corresponding result according to the identifier information and the current total service amount.
  • the foregoing notification message may further include the service total threshold value, and the service total threshold may include one or any combination of the following: a concurrent total request threshold; a concurrent total traffic threshold; each protocol type Concurrent total request threshold and/or concurrent total traffic threshold; concurrent total request threshold and/or concurrent total traffic threshold for each content provider domain name.
  • the content distribution device provided by this embodiment can be used as an upstream CDN according to the downstream connected thereto
  • the notification message sent by the CDN determines that the downstream CDN is the current total service amount of the service provided by the upstream CDN connected thereto, and according to the current service volume and the downstream CDN, the downstream CDN is provided by the upstream CDN.
  • the total service threshold which makes routing decisions for the user request to be forwarded, reduces the probability of forwarding the user request to the downstream CDN that cannot provide the service, thereby improving the accuracy of selecting the downstream CDN for the user to be forwarded, thus improving the accuracy. Route decision efficiency.
  • FIG. 1 and FIG. 5 to FIG. 7 for the corresponding description of the upstream CDN, and details are not described herein again.
  • FIG. 9 is a schematic structural diagram of a content distribution apparatus according to Embodiment 7 of the present invention.
  • the content distribution apparatus provided in this embodiment can be used as a downstream CDN, and the structure thereof can include: a generation module 91 and a transmission module 92.
  • the generating module 91 can be configured to generate a notification message for determining that the downstream CDN is the current total amount of service serving the upstream CDN to which it is connected; the downstream CDN includes the content distribution device.
  • the sending module 92 is configured to send the notification message to the upstream CDN, so that the upstream CDN makes a routing decision with respect to the user request to be forwarded by referring to the current total service amount.
  • the type of the notification message is not limited, and the information carried by the information may include: reference information used to count the total amount of the current service; or, the identification information and the total amount of the current service that have been counted.
  • the technical solutions corresponding to the two different types of parameters carried in the notification message are respectively described as follows: Mode 1: The notification message includes: reference information used to collect the current total service amount.
  • the reference message may include: at least one of the identification information and the following information: start indication information, end indication information, single traffic.
  • the identifier information includes: a CDN identifier of the downstream CDN, or a forwarding identifier allocated by the upstream CDN to the downstream CDN according to the forwarded user request;
  • the start indication information indicates: the downstream CDN is for the upstream CDN Forwarding the user request, starting to provide a service for the user;
  • the ending indication information indicates: the downstream CDN provides a service for the user for the user request forwarded by the upstream CDN;
  • the single traffic is: the downstream CDN is for User request forwarded by the upstream CDN to provide services for the user The traffic used by the service.
  • the reference message may further include at least one of the following information: the downstream CDN provides a user with a protocol type used by the user for the user request currently forwarded by the upstream CDN; and the upstream CDN is currently forwarded.
  • the user requests the domain name of the content provider of the requested content.
  • the notification message includes: identifier information and the total amount of the current service that has been counted.
  • the notification message may include: identifier information and the current total service volume; the identifier information includes: a CDN identifier of the downstream CDN, or the upstream CDN is the downstream CDN according to the forwarded user request.
  • the assigned forwarding ID includes: a CDN identifier of the downstream CDN, or the upstream CDN is the downstream CDN according to the forwarded user request.
  • the content distribution device may further include: a statistics module 93.
  • the statistics module 93 can be used to count the current total amount of services of the downstream CDN.
  • the current total service amount may include: a current total number of concurrent requests.
  • a current total number of concurrent requests when the service is provided for the user, an operation of adding 1 to the current total number of concurrent requests that have been recorded is performed; and, at the downstream CDN, the user request for forwarding the upstream CDN ends the service for the user.
  • a minus 1 operation is performed on the current total number of concurrent requests that have been recorded.
  • the current total service amount may include: current concurrent total traffic.
  • the statistics module 93 may be configured to perform an operation of increasing or decreasing a single traffic for the current concurrent total traffic that has been recorded, and refresh the corresponding result that has been recorded.
  • the single traffic is the traffic occupied by the user for the user request forwarded by the upstream CDN.
  • the statistics module 93 is further configured to: according to the user request that the downstream CDN forwards the user for the upstream CDN, provide a type of protocol used by the user, and categorize the current concurrent total number of requests and/or current concurrent The total flow rate; and/or the statistics module 93 is further configured to: categorize the current concurrent total number of requests and/or the current concurrent total traffic according to the domain name of the content provider of the requested content requested by the user currently forwarded by the upstream CDN. .
  • the content distribution apparatus may further include: a timing determination module 94.
  • Timing The module 94 can be configured to determine that the generating module generates the notification message, and the timing at which the sending module sends the notification message to the upstream CDN.
  • the timing includes: a time when the downstream CDN requests the user to be forwarded by the upstream CDN, and starts or ends the service for the user; or, the preset duration is a period, and the expiration time of the preset duration is preset.
  • the notification message may further include: a service total threshold value; the service total threshold value is an upper limit of the downstream CDN that can provide services for the upstream CDN, and specifically includes one of the following Or any combination: concurrent total request threshold; concurrent total traffic threshold; concurrent total request threshold and/or concurrent total traffic threshold for each protocol type; concurrent total request for each content provider domain name Number of thresholds and/or concurrent total flow thresholds.
  • a service total threshold value is an upper limit of the downstream CDN that can provide services for the upstream CDN, and specifically includes one of the following Or any combination: concurrent total request threshold; concurrent total traffic threshold; concurrent total request threshold and/or concurrent total traffic threshold for each protocol type; concurrent total request for each content provider domain name Number of thresholds and/or concurrent total flow thresholds.
  • the present embodiment provides that the content distribution apparatus can be generated as a downstream CDN and sent to the upstream CDN, including reference information for counting the current total service amount, or including the identification information and the total amount of the current service that has been counted.
  • the notification message is provided, so that the upstream CDN can refer to the current total service quantity and perform routing decisions on the user request to be forwarded, thereby improving the accuracy of the upstream CDN to select the downstream CDN for the user to be forwarded, thereby improving the routing decision efficiency.
  • FIG. 3 and FIG. 5 to FIG. 7 for the corresponding description of the downstream CDN, and details are not described herein again.
  • FIG. 10 is a schematic structural diagram of a CDN interconnection system according to Embodiment 8 of the present invention.
  • the CDN interconnection shown in Fig. 10 includes a first CDN 101 and a second CDN 102, and a first CDN 101 and a second CDN 102, which are interconnected upstream CDNs and downstream CDNs, respectively.
  • first CDN 101 refer to the description of the corresponding embodiment of FIG. 8.
  • implementation mechanism refer to FIG. 1 and FIG. 5 to FIG. 7 for the corresponding description of the upstream CDN.
  • the structure of the second CDN 102 refer to the corresponding embodiment of FIG. It is noted that the implementation mechanism can be referred to FIG. 3, FIG. 5 to FIG.
  • the first CDN determines that the downstream CDN is the current service provided by the upstream CDN connected thereto according to the notification message sent by the second CDN, that is, the downstream CDN.
  • the total amount of service and based on the current amount of service and the downstream CDN settings,
  • the downstream CDN is a service total threshold value that can be provided by the upstream CDN, and performs routing decisions on the user request to be forwarded, which reduces the probability of forwarding the user request to the downstream CDN that cannot provide the service, thereby improving the probability of being forwarded.
  • the user requests the accuracy of the downstream CDN, thus improving the efficiency of routing decisions.
  • modules in the apparatus in the embodiments may be distributed in the apparatus of the embodiment according to the embodiment, or may be correspondingly changed in one or more apparatuses different from the embodiment.
  • the modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Multimedia (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

路由决策方法、 内容分发装置和内容分发网络互连系统 技术领域
本发明实施例涉及信息技术领域， 特别是涉及一种路由决策方法、 内容 分发装置和内容分发网络互连系统。 背景技术
内容分发网络（ Content Delivery Network, 简称 CDN )是在现有的互联 网基础上建立的一层网络。 内容提供商 （Content Provider, 简称 CP )基于 CDN将内容发布到最接近用户的网络 "边缘"， 以便用户就近获取所需内容， 从而緩解骨干网拥塞， 提高响应速度。 实际应用中基于计费管理等因素， CP 往往倾向与一个 CDN服务提供商签约，而不是与多个 CDN服务提供商签约。 由于任何一个单独 CDN服务提供商的网络覆盖区域有限，而用户却分散在全 世界不同的区域， 因此需要在不同 CDN服务提供商的网络实现互连互通， 以 便相互使用对方的网络而达到更广的覆盖区域， 从而将其签约 CP 的内容交 付到更多的终端用户。
为实现 CDN互连互通， 可将 CDN服务提供商在不同区域部署的 CDN, 通过互联网相互连接以形成 CDN互连系统。 CDN互连系统中能为同一用户 提供服务的 CDN通常有多个， 这些 CDN互连互通， 且距离能够提供服务的 同一用户， 如用户 A较近的 CDN称为下游 CDN ( Downstream CDN, 简称 DCDN ), 距离用户 A较远的 CDN称为上游 CDN ( Upstream CDN, 简称 UCDN )。 当上游 CDN接收到用户请求时， 上游 CDN将用户请求直接转发到 距离用户较近的某个下游 CDN。如果该下游 CDN不能针对上游 CDN转发的 用户请求提供服务，则该上游 CDN将该用户请求转发到距离用户较近的其他 下游 CDN; 如此反复尝试， 以便用户能够就近获取所需的内容。
现有技术上游 CDN在对待转发的用户请求进行路由决策时，是通过反复 尝试的方式， 确定实际可向用户推送内容的下游 CDN, 因此其路由决策效率 较低。 发明内容
本发明实施例提供一种路由决策方法、 内容分发装置和内容分发网络互 连系统， 用以提高内容分发网络互连系统中上游 CDN的路由决策效率。
本发明实施例提供了一种路由决策方法， 包括：
接收下游 CDN发送的通知消息， 所述通知消息用于确定所述下游 CDN 为与之互连的上游 CDN提供服务的当前服务总量；
根据所述通知消息， 确定所述当前服务总量；
根据所述当前服务总量和服务总量门限值， 对待转发的用户请求进行路 由决策； 所述服务总量门限值为所述下游 CDN设置的、 所述下游 CDN能为 所述上游 CDN提供服务的上限。
本发明实施例还提供了另一种路由决策方法， 包括：
生成通知消息，所述通知消息用于确定下游 CDN为与之互连的上游 CDN 提供服务的当前服务总量；
向所述上游 CDN发送所述通知消息， 以供所述上游 CDN参考所述当前 服务总量， 对待转发的用户请求进行路由决策。
本发明实施例还提供了一种内容分发装置， 所述内容分发装置作为上游 CDN, 包括：
接收模块，用于接收下游 CDN发送的通知消息， 所述通知消息用于确定 确定模块， 用于根据所述通知消息， 确定所述当前服务总量；
决策模块， 用于根据所述当前服务总量和服务总量门限值， 对待转发的 用户请求进行路由决策； 所述服务总量门限值为所述下游 CDN设置的、所述 下游 CDN能为所述上游 CDN提供服务的上限。 本发明实施例还提供了另一种内容分发装置， 所述内容分发装置作为下 游 CDN, 包括：
生成模块，用于生成通知消息， 所述通知消息用于确定所述下游 CDN为 与之互连的上游 CDN提供服务的当前服务总量；
发送模块，用于向所述上游 CDN发送所述通知消息，以供所述上游 CDN 参考所述当前服务总量， 对待转发的用户请求进行路由决策。
本发明实施例还提供了一种内容分发网络互连系统， 包括： 第一 CDN, 和第二 CDN, 分别为互连的上述上游 CDN和上述下游 CDN。
本发明实施例提供的技术方案中， 上游 CDN根据与之互连的下游 CDN 发送的通知消息， 确定所述下游 CDN为与之相连的上游 CDN提供服务的当 前服务总量， 并根据该当前服务量以及下游 CDN设置的、 所述下游 CDN为 所述上游 CDN 能提供的服务总量门限值， 对待转发的用户请求进行路由决 策， 降低了将用户请求转发到不能提供服务的下游 CDN的几率，从而提高了 为待转发用户请求选择下游 CDN的准确性， 因而提高了路由决策效率。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对实 施例或现有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面 描述中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明实施例一提供的路由决策方法的流程图；
图 2为本发明实施例应用场景提供的 CDN互连系统结构示意图； 图 3为本发明实施例二提供的路由决策方法的流程图；
图 4为本发明实施例应用场景中上、下游 CDN之间互通的逻辑接口模型 示意图；
图 5为本发明实施例三提供的路由决策方法的信令交互图； 图 6为本发明实施例四提供的路由决策方法的信令交互图； 图 7为本发明实施例五提供的路由决策方法的信令交互图；
图 8为本发明实施例六提供的内容分发装置的结构示意图；
图 9为本发明实施例七提供的内容分发装置的结构示意图；
图 10为本发明实施例八提供的 CDN互连系统的结构示意图。 具体实施方式
下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行 清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而 不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有付 出创造性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
本发明以下实施例的序号仅仅为了描述， 不代表实施例的优劣。
图 1为本发明实施例一提供的路由决策方法的流程图。本实施例的执行主 体可为 CDN互连系统中的某一上游 CDN。 如图 1所示， 本实施例提供的路由 决策方法包括：
步骤 11 : 接收下游 CDN发送的通知消息， 所述通知消息用于确定所述下 游 CDN为与之相连的上游 CDN提供服务的当前服务总量。
步骤 12: 根据所述通知消息， 确定所述当前服务总量。
本发明实施例中所述的上游 CDN和下游 CDN, 是个相对概念。 图 2为本 发明实施例应用场景提供的 CDN互连系统结构示意图。 如图 2所示的 CDN互 连系统中， 第 11CDN与第 21CDN互连， 第 21CDN和第 31CDN互连， 且这 3个 CDN都能为用户 A提供服务。 则， 由于第 11CDN相对于第 21CDN距离用户 A 近， 因此， 第 11CDN相对第 21CDN而言是下游 CDN, 并且是与之互连的下游 CDN; 而第 21CDN相对于第 11CDN而言是上游 CDN, 并且是与之互连的上游 CDN。 此外， 由于第 21CDN相对于第 31CDN距离用户 A近， 因此， 第 11CDN 和第 21CDN, 分别相对于第 31CDN而言是下游 CDN; 第 31CDN分别相对于第 11 CDN和第 21 CDN而言，是上游 CDN; 且第 21 CDN是与第 31CDN互连的下游 CDN, 第 31CDN是与第 21CDN互连的上游 CDN; 以此类推。 为便于描述， 本 发明实施例以下所述的上游 CDN和下游 CDN, 如无特别说明， 上游 CDN和下 游 CDN互连， 下文不再赘述。此外，可以理解， 图 2所示的系统仅为一种示例， 不应理解为对本发明实施例技术方案的限制。
上游 CDN确定当前服务总量的具体实现方式不受限制， 例如可包括： 上 游 CDN自身进行统计并记录； 或者， 下游 CDN统计并上报、 由上游 CDN记录 或刷新相应结果。 下面对这两种方式， 分别予以说明：
方式一： 上游 CDN自身进行统计并记录。
该方式下， 上述通知消息可包括： 用于统计所述当前服务总量的参考信 息。 上游 CDN可根据参考信息， 统计并记录所述当前服务总量。
其中， 所述参考信息可包括： 标识信息、 以及开始指示信息或结束指示 信息。 所述开始指示信息表示： 所述下游 CDN针对所述上游 CDN转发的用户 请求， 开始为用户提供服务； 所述结束指示信息表示： 所述下游 CDN针对所 述上游 CDN转发的用户请求， 结束为用户提供服务。 所述标识信息包括： 所 述下游 CDN的 CDN标识， 或所述上游 CDN根据转发的用户请求向所述下游 CDN分配的转发标识； 所述当前服务总量包括： 当前并发总请求数， 本发明 实施例所述的当前并发总请求数即为： 所述下游 CDN当前接收到所述上游 CDN转发的用户请求的总数。 在上游 CDN统计当前并发总请求数时， 上游 CDN可对当前已记录的、 与所述标识信息相应的下游 CDN的所述当前并发总 请求数，针对所述开始指示信息执行加 1操作或针对所述结束指示信息执行减 1操作， 并刷新当前已记录的相应结果。
所述参考信息也可包括： 上述标识信息以及单次流量， 所述单次流量为 所述下游 CDN针对所述上游 CDN当前转发的用户请求， 为用户提供服务所占 用的流量； 所述当前服务总量包括当前并发总流量， 本发明实施例所述的当 前并发总流量即为： 所述下游 CDN当前接收到的、 所述上游 CDN转发的各用 户请求占用的流量之和。 在上游 CDN统计当前并发总流量时 , 上游 CDN可对 当前已记录的、 与所述标识信息相应的下游 CDN的当前并发总流量， 执行增 加或减少所述单次流量的操作， 并刷新当前已记录的相应结果。
此外， 所述参考信息还可包括： 所述下游 CDN针对所述上游 CDN当前转 发的用户请求， 为所述用户提供服务所使用的协议类型； 所述服务总量门限 值还可包括： 各协议类型的所述当前并发总请求数门限值和 /或所述当前并发 总流量门限值。 所述参考信息还可包括： 所述上游 CDN当前转发的用户请求 所请求内容的内容提供商的域名； 所述服务总量门限值还可包括： 各内容提 供商域名对应的所述当前并发总请求数门限值和 /或所述当前并发总流量门 限值。 则， 在上游 CDN统计当前并发总请求数时， 上游 CDN可根据所述协议 类型和 /或所述内容提供商的域名，对当前并发总请求数和 /或当前并发总流量 进行分类统计。
方式二： 下游 CDN统计并上 ·¾, 由上游 CDN记录或刷新相应结果。 该情形下， 所述通知消息可包括： 标识信息和所述当前服务总量； 所述 标识信息包括： 所述下游 CDN的 CDN标识， 或所述上游 CDN根据转发的用户 请求， 为所述下游 CDN分配的转发标识。 上游 CDN根据通知消息携带的当前 服务总量， 记录或刷新与该标识信息对应的相应结果。
步骤 13: 根据所述当前服务总量和服务总量门限值， 对待转发的用户请 求进行路由决策； 所述服务总量门限值为所述下游 CDN设置的、 所述下游 CDN能为所述上游 CDN提供服务的上限。
上游 CDN确定的当前服务总量可包括： 所述下游 CDN为与之互连的上游 CDN提供服务的当前并发总请求数和 /或当前并发总流量， 还可包括： 依据所 述协议类型或内容提供商的域名， 分类统计的所述当前并发总请求数和 /或所 述当前并发总流量。
所述服务总量门限值可包括以下之一或组合： 并发总请求数门限值； 并 发总流量门限值； 各协议类型的并发总请求数门限值和 /或并发总流量门限 值； 各内容提供商域名对应的并发总请求数门限值和 /或并发总流量门限值。 服务总量门限值可预先配置在上游 CDN上。 或者， 服务总量门限值可携带在 所述通知消息中， 由下游 CDN上报给上游 CDN, 以便下游 CDN在服务总量门 限值更改后及时通知上游 CDN, 从而提高了应用的灵活性。
在上游 CDN接收到用户请求时， 如果发现系统中存在距离该用户请求相 应用户较近的下游 CDN, 则参考自身最新记录的该下游 CDN的当前服务总量 及服务总量门限值， 进行路由决策。 例如：
当上游 CDN确定的所述当前服务总量为所述当前并发总请求数、 所述服 务总量门限值为所述并发总请求数门限值时， 上游 CDN可将自身记录的所述 当前并发总请求数， 与所述并发总请求数门限值进行比较， 如果所述当前并 发总请求数小于所述并发总请求数门限值，则向该下游 CDN转发该用户请求； 否则， 不向该下游 CDN转发该用户请求。
当上游 CDN确定的当前服务总量为所述当前并发总流量、 所述服务总量 门限值为所述并发总流量门限值时， 上游 CDN可将自身记录的所述当前并发 总流量， 与所述并发总流量门限值进行比较， 如果所述当前并发总流量小于 所述并发总流量门限值， 则向该下游 CDN转发该用户请求。 如果当前并发总 流量大于或等于并发总流量门限值， 则不向该下游 CDN转发该用户请求。
上游 CDN不向下游 CDN转发用户请求的情形下， 上游 CDN可自身为该用 户请求所对应的用户提供服务， 也可为该用户请求选择其他的转发路径等。
当然， 在实际应用中， 上游 CDN对所述当前并发总请求数和所述当前并 发总流量可都进行统计或分类统计， 并参照统计结果对待转发的路由请求进 行路由决策， 以提高路由决策的准确性， 因而提高了路由决策效率。
本实施例提供路由决策方法中， 上游 CDN根据与之互连的下游 CDN发送 的通知消息， 确定所述下游 CDN为与之相连的上游 CDN提供服务的当前服务 总量， 并根据该当前服务总量以及下游 CDN设置的、 所述下游 CDN为所述上 游 CDN能提供的服务总量门限值， 对待转发的用户请求进行路由决策， 降低 了将用户请求转发到不能提供服务的下游 CDN的几率， 从而提高了为待转发 用户请求选择下游 CDN的准确性， 因而提高了路由决策效率。
图 3为本发明实施例二提供的路由决策方法的流程图。本实施例的执行主 体可为 CDN互连系统中的某一下游 CDN。 如图 3所示， 本实施例提供的路由 决策方法包括：
步骤 31 : 生成通知消息， 所述通知消息用于确定下游 CDN为与之互连的 上游 CDN提供服务的当前服务总量。
通知消息的类型不受限制， 其携带的信息可包括： 用于统计所述当前服 务总量的参考信息； 或者， 标识信息和已统计好的所述当前服务总量。 下面 针对通知消息中携带的这两种不同类型参数对应的技术方案，分别予以说明： 方式一： 通知消息包括： 用于统计所述当前服务总量的参考信息。
该情形下， 所述参考消息可包括： 标识信息， 以及以下信息中的至少其 中一个： 开始指示信息， 结束指示信息， 单次流量。 其中， 所述标识信息可 包括： 所述下游 CDN的 CDN标识， 或所述上游 CDN根据转发的用户请求为所 述下游 CDN分配的转发标识。 所述开始指示信息表示： 所述下游 CDN针对所 述上游 CDN转发的用户请求，开始为用户提供服务。所述结束指示信息表示： 所述下游 CDN针对所述上游 CDN转发的用户请求， 结束为用户提供服务。 所 述单次流量为： 所述下游 CDN针对所述上游 CDN当前转发的用户请求， 为用 户提供服务所占用的流量。
所述参考信息还可包括以下信息中的至少其中一个： 所述下游 CDN针对 所述上游 CDN当前转发的用户请求， 为用户提供服务所使用的协议类型； 所 述上游 CDN当前转发的用户请求所请求内容的内容提供商的域名。
方式二： 通知消息包括： 标识信息和已统计好的所述当前服务总量。 所述标识信息可包括： 所述下游 CDN的 CDN标识， 或所述上游 CDN根据 转发的用户请求、 为所述下游 CDN分配的转发标识。
该情形下， 下游 CDN在生成通知消息之前， 还包括： 统计下游 CDN的所 述当前服务总量。
所述当前服务总量可包括： 当前并发总请求数， 和 /或， 当前并发总流量。 下游 CDN统计当前并发总请求数的方法可包括： 下游 CDN针对上游 CDN 转发的用户请求， 开始为用户提供服务时， 对当前已记录的所述当前并发总 请求数执行加 1操作，并刷新当前已记录的相应结果； 下游 CDN针对上游 CDN 转发的用户请求， 结束为用户提供服务时， 对当前已记录的所述当前并发总 请求数执行减 1操作， 并刷新当前已记录的相应结果。
下游 CDN统计当前并发总流量的方法可包括： 下游 CDN针对上游 CDN转 发的用户请求开始为用户提供服务时，对当前已记录的所述当前并发总流量， 执行增加单次流量的操作， 并刷新当前已记录的相应结果； 下游 CDN针对上 游 CDN转发的用户请求结束为用户提供服务时， 对当前已记录的所述当前并 发总流量， 执行减少单次流量的操作， 并刷新当前已记录的相应结果。 其中， 所述单次流量为针对所述上游 CDN当前转发的用户请求， 为用户提供服务所 占用的流量。
在下游 CDN统计当前并发总请求数和 /或当前并发总流量时，也可根据自 身针对所述上游 CDN当前转发的用户请求， 为用户提供服务所使用的协议类 型， 和 /或， 所请求内容的内容提供商的域名， 分类统计所述当前并发总请求 数和 /或当前并发总流量。
生成的通知消息中还可包括： 服务总量门限值。 其中， 所述服务总量门 限值包括以下之一或任意组合： 并发总请求数门限值； 并发总流量门限值； 各协议类型的并发总请求数门限值和 /或并发总流量门限值； 各内容提供商域 名对应的并发总请求数门限值和 /或并发总流量门限值。
步骤 32: 向所述上游 CDN发送所述通知消息， 以供所述上游 CDN参考所 述当前服务总量， 对待转发的用户请求进行路由决策。
下游 CDN可选择满足一定条件的时机， 生成通知消息并向上游 CDN发 送。 该时机可具体为： 时机一： 下游 CDN针对所述上游 CDN转发的用户请求， 开始或结束为用 户提供服务的时刻。 下游 CDN在该时机生成通知消息并向上游 CDN发送， 则 可实现下游 CDN数据实时上报或实时统计， 以及上游 CDN获取的数据实时更 新， 其数据实时性好。
时机二： 以预设时长为周期，每次预设时长的期满时刻。例如： 下游 CDN 可在时机一所述当前服务总量进行实时统计，并在时机二定时上报统计结果， 利于提高系统的整体性能。
上游 CDN接收到下游 CDN发送的通知消息， 根据该通知消息确定所述当 前服务总量， 并参考所述当前服务总量， 对待转发的用户请求进行路由决策 的实现方法， 可参见图 1对应实施例的记载， 在此不再赘述。
本实施例提供路由决策方法中， 下游 CDN生成并向上游 CDN发送， 包括 有用于统计所述当前服务总量的参考信息， 或者包括有标识信息和已统计好 的所述当前服务总量的通知消息， 以便上游 CDN可参考当前服务总量， 对待 转发的用户请求进行路由决策， 从而提高了上游 CDN为待转发用户请求选择 下游 CDN的准确性， 因而提高了路由决策效率。
图 4为本发明实施例应用场景中上、下游 CDN之间互通的逻辑接口模型示 意图。 在由上游 CDN和下游 CDN组成的一对互通的 CDN之间， 可采用以下接 口通信且各接口的定义如下：
互通配置接口 （ Control Protocol ) ： 上游 CDN向下游 CDN发送删除， 使 内容无效等命令的接口；
路由接口 （ Request Routing Protocol )： 通过该接口， 上游 CDN将用户请 求转发给下游 CDN; 下游 CDN通过该接口上报路由决策所需的信息， 如上报 本发明实施例所述的通知消息等。
元数据接口 ( Metadata Protocol )： 通过该接口， 互通的上、 下游 CDN交 互一些内容分发策略信息， 内容区域信息， 如该内容不允许在某些区域交付， 内容的可用时间窗信息等。
日志接口 （ Logging Protocol ) ： 通过该接口， 互通的上、 下游 CDN交互 日志相关信息， 如下游 CDN通过该接口向上游 CDN上报某时间段内， 代替上 游 CDN为某用户交付了多大流量的内容等。
此外， 互通的上、 下游 CDN之间还包括： 提供内容交付的节点（Delivery Node, 简称 DN ) ： 互通的上、 下游 CDN通过 DN交互用户请求相关的内容。
可以理解， 图 4所示的接口模型仅为一种示例， 不应理解为对本发明实施 例技术方案的限制。
下面结合图 4所示的上、 下游 CDN之间互通的逻辑接口模型， 并结合图 5- 图 7所示的具体场景， 详细说明本发明实施例的技术方案。 在以下图 5-图 7对 应的各实施例中， CDNA和 CDNB组成一对互连互通的 CDN , 且 CDNA是 CDNB的上游 CDN , CDNB是 CDNA的下游 CDN; CDNA距用户终端 A较远、 与内容提供商签约且距原始服务器（ Origin Server )较近， CDNB距用户终端 A较近、 距原始服务器（Origin Server )较远。 CDNA可包括： CDNA的路由 接口模块（ CDNA&RR )和内容交付节点（ CDNA DN )； CDNB可包括： CDNB 的路由接口模块（ CDNB&RR )和内容交付节点 （ CDNB DN ) 。
图 5为本发明实施例三提供的路由决策方法的信令交互图。本实施例中上 游 CDN即 CDNA, 根据下游 CDN即 CDNB发送的通知消息， 实时统计并记录 CDNB的当前服务总量。 如图 5所示， 本实施例提供的路由决策方法包括： 步骤 51：终端用户（ Eend User )通过用户设备 ( User Equipment,简称 UE ) , 向 CDNA&RR发送的域名服务器（ Domain Name Server, 简称 DNS)查询请求 ( DNS FQDNA ) 。
步骤 52: CDNA&RR通过用户位置等信息判断该 UE由 CDNB提供服务最 合适， 为了后续使用 HTTP的重定向机制， CDNA&RR将自己的 IP地址返回给
UE。
步骤 53: UE向步骤 52返回的 IP地址发送 HTTP请求（HTTP URLa ) 。 步骤 54: CDNA&RR接收 UE发送的 HTTP请求， 依据用户位置信息再次 判断该 UE由 CDNB提供服务最合适， 则根据 CDNB的当前服务总量及其服务 总量门限值进行路由决策， 以确定是否将该 HTTP请求转发给 CDNB。
假设 CDNB的当前服务总量为： CDNB的当前并发总请求数和当前并发总 流量， 服务总量门限值具体为并发总请求数门限值和并发总流量门限值， 贝' J , CDNA&RR进行路由决策时， 将自身记录的当前并发总请求数和当前并发总 流量， 分别与并发总请求数门限值和并发总流量门限值进行比较。 如果当前 并发总请求数小于并发总请求数门限值、 且当前并发总流量小于并发总流量 门限值， 则确定可向 CDNB转发本次用户请求， 以便由 CDNB后续为 UE提供 服务， 执行步骤 55; 否则， CDNA&RR为本次用户请求的转发选择其他下游 CDN。
步骤 55: CDNA&RR向 UE返回 CDNB&RR的 URL地址（ URLb ) , 以通知
UE根据该 URL地址与 CDNB建立连接。
步骤 56: UE向 CDNB&RR^送 DNS查询请求（ DNS FQDNB ) 。
步骤 57: CDNB&RR基于 UE位置信息、 该请求所请求内容的 CP的域名等 信息，选择一个为 UE最终交付内容的节点 CDNB DN, 并向 UE返回 CDNB DN 的 IP地址。
步骤 58: UE向 CDNB DN发送 HTTP请求（ HTTP URLb ) 。
步骤 59: CDNB DN收到 HTTP内容请求后， 发现自身没有该请求所需的 内容， 则向 CDNA&RR^送 DNS查询请求（DNS FQDNA ) 。
步骤 510: CDNA&RR选择内容交付节点即 CDNA DN, 并向 CDNB DN返 回 CDNA DN的 IP地址。
步骤 511： CDNB DN向 CDNA DN发送 HTTP请求（ HTTP URLa ) ， 用于 请求获取 UE本次用户请求所需的内容。
步骤 512: 如果 CDNA DN没有保存 UE本次用户请求所需的内容， 则向 CP 的原始服务器获取 UE本次用户请求所需的内容（Data ) 。 步骤 513: CDNA DN将 UE本次用户请求所需的内容， 发送给 CDNB DN。 步骤 514: CDNB DN开始向 UE交付其所需的内容（Data ) 。
步骤 515: 在 CDNB DN针对 CDNA转发的本次用户请求开始向 UE交付内 容时生成通知消息（Notify ) , 这里称为第一通知消息， 并经由 CDNB&RR向
CDNA&RR发送该第一通知消息。
上述步骤 515可与步骤 514并行执行。
第一通知消息可携带： CDNB的 CDN标识、 开始服务指示信息和单次流 量。 第一通知消息还可携带以下信息中的至少其中一个： CDNB针对 CDNA 转发的本次用户请求， 向 UE交付内容所使用的协议类型， 如 HTTP, RTP等； CDNB针对 CDNA转发的本次用户请求， 向 UE交付的内容的 CP的域名， 如 "video.sina.com" 等。 进一步的， 第一通知消息还可携带以下信息中的至少 其中一个： CDNB管理员设置的并发总请求数门限值， 并发总流量门限值， 各协议类型的并发总请求数门限值和并发总流量门限值， 各内容提供商域名 对应的并发总请求数门限值和并发总流量门限值。 例如： RTP的并发总请求 数门限值是 8, HTTP的并发总请求门限值是 20, 并发总请求数门限值是 100, 并发总流量门限值是 500M , RTP交付占用的并发总流量门限值是 100M , HTTP交付占用的并发总流量门限值是 300M等。
步骤 516: CDNA&RR接收第一通知消息， 并根据第一通知消息统计和记 录 CDNB的当前服务总量， 如统计 CDNB为 CDNA转发的用户请求、 提供服务 的当前并发总请求数和当前并发总流量， 并刷新已记录的相应结果。
CDNA&RR可在本地已记录的数据中， 查找与第一通知消息中携带的 CDN标识对应 CDN的当前并发总请求数和当前并发总流量， 针对通知消息中 携带的开始指示信息， 对已记录的当前并发总请求数执行加 1操作、 以及依据 第一通知消息中携带的单次流量， 对已记录的当前并发总流量执行增加所述 单次流量的操作， 并刷新本地的相应记录结果。
CDNA&RR还可依据第一通知消息中携带的协议类型和域名信息， 分类 统计 CDNB的当前并发总请求数和当前并发总流量。 例如： CDNA&RR统计 得到 CDNB的当前并发总请求数为 5, 其中， 3个是使用 RSTP协议类型交付， 2 个是使用 RTP协议类型交付； 3个使用 RSTP协议类型交付的并发请求中， 2个 是 "sina" 发布的内容， 1个是 "youtube" 发布的内容， 并对相应并发总流量 进行分类统计。
步骤 517: 在 CDNB DN针对 CDNA转发的本次用户请求， 结束向 UE交付 内容（Data ) 时生成通知消息 （Notify ) , 这里称为第二通知消息， 并经由 CDNB&RR向 CDNA&RR发送该第二通知消息。
第二通知消息可携带： CDNB的 CDN标识、 结束服务指示信息和单次流 量。 第二通知消息还可携带以下信息中的至少其中之一： CDNB针对 CDNA 转发的本次用户请求， 向 UE交付内容所使用的协议类型， 如 HTTP, RTP等； CDNB针对 CDNA转发的本次用户请求， 向 UE交付的内容的 CP的域名， 如 "video.sina.com" 等。
步骤 518: CDNA&RR接收上述第二通知消息， 并根据该第二通知消息统 计和记录 CDNB的当前服务总量， 即统计 CDNB为 CDNA转发的用户请求、 提 供服务的当前并发总请求数和当前并发总流量， 并刷新已记录的相应结果。
CDNA&RR可在本地已记录的数据中， 查找已记录的、 与第二通知消息 中携带的 CDN标识对应 CDN的当前并发总请求数和当前并发总流量， 针对第 二通知消息中携带的结束指示信息， 对本地已记录的当前并发总请求数执行 减 1操作， 以及依据第二通知消息中携带的单次流量， 对已记录的当前并发总 流量执行减少所述单次流量的操作， 并刷新本地已记录的相应结果。 在 CDNA&RR有分类统计的情形下， 还要对已记录的分类统计数据， 执行相应 的减 1或减少所述单次流量的操作， 并刷新本地已记录的相应结果。
本实施例提供的路由决策方法中， CDNB向 CDNA发送通知消息， 该通知 消息携带用于确定 CDNB为 CDNA提供服务的当前并发总请求数和当前并发 总流量所需的参考信息， CDNB根据该参考信息统计并刷新本地记录的相应 结果， 并根据本地记录的最新结果对待转发的用户请求进行路由决策， 降低 了将用户请求转发到不能提供服务的下游 CDN的几率， 提高了其路由决策的 准确性， 从而提高了路由决策效率。
图 6为本发明实施例四提供的路由决策方法的信令交互图。 本实施例中， 下游 CDN即 CDNB, 实时统计自身为上游 CDN即 CDNA提供服务的当前服务 总量， 并上报给 CDNA。 如图 6所示， 本实施例提供的路由决策方法包括： 步骤 61-步骤 614: 与步骤 51-步骤 514相似， 在此不再赘述。
步骤 615: CDNB DN在针对 CDNA转发的本次用户请求开始向 UE交付内 容时， 重新统计当前服务总量。
上述步骤 615可与步骤 614并行执行。
CDNB的当前服务总量可包括： CDNB的当前并发总请求数和并发总流 量。 当 CDNB DN开始向 UE交付本次用户请求所需的内容时， CDNB&RR可对 本地已记录的、 为 CDNA提供服务的当前并发总请求数执行加 1操作， 对本地 已记录的、 为 CDNA提供服务的当前并发总流量执行增加所述单次流量的操 作， 并刷新本地已记录的相应结果。 据该协议类型对当前并发总请求数和当前并发总流量， 进行分类统计。 例如： 本次内容交付使用协议类型的是 HTTP, 则 CDNB 将当前给 CDNA提供 服务的 HTTP当前并发总请求数加 1 , 将当前给 CDNA提供服务的 HTTP当前并 发总流量增加单次流量。 更进一步的， CDNB还可以判断本次交付的内容的 内容提供商的域名， 根据域名对当前并发总请求数和当前并发总流量进行分 类统计。例如， 本次交付的内容的内容提供商的域名为 "Youtube" , 则 CDNB 将当前给 CDNA提供服务的内容提供商域名为 "Youtube" 的当前并发总请求 数加 1 , 将当前给 "Youtube" 提供服务的当前并发总流量进行增量操作， 所 增加的量为 CDNB为本次内容交付所需占用的流量。
步骤 616: CDNB DN生成通知消息 （Notify ) , 这里称为第三通知消息， 并经由 CDNB&RR向 CDNA&RR发送该第三通知消息。
第三通知消息可携带： CDNB的 CDN标识、 CDNB的当前并发总请求数和 当前并发总流量。
第三通知消息还可携带： CDNB根据协议类型或 CP的域名， 分类统计的 各类当前并发总请求数和当前并发总流量。
第三通知消息还可携带以下信息中的至少其中之一： CDNB管理员设置 的并发总请求数门限值， 并发总流量门限值， 各协议类型的并发总请求数门 限值和并发总流量门限值， 各内容提供商域名对应的并发总请求数门限值和 并发总流量门限值。 例如： 并发总请求数门限值是 500, 并发总流量门限值是 1000M, RTP的并发总请求数门限值是 100及其并发总流量门限值是 200M, 内 容提供商域名为 "Youtube" 的并发总请求数门限值是 400及其并发总流量门 限值是 800M等。
步骤 617: CDNA&RR接收到第三通知消息后提取相应信息并刷新本地记 录的相应结果， 在下次用户请求来临时， 根据提取的这些信息再次执行步骤 64中的路由决策。
CDNA&RR从第三通知消息中提取的信息可包括： CDNB统计得到的当 前并发总请求数和当前并发总流量； 还可包括以下信息中的至少其中之一： 各类型的当前并发总请求数和当前并发总流量， 并发总请求数门限值， 并发 总流量门限值， 各类型的并发总请求数门限值和并发总流量门限值。
步骤 618: CDNB DN在针对 CDNA转发的本次用户请求结束向 UE交付内 容时， 重新统计当前服务总量。
当 CDNB DN感知到其向 UE交付内容结束时 ,可对 CDNB本地已记录的当 前并发总请求执行减 1操作 ,对本地已记录的当前并发总流量执行减少单次流 量的操作。 之后， CDNB刷新本地已记录的相应结果。 CDNB还可依据本次向 UE交付内容所需使用的协议类型、 以及内容的 CP的域名进行分类统计， 并刷 新本地已记录的相应结果。 步骤 619: CDNB DN生成通知消息 （Notify ) , 这里称为第四通知消息， 并经由 CDNB&RR向 CDNA&RR发送该第四通知消息。
该第四通知消息可携带： CDNB的 CDN标识、 CDNB的当前并发总请求数 和当前并发总流量。
该第四通知消息还可携带： CDNB根据协议类型或 CP的域名， 分类统计 的各类当前并发总请求数和当前并发总流量。
步骤 620: CDNA&RR接收到第四通知消息后提取相应信息并刷新本地已 记录的相应结果， 在下次用户请求来临时， 根据提取的这些信息再次执行步 骤 64中的路由决策。
本实施例提供的路由决策方法中， CDNB向 CDNA发送包括自身实时统计 结果的通知消息， 以便 CDNA从通知消息中提取统计结果并刷新本地记录的 相应结果。 CDNA可据本地记录的最新结果对待转发的用户请求进行路由决 策， 降低了将用户请求转发到不能提供服务的下游 CDN的几率， 提高了其路 由决策的准确性， 从而提高了路由决策效率。
可选的， 可对本实施例的部分技术手段进行变形， 作为本发明另一实施 方式。 例如： CDNB即下游 CDN内部仍然实时的统计为上游 CDN提供服务的 当前并发总请求数和当前并发总流量， 但不是每次统计后都向上游 CDN发送 通知消息， 即不执行本实施例中步骤 616和步骤 619； 而是 CDNB以预设时长 为周期， 定时向上游 CDN发送每次预设时长期满对应的时刻的统计结果， 该 统计结果可携带在通知消息中。 该定时的时长可以是上游 CDN, 即 CDNA指 定， 也可以是下游 CDN, 由 CDNB的管理员设定等。 CDNA收到 CDNB定时发 送的通知消息后， 提取通知消息携带的信息并刷新本地已记录的相应结果。 由于下游 CDN即 CDNB, 采用定时上报的方式通知上游 CDN即 CDNA, 因此 减少了 CDNA和 CDNB之间的信令交互， 节省信令开销，从而有利于提高系统 的整体性能。
图 7为本发明实施例五提供的路由决策方法的信令交互图。本实施例中上 游 CDN即 CDNA, 在转发用户请求时给下游 CDN即 CDNB时， 根据本次转发 的用户请求为 CDNB分配一个转发标识，后续 CDNB在感知到内容交付开始或 结束时发送通知消息给 CDNA, 其中携带的标识信息为该转发标识。 如图 7所 示， 本实施例提供的路由决策方法包括：
步骤 71 : 终端用户 （Eend User )通过 UE, 向 CDNA&RR发送的 DNS查询 请求（DNS FQDNA ) 。
步骤 72: CDNA&RR通过用户位置等信息判断该 UE由 CDNB提供服务最 合适， 则确定将本次用户请求转发到 CDNB进行处理， 因此， CDNA根据本次 转发的用户请求为 CDNB分配一个转发标识，并记录该转发标识和 CDNB的对 应关系。
步骤 73: CDNA&RR向 UE返回 CDNB的别名 CNAME、和负责解析该别名 的服务器地址即 CDNB&RR的地址， 还返回步骤 72中分配的转发标识。
步骤 74: UE向 CDNB&RR发送 DNS查询请求（ DNS CNAME of CDNB ) 。 步骤 75: CDNB&RR基于 UE位置信息、 该请求内容的 CP的域名等信息， 选择一个为 UE最终交付内容的节点 CDNB DN, 并向 UE返回 CDNB DN的 IP 地址。
步骤 76: UE向 CDNB DN发送携带 HTTP请求（HTTP URLb ) , 该请求中 还携带有步骤 72分配的转发标识。
步骤 77-步骤 712: 与步骤 59-步骤 514相似， 在此不再赘述。
步骤 713: 在 CDNB DN针对 CDNA转发的本次用户请求开始向 UE交付内 容时生成通知消息（Notify ) , 这里称为第五通知消息， 并经由 CDNB&RR向 CDNA&RR发送该第五通知消息。
上述步骤 713可与步骤 712并行执行。
该第五通知消息可携带： 转发标识和开始服务指示信息； 还可携带以下 信息中的至少其中之一： 单次流量； CDNB针对 CDNA转发的本次用户请求， 向 UE交付内容所使用的协议类型， 如 HTTP, RTP等； CDNB针对 CDNA转发 的本次用户请求， 向 UE交付的内容的 CP的域名， 如 "video.sina.com" 等。 进 一步的， 第一通知消息还可携带以下信息中的至少其中之一： CDNB管理员 设置的并发总请求数门限值， 并发总流量门限值， 各协议类型的并发总请求 数门限值和并发总流量门限值， 各内容提供商域名对应的并发总请求数门限 值和并发总流量门限值。 例如： 并发总请求数门限值是 500, 并发总流量门限 值是 1000M , RTP的并发总请求数门限值是 100及其并发总流量门限值是 200M, 内容提供商域名为 "Youtube" 的并发总请求数门限值是 400及其并发 总流量门限值是 800M等。
步骤 714: CDNA接收第五通知消息后， 根据该第五通知消息中的转发标 识索引到本地记录的 CDNB的当前服务总量， 依据第五通知消息中携带的其 他参考信息， 统计 CDNB的当前服务总量， 并刷新本地记录的相应结果。
假设： 当前服务总量包括当前并发总请求数和当前并发总流量。 则 CDNA&RR可针对通知消息中携带的开始指示信息， 对已记录的当前并发总 请求数执行加 1操作、 以及依据第五通知消息中携带的单次流量， 对已记录的 当前并发总流量执行增加所述单次流量的操作、并刷新本地的相应记录结果。
CDNA&RR还可依据第五通知消息中携带的协议类型和域名信息， 分类 统计 CDNB的当前并发总请求数和当前并发总流量。
步骤 715: CDNB DN结束向 UE交付其所需的内容（Data ) 时， UE通知 CDNB DN内容交付结束。
步骤 716: CDNB DN感知到内容交付结束时， 生成通知消息 （Notify ) , 这里称为第六通知消息， 并经由 CDNB&RR向 CDNA&RR发送该第六通知消 自
该第六通知消息可携带的信息，与步骤 713所述的第五通知消息可携带的 信息相对应。 具体的， 第六通知消息可携带： 步骤 72分配的转发标识和结束 服务指示信息， 还可携带以下信息中的至少其中之一： 单次流量； CDNB针 对 CDNA转发的本次用户请求， 向 UE交付内容所使用的协议类型， 如 HTTP, RTP等； CDNB针对 CDNA转发的本次用户请求， 向 UE交付的内容的 CP的域 名 , 如 "video.sina.com，， 等。
步骤 717: CDNA接收上述第六通知消息后， 根据该第六通知消息中的转 发标识索引到本地记录的 CDNB的当前服务总量， 依据第六通知消息中携带 的其他参考信息， 统计 CDNB的当前服务总量， 并刷新本地记录的相应结果。
CDNA&RR可针对第六通知消息中携带的结束指示信息， 对本地已记录 的当前并发总请求数执行减 1操作， 以及依据第六通知消息中携带的单次流 量， 对已记录的当前并发总流量执行减少所述单次流量的操作， 并刷新本地 已记录的相应结果。 在 CDNA&RR有分类统计的情形下， 还要对已记录的分 类统计数据， 执行相应的减 1或减少所述单次流量的操作， 并刷新本地已记录 的相应结果。
后续当有新的类似用户请求到达 CDNA时， CDNA判断统计的当前服务总 量是否小于服务总量门限值， 如果是， 则向 CDNB转发用户请求； 否则， 不 向 CDNB转发用户请求。
本实施例提供的路由决策方法中， CDNB向 CDNA发送携带有用于统计 CDNB当前服务总量的参考信息的第六通知消息， 该第六通知消息中携带有 CDNA根据转发的用户请求为 CDNB分配的转发标识， 以便 CDNA根据转发标 识索引到本地已记录的 CDNB的统计结果， 并依据其他参考信息实时统计并 刷新本地记录的相应结果。 CDNA可根据本地记录的最新结果对待转发的用 户请求进行路由决策， 降低了将用户请求转发到不能提供服务的下游 CDN的 几率， 提高了其路由决策的准确性， 从而提高了路由决策效率。
图 8为本发明实施例六提供的内容分发装置的结构示意图。 如图 8所示的 内容分发装置可作为上游 CDN, 具体包括： 接收模块 81、 确定模块 82和决策 模块 83。
接收模块 81用于接收下游 CDN发送的通知消息， 所述通知消息用于确定 所述下游 CDN为与之互连的上游 CDN提供服务的当前服务总量； 其中， 所述 上游 CDN即为本实施例所述的内容分发装置。
确定模块 82用于根据所述通知消息， 确定所述当前服务总量。
决策模块 83用于根据所述当前服务总量和服务总量门限值， 对待转发的 用户请求进行路由决策； 所述服务总量门限值为所述下游 CDN设置的、 所述 下游 CDN能为所述上游 CDN提供服务的上限。
本实施例提供的内容分发装置， 即上游 CDN确定当前服务总量的具体实 现方式不受限制， 例如可包括： 上游 CDN自身进行统计并记录； 或者， 下游 CDN统计并上 ·¾、 由上游 CDN记录或刷新相应结果。 下面对这两种方式， 分 别予以说明内容分发装置的具体结构。
方式一： 上游 CDN自身进行统计并记录。
该方式下， 可选的， 上述通知消息可包括： 用于统计所述当前服务总量 的参考信息。 相应的， 确定模块 82具体可用于根据所述参考信息， 统计并记 录所述当前服务总量。
所述参考信息可包括： 标识信息、 以及开始指示信息或结束指示信息， 所述开始指示信息表示： 所述下游 CDN针对所述上游 CDN转发的用户请求， 开始为用户提供服务； 所述结束指示信息表示： 所述下游 CDN针对所述上游 CDN转发的用户请求， 结束为用户提供服务； 所述标识信息包括： 所述下游 CDN的 CDN标识，或所述上游 CDN根据转发的用户请求为所述下游 CDN分配 的转发标识； 所述当前服务总量包括： 当前并发总请求数； 所述服务总量门 限值包括： 并发总请求数门限值。 该情形下， 确定模块 82具体可用于对当前 已记录的、 与所述标识信息相应的下游 CDN的所述当前并发总请求数， 针对 所述开始指示信息执行加 1操作或针对所述结束指示信息执行减 1操作， 并刷 新当前已记录的相应结果。
和 /或，
所述参考信息可包括： 标识信息和单次流量， 所述标识信息包括： 所述 下游 CDN的 CDN标识，或所述上游 CDN根据转发的用户请求为所述下游 CDN 分配的转发标识； 所述单次流量为所述下游 CDN针对所述上游 CDN当前转发 的用户请求， 为用户提供服务所占用的流量； 所述当前服务总量包括当前并 发总流量； 所述服务总量门限值包括： 并发总流量门限值。 该情形下， 确定 模块 82具体可用于对当前已记录的、 与所述标识信息相应的下游 CDN的所述 当前并发总流量， 执行增加或减少所述单次流量的操作、 并刷新当前已记录 的相应结果。
进一步的， 所述参考信息还可包括： 所述下游 CDN针对所述上游 CDN当 前转发的用户请求， 为用户提供服务所使用的协议类型； 所述服务总量门限 值还包括： 各协议类型的并发总请求数门限值和 /或并发总流量门限值； 相应 的， 确定模块 82还可用于根据所述协议类型， 分类统计所述当前并发总请求 数和 /或当前并发总流量。 和 /或， 所述参考信息还可包括： 所述上游 CDN当前 转发的用户请求所请求内容的内容提供商的域名； 所述服务总量门限值还包 括： 各内容提供商域名对应的并发总请求数门限值和 /或并发总流量门限值； 相应的， 确定模块 82还可用于根据所述内容提供商的域名， 分类统计所述当 前并发总请求数和 /或当前并发总流量。
方式二： 下游 CDN统计并上报、 由内容分发装置， 即上游 CDN记录或刷 新相应结果。
该情形下， 所述通知消息可包括： 标识信息和所述当前服务总量； 所述 标识信息包括： 所述下游 CDN的 CDN标识， 或所述上游 CDN根据转发的用户 请求为所述下游 CDN分配的转发标识。 相应的， 确定模块 82具体可用于根据 所述标识信息和所述当前服务总量， 记录或刷新相应结果。
上述通知消息还可包括所述服务总量门限值， 所述服务总量门限值可包 括以下之一或任意组合： 并发总请求数门限值； 并发总流量门限值； 各协议 类型的并发总请求数门限值和 /或并发总流量门限值； 各内容提供商域名对应 的并发总请求数门限值和 /或并发总流量门限值。
本实施例提供的内容分发装置可作为上游 CDN , 根据与之互连的下游 CDN发送的通知消息， 确定所述下游 CDN为与之相连的上游 CDN提供服务的 当前服务总量， 并根据该当前服务量以及下游 CDN设置的、 所述下游 CDN为 所述上游 CDN能提供的服务总量门限值，对待转发的用户请求进行路由决策， 降低了将用户请求转发到不能提供服务的下游 CDN的几率， 从而提高了为待 转发用户请求选择下游 CDN的准确性， 因而提高了路由决策效率。 本实施例 内容分发装置的实现机理， 可参见图 1、 图 5-图 7关于上游 CDN的相应记载， 在此不再赘述。
图 9为本发明实施例七提供的内容分发装置的结构示意图。 如图 9所示， 本实施例提供的内容分发装置可作为下游 CDN, 其结构可包括： 生成模块 91 和发送模块 92。
生成模块 91可用于生成通知消息， 所述通知消息用于确定下游 CDN为与 之互连的上游 CDN提供服务的当前服务总量； 所述下游 CDN包括所述内容分 发装置。
发送模块 92可用于向所述上游 CDN发送所述通知消息， 以供所述上游 CDN参考所述当前服务总量， 对待转发的用户请求进行路由决策。
通知消息的类型不受限制， 其携带的信息可包括： 用于统计所述当前服 务总量的参考信息； 或者， 标识信息和已统计好的所述当前服务总量。 下面 针对通知消息中携带的这两种不同类型参数对应的技术方案，分别予以说明： 方式一： 通知消息包括： 用于统计所述当前服务总量的参考信息。
该情形下， 所述参考消息可包括： 标识信息以及以下信息中的至少其中 之一： 开始指示信息， 结束指示信息， 单次流量。 所述标识信息包括： 所述 下游 CDN的 CDN标识，或所述上游 CDN根据转发的用户请求为所述下游 CDN 分配的转发标识； 所述开始指示信息表示： 所述下游 CDN针对所述上游 CDN 转发的用户请求， 开始为用户提供服务； 所述结束指示信息表示： 所述下游 CDN针对所述上游 CDN转发的用户请求， 结束为用户提供服务； 所述单次流 量为： 所述下游 CDN针对所述上游 CDN当前转发的用户请求， 为用户提供服 务所占用的流量。
进一步的， 所述参考消息还可包括以下信息中的至少其中之一： 所述下 游 CDN针对所述上游 CDN当前转发的用户请求， 为用户提供服务所使用的协 议类型；所述上游 CDN当前转发的用户请求所请求内容的内容提供商的域名。
方式二： 通知消息包括： 标识信息和已统计好的所述当前服务总量。 该情形下， 所述通知消息可包括： 标识信息和所述当前服务总量； 所述 标识信息包括： 所述下游 CDN的 CDN标识， 或所述上游 CDN根据转发的用户 请求为所述下游 CDN分配的转发标识。
内容分发装置还可包括： 统计模块 93。 统计模块 93可用于统计所述下游 CDN的所述当前服务总量。
其中， 所述当前服务总量可包括： 当前并发总请求数。 该情形下， 统计 为用户提供服务时， 对当前已记录的所述当前并发总请求数执行加 1操作； 以 及， 在所述下游 CDN针对所述上游 CDN转发的用户请求， 结束为用户提供服 务时， 对当前已记录的所述当前并发总请求数执行减 1操作。
和 /或，
所述当前服务总量可包括： 当前并发总流量。 该情形下， 统计模块 93具 体可用于对当前已记录的所述当前并发总流量， 执行增加或减少单次流量的 操作， 并刷新当前已记录的相应结果。 所述单次流量为针对所述上游 CDN当 前转发的用户请求， 为用户提供服务所占用的流量。
进一步的， 统计模块 93还可用于， 根据所述下游 CDN针对所述上游 CDN 当前转发的用户请求， 为用户提供服务所使用的协议类型， 分类统计所述当 前并发总请求数和 /或当前并发总流量； 和 /或， 统计模块 93还可用于， 根据所 述上游 CDN当前转发的用户请求所请求内容的内容提供商的域名， 分类统计 所述当前并发总请求数和 /或当前并发总流量。
上述技术方案中， 内容分发装置还可包括： 时机确定模块 94。 时机确定 模块 94可用于确定所述生成模块生成所述通知消息， 和所述发送模块向所述 上游 CDN发送所述通知消息的时机。 所述时机包括： 所述下游 CDN针对所述 上游 CDN转发的用户请求， 开始或结束为用户提供服务的时刻； 或者， 以预 设时长为周期， 每次预设时长的期满时刻。
上述技术方案中， 所述通知消息还可包括： 服务总量门限值； 所述服务 总量门限值为所述下游 CDN能为所述上游 CDN提供服务的上限， 具体可包括 以下之一或任意组合： 并发总请求数门限值； 并发总流量门限值； 各协议类 型的并发总请求数门限值和 /或并发总流量门限值； 各内容提供商域名对应的 并发总请求数门限值和 /或并发总流量门限值。
本实施例提供内容分发装置可作为下游 CDN, 生成并向上游 CDN发送， 包括有用于统计所述当前服务总量的参考信息、 或者包括有标识信息和已统 计好的所述当前服务总量的通知消息， 以便上游 CDN可参考当前服务总量， 对待转发的用户请求进行路由决策， 从而提高了上游 CDN为待转发用户请求 选择下游 CDN的准确性， 因而提高了路由决策效率。 本实施例内容分发装置 的实现机理， 可参见图 3、 图 5-图 7关于下游 CDN的相应记载， 在此不再赘述。
图 10为本发明实施例八提供的 CDN互连系统的结构示意图。 如图 10所示 的 CDN互连包括：第一 CDN101和第二 CDN102,第一 CDN101和第二 CDN102, 分别为互连的上游 CDN和下游 CDN。 其中， 第一 CDN101的结构可参见图 8对 应实施例的记载， 其实现机理可参见图 1、 图 5-图 7关于上游 CDN的相应记载； 第二 CDN102的结构可参见图 9对应实施例的记载，其实现机理可参见图 3、 图 5-图 7关于上游 CDN的相应记载； 第一 CDN101和第二 CDN 102在 CDN互连系 统的分布， 可参见图 3的记载； 且第一 CDN101和第二 CDN102之间的逻辑接 口， 可参见图 4的记载； 在此不再赘述。
本实施例提供的 CDN互连系统中， 第一 CDN即上游 CDN根据与之互连的 第二 CDN即下游 CDN发送的通知消息， 确定所述下游 CDN为与之相连的上游 CDN提供服务的当前服务总量， 并根据该当前服务量以及下游 CDN设置的、 所述下游 CDN为所述上游 CDN能提供的服务总量门限值， 对待转发的用户请 求进行路由决策，降低了将用户请求转发到不能提供服务的下游 CDN的几率， 从而提高了为待转发用户请求选择下游 CDN的准确性， 因而提高了路由决策 效率。
本领域普通技术人员可以理解： 附图只是一个实施例的示意图， 附图中 的模块或流程并不一定是实施本发明所必须的。
本领域普通技术人员可以理解： 实施例中的装置中的模块可以按照实施 例描述分布于实施例的装置中， 也可以进行相应变化位于不同于本实施例的 一个或多个装置中。 上述实施例的模块可以合并为一个模块， 也可以进一步 拆分成多个子模块。
本领域普通技术人员可以理解： 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成， 前述的程序可以存储于一计算机可读 取存储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而前述 的存储介质包括： ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介 质。
最后应说明的是： 以上实施例仅用以说明本发明的技术方案， 而非对其 限制； 尽管参照前述实施例对本发明进行了详细的说明， 本领域的普通技术 人员应当理解： 其依然可以对前述实施例所记载的技术方案进行修改， 或者 对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不使相应技术 方案的本质脱离本发明实施例技术方案的精神和范围。

Claims

权 利 要 求 书
1、 一种路由决策方法， 其特征在于， 包括：
接收下游 CDN发送的通知消息， 所述通知消息用于确定所述下游 CDN为 与之互连的上游 CDN提供服务的当前服务总量；
根据所述通知消息， 确定所述当前服务总量；
根据所述当前服务总量和服务总量门限值， 对待转发的用户请求进行路 由决策； 所述服务总量门限值为所述下游 CDN设置的、 所述下游 CDN能为所 述上游 CDN提供服务的上限。
2、 根据权利要求 1所述的方法， 其特征在于，
所述通知消息包括： 用于统计所述当前服务总量的参考信息；
根据所述通知消息， 确定所述当前服务总量， 包括： 根据所述参考信息， 统计并记录所述当前服务总量。
3、 根据权利要求 2所述的方法， 其特征在于，
所述参考信息包括： 标识信息， 以及开始指示信息或结束指示信息； 所 述开始指示信息表示： 所述下游 CDN针对所述上游 CDN转发的用户请求， 开 始为用户提供服务； 所述结束指示信息表示： 所述下游 CDN针对所述上游 CDN转发的用户请求， 结束为用户提供服务； 所述标识信息包括： 所述下游 CDN的 CDN标识，或所述上游 CDN根据转发的用户请求为所述下游 CDN分配 的转发标识； 所述当前服务总量包括： 当前并发总请求数； 所述服务总量门 限值包括： 并发总请求数门限值；
所述统计并记录所述当前服务总量， 包括： 对当前已记录的、 与所述标 识信息相应的下游 CDN的所述当前并发总请求数， 针对所述开始指示信息执 行加 1操作或针对所述结束指示信息执行减 1操作， 并刷新当前已记录的相应 结果。
4、 根据权利要求 2或 3所述的方法， 其特征在于，
所述参考信息包括： 标识信息和单次流量； 所述标识信息包括： 所述下 游 CDN的 CDN标识，或所述上游 CDN根据转发的用户请求为所述下游 CDN分 配的转发标识； 所述单次流量为所述下游 CDN针对所述上游 CDN当前转发的 用户请求， 为用户提供服务所占用的流量； 所述当前服务总量包括当前并发 总流量； 所述服务总量门限值包括： 并发总流量门限值；
所述统计并记录所述当前服务总量， 包括： 对当前已记录的、 与所述标 识信息相应的下游 CDN的所述当前并发总流量， 执行增加或减少所述单次流 量的操作， 并刷新当前已记录的相应结果。
5、 根据权利要求 3或 4所述的方法， 其特征在于，
所述参考信息还包括： 所述下游 CDN针对所述上游 CDN当前转发的用户 请求， 为用户提供服务所使用的协议类型； 所述服务总量门限值还包括： 各 协议类型的并发总请求数门限值和 /或并发总流量门限值； 统计所述当前并发 总请求数和 /或当前并发总流量， 包括： 根据所述协议类型， 分类统计所述当 前并发总请求数和 /或当前并发总流量；
和 /或，
所述参考信息还包括： 所述上游 CDN当前转发的用户请求所请求内容的 内容提供商的域名； 所述服务总量门限值还包括： 各内容提供商域名对应的 并发总请求数门限值和 /或并发总流量门限值； 统计所述当前并发总请求数和 /或当前并发总流量， 包括： 根据所述内容提供商的域名， 分类统计所述当前 并发总请求数和 /或当前并发总流量。
6、 根据权利要求 1所述的方法， 其特征在于，
所述通知消息包括： 标识信息和所述当前服务总量； 所述标识信息包括： 所述下游 CDN的 CDN标识， 或所述上游 CDN根据近转发的用户请求为所述下 游 CDN分配的转发标识；
根据所述通知消息， 确定所述当前服务总量， 包括： 根据所述标识信息 和所述当前服务总量， 记录或刷新相应结果。
7、 根据权利要求 1-6任一所述的方法， 其特征在于， 所述通知消息还包 括： 所述服务总量门限值。
8、 一种路由决策方法， 其特征在于，
生成通知消息， 所述通知消息用于确定下游 CDN为与之互连的上游 CDN 提供服务的当前服务总量；
向所述上游 CDN发送所述通知消息， 以供所述上游 CDN参考所述当前服 务总量， 对待转发的用户请求进行路由决策。
9、 根据权利要求 8所述的方法， 其特征在于，
所述通知消息包括： 用于统计所述当前服务总量的参考信息；
所述参考消息包括： 标识信息以及以下信息中的至少其中之一： 开始指 示信息， 结束指示信息， 单次流量；
所述标识信息包括： 所述下游 CDN的 CDN标识， 或所述上游 CDN根据转 发的用户请求为所述下游 CDN分配的转发标识； 所述开始指示信息表示： 所 述下游 CDN针对所述上游 CDN转发的用户请求， 开始为用户提供服务； 所述 结束指示信息表示： 所述下游 CDN针对所述上游 CDN转发的用户请求， 结束 为用户提供服务； 所述单次流量为： 所述下游 CDN针对所述上游 CDN当前转 发的用户请求， 为用户提供服务所占用的流量。
10、 根据权利要求 9所述的方法， 其特征在于， 所述参考消息还包括以下 信息中的至少其中之一：
所述下游 CDN针对所述上游 CDN当前转发的用户请求， 为用户提供服务 所使用的协议类型；
所述上游 CDN当前转发的用户请求所请求内容的内容提供商的域名。
11、 根据权利要求 8所述的方法， 其特征在于，
所述通知消息包括： 标识信息和所述当前服务总量； 所述标识信息包括： 所述下游 CDN的 CDN标识， 或所述上游 CDN根据转发的用户请求为所述下游 CDN分配的转发标识。
12、 根据权利要求 11所述的方法， 其特征在于， 在所述生成通知消息之 前， 所述方法还包括：
统计所述下游 CDN的所述当前服务总量。
13、 根据权利要求 12所述的方法， 其特征在于，
所述当前服务总量包括： 当前并发总请求数； 统计所述下游 CDN的所述 当前服务总量， 包括： 在所述下游 CDN针对所述上游 CDN转发的用户请求， 开始为用户提供服务时， 对当前已记录的所述当前并发总请求数执行加 1操 作； 以及， 在所述下游 CDN针对所述上游 CDN转发的用户请求， 结束为用户 提供服务时， 对当前已记录的所述当前并发总请求数执行减 1操作；
和 /或，
所述当前服务总量包括： 当前并发总流量； 统计所述下游 CDN的所述当 前服务总量， 包括： 对当前已记录的所述当前并发总流量， 执行增加或减少 单次流量的操作， 并刷新当前已记录的相应结果； 所述单次流量为针对所述 上游 CDN当前转发的用户请求， 为用户提供服务所占用的流量。
14、 根据权利要求 13所述的方法， 其特征在于， 统计所述下游 CDN的所 述当前服务总量， 包括：
根据所述下游 CDN针对所述上游 CDN当前转发的用户请求， 为用户提供 服务所使用的协议类型， 分类统计所述当前并发总请求数和 /或当前并发总流 量；
和 /或，
根据所请求内容的内容提供商的域名， 分类统计所述当前并发总请求数 和 /或当前并发总流量。
15、 根据权利要求 8-14任一所述的方法， 其特征在于， 生成所述通知消 息， 和向所述上游 CDN发送所述通知消息的时机， 包括：
所述下游 CDN针对所述上游 CDN转发的用户请求， 开始或结束为用户提 供服务的时刻；
或者， 以预设时长为周期， 每次预设时长的期满时刻。
16、 根据权利要求 8-15任一所述的方法， 其特征在于，
所述通知消息还包括： 服务总量门限值； 所述服务总量门限值为所述下 游 CDN能为所述上游 CDN提供服务的上限；
所述服务总量门限值包括以下之一或任意组合： 并发总请求数门限值； 并发总流量门限值； 各协议类型的并发总请求数门限值和 /或并发总流量门限 值； 各内容提供商域名对应的并发总请求数门限值和 /或并发总流量门限值。
17、 一种内容分发装置， 其特征在于， 所述内容分发装置作为上游 CDN, 包括：
接收模块， 用于接收下游 CDN发送的通知消息， 所述通知消息用于确定 所述下游 CDN为与之互连的所述上游 CDN提供服务的当前服务总量；
确定模块， 用于根据所述通知消息， 确定所述当前服务总量；
决策模块， 用于根据所述当前服务总量和服务总量门限值， 对待转发的 用户请求进行路由决策； 所述服务总量门限值为所述下游 CDN设置的、 所述 下游 CDN能为所述上游 CDN提供服务的上限。
18、 根据权利要求 17所述的装置， 其特征在于，
所述通知消息包括： 用于统计所述当前服务总量的参考信息；
所述确定模块， 具体用于根据所述参考信息， 统计并记录所述当前服务 总量。
19、 根据权利要求 18所述的装置， 其特征在于，
所述参考信息包括： 标识信息、 以及开始指示信息或结束指示信息； 所 述开始指示信息表示： 所述下游 CDN针对所述上游 CDN转发的用户请求， 开 始为用户提供服务； 所述结束指示信息表示： 所述下游 CDN针对所述上游 CDN转发的用户请求， 结束为用户提供服务； 所述标识信息包括： 所述下游 CDN的 CDN标识，或所述上游 CDN根据转发的用户请求为所述下游 CDN分配 的转发标识； 所述当前服务总量包括： 当前并发总请求数； 所述服务总量门 限值包括： 并发总请求数门限值； 所述确定模块， 具体用于对当前已记录的、 与所述标识信息相应的下游
CDN的所述当前并发总请求数，针对所述开始指示信息执行加 1操作或针对所 述结束指示信息执行减 1操作， 并刷新当前已记录的相应结果。
20、 根据权利要求 18或 19所述的装置， 其特征在于，
所述参考信息包括： 标识信息和单次流量； 所述标识信息包括： 所述下 游 CDN的 CDN标识，或所述上游 CDN根据转发的用户请求为所述下游 CDN分 配的转发标识； 所述单次流量为所述下游 CDN针对所述上游 CDN当前转发的 用户请求， 为用户提供服务所占用的流量； 所述当前服务总量包括当前并发 总流量； 所述服务总量门限值包括： 并发总流量门限值；
所述确定模块， 具体用于对当前已记录的、 与所述标识信息相应的下游 CDN的所述当前并发总流量， 执行增加或减少所述单次流量的操作， 并刷新 当前已记录的相应结果。
21、 根据权利要求 19或 20所述的方法， 其特征在于，
所述参考信息还包括： 所述下游 CDN针对所述上游 CDN当前转发的用户 请求， 为用户提供服务所使用的协议类型； 所述服务总量门限值还包括： 各 协议类型的并发总请求数门限值和 /或并发总流量门限值； 所述确定模块还用 于根据所述协议类型， 分类统计所述当前并发总请求数和 /或当前并发总流 量；
和 /或，
所述参考信息还包括： 所述上游 CDN当前转发的用户请求所请求内容的 内容提供商的域名； 所述服务总量门限值还包括： 各内容提供商域名对应的 并发总请求数门限值和 /或并发总流量门限值； 所述确定模块还用于根据所述 内容提供商的域名， 分类统计所述当前并发总请求数和 /或当前并发总流量。
22、 根据权利要求 17所述的装置， 其特征在于，
所述通知消息包括： 标识信息和所述当前服务总量； 所述标识信息包括： 所述下游 CDN的 CDN标识， 或所述上游 CDN根据转发的用户请求为所述下游 CDN分配的转发标识；
所述确定模块， 具体用于根据所述标识信息和所述当前服务总量， 记录 或刷新相应结果。
23、 根据权利要求 17-22任一所述的装置， 其特征在于，
所述通知消息还包括： 所述服务总量门限值。
24、 一种内容分发装置， 其特征在于， 所述内容分发装置作为下游 CDN, 包括：
生成模块， 用于生成通知消息， 所述通知消息用于确定所述下游 CDN为 与之互连的上游 CDN提供服务的当前服务总量；
发送模块， 用于向所述上游 CDN发送所述通知消息， 以供所述上游 CDN 参考所述当前服务总量， 对待转发的用户请求进行路由决策。
25、 根据权利要求 24所述的装置， 其特征在于，
所述通知消息包括： 用于统计所述当前服务总量的参考信息；
所述参考消息包括： 标识信息以及以下信息中的至少其中之一： 开始指 示信息， 结束指示信息， 单次流量；
所述标识信息包括： 所述下游 CDN的 CDN标识， 或所述上游 CDN根据转 发的用户请求为所述下游 CDN分配的转发标识； 所述开始指示信息表示： 所 述下游 CDN针对所述上游 CDN转发的用户请求， 开始为用户提供服务； 所述 结束指示信息表示： 所述下游 CDN针对所述上游 CDN转发的用户请求， 结束 为用户提供服务； 所述单次流量为： 所述下游 CDN针对所述上游 CDN当前转 发的用户请求， 为用户提供服务所占用的流量。
26、 根据权利要求 25所述的装置， 其特征在于，
所述参考消息还包括以下信息中的至少其中之一：
所述下游 CDN针对所述上游 CDN当前转发的用户请求， 为用户提供服务 所使用的协议类型；
所述上游 CDN当前转发的用户请求所请求内容的内容提供商的域名。
27、 根据权利要求 24所述的装置， 其特征在于，
所述通知消息包括： 标识信息和所述当前服务总量； 所述标识信息包括： 所述下游 CDN的 CDN标识， 或所述上游 CDN根据转发的用户请求为所述下游 CDN分配的转发标识。
28、 根据权利要求 24所述的装置， 其特征在于， 还包括：
统计模块， 用于统计所述下游 CDN的所述当前服务总量。
29、 根据权利要求 28所述的装置， 其特征在于，
所述当前服务总量包括： 当前并发总请求数； 所述统计模块具体用于： 时， 对当前已记录的所述当前并发总请求数执行加 1操作； 以及， 在所述下游 CDN针对所述上游 CDN转发的用户请求， 结束为用户提供服务时， 对当前已 记录的所述当前并发总请求数执行减 1操作；
和 /或，
所述当前服务总量包括： 当前并发总流量； 所述统计模块具体用于： 对 当前已记录的所述当前并发总流量， 执行增加或减少单次流量的操作， 并刷 新当前已记录的相应结果； 所述单次流量为针对所述上游 CDN当前转发的用 户请求， 为用户提供服务所占用的流量。
30、 根据权利要求 29所述的装置， 其特征在于，
所述统计模块， 还用于根据所述下游 CDN针对所述上游 CDN当前转发的 用户请求， 为用户提供服务所使用的协议类型， 分类统计所述当前并发总请 求数和 /或当前并发总流量；
和 /或，
所述统计模块， 还用于根据所述上游 CDN当前转发的用户请求所请求内 容的内容提供商的域名， 分类统计所述当前并发总请求数和 /或当前并发总流 量。
31、 根据权利要求 24-30任一所述的装置， 其特征在于， 还包括： 时机确定模块， 用于确定所述生成模块生成所述通知消息， 和所述发送 模块向所述上游 CDN发送所述通知消息的时机； 所述时机包括：
所述下游 CDN针对所述上游 CDN转发的用户请求， 开始或结束为用户提 供服务的时刻；
或者， 以预设时长为周期， 每次预设时长的期满时刻。
32、 根据权利要求 24-31任一所述的装置， 其特征在于，
所述通知消息还包括： 服务总量门限值； 所述服务总量门限值为所述下 游 CDN能为所述上游 CDN提供服务的上限；
所述服务总量门限值包括以下之一或任意组合： 并发总请求数门限值； 并发总流量门限值； 各协议类型的并发总请求数门限值和 /或并发总流量门限 值； 各内容提供商域名对应的并发总请求数门限值和 /或并发总流量门限值。
33、 一种内容分发网络互连系统， 其特征在于， 包括：
第一 CDN, 包括如权利要求 17-23任一所述的装置；
第二 CDN, 包括如权利要求 24-32任一所述的装置；
所述第一 CDN和所述第二 CDN, 分别为互连的上游 CDN和下游 CDN。
PCT/CN2011/075300 2011-06-03 2011-06-03 路由决策方法、内容分发装置和内容分发网络互连系统 WO2011157173A2 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2011/075300 WO2011157173A2 (zh) 2011-06-03 2011-06-03 路由决策方法、内容分发装置和内容分发网络互连系统
CN201180000966.XA CN102257777B (zh) 2011-06-03 2011-06-03 路由决策方法、内容分发装置和内容分发网络互连系统
US14/095,265 US9602378B2 (en) 2011-06-03 2013-12-03 Route decision method, content delivery apparatus, and content delivery network interconnection system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/075300 WO2011157173A2 (zh) 2011-06-03 2011-06-03 路由决策方法、内容分发装置和内容分发网络互连系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/095,265 Continuation US9602378B2 (en) 2011-06-03 2013-12-03 Route decision method, content delivery apparatus, and content delivery network interconnection system

Publications (2)

Publication Number Publication Date
WO2011157173A2 true WO2011157173A2 (zh) 2011-12-22
WO2011157173A3 WO2011157173A3 (zh) 2012-05-03

Family

ID=44983374

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/075300 WO2011157173A2 (zh) 2011-06-03 2011-06-03 路由决策方法、内容分发装置和内容分发网络互连系统

Country Status (3)

Country Link
US (1) US9602378B2 (zh)
CN (1) CN102257777B (zh)
WO (1) WO2011157173A2 (zh)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103297337A (zh) * 2012-02-23 2013-09-11 中兴通讯股份有限公司 一种实现内容分发网络互联路由的方法及系统
CN104348798B (zh) * 2013-07-31 2019-03-15 深圳市腾讯计算机系统有限公司 一种分配网络的方法、装置、调度服务器和系统
CN103685576A (zh) * 2014-01-03 2014-03-26 中国联合网络通信集团有限公司 一种cdn节点的交互方法及cdn管理系统
CN104349178B (zh) * 2014-11-21 2018-02-09 赛特斯信息科技股份有限公司 实现按需实时转码和自适应码率流媒体播放的系统及方法
CN105992016A (zh) * 2015-02-05 2016-10-05 天脉聚源（北京）科技有限公司 一种hls在线转码方法及系统
EP3298806B1 (en) * 2015-05-20 2019-10-16 Convida Wireless, LLC Methods and apparatus for analyzing and grouping service layer subscriptions and notifications for enhanced efficiency
CN104967967B (zh) * 2015-05-28 2020-06-02 海尔优家智能科技（北京）有限公司 一种多跳发现资源的方法和装置
FR3051307A1 (fr) * 2016-05-10 2017-11-17 Orange Procede d'acces a un contenu heberge sur un serveur selectionne en fonction de la localisation du terminal utilisateur
US10892940B2 (en) * 2017-07-21 2021-01-12 Cisco Technology, Inc. Scalable statistics and analytics mechanisms in cloud networking
CN110838932A (zh) * 2018-08-17 2020-02-25 阿里巴巴集团控股有限公司 网络限流方法、装置以及电子设备
US10467562B1 (en) * 2019-02-18 2019-11-05 Coupang, Corp. Systems and methods for computerized balanced delivery route assignment
CN112688995B (zh) * 2020-12-16 2021-12-14 中国联合网络通信集团有限公司 一种系统迁移方法和装置
CN113746920B (zh) * 2021-09-03 2023-11-28 北京知道创宇信息技术股份有限公司 一种数据转发方法、装置、电子设备及计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004073269A1 (ja) * 2003-02-13 2004-08-26 Fujitsu Limited 伝送システム，配信経路制御装置，負荷情報収集装置および配信経路制御方法
CN1859213A (zh) * 2006-03-01 2006-11-08 华为技术有限公司 在内容分发网络中保障服务水平的系统和方法
CN101263460A (zh) * 2005-08-01 2008-09-10 杰出网络公司 重负载下的路由选择
CN101702669A (zh) * 2009-11-18 2010-05-05 上海网宿科技股份有限公司 带宽分配方法和系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7519734B1 (en) * 2006-03-14 2009-04-14 Amazon Technologies, Inc. System and method for routing service requests
EP2234397A1 (en) * 2009-03-24 2010-09-29 Thomson Licensing Methods for delivering and receiving interactive multimedia data attached to an audio video content

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004073269A1 (ja) * 2003-02-13 2004-08-26 Fujitsu Limited 伝送システム，配信経路制御装置，負荷情報収集装置および配信経路制御方法
CN101263460A (zh) * 2005-08-01 2008-09-10 杰出网络公司 重负载下的路由选择
CN1859213A (zh) * 2006-03-01 2006-11-08 华为技术有限公司 在内容分发网络中保障服务水平的系统和方法
CN101702669A (zh) * 2009-11-18 2010-05-05 上海网宿科技股份有限公司 带宽分配方法和系统

Also Published As

Publication number Publication date
US20140095707A1 (en) 2014-04-03
WO2011157173A3 (zh) 2012-05-03
CN102257777B (zh) 2015-03-11
US9602378B2 (en) 2017-03-21
CN102257777A (zh) 2011-11-23

Similar Documents

Publication Publication Date Title
WO2011157173A2 (zh) 路由决策方法、内容分发装置和内容分发网络互连系统
WO2018152919A1 (zh) 一种路径选取方法及系统、网络加速节点及网络加速系统
EP2591573B1 (en) Method and apparatus for traffic classification
WO2016033979A1 (zh) 用户服务提供的处理方法、装置及系统
RU2571377C2 (ru) Система и способ управления службами, развитый nodeb и шлюз сети пакетной передачи данных
US20120198020A1 (en) Content distribution within a service provider network
US20080195511A1 (en) Method and system for accounting, accounting client and accounting processing unit
WO2021218718A1 (zh) 确定用户面功能及信息提供的方法、设备及介质
US9172760B2 (en) Method and device for monitoring service usage amount
WO2012106918A1 (zh) 内容处理方法、装置和系统
US20150207872A1 (en) Method and system for performing mobile cdn request routing
US20100080127A1 (en) Interception method and device thereof
CN107211035B (zh) 用于在内容递送网络中监测服务的方法和网络节点
TW201345285A (zh) 為無線使用者提供智慧型編解碼率調整的方法及設備
WO2012075970A1 (zh) 一种获取媒体内容的方法、设备及系统
CN103119981B (zh) 服务质量控制方法和设备
US20170310493A1 (en) Network entity and service policy management method
EP4091294A1 (en) A method of and a session management function for provisioning a user plane function, a method of and a user plane function for processing user traffic and a method of and charging function for charging user traffic
WO2022206529A1 (zh) 一种资源请求处理的方法、装置、计算机设备及介质
WO2012167546A1 (zh) 业务分发控制方法和设备
WO2009124474A1 (zh) 内容索引处理方法及系统、内容路由功能及内容分发控制实体
WO2011109934A1 (zh) 用于控制用户终端设备的服务质量的方法及装置
Ahdan et al. Adaptive Forwarding Strategy in Named Data Networking: A Survey
RU2656870C1 (ru) Способ, приспособление и устройство для управления политиками и тарификации
US20220021920A1 (en) Communication entity and a method for transmitting a video data stream

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180000966.X

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11795139

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11795139

Country of ref document: EP

Kind code of ref document: A2