US20100242097A1

US20100242097A1 - System and method for managing application program access to a protected resource residing on a mobile device

Info

Publication number: US20100242097A1
Application number: US12/728,174
Authority: US
Inventors: Scott Hotes; Tasos Roumeliotis; David Blackston
Original assignee: Wavemarket Inc
Current assignee: Smith Micro Software LLC
Priority date: 2009-03-20
Filing date: 2010-03-19
Publication date: 2010-09-23
Also published as: US9542540B2; US20150154389A1

Abstract

A computer-implemented method for managing application program access to a protected resource residing on a mobile device is provided. The method includes receiving from an application program a request for a permission to access the protected resource, and receiving from a source external to the mobile device an authentication of the application program. An authorization to provide the permission to access the protected resource is received and permission to access the protected resource is provided to the application program in response to receiving the authorization. Data produced by the protected resource is cryptographically signed, and a notification is generated in response to at least one of the application program requesting the permission to access the protected resource and the application program accessing the protected resource. A system for managing application program access to a protected resource residing on a mobile device is further provided.

Description

CROSS REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit of U.S. Provisional Application No. 61/161,879, filed Mar. 20, 2009, which is incorporated by reference as if fully set forth.

BACKGROUND

As telecommunication carriers continue to invest in location infrastructure, a proliferation of location-based services is developing ranging from consumer services such as local search and mobile social networking to enterprise services such as fleet management and asset tracking.
The location of a mobile device is typically considered a high-value asset. Accordingly, it would be desirable to protect the process of initiating a location fix of a mobile device, receiving the location details, and disseminating this information. This process typically begins with accessing an API within the device execution environment or operating system, which in turn accesses hardware location determining resources on the device. Hardware location determining resources typically include a dedicated chipset, for example a dedicated GPS/A-GPS chipset, or a part of a multi-function chipset.
Further, it would be desirable to protect other resources available on a mobile device. A data store including contents of user's address book, contents of a user's contact list, or contents of a user's electronic message inbox, such an SMS or MMS inbox, for example, are often considered private or confidential by a user and necessary to be protected from unauthorized access.

SUMMARY

The invention provides a computer-implemented method for managing application program access to a protected resource residing on a mobile device. The method includes receiving from an application program a request for a permission to access the protected resource, and receiving from a source external to the mobile device an authentication of the application program. An authorization to provide the permission to access the protected resource is received and permission to access the protected resource is provided to the application program in response to receiving the authorization.
The invention further provides a computer-implemented method for managing application program access to a protected resource residing on a mobile device, wherein the method includes providing the mobile device with a module separating an application program interface (API) layer for enabling an application program from a protected resource layer, comprising the protected resource, on the mobile device. A remote server remote to the mobile device is configured for connection to the mobile device via a network. The secure resource module receives from the application program via the API layer a request for a permission to access the protected resource. An authentication is transmitted with the remote server to the mobile device. The module receives from the remote server the authentication of the application program. The module receives from at least one of the remote server and a user an authorization to provide the permission for the application program to access the protected resource. The module provides to the application program the permission to access the protected resource in response to receiving the authorization.
The invention further provides a system for managing application program access to a protected resource residing on a mobile device comprising at least one computing device including at least one memory comprising instructions operable to enable the computing device to perform a procedure. The procedure includes receiving from an application program a request for a permission to access the protected resource, and receiving from a source external to the mobile device an authentication of the application program. An authorization to provide the permission to access the protected resource is received and permission to access the protected resource is provided to the application program in response to receiving the authorization.
The invention further provides computer-readable media tangibly embodying a program of instructions executable by a computing device to implement a method, the computing device being capable of interfacing with a communications network. The method includes receiving from an application program a request for a permission to access the protected resource, and receiving from a source external to the mobile device an authentication of the application program. An authorization to provide the permission to access the protected resource is received and permission to access the protected resource is provided to the application program in response to receiving the authorization.

BRIEF DESCRIPTION OF THE DRAWING(S)

The foregoing Summary as well as the following detailed description will be readily understood in conjunction with the appended drawings which illustrate preferred embodiments of the invention. In the drawings:

FIG. 1 is a schematic illustration of an exemplary operating environment in which a system for managing application program access to a protected resource residing on a mobile device according to a preferred embodiment of the invention is operable.

FIG. 2 is a flow chart showing a computer-implemented method for managing application program access to a protected resource residing on a mobile device according to a preferred embodiment of the invention.

FIG. 3 is a workflow diagram showing interactions of an authorization procedure between a remote authentication server application program interface (API) layer and a secure resource module according to a preferred embodiment of the invention.

