User configuration file downloading method, device, smart card and storage medium

Abstract

The present application provides a method, device, smart card and storage medium for downloading a user configuration file. The download method includes: downloading a user configuration file and identifying personalized files in the files in the user configuration file; when a shared file system corresponding to the user configuration file is created in a public space, the remaining files except the personalized file are removed from the user configuration file, or the personalized file is added to the shared file system, and the personalized file is associated with the user configuration file, and all files in the user configuration file are deleted. The shared file system can be used by multiple user configuration files including the user configuration file. In this way, by reusing the shared file system, when downloading the user configuration file, only the personalized file needs to be saved, which reduces the consumption of smart card space resources by the file system corresponding to the user configuration file.

Description

[0001] This application is a divisional application of Chinese patent application 202011558286.7, filed on December 24, 2020, entitled “User profile downloading method, management method, device, smart card and medium”. Technical Field

[0002] The present application relates to the technical field of smart cards, and in particular to a method and device for downloading a user configuration file, a smart card, and a storage medium. Background Art

[0003] eUICC (embedded Universal Integrated Circuit Card), also known as eSIM (embedded Subscriber Identifier Module), is a third-generation telecom smart card. When users use eSIM cards to sign up for operator information and apply for new mobile phone numbers, they mainly do so by downloading the corresponding Profile.

[0004] Currently, eSIM cards support downloading multiple profiles. There is no correlation between the profiles. They exist independently and do not affect each other. However, only one profile is allowed to be activated on the eSIM card at the same time, and other profiles need to be inactive. On the eSIM card, only the content of the activated profile can be used.

[0005] Each Profile will have a corresponding FileSystem (file system), which will contain a large number of files and file contents. Therefore, at present, every time an eSIM card downloads a Profile, it is necessary to save a set of file systems corresponding to the Profile in the eSIM card, which will greatly consume the space resources of the eSIM card, and the corresponding remaining space resources will be less, which will also affect the available space for downloading new Profiles and creating files and content. Summary of the invention

[0006] The purpose of the embodiments of the present application is to provide a Profile downloading method, a Profile management method, a device, a smart card and a readable storage medium to solve the above-mentioned problems.

[0007] An embodiment of the present application provides a profile downloading method, which is applied to a smart card, including: downloading a profile, and identifying personalized files in the files in the profile; when a shared file system corresponding to the profile is created in the public space of the smart card, removing the remaining files in the profile except the personalized files; or, when a shared file system corresponding to the profile is created in the public space of the smart card, adding the personalized files to the shared file system, associating the personalized files with the profile, and deleting all files in the profile; wherein the shared file system can be used by multiple profiles including the profile, and the shared file system has shared files that can be reused by the multiple profiles; the shared files are the remaining files in the profile except the personalized files.

[0008] In the above implementation process, a shared file system is constructed with the remaining files in the Profile except the personalized files, so that each time a Profile is downloaded, only the personalized files of the Profile need to be saved; the remaining files except the personalized files (i.e., shared files) can be obtained by reusing the shared file system, thereby reducing the consumption of smart card space resources by the file system corresponding to each Profile, so that more remaining space can be used to download new profiles and create files and content.

[0009] Further, the identifying of the personalized file in the files in the Profile includes: determining whether the Profile contains a file whose file identifier is consistent with a preset file identifier; if so, determining that the file whose file identifier is consistent with the preset file identifier is the personalized file.

[0010] In the above implementation process, by presetting the file identifiers (such as file names, etc.) of files that may be different between the Profiles, the personalized files in the Profile can be quickly identified by judging the file identifiers.

[0011] Furthermore, after downloading the Profile, the method further includes: determining whether a shared file system corresponding to the Profile already exists in the public space; if not, creating a shared file system corresponding to the Profile in the public space, and saving the remaining files in the Profile except the personalized file in the shared file system.

[0012] In the above implementation process, when there is no shared file system corresponding to the Profile, a shared file system is created and the remaining files in the Profile except the personalized files are saved in the shared file system. In this way, the shared file system is quickly created, which facilitates the subsequent reuse of the Profile of the shared file system.

[0013] Further, identifying personalized files in the files in the Profile includes: comparing the files in the Profile with the files in the shared file system in turn, and determining the files in the Profile that are different from those in the shared file system; the files in the Profile that are different from those in the shared file system are personalized files of the Profile.

[0014] In the above implementation process, by comparing with the files in the common file system, the part of the personalized files in the Profile that cannot be reused can be quickly determined.

[0015] Furthermore, before identifying personalized files in the files in the Profile, the method also includes: determining whether a shared file system corresponding to the Profile already exists in the public space; if a shared file system corresponding to the Profile does not exist in the public space, creating a shared file system corresponding to the Profile in the public space, and saving all files in the Profile in the shared file system.

[0016] In the above implementation process, when there is no corresponding shared file system for the Profile, a shared file system is constructed through all the files in the Profile, so as to determine the personalized file for file comparison when downloading a new profile. The personalized file determined in this way is more in line with the actual situation of each Profile, and the determination of the personalized file is also more flexible.

