Configuration file management method and related apparatus

Abstract

The application provides a profile management method and related device, the method is applied to an electronic device including an embedded user identification eSIM module, and the method comprises the following steps: receiving a first profile sent by a device cloud server, wherein the first profile comprises card information of a first operator and card information of a second operator, the first operator is different from the second operator, the card information of the first operator is used for accessing a network of the first operator, and the card information of the second operator is used for accessing a network of the second operator. According to the application, the card information of multiple operators is stored through the first profile, and the network of different operators is dynamically accessed through the first profile, so that the cost can be reduced while ensuring the online experience of users, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a configuration file management method and related apparatus. Background Technology

[0002] Currently, coverage blind spots exist in the networks of a single operator. To ensure a good internet experience for users, mobile phones and other electronic devices can be configured with multiple subscriber identity module (SIM) cards from different operators and dynamically switch between them to dynamically switch the connected operator network. However, this requires configuring and using multiple SIM card interfaces and multiple SIM cards, resulting in high costs. Alternatively, the embedded SIM (eSIM) module of the electronic device can store multiple profiles from different operators. Each profile is used to access the network of its corresponding operator, and the electronic device can dynamically switch between profiles to dynamically switch the connected operator network. However, this requires a large amount of storage space in the eSIM module and requires multiple operator servers to cooperate with the electronic device in downloading profiles, resulting in high costs. Summary of the Invention

[0003] This application discloses a configuration file management method and related apparatus, which can store card information of multiple operators in the first profile of the embedded user identification eSIM module, and dynamically access the networks of different operators through the first profile. This can reduce costs and improve user experience while ensuring the user's Internet access experience.

[0004] In a first aspect, this application provides a configuration file management method applied to an electronic device including an embedded eSIM module. The method includes: receiving a first configuration file profile sent by a device cloud server, wherein the first profile includes card information of a first operator and card information of a second operator. The first operator and the second operator are different. The card information of the first operator is used to access the network of the first operator, and the card information of the second operator is used to access the network of the second operator.

[0005] The first profile is determined by the device cloud server based on the SIM card information from the first operator and the second operator. In some examples, the device cloud server downloads the SIM card information from the first operator's server and the SIM card information from the second operator's server. In other examples, the SIM card information from the first operator is purchased from the first operator and pre-installed on the device cloud server, and the SIM card information from the second operator is purchased from the second operator and pre-installed on the device cloud server.

[0006] In the above method, the first profile obtained by the electronic device from the device cloud server includes SIM card information from multiple operators. The SIM card information from different operators in the first profile is used to access the networks of different operators. Therefore, the electronic device can dynamically switch the operator network it accesses through the first profile, ensuring a good internet experience for the user. This method of storing SIM card information from multiple operators in the first profile eliminates the need for the electronic device to configure and use multiple SIM card interfaces and multiple SIM cards, resulting in lower costs. It also eliminates the need for the electronic device to store multiple profiles (one profile stores SIM card information from one operator), reducing the storage pressure on the eSIM module. Furthermore, it eliminates the need for multiple operator servers to cooperate with the electronic device in downloading multiple profiles, further reducing costs.

[0007] In one possible implementation, the method further includes: the electronic device receiving a first input from a user requesting to purchase a service card package; and in response to the first input, sending a download request to a device cloud server. This download request is used to request the download of a first profile, for example, the download request is used to request the download of the first profile corresponding to the service card package. Then, the electronic device receives the first profile sent by the device cloud server based on the download request.

[0008] In some examples, the service card plan purchased by the user refers to multiple carrier networks, and the service card plan is used to enable the user's internet access. Therefore, the first profile corresponding to the service card plan purchased by the user is used to dynamically access different carrier networks, and to enable the user's internet access based on the accessed carrier network.

[0009] In the above method, when the user actively purchases a service card package, the electronic device downloads the first profile corresponding to that service card package from the device cloud server. This can be understood as downloading the first profile required by the user when there is a need, resulting in a better user experience.

[0010] In one possible implementation, the first profile includes shared information, first difference information, and second difference information. The card information of the first operator includes both shared information and first difference information. The card information of the second operator includes both shared information and second difference information. The first difference information includes one or more types of first difference data, and the second difference information includes one or more types of second difference data. The first type of first difference data differs from the second type of second difference data. Optionally, the shared information includes one or more types of shared data, and the shared data of the same type in the card information of the first operator and the card information of the second operator are identical.

[0011] In the above method, when the eSIM module stores card information from N operators (N is a positive integer greater than 1, such as 2) through the first profile, it stores one copy of common information and N copies of difference information, instead of storing card information from N operators separately through N profiles (N profiles store N copies of common information and N copies of difference information). This reduces the storage space occupied by the eSIM module, effectively alleviates the storage pressure on the eSIM module, and reduces costs.

[0012] In one possible implementation, the first profile includes a main file MF, x basic files EF under MF, s first application-specific files ADF under MF, and t second ADF under MF, where x, s, and t are all positive integers. The x EF under MF are used to store common information, the s first ADF under MF are used to store first difference information of the first operator, and the t second ADF under MF are used to store second difference information of the second operator. The card information of the first operator includes card information of s card applications of the first operator, and the s first ADFs respectively store the card information of the s card applications of the first operator. The card information of the second operator includes card information of t card applications of the second operator, and the t second ADFs respectively store the card information of t card applications of the second operator.

[0013] In some examples, the card application includes at least one of the following types: Global Subscriber Identity Module (USIM), Code Division Multiple Access Subscriber Identity Module (CSIM), and Internet Protocol Multimedia Service Identity Module (ISIM).

[0014] In some examples, x EFs include: EF-Integrated Circuit Card Identifier (ICCID), EF-Preferred Language (PL), and EF-Application Directory (DIR). EF-ICCID stores the ICCID shared by the first and second operators. EF-PL stores the encoding for multiple languages ​​and the preferred language among them. EF-DIR stores multiple Application Identifiers (AIDs), including the AIDs of the aforementioned s first ADFs and the AIDs of the aforementioned t second ADFs.

[0015] In some examples, a first ADF or a second ADF includes: EF - International Mobile Subscriber Identity (IMSI) (used to store the IMSI), EF - Access Rule Reference (ARR) (used to store the access rule index of the base file under the ADF), and EF - Authentication Key Ki (used to store Ki).

[0016] In the above method, the eSIM module stores shared information through x EFs in the first profile, stores first difference information through the first ADF in the first profile, and stores second difference information through the second ADF in the first profile, instead of directly storing card information from N operators through N profiles, which greatly alleviates the storage pressure on the eSIM module. Furthermore, different first ADFs store card information for different card applications of the first operator, and different second ADFs store card information for different card applications of the second operator. Since the ADFs can be addressed using AIDs, obtaining card information for different card applications of different operators is more convenient, effectively improving the usability of the eSIM function.

[0017] In one possible implementation, the above method further includes: the electronic device activating a first profile in the eSIM module, for example, activating the first profile corresponding to the service card plan after receiving a user's activation of the service card plan; the electronic device accessing the network of the first operator based on the card information of the first operator in the activated first profile; and then, if the conditions for switching operator networks are met, the electronic device accessing the network of the second operator based on the card information of the second operator in the still activated first profile.

[0018] In the above method, the electronic device can activate the first profile and access different operator networks through the card information of different operators in the first profile in different scenarios. The first profile only needs to be activated once, and it remains active in different scenarios. There is no need to switch profiles (including deactivating the old profile and activating the new profile), which effectively improves the speed of switching operator networks.

[0019] In one possible implementation, the electronic device includes a mobile communication module; when the electronic device accesses the network of the first operator based on the card information of the first operator in the first profile, the mobile communication module reads common information in the first profile stored in the eSIM module, and the mobile communication module reads first difference information in the first profile stored in the eSIM module, and then the mobile communication module accesses the network of the first operator based on the read common information and first difference information; when the electronic device accesses the network of the second operator based on the card information of the second operator in the first profile, the mobile communication module reads second difference information in the first profile stored in the eSIM module, and then the mobile communication module accesses the network of the second operator based on the read common information and second difference information.

[0020] In the above method, after the electronic device activates the first profile, it can read the common information and the first difference information in the first profile and access the network of the first operator. When it needs to switch to the network of the second operator, it is not necessary to read the common information in the first profile again. It is only necessary to read the second difference information in the first profile to access the network of the second operator. This speeds up the switching of operator networks and improves the user's Internet experience.

[0021] In one possible implementation, the first profile includes a median subarray (MF), x element-free (EF) arrays under the MF, s first active digital subarrays (ADFs) under the MF, and t second active digital subarrays (ADFs) under the MF, where x, s, and t are all positive integers. The x EF arrays under the MF are used to store shared information, the s first ADFs under the MF are used to store first difference information of the first operator, and the t second ADFs under the MF are used to store second difference information of the second operator. When the mobile communication module reads the shared information in the first profile stored in the eSIM module, the mobile communication module reads the data stored in the x EF arrays from the eSIM module. When the mobile communication module reads the first difference information in the first profile stored in the eSIM module, the mobile communication module reads the data stored in the third ADF array of the first profile from the eSIM module based on the first AID. The s first ADF arrays include the data stored in the third ADF array of the first profile. The third ADF corresponds to the first AID and is used to store card information of the card application corresponding to the first AID of the first operator. For example, the third ADF is a preset default ADF among s first ADFs, and the card application corresponding to the first AID is the preset default card application of the first operator. When the mobile communication module reads the second difference information in the first profile stored in the eSIM module, the mobile communication module reads the data stored in the fourth ADF of the first profile from the eSIM module based on the second AID. The aforementioned t second ADFs include the fourth ADF, which corresponds to the second AID and is used to store card information of the card application corresponding to the second AID of the second operator. For example, the fourth ADF is a preset default ADF among t second ADFs, and the card application corresponding to the second AID is the preset default card application of the second operator.

[0022] In the above method, the mobile communication module can read different ADFs in the first profile based on different AIDs. The AIDs are stored in the shared information. Only one reading of the shared information is needed to realize subsequent handover to read different ADFs, reducing unnecessary interaction between the mobile communication module and the eSIM module. The reading process is efficient and reliable, so the handover process of the operator network is also efficient and reliable.

[0023] In one possible implementation, the method further includes: after the electronic device accesses the network of the first operator based on the card information of the first operator in the first profile, displaying a first identifier of the mobile communication network, the first identifier indicating the first operator, for example, the first identifier is used to prompt the user that the electronic device has accessed the network of the first operator; after the electronic device accesses the network of the second operator based on the card information of the second operator in the first profile, displaying a second identifier of the mobile communication network, the second identifier indicating the second operator, for example, the second identifier is used to prompt the user that the electronic device has accessed the network of the second operator.

