Routing communications in an ad hoc network

• US 7,937,088 B2
• Filed: 03/26/2004
• Issued: 05/03/2011
• Est. Priority Date: 03/26/2004
• Status: Expired due to Fees

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Nanda, Sanjiv
• Primary Examiner(s): Corsaro; Nick
• Assistant Examiner(s): Ajayi; Joel
• Application Number:
  US10/809,997
• Publication Number:
  US 20050213531A1
• Time in Patent Office: 2,594 Days
• Field of Search: 370/401
• US Class Current: 455/445
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

Systems and techniques are disclosed relating to wireless communications. The systems and techniques involve wireless communications wherein a server terminal is configured to operate in a cluster on a network backbone. The server terminal includes a user interface configured to transmit and receive communications during a call with a first terminal connected to the network backbone, and a processor configured to support an inter-cluster call between second and third terminals by establishing a route on the network backbone for each communication packet transmitted from the second terminal to the third terminal.

Claims

1. A server terminal configured to operate in an ad hoc cluster of terminals, comprising:

a user interface configured to transmit and receive communications during a call with a first terminal connected to an ad hoc network backbone of an ad hoc network, the ad hoc network comprising a plurality of clusters, each of the clusters comprising at least two piconets and at least one gateway terminal, each gateway terminal configured to form a communications link between at least two of the plurality of clusters, each of the piconets comprising at least one intra-cluster bridge terminal, a master terminal, and a member terminal slaved to the master terminal, and the intra-cluster bridge terminal being a member of the two piconets and configured to form a communications link between the two piconets;

a processor configured to support an inter-cluster call between a second terminal in a first ad hoc cluster and a third terminal in a second ad hoc cluster by establishing a route on the network backbone for each communication packet transmitted from the second terminal to the third terminal, the route selected from a plurality of routes depending on whether the inter-cluster call is a first type of call or a second type of call that is different from the first type of call; and

the processor further configured to establish the route by;

mapping at least one adjacent ad hoc cluster to the corresponding gateway terminal and the corresponding master terminal; and

communicating with the corresponding master terminal associated with the selected one of the plurality of routes via the corresponding gateway terminal to support intra-cluster scheduling and forwarding of the communication packet from the second terminal.

2. The server terminal of claim 1, wherein the processor is further configured to establish the same route for each of the communication packets transmitted from the second terminal to the third terminal during the inter-cluster call for the first type of call, and to establish a different route for at least two of the communication packets transmitted from the second terminal to the third terminal during the inter-cluster call for the second type of call.

3. The server terminal of claim 1, wherein the processor is further configured to establish the route by constructing a network backbone topology map and selecting the route based on information in the network backbone topology map.

4. The server terminal of claim 3, wherein the processor is further configured to select the route as a function of the number of intermediary clusters between the second and third terminals.

5. The server terminal of claim 4, wherein the processor is further configured to select the route as a function of the energy of such transmission.

6. The server terminal of claim 1, wherein the processor is further configured to establish the route by mapping the third terminal to a primary route on the ad hoc network backbone to a first adjacent cluster and a secondary route on the ad hoc network backbone to a second adjacent cluster, and selecting the primary route or secondary route.

7. The server terminal of claim 6, wherein the processor is further configured to select the primary route during the first type of inter-cluster call, and select either the primary or secondary route during the second type of call, the selection of the primary or secondary route being based on the loading of the ad hoc network backbone.

8. The server terminal of claim 6, wherein the processor is further configured to establish the route by mapping the primary route to a first adjacent gateway terminal and a first adjacent master terminal for the first adjacent gateway terminal, and mapping the secondary route to a second adjacent gateway terminal and a second adjacent master terminal for the second adjacent gateway terminal.

9. The server terminal of claim 8, wherein the processor is further configured to establish the route by communicating with the respective one of the first adjacent master terminal or the second adjacent master terminal corresponding to the selected one of the primary or secondary routes to support intra-cluster scheduling and forwarding of such communication packet from the second terminal to the corresponding one of the first or second adjacent gateway.

10. The server terminal of claim 1, wherein the processor is further configured to establish the route using a network address assigned to the third terminal, and received from the network backbone in response to a location request.

11. The server terminal of claim 10, further comprising a cache, and wherein the processor is further configured to establish the route using a network address assigned to third terminal and stored in the cache.

27. The server terminal of claim 1, wherein the processor establishes the route on the ad hoc network backbone between a first inter-cluster bridge terminal in the first ad hoc cluster and a second inter-cluster bridge terminal in the second ad hoc cluster.

