Browse Prior Art Database

Mobile authentication challenge based on user application usage history

IP.com Disclosure Number: IPCOM000236320D
Publication Date: 2014-Apr-20
Document File: 3 page(s) / 52K

Publishing Venue

The IP.com Prior Art Database

Abstract

This disclosure relates to user authentication in a mobile device, more specifically to challenge based authentication in smartphones that have touch UI. Challenge based authentication can be used either as an alternative to user password or as a secondary authentication mechanism to verify the user identity (e.g., in case of user forgets her password). Several challenge based authentication methods exist, some require the user to answer questions about private facts (e.g., "what is the name of your pet dog?"), others require the user to perform some operation on the mobile phone (e.g., tap on the screen, draw something, sign, etc).

This invention suggests a novel challenge based user authentication based on user's application usage history which can be logged within her mobile device.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 91% of the total text.

Page 01 of 3

Mobile authentication challenge based on user application usage history

Provide a user a visual authentication challenge which depicts a list of application icons and require the user to perform a task based on metadata extracted from the user's application usage log/history (e.g.,app ids, app metadata, etc).

The idea is based on the fact that in most cases the user is the only person to know her application usage routines, such as playing angry birds app during his bus drive to work in the morning, using a specific diet tracking app, etc..

    The following are examples of app usage data based challenges for authenticating users.

Challenge 1: (use only app. usage frequency data + app. metadata from app store). Display user a list of apps. and ask user to select a subset of apps the user most/least use in general.

For example, the authentication method will display to the user 3 icons of apps that the user use, while the rest of the app icons will be icons of apps that are not installed in the user's device.

To make the authentication stronger, it is better to use apps that are both rarely used by the user and in general.

Such usage frequency can be obtained from app metadata from the "app store", e.g., Google Play API.


Page 02 of 3

2


Page 03 of 3

Challenge 2: (includes also temporal app. usage patterns)

This challenge is similar to the previous one, but also utilize the timestamps of application usage as recorded in the device log.

Therefore, we can further challen...