360-degree video delivery over next generation network
Systems, methods, and instrumentalities are disclosed for a 360-degree video streaming. A video streaming device may receive a 360-degree video stream from a network node. The video streaming device may determine a viewport associated with the video streaming device and/or the 360-degree video stream. The video streaming device may determine (e.g., based on the viewport) to request in advance a first segment and a second segment of the 360-degree video stream. The video streaming device may determine a relative priority order for the first segment and the second segment. The video streaming device may generate an anticipated requests message. The anticipated requests message may indicate the determined relative priority order, for example, by listing the first segment and the second segment in decreasing relative priority based on the determined relative priority order. The video streaming device may send the anticipated requests message to the network node.
1. A dynamic adaptive streaming over HTTP (DASH) aware network element (DANE) comprising:
a processor configured to:
receive, from a DASH client, a request associated with a DASH segment and an accepted alternatives message, wherein the accepted alternatives message comprises parameters associated with one or more acceptable alternative DASH segments the DASH client is willing to accept;
generate a delivered alternative message, wherein the delivered alternative message comprises an indication of an alternative DASH segment associated with the one of the one or more acceptable alternative DASH segments; and
send to the DASH client, in response to the accepted alternatives message, the delivered alternative message.
2. The DANE of claim 1 , wherein the processor is further configured to receive, from the DASH client, an anticipated requests message that includes an anticipated request for the DASH segment, wherein the anticipated request for the DASH segment is listed in the anticipated requests message based on a decreasing relative priority order, wherein the anticipated request for the DASH segment comprises a source uniform resource locator (URL) of a representation, a range, and a target time, and wherein the anticipated request is arranged with at least one other anticipated request in a decreasing relative priority order.
3. The DANE of claim 1 , wherein the parameters associated with the one or more acceptable alternative DASH segments comprise an alternative source uniform resource locator (URL), and an alternative range, wherein the alternative source URL indicates a URL of one of the one or more acceptable alternative DASH segments, and the alternative range indicates a byte range associated with one of the one or more acceptable alternative DASH segments.
4. The DANE of claim 1 , wherein the processor is further configured to receive an absolute deadline message comprising an absolute deadline associated with the DASH segment to be available in the DASH client, wherein the absolute deadline is date and time by when the requested DASH segment is to be completely received by the DASH client.
5. The DANE of claim 4 , wherein the processor is further configured to sort DASH segments including the DASH segment based on the absolute deadline.
6. The DANE of claim 1 , wherein the indication of the alternative DASH segment comprises a URL of the actual delivered content.
7. The DANE of claim 1 , wherein the processor is further configured to send the alternative DASH segment to the DASH client.
8. A method implemented by a dynamic adaptive streaming over HTTP (DASH) aware network element (DANE), the method comprising:
receiving, from a DASH client, a request associated with a DASH segment and an accepted alternatives message, wherein the accepted alternatives message comprises parameters associated with one or more acceptable alternative DASH segments the DASH client is willing to accept;
generating a delivered alternative message, wherein the delivered alternative message comprises an indication of an alternative DASH segment associated with the one of the one or more acceptable alternative DASH segments; and
sending to the DASH client, in response to the accepted alternatives message, the delivered alternative message.
9. The method of claim 8 , further comprising receiving, from the DASH client, an anticipated requests message that includes an anticipated request for the DASH segment, wherein the anticipated request for the DASH segment is listed in the anticipated requests message based on a decreasing relative priority order, wherein the anticipated request for the DASH segment comprises a source uniform resource locator (URL) of a representation, a range, and a target time, and wherein the anticipated request is arranged with at least one other anticipated request in a decreasing relative priority order.
10. The method of claim 8 , wherein the parameters associated with the one or more acceptable alternative DASH segments comprise an alternative source uniform resource locator (URL), and an alternative range, wherein the alternative source URL indicates a URL of one of the one or more acceptable alternative DASH segments, and the alternative range indicates a byte range associated with one of the one or more acceptable alternative DASH segments.
11. The method of claim 8 , further comprising receiving an absolute deadline message comprising an absolute deadline associated with the DASH segment to be available in the DASH client, wherein the absolute deadline is date and time by when the requested DASH segment is to be completely received by the DASH client.
12. The method of claim 11 , further comprising sorting DASH segments including the DASH segment based on the absolute deadline.
13. The method of claim 8 , wherein the indication of the alternative DASH segment comprises a URL of the actual delivered content.
14. The method of claim 8 , further comprising sending the alternative DASH segment to the DASH client.
15. A dynamic adaptive streaming over HTTP (DASH) client comprising:
a processor configured to at least:
generate an accepted alternatives message, wherein the accepted alternatives message comprises parameters associated with one or more acceptable alternative DASH segments the DASH client is willing to accept;
send, to a DASH aware network element (DANE), a request associated with a DASH segment and the accepted alternatives message indicating the one or more acceptable alternative DASH segments; and
receive from the DANE, in response to the accepted alternatives message, a delivered alternative message, wherein the delivered alternative message comprises an indication of an alternative DASH segment associated with the one of the one or more acceptable alternative DASH segments.
16. The DASH client of claim 15 , wherein the processor is further configured to send, to the DANE, an anticipated requests message that includes an anticipated request for the DASH segment, wherein the anticipated request for the DASH segment is listed in the anticipated requests message based on a decreasing relative priority order.
17. The DASH client of claim 16 , wherein the anticipated request for the DASH segment comprises a source uniform resource locator (URL) of a representation, a range, and a target time, and wherein the anticipated request is arranged with at least one other anticipated request in a decreasing relative priority order.
18. The DASH client of claim 15 , wherein the parameters associated with the one or more acceptable alternative DASH segments comprise an alternative source uniform resource locator (URL), and an alternative range.
19. The DASH client of claim 18 , wherein the alternative source URL indicates a URL of one of the one or more acceptable alternative DASH segments, and the alternative range indicates a byte range associated with one of the one or more acceptable alternative DASH segments.
20. The DASH client of claim 15 , wherein the processor is further configured to send an absolute deadline message comprising an absolute deadline associated with the DASH segment to be available in the DASH client, and wherein the absolute deadline is date and time by when the requested DASH segment is to be completely received by the DASH client.