Leaving a broadcast channel

Details Leaving a broadcast channel Leaving a broadcast channel

2000-07-31

2004-05-04

Winder, Patrice (Department: 2155)

Electrical computers and digital processing systems: multicomput

Computer conferencing

C709S227000

Reexamination Certificate

active

06732147

ABSTRACT:

TECHNICAL FIELD
The described technology relates generally to a computer network and more particularly, to a broadcast channel for a subset of a computers of an underlying network.
BACKGROUND
There are a wide variety of computer network communications techniques such as point-to-point network protocols, client/server middleware, multicasting network protocols, and peer-to-peer middleware. Each of these communications techniques have their advantages and disadvantages, but none is particularly well suited to the simultaneous sharing of information among computers that are widely distributed. For example, collaborative processing applications, such as a network meeting programs, have a need to distribute information in a timely manner to all participants who may be geographically distributed.
The point-to-point network protocols, such as UNIX pipes, TCP/IP, and UDP, allow processes on different computers to communicate via point-to-point connections. The interconnection of all participants using point-to-point connections, while theoretically possible, does not scale well as a number of participants grows. For example, each participating process would need to manage its direct connections to all other participating processes. Programmers, however, find it very difficult to manage single connections, and management of multiple connections is much more complex. In addition, participating processes may be limited to the number of direct connections that they can support. This limits the number of possible participants in the sharing of information.
The client/server middleware systems provide a server that coordinates the communications between the various clients who are sharing the information. The server functions as a central authority for controlling access to shared resources. Examples of client/server middleware systems include remote procedure calls (“RPC”), database servers, and the common object request broker architecture (“CORBA”). Client/server middleware systems are not particularly well suited to sharing of information among many participants. In particular, when a client stores information to be shared at the server, each other client would need to poll the server to determine that new information is being shared. Such polling places a very high overhead on the communications network. Alternatively, each client may register a callback with the server, which the server then invokes when new information is available to be shared. Such a callback technique presents a performance bottleneck because a single server needs to call back to each client whenever new information is to be shared. In addition, the reliability of the entire sharing of information depends upon the reliability of the single server. Thus, a failure at a single computer (i.e., the server) would prevent communications between any of the clients.
The multicasting network protocols allow the sending of broadcast messages to multiple recipients of a network. The current implementations of such multicasting network protocols tend to place an unacceptable overhead on the underlying network. For example, UDP multicasting would swamp the Internet when trying to locate all possible participants. IP multicasting has other problems that include needing special-purpose infrastructure (e.g., routers) to support the sharing of information efficiently.
The peer-to-peer middleware communications systems rely on a multicasting network protocol or a graph of point-to-point network protocols. Such peer-to-peer middleware is provided by the T.120 Internet standard, which is used in such products as Data Connection's D.C.-share and Microsoft's NetMeeting. These peer-to-peer middleware systems rely upon a user to assemble a point-to-point graph of the connections used for sharing the information. Thus, it is neither suitable nor desirable to use peer-to-peer middleware systems when more than a small number of participants is desired. In addition, the underlying architecture of the T.120 Internet standard is a tree structure, which relies on the root node of the tree for reliability of the entire network. That is, each message must pass through the root node in order to be received by all participants.
It would be desirable to have a reliable communications network that is suitable for the simultaneous sharing of information among a large number of the processes that are widely distributed.


