Object management method and intelligent card application system

Abstract

The invention relates to the technical field of intelligent card development, and discloses an object management method and an intelligent card application system.The method comprises the steps that when an object needs to be accessed, an application end calls an object access interface of an operating system and sends object reference to the operating system through the object access interface, the operating system obtains the object reference corresponding to the current application variable address from the object registry according to the application variable address, and the operating system accesses the corresponding object according to the object reference. When the application end is started, the operating system obtains the stored object registry and obtains object references corresponding to the application variable addresses based on the application variable addresses in the object registry; and when the object access interface is called by the application end, the access object is referenced according to the object introduced by the object access interface. According to the method and the device, the object reference cannot be lost under the condition that the equipment is powered off, and the object data can be directly accessed after the equipment is powered on again.

Description

Technical Field

[0001] The present application relates to the field of smart card development technology, and in particular to an object management method and a smart card application system. Background Art

[0002] In the prior art, in smart card applications developed in C language, global variables defined by the application are stored in RAM (random access memory). The application can only access RAM data (data in random access memory) through global variables, but cannot access Flash data (data in flash memory). Once the device running the application is powered off, the data in the global variables will be restored to the initial value, that is, the data written when the device is running will not be saved. As a result, after the system is restarted, the global variables cannot be used to access the data written when the device was last running, which brings great trouble to application development and data access. Summary of the invention

[0003] In view of this, the embodiments of the present application provide an object management method and a smart card application system, which can realize access to both RAM data and flash data through application variables, and even when the device is powered off, the object reference will not be lost, and the object data can be directly accessed after powering on again.

[0004] In a first aspect, an embodiment of the present application provides an object management method, which is applied to a smart card operating system, wherein the smart card operating system includes an object access interface, and the method includes:

[0005] When the application is started, the saved object registry is obtained, and based on the application variable addresses in the object registry, the object references corresponding to the application variable addresses are obtained;

[0006] When the object access interface is called by the application end, the object is accessed according to the object reference passed in by the object access interface.

[0007] In some embodiments, the smart card operating system further includes an object registration interface; the method further includes:

[0008] When the object registration interface is called by the application end, the saved object registration table is obtained, and the object reference of the object passed in by the object registration interface and the application variable address of the application variable storing the object reference are correspondingly written into the object registration table.

[0009] In some embodiments, the smart card operating system further includes: an object creation interface; the method further includes:

[0010] When the object creation interface is called by the application, an object data structure and the object reference of the object data structure are created for the current object according to the object parameters passed in by the object creation interface, and the object reference is returned to the application so that the application saves the object reference to the corresponding application variable.

[0011] In some embodiments, the smart card operating system further includes an object deletion interface, and the method further includes:

[0012] When the object deletion interface is called by the application end, the object reference corresponding to the application variable address is obtained from the object registration table according to the application variable address passed in by the object deletion interface;

[0013] A deletion operation is performed on the current object based on the object reference.

[0014] In some embodiments, the object data structure is used to record object information corresponding to the object; the object information includes object type, storage location and object status.

[0015] In some embodiments, the step of performing a deletion operation on the current object based on the object reference includes:

[0016] Determine the object data structure of the current object according to the object reference;

[0017] The current object is deleted according to the object information in the object data structure of the current object, and the mapping relationship between the object reference and the application variable address corresponding to the current object in the object registration table, and the storage space of the current object is released.

[0018] In some embodiments, the types of objects include permanent objects, DTR objects, and RTR objects.

[0019] In some embodiments, the object parameters include object type and object size;

[0020] Before the step of creating an object data structure for the current object according to the object parameters passed in by the object creation interface, the method further includes:

[0021] Allocate storage space for the current object according to the object type and the object size in the object parameters.

[0022] In a second aspect, an embodiment of the present application provides an object management method, which is applied to a smart card application end, including:

[0023] An object access interface of the operating system is called, and an object reference is sent to the operating system through the object access interface, so that the operating system accesses the object corresponding to the object reference according to the object reference.

[0024] In a third aspect, an embodiment of the present application provides a smart card application system, including: an application terminal and an operating system;

[0025] The application end is used to execute the above object management method;

[0026] The operating system is used to execute the above-mentioned object management method based on the interface call of the application end.

