Network media device
US-9448683-B2 · Sep 20, 2016 · US
US9729630B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9729630-B2 |
| Application number | US-201414167742-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 29, 2014 |
| Priority date | Jun 4, 2004 |
| Publication date | Aug 8, 2017 |
| Grant date | Aug 8, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A network media delivery system includes client devices and a host device. Each client device has a network interface, an engine for processing media data, and a media interface. The host device, which can be a computer, establishes network communication links with the client devices, which can be networked media stations, and sends media data to the client devices. The media data can be sent wirelessly as packets of media data transmitted at intervals to each client device. In one embodiment, the host device controls processing of media data such that processed media is delivered in a synchronized manner at each of the client devices. In another embodiment, the host device controls processing of media data such that processed media is delivered in a synchronized manner at the host device and at least one client device.
Opening claim text (preview).
What is claimed is: 1. A host device, comprising: a network interface for communicating with a first client device; a reference clock; and a processing component operatively coupled to the network interface and the reference clock, wherein the processing component is configured to: send, by the host device to the first client device, a request for sending information about latency within the first client device; send, by the host device to the first client device, one or more media packets based on a packet timeline determined for the first client device; and send, by the host device to the first client device, a first presentation timeline indicative of when to play back, at the first client device, media data included in the one or more media packets, wherein the first presentation timeline is determined by the host device based at least in part on the latency associated with the client device. 2. The host device of claim 1 , wherein to send the media data and the first presentation time line to the first client device, the processing component sends a unicast stream of first packets containing the media data to the first client device, each of the first packets having a timestamp specifying when to present the media data associated with the first packet. 3. The host device of claim 2 , wherein the first packets comprise Real-Time Transport Protocol encapsulated in User Datagram Protocol packets. 4. The host device of claim 2 , wherein the timestamps in the first packets comprise an adjustment based on a presentation latency associated with the first client device. 5. The host device of claim 1 , wherein to synchronize the first local clock of the first client device with the reference clock, the processing component sends second packets to the first client device via the network interface in response to requests from the first client device, the second packets having time information to correlate the first local clock with the reference clock. 6. The host device of claim 5 , wherein the second packets comprise Network Time Protocol (NTP) encapsulated in Real-Time Transport Control Protocol (RTCP) packets. 7. The host device of claim 1 , wherein the processing component synchronizes a second local clock of a second client device with the reference clock and generates a second presentation time line for the media data based on the reference clock, the second presentation time line specifying when to present the media data at the second client device such that the media data is presented in a synchronized manner at both the first and second client devices, the processing component sending the media data and the second presentation time line to the second client device via the network interface and controlling presentation of the sent media data at the second client device with the second presentation time line. 8. The host device of claim 1 , wherein separately sending the media data and the first presentation time line to the first client device comprises: sending the first presentation time line to the client device as part of a time announcement that is sent periodically from the host device to the client device, the periodic time announcement used to maintain a timing relationship between the host device and the client device. 9. A host device, comprising: a network interface for communicating with a plurality of client devices; and a processing component operatively coupled to the network interface, the processing component is configured to: send, by the host device to each of the client devices, a request for sending information about latency within each of the client devices; send, by the host device to each of the client devices, one or more media packets based on a packet timeline determined for each of the client devices; and send, by the host device to each of the client devices, a presentation timeline indicative of when to play back, at each of the client devices, media data included in the one or more media packets, wherein the presentation timeline is determined by the host device based at least in part on the latency associated with each of the client devices. 10. The host device of claim 9 , wherein to send the media data to each of the client devices via the network interface, the processing components sends a separate unicast stream of first packets containing the media data to each of the client devices, each of the first packets having a timestamp specifying when to present the media data associated with the first packet. 11. The host device of claim 10 , wherein the timestamps in the first packets for a given one of the client devices comprise an adjustment based on a presentation latency associated with the given client device. 12. The host device of claim 9 , wherein the host device comprises a reference clock, and wherein the processing component synchronizes each local clock of the client devices with the reference clock. 13. The host device of claim 12 , wherein to synchronize each of the local clocks with the reference clock, the processing component sends second packets to each of the client devices in response to requests from each of the client devices, the second packets having time information to correlate the local clocks with the reference clock. 14. The host device of claim 9 , further comprising: an engine for processing the media data into processed media; and a media interface for presenting the processed media data, wherein the processing component is operatively coupled to the engine and the media interface, the processing component controlling processing of the media data with the engine such that the media interface presents the processed media data in a synchronized manner commensurate with the plurality of client devices.
Electricity · mapped topic
for broadcast or conference {, e.g. multicast} · CPC title
Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title
Electricity · mapped topic
adapting media to device capabilities · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.