Profile file download management method, electronic device and computer storage medium

Abstract

The embodiments of the present application relate to a profile file download management method, electronic device and computer storage medium. The method obtains the address and password of the SM‑DP+ server; performs two-way authentication with the SM‑DP+ server, and establishes a communication connection after the two-way authentication; receives the target profile file metadata sent by the SM‑DP+ server, wherein the target profile file metadata includes the target profile file size; determines the remaining memory of the eSIM chip; if the remaining memory of the eSIM chip is less than the target profile file size, initiates a download process cancellation instruction to the eSIM chip; issues a prompt message to remind the user to clean up the memory of the eSIM chip; receives the user's deletion operation on the selected profile file, and deletes the selected profile file. The embodiments of the present application can solve the problem that when the profile file cannot be downloaded due to insufficient memory of the eSIM chip, the SM‑DP+ server sets the status of the profile file to an error, which affects the efficiency of the user downloading the profile file again.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a profile file download management method, an electronic device, and a computer storage medium. Background Art

[0002] When the embedded subscriber identity module (eSIM) card memory is insufficient, if the terminal downloads the profile file, an error will be reported due to insufficient memory. The Subscription Manager Data Preparation+ (SM-DP+) server will set the status of the profile file that failed to download to error. Since the profile file that failed to download is set to error, even if the storage space of the eSIM card is cleared later, the profile file cannot be downloaded directly again, which causes inconvenience to users in downloading profile files. Summary of the invention

[0003] In view of the above, it is necessary to provide a profile file download management method, electronic device and computer storage medium to solve the problem of inconvenience in user profile file download operation.

[0004] In the first aspect, an embodiment of the present application provides a profile file download management method, which is applied to a terminal device, wherein the terminal device includes an eSIM chip, and the method includes: obtaining the address and password of the SM-DP+ server, wherein the password includes an activation code (AC) and a confirmation code (CC) required to be verified in the process of downloading the target profile file; performing two-way authentication with the SM-DP+ server, and establishing a communication connection after the two-way authentication passes; receiving the target profile file metadata sent by the SM-DP+ server, wherein the target profile file metadata includes the size of the target profile file; determining the remaining memory of the eSIM chip; if the remaining memory of the eSIM chip is less than the size of the target profile file, canceling the download process of the target profile file; outputting a prompt message to remind the user to clean up the memory of the eSIM chip; after deleting the selected profile file, initiating the download process of the target profile file again. In the above scheme, when the terminal device determines that the remaining memory of the eSIM chip is less than the size of the target profile file, it initiates a download process cancellation instruction to the eSIM chip to prevent the SM-DP+ server from setting the status of the profile to an error. In addition, the terminal device also receives the user's deletion operation on the selected profile file and deletes the selected profile file. This avoids the problem that due to insufficient memory of the eSIM chip, the SM-DP+ server sets the status of the profile file to an error and the user needs to contact the operator again to reset the status of the profile file before continuing to download the profile file.

[0005] In one embodiment of the present application, the receiving the target profile file metadata sent by the SM-DP+ server includes: calling the ES8+.StoreMetadata instruction through the first interface (ES8+) to obtain the target profile file metadata, and determining the size of the target profile file. In the above technical solution, the terminal device calls the ES8+.StoreMetadata instruction through the first interface to obtain the target profile file metadata, and determines the target profile file size from the target profile file metadata.

[0006] In one embodiment of the present application, the determining the remaining memory of the eSIM chip includes: sending a request to the eSIM chip to obtain the remaining memory of the eSIM chip, and receiving the remaining memory of the eSIM chip sent by the eSIM chip. In the above technical solution, the terminal device obtains the remaining memory of the eSIM chip returned by the eSIM chip by sending a request to the eSIM chip to obtain the remaining memory.

[0007] In one embodiment of the present application, the sending of a request to the SIM chip to obtain the remaining memory of the eSIM chip, and receiving the remaining memory of the eSIM chip sent by the eSIM chip include: calling the ES10b.GetEUICCInfo instruction through the second interface (ES10b) to send a request to the eSIM chip to obtain the remaining memory of the eSIM chip, and receiving the remaining memory of the eSIM chip through the second interface. In the above technical solution, the ES10b.GetEUICCInfo instruction is called through the second interface to send a request to the eSIM chip to obtain the remaining memory of the eSIM chip, and the remaining memory of the eSIM chip returned by the eSIM chip is received through the second interface.

[0008] In one embodiment of the present application, the process of canceling the download of the target profile file includes: calling the ES10b.CancelSession instruction through the second interface (ES10b) to cancel the download process of the target profile file. In the above technical solution, the ES10b.CancelSession instruction is called through the second interface to initiate the download process cancellation instruction to the eSIM chip, thereby preventing the SM-DP+ server from setting the status of the profile to an error.

[0009] In one embodiment of the present application, after deleting the selected profile file, initiating the download process of the target profile file again includes: calling the ES10c.DeleteProfile instruction through the third interface (ES10c) to delete the profile file selected by the user. In the above technical solution, the terminal device automatically cleans up the profile file selected by the user through the third interface calling the ES10c.DeleteProfile instruction, thereby releasing the storage space of the eSIM chip.

