Content delivery

By using the rate evaluation module in the agent to identify and select the appropriate encoded bit rate subset, controlling the delivery rate of content fragments, the problem of low multicast reception efficiency in the m-ABR system is solved, and more efficient multicast usage and Improved client experience quality.

CN118947099APending Publication Date: 2024-11-12BRITISH TELECOM PLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380028357.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-29
Filing Date
2023-03-14
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The existing multicast adaptive bit rate (m-ABR) system has inefficient problems in data delivery rates and timing, which makes it difficult for clients to receive content fragments of different quality levels through multicast, especially when switching the ABR level frequently. , resulting in waste of resources and inefficient delivery.

Method used

By using the rate evaluation module in the proxy, identify the most frequently requested encoded bitrates and select an appropriate subset of encoded bitrates based on the bitrate, the delivery rate of the content fragment is controlled to affect the quality of subsequent content fragments requested by the client device by requesting subsequent content fragments by the client device Level, concentrating requests around a subset of available ABR levels, thereby improving multicast scalability.

Benefits of technology

It realizes more efficient and extensive multicast use, improves the efficiency of network optimization technology, reduces the demand for unicast servers, and improves the experience quality of client devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118947099A_ABST
    Figure CN118947099A_ABST
Patent Text Reader

Abstract

A method of controlling a delivery rate of content to a client device to affect a quality level at which the client device requests subsequent segments of content is provided. An object is to affect a client device such that it requests a piece of content at a consistent adaptive bitrate (ABR) level, where the level is a level at which many client devices are requesting a piece of content. The result is that the requests are more concentrated around a subset of available ABR levels. This enables any subsequent multicast to be used more efficiently and widely.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of managing content delivery in a network, and in particular to managing content delivery using a combination of unicast and multicast. Background Art

[0002] Video content is currently typically delivered to a series of client devices using unicast delivery, where a single data stream is transmitted to each individual client device. Web (HTTP) technology is used for content delivery, where the content is segmented into short segment files, typically about six to ten seconds in duration, so that each segment file can be requested by a client device and delivered to the client device using HTTP.

[0003] Each segment can also be encoded at a set of quality levels, each with a different bitrate and therefore a different file size. The client device monitors its buffer level and the achieved network throughput, and based on these determines the quality to request for the next segment in order to achieve a good compromise between media quality and timely delivery. This is often referred to as adaptive bitrate (ABR) streaming.

[0004] However, HTTP is delivered by unicast (one-to-one) transmission, so it is inefficient for delivering the same content to many client devices at the same time. Multicast (one-to-many) transmission will be more efficient. However, multicast is rarely used for any service except the online linear video channel of the network operator that is delivered to its own set-top box at present. Its main reason is that multicast is not suitable for open use on the Internet.

[0005] In order to bring the benefits of multicast scalability to HTTP-based Internet media streaming, a class of technologies called Multicast-Adaptive Bitrate (m-ABR) is being studied and standardized.

[0006] Multicast Adaptive Bitrate (m-ABR) is a relatively new technology. Its purpose is to allow more efficient delivery of ABR content over a network by enabling the use of multicast for content streams where many clients request the same content at approximately the same time.

[0007] One context for many m-ABR systems is to deploy multicast and enable m-ABR without making any changes to client devices and client applications that already support HTTP (unicast) streaming. This can be achieved using a hybrid approach that utilizes a combination of both multicast and unicast delivery, where a proxy is inserted between the client device and the content server. The proxy can inspect content requests from client devices and, when appropriate, subscribe to multicast streams, receive multicast content, and serve that content to the client, with the content packaged to look like unicast delivered content.

[0008] Examples of such hybrid solutions include: Cable Labs’ “IP Multicast Adaptive Bit Rate Architecture Technical Report” OC-TR-IP-MULTI-ARCH-C01-161026, 26 / 10 / 2016; 3GPP specifications 23.246 (MBMS Architecture and Functional Description), 26.346 (MBMS Protocol and Codec) and 26.347 (MBMS API); and DVB “Adaptive Media Streaming over IP Multicast” ETSI TS103769V1.1.1 (2020-11).

[0009] There are several issues related to the rate and timing of data delivery that prevent such m-ABR systems from functioning correctly.