28. The server terminal of claim 27, wherein the inter-cluster bridge terminals comprise Address, Location, and Route (ALR) servers.

43. The server terminal of claim 1, wherein the route on the ad hoc network backbone is configured to pass through a first picocell for the first type of call and configured not to pass through the first picocell for the second type of call.

53. The server terminal of claim 1, wherein the respective gateway terminal of one of the plurality of clusters is configured to form a direct communications link with another gateway terminal of a different one of the plurality of clusters, and wherein the respective intra-cluster bridge terminal of one of the two piconets is configured to form a direct communications link with another intra-cluster bridge terminal of a different one of the two piconets.

12. A method of communications on a server terminal configured to operate in an ad hoc cluster of terminals, comprising:

transmitting and receiving communications at the server terminal during a call with a first terminal connected to an ad hoc network backbone of an ad hoc network, the ad hoc network comprising a plurality of clusters, each of the clusters comprising at least two piconets and at least one gateway terminal, each gateway terminal configured to form a communications link between at least two of the plurality of clusters, each of the piconets comprising at least one intra-cluster bridge terminal, a master terminal, and a member terminal slaved to the master terminal, and the intra-cluster bridge terminal being a member of the two piconets and configured to form a communications link between the two piconets;

supporting an inter-cluster call between a second terminal in a first ad hoc cluster and a third terminal in a second ad hoc cluster by establishing a route on the ad hoc network backbone for each communication packet transmitted from the second terminal to the third terminal, the route selected from a plurality of routes depending on whether the inter-cluster call is a first type of call or a second type of call that is different from the first type of call; and

the establishing of the route further comprising;

mapping at least one adjacent ad hoc cluster to the corresponding gateway terminal and the corresponding master terminal; and

communicating with the corresponding master terminal associated with the selected one of the plurality of routes via the corresponding gateway terminal to support intra-cluster scheduling and forwarding of the communication packet from the second terminal.

13. The method of claim 12, wherein the same route is established for each of the communication packets transmitted from the second terminal to the third terminal during the first type of inter-cluster call.

14. The method of claim 12, wherein a different route is established for at least two of the communication packets transmitted from the second terminal to the third terminal during the second type of inter-cluster call.

15. The method of claim 12, wherein the route is established by constructing a network backbone topology map and selecting the established route based on information in the network backbone topology map.

16. The method of claim 15, wherein the route is selected as a function of the number of intermediary clusters between the second and third terminals.

17. The method of claim 16, wherein the route is selected as a function of the energy of such transmission.

18. The method of claim 12, wherein the route is established by mapping the third terminal to a primary route on the ad hoc network backbone to a first adjacent cluster and a secondary route on the ad hoc network backbone to a second adjacent cluster, and selecting the primary route or the secondary route.

19. The method of claim 18, wherein the primary route is selected for each of the communication packets transmitted from the second terminal to the third terminal during the inter-cluster call.

20. The method of claim 18, wherein the selection of the primary or secondary route for each of the communication packets transmitted from the second terminal to the third terminal during the inter-cluster call is based on the loading of the ad hoc network backbone.

21. The method of claim 18, wherein the route is established by mapping the primary route to a first adjacent gateway terminal and a first adjacent master terminal for the first adjacent gateway terminal, and mapping the secondary route to a second adjacent gateway terminal and a second adjacent master terminal for the second adjacent gateway terminal.

22. The method of claim 21, wherein the route is established by communicating with the respective one of the first adjacent master terminal or the second adjacent master terminal corresponding to the selected one of the primary or secondary routes to support intra-cluster scheduling and forwarding of such communication packet from the second terminal to the corresponding one of the first or second adjacent gateway terminal.

23. The method of claim 12, wherein the route is established using a network address assigned to third terminal, the method further comprising receiving the network address from the ad hoc network backbone in response to a location request.

24. The method of claim 23, wherein the route is established using a network address assigned to third terminal, the method further comprising retrieving the network address stored in cache at the server terminal.

29. The method of claim 12, wherein establishing the route on the ad hoc network includes establishing the route between a first inter-cluster bridge terminal in the first ad hoc cluster and a second inter-cluster bridge terminal in the second ad hoc cluster.

30. The method of claim 29, wherein establishing the route between the first inter-cluster bridge terminal in the first ad hoc cluster and the second inter-cluster bridge terminal in the second ad hoc cluster includes establishing the route between Address, Location, and Route (ALR) servers.