[0024] In the above method, when accessing different operator networks based on the card information of different operators in the first profile, the identifier of the operator corresponding to the currently accessed network can be displayed, allowing users to intuitively feel the switching of operator networks, which greatly improves the experience for users who want to perceive network switching.

[0025] In one possible implementation, the method further includes: after the electronic device accesses the network of the first operator based on the card information of the first operator in the first profile, displaying a third identifier of the mobile communication network; after the electronic device accesses the network of the second operator based on the card information of the second operator in the first profile, displaying a third identifier of the mobile communication network; wherein the third identifier indicates the first virtual operator, for example, the third identifier is used to prompt the user that the electronic device has accessed the network of the first virtual operator.

[0026] In the above method, when accessing different operator networks based on the card information of different operators in the first profile, the same virtual operator's logo can be displayed, and the process of switching operator networks can be made invisible. The network perceived by the user remains stable, which greatly improves the experience for users who are prone to anxiety about network switching.

[0027] In one possible implementation, the method further includes: when the electronic device receives a first notification message sent by a communication map server, determining that the conditions for switching operator networks are met, wherein the first notification message indicates that the electronic device accesses a second operator, the communication map server is used to maintain a first communication map, the first communication map includes information about the network of the first operator (e.g., coverage and signal quality) and information about the network of the second operator (e.g., coverage and signal quality), and the first notification message is determined based on the first communication map; or, when the electronic device detects that a first signal quality parameter is less than a quality threshold, determining that the conditions for switching operator networks are met, wherein the first signal quality parameter is used to characterize the signal quality of the network of the first operator accessed by the electronic device.

[0028] In some examples, when the electronic device and the communication map server maintain communication, the electronic device receives the first notification information sent by the communication map server. When the electronic device cannot maintain communication with the communication map server, it automatically detects whether the first signal quality parameter is less than the quality threshold.

[0029] In the above methods, there are multiple ways to determine whether the conditions for switching operator networks are met. For example, it can be determined by the notification information returned by the communication map server, which is based on the first communication map and is more reliable. Another example is self-detection, which can be implemented even without connecting to the communication map server and has a wide range of applications.

[0030] Secondly, this application provides an electronic device, including a transceiver, a processor, and a memory; the memory is used to store a computer program, and the processor calls the computer program to enable the communication device to execute the configuration file management method provided in the first aspect and any implementation thereof.

[0031] Thirdly, this application provides an electronic device including a mobile communication module and an eSIM module. The mobile communication module is used to execute the steps performed by the mobile communication module in the configuration file management method provided in the first aspect and any implementation of the first aspect. The eSIM module is used to execute the steps performed by the eSIM module in the configuration file management method provided in the first aspect and any implementation of the first aspect.

[0032] Fourthly, this application provides a computer storage medium including a computer program, which, when executed by a processor, is used to implement the configuration file management method provided by the first aspect and any implementation thereof.

[0033] Fifthly, this application provides a computer program product, including a computer program that, when the computer program runs on a processor, implements the configuration file management method provided by the first aspect and any implementation thereof.

[0034] In a sixth aspect, this application provides a chip system including a processing circuit and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processing circuit. The processing circuit is used to execute the code instructions to perform the configuration file management method provided in the first aspect and any implementation thereof.

[0035] In a seventh aspect, this application provides an electronic device that includes the methods or apparatus described in any aspect or embodiment of this application. The electronic device is, for example, a chip.

[0036] It should be understood that the descriptions of technical features, technical solutions, beneficial effects, or similar language in this application do not imply that all features and advantages can be achieved in any single implementation. Rather, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution, or beneficial effect is included in at least one implementation. Therefore, the descriptions of technical features, technical solutions, or beneficial effects in this application do not necessarily refer to the same implementation. Furthermore, the technical features, technical solutions, and beneficial effects described in this application can be combined in any suitable manner. Those skilled in the art will understand that this application can be implemented without one or more specific technical features, technical solutions, or beneficial effects of a particular implementation. In other implementations, additional technical features and beneficial effects may be identified in specific implementations that do not embody all implementations. Attached Figure Description

[0037] The following describes the accompanying drawings used in this application.

[0038] Figure 1 This is a schematic diagram of the hardware structure of an electronic device provided in this application;

[0039] Figure 2 This is a schematic diagram of the architecture of a communication system provided in this application;

[0040] Figure 3 This is a schematic diagram of the architecture of another communication system provided in this application;

[0041] Figure 4 This is a schematic diagram of the architecture of an electronic device provided in this application;

[0042] Figures 5A-5E , Figures 6A-6C These are some user interface diagrams provided in this application;

[0043] Figure 7 This is a flowchart illustrating a configuration file management method provided in this application;

[0044] Figure 8 This is a flowchart illustrating yet another configuration file management method provided in this application;

[0045] Figure 9 This is a flowchart illustrating yet another configuration file management method provided in this application;

[0046] Figure 10 This is a schematic diagram of the structure of a communication device provided in this application. Detailed Implementation

[0047] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings. The terminology used in the implementation section of this application is only for explaining specific embodiments of this application and is not intended to limit this application.

[0048] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0049] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0050] The following describes an electronic device provided by an embodiment of this application.

[0051] Figure 1 This is a schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of this application.

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

[0053] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0054] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0055] The processor 110 may also include a memory for storing instructions and data. In one embodiment, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

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

[0057] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging implementations, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging implementations, the charging management module 140 receives wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device 100 via the power management module 141.

[0058] The power management module 141 connects 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, providing power to the processor 110, internal memory 121, display screen 194, camera 193, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In another embodiment, the power management module 141 can also be located within the processor 110. In yet another embodiment, the power management module 141 and the charging management module 140 can be housed in the same device.

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

[0060] Antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. When an antenna covers multiple communication frequency bands for different communication methods, it can be called a cooperative antenna. For an explanation of cooperative antennas, please refer to the descriptions of antenna cooperative situations one, two, and three above. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In another embodiment, the antenna can be used in conjunction with a tuning switch.

[0061] The mobile communication module 150 can provide wireless communication solutions for applications on the electronic device 100, including second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G) mobile communication technologies. The mobile communication module 150 may include at least one filter, switch, power amplifier, low-noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In one embodiment, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In another embodiment, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0062] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through audio devices (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In one embodiment, the modem processor may be a separate device. In another embodiment, the modem processor may be independent of the processor 110 and housed within the same device as the mobile communication module 150 or other functional modules.

[0063] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), and SparkLink Alliance-standard wireless communication technologies (such as SLE and SLB). 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 antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0064] In one embodiment, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

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

[0066] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In one embodiment, electronic device 100 may include N displays screens 194, where N is a positive integer greater than 1.

[0067] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0068] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, converting it into an image visible to the naked eye. The ISP can also perform algorithmic optimization on image noise, brightness, etc. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In one embodiment, the ISP can be set in the camera 193.

[0069] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In one embodiment, electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0070] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when electronic device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.

[0071] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. Thus, electronic device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0072] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0073] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0074] Internal memory 121 can be used to store computer executable program code, which includes instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 110 executes various functional applications and data processing of electronic device 100 by running instructions stored in internal memory 121 and / or instructions stored in memory located in the processor.

[0075] Electronic device 100 can implement audio functions through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor. Electronic device 100 can also implement audio functions through connected Bluetooth devices, such as music playback and recording.

[0076] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In one embodiment, the audio module 170 can be located in the processor 110, or some functional modules of the audio module 170 can be located in the processor 110.

[0077] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or make hands-free calls through the speaker 170A.

[0078] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the electronic device 100 answers a telephone call or voice message, the receiver 170B can be brought close to the ear to listen to the voice.

[0079] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Electronic device 100 may have at least one microphone 170C. In another embodiment, electronic device 100 may have two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In yet another embodiment, electronic device 100 may have three, four, or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, among other functions.

[0080] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In one embodiment, pressure sensor 180A can be disposed on display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. Electronic device 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 194, electronic device 100 detects the intensity of the touch operation based on pressure sensor 180A. Electronic device 100 can also calculate the touch position based on the detection signal from pressure sensor 180A. In one embodiment, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example, when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

[0081] The gyroscope sensor 180B can be used to determine the motion posture of the electronic device 100. The barometric pressure sensor 180C is used to measure air pressure. The magnetic sensor 180D includes a Hall effect sensor. The accelerometer sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in various directions (generally three axes). The distance sensor 180F is used to measure distance. The proximity sensor 180G may include, for example, a light-emitting diode (LED) and a photodetector, such as a photodiode. The LED may be an infrared LED. The ambient light sensor 180L is used to sense ambient light intensity. The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can utilize the collected fingerprint characteristics to achieve fingerprint unlocking, accessing application locks, fingerprint photography, fingerprint answering of calls, etc. The temperature sensor 180J is used to detect temperature. The bone conduction sensor 180M can acquire vibration signals.

[0082] Touch sensor 180K, also known as a "touch device," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In another embodiment, touch sensor 180K can also be located on the surface of electronic device 100, in a different position than display screen 194.

[0083] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100. Motor 191 can generate vibration prompts. Indicator 192 can be an indicator light, used to indicate charging status, battery level changes, and also to indicate messages, missed calls, notifications, etc.

[0084] The eSIM module 195 can be embedded in the electronic device 100, for example, in a non-removable form, such as by embedding it inside the motherboard of the electronic device 100. It can replace a physical subscriber identity module (SIM) card (i.e., a physical SIM, pSIM) for interaction between the electronic device 100 and the network, enabling functions such as calls and data communication. However, the eSIM module 195 is generally much smaller. Unlike a physical SIM card, the eSIM module 195 allows for easy switching of phone numbers or changing of operators because the information on the eSIM module 195 is rewritable. The eSIM module 195 can be remotely configured via over-the-air (OTA) technology, enabling the downloading, activation, deactivation, and deletion of profiles.

[0085] The eSIM module 195 can store one or more profiles. A profile can be used to store card information of a non-physical SIM card (referred to as an eSIM) to provide, for example, voice and / or data services. The profile can be used by the electronic device 100 to access a mobile communication network, thereby enabling functions such as voice and data communication. In some embodiments, the electronic device 100 can activate a profile in the eSIM module 195 and register with the network using the activated profile. For example, the electronic device 100 can use the card information stored in the activated profile to perform legitimacy authentication (referred to as authorization) with the corresponding operator. After successful authentication, the electronic device 100 is allowed to access the mobile communication network.

[0086] The following examples illustrate the file types involved in the file structure of some profiles:

[0087] The master file (MF) is the unique identifier for each profile. For example, an MF might be designated as 3F00. The MF can be considered the root directory of the profile; all other files within the profile reside within the MF directory.

