Configuration file migration method and related device

Abstract

Provided are a configuration file migration method and a related device, the method being applied to a first terminal, the method comprising: displaying at least one terminal, the at least one terminal being determined by the first terminal through device discovery; in response to an operation of a user on a second terminal in the at least one terminal, establishing a secure communication connection with the second terminal, the second terminal storing a configuration file of an eSIM to be migrated; and acquiring the configuration file from the second terminal based on the secure communication connection with the second terminal. By establishing the secure communication connection with the second terminal, the first terminal and the second terminal can directly interact, the first terminal can directly obtain the configuration file from the second terminal, participation of an operator server is not needed, the process is relatively simple, and user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a configuration file migration method and related devices. Background Art

[0002] The subscriber identification module (SIM) card is used to store data and authenticate the customer's identity. The embedded SIM (eSIM) is a traditional SIM card embedded directly into the device chip, rather than being added to the device as a separate removable component. When one or more profiles of the eSIM are activated, the user can access the network of the operator to which he belongs.

[0003] When users change devices, since eSIM cannot be migrated to the new device by plugging and unplugging, they can only continue to use the original mobile phone number by migrating the configuration file. Migrating the configuration file is essentially the process of deactivating and deleting the configuration file on the old device, and the new device re-downloading the configuration file from the operator server (such as the subscription manager-data preparation+, SM-DP+ server).

[0004] Currently, users can go to online or offline operator business outlets to apply for configuration file migration. If the operator agrees to migrate the configuration file, the operator obtains the relevant identification of the old device, completes the deactivation and deletion of the configuration file on the old device, and obtains the relevant identification of the new device, and provides the user with a new activation code so that the new device can complete the download of the configuration file from the operator server based on the above activation code. The entire migration process is relatively complicated and the user experience is poor. Summary of the invention

[0005] The present application provides a configuration file migration method and related devices, in order to reduce the complexity of the migration process and improve the user experience.

[0006] In a first aspect, the present application provides a configuration file migration method, which can be executed by a first terminal, or the method can also be executed by a component configured in the first terminal (such as a chip, a chip system, etc.), or it can also be implemented by a logic module or software that can implement all or part of the functions of the first terminal. The present application does not limit this.

[0007] Exemplarily, the method includes: displaying at least one terminal, which is determined by a first terminal through device discovery; in response to a user's operation on a second terminal among the at least one terminal, establishing a secure communication connection with the second terminal, wherein a configuration file of an eSIM to be migrated is stored in the second terminal; and based on the secure communication connection with the second terminal, obtaining the configuration file from the second terminal.

[0008] In this application, the second terminal is a terminal storing the configuration file of the eSIM to be migrated. In other words, the second terminal is the source of the configuration file to be migrated, and the first terminal is a terminal receiving the configuration file, or the first terminal is the destination of the configuration file. In other words, the configuration file is migrated from the second terminal to the first terminal.

[0009] A secure communication connection can be understood as: based on the physical layer connection with the second terminal, the first terminal and the second terminal negotiate a key to establish a secure communication connection, and the key is used to encrypt the configuration file. In other words, the configuration file obtained by the first terminal from the second terminal is encrypted with the key. In other words, the second terminal can encrypt the configuration file to obtain an encrypted configuration file, and send the encrypted configuration file to the first terminal. Correspondingly, the first terminal receives the encrypted configuration file and decrypts it to obtain a decrypted configuration file. Encrypting the configuration file is beneficial to improving security. As an example and not a limitation, the first terminal and the second terminal can pre-negotiate a symmetric key to encrypt and decrypt the configuration file based on the symmetric key. This application does not limit the specific encryption method.

[0010] The configuration file may specifically refer to an operator configuration file, which may include, for example, but is not limited to, a combination of a file system, file content, data, and applications provided on a universal integrated circuit card (UICC) (such as an eSIM), mainly carrying information such as an international mobile subscriber identification number (IMSI) and authentication parameters, and can access its corresponding mobile network after activation.

[0011] In the above technical solution, the first terminal establishes a secure communication connection with the second terminal, and the two can interact directly. The second terminal is the server and the first terminal is the client. The first terminal can directly obtain the above configuration file from the second terminal. The entire migration process does not require the participation of the operator server, and the process is relatively simple, which is conducive to improving user experience.

[0012] In combination with the first aspect, in some possible implementations of the first aspect, the obtaining a configuration file from the second terminal based on the secure communication connection with the second terminal includes: receiving management interface data of the eSIM of the second terminal based on the secure communication connection with the second terminal, the management interface data of the eSIM of the second terminal being used to generate a management interface of the eSIM of the second terminal; and obtaining the configuration file from the second terminal in response to a user's operation on the management interface of the eSIM of the second terminal.

[0013] Based on the secure communication connection with the second terminal, the first terminal can obtain the management interface data of the eSIM of the second terminal to generate a management interface, so that the user can control the second terminal to transfer the configuration file to the first terminal by operating the management interface of the eSIM of the second terminal displayed on the first terminal, that is, the first terminal obtains the configuration file from the second terminal based on the secure communication connection with the second terminal. In this way, even if the second terminal fails to power on, the screen is broken, the battery is degraded, or even fails to start, the migration of the configuration file of the eSIM on the second terminal can be completed by operating the first terminal. There are more applicable scenarios and it is more universal. Moreover, even if the second terminal fails, the migration can be completed, which is conducive to improving the user experience during the migration process.

[0014] Optionally, the above-mentioned obtaining the configuration file from the second terminal in response to the user's operation on the management interface of the eSIM of the second terminal includes: sending a request message to the second terminal in response to the user clicking on the transmission operation of the management interface of the eSIM of the second terminal, the request message being used to request the second terminal to transmit the configuration file; and receiving the configuration file from the second terminal.

[0015] Optionally, before displaying at least one terminal, the first terminal may also display a management interface of its own eSIM based on a browser.

[0016] One possible design is that, in response to a first operation, a management interface of the eSIM of the first terminal is displayed based on a browser of the first terminal, the first operation being an operation in which a user clicks on an eSIM application, and the eSIM application is used to provide security authentication and storage of personal information services.

[0017] Among them, eSIM is similar to a SIM card application, which is used to provide security authentication and storage of personal information services. The eSIM application can be, for example, a menu application in a setting menu such as cellular settings, system application settings, etc., or a third-party application, or a small program in a third-party application, which is not limited in this application. By the user clicking on the eSIM application, the first terminal can call the browser to display the management interface of the eSIM of the first terminal, that is, to display the management interface of the eSIM of this terminal. In other words, the browser can be regarded as a client at this time, and the eSIM of the first terminal can be regarded as a server. The first terminal can access (or read) the eSIM of this terminal through the browser.

[0018] Another possible design is that, in response to the second operation, a settings menu is displayed, and the second operation is an operation in which the user clicks on the settings; in response to the third operation, a cellular settings menu is displayed, and the third operation is an operation in which the user clicks on the cellular settings in the settings menu; in response to the fourth operation, the management interface of the eSIM of the first terminal is displayed based on the browser of the first terminal, and the fourth operation is an operation in which the user clicks on the migration eSIM in the cellular settings menu.

[0019] Another possible design is that, in response to the fifth operation, the management interface of the eSIM of the first terminal is displayed based on the browser of the first terminal, and the fifth operation is an operation of the user inputting the eSIM domain name address in the browser application.

[0020] In combination with the first aspect, in some possible implementations of the first aspect, the displaying of at least one terminal includes: displaying the at least one terminal in response to a user clicking a device discovery operation in a management interface of an eSIM of the first terminal.

[0021] In combination with the first aspect, in some possible implementations of the first aspect, before obtaining the configuration file from the second terminal based on the secure communication connection with the second terminal, the method further includes: displaying a verification interface, which is generated based on verification interface data from the second terminal; in response to the user inputting one or more of the following verification factors on the verification interface, sending the verification factor input by the user to the second terminal: account information registered by the user on the second terminal, a personal identification number (PIN) set by the user when registering an account on the second terminal, biometric information, or a challenge code of the second terminal.

[0022] It can be understood that before obtaining the above configuration file from the second terminal, the second terminal can authenticate the user based on the above verification factor, which is conducive to improving security. Among them, the above verification interface data can refer to the elements (such as input boxes, buttons, etc.) contained in the verification interface and the layout of each element. The first terminal can generate and display the verification interface based on the above data, so that the user can enter the verification factor in the first terminal, thereby completing the verification of the user's identity. Among them, the biometric information can be, for example, fingerprints, faces, etc., which is not limited in this application.

[0023] On the second aspect, the present application provides a configuration file migration method, which can be executed by a second terminal, or the method can also be executed by a component configured in the second terminal (such as a chip, a chip system, etc.), or it can also be implemented by a logic module or software that can realize all or part of the functions of the second terminal. The present application does not limit this.

[0024] The second terminal stores a configuration file of the eSIM to be migrated.

[0025] Exemplarily, the method includes: establishing a secure communication connection with a first terminal; based on the secure communication connection with the first terminal, receiving a request message from the first terminal, the request message being used to request a second terminal to transmit the above-mentioned configuration file; based on the secure communication connection with the first terminal, sending the above-mentioned configuration file to the first terminal.

[0026] In the above technical solution, after the second terminal receives the request message based on the secure communication connection established with the second terminal, the second terminal directly sends the configuration file of the eSIM of the second terminal to the first terminal. In other words, the first terminal and the second terminal can interact directly, wherein the second terminal is the server and the first terminal is the client. That is to say, the first terminal requests the configuration file from the server as the client, and accordingly, the second terminal returns the above configuration file to the first terminal as the server. The entire migration process does not require the participation of the operator server, and the process is relatively simple, which is conducive to improving user experience.

[0027] In combination with the second aspect, in some possible implementations of the second aspect, before receiving a request message from the first terminal based on a secure communication connection with the first terminal, the method further includes: sending management interface data of the eSIM of the second terminal to the first terminal based on the secure communication connection with the first terminal, the management interface data of the eSIM of the second terminal being used to generate a management interface of the eSIM of the second terminal, and the request message is generated in response to a user's operation on the management interface of the eSIM of the second terminal.

