System and method for verifying and redirecting mobile applications

• US 10,491,590 B2
• Filed: 10/12/2015
• Issued: 11/26/2019
• Est. Priority Date: 10/12/2015
• Status: Active Grant

• Current Assignee: AssetWorks LLC (Constellation Software Incorporated)
• Original Assignee: AssetWorks LLC (Constellation Software Incorporated)
• Inventors: Brickel, Richard
• Primary Examiner(s): King, John B
• Assistant Examiner(s): Dhruv, Darshan I
• Application Number:
  US14/880,478
• Publication Number:
  US 20170104754A1
• Time in Patent Office: 1,506 Days
• CPC Class Codes: H04L 2209/80 Wireless
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04W 12/062 Pre-authentication
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications

Abstract

A system for securely providing a mobile device application on a mobile device access to a fleet operator datacenter for the mobile device application to obtain fleet data therefrom for use by a mobile device user. A verification server facilitates one or more fleet operator datacenters to authenticate a mobile device user, via configurable authentication requirements, before a mobile device user is able to communicate directly with the fleet operator datacenter.

Claims

1. A system for securely providing a mobile device application on a mobile device access to a fleet operator datacenter for the mobile device application to obtain fleet data therefrom for use by a mobile device user, the system comprising:

a verification server, comprising a non-transitory computer readable data storage and a processor, and a verification server uniform resource locator (URL) to facilitate communication therewith, the processor configured to;

provide a fleet operator list, of fleet operators having fleet operator datacenters, one of which is a selected fleet operator the mobile device user would like to gain access to, to a mobile device application on a mobile device in response to a request from the mobile device application for the fleet operator list, wherein the fleet operator list is a subset of all fleet operators known by the verification server, such subset comprising fleet operators using the mobile device application, such subset further based on a geographic location of the mobile device user;

obtain the selected fleet operator from a plurality of fleet operators, from a mobile device user selection on the mobile device;

receive a credential information request from the fleet operator server of the selected fleet operator;

send the credential information request to the mobile device;

communicate the credential information received from the mobile device to the fleet operator server to authenticate the mobile device user; and

when the mobile device user is authenticated, transmit a fleet operator URL of the fleet operator server of the selected fleet operator to the mobile device application to be a mobile device fleet operator URL to which the mobile device application communicates to receive fleet data;

wherein the request was provided by the mobile device to the verification server URL configured in the mobile device application before the mobile device application was downloaded from an app store and installed on the mobile device.

2. The system of claim 1 wherein the credential information request comprises a set of credential information that the selected fleet operator has configured to be required for authenticating a mobile device user.

3. The system of claim 2 wherein the verification server is further configured to receive a first public encryption key from the mobile device and the communicated credential information request is encrypted by the fleet operator server using the first public encryption key before it is received from the fleet operator server.

4. The system of claim 3 wherein the credential information request further comprises a second public encryption key and the communicated credential information is encrypted by the mobile device using the second public encryption key before it is received from the mobile device.

5. The system of claim 4 wherein the communicated credential information received from the mobile device to the fleet operator server is embedded within a signature, and the signature comprises a hash value of the credential information, date and time information and session information.

11. The system of claim 1 wherein one or all fleet operators appearing on the fleet operator list are configured in a way so that they remain anonymous.

6. A system for securely providing a mobile device application on a mobile device access to a fleet operator datacenter for the mobile device application to obtain fleet data therefrom for use by a mobile device user, the system comprising:

a wireless device having computer-executable instructions, on a non-transitory computer readable data storage and executable by a processor, implementing software for;

getting a fleet operator list, of fleet operators having fleet operator datacenters, one of which is a selected fleet operator the mobile device user would like to gain access to, from a verification server, wherein the fleet operator list is a subset of all fleet operators known by the verification server, such subset comprising fleet operators using the mobile device application, such subset further based on a geographic location of the mobile device user;

selecting the fleet operator from a plurality of fleet operators on the fleet operator list and communicating the selected fleet operator to the verification server via a verification server uniform resource locator;

receiving, from the verification server, a credential information request obtained by the verification server from a fleet operator server of the selected fleet operator;

enabling inputting and sending of credential information, from a mobile device user, responsive to the credential information request, to a verification server via a verification server uniform resource locator (URL) to send to the fleet operator server of the selected fleet operator to authenticate the mobile device user; and

when the mobile device user is authenticated, obtaining, from the fleet operator server via the verification server, a uniform resource locator of the fleet operator server of the selected fleet operator to be a mobile device fleet operator URL to which the mobile device application communicates to receive fleet data,

wherein the mobile device further comprises the verification server URL, to facilitate communication with the verification server, configured in the mobile device application before the mobile device application was downloaded from an app store and installed on the mobile device.

7. The system of claim 6 wherein the credential information request comprises a set of credential information that the selected fleet operator has configured to be required for authenticating a mobile device user.

8. The system of claim 7 wherein the credential information request further comprises a public encryption key and the communicated credential information is encrypted by the mobile device using the public encryption key before it is sent by the mobile device.

9. The system of claim 8 wherein the credential information sent by the mobile device is embedded within a signature, and the signature comprises a hash value of the credential information, date and time information and session information.

10. The system of claim 7 wherein the credential information request is encrypted and can only be decrypted by the mobile device application.

12. The system of claim 6 wherein one or all fleet operators appearing on the fleet operator list are configured in a way so that they remain anonymous.