[0017] Furthermore, in the process of determining files in the Profile that are different from those in the shared file system, the method further includes: saving the files in the shared file system that are different from the content of the profile into all Profiles other than the Profile that have permission to use the shared file system, and deleting the files with different contents from the shared file system; or, treating the files in the shared file system that are different from the content of the profile as personalized files and associating them with all Profiles other than the Profile that have permission to use the shared file system.

[0018] 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 contents of the file are the same in each profile downloaded before the profile, and only differ within the profile. To this end, the file with different contents in the shared file system can be used as the personalized file of each profile downloaded before the profile, thereby ensuring the accurate determination of the personalized file of each profile, and ensuring that when different profiles reuse the shared file system, the shared file system can be used correctly without causing file errors.

[0019] Furthermore, the Profile contains a first identification value; determining whether a shared file system corresponding to the Profile already exists in the public space includes: determining, based on the first identification value in the Profile, whether a shared file system matching the first identification value exists in the public space of the smart card; if so, determining that the shared file system is the shared file system corresponding to the Profile.

[0020] In actual applications, the differences between Profiles corresponding to different projects are often greater than the differences between Profiles corresponding to the same project. To this end, in the embodiment of the present application, a first identification value can be set for the Profile in advance, and a common file system for each Profile can be constructed based on the first identification value, so that it can be quickly determined whether there is a corresponding common file system for the latest downloaded Profile based on the first identification value.

[0021] Furthermore, after creating a shared file system corresponding to the Profile in the public space, the method further includes: allocating a second identification value matching the first identification value to the created shared file system.

[0022] An embodiment of the present application also provides a Profile management method, which is applied to a smart card, comprising: upon receiving an activation instruction, activating the Profile indicated by the activation instruction; calling a shared 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 files, and the shared file system can be used by multiple Profiles including the Profile.

[0023] In the above implementation process, a common file system is constructed with other files in the Profile except the personalized files, so that when each Profile is activated, the corresponding common file system can be called as its own file system, so that each Profile can be used normally without having to create its own file system for each Profile, thereby reducing the consumption of smart card space resources by the file system, so that more remaining space can be used to download new profiles and create files and content.

[0024] Furthermore, the method further includes: acquiring a first identification value of the Profile; searching for a shared file system matching the first identification value in a public space of the smart card; and the found shared file system is a shared file system corresponding to the Profile.

[0025] Furthermore, the method also includes: during the use of the Profile, if it is necessary to modify the content of the shared file in the shared file system, then: before the modification, the shared file is saved in all Profiles other than the Profile that have the permission to use the shared file system, and after the modification, the shared file is saved in the Profile as a personalized file of the Profile; or, before the modification, the shared file is associated with all Profiles other than the Profile that have the permission to use the shared file system as a personalized file, and after the modification, the shared file is associated with the Profile as a personalized file of the Profile.

[0026] In the above implementation process, the shared file modified during the use of the currently activated Profile is saved as the personalized file of the Profile in the Profile or associated with the Profile, and the shared file before modification is saved as the personalized file of all Profiles with the permission to use the shared file system except the Profile in the Profile or associated with these Profiles. In this way, the shared file system can be updated according to the personalized file generated during the use process, ensuring the reusability of the shared file system for each Profile.

[0027] Furthermore, the method also includes: during the use of the Profile, if the content of a preset special shared file in the shared file system is modified, then the preset special shared file is maintained as a file shared by all corresponding Profiles in the shared file system.

[0028] Furthermore, the preset special shared file is at least one of the following: a text message file; a phone book file.

[0029] In actual use, for SMS files, phone book files and other files, users often hope that the saved content is universal no matter which Profile is used. For example, when a user saves a new contact when using Profile 1, the user usually does not want the contact to disappear after switching to Profile 2. For this reason, in the above implementation process, by configuring special shared files, it is possible to avoid the modification of these files during the use of Profile, which causes these files to become personalized files, thereby improving the user experience.

[0030] An embodiment of the present application also provides a Profile downloading device, which is applied to a smart card, including: applied to a smart card, including: a downloading module and a first processing module; the downloading module is used to download the Profile and identify the personalized files in the files in the Profile; the first processing module is used to remove the remaining files except the personalized files in the Profile when a shared file system corresponding to the Profile is created in the public space of the smart card; or, when a shared file system corresponding to the Profile is created in the public space of the smart card, add the personalized files to the shared file system, associate the personalized files with the Profile, and delete all files in the Profile; wherein the shared file system has the remaining files in the Profile except the personalized files, and the shared file system can be used by multiple Profiles including the Profile.

[0031] An embodiment of the present application also 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 to activate the Profile indicated by the activation instruction when receiving the activation instruction; the second processing module is used to call the shared 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 multiple Profiles including the Profile.

[0032] An embodiment of the present application also provides a smart card, including a processor, a memory and a serial communication unit; the serial communication unit is used to realize connection communication between the processor and the memory; the processor is used to execute one or more programs stored in the memory to implement any of the above-mentioned Profile download methods, and / or implement any of the above-mentioned Profile management methods.

