# US 2017/0302634 A1 · Cryptographic security functions based on anticipated changes in dynamic minutiae

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0302634 A1
- Document ID: US20170302634A1
- Status: Published application
- Kind: A1
- Application number: 15/635,969
- Filed: 2017-06-28
- Published: 2017-10-19
- Earliest claimed: 2011-02-03
- Assignees: mSignia, Inc.
- Applicants: mSignia, Inc.
- Inventors: Paul Timothy Miller; George Allen Tuvell
- Web page: https://patentgrep.com/patent/US20170302634A1

## CPC

- H04L 63/0457: {wherein the sending and receiving network entities apply dynamic encryption, e.g. stream encryption (cryptographic mechanisms or cryptographic arrangements for stream encryption H04L9/065)}
- H04L 9/0861: {Generation of secret information including derivation or calculation of cryptographic keys or passwords}
- H04L 9/0866: {involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics}
- H04L 9/0872: {using geo-location information, e.g. location data, time, relative position or proximity to other entities}
- H04L 9/16: the keys or algorithms being changed during operation
- H04L 9/3231: {Biological data, e.g. fingerprint, voice or retina (network architectures or network communication protocols for supporting authentication of entities using biometrical features in a packet data network H04L63/0861)}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3271: {using challenge-response}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)}
- H04L 63/061: {for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838)}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/0861: {using biometrical features, e.g. fingerprint, retina-scan (cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231)}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Dynamic key cryptography validates mobile device users to cloud services by uniquely identifying the user's electronic device using a very wide range of hardware, firmware, and software minutiae, user secrets, and user biometric values found in or collected by the device. Processes for uniquely identifying and validating the device include: selecting a subset of minutia from a plurality of minutia types; computing a challenge from which the user device can form a response based on the selected combination of minutia; computing a set of pre-processed responses that covers a range of all actual responses possible to be received from the device if the combination of the particular device with the device's collected actual values of minutia is valid; receiving an actual response to the challenge from the device; determining whether the actual response matches any of the pre-processed responses; and providing validation, enabling authentication, data protection, and digital signatures.

## Claims

### Claim 1

A system comprising:
a non-transitory memory storing information associated with one or more identities, wherein the information stored for an identity includes a plurality of identity validation objects comprising a variable type, a data value associated with the variable type, and information related to one or more anticipated changes to the data value, wherein the plurality of identity validation objects includes objects representing at least one non-static characteristic associated with the identity selected from the group of non-static characteristics comprising: user added data, entertainment data, user contact data, calling application data, software component data, email data, network connection data, frequently called phone numbers, and geo-location data; and
one or more hardware processors in communication with the non-transitory memory and configured to execute instructions to cause the system to perform authentication operations comprising:
receiving, from a first device associated with a first identity over a network, a message based on a data value from the first device corresponding to a first variable type, wherein the data value serves a purpose for the first device other than a security purpose;
retrieving a first identity validation object that corresponds to the first identity and the first variable type, the first identity validation object comprising a first data value and first information related to one or more anticipated changes to the first data value;
determining whether the data value used to create the message is acceptable for the first identity using the first data value and the first information related to one or more anticipated changes stored in the first validation object;
in response to a determination that the data value is acceptable for the first identity, updating the first identity validation object for the first identity based on the data value; and
performing a subsequent authentication process for the first identity using the updated first identity validation object.

### Claim 2 (depends on 1)

The system of claim 1, wherein updating the first identity validation object comprises replacing the first data value in the first identity validation object with the data value.

### Claim 3 (depends on 1)

The system of claim 1, wherein updating the first identity validation object comprises:
generating information related to one or more anticipated changes to the data value; and
incorporating the generated information into the first identity validation object.

### Claim 4 (depends on 3)

The system of claim 3, wherein generating the information comprises:
retrieving, from an external source over a network, information related to one or more potential changes to a non-static characteristic of the first identity corresponding to the first variable type; and
deriving the information related to the one or more anticipated changes based on the retrieved information and the data value.

### Claim 5 (depends on 4)

The system of claim 4, wherein the external source comprises at least one of a second device that is associated with the first identity or a third device that is not associated with the first identity.

### Claim 6 (depends on 1)

The system of claim 1, wherein determining whether the data value from the first device is an acceptable data value for the first identity comprises:
generating, for the first identity, a set of possible data values corresponding to the first variable type by applying the first information related to one or more anticipated changes to the first data value, wherein the set of possible data values comprises the first data value;
determining at least one anticipated change from the first information that generates a possible data value corresponding to the data value from the first device; and
computing, for the data value from the first device, a score indicating a likelihood that the data value from the first device is associated with the first identity based on the one anticipated change; and
determining whether the computed score passes a predetermined threshold.

### Claim 7 (depends on 1)

The system of claim 1, wherein the plurality of identity validation objects includes objects representing at least three non-static characteristics associated with the identity selected from the group of non-static characteristics comprising: user customization data, entertainment data, user contact data, calling application data, software component data, email data, network connection data, frequently called phone numbers, and geo-location data.