[0010] In an embodiment of the present application, the outputting the prompt information includes: displaying the prompt information through a pop-up window.

[0011] In one embodiment of the present application, the acquiring the address and password of the SM-DP+ server includes: receiving the address and password of the SM-DP+ server input by the user through a file download setting interface. In the above technical solution, the address and password of the SM-DP+ server are received through the file download setting interface to start downloading the target profile file.

[0012] In one embodiment of the present application, obtaining the address and password of the SM-DP+ server includes: obtaining the address and password of the SM-DP+ server by scanning a QR code. In the above technical solution, the address and password of the SM-DP+ server are obtained by scanning a QR code to start downloading the target profile file.

[0013] In one embodiment of the present application, after receiving the target profile file metadata sent by the SM-DP + server, the method further includes: determining whether the target profile file metadata includes a limiting condition, wherein the limiting condition includes at least one of not being able to support activation and not being able to support deletion.

[0014] In one embodiment of the present application, after sending a request to the eSIM chip to obtain the remaining memory of the eSIM chip, and receiving the remaining memory of the eSIM chip sent by the eSIM chip, the method further includes: sending a request to the eSIM chip to obtain a profile file list, and receiving the profile file list sent by the eSIM chip.

[0015] In one embodiment of the present application, the request for obtaining a profile file list is sent to the eSIM chip by calling the ES10b.Getprofilesinfo instruction through the second interface (ES10b) to send a request for obtaining a profile file list to the eSIM chip. In the above technical solution, the request for obtaining a profile file list is sent to the eSIM chip by calling the ES10b.Getprofilesinfo instruction through the second interface.

[0016] In one embodiment of the present application, if the remaining memory of the eSIM chip is less than the size of the target profile file, canceling the download process of the target profile file includes: determining whether the target profile file is in the profile file list; if the target profile file is in the profile file list and the remaining memory of the eSIM chip is less than the size of the target profile file, canceling the download process of the target profile file. In the above technical solution, if the target profile file is in the profile file list and the remaining memory of the eSIM chip is less than the size of the target profile file, canceling the download process of the target profile file, thereby avoiding the SM-DP+ server from setting the status of the profile to an error.

[0017] In a second aspect, some embodiments of the present application provide an electronic device, which includes a memory and a processor: wherein the memory is used to store program instructions; the processor is used to read and execute the program instructions stored in the memory, and when the program instructions are executed by the processor, the electronic device executes the above-mentioned profile file download management method.

[0018] In a third aspect, some embodiments of the present application provide a computer storage medium storing program instructions. When the program instructions are executed on an electronic device, the electronic device executes the above-mentioned profile file download management method.

[0019] In addition, the technical effects brought about by the second to third aspects can be found in the descriptions related to the methods of each design in the above method part, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1a This is a schematic diagram of a SIM card setting interface in an embodiment of the present application.

[0021] Figure 1b This is a schematic diagram of a download setting interface in an embodiment of the present application.

[0022] Figure 1c This is a schematic diagram of a download display interface in an embodiment of the present application.

[0023] Figure 1d This is a schematic diagram of a SIM card setting interface in another embodiment of the present application.

[0024] Figure 1e This is a schematic diagram of a download setting interface in another embodiment of the present application.

[0025] Figure 2Schematic diagram of the architecture of a profile file download management system in one embodiment of the present application.

[0026] Figure 3 This is a flow chart of a profile file download management method in one embodiment of the present application.

[0027] Figure 4 This is a flow chart of bidirectional authentication between LPAd and SM-DP+ server in one embodiment of the present application.

[0028] Figure 5 This is a flowchart of a profile file download management method in another embodiment of the present application.

[0029] Figure 6 Schematic diagram of the hardware structure of an electronic device in one embodiment of the present application. DETAILED DESCRIPTION

[0030] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of some embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in some embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way.

[0031] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those generally understood by technicians in the technical field in this application. The terms used in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application. It should be understood that, unless otherwise specified in this application, " / " means or. For example, A / B can represent A or B. "And / or" in some embodiments of the present application is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. "At least one" means one or more. "Multiple" means two or more than two. For example, at least one of a, b or c can represent: a, b, c, a and b, a and c, b and c, a, b and c seven situations.

[0032] To facilitate the understanding of the following text, some terms are briefly explained first:

[0033] Subscriber identification module (SIM) cards may include: ordinary pluggable SIM cards, embedded universal integrated circuit cards (eUICC), also known as eSIM (embedded SIM), integrated universal integrated circuit cards (iUICC). The hardware circuit of the terminal carrying the SIM card is burned with the SIM card slot and its circuit structure. By inserting the SIM card in the SIM card slot, the hardware circuit will power on the card. The SIM card contains the card file and the authentication information of the network call. After the power-on is successful, the SIM card will be identified and the machine-card interaction on the protocol side will be performed. Among them, ordinary pluggable SIM cards need to replace the SIM card to achieve the replacement of code resources. eSIM and iUICC can download the profile required for connecting to the operator network from the mobile network operator. Among them, eSIM is an eSIM chip with an integrated card slot and a real card, in which the eSIM chip is welded on the baseband hardware, and the card file and the authentication parameters related to the network call need to be written into the eSIM chip by downloading the profile file.