FIG. 4 is a workflow diagram showing interactions of an authorization procedure between a remote authentication server application program interface (API) layer and a secure resource module according to a preferred embodiment of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

The preferred embodiments of the present invention are described below with reference to the drawing figures in which like numerals represent like elements throughout.
Referring to FIG. 1, a schematic illustration of an exemplary operating environment 10 is shown in which a mobile device 12 operates. The mobile device 12 includes a preferred system in the form of a secure resource module 20 for managing access of application programs 14 to one or more protected resources 24 residing on the mobile device 12. The mobile device 12 includes one or more computing devices and one or more memory devices, which computing devices and memory devices may be integrally constructed or connected in any suitable manner. The mobile device 12 provides a platform which enables an application program interface (API) layer 16, a privacy management layer, and a protected resource layer 22. The secure resource module 20, a secure log file 26, and a secure key store 28 are preferably incorporated in the privacy management layer 18. One or more protected resources 24 are preferably incorporated in the protected resource layer 22. The privacy management layer 18 is preferably a dedicated layer within the firmware or hardware of the mobile device 12. The protected resource layer 22 is preferably another dedicated layer within the firmware or hardware of the mobile device 20. The privacy management layer 18 is preferably configured to perform at least two important functions. First, access to a protected resource 24 results in the generation of a notification, and second, access to a protected resource 24 is controlled via the secure resource module 20.
The protected resources 24 include resources which generate or store information which can be deemed personal or private by a user, a telecommunication carrier, or other interested party. In a preferred embodiment, a protected resource 24 can include a resource for producing location data. Such a location resource can include a dedicated GPS location determining chipset or a multi-function chipset enabled for GPS location determination installed on the mobile device 12. Alternatively, a protected resource 24 can include a data store including contents of user's address book, contents of a user's contact list, or contents of a user's electronic message inbox, such an SMS or MMS inbox. Alternatively, the protected resource can include any resource deemed personal or private.
The secure resource module 20 can be installed on the mobile device 12 as one or more of a software, firmware or hardware module during manufacturer of the mobile device 12. Alternatively, the secure resource module 20 can be installed and or upgraded by a user as one or more of a software, firmware or hardware module, for example as a software or firmware module transmitted via a network accessible server such as a remote authentication server 40 over the Internet 60. The secure resource module 20 separates the API layer 16 from the protected resource layer 22. The secure resource module 20 can be configured for interface with one or both of a local resident application program 14 and a remote network-accessible application program 14 executed by a remote application server 50 via the API layer 16. Alternatively, the secure resource module 20 can be configured for interface with application program logic within the operating system of the mobile device 12.
The secure resource module 20 is configured to receive from an application program 14 via the API layer 16 a request for a permission to access the protected resource 24. The secure resource module 20 is preferably configured to receive an authentication of the application program 14 from a source external to the mobile device 12. Preferably, a remote authentication server 40 is provided for authenticating the application program 14. The remote authentication server 40 includes an authentication module 42 for performing authentication of the application program 14 and an API layer 44 which provides an interface between the secure resource module 20 and the authentication module 42. The authentication is preferably transmitted in the form of a cryptographically secure request token by the remote authentication server 40. The request token is received by the secure resource module 20 via an API functioning out of the API Layer 44 enabled by the remote authentication server 40.
The secure resource module 20 is further configured to receive an authorization to provide a permission to access the protected resource 24. The authorization is preferably cryptographically secure and digitally signed. The secure resource module 20 can receive the authorization in the form of a cryptographically secure digitally signed request, wherein the secure resource module 20 verifies the cryptographically secure digitally signed request. The authorization is preferably transmitted by the remote authentication server 40 and received by the secure resource module 20 via an API functioning out of the API Layer 44 enabled by the remote authentication server 40 in the form of a cryptographically secure access token. The authorization can be transmitted as a response to a password or other authenticating data entered or otherwise provided through the mobile device 12 by a user via the secure resource module 20, and transmitted to the authentication module 42 via the API Layer 44 enabled by the remote authentication server 40.
The secure resource module 20 is configured to provide the application program 14 the permission to access the protected resource 24 in response to receiving the authorization. The secure resource module 20 is further configured to sign data produced by the protected resource 24 to assure authenticity of the data provided to and used by the application program 14. The mobile device 12 is preferably provided with a cryptographically secure key store 28 enabled by the privacy management layer 18. The secure resource module 20 accesses the cryptographically secure key store 28 to obtain a key for cryptographically signing data produced by the protected resource 24.
The secure resource module 20 is configured to generate a notification in response to one or both of the application program 14 requesting the permission to access the protected resource 24 and the application program 14 accessing the protected resource 24. The notification informs a user of the mobile device 12 or a remote user monitoring the activity of the mobile device 12 when an application program 14 requests access to a protected resource 24 on the mobile device 12, or alternatively, when the application program 14 actually accesses the protected resource 24. The notification can be provided with a user-query to permit a user to provide an authorization or a portion of an authorization to provide a permission to the application program 14 to access the protected resource 24. Alternatively, the notification can merely notify the user of the request for permission to access the protected resource 24 or the actual access, as in a case where the authorization was provided solely by another source such as the remote authentication server 40, or as in a case where the authorization was previously provided by the user. The secure resource module 20 can transmit the notification in the form of one or more of a Short Message Service (SMS), a Multimedia Messaging Service (MMS), and an electronic mail. A cryptographically secure log file 26 is preferably provided enabled by the privacy management layer 18. The secure module 20 can further transmit the notification in the form of an addition to the cryptographically secure log file 26 stored on the mobile device 12.
Referring to FIG. 2, a computer-implemented method 100 for managing application program access to a protected resource residing on a mobile device is shown. The process 100 is preferably performed via the secure resource module 20 of FIG. 1. The process 100 may alternatively be performed via any suitable system. In the process 100, a request for a permission to access a protected resource is received from an application program (step 102). An authentication of the application program is received from a source external to the mobile device (step 104). An authorization to provide the permission to access the protected resource is received (step 106). Permission to access the protected resource is provided to the application program in response to receiving the authorization (step 108), and data produced by the protected resource is cryptographically signed (step 110). A notification is generated in response to at least one of the application program requesting the permission to access the protected resource and the application program accessing the protected resource (step 112).
The authentication module 42 is preferably configured to establish a user account using identifying information of a user. The remote authentication server 40 is configured to receive the identifying information through the API layer 44 from the mobile device 12 via the secure resource module 20, via a network connection, which network connection is preferably an Internet network connection 60. The identifying information preferably includes at least the name of the user, a telephone number associated with a user's mobile device, and a telecommunication carrier identifier associated with the user's mobile device used to establish a connection with the telecommunication carrier. The API layer 44 preferably provides an interface through a client application running on the mobile device 12, which client application is preferably a web client, WAP client, Java ME™ client, BREW™ client, SMS client or other suitable client. The remote authentication server 40 associates a user identifier, which is preferably randomly generated, with the user account. The remote authentication server 40 is preferably configured to receive from an executed application program 14 via the secure resource module 20 through the API layer 44 a request for the user identifier of the user.
The remote authentication server 40 is configured to receive via the API layer 44 an identifier request authorization, which, depending on the application program 14 and the preference of the user, is received from either user input or automatically from the application program 14 via the secure resource module 20. In the case where authorization is provided automatically via the application program 14, the identifier request authorization is preferably provided in the form of an element of known personal information from the user including but not limited to one or more of an email address, a physical address, and a telephone number associated with the mobile device 12. The remote authentication server 40 is configured to provide via the API layer 44 the user identifier to the application program 14 via the secure resource module 20 in response to receiving the identifier request authorization.
The remote authentication server 40 is preferably configured to receive from the secure resource module 20 through the API layer 44 a request for an authorization to provide an application program 14 permission to access the protected resource 24 of the user mobile device 12 associated with the pre-determined user identifier. Prior to providing the authorization to provide permission to access the protected resource 24, an authorization is preferably received by the remote authentication server 40 from a user via the mobile device 12 or other suitable client. The authorization of the user can take the form of a password, a digitally signed request, or other secure authorization protocol. The remote authentication server 40 is configured to provide the authorization to provide permission to access the protected resource 24 to the secure resource module 20 in response to receiving such authorization from the user, or alternatively, other suitable source. Preferably, if an authorization is not provided by a user or other source, no authorization to provide permission to access the protected resource 24 is provided by the remote authentication server 40 to the secure resource module 20. Depending on preference of the user, the authorization can be provided to the secure resource module 20 from the remote authentication server 40 as an authorization to provide permission to access the mobile device information one time, a predetermined number of times, for a specified time interval, until the authorization is revoked, or until any predetermined condition is met. The authorization is preferably received by the secure resource module 20 via the API layer 44 of the remote authentication server 40.
Referring to FIG. 3, a workflow 200 of an authorization procedure for providing a user identifier implemented by the secure resource module 20 and the remote authentication server 40 via the authentication module 42 and the API layer 44 according to a preferred embodiment of the present invention is shown. The application program 14 via the secure resource module 20 directs a request for a request token (step 202) through a request token URL 204 provided by the authentication module 42 via the API layer 44. The remote authentication server 40, via the authentication module 42, creates a request token (step 206) which is provided to the secure resource module 20 in response to the application program's request. If required by a user or a user's telecommunication carrier, or if necessitated by a particular application, a user agent is redirected by the secure resource module 20 to the remote authentication server 40 (step 208) through a user authorization URL 210 provided via the API layer 44 which implements a suitable web interface or other interface to permit the user to enter a required authorization. The remote authentication server 40, via the API layer 44 preferably authenticates the user, shows the user the user's privacy settings, receives the identifier request authorization from the user, and redirects the user agent back to the secure resource module 20 (step 212). The secure resource module 20 receives the redirected user agent (step 214) and provides the request token, as associated with the identifier request authorization from the user, to the remote authentication server 40 through an access token URL 218 provided by the authentication module 42 (step 216). The remote authentication server 40 provides an access token to the secure resource module 20 in exchange for receiving the authorized request token (step 220). The secure resource module 20 saves the access token and presents the access token to the remote authentication server 40 (step 222) through an identity URL 224, and the remote authentication server 40 provides the user identifier to the application program 14 via the secure resource module 20 in response to receiving the access token (step 226). The access token is preferably revoked immediately or within a predetermined time period after the user identifier is provided to the third party application program. The secure resource module 20 is preferably configured to securely store the request and access tokens such that they are not directly accessible by the application program 14.
In the case where user authorization is not required as a prerequisite for providing the user identifier to the third party application program, for example in instances where a user has already provided identifying information to the application program 14, steps 202, 206, 208, 212, 214, 216 and 220 are omitted. In such case, the application program 14 via the secure resource module 20 preferably provides an application-specific access token in the step 222 which includes identifying information previously provided to the application program 14 by the user in order to retrieve the user's user identifier. Alternatively, in cases where a user identifier is not applicable, the authorization procedure shown by the workflow 200 can be omitted entirely.
Referring to FIG. 4, a workflow 300 of an authorization procedure for authorizing access to a protected resource 24, implemented by the secure resource module 20 and the remote authentication server 40 via the authentication module 42 and the API layer 44 according to a preferred embodiment of the present invention is shown. The application program 14 via the secure resource module 20 directs a request for a request token (step 302), including the user identifier if a user identifier is applicable, through a request token URL 304 provided by the authentication module 42 via the API layer 44. The remote authentication server 40, via the authentication module 42 creates a request token (step 306) which is provided to the secure resource module 20 in response to the application program's request. If a user authorization is required, the user agent is redirected by the secure resource module 20 to the remote authentication server 40 (step 308) through a user authorization URL 310 provided via the API layer 44 which implements a suitable web interface or other consent user interface (UI) to permit the user to enter required authorization. The remote authentication server 40, via the authentication module 42 and the API layer 44 preferably authenticates the user and the application program, shows the user the user's privacy settings, receives the protected resource authorization from the user, and redirects the user agent back to the secure resource module (step 312). Alternatively, the application program can be authenticated without authenticating a user, and further, the application program can be authenticated without a user authorization and redirection of a user agent. The secure resource module 20 receives the redirected user agent (step 314) and provides the request token to the remote authentication server 40 through an access token URL 318 provided by the authentication module 42 via the API layer 44 (step 316). The remote authentication server 40 provides an access token to the secure resource module 20 in exchange for receiving the authorized request token (step 320). The secure resource module 20 saves the access token and presents the access token to the remote authentication server 40 (step 322) through a secure resource URL 324. The remote authentication server 40 provides the secure resource module 20 the authorization to provide a permission to the application program 14 to access the protected resource 24 in response to receiving the access token (step 326). The access token is preferably revoked immediately or within a predetermined time period after the authorization to provide permission to the application program 14 to access the protected resource 24 is provided. The secure resource module 20 is preferably configured to securely store the request and access tokens such that they are not directly accessible by the application program 14.
In communicating with the remote authentication server 40, the secure resource module 20 is preferably configured to use the access token to check for existing authorizations, and the remote authentication server 40 is preferably configured to notify the secure resource module 20 of the existing authorizations, from prior user authorizations stored by the remote authentication server 40. If there are no existing authorizations, the secure resource module 20 preferably prompts a user for authorization. If existing authorizations exist, the secure resource module 20 preferably updates the authorization status including the authorization access history stored on the remote authentication server 40. The secure resource module 20 is preferably configured to use the access token to manage authorizations on the remote authentication server 40 for a particular combination of user and application program 14. The secure resource module 20 can be additionally configured to use the access token in a process of submitting data generated and stored on the user mobile device to the remote authentication server 40.
While the preferred embodiments of the invention have been described in detail above, the invention is not limited to the specific embodiments described above, which should be considered as merely exemplary. Further modifications and extensions of the present invention may be developed, and all such modifications are deemed to be within the scope of the present invention as defined by the appended claims.

