US 11,930,254 B2
Patchable remote element for data manipulation
Iraj Sodagar, Los Angeles, CA (US)
Assigned to TENCENT AMERICA LLC, Palo Alto, CA (US)
Filed by TENCENT AMERICA LLC, Palo Alto, CA (US)
Filed on Apr. 1, 2021, as Appl. No. 17/220,590.
Claims priority of provisional application 63/042,282, filed on Jun. 22, 2020.
Claims priority of provisional application 63/010,285, filed on Apr. 15, 2020.
Claims priority of provisional application 63/009,150, filed on Apr. 13, 2020.
Claims priority of provisional application 63/006,666, filed on Apr. 7, 2020.
Prior Publication US 2021/0314674 A1, Oct. 7, 2021
Int. Cl. H04N 7/173 (2011.01); H04L 65/65 (2022.01); H04L 65/70 (2022.01); H04L 65/75 (2022.01); H04N 21/8543 (2011.01)
CPC H04N 21/8543 (2013.01) [H04L 65/65 (2022.05); H04L 65/70 (2022.05); H04L 65/75 (2022.05)] 20 Claims
OG exemplary drawing
 
1. A method for streaming media content, the method performed by at least one processor and comprising:
obtaining media content from a first content server based on determining to stream the media content from the first content server to a client device;
determining whether a manifest, included with the media content from the first server, indicates presence of a remote element;
resolving, in response to determining that the manifest indicates presence of the remote element, the remote element by updating a default remote element, included with the manifest, to an updated remote element signaling both to stream, to the client device, another media content from a second content server and to check, by the client device, for an event stream update indicating to resume a stream to the client device and from the first server while the other media content is streamed, to the client device, from the second content server, wherein resolving the remote element comprises resolving, in parallel, both an Xlink URL and an @patchURL, wherein the Xlink URL is a different URL than that of the @patchURL, and wherein resolving the Xlink URL comprises determining an updated time period as compared to a time period indicated in the manifest, and wherein resolving the @patchURL comprises determining to add the remote EventStream element to the updated remote element while the client device maintains a connection to the first content server;
manipulating, while the other media content is streamed, to the client device and from the second content server, the updated remote element after the default remote element is resolved, to the resolved remote element, based on a signaling by a document, of the event stream update, stored in a remote location; and
streaming, to the client device, at least one of the media content from the first content server and the other media content from the second content server based on manipulating the updated remote element,
wherein said signaling signals retrieving of a plurality of instructions, after the remote element is resolved, and applying the retrieved instructions to the resolved remote element.