[0027] The embodiments of the present application have the following beneficial effects: in the present application, object references are stored in global variables, and the mapping relationship between object references and application variable addresses is stored in the object registry. When the object needs to be accessed, the application side calls the object access interface of the operating system and passes the application variable address to the operating system. The operating system can determine the object reference based on the application variable address, and then access the corresponding object based on the object reference. In this way, even if the device loses power, the object reference will not be lost, and the object data can be accessed after powering on again. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0029] Figure 1 A first flow chart of the object management method according to an embodiment of the present application is shown;

[0030] Figure 2 A second flow chart of the object management method according to an embodiment of the present application is shown;

[0031] Figure 3 A third flow chart of the object management method according to an embodiment of the present application is shown;

[0032] Figure 4 A fourth flow chart of the object management method according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0033] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments.

[0034] The components of the embodiments of the present application generally described and shown in the drawings herein may be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0035] Hereinafter, the terms "including", "having" and their cognates that can be used in various embodiments of the present application are intended only to indicate specific features, numbers, steps, operations, elements, components or a combination of the foregoing items, and should not be understood as first excluding the existence of one or more other features, numbers, steps, operations, elements, components or a combination of the foregoing items or increasing the possibility of one or more features, numbers, steps, operations, elements, components or a combination of the foregoing items. In addition, the terms "first", "second", "third" and the like are only used to distinguish descriptions and cannot be understood as indicating or implying relative importance.

[0036] Unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meanings as those generally understood by those skilled in the art to which the various embodiments of the present application belong. The terms (such as those defined in generally used dictionaries) will be interpreted as having the same meanings as the contextual meanings in the relevant technical field and will not be interpreted as having idealized meanings or overly formal meanings unless clearly defined in the various embodiments of the present application.

[0037] In conjunction with the accompanying drawings, some embodiments of the present application are described in detail below. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0038] In the smart card application developed in C language of the prior art, the global variables defined by the application are stored in RAM (random access memory). The application can only access RAM data (data in random access memory) through global variables, but cannot access Flash data (data in flash memory). Once the device running the application is powered off, the data in the global variables will be restored to the initial value, that is, the data written when the device is running will not be saved. This means that after the system is restarted, the global variables cannot be used to access the data written when the device was last running, which brings great trouble to application development and data access. Based on this, the present application proposes an object management method and a smart card application system, which enables the application to access RAM data and Flash data, and the data in the global variables will not be lost after the device is powered off. After the device is restarted, the data in the application can be restored.

[0039] The object management method is described below in conjunction with some specific embodiments.

[0040] Before describing the following embodiments, the operating system of the present embodiment is described first. The operating system includes an object creation interface, an object registration interface, an object access interface, and an object deletion interface. The object creation interface is used when a new object needs to be created, and the application side sends information about creating the object to the operating system by calling the object creation interface, so that the operating system creates the corresponding object. The object registration interface is used when an object needs to be registered, and the application side sends information about registering the object to the operating system by calling the object registration interface, so that the operating system registers the corresponding object. The object access interface is used when the application side needs to access an object, and the application side calls the object access interface and sends access information to the operating system, so that the operating system accesses the corresponding object. The object deletion interface is used when an application needs to be deleted, and the application side calls the object deletion interface and sends deletion information to the operating system, so that the operating system performs a deletion operation on the corresponding object.

[0041] Figure 1 A flow chart of an object management method of an embodiment of the present application is shown. Exemplarily, the object management method is applicable to the interaction between the application end and the operating system to implement object management, and the object management method includes the following steps:

[0042] Step S10: when the application is started, the saved object registration table is obtained, and the object reference corresponding to each application variable address is obtained based on the application variable address in the object registration table.

[0043] The object registry is a table formed by mapping object references to application variable addresses. An object reference is a pointer or index pointing to an object instance. It does not directly contain all the data of the object, but points to the actual stored object.

[0044] Among them, the object reference is stored in the application variable, and the application variable is a global variable.

[0045] For example, each time the application is started, the operating system obtains the information in the object registry through the saved object registry, restores the object reference in the application variable, and enables the application to directly access the created object through the application variable. For the application, it only needs to create an object once, and then it can access the object multiple times.

[0046] Step S11, calling the object access interface of the operating system, and sending an object reference to the operating system through the object access interface.

[0047] Exemplarily, when the application needs to access the target object, it calls the object access interface provided by the operating system and sends the application variable address to the operating system through the object access interface.

