System and method for maintaining device state coherency

• US 10,002,174 B2
• Filed: 03/09/2017
• Issued: 06/19/2018
• 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:
  US15/455,003
• Publication Number:
  US 20170177694A1
• Time in Patent Office: 467 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:

receiving, by a server computer from a user device, a synchronization message,

wherein the synchronization message is generated after the user device automatically detects a removal of an application at the user device based on a triggering event, wherein the removal of the application changes functional code of the user device, and wherein the user device automatically detects the removal of the 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;

based at least in part on receiving the synchronization message, applying a coherency protocol for synchronizing end states in the server computer with data in the user device;

transmitting, via a network, an instruction to the user device to delete persistent sensitive data associated with the application;

after transmitting the instruction by the server computer to the user device, removing the persistent sensitive data from a memory associated with the application at the user device,

wherein the persistent sensitive data being removed is the persistent sensitive data that the application uses when the functional code associated with the application is executed, wherein the server computer is configured to synchronize data in the server computer with the data in the user device based upon a predetermined policy, wherein the predetermined policy specifies a condition to synchronize the server computer and the user device if the server computer and the user device share a common state and the change is due to a reconfiguration of the user device;

if there is discrepancy in the states, the server computer 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; and

providing, by the server computer via the network, an acknowledgement message indicating that the persistent sensitive data is removed or any subsequent transactions associated with the persistent sensitive data and the user device will be denied.

2. The method of claim 1, wherein the server computer is a wallet provider.

3. The method of claim 1, wherein synchronization message comprises information related to the change in state.

4. The method of claim 1, wherein the synchronization message is received from an intermediate entity prior to receiving the synchronization message from the user device, wherein the user device transmits the synchronization message to the intermediate entity, and the intermediate entity transmits the synchronization message to the server computer.

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 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 persistent sensitive data is an account number or expiration date.

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

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

11. A server computer 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;

receiving, from a user device, a synchronization message,

wherein the synchronization message is generated after the user device automatically detects a removal of an application at the user device based on a triggering event, wherein the removal of the application changes functional code of the user device, and wherein the user device automatically detects the removal of the 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;

based at least in part on receiving the synchronization message, applying a coherency protocol for synchronizing end states in the server computer with data in the user device;

transmitting, via a network, an instruction to the user device to delete persistent sensitive data associated with the application;

after transmitting the instruction by the server computer to the user device, removing the persistent sensitive data from a memory associated with the application at the user device,

wherein the persistent sensitive data being removed is data that the application uses when the functional code associated with the application is executed, wherein the server computer is configured to synchronize the data in the server computer with the data in the user device based upon a predetermined policy, wherein the predetermined policy specifies a condition to synchronize the server computer and the user device if the server computer and the user device share a common state and the change is due to a reconfiguration of the user device;

if there is discrepancy in the states, the server computer 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; and

providing, by the server computer via the network, an acknowledgement message indicating that the persistent sensitive data is removed or any subsequent transactions associated with the persistent sensitive data and the user device will be denied.

12. The server computer of claim 11, wherein the server computer is a wallet provider.

13. The server computer of claim 11, wherein synchronization message comprises information related to the change in state.

14. The server computer of claim 11, wherein the synchronization message is received from an intermediate entity prior to receiving the synchronization message from the user device, wherein the user device transmits the synchronization message to the intermediate entity, and the intermediate entity transmits the synchronization message to the server computer.

15. The server computer of claim 14, wherein the intermediate entity is a trusted service manager (TSM).

16. The server computer of claim 11, wherein the persistent sensitive data associated with the application comprises payment account information.

17. The server computer of claim 11, wherein the user device is a mobile device.

18. A system comprising:

a user device; and

a server computer, wherein the user device and the server computer are communicatively coupled to each other; and

wherein the server computer 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;

receiving, by the server computer from the user device, a synchronization message,

wherein the synchronization message is generated after the user device automatically detects a removal of an application at the user device based on a triggering event, wherein the removal of the application changes functional code of the user device, and wherein the user device automatically detects the removal of the 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;

based at least in part on receiving the synchronization message, applying a coherency protocol for synchronizing end states in the server computer with data in the user device;

transmitting, via a network, an instruction to the user device to delete persistent sensitive data associated with the application;

after transmitting the instruction by the server computer to the user device, removing the persistent sensitive data from a memory associated with the application at the user device,

 

wherein the persistent sensitive data being removed is the persistent sensitive data that the application uses when the functional code associated with the application is executed, wherein the server computer is configured to synchronize data in the server computer with the data in the user device based upon a predetermined policy, wherein the predetermined policy specifies a condition to synchronize the server computer and the user device if the server computer and the user device share a common state and the change is due to a reconfiguration of the user device;

if there is discrepancy in the states, the server computer 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; and

providing, by the server computer via the network, an acknowledgement message indicating that the persistent sensitive data is removed or any subsequent transactions associated with the persistent sensitive data and the user device will be denied.

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

20. The system of claim 18, wherein at least one computer in the system has a higher precedence over the user device or the server computer when resolving conflicts.