System and method for support of legacy communications protocols in a smart card

Abstract

A method and system for providing support for legacy protocols for remote method invocation on a computer system. An annotation in program source is used to build a mapping data structure appended to the executable program. During execution of an executable program legacy protocol messages are translated using the mapping data structure.

1 . A method for providing support for legacy (APDU) protocols for remote method invocation on a computer system (SC) designed to process remote method invocation using a native protocol (RPC), comprising: 
 transforming an annotated source program into an executable program suitable for execution on the computer system (SC) wherein the annotated source program contains annotations with information necessary to transform messages from the legacy protocol to a native protocol wherein the messages invoke methods of the source program;    organizing the annotations associated with each such method in a mapping data structure appended to the executable program;    executing the executable program on the computer system, comprising: 
 upon receipt of a message from a remote computer, determining whether the message is a message in the legacy protocol;  
 upon detecting that the message is a message in the legacy protocol, transforming the message into a message in the native protocol using information stored in the mapping data structure; and  
 processing the transformed message using a module designed to process messages in the native protocol.  
   
     
     
         2 . The method of  claim 1  wherein the annotations provide at least part of a message used to invoke the method using a message in the format of the legacy protocol whereby the annotation provide a mapping between the message in the format of the legacy protocol and method.  
     
     
         3 . The method of  claim 2  wherein the legacy protocol is APDU and the native protocol is RPC and wherein each annotation contains the APDU header corresponding to a particular RPC method of a server object.  
     
     
         4 . The method of  claim 3  wherein the mapping data structure comprises an APDU mapping entry for at least one method wherein the APDU mapping entry comprises an APDU header field and an RPC method name field thereby providing a mapping between the APDU header and RPC method name.  
     
     
         5 . The method of  claim 4  further comprising: 
 recording a server reference name upon receipt of an APDU select instance instruction wherein the server reference name corresponds to a particular instance; and    wherein the step of transforming a message comprises producing a message by pre-pending the server reference name to the server class name, the method name of the method being invoked and any payload data.    
     
     
         6 . The method of  claim 1  wherein the program annotations are Java annotations.  
     
     
         7 . The method of  claim 1  wherein the program annotations are. NET attributes.  
     
     
         8 . A converter for producing executable programs capable of receiving messages in a legacy protocol and to process such messages in a native protocol from a source program, comprising logic for: 
 reading annotations in the source program, wherein the annotations provide a mapping between method names for methods that may be invoked using messages in the legacy protocol and the native protocol; and    using the annotations to create a mapping data structure providing a mapping between method invoking instructions in the legacy protocol and method invoking instructions in the native protocol.    
     
     
         9 . The converter of  claim 8  wherein the annotations are ignored by a compiler.  
     
     
         10 . The converter of  claim 8  wherein the legacy protocol is ISO-7816 APDU protocol and the native protocol is RPC method invocation, and wherein each annotation is an APDU header corresponding to a method name for a method implementing a method to be invoked by the APDU header.  
     
     
         11 . The converter of  claim 8  wherein the logic for reading annotations and for using the annotations is logic executable on a software development computer system.  
     
     
         12 . The converter of  claim 8  wherein the logic for reading annotations and for using the annotations is logic executable on a smart card.  
     
     
         13 . The converter of  claim 8  wherein the program annotations are Java annotations.  
     
     
         14 . The converter of  claim 8  wherein the program annotations are .NET attributes.  
     
     
         15 . A software system for allowing method invocation in either a native protocol or in a legacy protocol, comprising: 
 a converter operable to produce executable programs from source programs, the converter comprising: 
 logic operable to produce a mapping data structure from annotations embedded in the source programs wherein the annotations provide a mapping between method invocations in the legacy protocol and corresponding method names; and  
   a communications module operable to use the mapping data structure to translate messages received in the legacy protocol into messages in the native protocol.    
     
     
         16 . The software system of  claim 15  wherein the legacy protocol is ISO-7816 APDU protocol and the native protocol is RPC, and wherein each annotation provides a mapping between an APDU header and a method name for a method to be invoked by a message having the APDU header.  
     
     
         17 . The software system of  claim 15 , wherein the converter operates on a software development computer system.  
     
     
         18 . The software system of  claim 15 , wherein the executable programs are loaded onto a smart card and the converter operates on the smart card.  
     
     
         19 . The software system of  claim 15  wherein the program annotations are Java annotations.  
     
     
         20 . The software system of  claim 15  wherein the program annotations are .NET attributes.