Systems and methods for interfacing with a network of moving things

• US 9,521,606 B1
• Filed: 04/14/2016
• Issued: 12/13/2016
• Est. Priority Date: 09/22/2015
• Status: Active Grant

• Current Assignee: Veniam Inc.
• Original Assignee: Veniam Inc.
• Inventors: Costa, Rui, Gomes, Joo
• Primary Examiner(s): Thompson, Jr., Otis L
• Application Number:
  US15/098,542
• Time in Patent Office: 243 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04B 1/3822 specially adapted for use in vehicles H04B1/3827 takes precedence
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04W 12/065 Continuous authentication
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 48/02 Access restriction performed under specific conditions
• CPC Class Codes: H04W 64/003 locating network equipment
• CPC Class Codes: H04W 88/08 Access point devices

Abstract

A request from a mobile access point that is installed on a vehicle may be received via network interface circuitry of one or more computing devices. Processing circuitry of the one or more computing devices may determine characteristics of a captive portal to present in response to the request based on current location of the vehicle and mobile access point. A captive portal with the determined characteristics is then provided by the processing circuitry, via the network interface circuitry, in response to the request.

Claims

1. A method comprising:

receiving, via network interface circuitry of one or more computing devices, a request from a mobile access point that is installed on a vehicle;

determining, by processing circuitry of the one or more computing devices, characteristics of a captive portal to present in response to the request based on current location of the vehicle and mobile access point, wherein the characteristics of the captive portal comprise visual and/or audio content of the captive portal, wherein the visual and/or audio content comprises traffic accounting information for a user device from which the request originated, and wherein the visual and/or audio content of the captive portal is determined based on a predetermined route of the vehicle; and

providing, by the processing circuitry via the network interface circuitry, the captive portal with the determined characteristics in response to the request.

2. The method of claim 1, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on the predetermined route of the vehicle.

3. The method of claim 1, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on a speed of the vehicle.

4. The method of claim 1, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on whether the vehicle is on schedule, behind schedule, or ahead of schedule on its route.

5. The method of claim 1, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on an affiliate associated with the mobile access point.

6. The method of claim 1, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on which of a plurality of network providers associated with the mobile access point provided a backhaul connection to the mobile access point for backhauling the request.

7. The method of claim 1, wherein the characteristics of the captive portal comprise an authentication technique to be used for authenticating a user device on behalf of which the request was sent.

8. The method of claim 7, wherein the authentication technique is selected from a set of techniques including username and password, and oAuth.

9. The method of claim 1, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on characteristics of a user device on behalf of which the request was sent.

10. The method of claim 9, wherein the characteristics of the user device comprise an expected location at which the user device will de-board the vehicle.

11. The method of claim 9, wherein the characteristics of the user device comprise whether the user device transferred from another vehicle within a determined amount of time of the current time.

12. The method of claim 1, comprising:

providing, by the processing circuitry, a plurality of application programming interfaces (APIs) wherein access to each one of the plurality of APIs is controlled separately from access to each other one of the plurality of APIs.

13. The method of claim 12, comprising restricting access to one or more of the plurality of APIs to a user device associated with an operator of the vehicle.

14. A method comprising:

receiving, via network interface circuitry of one or more computing devices, a request from a mobile access point that is installed on a vehicle;

determining, by processing circuitry of the one or more computing devices, characteristics of a captive portal to present in response to the request based on a current location of the vehicle and mobile access point and based on a predetermined route of the vehicle; and

providing, by the processing circuitry via the network interface circuitry, the captive portal with the determined characteristics in response to the request.

15. The method of claim 14, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on a speed of the vehicle.

16. The method of claim 14, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on whether the vehicle is on schedule, behind schedule, or ahead of schedule on its route.

17. The method of claim 14, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on an affiliate associated with the mobile access point.

18. The method of claim 14, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on which of a plurality of network providers associated with the mobile access point provided a backhaul connection to the mobile access point for backhauling the request.

19. The method of claim 14, wherein the characteristics of the captive portal comprise an authentication technique to be used for authenticating a user device on behalf of which the request was sent.

20. The method of claim 19, wherein the authentication technique is selected from a set of techniques including username and password, and oAuth.

21. The method of claim 14, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on characteristics of a user device on behalf of which the request was sent.

22. The method of claim 21, wherein the characteristics of the user device comprise an expected location at which the user device will de-board the vehicle.

23. The method of claim 21, wherein the characteristics of the user device comprise whether the user device transferred from another vehicle within a determined amount of time of the current time.

24. The method of claim 14, comprising:

providing, by the processing circuitry, a plurality of application programming interfaces (APIs) wherein access to each one of the plurality of APIs is controlled separately from access to each other one of the plurality of APIs.

