Method and apparatus for resource reservation in a multihop wireless network

• US 8,248,999 B2
• Filed: 11/13/2006
• Issued: 08/21/2012
• Est. Priority Date: 11/13/2006
• Status: Active Grant

• Current Assignee: Ruckus IP Holdings LLC
• Original Assignee: Motorola Solutions, Inc.
• Inventors: Ozer, Sebnem Zorlu, Goldberg, Keith J., Gossain, Hrishikesh
• Primary Examiner(s): Gelin, Jean
• Assistant Examiner(s): PATEL, MAHENDRA R
• Application Number:
  US11/559,239
• Publication Number:
  US 20080112357A1
• Time in Patent Office: 2,108 Days
• Field of Search: 370/329, 370/252, 370/337, 370/311, 370/338, 370/235, 370/348, 370/468, 370/395, 370/328, 455/446, 455/422, 709/238, 398/7
• US Class Current: 370/329
• CPC Class Codes: H04L 45/302 Route determination based on requested QoS
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/724 at intermediate nodes, e.g. resource reservation protocol [RSVP]
• CPC Class Codes: H04L 47/824 Applicable to portable or mobile terminals
• CPC Class Codes: H04W 28/26 Resource reservation
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

A message format for use in one or more multihop flow reservation messages in a multihop wireless network includes a reservation originator identification; a reservation terminator identification; a sequence control; and optionally a flow originator identification. A multihop flow reservation comprises forwarding a traffic stream request including the message format and forwarding a traffic stream reply including the message format along a multihop route. After the traffic stream reservation is completed, a data is forwarded along the multihop route.

Claims

1. A method for communicating a multihop flow reservation between a reservation originator and a reservation terminator along a path comprising a plurality of nodes in a multihop wireless network, the method comprising:

communicating one or more reservation messages between each of the plurality of nodes and an associated next hop node, wherein each of the communicated reservation messages includes an information element comprising;

an identification of the reservation originator of the multihop flow reservation,

an identification of the reservation terminator of the multihop flow reservation, and

a sequence control, wherein the sequence control identifies a current state of progress of the multihop flow reservation within the multihop wireless network and wherein the sequence control is incremented to indicate an operation on the multihop flow reservation;

receiving one or more reservation messages at the associated next hop node;

determining, by the associated next hop node, if the identification of the reservation originator combined with a traffic stream identification/access category maps to a particular flow in a traffic stream table of the associated next hop node; and

creating a new entry in a traffic stream table for the identification of the reservation originator and the traffic stream identification/access category when the identification of the reservation originator combined with the traffic stream identification/access category does not map to a particular flow in the traffic stream table.

2. A method for communicating a multihop flow reservation as claimed in claim 1, wherein the multihop wireless network comprises an 802.11e network, and further wherein the one or more reservation messages are selected from a group of messages comprising an Add Traffic Stream Request message (ADDTS.Request), an Add Traffic Stream response message (ADDTS.Response), and a Delete Traffic Stream message (DELTS).

3. A method for communicating a multihop flow reservation as claimed in claim 1, wherein the identification of the reservation originator identifies a source of the multihop flow reservation, and wherein the identification of the reservation terminator identifies a destination of the multihop flow reservation.

4. A method for communicating a multihop flow reservation as claimed in claim 1, wherein each of the communicated reservation messages further comprises:

an identification of a flow originator.

5. A method for communicating a multihop flow reservation as claimed in claim 1, further comprising:

determining a further next hop node using the identification of the reservation terminator in the information element and a routing table in the next hop node; and

sending the one or more reservation messages including the information element to the further next hop node.

6. A method for communicating a multihop flow reservation as claimed in claim 5, further comprising:

determining if the further next hop node is the terminator node; and

repeating the receiving, determining, creating, determining and sending steps at the further next hop node when the further next hop node is not the terminator node.

7. A method for communicating a multihop flow reservation as claimed in claim 1, further comprising:

updating, by the associated next hop node, a flow entry associated with a particular flow in the traffic stream table when the identification of the reservation originator combined with the traffic stream identification/access category maps to the particular flow in the traffic stream table of the next hop node and the sequence control in the received information element is more than a current sequence control in the flow entry.

8. A method for communicating a multihop flow reservation as claimed in claim 6, further comprising:

replying with an add data traffic stream response message including the information element when the further next hop node is the terminator node and the received reservation message is for a new flow.

9. A method for communicating a multihop flow reservation as claimed in claim 8, further comprising:

forwarding the add data traffic stream response message including the information element towards the initiator.

10. A method for communicating a multihop flow reservation as claimed in claim 9, further comprising:

forwarding one or more data frames from the initiator through the next hop node and the further next hop node to the terminator node.

11. A method for communicating a multihop flow reservation as claimed in claim 8, further comprising:

communicating a delete transmission stream message including the information element; and

deleting an entry in each of the traffic stream tables when the sequence number in the information element is greater than or equal to the sequence number of the flow maintained at the traffic stream table.

12. A method for communicating a multihop flow reservation as claimed in claim 6, further comprising:

replying with an add data traffic stream response message including the information element when the further next hop node is the terminator node and the received reservation message is for an existing flow when the sequence control in the received information element is more than a current sequence control entry for the flow in the traffic stream table.

13. A method for communicating a multihop flow reservation as claimed in claim 1, wherein the initiator comprises a device which can not support the traffic stream information element.

14. A method for communicating a multihop flow reservation as claimed in claim 13, wherein the associated next hop node comprises an access point, the method further comprising:

maintaining the sequence number on behalf of the device which can not support the traffic stream information element at the access point.

15. A method for communicating a multihop flow reservation as claimed in claim 14, further comprising:

receiving a data frame at the access point;

determining if the data originator identification combined with the traffic stream identification/access category maps to a particular flow in a traffic stream table of the access point; and

creating a new entry in the traffic stream table for the data originator as the reservation originator and the traffic stream identification/access category when the data originator identification combined with the traffic stream identification/access category does not map to a particular flow in the traffic stream table.

16. A method for communicating a multihop flow reservation as claimed in claim 15, further comprising:

creating a new traffic stream information element at the access point on behalf of the device which can not support the traffic information element;

setting the sequence control value to unknown by the access point on behalf of the device which can not support the traffic information element;

setting the reservation originator as the identification data frame originator; and

setting the reservation terminator as the identification of the destination of the data frame.

17. A method for communicating a multihop flow reservation as claimed in claim 16, further comprising when the next hop node is the terminator node:

setting the sequence code value by the terminator node when the sequence control in the received frame was set to unknown.

18. A method for communicating a multihop flow reservation as claimed in claim 1, wherein the information element further comprises an identification of a flow originator, the method further comprising:

creating a new entry in the traffic stream table for the identification of the flow originator, the identification of the reservation originator, and the traffic stream identification/access category when the identification of the flow originator and the identification of the reservation originator combined with the traffic stream identification/access category does not map to a particular flow in the traffic stream table.

19. A method for communicating a multihop flow reservation as claimed in claim 18, further comprising:

updating the flow entry in the traffic stream table when the identification of the flow originator and the identification of the reservation originator combined with the traffic stream identification/access category maps to a particular flow in the traffic stream table of the next hop node and the sequence control in the received information element is more than a current flow entry in the traffic stream table.