System and method for maintaining device state coherency

• US 9,633,098 B2
• Filed: 09/25/2013
• Issued: 04/25/2017
• Est. Priority Date: 09/25/2012
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Aissi, Selim, Kgil, Taeho
• Primary Examiner(s): Truong, Cam-Y
• Application Number:
  US14/036,938
• Publication Number:
  US 20140089261A1
• Time in Patent Office: 1,308 Days
• CPC Class Codes: G06F 11/1461 Backup scheduling policy
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/162 Delete operations erasing in storage systems G06F3/0652
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: G06F 2201/80 Database-specific techniques
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency ensuring consistency in mirrored systems G06F11/2064
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 50/01 Social networking

Abstract

Embodiments of the invention are directed to systems and methods for maintaining coherency between different entities in a distributed system. A coherency module automatically detects a change in state in a first entity, wherein the change in state relates to a change in functional code in the first entity. A synchronization message is transmitted to a second entity to synchronize data in the second entity with data in the first entity as a result of the change in state. The second entity is configured to synchronize the data in the second entity with the data in the first entity after receiving the synchronization message.

Claims

1. A method for maintaining coherency, the method comprising:

automatically detecting by a processor of a user device, a removal of a wallet application at the user device, wherein the removal of the wallet application changes functional code of the user device, and wherein the processor of the user device automatically detects the removal of the wallet application at the user device by identifying a change in state between a persistent storage at the user device and a system memory at the user device;

initiating a transmission of a synchronization message by the user device to a second entity to apply a coherency protocol for synchronizing end states in the second entity with data in the user device;

in response to the automatically detecting the removal of the wallet application, receiving an instruction from the second entity to delete persistent sensitive data associated with the wallet application;

in response to the automatically detecting the removal of the wallet application, deleting the persistent sensitive data associated with the wallet application, wherein the persistent sensitive data being deleted is data that the wallet application uses when the functional code associated with the wallet application is executed,

wherein the second entity is configured to synchronize the data in the second entity with the data in the user device based upon a predetermined policy with high level of privilege, the predetermined policy specifying a condition to synchronize the second entity and the user device if the second entity and the user device share a common state and the change is due to a reconfiguration of the user device; and

if there is discrepancy in the end states, the second entity and the user device resolve the discrepancy either by committing to a new state or aborting and rolling back to a previous state so that the end states are coherent.

2. The method of claim 1, wherein the second entity is a wallet provider.

3. The method of claim 1, wherein initiating the transmission of the synchronization message to the second entity comprises transmitting the synchronization message from the user device to the second entity.

4. The method of claim 1, wherein initiating the transmission of the synchronization message to the second entity comprises transmitting an initiation message to an intermediate entity, wherein the intermediate entity transmits the synchronization message to the second entity.

5. The method of claim 4, wherein the intermediate entity is a trusted service manager (TSM).

6. The method of claim 1, wherein the persistent sensitive data associated with the wallet application comprises payment account information.

7. The method of claim 1, wherein the user device is a mobile device.

8. The method of claim 1, wherein the data in the second entity is associated with a state in the second entity.

9. The method of claim 1, wherein the persistent sensitive data is an account number or expiration date.

10. The method of claim 1, wherein the sensitive data comprises at least one cryptographic key associated with the wallet application.

11. The method of claim 1, wherein the synchronization message is transmitted using Transmission Control Protocol/Internet Protocol (TCP/IP).

12. A user device comprising:

a processor;

a computer readable medium coupled to the processor, the computer readable medium comprising code executable by the processor to perform a method comprising;

automatically detecting a removal of a wallet application at the user device, wherein the removal of the wallet application changes functional code of the user device, and wherein the processor of the user device automatically detects the removal of the wallet application at the user device by identifying a change in state between a persistent storage at the user device and a system memory at the user device;

initiating a transmission of a synchronization message by the user device to a second entity to apply a coherency protocol for synchronizing end states in the second entity with data in the user device;

in response to the automatically detecting the removal of the wallet application, receiving an instruction from the second entity to delete persistent sensitive data associated with the wallet application;

in response to the automatically detecting the removal of the wallet application, deleting the persistent sensitive data associated with the wallet application, wherein the persistent sensitive data being deleted is data that the wallet application uses when the functional code associated with the wallet application is executed,

wherein the second entity is configured to synchronize the data in the second entity with the data in the user device based upon a predetermined policy with high level of privilege, the predetermined policy specifying a condition to synchronize the second entity and the user device if the second entity and the user device share a common state and the change is due to a reconfiguration of the user device; and

if there is discrepancy in the end states, the second entity and the user device resolve the discrepancy either by committing to a new state or aborting and rolling back to a previous state so that the end states are coherent.

13. The user device of claim 12, wherein the second entity is a wallet provider.

14. The user device of claim 12, wherein the data in the second entity is associated with a state in the second entity.

15. The user device of claim 12, wherein initiating the transmission of the synchronization message to the second entity comprises transmitting an initiation message to an intermediate entity, wherein the intermediate entity transmits the synchronization message to the second entity.

16. The user device of claim 12, wherein the persistent sensitive data associated with the wallet application comprises payment account information.

17. The user device of claim 12, wherein the user device is a mobile device.

18. A system comprising:

a user device; and

a second entity, wherein the user device and the second entity are communicatively coupled to each other; and

wherein the user device comprises;

a processor;

a computer readable medium coupled to the processor, the computer readable medium comprising code executable by the processor to perform a method comprising;

automatically detecting a removal of a wallet application at the user device, wherein the removal of the wallet application changes functional code of the user device, and wherein the processor of the user device automatically detects the removal of the wallet application at the user device by identifying a change in state between a persistent storage at the user device and a system memory at the user device;

initiating, by the user device, a transmission of a synchronization message to the second entity to apply a coherency protocol for synchronizing end states in the second entity with data in the user device;

in response to the automatically detecting the removal of the wallet application, receiving an instruction from the second entity to delete persistent sensitive data associated with the wallet application;

in response to the automatically detecting the removal of the wallet application, deleting the persistent sensitive data associated with the wallet application, wherein the persistent sensitive data being deleted is data that the wallet application uses when the functional code associated with the wallet application is executed,

wherein the second entity is configured to synchronize the data in the second entity with the data in the user device based upon a predetermined policy with high level of privilege, the predetermined policy specifying a condition to synchronize the second entity and the user device if the second entity and the user device share a common state and the change is due to a reconfiguration of the user device; and

if there is discrepancy in the end states, the second entity and the user device resolve the discrepancy either by committing to a new state or aborting and rolling back to a previous state so that the end states are coherent.

19. The system of claim 18, wherein the user device is a mobile device and the second entity is a wallet provider.