CN112702728B - User profile management method and device, smart card and readable storage medium - Google Patents
User profile management method and device, smart card and readable storage medium Download PDFInfo
- Publication number
- CN112702728B CN112702728B CN202011558286.7A CN202011558286A CN112702728B CN 112702728 B CN112702728 B CN 112702728B CN 202011558286 A CN202011558286 A CN 202011558286A CN 112702728 B CN112702728 B CN 112702728B
- Authority
- CN
- China
- Prior art keywords
- profile
- file
- file system
- common
- files
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/183—Processing at user equipment or user record carrier
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
- H04W8/205—Transfer to or from user equipment or user record carrier
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a user configuration file management method, a user configuration file management device, a smart card and a readable storage medium, wherein the management method comprises the following steps: when receiving an activation instruction, activating the Profile indicated by the activation instruction; calling a common file system corresponding to the Profile as a file system of the Profile; the shared file system has the remaining files in the Profile except the personalized file, and the shared file system can be used by a plurality of profiles including the Profile. Therefore, when each Profile is activated, the common file system can be called as the file system of the Profile, so that on the premise that each Profile can be normally used, the file system which belongs to the Profile is not required to be established for each Profile, the consumption of the space resources of the intelligent card by the file system is reduced, and more residual space can be used for downloading new profiles and establishing files and contents.
Description
Technical Field
The application relates to the technical field of smart cards, in particular to a user profile management method and device, a smart card and a readable storage medium.
Background
eUICC (embedded Universal Integrated Circuit Card), also called eSIM (embedded Subscriber identity Module) Card, is a third generation telecommunication smart Card. When a user uses the eSIM card to sign operator information and transacts a new mobile phone number, the user mainly downloads a corresponding Profile (user configuration file).
Currently, an eSIM card supports downloading of multiple profiles, and the profiles are not related, independent and independent, and do not affect each other. However, only one Profile is allowed to be in an activated state and the other profiles need to be in an inactivated state at the same time on the eSIM card. On the eSIM card, only the contents of the Profile in the activated state are available.
Each Profile corresponds to a file system (FileSystem), which contains a large number of files and file contents. Therefore, at present, each time the eSIM card downloads one Profile, a set of file system corresponding to the Profile needs to be stored for the Profile in the eSIM card, which greatly consumes space resources of the eSIM card, and the corresponding remaining space resources are few, which affects available space for downloading a new Profile and creating files and contents.
Disclosure of Invention
An embodiment of the present application aims to provide a Profile downloading method, a Profile management device, a smart card, and a readable storage medium, so as to solve the above problems.
The embodiment of the application provides a Profile downloading method, which is applied to an intelligent card and comprises the following steps: downloading a Profile and identifying personalized files in the Profile; when a common file system corresponding to the Profile is established in the public space of the intelligent card, removing other files except the personalized file in the Profile; or when a common file system corresponding to the Profile is created in the public space of the smart card, adding the personalized file into the common file system, associating the personalized file with the Profile, and deleting all files in the Profile; wherein the common file system is usable by a plurality of profiles including the Profile, and the common file system has therein a common file reusable by the plurality of profiles; the common files are the rest files in the Profile except the personalized files.
In the implementation process, a common file system with other files in the Profile except the personalized file is constructed, so that the personalized file of the Profile only needs to be stored when one Profile is downloaded; for the rest of files (i.e. common files) except the personalized file, the rest of files can be obtained by multiplexing the common file system, so that the consumption of the smart card space resource by the file system corresponding to each Profile is reduced, and more remaining space can be used for downloading new profiles and creating files and contents.
Further, the identifying personalized files in the Profile includes: judging whether a file with a file identifier consistent with a preset file identifier exists in the Profile; if so, determining the file with the file identification consistent with the preset file identification as the personalized file.
In the implementation process, the file identifiers (such as file names and the like) of the files possibly having differences among the profiles are preset, so that the personalized files in the profiles can be quickly identified through the judgment of the file identifiers.
Further, after downloading the Profile, the method further comprises: judging whether a common file system corresponding to the Profile exists in the public space; and if the personalized file does not exist in the public space, creating a common file system corresponding to the Profile in the public space, and storing the other files except the personalized file in the Profile in the common file system.
In the implementation process, when the common file system corresponding to the Profile does not exist, the common file system is created, and the other files in the Profile except the personalized file are stored in the common file system, so that the common file system is quickly created, and the subsequent use of the Profile of the common file system is convenient to reuse.
Further, the identifying personalized files among the files in the Profile includes: comparing the files in the Profile with the files in the common file system in sequence to determine the files in the Profile which are different from the files in the common file system; and the file in the Profile, which is different from the file in the common file system, is the personalized file of the Profile.
In the implementation process, the part of the personalized file which cannot be reused in the Profile can be quickly determined by comparing the files in the common file system.
Further, before identifying personalized files among the files within the Profile, the method further comprises: judging whether a common file system corresponding to the Profile exists in the public space; and if the common file system corresponding to the Profile does not exist in the common space, creating the common file system corresponding to the Profile in the common space, and storing all files in the Profile in the common file system.
In the implementation process, when the Profile does not have a corresponding common file system, the common file system is constructed through all files in the Profile, so that the personalized file for file comparison is determined when a new Profile is downloaded again. The personalized file determined in the way is more fit with the reality of each Profile, and the determination of the personalized file is more flexible.
Further, in the process of determining that there are files in the Profile that are distinct from files in the common file system, the method further comprises: saving the files in the shared file system, which are different from the content of the Profile, into all the profiles with the use permission of the shared file system except the Profile, and deleting the files with the different contents from the shared file system; or, taking the file in the shared file system, which is different from the content of the Profile, as a personalized file, and associating the personalized file with all the profiles except the Profile, which have the use permission of the shared file system.
In the actual comparison process, there may be files with the same file name but different contents (hereinafter referred to as difference files). This difference file indicates that the content of the file in each Profile downloaded before the Profile is the same, only the content in the Profile is different. Therefore, the files with different contents in the common file system can be used as the personalized files of the profiles downloaded before the Profile, so that the personalized files of the profiles are accurately determined, and the common file system can be correctly used without causing file errors when different profiles multiplex the common file system.
Further, the Profile has a first identification value therein; judging whether a common file system corresponding to the Profile exists in the public space or not, wherein the judging comprises the following steps: judging whether a common file system matched with the first identification value exists in the public space of the intelligent card or not according to the first identification value in the Profile; and if so, determining that the common file system is the common file system corresponding to the Profile.
In practical applications, the difference between profiles corresponding to different projects is often larger than the difference between profiles corresponding to the same project. Therefore, in the embodiment of the application, a first identification value may be set for the profiles in advance, and a common file system of each Profile is constructed based on the first identification value, so that determination of whether a newly downloaded Profile has a corresponding common file system can be quickly achieved based on the first identification value.
Further, after creating the common file system corresponding to the Profile in the common space, the method further includes: and allocating a second identification value matched with the first identification value to the created common file system.
The embodiment of the present application further provides a Profile management method, which is applied to a smart card, and includes: activating the Profile indicated by the activation instruction when the activation instruction is received; calling a common file system corresponding to the Profile as a file system of the Profile; the shared file system has the rest of the files in the Profile except the personalized files, and the shared file system can be used by a plurality of profiles including the Profile.
In the implementation process, the common file system with the other files in the profiles except the personalized file is constructed, so that when each Profile is activated, the corresponding common file system can be called to serve as the file system of the Profile, and the Profile does not need to create a file system which belongs to the Profile for each Profile on the premise that each Profile can be normally used, so that the consumption of the space resources of the smart card by the file system is reduced, and more remaining space can be used for downloading the new Profile and creating the file and the content.
Further, the method further comprises: acquiring a first identification value of the Profile; finding a common file system matched with the first identification value in the public space of the intelligent card; and the searched common file system is the common file system corresponding to the Profile.
Further, the method further comprises: in the using process of the Profile, if the content of the common file in the common file system needs to be modified, then: the common file is stored in all the profiles with the common file system use permission except the Profile before modification, and the common file is stored in the Profile as a personalized file of the Profile after modification; or, before modification, the common file is used as a personalized file to be associated with all the profiles with the common file system use authority except the Profile, and after modification, the common file is used as the personalized file of the Profile to be associated with the Profile.
In the implementation process, the common file modified in the currently activated Profile use process is used as the personalized file of the Profile and is stored in the Profile or is associated with the Profile, and the common file before modification is used as the personalized files of all profiles with the common file system use permission except the Profile and is stored in the profiles or is associated with the profiles. Therefore, the update of the common file system can be realized according to the personalized files caused in the using process, and the reusability of the common file system to each Profile is ensured.
Further, the method further comprises: in the using process of the Profile, if the content of a preset special common file in the common file system is modified, the preset special common file is kept as a file which is provided for all corresponding profiles in the common file system to share.
Further, the preset special shared file is at least one of the following files: a short message file; a telephone file.
In the actual application process, for files such as short message files and phone files, users often want to use any Profile in the actual use process, and the stored content of the files is universal. For example, a user has a new contact stored in Profile1, and the user does not usually want the contact to disappear after switching to Profile 2. Therefore, in the implementation process, the special shared files are configured, so that the files can be prevented from being changed into personalized files due to modification of the files in the using process of the Profile, and the using feeling of a user is improved.
The embodiment of the present application further provides a Profile downloading device, which is applied to a smart card, and includes: applied to a smart card, comprising: the device comprises a downloading module and a first processing module; the downloading module is used for downloading the Profile and identifying personalized files in the Profile; the first processing module is used for removing other files except the personalized file in the Profile when a common file system corresponding to the Profile is established in the public space of the intelligent card; or when a common file system corresponding to the Profile is created in the public space of the smart card, adding the personalized file into the common file system, associating the personalized file with the Profile, and deleting all files in the Profile; wherein the shared file system has the rest of the files in the Profile except the personalized file, and the shared file system can be used by a plurality of profiles including the Profile.
The embodiment of the present application further provides a Profile management device, which is applied to a smart card, and includes: an activation module and a second processing module; the activation module is used for activating the Profile indicated by the activation instruction when the activation instruction is received; the second processing module is used for calling the common file system corresponding to the Profile as the file system of the Profile; the shared file system has the remaining files in the Profile except the personalized file, and the shared file system can be used by a plurality of profiles including the Profile.
The embodiment of the application also provides an intelligent card which comprises a processor, a memory and a serial communication unit; the serial communication unit is used for realizing connection communication between the processor and the memory; the processor is configured to execute one or more programs stored in the memory to implement any one of the above-described Profile downloading methods and/or implement any one of the above-described Profile management methods.
An embodiment of the present application further provides a readable storage medium, where one or more programs are stored, and the one or more programs are executable by one or more processors to implement any of the above-mentioned Profile management methods.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic flowchart of a Profile downloading method according to an embodiment of the present application;
fig. 2 is a schematic flow chart of a Profile management method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a Profile in a smart card according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of another Profile in a smart card according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of another Profile in a smart card according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a Profile downloading device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a Profile management device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a smart card according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
The first embodiment is as follows:
in order to improve the utilization rate of the space in the smart card and reduce the space resource consumption for downloading the Profile, and therefore more space left in the smart card can be used for downloading the new Profile and creating files and contents, the embodiment of the application provides a Profile downloading method applicable to the smart card. As shown in fig. 1, fig. 1 is a schematic flow chart of a Profile downloading method provided in an embodiment of the present application, and the method includes:
s101: the Profile is downloaded and personalized files among the files within the Profile are identified.
It should be noted that the smart card described in the embodiment of the present application refers to a smart card that can support downloading multiple profiles, such as an eSIM card.
In the embodiment of the present application, the smart card may download the required Profile from a resource server provided by an operator, or the like.
S102: when a common file system corresponding to the Profile is established in the public space of the intelligent card, removing other files except the personalized file in the Profile; or when a common file system corresponding to the Profile is created in the public space of the smart card, adding the personalized file into the common file system, associating the personalized file with the Profile, and deleting all files in the Profile.
It should be noted that, in the embodiment of the present application, the common space of the smart card refers to a space within the smart card that is accessible by each Profile.
It should be understood that in practical applications, file systems of different profiles often have a large number of files with identical contents for different profiles. In the embodiment of the present application, the part of the files may be used as a shared file to construct a shared file system, and the shared file system is provided for each Profile to be multiplexed.
In a possible implementation manner of the embodiment of the present application, common files of various profiles that may be downloaded by the smart card may be predefined, so that a common file system is constructed in the smart card.
For example, an engineer may summarize experience to obtain common files for various profiles and save the common files on a device such as an internal database. After the smart card is powered on for the first time, the preset common files can be requested, and therefore a common file system with the common files is built in the smart card.
In addition, in the embodiment of the present application, an engineer may also summarize different files of various profiles according to experience, and record file identifiers of the files in advance, so that when downloading a Profile, it may be determined whether the Profile has files with file identifiers consistent with preset file identifiers, and the files with the file identifiers consistent with the preset file identifiers are taken as personalized files.
In the embodiment of the present application, the file identifier may adopt a file name or a file path, and the like.
For example, it is assumed that an engineer sets EF ICCID2FE2 file under MF 3F00 file, EF IMSI6F07 file under DF7F20 file, EF ACC 6F78 file under DF7F20 file, EF IMSI6F07 file under ADF7FF0 file, and EF ACC 6F78 file under ADF7FF0 file as personalized files, so that file paths MF 3F00-EF IMSI6F07, DF7F 20-EF 6imsi 07, DF 7F20-EF 6f78, ADF 7FF0-EF 6F07, ADF7FF 0-EF ACC 6F78, and the like ("-" indicates an upper file to a lower file) can be predefined in a smart card.
At this time, in another possible implementation manner of the embodiment of the present application, after downloading the Profile, it may be determined whether a common file system corresponding to the Profile already exists in the public space, so that when the Profile does not exist, the personalized file in the Profile is identified by the above method, the common file system corresponding to the Profile is created in the public space, and the other files except the personalized file in the Profile are stored in the common file system, so that the common file system is obtained.
It should be understood that, in the above possible embodiment, all files in the Profile may also be saved to the common file system, so as to obtain the common file system.
In addition, in the embodiment of the present application, the personalized file of each Profile may not be identified in a manner preset by an engineer, but the personalized file of each Profile may be determined continuously based on file comparison in different profiles.
For example, in the embodiment of the present application, after downloading the Profile, the files in the Profile may be sequentially compared with the common files in the common file system, so as to determine the files in the Profile that are different from the common file system. These files with differences are the personalized files of the Profile.
It should be noted that, in the embodiment of the present application, after downloading the Profile, it may be determined whether a common file system corresponding to the Profile already exists in the common space. Thus, in the absence of time, a common file system corresponding to the Profile is created in the common space, and all files in the Profile are saved in the common file system.
At this time, since the file in the common file system is identical to the file of the Profile, the comparison result shows that no personalized data exists in the Profile with respect to the common file system at present, so that the file in the Profile may not retain the file at all.
It should be noted that there are two types of distinct files within the compared Profile and in the common file system:
1. there are within the Profile, but there are no corresponding common files in the common file system.
2. The common file exists in the Profile and the corresponding common file exists in the common file system, but the content of the file existing in the Profile is different from that of the common file in the common file system.
For the first type of distinguishing file, it is only required to be directly used as the personalized file of the Profile, and for the second type of distinguishing file, besides it is required to be used as the personalized file of the Profile, it is also required to use the corresponding common file in the file system as the personalized file of all the profiles downloaded before the Profile, which corresponds to the common file system.
For example, after a first Profile is downloaded and a corresponding common file system is constructed, when a second Profile is downloaded, it is assumed that the newly downloaded second Profile corresponds to the common file system. At this time, the common space already has the shared file system corresponding to the newly downloaded Profile, and the newly downloaded file of the second Profile may be sequentially compared with the shared files in the shared file system, so as to determine the file in the second Profile that is different from the shared file system.
At this time, for the part of the difference files with different contents, except for determining that the part of the difference files in the second Profile is the personalized file of the second Profile, the part of the difference files in the shared file system is also determined to be the personalized file of the first Profile, and is not used as the shared file any more.
For example, if the comparison shows that the file1 exists in the second Profile, the file1 also exists in the common file system, but the content of the file1 in the second Profile is different from the content of the file1 in the common file system, the file1 existing in the second Profile is used as the personalized file of the second Profile, and the file1 in the file system is used as the personalized file of the first Profile.
Similarly, after continuing to download the third Profile, assume that the third Profile also corresponds to the common file system. At this time, the common space already has the shared file system corresponding to the newly downloaded third Profile, and the files of the newly downloaded third Profile may be sequentially compared with the shared files in the shared file system, so as to determine the files in the third Profile that are different from the files in the shared file system.
For the part of the distinguishing files with different contents, which exist in the third Profile and also exist in the common file system, besides determining that the part of the distinguishing files in the third Profile are personalized files of the third Profile, the part of the common files in the common file system are also determined to be personalized files of the first Profile and the second Profile and are not used as common files any more.
It should be noted that, in the embodiment of the present application, it may be set that only one common file system is constructed, and the common file system corresponds to all profiles. At this time, after downloading a Profile, as long as it is detected that a common file system is created in the common space, it can be determined that the common file system corresponding to the Profile exists.
Further, in the embodiment of the present application, it is also possible to set a permission to construct a plurality of common file systems.
Optionally, different first identification values may be added to the profiles of different items, so that when a common file system is created, different second identification values matched with the different first identification values are allocated to the created common file system, and when the corresponding common file system is determined, whether a common file system matched with the first identification value exists in the public space of the smart card may be determined according to the first identification value in the Profile, so as to implement the determination.
It should be noted that the first identification value in the Profile may be set by a provider of the Profile according to actual needs. For example in the header field of the Profile.
For example, in an actual application process, the file difference between profiles corresponding to the same project is often smaller than the file difference between profiles corresponding to different projects. Therefore, in this embodiment of the application, the provider of the Profile may add the same first identification value to the Profile belonging to the same project and add different first identification values to the profiles belonging to different projects according to the difference of the projects to which the Profile belongs.
In this embodiment of the application, when the second identification value is assigned according to the first identification value, the first identification value may be assigned to the common file system as the second identification value, so that whether the common file system is the common file system corresponding to the Profile is determined by determining whether the first identification value of the Profile is the same as the second identification value of the common file system.
It should be noted that, in the embodiment of the present application, there are at least the following two possible processing manners for the identified personalized document:
one possible way is: the personalized files in each Profile can be stored in each Profile, so that only shared files exist in the shared file system, and the reusability of the shared file system is ensured.
Yet another possibility is: personalized files in each Profile can be stored in the common file system, and only the association relationship between the personalized files and the profiles needs to be established (for example, a unique identifier is allocated to each Profile, and the unique identifiers of the profiles corresponding to the personalized files are recorded in the common file system in an associated manner). Therefore, after the Profile is activated, the identification of the personalized file corresponding to the Profile in the shared file system can be realized according to the unique identifier of the Profile.
In the embodiment of the present application, each file may be stored in a chained array or the like, but is not limited thereto.
It should also be noted that in the embodiment of the present application, after the common file system is constructed, normal use of each Profile may be used.
Referring to fig. 2, fig. 2 shows a Profile management method applied to a smart card according to an embodiment of the present application, including:
s201: and when receiving an activation instruction, activating the Profile indicated by the activation instruction.
In this embodiment of the present application, the activation instruction may be an instruction issued by a user to switch to a certain Profile, or may also be an instruction generated after the smart card is powered on to instruct to activate a default certain Profile, which is not limited in this embodiment of the present application.
S202: and calling the common file system corresponding to the Profile as the file system of the Profile.
In the embodiment of the present application, if only one common file system is set to exist, the file system in the public space may be directly acquired. And if a plurality of common file systems can exist, the activated first identification value of the Profile can be read, so that the common file system with the second identification value matched with the first identification value is found in the public space through the first identification value, and the common file system is called as the file system of the Profile.
It should be noted that if the personalized file of the Profile is stored in the Profile, the file in the Profile and the common file system may be linked during the process of using the Profile. When a certain file needs to be used in the using process, the corresponding file is searched in the Profile, and when the file does not exist in the Profile, the file is searched in the common file system. In addition, personalized files in the Profile can also be synchronized to the common file system first, so that when a certain file needs to be used in the using process, the file is directly searched in the common file system. It should be noted that, in the way of synchronizing the personalized files in the Profile to the common file system, when Profile switching is required or the smart card is powered off, the personalized files in the common file system may be removed first.
If the personalized files of the profiles are stored in the shared file system and are associated with each Profile. In the process of using the Profile, the unique identifier of the Profile may be obtained first, and then the personalized file of the Profile in the common file system corresponding to the Profile is specified based on the unique identifier of the Profile. Therefore, when a certain file needs to be used in the using process, the corresponding file is directly searched in the Profile, and the searched file is the common file in the common file system and the personalized file corresponding to the Profile.
It should be noted that, in the embodiment of the present application, if the content of the common file in the common file system needs to be modified in the using process of the Profile, the common file may be saved in all the profiles with the use permission of the common file system except the Profile before modification, and the common file may be saved in the Profile as the personalized file of the Profile after modification; or, the common file may be used as a personalized file to be associated with all profiles having the common file system use permission except the Profile before modification, and the common file may be used as a personalized file of the Profile to be associated with the Profile after modification. Therefore, the association of the personalized data caused in the using process is realized, and the reusability of the shared file system is ensured.
In addition, in the practical application process, there are often files, such as short message files and phone files, which the user wishes to reuse by each Profile even if the content of the file is modified.
For this reason, in a possible implementation manner of the embodiment of the present application, the special shared files may be predefined, so that in the process of using the Profile, if the content of the preset special shared file in the shared file system is modified, the preset special shared file is kept as a file in the shared file system shared by all corresponding profiles, and is not adjusted to be a personalized file in the foregoing manner.
In the embodiment of the present application, the special shared file may be set by an engineer or a user, for example, may be set as a short message file, a phone file, and the like.
According to the Profile downloading method and the Profile management method provided by the embodiment of the application, the common file system with the other files except the personalized file in the Profile is constructed, so that when one Profile is downloaded, only the personalized file of the Profile needs to be stored, and for the files except the personalized file, the common file system is multiplexed to obtain the files, so that the consumption of the space resources of the smart card by the file system corresponding to each Profile is reduced, and more spaces can be used for creating the files and the contents.
Example two:
the present embodiment takes several specific example situations as examples on the basis of the first embodiment, and further exemplifies the present application.
Example one:
firstly, the files in the Profile that can be personalized files can be predefined according to the practical experience of engineers: an EF ICCID2FE2 file under an MF 3F00 file, an EF IMSI6F07 file under a DF7F20 file, an EF ACC 6F78 file under a DF7F20 file, an EF IMSI6F07 file under an ADF7FF0 file, and an EF ACC 6F78 file under an ADF7FF0 file.
Then, when downloading the content of the Profile1, a set of shared file system is created, and the file of the Profile1 is stored in the shared file system. According to the defined files, identifying the personalized files of the Profile1, storing the personalized files into the Profile1, wherein the storage mode can be, but is not limited to, a chained array mode, and storing the rest files except the personalized files into a common file system. And making a first identification value A for the Profile1 identification, and making a second identification value A for the common file system identification.
And when downloading the content of the Profile2, not creating a new common file system, identifying the personalized file of the Profile2 according to the defined file, and storing the personalized file into the Profile 2. And also making a first identification value A for the Profile2 identification, wherein the identification uses a common file system A. Similarly, when downloading the Profile subsequently, the processing mode is the same as that of Profile2, and at this time, the structure in the obtained smart card is as shown in fig. 3.
Example two:
when downloading the content of the Profile1, creating a set of shared file systems, storing the files of the Profile1 to the shared file systems, identifying the first identification value of the Profile1 as A, and identifying the second identification value of the shared file systems as A.
When the content of the Profile2 is downloaded, a new file system is not created, and the first identification value of the Profile2 is identified as A; and simultaneously comparing the file contents of the same files, identifying files in the Profile2, which are different from the files in the common file system, storing the files in the Profile2 into the Profile2, and storing the files in the common file system into the Profile 1.
For example, comparing the EF ICCID2FE2 file under the MF 3F00 file, finding the content of the EF ICCID2FE2 file in the common file system, and then comparing with the content of the EF ICCID2FE2 file in the downloaded Profile2, otherwise, retaining the EF ICCID2FE2 file in the Profile2, for example, using but not limited to chained array save data, and saving the EF cid2FE2 file in the common file system in the Profile 1. At this time, files of the same file system but with partially different file contents are identified and recorded in the respective profiles.
Similarly, when downloading other profiles n, marking the mark as a first mark value A, marking the first mark value as A, identifying the files different from the shared file system again, and respectively storing and recording the files with different contents in the shared file system into the first n-1 profiles. At this time, the structure inside the smart card is obtained as shown in fig. 4.
Example three:
in the Profile format, a field "Profile file system identifier" may be added to the Profile header part to identify the codes of the file system in the Profile.
When downloading the content of the Profile1, whether the shared file system a is created is searched according to the "Profile file system identifier = a" of the Profile header part in the Profile1, if the shared file system a is not created, the shared file system a is created by adopting the method of the second example, and the "Profile file system identifier = a" identifier of the Profile1 is recorded as the first identifier value a, and the identifier uses the shared file system a.
When downloading the content of Profile2, the "Profile FileFileSystemidentifier" of the Profile header part in Profile2 is also obtained. If the "Profile filesystemldentifier = a" and the common file system a is already created, the new common file system is not created any more, the first identification value a is also made for the Profile2 identification, and the common file system a is also used for the identification. And simultaneously, storing the personalized file into the Profile and the Profile2 by adopting the mode of the second example.
And then, when the Profile is continuously downloaded, whether the common file system is established is determined according to the value of the Profile file system identifier, and if the common file system is established, the method of the second example is adopted. If not, a new common file system is established according to the value of establishing the profileFileSystemIdentifier, and then the operation is performed according to the mode of the second example.
After downloading the Profile for multiple times, the structure in the smart card is obtained as shown in fig. 5.
In the above example, profile1 and Profile2 … sequentially represent the first downloaded Profile and the second downloaded Profile ….
In the above example, when a certain Profile is activated, the corresponding common file system may be determined through the first identifier of the Profile. And then the personalized files in the activated Profile can be synchronized into the common file system, so that the common file system is convenient to use.
In the process of using the activated Profile, if the content of a certain file in the shared file system corresponding to the Profile needs to be changed, then:
if the file needing to be modified is the personalized file of the Profile, the personalized file in the Profile is synchronously modified, and the data consistency is ensured. If the file to be modified is not the personalized file of the Profile, the content before modification of the file is stored in the rest profiles which can share the common file system, then the files in the common file system are modified, and the modified file is stored in the Profile as the personalized file of the Profile.
In addition, in the embodiment of the present application, a phone file, a short message file, and the like may be identified as special shared files, so that after the contents of the special shared files are modified, the files are not synchronized into the profiles.
By the scheme, the common file system is created, and the individual personalized files of the profiles are stored, so that the space consumption of the file system is greatly reduced, and the smart card can have more space. If two profiles are downloaded, the file system would need to consume 20K of space, assuming that the creation of a file system for one Profile would need to consume 10K of space. By adopting the scheme of the embodiment of the application, if the shared file system consumes 10K of space, and the space for recording and storing the values of different file contents consumes about 1 to 2K, the two profiles consume about 11K to 12K in total, and the more the downloaded profiles are, the more the space is consumed.
Example three:
based on the same inventive concept, the embodiment of the present application further provides a Profile downloading device 100 and a Profile management device 200. Referring to fig. 6 and 7, fig. 6 illustrates a Profile download apparatus using the method shown in fig. 1, and fig. 7 illustrates a Profile management apparatus using the method shown in fig. 2. It should be understood that the specific functions of the apparatus 100 and the apparatus 200 can be referred to the above description, and the detailed description is omitted here as appropriate to avoid redundancy. The devices 100 and 200 include at least one software functional module that can be stored in memory in the form of software or firmware or solidified in the operating system of the devices 100 and 200. Specifically, the method comprises the following steps:
referring to fig. 6, the apparatus 100 is applied to a smart card device, and includes: a download module 101 and a first processing module 102. Wherein:
the downloading module 101 is configured to download a Profile and identify a personalized file in files in the Profile;
the first processing module 102 is configured to, when a common file system corresponding to the Profile is created in a public space of the smart card, remove, from the Profile, other files except the personalized file; or when a common file system corresponding to the Profile is created in the public space of the smart card, adding the personalized file into the common file system, associating the personalized file with the Profile, and deleting all files in the Profile;
wherein the common file system is usable by a plurality of profiles including the Profile, and has a common file therein which is reusable by the plurality of profiles; the common files are the rest files in the Profile except the personalized files.
In a feasible implementation manner of the embodiment of the present application, the downloading module 101 is specifically configured to determine whether a file with a file identifier that is consistent with a preset file identifier exists in the Profile; if so, determining the file with the file identification consistent with the preset file identification as the personalized file.
In the above feasible embodiment, the first processing module 102 is further configured to determine whether a common file system corresponding to a Profile already exists in the public space after the downloading module 101 downloads the Profile; and if the personalized file does not exist in the public space, creating a common file system corresponding to the Profile in the public space, and storing the other files except the personalized file in the Profile in the common file system.
In another possible implementation manner of the embodiment of the present application, the downloading module 101 is specifically configured to compare files in the Profile with files in the common file system in sequence, and determine files in the Profile that are different from the files in the common file system; and the file in the Profile, which is different from the file in the common file system, is the personalized file of the Profile.
In the above feasible embodiment, the first processing module 102 is further configured to determine whether a common file system corresponding to the Profile already exists in the public space before the downloading module 101 identifies a personalized file in the files in the Profile; and if the common file system corresponding to the Profile does not exist in the common space, creating the common file system corresponding to the Profile in the common space, and storing all files in the Profile in the common file system.
In the foregoing feasible embodiment, the first processing module 102 is further configured to, in the process of determining a file in the Profile that is different from a file in the common file system, store a file in the common file system that is different from the content of the Profile into all the profiles with the usage right of the common file system except for the Profile, and delete the file with the different content from the common file system; or, the file in the shared file system, which is different from the content of the Profile, is used as a personalized file, and is associated with all the profiles except the Profile, which have the use permission of the shared file system.
In the above two possible embodiments, the Profile has a first identification value therein; the first processing module 102 is specifically configured to determine, according to a first identifier value in the Profile, whether a common file system matching the first identifier value exists in a public space of the smart card; and if so, determining that the common file system is the common file system corresponding to the Profile.
In this embodiment of the application, the first processing module 102 is further configured to, after the common file system corresponding to the Profile is created in the public space, allocate a second identification value matching the first identification value to the created common file system.
Referring to fig. 7, the apparatus 200 is applied to a smart card device, and includes: an activation module 201 and a second processing module 202. Wherein:
the activation module 201 is configured to activate the Profile indicated by the activation instruction when the activation instruction is received;
the second processing module 202 is configured to call a common file system corresponding to the Profile as a file system of the Profile; the shared file system has the remaining files in the Profile except the personalized file, and the shared file system can be used by a plurality of profiles including the Profile.
In this embodiment of the application, the second processing module 202 is further configured to obtain a first identifier value of the Profile; searching a common file system matched with the first identification value in the public space of the intelligent card; and the searched common file system is the common file system corresponding to the Profile.
In this embodiment of the application, the second processing module 202 is further configured to, in the process of using the Profile, if the content of the common file in the common file system needs to be modified, then: the common file is saved in all the profiles with the common file system use permission except the Profile before modification, and the common file is saved in the Profile as a personalized file of the Profile after modification; or, before modification, the common file is used as a personalized file to be associated with all the profiles with the common file system use authority except the Profile, and after modification, the common file is used as the personalized file of the Profile to be associated with the Profile.
In this embodiment of the application, the second processing module 202 is further configured to, in a process of using the Profile, if content of a preset special common file in the common file system is modified, keep the preset special common file as a file in the common file system for all corresponding profiles to share.
In an embodiment of the present application, the predetermined special shared file is at least one of: short message files, phone files.
It should be understood that, for the sake of brevity, the contents described in some embodiments are not repeated in this embodiment.
Example four:
the present embodiment provides a smart card, which is shown in fig. 8, and includes a processor 801, a memory 802, and a serial communication unit 803. Wherein:
the serial communication unit 803 is used to realize connection communication between the processor 801 and the memory 802.
The processor 801 is configured to execute one or more programs stored in the memory 802 to implement the Profile downloading method or the Profile management method in the first embodiment and/or the second embodiment.
It will be appreciated that the configuration shown in fig. 8 is merely illustrative and that a smart card may also include more or fewer components than shown in fig. 8 or have a different configuration than shown in fig. 8. As long as the smart card can support multiple Profile downloads, it may be, for example, an eSIM card.
The present embodiment further provides a readable storage medium, such as a floppy disk, an optical disk, a hard disk, a flash Memory, a usb (Secure Digital Card), an MMC (Multimedia Card), etc., where one or more programs for implementing the above steps are stored in the readable storage medium, and the one or more programs may be executed by one or more processors to implement the steps of the Profile downloading method executed by the service distribution device in the first embodiment and/or the second embodiment, or to implement the Profile downloading method or the Profile management method in the first embodiment and/or the second embodiment. And will not be described in detail herein.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
In addition, units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
Furthermore, the functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
In this context, a plurality means two or more.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made to the present application by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (10)
1. A Profile management method is applied to a smart card and comprises the following steps:
activating the Profile indicated by the activation instruction when the activation instruction is received;
calling a common file system corresponding to the Profile as a file system of the Profile; the shared file system is provided with other files except personalized files in the profiles, and can be used by a plurality of profiles including the profiles;
the method further comprises the following steps:
in the using process of the Profile, if the content of the common file in the common file system needs to be modified, then:
the common file is saved in all the profiles with the common file system use permission except the Profile before modification, and the common file is saved in the Profile as a personalized file of the Profile after modification;
or, before modification, the common file is used as a personalized file to be associated with all the profiles with the common file system use authority except the Profile, and after modification, the common file is used as the personalized file of the Profile to be associated with the Profile.
2. The Profile management method according to claim 1, wherein the method further comprises:
acquiring a first identification value of the Profile;
finding a common file system with a second identification value matched with the first identification value in the public space of the intelligent card; and the searched common file system is the common file system corresponding to the Profile.
3. The Profile management method according to claim 1 or 2, wherein the method further comprises:
and in the using process of the Profile, if the content of the preset special shared file in the shared file system is modified, keeping the preset special shared file as a file shared by all corresponding profiles in the shared file system.
4. The Profile management method according to claim 3, wherein the preset special shared file is at least one of:
a short message file;
a telephone file.
5. The utility model provides a Profile management device which characterized in that, is applied to the smart card, includes: an activation module and a second processing module;
the activation module is used for activating the Profile indicated by the activation instruction when the activation instruction is received;
the second processing module is used for calling the common file system corresponding to the Profile as the file system of the Profile; the shared file system is provided with other files except personalized files in the profiles, and can be used by a plurality of profiles including the profiles;
the second processing module is further configured to, in a use process of the Profile, if the content of the common file in the common file system needs to be modified, then:
the common file is stored in all the profiles with the common file system use permission except the Profile before modification, and the common file is stored in the Profile as a personalized file of the Profile after modification;
or, before modification, the common file is used as a personalized file to be associated with all the profiles with the common file system use authority except the Profile, and after modification, the common file is used as the personalized file of the Profile to be associated with the Profile.
6. The Profile management apparatus of claim 5, wherein,
the second processing module is further configured to acquire a first identification value of the Profile; finding a second identification value matched with the first identification value in the public space of the intelligent card; and the searched common file system is the common file system corresponding to the Profile.
7. The Profile management apparatus according to claim 5 or 6, wherein the second processing module is further configured to, during the use of the Profile, if the content of a preset special shared file in the shared file system is modified, maintain the preset special shared file as a file shared by all corresponding profiles in the shared file system.
8. The Profile management apparatus according to claim 7, wherein the preset special shared file is at least one of:
a short message file;
a telephone file.
9. A smart card, comprising: a processor, a memory and a serial communication unit;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more programs stored in the memory to implement the Profile management method according to any one of claims 1 to 4.
10. A readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the Profile management method according to any one of claims 1 to 4.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011558286.7A CN112702728B (en) | 2020-12-24 | 2020-12-24 | User profile management method and device, smart card and readable storage medium |
| CN202211294461.5A CN115484585A (en) | 2020-12-24 | 2020-12-24 | User configuration file downloading method and device, smart card and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011558286.7A CN112702728B (en) | 2020-12-24 | 2020-12-24 | User profile management method and device, smart card and readable storage medium |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211294461.5A Division CN115484585A (en) | 2020-12-24 | 2020-12-24 | User configuration file downloading method and device, smart card and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112702728A CN112702728A (en) | 2021-04-23 |
| CN112702728B true CN112702728B (en) | 2022-12-06 |
Family
ID=75510316
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011558286.7A Active CN112702728B (en) | 2020-12-24 | 2020-12-24 | User profile management method and device, smart card and readable storage medium |
| CN202211294461.5A Pending CN115484585A (en) | 2020-12-24 | 2020-12-24 | User configuration file downloading method and device, smart card and storage medium |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211294461.5A Pending CN115484585A (en) | 2020-12-24 | 2020-12-24 | User configuration file downloading method and device, smart card and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN112702728B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104396289A (en) * | 2012-05-11 | 2015-03-04 | 苹果公司 | Provisioning an embedded subscriber identity module |
| CN109495874A (en) * | 2018-12-28 | 2019-03-19 | 恒宝股份有限公司 | The method and apparatus of Profile downloading |
| CN110475241A (en) * | 2019-08-08 | 2019-11-19 | 宇龙计算机通信科技(深圳)有限公司 | Loading method, device and the electronic equipment of MBN file |
| CN111918274A (en) * | 2020-07-30 | 2020-11-10 | 恒宝股份有限公司 | Code number configuration and management method and device, electronic equipment and readable storage medium |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100240413A1 (en) * | 2009-03-21 | 2010-09-23 | Microsoft Corporation | Smart Card File System |
| CN104469737B (en) * | 2014-11-17 | 2018-09-11 | 中国联合网络通信集团有限公司 | A kind of universal embedded integrated circuit card and its user signing contract information Activiation method |
| EP3276998A1 (en) * | 2016-07-29 | 2018-01-31 | Deutsche Telekom AG | Profile authorization server for download of sim profiles |
| CN106446158B (en) * | 2016-09-23 | 2022-12-20 | 宇龙计算机通信科技(深圳)有限公司 | Application data sharing method, sharing device and terminal |
| CN108134811B (en) * | 2017-11-10 | 2021-08-27 | 阿里巴巴（中国）有限公司 | Method, device and system for distributing or downloading target file |
| CN108040329B (en) * | 2017-12-07 | 2019-03-19 | 恒宝股份有限公司 | The load and its management method of eSIM module and its subscription data |
| CN109963275B (en) * | 2017-12-22 | 2022-01-28 | 中兴通讯股份有限公司 | Sending method and receiving method of subscription data and processing system of subscription data |
| IT201800005510A1 (en) * | 2018-05-18 | 2019-11-18 | PROCEDURE FOR THE GENERATION OF PERSONALIZED DATA OF PROFILE PACKAGE IN INTEGRATED CIRCUIT CARDS, CORRESPONDING SYSTEM AND IT PRODUCT | |
| CN109947852A (en) * | 2019-03-15 | 2019-06-28 | 北京思特奇信息技术股份有限公司 | A kind of detailed single memory space method for reducing body weight, device and computer storage medium |
-
2020
- 2020-12-24 CN CN202011558286.7A patent/CN112702728B/en active Active
- 2020-12-24 CN CN202211294461.5A patent/CN115484585A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104396289A (en) * | 2012-05-11 | 2015-03-04 | 苹果公司 | Provisioning an embedded subscriber identity module |
| CN109495874A (en) * | 2018-12-28 | 2019-03-19 | 恒宝股份有限公司 | The method and apparatus of Profile downloading |
| CN110475241A (en) * | 2019-08-08 | 2019-11-19 | 宇龙计算机通信科技(深圳)有限公司 | Loading method, device and the electronic equipment of MBN file |
| CN111918274A (en) * | 2020-07-30 | 2020-11-10 | 恒宝股份有限公司 | Code number configuration and management method and device, electronic equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115484585A (en) | 2022-12-16 |
| CN112702728A (en) | 2021-04-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3043261A1 (en) | Software installation method, device and system | |
| CN110266763B (en) | Method, system and storage medium for implementing block chain network interconnected across network segments | |
| WO2016023199A1 (en) | Method, device and system for security domain management | |
| CN103716346A (en) | Management method and device of application on android handset client | |
| CN105786606A (en) | Data transferring method and system for intelligent terminals | |
| EP2911431A1 (en) | Communications system, mobile communications device, transition control device, transition control method, and transition control program | |
| CN111698675A (en) | Data processing method, device and computer readable storage medium | |
| CN111142885B (en) | eSIM equipment management method, device, equipment and storage medium | |
| CN109542841B (en) | Method for creating data snapshot in cluster and terminal equipment | |
| CN101583204B (en) | Method and system for realizing managing universal combined circuit card multiple application files | |
| CN105376728A (en) | Boot method and communication terminal | |
| CN112702728B (en) | User profile management method and device, smart card and readable storage medium | |
| CN107623705B (en) | Storage mode upgrading method, device and system based on video cloud storage system | |
| CN110798358B (en) | Distributed service identification method and device, computer readable medium and electronic equipment | |
| US8326933B2 (en) | Appearance package management method, system and device | |
| CN104717280A (en) | Data synchronism marking method and device | |
| CN111372237B (en) | eSIM card operator file management method and device | |
| CN105827739A (en) | Contact person information synchronization method, device, server and system | |
| CN111417109B (en) | eSIM card and operator file management method and management system thereof | |
| CN112380411B (en) | Sensitive word processing method, device, electronic equipment, system and storage medium | |
| CN110839068B (en) | Service request processing method and device, electronic equipment and readable storage medium | |
| CN111953722B (en) | Synchronization method and device for terminal address book | |
| CN113950035A (en) | Method and terminal for dynamically updating NFC (near field communication) capability and UICC (Universal Integrated Circuit card) | |
| CN111092765B (en) | Intelligent driving method, system, electronic device and readable storage medium | |
| CN115469961A (en) | Method and device for creating container group, electronic equipment and storage medium |
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 |