An object management method and smart card application system

By introducing object management methods into the smart card operating system and using the object registry to store the mapping relationship between object references and application variable addresses, the problem of global variable data being lost after the device is powered off in C language development is solved, and the effect of being able to access object data even after the device is powered off is achieved.

CN119806498BActive Publication Date: 2026-11-17GUANGDONG CHUTIAN DRAGON SMART CARD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202411801297.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-12-09
Publication Date
2026-11-17
Estimated Expiration
2044-12-09

AI Technical Summary

Technical Problem

In existing technologies, smart card applications developed in C language cannot retain data in global variables after the device is powered off, resulting in the data being unusable after the system restarts.

Method used

By introducing object management methods into the smart card operating system, the mapping relationship between object references and application variable addresses is stored in the object registry, enabling the application to access RAM and Flash data and restore object references even after the device loses power.

Benefits of technology

This ensures that object references are not lost after a power outage and that object data can still be accessed after power is restored. It also expands the ways to use global variables and solves the problem of data preservation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119806498B_ABST
    Figure CN119806498B_ABST
Patent Text Reader

Abstract

This application relates to the field of smart card development technology, and discloses an object management method and a smart card application system. The method includes: when an object needs to be accessed, the application calls the operating system's object access interface and sends an object reference to the operating system through the object access interface. This allows the operating system to retrieve the object reference corresponding to the current application variable address from the object registry based on the application variable address, and then access the corresponding object based on the object reference. When the application starts, the operating system retrieves the saved object registry and obtains the object references corresponding to each application variable address based on the application variable addresses in the object registry. When the object access interface is called by the application, the object is accessed based on the object reference passed through the object access interface. This application ensures that object references are not lost even when the device is powered off, and object data can be directly accessed after power is restored.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This 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 Technology

[0002] In existing technologies, in smart card applications developed in C language, application-defined global variables are stored in RAM (random access memory). Applications can only access RAM data (data in random access memory) through global variables, but cannot access Flash data (data in flash memory). Furthermore, once the device running the application loses power, the data in the global variables will revert to its initial value. That is, the data written during device operation will not be saved. This means that after the system restarts, it is impossible to use global variables to access the data written during the last device operation, which brings great trouble to application development in accessing data. Summary of the Invention

[0003] In view of this, embodiments of this application provide an object management method and a smart card application system, which can access both RAM data and flash data through application variables, and the object references will not be lost when the device is powered off, and the object data can be directly accessed after power is restored.

[0004] In a first aspect, embodiments of this application provide an object management method applied to a smart card operating system, the smart card operating system including an object access interface, the method comprising:

[0005] When the application starts, it retrieves the saved object registry and obtains the object references corresponding to each application variable address based on the application variable addresses in the object registry.

[0006] 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.

[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, the saved object registry 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 written into the object registry.

[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 an object reference in the object data structure are created for the current object according to the object parameters passed by the object creation interface. The object reference is then sent back to the application so that the application can save 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, the object reference corresponding to the application variable address is obtained from the object registry according to the application variable address passed in by the object deletion interface;

[0013] Perform a deletion operation 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 state.

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

[0016] The object data structure of the current object is determined based on the object reference;

[0017] Delete the current object based on 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.

[0018] In some embodiments, the type of the object includes a permanent object, a DTR object, and an RTR object.

[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 based on the object parameters passed from the object creation interface, the method further includes:

[0021] Storage space is allocated to the current corresponding object based on the object type and object size in the object parameters.

[0022] Secondly, embodiments of this application provide an object management method applied to a smart card application, comprising:

[0023] The system invokes the operating system's object access interface and sends an object reference to the operating system through the object access interface, so that the operating system can access the object corresponding to the object reference based on the object reference.

[0024] Thirdly, embodiments of this application provide a smart card application system, including: an application terminal and an operating system;

[0025] The application is used to execute the object management method described above.

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

[0027] The embodiments of this application have the following beneficial effects: In this application, object references are stored in global variables, and the object registry stores the mapping relationship between object references and application variable addresses. When an object needs to be accessed, the application calls the operating system's object access interface 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 still be accessed after power is restored. Attached Figure Description

[0028] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0029] Figure 1 This paper illustrates a first flowchart of an object management method according to an embodiment of the present application.

[0030] Figure 2 This illustration shows a second flowchart of the object management method according to an embodiment of this application;

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

[0032] Figure 4 The diagram illustrates the fourth process flow of the object management method according to an embodiment of this application. Detailed Implementation

[0033] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0034] The components of the embodiments of this application described and illustrated in the accompanying drawings can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of this application provided in the drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0035] In the following text, the terms "comprising," "having," and their cognates, which may be used in various embodiments of this application, are intended only to indicate a particular feature, number, step, operation, element, component, or combination thereof, and should not be construed as primarily excluding the presence of one or more other features, numbers, steps, operations, elements, components, or combinations thereof, or adding the possibility of one or more combinations thereof. Furthermore, the terms "first," "second," "third," etc., are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance.