[0028] Based on the secure communication connection with the first terminal, the second terminal can send the management interface data of the eSIM of the second terminal to the first terminal to generate a management interface, so that the user can control the second terminal to transfer the configuration file to the first terminal by operating the management interface of the eSIM of the second terminal displayed on the first terminal. In this way, even if the second terminal fails to power on, the screen is broken, the battery is degraded, or even fails to start, the migration of the configuration file of the eSIM on the second terminal can be completed by operating the first terminal. There are more applicable scenarios and it is more universal. Moreover, even if the second terminal fails, the migration can be completed, which is conducive to improving the user experience during the migration process.

[0029] In combination with the second aspect, in some possible implementations of the second aspect, before sending the configuration file to the first terminal based on the secure communication connection with the first terminal, the method further includes: sending verification interface data to the second terminal, the verification interface data being used to generate a verification interface; receiving one or more of the following verification factors input by a user from the second terminal, and authenticating the user: account information registered by the user on the second terminal, a PIN set by the user when registering an account on the second terminal, biometric information, or a challenge code of the second terminal; and, sending the configuration file to the first terminal based on the secure communication connection with the first terminal includes: when the identity authentication of the user is successful, sending the configuration file to the first terminal based on the secure communication connection with the first terminal.

[0030] It can be understood that before sending the above configuration file to the first terminal, the second terminal can authenticate the user based on the above verification factor, which is conducive to improving security. Among them, the above verification interface data can refer to the elements contained in the verification interface (such as input boxes, buttons, etc.) and the layout of each element. The first terminal can generate and display the verification interface based on the above data for the user to enter the verification factor in the first terminal, thereby completing the verification of the user's identity. In the case of successful user identity authentication, the second terminal can send the above configuration file to the first terminal. Among them, biometric information can be, for example, fingerprints, faces, etc., which are not limited in this application.

[0031] In combination with the first aspect and the second aspect, in some possible implementations, the first terminal and the second terminal establish a secure communication connection based on any one of the following: wireless fidelity (Wi-Fi) connection, Bluetooth connection, or near field communication (NFC) connection.

[0032] A near-field connection such as a Wi-Fi connection, a Bluetooth connection, or NFC can be established between the first terminal and the second terminal. It should be understood that the above connection is only an example and should not constitute any limitation to this application. Among them, even if the second terminal fails to power on, the screen is broken, the battery is degraded, or even fails to start, the first terminal and the second terminal can establish an NFC connection, and then the first terminal directly obtains its configuration file from the second terminal.

[0033] In combination with the first aspect and the second aspect, in some possible implementations, when the first terminal and the second terminal establish a secure communication connection based on the NFC connection, the above-mentioned configuration file is carried in a data packet, and the data packet includes an application protocol data unit (application protocol data unit, APDU) header, an Internet protocol (internet protocol, IP) header, and a hypertext transfer protocol secure (hypertext transfer protocol secure, HTTPS) header from the outside to the inside; or, the data packet includes an APDU header and an HTTPS header from the outside to the inside. Among them, the HTTPS header can be replaced by a hypertext transfer protocol (hypertext transfer protocol, HTTP) header.

[0034] Among them, when the data packet does not include an IP header, the eSIM of the first terminal and the second terminal may not encapsulate the transmission control protocol (TCP) / IP protocol stack. This method can reuse the functions that the current eSIM already has, such as stripping the header of the TCP / IP data packet through the bearer independent protocol (BIP) gateway to obtain HTTP or HTTPS valid data, which is conducive to reducing costs.

[0035] In combination with the first aspect and the second aspect, in some possible implementations, when the first terminal and the second terminal establish a secure communication connection based on a Bluetooth connection, the configuration file is carried in a data packet, which includes, from the outside to the inside, a protocol data unit (PDU) header, an IP header, and an HTTPS header; or, the data packet includes, from the outside to the inside, a PDU header, an APDU header, and an HTTPS header.

[0036] In combination with the first aspect and the second aspect, in some possible implementations, when the first terminal and the second terminal establish a secure communication connection based on a Wi-Fi connection, the configuration file is carried in a data packet, and the data packet includes, from the outside to the inside, a physical layer protocol data unit (physical protocol data unit, PPDU) header, an IP header, and an HTTPS header; or, the data packet includes, from the outside to the inside, a PPDU header, an APDU header, and an HTTPS header.

[0037] In a third aspect, the present application provides a configuration file migration device, which can implement the method described in the first aspect and any possible implementation of the first aspect, or implement the method described in the second aspect and any possible implementation of the second aspect. The device includes a corresponding module for executing the above method. The module included in the device can be implemented by software and / or hardware.

[0038] In a fourth aspect, the present application provides a configuration file migration device, the device comprising a processor. The processor is coupled to a memory and can be used to execute a computer program in the memory to implement the method in the first aspect and any possible implementation of the first aspect, or to implement the method in the second aspect and any possible implementation of the second aspect.

[0039] Optionally, the device further comprises a communication interface, and the processor is coupled to the communication interface. The communication interface is used to receive a signal from other communication devices outside the device and transmit it to the processor, or send a signal from the processor to other communication devices outside the device. Exemplarily, the communication interface can be a transceiver, circuit, bus, module or other type of communication interface.

[0040] Optionally, the device further comprises a memory, and the processor is coupled to the memory. The memory is used to store program instructions and data.

[0041] In a fifth aspect, the present application provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed, it implements the method in the first aspect and any possible implementation of the first aspect, or implements the method in the second aspect and any possible implementation of the second aspect.

[0042] In a sixth aspect, the present application provides a computer program product comprising instructions, which, when executed, implement the method in the first aspect and any possible implementation of the first aspect, or implement the method in the second aspect and any possible implementation of the second aspect.

[0043] In the seventh aspect, the present application provides a chip system, which includes at least one processor for supporting the implementation of the functions involved in the above-mentioned first aspect and any possible implementation method of the first aspect, or for supporting the implementation of the functions involved in the above-mentioned second aspect and any possible implementation method of the second aspect, for example, receiving or processing the data involved in the above-mentioned method, etc.

[0044] In one possible design, the chip system also includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0045] The chip system may be composed of the chip, or may include the chip and other discrete devices.

[0046] In an eighth aspect, the present application provides a communication system, comprising a first terminal for implementing the method described in the first aspect and any possible implementation manner of the first aspect, and a second terminal for implementing the method described in the second aspect and any possible implementation manner of the second aspect.

[0047] It should be understood that the third to eighth aspects of the present application correspond to the technical solutions of the first and second aspects of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 is a schematic diagram of the hardware structure of the terminal provided in the embodiment of the present application;

[0049] Figure 2 It is a structural block diagram of software applicable to the terminal provided in the embodiment of the present application;

[0050] Figure 3 It is a flowchart of a method for migrating an existing configuration file provided in an embodiment of the present application;

[0051] Figure 4 is another flow chart of the migration method of the existing configuration files provided in the embodiment of the present application;

[0052] Figure 5 is a schematic diagram of a system architecture applicable to the method provided in the embodiment of the present application;

[0053] Figure 6 is another schematic diagram of a system architecture applicable to the method provided in an embodiment of the present application;

[0054] Figure 7 is a schematic flow chart of a configuration file migration method provided in an embodiment of the present application;

[0055] Figure 8is a schematic diagram of a management interface for entering an eSIM of a first terminal provided in an embodiment of the present application;

[0056] Fig. 9 is another schematic diagram of entering the management interface of the eSIM of the first terminal provided in an embodiment of the present application;

[0057] Fig.10 is a schematic diagram of an eSIM management interface of a first terminal provided in an embodiment of the present application;

[0058] Fig.11 It is a schematic diagram of the interface of the device discovery process provided by the embodiment of the present application;

[0059] Fig.12 is a schematic diagram of a first terminal displaying an eSIM management interface of a second terminal provided by an embodiment of the present application;

[0060] Fig.13 is a schematic diagram of an eSIM encapsulated TCP / IP protocol stack of a second terminal provided in an embodiment of the present application;

[0061] Fig.14 is a schematic diagram of an eSIM unencapsulated TCP / IP protocol stack of a second terminal provided in an embodiment of the present application;

[0062] Fig.15 It is a detailed flowchart of the configuration file migration method provided in the embodiment of the present application;

[0063] Fig.16 It is another detailed flowchart of the configuration file migration method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0064] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0065] To facilitate understanding of the embodiments of the present application, the following description is first made:

[0066] First, in this application, in order to clearly describe the technical solutions of the embodiments of this application, the words "first" and "second" are used to distinguish the same or similar items with basically the same functions and effects. For example, the first terminal and the second terminal are only used to distinguish different terminals, and their order is not limited. Those skilled in the art can understand that the words "first" and "second" do not limit the quantity and execution order, and the words "first" and "second" do not necessarily limit them to be different.

[0067] Second, in this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship, but it does not exclude the situation where the previous and next associated objects are in an "and" relationship. The specific meaning can be understood in combination with the context. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, c can be single or multiple.

[0068] Third, in the present application, "when", "assuming", "if", "under the circumstances" and "if" all mean that the device will take corresponding actions under certain objective circumstances, but do not limit the time, nor do they require that the device must have a judgment action when it is implemented, nor do they mean that there are other limitations.

[0069] Fourth, in the embodiments of the present application, the terminal may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication equipment, user agent or user device, etc., which is not limited to the embodiments of the present application.

[0070] In the embodiments of the present application, the types of terminals include, but are not limited to: mobile phones, tablet computers, computers with wireless transceiver functions (such as laptops, PDAs, etc.), mobile Internet devices (MID), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, fifth generation (5th generation) The present invention relates to terminals in the 5G generation (5G) network or terminals in the future evolved public land mobile network (PLMN), laptop computers, machine type communication (MTC) terminals, etc.

[0071] In addition, the terminal can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. IoT technology can achieve massive connections, deep coverage, and terminal power saving through narrow band (NB) technology, for example.

[0072] Figure 1 1 is a schematic diagram of the hardware structure of the terminal 100 provided in the embodiment of the present application. Figure 1 Describe in detail the possible hardware structure of the terminal.

[0073] For example, Figure 1FIG. 1 shows a schematic diagram of the structure of the terminal 100. Figure 1 As shown, the terminal 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 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.

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

