Populating resource-constrained devices with content verified using API definitions

Abstract

A method for remote incremental program verification includes receiving content verified by at least one content provider, installing the content on a resource-constrained device and issuing the resource-constrained device to an end user. The content includes at least one program unit and each program unit includes an Application Programming Interface (API) definition file and an implementation. Each API definition file defines items in its associated program unit that are made accessible to one or more other program units and each implementation includes executable code corresponding to the API definition file. The executable code includes type specific instructions and data. According to one aspect, subsequent installation of content on the resource-constrained device is disabled. A resource-constrained device includes a memory for providing content verified by at least one content provider and a virtual machine that is capable of executing instructions included within the content. The content includes at least one program unit and each program unit includes an Application Programming Interface (API) definition file and an implementation. Each API definition file defines items in its associated program unit that are made accessible to one or more other program units, each implementation includes executable code corresponding to the API definition file, and executable code includes type specific instructions and data.

1 - 77 . (canceled)  
   
   
       78 . A method comprising: 
 receiving content verified by at least one content provider, 
 wherein said content includes: 
 at least one program unit comprising an Application Programming Interface (API) definition file and an implementation 
 wherein said API definition file defines items in a program unit associated with said API definition file wherein said items are made accessible to one or more other program units; and  
 said implementation includes executable code corresponding to said API definition file wherein said executable code includes type specific instructions and data; and  
 
 
   installing said content on a resource-constrained device.    
   
   
       79 . The method of  claim 78  further comprising: 
 disabling subsequent installation of content on said resource-constrained device.    
   
   
       80 . The method of  claim 78  wherein said content provider comprises at least an applet provider.  
   
   
       81 . The method of  claim 78  wherein said content provider comprises at least a device manufacturer.  
   
   
       82 . The method of  claim 78  wherein said content provider comprises at least a device issuer.  
   
   
       83 . The method of  claim 78  wherein said content provider comprises at least a trusted post-issuance installer.  
   
   
       84 . The method of  claim 83  further comprising: 
 allowing post-issuance installation of verified content on said resource-constrained device by said trusted post-issuance installer, said post-installation occurring after issuance of said resource constrained device.    
   
   
       85 . The method of  claim 84  wherein said verified content in said post-issuance installation comprises: 
 a new program unit verified by said trusted post-issuance installer; and    said post-issuance installation is performed by said trusted post-issuance installer.    
   
   
       86 . The method of  claim 84  wherein post-issuance verification of said content is performed on a resource-rich device.  
   
   
       87 . The method of  claim 84  wherein post-issuance verification is performed on a terminal device.  
   
   
       88 . The method of  claim 83  wherein said content provider comprises said trusted post-issuance installer and at least one other content provider selected from a group consisting of an applet provider, a device manufacturer, and a device issuer.  
   
   
       89 . The method of claim  1  wherein said content provider comprises at least an untrusted post-issuance installer.  
   
   
       90 . The method of  claim 89  further comprising: 
 allowing post-issuance installation of verified content on said resource-constrained device by said untrusted post-issuance installer, said post-installation occurring after issuance of said resource constrained device.    
   
   
       91 . The method of  claim 90  wherein said verified content in said post-issuance installation comprises: 
 a new program unit verified by said untrusted post-issuance installer; and    said post-issuance installation is performed by said untrusted post-issuance installer.    
   
   
       92 . The method of  claim 90  wherein post-issuance verification of said content is performed on a resource-rich device.  
   
   
       93 . The method of  claim 90  wherein post-issuance verification is performed on a terminal device.  
   
   
       94 . The method of  claim 89  wherein said content provider comprises said untrusted post-issuance installer and at least one other content provider selected from a group consisting of an applet provider, a device manufacturer, and a device issuer.  
   
   
       95 . A program storage device readable by a machine, embodying a program of instructions executable by the machine to perform program verification, comprising: 
 receiving content verified by at least one content provider, 
 wherein said content includes: 
 at least one program unit comprising an Application Programming Interface (API) definition file and an implementation 
 wherein said API definition file defines items in a program unit associated with said API definition file wherein said items are made accessible to one or more other program units; and  
 said implementation includes executable code corresponding to said API definition file wherein said executable code includes type specific instructions and data; and  
 
 
   installing said content on a resource-constrained device.    
   
   
       96 . The program storage device of  claim 95  further comprising: 
 disabling subsequent installation of content on said resource-constrained device.    
   
   
       97 . A system for executing a software application, the system comprising: 
 a computing system that generates executable code, comprising means for receiving content verified by at least one content provider, said content including at least one program unit, each program unit comprising an Application Programming Interface (API) definition file and an implementation, each API definition file defining items in its associated program unit that are made accessible to one or more other program units, each implementation including executable code corresponding to said API definition file, said executable code including type specific instructions and data; and    means for installing said content on a resource-constrained device;    
   
   
       98 . A resource-constrained device comprising: 
 memory for providing content verified by at least one content provider, said content including at least one program unit, each program unit comprising an Application Programming Interface (API) definition file and an implementation, each API definition file defining items in its associated program unit that are made accessible to one or more other program units, each implementation including executable code corresponding to said API definition file, said executable code including type specific instructions and data; and    a virtual machine that is capable of executing instructions included within content.    
   
   
       99 . The resource-constrained device of  claim 98  wherein said resource-constrained device comprises a smart card.  
   
   
       100 . The resource-constrained device of  claim 98  further comprising: 
 an installer device for installation of said content on said resource-constrained device.    
   
   
       101 . The resource-constrained device of  claim 100  further comprising installation of additional content by a post-issuance installer after said resource-constrained device is issued to an end user