Mobile mesh Ad-Hoc networking

• US 7,649,872 B2
• Filed: 02/03/2005
• Issued: 01/19/2010
• Est. Priority Date: 06/24/2002
• Status: Active Grant

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Mustonen, Kai, Karkkainen, Tero, Lindstrom, Tapio, Naghian, Siamak, Makinen, Jarmo, Lahetkangas, Keijo
• Primary Examiner(s): HSU, ALPUS
• Application Number:
  US11/051,428
• Publication Number:
  US 20050153725A1
• Time in Patent Office: 1,811 Days
• Field of Search: 370/338, 370/352, 370/401, 455/406, 455/411, 455/426.1, 455/426.2
• US Class Current: 370/338
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

An architectural solution in which standalone ad-hoc network cells are used as an extension of the backbone infrastructure in terms of network architecture or/and its service capabilities is provided. These Ad-Hoc networks will integrate to the Internet via cellular and other access networks. This integration brings new possibilities to network operators and ISP'"'"'s. In its extended architecture, it is envisaged that the mobility issues are handled by utilizing the IP mobility capabilities, taking into account the mobile mesh Ad-Hoc specific requirements. A trunk node is elected from among nodes within a service area of an Ad-Hoc domain that underlies an access domain. The trunk node acts as a gateway between the nodes within the Ad-Hoc domain and a backbone access network. The election can be performed by the trunk node itself or by a radio resource management entity.

Claims

1. An apparatus, comprising:

a processor configured to elect a trunk node from among nodes within a service area of an ad-hoc domain that underlies an access domain and that is configured to provide wireless communication for the nodes within the service area,

wherein the trunk node acts as a gateway between the nodes within the ad-hoc domain and a backbone access network.

2. The apparatus of claim 1, wherein the backbone access network is selected from a wired entity and a wireless entity.

3. The apparatus of claim 1, wherein the trunk node is elected from a set of criteria, wherein the set of criteria comprises location coordinates, movement characteristics of the nodes, a number of hops, a handover capability, a service profile, service availability, a quality of service, a power level, routing metrics, an accounting and billing policy, and an identifier.

4. The apparatus of claim 1, wherein the processor is configured to perform at least one of an accounting operation and a billing operation.

5. The apparatus of claim 1, wherein the processor is configured to perform an authentication operation.

6. The apparatus of claim 5, wherein the authentication operation authorizes the trunk node to join the nodes within the ad-hoc domain to at least one of the backbone access network and an ad-hoc sub network of nodes.

7. The apparatus of claim 5, wherein the authentication operation is selected from a set of operations comprising an operation for providing authentication signaling, an operation for providing authentication, an operation for encryption/decryption and integrity check keys arrangement, and an operation for generating random parameters used in an authentication algorithm.

8. The apparatus of claim 1, wherein the ad-hoc domain comprises a standalone proximity ad-hoc network.

9. The apparatus of claim 1, wherein the ad-hoc domain is integrated into other networks.

10. The apparatus of claim 1, wherein the backbone access network is an internet infrastructure.

11. The apparatus of claim 1, wherein the access domain includes radio accesses that provide infrastructure oriented radio connection for the nodes.

12. The apparatus of claim 11, wherein the radio accesses include at least one of a mesh network, a wireless local area network, and a cellular network.

13. The apparatus of claim 11, wherein the ad-hoc domain provides peer-to-peer single-hop, multi-hop and multi-branch radio communication, including both infrastructure-less and infrastructure-oriented radio communication for the nodes.

14. The apparatus of claim 11, wherein the ad-hoc domain includes at least one of fixed nodes and mobile nodes.

15. The apparatus of claim 11, wherein the access domain is configured to transfer multi-hop traffic.

16. The apparatus of claim 11, wherein the access domain is configured to support transfer of authentication for an ad-hoc node moving between a single hop and a multihop connection.

17. The apparatus of claim 1, wherein the apparatus further comprises one of the trunk node and a radio resource management entity.

18. A computer readable medium comprising computer executable instructions for controlling a processor to perform a method, the method comprising:

electing a trunk node from among nodes within a service area of an ad-hoc domain that underlies an access domain and that is configured to provide wireless communication for the nodes within the service area,

wherein the trunk node acts as a gateway between the nodes within the Ad-Hoc domain and a backbone access network.

19. A method, comprising:

detecting nodes within a predefined number of hops;

accepting election as a trunk node from among the nodes, which are within a service area of an ad-hoc domain that underlies an access domain and that is configured to provide wireless communication for the nodes within the service area; and

communicating information between the nodes of the ad-hoc domain and a backbone access network.

20. The method of claim 19, wherein the backbone access network is selected from a wired entity and a wireless entity.

21. The method of claim 19, wherein accepting election as the trunk node is based on a set of criteria, wherein the set of criteria comprises location coordinates, movement characteristics of the nodes, a number of hops, a handover capability, a service profile, service availability, a quality of service, a power level, routing metrics, an accounting and billing policy, and an identifier.

22. The method of claim 19, further comprising performing at least one of an accounting operation and a billing operation.

23. The method of claim 19, further comprising performing an authentication operation.

24. The method of claim 23, wherein the authentication operation authorizes the trunk node to join the nodes within the ad-hoc domain to at least one of the backbone access network and an ad-hoc sub network of nodes.

25. The method of claim 23, wherein the authentication operation is selected from a set of operations comprising an operation for providing authentication signaling, an operation for providing authentication, an operation for encryption/decryption and integrity check keys arrangement, and an operation for generating random parameters used in an authentication algorithm.

26. The method of claim 19, wherein the ad-hoc domain comprises a standalone proximity ad-hoc network.