[0010] As described, ABR delivery involves encoding content at multiple quality levels, at different encoding bit rates, so that clients can request content segments at quality levels and bit rates appropriate for their current network throughput. However, in m-ABR systems, multicast is typically only provided with a subset of the bit rates available through unicast in the ABR tier. Therefore, clients requesting content segments at quality levels in the ABR tier will not be able to receive those content segments through multicast.

[0011] Furthermore, clients that frequently switch between different levels in the ABR hierarchy when making requests will also have difficulty receiving content segments via multicast. This is because it takes time and resources to change the multicast stream to which the client is subscribed, and it is inefficient to deliver content segments at one quality level via multicast and at another quality level via unicast if the client has switched to requesting segments at a different level in the ABR hierarchy than was received by multicast. Summary of the invention

[0012] It is an object of examples of the present invention to provide an improved content delivery mechanism that addresses one or more of the above-mentioned problems.

[0013] According to an example of the present invention, a method for managing content delivery through a proxy in a network is provided, wherein the network comprises a rate evaluation module connected to a plurality of proxies, each proxy being connected to a corresponding one or more client devices, wherein the content comprises a series of segments, wherein each segment is encoded at a plurality of bit rates, and the method comprises:

[0014] i) receiving, at a corresponding proxy, a request for a segment from each of a plurality of client devices, and determining an encoding bit rate corresponding to each requested segment;

[0015] ii) identifying, by a rate estimation module, a subset of encoding bit rates as the most frequently requested bit rates;

[0016] iii) receiving, at the corresponding proxy, a request for a segment from a target client device, and determining a further encoding bit rate associated with the segment requested by the target client device;

[0017] iv) selecting an encoding bit rate from the subset of encoding bit rates based on the further encoding bit rate;

[0018] v) when the encoding bit rate of the segment most recently requested by the target client device is higher than the selected bit rate, delivering the most recently requested segment from the proxy to the target client device at a delivery rate lower than the rate at which the requested segments are received by the proxy.

[0019] The selected one encoding bit rate of the subset of encoding bit rates may be the further encoding bit rate at which a majority of further requested segments are encoded.

[0020] Examples of the present invention allow for controlling the rate at which content segments are delivered to client devices to influence the quality at which the client device requests subsequent content segments. The goal is to influence the client device so that it requests content segments at a consistent ABR level, where this level is the level at which many client devices are requesting content segments. The result is that requests are more concentrated around a subset of available ABR levels. This enables more efficient and extensive use of any subsequent multicast.

[0021] Subsequent network optimization techniques such as caching and multicasting become more efficient as more clients request the same content at the same bitrate. Otherwise, the ability of an adaptive bitrate client to select from multiple bitrates independent of each other can work against network optimization techniques without necessarily improving the quality of experience.

[0022] The present invention operates without explicit knowledge of the media bitrate, where any required information can be inferred from observation of HTTP request and response pairs. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] For a better understanding of the present invention, reference will now be made, by way of example only, to the accompanying drawings, in which:

[0024] Figure 1 is a system diagram showing the main components of an example of the present invention;

[0025] Figure 2 is an example histogram showing the sizes of requested content fragments;

[0026] Figure 3 is a table showing examples of calculated segment sizes and encoding bit rates;

[0027] Figure 4 is a table showing an example summary of requests for content segments at each calculated bitrate level;

[0028] Figure 5 is a flow chart outlining the steps of an example of the present invention. DETAILED DESCRIPTION

[0029] The present invention is described herein with reference to specific embodiments. However, the present invention is not limited to these embodiments.

[0030] Examples of the present invention provide a method of controlling the delivery rate of content to a client device to influence the quality level at which the client device requests subsequent content segments. The goal is to influence the client device so that it requests content segments at a consistent adaptive bit rate (ABR) level, where this level is the level at which many client devices are requesting content segments. The result is that requests are more concentrated around a subset of available ABR levels. This enables more efficient and extensive use of any subsequent multicast.

[0031] Figure 1 An adaptive bitrate (ABR) streaming system 100 including the main components of an example of the present invention is shown. The system 100 includes a content source 102, a content encoder 104, a multicast transmitter 106, a rate estimation module 108, a unicast content server 110, a proxy 112, and a client device 114. The content source 102 provides content, such as live sports or TV broadcasts, to the content encoder 104 in the form of video sequences.

[0032] The proxy 112 may be located within a device such as a home gateway or router.

