Network based machine-to-machine system for monitoring

• US 9,882,958 B1
• Filed: 06/23/2014
• Issued: 01/30/2018
• Est. Priority Date: 10/13/2011
• Status: Active Grant

• Current Assignee: Excelfore Corp.
• Original Assignee: Excelfore Corp.
• Inventors: Crosbie, John Edward, Balakrishnan, Anoop, Acharya, Shrikant, Acharya, Shrinath
• Primary Examiner(s): Chan, Wing F
• Assistant Examiner(s): Krishnan, Raji
• Application Number:
  US14/312,261
• Time in Patent Office: 1,317 Days
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 60/00 Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 76/20 Manipulation of established connections
• CPC Class Codes: H04W 76/25 Maintenance of established connections

Abstract

Methods and systems are disclosed for remote monitoring of mobile computing devices. The method and systems can use cloud-type services to monitor the mobile computing devices. The cloud-type services can include a server that is configured to maintain a virtual link between one or more web-based computing devices and the mobile computing devices. So that, even if the mobile computing devices are not communicating with the server, the server can perform one or more actions to maintain the link between the web-based device and the mobile computing device. The cloud-type services can also include a server that authenticates the mobile computing devices, and that sends a link to the mobile computing device if the mobile computing device is authenticated, the link for use by the mobile computing device to connect to a back-end server that is separate from the server.

Claims

1. A cloud server comprising multiple servers, the cloud server comprising:

an authentication server configured to authenticate one or more mobile computing devices, the authentication server comprising;

an authentication memory; and

an authentication processor in communication with the authentication memory, the authentication processor configured to;

receive a request for authentication from a mobile computing device;

determine whether to authenticate the mobile computing device; and

in response to determining to authenticate the mobile computing device;

generate an authentication token, the authentication token having associated therewith a time of expiry of the authentication token;

send a link and the authentication token to the mobile computing device, the link for use by the mobile computing device to connect to a back-end server separate from the authentication server, the authentication token for encrypting information transmitted to the back-end server; and

send the authentication token and the time of expiry to the back-end server,

the back-end server configured to communicate with the mobile computing device in order to establish a virtual link between the one or more mobile computing devices and at least one web client, the back-end server comprising;

a back-end memory; and

a back-end processor in communication with the back-end memory, the back-end processor configured to;

receive a mobile computing device communication encrypted with the authentication token;

determine, based on the time of expiry, whether the authentication token is expired in order to determine whether to communicate with the mobile computing device; and

wherein, responsive to determining that the authentication token has expired, the authentication server further communicates with the mobile computing device in order for the authentication server to authenticate the mobile computing device again so that the mobile computing device communicates with the back-end server or with another back-end server;

a front-end server configured to communicate with the at least one web client; and

a virtual link device configured to provide an appearance that the virtual link between the mobile computing device and the at least one web client is maintained when the mobile computing device reverts to the authentication server in order for the authentication server to authenticate the mobile computing device again in order for the mobile computing device to communicate again with the at least one web client.

2. The cloud server of claim 1, wherein the link comprises a communication link URL.

3. The cloud server of claim 1, wherein the authentication processor is further configured to load balance the back-end server.

4. The cloud server of claim 3, wherein the authentication processor is configured to load balance the back-end server by invoking new server instances when new mobile computing devices connect to the back-end server or by relinquishing server instances when the mobile computing devices drop out of the back-end server.

5. The cloud server of claim 4, wherein the authentication processor is further configured to:

determine whether to disconnect a particular mobile computing device; and

if it is determined to disconnect the particular mobile computing device, send a command to the back-end server to disconnect the particular mobile computing device.

6. The cloud server of claim 1, wherein the one or more mobile computing devices communicate with the back-end server via dedicated links through a cellular network.

7. The cloud server of claim 1, wherein the authentication processor is further configured to:

communicate with the front-end server, the front-end server configured to communicate with a plurality of devices via an Internet.

8. The cloud server of claim 7, wherein the authentication processor is configured to receive a communication from the front-end server in order to be instantiated and initialized by the front-end server.

9. The cloud server of claim 8, wherein the back-end server communicates via cellular communication with the mobile computing device.

10. The cloud server of claim 1, wherein the back-end processor is configured to determine, based on the time of expiry, whether the authentication token is expired in order to determine whether to communicate with the mobile computing device responsive to determining that the authentication token has not been used within a predetermined time.

11. The cloud server of claim 1, wherein the authentication server is configured to send a plurality of links to the mobile computing device of a plurality of respective back-end servers, with each of the plurality of links having an associated authentication token.

12. A method for a cloud server to authenticate one or more mobile computing devices and to communicate with the one or more mobile computing devices, the method comprising:

receiving, by an authentication server, a request for authentication from a mobile computing device;

determining, by the authentication server, whether to authenticate the mobile computing device; and

in response to determining to authenticate the mobile computing device;

generating, by the authentication server, an authentication token, the authentication token having associated therewith a time of expiry of the authentication token;

sending, by the authentication server, a link and the authentication token to the mobile computing device, the link for use by the mobile computing device to connect to a back-end server separate from the authentication server, the authentication token for encrypting information transmitted to the back-end server; and

sending, by the authentication server, the authentication token and the time of expiry to the back-end server,

receiving, by the back-end server, a mobile computing device communication encrypted with the authentication token, the back-end server configured to establish a virtual link between the mobile computing devices and at least one web client; and

determining, by the back-end server based on the time of expiry, whether the authentication token is expired in order to determine whether to communicate with the mobile computing device,

wherein, responsive to determining that the authentication token has expired, the authentication server further communicates with the mobile computing device in order for the authentication server to authenticate the mobile computing device again so that the mobile computing device communicates with the back-end server or with another back-end server,

communicating, by a front end server, with the at least one web client; and

providing, by a virtual link device, an appearance that the virtual link between the mobile computing device and the at least one web client is maintained when the mobile computing device reverts to the authentication server in order for the authentication server to authenticate the mobile computing device again in order for the mobile computing device to communicate again with the at least one web client.

13. The method of claim 12, wherein the link comprises a communication link URL.

14. The method of claim 12, further comprising the authentication server load balancing the back-end server.

15. The method of claim 14, wherein load balancing the back-end server comprises invoking new server instances when new mobile computing devices connect to the back-end server or by relinquishing server instances when the mobile computing devices drop out of the back-end server.

16. The method of claim 14, further comprising:

determining whether to disconnect a particular mobile computing device; and

if it is determined to disconnect the particular mobile computing device, sending a command to the back-end server to disconnect the particular mobile computing device.

17. The method of claim 12, further comprising:

communicating, by the authentication server, with a front-end server, the front-end server configured to communicate with a plurality of devices via an Internet.

18. The method of claim 17, wherein communicating with the front-end server comprises receiving a communication from the front-end server in order to be instantiated and initialized by the front-end server.