[0033] An embodiment of the present application also provides a readable storage medium, which stores one or more programs. The one or more programs can be executed by one or more processors to implement any of the above-mentioned Profile management methods. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0035] Figure 1 A schematic diagram of a flow chart of a Profile downloading method provided in an embodiment of the present application;

[0036] Figure 2 A flow chart of a Profile management method provided in an embodiment of the present application;

[0037] Figure 3 A schematic diagram of the structure of a Profile in a smart card provided in an embodiment of the present application;

[0038] Figure 4 A schematic diagram of the structure of another profile in a smart card provided in an embodiment of the present application;

[0039] Figure 5 A schematic diagram of the structure of another profile in a smart card provided in an embodiment of the present application;

[0040] Figure 6 A schematic diagram of the structure of a Profile downloading device provided in an embodiment of the present application;

[0041] Figure 7 A schematic diagram of the structure of a Profile management device provided in an embodiment of the present application;

[0042] Figure 8 A schematic diagram of the structure of a smart card provided in an embodiment of the present application. DETAILED DESCRIPTION

[0043] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0044] Embodiment 1:

[0045] In order to improve the utilization of the space in the smart card and reduce the space resource consumption of downloading the Profile, so that more space is left in the smart card for downloading new profiles and creating files and content, the present application provides a Profile download method applicable to the smart card. Figure 1 As shown, Figure 1 A schematic diagram of a flow chart of a Profile download method provided in an embodiment of the present application includes:

[0046] S101: Download the Profile and identify personalized files in the files in the Profile.

[0047] It should be noted that the smart card described in the embodiments of the present application refers to a smart card that can support downloading multiple profiles, such as an eSIM card.

[0048] In the embodiment of the present application, the smart card can download the required Profile from a resource server provided by the operator.

[0049] S102: When a shared file system corresponding to the Profile is created in the public space of the smart card, the remaining files except the personalized file are deleted in the Profile; or, when a shared file system corresponding to the Profile is created in the public space of the smart card, the personalized file is added to the shared file system, the personalized file is associated with the Profile, and all files in the Profile are deleted.

[0050] It should be noted that, in the embodiment of the present application, the public space of the smart card refers to the space in the smart card that can be accessed by each Profile.

[0051] It should be understood that in actual application, for different Profiles, the file systems of different Profiles often have a large number of files with exactly the same content. In the embodiment of the present application, these files can be used as common files to construct a common file system for reuse by each Profile.

[0052] In a feasible implementation of the embodiment of the present application, common files of various profiles that may be downloaded by the smart card may be predefined, so as to construct a common file system in the smart card.

[0053] For example, engineers can obtain common files of various profiles based on experience and save each common file in 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, thereby building a common file system with these common files in the smart card.

[0054] In addition, in an embodiment of the present application, engineers can also obtain different files of various Profiles based on experience summary, and record the file identifiers of these files in advance, so that when downloading the Profile, it can be determined whether there are files in the Profile whose file identifiers are consistent with the preset file identifiers, and these files whose file identifiers are consistent with the preset file identifiers can be used as personalized files.

[0055] In the embodiment of the present application, the file identifier may be a file name or a file path, etc.

[0056] For example, assume that an engineer sets the EF ICCID 2FE2 file under the MF 3F00 file, the EFIMSI 6F07 file under the DF7F20 file, the EF ACC 6F78 file under the DF 7F20 file, the EF IMSI 6F07 file under the ADF7FF0 file, and the EF ACC 6F78 file under the ADF7FF0 file as personalized files, so that the file paths MF3F00-EF IMSI6F07, DF 7F20-EF IMSI 6F07, DF 7F20-EF ACC 6F78, ADF 7FF0-EFIMSI6F07, ADF 7FF0-EF ACC 6F78, etc. can be pre-defined in the smart card ("- " indicates from the upper file to the lower file).

[0057] At this point, in another feasible implementation of the embodiment of the present application, after downloading the Profile, it can be determined whether a shared file system corresponding to the Profile already exists in the public space. If it does not exist, the personalized files in the Profile can be identified by the above method, and a shared file system corresponding to the Profile can be created in the public space. The remaining files in the Profile except the personalized files can be saved in the shared file system, thereby obtaining a shared file system.

[0058] It should be understood that in the above feasible implementation mode, all files in the Profile may also be saved in the shared file system, thereby obtaining a shared file system.

[0059] In addition, in the embodiment of the present application, the personalized files of each Profile may be identified not through a method preset by an engineer, but based on the comparison of files in different Profiles to continuously determine the personalized files of each Profile.

[0060] For example, in the embodiment of the present application, after downloading the Profile, the files in the Profile can be compared with the common files in the common file system in turn, so as to determine the files that are different between the Profile and the common file system. These different files are the personalized files of the Profile.

[0061] It should be noted that in the embodiment of the present application, after downloading the Profile, it can be determined whether the shared file system corresponding to the Profile already exists in the public space. If not, a shared file system corresponding to the Profile is created in the public space, and all files in the Profile are saved in the shared file system.

[0062] At this time, since the files in the shared file system are completely identical to the files in the Profile, the comparison result is that the Profile currently has no personalized data relative to the shared file system, so the files in the Profile do not need to be retained at all.