[0033] It is assumed that the client device 114 is running a client application, which is the source of the content request. For simplicity, the term client device has been used to refer to a client device running a client application.

[0034] The content encoder 104 receives content from the content source 102 and encodes it using a suitable compression scheme (such as ITU-T Recommendation H.264 for video content), and divides the encoded content into a series of content segments, each of which typically has a duration of 2 seconds to 10 seconds. The content encoder 104 also encodes the content at one or more quality levels or bit rates, thereby generating one or more encoded segments (at each quality level) corresponding to each uncompressed content segment. This arrangement is a typical arrangement for adaptive bitrate streaming services.

[0035] The content segments encoded at one quality level corresponding to one encoding bit rate are delivered to the multicast transmitter 106 for transmission via multicast to any device subscribed to the corresponding multicast source. However, the present invention is not limited to this case and is also applicable when the content segments encoded at multiple quality settings corresponding to multiple encoding bit rates are delivered to the multicast transmitter 106 for transmission via multicast on multiple multicast channels (one channel for each quality setting).

[0036] The multicast transmitter 106 sends a stream of encoded content segments over a suitably configured multicast channel to all devices that have subscribed to the multicast channel.

[0037] The system 100 also includes a rate assessment module 108, the operation of which will be described below.

[0038] Content encoder 104 passes the encoded content segment data encoded at all required bit rates to unicast server 110 where the data is stored and made available for delivery via unicast. Unicast server 110 responds to unicast requests for content segments with unicast responses using the stored data.

[0039] The client device 114 may obtain a manifest file from the unicast server 110. The manifest file is used by the client device to identify where the segments are located (via the URLs in the manifest). The client device 114 may then request the segments in sequence using HTTP requests from the unicast server 110 and concatenate them to form a continuous stream of segments for playback. When each segment is available at multiple encoding bit rates on the unicast server 110, the client device 110 determines for each content segment to request its encoding bit rate (quality), taking into account factors such as available network throughput and how much data has been received and buffered at the client device awaiting playout.

[0040] Some HTTP requests made by client devices 114 for content will not utilize multicast delivery, but instead will be sent directly to unicast server 110, which delivers the requested content via unicast. Other requests by client devices 114 for content that may benefit from multicast delivery are redirected to or simply intercepted by proxy 112, and may be handled according to the examples described below.

[0041] The client device 114 may request and receive segments from the unicast server 110 from the beginning to the end of the streaming session. However, in some cases, the proxy 112 determines that multicast delivery may be used to receive some segments.

[0042] Proxy 112 monitors unicast content requests from client devices 114 and knows when content requested by client devices 114 is available for multicast reception.

[0043] The proxy 112 determines when a client device request for content can be satisfied using data that can be delivered by multicast, joins the relevant multicast channel at the appropriate time, and after receiving the data via multicast, replies to the client device request for unicast content, where the content is received via multicast but packaged as a unicast content response.

[0044] The client device 114 need not be aware of the proxy 112 and whether the content is delivered by unicast from a unicast content source via the proxy or by multicast to the proxy, which then delivers the content to the client device 114 in a unicast format.

[0045] The presence proxy 112 can use the data that may be delivered by the multicast to determine a number of ways in which a client device's request for content may be satisfied.

[0046] For example, if the client device 114 has made multiple consecutive requests for content segments at the same encoding quality level, that quality level may be achieved via multicast delivery, and each of those content segments has been delivered in less time than the segment period.

[0047] In another example, the proxy 112 may ignore the fact that some segments took more time than the segment period to be delivered, assuming that many segments were delivered in a period much less than the segment period. The proxy 112 may also ignore some variations in the quality at which the segments were requested if there is sufficient network throughput to deliver the content segments at a quality level available for multicast most or all of the time.

[0048] In a typical system, when the proxy 112 has decided to satisfy a client device request for content using data that can be delivered by multicast, the proxy 112 stops forwarding the client device request for content to the unicast server 110, and instead takes appropriate actions to join and obtain from the multicast channel the data requested by the client device 114. The proxy 112 then delivers those contents received via multicast to the client device 114, with the data formatted as a unicast response.

[0049] However, in situations where not all quality levels are available for multicast, or when clients frequently switch between different levels in the ABR hierarchy, this approach may lead to previously recognized problems. An example of how content delivery can be managed in an improved manner that mitigates some of these problems is now described.

