Systems and methods for generalized HTTP headers in dynamic adaptive streaming over HTTP (DASH)
Systems and methods for streaming content are disclosed. A Media Presentation Description (MPD) may be associated with streaming content, for example, in Dynamic Adaptive Streaming Over HTTP (DASH). An MPD may comprise an element, e.g., a header element or URL query element, which provides a name/Value functionality. An element may allow a request that results in insertion of custom headers. Requests may be used for retrieval of a subsegment, segment, or MPD, re-referencing of remote elements, or triggered by an event. The event may be embedded either in an MPD or in segments.
1. A method for obtaining streaming content, the method comprising:
a device receiving a Media Presentation Description (MPD) file for dynamic adaptive streaming over hypertext transfer protocol (DASH), the MPD file indicating a request type to be used by the device for a hypertext transfer protocol (HTTP) request;
the device generating a name parameter and value parameter pair feedback in an HTTP header form;
the device generating an HTTP request using the request type indicated in the MPD file;
the device sending the HTTP request, wherein the HTTP request comprises an HTTP header including the name parameter and value parameter feedback; and
the device receiving a response for the HTTP header in response to the HTTP request, the response comprising a value corresponding to the name parameter and value parameter pair feedback.
2. The method of claim 1 , wherein the MPD file specifies a name parameter.
3. The method of claim 1 , wherein the MPD file specifies a value parameter.
4. The method of claim 1 , wherein the request type is an XLink GET request.
5. The method of claim 1 , wherein the request type is an MPD GET request.
6. The method of claim 1 , wherein the request type is a DASH event GET request.
7. The method of claim 1 , wherein the MPD indicates the request type among a plurality of request types, and the plurality of request type comprises two or more of a DASH event GET request, an MPD GET request, or an XLink GET request.
8. The method of claim 1 , wherein the method comprises:
the device generating the name parameter and value parameter pair feedback in a uniform resource locator (URL) query form.
9. The method of claim 8 , wherein the method comprises:
the device translating the name parameter and value parameter pair feedback from the URL query form into the HTTP header form.
10. A device comprising:
a processor configured to:
receive a Media Presentation Description (MPD) file for dynamic adaptive streaming over hypertext transfer protocol (DASH), the MPD file indicating a request type to be used by the device for a hyper transfer protocol (HTTP) request;
generate a name parameter and value parameter pair feedback in an HTTP header form;
generate an HTTP request using the request type indicated in the MPD file;
send the HTTP request, wherein the HTTP request comprises an HTTP header including the name parameter and value parameter pair feedback; and
receive a response for the HTTP header in response to receiving the HTTP request, the response comprising a value corresponding to the name parameter and value parameter pair feedback.
11. The device of claim 10 , wherein the MPD file specifies a name parameter.
12. The device of claim 10 , wherein the MPD file specifies a value parameter.
13. The device of claim 10 , wherein the request type is an XLink GET request.
14. The device of claim 10 , wherein the request type is an MPD GET request.
15. The device of claim 10 , wherein the request type is a DASH event GET request.
16. The device of claim 10 , wherein the MPD indicates the request type among a plurality of request types, and the plurality of request type comprises two or more of a DASH event GET request, an MPD GET request, or an XLink GET request.
17. The device of claim 10 , wherein the processor is configured to:
generate the name parameter and value parameter pair feedback in a uniform resource locator (URL) query form.
18. The device of claim 17 , wherein the processor is configured to:
translate the name parameter and value parameter pair feedback from the URL query form into the HTTP header form.