[0063] It should be noted that there are usually two types of files that are different between the compared Profile and the shared file system:

[0064] 1. The profile exists, but the corresponding shared file does not exist in the shared file system.

[0065] 2. The shared file exists in the Profile and the corresponding shared file also exists in the shared file system, but the content of the file in the Profile is different from the content of the shared file in the shared file system.

[0066] For the first type of difference file, it can be directly used as the personalized file of the Profile. For the second type of difference file, in addition to using it as the personalized file of the Profile, the corresponding common file in the file system also needs to be used as the personalized file of all Profiles corresponding to the common file system downloaded before the Profile.

[0067] For example, after downloading the first profile and building the corresponding shared file system, when downloading the second profile, it is assumed that the newly downloaded second profile corresponds to the shared file system. At this time, the shared file system corresponding to the newly downloaded profile already exists in the public space, and the files of the newly downloaded second profile can be compared with the shared files in the shared file system in turn to determine the files in the second profile that are different from those in the shared file system.

[0068] At this time, for the part of the difference file that exists in the second Profile and has a corresponding shared file in the shared file system but has different content, in addition to determining that the part of the difference file in the second Profile is the personalized file of the second Profile, the part of the shared file in the shared file system will also be determined as the personalized file of the first Profile, and it will no longer be regarded as a shared file.

[0069] For example, the comparison finds that there is file 1 in the second profile and file 1 in the shared file system, but the content of file 1 in the second profile is different from the content of file 1 in the shared file system. In this case, file 1 in the second profile is used as the personalized file of the second profile, and file 1 in the file system is used as the personalized file of the first profile.

[0070] Similarly, when the third profile is downloaded, assuming that the third profile also corresponds to the shared file system, the shared file system corresponding to the newly downloaded third profile already exists in the public space, and the files of the newly downloaded third profile can be compared with the shared files in the shared file system in turn to determine the files in the third profile that are different from those in the shared file system.

[0071] For the difference files that exist in the third Profile and have corresponding shared files in the shared file system but have different contents, in addition to determining that the difference files in the third Profile are personalized files of the third Profile, the shared files in the shared file system are also determined to be personalized files of the first Profile and the second Profile, and are no longer considered shared files.

[0072] It should be noted that in the embodiment of the present application, it can be set to build only one common file system, which corresponds to all profiles. In this case, after downloading a profile, as long as a common file system is detected to be created in the public space, it can be determined that there is a common file system corresponding to the profile.

[0073] In addition, in the embodiment of the present application, it is also possible to set up to allow the construction of multiple shared file systems.

[0074] Optionally, different first identification values ​​can be added to the Profiles of different projects, so that when a shared file system is created, different second identification values ​​matching the different first identification values ​​can be assigned to the created shared file system. Therefore, when determining the corresponding shared file system, it can be determined based on the first identification value in the Profile whether there is a shared file system matching the first identification value in the public space of the smart card.

[0075] It should be noted that the first identification value in the Profile can be set by the provider of the Profile according to actual needs, for example, in the header field of the Profile.

[0076] For example, in actual application, the file differences between Profiles corresponding to the same project are often smaller than the file differences between Profiles corresponding to different projects. Therefore, in the embodiment of the present application, the provider of the Profile can add the same first identification value to the Profiles belonging to the same project and add different first identification values ​​to the Profiles belonging to different projects according to the different projects to which the Profiles belong.

[0077] In an embodiment of the present application, when the second identification value is assigned according to the first identification value, the first identification value can be assigned to the shared file system as the second identification value, thereby determining whether the shared file system is the shared file system corresponding to the Profile by judging whether the first identification value of the Profile is the same as the second identification value of the shared file system.

[0078] It should be noted that in the embodiment of the present application, there are at least the following two feasible processing methods for the identified personalized file:

[0079] One feasible way is to save the personalized files in each Profile in each Profile, so that only the shared files exist in the shared file system, thus ensuring the reusability of the shared file system.

[0080] Another feasible way is to save the personalized files in each Profile in a shared file system, and only need to build the association relationship between these personalized files and each Profile (for example, assign a unique identifier to each Profile, and record the unique identifier of each Profile corresponding to each personalized file in the shared file system). In this way, after activating the Profile, the personalized file corresponding to itself in the shared file system can be identified according to the unique identifier of the Profile.

[0081] In the embodiment of the present application, each file can be saved in a linked array or the like, but this is not a limitation.

[0082] It should also be noted that in the embodiment of the present application, after the common file system is constructed, each Profile can be used normally.

[0083] See also Figure 2 As shown, Figure 2 A profile management method applied to a smart card provided in an embodiment of the present application is shown, including:

[0084] S201: When an activation instruction is received, activate the Profile indicated by the activation instruction.

[0085] In the embodiment of the present application, the activation instruction may be an instruction issued by the user to switch to a certain Profile, or may be an instruction generated after the smart card is powered on to activate a default Profile, which is not limited in the embodiment of the present application.

[0086] S202: calling the shared file system corresponding to the Profile as the file system of the Profile.