[0088] A dedicated file (DF) is a file system used to define a profile. A profile may have one or more DFs, or none at all. A DF is a directory under a file system (MF). A DF can be a directory under an MF or a directory under another DF.

[0089] Application-Dedicated Files (ADFs) are a special type of DF. Currently, a profile can store card information for an operator's eSIM. This profile can include one or more ADFs, any one of which can be used to store all files (including EF, optional, and DF) of a virtual application (also known as a card application) for that operator's eSIM. Card applications include, but are not limited to, the Universal Subscriber Identity Module (USIM), the Internet Protocol (IP) Multimedia Services Identity Module (ISIM), and the CDMA2000 Subscriber Identity Module (CSIM). USIM is typically used in 3G and 4G networks, supporting more complex encryption algorithms and providing a higher level of security. ISIM is typically used in LTE networks, especially those providing LTE Voice over LTE (VoLTE) services, supporting IP network authentication and security services. CSIM is used in CDMA2000 networks and supports services specific to CDMA2000 networks, such as multimedia broadcast multicast service (MBMS).

[0090] An elementary file (EF) is a basic file that a profile can have. An EF is a basic file under MF or DF, and it is the basic unit used to store data.

[0091] In this embodiment, the profile identifier can be an issuer security domain profile-application identification (ISD P-AID), and different profiles have different ISD P-AIDs. The ADF identifier can be an application identifier (AID), which can be used to address / identify the ADF.

[0092] It should be understood that the electronic device shown in the embodiments of this application is merely an example, and the electronic device may have more or fewer components than those shown in the above embodiments, may combine two or more components, or may have different component configurations. The various components shown in the figures can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits. For example, electronic device 100 may include not only... Figure 1 The eSIM module 195 shown may further include a SIM card interface for connecting a pSIM. The pSIM can be inserted into or removed from the SIM card interface to make contact with or separate from the electronic device 100. The pSIM may include, but is not limited to, second form factor SIMs (2FF SIMs), third form factor SIMs (3FF SIMs), and fourth form factor SIMs (4FF SIMs). The electronic device 100 can authenticate with the communication service provider via the pSIM connected through the SIM card interface. Once authentication is successful, the electronic device 100 is allowed to access the mobile communication network.

[0093] Currently, after a user signs a contract or subscription with a certain operator, the electronic device 100 can download the operator's profile from the operator's server. This profile is used to store the operator's SIM card information and is used by the electronic device 100 to access the operator's network. However, the coverage of a single operator's network has blind spots. For example, users have a poor internet experience in areas near blind spots, as they cannot connect to the operator's network and therefore cannot access the internet. To ensure a good internet experience, the electronic device 100 can support multiple SIM cards and multiple standby modes. In one implementation, a user can sign a contract or subscription with multiple operators. Therefore, the electronic device 100 can download different operator profiles from the servers of different operators and store multiple profiles of different operators in the eSIM module. The electronic device 100 can dynamically switch the profile it uses, thereby dynamically switching the connected operator network. For example, the electronic device 100 can first activate the profile of operator A and access operator A's network based on this profile. After the modem of the electronic device 100 detects a deterioration in the signal quality of the current profile, the electronic device 100 can activate the profile of operator A, then activate the profile of operator B, and then access operator B's network based on this profile. This implementation method has many drawbacks. For example, it requires storing multiple profiles in the eSIM module, which consumes a lot of storage space in the eSIM module and is costly. It also requires users to sign contracts or subscribe with multiple operators, and requires servers of multiple operators to cooperate with electronic devices to download profiles, resulting in a poor user experience and high costs. Furthermore, when switching connected operator networks, it is necessary to switch profiles, and the process of switching profiles requires activating the old profile first and then activating the new profile (which takes at least 5 seconds), resulting in a slow speed of switching operator networks.

[0094] In another implementation, electronic device 100 can be configured with multiple pSIMs from different operators and dynamically switch between the pSIMs used, thereby dynamically switching the connected operator network. However, this requires electronic device 100 to configure and use multiple SIM card interfaces and multiple pSIMs, which is costly.

[0095] This application provides a configuration file management method applicable to an electronic device 100 including an eSIM module 195. The eSIM module 195 of the electronic device 100 can store a first profile, which may include card information from N operators, where any two of these N operators are different, and N is a positive integer greater than 1. For example, the first profile including card information from N operators can be called an extended SIM (XSIM) profile, a mixed SIM (XSIM) profile, or a variable / unknown SIM (XSIM) profile. Compared to the above two implementations, the first profile provided in this application can effectively reduce costs.

[0096] The first profile can include shared information and N different information segments, each corresponding to one of the N operators. The shared information consists of identical information from the card information of the N operators, while the different information consists of unique information from the card information of the N operators. Within the card information of any of the N operators, the card information of any one operator can include shared information and the different information from the N different information segments corresponding to that operator. The eSIM module 195 can store the card information of N different operators through the first profile (which stores one set of shared information and N sets of different information) instead of storing the card information of N different operators through N profiles (which store N sets of shared information and N sets of different information). This reduces the storage space occupied by the eSIM module 195, effectively alleviating the storage pressure on the eSIM module 195 and lowering costs.

[0097] The first profile can be downloaded by the electronic device 100 from the device cloud server. The first profile can be determined by the device cloud server based on the card information of N operators. Therefore, there is no need for the user to sign a contract or subscription with N operators, nor is there a need for the servers of N operators to cooperate with the electronic device 100 to download the profile, which improves the user experience and reduces costs.

[0098] In this embodiment, the electronic device 100 can activate the first profile and access different operator networks through the card information of different operators in the first profile in different scenarios. The first profile remains active in different scenarios without the need to switch profiles, which effectively improves the speed of switching operator networks.

[0099] For example, an operator's card information may include, but is not limited to, at least one of the following types of card data (card data can also be referred to as data): International Mobile Subscriber Identity (IMSI) (e.g., can be used for authentication), Key Identifier (Ki) (e.g., can be used for authentication), Authentication Key OPC (OPC is a key calculated based on Ki and the operator variant algorithm configuration field (OP)) (e.g., can be used for authentication), Hash value, Integrated Circuit Card Identity (ICCID), Administrative Data (AD), Broadcast Control Channel (BCCH), Forbidden PLMN (FPLMN), Location Information (LOCI), Packet Switched Location Information (PSLOCI), General Packet Radio Service (GPRS) Location Information (LOCIGPRS), and User Controlled PLMN Selector with Access Technology. Technology, PLMNWACT), access control class (ACC), enabled services table (EST), higher priority PLMN search period (HPPLMN), equivalent home PLMN (EHPLMN), universal subscriber identity module (USIM) service table (UST), network parameters,NETPAR), initialization values ​​for hyperframe number (STARTHFN), maximum value of start (THRESHOLD), short message service parameters (SMSP), and short message status (SMSS).

[0100] Figure 2 This is a schematic diagram of the architecture of a communication system 10 provided in an embodiment of this application.

[0101] like Figure 2 As shown, the communication system 10 may include an electronic device 100, a device cloud server 200, and multiple operator servers, including but not limited to operator A server 300 and operator B server 400.

[0102] In this application embodiment, the electronic device 100 can be any of the following: mobile phone, tablet computer, handheld computer, desktop computer, laptop computer, ultra-mobile personal computer (UMPC), netbook, cellular phone, personal digital assistant (PDA), as well as smart home devices such as smart screens and smart speakers, wearable devices such as smart bracelets, smartwatches, and smart glasses, extended reality (XR) devices such as augmented reality (AR), virtual reality (VR), and mixed reality (MR), in-vehicle devices, or smart city devices.

[0103] The device cloud server 200 can be used to provide a first profile download service for the electronic device 100. In some embodiments, the device cloud server 200 may include a device data server for providing the first profile download service. For example, the device data server may be a subscription manager-data preparation server (SM-DP) or a subscription manager-data preparation plus server (SM-DP+). In some embodiments, the device cloud server 200 can also be used to provide application services for the electronic device 100. For example, the device cloud server 200 may provide application services for a first network application, and the electronic device 100 with the first network application installed can access the device cloud server 200 and interact with it.

[0104] The operator's server may include, but is not limited to, a data server. The data server can be used to provide download services for the current operator's card information. For example, the data server is SM-DP or SM-DP+.

[0105] In some embodiments, the device cloud server 200 can purchase SIM card information from multiple operators. In some examples, the device cloud server 200 can download SIM card information from multiple operator servers, which can be understood as "online downloading" of operator SIM card information. Not limited to this, in other examples, the SIM card information from multiple operators can be purchased and pre-installed in the device cloud server 200, which can be understood as "offline pre-installation" of operator SIM card information. Then, the device cloud server 200 can analyze and process this SIM card information from multiple operators and encapsulate it into a first profile. The device cloud server 200 can store the first profile; for example, the device data server within the device cloud server 200 stores the first profile.

[0106] In some embodiments, the electronic device 100 can download a first profile from the device cloud server 200 and store the first profile in the eSIM module 195. For example, the electronic device 100 can download the first profile from the device data server in the device cloud server 200. The first profile may include card information from N different operators, where N is a positive integer greater than 1. This embodiment uses N=2 as an example; therefore, the first profile includes card information from a first operator and card information from a second operator. The first and second operators are different; for example, the first operator is operator A, and the second operator is operator B. After activating the first profile, the electronic device 100 can dynamically obtain card information from different operators from the first profile to access different operator networks, that is, dynamically switch the card information of the operator in the first profile, thereby dynamically switching the connected operator network.

[0107] Figure 3 This is a schematic diagram of the architecture of another communication system 10 provided in the embodiments of this application.

[0108] like Figure 3 As shown, the communication system 10 may include an electronic device 100 and a device cloud server 200, as described in the relevant descriptions and... Figure 2 similar.

[0109] like Figure 3 As shown, the architecture of electronic device 100 may include processor 101, mobile communication module 102, and eSIM module 103. Processor 101 may include application layer and framework layer.

[0110] The application layer of processor 101 may include one or more applications, such as Figure 3 The first network application is shown. In some embodiments, the first network application can be used to provide services such as purchasing, activating, deactivating, and deleting service card packages. After a user purchases a service card package, the electronic device 100 can download and store the service card package profile. After a user activates a service card package, the electronic device 100 can activate the service card package profile and use it for network registration. After a user deactivates a service card package, the electronic device 100 can deactivate the service card package profile. After a user deletes a service card package, the electronic device 100 can delete the service card package profile. The application in this embodiment can also be replaced with other forms of software such as mini-programs or atomic services.

