Method and system for broadcasting live data over a network

- Nvidia Corporation

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.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
RELATED U.S. PATENT APPLICATION

This Continuation Application claims the benefit of the co-pending, commonly-owned U.S. patent application Ser. No. 10/384,232, filed on Mar. 6, 2003, by Mark Pereira, and entitled “METHOD AND SYSTEM FOR BROADCASTING LIVE DATA OVER A NETWORK,” which is incorporated herein by reference.

FIELD OF THE INVENTION

Embodiments of the present invention relate to broadcasting live data. More specifically, embodiments of the present invention relate to methods and systems for broadcasting live data over a network.

BACKGROUND ART

Presently, computer systems and networks are utilized in many facets of daily life. For example, computer systems and networks are common both at home and in the workplace to increase output as well as provide user convenience and entertainment. One major utilization of computer systems is the broadcasting of live content over a network. For example, games are played on a network such as the internet wherein a server acts as the source of the game and a plurality of gamers (or players) connect directly with the server to play the game. Another example of live content broadcast is found in teleconferencing and virtual meetings.

As illustrated in Prior Art FIG. 1, in live content formats, a source 110 is being captured. As the content is captured, for example by an Internet camera, it is routed to a server 105 where it is fed into an encoder 150. Once the content is encoded it is transmitted (e.g., transmitter 130) via network 100 (e.g., the Internet) over a plurality of dedicated streams (e.g., 140 through 142) to all clients 120. Therefore, each client 120 has the opportunity to view the broadcast as it is happening. That is, each client 120 may see or hear what is said or done in real time with only a minimal delay or no delay at all.

However, one disadvantage to this approach is its inefficiency. Specifically, a dedicated stream (e.g., 140 through 142) is necessary per client 120. Therefore, it is appreciated that if a server has a substantial number of clients watching the live video stream, there may be no room to add additional clients. For example, server 105 may have bandwidth requirements that allow only a certain number of clients 120 to receive a certain quality bandwidth. Once the maximum number of clients 120 are reached, the server denies access to other clients 120 or reduce overall broadcast quality to open up more bandwidth for other clients 120.

Therefore, a particular live broadcast may not reach all intended clients due to bandwidth limitations, or the degraded quality of the broadcast may make reception of the broadcast poor and unstable with frequent pauses for rebuffering or reacquisition. These deleterious effects may further result in loss of clientele, unacceptable delays in reception of the live content, or the prohibitive expense of a more powerful server and/or network connection which may then maintain a higher number of streams at a higher quality.

Therefore, a method for broadcasting live data over a network, that is more efficient than the conventional art would be an improvement. The present invention provides such an improvement.

SUMMARY OF THE INVENTION

The present invention provides, in various embodiments, a method and system for broadcasting live data over a network. Furthermore, the present invention provides a method and system for broadcasting live data over a network which allows access to the broadcast only to authenticated users. In addition, the present invention provides a method and system for broadcasting live data over a network which maintains the quality (e.g., bandwidth) of the live content being broadcast. Moreover, the present invention provides a method and system for broadcasting live data over a network which is cost efficient.

Embodiments of the present invention pertain to methods 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.

In another embodiment, a server is broadcasting live content over a network such as the Internet. The broadcasting server authenticates a client to receive a broadcast and then either broadcasts directly to the client or allows the client to receive the broadcast from another device by selecting the device from a list of devices already receiving the broadcast. In so doing, the server can increase broadcast potential without subjecting clients to locked out conditions and/or reduced quality data associated with the server's bandwidth limitations.

In its various embodiments, the present invention can significantly reduce the bandwidth requirements of a network-based broadcast of live data. In addition, the present invention reduces the management responsibilities of the network-based broadcast. These and other objects and advantages of the various embodiments of the present invention will become recognized by those of ordinary skill in the art after having read the following detailed description of the embodiments that are illustrated in the various drawing figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments of the present invention and, together with the description, serve to explain the principles of the invention:

PRIOR ART FIG. 1 illustrates the conventional way live content is broadcast over a network.

FIG. 2 illustrates one system for broadcasting live data over a network in accordance with one embodiment of the present invention.

FIG. 3 illustrates another system for broadcasting live data over a network in accordance with one embodiment of the present invention.

FIG. 4 is a flowchart of a process for a device to access a live data broadcast in accordance with one embodiment of the present invention.

