Metrics and messages to improve experience for 360-degree adaptive streaming
A method for receiving and displaying media content may be provided. The method may include requesting a set of DASH video segments that are associated with various viewports and qualities. The method may include displaying the DASH video segments. The method may include determining a latency metric based on a time difference between the display of a DASH video segment and one of: a device beginning to move, the device ceasing to move, the device determining that the device has begun to move, the device determining that the device has stopped moving, or the display of a different DASH video segment. The different DASH video segment may be associated with one or more of a different quality or a different viewport.
1 . A device for receiving and displaying media content, the device comprises:
a first interface coupled to a sensor component, wherein the first interface is configured to receive, from the sensor component, first metrics data associated with a user's orientation;
a second interface coupled to a rendering component, wherein the second interface is configured to receive, from the rendering component, second metrics data associated with rendering dynamic adaptive streaming over HTTP (DASH) video segments; and
a processor configured to
receive the first metrics data associated with the user's orientation via the first interface coupled to the sensor component,
receive the second metrics data associated with rendering the DASH video segments via the second interface coupled to the rendering component, wherein the second metrics data is generated using one or more of color conversion, projection, or media composition,
generate a latency metric based on the first metrics data associated with the user's orientation and the second metrics data associated with rendering the DASH video segments, and
send the latency metric to a metrics server.
2 . The device of claim 1 , wherein the processor comprises a metrics processing component, the metrics processing component is coupled to the first interface and the second interface, and the latency metric is generated by the metrics processing component.
3 . The device of claim 1 , wherein the latency metric is generated further based on one of third metrics data associated with requesting and receiving the DASH video segments from a network, fourth metrics data associated with decoding the DASH video segments received from the network, or fifth metrics data associated with configuration parameters corresponding to the device.
4 . The device of claim 1 , wherein the latency metric is selected from the group consisting of a viewport switching latency, a quality viewport switching latency, an initial latency, and a settling latency.
5 . The device of claim 1 , wherein a network access component is coupled to at least one of the first interface or the second interface over a communication network.
6 . The device of claim 1 , wherein the device comprises a virtual reality client device.
7 . The device of claim 1 , wherein the latency metric comprises a comparable quality viewport switching latency.
8 . The device of claim 1 , wherein the device further comprises at least one of:
a third interface coupled to a network access component, the third interface configured to receive, from the network access component, third metrics data associated with requesting and receiving the DASH video segments from a network;
a fourth interface coupled to a media processing component, the fourth interface configured to receive, from the media processing component, fourth metrics data associated with decoding the DASH video segments received from the network; and
a fifth interface coupled to a control component, the fifth interface configured to receive, from the control component, fifth metrics data associated with configuration parameters corresponding to the device, wherein the latency metric is generated further based on at least one of the third metrics data associated with requesting and receiving the DASH video segments from the network, the fourth metrics data associated with decoding the DASH video segments received from the network, and the fifth metrics data associated with the configuration parameters corresponding to the device.
9 . The device of claim 1 , wherein the device comprises a third interface, a fourth interface, and a fifth interface, the processor comprises a metrics processing component, the metrics processing component is coupled to the first interface, the second interface, the third interface, the fourth interface, and the fifth interface, and the latency metric is generated by the metrics processing component.
10 . A method for receiving and displaying media content, the method comprises:
receiving first metrics data associated with a user's orientation via a first interface coupled to a sensor component, wherein the first interface is configured to receive, from the sensor component, the first metrics data associated with the user's orientation;
receiving second metrics data associated with rendering dynamic adaptive streaming over HTTP (DASH) video segments via a second interface coupled to a rendering component, wherein the second interface is configured to receive, from the rendering component, the second metrics data associated with rendering the DASH video segments, wherein the second metrics data is generated using one or more of color conversion, projection, or media composition;
generating a latency metric based on the first metrics data associated with the user's orientation and the second metrics data associated with rendering the DASH video segments; and
sending the latency metric to a metrics server.
11 . The method of claim 10 , wherein a metrics processing component is coupled to the first interface and the second interface, and the latency metric is generated by the metrics processing component.
12 . The method of claim 10 , wherein the latency metric is generated further based on one of third metrics data associated with requesting and receiving the DASH video segments from a network, fourth metrics data associated with decoding the DASH video segments received from the network, or fifth metrics data associated with configuration parameters corresponding to a device.
13 . The method of claim 10 , wherein the latency metric is selected from the group consisting of a viewport switching latency, a quality viewport switching latency, an initial latency, and a settling latency.
14 . The method of claim 10 , wherein a network access component is coupled to at least one of the first interface or the second interface over a communication network.
15 . The method of claim 10 , wherein the latency metric comprises a comparable quality viewport switching latency.
16 . The method of claim 10 , wherein the method further comprises:
receiving third metrics data associated with requesting and receiving the DASH video segments from a network via a third interface coupled to a network access component, wherein the third interface is configured to receive the third metrics data from the network access component;
receiving fourth metrics data associated with decoding the DASH video segments received from the network via a fourth interface coupled to a media processing component, wherein the fourth interface is configured to receive, from the media processing component, the fourth metrics data associated with decoding the DASH video segments received from the network; and
receiving fifth metrics data associated with configuration parameters corresponding to a device via a fifth interface coupled to a control component, wherein the fifth interface is configured to receive, from the control component, the fifth metrics data associated with the configuration parameters corresponding to the device, wherein the latency metric is generated further based on at least one of the third metrics data associated with requesting and receiving the DASH video segments from the network, the fourth metrics data associated with decoding the DASH video segments received from the network, and the fifth metrics data associated with the configuration parameters corresponding to the device.