[0111] The framework layer of processor 101 can be used to provide application programming interfaces (APIs) and programming frameworks for applications in the application layer. The framework layer may include some predefined functions, such as... Figure 3 The local profile assistant (LPA) service is shown. The LPA service can be used to manage profiles in the eSIM module 103, such as downloading, activating, deactivating, and deleting them. In some embodiments, the LPA service may include a local profile download (LPD) service and a local user interface (LUI) service. The LPD service can provide profile download services. The LUI service can provide services for users to perform profile management; for example, the LUI service can obtain user operation events related to profiles from the application layer and send profile control commands to the eSIM module 103 based on the obtained operation events.

[0112] The mobile communication module 102 can be used to implement the mobile communication function of the electronic device 100. For example, the mobile communication module 102 includes a modem. The description of the eSIM module 103 and... Figure 1 The description of eSIM module 195 is similar. In some embodiments, mobile communication module 102 and eSIM module 103 can communicate via standard protocols (e.g., International Organization for Standardization (ISO) standards). In some embodiments, upper-layer services such as application layer and framework layer in processor 101 can communicate with eSIM module 103 through mobile communication module 102. For example, LPA service / LPD service / LUI service communicates with eSIM module 103 through mobile communication module 102 to achieve profile management in eSIM module 103.

[0113] Next, through Figure 3 The configuration file management method provided in the embodiments of this application is illustrated by way of example.

[0114] like Figure 3In step 1, as shown, the user purchases a service card package through the first network application of electronic device 100, and the first network application of electronic device 100 downloads the first profile from device cloud server 200. The first network application can download the first profile from device cloud server 200 via the LPD service. In some examples, within GSMA standards (e.g., SGP), the LPD service of electronic device 100 can download the first profile from device cloud server 200 via the ES9+ interface, which can be used to provide secure transmission of the profile between device cloud server 200 and the LPD service.

[0115] like Figure 3 In step 2, as shown, the first network application of electronic device 100 sends a first profile to eSIM module 103, and eSIM module 103 stores the first profile. The first network application can send the first profile to eSIM module 103 via LPD service. LPD service can also send the first profile to eSIM module 103 via mobile communication module 102. In some examples, in GSMA standards (e.g., SGP), the LPD service of electronic device 100 uses the ES10b interface to enable LPA service to transmit the downloaded first profile to eSIM module 103.

[0116] like Figure 3 In step 3, as shown, the user activates a service card plan through the first network application of electronic device 100. The first network application of electronic device 100 activates the first profile in eSIM module 103 through LUI service. Specifically, LUI service can instruct eSIM module 103 to activate the first profile through mobile communication module 102, and eSIM module 103 activates the first profile upon this instruction. In some examples, in GSMA standards (e.g., SGP), the LUI service of electronic device 100 uses the ES10c interface to enable LPA service to instruct eSIM module 103 to activate the first profile.

[0117] like Figure 3As shown in step 4, in different scenarios, the mobile communication module 102 reads the card information of different operators from the first profile stored in the eSIM module 103 for network access. In some examples, in scenario 1, the mobile communication module 102 reads the card information of operator A from the first profile in the eSIM module 103 and uses the read card information of operator A to access the network of operator A. In scenario 2, the mobile communication module 102 reads the card information of operator B from the first profile in the eSIM module 103 and uses the read card information of operator B to access the network of operator B. That is, in different scenarios, the mobile communication module 102 can dynamically read the card information of different operators and use the card information of different operators to access the networks of different operators, thereby dynamically switching the accessed operator network. The first profile remains active in different scenarios, and there is no need to re-execute when switching operator networks. Figure 3 Step 3 is shown.

[0118] In some examples, the mobile communication module 102 and the eSIM module 103 can communicate via a standard protocol (e.g., the ISO standard), i.e., by exchanging application protocol data units (APDUs). The mobile communication module 102 can read the operator's card information included in the first profile from the eSIM module 103 based on the standard protocol communication process / APDU interaction process.

[0119] The following section provides an example of the file structure of the first profile in the eSIM module.

[0120] Figure 4 This is a schematic diagram of the architecture of an electronic device 100 provided in an embodiment of this application.

[0121] like Figure 4 As shown, the electronic device 100 may include a mobile communication module 102 and an eSIM module 103. The eSIM module 103 may store one or more profiles. Figure 4 The following example illustrates the storage of a first profile by the eSIM module 103. This embodiment of the application uses the example of the first profile including card information from a first operator (e.g., operator A) and card information from a second operator (e.g., operator B) for illustration. The first profile includes shared information, first difference information corresponding to operator A, and second difference information corresponding to operator B. The card information from operator A includes shared information and the first difference information, and the card information from operator B includes both shared information and the second difference information.

[0122] like Figure 4As shown, the first profile may include a File Explorer (MF), x Element-Defined Files (EFs) under the MF, a USIM1 file (USIM1 file is an ADF) under the MF, a USIM2 file (USIM2 file is an ADF) under the MF, y EFs under the USIM1 file, and z EFs under the USIM2 file. x, y, and z are positive integers, and y and z can be the same or different. The x EFs under the MF store common information in the first profile. USIM1 corresponds to operator A, and USIM2 corresponds to operator B. The USIM1 file under the MF (including y EFs) stores the first difference information corresponding to operator A in the first profile, and the USIM2 file under the MF (including z EFs) stores the second difference information corresponding to operator B in the first profile.

[0123] In some embodiments, shared information may include one or more types of shared data. Optionally, the same type of shared data in the card information of operator A and the card information of operator B is the same. Optionally, one type of shared data can be stored in one EF under MF, and different types of shared data can be stored in different EFs under MF. For example, as... Figure 4 As shown, the x EFs under MF can include, but are not limited to, EF-ICCID, EF-preferred languages ​​(PL), and EF-application directory (DIR). EF-ICCID stores the common data ICCIDs in the first profile. EF-PL stores the encodings of multiple languages, defining the preferred languages ​​in order of priority. EF-DIR stores multiple AIDs, which are identifiers for multiple ADFs in the first profile. ADFs in the first profile can be selected using their corresponding AIDs. EF-DIR can be understood as storing the mapping between AIDs and ADFs. For example, EF-DIR stores AID1 corresponding to USIM1 and AID2 corresponding to USIM2; AID1 is used to select USIM1, and AID2 is used to select USIM2.

[0124] In some embodiments, the first difference information may include one or more types of first difference data, and the second difference information may include one or more types of second difference data. The first type of first difference data in the first difference information is different from the first type of first difference data in the second difference information; that is, the same type of difference data in the card information of operator A and the card information of operator B are different. Optionally, one type of difference data can be stored through one EF (Entity Framework), and different types of difference data can be stored through different EFs. For example, as... Figure 4As shown, the y EFs in the USIM1 file corresponding to operator A can include, but are not limited to, EF-IMSI1, EF-Access Rule Reference (ARR)1, and EF-Ki1. Similarly, the z EFs in the USIM2 file corresponding to operator B can include, but are not limited to, EF-IMSI2, EF-ARR2, and EF-Ki2. Specifically, EF-IMSI1 in the USIM1 file stores IMSI1 from operator A's card information, and EF-IMSI2 in the USIM2 file stores IMSI2 from operator B's card information. EF-ARR1 in the USIM1 file stores the access rule index of the basic files in the USIM1 file, and EF-ARR2 in the USIM2 file stores the access rule index of the basic files in the USIM2 file. EF-Ki1 in the USIM1 file stores Ki1 from operator A's card information, and EF-Ki2 in the USIM2 file stores Ki2 from operator B's card information.