FIG. 5 is a flowchart of a process for exiting a live data broadcast in accordance with one embodiment of the present invention.

FIG. 6 is a flowchart of a process for broadcasting live data over a network according to an embodiment of the present invention.

FIG. 7 is a block diagram of exemplary circuitry of a computing system that may be used as a platform to implement embodiments of the present invention.

 DETAILED DESCRIPTION OF THE INVENTION

Reference will now be made in detail to embodiments of the invention, examples of which are illustrated in the accompanying drawings. While the invention will be described in conjunction with these embodiments, it will be understood that they are not intended to limit the invention to these embodiments. On the contrary, the invention is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims. Furthermore, in the following detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present invention.

Some portions of the detailed descriptions which follow are presented in terms of procedures, logic blocks, processing, and other symbolic representations of operations on data bits within an electronic computing device and/or memory system. These descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. A procedure, logic block, process, etc., is herein, and generally, conceived to be a self-consistent sequence of steps or instructions leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these physical manipulations take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computer system or similar electronic computing device. For reasons of convenience, and with reference to common usage, these signals are referred to as bits, values, elements, symbols, characters, terms, numbers, or the like with reference to the present invention.

It should be borne in mind, however, that all of these terms are to be interpreted as referencing physical manipulations and quantities and are merely convenient labels and are to be interpreted further in view of terms commonly used in the art. Unless specifically stated otherwise as apparent from the following discussions, it is understood that throughout discussions of the present invention, discussions utilizing terms such as “accessing”, “receiving”, “processing”, “creating”, “broadcasting”, “utilizing”, “directing”, “generating”, “providing”, “enqueuing”, “dequeuing”, “performing”, or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data. The data is represented as physical (electronic) quantities within the computing device's registers and memories and is transformed into other data similarly represented as physical quantities within the computing device's memories or registers or other such information storage, transmission, or display devices.

In general, the present invention allows a client that is receiving a live content broadcast from a server to not only receive the live content, but also retransmit the live content to another client. Thus, by having a client act as a second server, the live content may become available to more clients. As a result, a live broadcast may be viewed by more clients, and/or the overall quality of the broadcast may be increased. Therefore, by aggregating the broadcast clients available bandwidth, live data streams may be transmitted over a network (e.g., the Internet) to an unprecedented number of clients, at a higher quality level.

In one embodiment, the present invention reduces the number of clients directly accessing the broadcast server for the initial broadcast of live content over a network (e.g., the Internet). In so doing, the present invention may further allow the broadcast server to increase the bandwidth, and therefore the quality, of the live content being broadcast to each client. For example, if the broadcast server has a client or a number of clients watching a live video stream, and additional new clients also want to watch the same live video stream, the new clients may not necessarily receive their content from the broadcast server. In fact, the new clients may receive their content from the client/s already receiving the data stream.

That is, since the broadcast server has already sent the same live data to a client or clients, and that data has been buffered, the broadcast server may direct the already receiving client/s to broadcast the live data to the new clients. For example, since the server already knows which client/s are receiving the data it is sending as well as the transmission speeds at which the client/s are capable of sending and receiving, the server may direct any new clients to link to any of the other client/s already receiving the data.

In one embodiment, the client/s receiving the data may only rebroadcast the data to a new client after the broadcast server has signaled them about an incoming new link (e.g., a new client). In another embodiment, the client/s receiving the data may constantly rebroadcast the data being received. In general, a great benefit is realized when the broadcast server can transmit a single live video stream over a wide area network (WAN) to a single client in a local area network (LAN), and then that client can, in turn retransmit the live video stream to anyone else within the clients particular LAN. It should be appreciated that the re-transmitting of the live data may incur a slight delay due to the buffer and re-transmitting capabilities of the re-transmitting client. However, the slight delay which may be incurred is minimal. Thus, although the live data may be slightly delayed, it is nonetheless referred to herein as live data.

For example, a user may want to transmit a live broadcast of a wedding, child's baseball game, or meeting to other authorized clients (e.g., interested family members, friends, co-workers, or the like). Therefore, the user may use his own computing system as an initial server to broadcast or transmit the wedding, child's baseball game, or meeting over a network to the other interested parties. The first member of the interested party (e.g., relative, friend, co-worker, etc.) would then watch the broadcast and may also transmit it on to any other members of the interested party. Therefore, the entire interested party would have the opportunity to view the broadcast as it is happening. That is, they may see or hear what is said or done in real time with only a slight delay or no delay at all. Thus an initial broadcast to a network does not require a user to establish extreme amounts of bandwidth which may have high expense, portability, and convenience issues.