44. The method of claim 12, wherein the route on the ad hoc network backbone is configured to pass through a first picocell for the first type of call and configured not to pass through the first picocell for the second type of call.

54. The method of claim 12, wherein the respective gateway terminal of one of the plurality of clusters is configured to form a direct communications link with another gateway terminal of a different one of the plurality of clusters, and wherein the respective intra-cluster bridge terminal of one of the two piconets is configured to form a direct communications link with another intra-cluster bridge terminal of a different one of the two piconets.

25. A server terminal configured to operate in an ad hoc cluster of terminals, comprising:

means for transmitting and receiving communications during a call with a first terminal connected to an ad hoc network backbone of an ad hoc network, the ad hoc network comprising a plurality of clusters, each of the clusters comprising at least two piconets and at least one gateway terminal, each gateway terminal configured to form a communications link between at least two of the plurality of clusters, each of the piconets comprising at least one intra-cluster bridge terminal, a master terminal, and a member terminal slaved to the master terminal, and the intra-cluster bridge terminal being a member of the two piconets and configured to form a communications link between the two piconets;

means for establishing a route on the ad hoc network backbone for each communication packet transmitted from a second terminal in a first ad hoc cluster to a third terminal in a second ad hoc cluster during an inter-cluster call, the route selected from a plurality of routes depending on whether the inter-cluster call is a first type of call or a second type of call that is different from the first type of call; and

the means for establishing the route further comprising;

means for mapping at least one adjacent ad hoc cluster to the corresponding gateway terminal and the corresponding master terminal; and

means for communicating with the corresponding master terminal associated with the selected one of the plurality of routes via the corresponding gateway terminal to support intra-cluster scheduling and forwarding of the communication packet from the second terminal.

45. The server terminal of claim 25, wherein the route on the ad hoc network backbone is configured to pass through a first picocell for the first type of call and configured not to pass through the first picocell for the second type of call.

55. The server terminal of claim 25, wherein the respective gateway terminal of one of the plurality of clusters is configured to form a direct communications link with another gateway terminal of a different one of the plurality of clusters, and wherein the respective intra-cluster bridge terminal of one of the two piconets is configured to form a direct communications link with another intra-cluster bridge terminal of a different one of the two piconets.

26. A method of communications to serve a plurality of terminals in an ad hoc cluster, the method comprising:

using a primary server terminal to support a plurality of inter-cluster calls for a number of the terminals in the ad hoc cluster by establishing a route on an ad hoc network backbone of an ad hoc network for each of the communication packets transmitted by each of the terminals to a corresponding other ad hoc cluster, the ad hoc network comprising a plurality of clusters, each of the clusters comprising at least two piconets and at least one gateway terminal, each gateway terminal configured to form a communications link between at least two of the plurality of clusters, each of the piconets comprising at least one intra-cluster bridge terminal, a master terminal, and a member terminal slaved to the master terminal, and the intra-cluster bridge terminal being a member of the two piconets and configured to form a communications link between the two piconets;

dynamically designating one of the terminals in the ad hoc cluster as a backup server terminal in accordance with an ad hoc protocol;

detecting a failure of the primary server terminal;

processing a message received from the ad hoc network backbone at the backup server terminal based on detecting the failure, the message being addressed to the primary server terminal;

selecting each route for each of the plurality of inter-cluster calls from a plurality of routes depending on whether the inter-cluster call is a first type of call or a second type of call that is different from the first type of call; and

the establishing of each route further comprising;

mapping at least one adjacent ad hoc cluster to the corresponding gateway terminal and the corresponding master terminal; and

communicating with the corresponding master terminal associated with the selected one of the plurality of routes via the corresponding gateway terminal to support intra-cluster scheduling and forwarding of the respective communication packet.

46. The method of claim 26, wherein the route on the ad hoc network backbone is configured to pass through a first picocell for the first type of call and configured not to pass through the first picocell for the second type of call.

56. The method of claim 26, wherein the respective gateway terminal of one of the plurality of clusters is configured to form a direct communications link with another gateway terminal of a different one of the plurality of clusters, and wherein the respective intra-cluster bridge terminal of one of the two piconets is configured to form a direct communications link with another intra-cluster bridge terminal of a different one of the two piconets.

31. At least one processor for communications on a server terminal configured to operate in an ad hoc cluster of terminals, comprising:

a first module for transmitting and receiving communications at the server terminal during a call with a first terminal connected to an ad hoc network backbone of an ad hoc network, the ad hoc network comprising a plurality of clusters, each of the clusters comprising at least two piconets and at least one gateway terminal, each gateway terminal configured to form a communications link between at least two of the plurality of clusters, each of the piconets comprising at least one intra-cluster bridge terminal, a master terminal, and a member terminal slaved to the master terminal, and the intra-cluster bridge terminal being a member of the two piconets and configured to form a communications link between the two piconets;

a second module for supporting an inter-cluster call between a second terminal in a first ad hoc cluster and a third terminal in a second ad hoc cluster by establishing a route on the network backbone for each communication packet transmitted from the second terminal to the third terminal, the route selected from a plurality of routes depending on whether the inter-cluster call is a first type of call or a second type of call that is different from the first type of call; and

the second module for supporting the inter-cluster call by establishing the route further configured for;

mapping at least one adjacent ad hoc cluster to the corresponding gateway terminal and the corresponding master terminal; and

communicating with the corresponding master terminal associated with the selected one of the plurality of routes via the corresponding gateway terminal to support intra-cluster scheduling and forwarding of the communication packet from the second terminal.

37. The at least one processor of claim 31, wherein the second module establishes the route on the ad hoc network backbone between a first inter-cluster bridge terminal in the first ad hoc cluster and a second inter-cluster bridge terminal in the second ad hoc cluster.

38. The at least one processor of claim 37, wherein the first and second inter-cluster bridge terminals are Address, Location, and Route (ALR) servers.

39. The at least one processor of claim 31, wherein the second module is further configured to establish the route by mapping a primary route on the ad hoc network backbone to a first adjacent ad hoc cluster and a secondary route on the ad hoc network backbone to a second adjacent ad hoc cluster, and selecting the primary route or secondary route.

40. The at least one processor of claim 39, wherein the second module is further configured to select the primary route during the first type of inter-cluster call, and to select either the primary or secondary route during the second type of call, the selection of the primary or secondary route being based on the loading of the ad hoc network backbone.

41. The at least one processor of claim 39, wherein the second module is further configured to establish the route by mapping the primary route to a first adjacent gateway terminal and a first adjacent master terminal for the first adjacent gateway terminal, and mapping the secondary route to a second adjacent gateway terminal and a second adjacent master terminal for the second adjacent gateway terminal.

42. The at least one processor of claim 41, wherein the second module is further configured to establish the route by communicating with the respective first or second adjacent master terminal mapped to the first or second adjacent ad hoc cluster corresponding to the selected one of the primary or secondary routes to support intra-cluster scheduling and forwarding of such communication packet from the second terminal.

47. The processor of claim 31, wherein the route on the ad hoc network backbone is configured to pass through a first picocell for the first type of call and configured not to pass through the first picocell for the second type of call.

57. The at least one processor of claim 31, wherein the respective gateway terminal of one of the plurality of clusters is configured to form a direct communications link with another gateway terminal of a different one of the plurality of clusters, and wherein respective the intra-cluster bridge terminal of one of the two piconets is configured to form a direct communications link with another intra-cluster bridge terminal of a different one of the two piconets.

32. A computer program product for communications on a server terminal configured to operate in an ad hoc cluster of terminals, comprising:

a computer-readable storage medium comprising;

a first set of codes for causing a computer to transmit and to receive communications at the server terminal during a call with a first terminal connected to an ad hoc network backbone of an ad hoc network, the ad hoc network comprising a plurality of clusters, each of the clusters comprising at least two piconets and at least one gateway terminal, each gateway terminal configured to form a communications link between at least two of the plurality of clusters, each of the piconets comprising at least one intra-cluster bridge terminal, a master terminal, and a member terminal slaved to the master terminal, and the intra-cluster bridge terminal being a member of the two piconets and configured to form a communications link between the two piconets;

a second set of codes for causing the computer to support an inter-cluster call between a second terminal in a first ad hoc cluster and a third terminal in a second ad hoc cluster by establishing a route on the network backbone for each communication packet transmitted from the second terminal to the third terminal, the route selected from a plurality of routes depending on whether the inter-cluster call is a first type of call or a second type of call that is different from the first type of call; and

the second set of codes for establishing the route further comprising;

at least one code for mapping at least one adjacent ad hoc cluster to the corresponding gateway terminal and the corresponding master terminal; and