[0034] Among them, ordinary pluggable SIM cards are smart cards mainly used to store user identification data, SMS data and phone numbers. They comply with the European Telecommunications Standards Institute (ETSI) and the International Organization for Standardization (ISO)-7816 standard SIM cards. Generally refers to the SIM card purchased by the user from the communication operator. Fixed SIM data has been burned into it when it leaves the factory. After it is placed in the terminal, the user has the right to use the communication services provided by the operator. The SIM card can be replaced by plugging and unplugging and the code number resources can be changed. The hardware packaging structure and corresponding pins of the SIM card comply with the ISO 7816 protocol, and the 3GPP (3rd Generation Partnership Project) protocol communication between the terminal and the SIM card.

[0035] eUICC, also known as eSIM, is a secure element that can be remotely managed by multiple communication operators for contracted users. The eSIM is soldered in the baseband hardware circuit and cannot be plugged in or out.

[0036] iUICC refers to a universal integrated circuit card (UICC) fixed to a terminal and used, which can remotely download and select sim modules.

[0037] The local profile assistant (LPA) can be used for profile file download management, service discovery, and providing users with a user interface UI (such as a profile file installation list), so that users can manage the local profile files of the eSIM (for example, activating, deactivating, deleting, downloading, or unlocking the Profile). In addition, the terminal device can also retrieve the eUICC identification (eUICC identification, EID) and / or the integrated circuit card identification (integrated circuit card ID, ICCID) through the LPA module. The LPA module is a virtual logic module. The LPA includes a local discovery service (LDS), a local profile download (LPD), and a local user interface UI (LUI). The LPA in the terminal device and eSIM can be composed of any one or more of LDS, LPD, and LUI.

[0038] The service provider can be a basic operator, such as China Mobile, China Unicom, etc.; it can also be a terminal manufacturer as a service provider; it can also be a card manufacturer as a service provider; it can also be a certain enterprise as a service provider; it can also be a certain virtual operator as a service provider, etc. The service provider server is a server deployed by the service provider to provide wireless communication services, such as a mobile network operator (MNO) server, a service platform server provided by a terminal manufacturer for its branded terminal, or a service platform server provided by an enterprise for its enterprise users, etc.

[0039] Usually, when the eSIM card memory is insufficient, if the terminal downloads a new profile file, an error will be reported due to insufficient memory. The Subscription Manager Data Preparation+ (SM-DP+) server will set the status of the profile file that failed to download to error. At this time, if the user obtains sufficient storage space by deleting the existing files in the eSIM chip, if the user downloads the profile file again, he needs to contact the operator to reset the status of the profile file to downloadable status before he can successfully download it, which causes inconvenience to the user in downloading the profile file.

[0040] refer to Figure 1a The following is the SIM card setting interface displayed on the terminal device. The user clicks the "Add eSIM" option on the SIM card setting interface of the terminal device to enter the file download setting interface (reference Figure 1b ). The file download setting interface includes an address field and a password field. The address field is used to receive the address of the SM-DP+ server entered by the user. The password field is used to receive the activation code entered by the user. Figure 1b , the address of the SM-DP+ server entered by the user in the address field can be "testsmdpplus1.example.com", and the activation password entered in the password field can be "2315". After entering the address of the SM-DP+ server and the activation code, the user clicks the "Next (NEXT)" option to execute the download of the Profile file and enter the download display interface. Reference Figure 1c As shown, the download display interface is used to display the download result. Since the eSIM chip does not have enough storage space for downloading a new Profile file, the download display interface displays a prompt message to remind the user that the Profile file download failed, and the SM-DP+ server sets the status of the Profile file to error. In one embodiment of the present application, the prompt message may be that the eSIM chip does not have enough storage space for downloading the Profile file, please delete other Profile files and download again (Insufficient storage on eSIM chip. Delete aneSIM and try again).

[0041] If the user is Figure 1d Select the profile file to be deleted on the SIM card setting interface shown in the figure and click the "Disabled" option to delete the selected profile file to release the memory space of the eSIM chip. The user clicks the "Add eSIM" option on the SIM card setting interface of the terminal to enter the file download setting interface (refer to Figure 1b ). The user enters the address of the SM-DP+ server and the activation code in the file download settings interface and clicks the "Next" option to download the Profile file. At this point, although the user has manually deleted the profile file so that the memory space of the eSIM chip can meet the download requirements, when downloading the profile file again in the file download settings interface (refer to Figure 1e) will display an error message, reminding the user that the profile file is unavailable and that the user needs to contact the carrier to re-preset the profile status to a downloadable status, which causes inconvenience to the user's operation. For example, the error message may be "The eSIM profile is already in use or is invalid. Contact your carrier for details."

[0042] In order to solve the above-mentioned technical problems, the embodiment of the present application provides a profile file download management method, which can solve the problem that when the memory of the eSIM chip is insufficient, the user needs to contact the operator again to reset the profile status before continuing to download the profile file. In order to facilitate the description of the profile file download management method, the following first describes the profile file download management system. Figure 2 As shown, it is a schematic diagram of an application scenario of a profile file download management system in one embodiment of the present application. Figure 2 As shown, the profile file download management system 10 includes an operator server 20, an SM-DP+ server 30, and a terminal 40. The terminal 40 includes a local profile assistant device (Local Profile Assistant (LPA) when LPA is in the device, LPAd) 41 and an eSIM chip 42. LPAd 41 is used to obtain the address and password of the SM-DP+ server, and establish a communication connection with the SM-DP+ server 30 according to the address and password of the SM-DP+ server.