With reference now to FIG. 2, one system for broadcasting live data over a network is shown in accordance with an embodiment of the present invention. System 200 includes a source 210, broadcast server 205, dedicated streams 240 and 245, and clients 220, 230, and 240. Source 210 may be an easy capture device (such as a microphone, video camera, net camera, or the like) which may be used to capture or “feed” the live data to a broadcast server 205. Broadcast server 205 includes encoder 250 bus 255 and transmitter 230 and may be utilized to broadcast (and possibly encode) live data. That is, broadcast server 205 may be any device which can encode the live data from a source 210 and transmit the live data over a network (e.g., the Internet). In one embodiment, broadcast server 205 may be a computing system such as computing system 700 of FIG. 7.

First client 220 may access broadcast server 205 to receive the live data. For example, first client 220 may access broadcast server 205 and receive the live data via an initial data stream 240. In addition, as described in more detail herein, first client 220 may buffer and retransmit the broadcast from broadcast server 205. In one embodiment, first client 220 may be a computing device such as computing system 700 of FIG. 7. As described in more detail herein, clients 230 and 240 may access broadcast server 205, authenticate with broadcast server 205 receive a list of clients (e.g., first client 220) receiving and re-transmitting the live broadcast, select a client (e.g., first client 220), inform the broadcast server 205, and then begin receiving the live broadcast from first client 220. Therefore, client 230 and/or client 240 may receive the live data via streams 245 instead of receiving the live data directly from broadcast server 205.

For example, once broadcast server 205 is initially contacted by a first client 220, broadcast server 205 may authenticate first client 220 and begin to broadcast the live data to first client 220 via stream 240. Then, when another client (e.g., second client 230) contacts broadcast server 205 to receive the live broadcast, the broadcasting server 205 may authenticate second client 230 to receive the broadcast. Second client 230 may then receive a list of clients already receiving the broadcast. Second client 230 may then select a client from the list (e.g., first client 220) and inform broadcast server of the selection. Second client 230 may then contact first client 220 which is already receiving and transmitting (or capable of transmitting) the broadcast (e.g., client 220). Once second client 230 contacts first client 220, second client 230 begins receiving the live broadcast from first client 220 via stream 245. In so doing, broadcast server 205 can increase broadcast potential without subjecting clients to locked out conditions and/or slowed data associated with the broadcast server's bandwidth limitations. In addition, broadcast server 205 can further reduce processing requirements by allowing second client 230 to select which client it desires to receive the live broadcast from.

With reference now to FIG. 3, another system for broadcasting live data over a network is shown in accordance with another embodiment of the present invention. Specifically, system 300 shows the incorporation of a second branch of clients. For example, system 300 has a second stream 340 transmitted over a network (e.g., the Internet). In so doing, system 300 has the ability to add additional clients 330 and 340 to the network link via network streams 345. This is important since too many links in one re-transmit network may degrade the timeliness of the live data due to the possible rebuffering of the data stream per client.

As stated herein, FIG. 3 also illustrates the ability of a client (e.g., client 320) that is receiving the data stream (e.g. stream 340) from the server 205 to retransmit to more than one client. For example, client 320 may be broadcasting to a client 330 via stream 345 as well as client 340 via a separate stream 345. Thus, another branch is developed in the re-broadcasting network of system 300. This may be useful in the case of a client 320 residing behind a firewall and re-broadcasting to other clients within a LAN as described in more detail herein.

With reference now to FIG. 4, a flowchart of a process for a device to access a live data broadcast is shown in accordance with one embodiment of the present invention. It is appreciated that the steps of flowchart 400 are exemplary and that some steps may be skipped and other steps may be added depending on the plurality of possible contacting and re-transmitting protocols which may be used by the plethora of possible client devices. The present steps (e.g., steps 405 through 450) are meant to illustrate one of the plurality of possible ways in which a client may receive a live broadcast.

With reference now to step 405 of FIG. 4 and FIG. 2, a client contacts a broadcast server 205 to obtain a live data broadcast. As described herein, the client may contact broadcast server 205 via a network connection.