at least one code for communicating with the corresponding master terminal associated with the selected one of the plurality of routes via the corresponding gateway terminal to support intra-cluster scheduling and forwarding of the communication packet from the second terminal.

48. The computer program product of claim 32, wherein the route on the ad hoc network backbone is configured to pass through a first picocell for the first type of call and configured not to pass through the first picocell for the second type of call.

58. The computer program product of claim 32, wherein the respective gateway terminal of one of the plurality of clusters is configured to form a direct communications link with another gateway terminal of a different one of the plurality of clusters, and wherein the respective intra-cluster bridge terminal of one of the two piconets is configured to form a direct communications link with another intra-cluster bridge terminal of a different one of the two piconets.

33. At least one processor for communications to serve a plurality of terminals in an ad hoc cluster, comprising:

a first module for using a primary server terminal to support a plurality of inter-cluster calls for a number of the terminals in the ad hoc cluster by establishing a route on an ad hoc network backbone of an ad hoc network for each of the communication packets transmitted by each of the terminals to a corresponding other ad hoc cluster, the ad hoc network comprising a plurality of clusters, each of the clusters comprising at least two piconets and at least one gateway terminal, each gateway terminal configured to form a communications link between at least two of the plurality of clusters, each of the piconets comprising at least one intra-cluster bridge terminal, a master terminal, and a member terminal slaved to the master terminal, and the intra-cluster bridge terminal being a member of the two piconets and configured to form a communications link between the two piconets;

a second module for dynamically designating one of the terminals in the ad hoc cluster as a backup server terminal in accordance with an ad hoc protocol;

a third module for detecting a failure of the primary server terminal;

a fourth module for processing a message received from the ad hoc network backbone at the backup server terminal based on detecting the failure, the message being addressed to the primary server terminal;

the first module selecting each route from a plurality of routes depending on whether the inter-cluster call is a first type of call or a second type of call that is different from the first type of call; and

the first module establishing each route by;

mapping at least one adjacent ad hoc cluster to the corresponding gateway terminal and the corresponding master terminal; and

communicating with the corresponding master terminal associated with the selected one of the plurality of routes via the corresponding gateway terminal to support intra-cluster scheduling and forwarding of the respective communication packet.

49. The processor of claim 33, wherein the route on the ad hoc network backbone is configured to pass through a first picocell for the first type of call and configured not to pass through the first picocell for the second type of call.

59. The processor of claim 33, wherein the respective gateway terminal of one of the plurality of clusters is configured to form a direct communications link with another gateway terminal of a different one of the plurality of clusters, and wherein the respective intra-cluster bridge terminal of one of the two piconets is configured to form a direct communications link with another intra-cluster bridge terminal of a different one of the two piconets.

34. A computer program product for communications to serve a plurality of terminals in an ad hoc cluster, comprising:

a computer-readable storage medium comprising;

a first set of codes for causing a computer to use a primary server terminal to support a plurality of inter-cluster calls for a number of the terminals in the ad hoc cluster by establishing a route on an ad hoc network backbone of an ad hoc network for each of the communication packets transmitted by each of the terminals to a corresponding other ad hoc cluster, the ad hoc network comprising a plurality of clusters, each of the clusters comprising at least two piconets and at least one gateway terminal, each gateway terminal configured to form a communications link between at least two of the plurality of clusters, each of the piconets comprising at least one intra-cluster bridge terminal, a master terminal, and a member terminal slaved to the master terminal, and the intra-cluster bridge terminal being a member of the two piconets and configured to form a communications link between the two piconets;

a second set of codes for causing the computer to dynamically designate one of the terminals in the ad hoc cluster as a backup server terminal in accordance with an ad hoc protocol;

a third set of codes for causing the computer to detect a failure of the primary server terminal;

a fourth set of codes for causing the computer to process a message received from the ad hoc network backbone at the backup server terminal based on detecting the failure, the message being addressed to the primary server terminal;

first set of codes further comprising at least one code for selecting each route from a plurality of routes depending on whether the inter-cluster call is a first type of call or a second type of call that is different from the first type of call; and

the first set of codes for the establishing of each route further comprising;

at least one code for mapping at least one adjacent ad hoc cluster to the corresponding gateway terminal and the corresponding master terminal; and

at least one code for communicating with the corresponding master terminal associated with the selected one of the plurality of routes via the corresponding gateway terminal to support intra-cluster scheduling and forwarding of the respective communication packet.