[0043] After establishing the communication connection, the SM-DP+ server sends profile file metadata (profileMetadata) to LPAd 41, where the profile file metadata includes the profile file size. LPAd 41 calls the ES8+.StoreMetadata instruction through the first interface (ES8+) to obtain the profile metadata and determine the profile file size. LPAd 41 calls the ES10b.GetEUICCInfo instruction through the second interface (ES10b) to obtain the memory of the eSIM chip 42. LPAd 41 compares the memory of the eSIM chip 42 with the profile file size. If the memory of the eSIM chip 42 is smaller than the profile file size, the ES10b.CancelSession instruction is called through the second interface to initiate a download process cancellation instruction to the eSIM chip 42 and the SM-DP+ server 30 to prevent the SM-DP+ server 30 from setting the status of the profile to error. LPAd 41 calls the ES10c.DeleteProfile command through the third interface (ES10c) to clean up the profile file in the eSIM chip 42 for the user, thereby avoiding the problem that the SM-DP+ server 30 sets the status of the profile file to error due to insufficient memory of the eSIM chip 42, and the user needs to contact the operator again to reset the profile status before continuing to download the profile file.

[0044] In an embodiment of the present application, the terminal 40 may be one of the following devices: a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, and a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, a vehicle-mounted device, a smart home device, and / or a smart city device. The embodiments of the present application do not impose any special restrictions on the specific type of the terminal 40.

[0045] The above description does not constitute a limitation on the architecture diagram of the profile file download management system 10 of the embodiment of the present application. The architecture of the profile file download management system 10 of the embodiment of the present application includes but is not limited to the following: Figure 2 The architecture shown.

[0046] The profile file download management method provided in this application can be applied in the profile file download management system 10. Figure 3 The flowchart shown illustrates the signal interaction process between various devices in the profile file download management system 10 to implement the download management of the profile file at the terminal 40.

[0047] refer to Figure 3 As shown, it is a flowchart of a profile file download management method provided in an embodiment of the present application, which specifically includes the following steps.

[0048] In step S31, LPAd 41 obtains the address and password of the SM-DP+ server 30 to download the target Profile file, wherein the password includes an activation code (AC) code and a CC code that need to be verified during the download of the target Profile file.

[0049] In one embodiment of the present application, LPAd 41 is configured through a file download setting interface (see Figure 1b ) Receive the address and password of the SM-DP+ server entered by the user. For example, LPAd 41 receives the address of the SM-DP+ server 30 entered by the user in the address field of the file setting interface, and receives the AC code and CC code entered by the user in the password field.

[0050] In another embodiment of the present application, LPAd 41 may also obtain the address and password of the SM-DP+ server 30 by scanning a QR code.

[0051] In step S32, LPAd 41 performs two-way authentication with SM-DP+ server 30, and establishes a communication connection after the two-way authentication.

[0052] refer to Figure 4 As shown, it is a flowchart of two-way authentication between LPAd 41 and SM-DP+ server 30 in one embodiment of the present application, including the following steps.

[0053] In step S321, LPAd 41 obtains the support list of the certificate issuer (CI) public key and the random number from the eSIM chip 42 (ie, eUICC) and sends them to the SM-DP+ server 30.

[0054] In step S322, the SM-DP+ server 30 selects a supported CI public key to generate an SM-DP+ server certificate, and sends the information signed by the SM-DP+ server certificate and the SM-DP+ server private key to LPAd 41.

[0055] In step S323, LAd 41 sends the information signed by the SM-DP+ server certificate and the SM-DP+ server private key to the eSIM chip 42.

[0056] In step S324, the eSIM chip 42 completes the first authentication, confirms the validity of the SM-DP+ server certificate, and then sends the EUM certificate and eUICC certificate to the LAd 41.

[0057] In step S325 , LPAd 41 sends the EUM certificate to the SM-DP+ server 30 .

[0058] In step S326, the SM-DP+ server 30 completes secondary authentication and confirms the validity of the EUM certificate and the eUICC certificate.

[0059] Step S33: The SM-DP+ server 30 searches for the target profile file.

[0060] Step S34: The SM-DP+ server 30 processes the download progress information of the target profile file.

[0061] In one embodiment of the present application, the SM-DP+ server 30 calls the ES2+.Handledownloadprogressinfo instruction through the fourth interface (ES2+) to process the download progress information of the target profile file from the operator server 20.

[0062] Step S35, establishing target profile file metadata (profile Metadata).

[0063] In one embodiment of the present application, the target profile file metadata includes basic attributes of the profile file. In one embodiment of the present application, the target profile file metadata includes, but is not limited to: identity information of the target profile file and the size of the target profile file.

[0064] In step S36 , the SM-DP+ server 30 sends the target profile metadata to the LPAd 41 .

[0065] In one embodiment of the present application, LPAd 41 calls ES8+.StoreMetadata instruction through the first interface (ES8+) to obtain profile file metadata and determine the target profile file size.