### Claim 8 (depends on 1)

The system of claim 1, wherein updating the first identity validation object further comprises:
determining that at least one anticipated change from the one or more anticipated changes stored in the first identity validation object is no longer applicable to the first identity based on the data value of the first device; and
designating information related to the at least one anticipated change in the first identity validation object as obsolete.

### Claim 9

A system comprising:
a non-transitory memory storing information associated with one or more identities, wherein the information stored for an identity includes a plurality of identity validation objects comprising a variable type, a data value associated with the variable type, and information related to one or more anticipated changes to the data value, wherein the plurality of identity validation objects includes objects representing at least one non-static characteristic associated with the identity selected from the group of non-static characteristics comprising: user added data, entertainment data, user contact data, calling application data, software component data, email data, network connection data, frequently called phone numbers, and geo-location data; and
one or more hardware processors in communication with the non-transitory memory and configured to execute instructions to cause the system to perform operations comprising:
receiving, from an external source over a network, information related to potential changes to the at least one non-static characteristic associated with a first identity;
retrieving a first identity validation object corresponding to the at least one non-static characteristic, the first identity validation object comprising a first variable type, a first data value, and first information related to one or more anticipated changes to the first data value;
deriving, based on the received information from the external source and the first data value of the first identity validation object, information related to an anticipated change to the first data value;
updating the first identity validation object with the derived information; and
performing a subsequent authentication process for the first identity using the updated first identity validation object.

### Claim 10 (depends on 9)

The system of claim 9, wherein the external source is associated with an entity different than the first identity.

### Claim 11 (depends on 10)

The system of claim 10, wherein the received information comprises update information related to at least one software component running on a device associated with the first identity, wherein the information related to the anticipated change is derived by installing a new version of the at least one software component on a test device and retrieving a data value corresponding to the first variable type from the test device after the installation.

### Claim 12 (depends on 9)

The system of claim 9, wherein the external source comprises a device associated with the first identity, wherein the received information comprises usage information of the device, and wherein the operations further comprise:
deriving a usage trend for the first identity based on the usage information of the device, wherein updating the first identity validation object comprises incorporating the derived usage trend into the first information of the first identity validation object.

### Claim 13 (depends on 9)

The system of claim 9, wherein updating the first identity validation object comprises incorporating the derived information related to the anticipated change into the first information of the first identity validation object.

### Claim 14 (depends on 9)

The system of claim 9, wherein the plurality of identity validation objects includes objects representing at least three non-static characteristics associated with the identity selected from the group of non-static characteristics comprising: user customization data, entertainment data, user contact data, calling application data, software component data, email data, network connection data, frequently called phone numbers, and geo-location data.

### Claim 15 (depends on 9)

The system of claim 9, wherein updating the first identity validation object further comprises assigning a score to the derived information related to the anticipated change, wherein the assigned score indicates a likelihood that a data value of the first variable type found on a device associated with the first identity corresponds to a data value generated by applying the derived information to the first data value.

### Claim 16

A method, comprising:
storing information associated with one or more identities, wherein the information stored for an identity includes a plurality of identity validation objects comprising a variable type, a data value associated with the variable type, and information related to one or more anticipated changes to the data value, wherein the plurality of identity validation objects includes objects representing at least one non-static characteristic associated with the identity selected from the group of non-static characteristics comprising: user added data, entertainment data, user contact data, calling application data, software component data, email data, network connection data, frequently called phone numbers, and geo-location data;
receiving, from a first device associated with a first identity over a network, a message based on a data value from the first device corresponding to a first variable type, wherein the data value serves a purpose for the first device other than a security purpose;
retrieving a first identity validation object that corresponds to the first identity and the first variable type, the first identity validation object comprising a first data value and first information related to one or more anticipated changes to the first data value;
determining whether the data value used to create the message is acceptable for the first identity using the first data value and the first information related to one or more anticipated changes stored in the first validation object;
in response to a determination that the data value is acceptable for the first identity, updating the first identity validation object for the first identity based on the data value; and
performing a subsequent authentication process for the first identity using the updated first identity validation object.

### Claim 17 (depends on 16)

The method of claim 16, wherein updating the first identity validation object comprises replacing the first data value in the first identity validation object with the data value.

### Claim 18 (depends on 16)

The method of claim 16, wherein updating the first identity validation object further comprises:
generating information related to one or more anticipated changes to the data value; and
incorporating the generated information into the first information of the first identity validation object.

### Claim 19 (depends on 16)

The method of claim 16, wherein the plurality of identity validation objects includes objects representing at least three non-static characteristics associated with the identity selected from the group of non-static characteristics comprising: user customization data, entertainment data, user contact data, calling application data, software component data, email data, network connection data, frequently called phone numbers, and geo-location data.

### Claim 20 (depends on 16)

The system of claim 16, wherein the first identity validation object represents the at least one non-static characteristic.