[0087] In the embodiment of the present application, if it is set that there is only one shared file system, the file system in the public space can be directly obtained. If it is set that there can be multiple shared file systems, the first identification value of the activated Profile can be read, so as to find a shared file system with a second identification value matching the first identification value in the public space through the first identification value, and call the shared file system as the file system of the Profile.

[0088] It should be noted that if the personalized files of the Profile are saved in the Profile, then during the use of the Profile, the files in the Profile can be linked to the shared file system. When a certain file is needed during use, first search for the corresponding file in the Profile. If the file does not exist in the Profile, then search for the file in the shared file system. In addition, the personalized files in the Profile can be synchronized to the shared file system first, so that when a certain file is needed during use, the file can be directly searched in the shared file system. It should be noted that for the method of synchronizing the personalized files in the Profile to the shared file system first, when the Profile needs to be switched or the smart card is powered off, the personalized files in the shared file system can be removed first.

[0089] If the personalized files of the Profile are stored in a shared file system and are associated with each Profile, then in the process of using the Profile, you can first obtain the unique identifier of the Profile, and then, based on the unique identifier of the Profile, identify the personalized files of the Profile in the shared file system corresponding to the Profile. Therefore, when a certain file is needed during use, the corresponding file can be directly searched in the Profile, and the files to be searched are the shared files in the shared file system and the personalized files corresponding to the Profile.

[0090] It should be noted that in the embodiment of the present application, if the content of a shared file in a shared file system needs to be modified during the use of a Profile, the shared file can be saved to all Profiles other than the Profile that have the right to use the shared file system before modification, and the shared file can be saved to the Profile as a personalized file of the Profile after modification; or the shared file can be associated with all Profiles other than the Profile that have the right to use the shared file system as a personalized file before modification, and the shared file can be associated with the Profile as a personalized file of the Profile after modification. In this way, the association of personalized data caused during use is achieved, ensuring the reusability of the shared file system.

[0091] In addition, in actual application, there are often files that users hope can still be reused by various profiles even if the file content is modified, such as text message files and phone book files.

[0092] To this end, in a feasible implementation of the embodiment of the present application, these special shared files can be pre-defined, so that during the use of the Profile, if the content of the preset special shared file in the shared file system is modified, the preset special shared file will continue to be maintained as a file shared by all corresponding Profiles in the shared file system, instead of being adjusted to a personalized file in the aforementioned manner.

[0093] In the embodiment of the present application, special shared files can be set by engineers or users, for example, they can be set as text message files and phone book files.

[0094] The profile downloading method and profile management method provided in the embodiments of the present application construct a shared file system having other files in the profile except the personalized file, so that each time a profile is downloaded, only the personalized file of the profile needs to be saved. For files other than the personalized file, the shared file system is reused to obtain them, thereby reducing the consumption of smart card space resources by the file system corresponding to each profile, so that more space can be used to create files and content.

[0095] Embodiment 2:

[0096] This embodiment is based on the first embodiment and takes several specific examples as examples to further illustrate the present application.

[0097] Example 1:

[0098] First, based on the actual experience of engineers, you can pre-define the files in the Profile that can be used as personalized files: EF ICCID 2FE2 file under MF 3F00 file, EF IMSI 6F07 file under DF 7F20 file, EF ACC 6F78 file under DF 7F20 file, EF IMSI 6F07 file under ADF 7FF0 file, and EF ACC 6F78 file under ADF 7FF0 file.

[0099] Then, when downloading the content of Profile1, create a shared file system and save the files of Profile1 to the shared file system. According to the above-defined files, identify the personalized files of Profile1 and save the personalized files to Profile1. The saving method can be but not limited to the chain array method to save the remaining files except the personalized files. And make the first identification value A for Profile1, and the second identification value A for the shared file system.

[0100] When downloading Profile2, no new shared file system is created. According to the above-defined file, the personalized file of Profile2 is identified and saved in Profile2. The first identification value A is also set for Profile2, indicating that the shared file system A is used. Similarly, when downloading Profiles later, the processing method is the same as Profile2. At this time, the structure in the smart card is as follows: Figure 3 shown.

[0101] Example 2:

[0102] When downloading the content of Profile1, a shared file system is created, and the files of Profile1 are saved to the shared file system. The first identification value identifying Profile1 is A, and the second identification value identifying the shared file system is A.

[0103] When downloading the content of Profile2, a new file system is not created, and the first identification value of Profile2 is also marked as A; at the same time, the file contents of the same files are compared, and the files in Profile2 are identified as different from the files in the shared file system, and the files in Profile2 are saved in Profile2, and the files in the shared file system are saved in Profile1.

[0104] For example, compare the EF ICCID 2FE2 file under the MF 3F00 file, find the content of the EF ICCID2FE2 file in the shared file system, and then compare it with the content of the EF ICCID2FE2 file in the downloaded Profile2. If they are different, keep the EF ICCID 2FE2 file in Profile2, for example, use but not limited to linked arrays to save data, and save the EF ICCID 2FE2 file in the shared file system to Profile1. At this time, the files with the same file system but partially different file contents are identified and recorded in their respective Profiles.

