Multicast streaming

• US 10,659,502 B2
• Filed: 03/24/2015
• Issued: 05/19/2020
• Est. Priority Date: 03/31/2014
• Status: Active Grant

• Current Assignee: British Telecommunications PLC (BT Group PLC)
• Original Assignee: British Telecommunications PLC (BT Group PLC)
• Inventors: Crabtree, Ian, Nilsson, Michael, Turnbull, Rory, Appleby, Stephen
• Primary Examiner(s): Joo, Joshua
• Application Number:
  US15/129,486
• Publication Number:
  US 20170118263A1
• Time in Patent Office: 1,883 Days
• Field of Search: None
• CPC Class Codes: H04L 65/611 for multicast or broadcast systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06
• CPC Class Codes: H04L 65/70 Media network packetisation
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04N 21/23439 for generating different versions
• CPC Class Codes: H04N 21/4383 Accessing a communication channel
• CPC Class Codes: H04N 21/6405 Multicasting data broadcast and multicast in packet switching networks H04L12/18
• CPC Class Codes: H04N 21/6408 Unicasting
• CPC Class Codes: H04N 21/8456 by decomposing the content in the time domain, e.g. in time segments
• CPC Class Codes: H04W 76/40 for selective distribution or broadcast

Abstract

The invention presents a method of providing feedback for receipt of a multicast video stream. The feedback mechanism allows the number of clients receiving over multicast to be determined, which can then be used to manage multicast delivery, including switching decisions between multicast and unicast. Video content is delivered over a multicast stream from a content server to a plurality of client devices. The client devices are each configured to respond at regular intervals whilst receiving the multicast video stream by transmitting an HTTP HEAD request message to the content server. The HTTP HEAD request refers to metadata relating to a manifest file associated with the video stream. The number of client devices receiving the multicast video stream is determined based on the number of HEAD requests received at the content server. The multicast video delivery can then be managed accordingly, and can also take into account the number of unicast clients that are requesting the corresponding unicast stream to the multicast stream.

Claims

1. A method of managing multicast video delivery comprising:

receiving a multicast video stream at a plurality of client devices from a content server;

transmitting regularly from each of the client devices, while a multicast video stream is being received, a first message to the content server in response to receiving the multicast video stream;

determining, at the content server, the number of client devices receiving the multicast video stream based on the regularly transmitted first messages; and

managing the multicast video delivery in dependence on the number of client devices determined,

wherein each of the first messages from the client devices to the content server is an HTTP HEAD request message; and

wherein the method further comprises;

receiving a unicast video stream at another plurality of client devices from the content server;

transmitting regularly from each of the client devices receiving a unicast video stream, while the unicast video stream is being received, a second message to the content server in response to receiving the unicast the video stream, the second message being an HTTP GET request and being different from the first message;

determining the number of client devices receiving the unicast video stream based on the transmitted second messages;

comparing the determined number of client devices receiving the unicast video stream and the determined number of client devices receiving the multicast video stream; and

managing the multicast video delivery based on the comparison of the determined number of client devices receiving the unicast video stream and the determined number of client devices receiving the multicast video stream.

2. A method according to claim 1, wherein the HTTP HEAD request is for updates to a manifest file associated with the video stream.

3. A content server comprising:

a processing system operatively coupled to a communications interface and a data store for storing video content so that the content server is configured to at least;

transmit a multicast video stream to a plurality of client devices;

receive a first message transmitted regularly from each of the client devices while a multicast video stream is being received by the client devices in response to receipt of the multicast video stream by the client devices;

determine the number of client devices receiving the multicast video stream based on the received first messages which are transmitted regularly from each of the client devices;

manage the multicast video delivery in dependence on the number of client devices determined;

wherein each of the first messages from the client devices to the content server is an HTTP HEAD request message; and

wherein the content server is further configured to;

transmit a unicast video stream to a second plurality of devices;

receive a second message transmitted regularly from each of the client devices receiving the unicast video stream while the unicast video stream is being received by each of the second plurality of client devices, the second message being an HTTP GET request and being different from the first message;

determine the number of client devices receiving the unicast video stream based on the transmitted second messages;

compare the determined number of client devices receiving the unicast video stream and the determined number of client devices receiving the multicast video stream; and

manage the multicast video delivery based on the comparison of the determined number of client devices receiving the unicast video stream and the determined number of client devices receiving the multicast video stream.

4. The content server according to claim 3, wherein the HTTP HEAD request is for updates to a manifest file associated with the video stream.