[0075] The application processor outputs sound signals through the audio module 170 (such as the speaker 170A, etc.), or displays images or videos through the display screen 194.

[0076] The controller may be the nerve center and command center of the terminal 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0077] 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.

[0078] The processor 110 can perform different operations to achieve different functions by executing instructions. The instructions can be, for example, instructions pre-stored in the memory before the device leaves the factory, or instructions read from the APP after the user installs a new application (APP) during use, and the embodiments of the present application do not impose any limitation on this.

[0079] 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 secure digital input and output interface (SDIO), a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a universal synchronous asynchronous receiver / transmitter (USART), a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM interface, and / or a USB interface, etc.

[0080] The USB interface 130 is an interface that complies with the USB standard specification, and specifically 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 terminal 100, and can also be used to transmit data between the terminal 100 and peripheral devices. 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, such as AR devices, etc.

[0081] It is understandable that the interface connection relationship between the modules illustrated in the present application is only for illustrative purposes and does not constitute a structural limitation on the terminal 100. In other embodiments, the terminal 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0082] In an embodiment of the present application, a physical input (I) / output (O) interface may adopt a high-speed physical interface, such as a USB interface, an I2C interface, a serial peripheral interface (SPI), or an improved inter integrated circuit (I3C) interface, etc.; an International Organization for Standardization (IOS) input / output interface may also be adopted, and the present application does not limit this.

[0083] 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 terminal 100. While the charging management module 140 is charging the battery 142, it may also power the electronic device through the power management module 141.

[0084] 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 external memory, 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.

[0085] The wireless communication function of the terminal 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.

[0086] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of the antennas.

[0087] The mobile communication module 150 can provide wireless communication solutions including 2G / 3G / 4G / 5G etc. applied on the terminal 100 .

[0088] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN, such as Wi-Fi), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., applied on the terminal 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 filters it, 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.

[0089] In some embodiments, the antenna 1 of the terminal 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the terminal 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), fifth generation (5G) communication system, BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS may include a global positioning system (GPS), a GNSS, a BeiDou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite-based augmentation system (SBAS).

[0090] The terminal 100 can realize 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, which execute program instructions to generate or change display information.

[0091] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. It should be understood that the display screen 194 may also include more components. For example, a backlight plate, a drive circuit, etc. Among them, the backlight plate can be used to provide a light source, and the display panel emits light based on the light source provided by the backlight plate. The drive circuit can be used to control whether the liquid crystal of the liquid crystal layer is light-transmissive or light-proof.

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

[0093] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as storing music, video and other files in the external memory card.

[0094] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the terminal 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the terminal 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0095] The terminal 100 can implement audio functions such as music playing and recording through the audio module 170, such as the speaker 170A, the receiver 170B, the microphone 170C and the earphone interface 170D, and the application processor.

[0096] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or disconnected from the terminal 100 by inserting the SIM card interface 195 or pulling the SIM card out of the SIM card interface 195. The terminal 100 can support one or more SIM card interfaces. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. 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 terminal 100 interacts with the network through the SIM card to implement functions such as calls and data communications.

[0097] In the present application, the terminal 100 uses an eSIM, i.e., an embedded SIM card. An eSIM is a traditional SIM card that is directly embedded into the chip of the terminal 100, rather than being added to the terminal 100 as an independent removable component. When one or more profiles of the eSIM are activated, the user can access the network of the operator to which he belongs.

[0098] It is to be understood that the structure illustrated in the present application does not constitute a specific limitation on the terminal 100. In other embodiments, the terminal 100 may include more or fewer components than shown in the figure, or combine some components, or split 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.

[0099] In addition, the operating system of the terminal device may be an Android operating system (Android OS), a Harmony OS, an open source Harmony OS, etc. The present application embodiment does not impose any limitation on this.

[0100] Figure 2 It is a structural block diagram of the software applicable to the terminal provided in the embodiment of the present application. It can be understood that Figure 2 Taking the layered architecture of OpenHarmony as an example, the software structure of the terminal is exemplified. In this application, the type of the operating system of the terminal is not limited.

[0101] like Figure 2 As shown, in some embodiments, the operating system is divided into four layers, from top to bottom, namely, the application layer, the framework layer, the system service layer, and the kernel layer. In some embodiments, the terminal device also includes hardware, such as a GPU, a central processing unit (CPU), a display screen, etc.

[0102] The application layer can include a series of application programs. Figure 2 As shown, the application layer can include system applications and third-party applications. System applications can be understood as some applications that come with the system, such as camera, gallery (or album), calendar, call, map, Bluetooth, video and music applications. Third-party applications can be understood as non-system applications that can be downloaded and installed from the application store.

[0103] The framework layer can include user interface (UI) framework, user program framework, component framework, capability (Ability) framework, etc. The framework layer provides the operating system's application with multi-language user program framework and component framework in C, C++, JavaScript (JS) and other languages, as well as a multi-language framework (application programming interface, API) for various software and hardware services to be open to the outside world; it also provides devices with multi-language UI frameworks in C, C++, JS and other languages. The APIs supported by different devices are related to the degree of componentization and tailoring of the system.

[0104] The system service layer can include the system basic capability subsystem set, the basic software service subsystem set, the enhanced software service subsystem set and the hardware service subsystem set. The system service layer is the core capability set of the operating system, providing services for applications through the framework layer.

[0105] Among them, the system basic capability subsystem set can be composed of subsystems such as distributed soft bus and distributed data management. The system basic capability subsystem set can provide basic capabilities for the operation, scheduling, migration and other operations of distributed applications on multiple devices.

[0106] The basic software service subsystem set can be composed of subsystems such as event notification, telephone, multimedia, etc., and can provide public and general software services.

[0107] The enhanced software service subsystem set can be composed of subsystems such as smart screen proprietary services, wearable proprietary services, IoT proprietary services, etc., and can provide differentiated capability-enhanced software services for different devices.

[0108] The hardware service subsystem set can be composed of subsystems such as location services, biometric recognition, wearable proprietary hardware services, IoT proprietary hardware services, etc., which can provide hardware services.

[0109] It should be noted that, according to the deployment environment of different device forms, the basic software service subsystem set, enhanced software service subsystem set and hardware service subsystem set can be cut according to the subsystem granularity, and each subsystem can be cut according to the functional granularity. This embodiment of the application does not make any limitation to this.

[0110] The kernel layer can include the kernel subsystem and the driver subsystem. The operating system can adopt a multi-kernel design. Based on the kernel subsystem, the operating system supports the selection of suitable OS kernels for different resource-constrained devices; the kernel abstraction layer (KAL) shields the differences between multiple kernels and provides basic kernel capabilities to the upper layer, including process management / thread management, memory management, file system, network management, and peripheral management. The driver framework in the driver subsystem is the basis for the openness of the operating system hardware ecosystem, and can provide unified peripheral access capabilities and driver development and management frameworks.

[0111] It should be understood that Figure 1 and Figure 2 The structure of the terminal described is only an example and should not limit the embodiments of the present application.

[0112] To facilitate understanding, the following is a brief explanation of the terms involved in this application.

[0113] 1. SIM and eSIM: SIM cards are used to store data and authenticate customer identities. eSIM embeds the traditional SIM card directly into the device chip instead of adding it to the device as an independent removable component. When one or more profiles of the eSIM are activated, the user can access the network of the operator to which he belongs. It is understandable that when the user changes the device, the SIM can be migrated to the new device by plugging and unplugging, but the eSIM cannot be migrated by plugging and unplugging. The method provided in this application is mainly applicable to the migration of eSIM configuration files.

[0114] 2. Configuration file: specifically, it refers to the operator configuration file. The configuration file may include, but is not limited to, a combination of file systems, file contents, data and applications provided on the UICC (such as eSIM), mainly carrying information such as IMSI and authentication parameters, and can access its corresponding mobile network after activation.

[0115] It should be understood that in the present application, profile is an example of a configuration file, and there may be other possible forms or names, or there may be the possibility of being defined with other names, which is not limited in the present application.

[0116] The following will be combined Figure 3 and Figure 4 Describe in detail the migration process of existing configuration files. Figure 3 The migration process of the configuration files shown in the figure requires not only the participation of the operator's server, but also the user needs to go to the operator's business outlets; Figure 4 During the migration of the configuration files shown, although the user does not need to go to the operator's business outlets, the operator's server still needs to be involved.

[0117] Figure 3 It is a flow chart of a method for migrating an existing configuration file provided in an embodiment of the present application.

[0118] like Figure 3 As shown, the user can go to the operator's business outlets to apply for the migration of the configuration file. If the operator agrees to migrate the configuration file, obtain the relevant identification of the old device (such as the international mobile equipment identity (IMEI) and / or electronic identity (EID)) to complete the deactivation and deletion of the configuration file on the old device; and obtain the relevant identification of the new device (such as IMEI and / or EID), and provide the user with a new activation code so that the new device can complete the download of the configuration file from the operator server (such as SM-DP+ server) based on the above activation code.

[0119] In this application, the old device refers to the device that stores the configuration file of the eSIM to be migrated. The new device refers to the device that needs to re-download the configuration file from the operator server, in other words, the configuration file needs to be migrated from the old device to the new device.

[0120] Figure 4 This is another flow chart of the method for migrating existing configuration files provided in an embodiment of the present application.

[0121] like Figure 4 As shown, both the old device and the new device download the configuration file from the operator server. Exemplarily, the configuration file of the old device can be downloaded from the operator server (such as the SM-DP+ server). When the user wants to migrate the configuration file of the old device to the new device, the old device can send its own preference configuration information to the new device by scanning the code or connecting to Bluetooth, wherein the above-mentioned preference configuration information includes, but is not limited to: the Wi-Fi connected to the old device, screen saver settings, privacy settings, the package used by the eSIM and other information, which is not specifically limited in this application. Furthermore, the operator server confirms whether the old device is eligible for migration. If the old device is eligible for migration, the configuration file of the eSIM of the old device is deactivated and deleted. In addition, the operator server returns the activation code of the configuration file to the old device, the old device sends the activation code of the configuration file to the new device, and the new device completes the download of the configuration file from the operator server based on the above activation code.