Claims

1. A computer-implemented method for managing application program access to a protected resource residing on a mobile device, the method comprising:

receiving from an application program a request for a permission to access the protected resource;

receiving from a source external to the mobile device an authentication of the application program;

receiving an authorization to provide the permission to access the protected resource; and

providing the permission to access the protected resource to the application program in response to receiving the authorization.

2. The method of claim 1, wherein receiving the authorization comprises receiving a cryptographically secure access token via an API.

3. The method of claim 1, wherein receiving the authorization comprises receiving a password and receiving a cryptographically secure access token via an API after receiving the password.

4. The method of claim 1, wherein receiving the request for the permission to access the protected resource comprises receiving a request for a permission to access a resource for producing location data.

5. The method of claim 1, wherein receiving the request for the permission to access the protected resource comprises receiving a request for a permission to access at least one of a dedicated GPS location determining chipset and a multi-function chipset enabled for GPS location determination.

6. The method of claim 1, wherein receiving the request for the permission to access the protected resource comprises receiving a request for a permission to access at least one of contents of an address book of the mobile device, contents of a contact list of the mobile device, and contents of an SMS inbox of the mobile device.

7. The method of claim 1, wherein receiving the authentication from the source external to the mobile device comprises receiving a cryptographically secure request token via an API.

8. The method of claim 1, further comprising:

cryptographically signing data produced by the protected resource; and

generating a notification in response to at least one of the application program requesting the permission to access the protected resource and the application program accessing the protected resource.

9. The method of claim 8, further comprising transmitting the notification in the form of at least one of an SMS, an MMS, and an electronic mail.

10. The method of claim 8, further comprising transmitting the notification in the form of an addition to a cryptographically secure log file stored on the mobile device.

11. The method of claim 8, further comprising providing the device with a cryptographically secure key store, wherein cryptographically signing data produced by the protected resource comprises accessing the cryptographically secure key store.

12. The method of claim 8, further comprising providing the device with a device-unique cryptographically secure key store, wherein cryptographically signing data produced by the protected resource comprises accessing the device-unique cryptographically secure key store.

13. The method of claim 1, wherein receiving the authorization comprises receiving a password.

14. The method of claim 1, wherein receiving the authorization comprises receiving a cryptographically secure digitally signed request, and wherein the method further comprises verifying the cryptographically secure digitally signed request.

15. A computer-implemented method for managing application program access to a protected resource residing on a mobile device, the method comprising:

providing the mobile device with a module separating an application program interface (API) layer for enabling an application program from a protected resource layer, comprising the protected resource, on the mobile device;

providing a remote server remote to the mobile device configured for connection to the mobile device via a network;