[0050] In an example, it is envisioned that system 100 may include multiple client devices. Each client device 114 is logically associated with one proxy 112, but in practice a single proxy may provide content to more than one client device. In this case, the proxy may only need to receive one copy of a content segment from a unicast server 110 or a multicast transmitter 106, even when more than one client device requests it.

[0051] Examples of the present invention are applied independently to each content stream. The content stream can be identified using elements of the domain and path of the URL associated with the requested fragment. For example, the stream can be identified from a path prefix or using a regular expression. In the following description, it will be assumed that all URLs refer to the same content stream.

[0052] Examples of the present invention are described below.

[0053] Client devices 114 request content segments from unicast server 110. These requests and associated responses are passed through proxy 112.

[0054] If known, the proxy 112 stores the ABR level L n , client device 114 has requested a content segment at this ABR level, index n. Proxy 112 also stores the time t at which the request was made by client device 114 n , size S n The segments are stored in bytes, for example, of the segments delivered from the unicast server 110, and the rate R at which the segments are delivered from the unicast server 110 to the proxy 112 is determined and stored. n .

[0055] The agent 112 can determine the ABR level L n, the client device 114 has requested the content segment at the ABR level to the URL that the client device 114 used to request the content segment. For example, if the client device 114 has requested https: / / t2-btsport-live-hls-prod.akamaized.net / out / u / bts1 / bts1_7_15055280.ts?m=1543850508, then if the proxy 112 understands the format of the URL, it can determine that the client device 114 has requested the ABR level L. n A content fragment equal to 7.

[0056] Sometimes, either after each content segment request and response or less frequently, proxy 112 reports to rate assessment module 108 data it has stored about requests that client devices 114 have made for content segments. This data may include the L of one or more segments. n (ABR level), t n (Time), S n (size) and R n (rate).

[0057] The system 100 may include a plurality of proxies (or a population of proxies), wherein each proxy has one or more client devices connected thereto, and wherein each proxy will receive requests for content segments from one or more client devices connected thereto. Thus, there is effectively a population of proxies as well as a population of client devices in the system 100. Each proxy is connected to a rate assessment module 108.

[0058] The rate evaluation module 108 receives information from the proxy group about the content segments requested by the client device group. If the proxy group is able to provide the ABR level L of the requested content segment, n , the rate assessment module 108 can use this information directly. Otherwise, the rate assessment module 108 can analyze the size S of the content segment that has been delivered. n to associate an ABR level with each content fragment requested.

[0059] Figure 2 An example of a histogram that the rate assessment module 108 may generate based on information it receives from a proxy population about the sizes of segments that client devices have requested is shown. Since most HTTP adaptive streaming systems use constant bitrate encoding for segments, the sizes of segments will be clustered around a set of discrete values, each such discrete value corresponding to a nominal encoding bitrate. Larger segment sizes tend to be associated with higher nominal encoding bitrates and higher video quality. Figure 2 Clustering around four discrete values ​​is shown.

[0060] The rate assessment module 108 may analyze these statistics regarding the sizes of requested content segments to generate summary statistics at the ABR level. Figure 3 An example is shown in FIG. 1 , where rate assessment module 108 has identified four ABR levels, and for each ABR level has calculated the average segment size and the 2% and 98% percentiles. In this case, there is no overlap between the 98% percentile for one ABR level and the 2% percentile for the next higher ABR level. These statistics can be used by rate assessment module 108 and proxy 112 to associate requested content segments with ABR levels using the size of the content segments. This association may not actually be correct in all cases, but any such misclassification will not prevent system operation.

[0061] The rate assessment module 108 can also determine the encoding bit rate of each ABR level identified by analyzing the time interval between requests for content fragments from the same client device. Typically, client devices will request content fragments at regular time periods equal to the fragment interval, but this may not always be the case. In some cases, client devices may request the same fragment more than once, usually at different quality levels (different encoding bit rates). And sometimes, client devices will have longer periods between requests for content fragments, reasons including low network throughput preventing content fragments from being delivered within the fragment period, and user pausing playback and restoring later. However, the rate assessment module 108 can determine a good estimate of the fragment interval by calculating the typical time interval between the client device's request for content fragments and the request from multiple client devices. A method for calculating this typical time interval between requests for content fragments is to use the median of the time interval.