[0122] It can be seen that in Figure 3 and Figure 4 The migration process of the configuration file shown is essentially the process of deactivating and deleting the configuration file on the old device, and re-downloading the configuration file from the operator server on the new device. The entire migration process requires the participation of the operator server, involves many network elements, is relatively complex, and has a low user experience.

[0123] In order to improve user experience, the present application provides a configuration file migration method. The first terminal establishes a secure communication connection with the second terminal. The first terminal and the second terminal can interact directly. The second terminal is a server and the first terminal is a client. The first terminal can access the second terminal as a client and obtain the above configuration file directly from the second terminal. The entire migration process does not require the participation of the operator server, and the process is relatively simple, achieving the same level of convenience as physical SIM transfer, which is conducive to improving user experience.

[0124] Before describing in detail the configuration file migration method provided by the present application, a system applicable to the method provided by the present application is first described in detail below.

[0125] Figure 5It is a schematic diagram of a system architecture suitable for the method provided in the embodiment of the present application.

[0126] like Figure 5 As shown, the system includes a first terminal and a second terminal. The second terminal is a terminal storing a configuration file of the eSIM to be migrated. In other words, the second terminal is the source of the configuration file to be migrated, and the first terminal is a terminal receiving the configuration file, or the first terminal is the destination of the configuration file. In other words, the configuration file is migrated from the second terminal to the first terminal.

[0127] A secure communication connection can be established between the first terminal and the second terminal based on any of the following: Wi-Fi connection, Bluetooth connection, or NFC connection to achieve peer to peer (P2P) transmission. The first terminal can act as a client and directly obtain the configuration file of the eSIM to be migrated from the second terminal (acting as a server).

[0128] Optionally, the first terminal can obtain its own eSIM configuration file by calling the browser. In this case, the browser can be regarded as the client and the eSIM can be regarded as the server. The first terminal can also obtain the eSIM configuration file of the second terminal by calling the browser. In this case, the first terminal can be regarded as the client and the second terminal can be regarded as the server.

[0129] Figure 6 is another schematic diagram of a system architecture applicable to the method provided in the embodiment of the present application. Figure 6 In, yes Figure 5 The modules in the first terminal and the second terminal are illustrated in more detail.

[0130] like Figure 6 As shown, the second terminal includes a routing (rooting) gateway, eSIM, communication hardware, etc. Among them, the eSIM in the second terminal can be regarded as a server, and the eSIM includes a server module (such as a mobile network operator smart card web server (mobile network operator smart card web server, Mno smart card web server) and a configuration file database. The configuration file database is used to store configuration files, and the server module can obtain configuration files from the configuration file database. The server module is used to provide server functions, or in other words, the first terminal can access the eSIM in the second terminal as a client. The routing gateway in the second terminal is used to parse the IP data packet address from the upper layer (using the TCP / IP protocol) to determine whether to transmit the IP data packet to other devices in the local area network or to the local server (that is, the server module).

[0131] The first terminal includes a browser, a routing gateway, an eSIM, communication hardware, etc. Among them, when the first terminal accesses the eSIM of the second terminal, the eSIM of the first terminal can be regarded as a client. When the first terminal accesses its own eSIM through a browser, the eSIM of the first terminal can be regarded as a server. The eSIM includes a server module (such as Mno webserver), a client module (admin client agent), and a configuration file database. Among them, the browser is used to provide local services and remote services. The local service means that the first terminal can access the local eSIM (regarded as the server) through the browser (regarded as the client). Specifically, the server module of the first terminal can obtain the configuration file from the configuration file database of the first terminal, and then return it to the browser. Remote service means that the first terminal can access the eSIM of the second terminal through the browser.

[0132] The routing gateway in the first terminal is used to resolve the IP data packet address to determine whether to transmit the IP data packet to other devices in the local area network or to the local server. The client module in the eSIM of the first terminal is used to provide client functions. The server module is used to provide server functions. The first terminal can access the local eSIM through a browser. At this time, the local eSIM is regarded as the server. The configuration file database is used to store configuration files, and the server module can obtain configuration files from the configuration file database.

[0133] The eSIM of the second terminal and the eSIM of the first terminal can establish a transport layer path, and the communication hardware of the second terminal and the communication hardware of the first terminal can establish a physical layer path. The application layer data flow can be used to transmit application layer data.

[0134] It can be understood that in the present application, the configuration file of the eSIM of the second terminal may be encrypted before being transmitted to the first terminal to improve security. The first terminal and the second terminal may negotiate a key based on a physical layer connection to establish a secure communication connection between the two terminals. The key may be a symmetric key. The second terminal may encrypt the configuration file based on the key, and the first terminal may decrypt it based on the key.

[0135] The following will describe in detail the configuration file migration method provided by the present application in conjunction with the accompanying drawings.

[0136] Figure 7 It is a schematic flow chart of a configuration file migration method 700 provided in an embodiment of the present application. Figure 7 The method 700 shown may include steps 710 to 730. Each step in the method 700 is described in detail below.

[0137] It should be understood that Figure 7 The method 700 shown is described by taking the first terminal as the execution subject as an example, but no limitation should be imposed on the execution subject of the method. As long as the program that can record the code of the method provided by the embodiment of the present application can be run, the method provided by the embodiment of the present application can be executed. For example, the first terminal can also be replaced by a component configured in the first terminal (such as a chip, a chip system, etc.), or other functional modules that can call and execute programs. The embodiment of the present application does not limit this.

[0138] In step 710, at least one terminal is displayed, where the at least one terminal is determined by the first terminal through device discovery.

[0139] The first terminal may discover at least one terminal through the device, and display the at least one terminal through the user interface, so that the user can select a terminal storing the configuration file of the eSIM to be migrated.

[0140] In one example, taking NFC scanning discovery as an example, the first terminal can determine at least one terminal within its field strength range through device discovery. For example, in response to the user clicking the device discovery operation on the first terminal, the first terminal can prompt the user through the user interface to "move closer to surrounding devices and use NFC scanning". In response to the user moving according to the prompt, the first terminal can display at least one terminal within the field strength range of the first terminal through the user interface, so that the user can select a terminal storing the configuration file of the eSIM to be migrated.

[0141] In another example, taking Bluetooth scanning discovery as an example, the first terminal can determine at least one terminal within its broadcast range through device discovery. For example, in response to the user clicking the device discovery operation on the first terminal, the first terminal can discover at least one terminal within its broadcast range through broadcast, and display the at least one terminal through a user interface, so that the user can select a terminal storing the configuration file of the eSIM to be migrated.

[0142] In step 720, in response to a user's operation on a second terminal among the at least one terminal, a secure communication connection is established with the second terminal, in which a configuration file of the eSIM to be migrated is stored.

[0143] Exemplarily, the first terminal displays the at least one terminal, and in response to a user selecting a second terminal from the at least one terminal, establishes a secure communication connection with the second terminal.

[0144] In the present application, a secure communication connection can be understood as: based on the physical layer connection with the second terminal, the first terminal and the second terminal negotiate a key to establish a secure communication connection, and the key is used to encrypt the configuration file. In other words, the configuration file obtained by the first terminal from the second terminal is encrypted with the key. In other words, the second terminal can encrypt the configuration file to obtain an encrypted configuration file, and send the encrypted configuration file to the first terminal. Correspondingly, the first terminal receives the encrypted configuration file and decrypts it to obtain a decrypted configuration file. Encrypting the configuration file is conducive to improving security. As an example and not a limitation, the first terminal and the second terminal can pre-negotiate a symmetric key to encrypt and decrypt the configuration file based on the symmetric key. The present application does not limit the specific encryption method.

[0145] Optionally, the first terminal and the second terminal establish a secure communication connection based on any one of the following: Wi-Fi connection, Bluetooth connection or NFC connection.

[0146] A Wi-Fi connection, a Bluetooth connection, or a short-distance communication connection such as NFC may be established between the first terminal and the second terminal. It should be understood that the above connection is only an example and should not constitute any limitation to this application.

[0147] It can be understood that the above-mentioned Wi-Fi connection, Bluetooth connection or NFC connection belongs to a physical layer connection, and the first terminal can further establish a transport layer connection with the second terminal. Exemplarily, the first terminal acts as a client and the second terminal acts as a server. The first terminal and the second terminal can establish a transport layer link based on the TCP / IP protocol using the transport layer security protocol (TLS) protocol. For example, the first terminal as a client can complete a TCP / IP three-way handshake with the second terminal to establish a TLS secure encrypted link. For example, the first terminal and the second terminal can negotiate a key to establish a secure communication link, and the key is used to encrypt the configuration file. For the process of the three-way handshake, please refer to the known technology, which will not be described in detail here.

[0148] The first terminal displays the at least one terminal, and in response to a user selecting a second terminal from the at least one terminal, establishes a physical layer connection with the second terminal. Furthermore, the first terminal, as a client, can complete a TCP / IP three-way handshake with the second terminal to establish a transport layer connection.

[0149] Optionally, before displaying at least one terminal, the first terminal may call a browser to display a management interface of its own eSIM.

[0150] One possible design is that, in response to a first operation, a management interface of the eSIM of the first terminal is displayed based on a browser of the first terminal, the first operation being an operation in which a user clicks on an eSIM application, and the eSIM application is used to provide security authentication and storage of personal information services.

[0151] Among them, eSIM is similar to a SIM card application, which is used to provide security authentication and storage of personal information services. The eSIM application can be, for example, a menu application in a setting menu such as cellular settings, system application settings, etc., or a third-party application, or a small program in a third-party application, which is not limited in this application. Through the operation of the user clicking on the eSIM application, the first terminal can call the browser to display the management interface of the eSIM of the first terminal, that is, to display the management interface of the eSIM of this terminal. In other words, the browser can be regarded as a client at this time, and the eSIM of the first terminal can be regarded as a server. The first terminal can access (or read) the eSIM of this terminal through the browser without relying on the existing local profile assistant (LPA) system application.

[0152] The management interface of the eSIM of the first terminal includes, but is not limited to, the following contents: configuration file information, subscription, download, installation, update, activation, deactivation, deletion and transmission, etc.; the above contents are displayed to the user in a web page interactive graphical interface, and the web page content can be directly provided by the eSIM.

[0153] Figure 8 It is a schematic diagram of the management interface of the eSIM of the first terminal provided in an embodiment of the present application.

[0154] like Figure 8 As shown in a), the first terminal displays the phone's setting menu through the user interface, for example, including online identification of unfamiliar numbers, harassment call blocking, phone secretary, call recording, smart dialing, eSIM applications, etc. In response to the user clicking the eSIM application operation, the first terminal can call the browser to display the management interface of the eSIM of the first terminal, such as Figure 8 As shown in b), the management interface of the eSIM of the first terminal includes information, subscription, download, installation, update, activation, deactivation, deletion and transmission of the configuration file. Further, in response to the user clicking on an item (such as deletion of the configuration file) in the management interface of the eSIM of the first terminal, the first terminal can delete its own eSIM configuration file. It can be understood that the management interface of the eSIM of the first terminal includes the transmission of the configuration file. If the item (transmission of the configuration file) is clicked, the configuration file of the eSIM of the first terminal can be migrated to another terminal (such as a third terminal) connected to it in a secure communication.