With reference now to step 407 of FIG. 4 and FIG. 2, once the client contacts broadcast server 205, broadcast server 205 may authenticate the client to ensure that the client has permission to access to the desired live broadcast. For example, if the live broadcast is a business meeting, the clients involved in the meeting may be the only clients authorized to receive the broadcast. Therefore, if an unauthorized user contacted broadcast server 205, or any of the other clients receiving the live broadcast, the unauthorized user would be denied access and could not receive the original live broadcast or any re-transmissions of the live broadcast. In one embodiment, the authentication may be based on a pre-determined status (e.g., CEO of a company may have access to all live broadcasts received within the company firewall), or the authentication may be based on specific situational dictation (e.g., competing clients may be allowed access to the same live broadcast if a universal dispersion of the information is required).

With reference now to step 410 of FIG. 4 and FIG. 2, after authenticating the client broadcast server 205 may check to see if the desired live data is being broadcast over a network. For example, broadcast server 205 may check to see the number of streams 240 related to the desired live data which are being broadcast over the network.

With reference now to step 420 of FIG. 4 and FIG. 2, if broadcast server 205 is not broadcasting the desired live data over the network, then broadcast server 205 will initiate a stream 240 to deliver the live broadcast to first client 220.

However, with reference now to step 430 of FIG. 4 and FIG. 2, if broadcast server 205 is broadcasting the desired live data over the network, then in one embodiment, broadcast server 205 may maintain a list of all clients receiving and transmitting (or capable of transmitting) the broadcast data. Therefore, broadcast server 205 may provide the second client with a list of the devices which are already receiving the live broadcast. For example, if broadcast server 205 is broadcasting the desired live data over the network, then in one embodiment, broadcast server 205 may give the second client 230 a list of devices (e.g., first client 220) which are already receiving the live broadcast.

With reference now to step 440 of FIG. 4 and FIG. 2, the second client will then select the device from which it will receive the live broadcast. For example, second client 230 may select first client 220 as its source for receiving the live data. In another embodiment, broadcast server 205 may direct the second client 230 to receive the broadcast from a specified first client 220 instead of allowing the second client 230 to select first client 220 from a list. In one embodiment, during the login process, the second client 230 may select the first client 220 based on broadcasting properties of the first client 220 such as IP address, speed of connection, number of clients already receiving from the first client, history of first client up-time, and the like.

With reference now to step 450 of FIG. 4 and FIG. 2, the second client may receive the live broadcast from the first client. For example, second client 230 may receive the live broadcast from first client 220. As stated herein, first client 220 may be constantly re-transmitting the live data, or first client 220 may not start re-transmitting the live data until broadcast server 205 authorizes it to do so. Therefore, in one embodiment, access to the live broadcast may be controlled by broadcast server 205.

With reference now to FIG. 5, a flowchart of a process for exiting a live data broadcast is shown in accordance with one embodiment of the present invention. Specifically, due to the possibility that a client wishing to exit a broadcast may be a link in the receive/re-transmit chain, flowchart 500 is utilized as one embodiment for maintaining the integrity of the live broadcast for all clients involved. However, it is appreciated that the steps of flowchart 500 are exemplary and that some steps may be skipped and other steps may be added depending on the plurality of possible exit protocols which may be used by the plethora of possible client devices. The present steps (e.g., steps 505 through 560) are meant to illustrate one of the plurality of possible ways in which a client may exit a live broadcast.

With reference now to step 505 of FIG. 5 and FIG. 2, the client receiving the live broadcast contacts broadcast server 205 and requests to stop receiving the broadcast. This step may be initiated by a client or a device that has received a command to stop reception by a client. Step 505 may also be utilized by broadcast server 205 to stop the live broadcast to a client. For example, broadcast server 205 may stop the live broadcast to a client due to overdue fees, another clients' explicit exclusion demand, improper actions of the client, or the like. In any case, the status of the departing client should be obtained.

With reference still now to step 510 of FIG. 5 and FIG. 2, a query of whether or not the client is broadcasting to another device is necessary. If the client is broadcasting to another device then a warning may be necessary to ensure that the integrity of the live broadcast is not disrupted.

With reference still to FIG. 2, and now to step 520 of FIG. 5, if the client is not broadcasting to another device, then the client may inform broadcast server 205 of its departure and stop reception of stream 240. For example, if client 240 is departing, then since client 240 is not re-transmitting to another client, it may simply inform broadcast server 205 and stop receiving the live broadcast.