REFERENCES:
patent: 4912656 (1990-03-01), Cain et al.
patent: 5056085 (1991-10-01), Vu
patent: 5309437 (1994-05-01), Perlman et al.
patent: 5426637 (1995-06-01), Derby et al.
patent: 5535199 (1996-07-01), Amri et al.
patent: 5568487 (1996-10-01), Sitbon et al.
patent: 5636371 (1997-06-01), Yu
patent: 5673265 (1997-09-01), Gupta et al.
patent: 5696903 (1997-12-01), Mahany
patent: 5732074 (1998-03-01), Spaur et al.
patent: 5732219 (1998-03-01), Blumer et al.
patent: 5734865 (1998-03-01), Yu
patent: 5737526 (1998-04-01), Periasamy et al.
patent: 5754830 (1998-05-01), Butts et al.
patent: 5761425 (1998-06-01), Miller
patent: 5764756 (1998-06-01), Onweller
patent: 5790548 (1998-08-01), Sistanizadeh et al.
patent: 5790553 (1998-08-01), Deaton, Jr. et al.
patent: 5799016 (1998-08-01), Onweller
patent: 5802285 (1998-09-01), Hirviniemi
patent: 5864711 (1999-01-01), Mairs et al.
patent: 5867660 (1999-02-01), Schmidt et al.
patent: 5867667 (1999-02-01), Butman et al.
patent: 5870605 (1999-02-01), Bracho et al.
patent: 5874960 (1999-02-01), Mairs et al.
patent: 5899980 (1999-05-01), Wilf et al.
patent: 5907610 (1999-05-01), Onweller
patent: 5928335 (1999-07-01), Morita
patent: 5935215 (1999-08-01), Bell et al.
patent: 5946316 (1999-08-01), Chen et al.
patent: 5948054 (1999-09-01), Nielsen
patent: 5949975 (1999-09-01), Batty et al.
patent: 5956484 (1999-09-01), Rosenberg et al.
patent: 5974043 (1999-10-01), Solomon
patent: 5987506 (1999-11-01), Carter et al.
patent: 6003088 (1999-12-01), Houston et al.
patent: 6013107 (2000-01-01), Blackshear et al.
patent: 6023734 (2000-02-01), Ratcliff et al.
patent: 6029171 (2000-02-01), Smiga et al.
patent: 6032188 (2000-02-01), Mairs et al.
patent: 6038602 (2000-03-01), Ishikawa
patent: 6047289 (2000-04-01), Thorne et al.
patent: 6073177 (2000-06-01), Hebel et al.
patent: 6094676 (2000-07-01), Gray et al.
patent: 6199116 (2001-03-01), May et al.
patent: 6216177 (2001-04-01), Mairs et al.
patent: 6223212 (2001-04-01), Batty et al.
patent: 6243691 (2001-06-01), Fisher et al.
patent: 6252884 (2001-06-01), Hunter
patent: 6268855 (2001-07-01), Mairs et al.
patent: 6271839 (2001-08-01), Mairs et al.
patent: 6285363 (2001-09-01), Mairs et al.
patent: 6304928 (2001-10-01), Mairs et al.
patent: 6353599 (2002-03-01), Bi et al.
patent: 6618752 (2003-09-01), Moore et al.
Bondy et al. “Graph Theory With Applications” American Elsevier Publishing Co. Inc. pp. 47-50 Secion 3.3.*
Yavatkar et al. “A Reliable Dissemination Protocol for Interactive Collaborative Applications” Proc. ACM Multimedia, 1995 p.333-344 http:/citeseer.nj.nec.com/article/yavatkar95reliable.html.*
Alagar, S. and Venkatesan, S., “Reliable Broadcast in Mobile Wireless Networks,” Department of Computer Science, University of Texas at Dallas, Military Communications Conference, 1995, MILCOM '95 Conference Record, IEEE San Diego, California, Nov. 5-8, 1995 (pp. 236-240).
International Search Report for The Boeing Company, International Patent Application No. PCT/US01/24240, Jun. 5, 2002 (7 pages).
U.S. patent application Ser. No. 09/629,570, Bourassa et al., filed Jul. 31, 2000.
U.S. patent application Ser. No. 09/629,576, Bourassa et al., filed Jul. 31, 2000.
U.S. patent application Ser. No. 09/629,575, Bourassa et al., filed Jul. 31, 2000.
U.S. patent application Ser. No.09/629,572, Bourassa et al., filed Jul. 31, 2000.
U.S. patent application Ser. No. 09/629,023, Bourassa et al., filed Jul. 31, 2000.
U.S. patent application Ser. No. 09/629,043, Bourassa et al., filed Jul. 31, 2000.
U.S. patent application Ser. No. 09/629,024, Bourassa et al., filed Jul. 31, 2000.
U.S. patent application Ser. No. 09/629,042, Bourassa et al., filed Jul. 31, 2

Affiliated with

Also associated with

Rating

Leaving a broadcast channel does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Leaving a broadcast channel, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Leaving a broadcast channel will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3218457