[0155] Another possible design is that, in response to the second operation, a settings menu is displayed, and the second operation is an operation in which the user clicks on the settings; in response to the third operation, a cellular settings menu is displayed, and the third operation is an operation in which the user clicks on the cellular settings in the settings menu; in response to the fourth operation, the management interface of the eSIM of the first terminal is displayed based on the browser of the first terminal, and the fourth operation is an operation in which the user clicks on the migration eSIM in the cellular settings menu.

[0156] Fig. 9 This is another schematic diagram of the management interface for entering the eSIM of the first terminal provided in an embodiment of the present application.

[0157] like Fig. 9 As shown in a), the first terminal displays a setting menu through a user interface, for example, including display and brightness, sound and vibration, shortcuts and assistance, system navigation, system management, cellular settings, etc. In response to the user clicking the cellular settings operation, the first terminal displays the cellular settings menu, such as Fig. 9 As shown in b), for example, it includes data, dialing and information, traffic management, traffic store, migration eSIM, advanced settings, etc. In response to the user clicking the operation of migrating eSIM, the first terminal can call the browser to display the management interface of the eSIM of the first terminal, such as Fig. 9 As shown in c), the management interface of the eSIM of the first terminal includes information, subscription, download, installation, update, activation, deactivation, deletion and transmission of the configuration file, etc. Further, in response to the user clicking on an item (such as deletion of the configuration file) in the management interface of the eSIM of the first terminal, the first terminal can delete the configuration file of its own eSIM.

[0158] It should be noted that one possible implementation method is: Fig. 9 The migration of the eSIM shown in b) may indicate that the configuration file of the eSIM on the first terminal is migrated to another terminal, or may indicate that the first terminal obtains the configuration file of the eSIM of another terminal (such as the second terminal).

[0159] Fig.10 is a schematic diagram of the management interface of the eSIM of the first terminal provided in an embodiment of the present application. Fig.10 As shown, in response to the user clicking on the operation of migrating eSIM, the first terminal can call a browser to display the management interface of the eSIM of the first terminal. The management interface of the eSIM of the first terminal may include a device discovery button. In response to the user clicking on the operation of device discovery, the first terminal displays at least one terminal. In response to the user selecting the second terminal among the above at least one terminal, the first terminal establishes a secure communication connection with the second terminal, and the first terminal can obtain the configuration file of the eSIM of the second terminal.

[0160] Fig.11 Schematic diagram of the interface of the device discovery process provided by the embodiment of the present application. Fig.11 As shown, in response to the user clicking on the operation of migrating eSIM, the first terminal displays at least one terminal determined through device discovery, such as the second terminal, the third terminal, the fourth terminal and the fifth terminal in the figure, and in response to the user selecting the second terminal among the above at least one terminal, the first terminal establishes a secure communication connection with the second terminal, and the first terminal can obtain the configuration file of the eSIM of the second terminal.

[0161] It should be understood that Figures 8 to 11 The interface shown is only an example and should not constitute any limitation to the present application. For example, in some embodiments, the above interface may include more or less content, and for another example, the above interface may be displayed in other forms, which is not limited by the present application.

[0162] It should also be understood that the first terminal calls the browser to display the management interface of its own eSIM. At this time, the browser can be regarded as a client, and the eSIM of the first terminal itself can be regarded as a server. The browser accesses the local eSIM as a client. The domain name address of the local eSIM can be preset (or there is no need for the user to enter it manually). After the first terminal calls the browser, the domain name address is used by default to access the local eSIM.

[0163] Another possible design is that, in response to the fifth operation, the management interface of the eSIM of the first terminal is displayed based on the browser of the first terminal, and the fifth operation is an operation of the user inputting the eSIM domain name address in the browser application.

[0164] Exemplarily, after the user opens the browser of the first terminal, in response to the user inputting the eSIM domain name address in the browser, the first terminal displays the management interface of its own eSIM.

[0165] Optionally, the management interface of the eSIM of the first terminal includes a device discovery button, and the displaying of at least one terminal includes: in response to a user clicking an operation of device discovery in the management interface of the eSIM of the first terminal, displaying the at least one terminal.

[0166] Exemplarily, the management interface of the eSIM of the first terminal may include a device discovery button. In response to a user clicking on the device discovery operation, the first terminal displays at least one of the above-mentioned terminals; in response to a user selecting a second terminal among the above-mentioned at least one terminal, the first terminal establishes a secure communication connection with the second terminal.

[0167] It can be understood that in order to improve security, before the first terminal establishes a secure communication connection with the second terminal, the second terminal can display a prompt message, which is used to prompt the user whether to confirm the establishment of the connection. In response to the user clicking to confirm the connection, the first terminal establishes a secure communication connection with the second terminal.

[0168] Exemplarily, in response to a user selecting a second terminal among the at least one terminal, the first terminal sends a request to establish a connection to the second terminal. After receiving the request, the second terminal prompts the user "Do you confirm to establish the connection?". In response to the user clicking confirm, the first terminal establishes a secure communication connection with the second terminal.

[0169] In step 730, the configuration file is obtained from the second terminal based on the secure communication connection with the second terminal.

[0170] After the first terminal establishes a secure communication connection with the second terminal, the configuration file may be obtained from the second terminal based on the secure communication connection with the second terminal.

[0171] One possible implementation method is that the first terminal receives management interface data of the eSIM of the second terminal based on a secure communication connection with the second terminal, and the management interface data of the eSIM of the second terminal is used to generate a management interface of the eSIM of the second terminal; in response to the user's operation on the management interface of the eSIM of the second terminal, the configuration file is obtained from the second terminal.

[0172] Exemplarily, the first terminal as a client can receive the management interface data of the eSIM of the second terminal based on the secure communication connection with the second terminal, and then generate and display the management interface of the eSIM of the second terminal based on the management interface data. In response to the user clicking the transmission operation in the management interface of the eSIM of the second terminal, the configuration file is obtained from the second terminal.

[0173] It can be understood that in response to the user clicking on the transmission operation in the management interface of the eSIM of the second terminal, the first terminal can send a request message to the second terminal to request the second terminal to transmit the above-mentioned configuration file. After receiving the above-mentioned request message, the second terminal sends the above-mentioned configuration file to the first terminal based on the communication connection with the first terminal.

[0174] Fig.12 This is a schematic diagram of a first terminal displaying an eSIM management interface of a second terminal provided in an embodiment of the present application.

[0175] like Fig.12As shown in a), the first terminal can receive the management interface data of the eSIM of the second terminal based on the secure communication connection with the second terminal, and then generate and display the management interface of the eSIM of the second terminal based on the management interface data. The management interface of the eSIM of the second terminal includes information, subscription, download, installation, update, activation, deactivation, deletion and transmission of the configuration file. Among them, in response to the user clicking on the transmission of the configuration file, the first terminal can obtain the configuration file of the second terminal. It can be seen that the top may include a drop-down menu for selecting which eSIM management interface to view. In response to the user clicking on the drop-down menu, the first terminal displays the first terminal and the second terminal that can be selected, such as Fig.12 As shown in b), the user can select which eSIM on which terminal to access. For example, in response to the user selecting the first terminal, the first terminal displays the eSIM of the first terminal that can be selected, such as Fig.12 As shown in c), the first terminal includes eSIM1 and eSIM 3. In response to the user selecting the operation of eSIM 1, the first terminal displays the management interface of eSIM 1.

[0176] Understandably, Fig.12 a) in FIG. 1 shows that the first terminal displays the management interface of the eSIM 2 on the second terminal, but this shall not constitute any limitation to the present application. Fig.12 If the second terminal is shown in b), the first terminal can display all eSIMs (such as eSIM 2 and eSIM 4) on the second terminal. In response to the user selecting eSIM 4, the first terminal can also display the management interface of eSIM 4 of the second terminal.

[0177] Optionally, after the user clicks on Transfer in the management interface of the eSIM of the second terminal, the second terminal may return a prompt message to the first terminal, which prompts the user whether to confirm the transfer. The first terminal displays the prompt message through the interface, and in response to the user clicking on Confirm, the second terminal sends the configuration file to the first terminal.

[0178] In order to improve security, before obtaining the configuration file from the second terminal based on the secure communication connection with the second terminal, the method 700 further includes: displaying a verification interface, which is generated based on the verification interface data from the second terminal; in response to the user inputting one or more of the following verification factors in the verification interface, sending the verification factor input by the user to the second terminal: the account information registered by the user on the second terminal, the PIN set by the user when registering the account on the second terminal, the biometric information, or the challenge code of the second terminal. The biometric information may be, for example, a fingerprint, a face, etc., which is not limited in this application.

[0179] The above-mentioned verification interface data may refer to the elements contained in the verification interface (such as input boxes, buttons, etc.) and the layout of each element. The first terminal may generate and display a verification interface based on the above-mentioned data for the user to input a verification factor in the first terminal, thereby completing the verification of the user's identity.

[0180] Exemplarily, before the first terminal obtains the configuration file from the second terminal based on the secure communication connection with the second terminal, the second terminal sends verification interface data to the first terminal, and after the first terminal receives the verification interface data, it generates and displays the verification interface. In response to the user inputting the verification factor on the verification interface of the first terminal, the first terminal sends the verification factor input by the user to the second terminal, and after the second terminal receives the verification factor, it verifies the user's identity.