[0105] Similarly, when downloading other Profile n, the mark is the first mark value A, and the first mark value is A, and the files different from those in the shared file system are identified again, and the files with different contents in the shared file system are saved and recorded in the first n-1 Profiles respectively. At this time, the structure in the smart card is as follows Figure 4 shown.

[0106] Example 3:

[0107] In the Profile format, a field "profileFileSystemIdentifier" can be added to the Profile header to identify the encoding of the file system in the Profile.

[0108] When downloading the content of Profile1, check whether the shared file system A has been created based on the "profileFileSystemIdentifier=A" in the Profile header part of Profile1. If not, create the shared file system A using the method of Example 2 above, and record the "profileFileSystemIdentifier=A" identifier of Profile1 as the first identifier value A, indicating the use of the shared file system A.

[0109] When downloading Profile2 content, the "profileFileSystemIdentifier" in the Profile header of Profile2 is also obtained. If "profileFileSystemIdentifier = A" and the shared file system A has been created, no new shared file system is created, and the first identification value A is also set for the Profile2 identifier, and the identifier also uses the shared file system A. At the same time, the method of Example 2 above is used to save the personalized file in Profile and Profile2.

[0110] When the profile is downloaded, the value of "profileFileSystemIdentifier" is used to determine whether a shared file system has been established. If it has been established, the method of Example 2 is used. If it has not been established, a new shared file system is established according to the value of profileFileSystemIdentifier, and then the operation is performed in the same way as in Example 2.

[0111] After downloading the Profile multiple times, the structure of the smart card is as follows Figure 5 shown.

[0112] In the above example, Profile1, Profile2, ... respectively represent the Profile downloaded for the first time, the Profile downloaded for the second time, ...

[0113] In the above example, when a certain Profile is activated, the corresponding shared file system can be determined by the first identifier of the Profile. Then, the personalized files in the activated Profile can be synchronized to the shared file system, which facilitates the use of the shared file system.

[0114] During the use of an activated Profile, if you need to change the content of a file in the shared file system corresponding to the Profile, then:

[0115] If the file to be modified is a personalized file of the Profile, the personalized file in the Profile is modified synchronously to ensure data consistency. If the file to be modified is not a personalized file of the Profile, the content of the file before modification is saved to other Profiles that can share the shared file system, and then the file in the shared file system is modified, and the modified file is saved as the personalized file of the Profile in the Profile.

[0116] In addition, in an embodiment of the present application, phone book files, text message files, etc. can be marked as special shared files, so that after the contents of these special shared files are modified, they are not synchronized to each Profile.

[0117] Through the above scheme, by creating a shared file system and saving the personalized files of each Profile, the space consumption of the file system is greatly saved, so that more space can be left on the smart card. For example, assuming that the creation of a file system for a Profile requires 10K of space, downloading two Profiles requires 20K of space. If the scheme of the embodiment of the present application is adopted, if a shared file system is used, it consumes 10K of space, plus the space consumption of recording and saving the values ​​of different file contents is about 1 to 2K, the two Profiles consume a total of about 11K to 12K, and as more Profiles are downloaded, more space will be saved.

[0118] Embodiment three:

[0119] Based on the same inventive concept, the present application also provides a Profile downloading device 100 and a Profile management device 200. Figure 6 and Figure 7 As shown, Figure 6 Shows the use of Figure 1 The method shown is for downloading a profile. Figure 7 Shows the use of Figure 2 The profile management device of the method shown. It should be understood that the specific functions of the device 100 and the device 200 can be referred to the description above. To avoid repetition, the detailed description is appropriately omitted here. The device 100 and the device 200 include at least one software function module that can be stored in the memory in the form of software or firmware or fixed in the operating system of the device 100 and the device 200. Specifically:

[0120] See also Figure 6 As shown, the device 100 is applied to a smart card, and includes: a download module 101 and a first processing module 102. Among them:

[0121] The download module 101 is used to download the Profile and identify the personalized files in the files in the Profile;

[0122] The first processing module 102 is configured to, when a shared file system corresponding to the Profile is created in the public space of the smart card, remove the remaining files except the personalized file in the Profile; or, when a shared file system corresponding to the Profile is created in the public space of the smart card, add the personalized file to the shared file system, associate the personalized file with the Profile, and delete all files in the Profile;

[0123] The shared file system can be used by multiple profiles including the profile, and the shared file system contains shared files that can be reused by the multiple profiles; the shared files are the remaining files in the profile except the personalized files.

[0124] In a feasible implementation of the embodiment of the present application, the download module 101 is specifically used to determine whether there is a file in the Profile whose file identifier is consistent with the preset file identifier; if so, determine that the file whose file identifier is consistent with the preset file identifier is the personalized file.

[0125] In the above feasible implementation manner, the first processing module 102 is further used to determine whether a shared file system corresponding to the Profile already exists in the public space after the download module 101 downloads the Profile; if not, create a shared file system corresponding to the Profile in the public space, and save the remaining files in the Profile except the personalized file in the shared file system.