[0062] The rate evaluation module 108 processes the information it has received from the proxy population to determine ABR levels at which content segments in the identified ABR levels have been frequently requested, and ABR levels at which content segments in the identified ABR levels have been less frequently requested. The rate evaluation module 108 may do this, for example, by creating a histogram of the frequency at which content segments have been requested at different ABR levels. If the proxy population is able to provide an ABR level L at which content segments have been requested, the rate evaluation module 108 may determine the frequency at which content segments have been requested. n , the rate assessment module 108 may use this information directly, otherwise it may use the above classification using the size of the requested content segment.

[0063] ABR Level 1 is a low bitrate, low quality level used by some client devices when network throughput is poor. To maintain continuity of service, it is important that client devices can request and receive this ABR level. ABR Level 2, ABR Level 3, and ABR Level 4 provide increasing quality levels as bitrate requirements increase.

[0064] Considering the processed data, the rate assessment module 108 may conclude that since ABR levels 2 and 4 are frequently requested, these should be available via multicast. And since ABR level 3 is less frequently requested, this should not be available via multicast. But in addition, if the client device were to request content segments at ABR level 2 or 4, the overall system performance may be improved. If no content segments are requested at ABR level 3, caching may be more efficient for unicast delivery, and if more content segments are requested at ABR level 2 or 4, more use may be made of multicast, since these ABR levels are most likely to be available via multicast, assuming they are most frequently requested.

[0065] refer to Figure 4 The summary statistics in the table of , which shows the processed data summarized by the percentage of requests for each ABR level. In this example, ABR levels 1 and 3 have the lowest percentage of requests, and ABR levels 2 and 4 have a higher percentage of requests.

[0066] The rate estimation module 108 reports to the proxy group the information it has determined about the ABR level, the size of the segment, and the encoding bit rate, such as Figure 3 It also reports that content fragments are frequently requested at ABR levels 2 and 4, and less frequently requested at ABR level 3, such as Figure 4 The rate evaluation module 108 can provide guidance to the agent group based on this information, for example, taking no action to try to influence the ABR level decision of the client device, or taking action to try to influence the ABR level decision of the client device to avoid selecting one or more specific ABR levels.

[0067] If proxy 112 was previously unable to determine ABR level L from a request made by client device 114 for segment n n For example, since it cannot be parsed from the HTTP GET request, the proxy 112 uses the statistics provided by the rate evaluation module 108 and the stored segment size S n To determine the possible ABR level L n , and store the determined L n As an example, use Figure 3 If the stored fragment Sn =3.89 megabytes (Mbyte), proxy 112 can conclude that the segment is requested at ABR level 3 because the size is between the 2% and 98% percentiles for ABR level 3 as reported by rate assessment module 108.

[0068] Proxy 112 receives and acts upon this information and guidance from rate assessment module 108. Proxy 112 may accordingly set a parameter indicative of its mode of operation M. If rate assessment module 108 recommends that no action be taken to attempt to influence the ABR level decision of the client device, then M may be set equal to "off". Otherwise, proxy 112 may set M equal to one of two possible values ​​depending on whether proxy 112 deems it appropriate to follow guidance from rate assessment module 108 to attempt to influence the ABR level decision of the client device.

[0069] Proxy 112 considers data that it has previously collected and stored regarding the ABR levels at which client devices 114 have requested content segments. In the event that client devices 114 request content segments at a consistent ABR level, even if that level is a level that rate evaluation module 108 indicates is not requested as frequently as other levels (such as ABR level 3 in the example above), proxy 112 may determine not to take a particular action in response to information from rate evaluation module 108, and may set M equal to “unconstrained”.

[0070] In the case where the client device 114 has requested content segments at inconsistent ABR levels, and in particular in the case where the client device 114 has requested most content segments at a level lower than the infrequently requested level indicated by the rate evaluation module 108 (e.g., see Figure 4 , at ABR level 3), proxy 112 may take actions to attempt to influence client device 114 to not request subsequent content segments at the infrequent request level, and may set M equal to “limited”.

[0071] In this example, where client device 114 has requested most content segments at ABR level 2 or lower and a few content segments at ABR level 3, proxy 112 may take action to influence client device 114 to request subsequent content segments not at ABR level 3 but preferably at ABR level 2. Although this may result in some content segments being requested at ABR level 2 instead of ABR level 3, the quality of experience for users of client device 114 may actually be improved, as consistent quality has been found to provide a better quality of experience than variable quality. Additionally, by client device 114 always requesting content segments at ABR level 2, multicast may be used to deliver content segments to proxy 112, thereby reducing demands on the network and unicast server 110, which in turn may allow higher quality content segments to be delivered to some client devices.