[0181] If the second terminal fails to power on, has a cracked screen, has a degraded battery, or even fails to boot, the second terminal may not be able to display the challenge code. Therefore, the second terminal can verify the user's identity based on the account information registered by the user on the second terminal and / or the PIN set by the user when registering the account on the second terminal.

[0182] As can be seen above, the second terminal can verify the user's identity based on the above verification factors. In addition, the first terminal can also verify the user's identity based on the verification code. For example, the first terminal can display the verification code, which can be a verification code of the type "3+4=?", etc. If the user enters it correctly, the user's identity is successfully authenticated. In other words, it means that the user is operating normally, not maliciously attacking.

[0183] When the user identity authentication is successful, the second terminal may send the configuration file to the first terminal based on the secure communication connection with the first terminal.

[0184] It is understandable that if the second terminal verifies the user identity based on the above verification factors each time, the process is relatively complicated. Therefore, the second terminal can send a token to the first terminal when the user identity verification is successful for the first time, and the token can be used for subsequent communication between the first terminal and the second terminal. In other words, the first terminal and the second terminal can complete the identity verification through the above token when they interact with each other.

[0185] It can be understood that in the above description, in another implementation manner in which the first terminal directly obtains the configuration file from the second terminal, the second terminal may also actively send the configuration file to the first terminal.

[0186] Exemplarily, the second terminal can display its own eSIM management interface based on the browser (similar to the process of the first terminal displaying its own eSIM management interface based on the browser, which is not described in detail here). In response to the user clicking on the transmission operation in the eSIM management interface, the second terminal can display at least one terminal for the user to select. In response to the user selecting the first terminal, the first terminal establishes a secure communication connection with the second terminal, and the second terminal actively sends the configuration file to the first terminal based on the secure communication connection with the first terminal.

[0187] Optionally, when the first terminal and the second terminal establish a secure communication connection based on the NFC connection, the above configuration file is carried in a data packet, which includes an APDU header, an IP header, and an HTTPS header from the outside to the inside; or, the data packet includes an APDU header and an HTTPS header from the outside to the inside. The HTTPS header can be replaced by an HTTP header.

[0188] When the first terminal and the second terminal establish a secure communication connection based on a Bluetooth connection, the configuration file is carried in a data packet, which includes a PDU header, an IP header, and an HTTPS header from the outside to the inside; or, the data packet includes a PDU header, an APDU header, and an HTTPS header from the outside to the inside.

[0189] When the first terminal and the second terminal establish a secure communication connection based on the Wi-Fi connection, the configuration file is carried in a data packet, which includes a PPDU header, an IP header, and an HTTPS header from the outside to the inside; or, the data packet includes a PPDU header, an APDU header, and an HTTPS header from the outside to the inside.

[0190] Among them, when the data packet includes an IP header, the eSIM of the first terminal and the second terminal encapsulates the TCP / IP protocol stack. When the data packet does not include an IP header, the eSIM of the first terminal and the second terminal may not encapsulate the TCP / IP protocol stack. This method can reuse the functions currently available in the eSIM, such as stripping the header of the TCP / IP data packet through the BIP gateway to obtain HTTP or HTTPS valid data, which is conducive to reducing costs.

[0191] The following describes in detail the cases where the eSIM of the second terminal encapsulates the TCP / IP protocol stack and does not encapsulate the TCP / IP protocol stack.

[0192] Fig.13 It is a schematic diagram of the eSIM encapsulated TCP / IP protocol stack of the second terminal provided in an embodiment of the present application.

[0193] like Fig.13As shown, in common scenarios, if a user uses a certain browser, the first terminal can access the cloud server corresponding to the browser through cellular or Wi-Fi. In more detail, the first terminal transmits the data packet to the server corresponding to the browser through the TCP / IP protocol stack, routing gateway, and cellular (or Wi-Fi) in sequence. In the present application, the eSIM of the second terminal is encapsulated with a TCP / IP protocol stack. In other words, the data packet carrying the above-mentioned configuration file includes an IP header. The physical input / output interface uses a high-speed physical interface, such as a USB interface, an I2C interface, an SPI, or an I3C interface. The first terminal transmits the data packet to the eSIM of the second terminal through the TCP / IP protocol stack, the routing gateway, the eSIM of the first terminal, and the NFC of the first terminal in sequence, wherein the eSIM of the second terminal serves as a web server. On the contrary, after the web server of the second terminal obtains the configuration file from the configuration file database, it encapsulates the IP header and returns it to the first terminal.

[0194] Fig.14 It is a schematic diagram of the unencapsulated TCP / IP protocol stack of the eSIM of the second terminal provided in an embodiment of the present application.

[0195] like Fig.14 As shown, in common scenarios, the modem of the second terminal can send commands to the eSIM of the second terminal, such as commands for initializing a terminal profile, commands for querying status, fetch commands, envelope commands, etc. The eSIM of the second terminal returns the result to the modem. In the present application, the eSIM of the second terminal reuses the existing BIP protocol stack and the International Organization for Standardization (ISO) IO interface. The first terminal sends remote commands to the eSIM of the second terminal, such as commands for initializing a remote configuration file, commands for querying status at the remote end, fetch commands at the remote end, envelope commands at the remote end, etc. The eSIM of the second terminal, as a server, returns a pipe to the first terminal to open its server application. The eSIM of the second terminal does not encapsulate the TCP / IP protocol stack, so when the first terminal sends data to the second terminal, the BIP gateway of the first terminal strips the IP packet header.

[0196] It should be noted that Fig.13 and Fig.14 The scheme of establishing a physical layer connection between the first terminal and the second terminal via NFC is only shown, but it should not constitute any limitation to the present application. The first terminal and the second terminal can also establish a physical layer connection via Wi-Fi or Bluetooth. In other words, Fig.13 and Fig.14NFC can also be replaced by Wi-Fi or Bluetooth.

[0197] The following will be combined Fig.15 The interaction process between the modules when the TCP / IP protocol stack is encapsulated in the eSIM of the second terminal is described in detail.

[0198] Fig.15 It is a detailed flowchart of the configuration file migration method provided in the embodiment of the present application.

[0199] like Fig.15 As shown, the first terminal can access the management interface of the eSIM of the local terminal through a browser. Exemplarily, the browser, as a client, completes a TCP / IP three-way handshake with the server module of the eSIM of the local terminal to establish a TLS secure encryption link. Exemplarily, in response to the user inputting an account and password (or performing biometric identification based on biometric information), the server module of the eSIM is logged in. Among them, biometric identification relies on fast identity online (FIDO) authentication. When the user registers for the first time, he can be prompted to activate FIDO authentication. At this time, the trusted execution environment (TEE) generates a public-private key pair, and the public key, website domain name information, client identification and other information are transmitted to the server module of the eSIM. Among them, TEE is a security framework running in the device. The enabling of the public-private key pair is associated with biometric information such as user fingerprints and faces. When logging in to the server module of the eSIM next time, it is prompted to verify biometric information such as fingerprints, and then the login information is signed with a matching private key and sent to the server module of the eSIM. The server module uses the registered public key to verify the signature to successfully log in.

[0200] The server module of the eSIM at the local end returns a website homepage file (index.html homepage), that is, management interface data of the eSIM at the local end, and the first terminal displays the website homepage, that is, the management interface of the eSIM at the local end, and the management interface includes, for example, but is not limited to query, subscription, download, installation, update, activation, deactivation, deletion and transmission of the configuration file of the eSIM at the local end.

[0201] It can be understood that the two implementation methods of the first terminal entering the management interface of the eSIM of the local terminal through the browser can be referred to Figure 8 and Fig. 9 The relevant description will not be described in detail here.

[0202] The process of establishing a communication connection between the first terminal and the second terminal is described in detail below.

[0203] In response to the user clicking on the device discovery operation in the management interface of the eSIM on the local side (i.e., the homepage of the website), the HTTPS message is sent to the server module of the eSIM on the local side, and the reader application is activated through this server module. In other words, the reader application is activated by operating the homepage of the website. The reader application can establish a pipe (PIPE) from the eSIM reader application gate to the reader RF gate through the host controller interface (HCI) of the eSIM management gate (adm gate) and the NFC management gate HCI, and transmit the APDU command of the reader application through this pipe.

[0204] After the reader application is activated, the application returns an HTTPS message of "approach nearby devices, use NFC scanning" through the server module, and the first terminal presents it to the user through the user interface.

[0205] When the second terminal enters the field strength range of the first terminal, the NFC of the first terminal establishes a channel with the NFC of the second terminal. Further, an internal channel of the second terminal is established, for example, through a card-type communication channel established between the management gate HCI of the eSIM and the management gate HCI of the NFC, a channel is established from the card application gate of the eSIM to the card RF gate, and the APDU command of the card application is transmitted through this channel.

[0206] The browser of the first terminal acts as a client and completes a TCP / IP three-way handshake with the server module of the eSIM of the second terminal to establish a TLS secure encrypted link. Exemplarily, in response to the user inputting an account number and password (or performing biometric identification based on biometric information), the server module of the eSIM of the second terminal is logged in. The server module of the eSIM of the second terminal returns the management interface data of the eSIM of the second terminal, and the first terminal displays the management interface of the eSIM of the second terminal, for example, including but not limited to querying, subscribing, downloading, installing, updating, activating, deactivating, deleting and transmitting the configuration file of the eSIM of the second terminal.

[0207] In response to the user's selection of transmission, the server module of the eSIM of the second terminal returns an HTTPS message to the browser of the first terminal, and the HTTPS message is used to prompt the user whether to confirm the transmission. In response to the user clicking to confirm the transmission, the first terminal can send an HTTPS message to the server module of the second terminal, and the HTTPS message carries a token. Further, the server module calls the profile package backup application to encrypt and package the configuration file, and the encryption key is generated through negotiation. Then the second terminal sends the encrypted configuration file to the first terminal through the server module, and accordingly, the first terminal receives the encrypted configuration file. The first terminal can decrypt the configuration file and write it into the configuration file database.

[0208] The following will be combined Fig.16 The interaction process between the modules when the TCP / IP protocol stack is not encapsulated in the eSIM of the second terminal is described in detail.

[0209] Fig.16 It is another detailed flowchart of the configuration file migration method provided in an embodiment of the present application.

[0210] Fig.16 and Fig.15 The embodiment shown differs in that Fig.16 In the example, the first terminal includes a BIP gateway, a modem, and an on-chip BIP universal subscriber identity module application toolkit (USAT) application. The three modules act as a bridge when establishing an HTTPS secure link and subsequently accessing the server module of the eSIM of the local terminal and / or the server module of the eSIM of the second terminal through a browser. Since the eSIM does not encapsulate the TCP / IP protocol stack, the HTTPS request information and response information cannot be directly transmitted using a browser application. Fig.16In the illustrated embodiment, when the eSIM does not encapsulate the TCP / IP protocol stack, the HTTPS request information from the browser application of the first terminal is converted in the BIP gateway into an APDU command of the initialization response (terminal response) of the USAT application that the eSIM can recognize, and the APDU data field (i.e., the HTTPS request information) is split into frame data. These APDUs are sent to the USAT application on the eSIM chip through a modem, and then restored and packaged into an HTTPS stream (stream), which is further processed and responded to by the on-chip server module; when sending the HTTPS response information, it may be sent in fragments based on the length of the message to be sent. Specifically, a "send data (store mode) proactive" command is first sent to the BIP gateway. After completing the sending of the "send data (immediately mode)" command, the BIP gateway restores the HTTPS stream and returns it to the browser application of the first terminal.

[0211] In addition, Fig.16 In the example, the user identification application toolbox (SIM tool kit, STK) can be used to trigger the eSIM to send a proactive command "proactive cmd", that is, the "open channel by server" command, to open an HTTPS link from the first terminal eSIM server to the first terminal browser. After the link is established, the server module of the local eSIM can be accessed (or read) in the browser through the website homepage file (index.html homepage). Among them, the first terminal establishes an HTTPS link between the browser and the server module of the eSIM of the second terminal, and can trigger the nearby eSIM to send a proactive command "proactivecmd", that is, the "open channel by server" command, by activating the reader RF door application and triggering the nearby eSIM request message, and sending the relevant APDU command to open another HTTPS link from the second terminal eSIM server to the first terminal browser.

[0212] The specific interaction process between the first terminal and the second terminal is as follows:

[0213] The following first describes in detail the verification process when accessing the local eSIM for level f and level eSIM, respectively. Level f and level e refer to the capability levels of the eSIM.

[0214] For f-level eSIM, when the eSIM is powered on, the eSIM of the first terminal sends a proactive command of "proactive cmd: DECLARESERVICE (add flag, Service Identifier = X, Service Record PDU)" to indicate to the browser side that it supports the eSIM server function. The browser side executes it correctly and adds it to its own service database (servicedatabase) for subsequent upper-layer application access. At the same time, the browser side returns an initialization response (terminal response) identifier.

[0215] The browser application of the first terminal is used as the UI operation entry to access the server module of the eSIM of the first terminal. The server module of the eSIM returns the management interface of the eSIM of the local terminal (that is, the homepage of the website). In response to the user entering the eSIM domain name address in the browser application, the BIP gateway triggers a local connection event and sends an APDU of "envelope (local connection)" to the eSIM of the local terminal; the eSIM returns an active command of "OPEN CHANNEL by SERVER (Service Identifier = X, Service Record PDU = '00')", which is intended to establish an HTTPS secure link pointing to the local browser. After successful execution, the BIP gateway returns an initialization response identifier.

[0216] The eSIM server module completes the TCP / IP three-way handshake with the browser application, prompting for login authentication. In more detail, the eSIM returns the active command "SEND DATA (Store, Data)", the BIP gateway responds with an initialization response identifier, and waits for "SEND DATA (Immediate, Data)", and then sends the package to the browser based on the TCP / IP socket. At this time, in response to the user operation, the prompt "Please log in to the server" is displayed.

[0217] In response, the browser client sends response data to the eSIM server module (the response data includes the certificate exchange and key negotiation data required to establish a secure link). After receiving the response, the BIP gateway sends "ENVELOPE (Data available, Channel Identifier)" to indicate that the eSIM currently has data to be received. The eSIM sends the "RECEIVEDATA (Channel identifier, Channel Data length)" command. The BIP gateway receives this active command and transmits the TCP / IP socket response information from the client in packets based on the BIP initialization response command.

[0218] The above-mentioned "SEND data / RECEIVE data", "envelope", and initialization response may be exchanged multiple times in the TCP / IP handshake, and this application does not limit this.

[0219] The eSIM continues to send the above website homepage as a UI portal for users to operate and access the eSIM server module. For login authentication and authorization, for example, in response to the user entering an account and password (or performing biometric identification based on biometric information), the eSIM server module can be logged in. For more detailed procedures, please refer to Fig.15 Related description.

[0220] For e-level eSIM, unlike f-level eSIM, when the eSIM is powered on, it will not show the device that it supports the eSIM server module. The user needs to initiate a request through the STK menu. After the user clicks the STK menu, the browser side sends the "ENVELOPE (SELECT ITEM)" command to the eSIM server module. The eSIM returns an active command of "OPEN CHANNEL by SERVER (UICC / terminal interface transport level)" to establish an HTTPS secure link pointing to the local browser. After the BIP gateway executes successfully, it returns an initialization response identifier. For other steps, please refer to the f-level eSIM, which will not be described in detail here. In addition, in addition to the user being able to enter the eSIM domain name address in the browser application, it can also be triggered by clicking on the eSIM application, which is not limited in this application.

[0221] The process of discovering and establishing a connection with the first terminal will be described in detail below. In response to the user clicking on the device discovery operation in the management interface of the eSIM on this side (i.e., the homepage of the website), the reader application is activated. In addition, the server module of the eSIM in the nearby terminal device can be triggered to return the activation configuration information of "open channel by server". The reader application can establish a pipe (PIPE) from the eSIM's reader application gate to the reader RF gate (reader RFgate) through the established reader-type management communication pipeline between the eSIM's management gate HCI and the NFC's management gate HCI, and use this pipeline to pass the reader application's APDU commands.

[0222] After the reader application is activated, the application returns an HTTPS message of "approach nearby devices, use NFC scanning" through the server module, and the first terminal presents it to the user through the user interface.

[0223] When the second terminal enters the field strength range of the first terminal, the NFC of the first terminal establishes a channel with the NFC of the second terminal. Through the management gate HCI of the eSIM and the management gate HCI of the NFC, a pipeline is established from the card application gate of the eSIM to the card RF gate, and the APDU command of the card application is transmitted through this pipeline, that is, the reader application APDU command sent by the first terminal. The establishment of the above pipeline can be completed when the eSIM of the second terminal is powered on based on performance considerations.

[0224] The APDU command data domain of the reader application may include commands for initializing the configuration file (terminal profile), status query (status) commands, fetch commands, envelope commands, initialization responses (terminal response) and other commands, and may also include other necessary APDU commands specified by the European Telecommunications Standards Institute (ETSI) 102221 / 223. These commands are sent to the second terminal through near-field communication technologies such as NFC, and the eSIM card application of the second terminal first receives them, and then transparently transmits them to the BIPUAST application to trigger the f-level eSIM to return the active command "DECLARE SERVICE (add flag, Service Identifier = X, Service Record PDU)", or trigger the e-level eSIM to return the active command "open channel by server", and then establish an HTTPS secure link from the server module of the eSIM of the second terminal to the browser of the first terminal, just like accessing the server module of the eSIM on the local end. Among them, the difference between the f-level eSIM and the e-level eSIM is that the f-level eSIM does not need to additionally trigger the eSIM to enter the server mode.

[0225] The server module of the eSIM of the second terminal returns the management interface data of the eSIM of the second terminal, and the first terminal displays the management interface of the eSIM of the second terminal, for example, including but not limited to query, subscription, download, installation, update, activation, deactivation, deletion and transmission of the configuration file of the eSIM of the second terminal.

[0226] In response to the user selecting the transmission operation, the server module of the eSIM of the second terminal returns an HTTPS message to the browser of the first terminal, and the HTTPS message is used to prompt the user whether to confirm the transmission. In response to the user clicking to confirm the transmission operation, the first terminal can send an HTTPS message to the server module of the second terminal, and the HTTPS message carries a token. After confirmation, an E2E secure transmission link based on the internal module of the eSIM is established.

[0227] Furthermore, the server module calls a profile package backup application to encrypt and package the configuration file, and the encryption key is generated through negotiation. Then the second terminal sends the encrypted configuration file to the first terminal through the server module, and accordingly, the first terminal receives the encrypted configuration file. The first terminal can decrypt the configuration file and write it into the configuration file database.

[0228] When sending and receiving data, the server module of the eSIM of the second terminal needs to go through the subpackaging and assembly processing of the BIP USAT module on the eSIM chip, among which BIP active commands: "SEND data", "RECEIVE data" and CAT commands: "envelop", "terminal response" are the basic carriers for transmitting the above data. BIP active commands are used to transmit HTTPS messages at the lower layer of the BIP gateway, and sockets are used to transmit HTTPS messages at the upper layer of the BIP gateway.

[0229] It should be noted that Fig.15 and Fig.16 Only a scheme in which the first terminal and the second terminal establish a physical layer connection through NFC is shown, but it should not constitute any limitation to the present application. The first terminal and the second terminal may also establish a physical layer connection through Wi-Fi or Bluetooth. In the case where the first terminal and the second terminal establish a physical layer connection based on Bluetooth, the data transmitted between the first terminal and the second terminal may be carried in a PDU, and in the case where the first terminal and the second terminal establish a physical layer connection based on Wi-Fi, the data transmitted between the first terminal and the second terminal may be carried in a PPDU.

[0230] Based on the above technical solution, after the second terminal receives the request message based on the secure communication connection established with the second terminal, the second terminal directly sends the configuration file of the eSIM of the second terminal to the first terminal. In other words, the first terminal and the second terminal can interact directly, wherein the second terminal is the server and the first terminal is the client. That is to say, the first terminal requests the configuration file from the server as the client, and accordingly, the second terminal returns the above configuration file to the first terminal as the server. The entire migration process does not require the participation of the operator server, and the process is relatively simple, which is conducive to improving user experience.