However, with reference now to step 530 of FIG. 5 and FIG. 2, if the client is broadcasting to another device, then the client may send a message informing broadcast server 205 and the next lower device in the chain of the intent to stop broadcast reception and re-transmission. For example, client 230 may transmit a signal to broadcast server 205 and client 240 of its intent to stop reception and re-transmission. In another embodiment, the departing client 230 may simply send the message to broadcast server 205. Then, broadcast server 205 may either inform client 240 of the imminent departure of client 230 or may simply reassign client 240 to a new transmitter. In yet another embodiment, the departing client 230 may simply send the message to the next lower client 240. Then, client 240 may either inform broadcast server 205 of the imminent departure of client 230 or may simply reassign itself to a new transmitter. In addition to sending a message, client 230 may also keep receiving and transmitting the live data until client 240 transfers to a new transmitter.

With reference now to step 540 of FIG. 5 and FIG. 2, the next lower client in the chain may receive a new source list for receiving the live broadcast. For example, client 240 may receive a source list from broadcast server 205 with client 220 being made available as a source. In another embodiment, as stated herein, broadcast server 205 may simply reassign client 240 to a new transmitter (e.g., client 220). In addition, the next lower client may maintain a list of all other clients accessing the broadcast at a lower level in its specific chain. In so doing, the next lower client may ensure that it will not default to receive the broadcast from another client accessing its own broadcast at a lower level. For example, if client 220 were departing, then client 230 would not want to move its reception to the transmissions of client 240.

With reference still now to step 550 of FIG. 5 and FIG. 2, the next lower client in the chain selects the new source for receiving the live broadcast. For example, if client 230 is departing, then client 240 may select client 220 as its new source for receiving the live broadcast. In another embodiment, as stated herein, server 205 may simply assign client 240 to a new transmitter. In yet another embodiment, when client 230 departs, client 240 may simply move up the chain and begin receiving the live broadcast from client 220 without selecting from a list. However, in such a case, it must be ensured that the buffer maintained by client 230 was not so large that a significant portion of the live broadcast will be lost during the changeover to reception from client 210. That is, a client should not step up in the branches of the chain an amount of time greater than what is stored in the clients' buffer.

With reference now to step 560 of FIG. 5 and FIG. 2, the next lower client in the chain begins receiving the live broadcast from the new transmitter. For example, client 240 will begin receiving the live broadcast from client 220. After the next lower client has begun reception from another transmitter, the departing client moves back to step 510 wherein the question of the client broadcasting to another device is asked. If the answer to the question is no then the step 520 is performed and the client may depart. However, if the answer is yes then the process must begin again at step 530.

With reference now to FIG. 6, a flowchart of a process for broadcasting live data over a network is shown in accordance with an embodiment of the present invention.

With reference now to step 601 of FIG. 6, live data may be accessed. As stated herein, the live data may be audio and/or video data transmitted as live or real time.

With reference now to step 602 of FIG. 6, a first client is authenticated. As stated herein, the authentication of the first client may be based on a static authentication (e.g., a CEO may have access to all live broadcasts behind the company firewall), or a dynamic authentication (e.g., the authentication may be provided or revoked dependent on a specific situation).

With reference now to step 603 of FIG. 6, in one embodiment the live data may be broadcast to a first client capable of buffering and re-transmitting the live data. In one embodiment, the live data may be broadcast to the first client via a broadcast server. As stated herein, the client may be any type of computing device capable of accessing a network and receiving live data. For example, the client may be a computer, a wireless telephone, a personal digital assistant (PDA), or the like which can access a network as well as playback and re-transmit data.

In one embodiment, in order to motivate clients to re-transmit the live broadcast, a fee (e.g., brownie points, demerits, money, access time, etc.) may be charged per client per amount of broadcast received, and a reward (e.g., brownie points, merits, money, access time, etc.) may be paid per client per amount of broadcast transmitted.

In another embodiment, a first client may be assigned as a high priority client. That is, the first client may be a receive only client. For example, if the first client 220 is a client such as a CEO, the first client may inform broadcast server 205 that it will not re-transmit the live broadcast in order to maintain a higher personal performance level. In yet another embodiment, the second client may be assigned as a high priority client. For example, if the first client 220 is a client such as a CEO, the first client may inform broadcast server 205 that it will not re-transmit the live broadcast in order to maintain a higher personal performance level.

