Granted Patent B2

US 12,244,879 · App. 18/109,091 · Granted Mar 4, 2025

Inventor: Alexander Giladi (Princeton, NJ)

Assignee: InterDigital Patent Holdings, Inc.

H04N21/2353H04N9/8205H04N21/23424H04N21/4335H04N21/44004H04N21/812

Abstract

Claims (27)

1. A computing device, comprising:

a processor configured to:

identify a timing parameter synchronized to a media timeline;

receive a Moving Picture Experts Group-Dynamic Adaptive Streaming over HTTP (MPEG-DASH) event scheme comprising a payload, the payload indicating a uniform resource locator (URL) template for enabling the computing device to respond to an MPEG-DASH callback event using at least one client-side URL parameter;

compute the at least one client-side URL parameter;

generate, at a first time based on the timing parameter synchronized to the media timeline, a URL based on the URL template that is received in the payload of the MPEG-DASH event scheme and the at least one computed client-side URL parameter;

send, at a second time based on the timing parameter synchronized to the media timeline, a Hypertext Transfer Protocol (HTTP) GET Request using the generated URL to respond to the MPEG-DASH callback event;

receive an HTTP Response in response to the HTTP GET Request; and

disregard the HTTP Response received in response to the HTTP GET Request.

2. The computing device of claim 1 , wherein the at least one computed client-side URL parameter further comprises at least one of device information or connection information.

3. The computing device of claim 1 , wherein the processor is further configured to:

send at least one of an HTTP PUT Request and an HTTP POST Request via the URL.

4. A method of scheduling an MPEG-DASH event, comprising:

identifying a timing parameter synchronized to a media timeline;

receiving an MPEG-DASH event scheme comprising a payload, the payload indicating a uniform resource locator (URL) template for enabling a computing device to respond to an MPEG-DASH callback event using at least one client-side URL parameter;

compute the at least one client-side URL parameter;

generating, at a first time based on the timing parameter synchronized to the media timeline, a URL based on the URL template that is received in the payload of the MPEG-DASH event scheme and the at least one computed client-side URL parameter;

sending, at a second time based on the timing parameter synchronized to the media timeline, an HTTP GET Request using the generated URL to respond to the MPEG-DASH callback event;

receiving an HTTP Response in response to the HTTP GET Request; and

disregarding the HTTP Response received in response to the HTTP GET Request.

5. The method of claim 4 , wherein the at least one computed client-side URL parameter further comprises at least one of device information or connection information.

6. The method of claim 4 , further comprising:

sending at least one of an HTTP PUT Request and an HTTP POST Request via the URL.

7. The computing device of claim 1 , wherein the at least one client-side URL parameter further comprises at least one of a social network identification or viewer information of the computing device, and wherein the viewer information of the computing device comprises at least one of a number of viewers, whether the computing device is in a user's hands or at rest, or an emotional response.

8. The method of claim 4 , wherein the at least one client-side URL parameter further comprises at least one of a social network identification or viewer information of the computing device, and wherein the viewer information of the computing device comprises at least one of a number of viewers, whether the computing device is in a user's hands or at rest, or an emotional response.

9. The computing device of claim 1 , wherein the at least one client-side URL parameter comprises at least a GPS coordinate.

10. The method of claim 4 , wherein the at least one client-side URL parameter comprises at least a GPS coordinate.

Continuity (5)

References Cited (80)