Apparatus and method for determining aggregated link costs in a mobile ad hoc network

• US 7,480,248 B2
• Filed: 01/23/2004
• Issued: 01/20/2009
• Est. Priority Date: 08/22/2003
• Status: Expired due to Fees

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Leung, Nim K., Zhou, Jinhui, Herle, Sudhindra, Duggi, Mohan R.
• Primary Examiner(s): Pham; Chi H.
• Assistant Examiner(s): HOM, SHICK C
• Application Number:
  US10/763,409
• Publication Number:
  US 20050041591A1
• Time in Patent Office: 1,824 Days
• Field of Search: 370/311, 370/222, 370/341, 370/253
• US Class Current: 370/238
• CPC Class Codes: H04L 45/123 Evaluation of link metrics techniques for monitoring network metrics H04L43/08
• CPC Class Codes: H04L 45/302 Route determination based on requested QoS
• CPC Class Codes: H04M 15/31 Distributed metering or calculation of charges
• CPC Class Codes: H04M 15/44 Augmented, consolidated or itemized billing statement or bill presentation
• CPC Class Codes: H04M 15/49 Connection to several service providers
• CPC Class Codes: H04M 15/55 for hybrid networks
• CPC Class Codes: H04M 15/8022 Determining tariff or charge band
• CPC Class Codes: H04M 15/8044 Least cost routing
• CPC Class Codes: H04M 2215/0104 Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing
• CPC Class Codes: H04M 2215/22 Bandwidth or usage-sensitve billing
• CPC Class Codes: H04M 2215/32 Involving wireless systems
• CPC Class Codes: H04M 2215/42 Least cost routing, i.e. provision for selecting the lowest cost tariff
• CPC Class Codes: H04M 2215/44 Charging/billing arrangements for connection made over different networks, e.g. wireless and PSTN, ISDN, etc.
• CPC Class Codes: H04M 2215/46 Connection to several service providers
• CPC Class Codes: H04M 2215/7421 Determine tariff or charge band
• CPC Class Codes: H04M 2215/745 Least cost routing, e.g. Automatic or manual, call by call or by preselection
• CPC Class Codes: H04M 2215/96 Distributed calculation of charges, e.g. in different nodes like for mobiles between HLR and VLR, or between the terminal and the billing function
• CPC Class Codes: H04W 40/02 Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 40/28 for reactive routing
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

For use in a mobile ad hoc network (MANET), a first MANET node for aggregating route cost information associated with a first route from a source MANET node to a destination MANET node. The first MANET node comprises: 1) a radio frequency (RF) transceiver for wirelessly communicating with other MANET nodes; and 2) a controller for receiving incoming data packets from the RF transceiver and sending outgoing data packets to the RF transceiver. The controller receives a Route Request (RREQ) message generated by the source MANET node and retrieves initial route cost information from the RREQ message. The initial route cost information comprises an RF link cost parameter for a preceding RF link between the first MANET node and the source MANET node and a node cost parameter for a preceding MANET node between the first MANET node and the source MANET node.

Claims

1. For use in a mobile ad hoc network formed by a plurality of mobile ad hoc network (MANET) nodes, a first MANET node capable of aggregating route cost information associated with a first route from a source MANET node to a destination MANET node, said first MANET node comprising:

a radio frequency (RF) transceiver capable of wirelessly communicating with other ones of said plurality of MANET nodes; and

a controller capable of receiving incoming data packets from said RF transceiver and sending outgoing data packets to said RF transceiver, wherein said controller receives a Route Request (RREQ) message generated by said source MANET node and retrieves initial route cost information from said RREQ message, said initial route cost information comprising at least one RF link cost parameter and at least one node cost parameter, wherein said controller updates said initial route cost information in said RREQ message by adding to said initial route cost information (i) an RF link cost parameter associated with an RF link to an immediately preceding MANET node between said first MANET node and said source MANET node in said first route and (ii) a first node cost parameter associated with said first MANET node, and wherein the controller is further capable of assigning a first node-specific weight to the at least one RF link cost parameter added to the initial route cost information and assigning a second node-specific weight to the at least one node cost parameter added to the initial route cost information.

