METHOD FOR PEER TO PEER MOBILE CONTEXT AUTHENTICATION

• US 20150244699A1
• Filed: 02/02/2015
• Published: 08/27/2015
• Est. Priority Date: 02/21/2014
• Status: Active Grant

• Current Assignee: LiveEnsure, Inc.
• Original Assignee: LiveEnsure, Inc.
• Inventors: Hessler, Christian J.
• Granted Patent: US 9,754,097 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 9/32 including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• CPC Class Codes: H04W 12/062 Pre-authentication
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys

Abstract

The invention is a system and a method for achieving private, personalized, real-time authentication of one or more networked peer users and their mobile or wearable electronic computing devices through holistic contextual verification of the device, location, proximity, knowledge and behavioral attributes for a defined session, event, object or resource access or mutual user and device identity context verification.

Claims

1. A computer-based method of authenticating a user on a mobile, wearable or fixed electronic data processing unit to another user or users on other mobile, wearable or fixed electronic data processing units, the steps comprising:

providing a server;

providing a primary electronic data processing unit;

providing a secondary electronic data processing unit;

providing an intermediate host (website, app, device, direct session);

wherein said host may be comprised of a presentation;

wherein said electronic data processing units may be comprised of an application;

wherein said server, host and said electronic data processing units are in network communication;

where said primary electronic data processing unit preferably initiates direct connection to said secondary electronic data processing unit;

or

where said primary electronic data processing unit preferably tags host content, connection, resource, device, session, data, event, object with required authentication service object;

where an primary electronic data processing unit or secondary electronic data processing unit session initiation or tagged host content provision, engagement or consumption preferably triggers server to provision shared authentication object with request to authenticate;

returning by said server to said host or said secondary electronic data processing unit an object;

presenting said object to said secondary electronic data processing unit application;

creating by said server a first template and a second template in a memory;

processing said first template by said server;

processing said second template by said secondary electronic data processing unit;

presenting said object to said secondary electronic data processing unit by said host via said browser channel;

accepting and retrieving by said secondary electronic data processing unit said object by following said object by said secondary electronic data processing unit independent of said server via a third channel;

interrogating by said server a plurality of contextual elements;

filling said first template by said server based on said plurality of contextual elements;

constructing a one-time contextual server signature by said server;

interrogating by said application on said secondary electronic data processing unit a plurality of similar contextual elements from a perspective of said electronic data processing unit;

filling said second template by said application based on said plurality of similar contextual elements;

constructing a one-time contextual application signature by said application; and

determining by said server whether said one-time contextual application signature sufficiently matches said one-time contextual server signature;

authenticating said secondary electronic data processing unit when said match is sufficient;

rejecting said secondary electronic data processing unit if said match is insufficient.

2. The method of claim 1, wherein said step of said primary electronic data processing unit or secondary electronic data processing unit initiation or connection to trigger request to authenticate is preferably a synchronous network session between said electronic data processing unit without intermediate host, such as in chat, streaming or device to device communication.

3. The method of claim 1, wherein said step of accepting by said secondary electronic data processing unit may be enabled via said secondary electronic data processing unit'"'"'s ability to scan, sense, enter, input, consume or respond to said object on said secondary electronic data processing unit directly from server without intermediary host (app to app).

4. The method of claim 1, wherein said step of accepting by said secondary electronic data processing unit may be enabled via said secondary electronic data processing unit'"'"'s ability to scan, sense, enter, input, consume or respond to said object on host.

5. The method of claim 1 or 2, wherein said step of accepting by said secondary electronic data processing unit may be enabled via said secondary electronic data processing unit'"'"'s ability to connect directly with server via the smart channel and engage the active session and consume and process authentication object without scan, sense, enter, input or response to said object on host.

6. The method of claim 1 or 2, wherein said plurality of contextual elements and said plurality of similar contextual elements may be selected from the group of elements consisting of:

server, user, device, wearable, biometric, location, proximity, any supplied credentials, or stored algorithms about the user behavior, attributes, knowledge or history.

7. The method of claim 1 or 2, wherein said user may perform one or more voluntary or involuntary behavioral actions, gestures or motions via the secondary electronic data processing unit that are interrogated during said interrogation steps.

8. The method of claim 1 or 2 wherein either said primary electronic data processing unit or host may be in communication with one or more secondary electronic data processing unit who each require individual and discrete authentication.

9. The method of claim 1 or 2 wherein the parties involved may be a host authenticating one or more secondary electronic data processing units and their users as peers across a shared network, within a session, via the service functionality.