With reference now to step 604 of FIG. 6, a second client is authenticated. As stated herein, the authentication of the second client may be based on a static authentication (e.g., a CEO may have access to all live broadcasts behind the company firewall), or a dynamic authentication (e.g., the authentication may be provided or revoked dependent on a specific situation).

Referring now to step 605 of FIG. 6, in one embodiment, a list of the clients receiving the live data is sent to the second client. For example, when the second client 230 contacts broadcast server 205, broadcast server 205 may transmit the list to second client 230. Included in the list may be first client 220 and any other clients receiving the live broadcast.

Referring now to step 606, of FIG. 6, the second client may select to receive the live data from the first client, contact the first client, and then begin reception of the live data from the first client. For example, after second client 230 receives the list of clients from broadcast server 205, the second client 230 may select first client 220. Then, second client 230 may contact first client 220 and request stream 245 to be established. Once stream 245 is established, second client 230 may begin reception from first client 220. In addition, second client 230 may inform the broadcast server 205 of the selection in order that broadcast server 205 may update its database of clients receiving and re-transmitting the broadcast data.

In addition, the broadcast server may maintain a bandwidth reserve to temporarily transmit to a second client in case of a fault occurring with the first client. For example, if the first client unexpectedly fails (or drops out), the broadcast server may temporarily transmit the live data to the second client until a suitable replacement first client can be identified and/or utilized. In another embodiment, if the first client unexpectedly fails (or drops out), the broadcast server may take over the transmission of the live data to the second client.

With reference now to FIG. 7, a block diagram of an embodiment of an exemplary computer system 700 used in accordance with the present invention. It should be appreciated that system 700 is not strictly limited to be a computer system. As such, system 700 of the present embodiment is well suited to be any type of computing device (e.g., server computer, portable computing device, desktop computer, mobile phone, pager, personal digital assistant, etc.). Within the following discussions of the present invention, certain processes and steps are discussed that are realized, in one embodiment, as a series of instructions (e.g., software program) that reside within computer readable memory units of computer system 700 and executed by a processor(s) of system 700. When executed, the instructions cause computer 700 to perform specific actions and exhibit specific behavior that is described in detail herein.

Computer system 700 of FIG. 7 comprises an address/data bus 255 for communicating information, one or more central processors 702 coupled with bus 255 for processing information and instructions. Central processor unit(s) 702 may be a microprocessor or any other type of processor. The computer 700 also includes data storage features such as a computer usable volatile memory unit 704 (e.g., random access memory, static RAM, dynamic RAM, etc.) coupled with bus 255 for storing information and instructions for central processor(s) 702, a computer usable non-volatile memory unit 706 (e.g., read only memory, programmable ROM, flash memory, EPROM, EEPROM, etc.) coupled with bus 255 for storing static information and instructions for processor(s) 702. System 700 also includes one or more signal generating and receiving devices 708 coupled with bus 255 for enabling system 700 to interface with other electronic devices and computer systems. The communication interface(s) 708 of the present embodiment may include wired and/or wireless communication technology.

Optionally, computer system 700 may include an alphanumeric input device 714 including alphanumeric and function keys coupled to the bus 255 for communicating information and command selections to the central processor(s) 702. The computer 700 can include an optional cursor control or cursor directing device 716 coupled to the bus 255 for communicating user input information and command selections to the central processor(s) 702. The cursor-directing device 716 may be implemented using a number of well known devices such as a mouse, a track-ball, a track-pad, an optical tracking device, and a touch screen, among others. Alternatively, it is appreciated that a cursor may be directed and/or activated via input from the alphanumeric input device 714 using special keys and key sequence commands. The present embodiment is also well suited to directing a cursor by other means such as, for example, voice commands.

The system 700 of FIG. 7 may also include one or more optional source devices 210 such as an easy capture device (e.g., camera, microphone, etc.) coupled with bus 255 for providing live content to system 700. An optional display device 712 is coupled to bus 255 of system 700 for displaying video and/or graphics. It should be appreciated that optional display device 712 may be a cathode ray tube (CRT), flat panel liquid crystal display (LCD), field emission display (FED), plasma display or any other display device suitable for displaying video and/or graphic images and alphanumeric characters recognizable to a user.

Thus, the present invention provides, in various embodiments, a method and system for broadcasting live data over a network. Furthermore, the present invention provides a method and system for broadcasting live data over a network which allows access to the broadcast only to authenticated users. In addition, the present invention provides a method and system for broadcasting live data over a network which maintains the quality (e.g., bandwidth) of the live content being broadcast. Moreover, the present invention provides a method and system for broadcasting live data over a network which is cost efficient.