[0072] The proxy 112 uses the operation mode parameter M to indicate which of the two operation modes is in use, ie, whether to attempt to influence the client device 114 to not request content segments at an ABR level that is infrequently requested by the client device population.

[0073] When M is equal to "limited", the proxy 112 maintains an upper threshold T and uses the upper threshold T to limit the rate at which content segments are delivered from the proxy 112 to the client device 114 in an attempt to influence the ABR level at which the client device 114 requests the content segments.

[0074] When M equals “unconstrained,” proxy 112 does not change upper threshold T and does not use the threshold at all, and simply forwards content segments received from unicast server 110 to client device 114 as fast as they are received from unicast server 110 .

[0075] Proxy 112 may determine whether to set M equal to “restricted” or “unrestricted” based on information it has stored about requests for content segments from client devices 114 .

[0076] The proxy 112 may use the R of the most recently requested and delivered content segments. n The average delivery rate is calculated using one or more stored values For delivering content segments from unicast server 110 to proxy 112. This average rate can be calculated as R n The arithmetic, geometric, or harmonic mean of the values ​​of , or calculated as the median or a particular percentile, or calculated as any other representative value. As an example, can be calculated as R n The arithmetic mean of the five most recent values ​​of .

[0077] The agent 112 can use the stored Ln One or more values ​​to calculate the average ABR level of the most recently requested content fragments This can also be calculated for any representative value. As an example, can be calculated as L n The arithmetic mean of the five most recent values ​​of .

[0078] Proxy 112 can be used and These calculated values ​​are used to set or change the value of M.

[0079] If M is equal to "restricted", then proxy 112 may determine to change M to "unrestricted" if the most recently requested content segment has been delivered relatively quickly from unicast server 110 to proxy 112. For example, proxy 112 may is compared to the bitrate threshold, and if greater than the threshold, M is set equal to "unconstrained" so that the rate at which subsequent content segments are delivered from proxy 112 to client device 114 is not limited by proxy 112. For example, by setting the bitrate threshold to the encoding bitrate at ABR level 4, M will be changed to "unconstrained" when, on average, there is a sufficient data rate for timely delivery of segments at ABR level 4.

[0080] If M is equal to "unconstrained", the proxy may determine to change M to "constrained" if the content segment was recently requested at a lower ABR level (such as at ABR levels 2 and 3). For example, the proxy 112 may is compared to the ABR level threshold, and if less than the threshold, M is set equal to "limited" to attempt to influence client device 114 to not request subsequent content fragments at ABR level 3. By setting the ABR level threshold to 3, proxy 112 will switch to attempting to influence the ABR decision of client device 114 when more fragments are requested at ABR level 2 than at ABR level 4.

[0081] Described below is how proxy 112 may take actions to attempt to influence client device 114 to not request subsequent content fragments at ABR level 3, but instead request subsequent content fragments at ABR level 2 by controlling the rate at which content fragments are delivered from proxy 112 to client device 114, when operating mode parameter M is equal to "limited."

[0082] The goal is for proxy 112 to deliver content segments to client device 114 at a rate that influences client device 114 to request subsequent content segments at ABR level 2, without preventing the client from requesting subsequent content segments at ABR level 4 (if network conditions permit). Proxy 112 may also choose to stop controlling the rate at which content segments are delivered to client device 114 if the proxy believes that client device 114 will always request content segments at ABR level 3 and above, because in this case influencing client device 114 to always request content segments at ABR level 2 may significantly degrade video quality.

[0083] The proxy 112 sets an initial upper threshold value T for the rate at which it will deliver content segments to the client device 114. If content segments are received from the unicast server 110 at a rate lower than T at the proxy 112, the proxy 112 will not be able to deliver the content segments to the client device 114 at the rate T. The initial upper threshold value T can be set in various ways, including but not limited to the encoding bit rate of ABR level 3 indicated by the rate evaluation module 108, or the rate at which one or more previous segments are received from the unicast server 110, or an average of the rates.