[0066] In step S37, LAd 41 determines whether the target profile file metadata includes a limiting condition.

[0067] In one embodiment of the present application, the limiting condition includes at least one of not being able to support activation and not being able to support deletion. In one embodiment of the present application, the limiting condition is not judged in the download process of the profile file, but is used to limit the user's operation when the user deactivates or deletes the profile file in the user usage scenario after the profile file is successfully downloaded. In one embodiment of the present application, step S38 is executed when it is determined that the target profile file metadata includes the limiting condition. In another embodiment of the present application, step S37 can be omitted.

[0068] In step S38 , LPAd 41 sends a request to the eSIM chip 42 to obtain the remaining memory of the eSIM chip 42 .

[0069] In one embodiment of the present application, LPAd 41 calls ES10b.GetEUICCInfo instruction through the second interface (ES10b) to send a request for obtaining the remaining memory size of the eSIM chip 42 to the eSIM chip 42.

[0070] In step S39 , the eSIM chip 42 sends information about the remaining memory size of the eSIM chip 42 to the LAd 41 .

[0071] In step S40 , LPAd 41 sends a request to the eSIM chip 42 to obtain a Rules Authorisation Table (RAT).

[0072] In one embodiment of the present application, LPAd 41 calls ES10b.GetBAT instruction through the second interface (ES10b) to send a request to eSIM chip 42 to obtain RAT. In one embodiment of the present application, RAT is used to check the corresponding authorization, including checking the authorization for access between card vendors, operators and terminal equipment vendors. In one embodiment of the present application, if the terminal does not support a certain feature, such as not supporting PPR, even if the corresponding operator and card vendor are in the authorization table, the download will report an error.

[0073] In step S41 , the eSIM chip 42 sends the RAT to the LPAd 41 .

[0074] In step S42, LAd 41 sends a request to the eSIM chip 42 to obtain a profile file list.

[0075] In one embodiment of the present application, LPAd 41 sends a request for obtaining a profile file list to the eSIM chip 42 by calling the ES10b.Getprofilesinfo instruction through the second interface (ES10b).

[0076] In step S43 , the eSIM chip 42 sends the profile file list to the LAd 41 .

[0077] In step S44, LAd 41 determines that the remaining memory of eSIM chip 42 is smaller than the target profile file size.

[0078] In one embodiment of the present application, LPAd 41 determines whether the remaining memory of the eSIM chip 42 is less than the target profile file size. If the remaining memory of the eSIM chip 42 is less than the target profile file size, step S45 is executed; if the remaining memory of the eSIM chip 42 is greater than or equal to the target profile file size, LPAd 41 sends an indication message to the SIM chip 42 to instruct the re-download of the target Profile file.

[0079] Step S45: LAd 41 sends a download process cancel instruction to the eSIM chip 42.

[0080] In one embodiment of the present application, LPAd 41 calls ES10b.CancelSession command through the second interface (ES10b) to initiate a download process cancellation command to the eSIM chip 42 and the SM-DP+ server 30 to prevent the SM-DP+ server 30 from setting the status of the target profile file to error.

[0081] Step S46: LAd 41 sends a prompt message to remind the user to clean up the memory of the eSIM chip.

[0082] In one embodiment of the present application, LPAd 41 displays a prompt message through a pop-up window. The prompt message may be that the eSIM chip memory is insufficient, click to clean up unactivated and unused profile files.

[0083] Step S47: LPAd 41 receives the user's deletion operation on the selected profile file and deletes the selected profile file.

[0084] In one embodiment of the present application, LAd 41 calls ES10c.DeleteProfile command through the second interface to automatically clean up the profile file of the eSIM chip 42 selected by the user.

[0085] Step S48: Send instruction information to the SIM chip 42 to instruct to re-download the target Profile file.

[0086] Step S49: Determine whether the restriction condition of the target Profile file satisfies the RAT. If the restriction condition of the target Profile file satisfies the RAT, execute step S51; if the restriction condition of the target Profile file does not satisfy the RAT, execute step S50.

[0087] Step S50: Refuse to download the target Profile file.

[0088] Step S51: Download the target Profile file.

[0089] In one embodiment of the present application, the target profile file metadata also includes preset terminal capability information. After step S36, the method further includes: after the LPAd 41 receives the target profile file metadata sent by the SM-DP+ server 30, obtaining the preset terminal capability information from the target profile file metadata; obtaining the terminal capability information of the terminal 40; determining whether the terminal capability information of the terminal 40 matches the preset terminal capability information; if the terminal capability information of the terminal 40 does not match the preset terminal capability information, executing step S50; if the terminal capability information of the terminal 40 matches the preset terminal capability information, executing step S38.

[0090] LPAd 41 compares the remaining memory of the eSIM chip 42 with the size of the profile file. If the remaining memory of the eSIM chip 42 is less than the size of the profile file, the ES10b.CancelSession command is called through the second interface to initiate a download process cancellation command to the eSIM chip 42 and the SM-DP+ server 30, thereby preventing the SM-DP+ server 30 from setting the status of the profile to error. LPAd 41 calls the ES10c.DeleteProfile command through the third interface (ES10c) to automatically clear the profile file selected by the user in the eSIM chip 42, thereby avoiding the problem that the user needs to contact the operator again to reset the profile status before continuing to download the profile file after the SM-DP+ server 30 sets the status of the profile file to error due to insufficient memory of the eSIM chip 42.

