Embedded SIM (Subscriber Identity Module) management method, system and equipment and computer medium
The eSIM management method addresses the challenge of flexible application by enabling secure and efficient rebinding of configuration files through verification and prompt messages, enhancing usability and reducing file loss risks.
Patent Information
- Application Number
- CN202510573150.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-30
- Publication Date
- 2025-07-15
AI Technical Summary
In the prior art, the configuration file of the embedded SIM cannot be unbound when the device and the server communicate fluctuates, resulting in poor application flexibility and cannot be re-downloaded and used on other devices.
The server checks the binding device of the configuration file. If the target device is not bound, a forced migration prompt message will be sent. The target device generates security verification information and rebinates the configuration file after verification to realize the forced migration of the configuration file.
Improves the application flexibility of embedded SIM, reduces operator maintenance costs due to loss of configuration files or illegal abuse, and enhances security and convenience.
Smart Images
Figure CN120321657A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and more specifically, to an embedded SIM card management method, system, device and computer medium. Background Art
[0002] eSIM (embedded SIM) is a new type of SIM card technology that digitally replaces the traditional physical SIM card. eSIM allows users to activate the operator's network services on the device by downloading a profile, instead of relying on the plug-in and pull-out operation of the physical card. In this process, in order to prevent the configuration file from being copied to multiple devices and to ensure the security of network services, after the device downloads the configuration file, the server will bind the configuration file to the device one by one to ensure that a configuration file can only be used by a single device.
[0003] However, when deleting the configuration file of the embedded SIM, the device needs to send a deletion request to the server to unbind the configuration file and the device. If the communication between the device and the server fluctuates and the server fails to process the deletion request, the server cannot unbind the configuration file, resulting in the loss of the configuration file and the inability to re-download and use it on other devices, resulting in poor application flexibility of the embedded SIM.
[0004] In summary, how to improve the application flexibility of embedded SIM is an urgent problem to be solved by those skilled in the art. Summary of the invention
[0005] The purpose of this application is to provide an embedded SIM management method, which can solve the technical problem of how to improve the application flexibility of embedded SIM to a certain extent. This application also provides an embedded SIM management system, a computer device and a computer readable storage medium.
[0006] In order to achieve the above objectives, this application provides the following technical solutions:
[0007] An embedded SIM management method, applied to a server, comprising:
[0008] Receiving an application request from a target device for a configuration file, wherein the configuration file is used to configure an embedded SIM;
[0009] Checking the device bound to the configuration file;
[0010] In response to the configuration file being bound to a device but not bound to the target device, sending a prompt message indicating forced migration to the target device;
[0011] Receiving security verification information sent by the target device in response to the prompt information;
[0012] Verify the security verification information. If the verification is successful, rebind the configuration file to the target device so that the target device can apply the configuration file.
[0013] In an exemplary embodiment, after checking the binding device of the configuration file, it further includes:
[0014] In response to the configuration file not being bound to a device, check whether there is security verification data corresponding to the configuration file stored;
[0015] In response to the security verification data not being stored, send setting information indicating setting the security verification data to the target device;
[0016] Receive the security verification data sent by the target device in response to the setting information and store it to verify the security verification information based on the security verification data.
[0017] In an exemplary embodiment, after checking the binding device of the configuration file, it further includes:
[0018] In response to the configuration file being bound to the target device, detect whether the target device has the authentication function enabled;
[0019] In response to the target device having the authentication function enabled, send verification information indicating performing authentication to the target device;
[0020] Receive the authentication data sent by the target device in response to the verification information;
[0021] Verify the authentication data. If the verification passes, transmit the configuration file to the target device.
[0022] In an exemplary embodiment, after checking the binding device of the configuration file, it further includes:
[0023] In response to the configuration file being bound to the target device, send update information indicating performing security update to the target device;
[0024] If security update data sent by the target device in response to the update information is received, update the stored security verification data with the security update data, where the security verification data is used to verify the security verification information;
[0025] If a direct download request sent by the target device in response to the update information is received, transmit the configuration file to the target device.
[0026] In an exemplary embodiment, after verifying the security verification information, the method further includes:
[0027] If the verification is successful, determine the historical device last bound to the configuration file;
[0028] Mark the historical device as an incorrectly bound device of the configuration file;
[0029] Send an unbinding instruction to the historical device to delete the configuration file stored in the historical device.
[0030] In an exemplary embodiment, after verifying the security verification information, the method further includes:
[0031] If the verification fails, accumulate the real-time number of verification failures;
[0032] Detect whether the real-time number is greater than a set number;
[0033] In response to the real-time number being less than or equal to the set number, send an alarm message indicating security verification failure to the target device;
[0034] Receive the security verification information sent by the target device after responding to the alarm message, and return to execute the step of verifying the security verification information;
[0035] In response to the real-time number being greater than the set number, end the application of the configuration file by the target device.
[0036] An embedded SIM management method applied to a target device includes:
[0037] Send an application request for a configuration file to a server, where the configuration file is used to configure an embedded SIM;
[0038] In response to receiving a prompt message indicating forced migration sent by the server, respond to the prompt message to generate security verification information;
[0039] Transmit the security verification information to the server so that after the server verifies the security verification information successfully, bind the configuration file to the target device;
[0040] Download the configuration file from the server for application;
[0041] Wherein, the prompt message includes information generated by the server after detecting that the configuration file has been bound to a device and not bound to the target device.
[0042] An embedded SIM management system applied to a server includes:
[0043] A request receiving module, configured to receive an application request of a configuration file from a target device, where the configuration file is used to configure the embedded SIM;
[0044] A binding checking module, configured to check the binding device of the configuration file;
[0045] A prompt sending module, configured to send a prompt message indicating forced migration to the target device in response to that the configuration file has been bound to a device and is not bound to the target device;
[0046] A verification receiving module, configured to receive security verification information sent by the target device after responding to the prompt message;
[0047] A security verification module, configured to verify the security verification information. If the verification is successful, rebind the configuration file to the target device so that the target device can apply the configuration file.
[0048] A computer device, comprising:
[0049] A memory, configured to store a computer program;
[0050] A processor, configured to implement the steps of the embedded SIM management method as described in any one of the above when executing the computer program.
[0051] A computer storage medium, in which a computer program is stored, and the computer program implements the steps of the embedded SIM management method as described in any one of the above when executed by a processor.
[0052] An embedded SIM management method provided by this application is applied to a server. It receives an application request for a configuration file from a target device, where the configuration file is used to configure the embedded SIM; checks the bound device of the configuration file; in response to the configuration file being bound to a device and not bound to the target device, sends a prompt message indicating forced migration to the target device; receives the security verification information sent by the target device after it responds to the prompt message; verifies the security verification information, and if the verification is successful, rebinds the configuration file to the target device so that the target device can apply the configuration file. In this application, when the target device applies the configuration file, the server can check the bound device of the configuration file. If the device bound to the configuration file is not the target device, a prompt message can be sent to cause the target device to send security verification information. In this way, after the server verifies the security verification information, it can enable the target device to apply the configuration file for embedded SIM configuration, without waiting for other devices to release the configuration file, achieving forced and secure migration of the configuration file, improving the flexible migration of the configuration file, and further improving the application flexibility of the embedded SIM. An embedded SIM card management system, a computer device, and a computer-readable storage medium provided by this application also solve the corresponding technical problems. BRIEF DESCRIPTION OF THE DRAWINGS
[0053] In order to more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of this application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on the provided drawings.
[0054] Figure 1 It is a flowchart of an embedded SIM management method provided by an embodiment of this application;
[0055] Figure 2 It is a flowchart of a smartphone applying a configuration file;
[0056] Figure 3 It is another flowchart of an embedded SIM management method provided by an embodiment of this application;
[0057] Figure 4 It is a schematic structural diagram of an embedded SIM management system provided by an embodiment of this application;
[0058] Figure 5 It is a structural diagram of a computer device 20 shown according to an exemplary embodiment. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0059] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the protection scope of the present application.
[0060] Please refer to Figure 1 , Figure 1 , which is a flowchart of an embedded SIM management method provided by an embodiment of the present application.
[0061] An embedded SIM management method provided by an embodiment of the present application, which is applied to a server, may include the following steps:
[0062] Step S101: Receive an application request for a configuration file from a target device, where the configuration file is used to configure the embedded SIM.
[0063] In practical applications, the server is used to manage the configuration file (profile) of the embedded SIM. When the target device applies the embedded SIM, it needs to apply to the server to download the configuration file, that is, the target device needs to generate an application request for the configuration file and send the application request to the server so that the server can process the operation of providing the configuration file to the target device.
[0064] It should be noted that the target device refers to a mobile terminal supporting eSIM, and its type can be flexibly determined according to the application scenario. For example, the target device can be a smart phone, a tablet computer, a smart watch, a laptop computer, etc.; the application request can be a request to download the configuration file or other requests representing the application of the configuration file. In addition, considering that the target device needs to interact with the server, there can be communication modules such as WWAN (Wireless Wide Area Network) modules in the target device, and it can be connected to WIFI (wireless network communication technology) for data transmission.
[0065] Step S102: Check the device bound to the configuration file.
[0066] In practical applications, the configuration file is only used by a single device. To ensure that the configuration file can only be used by one device at a time, the server binds the configuration file to the device. If the target device is not currently bound to the configuration file, the target device cannot apply the configuration file. In other words, the device binding result of the configuration file affects the use of the configuration file by the target device. Therefore, the server needs to check the bound device of the configuration file so as to decide later whether the target device can apply the configuration file according to the check result. This bound device refers to the device that normally applies the configuration file for eSIM configuration. For example, the device currently applying the configuration file is the bound device.
[0067] Step S103: In response to the configuration file being bound to a device and not being bound to the target device, send a prompt message indicating forced migration to the target device.
[0068] Step S104: Receive the security verification information sent by the target device after the target device responds to the prompt message.
[0069] Step S105: Verify the security verification information. If the verification is successful, rebind the configuration file to the target device so that the target device can apply the configuration file.
[0070] In practical applications, if the check result shows that the configuration file is bound to a device but the bound device is not the target device, the target device cannot use the configuration file. The server needs to wait until the configuration file is unbound by the bound historical device before it can provide the configuration file for the target device to apply. However, this process is cumbersome and cannot guarantee that the historical device successfully unbinds the configuration file. To avoid this situation, the server can generate a prompt message indicating forced migration of the configuration file and send it to the target device to inform the target device that forced migration of the configuration file can be performed through the prompt message. Correspondingly, if the target device decides to forcibly migrate the configuration file, it can respond to this prompt message and send security verification information to the server. The server then verifies the received security verification information. If the verification passes, it indicates that the forced migration process of the configuration file is secure, and the server can rebind the configuration file to the target device so that the target device can apply the configuration file for eSIM configuration.
[0071] In an exemplary embodiment, after checking the binding device of the configuration file, if the configuration file is not bound to a device, the target device can directly apply the configuration file. However, considering that forced migration of the configuration file may be required later, to meet this requirement, the security verification data for forced migration of the configuration file can be agreed upon with the target device first, so that the security verification information can be verified through the security verification data later. That is, when the server responds to the configuration file not being bound to a device, it checks whether there is security verification data corresponding to the configuration file; in response to there being no stored security verification data, it sends setting information indicating the setting of security verification data to the target device, receives the security verification data sent by the target device in response to the setting information, and stores it to verify the security verification information based on the security verification data. Correspondingly, in response to there being stored security verification data, the configuration file can be directly provided for the target device to download and use.
[0072] It should be noted that the type of security verification information can be flexibly determined according to the application scenario. For example, the security verification information can include one or more of a string password, a SMS verification code, biometric data, etc. In this way, users can select the most suitable verification method according to their needs, enhancing convenience and security; among them, the string password can be a custom string password entered by the user, such as a combination of letters, numbers or symbols; the SMS verification code can be a one-time verification code sent by the server to the user's communication device for verifying the user's identity; the biometric data can be verification data collected using the built-in biometric technology of the target device, such as fingerprint recognition, face recognition, etc. It should also be noted that the security verification data for verifying the security verification information and the verification method of the security verification information can be determined according to the type of security verification information. For example, when the security verification information is a string password, the security verification data can be a pre-stored string password, and the verification method can be to verify whether the string password transmitted by the target device is consistent with the pre-stored string password. If they are consistent, the verification passes; if not, the verification fails, etc.
[0073] In an exemplary embodiment, after checking the binding device of the configuration file, if the configuration file has been bound to the target device, the server can directly provide the configuration file for the target device to use. However, considering that the target device may be used by other users other than the target device holder, in order to prevent other users from misusing the embedded SIM, the server can also authenticate the applicant of the target device and decide whether to provide the configuration file for the target device to use according to the authentication result. That is, after the server responds to the fact that the configuration file has been bound to the target device, it can also detect whether the target device has enabled the authentication function; in response to the target device having enabled the authentication function, it sends verification information indicating authentication to the target device; receives the authentication data sent by the target device after responding to the verification information; verifies the authentication data, and if the verification passes, transmits the configuration file to the target device; if the verification fails, it can end the application of the configuration file by the target device. In this way, even when the configuration file has been bound to the target device, the target device can ensure that only itself can apply the embedded SIM by enabling the authentication function, further improving the application security of the embedded SIM.
[0074] It should be noted that the authentication data can be flexibly determined according to the application scenario. For example, in the scenario of simplifying user operations, the authentication data can be a certain character or simple pattern set by the user. Of course, the authentication data can also be a human face, etc., and the present application does not make specific limitations here.
[0075] In an exemplary embodiment, after checking the binding device of the configuration file, if the configuration file is exactly bound to the target device, the target device can also be used to update the security verification data to update the verification method of the security verification information, avoiding the security risks brought by the cracking or leakage of the security verification data of the target device. That is, after the server responds to the fact that the configuration file has been bound to the target device, it can also send update information indicating security update to the target device; if it receives the security update data sent by the target device after responding to the update information, it updates the stored security verification data according to the security update data, and the security verification data is used to verify the security verification information; if it receives a direct download request sent by the target device after responding to the update information, it skips the update of the security verification data and transmits the configuration file to the target device.
[0076] In an exemplary embodiment, after verifying the security verification information, in order to avoid the problem of configuration file application conflicts caused by the historical devices bound to the configuration file applying the configuration file again, after the server successfully verifies the security verification information, it can also determine the historical devices last bound to the configuration file; mark the historical devices as incorrectly bound devices of the configuration file; and send an unbinding instruction to the historical devices to delete the configuration files stored in the historical devices. In this process, the server can also send an unbinding instruction to the historical devices when the historical devices are online to delete the configuration files stored in the historical devices, so as to avoid the historical devices applying the configuration file again for the application of the embedded SIM.
[0077] In an exemplary embodiment, in order to avoid the target device maliciously downloading the configuration file, the number of times the target device applies the security verification information can also be limited. That is, after the server verifies the security verification information, if the verification fails, it can also accumulate the real-time number of verification failures; detect whether the real-time number is greater than the set number; in response to the real-time number being less than or equal to the set number, send an alarm message indicating security verification failure to the target device; receive the security verification information sent by the target device after responding to the alarm message, and return to execute the step of verifying the security verification information; in response to the real-time number being greater than the set number, end the application of the configuration file by the target device and clear the real-time number to zero for the next time to start counting from zero.
[0078] An embedded SIM management method provided in this application is applied to a server, which receives an application request for a configuration file from a target device, where the configuration file is used to configure the embedded SIM; checks the binding device of the configuration file; in response to the configuration file having a bound device and not being bound to the target device, sends a prompt message indicating forced migration to the target device; receives the security verification information sent by the target device after responding to the prompt message; verifies the security verification information, and if the verification is successful, rebinds the configuration file to the target device so that the target device can apply the configuration file. In this application, when the target device applies the configuration file, the server can check the binding device of the configuration file. If the configuration file is not bound to the target device, a prompt message can be sent to cause the target device to send the security verification information. In this way, after the server passes the verification of the security verification information, the target device can apply the configuration file to configure the embedded SIM, without waiting for other devices to unbind the configuration file, realizing the forced and secure migration of the configuration file, improving the flexible migration of the configuration file, and further improving the application flexibility of the embedded SIM. In addition, it reduces the customer service support required by the operator due to the loss or illegal abuse of the configuration file and reduces the maintenance cost.
[0079] To facilitate the understanding of the embedded SIM management solution provided by this application, it is now assumed that the historical device is a smartwatch, the target device is a smartphone, the configuration file is bound to the EID (embedded identity) of the device, and the security verification information is a password. Then the process of the mobile phone configuring the embedded SIM can be as follows Figure 2 as shown, including the following steps:
[0080] The user attempts to download the bound profile in the eSIM settings interface of the smartphone;
[0081] The server checks the EID currently bound to the profile:
[0082] If the profile is not bound to any EID, the user is prompted through the smartphone to set a download password; the user sets the password through the smartphone and clicks download; the server binds the profile to the smartphone EID, updates the password, and then sends the profile to the smartphone;
[0083] If the EID bound to the profile is inconsistent with the smartphone, it is prompted that a download password needs to be entered for forced migration; the user transmits the password through the smartphone to the server for verification; if the verification passes, the server unbinds the smartwatch EID, rebinds the smartphone EID, the server records the smartwatch EID in the "error EID list", sends a deletion instruction to the smartwatch, and sends the profile to the smartphone; if the password verification fails, it is prompted that the password is incorrect and needs to be re-entered. If the password is entered correctly within 3 times, the smartwatch EID is unbound and subsequent steps are executed. If the password is entered incorrectly within 3 times, the process ends;
[0084] If the EID bound to the profile is consistent with the smartwatch, it is prompted to directly download or download after modifying the password; if the user directly downloads through the smartphone, the server sends the profile to the smartphone; if the user modifies the password and downloads through the smartphone, the server updates the profile download password and then sends the profile to the smartphone.
[0085] Please refer to Figure 3 , Figure 3 which is another flowchart of an embedded SIM management method provided by an embodiment of this application.
[0086] An embedded SIM management method provided by an embodiment of this application, which is applied to a target device, may include the following steps:
[0087] Step S201: Send an application request for a configuration file to the server, where the configuration file is used to configure the embedded SIM.
[0088] Step S202: In response to receiving the prompt information indicating forced migration sent by the server, respond to the prompt information to generate security verification information.
[0089] Step S203: Transmit the security verification information to the server so that after the server successfully verifies the security verification information, it binds the configuration file to the target device.
[0090] Step S204: Download the configuration file from the server for application; wherein, the prompt information includes the information generated after the server checks that the configuration file has been bound to a device and is not bound to the target device.
[0091] For the corresponding description of an embedded SIM management method applied to a target device provided in the embodiments of the present application, reference may be made to the above embodiments, and details are not described herein again.
[0092] Please refer to Figure 4 , Figure 4 which is a schematic structural diagram of an embedded SIM management system provided in the embodiments of the present application.
[0093] An embedded SIM management system provided in the embodiments of the present application, which is applied to a server, may include:
[0094] A request receiving module 101, configured to receive an application request for a configuration file from a target device, where the configuration file is used to configure an embedded SIM;
[0095] A binding check module 102, configured to check the binding device of the configuration file;
[0096] A prompt sending module 103, configured to send a prompt information indicating forced migration to the target device in response to the configuration file being bound to a device and not bound to the target device;
[0097] A verification receiving module 104, configured to receive the security verification information sent by the target device after responding to the prompt information;
[0098] A security verification module 105, configured to verify the security verification information. If the verification is successful, rebind the configuration file to the target device so that the target device can apply the configuration file.
[0099] An embedded SIM management system provided in the embodiments of the present application, which is applied to a server, may further include:
[0100] A setting module, after the binding check module checks the binding device of the configuration file, in response to the configuration file not being bound to a device, checks whether there is security verification data corresponding to the configuration file; in response to there being no stored security verification data, sends setting information indicating setting security verification data to the target device; receives and stores the security verification data sent by the target device in response to the setting information, so as to verify the security verification information based on the security verification data.
[0101] An embedded SIM management system provided by an embodiment of the present application, applied to a server, may further include:
[0102] An authentication module, after the binding check module checks the binding device of the configuration file, in response to the configuration file being bound to the target device, detects whether the target device has the authentication function enabled; in response to the target device having the authentication function enabled, sends verification information indicating performing authentication to the target device; receives the authentication data sent by the target device in response to the verification information; verifies the authentication data, and if the verification passes, transmits the configuration file to the target device.
[0103] An embedded SIM management system provided by an embodiment of the present application, applied to a server, may further include:
[0104] A security update module, after the binding check module checks the binding device of the configuration file, in response to the configuration file being bound to the target device, sends update information indicating performing security update to the target device; if receiving the security update data sent by the target device in response to the update information, updates the stored security verification data according to the security update data, and the security verification data is used to verify the security verification information; if receiving a direct download request sent by the target device in response to the update information, transmits the configuration file to the target device.
[0105] An embedded SIM management system provided by an embodiment of the present application, applied to a server, may further include:
[0106] A binding release module, after the security verification module verifies the security verification information, if the verification is successful, determines the historical device to which the configuration file was last bound; marks the historical device as the incorrectly bound device of the configuration file; sends an unbinding instruction to the historical device to delete the configuration file stored in the historical device.
[0107] An embedded SIM management system provided by an embodiment of the present application, applied to a server, may further include:
[0108] The number detection module is used to, after the security verification module verifies the security verification information, if the verification fails, accumulate the real-time number of failed verifications; detect whether the real-time number is greater than the set number; in response to the real-time number being less than or equal to the set number, send an alarm message indicating security verification failure to the target device; receive the security verification information sent by the target device after responding to the alarm message, and return to execute the step of verifying the security verification information; in response to the real-time number being greater than the set number, end the application of the configuration file by the target device.
[0109] An embedded SIM management system provided by an embodiment of the present application is applied to a target device and may include:
[0110] The request sending module is used to send an application request for the configuration file to the server, and the configuration file is used to configure the embedded SIM.
[0111] The verification generation module is used to, in response to receiving a prompt message indicating forced migration sent by the server, respond to the prompt message and generate security verification information.
[0112] The verification sending module is used to transmit the security verification information to the server, so that after the server verifies the security verification information successfully, the configuration file is bound to the target device.
[0113] The download module is used to download the configuration file from the server for application.
[0114] Among them, the prompt message includes the information generated after the server checks that the configuration file has been bound to a device and is not bound to the target device.
[0115] Furthermore, an embodiment of the present application also provides a computer device. Figure 5 It is a structural diagram of a computer device 20 shown according to an exemplary embodiment, and the content in the figure cannot be considered as any limitation on the scope of use of the present application.
[0116] Figure 5 It is a structural schematic diagram of a computer device 20 provided by an embodiment of the present application. The computer device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. Among them, the memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21 to implement the relevant steps in the embedded SIM management method disclosed in any of the foregoing embodiments. In addition, the computer device 20 in this embodiment may specifically be a server.
[0117] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the computer device 20; the communication interface 24 can create a data transmission channel between the computer device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and no specific limitation is imposed on it here; the input / output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and no specific limitation is imposed here.
[0118] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, a random access memory, a magnetic disk, an optical disc, etc. The resources stored thereon can include an operating system 221, a computer program 222, video data 223, etc., and the storage method can be temporary storage or permanent storage.
[0119] Among them, the operating system 221 is used to manage and control each hardware device and the computer program 222 on the computer device 20 to enable the processor 21 to perform operations and processing on the data 223 in the memory 22, and it can be Windows Server, Netware, Unix, Linux, etc. In addition to the computer program that can be used to complete the embedded SIM management method executed by the computer device 20 disclosed in any of the foregoing embodiments, the computer program 222 can further include computer programs that can be used to complete other specific tasks. The data 223 can include various data collected by the computer device 20.
[0120] It should be noted that the computer device can specifically be a module capable of implementing positioning and communication functions or a terminal device including the module, etc. The terminal device can specifically be a mobile terminal and / or an intelligent device, etc. The mobile terminal can specifically be at least one of a mobile phone, a tablet computer, a laptop computer, etc. The intelligent device can specifically be at least one of a smart watch, a smart refrigerator, a smart speaker, a smart washing machine, a smart TV, etc. The module can specifically be any one of a 2G communication module, a 3G communication module, a 4G communication module, a 5G communication module, an NB-IOT communication module, etc.
[0121] Furthermore, the embodiment of this application also discloses a computer storage medium in which a computer program is stored. When the computer program is loaded and executed by a processor, the steps of the embedded SIM management method disclosed in any of the foregoing embodiments are implemented.
[0122] For the description of the relevant parts in an embedded SIM management system, a computer device, and a computer-readable storage medium provided in the embodiments of the present application, please refer to the detailed description of the corresponding parts in an embedded SIM management method provided in the embodiments of the present application, which will not be elaborated herein. In addition, the parts of the above technical solutions provided in the embodiments of the present application that are consistent with the implementation principles of the corresponding technical solutions in the prior art are not described in detail to avoid excessive elaboration.
[0123] It should also be noted that in this document, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "comprising a..." does not exclude the existence of additional identical elements in the process, method, article or device comprising the element.
[0124] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. An embedded SIM management method, characterized in that, Applied to a server, including: Receiving an application request from a target device for a configuration file, where the configuration file is used to configure an embedded SIM; Checking the binding device of the configuration file; In response to the configuration file being bound to a device and not bound to the target device, sending a prompt message indicating forced migration to the target device; Receiving security verification information sent by the target device after responding to the prompt message; Verifying the security verification information. If the verification is successful, rebinding the configuration file to the target device so that the target device can apply the configuration file.
2. The method according to claim 1, wherein After checking the binding device of the configuration file, it further includes: In response to the configuration file not being bound to a device, checking whether there is stored security verification data corresponding to the configuration file; In response to there being no stored security verification data, sending setting information indicating setting the security verification data to the target device; Receiving and storing the security verification data sent by the target device after responding to the setting information, and verifying the security verification information based on the security verification data.
3. The method according to claim 1, characterized in that After checking the binding device of the configuration file, it further includes: In response to the configuration file being bound to the target device, detecting whether the target device has the authentication function enabled; In response to the target device having the authentication function enabled, sending verification information indicating authentication to the target device; Receiving authentication data sent by the target device after responding to the verification information; Verifying the authentication data. If the verification passes, transmitting the configuration file to the target device.
4. The method according to claim 1, wherein After checking the binding device of the configuration file, it further includes: In response to the configuration file being bound to the target device, sending update information indicating security update to the target device; If receiving security update data sent by the target device after responding to the update information, updating the stored security verification data according to the security update data, where the security verification data is used to verify the security verification information; If receiving a direct download request sent by the target device after responding to the update information, transmitting the configuration file to the target device.
5. The method according to claim 1, wherein After verifying the security verification information, it further includes: If the verification is successful, determining the historical device to which the configuration file was last bound; Marking the historical device as the incorrectly bound device of the configuration file; Sending an unbinding instruction to the historical device to delete the configuration file stored by the historical device.
6. The method according to claim 1, wherein After verifying the security verification information, it further includes: If the verification fails, accumulating the real-time number of verification failures; Detecting whether the real-time number is greater than a set number; In response to the real-time number being less than or equal to the set number, sending an alarm message indicating security verification failure to the target device; Receiving the security verification information sent by the target device after responding to the alarm message, and returning to execute the step of verifying the security verification information; In response to the fact that the real - time count is greater than the set count, end the application of the configuration file to the target device.
7. An embedded SIM management method, characterized in that The application to the target device includes: Send an application request for the configuration file to the server, where the configuration file is used to configure the embedded SIM; In response to receiving the prompt message indicating forced migration sent by the server, respond to the prompt message to generate security verification information; Transmit the security verification information to the server so that after the server successfully verifies the security verification information, bind the configuration file to the target device; Download the configuration file from the server for application; Wherein, the prompt message includes the information generated after the server checks that the configuration file has been bound to a device and is not bound to the target device.
8. An embedded SIM management system, characterized in that, The application to the server includes: A request receiving module, configured to receive an application request for a configuration file from a target device, where the configuration file is used to configure the embedded SIM; A binding check module, configured to check the bound device of the configuration file; A prompt sending module, configured to send a prompt message indicating forced migration to the target device in response to the fact that the configuration file has been bound to a device and is not bound to the target device; A verification receiving module, configured to receive the security verification information sent by the target device after responding to the prompt message; A security verification module, configured to verify the security verification information. If the verification is successful, rebind the configuration file to the target device so that the target device can apply the configuration file.
9. A computer device, characterized in that, It includes: A memory, configured to store a computer program; A processor, configured to implement the steps of the embedded SIM management method according to any one of claims 1 to 7 when executing the computer program.
10. A computer storage medium, characterized in that, A computer program is stored in the computer storage medium, and when the computer program is executed by a processor, it implements the steps of the embedded SIM management method according to any one of claims 1 to 7.