50. The computer program product of claim 34, wherein the route on the ad hoc network backbone is configured to pass through a first picocell for the first type of call and configured not to pass through the first picocell for the second type of call.

60. The computer program product of claim 34, wherein the gateway terminal of one of the plurality of clusters is configured to form a direct communications link with another gateway terminal of a different one of the plurality of clusters, and wherein the intra-cluster bridge terminal of one of the two piconets is configured to form a direct communications link with another intra-cluster bridge terminal of a different one of the two piconets.

35. An apparatus for communications to serve a plurality of terminals in an ad hoc cluster, comprising:

means for using a primary server terminal to support a plurality of inter-cluster calls for a number of the terminals in the ad hoc cluster including means for establishing a route on an ad hoc network backbone of an ad hoc network for each of the communication packets transmitted by each of the terminals to a corresponding other ad hoc cluster, the ad hoc network comprising a plurality of clusters, each of the clusters comprising at least two piconets and at least one gateway terminal, each gateway terminal configured to form a communications link between at least two of the plurality of clusters, each of the piconets comprising at least one intra-cluster bridge terminal, a master terminal, and a member terminal slaved to the master terminal, and the intra-cluster bridge terminal being a member of the two piconets and configured to form a communications link between the two piconets;

means for dynamically designating one of the terminals in the ad hoc cluster as a backup server terminal in accordance with an ad hoc protocol;

means for detecting a failure of the primary server terminal;

means for processing a message received from the ad hoc network backbone at the backup server terminal based on detecting the failure, the message being addressed to the primary server terminal; and

the means for establishing of each route further comprising;

means for selecting each route from a plurality of routes depending on whether the inter-cluster call is a first type of call or a second type of call that is different from the first type of call;

means for mapping at least one adjacent ad hoc cluster to the corresponding gateway terminal and the corresponding master terminal; and

means for communicating with the corresponding master terminal associated with the selected one of the plurality of routes via the corresponding gateway terminal to support intra-cluster scheduling and forwarding of the respective communication packet.

51. The apparatus of claim 35, wherein the route on the ad hoc network backbone is configured to pass through a first picocell for the first type of call and configured not to pass through the first picocell for the second type of call.

61. The apparatus of claim 35, wherein the respective gateway terminal of one of the plurality of clusters is configured to form a direct communications link with another gateway terminal of a different one of the plurality of clusters, and wherein the respective intra-cluster bridge terminal of one of the two piconets is configured to form a direct communications link with another intra-cluster bridge terminal of a different one of the two piconets.

36. A terminal system for communications, comprising:

a primary server terminal used to support a plurality of inter-cluster calls for a number of the terminals in the ad hoc cluster by establishing a route on an ad hoc network backbone of an ad hoc network for each of the communication packets transmitted by each of the terminals to a corresponding other ad hoc cluster, the ad hoc network comprising a plurality of clusters, each of the clusters comprising at least two piconets and at least one gateway terminal, each gateway terminal configured to form a communications link between at least two of the plurality of clusters, each of the piconets comprising at least one intra-cluster bridge terminal, a master terminal, and a member terminal slaved to the master terminal, and the intra-cluster bridge terminal being a member of the two piconets and configured to form a communications link between the two piconets;

a processor for dynamically designating one of the terminals in the ad hoc cluster as a backup server terminal in accordance with an ad hoc protocol, for detecting a failure of the primary server terminal, and for processing a message received from the ad hoc network backbone at the backup server terminal based on detecting the failure, the message being addressed to the primary server terminal, each route selected from a plurality of routes depending on whether the inter-cluster call is a first type of call or a second type of call that is different from the first type of call;

the establishing of each route further comprising;

mapping at least one adjacent ad hoc cluster to the corresponding gateway terminal and the corresponding master terminal; and

communicating with the corresponding master terminal associated with the selected one of the plurality of routes via the corresponding gateway terminal to support intra-cluster scheduling and forwarding of the respective communication packet.

52. The terminal system of claim 36, wherein the route on the ad hoc network backbone is configured to pass through a first picocell for the first type of call and configured not to pass through the first picocell for the second type of call.

62. The terminal system of claim 36, wherein the respective gateway terminal of one of the plurality of clusters is configured to form a direct communications link with another gateway terminal of a different one of the plurality of clusters, and wherein the respective intra-cluster bridge terminal of one of the two piconets is configured to form a direct communications link with another intra-cluster bridge terminal of a different one of the two piconets.