CN105302666A - JAVA CARD based backup and recovery method for data in application - Google Patents
JAVA CARD based backup and recovery method for data in application Download PDFInfo
- Publication number
- CN105302666A CN105302666A CN201510656798.XA CN201510656798A CN105302666A CN 105302666 A CN105302666 A CN 105302666A CN 201510656798 A CN201510656798 A CN 201510656798A CN 105302666 A CN105302666 A CN 105302666A
- Authority
- CN
- China
- Prior art keywords
- application
- backupdataapp
- app
- internal data
- javacard
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a JAVA CARD based backup and recovery method for data in an application. The method comprises: developing a BackUpDataApp; obtaining data in an App by utilizing the BackUpDataApp, and performing backup on the data; deleting an App package, writing the data into a new App package, and installing a new App; and obtaining the data backed up in the BackUpDataApp by utilizing the new App, and writing the data into a corresponding region of the new App, so that the data in the App of the JAVA CARD is recovered. According to the method, the data in the App are efficiently and securely backed up and recovered.
Description
Technical field
The present invention relates to a kind of backup and recovery method, particularly a kind of backup of the application internal data based on JAVACARD and restoration methods.
Background technology
Being integrated with the smart card that various App applies is that the life of people brings great convenience, and most important in these smart cards is exactly JAVACARD.JAVACARD has two large advantages: it supports one card for multiple uses and recycling.Wherein, support that one card for multiple uses way refers to that JAVACARD can exist multiple different application simultaneously, so JavaCard just can meet the demand of difference in functionality, such as, it can have electronic purse function, while also can have identity verify function; Recycling refers to that the application on JAVACARD can be carried out deleting or again adding new application as required, and the smart card without the need to more renewing, so greatly strengthen the dirigibility of application of IC cards.But along with the development of scientific and technical information technology, the application kind in JAVACARD gets more and more, and the renewal speed of application is also more and more faster, or when defect appears in the application on card, this constantly deletes the application in JAVACARD with regard to needing, and adds, upgrade, the operations such as upgrading.In the prior art, the following two kinds of methods of general employing carry out aforesaid operations to the application in JAVACARD: the first is: based on the advantage of recycling, delete original application on former card, reload new application; The second is: directly destroy old card, changes the neocaine being loaded with new opplication.But no matter be which kind of method above-mentioned, on card, original internal data comprising individuation data all cannot be preserved, all lost, need again to write new internal data to card, this just causes the waste of data message, extend card production course, in addition, second method also creates the waste of card.Therefore, a kind of can the application internal data of JAVACARD backup and the method recovered efficiently is urgently developed.
Summary of the invention
The object of the invention is to be achieved through the following technical solutions:
The backup of App application internal data and restoration methods in a kind of JAVACARD, the method comprises, exploitation BackUpDataApp application, utilize this BackUpDataApp to apply obtain App application internal data and back up it, delete App application bag, be loaded into newApp application bag, and newApp application is installed, utilize newApp to apply acquisition backed up the internal data in BackUpDataApp application before this and write newApp corresponding region, realize the backup to App application internal data in JAVACARD and recovery operation, in JAVACARD, App application achieves BackUpDataInterface and shares interface, the exploitation of BackUpDataApp application shares interface exploitation according to BackUpDataInterface, in internal data backup procedure, described BackUpDataApp application is shared interface and App by BackUpDataInterface and is applied and engage in the dialogue, in JAVACARD, the backup flow process of App application internal data comprises, 1) BackUpDataApp application request is utilized to access the shared interface of App application by the JCSystem.getAppletShareableInterfaceObject () called in JAVACARD system, 2) due to BackUpDataApp application, JCRE (JavaCardRuntimeEnvironment) carrys out by the getShareableInterfaceObject () method calling App application shared with the interface that requirement shares App application, 3) if App application allows to share, BackUpDataApp application is quoted the shared object of an acquisition App application, namely BackUpDataApp application may have access to App application, BackUpDataApp application obtains all internal datas of App application by the getDataByte () method calling App application, be kept at the data backup district of oneself, after completing, data backup operation terminates, BackUpDataApp application achieves BackUpDataInterface and shares interface, the exploitation of newApp application shares interface exploitation according to BackUpDataInterface, in the rejuvenation of internal data, described newApp application is shared interface and BackUpDataApp by BackUpDataInterface and is applied and engage in the dialogue, in JAVACARD, the recovery flow process of App application internal data comprises, 1) the shared interface applied by JCSystem.getAppletShareableInterfaceObject () the way access BackUpDataApp of calling system of newApp application request, 2) due to newApp application, JCRE carrys out by the getShareableInterfaceObject () method calling BackUpDataApp application shared with the interface that requirement shares BackUpDataApp, 3) if BackUpDataApp application allows to share, newApp applies quoting the shared object of an acquisition BackUpDataApp, so namely newApp application may have access to BackUpDataApp application, newApp application obtains all Backup Datas in BackUpDataApp application by the getDataByte () method calling BackUpDataApp, and being write corresponding data field, data restore operation completes, before App application internal data carries out internal data backup and internal data recovery operation in JAVACARD, also comprise authenticating step, this authenticating step comprises the step adopting key encryption and decryption technology to do certification, and certification is by then allowing access internal data, and authentification failure then refuses its access, described internal data backup operation and described internal data recovery operation all comprise the backup and the recovery that are realized internal data by shared interface across application access mode, internal data backup area is present in JavaCard inside, and certain internal data backup area also may reside in other system or equipment buffer memory, wherein, the App application in JAVACARD comprises multiple from each in the different applet App application of different supplier, and this different applet App is isolated by fire wall between applying, App application in described JAVACARD is the App application with functional defect, and described newApp is the App application of having repaired functional defect.
Relative to prior art, the present invention has the following advantages:
In JAVACARD of the present invention, the backup of App application internal data and restoration methods are without the need to applying typing internal data again to the App repaired, but directly original Backup Data is recovered, achieve the efficiency utilization to App internal data, in addition, also added encrypting and authenticating step, improve the security of data backup and resume.
Figure of description
Fig. 1: the data structure needing App application in the JAVACARD of backup;
The data backup process flow diagram of App application in Fig. 2: JAVACARD;
The card internal data structure after App application bag is deleted in Fig. 3: JAVACARD;
The Data Recovery Process figure of new App application in Fig. 4: JAVACARD.
Specific embodiment
Now further describe technical scheme of the present invention in conjunction with Figure of description and concrete real mode.
In the JAVACARD of the present embodiment, the backup of App application internal data and restoration methods mainly comprise, the backup of data and the recovery of data.There is in JAVACARD multiple functional App application being applicable to various applied environment, that is, JAVACARD platform is applied environment more than, same JAVACARD co-exists the different applet App application from different supplier, each applet is assigned to one and performs context, this context controls to the access of the object distributing to it, and a boundary performed between context and another execution context is often called as the fire wall (AppletFirewall) of application A pp application.JavaCard fire wall creates a virtral reactor, and such object can only be accessed and is present in (public) method in identical fire wall and data.A fire wall may comprise many applets and other objects.The action scope that JavaCard performs context current is routine package.
Functional defect is had: when functional defect has appearred in the App application in JAVACARD for App application in JAVACARD, then need to carry out repair process to this App application, adopt restorative procedure of the prior art cannot preserve this App apply in internal data, need the internal data that typing is again new, waste data resource.Method of the present invention can realize without the need to the new internal data of typing again, and by recovering the internal data backed up before this, the reparation App achieving efficient quick applies.In JAVACARD of the present invention App application internal data backup and recover flow process comprise, first BackUpDataApp application is loaded, backup App application internal data, delete App application bag, then reload the newApp application of having repaired functional defect to wrap in JAVACARD, install this newApp to apply, the App application internal data recovering to back up before this, in newApp application, finally deletes BackUpDataApp application.
First, with reference to Fig. 1, need the JAVACARD inner structure backing up App application to comprise, BackUpDataInterface shares interface, App application master routine (the internal data AppData [] that need back up obtains Backup Data interface getDataByte ()).If realize the backup to App application internal data, its prerequisite is that this App application must realize promisingly realizing data backup function and the BackUpDataInterface that designs shares interface, and this interface provides access passage for extraneous access App application.Before App application internal data backs up in JAVACARD, need first to develop the BackUpDataApp application of backup in order to realize App application internal data and recovery, and the exploitation that this BackUpDataApp applies shares interface exploitation according to BackUpDataInterface, in the process to App application internal data Backup and Restore, BackUpDataApp application is shared by this BackUpDataInterface the interactive dialogue that interface applied with App in JAVACARD and is operated.
With reference to Fig. 2, in JAVACARD, the backup flow process of App application internal data comprises, and 1) utilize BackUpDataApp application request to access the shared interface of App application by the JCSystem.getAppletShareableInterfaceObject () called in JAVACARD system; 2) due to BackUpDataApp application, JCRE (JavaCardRuntimeEnvironment) carrys out by the getShareableInterfaceObject () method calling App application shared with the interface that requirement shares App application; 3) if App application allows to share, BackUpDataApp application is quoted the shared object of an acquisition App application.Namely BackUpDataApp application may have access to App application, BackUpDataApp application obtains all internal datas of App application by the getDataByte () method calling App application, be kept at the data backup district of oneself, after completing, data backup operation terminates.
After internal data has backed up, then delete original App application bag on JAVACARD, delete the JAVACARD inner structure after App application as shown in Figure 3.
On deletion JAVACARD after original App application bag, carry out the recovery operation of internal data.With reference to Fig. 4, first, be loaded in JavaCard by the newApp application bag having repaired functional defect, after installing the success of newApp application example, its structure as shown in Figure 4.
Internal data restoration methods is substantially identical with internal data backup method, it is an inverse process of internal data backup method, all share interface by BackUpDataInterface to realize across the mode of application access, in this JAVACARD, the recovery flow process of App application internal data comprises, 1) the shared interface applied by JCSystem.getAppletShareableInterfaceObject () the way access BackUpDataApp of calling system of newApp application request; 2) due to newApp application, JCRE carrys out by the getShareableInterfaceObject () method calling BackUpDataApp application shared with the interface that requirement shares BackUpDataApp; 3) if BackUpDataApp application allows to share, newApp applies quoting the shared object of an acquisition BackUpDataApp, so namely newApp application may have access to BackUpDataApp application, newApp application obtains all Backup Datas of BackUpDataApp application by the getDataByte () method calling BackUpDataApp, and being write corresponding data field, data restore operation completes.
Wherein, in JAVACARD in the present invention, the backup of App application internal data and restoration methods comprise the backup and the recovery that are realized data by shared interface across application access mode, and App application internal data backs up and before recovery operation in JAVACARD, also comprise authenticating step, this authenticating step comprises the step adopting key encryption and decryption technology to do certification, certification is by then allowing access internal data, and authentification failure then refuses its access.
In order to the security that the internal data of some sensitivities is preserved, internal data backup area of the present invention is preferably present in JavaCard inside, can certainly be present in other system or equipment buffer memory.
In JAVACARD of the present invention, the backup of App application internal data and restoration methods achieve the safety to App application internal data in JAVACARD, efficient backup and recovery, avoid the waste of data resource, and the card that fabrication brings again is wasted, and effectively raises the remediation efficiency to App in JAVACARD.
Claims (10)
1. the backup of App application internal data and restoration methods in a JAVACARD, it is characterized in that, the method comprises, exploitation BackUpDataApp application, utilize this BackUpDataApp to apply obtain App application internal data and back up it, delete App application bag, be loaded into newApp application bag, and newApp application is installed, utilize newApp to apply acquisition backed up the internal data in BackUpDataApp application before this and write newApp corresponding region, realize the recovery operation to App application internal data in JAVACARD.
2. method according to claim 1, it is characterized in that, wherein, in JAVACARD, App application achieves BackUpDataInterface and shares interface, and the exploitation of BackUpDataApp application shares interface exploitation according to BackUpDataInterface, in internal data backup procedure, described BackUpDataApp application is shared interface and App by BackUpDataInterface and is applied and engage in the dialogue; BackUpDataApp application also achieves BackUpDataInterface and shares interface, and the exploitation of newApp application shares interface exploitation according to BackUpDataInterface, in internal data rejuvenation, described newApp application shares interface by BackUpDataInterface and BackUpDataApp engages in the dialogue.
3. method according to claim 1, it is characterized in that, wherein in JAVACARD, the backup flow process of App application internal data comprises, and 1) utilize BackUpDataApp application request to access the shared interface of App application by the JCSystem.getAppletShareableInterfaceObject () called in JAVACARD system; 2) due to BackUpDataApp application, JCRE (JavaCardRuntimeEnvironment) carrys out by the getShareableInterfaceObject () method calling App application shared with the interface that requirement shares App application; 3) if App application allows to share, BackUpDataApp application is quoted the shared object of an acquisition App application, namely BackUpDataApp application may have access to App application, BackUpDataApp application obtains all internal datas of App application by the getDataByte () method calling App application, be kept at the data backup district of oneself, after completing, data backup operation terminates.
4. method according to claim 1, it is characterized in that, in JAVACARD, the recovery flow process of App application internal data comprises, 1) the shared interface applied by JCSystem.getAppletShareableInterfaceObject () the way access BackUpDataApp of calling system of newApp application request; 2) due to newApp application, JCRE carrys out by the getShareableInterfaceObject () method calling BackUpDataApp application shared with the interface that requirement shares BackUpDataApp; 3) if BackUpDataApp application allows to share, newApp applies quoting the shared object of an acquisition BackUpDataApp, so namely newApp application may have access to BackUpDataApp application, newApp application obtains all Backup Datas of BackUpDataApp application by the getDataByte () method calling BackUpDataApp, and being write corresponding data field, data restore operation completes.
5. method as claimed in one of claims 1-4, it is characterized in that, App application internal data backs up and before recovery operation in JAVACARD, also comprise authenticating step, this authenticating step comprises the step adopting key encryption and decryption technology to do certification, certification is by then allowing access internal data, and authentification failure then refuses its access.
6. method as claimed in one of claims 1-4, is characterized in that, described internal data backup operation and described internal data recovery operation all comprise the backup and the recovery that are realized internal data by shared interface across application access mode.
7. method as claimed in one of claims 1-4, is characterized in that, internal data backup area is present in JavaCard inside.
8. method as claimed in one of claims 1-4, is characterized in that, internal data backup area is not got rid of and is present in other system or equipment buffer memory.
9. method as claimed in one of claims 1-4, it is characterized in that, wherein, the App application in JAVACARD comprises multiple from each in the different applet App application of different supplier, and this different applet App is isolated by fire wall between applying.
10. method as claimed in one of claims 1-4, is characterized in that, the App application in described JAVACARD is the App application with functional defect, and described newApp is the App application of having repaired functional defect.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510656798.XA CN105302666A (en) | 2015-10-13 | 2015-10-13 | JAVA CARD based backup and recovery method for data in application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510656798.XA CN105302666A (en) | 2015-10-13 | 2015-10-13 | JAVA CARD based backup and recovery method for data in application |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105302666A true CN105302666A (en) | 2016-02-03 |
Family
ID=55199958
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510656798.XA Pending CN105302666A (en) | 2015-10-13 | 2015-10-13 | JAVA CARD based backup and recovery method for data in application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105302666A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109144775A (en) * | 2018-06-30 | 2019-01-04 | 深圳市文鼎创数据科技有限公司 | Application data backup restoration method, electronic equipment and the storage medium of smart card |
| CN109446785A (en) * | 2018-10-15 | 2019-03-08 | 江苏恒宝智能系统技术有限公司 | A kind of memory management method of smart card and its personal data |
| CN109445815A (en) * | 2018-10-15 | 2019-03-08 | 江苏恒宝智能系统技术有限公司 | A kind of smart card and its application upgrade method |
| CN109819018A (en) * | 2018-12-29 | 2019-05-28 | 飞天诚信科技股份有限公司 | A kind of hot update method that realizing smart card executable file and device |
| CN110166452A (en) * | 2019-05-21 | 2019-08-23 | 东信和平科技股份有限公司 | A kind of access control method and system based on JavaCard shared interface |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1338069A (en) * | 1999-01-22 | 2002-02-27 | 太阳微系统公司 | Techniques for implementing security on a small footprint device using a context barrier |
| US20100077392A1 (en) * | 2006-12-01 | 2010-03-25 | Kian Teck Soh | Cap file for the personalization of a java application |
| US7942313B1 (en) * | 1998-10-09 | 2011-05-17 | Diebold, Incorporated | Automated banking machine system and monitoring method |
| US20110126183A1 (en) * | 2008-07-21 | 2011-05-26 | Eddy Bernard | Loading and updating an application requiring personalization |
| CN103761126A (en) * | 2014-01-07 | 2014-04-30 | 中国神华能源股份有限公司 | Method and device for upgrading application program |
| US20150193221A1 (en) * | 2014-01-06 | 2015-07-09 | Apple Inc. | On-board applet migration |
| CN105187410A (en) * | 2015-08-18 | 2015-12-23 | 深圳市雪球科技有限公司 | Application self-upgrading method and system |
-
2015
- 2015-10-13 CN CN201510656798.XA patent/CN105302666A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7942313B1 (en) * | 1998-10-09 | 2011-05-17 | Diebold, Incorporated | Automated banking machine system and monitoring method |
| CN1338069A (en) * | 1999-01-22 | 2002-02-27 | 太阳微系统公司 | Techniques for implementing security on a small footprint device using a context barrier |
| US20100077392A1 (en) * | 2006-12-01 | 2010-03-25 | Kian Teck Soh | Cap file for the personalization of a java application |
| US20110126183A1 (en) * | 2008-07-21 | 2011-05-26 | Eddy Bernard | Loading and updating an application requiring personalization |
| US20150193221A1 (en) * | 2014-01-06 | 2015-07-09 | Apple Inc. | On-board applet migration |
| CN103761126A (en) * | 2014-01-07 | 2014-04-30 | 中国神华能源股份有限公司 | Method and device for upgrading application program |
| CN105187410A (en) * | 2015-08-18 | 2015-12-23 | 深圳市雪球科技有限公司 | Application self-upgrading method and system |
Non-Patent Citations (1)
| Title |
|---|
| 徐宏宁: "JCRE平台结构的研究与设计", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109144775A (en) * | 2018-06-30 | 2019-01-04 | 深圳市文鼎创数据科技有限公司 | Application data backup restoration method, electronic equipment and the storage medium of smart card |
| CN109446785A (en) * | 2018-10-15 | 2019-03-08 | 江苏恒宝智能系统技术有限公司 | A kind of memory management method of smart card and its personal data |
| CN109445815A (en) * | 2018-10-15 | 2019-03-08 | 江苏恒宝智能系统技术有限公司 | A kind of smart card and its application upgrade method |
| CN109446785B (en) * | 2018-10-15 | 2019-11-08 | 江苏恒宝智能系统技术有限公司 | A kind of memory management method of smart card and its personal data |
| CN109819018A (en) * | 2018-12-29 | 2019-05-28 | 飞天诚信科技股份有限公司 | A kind of hot update method that realizing smart card executable file and device |
| CN109819018B (en) * | 2018-12-29 | 2021-06-08 | 飞天诚信科技股份有限公司 | Method and device for realizing hot updating of executable file of smart card |
| CN110166452A (en) * | 2019-05-21 | 2019-08-23 | 东信和平科技股份有限公司 | A kind of access control method and system based on JavaCard shared interface |
| CN110166452B (en) * | 2019-05-21 | 2022-03-04 | 东信和平科技股份有限公司 | Access control method and system based on JavaCard shared interface |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104995627B (en) | Cipher key revocation in system-on-chip apparatus | |
| CN105302666A (en) | JAVA CARD based backup and recovery method for data in application | |
| CN103970585B (en) | Create the method and device of virtual machine | |
| CN105556478A (en) | Systems and methods for protecting virtual machine data | |
| CN102073560A (en) | Data backup method and device | |
| JP2006119901A (en) | Portable electronic apparatus and application updating method for the portable electronic apparatus | |
| CN108027757A (en) | Recover the system and method for data for never transparent data backup stream | |
| US8983072B2 (en) | Portable data carrier featuring secure data processing | |
| CN108804913B (en) | Application program running method and device | |
| CN106681865B (en) | Service recovery method and device | |
| CN105022678A (en) | Data backup method and apparatus for virtual machine | |
| CN105630965A (en) | System and method for securely deleting file from user space on mobile terminal flash medium | |
| CN116610498B (en) | Data backup and recovery method, system, equipment and medium based on object storage | |
| CN105550071B (en) | System file upgrades and detection method, communication equipment | |
| CN105159797A (en) | Oracle database based backup and recovery method | |
| CN107066346A (en) | A kind of data back up method, data reconstruction method and device | |
| CN104361297B (en) | A kind of file encryption-decryption method based on (SuSE) Linux OS | |
| CN104866504B (en) | A kind of method and device that Function Extension is carried out to Android software | |
| CN105955773A (en) | System upgrading method and device | |
| US8972745B2 (en) | Secure data handling in a computer system | |
| CN104680040A (en) | Software loading number and activation control method and system | |
| CN106951771B (en) | Mobile terminal using method of android operating system | |
| CN105786641A (en) | Method, equipment and intelligent card for back-upping and recovery of intelligent card application data | |
| CN110955525B (en) | Network definition storage method, network definition reading method and network definition reading system based on FPGA (field programmable Gate array) equipment | |
| WO2015116204A1 (en) | Encrypted in-place operating system migration |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB03 | Change of inventor or designer information |
Inventor after: Liu Lei Inventor after: Lin Weijiang Inventor after: Zhou Xiangtao Inventor after: Zhang Hanjiu Inventor after: Zhang Xiaochuan Inventor before: Liu Lei Inventor before: Lin Weijiang Inventor before: Zhou Xiangtao Inventor before: Zhang Hanjiu |
|
| COR | Change of bibliographic data | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160203 |
|
| RJ01 | Rejection of invention patent application after publication |