US 7,400,582 B2Grant
Bi-directional and reverse directional resource reservation setup protocol
Issue Date:2008-07-15
•18 Claims
•9 Drawing Sheets
Abstract
The invention relates to establishing a wireless packet session between at least two users. At least one of the users is a wireless user. A first of the at least two users sends a reservation setup protocol (RSVP) PATH message to a second user of the two users. The RSVP PATH message includes information for reserving resources for transmissions from only the first user to the second user; or from the first user to the second user and the second user to the first user, or only for transmissions from the second user to the first user. In response to receiving the RSVP PATH message, the second user transmits a RSVP reservation (RESV) message to the first user. Transmissions occur using the reserved resources.
Metadata
Assignee
- InterDigital Technology Corporation
Inventors
- Kamel M. Shaheen
- Sharif M. Shahrier
Application Information
Application Number:US 10/288,065
Filing Date:2002-11-04
Priority Date:2001-11-02
Art Unit:2616
Classifications
IPC:
H04L12/26H04B7/212G06F15/173
Patent Drawings (9 sheets)
Description
Cross Reference to Related Application(s)
[0001] This application claims priority from U.S. provisional application No. 60/336,304, filed Nov. 2, 2001, which is incorporated by reference as if fully set forth.
Field of Invention
[0002] The present invention relates to wireless packet based communications. In particular, the invention relates to establishing wireless packet based communications.
Background
[0003] For certain Internet applications, resources are reserved to achieve the necessary quality of service (QOS). The reservation of resources allows packet based networks to operate like circuit switched networks. FIG. 1 is an illustration of a simplified wireless packet based, such as Internet based, communication session, such as for wireless Internet, wireless multimedia, voice over Internet Protocol, video conferencing or video telephony, between two wireless users, user A and user B. Differing sessions have differing performance requirements, such as setup time, delay, reliability, integrity and quality of service (QOS). User A is shown as user equipment (UE) 20 and user B is shown as UE 22. User A sends and receives communicates via the packet network 28 using its cellular network 24. User B similarly sends and receives communications via the packet network 28 using its cellular network 26.
[0004] FIG. 2 is an illustration of establishing such a session. User A sends a resource reservation setup protocol (RSVP) PATH message 30 to establish the session. The RSVP PATH message 30 is sent to user B via various network routers (Router 1-Router N). Each router determines whether the resources are available for the session. If adequate resources are available, the RSVP PATH message 30 is updated and passed to the next router. If adequate resources are not available, an error message is sent back to user A. When user B receives the RSVP PATH message 30, user B responds by sending a RSVP reservation (RESV) message 32 to reserve the resources throughout the networks 24, 26, 28. As the RSVP RESV message 32 is sent through the networks, resources are allocated to support the communications from user A to user B. If the resources are successfully allocated, user A receives the RSVP RESV message 32. User A sends a confirmation (RSVP confirm) message 34 to user B to acknowledge receipt of the RSVP RESV message 32.
[0005] To allocate resources for user B's communications to user A, user B sends a RSVP PATH message 30 to user A via various network routers (Router 1-Router N). When user A receives the RSVP PATH message 30, user A responds by sending a RSVP RESV message 32 to reserve the resources throughout the networks 24, 26, 28. As the RSVP RESV message 32 is sent through the networks 24, 26, 28, resources are allocated to support the communications from user B to user A. If the resources are successfully allocated, user B receives the RESV message 32. User B sends a RSVP confirm message 34 to user A to acknowledge receipt of the RSVP RESV message 34.
[0006] To maintain the resource allocations, Refresh PATH messages 36 are periodically sent through the networks 24, 26, 28. User A sends Refresh PATH messages 36 through the networks 24, 26, 28 to user B to maintain the resources for user A's transmissions and user B sends Refresh PATH messages 36 through the networks 24, 26, 28 to user A to maintain the resources for user B's transmissions. If the Refresh PATH messages 36 are not sent, the reservation states will expire with the allocated resources being released.
[0007] Sending all these messages to allocate resources uses valuable network resources. Accordingly, it is desirable to have alternate approaches to establishing wireless Internet sessions.
Summary
[0008] The invention relates to establishing a wireless packet session between at least two users. At least one of the users is a wireless user. A first of the at least two users sends a reservation setup protocol (RSVP) PATH message to a second user of the two users. The RSVP PATH message includes information for reserving resources for transmissions from only the first user to the second user; or from the first user to the second user and the second user to the first user, or only for transmissions from the second user to the first user. In response to receiving the RSVP PATH message, the second user transmits a RSVP reservation (RESV) message to the first user. Transmissions occur using the reserved resources.
Brief Description of the Drawing(s)
[0009] FIG. 1 is an illustration of simplified wireless packet based communication system.
[0010] FIG. 2 is an illustration of establishing a wireless packet session.
[0011] FIG. 3 is an illustration of establishing a wireless packet session using bi-directional reservation setup protocol.
[0012] FIG. 4 is an illustration of establishing a wireless packet session using reverse direction reservation setup protocol.
[0013] FIG. 5 is a simplified illustration of a preferred reservation setup message.
[0014] FIG. 6 is a simplified illustration of a preferred forward direction reservation setup message.
[0015] FIG. 7 is a simplified illustration of a preferred reverse direction reservation setup protocol message.
[0016] FIG. 8 is a simplified illustration of a preferred bi-directional reservation setup protocol message.
[0017] FIG. 9 is an illustration of a preferred bi-directional reservation setup protocol PATH message.
[0018] FIG. 10 is an illustration of the SENDER13 TSPEC of FIG. 9 .
[0019] FIGS. 11 and 12 are illustrations of the ADSPEC of FIG. 9 .
[0020] FIG. 13 is an illustration of a preferred bi-directional reservation setup protocol reservation message.
[0021] FIGS. 14 and 15 are illustrations of FLOWSPECs of the bi-directional reservation setup protocol reservation message of FIG. 13 .
[0022] FIG. 16 is a simplified block diagram of a wireless user equipment.
Detailed Description of the Preferred Embodiment(s)
[0023] FIG. 3 is an illustration of bi-directional resource reservation setup protocol. User A desires to setup a bi-directional packet based, such as Internet, session with user B. The requirements, such as bit rate and relative delay, for the session are based on prior negotiations. Both users A and B may be wireless users or one of the two is a wireless user and the other is a wired user. To initiate the session, user A (the originating user) sends a bi-directional RSVP PATH message 38. The bi-directional RSVP PATH message 38 contains resource allocation information for both the communications transmitted from user A to user B and from user B to user A. The preferred format of these communications is discussed in more detail in conjunction with FIGS. 8 , 9, 10, 11 and 12. Although the invention is described primarily in conjunction with two-direction communications, the invention is extendable to any multiple party communications, such as three-way calling.
[0024] The bi-directional RSVP PATH message 38 is send through the various routers (Router 1-Router N) of the networks to user B. User B sends a bi-directional RSVP RESV message 40 to allocate the resources for both users through the networks 24, 26, 28. A preferred bi-directional RSVP RESV message 40 is described in more detail in conjunction with FIGS. 8 , 13, 14 and 15. Upon transferring the bi-directional RSVP RESV message 40, each network allocates the resources for both user A's and user B's transmissions. Upon receiving the bi-directional RSVP RESV message 40, indicating that the resources have been successfully allocated, user A sends a bi-directional RSVP confirm message 42 to user B through the networks. Upon receiving the bi-directional RSVP confirm message 42, bi-direction communication between users A and B begins. Preferably, the originating user, user A, is responsible for the session, such as for billing purposes. Making the originating user responsible for the session simplifies billing procedures.
[0025] To maintain the resource allocations, periodically, bi-directional Refresh PATH messages 44 are sent by user A through the networks to user B. Upon transferring the bi-directional Refresh PATH messages 44, the networks maintain the resource allocations for both directions.
[0026] Using the bi-directional messages reduces overhead required for the establishment of the session. Instead of both user A and user B sending RSVP PATH 30, RSVP RESV 32 and RSVP confirm 34 messages, only one user sends bi-directional messages. Although the information carried by each of these messages is typically increased, by reducing the number of messages, the overall network overhead is decreased. Additionally, the bi-directional messaging avoids call scenarios, where the resources in one direction are established and the resources in the other direction are not. The reduced overhead lessens the impact on air resources and improves network performance.
[0027] FIG. 4 is an illustration of reverse resource reservation setup protocol. User A desires to setup an Internet session where only user B transmits information. Both users A and B may be wireless users or one of the two is a wireless user and the other is a wired user. To initiate the session, user A (the originating user) sends a reverse direction RSVP PATH message 46. The reverse direction RSVP PATH message 46 contains resource allocation information for user B's transmissions to user A.
[0028] The reverse direction RSVP PATH message 46 is send through the various routers (Router 1-Router N) of the networks to user B. User B sends a reverse direction RSVP RESV message 48 to allocate the resources for its transmission. Upon receiving the reverse direction RSVP RESV message 48, user A sends a reverse direction RSVP confirm message 50 to user B through the networks 24, 26, 28. Upon receiving the reverse direction RSVP confirm message 50, user B begins transferring data to user A. Preferably, user A (although user A is not transmitting any substantive information) is responsible for the session.
[0029] FIG. 5 is an illustration of a simplified preferred RSVP message, illustrating generically the RSVP PATH, RSVP RESV and RSVP confirm messages. The preferred message has an IP header having a direction indicator, (forward, reverse and bi-directional) and having objects 581-58N. Preferably, the message is based on and is backward compatible with RFC 2205 and the direction indicator is a four bit indicator. For RFC 2205, the four bits of the direction indicator 541 are assigned the value “0000” for the forward direction (the originating user only sends information). A preferred forward direction RSVP message is shown in FIG. 6 , with only objects 58F1-58FN for the forward direction, “(FORWARD)”, being included. In RFC 2205, each user (each of users A and B) is an originating user. A value “0011” for the direction indicator 542 indicates the reverse direction (the originating user only receives information). A preferred reverse direction RSVP message is shown in FIG. 7 . In FIG. 7 , all of the objects 58R1-58RN are for the reverse direction, “(REVERSE)”. A value “1111” for the direction indicator 543 indicates both directions are used (the originating user will receive and send). A preferred bi-directional RSVP message is shown in FIG. 8 . In FIG. 8 , both “(FORWARD)” 58F1-58FN and “(REVERSE)” 58R1-58RN objects are present.
[0030] FIG. 9 is an illustration of a preferred bi-directional RSVP PATH message compatible with RFC 2205. The bi-directional RSVP PATH message has fields for the “<Path Message>”, “<Common Header>”, “<INTEGRITY>”, “<SESSION>”, “<RSVP13 HOP>”, “<TIME13 VALUES>”, “<POLICY13 DATA>”, “<sender description>”, “<sender descriptor>”, “<SENDER13 TEMPLATE>”, “<SENDER13 TSPEC>” and “<ADSPEC>”.
[0031] FIG. 10 is an illustration of a “<SENDER13 TSPEC>”. Along the top of the figure are numbers indicating the bit positions from bit position 0 to 31. As shown in FIG. 10 for a bi-directional RSVP PATH message, both “(Forward)” and “(Reverse)” information is included.
[0032] Two illustrations of the “<ADSPEC>” field are shown in FIGS. 11 and 12 . FIG. 11 illustrates a PATH Default ADSPEC and FIG. 12 illustrates a PATH Guaranteed Service ADSPEC. As shown in those figures, both ADSPECs contain both forward and reverse information.
[0033] FIG. 13 is an illustration of a preferred bi-directional RSVP RESV message compatible with RFC 2205. The bi-directional RSVP RESV message has fields for “<Resv Message>”, “<Common Header>”, “<INTEGRITY>”, “<SESSION>”, “<RSVP13 HOP>”, “<TIME13 VALUES>”, “<RESV13 CONFIRM>”, “<SCOPE>”, “<POLICY13 DATA>”, “<STYLE>”, “<flow descriptor list>” and “<flow descriptor>”.
[0034] The direction indicator is included in the “<flow descriptor list>”. Two illustrations of preferred FLOWSPECs of the “<flow descriptor list>” are shown in FIGS. 14 and 15 . FIG. 14 is a FLOWSPEC for Guaranteed service and FIG. 15 is a FLOWSPEC for Guaranteed Service Extension Format. As shown in FIGS. 14 and 15 for a bi-directional RSVP RESV message, both forward and reverse direction information is carried by the message.
[0035] FIG. 16 is a block diagram of a wireless user equipment for use in bi-directional, reverse direction and forward direction reservation setup protocol messaging. A RSVP message generator 72 produces the RSVP PATH messages (including bi-directional RSVP and reverse direction RSVP PATH messages), RSVP RESV messages (including bi-directional RSVP and reverse direction RSVP RESV messages), RSVP Confirm messages (including bi-directional RSVP and reverse direction RSVP Confirm messages) and Refresh PATH messages (including bi-directional and reverse direction Refresh Path messages). A RSVP receiver is used to receive the various RSVP messages. The messages that the UE transmits or receives is based on the whether the UE is the originating user or non-originating user, as previously described.
[0036] Session data is transmitted and received using a session data transmitter 76 and a session data receiver 78. An antenna 70 or antenna array are used to radiate and receive the various messages and communications across the air interface.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A method for establishing a wireless packet based session between at least two users, at least one of the two users being a wireless user, the method comprising:
a first of the at least two users sending a reservation setup protocol (RSVP) PATH message to a second user of the two users, wherein the RSVP PATH message includes information for reserving resources for transmissions from the first user to the second user and for reserving resources for transmissions from the second user to the first user;
receiving a RSVP reservation (RESV) message from the second user in response to the second user receiving the RSVP PATH message wherein the RSVP RESV message is sent through at least one packet based network, and wherein resources for the transmissions from the first and second user are reserved; and
at least the first user transmitting wireless packet based session information utilizing the reserved resources.
2. The method of claim 1 further comprising in response to receiving the RSVP RESV message by the first user, the first user sending a RSVP Confirm message to the second user to confirm receipt of the RSVP RESV message.
3. The method of claim 1 wherein the first and second users are each wireless users.
4. The method of claim 1 wherein the first user is a wireless user and the second user is a wired user.
5. The method of claim 1 wherein the first user is a wired user and the second user is a wireless user.
6. The method of claim 1 wherein the RSVP PATH message includes a direction indicator indicating the RSVP PATH message comprising information for reserving resources for the first and second user's transmissions.
7. The method of claim 6 wherein the direction indicator is a four bit indicator.
8. The method of claim 6 wherein the direction indicator has a value of “1111” to indicate that the information for reserving resources for the first and second user's transmissions is included.
9. The method of claim 1 wherein the first user is responsible for the wireless packet based session.
10. The method of claim 1 wherein the first user is billed for the session.
11. A method for establishing a wireless packet based session between at least two users, at least one of the two users being a wireless user, the method comprising:
receiving a reservation setup protocol (RSVP) PATH message from a first user at a second user of the at least two users, wherein the RSVP PATH message includes information for reserving resources for transmissions from the second user to the first user and not information for transmissions for the first user to the second user;
in response to receiving the RSVP PATH message, sending a RSVP reservation (RESV) message to the first user, as the RSVP RESV message is sent through at least one packet based network, resources for the transmission for the second user being reserved; and
at least the second user transmitting session information utilizing the reserved resources.
12. The method of claim 11 further comprising receiving an RSVP Confirm message from the first user in response to receiving the RSVP RESV message by the first user, wherein the RSVP Confirm message confirms receipt of the RSVP RESV message.
13. The method of claim 11 wherein the first and second users are each wireless users.
14. The method of claim 11 wherein the first user is a wireless user and the second user is a wired user.
15. The method of claim 11 wherein the first user is a wired user and the second user is a wireless user.
16. The method of claim 11 wherein the RSVP PATH message includes a direction indicator indicating the RSVP PATH message comprising information for reserving resources for the first and second user's transmissions.
17. The method of claim 16 wherein the direction indicator is a four bit indicator.
18. The method of claim 17 wherein the direction indicator has a value of “0011” to indicate that the information for reserving resources is only for the second user's transmissions.
Patent Citations (24)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5881064(A) | 1999-03-01 | Lin et al. | Applicant |
| US6385195(B2) | 2002-05-01 | Sicher et al. | Applicant |
| US6496479(B1) | 2002-12-01 | Shionozaki | Applicant |
| US6563794(B1) | 2003-05-01 | Takashima et al. | Applicant |
| US6671276(B1) | 2003-12-01 | Bakre et al. | Applicant |
| US6757266(B1) | 2004-06-01 | Hundscheidt | Applicant |
| US6920499(B2) | 2005-07-01 | Chen | Examiner |
| US6999436(B2) | 2006-02-01 | Zheng et al. | Examiner |
| US7123598(B1) | 2006-10-01 | Chaskar | Examiner |
| US7143168(B1) | 2006-11-01 | DiBiasio et al. | Examiner |
| US2001/0026554(A1) | 2001-10-01 | Holler et al. | Applicant |
| US2001/0027490(A1) | 2001-10-01 | Fodor et al. | Examiner |
| US2001/0054103(A1) | 2001-12-01 | Chen | Examiner |
| US2002/0015395(A1) | 2002-02-01 | Karagiannis | Applicant |
| US2002/0085494(A1) | 2002-07-01 | Seddigh et al. | Examiner |
| US2002/0091810(A1) | 2002-07-01 | Hundscheidt et al. | Examiner |
| EP1032179 | 1999-02-01 | Applicant | |
| JP2005-327710 | 1993-12-01 | Applicant | |
| JP11-154959 | 1999-06-01 | Applicant | |
| JP2000-078145 | 1999-06-01 | Applicant | |
| JP2001-053675 | 2001-02-01 | Applicant | |
| KR20010010980 | 2001-02-01 | Applicant | |
| KR2005-90088 | 2005-09-01 | Applicant | |
| TW435023 | 2001-05-01 | Applicant |
Non-Patent Literature (48)
- Kan et al, Internet Draft, Nokia Research Center, entitled: Two-plane and Three-tier QoS Framework for Mobile Ipv6 Networks, Apr. 2002, pp. 1-16.Applicant
- Shaheen et al, Internet Draft, InterDigital, entitled The Use of Bi-Directional RSVP in the Wireless Internet, Jul. 2002, pp. 1-22.Applicant
- Brunner et al., Internet Draft, NEC, entitled: Requirements for Qos Signaling Protocols, May 2002, pp. 1-59.Applicant
- Cable Television Laboratories, Inc. entitled: “PacketCable™ Dynamic Quality-of-Service Specification”, PKT-SP-DQOS-I02-000818, © 1999, 2000, pp. 1-203.Applicant
- Talukdar et al., MRSVP: A Resource Reservation Protocol For An Integrated Services Network With Mobile Hosts, http://citeseer.nj.nec.com/181006.htm, pp. 1-25, 1997.Applicant
- Braden et al, “Resource ReSerVation Protocol (RSVP)—Version 1 Functional Specification.” Network Working Group, Sep. 1997, pp. 18-21.Applicant
- Kan et al, Internet Draft, Nokia Research Center,entitled: Two-plane and Three-tier QoS Framework for Mobile lpv6 Networks, Apr. 2002, pp.1-16.Applicant
- Shaheen et al, Internet Draft, InterDigital, entitled The Use of Bi-Directional RSVP in the Wireless Internet, Jul. 2002, pp. 1-22.Applicant
- Brunner et al., Internet Draft, NEC, entitled: Requirements for QoS Signaling Protocols, May 2002, pp. 1-59.Applicant
- Cable Television Laboratories, Inc. entitled: “PacketCable ™ Dynamic Quality-of-Service Specification”, PKT-SP-DQOS-I02-000818, ©1999, 2000, pp. 1-203.Applicant
- Talukdar et al., MRSVP: A Resource Reservation Protocol For An Integrated Services Network With Mobile Hosts, http://citeseer.nj.nec.com/181006.htm, pp. 1-25, 1997.Applicant
- Braden et al. “Resource ReSerVation Protocol (RSVP) - Version 1 Functional Specification.” Network Working Group, Sep. 1997, pp. 18-21.Applicant
- J. Wroclawski “The Use of RSVP with IETF Integrated Services”, Network Working Group, RFC 2210, Sep. 1997.Applicant
- S. Shenker et al., “Network Element Service Specification Template”, Network Working Group, RFC 2216, Sep. 1997.Applicant
- S. Shenker et al. “Specification of Guaranteed Quality of Service”, Network working Group, RFC 2212, Sep. 1997.Applicant
- J. Wroclawski “Specification of the Controlled-Load Network Element Service”, Network Working Group, RFC 2211, Sep. 1997.Applicant
- S, Shenker et al. “General Characterization Parameters for Integrated Service Network Elements”, Network Working Group, RFC 2215, Sep. 1997.Applicant
- F. Baker et al.“RSVP Cryptographic Authentication”, Network Working Group, RFC 2747, Jan. 2000.Applicant
- R. Srinivasan “XDR: External Data Representation Standard”, Network Working Group, RFC 1832, Aug. 1995.Applicant
- Kan et al, Internet Draft, Nokia Research Center, entitled: Two-plane and Three-tier QoS Framework for Mobile Ipv6 Networks, Apr. 2002, pp. 1-16.Applicant
- Shaheen et al, Internet Draft, InterDigital, entitled The Use of Bi-Directional RSVP in the Wireless Internet, Jul. 2002, pp. 1-22.Applicant
- Brunner et al., Internet Draft, NEC, entitled: Requirements for QoS Signaling Protocols, May 2002, pp. 1-59.Applicant
- Cable Television Laboratories, Inc. entitled: “PacketCable ™ Dynamic Quality-of-Service Specification”, PKT-SP-DQOS-102-000818, ©1999, 2000, pp. 1-203.Applicant
- Talukdar et al., MRSVP: A Resource Reservation Protocol For An Integrated Services Network With Mobile Hosts, http://citesser.nj.nec.com/181006.htm, pp. 1-25, 1997.Applicant
- Braden et al. “resource ReSerVation Protocol (RSVP) - Version 1 Functional Specification.” Network Working Group, Sep. 1997, pp. 18-21.Applicant
- J. Wroclawski “The Use of RSVP with IETF Integrated Services”, Network Working Group, RFC 2210, Sep. 1997.Applicant
- S. Shenker et al. “Network Element Service Specification Template”, Network Working Group, RFC 2216, Sep. 1997.Applicant
- S. Shenker et al. “Specification of the Controlled-Load Network Element Service Network Elements”, Network Working Group, RFC 2215, Sep. 1997.Applicant
- J. Wroclawski “Specification of the Controlled-Load Network Element Service”, Network Working Group, RFC 2215, Sep. 1997.Applicant
- S. Shenker et al. “General Characterization Parameters for Integrated Service Network Elements”, Network Working Group, RFC 2215, Sep. 1997.Applicant
- F. Baker et al. “RSVP Cryptographic Authentication”, Network working Group, RFC 2747, Jan. 2000.Applicant
- R. Srinivasan “XDR: External Data Representation Standard”, Network Working Group, RFC 1832, Aug. 1995.Applicant
- Kan et al, Internet Draft, Nokia Research Center, entitled: Two-plane and Three-tier QoS Framework for Mobile Ipv6 Networks, Apr. 2002, pp. 1-16.Applicant
- Shaheen et al, Internet Draft, InterDigital, entitled The Use of Bi-Directional RDVP in the Wireless Internet, Jul. 2002, pp. 1-22.Applicant
- Braden et al. “Resource ReSerVation Protocol (RSVP) - Version 1 Functional Specification.” Network Working Group, Sep. 1997, pp. 18-21.Applicant
- Brunner et al., Internet Draft, NEC, entitled: Requirements for QoS Signaling Protocols, May 2002, pp. 1-59.Applicant
- Cable Television Laboratories, Inc.entitled: “PacketCable ™ Dynamic Quality-of-Service Specification”, PKT-SP-DQOS-102-000818, ©1999, pp. 1-203.Applicant
- F. Baker et al. “RSVP Cryptographic Authentication”, Network Work Group, RFC 2747, Jan. 2000.Applicant
- J. Wroclawski “Specification of the Controlled-Load Network Element Service”, Network Working Group, RFC 2211, Sep. 1997.Applicant
- J. Wroclawski “The Use of RSVP with IETF Integrated Services”, Network Working Group, RFC 2210, Sep. 1997.Applicant
- R. Srinivasan “XDR: External Data Representation Standard”, Network Working Group, RFC 1832, Aug. 1995.Applicant
- S. Shenker et al. “General Characterization Parameters for Integrated Service Network Elements”, Network Working Group, RFC 2215, Sep. 1997.Applicant
- S. Shenker et al. “Network Element Service Specification Template”, Network Working Group, RFC 2216, Sep. 1997.Applicant
- S. Shenker et al. “Specification of Guaranteed Quality of Service”, Network Working Group, RFC 2212, Sep. 1997.Applicant
- Shahrier et al., “A Framework for Bi-Directional QoS Signaling,” Internet Draft, (Dec. 2002).Applicant
- Talukdar et al., MRSVP: A Resource Reservation Protocol For An Integrated Services Network With Mobile Hosts, http://citeseer.nj.nec.com/181006.htm, pp. 1-25, 1997.Applicant
- Teraoka, “Next Generation Internet,” bit, vol. 30, No. 11, pp. 9-14 (nov. 1998).Applicant
- Watanabe et al., “Gateway for Media Cruising Resource Reservation Protocols in ATM Network,”Joint 4th IEEE International Conference on ATM, pp. 269 - 273 (2001).Applicant