Network-initiated content streaming control
Methods and systems are described for enabling network-initiated control of streaming of segmented content from a content delivery node to at least one client, the client being configured to access at least part of the segmented content on the basis of a manifest file. A first manifest file is received identifying one or more segments and location information for locating one or more content delivery nodes configured to transmit one or more segments to at least one client. In response to reception of the first manifest file, channel set-up information is provided. At least one streaming control channel is established between at least one client and a control channel server function associated with the content delivery node on the basis of the control channel set-up information. The at least one client is configured for receiving at least one manifest file update message via the streaming control channel.
1. A content processing device comprising a client for controlling reception of segmented content transmitted from at least one delivery node, said first delivery node being associated with a first control channel server function, said client being configured for:
transmitting to said at least one delivery node a request for delivering segmented content, said delivering being based on a streaming protocol;
receiving a manifest file comprising one or more segment identifiers and location information for locating one or more content delivery nodes configured to transmit one or more segments associated with said segment identifiers to said at least one client;
being provided with channel set-up information; and,
establishing a streaming control channel between said at least one client and said first control channel server function on the basis of said first channel set-up information, said at least one client being configured for receiving at least one manifest file update message from said first control channel server function.
2. A content processing device according to claim 1 , wherein said streaming control channel is being established on the basis of at least one protocol selected from the group of a WebSocket protocol, a SIP protocol, and an XMPP protocol.
3. A content processing device according to claim 2 , wherein said client is an HTTP Adaptive Streaming client, and said streaming protocol is an HTTP Adaptive Streaming type of protocol.
4. A content processing device according to claim 3 , wherein said HTTP Adaptive Streaming client is an MPEG DASH compatible client.
5. A content processing device according to claim 2 wherein said streaming protocol is an HTTP-based streaming protocol or a derivative thereof.
6. A content processing device according to claim 1 , said client being configured for monitoring said streaming control channel for at least one manifest file update message.
7. A content processing device according to claim 6 wherein said streaming protocol is an HTTP-based streaming protocol or a derivative thereof.
8. A content processing device according to claim 1 , said client being configured for detecting a manifest file update message;
retrieving at least part of a second manifest file in response to the detection of said manifest file update message.
9. A content processing device according to claim 1 , said client being configured for receiving at least part of said channel set-up information in said first manifest file.
10. A content processing device according to claim 9 , wherein said client is an HTTP Adaptive Streaming client, and said streaming protocol is an HTTP Adaptive Streaming type of protocol.
11. A content processing device according to claim 10 , wherein said HTTP Adaptive Streaming client is an MPEG DASH compatible client.
12. A content processing device according to claim 11 , wherein said streaming control channel is being established on the basis of a Web Socket protocol.
13. A content processing device according to claim 12 , wherein the at least part of said channel set-up information comprises at least one of a channel target parameter providing a reference to a network node comprising a streaming control function or a channel parameter referring to a Websocket version.
14. A content processing device according to claim 13 , said client being configured for monitoring said streaming control channel for at least one manifest file update message.
15. A content processing device according to claim 10 , wherein said streaming control channel is being established on the basis of a Web Socket protocol.
16. A content processing device according to claim 15 , wherein the at least part of said channel set-up information comprises at least one of a channel target parameter providing a reference to a network node comprising a streaming control function or a channel parameter referring to a Websocket version.
17. A content processing device according to claim 16 , said client being configured for monitoring said streaming control channel for at least one manifest file update message.
18. A content processing device according to claim 10 wherein said channel set-up information comprises server location information for locating said control channel server function in the network.
19. A content processing device according to claim 1 , wherein said manifest file update message comprises at least part of a second manifest file or wherein said manifest file update message comprises manifest file location information for locating and requesting at least part of said second manifest file.
20. A content processing device according to claim 19 wherein said streaming protocol is an HTTP-based streaming protocol or a derivative thereof.
21. A content processing device according to claim 1 , said client being configured for receiving at least part of said channel set-up information in said first manifest file, wherein said streaming control channel is being established on the basis of at least one protocol selected from the group of a WebSocket protocol, a SIP protocol, and an XMPP protocol.
22. A content processing device according to claim 21 , wherein said client is an HTTP Adaptive Streaming client, and said streaming protocol is an HTTP Adaptive Streaming type of protocol.
23. A content processing device according to claim 22 , wherein said HTTP Adaptive Streaming client is an MPEG DASH compatible client.
24. A content processing device according to claim 22 wherein said channel set-up information comprises server location information for locating said control channel server function in the network.
25. A content processing device according to claim 1 , said client being configured for detecting a manifest file update message, wherein said manifest file update message comprises manifest file location information for locating and requesting at least part of said second manifest file; retrieving at least part of a second manifest file in response to the detection of said manifest file update message.
26. A content processing device according to claim 1 , wherein said streaming control channel is being established on the basis of at least one protocol selected from the group of a WebSocket protocol, a SIP protocol, and an XMPP protocol, said client being configured for monitoring said streaming control channel for at least one manifest file update message; detecting said manifest file update message, wherein said manifest file update message comprises manifest file ocation information for locating and requesting at least part of said second manifest file; retrieving at least part of a second manifest file in response to the detection of said manifest file update message.
27. A content processing device according to claim 26 , wherein said client is an HTTP Adaptive Streaming client, and said streaming protocol is an HTTP Adaptive Streaming type of protocol.
28. A content processing device according to claim 27 , wherein said HTTP Adaptive Streaming client is an MPEG DASH compatible client.
29. A content processing device according to claim 1 , wherein said client is an HTTP Adaptive Streaming client, and said streaming protocol is an HTTP Adaptive Streaming type of protocol.
30. A content processing device according to claim 29 , wherein said HTTP Adaptive Streaming client is an MPEG DASH compatible client.