Handoff at an ad-hoc mobile service provider

• US 9,392,445 B2
• Filed: 08/08/2008
• Issued: 07/12/2016
• Est. Priority Date: 08/17/2007
• Status: Expired due to Fees

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Krishnaswamy, Dilip
• Primary Examiner(s): Skripnikov, Alex
• Application Number:
  US12/188,990
• Publication Number:
  US 20090046658A1
• Time in Patent Office: 2,895 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04W 12/04 Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/062 Pre-authentication
• CPC Class Codes: H04W 36/0038 of security context information
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

An ad-hoc service provider is configured to support pre-authentication with a server for the purpose of receiving a handoff of a mobile client from another ad-hoc service provider. The ad-hoc service provider is further configured to enable the mobile client to maintain a session with the server while receiving the handoff from said another ad-hoc service provider.

Claims

1. A mobile ad-hoc service provider, comprising:

a processing system comprising a processor, the processing system being configured to support pre-authentication of the mobile ad-hoc service provider with a server using information received at the server via a tunnel through another ad-hoc service provider, the pre-authentication for the purpose of receiving a handoff of a mobile client from the another ad-hoc service provider, the processing system being further configured to enable the mobile client to maintain a session with the server while receiving the handoff from said another ad-hoc service provider, the processing system being configured to maintain a wireless link between the another ad-hoc service provider and the ad-hoc service provider for receiving data packets routed to the another ad-hoc service provider for the mobile client during the handoff, the processing system being configured to establish a connection with the mobile client to receive the handoff in response to receiving a message encrypted with a key from the mobile client.

2. The mobile ad-hoc service provider of claim 1 wherein the processing system is further configured to support the pre-authentication by receiving the key from the server to support an encrypted link between the mobile ad-hoc service provider and the mobile client.

3. The mobile ad-hoc service provider of claim 1 wherein the processing system is further configured to support the pre-authentication by receiving authorization from the server to communicate with the mobile client.

4. The mobile ad-hoc service provider of claim 1 wherein the processing system is further configured to support the pre-authentication by receiving a key from the server to support an encrypted link between the mobile ad-hoc service provider and said another ad-hoc service provider.

5. The mobile ad-hoc service provider of claim 1 wherein the processing system is further configured to support the pre-authentication by receiving authorization from the server to communicate with said another ad-hoc service provider.

6. The mobile ad-hoc service provider of claim 1 wherein the processing system is further configured to enable the mobile client to maintain the session with the server while receiving the handoff by supporting the tunnel with said another ad-hoc service provider.

7. The mobile ad-hoc service provider of claim 6 wherein the processing system is further configured to receive through the tunnel at least some packets received by said another ad-hoc service provider from the mobile client.

8. The mobile ad-hoc service provider of claim 1 wherein the processing system is further configured to receive one or more of said at least some packets from said another ad-hoc service provider through yet another ad-hoc service provider.

9. The mobile ad-hoc service provider of claim 1 wherein the processing system is further configured to provide an IPv4 or IPv6 address to the mobile client.

10. The mobile ad-hoc service provider of claim 9 wherein the IPv4 or IPv6 address comprises a MobileIP address.

11. The mobile ad-hoc service provider of claim 1 wherein the processing system is further configured to receive from the server a message to receive the handoff of the mobile client from said another ad-hoc service provider.

12. The mobile ad-hoc service provider of claim 1 wherein the processing system is further configured to support a hard handoff.

13. The mobile ad-hoc service provider of claim 1 wherein the processing system is further configured to support a soft handoff.

14. The mobile ad-hoc service provider of claim 1 wherein the processing system is further configured to send a message to the server indicating that the handoff is complete.

15. A method of receiving a handoff at a mobile ad-hoc service provider, comprising:

supporting pre-authentication between the mobile ad-hoc service provider and a server using information received at the server via a tunnel through another ad-hoc service provider, the pre-authentication for the purpose of receiving a handoff of a mobile client from the another ad-hoc service provider;

establishing a connection with the mobile client to receive the handoff in response to receiving a message encrypted with a key from the mobile client;

enabling the mobile client to maintain a session with the server while receiving the handoff from said another ad-hoc service provider; and

maintaining a wireless link between the another ad-hoc service provider and the ad-hoc service provider for receiving data packets routed to the another ad-hoc service provider for the mobile client during the handoff.

16. The method of claim 15 wherein the pre-authentication is supported by receiving the key from the server to support an encrypted link between the mobile ad-hoc service provider and the mobile client.

17. The method of claim 15 wherein the pre-authentication is supported by receiving authorization from the server to communicate with the mobile client.

18. The method of claim 15 wherein the pre-authentication is supported by receiving a key from the server to support an encrypted link between the mobile ad-hoc service provider and said another ad-hoc service provider.

19. The method of claim 15 wherein the pre-authentication is supported by receiving authorization from the server to communicate with said another ad-hoc service provider.

20. The method of claim 15 wherein the mobile client is enabled to maintain the session with the server while receiving the handoff by supporting the tunnel with said another ad-hoc service provider.

21. The method of claim 20 further comprising receiving through the tunnel at least some packets received by said another ad-hoc service provider from the mobile client.

