User profile selection using contextual authentication
Abstract
In embodiments, apparatuses, methods and storage media (transitory and non-transitory) are described that are associated with user profile selection using contextual authentication. In various embodiments, a first user of a computing device may be authenticated and have an access control state corresponding to a first user profile established, the computing device may select a second user profile based at least in part a changed user characteristic, and the computing device may present a resource based at least in part on the second user profile. In various embodiments, the computing device may include a sensor and a user profile may be selected based at least in part on an output of the sensor and a previously stored template generated by a machine learning classifier.
Claims
exact text as granted — not AI-modified1 - 24 . (canceled)
25 . At least one non-transitory computer-readable medium (CRM) comprising instructions to cause a computer server remote from a mobile phone, in response to execution of the instructions by one or more processors of the computer server, to:
receive data representative of usage characteristics of a user of the mobile phone; establish a usage characteristic profile of the user based at least in part on the received data representative of usage characteristics of the user; and store the established usage characteristic profile of the user remotely from the mobile phone; wherein the usage characteristic profile remotely stored from the mobile phone is subsequently used to authenticate whether an attempting user making an attempt to access a resource with the mobile phone is the user.
26 . The non-transitory CRM of claim 25 , wherein the data representative of usage characteristics of a user of the mobile phone comprise behaviometric data of the user collected while the user is using the mobile phone.
27 . The non-transitory CRM of claim 26 , wherein the behaviometric data of the user comprise pressure data, placement data, swipe speed data or movement data collected while the user is using the mobile phone.
28 . The non-transitory CRM of claim 25 , wherein the usage characteristics profile of the user comprises a usage characteristics model of the user.
29 . The non-transitory CRM of claim 25 , wherein the data, the usage characteristics, and the user are respectively first data, first usage characteristics, and first user; and the computer server is further caused to receive second data representative of second usage characteristics of a second user of the mobile phone, and determine, in response to the receipt of the second data, a confidence level with respect to whether the first and second users are the same user.
30 . The non-transitory CRM of claim 25 , wherein the computer server is caused to continuously receive data representative of usage characteristics of the mobile phone, and monitor, continuously, usage characteristics of the mobile phone.
31 . The non-transitory CRM of claim 25 , wherein a successful result of the authentication includes identification of the user.
32 . The non-transitory CRM of claim 25 , wherein a successful result of the authentication includes verification that the attempting user making the attempt to access the resource with the mobile phone is the user.
33 . The non-transitory CRM of claim 25 , wherein a result of the authentication is used to allow or disallow usage of an application.
34 . The non-transitory CRM of claim 25 , wherein a result of the authentication is used to determine an access control state of the mobile phone.
35 . A method comprising:
receiving, by a computer server remote from a mobile phone, data representative of usage characteristics of a user of the mobile phone; establishing, by the computer server, a usage characteristic profile of the user based at least in part on the received data representative of usage characteristics of the user; and storing, by the computer server, the established usage characteristic profile of the user remotely from the mobile phone; wherein the usage characteristic profile remotely stored from the mobile phone is subsequently used to authenticate whether an attempting user making an attempt to access a resource of the mobile phone is the user.
36 . The method of claim 35 , wherein the data representative of usage characteristics of a user of a mobile phone comprise behaviometric data of the user collected while the user is using the mobile phone.
37 . The method of claim 36 , wherein the behaviometric data of the user comprise pressure data, placement data, swipe speed data or movement data collected while the user is using the mobile phone.
38 . The method of claim 35 , wherein the usage characteristics profile of the user comprises a usage characteristics model of the user.
39 . The method of claim 35 , wherein the data, the usage characteristics, and the user are respectively first data, first usage characteristics, and first user; and the method further comprises receiving, by the computer server, second data representative of second usage characteristics of a second user of the mobile phone, and determining, by the computer server, in response to the receipt of the second data, a confidence level with respect to whether the first and second users are the same user.
40 . The method of claim 35 , wherein the method further comprises continuously receiving, by the computer server, data representative of usage characteristics of the mobile phone, and monitoring, by the computer server, continuously, usage characteristics of the mobile phone.
41 . The method of claim 35 , wherein a successful result of the authentication includes identification of the user.
42 . The method of claim 35 , wherein a successful result of the authentication includes verification that the attempting user making the attempt to access the resource with the mobile phone is the user.
43 . The method of claim 35 , wherein a result of the authentication is used to allow or disallow usage of an application.
44 . The method of claim 35 , wherein a result of the authentication is used to determine an access control state of the mobile phone.
45 . An apparatus comprising;
one or more processor; memory; a security module stored in the memory, and executed by the one or more processor to: receive data representative of usage characteristics of a user of the mobile phone; establish a usage characteristic profile of the user based at least in part on the received data representative of usage characteristics of the user; and store the established usage characteristic profile of the user remotely from the mobile phone; wherein the usage characteristic profile remotely stored from the mobile phone is subsequently used to authenticate whether an attempting user making an attempt to access a resource of the mobile phone is the user.
46 . The apparatus of claim 45 , wherein the data representative of usage characteristics of a user of a mobile phone comprise behaviometric data of the user collected while the user is using the mobile phone.
47 . The apparatus of claim 45 , wherein the data, the usage characteristics and the user are respectively first data, first usage characteristics, and first user; and the security module is further executed to receive second data representative of second usage characteristics of a second user of the mobile phone, and determine, in response to the receipt of the second data, a confidence level with respect to whether the first and second users are the same user.
48 . The apparatus of claim 45 , wherein the security module is further executed to continuously receive data representative of usage characteristics of the mobile phone, and to monitor, continuously, usage characteristics of the mobile phone.
49 . The apparatus of claim 45 , wherein a successful result of the authentication includes identification of the user, verification that the attempting user making the attempt to access the resource with the mobile phone is the user, or allowance or disallowance of usage of an application.Join the waitlist — get patent alerts
Track US2018103034A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.