# US 8,788,692 B2 · Method and system for broadcasting live data over a network > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,788,692 B2 - Document ID: US8788692B2 - Status: Granted - Kind: B2 - Application number: 12/016,962 - Filed: 2008-01-18 - Published: 2008-05-15 - Granted: 2014-07-22 - Earliest claimed: 2003-03-06 - Assignees: NVIDIA Corporation - Applicants: Mark Anthony Pereira - Inventors: Mark Anthony Pereira - Web page: https://patentgrep.com/patent/US8788692B2 ## CPC - H04L 12/1854: {with non-centralised forwarding system, e.g. chaincast} - H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Method and system for broadcasting live data over a network are described. In one embodiment, live data is accessed. Next, a first client is authenticated. The live data is then broadcast to a first client, wherein the first client is capable of buffering and re-transmitting the live data. Next, a second client is authenticated. A list of clients receiving the live data is then sent to the second client. The second client then selects the first client from the list, contacts the first client, and then receives the live data from the first client. ## Claims ### Claim 1 A server implemented method for terminating broadcasting of live data, said method comprising: broadcasting live data from said server to a first client, wherein said first client is operable to retransmit said live data to a second client, and wherein said server is a primary source of said live data being broadcasted to all clients; receiving a termination request signal from said first client; and enabling said second client to receive said live data from a third client before departure of said first client, wherein said first client is operable to signal said second client that the first client is going to stop retransmission of said live data prior to said second client receiving information about said third client, wherein said second client maintains a first list of clients subordinate to said second client in a broadcasting chain, and wherein said enabling comprises using said first list to ensure that said third client is above said second client in said broadcasting chain, wherein said enabling further comprises: sending a second list of clients to said second client, wherein said second list comprises clients that are receiving said live data, and wherein said second list comprises clients that are capable of retransmission of said live data, and wherein said second client in response to selecting said third client receives said live data from said third client, wherein said second list of clients comprises broadcast properties comprising: an IP address of said third client; a speed of connection of said third client; a number of clients already receiving said live data from said third client, and wherein said broadcasting chain connects said server to said third client and further connects said third client to said second client. ### Claim 2 (depends on 1) The method as described in claim 1, wherein said enabling comprises: directing said third client to retransmit said live data to said second client. ### Claim 3 (depends on 1) The method as described in claim 1 wherein said server directs said third client to retransmit said live data to said second client. ### Claim 4 (depends on 1) The method as described in claim 1, wherein said broadcast properties further comprise: a history of said third client up-time. ### Claim 5 (depends on 1) The method as described in claim 1 further comprising: in response to said enabling, terminating said broadcasting said live data to said first client. ### Claim 6 (depends on 1) The method as described in claim 1, wherein said third client is accessing said live data at an upper level of a broadcasting chain in comparison to said second client. ### Claim 7 (depends on 1) The method as described in claim 1 further comprising: maintaining said retransmission of said live data from said first client to said client until said second client receives said live data from said third client. ### Claim 8 (depends on 1) The method as described in claim 1, wherein said first client receives said live data directly from said server. ### Claim 9 A system comprising a processor, a transmitter/receiver and a memory component operable to store instructions that when executed on said processor implement a method for terminating broadcasting of live data, said method comprising: broadcasting live data from said system to a first client, wherein said first client is operable to retransmit said live data to a second client, and wherein said system is a primary source of said live data being broadcasted to all clients; receiving a termination request signal from said first client; and enabling said second client to receive said live data from a third client before departure of said first client, wherein said first client is operable to signal said second client that the first client is going to mopetransmission of said live data prior to said second client receiving information about said third client, wherein said enabling comprises directing said third client to retransmit said live data to said second client, wherein said second client maintains a first list of clients subordinate to said second client in a broadcasting chain, and wherein said enabling comprises using said first list to ensure that said third client is above said second client in said broadcasting chain, wherein said enabling further comprises: sending a second list of clients to said second client, wherein said second list comprises client that are receiving said live data, and wherein said second list comprise clients that are capable of retransmission of said live data, and wherein said second client in response to selecting said third client receives said live data from said third client, wherein said second list of clients comprises broadcast properties comprising: an IP address of said third client; a speed of connection of said third client; and a number of clients already receiving said live data from said third client, wherein said broadcasting chain connects said server to said third client and further connects said third client to said second client. ### Claim 10 (depends on 9) The system as described in claim 9, wherein said server directs said third client to retransmit said live data to said second client. ### Claim 11 (depends on 9) The system as described in claim 9 wherein said properties further comprise: a history of said third client up-time. ### Claim 12 (depends on 9) The system as described in claim 9 wherein said method further comprises: in response to said enabling, terminating said broadcasting said live data to said first client. ### Claim 13 (depends on 9) The system as described in claim 9, wherein said third client is accessing said live data at an upper level of a broadcasting chain in comparison to said second client. ### Claim 14 (depends on 9) The system as described in claim 9 wherein said method further comprises: maintaining said retransmission of said live data from said first client to said client until said second client receives said live data from said third client. ### Claim 15 (depends on 9) The system as described in claim 9, wherein said first client receives said live data directly from said server. ### Claim 16 (depends on 9) The system as described in claim 9, wherein said second client is operable to signal said system that the first client is going to stop retransmission.