[0091] refer to Figure 5 FIG. 4 is a flow chart of a profile file download management method provided by another embodiment of the present application. The method is applied in LPAd 41 and specifically includes the following steps.

[0092] In step S61, LAd 41 obtains the address and password of the SM-DP+ server to download the target Profile file, where the password includes the AC code and CC code that need to be verified during the download of the target Profile file.

[0093] In one embodiment of the present application, the SM-DP+ server is called a subscription management server, which is a server for downloading Profile. The SM-DP+ server may be a subscription manager data preparation (SM-DP) server, wherein the SM-DP server includes an SM-DP+ server 30.

[0094] In step S62, LPAd 41 performs two-way authentication with the SM-DP+ server and establishes a communication connection after the two-way authentication.

[0095] In step S63, LAd 41 receives the target profile file metadata sent by the SM-DP+ server, where the target profile file metadata includes the target profile file size.

[0096] In one embodiment of the present application, LPAd 41 calls ES8+.StoreMetadata instruction through the first interface (ES8+) to obtain target profile file metadata and determine the target profile file size.

[0097] In step S64, LPAd 41 determines the remaining memory of the eSIM chip.

[0098] In one embodiment of the present application, LPAd 41 determines the remaining memory of the eSIM chip, including: LPAd 41 sends a request to the eSIM chip 42 to obtain the remaining memory of the eSIM chip 42, and receives the remaining memory of the eSIM chip 42 sent by the eSIM chip 42.

[0099] In one embodiment of the present application, LPAd 41 calls ES10b.GetEUICCInfo instruction through the second interface (ES10b) to send a request to the eSIM chip 42 to obtain the remaining memory of the eSIM chip 42, and receives the size of the remaining memory of the eSIM chip 42 sent by the eSIM chip 42 through the second interface.

[0100] In step S65 , when LAd 41 determines that the remaining memory of eSIM chip 42 is smaller than the target profile file size, it sends a download process cancel instruction to eSIM chip 42 .

[0101] In one embodiment of the present application, LPAd 41 calls the ES10b.CancelSession instruction through the second interface (ES10b) to initiate a download process cancellation instruction to the eSIM chip 42 and the SM-DP+ server 30, thereby preventing the SM-DP+ server 30 from setting the status of the target profile file to error.

[0102] Step S66: LAd 41 sends a prompt message, where the prompt message is used to remind the user to clean up the memory of the eSIM chip.

[0103] In one embodiment of the present application, LPAd 41 displays a prompt message through a pop-up window. The prompt message may be that the eSIM chip memory is insufficient, click to clean up unactivated and unused profile files.

[0104] Step S67: LPAd 41 receives the user's deletion operation on the selected profile file, deletes the selected profile file, and after deleting the selected profile file, initiates the download process of the target profile file again.

[0105] In one embodiment of the present application, LPAd 41 calls ES10c.DeleteProfile instruction through the third interface (ES10c) to automatically clear the profile file of the eSIM chip 42 selected by the user.

[0106] refer to Figure 6 FIG. 4 is a schematic diagram of the hardware structure of an electronic device 100 in an embodiment of the present application. The electronic device 100 includes a terminal 40 .

[0107] The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0108] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine some components, or separate some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0109] The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0110] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0111] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0112] In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0113] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple groups of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through the I2C interface, so that the processor 110 communicates with the touch sensor 180K through the I2C bus interface, thereby realizing the touch function of the electronic device 100.

[0114] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to achieve communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 via the I2S interface to achieve the function of answering a call through a Bluetooth headset.

[0115] The PCM interface can also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface to realize the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0116] The UART interface is a universal serial data bus for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is generally used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

[0117] The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to implement the shooting function of the electronic device 100. The processor 110 and the display screen 194 communicate via the DSI interface to implement the display function of the electronic device 100.

[0118] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0119] The USB interface 130 is an interface that complies with the USB standard specification, and can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transfer data between the electronic device 100 and a peripheral device. It can also be used to connect headphones to play audio through the headphones. The interface can also be used to connect other electronic devices 100, such as AR devices, etc.

[0120] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present invention is only a schematic illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0121] The charging management module 140 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. While the charging management module 140 is charging the battery 142, it may also power the electronic device 100 through the power management module 141.

[0122] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0123] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0124] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0125] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0126] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0127] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0128] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0129] The electronic device 100 implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

[0130] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

[0131] The electronic device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0132] ISP is used to process the data fed back by camera 193. For example, when taking a photo, the shutter is opened, and the light is transmitted to the camera photosensitive element through the lens. The light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to ISP for processing and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on the noise, brightness, and skin color of the image. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, ISP can be set in camera 193.

[0133] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0134] The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the electronic device 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0135] Video codecs are used to compress or decompress digital videos. The electronic device 100 may support one or more video codecs. Thus, the electronic device 100 may play or record videos in a variety of coding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0136] NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of electronic device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

[0137] The internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM).

[0138] Random access memory may include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM, for example, the fifth generation DDR SDRAM is generally referred to as DDR5 SDRAM), etc.

[0139] Non-volatile memory may include disk storage devices and flash memory.