[0231] The present application also provides a configuration file migration device, which can achieve Figure 7 , Fig.13 , Fig.14 , Fig.15 or Fig.16 The method described in the embodiment shown. The device includes corresponding modules for executing the above method. The modules included in the device can be implemented by software and / or hardware.

[0232] The present application also provides a configuration file migration device, which includes a memory and a processor, wherein the memory is used to store a computer program, and the processor is used to call and execute the computer program, so that the device can achieve Figure 7 , Fig.13 , Fig.14 , Fig.15 or Fig.16 The method described in the illustrated embodiments.

[0233] The present application also provides a communication system, comprising the first terminal and the second terminal as described above.

[0234] The present application also provides a chip system, which includes at least one processor for implementing the above Figure 7 , Fig.13 , Fig.14 , Fig.15 or Fig.16 The functions involved in the methods described in the illustrated embodiments, for example, receive or process the data and / or information involved in the above methods.

[0235] In one possible design, the chip system also includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0236] The chip system may be composed of the chip, or may include the chip and other discrete devices.

[0237] The present application also provides a computer-readable storage medium, wherein a computer program (also referred to as code or instruction) is stored on the computer storage medium. When the computer program is executed by a processor, the above Figure 7 , Fig.13 , Fig.14 , Fig.15 or Fig.16 The method described in the illustrated embodiment is carried out.

[0238] The present application also provides a computer program product, the computer program product comprising: a computer program (also referred to as code, or instruction), when the computer program is executed, causes the computer to execute Figure 7 , Fig.13 , Fig.14 , Fig.15 or Fig.16 The method described in the illustrated embodiments.

[0239] It should be understood that the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor can be combined to perform. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0240] It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0241] The terms "unit", "module", etc. used in this specification may be used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. The units and modules in the embodiments of the present application have the same meaning and can be used interchangeably.

[0242] It will be appreciated by those skilled in the art that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or in combination with computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application. In the several embodiments provided in this application, it should be understood that the disclosed devices, equipment and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point, 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.

[0243] In the above embodiments, the functions of each functional unit can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When loading and executing computer program instructions (programs) on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrated. Available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, digital video discs (DVD)), or semiconductor media (eg, solid state drives (SSD)).

[0244] If the functions provided by the embodiments of the present application are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0245] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A configuration file migration method, characterized in that: Applied to a first terminal, the method includes: displaying at least one terminal, where the at least one terminal is determined by the first terminal through device discovery; In response to a user's operation on a second terminal of the at least one terminal, establishing a secure communication connection with the second terminal, wherein the second terminal stores a configuration file of an embedded subscriber identity module eSIM to be migrated; The configuration file is obtained from the second terminal based on a secure communication connection with the second terminal.

2. The method according to claim 1, characterized in that The obtaining the configuration file from the second terminal based on the secure communication connection with the second terminal includes: Receiving management interface data of the eSIM of the second terminal based on a secure communication connection with the second terminal, where the management interface data of the eSIM of the second terminal is used to generate a management interface of the eSIM of the second terminal; In response to a user operation on a management interface of the eSIM of the second terminal, the configuration file is obtained from the second terminal.

3. The method according to claim 2, characterized in that The acquiring the configuration file from the second terminal in response to the user operating the management interface of the eSIM of the second terminal includes: In response to a user clicking a transmission operation on the management interface of the eSIM of the second terminal, sending a request message to the second terminal, where the request message is used to request the second terminal to transmit the configuration file; The configuration file is received from the second terminal.

4. The method according to any one of claims 1 to 3, characterized in that The first terminal and the second terminal establish a secure communication connection based on any one of the following: a wireless fidelity Wi-Fi connection, a Bluetooth connection, or a near field communication NFC connection.

5. The method according to any one of claims 1 to 4, characterized in that Before displaying at least one terminal, the method further includes: In response to a first operation, a management interface of the eSIM of the first terminal is displayed based on a browser of the first terminal, wherein the first operation is an operation in which a user clicks on an eSIM application, and the eSIM application is used to provide services of security authentication and storage of personal information.

6. The method according to any one of claims 1 to 4, characterized in that Before displaying at least one terminal, the method further includes: In response to a second operation, displaying a settings menu, wherein the second operation is an operation in which the user clicks on settings; In response to a third operation, displaying a cellular settings menu, wherein the third operation is an operation in which a user clicks on a cellular setting in the settings menu; In response to a fourth operation, a management interface of the eSIM of the first terminal is displayed based on the browser of the first terminal, and the fourth operation is an operation of a user clicking on the migration eSIM in the cellular setting menu.

7. The method according to any one of claims 1 to 4, characterized in that Before displaying at least one terminal, the method further includes: In response to a fifth operation, a management interface of the eSIM of the first terminal is displayed based on the browser of the first terminal, and the fifth operation is an operation of a user inputting an eSIM domain name address in a browser application.

8. The method according to any one of claims 5 to 7, characterized in that The display of at least one terminal includes: In response to a user clicking on a device discovery operation in the management interface of the eSIM of the first terminal, the at least one terminal is displayed.

9. The method according to any one of claims 1 to 8, characterized in that Before acquiring the configuration file from the second terminal based on the secure communication connection with the second terminal, the method further includes: displaying a verification interface, wherein the verification interface is generated based on the verification interface data from the second terminal; In response to the user inputting one or more of the following verification factors on the verification interface, the verification factors input by the user are sent to the second terminal: the account information registered by the user on the second terminal, the personal identification password PIN set by the user when registering an account on the second terminal, the challenge code of the second terminal, or biometric information.

10. The method according to any one of claims 1 to 9, characterized in that When the first terminal and the second terminal establish a secure communication connection based on the NFC connection, the configuration file is carried in a data packet, and the data packet includes, from the outside to the inside, an application protocol data unit APDU header, an Internet protocol IP header, and a hypertext transfer security protocol HTTPS header; or, the data packet includes, from the outside to the inside, an APDU header and an HTTPS header.

11. The method according to any one of claims 1 to 9, characterized in that When the first terminal and the second terminal establish a secure communication connection based on a Bluetooth connection, the configuration file is carried in a data packet, and the data packet includes a protocol data unit PDU header, an IP header, and an HTTPS header from the outside to the inside; or, the data packet includes a PDU header, an APDU header, and an HTTPS header from the outside to the inside.

12. The method according to any one of claims 1 to 9, characterized in that When the first terminal and the second terminal establish a secure communication connection based on a Wi-Fi connection, the configuration file is carried in a data packet, and the data packet includes, from the outside to the inside, a physical layer protocol data unit PPDU header, an IP header, and an HTTPS header; or, the data packet includes, from the outside to the inside, a PPDU header, an APDU header, and an HTTPS header.

13. A method for migrating a configuration file, characterized in that: Applied to a second terminal, the second terminal storing a configuration file of an embedded subscriber identity module eSIM to be migrated, the method comprising: Establishing a secure communication connection with the first terminal; Based on the secure communication connection with the first terminal, receiving a request message from the first terminal, the request message being used to request the second terminal to transmit the configuration file; The configuration file is sent to the first terminal based on a secure communication connection with the first terminal.

14. The method according to claim 13, characterized in that Before receiving a request message from the first terminal based on the secure communication connection with the first terminal, the method further includes: Based on a secure communication connection with the first terminal, management interface data of the eSIM of the second terminal is sent to the first terminal, the management interface data of the eSIM of the second terminal is used to generate a management interface of the eSIM of the second terminal, and the request message is generated in response to a user's operation on the management interface of the eSIM of the second terminal.

15. The method according to claim 13 or 14, characterized in that The first terminal and the second terminal establish a secure communication connection based on any one of the following: a wireless fidelity Wi-Fi connection, a Bluetooth connection, or a near field communication NFC connection.

16. The method according to any one of claims 13 to 15, characterized in that Before sending the configuration file to the first terminal based on the secure communication connection with the first terminal, the method further includes: Sending verification interface data to the second terminal, where the verification interface data is used to generate a verification interface; Receiving one or more of the following verification factors input by the user of the second terminal and authenticating the user: account information registered by the user on the second terminal, a personal identification password PIN set by the user when registering an account on the second terminal, a challenge code of the second terminal, or biometric information; and sending the configuration file to the first terminal based on a secure communication connection with the first terminal, comprising: In the case where the identity authentication of the user is successful, the configuration file is sent to the first terminal based on a secure communication connection with the first terminal.

17. The method according to any one of claims 13 to 16, characterized in that When the first terminal and the second terminal establish a secure communication connection based on the NFC connection, the configuration file is carried in a data packet, and the data packet includes, from the outside to the inside, an application protocol data unit APDU header, an Internet protocol IP header, and a hypertext transfer security protocol HTTPS header; or, the data packet includes, from the outside to the inside, an APDU header and an HTTPS header.

18. The method according to any one of claims 13 to 16, characterized in that When the first terminal and the second terminal establish a secure communication connection based on a Bluetooth connection, the configuration file is carried in a data packet, and the data packet includes a protocol data unit PDU header, an IP header, and an HTTPS header from the outside to the inside; or, the data packet includes a PDU header, an APDU header, and an HTTPS header from the outside to the inside.

19. The method according to any one of claims 13 to 16, characterized in that When the first terminal and the second terminal establish a secure communication connection based on a Wi-Fi connection, the configuration file is carried in a data packet, and the data packet includes, from the outside to the inside, a physical layer protocol data unit PPDU header, an IP header, and an HTTPS header; or, the data packet includes, from the outside to the inside, a PPDU header, an APDU header, and an HTTPS header.

20. A configuration file migration device, characterized in that: comprising a processor and a memory, wherein: The memory is used to store computer programs; The processor is configured to call the computer program to enable the apparatus to implement the method according to any one of claims 1 to 12, or to enable the apparatus to implement the method according to any one of claims 13 to 19.

21. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by a computer, the method according to any one of claims 1 to 12 is implemented, or the method according to any one of claims 13 to 19 is implemented.

22. A computer program product, characterized in that The computer program product comprises instructions, and when the instructions are executed by a computer, the method according to any one of claims 1 to 12 is implemented, or the method according to any one of claims 13 to 19 is implemented.

Images