Bi-directional and reverse directional resource reservation setup protocol

Abstract

A wireless user equipment (UE) may include a reservation setup protocol (RSVP) message generator. The RSVP message generator may be configured to generate a RSVP message to a communication peer via a network that includes at least one router for reserving resources along a path. The RSVP PATH message may include a bi-directional direction indicator, an address of at least one router, and at least one of an indication of a peak data rate, token bucket rate, or maximum packet size. The message may provide an indication for reservation of bi-directional communication resources, wherein the bi-directional communication resources include resources in a direction from the device and in a direction toward the device. The UE may also include an RSVP message receiver configured to receive a refresh message, wherein the resources along the path are maintained upon receipt of the refresh message. The refresh message may be received periodically.

Description

FIELD OF INVENTION

The present invention relates to wireless packet based communications. In particular, the invention relates to establishing wireless packet based communications.

BACKGROUND

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.

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.

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.

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.

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

A wireless user equipment (UE) configured to initiate a packet based session is disclosed. The UE includes a reservation setup protocol (RSVP) message generator configured to transmit a RSVP PATH message. The RSVP PATH message includes a direction indication. The direction indicator indicates that reservations should be made for the UE to transmit only, to receive only or to both transmit and receive. The UE also includes an RSVP message receiver configured to receive an RSVP RESV message indicating that reservations have been made as a result of the RSVP PATH message.

BRIEF DESCRIPTION OF THE DRAWING(S)

FIG. 1 is an illustration of simplified wireless packet based communication system.

FIG. 2 is an illustration of establishing a wireless packet session.

FIG. 3 is an illustration of establishing a wireless packet session using bi-directional reservation setup protocol.

FIG. 4 is an illustration of establishing a wireless packet session using reverse direction reservation setup protocol.

FIG. 5 is a simplified illustration of a preferred reservation setup message.

FIG. 6 is a simplified illustration of a preferred forward direction reservation setup message.

FIG. 7 is a simplified illustration of a preferred reverse direction reservation setup protocol message.

FIG. 8 is a simplified illustration of a preferred bi-directional reservation setup protocol message.

FIG. 9 is an illustration of a preferred bi-directional reservation setup protocol PATH message.

FIG. 10 is an illustration of the SENDER_TSPEC of FIG. 9.

FIGS. 11 and 12 are illustrations of the ADSPEC of FIG. 9.

FIG. 13 is an illustration of a preferred bi-directional reservation setup protocol reservation message.

FIGS. 14 and 15 are illustrations of FLOWSPECs of the bi-directional reservation setup protocol reservation message of FIG. 13.

FIG. 16 is a simplified block diagram of a wireless user equipment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

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.

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.

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.

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.

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.

The reverse direction RSVP PATH message 46 is sent 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.

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 58₁-58_N. 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 54₁ 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 58_F1-58_FN 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 54₂ 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 58_R1-58_RN are for the reverse direction, “(REVERSE)”. A value “1111” for the direction indicator 54₃ 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)” 58_F1-58_FN and “(REVERSE)” 58_R1-58_RN objects are present.

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>”, “<RSVP_HOP>”, “<TIME_VALUES>”, “<POLICY_DATA>”, “<sender description>”, “<sender descriptor>”, “<SENDER_TEMPLATE>”, “<SENDER_TSPEC>” and “<ADSPEC>”.

FIG. 10 is an illustration of a “<SENDER_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.

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.

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>”, “<RSVP_HOP>”, “<TIME_VALUES>”, “<RESV_CONFIRM>”, “<SCOPE>”, “<POLICY_DATA>”, “<STYLE>”, “<flow descriptor list>” and “<flow descriptor>”.

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.

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. An 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). An RSVP message receiver 74 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.

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

1. A device comprising: a reservation setup protocol (RSVP) processor configured to generate an RSVP message; anda transmitter operatively coupled to the RSVP processor, the transmitter configured to transmit the RSVP message, to a communication peer via a network that includes at least one router, for reserving resources along a path;wherein the RSVP message includes a bi-directional direction indicator, an address of at least one router, and at least one of an indication of a peak data rate, a token bucket rate, or a maximum packet size.

2. The device of claim 1 wherein the RSVP message provides an indication for reservation of bi-directional communication resources, wherein the bi-directional communication resources include resources in a direction from the device and in a direction toward the device.

3. The device of claim 1 further comprising: a receiver operatively coupled to the RSVP processor, the receiver configured to receive a refresh message, wherein the resources along the path are maintained upon receipt of the refresh message.

4. The device of claim 3 wherein the refresh message is received periodically.

5. The device of claim 1 wherein the network is a wireless network.

6. The device of claim 1 wherein the RSVP message includes information to reserve resources for communication by routers along the path after the RSVP message is transmitted to the communication peer.

7. The device of claim 1 further comprising: a receiver operatively coupled to the RSVP processor, the receiver configured to receive an indication that resources have been successfully allocated.

8. A device comprising: a reservation setup protocol (RSVP) processor configured to generate a first RSVP message;a transmitter operatively coupled to the RSVP processor, the transmitter configured to transmit the first RSVP message, to a communication peer via a network that includes at least one router, for reserving resources along a path; anda receiver operatively coupled to the RSVP processor, the receiver configured to receive a second RSVP message from the communication peer in response to the first RSVP message, wherein the second RSVP message includes allocation information for resources to be modified;wherein the resources to be modified include resources for communication in directions both from the communication peer and toward the communication peer.

9. The device of claim 8 wherein the receiver is further configured to receive a refresh message, wherein the resources are maintained upon receipt of the refresh message.

10. The device of claim 9 wherein the refresh message is received periodically.

11. The device of claim 8 wherein the network is a wireless network.

12. The device of claim 8 wherein resources for communication in both directions to and from the communication peer are modified by routers along the path as the second message traverses the network along the path.

13. The device of claim 8 wherein the receiver is further configured to receive an indication that resources have been successfully allocated.

14. A method comprising: generating, by a reservation setup protocol (RSVP) processor in a device, an RSVP message; andtransmitting, by a transmitter, the RSVP message in the device, to a communication peer via a network that includes at least one router, for reserving resources along a path;wherein the RSVP message includes a bi-directional direction indicator, an address of at least one router, and at least one of an indication of a peak data rate, a token bucket rate, or a maximum packet size.

15. The method of claim 14 wherein the RSVP message provides an indication for reservation of bi-directional communication resources, wherein the bi-directional communication resources include resources in a direction from the device and in a direction toward the device.

16. The method of claim 14 further comprising: receiving, by a receiver in the device, a refresh message, wherein the resources along the path are maintained upon receipt of the refresh message.

17. The method of claim 16 wherein the refresh message is received periodically.

18. The method of claim 14 wherein the network is a wireless network.

19. The method of claim 14 wherein the RSVP message includes information to reserve resources for communication by routers along the path after the RSVP message is transmitted to the communication peer.

20. The method of claim 14 further comprising receiving, by a receiver in the device, an indication that resources have been successfully allocated.