[0140] Flash memory can be divided into NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. according to the operating principle; single-level cell (SLC), multi-level cell (MLC), triple-level cell (TLC), quad-level cell (QLC), etc. according to the storage unit potential level; universal flash storage (UFS), embedded multi media card (eMMC), etc. according to the storage specification.

[0141] The random access memory can be directly read and written by the processor 110, and can be used to store executable programs (such as machine instructions) of the operating system or other running programs, and can also be used to store user and application data, etc.

[0142] The non-volatile memory may also store executable programs and user and application data, etc., and may be loaded into the random access memory in advance for direct reading and writing by the processor 110 .

[0143] The external memory interface 120 can be used to connect to an external non-volatile memory to expand the storage capacity of the electronic device 100. The external non-volatile memory communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and videos are stored in the external non-volatile memory.

[0144] The internal memory 121 or the external memory interface 120 is used to store one or more computer programs. The one or more computer programs are configured to be executed by the processor 110. The one or more computer programs include multiple instructions. When the multiple instructions are executed by the processor 110, the profile file download management method executed on the electronic device 100 in the above embodiment can be implemented to implement the profile file download management function of the electronic device 100.

[0145] The electronic device 100 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0146] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110.

[0147] The speaker 170A, also called a "speaker", is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or listen to a hands-free call through the speaker 170A.

[0148] The receiver 170B, also called a "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or voice message, the voice can be received by placing the receiver 170B close to the human ear.

[0149] Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to microphone 170C to input the sound signal into microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the sound source, realize directional recording function, etc.

[0150] The earphone interface 170D is used to connect a wired earphone and can be a USB interface 130, or a 3.5 mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0151] The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be set on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 can also calculate the touch position according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.

[0152] The gyro sensor 180B can be used to determine the motion posture of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 around three axes (i.e., x, y, and z axes) can be determined by the gyro sensor 180B. The gyro sensor 180B can be used for anti-shake shooting. For example, when the shutter is pressed, the gyro sensor 180B detects the angle of the electronic device 100 shaking, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shaking of the electronic device 100 through reverse movement to achieve anti-shake. The gyro sensor 180B can also be used for navigation and somatosensory game scenes.

[0153] The pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude through the air pressure value measured by the pressure sensor 180C to assist positioning and navigation. The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip leather case. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover according to the magnetic sensor 180D. Then, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, the characteristics such as automatic unlocking of the flip cover are set. The acceleration sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in all directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the electronic device 100, and is applied to horizontal and vertical screen switching, pedometers and other applications. Distance sensor 180F, used to measure distance. The electronic device 100 can measure distance through infrared or laser. In some embodiments, when photographing a scene, the electronic device 100 may utilize the distance sensor 180F to measure distance to achieve fast focusing.

[0154] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 can use the proximity light sensor 180G to detect that the user holds the electronic device 100 close to the ear to talk, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode and pocket mode to automatically unlock and lock the screen.

[0155] The ambient light sensor 180L is used to sense the ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

[0156] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0157] The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of a processor located near the temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to avoid abnormal shutdown of the electronic device 100 due to low temperature. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 performs a boost on the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

[0158] The touch sensor 180K is also called a "touch control device". The touch sensor 180K can be set on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch control screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the electronic device 100, which is different from the position of the display screen 194.

[0159] The bone conduction sensor 180M can obtain a vibration signal. In some embodiments, the bone conduction sensor 180M can obtain a vibration signal of a vibrating bone block of the vocal part of the human body. The bone conduction sensor 180M can also contact the human pulse to receive a blood pressure beat signal. In some embodiments, the bone conduction sensor 180M can also be set in an earphone and combined into a bone conduction earphone. The audio module 170 can parse out a voice signal based on the vibration signal of the vibrating bone block of the vocal part obtained by the bone conduction sensor 180M to realize a voice function. The application processor can parse the heart rate information based on the blood pressure beat signal obtained by the bone conduction sensor 180M to realize a heart rate detection function.

[0160] The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.

[0161] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0162] Indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0163] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to and separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195. The electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100.

[0164] This embodiment also provides a computer program product. When the computer program product runs on a computer, it enables the computer to execute the above-mentioned related steps to implement the profile file download management method in the above-mentioned embodiment.

[0165] In addition, some embodiments of the present application also provide a device, which may specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer execution instructions, and when the device is running, the processor may execute the computer execution instructions stored in the memory so that the chip executes the profile file download management method in the above-mentioned method embodiments.

[0166] Among them, the electronic device, computer storage medium, computer program product or chip provided in this embodiment is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above and will not be repeated here.

[0167] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0168] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, 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 interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0169] The unit described as a separate component may or may not be physically separated, and the component displayed as a unit may be a physical unit or multiple physical units, that is, it may be located in one place, or it may be distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, each functional unit in each embodiment of the present application may be integrated in a processing unit, or each unit may exist physically separately, or two or more units may be integrated in one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0170] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of some embodiments of the present application are essentially or partly contributed to the prior art or all or part of the technical solutions can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the methods of each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0171] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of some embodiments of the present application and are not limiting. Although some embodiments of the present application are described in detail with reference to the preferred embodiments, ordinary technicians in this field should understand that the technical solutions of some implementation examples of the present application can be modified or replaced by equivalents without departing from the spirit and scope of the technical solutions of some embodiments of the present application.

