System and method for sending packets over a computer network

• US 6,873,627 B1
• Filed: 07/30/1999
• Issued: 03/29/2005
• Est. Priority Date: 01/19/1995
• Status: Expired due to Fees

• Current Assignee: Hanger Solutions, LLC (IP Investments Group LLC)
• Original Assignee: The Fantastic Co. AG
• Inventors: White, Marc, Miller, C. Kenneth, Michelson, Craig, Gardner, Thomas, Andresen, Thomas, Cates, Kenneth, Robertson, Kary
• Primary Examiner(s): Pham, Chi
• Assistant Examiner(s): George, Keith M.
• Application Number:
  US09/364,761
• Time in Patent Office: 2,069 Days
• Field of Search: 370/236, 370/312, 370/389, 370/351, 370/390, 370/392, 370/395.5, 370/432, 370464-467, 370/471, 370/475, 709/203, 709/200, 709/228, 709/230, 709/238
• US Class Current: 370/466
• CPC Class Codes: H04L 1/1614 using bitmaps
• CPC Class Codes: H04L 1/1809 Selective-repeat protocols
• CPC Class Codes: H04L 12/184 with heterogeneous receivers, e.g. layered multicast
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• CPC Class Codes: H04L 12/1863 comprising mechanisms for improved reliability, e.g. status reports arrangements for detecting or preventing errors by carrying supervisory signal the return channel H04L1/16
• CPC Class Codes: H04L 12/1868 Measures taken after transmission, e.g. acknowledgments
• CPC Class Codes: H04L 2001/0093 Point-to-multipoint
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 43/0829 Packet loss
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/11 Identifying congestion
• CPC Class Codes: H04L 47/115 using a dedicated packet
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 47/29 using a combination of thresholds
• CPC Class Codes: H04L 5/1446 of transmission speed
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 67/63 : Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/16 : Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/163 : In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04L 69/24 : Negotiation of communication capabilities
• CPC Class Codes: H04L 69/324 : in the data link layer [OSI layer 2], e.g. HDLC
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04W 4/06 : Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Abstract

The benefits of a multicast-enabled network are realized by a flexible, easy to deploy, software-based solution that does not require reconfiguring of network routers. Systems and methods that implement this solution can perform as follows. A packet is received that was sent by a sender to at least one receiver, and the packet includes a parameter relating to a multicast announce address. A forwarding rules set is associated with the packet if the parameter has a defined value. This forwarding rules set is used to determine whether any of the at least one destination addresses included in the packet corresponds to one of the receivers that has a receiver format that must be converted. In addition, the forwarding rules set defines when a packet should be converted from a sender format to a receiver format before forwarding the packet. The packet is converted from the sender format to the receiver format for each destination address identified as requiring conversion, and forwarded in accordance with the forwarding rules set.

Claims

1. A method for sending packets over a computer network, comprising:

a) receiving a packet sent by a sender to at least one receiver, the packet comprising a parameter relating to a multicast announce address;

b) associating a forwarding rule set with the packet if the parameter has a defined value;

c) using the forwarding rules set to determine if any of the at least one destination addresses associated with the multicast announce address corresponds to a receiver that has a receiver format that must be converted, where the forwarding rules set defines when a packet should be converted from a sender format to a receiver format before forwarding the packet;

d) converting the packet from the sender format to the receiver format for each destination address identified in step (c)(b) as requiring conversion;

e) forwarding the packet in accordance with the forwarding rules set; and

f) configuring the forwarding rules set to be responsive to the addresses and formats of all senders and receivers on the computer network.

2. The method of claim 1, wherein the step of converting the packet from a sender format to a receiver format further comprises converting the packet from a sender format selected from the group consisting of multicast, broadcast, and unicast.

3. The method of claim 1 wherein the step of converting the packet from the sender format to the receiver format further comprises converting the packet from the sender format to a plurality of identical packets each having a receiver format.

4. The method of claim 1 wherein the step of converting the packet from the sender format to the receiver format further comprises:

(c-a) storing in at least one field in the packet a copy of each of the destination addresses in the packet identified in step (b) as requiring conversion, each stored destination address being in the sender format; and

(c-b) converting the destination addresses of the packet identified in step (b) as requiring conversion from the sender format to the receiver format.

5. The method of claim 4 further comprising the steps of:

(e) receiving the forwarded packet at each destination address;

(f) restoring the original destination addresses that were encapsulated within the forwarded packet as the destination addresses for the packet; and

