A java card and its application patching method

Abstract

The invention provides a JavaCard and method for patching an application of the JavaCard. The method comprises the following steps: downloading a patch of an appointed application program, wherein the patch comprises an applet subclass which inherits the appointed application program; and instantiating the patch. The invention utilizes an inheritance relationship to design an efficient, easy, simple and practical commercial application patching mechanism which aims at the JavaCard, a hierarchical patch framework designed in the application APPLET is built in a hard mask JavaCard, and a problem appearing in any layer in the APPLET can be revised.

Description

technical field [0001] The invention relates to the field of smart cards, in particular to a Java card and a method for patching its application. Background technique [0002] With the continuous advancement of science and technology, the application of smart cards has been involved in various fields of human life, such as commerce, medical care, insurance, transportation, social public utilities and other fields. At the same time, the number of smart cards in the hands of users is also increasing, especially for the same type of cards, it is often necessary to replace a new card to upgrade the card information. Therefore, how to efficiently use smart cards, that is, how to design the patch mechanism of smart cards to achieve It is very important to update the card application after the card is issued. [0003] In general, for NATIVE (local implementation) cards, if you find that there is a program error in COS (Card Operating System, card operating system) or you need to a...

AI Technical Summary

Problems solved by technology

[0006] The above is the development of the NATIVE card patch mechanism, but for JavaCard (Java Card) based on the idea of ​​object-oriented programming, due to the limitation of cross-CAP (Converted Applet, converted small application program) package access, there is almost no practical patch mechanism

This leads to poor flexibility in JavaCard application development, especially when problems occur after the card has been masked or delivered for use, the modification will be very difficult and the modification cycle will be long

For security reasons, the Java platform has great restrictions on the application structure. The existing patch mechanism is still in the theoretical stage, and there is still a certain distance from the goal of being efficient, easy to implement, simple and practical. Most JavaCard COS problems are still Use the method of full post-download (JAVA program has the attribute of dynamic download, full post-download means to download all the application programs afterward, discarding all the application programs that have been masked) to modify

[0007] The existing patch mechanism is only at the theoretical stage, and does not consider the space cost of later patch development. If there is a problem with the application, the patch will waste a lot of valuable erasable storage area resources, especially in the commercial process, which will seriously affect Card Competitiveness

Images