27. The method of claim 19, wherein the ad-hoc domain is integrated into other networks.

28. The method of claim 19, wherein the backbone access network is an internet infrastructure.

29. The method of claim 19, wherein the access domain includes radio accesses that provide infrastructure oriented radio connection for the nodes.

30. The method of claim 29, wherein the radio accesses include at least one of a mesh network, a wireless local area network, and a cellular network.

31. The method of claim 29, wherein the ad-hoc domain provides peer-to-peer single-hop, multi-hop and multi-branch radio communication, including both infrastructure-less and infrastructure-oriented radio communication for the nodes.

32. The method of claim 29, wherein the ad-hoc domain includes at least one of fixed nodes and mobile nodes.

33. The method of claim 29, wherein the access domain is configured to transfer multi-hop traffic.

34. The method of claim 29, wherein the access domain is configured to support transfer of authentication for an ad-hoc node moving between a single hop and a multihop connection.

35. The method of claim 19, wherein election of the trunk node is performed by one of the trunk node and a radio resource management entity.

36. A computer readable medium comprising computer executable instructions for controlling a processor to implement a method, the method comprising:

detecting nodes within a predefined number of hops;

accepting election as a trunk node from among the nodes, which are within a service area of an ad-hoc domain that underlies an access domain and that is configured to provide wireless communication for the nodes within the service area; and

communicating information between the nodes of the ad-hoc domain and a backbone access network.

37. A method, comprising:

establishing communication with nodes within a service area of an ad-hoc domain that underlies an access domain and that is configured to provide wireless communication for the nodes within the service area; and

providing election parameters for electing a trunk node from among the nodes, wherein the trunk node acts as a gateway between the nodes within the ad hoc domain and a backbone access network.

38. The method of claim 37, further comprising electing the trunk node from among the nodes.

39. The method of claim 37, further comprising communicating information between the trunk node and a backbone access network.

40. The method of claim 37, wherein the backbone access network is selected from a wired entity and a wireless entity.

41. The method of claim 37, wherein the election parameters comprise at least one of location coordinates, movement characteristics of the nodes, a number of hops, a handover capability, a service profile, service availability, a quality of service, a power level, routing metrics, an accounting and billing policy, and an identifier.

42. The method of claim 37, further comprising providing information to a computing device that performs at least one of an accounting operation and a billing operation.

43. The method of claim 37, further comprising providing information to a computing device that performs an authentication operation.

44. The method of claim 43, wherein the authentication operation authorizes the trunk node to join the nodes within the ad-hoc domain to at least one of the backbone access network and an ad-hoc sub network of nodes.

45. The method of claim 43, wherein the authentication operation is selected from a set of operations comprising an operation for providing authentication signaling, an operation for providing authentication, an operation for encryption/decryption and integrity check keys arrangement, and an operation for generating random parameters used in an authentication algorithm.

46. The method of claim 37, wherein the ad-hoc domain comprises a standalone proximity ad-hoc network.

47. The method of claim 37, wherein the ad-hoc domain is integrated into other networks.

48. The method of claim 37, wherein the backbone access network is an internet infrastructure.

49. The method of claim 37, wherein the access domain includes radio accesses that provide infrastructure oriented radio connection for the nodes.

50. The method of claim 49, wherein the radio accesses include at least one of a mesh network, a wireless local area network, and a cellular network.

51. The method of claim 49, wherein the ad-hoc domain provides peer-to-peer single-hop, multi-hop and multi-branch radio communication, including both infrastructure-less and infrastructure-oriented radio communication for the nodes.

52. The method of claim 49, wherein the ad-hoc domain includes at least one of fixed nodes and mobile nodes.

53. The method of claim 49, wherein the access domain is configured to transfer multi-hop traffic.

54. The method of claim 49, wherein the access domain is configured to support transfer of authentication for an ad-hoc node moving between a single hop and a multihop connection.

55. The method of claim 37, wherein election of the trunk node is performed by the trunk node.

56. A computer readable medium comprising computer executable instructions for controlling a processor to implement a method, the method comprising:

establishing communication with nodes within a service area of an ad-hoc domain that underlies an access domain and that is configured to provide wireless communication for the nodes within the service area; and

providing election parameters for electing a trunk node from among the nodes, wherein the trunk node acts as a gateway between the nodes within the Ad-Hoc domain and a backbone access network.

57. A method, comprising:

electing a trunk node from among nodes within a service area of an ad-hoc domain that underlies an access domain and that is configured to provision wireless communication for the nodes within the service area; and

configuring the trunk node to act as a gateway between the nodes within the ad-hoc domain and a backbone access network.

58. The method of claim 57, wherein the backbone access network is selected from a wired entity and a wireless entity.

59. An apparatus, comprising:

a detector configured to detect nodes within a predefined number of hops;

an acceptor configured to accept election as a trunk node from among the nodes, which are within a service area of an ad-hoc domain that underlies an access domain and that is configured to provide wireless communication for the nodes within the service area; and

a communicator configured to communicate information between the nodes of the ad-hoc domain and a backbone access network.

60. The apparatus of claim 59, wherein the backbone access network is selected from a wired entity and a wireless entity.

61. An apparatus, comprising:

an establisher configured to establish communication with nodes within a service area of an ad-hoc domain that underlies an access domain and that is configured to provide wireless communication for the nodes within the service area; and

a provider configured to provide election parameters for electing a trunk node from among the nodes, wherein the trunk node acts as a gateway between the nodes within the ad-hoc domain and a backbone access network.

62. The apparatus of claim 61, wherein the trunk node is elected from among the nodes.