[0048] Step S12: when the object access interface is called by the application, the object is accessed according to the object reference passed in by the object access interface.

[0049] Exemplarily, since the object registry stores the mapping relationship between application variable addresses and object references, after receiving the object reference sent by the application through the object access interface, the access operation can be performed on the object to be accessed according to the object reference, and the access operation result of the target object can be returned to the application after the access operation is completed.

[0050] In this embodiment, the object reference is stored in the application variable, and the mapping relationship between the object reference and the application variable address is stored in the object registry. When the object needs to be accessed, the application calls the object access interface of the operating system and passes the object reference to the operating system. The operating system accesses the object corresponding to the object reference based on the object reference. In this way, even if the device loses power, the object reference will not be lost, and the object data can be accessed after power is restored.

[0051] In some embodiments, Figure 2 As shown, the object management methods include:

[0052] Step S13: calling the object registration interface of the operating system, and sending the corresponding object to the operating system through the object registration interface.

[0053] Step S14, when the object registration interface is called by the application end, the saved object registration table is obtained, and the object reference of the object passed in by the object registration interface and the application variable address of the application variable storing the object reference are correspondingly written into the object registration table.

[0054] Exemplarily, when a new object needs to be registered, the application side calls the object registration interface provided by the operating system, and then sends the object to be registered to the operating system through the object registration interface. When the application side calls the object registration interface of the operating system, the operating system responds to the calling instruction and obtains the object registration table stored in the operating system, so as to write the mapping relationship between the corresponding object reference and the application variable address into the object registration table when the object is registered.

[0055] Among them, the object reference is the reference variable created for each object when the operating system creates the object. The application variable is the variable created by the application side for the corresponding object when the object is created, and after the application variable is created, the corresponding application variable address is assigned to the application variable.

[0056] After the operating system receives the object to be registered sent by the application through the object registration interface, the corresponding object reference and application variable address can be determined based on the object, and then the mapping relationship between the corresponding object reference and application variable address is written into the object registration table so that the object access operation can be performed subsequently through the object reference.

[0057] Step S10: when the application is started, the saved object registration table is obtained, and the object reference corresponding to each application variable address is obtained based on the application variable address in the object registration table.

[0058] Step S11, calling the object access interface of the operating system, and sending an object reference to the operating system through the object access interface.

[0059] Step S12: when the object access interface is called by the application, the object is accessed according to the object reference passed in by the object access interface.

[0060] Among them, steps S10, S11 and S12 are the same as those in the above embodiment and will not be described again.

[0061] In some embodiments, Figure 3 As shown, the object management methods include:

[0062] Step S15, calling the object creation interface of the operating system, and sending corresponding parameters to the operating system through the object creation interface.

[0063] Step S16, when the object creation interface is called by the application end, an object data structure and an object reference of the object data structure are created for the current object according to the object parameters passed in by the object creation interface, and the object reference is returned to the application end.

[0064] Step S17, receiving the corresponding object reference sent by the operating system, and saving the corresponding object reference to the corresponding application variable.

[0065] Exemplarily, when an object needs to be created, the application side calls the object creation interface provided by the operating system to send the object parameters of the object to be created to the operating system. The object parameters include, but are not limited to, the object type and the object size; the object types include permanent objects, DTR (CLEAR_ON_DESELECT RAM, cancel clear RAM) objects, and RTR (CLEAR_ON_RESET RAM, reset clear RAM) objects, wherein permanent objects are flash data, and DTR objects and RTR objects are RAM data, that is, this embodiment can create any type of object.

[0066] After the operating system receives the object parameters sent by the application through the object creation interface, it creates an object data structure for the current object based on the object parameters. The object data structure is mainly used to record object-related information, including but not limited to object type, object status (such as whether it is registered, whether it is accessible, etc.), object storage location and other metadata (such as creation time, last access time, etc.). After the operating system creates the object data structure for the current object, it also needs to create a corresponding object reference for the object data structure, and then send the created corresponding object reference to the application. After receiving the object reference, the application saves the object reference to the corresponding application variable.

[0067] In addition, after the operating system receives the object parameters sent by the application through the object creation interface, it also allocates storage space for the corresponding object according to the object type and object size in the object parameters. For example, if the object type is a permanent object, flash space is allocated for the current object; if the object type is a DTR object, DTR space is allocated for the object; if the object type is an RTR object, RTR space is allocated for the object.

