Method and device for route searching in a bluetooth ad-hoc network

• US 20030110291A1
• Filed: 12/12/2001
• Published: 06/12/2003
• Est. Priority Date: 12/12/2001
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Chen, Hongyuan
• Application Number:
  US10/020,808
• Publication Number:
  US 20030110291A1
• Time in Patent Office: Days
• US Class Current: 709/244
• CPC Class Codes: H04L 45/26 Route discovery packet
• CPC Class Codes: H04W 40/32 for defining a routing cluster membership
• CPC Class Codes: H04W 48/08 Access restriction or access information delivery, e.g. discovery data delivery signalling during connection H04W76/00
• CPC Class Codes: H04W 48/16 Discovering, processing access restriction or access information
• CPC Class Codes: H04W 84/20 Master-slave selection or change arrangements

Abstract

A method for transmitting a route request in an ad-hoc network having master nodes and slave nodes includes transmitting the route request to the master nodes of the network via a unicast transmission and transmitting a reply identifying the route. Each node of the network which receives the request performs a route request algorithm. The algorithm may be implemented in the network layer of the device protocol stack or in the link layer of the device protocol stack.

Claims

1. A method for transmitting a route request for a route between a source node and a destination node in an ad-hoc network and for transmitting a reply identifying the route, the ad-hoc network including a plurality of nodes including at least one master node in at least one piconet, said method comprising:

transmitting the route request from the receiving node in the ad-hoc network to the at least one master node of said at least one piconet via a unicast transmission; and

generating a route reply and sending the route reply to the source node, the route reply identifying the route in the ad-hoc network between the source node and the destination node.

2. The method of claim 1, wherein the route request is received by the receiving node from another node in the at least one piconet.

3. The method of claim 1, wherein the route request is generated within the receiving node.

4. The method of claim 1, further comprising the steps of:

(a) determining, before said step of transmitting, whether the route request has been previously received at the receiving node; and

(b) ignoring the route request if it is determined in said step (a) that the route request has been previously received at the receiving node.

5. The method of claim 4, wherein the route request is received by the receiving node from another node in the at least one piconet.

6. The method of claim 4, wherein the route request is generated within the receiving node.

7. The method of claim 1, further comprising the steps of:

(a) determining, before said step of transmitting, whether the receiving node is a master node; and

(b) determining whether the destination node is in the piconet of the receiving node if it is determined in said step (a) that the receiving node is a master node,

wherein said step of generating a route reply and sending the route reply to the source node is performed if it is determined in said step (b) that the destination node is in the piconet of the node, and said step of transmitting is performed if it is determined in said step (b) that the destination node is not in the piconet of the receiving node.

8. The method of claim 7, further comprising the step of adding the receiving node to a route list of a packet containing the route request before said step of generating a route reply if it is determined in said step (b) that the destination node is in the piconet of the receiving node.

9. The method of claim 1, further comprising the steps of:

(a) determining, before said step of transmitting, whether the receiving node is a master node; and

(b) determining whether the receiving node is participating in multiple piconets if it is determined in said step (a) that the receiving node is not a master node,

wherein said step of transmitting the route request to a master node of the receiving node includes transmitting the route request if it is determined in said step (b) that the receiving node is not participating in multiple piconets.

10. The method of claim 9, further comprising the step:

(c) determining whether the destination node is in the piconet of the master node of the receiving node after said step (b),

wherein said step of generating a route reply and sending the route reply to the source node includes generating and sending the route reply if it is determined in said step (c) that the destination node is in the piconet of the master node of the receiving node, and said step of transmitting the route request includes transmitting the route request if it is determined in said step (c) that the destination node is not in the piconet of the master node of the receiving node.

11. The method of claim 10, wherein the step of transmitting the route request comprises transmitting the route request to master nodes in piconets other than the piconet from which the route request was received if it is determined in said step (b) that the receiving node is participating in multiple piconets.