[0125] In some embodiments, the eSIM module 103 can activate a first profile. The mobile communication module 102 can interact with the eSIM module 103 via, for example, a standard protocol, using an APDU and reading the first profile. An implementation flow is illustrated below: Figure 4 In step 1, as shown, the mobile communication module 102 reads the shared information in the first profile from the eSIM module 103, that is, the mobile communication module 102 reads the data stored in x EFs (e.g., EF-ICCID, EF-PL, EF-DIR) under the MF in the first profile. Figure 4 In step 2, as shown, in scenario 1, the mobile communication module 102 selects and reads the difference information 1 stored in the USIM1 file. That is, the mobile communication module 102 selects the USIM1 file in the first profile, and then reads the data stored in the y EFs (e.g., EF-IMSI1, EF-ARR1, EF-Ki1) under the USIM1 file. Therefore, in scenario 1 (e.g., within the coverage area of ​​operator A's network), the mobile communication module 102 can use the read common information and difference information 1 to access operator A's network. Figure 4As shown in step 3, in scenario 2, the mobile communication module 102 selects and reads the difference information 2 stored in the USIM2 file. That is, the mobile communication module 102 selects the USIM2 file in the first profile, and then the mobile communication module 102 reads the data stored in the z EFs (e.g., EF-IMSI2, EF-ARR2, EF-Ki2) under the USIM2 file. Therefore, in scenario 2 (e.g., within the coverage area of ​​operator B's network), the mobile communication module 102 can use the read common information and difference information 2 to access operator B's network.

[0126] Not limited to Figure 4 In the illustrated embodiments, in other embodiments, the first profile may further include more ADFs, and multiple ADFs may correspond to the same operator. For example, the first profile includes card information from a first operator and card information from a second operator. The card information from the first operator includes card information for *s* card applications of the first operator, and the card information from the second operator includes card information for *t* card applications of the second operator, where *s* and *t* are positive integers. The first profile may include *s* first ADFs and *t* second ADFs. The *s* first ADFs respectively store card information for the *s* card applications of the first operator, and the *t* second ADFs respectively store card information for the *t* card applications of the second operator. For example, the *s* first ADFs include USIM1, ISIM1, and CSIM1, and the *t* second ADFs include USIM2, ISIM2, and CSIM2. The EF-DIR under the MF in the first profile may store the AIDs corresponding to the *s* first ADFs and the AIDs corresponding to the *t* second ADFs.

[0127] Not limited to Figure 4 In the embodiments shown, the first profile may further include additional operator ADFs in other embodiments. For example, the first profile may include N ADFs under the MF, each storing difference information for one of the N operators.

[0128] The following describes, by way of example, the application scenarios and user interfaces of the embodiments of this application.

[0129] Figures 5A-5B This is a schematic diagram of a user interface for purchasing a service card package provided in an embodiment of this application.

[0130] like Figure 5AAs shown, the electronic device 100 can display a user interface 510 for a first network application. The user interface 510 may include a status bar 511 at the top, a search bar (for searching for data plans to a desired destination), a recommendation list 512, a display bar (for displaying advertising content), a trip bar (for viewing user trip information), and a menu bar 513 at the bottom. The status bar 511 at the top may include a pSIM / eSIM signal identifier 511A, a Wi-Fi network signal identifier, battery level, and time information. The pSIM / eSIM signal identifier 511A indicates that the electronic device 100 is currently connected to a 5G network with four signal bars (full bars). The Wi-Fi network signal identifier indicates that the electronic device 100 is currently connected to a Wi-Fi network with four signal bars (full bars). The recommendation list 512 is used to recommend different data plans, such as a recommendation control 512A for a "global" data plan. The menu bar 513 may include a "Recommended" control 513A and a "My" control 513B. The "Recommended" control 513A is selected, indicating that the user interface 510 is currently displaying the page corresponding to the "Recommended" control 513A. The "My" control 513B can be used to trigger the display of user information, such as purchased data plans, order details, favorites, and settings. Users can purchase the required data plans (i.e., the aforementioned service card plans) through the first network application, and users can activate the purchased data plans to access the internet.

[0131] like Figure 5B As shown, electronic device 100 can display user interface 520 of a first network application. In some examples, user interface 520 can be an electronic device 100 responding to an action on... Figure 5A The user interface 510 shows the recommended control 512A's user operation (e.g., touch click operation). The user interface 520 may include information on "Global 1-Month" data plans, such as a display bar 521 for the standard plan and a display bar 522 for the upgraded plan. Display bar 521 may include the description of the standard plan "Single Carrier Coverage" and purchase option 521A, which may include the purchase amount "29.9 yuan per month". Display bar 522 may include the description of the upgraded plan "Multiple Carrier Coverage, providing multiple network guarantees, more stable signal, faster internet speed", and purchase option 522A, which may include the purchase amount "49.9 yuan per month".

[0132] In some embodiments, a user can purchase the aforementioned standard data plan. The electronic device 100 can receive user actions (e.g., touch clicks) applied to the purchase option 521A in the display bar 521 of the standard data plan. In response to this user action, the electronic device 100 can display a payment interface. When the user successfully pays through the payment interface, the purchase of the standard data plan is successful. At this time, the electronic device 100 can download the profile corresponding to the standard data plan. This profile may include a carrier's SIM card information, and the electronic device 100 can subsequently access the carrier's network through the SIM card information in the profile.

[0133] In some embodiments, a user can purchase the aforementioned upgrade package. The electronic device 100 can receive user actions (e.g., touch clicks) applied to the purchase option 522A in the display bar 522 of the upgrade package. In response to the user action, the electronic device 100 can display a payment interface. When the user successfully pays through the payment interface, the upgrade package purchase is successful. At this time, the electronic device 100 can download the profile corresponding to the upgrade package (e.g., the first profile mentioned above). The profile corresponding to the upgrade package can include card information from multiple different operators. The electronic device 100 can subsequently dynamically switch the network of the accessing operator using the different operator card information in the profile.

[0134] Figures 5C-5D This is a schematic diagram of the user interface for enabling a service card package according to an embodiment of this application.

[0135] like Figure 5C As shown, the electronic device 100 can display a user interface 530 of a first network application. In some examples, the user interface 530 may be a response received by the electronic device 100 from an application... Figure 5AThis is displayed after a user operation (e.g., a touch click) on the "My" control 513B in the user interface 510. The user interface 530 may include a status bar 531 at the top, which may include the eSIM signal identifier 531A, battery level, and time information. The user interface 530 may be used to display data plan orders purchased by the current account, such as a display bar 532 for a "Global 1-Month" data plan and a display bar 533 for a "Country C 10GB Data" data plan. Display bar 532 may include a toggle control 532A, a plan description "Upgrade Plan (Multi-Operator Coverage)", and a status message "Enabled". The toggle control 532A is used to turn the "Global 1-Month" data plan displayed in display bar 532 on or off. Display bar 533 may include a toggle control 533A, a plan description "Standard Plan (Single-Operator Coverage)", and a status message "Disabled". The toggle control 533A is used to turn the "Country C 10GB Data" data plan displayed in display bar 533 on or off. Figure 5C The "Global 1-Month" data plan shown is enabled. Figure 5C The "C Country 10GB Data Plan" shown is not enabled.

[0136] like Figure 5C As shown, when the "Global 1-Month Data Plan" displayed in the display bar 532 is active, the electronic device 100 can activate the first profile corresponding to this data plan and use the SIM card information of operator A in the first profile to access operator A's network. At this time, the signal indicator 531A in the status bar 531 shown in the user interface 530 of the electronic device 100 includes the characters "Operator A", indicating that the electronic device 100 is currently accessing operator A's network with 4 signal bars (i.e., full bars). In some embodiments, when the electronic device 100 determines that it needs to switch to operator B's network, for example, when the electronic device 100 moves from the coverage area of ​​operator A's network to the coverage area of ​​operator B's network, it can use the SIM card information of operator B in the activated first profile to access operator B's network, that is, switch from accessing operator A's network to accessing operator B's network without reactivating the first profile. At this time, the electronic device 100 can display Figure 5D The user interface shown is 540. Figure 5D The user interface 540 shown is... Figure 5C Similar to the user interface 530 shown, the status bar 541 shown in the user interface 540 includes the eSIM signal identifier 541A, which includes the characters "B operator", indicating that the electronic device 100 is currently connected to the B operator network with 4 signal bars (i.e., full bars).

[0137] Figure 5EThis is a schematic diagram of the user interface for enabling another service card package provided in this application embodiment.

[0138] like Figure 5E As shown, the electronic device 100 can display a user interface 550 of a first network application, and the user interface 550 and Figure 5C The user interface 530 shown is similar. In the user interface 550, when the "Global 1-Month" data plan displayed in the display bar 532 is enabled, the electronic device 100 can activate the first profile corresponding to the data plan and use the SIM card information of the operator in the first profile to access the corresponding operator network. Regardless of which operator's SIM card information in the first profile is used to access which operator network (e.g., operator A network or operator B network mentioned above), the electronic device 100 can display the eSIM signal identifier 551A shown in the status bar 551 of the user interface 550. The signal identifier 551A includes the characters "Skyroam", indicating that the electronic device 100 is currently connected to the "Skyroam" virtual operator with 4 signal bars (i.e., full bars).

[0139] Figure 5E The characters included in the eSIM signal identifier 551A shown are for illustrative purposes only and should not be construed as limiting. The characters included in the eSIM signal identifier 551A may indicate the virtual operator corresponding to the first profile, such as the virtual operator to which the device cloud server 200 belongs.

[0140] Figures 6A-6C This is a schematic diagram of the user interface for enabling another service card package provided in this application embodiment.

[0141] like Figure 6A As shown, the electronic device 100 can display a user interface 610 for setting up applications. When the electronic device 100 displays the user interface 610, it can access the operator's network using the operator's card information in the first profile. The user interface 610 may include a status bar 611 at the top, a search box (for searching settings items), a personal account space, and a settings option list 612. The status bar 611 may include the eSIM signal identifier 611A, battery level, and time information. The signal identifier 611A includes the characters "Skyroam," indicating that the electronic device 100 is currently connected to the "Skyroam" virtual operator with 4 signal bars (i.e., full bars). The settings option list 612 includes, for example, WLAN, Bluetooth, mobile network, eSIM management 612A, desktop and personalization, display and brightness, and Do Not Disturb mode. In some embodiments, the electronic device 100 can receive user operations (e.g., touch clicks) applied to the eSIM management 612A in the user interface 610, and in response to the user operation, display the eSIM management user interface. Specific examples can be found in [link to specific examples]. Figure 6B The user interface shown is 620.

[0142] like Figure 6B As shown, the user interface 620 may include an eSIM list in the electronic device 100. The eSIM list may include information about one or more profiles corresponding to eSIMs, such as option 621A for the "Skyroam" eSIM (corresponding to the first profile), option 621B for the "Carrier A" eSIM (corresponding to a profile including card information from Carrier A), and option 621C for the "Carrier B" eSIM (corresponding to a profile including card information from Carrier B). Option 621A corresponds to the "Skyroam" eSIM in an "enabled" state, option 621B corresponds to the "Carrier A" eSIM in an "disabled" state, and option 621C corresponds to the "Carrier B" eSIM in a "disabled" state. Therefore, the first profile is active, and the other profiles are inactive. In some embodiments, the electronic device 100 may receive a user operation (e.g., a touch click) applied to option 621A in the user interface 620, and in response to the user operation, display the "Skyroam" eSIM information. See specific examples for details. Figure 6C The user interface 630 shown.

[0143] like Figure 6C As shown, the user interface 630 may include a status bar 631 at the top (including an eSIM signal identifier 631A), an eSIM enabled display bar 632, and an eSIM information display bar 633. The display bar 632 may include a toggle control 632A, which can be used to enable or disable the "Skyroam" eSIM. The display bar 633 may include the "Skyroam" eSIM's network operator 633A, the "Skyroam" eSIM's phone number 633B, and the corresponding "Skyroam" eSIM's service package 633C (including the characters "49.9 yuan package"). The "Skyroam" eSIM's network operator 633A includes the characters "adaptive," and the "Skyroam" eSIM's phone number 633B also includes the characters "adaptive," indicating that when the electronic device 100 uses the "Skyroam" eSIM to register on the network, it can adaptively / dynamically switch operators. That is, the electronic device 100 can dynamically use the card information of different operators in the first profile to access different operator networks, therefore the phone number is also adaptive.

[0144] like Figure 6CAs shown, the switch control 632A in the user interface 630 is in the ON state, indicating that "Skyroam" eSIM has been enabled. When "Skyroam" eSIM is enabled, the first profile can be activated, and the electronic device 100 can use the operator's card information in the activated first profile to access the operator's network. At this time, the eSIM signal identifier 631A shown in the user interface 630 includes the characters "Skyroam", indicating that the electronic device 100 is currently connected to the "Skyroam" virtual operator with 4 signal bars (i.e., full bars).

[0145] Not limited to Figure 6C In the example shown, in other examples, the characters included in the network operator 633A of the "Skyroam" eSIM can also be the identifier of a virtual operator, such as "Skyroam".

[0146] The following is a flowchart illustrating the configuration file management method provided in this application embodiment.

[0147] Figure 7 This is a flowchart illustrating a configuration file management method provided in an embodiment of this application. This method can be applied to... Figure 2 The communication system 10 shown. This method may include, but is not limited to, the following steps:

[0148] S101: Device cloud server 200 downloads card information of operator A from operator A's server 300.

[0149] S102: Device cloud server 200 downloads operator B's card information from operator B's server 400.

[0150] Among them, operator A can also be called the first operator, and operator B can also be called the second operator.

[0151] S101 and S102 are optional steps. In other embodiments, it may also involve purchasing the card information of operator A and operator B offline and then pre-setting the card information of operator A and operator B in the device cloud server 200.

[0152] S103: Device cloud server 200 determines the first profile, wherein the first profile includes card information of operator A and card information of operator B.

[0153] In some embodiments, the device cloud server 200 can determine a first profile based on the obtained SIM card information from operator A and operator B. The first profile includes the SIM card information from operator A and operator B. Operator A may also be referred to as the first operator, and operator B may also be referred to as the second operator; the first operator and the second operator are different. The SIM card information from the first operator is used to access the first operator's network, and the SIM card information from the second operator is used to access the second operator's network.

[0154] In some embodiments, the first profile may include shared information, first difference information, and second difference information, wherein the card information of operator A includes shared information and first difference information, and the card information of operator B includes both shared information and second difference information. In some examples, the shared information may include one or more types of shared data, and the same type of shared data is present in the card information of operator A and operator B. In some examples, the first difference information may include one or more types of first difference data, and the second difference information may include one or more types of second difference data, wherein the first type of first difference data in the first difference information differs from the first type of first difference data in the second difference information; that is, the same type of difference data is different in the card information of operator A and operator B.

[0155] In some embodiments, the first profile includes a function vector (MF), x element-defining vectors (EF) under the MF, s first active digital branching vectors (ADFs) under the MF, and t second active digital branching vectors (ADFs) under the MF, where x, s, and t are all positive integers. The x EFs under the MF are used to store shared information. The s first ADFs under the MF are used to store first difference information for operator A, wherein operator A's card information includes card information for s card applications of operator A, and the card information for the s card applications of operator A belongs to the first difference information; therefore, the s first ADFs can each store the card information for the s card applications of operator A. The t second ADFs under the MF are used to store second difference information for operator B, wherein operator B's card information includes card information for t card applications of operator B, and the card information for the t card applications of operator B belongs to the second difference information; therefore, the t second ADFs can each store the card information for the t card applications of operator B. An example of the first profile can be found in [link to example]. Figure 4 The first profile shown. Figure 4 Let's take an example where both s and t are 1.

[0156] Figure 7S101-S103 exemplarily illustrate the process by which the device cloud server 200 determines a first profile, but should not be construed as limiting. In specific implementations, the device cloud server 200 can determine multiple first profiles, where any one first profile includes card information from multiple operators, and the card information from different operators included in different first profiles can be different. In some examples, the device cloud server 200 can determine two first profiles (which may be referred to as a second profile and a third profile), where the operators corresponding to the card information included in the second profile and the operators corresponding to the card information included in the third profile are partially or completely different. For example, the second profile includes card information from operator A and operator B, and the third profile includes card information from operator B, operator C, and operator D.

[0157] S104: The processor 101 of the electronic device 100 receives input from the user regarding the purchase of a service card package.

[0158] For example, such as Figure 5B As shown, the electronic device 100 receives input from a user to purchase a service card package. This may include: the electronic device 100 receiving user actions (e.g., touch clicks) on the purchase option 522A in the upgrade package display bar 522 shown on the user interface 520, and receiving the user's payment action. When the user successfully pays, the electronic device 100 can determine that the service card package purchase was successful. At this time, the electronic device 100 can download the first profile.

[0159] S105: The processor 101 of the electronic device 100 sends a download request to the device cloud server 200 to request the download of the first profile.

[0160] S106: Device cloud server 200 sends the first profile to processor 101 of electronic device 100.

[0161] In some embodiments, in response to the input shown in S104, the processor 101 may instruct the mobile communication module or wireless communication module of the electronic device 100 to send a download request to the device cloud server 200, and receive the first profile sent by the device cloud server 200 through the mobile communication module or wireless communication module of the electronic device 100. The embodiments of this application do not limit the communication method used when sending the download request and receiving the first profile.

[0162] In some embodiments, the download request is used to request the download of a first profile of a target device 100. Optionally, the download request is used to request the download of a first profile corresponding to a service card package purchased by the user. The download request may carry an identifier corresponding to the first profile to be downloaded, or an identifier of a service card package purchased by the user. The device cloud server 200 can determine the target first profile from one or more first profiles based on the received download request, and then send the target first profile to the electronic device 100.

[0163] S107: The processor 101 of the electronic device 100 sends the first profile to the eSIM module 103.

[0164] S108: The eSIM module 103 of the electronic device 100 stores the first profile.

[0165] Not limited to Figure 7 In some embodiments, the download request may not be triggered by the user input shown in S104, but rather by the electronic device 100 actively sending the download request under certain specific conditions. In other embodiments, the device cloud server 200 may actively send the first profile to the electronic device 100. For example, the device cloud server 200 may actively trigger the update of the electronic device 100 (including sending the first profile).

[0166] Figure 8 This is a flowchart illustrating another configuration file management method provided in this application embodiment. This method can be applied to... Figure 1 The illustrated electronic device 100. This method can be applied to... Figure 2 The illustrated electronic device 100. This method can be applied to... Figure 3 The electronic device 100 shown. The method may include, but is not limited to, the following steps:

[0167] S201: The processor 101 of the electronic device 100 receives input from the user to activate a service card package.

[0168] S201 is an optional step. In some embodiments, the service card package may be enabled by default after successful purchase. In other embodiments, the service card package may be enabled after successful purchase if preset conditions are met, such as not being connected to a WLAN network and / or not having a SIM card inserted.

[0169] S202: The processor 101 of the electronic device 100 instructs the mobile communication module 102 to register on the network through the first profile.

[0170] In some embodiments, the processor 101 may send network registration indication information to the mobile communication module 102. The network registration indication information may include the identifier of the first profile, ISP-AID, for indicating network registration through the first profile.

[0171] S203: The mobile communication module 102 of the electronic device 100 instructs the eSIM module 103 to activate the first profile.

[0172] In some embodiments, the mobile communication module 102 may send activation indication information to the eSIM module 103. The activation indication information may include the identifier of the first profile, ISP-AID, for indicating the activation of the first profile.

[0173] S204: The eSIM module 103 of the electronic device 100 activates the first profile.

[0174] In some embodiments, the eSIM module 103 may receive activation indication information sent by the mobile communication module 102 and activate the first profile in response to the activation indication information.

[0175] In some embodiments, after activating the first profile, the electronic device 100 can access the network of operator A based on the card information of operator A in the first profile, i.e., execute S205-S208. Then, if the conditions for switching operator networks are met, the electronic device 100 can access the network of operator B based on the card information of operator B in the first profile, i.e., execute S209-S213.

[0176] S205: The mobile communication module 102 of the electronic device 100 controls the eSIM module 103 to reset.

[0177] S206: The mobile communication module 102 of the electronic device 100 reads the shared information in the first profile stored in the eSIM module 103.

[0178] S207: The mobile communication module 102 of the electronic device 100 reads the first difference information in the first profile stored in the eSIM module 103.

[0179] S208: The mobile communication module 102 of the electronic device 100 accesses the network of operator A based on the read common information and first difference information.

[0180] In some embodiments, after activating the first profile, the electronic device 100 can initialize the first profile, for example, by executing S205-S207. In some embodiments, the first difference information read by the mobile communication module 102 after reading the shared information can be the difference information of the operator read by default, that is, the card information of operator A in the first profile read can be the card information of the operator read by default. Not limited thereto, in other embodiments, the first difference information read can be determined according to a preset rule, that is, the card information of operator A in the first profile read can be determined according to a preset rule. For example, when the electronic device 100 determines that it is currently within the coverage area of ​​operator A's network, it determines to read the card information of operator A in the first profile (including reading the first difference information) in order to access operator A's network.

[0181] S209: The communication map server 500 determines that electronic device 100 needs to switch to operator B's network.

[0182] S210: The communication map server 500 sends a handover instruction to the mobile communication module 102 to instruct the electronic device 100 to switch to the B operator's network.

[0183] S211: The mobile communication module 102 of the electronic device 100 sends a handover command (indicating a change of operator event) to the eSIM module 103.

[0184] In some embodiments, the communication map server 500 may maintain a first communication map, which may include information on multiple operator networks, such as information on operator network A and operator network B. In some examples, the information of any operator network in the first communication map may include the coverage area of ​​that operator network, optional information such as signal quality, etc. The communication map server 500 may determine, based on the first communication map, that the electronic device 100 needs to switch to operator network B, which offers a better internet experience, and thus send a switching instruction to the electronic device 100.

[0185] In some embodiments, the communication map server 500 can receive the real-time location and accessed operator network reported by the electronic device 100, optionally including signal quality. The communication map server 500 can determine whether the electronic device 100 needs to switch operator networks based on the information reported by the electronic device 100 and a first communication map. In some examples, when the electronic device 100 is about to leave the coverage area of ​​operator A, it can be determined that the electronic device 100 needs to switch operator networks. In some examples, when the signal quality of operator A accessed by the electronic device 100 is poor, it can be determined that the electronic device 100 needs to switch operator networks. This application embodiment does not limit the specific method for determining whether the electronic device 100 needs to switch operator networks, or which operator network to switch to.

[0186] In some embodiments, after receiving the handover indication information, the mobile communication module 102 may send a handover command to the eSIM module 103 to notify the eSIM module 103 of the operator handover event. Optionally, the handover indication information may carry the identifier of operator B. Optionally, the handover command may carry the identifier of operator B.

[0187] In some embodiments, after receiving a handover instruction, the electronic device 100 determines that it needs to switch to operator B's network. The electronic device 100 can determine that the first profile includes operator B's card information based on the information obtained in S205-S206, and therefore determines to use the card information of operator B in the activated first profile to access operator B's network. Thus, S212-S213 can be executed. Since the first profile has already been activated, the electronic device 100 does not need to reactivate the first profile, i.e., it does not need to re-execute S204-S205; the first profile remains active during S212-S213. Since the shared information in the first profile has already been read, the electronic device 100 does not need to read the shared information in the first profile again, i.e., it does not need to re-execute S206.

[0188] S212: The mobile communication module 102 of the electronic device 100 reads the second difference information in the first profile stored in the eSIM module 103.

[0189] S213: The mobile communication module 102 of the electronic device 100 accesses the B operator network based on the read common information and second difference information.

[0190] In some embodiments, after receiving the handover instruction information sent by the communication map server 500, the mobile communication module 102 can actively trigger the reading process of the second difference information, that is, S212 is actively triggered by the mobile communication module 102. The mobile communication module 102 can actively switch the read difference information based on the AID. In some examples, the first ADF in the first profile stores the first difference information, and the second ADF in the first profile stores the second difference information. The first ADF corresponds to the first AID, and the second ADF corresponds to the second AID. S207 can be implemented based on the first AID, and S212 can be implemented based on the second AID. The mobile communication module 102 can switch the read ADF based on the AID.

[0191] In some embodiments, after receiving the handover instruction information, the mobile communication module 102 can send it to the processor 101 for processing. The processor 101 can determine whether to switch the accessed operator network based on the handover instruction information and the current network status of the electronic device 100. When a switch is determined, the processor 101 can send a corresponding notification to the mobile communication module 102 to cause the mobile communication module 102 to execute S212 and S213. Optionally, the notification can carry the AID corresponding to operator B (i.e., the AID of the ADF used to store card information of operator B's card application). The mobile communication module 102 can read the card information (belonging to the second difference information) stored in the corresponding ADF based on the AID carried in the notification.

[0192] In some embodiments, S212 can also be executed in advance, for example, after S206 and before S208, or after S208 and before S211. That is, the mobile communication module 102 can obtain the card information of operator B in advance, so that S213 can be executed directly after S211, further improving the speed of switching operator networks.

[0193] In some embodiments, after S208, the electronic device 100 displays a first identifier of the mobile communication network, the first identifier indicating operator A, for example, the first identifier is... Figure 5C The status bar 531 shows the eSIM signal identifier 531A. Following S213, the electronic device 100 displays a second identifier for the mobile communication network, indicating the B operator; for example, the second identifier is... Figure 5D The eSIM signal identifier 541A is shown in the status bar 541.

[0194] In other embodiments, after S208, the electronic device 100 displays a third identifier of the mobile communication network, and after S213, the electronic device 100 continues to display the third identifier of the mobile communication network, which indicates the first virtual operator. For example, the third identifier is... Figure 5E The eSIM signal identifier 551A is shown in the status bar 551.

[0195] Not limited to Figure 8 In the illustrated embodiment, in other embodiments, the electronic device 100 may automatically detect whether a switch to a different operator network is needed, in which case S209-S211 are not executed. In some examples, when the electronic device 100 detects that the current first signal quality parameter is less than a quality threshold, it determines to switch operator networks. The first signal quality parameter characterizes the signal quality of the operator network A currently accessed by the electronic device 100, and can also be understood as characterizing the signal quality corresponding to the card information of operator A currently used by the electronic device 100. The first signal quality parameter is, for example, but not limited to, quality of service (QoS). In this case, S212 may be actively triggered by the mobile communication module 102 or by the eSIM module 103 (i.e., a refresh is performed). In some examples, when the eSIM module 103 refreshes, it can traverse the operator difference information in the activated first profile (e.g., traverse the ADF in the activated first profile). Therefore, the mobile communication module 102 can traverse and read the operator difference information in the activated first profile (e.g., traverse and read the ADF in the activated first profile) under the active trigger of the eSIM module 103, and try to access the corresponding operator network using the read common information and difference information. When the access is successful, the traversal can be ended.

[0196] Next Figure 8 S205-S213 shown below will be described by way of example. Figure 4 The first profile shown is used as an example for explanation.

[0197] Figure 9 This is a flowchart illustrating another configuration file management method provided in this application embodiment. This method can be applied to... Figure 1 The illustrated electronic device 100. This method can be applied to... Figure 2 The illustrated electronic device 100. This method can be applied to... Figure 3 The electronic device 100 shown. The method may include, but is not limited to, the following steps:

[0198] S301: The mobile communication module 102 of the electronic device 100 indicates a first profile cold reset to the eSIM module 103.

[0199] S302: The eSIM module 103 of the electronic device 100 sends a reset response (ATR) to the mobile communication module 102.

[0200] In some embodiments, after activating the first profile, the first profile can be initialized. The initialization of the first profile may include resetting, reading common information (i.e., reading x EFs under the MF of the first profile), and USIM1 initialization. Examples of the reset implementation can be found in S301-S302, examples of the reading common information implementation can be found in S303-S308, and examples of the USIM1 initialization implementation can be found in S309-S318.

[0201] S303: The mobile communication module 102 of the electronic device 100 sends a Select Master File (SelectMF) command (carrying the identifier of MF) to the eSIM module 103.

[0202] S304: The eSIM module 103 of the electronic device 100 sends a response 1 to the mobile communication module 102 (indicating that the eSIM module 103 has successfully acquired the MF in the first profile).

[0203] In some embodiments, since the first profile in the eSIM module 103 is active, the eSIM module 103 can find the MF from the active first profile based on the MF identifier carried by the SelectMF command. After finding the MF of the first profile, the eSIM module 103 can return a response (Response 1) to the mobile communication module 102 to indicate to the mobile communication module 102 that the eSIM module 103 has successfully obtained the MF of the first profile.

[0204] S305: The mobile communication module 102 of the electronic device 100 sends a SelectICCID command (carrying the EF-ICCID identifier) ​​to the eSIM module 103.

[0205] S306: The eSIM module 103 of the electronic device 100 sends the ICCID from the EF-ICCID to the mobile communication module 102.

[0206] S307: The mobile communication module 102 of the electronic device 100 sends a SelectDIR command (carrying the identifier of EF-DIR) to the eSIM module 103.

[0207] S308: The eSIM module 103 of the electronic device 100 sends data in EF-DIR (including AID1 and AID2) to the mobile communication module 102.

[0208] In some embodiments, after S303-S304, that is, after the MF in the first profile is selected, the mobile communication module 102 can read x EFs under the MF in the first profile stored by the eSIM module 103. S305-S306 exemplarily illustrate the implementation process of reading EF-ICCID under the MF, and S307-S308 exemplarily illustrate the implementation process of reading EF-DIR under the MF. The implementation process of reading other EFs under the MF is similar and will not be listed one by one.

[0209] In some embodiments, after reading the shared information, USIM1 initialization can be performed. USIM1 initialization may include a negotiation process, reading the first difference information, and subscribing to listening events. Examples of the implementation of the negotiation process can be found in S309-S310, examples of the implementation of reading the first difference information can be found in S311-S314, and examples of the implementation of subscribing to listening events can be found in S316-S317.

[0210] S309: The mobile communication module 102 of the electronic device 100 sends a Terminal Profile command to the eSIM module 103.

[0211] S310: The eSIM module 103 of the electronic device 100 sends a Terminal Response command 1 to the mobile communication module 102 (indicating that the Terminal Profile command was executed successfully).

[0212] In some embodiments, the Terminal Profile command can be used to notify the eSIM module 103 of commands supported by the mobile communication module 102 (e.g., SIM application toolkit (SAT) commands). After receiving the Terminal Profile command, the eSIM module 103 can return a corresponding response (i.e., Terminal Response command 1) to the mobile communication module 102, which can indicate that the Terminal Profile command was executed successfully.

[0213] S311: The mobile communication module 102 of the electronic device 100 sends a SelectUSIM1 command (carrying the identifier AID1 of USIM1) to the eSIM module 103.

[0214] S312: The eSIM module 103 of the electronic device 100 sends response 2 to the mobile communication module 102 (indicating that the eSIM module 103 has successfully obtained USIM1 in the first profile).

[0215] In some embodiments, since the MF in the first profile is selected, the eSIM module 103 can locate the USIM1 file from the ADF under the MF based on the identifier of the USIM1 file carried by the Select USIM1 command. After locating the USIM1 file in the first profile, the eSIM module 103 can return a response 2 to the mobile communication module 102 to indicate to the mobile communication module 102 that the eSIM module 103 has successfully obtained the USIM1 file in the first profile.

[0216] S313: The mobile communication module 102 of the electronic device 100 sends a SelectIMSI1 command (carrying the identifier of EF-IMSI1) to the eSIM module 103.

[0217] S314: The eSIM module 103 of the electronic device 100 sends IMSI1 from EF-IMSI1 to the mobile communication module 102.

[0218] In some embodiments, after S311-S312, that is, after the USIM1 file in the first profile is selected, the mobile communication module 102 can read the y EFs under USIM1 in the first profile stored by the eSIM module 103. S313-S314 exemplarily illustrate the implementation process of reading EF-IMSI1 under USIM1. The implementation process of reading other EFs under USIM1 is similar and will not be listed one by one.

[0219] S315: The mobile communication module 102 of the electronic device 100 accesses the network of operator A based on the read common information and first difference information.

[0220] In some embodiments, the mobile communication module 102 can access the network of operator A based on the data stored in the EF under MF in the first profile and the data stored in the EF under USIM1. In some examples, the mobile communication module 102 can send an AttachRequest message (carrying IMSI1) to the server of operator A's network and receive an AttachAccept message returned by the server of operator A's network, thereby completing the registration of electronic device 100 to operator A's core network.

[0221] S316: The eSIM module 103 of the electronic device 100 sends a Setup event list command to the mobile communication module 102 (instructing to listen for operator switching events).

[0222] S317: The mobile communication module 102 of the electronic device 100 sends Terminal Response command 2 to the eSIM module 103 (indicating that the monitoring event was set successfully).

[0223] In some embodiments, the eSIM module 103 can proactively send a Setup eventlist command to the mobile communication module 102 to indicate a request to listen to a certain event. This embodiment of the application uses listening to a carrier switching event as an example for explanation. After receiving the Setup event list command, the mobile communication module 102 can return a corresponding response (i.e., Terminal Response command 2) to the eSIM module 103. Terminal Response command 2 can indicate that the setting for listening to the carrier switching event was successful.

[0224] S318: The mobile communication module 102 of the electronic device 100 sends a status command 1 to the eSIM module 103.

[0225] In some embodiments, upon successful USIM1 initialization, the mobile communication module 102 may send a specific status command 1 to the eSIM module 103 to indicate that a session on operator A's network is ready. In some examples, during the process of the mobile communication module 102 accessing operator A's network, the mobile communication module 102 may periodically send status command 1 to the eSIM module 103 to indicate that a session on operator A's network is currently in progress. The status command 1 can be understood as a "heartbeat" command.

[0226] S319: The mobile communication module 102 of the electronic device 100 sends a notification command (indicating a carrier switching event) to the eSIM module 103.

[0227] In some embodiments, since the operator switching event is successfully set in S316-S317, when the mobile communication module 102 determines that the electronic device 100 needs to switch operators, it can send a corresponding notification command to the eSIM module 103 to notify the eSIM module 103 of the operator switching event.

[0228] In some embodiments, when the electronic device 100 determines which operator network to access, it may initialize USIM2 in the first profile. Examples of USIM2 initialization can be found in S320-S325. During the initialization of USIM2 in the first profile, the first profile remains active.

[0229] S320: The mobile communication module 102 of the electronic device 100 sends a SelectUSIM2 command (carrying the identifier AID2 of USIM2) to the eSIM module 103.

[0230] S321: The eSIM module 103 of the electronic device 100 sends a response 3 to the mobile communication module 102 (indicating that the eSIM module 103 has successfully acquired USIM2 in the first profile).

[0231] In some embodiments, since the first profile has been activated and the MF in the first profile has been selected, the eSIM module 103 can locate the USIM2 file from the ADF under the MF according to the USIM2 file identifier carried by the Select USIM2 command. After locating the USIM2 file in the first profile, the eSIM module 103 can return a response 3 to the mobile communication module 102 to indicate to the mobile communication module 102 that the eSIM module 103 has successfully obtained the USIM2 file in the first profile.

[0232] S322: The mobile communication module 102 of the electronic device 100 sends a SelectIMSI2 command (carrying the identifier of EF-IMSI2) to the eSIM module 103.

[0233] S323: The eSIM module 103 of the electronic device 100 sends the IMSI2 in EF-IMSI2 to the mobile communication module 102.

[0234] In some embodiments, after S320-S321, that is, after the USIM2 file in the first profile is selected, the mobile communication module 102 can read z EFs under USIM2 in the first profile stored by the eSIM module 103. S322-S323 exemplarily illustrate the implementation process of reading EF-IMSI2 under USIM2. The implementation process of reading other EFs under USIM2 is similar and will not be listed one by one.

[0235] In some embodiments, the process of the mobile communication module 102 reading the difference information 2 (e.g., S320-S323) can also be executed in advance, for example, reading the difference information 2 during the USIM1 initialization process, or reading the difference information 2 after USIM1 initialization and before S319. That is to say, the mobile communication module 102 can obtain the card information of operator B in advance, so that S324 can be executed directly after S319, further improving the speed of switching operator networks.

[0236] S324: The mobile communication module 102 of the electronic device 100 accesses the B operator network based on the read common information and second difference information.

[0237] In some embodiments, the mobile communication module 102 can access the B operator's network based on the data stored in the EF under the MF in the first profile and the data stored in the EF under USIM2. In some examples, the mobile communication module 102 can send an AttachRequest message (carrying IMSI2) to the server of the B operator's network and receive an AttachAccept message returned by the server of the B operator's network, thereby completing the registration of the electronic device 100 to the core network of the B operator.

[0238] S325: The mobile communication module 102 of the electronic device 100 sends a status command 2 to the eSIM module 103.

[0239] In some embodiments, upon successful USIM2 initialization, the mobile communication module 102 may send a specific status command 2 to the eSIM module 103 to indicate that a session with operator B's network is ready. In some examples, during the process of the mobile communication module 102 accessing operator B's network, the mobile communication module 102 may periodically send the status command 2 to the eSIM module 103 to indicate that a session with operator B's network is currently in progress. The status command 2 can be understood as a "heartbeat" command.

[0240] Figure 10 This is a schematic diagram of the structure of a communication device 1000 provided in an embodiment of this application. The communication device 1000 may be a device cloud server 200, or a device therein.

[0241] like Figure 10As shown, the communication device 1000 includes a processor 1001 and a transceiver 1002 internally connected and communicating with the processor 1001. The processor 1001 can be a general-purpose processor or a dedicated processor, such as a central processing unit (CPU). The transceiver 1002, also known as a transceiver unit, transceiver, or transceiver circuit, is used to implement transceiver functions. The transceiver 1002 may include a receiver and a transmitter. The receiver, also known as a receiver circuit, is used to implement a receiving function; the transmitter, also known as a transmitter or transmitting circuit, is used to implement a transmitting function.

[0242] In some embodiments, the communication device 1000 may further include an antenna 1003 and / or a radio frequency unit (RF unit). Figure 10 (Not shown in the image). The antenna 1003 and / or the radio frequency unit may be located inside the communication device 1000 or separate from the communication device 1000, that is, the antenna 1003 and / or the radio frequency unit may be deployed remotely or in a distributed manner.

[0243] In some embodiments, the communication device 1000 may include one or more memories 1004, which may store instructions, which may be computer programs, that can be executed on the communication device 1000 to cause the communication device 1000 to perform the method steps described in the above embodiments of this application. Optionally, the memory 1004 may also store data. The communication device 1000 and the memory 1004 may be provided separately or integrated together.

[0244] Figure 10 The processor 1001, transceiver 1002, and memory 1004 shown can be connected via a communication bus.

[0245] In any of the above designs, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0246] In any of the above designs, the processor 1001 may store instructions, which may be computer programs. These computer programs, running on the processor 1001, cause the communication device 1000 to execute the method steps performed by the device cloud server 200 in the above method embodiments. The computer program may be embedded in the processor 1001; in this case, the processor 1001 may be implemented in hardware.

[0247] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps performed by the electronic device 100 in the above-described method embodiments.

[0248] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps performed by the device cloud server 200 in the above-described method embodiments.

[0249] This application also provides a computer program product, including a computing program, which, when run on a computer, enables the computer to perform the steps executed by the electronic device 100 in the above-described method embodiments.

[0250] This application also provides a computer program product, including a computing program, which, when run on a computer, enables the computer to perform the steps executed by the device cloud server 200 in the above-described method embodiments.

[0251] This application also provides a chip system, which includes a processing circuit interface circuit. The interface circuit receives code instructions and transmits them to the processing circuit. The processing circuit executes the code instructions to enable the chip system to perform the steps executed by the electronic device 100 in any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0252] This application also provides a chip system, which includes a processing circuit interface circuit. The interface circuit receives code instructions and transmits them to the processing circuit. The processing circuit executes the code instructions to enable the chip system to perform the steps executed by the device cloud server 200 in any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0253] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A configuration file management method, applied to an electronic device including an embedded eSIM module, characterized in that, The method includes: The first configuration file (profile) sent by the receiving device's cloud server; The first profile is stored in the eSIM module. The first profile includes card information from a first operator and card information from a second operator. The first operator and the second operator are different. The card information from the first operator is used to access the network of the first operator, and the card information from the second operator is used to access the network of the second operator.