2. The first MANET node as set forth in claim 1 wherein said at least one RF link cost parameter is a zero value and said at least one node cost parameter is a zero value if said first MANET node receives said RREQ message directly from said source MANET node.

3. The first MANET node as set forth in claim 1 wherein said controller stores said initial route cost information retrieved from said RREQ message in a route table associated with said first MANET node.

4. The first MANET node as set forth in claim 1 wherein the first MANET node is a cell phone.

5. The first MANET node as set forth in claim 1 wherein said controller forwards said RREQ message containing said updated route cost information to a next MANET node between said first MANET node and said destination MANET node in said first route.

6. The first MANET node as set forth in claim 5 wherein said controller further receives a Route Reply (RREP) message generated by said destination MANET node and retrieves initial route cost information from said RREP message, said initial route cost information comprising at least one RF link cost parameter and at least one node cost parameter.

7. The first MANET node as set forth in claim 6 wherein said at least one RF link cost parameter in said RREP message is a zero value and said at least one node cost parameter in said RREP message is a zero value if said first MANET node receives said RREP message directly from said destination MANET node.

8. The first MANET node as set forth in claim 6 wherein said controller stores said initial route cost information retrieved from said RREP message in said route table.

9. The first MANET node as set forth in claim 6 wherein said controller updates said initial route cost information in said RREP message by adding to said initial route cost information (i) an RF link cost parameter associated with an RF link to an immediately preceding MANET node between said first MANET node and said destination MANET node in said first route and (ii) a first node cost parameter associated with said first MANET node.

10. The first MANET node as set forth in claim 9 wherein said controller forwards said RREP message containing said updated route cost information to a next MANET node between said first MANET node and said source MANET node in said first route.

11. For use in a mobile ad hoc network formed by a plurality of mobile ad hoc network (MANET) nodes, a method of aggregating in a first MANET node route cost information associated with a first route from a source MANET node to a destination MANET node, the method comprising the steps of:

wirelessly communicating with other ones of the plurality of MANET nodes;

receiving in the first MANET node a Route Request (RREQ) message generated by the source MANET node;

retrieving initial route cost information from the RREQ message, the initial route cost information comprising at least one radio frequency (RF) link cost parameter and at least one node cost parameter;

updating the initial route cost information in the RREQ message by adding to the initial route cost information (i) an RF link cost parameter associated with an RF link to an immediately preceding MANET node between the first MANET node and the source MANET node in the first route and (ii) a first node cost parameter associated with the first MANET node;

assigning a first node-specific weight to the at least one RF link cost parameter added to the initial route cost information; and

assigning a second node-specific weight to the at least one node cost parameter added to the initial route cost information.

12. The method as set forth in claim 11 wherein the at least one RF link cost parameter is a zero value and the at least one node cost parameter is a zero value if the first MANET node receives the RREQ message directly from the source MANET node.

13. The method as set forth in claim 11 further comprising the step of storing the initial route cost information retrieved from the RREQ message in a route table associated with the first MANET node.

14. The method as set forth in claim 11 where in the first MANET node is a cell phone.

15. The method as set forth in claim 11 further comprising the step of forwarding the RREQ message containing the updated route cost information to a next MANET node between the first MANET node and the destination MANET node in the first route.

16. The method as set forth in claim 15 further comprising the steps of:

receiving in the first MANET node a Route Reply (RREP) message generated by the destination MANET node; and

retrieving initial route cost information from the RREP message, the initial route cost information comprising at least one RF link cost parameter and at least one node cost parameter.

17. The method as set forth in claim 16 wherein the at least one RF link cost parameter in the RREP message is a zero value and the at least one node cost parameter in the RREP message is a zero value if the first MANET node receives the RREP message directly from the destination MANET node.

18. The method as set forth in claim 16 further comprising the step of storing the initial route cost information retrieved from the RREP message in the route table.

19. The method as set forth in claim 16 further comprising the step of updating the initial route cost information in the RREP message by adding to the initial route cost information (i) an RF link cost parameter associated with an RF link to an immediately preceding MANET node between the first MANET node and the destination MANET node in the first route and (ii) a first node cost parameter associated with the first MANET node.

20. The method as set forth in claim 19 further comprising the step of forwarding the RREP message containing the updated route cost information to a next MANET node between the first MANET node and the source MANET node in the first route.