[0068] Step S13: calling the object registration interface of the operating system, and sending the corresponding object to the operating system through the object registration interface.

[0069] Step S14, when the object registration interface is called by the application end, the saved object registration table is obtained, and the object reference of the object passed in by the object registration interface and the application variable address of the application variable storing the object reference are correspondingly written into the object registration table to establish a corresponding relationship between the object reference and the application variable address.

[0070] Step S10: when the application is started, the saved object registration table is obtained, and the object reference corresponding to each application variable address is obtained based on the application variable address in the object registration table.

[0071] Step S11, calling the object access interface of the operating system, and sending an object reference to the operating system through the object access interface.

[0072] Step S12: when the object access interface is called by the application, the object is accessed according to the object reference passed in by the object access interface.

[0073] Among them, steps S10, S11, S12, S13 and S14 are the same as those in the above embodiment and will not be repeated here.

[0074] In this embodiment, when creating an object, the operating system will create an object data structure corresponding to the object, and create an object reference corresponding to the object data structure, and then send the object reference back to the application end, which will save it to the corresponding application variable after receiving the object reference. When registering an object, the application end will send the object reference corresponding to the object to be registered to the operating system, and then the operating system will form a mapping relationship between the object reference and the application variable address of the application variable storing the object reference and then write it into the object registration table, so that the object data structure and the application variable form a corresponding relationship, so that when accessing the object, the object information of the object to be accessed can be directly obtained according to the application variable.

[0075] In addition, the object in the present application can be a permanent object, a DTR object or an RTR object, that is, each object type is applicable to the method of the present embodiment. Compared with the disadvantage that the application variables developed in the C language in the prior art can only access RAM data, the present embodiment can access not only RAM data but also flash data through application variables.

[0076] Furthermore, the object reference of this embodiment is mapped to the application variable address and saved in the object registry, so that the object reference of the object will not be lost even if the device (such as a smart card) loses power. The object data can be directly accessed after the device is powered on again, expanding the use of global variables in application development.

[0077] In some embodiments, Figure 4 As shown, the object management methods include:

[0078] Step S15, calling the object creation interface of the operating system, and sending corresponding parameters to the operating system through the object creation interface.

[0079] Step S16, when the object creation interface is called by the application end, an object data structure and an object reference of the object data structure are created for the current object according to the object parameters passed in by the object creation interface, and the object reference is returned to the application end.

[0080] Step S17, receiving the corresponding object reference sent by the operating system, and saving the corresponding object reference to the corresponding application variable.

[0081] Step S13: calling the object registration interface of the operating system, and sending the corresponding object to the operating system through the object registration interface.

[0082] Step S14, when the object registration interface is called by the application end, the saved object registration table is obtained, and the object reference of the object passed in by the object registration interface and the application variable address of the application variable storing the object reference are correspondingly written into the object registration table.

[0083] Step S10: when the application is started, the saved object registration table is obtained, and the object reference corresponding to each application variable address is obtained based on the application variable address in the object registration table.

[0084] Step S11, calling the object access interface of the operating system, and sending an object reference to the operating system through the object access interface.

[0085] Step S12: when the object access interface is called by the application, the object is accessed according to the object reference passed in by the object access interface.

[0086] Steps S10, S11, S12, S13, S14, S15, S16 and S17 are the same as those in the above embodiment and will not be described in detail here.

[0087] Based on the above steps, this embodiment also includes:

[0088] Step S18, calling the object deletion interface of the operating system, and sending the application variable address of the object to be deleted to the operating system through the object deletion interface.

[0089] Step S19: when the object deletion interface is called by the application end, the object reference corresponding to the application variable address is obtained from the object registration table according to the application variable address passed in by the object deletion interface.

[0090] Step S20: performing a delete operation on the current object based on the object reference.

[0091] Exemplarily, when an object needs to be deleted, the application side calls the object deletion interface provided by the operating system to send the application variable address of the object to be deleted to the operating system. After the operating system receives the application variable address corresponding to the object to be deleted, it can obtain the object reference corresponding to the application variable address through the object registry, and then the operating system can perform the corresponding deletion operation on the corresponding object based on the corresponding object reference.

[0092] The deletion operation is performed on the current object based on the object reference, specifically including:

[0093] Determine the object data structure of the current object according to the object reference; delete the current object according to the object information in the object data structure of the current object, and the mapping relationship between the object reference and the application variable address corresponding to the current object in the object registry, and release the storage space of the current object. It can be understood that in this embodiment, after determining the object reference of the object to be deleted, the corresponding deletion operation can be performed on the corresponding object based on the corresponding object reference, and the space occupied by the corresponding object is released. In addition, when deleting the object, it is also necessary to delete the record containing the target variable in the object registry, and return the deletion operation result of the corresponding object to the application end.

[0094] On the basis of the above embodiment, this embodiment can also perform a deletion operation on the corresponding object, thereby realizing the management of the entire life cycle of the object.

[0095] The present application also provides a smart card application system, including: an application end and an operating system; the application end and the operating system are respectively used to execute the object management method in the above embodiment.

[0096] The present application also provides a smart card, which includes the above-mentioned smart card application system.

[0097] The application end and the operating system in the smart card application system both include a processor and a memory, wherein the memory stores a computer program, and the processor enables the smart card to execute the above-mentioned object management method by running the computer program.

[0098] Among them, the processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, including a central processing unit (CPU), a graphics processing unit (GPU) and a network processor (NP), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or at least one of other programmable logic devices, discrete gates or transistor logic devices, and discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc., which can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application.

[0099] The memory may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc. The memory is used to store a computer program, and the processor may execute the computer program accordingly after receiving an execution instruction.

[0100] The present application also provides a computer-readable storage medium for storing the computer program used in the above-mentioned terminal device. For example, the computer-readable storage medium may include, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0101] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and structure diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in an alternative implementation, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the structure diagram and / or the flow diagram, and the combination of boxes in the structure diagram and / or the flow diagram, can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0102] In addition, the functional modules or units in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0103] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a smart phone, a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application.

[0104] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. An object management method, characterized in that: Applied to a smart card operating system, the smart card operating system includes an object access interface, and the method includes: When the application is started, the saved object registry is obtained, and based on the application variable addresses in the object registry, the object references corresponding to the application variable addresses are obtained; When the object access interface is called by the application end, the object is accessed according to the object reference passed in by the object access interface.

2. The object management method according to claim 1, characterized in that: The smart card operating system also includes an object registration interface; the method also includes: When the object registration interface is called by the application end, the saved object registration table is obtained, and the object reference passed in by the object registration interface and the application variable address of the application variable storing the object reference are correspondingly written into the object registration table.

3. The object management method according to claim 2, characterized in that: The smart card operating system further includes: an object creation interface; the method further includes: When the object creation interface is called by the application, an object data structure and the object reference of the object data structure are created for the current object according to the object parameters passed in by the object creation interface, and the object reference is returned to the application so that the application saves the object reference to the corresponding application variable.

4. The object management method according to claim 1, characterized in that: The smart card operating system further includes an object deletion interface, and the method further includes: When the object deletion interface is called by the application end, the object reference corresponding to the application variable address is obtained from the object registration table according to the application variable address passed in by the object deletion interface; A deletion operation is performed on the current object based on the object reference.

5. The object management method according to claim 3, characterized in that: The object data structure is used to record object information corresponding to the object; the object information includes object type, storage location and object status.

6. The object management method according to claim 5, characterized in that: The step of performing a deletion operation on the current object based on the object reference comprises: Determine the object data structure of the current object according to the object reference; The current object is deleted according to the object information in the object data structure of the current object, and the mapping relationship between the object reference and the application variable address corresponding to the current object in the object registration table, and the storage space of the current object is released.

7. The object management method according to claim 1, characterized in that: The types of objects include permanent objects, DTR objects and RTR objects.

8. The object management method according to claim 3, characterized in that: The object parameters include object type and object size; Before the step of creating an object data structure for the current object according to the object parameters passed in by the object creation interface, the method further includes: Allocate storage space for the current object according to the object type and the object size in the object parameters.

9. An object management method, characterized in that: Applied to smart card application end, including: An object access interface of the operating system is called, and an object reference is sent to the operating system through the object access interface, so that the operating system accesses a corresponding object corresponding to the object reference according to the object reference.

10. A smart card application system, characterized in that: include: Application and operating system; The application end is used to execute the object management method according to claim 9; The operating system is used to execute the object management method described in any one of claims 1-8 based on the interface call of the application end.

Images