The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the Claims appended hereto and their equivalents.

Claims

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.

2. The method as described in claim 1, wherein said enabling comprises:

directing said third client to retransmit said live data to said second client.

3. The method as described in claim 1 wherein said server directs said third client to retransmit said live data to said second client.

4. The method as described in claim 1, wherein said broadcast properties further comprise: a history of said third client up-time.

5. The method as described in claim 1 further comprising:

in response to said enabling, terminating said broadcasting said live data to said first client.

6. 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.

7. 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.

8. The method as described in claim 1, wherein said first client receives said live data directly from said server.

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: 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,

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:
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.

10. The system as described in claim 9, wherein said server directs said third client to retransmit said live data to said second client.

11. The system as described in claim 9 wherein said properties further comprise: a history of said third client up-time.

12. 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.

13. 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.

14. 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.

15. The system as described in claim 9, wherein said first client receives said live data directly from said server.

16. 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.

Referenced Cited
U.S. Patent Documents
5377327 December 27, 1994 Jain et al.
5455569 October 3, 1995 Sherman et al.
5559933 September 24, 1996 Boswell
5590118 December 31, 1996 Nederlof
5751336 May 12, 1998 Aggarwal et al.
5778187 July 7, 1998 Monteiro et al.
5790958 August 4, 1998 McCoy et al.
5850396 December 15, 1998 Gilbert
5852714 December 22, 1998 Tseng et al.
5854892 December 29, 1998 Liu et al.
5884031 March 16, 1999 Ice
5948070 September 7, 1999 Fujita
5949411 September 7, 1999 Doerr et al.
6081840 June 27, 2000 Zhao
6084510 July 4, 2000 Lemelson et al.
6105145 August 15, 2000 Morgan et al.
6122259 September 19, 2000 Ishida
6185598 February 6, 2001 Farber et al.
6189039 February 13, 2001 Harvey et al.
6195680 February 27, 2001 Goldszmidt et al.
6222821 April 24, 2001 Sees et al.
6249810 June 19, 2001 Kiraly
6374289 April 16, 2002 Delaney et al.
6377996 April 23, 2002 Lumelsky et al.
6393468 May 21, 2002 McGee
6400407 June 4, 2002 Zigmond et al.
6434622 August 13, 2002 Monteiro et al.
6618752 September 9, 2003 Moore et al.
6633901 October 14, 2003 Zuili
6718361 April 6, 2004 Basani et al.
6859839 February 22, 2005 Zahorjan et al.
6901604 May 31, 2005 Kiraly
6970937 November 29, 2005 Huntington
7035933 April 25, 2006 O'Neal et al.
7136840 November 14, 2006 Pinkas et al.
20020059592 May 16, 2002 Kiraly
20030231629 December 18, 2003 Banerjee et al.
20040085928 May 6, 2004 Chari et al.
20040143672 July 22, 2004 Padmanabham et al.
20040143678 July 22, 2004 Chari et al.
20060253747 November 9, 2006 Gillies et al.
20080063003 March 13, 2008 O'Neal
20080212498 September 4, 2008 O'Neal et al.
20080294745 November 27, 2008 Lowery et al.
Foreign Patent Documents
0851364 July 1998 EP
97/48051 December 1997 WO
99/38266 July 1999 WO
00/49743 August 2000 WO
Other references
  • Furht, Barko, Westwater, Raymond, and Ice, Jeffrey “IP Simulcast: A New Technique for Multimedia Broadcasting Over the Internet”, Journal of Computing and Information, 1998.
  • Dejesus, Edmund X., “How the Internet Will Replace Broadcasting” Peterborough, New Hampshire, US.
  • “Pipe Dream Announces Breakthrough Internet Technology” Business Wire, Nov. 11, 1996.
Patent History
Patent number: 8788692
Type: Grant
Filed: Jan 18, 2008
Date of Patent: Jul 22, 2014
Patent Publication Number: 20080114891
Assignee: Nvidia Corporation (Santa Clara, CA)
Inventor: Mark Anthony Pereira (Livermore, CA)
Primary Examiner: Jerry Dennison
Application Number: 12/016,962
Classifications
Current U.S. Class: Computer-to-computer Data Streaming (709/231)
International Classification: G06F 15/16 (20060101);