[0084] Subsequently, in the event that client device 114 requests a content segment at an ABR level higher than ABR level 2, the bitrate used by proxy 112 to deliver the previous one or more content segments to client device 114 is likely too high, and thus proxy 112 should lower the upper threshold T for the rate at which the content segments are delivered to client device 114. Proxy 112 may reduce the value of upper threshold T, for example, by multiplying upper threshold T by a positive factor less than 1 (e.g., 0.97).

[0085] In the event that client device 114 requests a content segment at an ABR level lower than ABR level 2 and proxy 112 has been delivering the previous one or more content segments to client device 114 at a rate lower than the rate at which proxy 112 has received the previous one or more content segments from unicast server 110, the bitrate used by proxy 112 to deliver the previous one or more content segments to client device 114 is likely too low, and thus proxy 112 should increase the upper threshold T to the rate at which it delivers content segments to client device 114. Proxy 112 may increase the value of upper threshold T, for example, by multiplying upper threshold T by a positive factor greater than 1 (e.g., 1.03).

[0086] Now refer to Figure 5 The flowchart shown describes an example.

[0087] In step 500, the proxy 112 initializes a parameter M indicating an operating mode to "off." This indicates that the proxy 112 has not received guidance from the rate assessment module 108 to attempt to influence the ABR level of the client device 114 requesting the content segment, and therefore the proxy 112 forwards the content segment to the client device 114 as fast as it is received from the unicast server 110.

[0088] In step 502, at ABR level L n , agent 112 at time t n A request for content segment n is received from client device 114. Proxy 112 may not be able to determine L from the parameters of the request. n . Agent 112 stores t n , and if known, store L n .

[0089] In step 504, proxy 112 forwards the request to unicast server 110 and receives the requested segment in response.

[0090] In step 506, the agent 112 stores the size S of the segment n , and determining and storing the rate R at which the content segment is received by the proxy 112 from the unicast server 110 n .

[0091] In step 508, the agent 112 sends the information t n , S n , R n and if known, L n to the rate assessment module 108. The proxy 112 may choose not to do this for each content segment, and may instead send the information for more than one content segment after it has been requested and received.

[0092] In step 510, the proxy 112 receives statistics determined from the information received from the proxy population from the rate assessment module 108. The statistics may include statistics related to the ABR levels, including, for each of a plurality of ABR levels, an average segment size, an indication of a range of segment sizes, and an estimated encoding bit rate.

[0093] If the ABR level L could not be determined previously n , the proxy 112 uses the statistics provided by the rate estimation module 108 and the stored segment size S n To determine the possible ABR level L n , and store the determined L n The value of .

[0094] In step 512, proxy 112 considers additional information received from rate evaluation module 108, which may include statistics indicating the relative frequency with which content segments have been requested at each of the plurality of ABR levels, and may include guidance to proxy 112 as to whether to attempt to influence client device 114 to not request content segments at one or more particular ABR levels.

[0095] If the rate evaluation module 108 has indicated that the proxy 112 should not attempt to influence the ABR level decision to be made by the client device 114 , the proxy 112 sets the operation mode parameter M to “off” and the flow proceeds to step 522 , otherwise the flow proceeds to step 514 .

[0096] In step 514, the proxy 112 sets the operating mode parameter M to "restricted" or "unrestricted." The proxy 112 sets this parameter based on parameters including the ABR level at which the client device 114 has requested one or more previous content segments and the rate at which the one or more previous content segments have been delivered from the unicast server 110.

[0097] The purpose of the proxy 112 is to try to influence the client device 114 to not make occasional requests for ABR level 3 in most requests for ABR level 2, but to make consistent requests for ABR level 2, while allowing the client device 114 to continue to request content segments at ABR level 3 and above consistently if it does so. In the former case, the proxy 112 sets M to "restricted", while in the latter case, the proxy 112 sets M to "unrestricted".

[0098] For example, if one or more previous content fragments have been requested primarily at ABR level 2, but some content fragments have been requested at ABR level 3, and if the rate at which these content fragments have been delivered is generally less than the encoding bitrate of ABR level 3, then the proxy may set M to "constrained". However, if one or more previous content fragments have been requested at ABR level 3 or higher, and if the rate at which these content fragments have been delivered is significantly higher than the encoding bitrate of ABR level 3, then the proxy may set M to "unconstrained".

[0099] The proxy 112 may also apply hysteresis in determining the setting of M to reduce the frequency of switching between M equal to "limited" and M equal to "unrestricted." For example, a threshold for the rate at which one or more previous content segments are received from the unicast server 110 may be higher than a threshold for changing M from "unrestricted" to "limited."