[0126] In another feasible implementation of the embodiment of the present application, the download module 101 is specifically used to compare the files in the Profile with the files in the shared file system in turn, and determine the files in the Profile that are different from those in the shared file system; the files in the Profile that are different from those in the shared file system are personalized files of the Profile.

[0127] In the above feasible implementation manner, the first processing module 102 is also used to determine whether a shared file system corresponding to the Profile already exists in the public space before the download module 101 identifies the personalized files in the files in the Profile; if a shared file system corresponding to the Profile does not exist in the public space, a shared file system corresponding to the Profile is created in the public space, and all files in the Profile are saved in the shared file system.

[0128] In the above feasible implementation manner, the first processing module 102 is further used to, in the process of determining the files in the Profile that are different from those in the shared file system, save the files in the shared file system that are different from the profile's content into all Profiles other than the Profile that have the right to use the shared file system, and delete the files with different content from the shared file system; or, use the files in the shared file system that are different from the profile's content as personalized files and associate them with all Profiles other than the Profile that have the right to use the shared file system.

[0129] In the above two feasible implementation modes, the Profile contains a first identification value; the first processing module 102 is specifically used to determine whether there is a shared file system matching the first identification value in the public space of the smart card based on the first identification value in the Profile; if so, determine that the shared file system is the shared file system corresponding to the Profile.

[0130] In the embodiment of the present application, the first processing module 102 is further configured to, after creating a shared file system corresponding to the Profile in the public space, assign a second identification value matching the first identification value to the created shared file system.

[0131] See also Figure 7 As shown, the device 200 is applied to a smart card, and includes: an activation module 201 and a second processing module 202. Among them:

[0132] The activation module 201 is used to activate the Profile indicated by the activation instruction upon receiving the activation instruction;

[0133] The second processing module 202 is used to call the shared file system corresponding to the Profile as the file system of the Profile; the shared file system contains the remaining files in the Profile except the personalized file, and the shared file system can be used by multiple Profiles including the Profile.

[0134] In an embodiment of the present application, the second processing module 202 is further used to obtain a first identification value of the Profile; find a shared file system matching the first identification value in the public space of the smart card; and the found shared file system is the shared file system corresponding to the Profile.

[0135] In an embodiment of the present application, the second processing module 202 is also used for, during the use of the Profile, if it is necessary to modify the content of a shared file in the shared file system, then: before the modification, the shared file is saved in all Profiles other than the Profile that have the permission to use the shared file system, and after the modification, the shared file is saved in the Profile as a personalized file of the Profile; or, before the modification, the shared file is associated as a personalized file with all Profiles other than the Profile that have the permission to use the shared file system, and after the modification, the shared file is associated with the Profile as a personalized file of the Profile.

[0136] In an embodiment of the present application, the second processing module 202 is also used to keep the preset special shared file as a file shared by all corresponding Profiles in the shared file system if the content of the preset special shared file in the shared file system is modified during the use of the Profile.

[0137] In the embodiment of the present application, the preset special shared file is at least one of the following: a text message file, a phone book file.

[0138] It should be understood that, for the sake of brevity, some of the contents described in the first embodiment will not be repeated in this embodiment.

[0139] Embodiment 4:

[0140] This embodiment provides a smart card. Figure 8 As shown, it includes a processor 801, a memory 802 and a serial communication unit 803. Among them:

[0141] The serial communication unit 803 is used to realize the connection and communication between the processor 801 and the memory 802 .

[0142] The processor 801 is used to execute one or more programs stored in the memory 802 to implement the Profile downloading method or Profile management method in the above-mentioned embodiment 1 and / or embodiment 2.

[0143] Understandably, Figure 8 The structure shown is for illustration only. The smart card may also include Figure 8 More or fewer components as shown, or with Figure 8 As long as the smart card can support multiple Profile downloads, it can be, for example, an eSIM card.

[0144] This embodiment also provides a readable storage medium, such as a floppy disk, an optical disk, a hard disk, a flash memory, a U disk, an SD (Secure Digital Memory Card) card, an MMC (Multimedia Card) card, etc., in which one or more programs for implementing the above steps are stored, and the one or more programs can be executed by one or more processors to implement the steps of the Profile download method executed by the service distribution device in the above embodiment 1 and / or embodiment 2, or to implement the Profile download method or Profile management method in the above embodiment 1 and / or embodiment 2. No further details will be given here.

[0145] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0146] In addition, the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

[0148] In this document, relational terms such as first and second, etc. are used merely to distinguish one entity or operation from another entity or operation, but do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0149] As used herein, a plurality refers to two or more than two.

