CN117135620A

CN117135620A - Profile file downloading management method, electronic equipment and computer storage medium

Info

Publication number: CN117135620A
Application number: CN202310119627.8A
Authority: CN
Inventors: 吴雪霜; 王祯; 樊攀蕾
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2023-02-01
Filing date: 2023-02-01
Publication date: 2023-11-28

Abstract

The embodiment of the application relates to a profile file downloading management method, electronic equipment and a computer storage medium. The method obtains an address and a password of an SM-DP+ server; carrying out bidirectional authentication with an SM-DP+ server, and carrying out communication connection after the bidirectional authentication; receiving target profile file metadata sent by an SM-DP+ server, wherein the target profile file metadata comprises a target profile file size; determining the residual memory of the eSIM chip; if the residual memory of the eSIM chip is smaller than the size of the target profile file, initiating a downloading flow cancellation instruction to the eSIM chip; sending out prompt information to remind a user to clean the memory of the eSIM chip; and receiving the deleting operation of the user on the selected profile file, and deleting the selected profile file. The embodiment of the 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 state of the profile file as an error and then influences the efficiency of downloading the profile file again by a user.

Description

Profile file downloading management method, electronic equipment and computer storage medium

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a profile file download management method, an electronic device, and a computer storage medium.

Background

When the embedded subscriber identity module (embedded subscriber identity module, eSIM) card has insufficient memory, if the terminal downloads the profile file, the error is reported due to insufficient memory. The subscription management data preparation (Subscription Manager Data Preparation +, SM-dp+) server sets the status of the profile file with failed download as error. Because the Profile file with failed download is set as an error, even if the storage space of the eSIM card is cleaned later, the Profile file cannot be directly downloaded again, and the eSIM causes inconvenience to the user in downloading the Profile file.

Disclosure of Invention

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

In a first aspect, an embodiment of the present application provides a profile file download management method, applied to a terminal device, where the terminal device includes an eSIM chip, and the method includes: acquiring an address and a password of an SM-DP+ server, wherein the password comprises an Activation Code (AC) and a confirmation Code (Confirmation Code, CC) which need to be verified in the process of downloading a target profile file; carrying out bidirectional authentication with the SM-DP+ server, and establishing communication connection after the bidirectional authentication is passed; receiving target profile file metadata sent by the SM-DP+ server, wherein the target profile file metadata comprises the size of the target profile file; determining the residual memory of the eSIM chip; if the residual memory of the eSIM chip is smaller than the size of the target profile file, canceling the downloading flow of the target profile file; outputting prompt information to remind a user to clean the memory of the eSIM chip; and after deleting the selected profile file, initiating the downloading flow of the target profile file again. In the above scheme, when the terminal device determines that the residual memory of the eSIM chip is smaller than the target profile file size, the SM-dp+ server is prevented from setting the profile state as an error by initiating a download flow cancellation instruction to the eSIM chip. In addition, the terminal equipment also receives the deleting operation of the user on the selected profile file, and deletes the selected profile file, so that the problem that the SM-DP+ server can continuously download the profile file only by re-contacting the operator to reset the state of the profile file after setting the state of the profile file as an error due to insufficient memory of an eSIM chip is avoided.

In an embodiment of the present application, the receiving the target profile file metadata sent by the SM-dp+ server includes: and calling an ES < 8+ > storage metadata instruction through a first interface (ES < 8+ >) to acquire the metadata of the target profile file, and determining the size of the target profile file. In the above technical solution, the terminal device invokes ES8+. Store metadata instruction through the first interface to obtain the metadata of the target profile file, and determines the size of the target profile file from the metadata of the target profile file.

In an embodiment of the present application, the determining the remaining memory of the eSIM chip includes: and sending a request for acquiring the residual memory of the eSIM chip to the eSIM chip, and receiving the residual memory of the eSIM chip sent by the eSIM chip. In the above technical solution, the terminal device obtains the residual memory of the eSIM chip returned by the eSIM chip by sending a request for obtaining the residual memory to the eSIM chip.

In an embodiment of the present application, the sending the request for obtaining the remaining memory of the eSIM chip to the SIM chip, and receiving the remaining memory of the eSIM chip sent by the eSIM chip includes: and calling an ES10b.GetEUICCInfo instruction through a second interface (ES 10 b), sending a request for acquiring the residual memory of the eSIM chip to the eSIM chip, and receiving the residual memory of the eSIM chip through the second interface. In the above technical solution, the request for acquiring the residual memory of the eSIM chip is sent to the eSIM chip by calling the esi10b.geteuiccinfo instruction through the second interface, and the residual memory of the eSIM chip returned by the eSIM chip is received through the second interface.

In an embodiment of the present application, the canceling the downloading procedure of the target profile file includes: and calling an ES10b.CancelSession instruction through a second interface (ES 10 b), and canceling the downloading flow of the target profile file. In the above technical solution, the ES10b.CancelSession instruction is called through the second interface to initiate the download procedure cancel instruction to the eSIM chip, so that the SM-DP+ server is prevented from setting the profile state as an error.

In an embodiment of the present application, after deleting the selected profile file, the downloading process of the target profile file is initiated again, including: and calling an ES10c.DeleteProfile instruction through a third interface (ES 10 c), and deleting the profile file selected by the user. In the above technical solution, the terminal device invokes the ES10c.DeleteProfile instruction through the third interface to automatically clean the profile file selected by the user, thereby releasing the storage space of the eSIM chip.

In an embodiment of the present application, the outputting the prompt information includes: and displaying the prompt information through a popup window.

In an embodiment of the present application, the obtaining the address and the password of the SM-dp+ server includes: and receiving the address of the SM-DP+ server and the password input by a user through a file downloading setting interface. In the technical scheme, the address and the password of the SM-DP+ server are received through the file downloading setting interface so as to start downloading the target profile file.

In an embodiment of the present application, the obtaining the address and the password of the SM-dp+ server includes: and acquiring the address of the SM-DP+ server and the password by scanning the two-dimensional code. In the technical scheme, the address and the password of the SM-DP+ server are obtained by scanning the two-dimensional code, so that the downloading of the target profile file is started conveniently.

In an embodiment of the present application, after receiving the target profile file metadata sent by the SM-dp+ server, the method further includes: and judging whether the target profile file metadata comprises a limiting condition, wherein the limiting condition comprises at least one of the incapable of supporting activation and incapable of supporting deletion.

In an embodiment of the present application, after the sending the request for obtaining the remaining memory of the eSIM chip to the eSIM chip and receiving the remaining memory of the eSIM chip sent by the eSIM chip, the method further includes: and sending a request for acquiring a profile file list to the eSIM chip, and receiving the profile file list sent by the eSIM chip.

In an embodiment of the present application, the sending a request to the eSIM chip to obtain a profile file list includes: and calling ES10b.GetProfileInfo instructions through a second interface (ES 10 b) to send a request for acquiring a profile file list to the eSIM chip. In the above technical solution, the request for obtaining the profile file list is sent to the eSIM chip by calling the ES10b.getprofileinfo instruction through the second interface.

In an embodiment of the present application, if the remaining memory of the eSIM chip is smaller than the size of the target profile file, canceling the downloading procedure of the target profile file includes: judging whether the target profile file is in the profile file list or not; and if the target profile file is in the profile file list and the residual memory of the eSIM chip is smaller than the size of the target profile file, canceling the downloading flow 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 smaller than the size of the target profile file, the downloading process of the target profile file is canceled, so that the SM-dp+ server is prevented from setting the status of the profile as an error.

In a second aspect, some embodiments of the present application provide an electronic device comprising a memory and a processor: wherein the memory is used for storing program instructions; and the processor is used for reading and executing the program instructions stored in the memory, and when the program instructions are executed by the processor, the electronic equipment is caused to execute the profile file downloading management method.

In a third aspect, some embodiments of the present application provide a computer storage medium storing program instructions that, when executed on an electronic device, cause the electronic device to perform the profile file download management method described above.

In addition, the technical effects of the second aspect to the third aspect may be referred to in the description related to the method designed in the method section above, and will not be repeated here.

Drawings

Fig. 1a is a schematic diagram of a SIM card setting interface according to an embodiment of the present application.

FIG. 1b is a diagram illustrating a download setup interface according to an embodiment of the present application.

FIG. 1c is a diagram illustrating a download display interface according to an embodiment of the application.

Fig. 1d is a schematic diagram of a SIM card setting interface according to another embodiment of the present application.

Fig. 1e is a schematic diagram of a download setup interface according to another embodiment of the present application.

Fig. 2 is a schematic architecture diagram of a profile file download management system according to an embodiment of the application.

Fig. 3 is a flowchart of a profile file download management method according to an embodiment of the present application.

Fig. 4 is a flow chart of bi-directional authentication between the LPAd and the SM-dp+ server according to one embodiment of the present application.

Fig. 5 is a flowchart of a profile file download management method according to another embodiment of the present application.

Fig. 6 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the application.

Detailed Description

The terms "first" and "second" are used below for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In describing some embodiments of the application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "e.g." in some embodiments of the present application should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. It is to be understood that, unless otherwise indicated, a "/" means or. For example, A/B may represent A or B. The "and/or" in some embodiments of the present application is merely one association relationship describing the associated object, meaning that three relationships may exist. For example, a and/or B may represent: a exists alone, A and B exist simultaneously, and B exists alone. "at least one" means one or more. "plurality" means two or more than two. For example, at least one of a, b or c may represent: seven cases of a, b, c, a and b, a and c, b and c, a, b and c.

For ease of understanding, some terms will be briefly described first:

a subscriber identity module (subscriber identification module, SIM) card may include: a common pluggable SIM card, an embedded universal integrated circuit card (embedded universal integrated circuit card, eUICC), may also be referred to as eSIM (embedded SIM), an integrated universal integrated circuit card (integrated universal integrated circuit card, eUICC). The hardware circuit of the terminal carrying the SIM card is provided with an SIM card slot and a circuit structure thereof, the SIM card slot is inserted with the SIM card, the hardware circuit can electrify the card, the SIM card contains card files and authentication information of the network-filling call, and after the electrifying is successful, the SIM card is identified, and the machine-card interaction at the protocol side is carried out. The common pluggable SIM card needs to realize the replacement of the code number resource by replacing the SIM card. The eSIM, uicc can download from the mobile network operator the Profile needed for connecting to the operator network. The eSIM is an eSIM chip integrating a card slot and a real card, wherein the eSIM chip is welded on baseband hardware, and card files and authentication parameters related to network injection communication are required to be written in the eSIM chip in a profile file downloading mode.

The common pluggable SIM card is a smart card mainly used for storing user identification data, short message data and telephone numbers, and is a SIM card conforming to the standards of the european telecommunications standards institute (European telecommunications standards institute, ETSI) and international organization for standardization (international organization for standardization, ISO) -7816. Generally, a user purchases a SIM card at a communication carrier, burns fixed SIM data when leaving the factory, and has the right to use communication services provided by the carrier after placing the SIM card in a terminal, so that the SIM card and code number changing resources can be replaced by plugging and unplugging. The hardware packaging structure and corresponding pins of the SIM card follow the ISO 7816 protocol, and the 3GPP (3 rd Generation Partnership Project, third generation partnership project) protocol between the terminal and the SIM card communicates.

The eUICC may also be called an eSIM, which is a secure element that can be used by multiple carriers to remotely manage subscribers, and the eSIM is welded in a baseband hardware circuit and is not pluggable.

The uicc refers to a universal integrated circuit card (uicc) secured to a terminal and used that is capable of remotely downloading and selecting sim modules.

The local configuration agent (local Profile assistant, LPA) can be used for Profile file download management, service discovery, providing a user interface UI (e.g., a Profile file installation list) for a user, etc., so that the user can manage Profile files local to the eSIM (e.g., activate, deactivate, delete download, unlock, etc. Profile). In addition, the terminal device may also retrieve the eUICC identification (eUICC identification, EID) and/or the integrated circuit card identification (integrated circuit card ID, ICCID) via the LPA module. The LPA module is a virtual logic module, which includes a local discovery service (local discoveryservice, LDS), a local profile download (local Profile download, LPD), and a local user interface UI interface (local user interface, LUI). The LPA in the end device and eSIM can consist of any one or more of an LDS, LPD, and LUI.

The service provider may be some basic operator, for example: operators such as China Mobile, china Unicom, and the like; a certain terminal manufacturer can also be used as a service provider; a certain card merchant can also be used as a service provider; it may be that a certain enterprise serves as a service provider, or that a certain virtual operator serves as a service provider, etc. The service provider server is a server deployed by a service provider for providing wireless communication services, such as a mobile network operator (mobile network operator, MNO) server, a service platform server provided by a terminal manufacturer for its branded terminals, or a service platform server provided by an enterprise for its enterprise users, etc.

Generally, when the memory of the eSIM card is insufficient, if the terminal downloads a new profile file, the new profile file may be reported as being wrong due to the insufficient memory. The subscription management data preparation (Subscription Manager Data Preparation +, SM-dp+) server sets the status of the profile file with failed download as 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, the user needs to contact the operator to reset the status of the profile file to the downloadable status before the profile file can be downloaded successfully, thereby causing inconvenience in downloading the profile file by the user.

Referring to fig. 1a, an interface is provided for a SIM card displayed on a terminal apparatus. The user clicks the "add eSIM (Add eSIM)" option on the SIM card settings interface of the terminal device, and enters the file download settings interface (see fig. 1 b). The file download setting interface comprises an address field and a password field. The address field is used for receiving an address of the SM-DP+ server input by a user. The password field is used for receiving an activation code input by a user. Referring to fig. 1b, the address of the SM-dp+ server input by the user in the address field may be "testsmdpplus1.Example. Com", and the activation password input in the password field may be "2315". After inputting the address and the activation code of the SM-dp+ server, the user clicks the "NEXT" option, performs downloading of the Profile file, and enters the download display interface. Referring to fig. 1c, the download display interface is used to display the download result. Because the eSIM chip does not have enough storage space for downloading the new Profile file, the download display interface displays prompt information to remind the user that the Profile file is not downloaded, and the SM-dp+ server sets the status of the Profile file to error. In an embodiment of the present application, the hint information may be that the eSIM chip does not have enough memory for downloading the Profile file, and the Profile file is downloaded again after deleting other Profile files (Insufficient storage on eSIM chip. Delete an eSIM and try again).

If the user selects the Profile file to be deleted on the SIM card setting interface shown in fig. 1d and clicks the "disable" option, the selected Profile file is deleted to release the memory space of the eSIM chip. The user clicks the "new eSIM" option on the SIM card setting interface of the terminal and then enters the file download setting interface (refer to fig. 1 b). And the user clicks a next option to download the Profile file after inputting the address and the activation code of the SM-DP+ server in the file download setting interface. At this time, although the user has manually deleted the profile file so that the memory space of the eSIM chip can meet the downloading requirement, when the profile file is downloaded again, an error reporting message is displayed on the file downloading setting interface (refer to fig. 1 e), so as to remind the user that the profile file is unavailable, and the operator needs to be contacted to reset the state of the profile to be in a downloadable state, which causes inconvenience to the operation of the user. For example, the error message may be "eSIM profile has been used or invalid, please contact your operator to get detailed information (The eSIM profile is already in used or is invalid your carrier for details)".

In order to solve the technical problems, the embodiment of the application provides a profile file downloading management method, which can solve the problem that a user can continuously download profile files only by re-contacting an operator to reset a profile state when the memory of an eSIM chip is insufficient. In order to facilitate description of the profile file download management method, the profile file download management system will be described first. Fig. 2 is a schematic view of an application scenario of a profile file download management system according to an embodiment of the present application. As shown in fig. 2, 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 helper device (Local Profile Assistant (LPA) when LPA is in the device, LPAd) 41 and an eSIM chip 42. The LPAd 41 is configured to obtain an address and a password of the SM-dp+ server, and establish a communication connection with the SM-dp+ server 30 according to the address and the password of the SM-dp+ server.

After the communication connection is established, the SM-dp+ server transmits profile file Metadata (profile Metadata) including the profile file size to the LPAd 41. The LPAd 41 obtains profile metadata by calling an ES8+ StoreMetadata instruction through a first interface (ES 8+), and determines a profile file size. The LPAd 41 invokes an esi10b.geteuiccinfo instruction over a second interface (ES 10 b) to fetch the memory of the eSIM chip 42. The LPAd 41 compares the memory of the eSIM chip 42 with the profile file size, and if the memory of the eSIM chip 42 is smaller than the profile file size, invokes an eSIM 10b.cancelsession instruction via the second interface to initiate a download procedure cancellation instruction to the eSIM chip 42 and the SM-dp+ server 30, so as to avoid the SM-dp+ server 30 setting the state of the profile as error. The LPAd 41 calls the esim.deleteprofile command through the third interface (ES 10 c) to clean the profile file in the eSIM chip 42 for the user, so that the problem that the user needs to re-contact the operator to reset the profile state after the SM-dp+ server 30 sets the state of the profile file to error due to insufficient memory of the eSIM chip 42 to continuously download the profile file is avoided.

In an embodiment of the present application, the terminal 40 may be one of the following devices: a cell phone, tablet, desktop, laptop, handheld, notebook, ultra mobile personal computer (ultra-mobile personal computer, UMPC), netbook, and cellular telephone, personal digital assistant (personal digital assistant, PDA), augmented reality (augmented reality, AR) device, virtual Reality (VR) device, artificial intelligence (artificial intelligence, AI) device, wearable device, vehicle-mounted device, smart home device, and/or smart city device. The embodiment of the present application is not particularly limited with respect to the specific type of the terminal 40.

The above description should not be construed as limiting the architecture diagram of the profile file download management system 10 according to the embodiment of the present application, but the architecture of the profile file download management system 10 according to the embodiment of the present application includes, but is not limited to, the architecture shown in fig. 2.

The profile file downloading management method provided by the application can be applied to the profile file downloading management system 10. The following will describe a signal interaction process between the respective devices in the profile file download management system 10 in conjunction with the flowchart shown in fig. 3, so as to implement download management of the profile file at the terminal 40.

Referring to fig. 3, a flowchart of a profile file download management method according to an embodiment of the present application specifically includes the following steps.

In step S31, the LPAd 41 obtains the address and the 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 in the process of downloading the target Profile file.

In an embodiment of the present application, the LPAd 41 receives the address and password of the SM-dp+ server input by the user through the file download setup interface (refer to fig. 1 b). For example, the LPAd 41 receives the address of the SM-dp+ server 30 input by the user in the address field of the file setting interface, and receives the AC code and the CC code input by the user in the password field.

In another embodiment of the present application, the LPAd 41 can also obtain the address and password of the SM-dp+ server 30 by scanning two-dimensional codes.

In step S32, the LPAd 41 performs bidirectional authentication with the SM-dp+ server 30 and performs communication connection after the bidirectional authentication.

Referring to fig. 4, a flow chart of the bidirectional authentication between the LPAd 41 and the SM-dp+ server 30 according to an embodiment of the present application is shown, which includes the following steps.

In step S321, the LPAd 41 obtains a support list of Certificate Issuer (CI) public keys and a random number from the eSIM chip 42 (i.e., eUICC) and sends them to the SM-dp+ server 30.

In step S322, the SM-dp+ server 30 selects the supported CI public key to generate the SM-dp+ server certificate, and sends the information signed by the SM-dp+ server certificate and the SM-dp+ server private key to the LPAd 41.

In step S323, the LPAd 41 sends the information signed by the SM-dp+ server certificate and the SM-dp+ server private key to the eSIM chip 42.

In step S324, the eSIM chip 42 completes the first authentication, and sends the EUM certificate and the eUICC certificate to the LPAd 41 after confirming the validity of the SM-dp+ server certificate.

In step S325, the LPAd 41 sends the EUM certificate to the SM-dp+ server 30.

In step S326, the SM-dp+ server 30 completes the secondary authentication, confirming the EUM certificate and eUICC certificate validity.

In step S33, the SM-dp+ server 30 searches for the target profile file.

In step S34, the SM-dp+ server 30 processes the download progress information of the target profile file.

In an embodiment of the present application, the SM-dp+ server 30 instructs the process of downloading progress information of the target profile file from the carrier server 20 through the fourth interface (es2+) call es2+) Handle downloadprogressinfo.

Step S35, creating the target profile Metadata (profile Metadata).

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.

In step S36, the SM-dp+ server 30 transmits the target profile file metadata to the LPAd 41.

In one embodiment of the present application, LPAd 41 obtains profile file metadata by calling ES8+ store metadata instruction through the first interface (ES 8+) and determines the target profile file size.

In step S37, the LPAd 41 determines whether the target profile file metadata includes a limiting condition.

In an embodiment of the application, the defined condition includes at least one of an inability to support activation and an inability to support deletion. In an embodiment of the present application, the limiting condition is not determined in the downloading process of the profile file, but is used to limit the operation of the user when the user deactivates or deletes the profile file when the user uses the scene after the profile file is downloaded successfully. In an embodiment of the present application, step S38 is performed when it is determined that the target profile file metadata includes a constraint. In another embodiment of the present application, step S37 may be omitted.

In step S38, the LPAd 41 sends a request to the eSIM chip 42 to acquire the remaining memory of the eSIM chip 42.

In one embodiment of the application, the LPAd 41 sends a request to the eSIM chip 42 to obtain the remaining memory size of the eSIM chip 42 by invoking an ES10b.GetEUICCInfo instruction through the second interface (ES 10 b).

In step S39, the eSIM chip 42 sends information of the remaining memory size of the eSIM chip 42 to the LPAd 41.

In step S40, the LPAd 41 sends a request to the eSIM chip 42 to acquire a rule authorization table (Rules Authorisation Table, RAT).

In one embodiment of the application, the LPAd 41 sends a request to acquire a RAT to the eSIM chip 42 by invoking an ES10b.getbat instruction through a second interface (ES 10 b). In an embodiment of the application, the RAT is used to check corresponding grants, including checking grants of inter-merchant admission for the card, the operator and the terminal device. In an embodiment of the application, if the terminal does not support a certain feature, such as PPR, the download will be misplaced even in the authorization table of the respective operator and card vendor.

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

In step S42, the LPAd 41 sends a request to acquire a profile file list to the eSIM chip 42.

In one embodiment of the application, the LPAd 41 sends a request to the eSIM chip 42 to retrieve a list of profile files by invoking an ES10 b.getprofileinfo instruction through a second interface (ES 10 b).

In step S43, the eSIM chip 42 sends the profile file list to the LPAd 41.

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

In an embodiment of the present application, the LPAd 41 determines whether the remaining memory of the eSIM chip 42 is smaller than the target profile file size, and if the remaining memory of the eSIM chip 42 is smaller 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, the LPAd 41 sends an indication to the SIM chip 42 to indicate that the target Profile file is to be re-downloaded.

Step S45: the LPAd 41 initiates a download flow cancellation instruction to the eSIM chip 42.

In an embodiment of the present application, the LPAd 41 invokes an es10b.cancelsession instruction through the second interface (ES 10 b) to initiate a download procedure cancel instruction to the eSIM chip 42 and the SM-dp+ server 30, avoiding the SM-dp+ server 30 from setting the state of the target profile file to error (error).

Step S46: the LPAd 41 sends out prompt information to remind the user to clean the memory of the eSIM chip.

In one embodiment of the present application, the LPAd 41 displays a prompt message through a pop-up window. The prompt message may be that the memory of the eSIM chip is insufficient, and the unused profile file is clicked and cleaned.

Step S47: the LPAd 41 receives the deleting operation of the user on the selected profile file, and deletes the selected profile file.

In an embodiment of the present application, the LPAd 41 automatically clears the profile file of the eSIM chip 42 selected by the user by invoking the esim.deleteprofile instruction through the second interface.

Step S48, sending indication information to the SIM chip 42 to indicate that the target Profile file is re-downloaded.

Step S49, judging whether the limitation condition of the target Profile file meets the RAT. If the constraint condition of the target Profile file meets the RAT, executing step S51; if the constraint condition of the target Profile file does not meet the RAT, step S50 is executed.

And S50, refusing the downloading of the target Profile file.

And S51, downloading the target Profile file.

In an embodiment of the present application, the target profile file metadata further includes preset terminal capability information. After step S36, the method further comprises: after receiving the target profile file metadata sent by the SM-DP+ server 30, the LPAd 41 acquires preset terminal capability information from the target profile file metadata; acquiring terminal capability information of the terminal 40; judging whether the terminal capability information of the terminal 40 is matched with the preset terminal capability information; if the terminal capability information of the terminal 40 is not matched with the preset terminal capability information, step S50 is performed, and if the terminal capability information of the terminal 40 is matched with the preset terminal capability information, step S38 is performed.

The LPAd 41 compares the residual memory of the eSIM chip 42 with the profile file size, and if the residual memory of the eSIM chip 42 is smaller than the profile file size, invokes an eSIM 10b.cancelsession instruction to initiate a download procedure cancel instruction to the eSIM chip 42 and the SM-dp+ server 30 through the second interface, so as to avoid the SM-dp+ server 30 setting the state of the profile as error. The LPAd 41 automatically clears the profile file selected by the user in the eSIM chip 42 for the user by calling the esa10c.deleteprofile command through the third interface (ES 10 c), so that the problem that the user needs to re-contact the operator to reset the profile state to continuously download the profile file after the SM-dp+ server 30 sets the state of the profile file to error due to insufficient memory of the eSIM chip 42 is avoided.

Referring to fig. 5, a flowchart of a profile file download management method according to another embodiment of the present application is shown. The method is applied to the LPAd 41, and specifically comprises the following steps.

In step S61, the LPAd 41 obtains the address and the password of the SM-dp+ server to download the target Profile file, wherein the password includes the AC code and the CC code that need to be verified in the process of downloading the target Profile file.

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 management data preparation (subscription manager data preparation, SM-DP) server, wherein the SM-DP server includes the SM-dp+ server 30.

Step S62, the LPAd 41 performs bidirectional authentication with the SM-DP+ server, and performs communication connection after the bidirectional authentication.

In step S63, the LPAd 41 receives the target profile file metadata sent by the SM-dp+ server, where the target profile file metadata includes a target profile file size.

In one embodiment of the present application, the LPAd 41 obtains the target profile file metadata by calling ES8+ store metadata instruction through the first interface (ES 8+), and determines the target profile file size.

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

In one embodiment of the application, the LPAd 41 determining the remaining memory of the eSIM chip comprises: the LPAd 41 sends a request to the eSIM chip 42 to acquire the remaining memory of the eSIM chip 42 and receives the remaining memory of the eSIM chip 42 sent by the eSIM chip 42.

In one embodiment of the present application, the LPAd 41 invokes an esi10b.geteuiccinfo instruction to send a request to the eSIM chip 42 to obtain the remaining memory of the eSIM chip 42 through the second interface (ES 10 b), and receives the size of the remaining memory of the eSIM chip 42 sent by the eSIM chip 42 through the second interface.

In step S65, the LPAd 41 initiates a download procedure cancel instruction to the eSIM chip 42 when it is determined that the remaining memory of the eSIM chip 42 is smaller than the target profile file size.

In an embodiment of the present application, the LPAd 41 invokes an esa10b.cancelsession instruction through the second interface (ES 10 b) to initiate a download procedure cancel instruction to the eSIM chip 42 and the SM-dp+ server 30, avoiding the SM-dp+ server 30 from setting the state of the target profile file to error.

Step S66: the LPAd 41 sends out prompt information, which is used for reminding a user to clean the memory of the eSIM chip.

Step S67: the LPAd 41 receives the deleting operation of the user on the selected profile file, deletes the selected profile file, and initiates the downloading flow of the target profile file again after deleting the selected profile file.

In one embodiment of the present application, the LPAd 41 automatically clears the profile file of the eSIM chip 42 selected by the user by invoking an es10c.deleteprofile instruction through the third interface (ES 10 c).

Referring to fig. 6, a hardware structure of an electronic device 100 according to an embodiment of the application is shown. The electronic device 100 comprises a terminal 40.

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge 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, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It should be understood that the illustrated structure of the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the application, electronic device 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

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

The I2C interface is a bi-directional synchronous serial bus comprising a serial data line (SDA) and a serial clock line (derail clock line, SCL). In some embodiments, the processor 110 may contain multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, charger, flash, camera 193, etc., respectively, through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through an I2C interface, such that the processor 110 communicates with the touch sensor 180K through an I2C bus interface to implement a touch function of the electronic device 100.

The I2S interface may be used for audio communication. In some embodiments, the processor 110 may contain multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through the I2S interface, to implement a function of answering a call through the bluetooth headset.

PCM interfaces may also be used for audio communication to sample, quantize and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface to implement a function of answering a call through the bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus for asynchronous communications. The bus may be a bi-directional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is typically used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through a UART interface, to implement a function of playing music through a bluetooth headset.

The MIPI interface may be used to connect the processor 110 to peripheral devices such as a display 194, a camera 193, and the like. The MIPI interfaces include camera serial interfaces (camera serial interface, CSI), display serial interfaces (display serial interface, DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the photographing functions of electronic device 100. The processor 110 and the display 194 communicate via a DSI interface to implement the display functionality of the electronic device 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal or as a data signal. In some embodiments, a GPIO interface may 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, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, an MIPI interface, etc.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transfer data between the electronic device 100 and a peripheral device. And can also be used for connecting with a headset, and playing audio through the headset. The interface may also be used to connect other electronic devices 100, such as AR devices, etc.

It should be understood that the interfacing relationship between the modules illustrated in the embodiments of the present application is only illustrative, and is not meant to limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also employ different interfacing manners in the above embodiments, or a combination of multiple interfacing manners.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130. In some wireless charging embodiments, the charge management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device 100 through the power management module 141 while charging the battery 142.

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating 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. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc., as applied to the electronic device 100. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

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

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

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (flex), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The electronic device 100 may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. ISP can also optimize the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred 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 the like format. In some embodiments, electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent awareness of the electronic device 100 may be implemented through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

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

The random access memory may include a static random-access memory (SRAM), a dynamic random-access memory (dynamic random access memory, DRAM), a synchronous dynamic random-access memory (synchronous dynamic random access memory, SDRAM), a double data rate synchronous dynamic random-access memory (double data rate synchronous dynamic random access memory, DDR SDRAM, such as fifth generation DDR SDRAM is commonly referred to as DDR5 SDRAM), etc.;

the nonvolatile memory may include a disk storage device, a flash memory (flash memory).

The FLASH memory may include NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. divided according to an operation principle, may include single-level memory cells (SLC), multi-level memory cells (MLC), triple-level memory cells (TLC), quad-level memory cells (QLC), etc. divided according to a storage specification, may include universal FLASH memory (english: universal FLASH storage, UFS), embedded multimedia memory cards (embedded multi media Card, eMMC), etc. divided according to a storage specification.

The random access memory may be read directly from and written to by the processor 110, may be used to store executable programs (e.g., machine instructions) for an operating system or other on-the-fly programs, may also be used to store data for users and applications, and the like.

The nonvolatile memory may store executable programs, store data of users and applications, and the like, and may be loaded into the random access memory in advance for the processor 110 to directly read and write.

The external memory interface 120 may be used to connect external non-volatile memory to enable expansion of the memory capabilities of the electronic device 100. The external nonvolatile 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 video are stored in an external nonvolatile memory.

The internal memory 121 or the external memory interface 120 is used to store one or more computer programs. One or more computer programs are configured to be executed by the processor 110. The one or more computer programs include a plurality of instructions that, when executed by the processor 110, implement the profile file download management method executed on the electronic device 100 in the above embodiment to implement the profile file download management function of the electronic device 100.

The electronic device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The electronic device 100 may listen to music, or to hands-free conversations, through the speaker 170A.

A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When electronic device 100 is answering a telephone call or voice message, voice may be received by placing receiver 170B in close proximity to the human ear.

Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C, and may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may also be provided with three, four, or more microphones 170C to enable collection of sound signals, noise reduction, identification of sound sources, directional recording functions, etc.

The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be a USB interface 130 or a 3.5mm open mobile electronic device 100 platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 may also calculate the location of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example: and executing an instruction for checking the short message when the touch operation with the touch operation intensity smaller than the first pressure threshold acts on the short message application icon. And executing an instruction for newly creating the short message when the touch operation with the touch operation intensity being greater than or equal to the first pressure threshold acts on the short message application icon.

The gyro sensor 180B may be used to determine a motion gesture of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., x, y, and z axes) may be determined by gyro sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects the shake angle of the electronic device 100, calculates the distance to be compensated by the lens module according to the angle, and makes the lens counteract the shake of the electronic device 100 through the reverse motion, so as to realize anti-shake. The gyro sensor 180B may also be used for navigating, somatosensory game scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude from barometric pressure values measured by barometric pressure sensor 180C, aiding in positioning and navigation. The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip cover using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip machine, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the detected opening and closing state of the leather sheath or the opening and closing state of the flip, the characteristics of automatic unlocking of the flip and the like are set. The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the electronic device 100 is stationary. The method can also be used for identifying the gesture of the electronic equipment 100, and can be applied to applications such as horizontal and vertical screen switching, pedometers and the like. A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, the electronic device 100 may range using the distance sensor 180F to achieve quick focus.

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 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it may be determined that there is an object in the vicinity of the electronic device 100. When insufficient reflected light is detected, the electronic device 100 may determine that there is no object in the vicinity of the electronic device 100. The electronic device 100 can detect that the user holds the electronic device 100 close to the ear by using the proximity light sensor 180G, so as to automatically extinguish the screen for the purpose of saving power. The proximity light sensor 180G may also be used in holster mode, pocket mode to automatically unlock and lock the screen.

The ambient light sensor 180L is used to sense ambient light level. The electronic device 100 may adaptively adjust the brightness of the display 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust white balance when taking a photograph. Ambient light sensor 180L may also cooperate with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent false touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 may utilize the collected fingerprint feature to unlock the fingerprint, access the application lock, photograph the fingerprint, answer the incoming call, etc.

The temperature sensor 180J is for detecting temperature. In some embodiments, the electronic device 100 performs a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 performs a reduction in the performance of a processor located in the vicinity of temperature sensor 180J in order to reduce power consumption to implement thermal protection. In other embodiments, when the temperature is below another threshold, the electronic device 100 heats the battery 142 to avoid the low temperature causing the electronic device 100 to be abnormally shut down. In other embodiments, when the temperature is below a further threshold, the electronic device 100 performs boosting of the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperatures.

The touch sensor 180K, also referred to as a "touch device". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a different location than the display 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, bone conduction sensor 180M may acquire a vibration signal of a human vocal tract vibrating bone pieces. The bone conduction sensor 180M may also contact the pulse of the human body to receive the blood pressure pulsation signal. In some embodiments, bone conduction sensor 180M may also be provided in a headset, in combination with an osteoinductive headset. The audio module 170 may analyze the voice signal based on the vibration signal of the sound portion vibration bone block obtained by the bone conduction sensor 180M, so as to implement a voice function. The application processor may analyze the heart rate information based on the blood pressure beat signal acquired by the bone conduction sensor 180M, so as to implement a heart rate detection function.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects by touching different areas of the display screen 194. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be inserted into the SIM card interface 195, or removed from the SIM card interface 195 to enable contact and separation with the electronic device 100. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support Nano SIM cards, micro SIM cards, and the like. The same SIM card interface 195 may be used to insert multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, i.e.: an embedded SIM card. eSIM cards can be embedded in the electronic device 100.

The present embodiment also provides a computer program product, which when run on a computer, causes the computer to perform the above-mentioned related steps to implement the profile file download management method in the above-mentioned embodiment.

In addition, some embodiments of the present application provide an apparatus, which may be embodied as a chip, component or module, which may include a processor and a memory coupled to each other; the memory is used for storing computer executing instructions, and when the device runs, the processor can execute the computer executing instructions stored in the memory, so that the chip executes the profile file downloading management method in each method embodiment.

The electronic device, the computer storage medium, the computer program product, or the chip provided in this embodiment are used to execute the corresponding methods provided above, so that the beneficial effects thereof can be referred to the beneficial effects in the corresponding methods provided above, and will not be described herein.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and the parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated unit may be stored in a readable storage medium if implemented in the form of a software functional unit and sold or used as a stand-alone product. Based on such understanding, the technical solutions of some embodiments of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solutions in the form of a software product stored in a storage medium, including several instructions to cause a device (which may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Finally, it should be noted that the above-mentioned embodiments are merely for illustrating the technical solutions of some embodiments of the present application, and not for limiting, and although some embodiments of the present application have been described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications or equivalent substitutions can be made to the technical solutions of some embodiments of the present application 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, wherein the terminal device comprises an eSIM chip, the method comprising:

acquiring an address and a password of an SM-DP+ server, wherein the password comprises an Activation Code (AC) and a confirmation Code (Confirmation Code, CC) which need to be verified in the process of downloading a target profile file;

carrying out bidirectional authentication with the SM-DP+ server, and establishing communication connection after the bidirectional authentication is passed;

receiving target profile file metadata sent by the SM-DP+ server, wherein the target profile file metadata comprises the size of the target profile file;

determining the residual memory of the eSIM chip;

if the residual memory of the eSIM chip is smaller than the size of the target profile file, canceling the downloading flow of the target profile file;

outputting prompt information to remind a user to clean the memory of the eSIM chip;

and after deleting the selected profile file, initiating the downloading flow of the target profile file again.

2. The profile file download management method as claimed in claim 1, wherein said receiving the target profile file metadata transmitted by the SM-dp+ server comprises:

And calling an ES < 8+ > storage metadata instruction through a first interface (ES < 8+ >) to acquire the metadata of the target profile file, and determining the size of the target profile file.

3. The profile file download management method as in claim 1, wherein the determining the remaining memory of the eSIM chip comprises: and sending a request for acquiring the residual memory of the eSIM chip to the eSIM chip, and receiving the residual memory of the eSIM chip sent by the eSIM chip.

4. The profile file download management method as in claim 3, wherein 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 comprises:

and calling an ES10b.GetEUICCInfo instruction through a second interface (ES 10 b), sending a request for acquiring the residual memory of the eSIM chip to the eSIM chip, and receiving the residual memory of the eSIM chip through the second interface.

5. The profile file download management method as in claim 1, wherein said canceling the download flow of the target profile file comprises:

and calling an ES10b.CancelSession instruction through a second interface (ES 10 b), and canceling the downloading flow of the target profile file.

6. The method for managing downloading of profile files according to claim 1, wherein the step of restarting the downloading process of the target profile file after deleting the selected profile file comprises the steps of:

and calling an ES10c.DeleteProfile instruction through a third interface (ES 10 c), and deleting the profile file selected by the user.

7. The profile file download management method as claimed in claim 1, wherein the outputting the hint information includes:

and displaying the prompt information through a popup window.

8. The profile file download management method as claimed in claim 1, wherein the obtaining the address and password of the SM-dp+ server comprises:

and receiving the address of the SM-DP+ server and the password input by a user through a file downloading setting interface.

9. The profile file download management method as claimed in claim 1, wherein the obtaining the address and password of the SM-dp+ server comprises:

and acquiring the address of the SM-DP+ server and the password by scanning the two-dimensional code.

10. The profile file download management method as claimed in claim 1, wherein after said receiving the target profile file metadata transmitted by the SM-dp+ server, the method further comprises:

And judging whether the target profile file metadata comprises a limiting condition, wherein the limiting condition comprises at least one of the incapable of supporting activation and incapable of supporting deletion.

11. The profile file download management method as in claim 3, wherein after said 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 comprises:

and sending a request for acquiring a profile file list to the eSIM chip, and receiving the profile file list sent by the eSIM chip.

12. The profile file download management method as set forth in claim 11, wherein said sending a request to the eSIM chip to obtain a list of profile files comprises:

and calling ES10b.GetProfileInfo instructions through a second interface (ES 10 b) to send a request for acquiring a profile file list to the eSIM chip.

13. The profile file download management method according to claim 12, wherein if the remaining memory of the eSIM chip is smaller than the size of the target profile file, canceling the download procedure of the target profile file comprises:

Judging whether the target profile file is in the profile file list or not;

and if the target profile file is in the profile file list and the residual memory of the eSIM chip is smaller than the size of the target profile file, canceling the downloading flow of the target profile file.

14. An electronic device, the electronic device comprising a memory and a processor:

the memory is used for storing program instructions;

the processor being configured to read and execute the program instructions stored in the memory, which when executed by the processor, cause the electronic device to perform the profile file download management method according to any one of claims 1 to 13.

15. A computer storage medium storing program instructions which, when run on an electronic device, cause the electronic device to perform the profile file download management method according to any one of claims 1 to 13.