(g) forwarding the packet to the destination addresses restored in step (f).

6. The method of claim 1 further comprising the step of discarding the packet if its source address is the same as its destination address.

7. The method of claim 1 further comprising the step of discarding the packet if the packet has already been multicast.

8. The method of claim 1 further comprising the step of discarding the packet if the packet has been forwarded a predetermined number of times.

9. The method of claim 1 further comprising the steps of:

e) receiving the packet forwarded in step (d) at a destination address; and

f) repeating steps (a) through (d).

10. The method of claim 1 further comprising the steps of:

(e) forwarding the packet to at least one destination address that does not require conversion, for each destination address identified in step (b) as not requiring conversion.

11. The method of claim 1, further comprising the steps of:

e) setting at least one parameter in the packet at the sender;

f) modifying the parameter each time that the packet is forwarded;

g) discarding the packet if a predetermined condition relating to the parameter is met; and

h) forwarding the packet to each destination address specified in the packet, if the packet is not discarded in step (g).

12. A method for sending packets over a computer network, comprising:

a) receiving a first packet sent by a sender to at least one receiver, the packet comprising at least one parameter relating to a multicast announce address;

b) associating a predetermined forwarding rule set with the packet if the parameter has a defined value, the predetermined forwarding rule set responsive to the parameter and to senders and receivers on the network;

c) associating a dynamic session forwarding rule set with the packet that is responsive to the parameter, if the parameter has a defined value;

d) using the forwarding rules set to determine if any of the at least one destination addresses associated with the multicast announce address corresponds to a receiver having a receiver format that must be converted, the forwarding rules set defining when a packet should be converted from a sender format to a receiver format before forwarding the packet;

e) converting the packet from the sender format to the receiver format for each destination address identified in step (b) as requiring conversion;

f) forwarding the first packet to each of the destination addresses included in the packet; and

g) using the session forwarding rules set to determine whether any of the destination addresses associated with the multicast announce address in future packets sent from the sender correspond to receivers having a receiver format that must be converted.

13. The method of claim 12, further comprising the step of (h) restoring the predetermined forwarding rules set upon the occurrence of a specified condition.

14. The method of claim 13 wherein the condition comprises a reaching a predetermined limit for a parameter selected from the list consisting of session timeout, time limit, content size, content rate, hop count, and forwarding limit.

15. The method of claim 12 further comprising the step of deleting the session forwarding rules set when sending of packets over the computer network in accordance with the multicast announce address is complete.

16. The method of claim 12 wherein the step of receiving a first packet further comprises receiving a first packet having a list relating to at least one receiver designated to receive additional packets from the senders.

17. The method of claim 12 wherein the step of receiving a first packet from the sender having a parameter further comprises receiving a first packet having a data transfer multicast address.

18. The method of claim 12 wherein the step of receiving a first packet from the sender having a parameter further comprises receiving a first packet having port information.

19. The method of claim 18 wherein the port information further comprises a first packet having a User Datagram Protocol (UDP) port.

20. The method of claim 12 wherein the step of receiving a first packet from the sender having a parameter further comprises receiving a first packet having information relating to the size of the additional packets to be sent from the sender.

21. The method of claim 12 wherein the step of receiving a first packet from the sender having a parameter further comprises receiving a first packet having information relating to the rate at which the sender will transmit additional packets.

22. The method of claim 12 wherein the step of receiving a first packet from the sender having a parameter further comprises receiving a first packet having information relating to a time limit beyond which packets will not be sent from the sender.

23. The method of claim 12 wherein the step of receiving a first packet from the sender having a parameter further comprises receiving a first packet having information relating to a time limit for receiving acknowledgements from receivers that receive additional packets from the sender.

24. A system for sending a packet over at least one computer network, comprising:

a) means for receiving a packet sent by a sender to at least one receiver, the packet comprising a parameter relating to a multicast announce address;

b) means for associating a forwarding rule set with the packet if the parameter has a defined value;

c) means for using the forwarding rules set to determine if any of the at least one destination addresses associated with the multicast announce address corresponds to a receiver that has a receiver format that must be converted, where the forwarding rules set defines when a packet should be converted from a sender format to a receiver format before forwarding the packet;

d) means for converting the packet from the sender format to the receiver format for each destination address identified in step (c)(b) as requiring conversion;

e) means for forwarding the packet in accordance with the forwarding rules set; and

f) means for configuring the forwarding rules set to be responsive to the addresses and formats of all senders and receivers on the computer network.