22. The method of claim 15 wherein one or more of said at least some packets received from said another ad-hoc service provider are received through yet another ad-hoc service provider.

23. The method of claim 15 further comprising providing an IPv4 or IPv6 address to the mobile client.

24. The method of claim 15 wherein the IPv4 or IPv6 address comprises a MobileIP address.

25. The method of claim 15 further comprising receiving from the server a message to receive the handoff of the mobile client from said another ad-hoc service provider.

26. The method of claim 15 wherein the handoff comprises a hard handoff.

27. The method of claim 15 wherein the handoff comprises a soft handoff.

28. The method of claim 15 further comprising sending a message to the server indicating that the handoff is complete.

29. A mobile ad-hoc service provider, comprising:

means for supporting pre-authentication between the mobile ad-hoc service provider and a server using information received at the server via a tunnel through another ad hoc service provider, the pre-authentication for the purpose of receiving a handoff of a mobile client from the another ad-hoc service provider;

means for establishing a connection with the mobile client to receive the handoff in response to receiving a message encrypted with a key from the mobile client;

means for enabling the mobile client to maintain a session with the server while receiving the handoff from said another ad-hoc service provider, and

means for maintaining a wireless link between the another ad-hoc service provider and the ad-hoc service provider for receiving data packets routed to the another ad-hoc service provider for the mobile client during the handoff.

30. The mobile ad-hoc service provider of claim 29 further comprising means for receiving through the tunnel at least some packets received by said another ad-hoc service provider from the mobile client.

31. The mobile ad-hoc service provider of claim 29 wherein the means for receiving at least some packets is configured to receive one or more of said at least some packets received from said another ad-hoc service provider through yet another ad-hoc service provider.

32. The mobile ad-hoc service provider of claim 29 further comprising means for providing an IPv4 or IPv6 address to the mobile client.

33. The mobile ad-hoc service provider of claim 32 wherein the IPv4 or IPv6 address comprises a MobileIP address.

34. The mobile ad-hoc service provider of claim 29 further comprising means for receiving from the server a message to receive the handoff of the mobile client from said another ad-hoc service provider.

35. The mobile ad-hoc service provider of claim 29 further comprising means for receiving a hard handoff.

36. The mobile ad-hoc service provider of claim 29 further comprising means for receiving a soft handoff.

37. The mobile ad-hoc service provider of claim 29 further comprising means for sending a message to the server indicating that the handoff is complete.

38. A non-transitory machine-readable medium comprising instructions executable by a processing system in a mobile ad-hoc service provider, the instructions comprising code for:

supporting pre-authentication between the mobile ad-hoc service provider and a server using information received at the server via a tunnel through another ad hoc service provider, the pre-authentication for the purpose of receiving a handoff of a mobile client from the another ad-hoc service provider;

establishing a connection with the mobile client to receive the handoff in response to receiving a message encrypted with a key from the mobile client;

enabling the mobile client to maintain a session with the server while receiving the handoff from said another ad-hoc service provider; and

maintaining a wireless link between the another ad-hoc service provider and the ad-hoc service provider for receiving data packets routed to the another ad-hoc service provider for the mobile client during the handoff.

39. The non-transitory machine-readable medium of claim 38 wherein the code for supporting pre-authentication comprises code for receiving the key from the server to support an encrypted link between the mobile ad-hoc service provider and the mobile client.

40. The non-transitory machine-readable medium of claim 39 wherein the code for supporting pre-authentication comprises code for receiving authorization from the server to communicate with the mobile client.

41. The non-transitory machine-readable medium of claim 38 wherein the code for supporting pre-authentication comprises code for receiving a key from the server to support an encrypted link between the mobile ad-hoc service provider and said another ad-hoc service provider.

42. The non-transitory machine-readable medium of claim 38 wherein the code for supporting pre-authentication comprises code for receiving authorization from the server to communicate with said another ad-hoc service provider.

43. The non-transitory machine-readable medium of claim 38 wherein the code for enabling the mobile client to maintain the session with the server while receiving the handoff comprises code for supporting the tunnel with said another ad-hoc service provider.

44. The non-transitory machine-readable medium of claim 43 wherein the instructions further comprise code for receiving through the tunnel at least some packets received by said another ad-hoc service provider from the mobile client.

45. The non-transitory machine-readable medium of claim 38 wherein the code for receiving at least some packets is configured to receive one or more of said at least some packets received from said another ad-hoc service provider through yet another ad-hoc service provider.

46. The non-transitory machine-readable medium of claim 38 wherein the instructions further comprise code for providing an IPv4 or IPv6 address to the mobile client.

47. The non-transitory machine-readable medium of claim 46 wherein the IPv4 or IPv6 address comprises a MobileIP address.

48. The non-transitory machine-readable medium of claim 38 wherein the instructions further comprise code for receiving from the server a message to receive the handoff of the mobile client from said another ad-hoc service provider.

49. The non-transitory machine-readable medium of claim 38 wherein the instructions further comprise code for receiving a hard handoff.

50. The non-transitory machine-readable medium of claim 38 wherein the instructions further comprise code for receiving a soft handoff.

51. The non-transitory machine-readable medium of claim 38 wherein the instructions further comprise code for sending a message to the server indicating that the handoff is complete.