2. The method as described in claim 1, characterized in that, Before the first configuration file profile sent by the receiving device cloud server, the method further includes: Receive the user's first input when purchasing a service card package; In response to the first input, a download request is sent to the device cloud server, the download request being used to request the download of the first profile.

3. The method as described in claim 1 or 2, characterized in that, The first profile includes shared information, first difference information, and second difference information. The card information of the first operator includes the shared information and the first difference information. The card information of the second operator includes the shared information and the second difference information. The first difference information includes one or more types of first difference data. The second difference information includes one or more types of second difference data. The first type of first difference data is different from the second type of second difference data.

4. The method as described in claim 3, characterized in that, The first profile includes x basic files (EF), s first application-specific files (ADF), and t second ADFs, where x, s, and t are all positive integers. The x EFs are used to store the shared information, the s first ADFs are used to store the first difference information, and the t second ADFs are used to store the second difference information. The card information of the first operator includes card information of s card applications of the first operator, and the s first ADFs respectively store the card information of the s card applications. The card information of the second operator includes card information of t card applications of the second operator, and the t second ADFs respectively store the card information of the t card applications.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Activate the first profile in the eSIM module; Access to the first operator's network based on the card information of the first operator in the first profile; If the conditions for switching carrier networks are met, the user can access the network of the second carrier based on the card information of the second carrier in the first profile.