[0036] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of this application pertain. Terms (such as those defined in commonly used dictionaries) shall be interpreted as having the same meaning as in their contextual meaning in the relevant technical field and shall not be construed as having an idealized or overly formal meaning, unless clearly defined in the various embodiments of this application.

[0037] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0038] In existing smart card applications developed using C language, application-defined global variables are stored in RAM (Random Access Memory). Applications can only access RAM data (data in RAM) through these global variables, but cannot access Flash data (data in flash memory). Furthermore, once the device running the application loses power, the data in the global variables reverts to its initial value; that is, data written during device operation is not saved. This means that after a system restart, the global variables cannot be used to access data written during the last device operation, causing significant difficulties for application development in accessing data. Based on this, this application proposes an object management method and a smart card application system that allows applications to access both RAM and Flash data, and the data in the global variables is not lost after a power outage; the data in the application can be restored after a device restart.

[0039] The following examples illustrate the object management method.

[0040] Before describing the following embodiments, the operating system of this embodiment will be described first. This 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 by the application to send object creation information to the operating system when a new object needs to be created, so that the operating system can create the corresponding object. The object registration interface is used by the application to send object registration information to the operating system when an object needs to be registered, so that the operating system can register the corresponding object. The object access interface is used by the application to send access information to the operating system when it needs to access an object, so that the operating system can access the corresponding object. The object deletion interface is used by the application to send deletion information to the operating system when an application needs to be deleted, so that the operating system can perform a deletion operation on the corresponding object.

[0041] Figure 1 A flowchart illustrating an object management method according to an embodiment of this application is shown. Exemplarily, this object management method is applicable to interactions between an application and an operating system to manage objects. The object management method includes the following steps:

[0042] Step S10: When the application starts, obtain the saved object registry, and obtain the object references corresponding to each application variable address based on the application variable addresses in the object registry.

[0043] The object registry is a table formed by establishing a mapping relationship between object references and application variable addresses. An object reference is a pointer or index to an object instance; it does not directly contain all the object's data, but rather points to the actual stored object.

[0044] The object reference is stored in the application variable, which is a global variable.

[0045] As an example, each time the application starts, the operating system retrieves information from the saved object registry and restores object references in application variables, allowing the application to directly access already created objects through these application variables. For the application, the object only needs to be created once, and can be accessed multiple times thereafter.

[0046] Step S11: Call the operating system's object access interface and send an object reference to the operating system through the object access interface.

[0047] As an example, 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] For example, 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 object to be accessed can be accessed based on 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 object registry stores the mapping relationship between the object reference and the address of the application variable. 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 still be accessed after power is restored.

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

[0052] Step S13: Call the operating system's object registration interface and send 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, the saved object registry 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 written into the object registry.

[0054] As an example, when a new object needs to be registered, the application calls the object registration interface provided by the operating system, and then sends the object to be registered to the operating system through this interface. When the application calls the operating system's object registration interface, the operating system responds to the call instruction by retrieving the object registry stored in the operating system, so that the mapping relationship between the corresponding object reference and the application variable address can be written into the object registry during object registration.