receiving with the secure resource module from the application program via the API layer a request for a permission to access the protected resource;

transmitting an authentication with the remote server to the mobile device;

receiving from the remote server with the module the authentication of the application program;

receiving from at least one of the remote server and a user with the module an authorization to provide the permission for the application program to access the protected resource; and

providing with the module to the application program the permission to access the protected resource in response to receiving the authorization.

16. The method of claim 15, further comprising:

cryptographically signing with the module data produced by the protected resource; and

generating with the module a notification in response to at least one of the application program requesting the permission to access the protected resource and the application program accessing the protected resource.

17. A system for managing application program access to a protected resource residing on a mobile device comprising at least one computing device including at least one memory comprising instructions operable to enable the computing device to perform a procedure comprising:

providing the permission to access the protected resource in response to receiving the authorization.

18. The system of claim 17, wherein the at least one memory further comprises instructions operable to enable the computing device to perform a procedure comprising:

cryptographically signing data produced by the protected resource; and

generating a notification in response to the application program accessing the protected resource.

19. Computer-readable media tangibly embodying a program of instructions executable by a computing device to implement a method, the computing device being capable of interfacing with a communications network, the method comprising:

20. The computer-readable media of claim 19, embodying the program of instructions executable by a computing device to implement the method further comprising:

cryptographically signing data produced by the protected resource; and