12. The method of claim 11, further comprising the steps of:

(i) determining, before performing said step (a), whether the route request has been previously received at the receiving node; and

(ii) ignoring the route request if it is determined in said step (i) that the route request has been previously received at the receiving node.

13. The method of claim 1, further comprising the steps of:

(a) determining, before said step of transmitting, whether the receiving node is a master node; and

(b) determining whether the receiving node is participating in multiple piconets if it is determined in said step (a) that the receiving node is not a master node,

wherein said step of transmitting the route request includes transmitting the route request to master nodes in piconets other than the piconet from which the route request was received if it is determined in said step (b) that the receiving node is participating in multiple piconets.

14. A device-readable memory for a communication device, the memory storing device-readable instructions for transmitting a route request in an ad-hoc network and for generating a route reply identifying the route, the route request being one of received at and generated by the communication device for a route between a source node and a destination node in the ad-hoc network, the ad-hoc network including a plurality of nodes including the communication device and at least one master node in at least one piconet, said memory comprising device-readable instructions for transmitting the route request from the communication device in the ad-hoc network to the at least one master node of the at least one piconet via a unicast transmission and for generating a route reply and sending the route reply to the source node, the route reply identifying the route in the ad-hoc network between the source node and the destination node.

15. The memory of claim 14, further comprising device-readable instructions for determining whether the route request has been previously received at the communication device before transmitting the route request and for ignoring the route request if it is determined that the route request has been previously received at the communication device.

16. The memory of claim 14, further comprising device-readable instructions for determining whether the communication device is a master node before transmitting the route request and for determining whether the destination node is in the piconet of the communication device if it is determined that the communication node is a master node, wherein said device-readable instructions for generating a route reply and sending the route reply to the source node include instructions for generating and sending the route reply if it is determined that the destination node is in the piconet of the communication device, and said device-readable instructions for transmitting the route request include instructions for transmitting the route request if it is determined that the destination node is not in the piconet of the communication device.

17. The memory of claim 16, wherein said device-readable instructions for generating a route reply further include device-readable instructions for adding the communication device to a route list of a packet containing the route request before sending the route reply if it is determined that the destination node is in the piconet of the communication device.

18. The memory of claim 14, further comprising device-readable instructions for determining, before transmitting the route request, whether the communication node is a master device and for determining whether the communication device is participating in multiple piconets if it is determined that the communication device is not a master node, wherein said device-readable instructions for transmitting the route request include instructions for transmitting the route request to a master node of the communication device if it is determined that the communication device is not participating in multiple piconets.

19. The memory of claim 18, further comprising device-readable instructions for determining whether the destination node is in the piconet of the master node of the communication device, wherein the device-readable instructions for generating a route reply and sending the route reply to the source node include instructions for generating and sending the route reply if it is determined that the destination node is in the piconet of the master node of the communication device, and said device-readable instructions for transmitting the route request include instructions for transmitting the route request if it is determined that the destination node is not in the piconet of the master node of the communication device.

20. The memory of claim 19, wherein said device-readable instructions for transmitting the route request include instructions for transmitting the route request to master nodes in piconets other than the piconet from which the route request was received if it is determined that the communication device is participating in multiple piconets.

21. The memory of claim 20, further comprising device readable instructions for determining whether the route request has been previously received at the communication device before determining whether the communication device is a master node, and for ignoring the route request if it is determined that the route request has been previously received at the communication device.

22. The memory of claim 14, further comprising device-readable instructions for determining, before transmitting the route request, whether the communication device is a master node and for determining whether the communication device is participating in multiple piconets if it is determined that the communication device is not a master node, wherein said device-readable instructions for transmitting the route request include instructions for transmitting the route request to master nodes in piconets other than the piconet from which the route request was received if it is determined that the communication device is participating in multiple piconets.

