Error detection/correction and fault detection/recovery – Data processing system error or fault handling – Reliability and availability
Reexamination Certificate
2000-12-14
2004-06-15
Beausoliel, Robert (Department: 2184)
Error detection/correction and fault detection/recovery
Data processing system error or fault handling
Reliability and availability
C725S151000, C713S163000
Reexamination Certificate
active
06751747
ABSTRACT:
FIELD OF THE INVENTION
The present invention relates generally to communication systems, and more particularly to providing redundancy for multicast streams in a multicast communication system.
BACKGROUND OF THE INVENTION
In today's information age, communication networks are often used for transporting information from an information provider to one or more information consumers.
One technique for transporting information from an information provider to a group of information consumers over the communication network is known as “multicasting.” Multicasting is a well-know method of transmitting information to selected groups of users across a network, such as the Internet. For example, the transmission of an e-mail message to a group of users, each user being listed on a mailing list, may use multicasting principles. Video conferencing and teleconferencing may also use multicasting principles and, accordingly, are often referred to as “multi-conferencing.” Multicasting allows the information provider (referred to hereinafter as a “multicast source”) to transmit a single unit of multicast information (referred to hereinafter as a “multicast packet”) simultaneously to all information consumers (referred to hereinafter individually as a “multicast host” and collectively as “multicast hosts”) in the multicast group, specifically by addressing the multicast packet to the multicast group using a multicast address. The multicast hosts monitor the communication network for multicast packets addressed to the multicast group.
In order to distribute multicast packets from a particular multicast source S to the multicast hosts for a particular multicast group G, the multicast packet is routed through the communication network by a number of routers. The communication network may include multiple routing domains, and therefore the multicast packet may traverse multiple routing domains. Each router runs various routing protocols to determine, among other things, a “next hop” for each packet based upon address information in the packets. Such routing information is used to establish a multicast distribution tree, and is maintained by each router in one or more routing tables (often referred to as a “routing information base”). Due to the increased demand for applications utilizing multicasting principles, protocols such as the Internet Group Multicast Protocol (“IGMP”) have been developed and refined to support multicasting over a Transmission Control Protocol/Internet Protocol (“TCP/IP”) network, such as the Internet. The new protocols, such as IGMP, allow users to easily create and join multicasting session (“multicasts”).
Typically, multicast networks are configured to communicate provider information from multiple providers to multicast clients over a single primary communications link. To provide redundancy, multicast networks are also connected to the multicast clients via a backup link as well so that, in the event of a failure in the primary link, the network will switch-over to the backup link to communicate the provider information.
One problem with the redundancy feature in the typical multicast network is that there is no provision made for a failure in a network provider which is unrelated to a link failure but which terminates the communication of provider information to the multicast clients. This can happen, for example, from the failure of one of the routers used to distribute multicast packets containing provider information to the multicast hosts. Because the network fails to detect a link failure, the switch-over to the backup link is not performed, resulting in the provider information not being communicated to the multicast clients.
Thus, a technique for providing redundancy in a multicast network in the event of a failure other than a link failure is needed.
SUMMARY OF THE INVENTION
In accordance with one aspect of the present invention, a networking device joins a multicast group over a primary interface. Joining the multicast group over the primary interface enables the networking device to receive multicast group information (i.e., a multicast stream) over the primary interface. The networking device monitors for multicast group information received over the primary interface. The networking device determines that there is a failure if no multicast group information is received over the primary interface for a predetermined amount of time. Upon detecting such a failure, the networking device typically joins the multicast group over a backup interface in order to continue receiving the multicast group information over the backup interface.
According to another aspect of the invention, the networking device receives a request from a multicast host to become a member of a multicast group and joins the multicast group over the primary interface on behalf of the multicast host. Upon determining that no information from the multicast group is received for a period of time over the primary interface, the networking device joins the multicast group over the backup interface on behalf of the multicast host to receive the information. The networking device remains joined to the multicast group over the primary interface on behalf of the multicast host and leaves the backup interface upon determining that the information is once again being received over the primary interface.
REFERENCES:
patent: 5748958 (1998-05-01), Badovinatz et al.
patent: 6512774 (2003-01-01), Vepa et al.
patent: 6523069 (2003-02-01), Luczycki et al.
patent: 6529882 (2003-03-01), Park et al.
patent: 6532233 (2003-03-01), Momona et al.
patent: 6539000 (2003-03-01), Murai et al.
patent: 2002/0165977 (2002-11-01), Novaes
W. Fenner, “Internet Group Management Protocol, Version 2,” Xerox PARC, Nov. 1997.
Cain, Deering, Kouvelas, Thyuagarajan, “Internet Group Management Protocol, Version 3,” <draft-ietf-idmr-igmp-v3-04.txt>, Jun. 2000.
Beausoliel Robert
McCarthy Christopher
Nortel Networks Limited
Steubing McGuinness & Manaras LLP
LandOfFree
System, device, and method for detecting and recovering from... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with System, device, and method for detecting and recovering from..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and System, device, and method for detecting and recovering from... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3304130