5. A method of managing multicast video delivery comprising:

receiving a multicast video stream at a plurality of client devices from a content server;

transmitting regularly from each of the client devices, while a multicast video stream is being received, a first message to the content server in response to receiving the multicast video stream;

determining, at the content server, the number of client devices receiving the multicast video stream based on the regularly transmitted first messages;

receiving a unicast video stream at another plurality of client devices from the content server;

transmitting regularly from each of the client devices receiving a unicast video stream, while the unicast video stream is being received, a second message to the content server in response to receiving the unicast the video stream, the second message being an HTTP GET request and being different from the first message;

determining the number of client devices receiving the unicast video stream based on the transmitted second messages;

comparing the determined number of client devices receiving the unicast video stream and the determined number of client devices receiving the multicast video stream; and

managing the multicast video delivery based on the comparison of the determined number of client devices receiving the unicast video stream and the determined number of client devices receiving the multicast video stream.

6. A method according to claim 5, wherein the managing comprises determining whether to continue transmission of the video stream by multicast.

7. A content server comprising:

a processing system operatively coupled to a communications interface and a data store for storing video content so that the content server is configured to at least;

transmit a multicast video stream to a plurality of client devices;

receive a first message transmitted regularly from each of the client devices while a multicast video stream is being received by the client devices in response to receipt of the multicast video stream by the client devices;

determine the number of client devices receiving the multicast video stream based on the received first messages which are transmitted regularly from each of the client devices;

transmit a unicast video stream to a second plurality of devices;

receive a second message transmitted regularly from each of the client devices receiving the unicast video stream while the unicast video stream is being received by each of the second plurality of client devices, the second message being an HTTP GET request and being different from the first message;

determine the number of client devices receiving the unicast video stream based on the transmitted second messages;

compare the determined number of client devices receiving the unicast video stream and the determined number of client devices receiving the multicast video stream; and

manage the multicast video delivery based on the comparison of the determined number of client devices receiving the unicast video stream and the determined number of client devices receiving the multicast video stream.

8. The content server according to claim 7, wherein the content server is further configured to determine whether to continue transmission of the video stream by multicast in order to manage the multicast video delivery based on the comparison of the determined number of client devices receiving the unicast video stream and the determined number of client devices receiving the multicast video stream.

9. A method of managing multicast video delivery comprising:

receiving a multicast video stream at a plurality of client devices from a content server;

transmitting regularly from each of the client devices, while a multicast video stream is being received, a first message to the content server in response to receiving the multicast video stream;

determining, at the content server, the number of client devices receiving the multicast video stream based on the regularly transmitted first messages; and

managing the multicast video delivery in dependence on the number of client devices determined,

wherein each of the first messages from the client devices to the content server is an HTTP HEAD request message; and

wherein the method further comprises determining a number of client devices requesting a unicast video stream; and

wherein the multicast video delivery is managed in dependence on the determined number of client devices receiving the multicast video stream and the determined number of client devices requesting the unicast video stream.

10. A method according to claim 9, wherein the requests for the unicast video stream from the client devices are HTTP GET requests.

11. A method according to claim 9, wherein

managing the multicast video delivery includes switching between unicast and multicast delivery methods in dependence on the determined number of client devices receiving the multicast video stream and the determined number of client devices requesting a unicast video stream.

12. A content server comprising:

a processing system operatively coupled to a communications interface and a data store for storing video content so that the content server is configured to at least;

transmit a multicast video stream to a plurality of client devices;

receive a first message transmitted regularly from each of the client devices while a multicast video stream is being received by the client devices in response to receipt of the multicast video stream by the client devices;

determine the number of client devices receiving the multicast video stream based on the received first messages which are transmitted regularly from each of the client devices;

manage the multicast video delivery in dependence on the number of client devices determined;

wherein each of the first messages from the client devices to the content server is an HTTP HEAD request message;

wherein;

the content server is further configured to determine a number of client devices requesting a unicast video stream; and

wherein the multicast video delivery is managed in dependence on the determined number of client devices receiving the multicast video stream and the determined number of client devices requesting the unicast video stream.

13. The content server according to claim 12 wherein the requests for the unicast video stream from the client devices are HTTP GET requests.

14. The content server according to claim 12, wherein

managing the multicast video delivery by the content server includes switching between unicast and multicast delivery methods in dependence on the determined number of client devices receiving the multicast video stream and the determined number of client devices requesting the unicast video stream.