Multiplex communications – Communication techniques for information carried in plural... – Adaptive
Reexamination Certificate
2000-04-12
2004-07-20
Phan, Man (Department: 2665)
Multiplex communications
Communication techniques for information carried in plural...
Adaptive
C370S230000, C370S351000, C370S390000, C370S410000, C709S226000, C709S240000
Reexamination Certificate
active
06765927
ABSTRACT:
BACKGROUND OF THE INVENTION
Data communication switches are becoming more and more intelligent. Whereas legacy data communication switches provided indiscriminate first-in, first-out forwarding of packets, more recent data communication switches support differential packet forwarding based on flow characteristics under the Quality of Service (QoS) label. The trend toward QoS started first in cell-switched ATM networks, but has migrated to packet-switched networks and protocols, including bridging (Layer 2, or “L2”), routing (Layer 3, or “L3”) and transport (Layer 4, or “L4”) protocols.
Standardized QoS elements are emerging in packet switched networks. One standard element is a signaling protocol through which a QoS may be provisioned end-to-end for a flow. This signaling protocol is called the Resource Reservation Protocol (RSVP). In conventional RSVP-signaled QoS provisioning, an RSVP-aware source host, called a “sender”, desiring to initiate a flow with an RSVP-aware destination host, called a “receiver”, transmits downstream an RSVP Path message specifying parameters for a proposed flow. Switches along the flowpath review the RSVP Path message and modify certain message fields as required to indicate limitations and conditions on their ability to deliver QoS services to the flow. The RSVP-aware destination host receives the RSVP Path message and uses the information therein to generate and transmit an RSVP Resv message back upstream requesting the provisioning of a specific QoS for the flow at each switch along the flowpath. Each switch determines whether or not to accept the request based on whether the switch has sufficient available resources to provide the requested QoS and whether the flow is entitled to the requested QoS. If the reservation is accepted, the switches are configured to forward packets within the flow in accordance with the QoS. In this way, an RSVP-signaled QoS for the flow is provisioned end-to-end along the flowpath.
While standard RSVP-signaled QoS, as outlined above, provides a means for end-to-end QoS provisioning within a network, it is only known to be available for flows between hosts that are RSVP-aware. There is a need to extend the benefits of RSVP-signaled QoS to flows involving RSVP-unaware hosts.
SUMMARY OF THE INVENTION
The present invention provides RSVP host proxy services for extending RSVP-signaled QoS provisioning to flows involving hosts that are not RSVP-aware.
In accordance with an RSVP sender host proxy service, a switch through which a first host accesses a network acts as an RSVP sender host proxy for the first host. Upon receiving a data packet for a new flow from the first host, and determining that the RSVP sender host proxy service is enabled for the first host, the switch generates and transmits on a flowpath to a second host an RSVP Path message. In accordance with RSVP, the RSVP Path message prompts the second host to generate and return on the flowpath an RSVP Resv message.
In accordance with an RSVP receiver host proxy service, a switch through which a first host accesses a network acts as an RSVP receiver host proxy for the first host. Upon receiving an RSVP Path message generated and transmitted by a second host and determining that the RSVP receiver host proxy service is enabled for the first host, the switch generates and returns on a flowpath to the second host an RSVP Resv message.
A switch serving as an RSVP host proxy for a host may continue to act as an RSVP router for hosts.
These and other aspects of the inventions may be better understood by reference to the following detailed description taken in conjunction with the accompanying drawings briefly described below.
REFERENCES:
patent: 5881246 (1999-03-01), Crawley et al.
patent: 5903735 (1999-05-01), Kiffer et al.
patent: 6021263 (2000-02-01), Kujoory et al.
patent: 6031841 (2000-02-01), Woundy
patent: 6058113 (2000-05-01), Chang
patent: 6073175 (2000-06-01), Tavs et al.
patent: 6101549 (2000-08-01), Baugher et al.
patent: 6252857 (2001-06-01), Fendick et al.
patent: 6286052 (2001-09-01), McCloghrie et al.
patent: 6341127 (2002-01-01), Katsube et al.
patent: 6343326 (2002-01-01), Acharya et al.
patent: 6385207 (2002-05-01), Woundy
patent: 6453349 (2002-09-01), Kano et al.
patent: 6519254 (2003-02-01), Chuah et al.
patent: 6567857 (2003-05-01), Gupta et al.
patent: 6621793 (2003-09-01), Widegren et al.
Software Functional Specification, Resource Reservation Protocol (RSVP), 8 pages.
Moy, “OSPF Version 2,” Mar. 1994, RFC 1583, p. 1-216.
Braden, et al., “Resource ReSerVation Protocol (RSVP)—Version 1 Functional Specification,” Sep. 1997, RFC 2205, pp. 1-112.
Baker, et al., “RSVP Management Information Base using SMIv2,” Sep. 1997, RFC 2206, pp. 1-64.
Braden, et al., “Resource ReSerVation Protocol (RSVP)—Version 1 Message Processing Rules,” Sep. 1997, RFC 2209, pp. 1-25.
Wroclawski, “The Use of RSVP with IETF Integrated Services,” Sep. 1997, RFC 2210, pp. 1-33.
Shenker, et al., “General Characterization Parameters for Integrated Service Network Elements”, Sep. 1997, RFC 2215, pp. 1-16.
Wahl, et al., “Lightweight Directory Access Protocol (v3)”, Dec. 1997, RFC 2251, pp. 1-50.
Moy, J., “OSPF Version 2,” www.ietf.org/rfc/rfc1583.txt, pp. 1-216, Mar. 1994.
Braden, R., et al., “Resource ReSerVation Protocol (RSVP)—Version 1 Functional Specification,” www.ietf.org/rfc/rfc2205.txt, pp. 1-112, Sep. 1997.
Baker, F., et al., “RSVP Management Information BAse Using SMIv2,” www.ietf.org/rfc/rfc2206.txt. pp. 1-64, Sep. 1997.
Braden, R., et al., “Resource ReSerVation Protocol (RSVP)—Version 1 Message Processing Rules,” www.ietf.org/rfc/rfc2209.txt, pp. 1-25, Sep. 1997.
Wroclawski, J., “The Use of RSVP with IETF Integrated Services,” www.ietf.org/rfc/rfc2210.txt, pp. 1-33, Sep. 1997.
Shenker, S., et al., “General Characterization Parameters for Integrated service Network Elements,” www.ietf.org/rfc/rfc2216.txt, pp. 1-16, Sep. 1997.
Wahl, M., et al., “Lightweight Directory Access Protocol (v3),” www.ietf.org/rfc/rfc2251.txt, pp. 1-50, Dec. 1997.
Edginton D. Brian
Martin Christopher
Alcatel
Cordeiro David A.
Michael Blaine Brooks P.C.
Nagelstad Andrew S.
Phan Man
LandOfFree
RSVP proxy service for communication network does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with RSVP proxy service for communication network, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and RSVP proxy service for communication network will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3200491