[0100] In step 516, if the guidance from rate assessment module 108 regarding attempting to influence the ABR level decision to be made by client device 114 is the same as the guidance previously received by proxy 112, then flow moves to step 520, otherwise flow moves to step 518. Such changes in guidance include changing from not attempting to influence the ABR level decisions to be made by client device 114 to attempting to influence them; and including changing the specific ABR level of attempting to influence client device 114 to not request the content segment.

[0101] In step 518 , rate assessment module 108 has given new or different guidance to proxy 112 , which involves attempting to influence the ABR level decision to be made by client device 114 .

[0102] Regardless of the value of M that the proxy 112 has set, the proxy 112 sets an upper threshold T on the rate at which it will deliver content segments to the client device 114. The upper threshold T can be set in a variety of ways, including but not limited to the encoding bit rate of ABR level 3 indicated by the rate evaluation module 108, or the rate or average of the rates at which one or more previous content segments are received from the unicast server 108. As described below, the proxy 112 only applies the upper threshold T when M = "limited".

[0103] The process goes to step 522.

[0104] In step 520, if the operation mode M is equal to "restricted", the agent 112 determines whether to adjust the value of the upper threshold T, and if so, adjusts it accordingly. Otherwise, that is, if the operation mode M is not equal to "restricted", the agent 112 does not change the value of the upper threshold T.

[0105] If the operation mode M is equal to "limited" and the ABR level of the content segment is above ABR level 2, the proxy 112 decreases the upper threshold T by, for example, multiplying the upper threshold T by a positive factor less than 1 (eg, 0.97).

[0106] If the operation mode M is equal to "limited" and the ABR level of the content segment is lower than ABR level 2, and the previous segment is received from the unicast server 110 faster than the rate T, that is, if R n-1 >T, the agent 112 increases the upper threshold T by, for example, multiplying it by a positive factor greater than 1 (eg, 1.03).

[0107] In step 522, the proxy 112 delivers the content segment data to the client device 114 as a unicast response to the request from the client device 114. The client device 114 receives the content segment data and may then play the content segment data.

[0108] If the operating mode parameter M is equal to "limited", the proxy 112 controls the rate at which the content segment is delivered to the client device 114 to be as fast as the content segment is received from the unicast server 110. n , but not faster than the upper threshold T. In addition, the proxy 112 receives content segments at a rate R from the unicast server 110 n The content segment data is delivered to the client device 114 as fast as possible. This is shown in the following equation (1):

[0109]

[0110] In step 524 , if the proxy 112 receives another request for a content segment from the client device 114 , the variable n is incremented by 1 and the process goes to step 502 , otherwise the process terminates.

[0111] Note that in these examples, references to ABR level 3 may be generalized to an infrequently requested level, and references to ABR levels 2 or 4 may be generalized to frequently requested levels. Reference has been made to specific level numbers to simplify the description of the examples.

[0112] In general, it should be noted herein that although the above describes examples of the present invention, several changes and modifications may be made to the described examples without departing from the scope of the present invention as defined in the appended claims. Those skilled in the art will recognize modifications to the described examples.

Claims

1. A method for managing content delivery through a proxy in a network, the network comprising a rate assessment module connected to a plurality of proxies, each proxy being connected to a corresponding one or more client devices, the content comprising a series of segments, wherein: Each segment is encoded at multiple bit rates, the method comprising: i) receiving, at a corresponding proxy, a request for a segment from each of the plurality of client devices, and determining an encoding bit rate corresponding to each requested segment; ii) identifying, by the rate estimation module, a subset of encoding bit rates as the most frequently requested bit rates; iii) receiving, at a corresponding proxy, a request for a segment from a target client device, and determining a further encoding bit rate associated with the segment requested by the target client device; iv) selecting an encoding bit rate from a subset of said encoding bit rates based on said further encoding bit rate; v) when the encoding bit rate of the most recently requested segment by the target client device is higher than the selected bit rate, delivering the most recently requested segment from the proxy to the target client device at a delivery rate lower than the rate at which the requested segments are received by the proxy.

2. The method according to claim 1, wherein: One encoding bit rate selected from the subset of encoding bit rates is a further encoding bit rate at which a majority of further requested segments are encoded.