[0055] Object references are reference variables created for each object when the operating system creates an object. Application variables are variables created by the application for the corresponding object when the object is created, and a corresponding application variable address is assigned to that application variable after its creation.

[0056] After the operating system receives the object to be registered sent by the application through the object registration interface, it can determine the corresponding object reference and application variable address based on the object. Then, it writes the mapping relationship between the corresponding object reference and application variable address into the object registry so that subsequent access operations on the object can be performed through the object reference.

[0057] Step S10: When the application starts, obtain the saved object registry, and obtain the object references corresponding to each application variable address based on the application variable addresses in the object registry.

[0058] Step S11: Call the operating system's object access interface and send 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] Steps S10, S11, and S12 are the same as in the above embodiments and will not be repeated here.

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

[0062] Step S15: Call the operating system's object creation interface and send the corresponding parameters to the operating system through the object creation interface.

[0063] Step S16: When the object creation interface is called by the application, 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.

[0064] Step S17: Receive the corresponding object reference sent by the operating system and save the corresponding object reference to the corresponding application variable.

[0065] As an example, when an object needs to be created, the application sends object parameters to the operating system by calling the object creation interface provided by the operating system. These object parameters include, but are not limited to, object type and object size. Object types include permanent objects, DTR (Clear-On-Deselect RAM) objects, and RTR (Clear-On-Reset RAM) objects. Permanent objects are flash data, while DTR and RTR objects are RAM data; that is, this embodiment can create any type of object.

[0066] After receiving the object parameters sent by the application through the object creation interface, the operating system creates an object data structure for the current object based on these parameters. This object data structure is mainly used to record object-related information, including but not limited to object type, object state (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 creating the object data structure for the current object, the operating system also needs to create a corresponding object reference for this 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: Call the operating system's object registration interface and send 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, the saved object registry 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 written into the object registry to establish the correspondence between the object reference and the application variable address.

[0070] Step S10: When the application starts, obtain the saved object registry, and obtain the object references corresponding to each application variable address based on the application variable addresses in the object registry.

[0071] Step S11: Call the operating system's object access interface and send 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] Steps S10, S11, S12, S13 and S14 are the same as in the above embodiments, and will not be repeated here.

[0074] In this embodiment, when an object is created, the operating system creates an object data structure corresponding to the object and an object reference corresponding to the object data structure. This object reference is then sent back to the application. Upon receiving the object reference, the application saves it to the corresponding application variable. When registering an object, the application sends the object reference corresponding to the object to be registered to the operating system. The operating system then maps this object reference to the address of the application variable storing the object reference and writes it to the object registry. This establishes a correspondence between the object data structure and the application variable, allowing the access to the object information to be obtained directly from the application variable when accessing the object.

[0075] Furthermore, the objects in this application can be permanent objects, DTR objects, or RTR objects; that is, each object type is applicable to the method of this embodiment. Compared to the limitation of existing C language application variables that can only access RAM data, this embodiment can achieve access to both RAM data and flash data through application variables.

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

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

[0078] Step S15: Call the operating system's object creation interface and send the corresponding parameters to the operating system through the object creation interface.

[0079] Step S16: When the object creation interface is called by the application, 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.

[0080] Step S17: Receive the corresponding object reference sent by the operating system and save the corresponding object reference to the corresponding application variable.

[0081] Step S13: Call the operating system's object registration interface and send 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, the saved object registry 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 written into the object registry.

[0083] Step S10: When the application starts, obtain the saved object registry, and obtain the object references corresponding to each application variable address based on the application variable addresses in the object registry.

[0084] Step S11: Call the operating system's object access interface and send 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 in the above embodiments, and will not be repeated here.

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

[0088] Step S18: Call the operating system's object deletion interface and send 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, the object reference corresponding to the application variable address is obtained from the object registry based on the application variable address passed in by the object deletion interface.

[0090] Step S20: Perform a deletion operation on the current object based on the object reference.

[0091] As an example, when an object needs to be deleted, the application sends the application variable address of the object to be deleted to the operating system by calling the object deletion interface provided by the operating system. After receiving the application variable address of the object to be deleted, the operating system 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] Specifically, performing a deletion operation on the current object based on an object reference includes:

[0093] The object data structure of the current object is determined based on the object reference; the current object is deleted based on the object information in the object data structure, and the mapping relationship between the object reference and the application variable address corresponding to the current object in the object registry is also determined, and the storage space of the current object is released. 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 can be released. In addition, when deleting an 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.

[0094] Based on the above embodiments, this embodiment can also perform deletion operations on the corresponding objects, thereby realizing the management of the entire lifecycle of the objects.

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

[0096] This application also provides a smart card that includes the aforementioned smart card application system.

[0097] The application terminal and operating system of this smart card application system both include a processor and a memory. The memory stores computer programs, and the processor executes the computer programs to enable the smart card to perform the object management method described above.

[0098] The processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, including at least one of a Central Processing Unit (CPU), Graphics Processing Unit (GPU), Network Processor (NP), Digital Signal Processor (DSP), Application-Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application.

[0099] The memory can be, but is not limited to, Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc. The memory is used to store computer programs, and the processor can execute the computer programs accordingly after receiving execution instructions.

[0100] This application also provides a computer-readable storage medium for storing the computer program used in the aforementioned terminal device. For example, the computer-readable storage medium may include, but is not limited to, various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0101] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that, in alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

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

[0103] If the aforementioned functions are implemented as software functional 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 this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a smartphone, personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0104] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. An object management method, characterized in that, A smart card operating system developed using the C language, the smart card operating system including an object creation interface, an object registration interface, and an object access interface, the method including: When the object creation interface is called by the application, an object data structure and an object reference of the object data structure are created for the current object based on the object parameters passed to the object creation interface. The object reference is then sent back to the application so that the application can save the object reference to the corresponding application variable. The application variable is a global variable. The object parameters include the object type and the object size. The object type includes permanent objects, DTR objects, and RTR objects. The permanent object is flash data, and the DTR and RTR objects are RAM data. Before the step of creating an object data structure for the current object based on the object parameters passed from the object creation interface, the method further includes: allocating storage space for the current corresponding object according to the object type and object size in the object parameters; wherein, if the object type is a permanent object, then flash space is allocated for the current object; if the object type is a DTR object, then DTR space is allocated for the object; if the object type is an RTR object, then RTR space is allocated for the object. When the object registration interface is called by the application, the saved object registry is obtained, and the object reference passed in by the object registration interface and the application variable address storing the object reference are written into the object registry. The object registry is a table formed after establishing a mapping relationship between object references and application variable addresses. An object reference is a pointer or index pointing to an object instance. The object reference does not contain all the data of the object, but points to the actual stored object. When the application starts, it retrieves the saved object registry and obtains the object references corresponding to each application variable address based on the application variable addresses in the object registry. Each time the application starts, the operating system retrieves the information in the saved object registry and restores the object references in the application variables, so that the application can directly access the created objects through the application variables. 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.

2. The object management method according to claim 1, characterized in that, The smart card operating system also includes an object deletion interface, and the method further includes: When the object deletion interface is called by the application, the object reference corresponding to the application variable address is obtained from the object registry according to the application variable address passed in by the object deletion interface; Perform a deletion operation on the current object based on the object reference.

3. The object management method according to claim 1, 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.

4. The object management method according to claim 3, characterized in that, The step of performing a deletion operation on the current object based on the object reference includes: The object data structure of the current object is determined based on the object reference; Delete the current object based on 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.

5. An object management method, characterized in that, Applications in smart card applications include: The system invokes the operating system's object access interface and sends an object reference to the operating system through the object access interface, so that the operating system can access the corresponding object based on the object reference; wherein the operating system is a smart card operating system developed in C language as described in any one of claims 1-4.

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

Citation Information

Patent Citations

  • JAVA intelligent card structure and object management method thereof

    CN105653464A

  • Java card and temporary object management method thereof

    CN110287695A