6. The method as described in claim 5, characterized in that, The electronic device includes a mobile communication module; The step of accessing the network of the first operator based on the card information of the first operator in the first profile includes: the mobile communication module reading the common information in the first profile stored in the eSIM module; the mobile communication module reading the first difference information in the first profile stored in the eSIM module; and the mobile communication module accessing the network of the first operator based on the common information and the first difference information. The step of accessing the network of the second operator based on the card information of the second operator in the first profile includes: the mobile communication module reading the second difference information in the first profile stored by the eSIM module; and the mobile communication module accessing the network of the first operator based on the common information and the second difference information.

7. The method as described in claim 6, characterized in that, The first profile includes x basic files (EF), s first application-specific files (ADF), and t second ADFs, where x, s, and t are all positive integers. The x EFs are used to store the common information, the s first ADFs are used to store the first difference information, and the t second ADFs are used to store the second difference information. The mobile communication module reads the shared information in the first profile stored in the eSIM module, including: the mobile communication module reads the data stored in the x EFs from the eSIM module; The mobile communication module reads the first difference information in the first profile stored in the eSIM module, including: the mobile communication module reads the data stored in the third ADF of the first profile from the eSIM module based on the first AID, the s first ADFs include the third ADF, the third ADF corresponds to the first AID, and the third ADF is used to store the card information of the card application corresponding to the first AID of the first operator; The mobile communication module reads the second difference information in the first profile stored in the eSIM module, including: the mobile communication module reads the data stored in the fourth ADF of the first profile from the eSIM module based on the second AID, wherein the t second ADFs include the fourth ADF, the fourth ADF corresponds to the second AID, and the fourth ADF is used to store the card information of the card application corresponding to the second AID of the second operator.