[0150] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A Profile downloading method, characterized in that: Applied to smart cards, including: Download the Profile and identify the personalized files in the files within the Profile; When a shared file system corresponding to the Profile is created in the public space of the smart card, other files except the personalized file are removed from the Profile; or, when a shared file system corresponding to the Profile is created in the public space of the smart card, the personalized file is added to the shared file system, the personalized file is associated with the Profile, and all files in the Profile are deleted; The shared file system can be used by multiple profiles including the profile, and the shared file system contains shared files that can be reused by the multiple profiles; the shared files are the remaining files in the profile except the personalized files; The identifying of the personalized files in the files in the Profile includes: Compare the files in the Profile with the files in the shared file system in sequence, and determine the files in the Profile that are different from those in the shared file system; the files in the Profile that are different from those in the shared file system are personalized files of the Profile; In the process of determining the files in the Profile that are different from the files in the shared file system, the method further includes: Save the files in the shared file system that are different from the profile in content to all profiles other than the profile that have permission to use the shared file system, and delete the files in the shared file system that are different in content; Or, a file in the shared file system that is different from the content of the profile is used as a personalized file and is associated with all profiles other than the profile that have the right to use the shared file system.

2. The Profile downloading method according to claim 1, characterized in that: The identifying of the personalized files in the files in the Profile includes: Determine whether the Profile contains a file whose file identifier is consistent with a preset file identifier; If so, it is determined that the file whose file identifier is consistent with the preset file identifier is the personalized file.

3. The Profile downloading method according to claim 2, characterized in that: After downloading the Profile, the method further includes: Determine whether a shared file system corresponding to the Profile already exists in the public space; If it does not exist, a shared file system corresponding to the Profile is created in the public space, and other files in the Profile except the personalized file are saved in the shared file system.

4. The Profile downloading method according to claim 1, characterized in that: Before identifying the personalized file in the file in the Profile, the method further includes: Determine whether a shared file system corresponding to the Profile already exists in the public space; If the shared file system corresponding to the Profile does not exist in the public space, a shared file system corresponding to the Profile is created in the public space, and all files in the Profile are stored in the shared file system.

5. The Profile downloading method according to claim 1 or 3, characterized in that: The Profile has a first identification value; Determining whether a shared file system corresponding to the Profile already exists in the public space includes: According to the first identification value in the Profile, determining whether there is a shared file system matching the first identification value in the public space of the smart card; If it exists, determine that the shared file system is the shared file system corresponding to the Profile.

6. The Profile downloading method according to claim 5, characterized in that: After creating a shared file system corresponding to the Profile in the public space, the method further includes: A second identification value matching the first identification value is allocated to the created shared file system.

7. A Profile downloading device, characterized in that: Applied to a smart card, comprising: a download module and a first processing module; The download module is used to download the Profile and identify the personalized files in the files in the Profile; The first processing module is configured to, when a shared file system corresponding to the Profile is created in the public space of the smart card, remove the remaining files except the personalized file in the Profile; or, when a shared file system corresponding to the Profile is created in the public space of the smart card, add the personalized file to the shared file system, associate the personalized file with the Profile, and delete all files in the Profile; The shared file system can be used by multiple profiles including the profile, and the shared file system contains shared files that can be reused by the multiple profiles; the shared files are the remaining files in the profile except the personalized files; The download module is specifically used to compare the files in the Profile with the files in the shared file system in sequence, and determine the files in the Profile that are different from those in the shared file system; the files in the Profile that are different from those in the shared file system are personalized files of the Profile; The first processing module is further configured to, in the process of determining the files in the profile that are different from those in the shared file system, save the files in the shared file system that are different from those in the profile into all profiles other than the profile that have the right to use the shared file system, and delete the files with different contents from the shared file system; or, use the files in the shared file system that are different from those in the profile as personalized files and associate them with all profiles other than the profile that have the right to use the shared file system.

8. The Profile downloading device according to claim 7, characterized in that: The download module is specifically used to determine whether there is a file in the Profile with a file identifier consistent with a preset file identifier; if so, determine that the file with the file identifier consistent with the preset file identifier is the personalized file.

9. The Profile downloading device according to claim 8, characterized in that: The first processing module is also used to determine whether a shared file system corresponding to the Profile already exists in the public space after the download module downloads the Profile; if not, create a shared file system corresponding to the Profile in the public space, and save the remaining files in the Profile except the personalized file in the shared file system.

10. The Profile downloading device according to claim 7, characterized in that: The first processing module is also used to determine whether a shared file system corresponding to the Profile already exists in the public space before the download module identifies the personalized files in the files in the Profile; if the shared file system corresponding to the Profile does not exist in the public space, create a shared file system corresponding to the Profile in the public space, and save all files in the Profile in the shared file system.

11. The Profile downloading device according to claim 7 or 9, characterized in that: The Profile has a first identification value; The first processing module is specifically used to determine whether there is a shared file system matching the first identification value in the public space of the smart card according to the first identification value in the Profile; if so, determine that the shared file system is the shared file system corresponding to the Profile.

12. The Profile downloading device according to claim 11, characterized in that: The first processing module is further configured to, after creating a shared file system corresponding to the Profile in the public space, assign a second identification value matching the first identification value to the created shared file system.

13. A smart card, characterized in that: include: Processor, memory and serial communication unit; The communication bus is used to realize the connection and communication between the processor and the memory; The processor is used to execute one or more programs stored in the memory to implement the Profile download method according to any one of claims 1 to 6.

14. A readable storage medium, characterized in that: The readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the Profile downloading method according to any one of claims 1 to 6.

Images