CN113347620A - Method, device, equipment and storage medium for compatibility of multi-version application air card issuing - Google Patents
Method, device, equipment and storage medium for compatibility of multi-version application air card issuing Download PDFInfo
- Publication number
- CN113347620A CN113347620A CN202110894679.3A CN202110894679A CN113347620A CN 113347620 A CN113347620 A CN 113347620A CN 202110894679 A CN202110894679 A CN 202110894679A CN 113347620 A CN113347620 A CN 113347620A
- Authority
- CN
- China
- Prior art keywords
- personalized data
- card
- data file
- application
- version information
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Abstract
The invention relates to the technical field of card issuing, and discloses a method, a device, equipment and a storage medium for issuing a multi-version application-compatible null card, wherein the method comprises the following steps: acquiring a user card opening request; determining target application version information of the current empty card issuing equipment according to the user card opening request; matching in a personalized data pool according to the target application version information to obtain a target personalized data file; and carrying out card opening operation according to the target personalized data file and the target application version information. Through the management and control of the application versions, the data pools of different versions are divided, so that the problem of incompatibility of multi-version application personalized data files is solved.
Description
Technical Field
The invention relates to the technical field of card issuing, in particular to a method, a device, equipment and a storage medium for issuing a card compatible with multi-version application.
Background
A Trusted Service Manager (TSM) is a system for realizing space management, application access and over-the-air card sending of a security module based on a one-card multi-application technology, and the TSM is divided into two types including a security module provider TSM (SEI-TSM) and a Service provider TSM (SP-TSM), wherein the SP-TSM can relate to downloading, installation, locking, unlocking and personalization operations of an application in the card sending process. At present, due to different application implementations of various manufacturers, migration in and migration out of an air card among different application versions are generally achieved by deploying a plurality of SP-TSM air distribution platforms to distinguish multi-version applications, but due to the fact that a plurality of air distribution platforms need to be deployed, maintenance and upgrading costs are high, deployed server resources are high in expenditure, and certain resource waste is caused.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a method, a device, equipment and a storage medium for compatibility of multi-version application empty issue, and aims to solve the technical problem that how to solve the problem of incompatibility of personalized data among multi-version applications without additionally adding server resources in the prior art.
In order to achieve the above object, the present invention provides a method for issuing a card over the air compatible with multiple versions of applications, which comprises the following steps:
acquiring a user card opening request;
determining target application version information of the current empty card issuing equipment according to the user card opening request;
matching in a personalized data pool according to the target application version information to obtain a target personalized data file;
and carrying out card opening operation according to the target personalized data file and the target application version information.
Optionally, before acquiring the user card opening request, the method further includes:
acquiring application version information of the empty card issuing equipment;
determining a personalized data file of a corresponding version according to the application version information;
and establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a personalized data pool for storage.
Optionally, after determining the personalized data file of the corresponding version according to the application version information, the method further includes:
acquiring project information in the personalized data file;
determining an attribute file of application version information according to the project information;
importing the personalized data file and the attribute file into a service provider platform so that the service provider platform judges whether the personalized data file corresponds to the application version information according to the attribute file;
and when the personalized data file corresponds to the application version information, establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a personalized data pool for storage.
Optionally, the importing the personalized data file and the attribute file to a service provider platform to enable the service provider platform to determine whether the personalized data file corresponds to the application version information according to the attribute file includes:
and importing the personalized data file and the attribute file into a service provider platform so that the service provider platform determines whether the personalized data file corresponds to the application version information according to the matching degree of the application information of the attribute file and the personalized data file.
Optionally, the establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a personalized data pool for storage includes:
acquiring a personalized data storage instruction, wherein the personalized data storage instruction comprises first storage position information of a personalized data file in a personalized data pool;
and establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a first storage position corresponding to the personalized data pool for storage according to the personalized data storage instruction.
Optionally, the matching in a personalized data pool according to the target application version information to obtain a target personalized data file includes:
and inquiring a mapping relation table in a personalized data pool according to the target application version information to obtain a target personalized data file.
Optionally, after the card opening operation is performed according to the target personalization data and the target application version information, the method further includes:
acquiring a user card transfer request and user card information;
determining initial application version information of a migration equipment terminal according to the user card migration request, and transmitting the user card information to the migration equipment terminal;
determining an initial personalized data file according to the initial application version information;
acquiring a personalized data storage instruction, wherein the personalized data storage instruction comprises second storage position information of a personalized data file;
and feeding back the initial personalized data file and the initial application version information to a second storage position corresponding to a personalized data pool for storage according to the personalized data storage instruction, and deleting the target application version information and the target personalized data file stored in a first storage position corresponding to the user card information so as to finish the user card transfer request.
In addition, in order to achieve the above object, the present invention further provides a multi-version application compatible air card issuing device, including:
the acquisition module is used for acquiring a card opening request of a user;
the determining module is used for determining the target application version information of the current empty card issuing equipment according to the user card opening request;
the matching module is used for matching in a personalized data pool according to the target application version information to obtain target personalized data;
and the card opening module is used for carrying out card opening operation according to the target personalized data and the target application version information.
In addition, in order to achieve the above object, the present invention further provides a multi-version application compatible air card issuing device, including: a memory, a processor, and a compatible multi-version application air card issuing program stored on the memory and executable on the processor, the compatible multi-version application air card issuing program configured to implement the steps of the compatible multi-version application air card issuing method as described above.
In addition, to achieve the above object, the present invention further provides a storage medium, which stores thereon a compatible multi-version application air card distribution program, and when being executed by a processor, the compatible multi-version application air card distribution program implements the steps of the compatible multi-version application air card distribution method as described above.
The invention obtains the user card opening request; determining target application version information of the current empty card issuing equipment according to the user card opening request; matching in a personalized data pool according to the target application version information to obtain a target personalized data file; and carrying out card opening operation according to the target personalized data file and the target application version information. Through the management and control of the application versions, the data pools of different versions are divided, so that the problem of incompatibility of personalized data files among multi-version applications is solved.
Drawings
Fig. 1 is a schematic structural diagram of a multi-version application air card issuing device compatible with a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a first embodiment of a method for issuing a card in an empty state compatible with multiple versions of an application according to the present invention;
FIG. 3 is a flowchart illustrating a second embodiment of the method for issuing a card in an empty state compatible with multiple versions of an application according to the present invention;
FIG. 4 is a schematic diagram of an organization framework compatible with an embodiment of a method for issuing a card in a multi-version application air-issuing system according to the present invention;
FIG. 5 is a schematic processing flow diagram illustrating a method for issuing a card in an empty state compatible with multiple versions of applications according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating a third embodiment of a method for issuing a card in an empty state compatible with multiple versions of an application according to the present invention;
fig. 7 is a block diagram of a first embodiment of the apparatus for issuing a card in a multi-version application-compatible manner according to the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a compatible multi-version application air card issuing device of a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the multi-version application compliant null card issuing device may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a Wireless interface (e.g., a Wireless-Fidelity (Wi-Fi) interface). The Memory 1005 may be a Random Access Memory (RAM) Memory, or may be a Non-Volatile Memory (NVM), such as a disk Memory. The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the configuration shown in fig. 1 does not constitute a limitation of a multi-version application air card device, and may include more or fewer components than shown, or some components in combination, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a storage medium, may include therein an operating system, a network communication module, a user interface module, and a multi-version application-compatible air card issuing program.
In the compatible multi-version application air card issuing device shown in fig. 1, the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 of the multi-version application compatible air card issuing device of the present invention may be arranged in the multi-version application compatible air card issuing device, and the multi-version application compatible air card issuing device calls the multi-version application compatible air card issuing program stored in the memory 1005 through the processor 1001 and executes the multi-version application compatible air card issuing method provided by the embodiment of the present invention.
An embodiment of the present invention provides a method for issuing a card in a manner compatible with multiple versions of an application, and referring to fig. 2, fig. 2 is a flowchart illustrating a first embodiment of the method for issuing a card in a manner compatible with multiple versions of an application.
In this embodiment, the method for issuing the card in the air compatible with the multi-version application includes the following steps:
step S10: and acquiring a card opening request of a user.
It should be noted that, the execution main body in this embodiment may be a device compatible with the multi-version application air card, and may also be another device capable of implementing the same or similar functions.
It can be understood that the user card opening request may be a request for a user to perform a card opening operation, and generally, a card application to be opened is selected according to a user requirement, so as to trigger the user card opening request.
Step S20: and determining the target application version information of the current empty card issuing equipment according to the user card opening request.
It should be understood that the application loaded in the air card issuing device is divided into three versions, including a version currently loaded in the device, a version under development, and a version modified based on the cryptographic algorithm, which is not limited in this embodiment, and therefore, the application version includes any one of a version currently loaded in the device, a version under development, and a version modified based on the cryptographic algorithm.
It should be noted that, when the user equipment opens the card, the card issuing device uploads target application version information downloaded in advance in the device, where the target application version information includes an application version, an identifier of the application version, and a device model, and the identifier of the application version may be set by a person in the art and is mainly used to search personalized data corresponding to the application version, which is not limited in this embodiment.
Step S30: and matching in a personalized data pool according to the target application version information to obtain a target personalized data file.
It can be understood that the target personalized data file is a set of encrypted KEY (KEY) ciphertext and a personalization instruction, and the air card device searches the corresponding target personalized data file in the personalized data pool of the corresponding version according to the target application version information of the user device.
Further, step S30 includes:
and inquiring a mapping relation table in a personalized data pool according to the target application version information to obtain a target personalized data file.
It should be understood that the personalized data pool includes the personalized data file and the mapping relationship table established by the application version information, so that the target personalized data file corresponding to the application version information can be searched in the mapping relationship table through the identifier of the target application version.
Step S40: and carrying out card opening operation according to the target personalized data file and the target application version information.
It should be noted that, when the target personalized data file and the target application version information are acquired, a card opening operation may be performed.
The embodiment obtains the card opening request of the user; determining target application version information of the current empty card issuing equipment according to the user card opening request; matching in a personalized data pool according to the target application version information to obtain a target personalized data file; and carrying out card opening operation according to the target personalized data file and the target application version information. Through management and control of application versions, data pools of different versions are divided, and therefore the problem that personalized data among multi-version applications are incompatible is solved.
Referring to fig. 3, fig. 3 is a flowchart illustrating a method for issuing a card in a multi-version application-compatible air card issuing manner according to a second embodiment of the present invention.
Based on the first embodiment, before the step S10, the method for issuing a card by empty for multi-version application in this embodiment further includes:
step S101: and acquiring the application version information of the empty card issuing equipment.
It can be understood that the air card issuing device uploads the application version information in the device, where the application version information includes an application version, an identifier of the application version, and a device model, and the application version includes any one of a version loaded in the device, a version being developed, and a version modified based on a cryptographic algorithm, which is not limited in this embodiment.
Step S102: and determining the personalized data file of the corresponding version according to the application version information.
It can be understood that different scripting languages are called through different application versions, and the personalized language corresponding to the script is generated by branches of the different scripting languages, so that the corresponding personalized data file is generated, and therefore the personalized data file of the corresponding version can be generated according to the specified application version, and the personalized data file is exported.
Further, after step S102, the method further includes:
and acquiring the project information in the personalized data file.
It should be noted that, because the personalized data file is a set of encrypted KEY (KEY) ciphertext and a personalized instruction, the blank card issuing device system cannot directly identify the personalized data file, and therefore, when deriving the personalized data file, it is necessary to obtain item information in the personalized data file, where the item information includes an application version, a card type, a card number start, a manufacturing quantity, and the like, which is not limited in this embodiment.
And determining the attribute file of the application version information according to the project information.
It should be understood that the selected item information is recorded as a property file, and the property file and the personalized data file are compressed and packaged together for export, wherein the property file may be a TXT text file, which is not limited by the embodiment.
And importing the personalized data file and the attribute file into a service provider platform so that the service provider platform judges whether the personalized data file corresponds to the application version information or not according to the attribute file.
Further, importing the personalized data file and the attribute file to a service provider platform so that the service provider platform determines whether the personalized data file corresponds to the application version information according to the attribute file includes:
and importing the personalized data file and the attribute file into a service provider platform so that the service provider platform determines whether the personalized data file corresponds to the application version information according to the matching degree of the application information of the attribute file and the personalized data file.
It can be understood that the empty card issuing device imports the personalized data file and the attribute file into the service provider platform, and when the service provider platform receives the personalized data file and the attribute file, the service provider platform decompresses and identifies the personalized data file and the attribute file, so as to obtain the application version of the personalized data file and the application version of the attribute file.
It should be understood that the application information may be an application version of the property file, and the matching degree may be whether the application version of the property file is consistent with the application version of the personalized data file, and may be represented by 1 and 0 in the specific implementation process. If the application version of the attribute file is consistent with the application version of the personalized data file, the matching degree is 1, which indicates that the personalized data file corresponds to the application version, that is, it can be further determined that the personalized data file is generated by the application version, and if the application version of the attribute file is inconsistent with the application version of the personalized data file, the matching degree is 0, which indicates that the personalized data file does not correspond to the application version.
And when the personalized data file corresponds to the application version information, establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a personalized data pool.
It should be noted that, when the personalized data file corresponds to the application version, the personalized data file is allocated to the corresponding data pool according to the application version in the attribute file, that is, a mapping relation table is established according to the personalized data file and the application version information, and the mapping relation table is fed back to the personalized data pool.
Step S103: and establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a personalized data pool.
Further, step S103 includes:
acquiring a personalized data storage instruction, wherein the personalized data storage instruction comprises first storage position information of a personalized data file in a personalized data pool.
It is understood that the personalization data storage command is a command for the user to select a storage location of the personalization data file, and the personalization data pool is divided into multiple versions of data pools, which may be represented by the data pool V0, the data pool V1, and the data pool V2 in the implementation process, which is not limited by the embodiment.
It should be understood that the first storage location information may be any one of storage locations of data pool V0, data pool V1, and data pool V2, which is not limited by the present embodiment, and therefore, personalized data storage instructions are obtained, wherein the personalized data storage instructions include personalized data files in any one of storage locations of data pool V0, data pool V1, or data pool V2 of the personalized data pool.
And establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a first storage position corresponding to the personalized data pool for storage according to the personalized data storage instruction.
It should be noted that, a mapping relationship table is established according to the personalized data file and the application version information, where the mapping relationship table includes a corresponding relationship between the personalized data file and the application version information, so that the personalized data file corresponding to the mapping relationship table is conveniently searched through the application version identifier.
It can be understood that, after the mapping table is established, the mapping table is fed back to any position of the data pool V0, the data pool V1 or the data pool V2 corresponding to the personalized data pool for storage according to the personalized data storage instruction.
It is understood that, in summary, fig. 4 is a schematic diagram of an organization framework, wherein the air card issuing system includes a data preparation system, an Sp-tsm management platform, i.e., a service provider management platform, and an Sp-tsm sub-platform, i.e., a service provider sub-platform; the process flow diagram shown in fig. 5 illustrates a process flow diagram, in which the data preparation subsystem is used to select devices for version generation of CPS files, i.e., personalized data files, and package export of CPS files and attribute files, the Sp-tsm management platform is used to import CPS file packages and identify attribute files, and place CPS files into data pools for versions, and the Sp-tsm sub-platform includes a data pool V0, a data pool V1, and a data pool V2.
The embodiment obtains the application version information of the air card issuing equipment; determining a personalized data file of a corresponding version according to the application version information; and establishing a mapping relation table according to the personalized data file and the application version information, feeding the mapping relation table back to a personalized data pool for storage, and storing the personalized data file in the personalized data pool by establishing the mapping relation table of the personalized data file and the application version information, so that the problem of incompatibility of the personalized data files among multiple versions of applications is solved, and the accuracy of solving the problem of incompatibility of the personalized data files among multiple versions of applications is effectively improved.
Referring to fig. 6, fig. 6 is a flowchart illustrating a third embodiment of a method for issuing a card in a multi-version application-compatible manner according to the present invention.
Based on the foregoing embodiment, after the step S30, the method for issuing a card by empty for multi-version application in this embodiment further includes:
step S401: and acquiring a user card transfer request and user card information.
It should be noted that the card migration in this embodiment is a process of migrating in/out between different application versions, that is, a process of migrating an old device between different application versions to a new device, so that when the user device operates the card migration, a user card migration request is triggered, and the old device needs to migrate card information to the cloud, so that the user card migration request and the card information of the user can be further obtained.
It is understood that the user card information includes information of the user, such as card information, balance in the card, and transaction record, which is not limited in this embodiment.
Step S402: and determining initial application version information of the migration equipment terminal according to the user card migration request, and transmitting the user card information to the migration equipment terminal.
It should be understood that the initial application version information is the application version information of the terminal of the migration device, that is, the new device, and the card information on the cloud is migrated to the new device and deleted.
Step S403: and determining an initial personalized data file according to the initial application version information.
It can be understood that, when a user migrates cards among different devices, since there may be application version differences in the user devices and the personalization data needs to be generated in real time, an initial personalization data file corresponding to the start application version information can be determined.
Step S404: a personalization data storage instruction is obtained, the personalization data storage instruction comprising second storage location information of the personalization data file.
It will be appreciated that the second storage location information may be any one of two storage locations other than the first storage location of the old device personalization data file, for example, if the old device is stored in data pool V0, then the second storage location information is any one of data pools V1 or V2, which is not limited by the present embodiment, and therefore, by obtaining a personalization data storage command that includes the storage location of the new device generated personalization data file in the personalization data pool.
Step S405: and feeding back the initial personalized data file and the initial application version information to a second storage position corresponding to a personalized data pool for storage according to the personalized data storage instruction, and deleting the target application version information and the target personalized data file stored in a first storage position corresponding to the user card information so as to finish the user card transfer request.
It can be understood that the initial personalization data file and the initial application version information are stored in a second storage location corresponding to the personalization data pool based on the personalization data storage instruction, and the target application version information and the target personalization data file corresponding to the card information stored in the first storage location are further deleted, so as to complete the user card migration request.
It should be understood that, for example, the application version of the old device is the application X0 version, the application version of the new device is the application X1 version, when acquiring a card migration request of a user, the card is migrated to the cloud first, in this state, the personalized data file and the application version information of the card are located in the data pool V0, since the new device needs a card migration operation, the new device migrates the card from the cloud, and the application version of the new device is the application X1 version, which have a version difference of personalized limb, and cannot be migrated directly, the personalized card issuance data file needs to be regenerated for the card number, and is placed in the data pool V1 corresponding to the application X1 version, and the personalized card issuance file and the application version information corresponding to the card number are deleted in the data pool V0, the migration of the personalized data is completed, and finally the new personalized data file is issued to the new device, and completing the card migration.
The embodiment obtains the user card transferring request and the user card information; determining initial application version information of a migration equipment terminal according to the user card migration request, and transmitting the user card information to the migration equipment terminal; determining an initial personalized data file according to the initial application version information; acquiring a personalized data storage instruction, wherein the personalized data storage instruction comprises second storage position information of a personalized data file; and feeding back the initial personalized data file and the initial application version information to a second storage position corresponding to a personalized data pool for storage according to the personalized data storage instruction, and deleting the target application version information and the target personalized data file stored in a first storage position corresponding to the user card information so as to finish the user card transfer request. Therefore, the problem of incompatibility of personalized data files among multi-version applications, which causes the difficult problems of issuing cards, transferring in/out of multi-version applications, is effectively solved.
In addition, an embodiment of the present invention further provides a storage medium, where the storage medium stores a compatible multi-version application air card issuing program, and when the compatible multi-version application air card issuing program is executed by a processor, the method for implementing the compatible multi-version application air card issuing method described above is implemented.
Since the storage medium adopts all technical solutions of all the embodiments, at least all the beneficial effects brought by the technical solutions of the embodiments are achieved, and no further description is given here.
Referring to fig. 7, fig. 7 is a block diagram illustrating a first embodiment of a multi-version application-compatible air card issuing device according to the present invention.
As shown in fig. 7, the apparatus for issuing a card in an empty state compatible with multiple versions of applications according to an embodiment of the present invention includes:
the obtaining module 10 is configured to obtain a card opening request of a user.
It can be understood that the user card opening request may be a request for a user to perform a card opening operation, and generally, a card application to be opened is selected according to a user requirement, so as to trigger the user card opening request.
And the determining module 20 is configured to determine the target application version information of the current empty card issuing device according to the user card opening request.
It should be understood that the application loaded in the air card issuing device is divided into three versions, including a version currently loaded in the device, a version under development, and a version modified based on the cryptographic algorithm, which is not limited in this embodiment, and therefore, the application version includes any one of a version currently loaded in the device, a version under development, and a version modified based on the cryptographic algorithm.
It should be noted that, when the user equipment opens the card, the card issuing device uploads target application version information downloaded in advance in the device, where the target application version information includes an application version, an identifier of the application version, and a device model, and the identifier of the application version may be set by a person in the art and is mainly used to search personalized data corresponding to the application version, which is not limited in this embodiment.
And the matching module 30 is configured to perform matching in the personalized data pool according to the target application version information to obtain a target personalized data file.
It can be understood that the target personalized data file is a set of encrypted KEY (KEY) ciphertext and a personalization instruction, and the air card device searches the corresponding target personalized data file in the personalized data pool of the corresponding version according to the target application version information of the user device.
Further, matching in a personalized data pool according to the target application version information to obtain a target personalized data file comprises:
it should be understood that the personalized data pool includes the personalized data file and the mapping relationship table established by the application version information, so that the target personalized data file corresponding to the application version information can be searched in the mapping relationship table through the identifier of the target application version.
And the card opening module 40 is used for performing card opening operation according to the target personalized data file and the target application version information.
It should be noted that, when the target personalized data file and the target application version information are acquired, a card opening operation may be performed.
The embodiment obtains the card opening request of the user; determining target application version information of the current empty card issuing equipment according to the user card opening request; matching in a personalized data pool according to the target application version information to obtain a target personalized data file; and carrying out card opening operation according to the target personalized data file and the target application version information. Through management and control of application versions, data pools of different versions are divided, and therefore the problem that personalized data files among multi-version applications are incompatible is solved.
In an embodiment, the obtaining module 10 is further configured to obtain application version information of the card issuing device; determining a personalized data file of a corresponding version according to the application version information; and establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a personalized data pool for storage.
In an embodiment, the obtaining module 10 is further configured to obtain the item information in the personalized data file; determining an attribute file of application version information according to the project information; importing the personalized data file and the attribute file into a service provider platform so that the service provider platform judges whether the personalized data file corresponds to the application version information according to the attribute file; and when the personalized data file corresponds to the application version information, establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a personalized data pool for storage.
In an embodiment, the determining module 20 is further configured to import the personalized data file and the attribute file to a service provider platform, so that the service provider platform determines whether the personalized data file corresponds to the application version information according to a matching degree of the application information of the attribute file and the personalized data file.
In an embodiment, the obtaining module 10 is further configured to obtain a personalized data storage instruction, where the personalized data storage instruction includes first storage location information of a personalized data file in a personalized data pool; and establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a first storage position corresponding to the personalized data pool for storage according to the personalized data storage instruction.
In an embodiment, the matching module 30 is further configured to query a mapping relation table in a personalized data pool according to the target application version information, so as to obtain a target personalized data file.
In an embodiment, the compatible multi-version application air card issuing device further comprises a card migrating module, wherein the card migrating module is used for acquiring a user card migrating request and user card information; determining initial application version information of a migration equipment terminal according to the user card migration request, and transmitting the user card information to the migration equipment terminal; determining an initial personalized data file according to the initial application version information; acquiring a personalized data storage instruction, wherein the personalized data storage instruction comprises second storage position information of a personalized data file; and feeding back the initial personalized data file and the initial application version information to a second storage position corresponding to a personalized data pool for storage according to the personalized data storage instruction, and deleting the target application version information and the target personalized data file stored in a first storage position corresponding to the user card information so as to finish the user card transfer request.
In other embodiments or specific implementation methods of the apparatus compatible with multiple versions of application air card issuers of the present invention, reference may be made to the above embodiments of the methods, and details are not repeated here.
It should be understood that the above is only an example, and the technical solution of the present invention is not limited in any way, and in a specific application, a person skilled in the art may set the technical solution as needed, and the present invention is not limited thereto.
It should be noted that the above-described work flows are only exemplary, and do not limit the scope of the present invention, and in practical applications, a person skilled in the art may select some or all of them to achieve the purpose of the solution of the embodiment according to actual needs, and the present invention is not limited herein.
In addition, the technical details that are not described in detail in this embodiment may refer to the method for issuing a card in a multi-version-compatible application space provided in any embodiment of the present invention, and are not described herein again.
Further, it is to be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (e.g. Read Only Memory (ROM)/RAM, magnetic disk, optical disk), and includes several instructions for enabling a terminal device (e.g. a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A method for issuing a card in a manner of being compatible with multiple versions of applications in a null manner is characterized by comprising the following steps:
acquiring a user card opening request;
determining target application version information of the current empty card issuing equipment according to the user card opening request;
matching in a personalized data pool according to the target application version information to obtain a target personalized data file;
and carrying out card opening operation according to the target personalized data file and the target application version information.
2. The method for issuing the card with the multiple versions of the application being compatible with according to claim 1, wherein before the obtaining the card-opening request of the user, the method further comprises:
acquiring application version information of the empty card issuing equipment;
determining a personalized data file of a corresponding version according to the application version information;
and establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a personalized data pool for storage.
3. The method for issuing a card over the air compatible with multiple versions of applications according to claim 2, wherein after determining the corresponding version of the personalized data file according to the application version information, the method further comprises:
acquiring project information in the personalized data file;
determining an attribute file of application version information according to the project information;
importing the personalized data file and the attribute file into a service provider platform so that the service provider platform judges whether the personalized data file corresponds to the application version information according to the attribute file;
and when the personalized data file corresponds to the application version information, establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a personalized data pool for storage.
4. The method according to claim 3, wherein the importing the personalized data file and the attribute file to a service provider platform so that the service provider platform determines whether the personalized data file corresponds to the application version information according to the attribute file comprises:
and importing the personalized data file and the attribute file into a service provider platform so that the service provider platform determines whether the personalized data file corresponds to the application version information according to the matching degree of the application information of the attribute file and the personalized data file.
5. The method according to claim 2, wherein the creating a mapping table according to the personalized data file and the application version information, and feeding the mapping table back to a personalized data pool for storage comprises:
acquiring a personalized data storage instruction, wherein the personalized data storage instruction comprises first storage position information of a personalized data file in a personalized data pool;
and establishing a mapping relation table according to the personalized data file and the application version information, and feeding the mapping relation table back to a first storage position corresponding to the personalized data pool for storage according to the personalized data storage instruction.
6. The method for issuing the empty credit card compatible with the multi-version application according to any one of claims 1 to 5, wherein the matching in the personalized data pool according to the target application version information to obtain the target personalized data file comprises:
and inquiring a mapping relation table in a personalized data pool according to the target application version information to obtain a target personalized data file.
7. The method for issuing the empty card of the compatible multi-version application according to any one of claims 1 to 5, wherein after the card-opening operation is performed according to the target personalization data and the target application version information, the method further comprises:
acquiring a user card transfer request and user card information;
determining initial application version information of a migration equipment terminal according to the user card migration request, and transmitting the user card information to the migration equipment terminal;
determining an initial personalized data file according to the initial application version information;
acquiring a personalized data storage instruction, wherein the personalized data storage instruction comprises second storage position information of a personalized data file;
and feeding back the initial personalized data file and the initial application version information to a second storage position corresponding to a personalized data pool for storage according to the personalized data storage instruction, and deleting the target application version information and the target personalized data file stored in a first storage position corresponding to the user card information so as to finish the user card transfer request.
8. A multi-version application compatible air card issuing device is characterized by comprising:
the acquisition module is used for acquiring a card opening request of a user;
the determining module is used for determining the target application version information of the current empty card issuing equipment according to the user card opening request;
the matching module is used for matching in a personalized data pool according to the target application version information to obtain a target personalized data file;
and the card opening module is used for carrying out card opening operation according to the target personalized data file and the target application version information.
9. A multi-version application compliant null card issuing device, comprising: a memory, a processor, and a compatible multi-version application air card issuing program stored on the memory and executable on the processor, the compatible multi-version application air card issuing program configured to implement the compatible multi-version application air card issuing method according to any one of claims 1 to 7.
10. A storage medium having stored thereon a multi-version application-compatible air card distribution program that, when executed by a processor, implements the multi-version application-compatible air card distribution method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110894679.3A CN113347620B (en) | 2021-08-05 | 2021-08-05 | Method, device, equipment and storage medium for compatibility of multi-version application air card issuing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110894679.3A CN113347620B (en) | 2021-08-05 | 2021-08-05 | Method, device, equipment and storage medium for compatibility of multi-version application air card issuing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113347620A true CN113347620A (en) | 2021-09-03 |
| CN113347620B CN113347620B (en) | 2021-11-12 |
Family
ID=77480820
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110894679.3A Active CN113347620B (en) | 2021-08-05 | 2021-08-05 | Method, device, equipment and storage medium for compatibility of multi-version application air card issuing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113347620B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103208065A (en) * | 2012-01-16 | 2013-07-17 | 深圳市家富通汇科技有限公司 | Method and apparatus for personalizing secure elements in mobile devices |
| US20140298322A1 (en) * | 2013-03-26 | 2014-10-02 | Jvl Ventures, Llc | Systems, methods, and computer program products for managing service installation |
| US20150188912A1 (en) * | 2013-12-31 | 2015-07-02 | Hoyos Labs Corp. | System and method for biometric protocol standards |
| CN105376060A (en) * | 2014-08-27 | 2016-03-02 | 中国移动通信集团公司 | Configurable mandatory data authentication mode-based authentication method, device and system |
| CN105592033A (en) * | 2014-12-30 | 2016-05-18 | 中国银联股份有限公司 | Trusted service management system and method |
| CN109446159A (en) * | 2018-09-03 | 2019-03-08 | 中国平安财产保险股份有限公司 | Multi version file management method, server and computer readable storage medium |
| CN109863475A (en) * | 2017-10-09 | 2019-06-07 | 华为技术有限公司 | The upgrade method and relevant device of a kind of application in safety element |
| US20210072972A1 (en) * | 2014-10-10 | 2021-03-11 | Visa International Service Association | Methods and systems for partial personalization during application update |
-
2021
- 2021-08-05 CN CN202110894679.3A patent/CN113347620B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103208065A (en) * | 2012-01-16 | 2013-07-17 | 深圳市家富通汇科技有限公司 | Method and apparatus for personalizing secure elements in mobile devices |
| US20140298322A1 (en) * | 2013-03-26 | 2014-10-02 | Jvl Ventures, Llc | Systems, methods, and computer program products for managing service installation |
| US20150188912A1 (en) * | 2013-12-31 | 2015-07-02 | Hoyos Labs Corp. | System and method for biometric protocol standards |
| CN105376060A (en) * | 2014-08-27 | 2016-03-02 | 中国移动通信集团公司 | Configurable mandatory data authentication mode-based authentication method, device and system |
| US20210072972A1 (en) * | 2014-10-10 | 2021-03-11 | Visa International Service Association | Methods and systems for partial personalization during application update |
| CN105592033A (en) * | 2014-12-30 | 2016-05-18 | 中国银联股份有限公司 | Trusted service management system and method |
| CN109863475A (en) * | 2017-10-09 | 2019-06-07 | 华为技术有限公司 | The upgrade method and relevant device of a kind of application in safety element |
| CN109446159A (en) * | 2018-09-03 | 2019-03-08 | 中国平安财产保险股份有限公司 | Multi version file management method, server and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 罗敏: "基于TSM平台的卡片迁移设计与研究", 《中国优秀硕士学位论文全文数据库工程科技辑》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113347620B (en) | 2021-11-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104793946B (en) | Dispositions method and system are applied based on cloud computing platform | |
| CN108287694B (en) | Application program construction method, system, computer device and storage medium | |
| CN101833467B (en) | Method and equipment for adding menu items into Android menu | |
| CN107273148B (en) | Update driven migration of data | |
| CN107506221A (en) | Application program updating method, apparatus and equipment | |
| CN109726134B (en) | Interface test method and system | |
| CN109032631B (en) | Application program patch package obtaining method and device, computer equipment and storage medium | |
| CN111068328A (en) | Game advertisement configuration table generation method, terminal device and medium | |
| CN107797818A (en) | Application program updating method and device | |
| CN107301179A (en) | The method and apparatus of data base read-write separation | |
| CN110362341B (en) | Business management method, device, equipment and storage medium based on micro-service architecture | |
| CN114218315A (en) | Interface generation method and device, computer equipment and storage medium | |
| CN112612833B (en) | Rule package updating method, device, equipment and storage medium | |
| CN111831744B (en) | System, method and medium for searching data on DAPP chain | |
| CN113296891A (en) | Multi-scene knowledge graph processing method and device based on platform | |
| CN113347620B (en) | Method, device, equipment and storage medium for compatibility of multi-version application air card issuing | |
| CN113568603B (en) | Component object creating and interface method calling method, terminal and storage device | |
| CN106778193B (en) | Client and UI interaction method | |
| CN115203747A (en) | Data account creation method and device | |
| CN115221559A (en) | Data account access authorization method and device | |
| CN114860202A (en) | Project operation method, device, server and storage medium | |
| CN113948164A (en) | Clinical medicine management method, device, equipment and computer readable storage medium | |
| CN112559131A (en) | Method, device and equipment for updating container mirror image and computer readable storage medium | |
| CN108345461B (en) | Application updating method and device and computer readable storage medium | |
| US10489775B2 (en) | Integrated circuit card adapted to transfer first data from a first application for use by a second application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |