REMOTE CARD CONTENT MANAGEMENT USING SYNCHRONOUS SERVER-SIDE SCRIPTING

• US 20130318508A1
• Filed: 05/24/2012
• Published: 11/28/2013
• Est. Priority Date: 05/24/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Lee, Jin Ho, Jin Eo, Young, Lee, Hyeongki, Lee, JooHo
• Granted Patent: US 8,813,029 B2
• Time in Patent Office: Days
• US Class Current: 717/139
• CPC Class Codes: G06F 9/44 Arrangements for executing specific programs
• CPC Class Codes: G06F 9/45512 Command shells
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Remote card content management using synchronous server-side scripting is provided. A system includes a computer processor and a script interpreter executable by the computer processor. The script interpreter is configured to perform a method. The method includes parsing a script configured to perform a card content management operation as a sequence of operations for a secure element based on receiving a request from a mobile device located remotely from the computer processor. The method also includes creating an execution context for the script to identify the sequence of operations in the script as non-flushing and flushing nodes. A flushing node is identified as an operation that sends a response to the request and expects a subsequent request from the mobile device for the secure element. The method further includes pausing execution of the script upon sending the response at the flushing node.

Claims

1. A system, comprising:

a computer processor; and

a script interpreter executable by the computer processor, the script interpreter configured to perform a method comprising;

parsing a script configured to perform a card content management operation as a sequence of operations for a secure element based on receiving a request from a mobile device located remotely from the computer processor;

creating an execution context for the script to identify the sequence of operations in the script as non-flushing and flushing nodes, a flushing node identified as an operation that sends a response to the request and expects a subsequent request from the mobile device for the secure element; and

pausing execution of the script upon sending the response at the flushing node.

2. The system of claim 1, wherein pausing execution of the script further comprises:

marking the flushing node as a current node in the execution context;

storing the execution context; and

halting execution of the script until the subsequent request is received.

3. The system of claim 2, wherein the script interpreter is further configured to perform:

upon receiving the subsequent request, identifying the current node in the execution context; and

continuing execution of the script until a next flushing node is reached.

4. The system of claim 1, further comprising:

a card content management processor comprising;

the script interpreter, a plurality of card content management scripts associated with the card content management operation, and a current script identifier.

5. The system of claim 4, further comprising:

an application container comprising an instance of the card content management processor and a card content management handler, the card content management handler configured to invoke the instance of the card content management processor.

6. The system of claim 5, further comprising:

a map configured to identify a unique identifier associated with the card content management operation and the instance of the card content management processor associated with the card content management operation for the secure element.

7. The system of claim 6, further comprising:

a plurality of instances of the card content management processor associated with a plurality of card content management operations for a plurality of secure elements located remotely from the computer processor, wherein each of the instances of the card content management processor has a separate entry in the map and each of the instances of the card content management processor is a separate component in the application container.

8. The system of claim 1, wherein the secure element is a smart card in the mobile device.

9. The system of claim 8, wherein the request is for an application protocol data unit for the smart card, and further comprising:

based on receiving the request, responding with the application protocol data unit at the flushing node.

10. The system of claim 9 wherein the script interpreter only sends the application protocol data unit in response to the request for the application protocol data unit.

11. A computer program product comprising a non-transitory storage medium having computer-readable program code embodied thereon, which when executed by a computer processor, causes the computer processor to implement a method, the method comprising:

parsing a script configured to perform a card content management operation as a sequence of operations for a secure element based on receiving a request from a mobile device located remotely from the computer processor;

creating an execution context for the script to identify the sequence of operations in the script as non-flushing and flushing nodes, a flushing node identified as an operation that sends a response to the request and expects a subsequent request from the mobile device for the secure element; and

pausing execution of the script upon sending the response at the flushing node.

12. The computer program product of claim 11, wherein pausing execution of the script further comprises:

marking the flushing node as a current node in the execution context;

storing the execution context; and

halting execution of the script until the subsequent request is received.

13. The computer program product of claim 11, further comprising:

upon receiving the subsequent request, identifying the current node in the execution context; and

continuing execution of the script until a next flushing node is reached.

14. The computer program product of claim 11, further comprising:

associating a plurality of card content management scripts with the card content management operation; and

identifying and retrieving a current script using a current script identifier.

15. The computer program product of claim 14, further comprising:

invoking an instance of a card content management processor associated with the card content management operation in an application container, the card content management processor comprising;

a script interpreter, the plurality of card content management scripts associated with the card content management operation, and the current script identifier.

16. The computer program product of claim 15, further comprising:

accessing a map based on a unique identifier associated with the card content management operation to determine which instance of the card content management processor is associated with the card content management operation for the secure element.

17. The computer program product of claim 16, wherein a plurality of instances of the card content management processor is associated with a plurality of card content management operations for a plurality of secure elements located remotely from the computer processor, and each of the instances of the card content management processor has a separate entry in the map and each of the instances of the card content management processor is a separate component in the application container.

18. The computer program product of claim 11, wherein the secure element is a smart card in the mobile device.

19. The computer program product of claim 18, wherein the request is for an application protocol data unit for the smart card, and further comprising:

based on receiving the request, responding with the application protocol data unit at the flushing node.

20. The computer program product of claim 19, further comprising:

only sending the application protocol data unit in response to the request for the application protocol data unit.