Claims

1. A profile file download management method, applied to a terminal device, characterized in that: The terminal device includes an eSIM chip, and the method includes: Obtain the address and password of the SM-DP+ server, where the password includes the activation code (AC) and confirmation code (CC) required to verify during the download of the target profile file; Perform two-way authentication with the SM-DP+ server and establish a communication connection after the two-way authentication passes; receiving target profile file metadata sent by the SM-DP+ server, the target profile file metadata including a size of the target profile file, wherein the SM-DP+ server processes download progress information of the target profile file; Obtaining preset terminal capability information from the target profile file metadata; obtaining terminal capability information of the terminal device; if the terminal capability information does not match the preset terminal capability information, refusing to download the target Profile file; If the terminal capability information matches the preset terminal capability information, determining the remaining memory of the eSIM chip; If the remaining memory of the eSIM chip is less than the size of the target profile file, canceling the download process of the target profile file includes: initiating a download process cancellation instruction to the SM-DP+ server by calling a CancelSession instruction, so that the SM-DP+ server does not set the status of the target profile file to an error; Outputting a prompt message to remind the user to clean up the memory of the eSIM chip; Determine the Profile file to be deleted selected by the user on the SIM card setting interface, and after deleting the selected Profile file, re-initiate the download process of the target Profile file, wherein the selected Profile file is an unactivated and unused Profile file, and the re-initiating the download process of the target Profile file includes: if the restriction condition of the target Profile file satisfies the rule authorization table RAT, download the target Profile file.

2. The profile file download management method according to claim 1, characterized in that: The receiving the target profile file metadata sent by the SM-DP+ server includes: Calling the ES8+.StoreMetadata instruction through the first interface (ES8+) to obtain the target profile file metadata and determine the size of the target profile file, Determining the remaining memory of the eSIM chip includes: A request for obtaining the remaining memory of the eSIM chip is sent to the eSIM chip, and the remaining memory of the eSIM chip sent by the eSIM chip is received.

3. The profile file download management method according to claim 2, characterized in that: The sending a request to the eSIM chip to obtain the remaining memory of the eSIM chip includes: When it is determined that the target profile file metadata includes a limiting condition, executing the step of sending a request to the eSIM chip to obtain the remaining memory of the eSIM chip; The limiting condition includes at least one of not being able to support activation and not being able to support deletion.

4. The profile file download management method according to claim 3, characterized in that: The sending a request to the SIM chip to obtain the remaining memory of the eSIM chip, and receiving the remaining memory of the eSIM chip sent by the eSIM chip includes: The ES10b.GetEUICCInfo instruction is called through the second interface (ES10b) to send a request to the eSIM chip to obtain the remaining memory of the eSIM chip, and the remaining memory of the eSIM chip is received through the second interface.

5. The profile file download management method according to claim 1, characterized in that: The process of canceling the download of the target profile file includes: The ES10b.CancelSession instruction is called through the second interface (ES10b) to cancel the download process of the target profile file.

6. The profile file download management method according to claim 1, characterized in that: After deleting the selected profile file, initiating a download process for the target profile file again includes: The ES10c.DeleteProfile instruction is called through the third interface (ES10c) to delete the profile file selected by the user.

7. The profile file download management method according to claim 1, characterized in that: The output prompt information includes: The prompt information is displayed through a pop-up window.

8. The profile file download management method according to claim 1, characterized in that: The obtaining of the address and password of the SM-DP+ server includes: Receive the address of the SM-DP+ server and the password entered by the user through the file download setting interface.

9. The profile file download management method according to claim 1, characterized in that: The obtaining of the address and password of the SM-DP+ server includes: Obtain the address and password of the SM-DP+ server by scanning the QR code.

10. The profile file download management method according to claim 3, characterized in that: After sending a request to the eSIM chip to obtain the remaining memory of the eSIM chip and receiving the remaining memory of the eSIM chip sent by the eSIM chip, the method further includes: Send a request to the eSIM chip to obtain a profile file list, and receive the profile file list sent by the eSIM chip.

11. The profile file download management method according to claim 10, characterized in that: The sending a request to the eSIM chip to obtain a profile file list includes: The ES10b.Getprofilesinfo instruction is called through the second interface (ES10b) to send a request for obtaining a profile file list to the eSIM chip.

12. The profile file download management method according to claim 11, characterized in that: The process of canceling downloading of the target profile file if the remaining memory of the eSIM chip is smaller than the size of the target profile file includes: Determine whether the target profile file is in the profile file list; If the target profile file is in the profile file list and the remaining memory of the eSIM chip is smaller than the size of the target profile file, the download process of the target profile file is canceled.

13. An electronic device, characterized in that: The electronic device comprises a memory and a processor: The memory is used to store program instructions; The processor is used to read and execute the program instructions stored in the memory. When the program instructions are executed by the processor, the electronic device executes the profile file download management method as described in any one of claims 1 to 12.

14. A computer storage medium, characterized in that: The computer storage medium stores program instructions, and when the program instructions are executed on an electronic device, the electronic device executes the profile file download management method according to any one of claims 1 to 12.

Images