8. The method according to any one of claims 5-7, characterized in that, The method further includes: After accessing the network of the first operator based on the card information of the first operator in the first profile, the first identifier of the mobile communication network is displayed, and the first identifier indicates the first operator. After the card information of the second operator in the first profile is used to access the network of the second operator, a second identifier of the mobile communication network is displayed, and the second identifier indicates the second operator.

9. The method according to any one of claims 5-7, characterized in that, The method further includes: After accessing the network of the first operator based on the card information of the first operator in the first profile, a third identifier of the mobile communication network is displayed, and the third identifier indicates the first virtual operator. After the card information of the second operator in the first profile is used to access the network of the second operator, the third identifier of the mobile communication network is displayed.

10. The method according to any one of claims 5-7, characterized in that, The method further includes: Upon receiving a first notification message from a communication map server, it is determined that the conditions for switching operator networks are met. The first notification message instructs the electronic device to connect to the second operator. The communication map server maintains a first communication map, which includes information about the networks of the first operator and the second operator. The first notification message is determined based on the first communication map. Alternatively... When the first signal quality parameter is detected to be less than the quality threshold, it is determined that the conditions for switching operator networks are met, wherein the first signal quality parameter is used to characterize the signal quality of the network of the first operator to which the network is accessed.

11. An electronic device, characterized in that, It includes a transceiver, a processor, and a memory, the memory being used to store a computer program, and the processor calling the computer program to perform the steps in the method as described in any one of claims 1-10.

12. An electronic device, characterized in that, The method includes a mobile communication module and an eSIM module, wherein the mobile communication module is configured to perform the steps performed by the mobile communication module in any one of the methods described in claims 1-10, and the eSIM module is configured to perform the steps performed by the eSIM module in any one of the methods described in claims 1-10.

13. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, implements the method as described in claims 1-10.

14. A computer program product, characterized in that, When the computer program product is run on a processor, it is used to implement the method as described in claims 1-10.

15. A chip system, characterized in that, It includes a processing circuit and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to execute the code instructions to perform the method as described in claims 1-10.

Images