25. The method of claim 24, comprising restricting access to one or more of the plurality of APIs to a user device associated with an operator of the vehicle.

26. A method comprising:

receiving, via network interface circuitry of one or more computing devices, a request from a mobile access point that is installed on a vehicle;

determining, by processing circuitry of the one or more computing devices, characteristics of a captive portal to present in response to the request based on current location of the vehicle and mobile access point and based on whether the vehicle is on schedule, behind schedule, or ahead of schedule on its route; and

providing, by the processing circuitry via the network interface circuitry, the captive portal with the determined characteristics in response to the request.

27. The method of claim 26, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on a speed of the vehicle.

28. The method of claim 26, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on an affiliate associated with the mobile access point.

29. The method of claim 26, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on which of a plurality of network providers associated with the mobile access point provided a backhaul connection to the mobile access point for backhauling the request.

30. The method of claim 26, wherein the characteristics of the captive portal comprise an authentication technique to be used for authenticating a user device on behalf of which the request was sent.

31. The method of claim 26, wherein the authentication technique is selected from a set of techniques including username and password, and oAuth.

32. The method of claim 26, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on characteristics of a user device on behalf of which the request was sent.

33. The method of claim 32, wherein the characteristics of the user device comprise an expected location at which the user device will de-board the vehicle.

34. The method of claim 32, wherein the characteristics of the user device comprise whether the user device transferred from another vehicle within a determined amount of time of the current time.

35. The method of claim 26, comprising:

providing, by the processing circuitry, a plurality of application programming interfaces (APIs) wherein access to each one of the plurality of APIs is controlled separately from access to each other one of the plurality of APIs.

36. The method of claim 35, comprising restricting access to one or more of the plurality of APIs to a user device associated with an operator of the vehicle.

37. A method comprising:

receiving, via network interface circuitry of one or more computing devices, a request from a mobile access point that is installed on a vehicle;

determining, by processing circuitry of the one or more computing devices, characteristics of a captive portal to present in response to the request based on current location of the vehicle and mobile access point and based on characteristics of a user device on behalf of which the request was sent, and wherein the characteristics of the user device comprise an expected location at which the user device will de-board the vehicle; and

providing, by the processing circuitry via the network interface circuitry, the captive portal with the determined characteristics in response to the request.

38. The method of claim 37, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on a speed of the vehicle.

39. The method of claim 37, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on an affiliate associated with the mobile access point.

40. The method of claim 37, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on which of a plurality of network providers associated with the mobile access point provided a backhaul connection to the mobile access point for backhauling the request.

41. The method of claim 37, wherein the characteristics of the captive portal comprise an authentication technique to be used for authenticating a user device on behalf of which the request was sent.

42. The method of claim 41, wherein the authentication technique is selected from a set of techniques including username and password, and oAuth.

43. The method of claim 37, wherein the characteristics of the user device comprise whether the user device transferred from another vehicle within a determined amount of time of the current time.

44. The method of claim 37, comprising:

providing, by the processing circuitry, a plurality of application programming interfaces (APIs) wherein access to each one of the plurality of APIs is controlled separately from access to each other one of the plurality of APIs.

45. The method of claim 44, comprising restricting access to one or more of the plurality of APIs to a user device associated with an operator of the vehicle.

46. A method comprising:

receiving, via network interface circuitry of one or more computing devices, a request from a mobile access point that is installed on a vehicle;

determining, by processing circuitry of the one or more computing devices, characteristics of a captive portal to present in response to the request based on current location of the vehicle and mobile access point and based on characteristics of a user device on behalf of which the request was sent, wherein the characteristics of the user device comprise whether the user device transferred from another vehicle within a determined amount of time of the current time; and

providing, by the processing circuitry via the network interface circuitry, the captive portal with the determined characteristics in response to the request.

47. The method of claim 46, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on a speed of the vehicle.

48. The method of claim 46, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on an affiliate associated with the mobile access point.

49. The method of claim 46, comprising determining, by the processing circuitry of the one or more computing devices, the characteristics of the captive portal based on which of a plurality of network providers associated with the mobile access point provided a backhaul connection to the mobile access point for backhauling the request.

50. The method of claim 46, wherein the characteristics of the captive portal comprise an authentication technique to be used for authenticating a user device on behalf of which the request was sent.

51. The method of claim 50, wherein the authentication technique is selected from a set of techniques including username and password, and oAuth.

52. The method of claim 46, comprising:

providing, by the processing circuitry, a plurality of application programming interfaces (APIs) wherein access to each one of the plurality of APIs is controlled separately from access to each other one of the plurality of APIs.

53. The method of claim 52, comprising restricting access to one or more of the plurality of APIs to a user device associated with an operator of the vehicle.