23. A wireless communication device for transmitting a route request for a route between a source node and a destination node in an ad-hoc network and for generating a route reply identifying the route, the route request being one of received at and generated by the device, wherein the ad-hoc network includes a plurality of nodes including the device and at least one master node in at least one piconet, said device comprising a transceiver and a memory storing device-executable instructions for transmitting the route request to the at least one master node of the at least one piconet via a unicast transmission and for generating a route reply and sending the route reply to the source node, the route reply identifying the route in the ad-hoc network between the source node and the destination node.

24. The device of claim 23, wherein said transceiver comprises a Bluetooth radio.

25. The device of claim 23, further comprising a protocol stack including a network layer and a link layer, said device-executable instructions comprising a part of said network layer.

26. The device of claim 25 wherein said network layer comprises a network block comprising device-executable instructions for ad-hoc networking, said device-executable instructions for transmitting the route request comprising a part of said device-executable instructions for ad-hoc networking.

27. The device of claim 23, further comprising a protocol stack including a network layer and a link layer, said device executable instructions comprising a part of said link layer.

28. The device of claim 27, wherein said link layer comprises a Bluetooth driver with a personal area network profile, said device-executable instructions comprising a part of said personal area network profile.

29. The device of claim 23, wherein said memory further comprises device-readable instructions for determining whether the route request has been previously received at the communication device before transmitting the route request and for ignoring the route request if it is determined that the route request has been previously received at the communication device.

30. The device of claim 23, wherein said memory further comprises device-readable instructions for determining whether the communication device is a master node before transmitting the route request and for determining whether the destination node is in the piconet of the communication device if it is determined that the communication device is a master node, wherein the device-readable instructions for generating a route reply and sending the route reply to the source node include instructions for generating and sending the route reply if it is determined that the destination node is in the piconet of the communication node, and said device-readable instructions for transmitting the route request include instructions for transmitting the route-request if it is determined that the destination node is not in the piconet of the communication node.

31. The device of claim 30, wherein said device-readable instructions for generating a route reply further include device-readable instructions for adding the communication device to a route list of a packet containing the route request before sending the route reply if it is determined that the destination node is in the piconet of the communication device.

32. The device of claim 23, wherein said memory further comprises device-readable instructions for determining, before transmitting the route request, whether the communication device is a master node and for determining whether the communication device is participating in multiple piconets if it is determined that the communication device is not a master node, wherein said device-readable instructions for transmitting a route request include instructions for transmitting the route request to a master node of the communication device if it is determined that the communication device is not participating in multiple piconets.

33. The device of claim 32, wherein said memory further comprises device-readable instructions for determining whether the destination node is in the piconet of the master node of the communication device, wherein said device-readable instructions for generating a route reply and sending the route reply to the source node include instructions for generating and sending the route reply if it is determined that the destination node is in the piconet of the master node of the communication device, and said device-readable instructions for transmitting the route request include instructions for transmitting the route request if it is determined that the destination node is not in the piconet of the master node of the communication device.

34. The device of claim 33, wherein said device-readable instructions for transmitting the route request include instructions for transmitting the route request to master nodes in piconets other than the piconet from which the route request was received if it is determined that the communication device is participating in multiple piconets.

35. The device of claim 34, wherein said memory further comprises device-readable instructions for determining whether the route request has been previously received at the communication device before determining whether the communication device is a master node, and for ignoring the route request if it is determined that the route request has been previously received at the communication device.

36. The device of claim 23, wherein said memory further comprises device-readable instructions for determining, before transmitting the route request, whether the communication device is a master node and for determining whether the communication device is participating in multiple piconets if it is determined that the communication device is not a master node, said device-readable instructions for transmitting a route request including instructions for transmitting the route request to master nodes in piconets other than the piconet from which the route request was received if it is determined that the communication device is participating in multiple piconets.

37. The device of claim 23, wherein said device comprises a mobile phone.

38. The device of claim 23, wherein said transceiver is operable for communication via a Bluetooth protocol.