Communication method and electronic equipment

Abstract

The invention provides a communication method and electronic equipment, and relates to the technical field of terminals. The method comprises the following steps: newly adding area-followed card-followed MBN files of different operators in different areas in the electronic equipment, wherein the area-followed card-followed MBN files represent configuration requirements of the corresponding operators on network parameters of mobile communication in the corresponding areas. The electronic equipment can perform mobile communication with the network side based on the area where the electronic equipment is currently located and the network parameters in the area-following-card MBN file corresponding to the operator to which the SIM card belongs, so that the specific configuration requirement of the operator to which the SIM card belongs in the area where the electronic equipment is currently located is met, the flexible configuration of the network parameters is realized, and the user experience is improved. Therefore, the problem that the network capability of the electronic equipment is limited due to the fact that the configuration requirement of the operator in a certain area is changed but the electronic equipment still carries out mobile communication according to the universal card-following MBN file corresponding to the operator, that is, the electronic equipment carries out mobile communication according to the fixed network parameters is avoided.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a communication method and electronic device. Background Technology

[0002] Currently, electronic devices can use a Subscriber Identification Module (SIM) card for mobile communication after it is installed. For example, the electronic device can load a modem boot network (MBN) file corresponding to the operator to which the SIM card belongs, allowing it to interact with network devices using the MBN file and thus achieve mobile communication.

[0003] However, if electronic devices only use the MBN file corresponding to that operator for mobile communication, the communication capabilities of the electronic devices may be limited. Summary of the Invention

[0004] This application provides a communication method and an electronic device to avoid limiting the communication capabilities of the electronic device.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, a communication method is provided for use in an electronic device. When conditions are met to trigger the loading of the modem boot network MBN file, the electronic device can determine whether a first MBN file (i.e., a region-specific MBN file) exists corresponding to the device's first region information and SIM card information. This first MBN file represents the network parameter configuration rules for mobile communication under the first region by the first operator corresponding to the SIM card information. The first region represents the region where the electronic device is currently located.

[0007] If the aforementioned first MBN file exists, the electronic device can directly load the first MBN file. Subsequently, the electronic device can conduct mobile communication with network devices based on the first MBN file.

[0008] In this application, the electronic device adds a region-specific and SIM card-specific MBN file related to the region and operator. If, under the condition that triggers the loading of the MBN file is met, a region-specific and SIM card-specific MBN file exists corresponding to the first region where the electronic device is currently located and the first operator to which the SIM card belongs, the electronic device can use this region-specific and SIM card-specific MBN file for mobile communication. This satisfies the configuration requirements of the first operator in the first region, enabling the electronic device to access the mobile network using the specific network methods supported by the first operator in the first region. This improves the network capabilities of the electronic device and avoids limitations on its network capabilities due to the use of the first operator's general configuration requirements.

[0009] Alternatively, if the first MBN file does not exist, the electronic device can directly load the second MBN file corresponding to the SIM card information. This second MBN file represents the general configuration rules of the first operator for mobile communication network parameters. Based on this, the electronic device can still access the mobile network normally even if a corresponding area-specific MBN file does not exist.

[0010] In one possible design, the aforementioned first MBN file represents the specific configuration rules of the first operator for mobile communication network parameters within the first area. Correspondingly, after loading the first MBN file, the electronic device can also load the second MBN file corresponding to the first operator. Subsequently, the electronic device can conduct mobile communication with network equipment based on both the first and second MBN files. This allows the electronic device to utilize both the specific configuration requirements of the first operator within the first area and the general configuration requirements of the first operator for network configuration.

[0011] In one possible design approach, when the aforementioned electronic device includes multiple SIM cards, it is necessary to load the MBN file corresponding to each SIM card. That is, for each SIM card, if there exists a first MBN file corresponding to the first area information and the SIM card information, the electronic device can load the first MBN file corresponding to the SIM card information, thereby meeting the configuration requirements of the operators to which different SIM cards belong under the first area.

[0012] In addition, if there is no first MBN file corresponding to the first area information and SIM card information, the electronic device can load the second MBN file corresponding to the SIM card information.

[0013] After loading the MBN file, if a first MBN file exists corresponding to the first area information and the SIM card information of the target SIM card, the electronic device can perform mobile communication with the network device based on the first MBN file. The target SIM card is one of multiple SIM cards used for accessing the mobile network. Based on this, the electronic device can access the mobile network provided by the operator to which the target SIM card belongs, according to the specific configuration requirements of that operator in the first area, thereby improving the network capabilities of the electronic device.

[0014] In addition, if there is no first MBN file corresponding to the first area information and the SIM card information of the target SIM card, the electronic device can use the second MBN file corresponding to the SIM card information of the target SIM card to conduct mobile communication with the network device.

[0015] In one possible design, the aforementioned first MBN file is located in a first directory corresponding to the first region, and this first directory is used to store the MBN files corresponding to the operators within the first region. The first directory corresponding to the first region is then located in a second directory, which is used to store the MBN files corresponding to operators in different regions.

[0016] The aforementioned second MBN file belongs to the third directory, which stores MBN files corresponding to different operators. The second and third directories are listed side-by-side. This facilitates electronic devices in finding or compiling MBN files, thereby enabling them to load the required MBN files and improving communication efficiency.

[0017] In one possible design approach, the conditions for triggering the loading of the MBN file (or the conditions for triggering network configuration) include the electronic device being in an OTA upgrade scenario or the SIM card of the electronic device changing. Optionally, the OTA upgrade scenario may include a COTA upgrade scenario.

[0018] In one possible design, where the condition for triggering the loading of the MBN file is that the electronic device is undergoing an OTA upgrade, the electronic device is in the second region before the condition for triggering the loading of the MBN file is met. That is, the electronic device's region information is the second region information. The second region information differs from the first region information.

[0019] If a second area information and a third MBN file corresponding to the first operator exist for the electronic device, mobile communication with the network device is conducted based on the third MBN file. This satisfies the first operator's configuration requirements for network parameters in the second area, enabling flexible configuration of network parameters and preventing limitations on the electronic device's network capabilities. Therefore, if the electronic device's area changes from the second area to the first area, the electronic device can use the first operator's area-specific MBN file (the latest area) for mobile communication, satisfying the first operator's configuration requirements in different areas and preventing limitations on the electronic device's network capabilities.

[0020] If the aforementioned third MBN file does not exist, it indicates that the electronic device does not have a usable region-specific MBN file. In this case, the electronic device can use the second MBN file corresponding to the first operator to conduct mobile communication with the network equipment, thereby ensuring that the electronic device can access the mobile network provided by the first operator. Therefore, if, in the first region, the electronic device does not have the aforementioned first MBN file but still uses the second MBN file for network configuration, then although the region of the electronic device changes, the network configuration remains unchanged.

[0021] In one possible design, when the conditions for triggering the loading of the MBN file include an electronic device undergoing an OTA upgrade, the electronic device can receive an upgrade data packet sent by the server. This upgrade data packet includes information about the first region and a fourth MBN file corresponding to at least one operator within the first region. The fourth MBN file corresponding to an operator within the first region represents the operator's configuration rules for mobile communication network parameters within that region.

[0022] Subsequently, the mobile phone can change the area information of the electronic device from the second area information to the first area information, thereby updating the area information. Here, the at least one operator includes the aforementioned first operator, and the fourth MBN file includes the aforementioned first MBN file.

[0023] Based on this, electronic devices can use upgrade data packages to add MBN files that are specific to the region and the card, thereby meeting the configuration requirements of the corresponding operator in the corresponding region.

[0024] In one possible design, after receiving the upgrade data packet, the electronic device can save the fourth MBN file (i.e., the area-specific MBN file) corresponding to at least one operator in the first region in the first directory corresponding to the first region. Then, for each of the at least one operator, the electronic device can compile the operator-specific fourth MBN file. Based on this, by saving the newly added area-specific MBN file in the first directory, the electronic device can determine whether the newly added area-specific MBN file exists through this first directory. Furthermore, by compiling the newly added area-specific MBN file, the electronic device can use the area-specific MBN file.

[0025] In one possible design approach, the process of compiling the fourth MBN file corresponding to the aforementioned operator may include:

[0026] The electronic device first references the operator's corresponding fourth MBN file to the operator's corresponding fifth MBN file in the third directory. The operator's fifth MBN file represents the operator's general configuration rules for mobile communication network parameters. Then, the electronic device can compile the operator's corresponding fourth MBN file while compiling the operator's fifth MBN file (i.e., the general SIM-compatible MBN file), thus achieving the compilation of the region-specific SIM-compatible MBN file.

[0027] In one possible implementation, the aforementioned SIM card change includes the installation of a new SIM card in the electronic device (i.e., the addition of a new SIM card). This allows the mobile phone to load the area-specific MBN file corresponding to the first region and the operator to which the new SIM card belongs, in order to determine the operator's configuration requirements in the first region and achieve flexible configuration of network parameters.

[0028] Secondly, this application provides an electronic device, the electronic device including a memory, a SIM card and one or more processors; the memory, the SIM card and the processor are coupled; the memory is used to store computer program code, the SIM card is used for mobile communication, and the computer program code includes computer instructions; when the processor executes the computer instructions, the electronic device performs the method described above.

[0029] Thirdly, this application provides a chip, the chip including a communication interface and at least one processor:

[0030] The communication interface is used for inputting and / or outputting signaling or data;

[0031] The at least one processor is used to execute a computer program to implement the method described above.

[0032] Fourthly, this application provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the method described above.

[0033] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the method described above.

[0034] It is understood that the beneficial effects achieved by the electronic device described in the second aspect, the chip described in the third aspect, the computer-readable storage medium described in the fourth aspect, and the computer program product described in the fifth aspect can be referred to the beneficial effects in the first aspect and any of its possible design embodiments, which will not be repeated here. Attached Figure Description

[0035] Figure 1A A schematic diagram illustrating an upgrade scenario provided in an embodiment of this application;

[0036] Figure 1B A schematic diagram of an MBN file provided in an embodiment of this application;

[0037] Figure 2 A schematic diagram of a communication method provided in an embodiment of this application;

[0038] Figure 3 A schematic diagram illustrating a SIM card configuration provided in an embodiment of this application;

[0039] Figure 4 A schematic diagram of a communication method provided in an embodiment of this application. Figure Two ;

[0040] Figure 5 A schematic diagram of a communication method provided in an embodiment of this application. Figure Three ;

[0041] Figure 6 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0042] Figure 7 A schematic diagram of a communication method provided in an embodiment of this application. Figure Four ;

[0043] Figure 8 A schematic diagram of a directory structure provided in an embodiment of this application;

[0044] Figure 9 A schematic diagram of the hardware structure of an electronic device provided in this application embodiment. Figure Two ;

[0045] Figure 10This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0046] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "exemplary" or "for example" are used in the embodiments of this application to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a specific manner. In the embodiments of this application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. In the embodiments of this application, "first," "second," "1," and "2" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, features defined with "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "multiple" means two or more.

[0047] To facilitate understanding of the solution in this application, the terms used in this application will be explained below.

[0048] Over-the-air (OTA) updates are the process by which electronic devices update their software systems (or upgrade online) via wireless communication. For example... Figure 1A As shown, electronic devices can automatically or in response to user operations receive data packets (referred to as upgrade data packets) sent by the server via OTA for software system upgrades, so as to perform updates using the upgrade data packets.

[0049] OTA (Over-The-Air) methods can include configuration over the air (COTA) upgrades, which are data packets customized by equipment manufacturers according to the needs of operators to achieve the functions expected by operators.

[0050] The modem configuration framework (MCFG) is used to initiate a single binary mapping to pair with configuration data / images of multiple software / hardware configurations that can be supported, and it is primarily implemented through MBN files.

[0051] An MBN file is a configuration file related to SIM card and network environment configuration. The MBN file can include the network standards supported by the electronic device and is used to configure the device's network capabilities, such as those for CDMA2000, GSM, and LTE networks. Simply put, the MBN file is actually a set of important non-volatile (NV) parameters, an encrypted filesystem (EFS), and policy management settings. It provides the configuration information (or network parameters) required for the electronic device to access wireless communication networks (such as mobile networks) to meet the requirements of the corresponding wireless communication network operators or laboratory testing and verification requirements.

[0052] For example, such as Figure 1B As shown, the MBN file can include a software MBN file (mcfg_sw.mbn) and a hardware MBN file (mcfg_hw.mbn). Loading the software MBN file requires the hardware MBN file as a basis. The hardware MBN file can include configuration information about the electronic device's hardware capabilities related to the wireless communication network, such as whether the electronic device is configured with a single SIM card or multiple SIM cards. The software MBN file can include configuration information about the software capabilities related to the wireless communication network, such as access point name (APN) parameters, whether it supports the GEA (GSM Encryption) algorithm, and whether it supports the A5 algorithm. Both GEA and A5 algorithms are encryption algorithms used to encrypt data during wireless communication transmission to protect the confidentiality and integrity of user data.

[0053] Additionally, MBN files can also include custom MBN files, which may include custom NV parameters (or custom network parameters) and / or custom area parameters to meet specific needs. Custom area parameters represent the network parameters of an electronic device within a specific area. Custom MBN files can also be described as MBN files customized by OEM manufacturers, or simply OEM MBN files.

[0054] Region: This indicates the region where the electronic device is shipped. For example, if the region of an electronic device is DEF-EU, it means that the electronic device is shipped from Europe. Region information can be written into the electronic device; it is part of the device's hardware information. When an electronic device leaves the factory, it usually has a default region value. In COTA (Cota on Demand) upgrade scenarios, the region information of the electronic device may change.

[0055] A universal SIM-enabled MBN file refers to the MBN file corresponding to the operator of the SIM card in an electronic device. The universal SIM-enabled MBN file provides fixed network parameters. As long as a SIM card from operator A is inserted into the electronic device, regardless of the current area of ​​the device, the electronic device will use the MBN file corresponding to operator A for wireless communication, such as mobile communication.

[0056] A region-specific MBN file refers to the MBN file of the operator within the region where the electronic device is currently located; in other words, it refers to the operator's MBN file for that region. The region-specific MBN file corresponds to both the operator and the region. An operator may be able to provide mobile networks in different regions, and correspondingly, the operator's configuration requirements for mobile network (or mobile communication) parameters may differ in different regions. Therefore, configuring the operator's MBN files for different regions is used to configure the mobile network parameters.

[0057] For example, if the electronic device is currently in area 1, and there are MBN files corresponding to operator A and operator B in area 1, and the SIM card of the electronic device is operated by operator A, then the electronic device uses the MBN file corresponding to operator A in area 1 for mobile communication.

[0058] In some embodiments, electronic devices, in specific scenarios (such as SIM card insertion, COTA upgrades, etc.), need to initialize the MCFG framework and load the MBN file to utilize the network parameters of the MBN file for wireless communication with the network side, such as mobile communication. The specific process may be as follows: Figure 2 As shown, firstly, the electronic device loads the default configured MBN file, which can include both a default hardware MBN file and a default software MBN file. This prevents the electronic device from being unable to perform mobile communication if a customized MBN file or a generic SIM card MBN file is missing. Next, the electronic device obtains the SIM card information and loads the generic SIM card MBN file corresponding to that information. This generic SIM card MBN file represents the generic SIM card MBN file corresponding to the operator to which the SIM card information belongs. This generic SIM card MBN file also includes both generic software MBN files and generic hardware MBN files.

[0059] Because the general-purpose SIM-acquired MBN file has a higher priority than the default-configured MBN file, the electronic device uses this general-purpose SIM-acquired MBN file to configure network parameters for mobile communication with the network. Alternatively, the electronic device can also use the default-configured MBN file for mobile communication; the process can be found in the description below of using both the general-purpose SIM-acquired MBN file and a customized MBN file.

[0060] Specifically, when an electronic device has a single SIM card installed, it can load the generic MBN file corresponding to that SIM card's SIM card information. When multiple SIM cards are installed, regardless of whether they operate with the same carrier, for each SIM card, the electronic device can read its SIM card information to load the corresponding generic MBN file. Then, the electronic device can perform mobile communication based on the network parameters of the generic MBN file corresponding to the target SIM card's SIM card information. In short, even if multiple generic MBN files are loaded, only one of them has active network parameters. The target SIM card is the SIM card used to access the mobile network, such as... Figure 3 The SIM card corresponding to card 1 shown is the target SIM card.

[0061] However, the area of ​​an electronic device may change, and operators have different requirements for the configuration of mobile network parameters in different areas. However, the electronic device still interacts with the network side according to the network parameters in the corresponding general MBN file of the operator. That is, it conducts mobile communication in different areas according to fixed network parameters, which cannot meet the characteristic requirements of operators in different areas and leads to the restriction of mobile communication of electronic devices.

[0062] For example, the GEA algorithm status parameter in the general SIM card MBN file for operator A is set to 0 (indicating it's off), meaning that GEA encryption is not allowed in mobile communications. However, in a COTA upgrade scenario, the electronic device switches to area 1. Operator A supports GEA in area 1, so ideally, the GEA algorithm status parameter in area 1 should be set to 1 (indicating it's on), allowing GEA encryption in mobile communications. However, the electronic device still uses the general SIM card MBN file, preventing it from using GEA for encryption and thus failing to meet operator A's requirements in area 1, ultimately limiting mobile communication.

[0063] Optionally, before loading the generic MBN file included with the card, if a custom MBN file exists in the electronic device, such as...Figure 4 As shown, the electronic device can also load a customized MBN file. As mentioned above, a customized MBN file can include customized area parameters. Then, the electronic device obtains the SIM card information and loads the general MBN file corresponding to the SIM card information. Afterwards, the electronic device can configure itself based on the network parameters in the customized MBN file or the general MBN file to conduct mobile communication with the network side.

[0064] Specifically, the customized MBN file has a lower priority than the general MBN file included with the SIM card. In this case, for network parameters that are not present in the general MBN file but exist in the customized MBN file, the electronic device can directly configure the device based on the parameter value in the customized MBN file. However, for network parameters that exist in both the general MBN file and the customized MBN file, the electronic device can configure the device based on the parameter value in the general MBN file.

[0065] In addition, for network parameters that exist in the general MBN file but not in the customized MBN file, electronic devices can be configured based on the network parameters in the general MBN file.

[0066] However, while electronic devices can configure network parameters using customized area parameters in the customized MBN file, different operators within the same area may have different requirements for network parameter configuration. For example, they may have different requirements for APN parameters, GEA algorithm status parameters, and A5 algorithm status parameters. But electronic devices can only use these customized area parameters for configuration. In other words, electronic devices can only use general area parameters to communicate with different operators and cannot meet the configuration requirements of different operators. For instance, operator A might want the GEA algorithm status parameter value to be 1 in area 1, while operator B might want it to be 0. However, the customized area parameters for the GEA algorithm status parameter are set to 1, therefore, operator B's configuration requirements cannot be met.

[0067] In addition, due to platform limitations, for network parameters that exist in both the general SIM card MBN file and the custom MBN file, the electronic device can be configured based on the parameter value of the network parameter in the general SIM card MBN file, which will also limit the network capabilities of the electronic device.

[0068] Therefore, this application adds a region-specific MBN file. In specific scenarios (such as card insertion, OTA upgrades, etc.), the electronic device initializes the MCFG framework. For example... Figure 5As shown, the electronic device can obtain the latest area information and SIM card information. Then, the electronic device can search from a specific directory for a target area-specific MBN file corresponding to the latest area information and SIM card information. This target area-specific MBN file represents the network parameter configuration rules (i.e., configuration requirements) for mobile communication under the latest area by the operator corresponding to the SIM card information.

[0069] When a target area-specific and SIM card-specific MBN file exists, the electronic device can load this file. Then, based on the network parameters in the MBN file, the device can configure its network to communicate with the network equipment (or network side, such as a base station) of the operator corresponding to the SIM card information. Therefore, the electronic device can include MBN files corresponding to different operators in different areas. The device can perform mobile communication based on the network parameter configuration requirements of the operator in the latest area (i.e., the operator in the latest area), satisfying the characteristics of different areas and operators (i.e., meeting the configuration requirements of the same operator in different areas, or different operators in the same area). This allows the electronic device to use both area-specific and SIM card-specific MBN files for mobile communication, achieving flexible configuration of network parameters and avoiding limitations on the device's network capabilities.

[0070] In the absence of the aforementioned target area-specific MBN file, the electronic device can obtain and load the universal MBN file corresponding to the SIM card information. Network configuration is then performed based on the network parameters within the universal MBN file, enabling mobile communication using these configured network parameters. This satisfies the operator's general configuration requirements, ensuring the electronic device can perform mobile communication.

[0071] For example, the aforementioned electronic device may be a mobile phone, tablet computer, wearable device (such as a smartwatch), personal digital assistant (PDA), router, laptop computer, in-vehicle device, Internet of Things device, etc., which is equipped with a SIM card, that is, a device capable of mobile communication. The embodiments of this application do not impose any special restrictions on the specific form of the electronic device.

[0072] Figure 6 A schematic diagram of the structure of the electronic device 100 is shown.

[0073] Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and SIM card interface 195, etc.

[0074] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0075] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor (or modem, baseband processor), graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), and / or neural network processing unit (NPU), etc. The different processing units may be independent devices or integrated into one or more processors.

[0076] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

[0077] The processor 110 may also include a memory for storing instructions and data. In some embodiments, 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 retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0078] In some embodiments, the processor 110 may include one or more interfaces. 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 subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0079] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0080] The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, internal memory 121, external memory, display 194, camera 193, and wireless communication module 160, etc.

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

[0082] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0083] The mobile communication module 150 can provide solutions for mobile communication (or mobile networks) including 2G / 3G / 4G / 5G, applied to the electronic device 100. 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 some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, 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.

[0084] 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 some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0085] 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 Wi-Fi), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), and other wireless communication technologies.

[0086] In some embodiments, 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).

[0087] The electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

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

[0089] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the electronic device 100.

[0090] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. 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.

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

[0092] The aforementioned sensor module 180 may include one or more of the following: pressure sensor, gyroscope sensor, barometric pressure sensor, magnetic sensor, accelerometer, distance sensor, proximity sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor, and bone conduction sensor.

[0093] Buttons 190 include a power button, volume buttons, etc. Motor 191 can generate vibration feedback. Indicator 192 can be an indicator light.

[0094] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0095] Optionally, the electronic device 100 can read SIM card information from the SIM card, such as the mobile country code (MCC), mobile network code (MNC), and integrated circuit card identity (ICCID). The SIM card information can be used to determine the operator to which the SIM card belongs (or described as the operator corresponding to the SIM card), thereby determining the corresponding MBN file.

[0096] This application provides a communication method. An electronic device can place region-specific and SIM card-specific MBN files corresponding to different operators in different regions in a specific directory. When conditions are met to trigger loading of the MBN file, the electronic device can read the region-specific and SIM card-specific MBN file corresponding to the latest region of the electronic device and the operator to which the electronic device's SIM card belongs from the specific directory. This MBN file can then be used for network configuration, enabling mobile communication with network equipment, meeting the configuration requirements of the region and operator, and preventing restrictions on the electronic device's mobile communication.

[0097] For example, the conditions for triggering the loading of the MBN file may include the electronic device being in a SIM card insertion scenario or the electronic device undergoing an OTA upgrade (such as a COTA upgrade). The following example, using a mobile phone as the electronic device and the electronic device undergoing a COTA upgrade, illustrates the communication method provided in this application. Figure 7 As shown, the communication method may include:

[0098] S301. In response to a click on the update control, the mobile phone receives an upgrade data packet sent by the server. The upgrade data includes area information 1 for area 1, and at least one MBN file corresponding to the area and SIM card for each operator under area 1.

[0099] In this context, the MBN file associated with the operator in Area 1 (or the first area) represents the network parameter configuration rules for the mobile network under that operator in Area 1, i.e., the network parameter configuration requirements for electronic devices under that operator in Area 1. For example, if Area 1 includes operator A and operator B, the upgrade data package may include the MBN file associated with operator A and operator B in Area 1.

[0100] Generally, the aforementioned card-specific MBN file can include both hardware MBN files and software MBN files. However, it is also possible that the card-specific MBN file may include either a hardware MBN file or a software MBN file.

[0101] In this embodiment, when a mobile network configuration update is required, the mobile phone can display an update prompt message and a corresponding update control. This update control triggers the phone to perform an update. After receiving a user's click on the update control, the electronic device downloads an upgrade data package from the server for a Cota update. Additionally, the phone can also display a cancel control corresponding to the update prompt message, which triggers the phone to stop the update.

[0102] Of course, triggering a COTA upgrade on an electronic device via an update control is just one example; there are other ways to trigger a COTA upgrade. For instance, if a user sets up automatic updates, the electronic device can automatically download the upgrade data package from the server when a mobile network configuration update is needed.

[0103] S302. The mobile phone places at least one MBN file corresponding to the card and region under region 1 in directory 1.

[0104] For example, the above-mentioned directory 1 and directory 2, which belongs to the general SIM card MBN file corresponding to the existing operator on the mobile phone, are at the same level. That is to say, directory 1 (or the second directory) and directory 2 (or the third directory) are parallel directories, so that the region-specific SIM card MBN file and the general SIM card file are parallel.

[0105] For example, directory 1 could be like this: Figure 8 The directory shown is carrier / vendorcountry, and directory 2 is the common directory. Figure 8 TELCEL_MX in the text can be the aforementioned area 1. The operator 4 under TELCEL_MX indicates the area-specific MBN file corresponding to operator 4 under area 1 (which can be used as an example of the first MBN file). Additionally... Figure 8 The common directory contains the general MBN file for operator 1, operator 2, operator 3, and operator 4.

[0106] The above Figure 8 The operator 1 under DEF_EU refers to the MBN file corresponding to operator 1 under DEF_EU, which is associated with the region and card. The operator 2 under DEF_EU refers to the MBN file corresponding to operator 2 under DEF_EU, which is associated with the region and card.

[0107] Similarly, Figure 8In DEF_LA, Carrier 1 refers to the MBN file corresponding to Carrier 1 under DEF_LA, which is associated with the region and card. Carrier 2 under DEF_LA refers to the MBN file corresponding to Carrier 2 under DEF_EU, which is associated with the region and card.

[0108] It should be noted that directory 1 can be created by the mobile phone when creating directory 2, or when the mobile phone first obtains the MBN file with the region and card. This application does not restrict the timing of the creation of directory 1.

[0109] S303. For each operator under the above-mentioned area 1, the mobile phone generates the group index 1 corresponding to the MBN file of the area and card for that operator.

[0110] S304. The mobile phone adds the group index 1 corresponding to the operator to the general SIM card MBN file directory corresponding to the operator under directory 2, so that the area-specific SIM card MBN file corresponding to the operator and the general SIM card MBN file corresponding to the operator belong to the same group.

[0111] Optionally, the mobile phone will also add the group index 1 corresponding to the above-mentioned operator to the corresponding card file directory under directory 1.

[0112] Continuing with the example above, the group index 1 corresponding to the carrier-specific MBN file for carrier 4 under TELCEL_MX (which can be used as an example of the first directory corresponding to the first region) is hn_mcfg_sw_gen_carrier4.xml. This group index 1 is added to the general MBN file directory for carrier 4 in directory 2 (i.e., under Carrier / common / carrier4) and to the carrier-specific MBN file directory for carrier 4 in directory 1 (i.e., under carrier / vendorcountry / carrier4). This allows the carrier-specific MBN file for carrier 4 under TELCEL_MX to be referenced in the general MBN file for carrier 4 via a group, thus establishing a connection between the carrier-specific MBN file and the general MBN file for carrier 4. This enables the mobile phone to compile the carrier-specific MBN file for carrier 4.

[0113] For example, the implementation code that adds group index 1 of hn_mcfg_sw_gen_carrier4.xml to Carrier / common / carrier4 may include:

[0114] <xml verstion="1.0"encoding="utf-8">

[0115] <NvData McfgXmlVersion="2.0">

[0116] <NvConfigurationData carrierIndex="0" version="mcfg.0.0" type="1" / >

[0117] <NvItemData ="Banner" id="71" description="" comment="" category="Display" Subscription_mask="0x07" mcfgAttributes="0x19" mcfgVariant="1">

[0118] <Member name="letters" description="" comment="" sizeof="13" type="string">TELCEL_MX

[0119]

[0120] <GroupFile namse="hn_mcfg_sw_gen_Operator 4.xml" description="vendorcountry for TELCEL_MX" buildpath="carier / vendorcountry / TELCEL_MX / Operator 4 / hn_mcfg_sw_gen_Operator 4.xml" / >

[0121]

[0122] It should be noted that the above-mentioned association relationship between the per-region per-card MBN file corresponding to the operator under Area 1 established by the group method and the general per-card MBN file corresponding to the operator is only an example. The mobile phone can also establish the association in other ways. For example, by writing the association relationship at a specified location, such as writing the identifier (such as the name) of the per-region per-card MBN file corresponding to the operator and the identifier of the general per-card MBN file corresponding to the operator to the specified location, the establishment of the association relationship can be achieved, so that when the mobile phone compiles the general per-card MBN file, it can compile the associated general per-card MBN file.

[0123] S305. The mobile phone compiles the general per-card MBN file corresponding to the operator under Directory 2 of the mobile phone compilation, and based on the above Group Index 1, compiles the per-region per-card MBN file corresponding to the operator.

[0124] In this embodiment, for each operator under region 1, since index 1 exists in the general SIM-attached MBN file directory corresponding to that operator, meaning that the region-attached MBN file (or fourth MBN file) corresponding to that operator is already referenced in the general SIM-attached MBN file (or fifth MBN file), the mobile phone will compile the region-attached MBN file corresponding to that operator during the compilation of the general SIM-attached MBN file, thereby generating both the general SIM-attached MBN file and the region-attached MBN file corresponding to that operator. These two compiled files can be located in the modem image directory.

[0125] Continuing with the example above, the mobile phone compiles the general SIM-attached MBN file corresponding to Carrier 4 and the area-specific SIM-attached MBN file corresponding to Carrier 4, generating two compiled MBN files. One is the compiled file for the general SIM-attached MBN file corresponding to Carrier 4, located in the directory common / carrier4 / mcfg_sw.mbn, and the other is the compiled file for the area-specific SIM-attached MBN file corresponding to Carrier 4, located in the directory common / TELCEL_MX / carrier4 / mcfg_sw.mbn. This allows the two MBN files to be embedded into the Modem mapping.

[0126] In some embodiments, since the MBN file corresponding to the operator under region 1 is imported into the general MBN file corresponding to that operator, the general MBN file corresponding to that operator changes. Therefore, the mobile phone recompiles the general MBN file corresponding to that operator. However, for the general MBN file that has not changed (i.e., the general MBN file corresponding to an operator that is different from any operator under region 1), and for non-new MBN files (i.e., MBN files other than the MBN files corresponding to the operators under region 1 mentioned above; in other words, MBN files that the mobile phone already has), the mobile phone does not need to recompile the unchanged general MBN files and non-new MBN files.

[0127] Continuing with the example above, when using the new carrier 4's corresponding area-specific MBN file, the phone does not need to compile the general MBN files corresponding to carriers 1-3 in the common directory, the area-specific MBN files corresponding to carriers 1-2 in the DEF_EU area under the vendorcountry directory, and the area-specific MBN files corresponding to carriers 1-2 in the DEF_LA area.

[0128] Of course, when adding a new card-specific MBN file, the mobile phone can also compile all general card-specific MBN files and card-specific MBN files on the phone. This application does not restrict this.

[0129] In some embodiments, the compiled MBN file can be obtained by the mobile phone compiling the MBN file in the upgrade data package, or the compiled MBN file can be sent directly by the server, and the mobile phone does not need to compile it and can save it directly. In other words, the above steps S03-S304 are optional.

[0130] The above describes the process of compiling the MBN file into a binary executable file using a mobile phone. Additionally, in a COTA upgrade scenario, the phone's region settings may change. After such a change, the phone can update its region settings. The following section uses the S307 as an example to illustrate the process of updating the region settings.

[0131] S306. The mobile phone updates the area information in the mobile phone to the area information 1 of the aforementioned area 1.

[0132] The area information can be the identifier for area 1. After receiving area information 1 in the upgrade data packet, the mobile phone can set area information 2 (or the second area information of the second area) recorded by the mobile phone as area information 1. It is understandable that when the mobile phone is in area 2, the loading of the MBN file is consistent with the MBN file judgment and loading process described below. For example, it first checks whether a region-specific MBN file corresponding to area 2 and the operator to which the SIM card belongs exists. If it exists, the mobile phone can load that region-specific MBN file. If it does not exist, the mobile phone will load the general MBN file corresponding to that operator.

[0133] For example, the mobile phone can set the area configuration item in the oeminfo configuration item or AP configuration item to area information 1, such as vendorcontry=DEF_EU, where vendorcontry is the area configuration item and DEF_EU is area information 1, thereby updating the area information.

[0134] In a COTA upgrade scenario, the phone will also initialize the MCFG framework. The initialization process of the MCFG framework will be described below.

[0135] S307, the phone loads the compiled file of the default configuration MBN file.

[0136] S308, the mobile phone loads a compiled file of a customized MBN file.

[0137] The implementation process of S307-S308 can be referred to the relevant description above, and will not be repeated here.

[0138] S309. When a single SIM card is installed in the mobile phone, the mobile phone reads the area information 1 and the SIM card information of the SIM card.

[0139] For example, the mobile phone can read the latest area information from the area configuration item in the oeminfo configuration item or AP configuration item, i.e., the area information 1 mentioned above. The mobile phone can also read SIM card information from the SIM card.

[0140] S310. The mobile phone determines whether there is a universal accompanying MBN file 1 in directory 1 that corresponds to the area information 1 and SIM card information.

[0141] In this embodiment of the application, if a region-specific MBN file 1 (which can be used as an example of a first MBN file) corresponding to region information 1 and SIM card information exists, the mobile phone can execute S311. If a region-specific MBN file 1 does not exist, the mobile phone can execute S314.

[0142] S311, The mobile phone loads the compiled file of MBN file 1, which is attached to the card and region.

[0143] For example, the mobile phone reads the compiled file of the MBN file 1 with the region and card from the Modem image, runs the compiled file, and saves the network parameters in the MBN file 1 with the region and card on the mobile phone. That is, the configuration of the mobile network of the operator to which the SIM card belongs in the region is saved on the mobile phone, thereby loading the compiled file of MBN file 1 with the region and card.

[0144] S312. The mobile phone loads the compiled file of the general MBN file 1 corresponding to the SIM card information. Among them, the general MBN file 1 has a lower priority than the MBN file 1 with the region information mentioned above.

[0145] S313: The mobile phone interacts with the network side based on the network parameters in the SIM card-specific MBN file 1 and the general SIM card-specific MBN file 1.

[0146] In some embodiments, after loading the area-specific MBN file 1, the mobile phone can continue to load the general MBN file 1 (which can be used as an example of a second MBN file), so that the mobile phone can perform network configuration using both the operator's specific configuration requirements under area 1 and the operator's general configuration requirements.

[0147] Specifically, since the priority of the general SIM card MBN file 1 is lower than that of the region-specific SIM card MBN file 1, for network parameters that exist in both the general SIM card MBN file 1 and the region-specific SIM card MBN file 1, the mobile phone can configure the network parameters based on the parameter values ​​in the region-specific SIM card MBN file 1.

[0148] In addition, for network parameters that do not exist in the general SIM card MBN file 1 but exist in the region-specific SIM card MBN file 1, the mobile phone can configure them based on the parameter values ​​of the network parameters in the region-specific SIM card MBN file 1.

[0149] Furthermore, for network parameters that exist in the general SIM card MBN file 1 but not in the area-specific SIM card MBN file 1, the mobile phone can configure the network parameters based on the parameter values ​​in the general SIM card MBN file 1.

[0150] In this embodiment, the mobile phone accesses the mobile network provided by the corresponding operator based on the network parameters in the area-specific MBN file 1, thereby updating the mobile network and meeting the specific configuration requirements of the operator for network parameters in area 1. For example, the GEA algorithm status parameter is configured to be 0 (indicating off) in the general SIM-specific MBN file 1 (common / operator4 / mcfg_sw.mbn). However, in a COTA upgrade scenario, when the mobile phone switches to area 1, the mobile network provided by operator4 in area 1 can support the algorithm capability. The area-specific MBN file 1 (e.g., common / TELCEL_MX / operator4 / mcfg_sw.mbn) is configured with the GEA algorithm status parameter set to 1 (indicating on), enabling the mobile phone to use the GEA algorithm to encrypt the transmitted communication data, enhancing the network capabilities of the electronic device and improving the user experience.

[0151] In some embodiments, the aforementioned area-specific MBN file 1 may only include the specific configuration requirements of the operator to which the SIM card information 1 belongs in area 1. In this case, the mobile phone can coordinate the configuration with the general network parameters in the general MBN file 1 corresponding to that operator. Alternatively, the area-specific MBN file 1 may also include the general network parameters in the general MBN file 1. Simply put, the area-specific MBN file 1 may include all the files required for mobile communication, allowing the mobile phone to load only the area-specific MBN file 1 without loading the general MBN file. Correspondingly, the mobile phone can interact with the network side based on the network parameters in the area-specific MBN file 1.

[0152] Sections S311-S313 above described the process of mobile communication based on a region-specific MBN file 1 corresponding to the latest region of the mobile phone (i.e., region 1 mentioned above) and the operator to which the SIM card belongs, in a single-SIM card scenario. Alternatively, there may be a situation where this region-specific MBN file 1 does not exist. The following section will continue to describe how the mobile phone performs mobile communication in this case.

[0153] S314. The mobile phone loads the compiled file of the general accompanying MBN file 1 corresponding to the SIM card information.

[0154] S315 The mobile phone interacts with the network side based on the network parameters in the compilation file of the aforementioned general SIM card MBN file 1.

[0155] The implementation process of S314-S315 can be referred to the description of mobile communication based on the general SIM card MBN file above, and will not be repeated here.

[0156] The above describes how a mobile phone uses the MBN file for mobile communication when a single SIM card is installed. Of course, there are also cases where a mobile phone has multiple SIM cards. The following will use a multi-SIM phone, including SIM card 1 and SIM card 2, as an example to illustrate how the phone performs mobile communication.

[0157] S316, The mobile phone reads area information 1, SIM card information 1 of SIM card 1 and SIM card information 2 of SIM card 2.

[0158] S317. If a region-specific MBN file 2 corresponding to region information 1 and SIM card information 1 exists in directory 1, the mobile phone loads the region-specific MBN file 2.

[0159] S318. The mobile phone loads the general MBN file 2 corresponding to the SIM card information 1. Among them, the general MBN file 2 has a lower priority than the area-specific MBN file 2 mentioned above.

[0160] For example, the mobile phone can determine whether the aforementioned area-specific and card-specific MBN file 2 exists (which can be used as an example of the first MBN file). If it exists, the mobile phone can directly load the area-specific and card-specific MBN file 2 to meet the network parameter configuration requirements of the operator to which SIM card 1 belongs in area 1. Alternatively, if it does not exist, the mobile phone can directly load the general card-specific MBN file 2 corresponding to SIM card information 1 (which can be used as an example of the second MBN file).

[0161] S319. If there is no corresponding MBN file 3 for area information 1 and SIM card information 2 in directory 1, the mobile phone loads the general MBN file 3 corresponding to SIM card information 2.

[0162] For example, the mobile phone can determine whether the aforementioned area-specific and card-specific MBN file 3 exists (which can be used as an example of the first MBN file). If it does not exist, the mobile phone can directly load the general card-specific MBN file 3 corresponding to SIM card information 2 (which can be used as an example of the second MBN file). Alternatively, if it exists, the mobile phone can directly load the area-specific and card-specific MBN file 3 to meet the specific network parameter configuration requirements of the operator to which SIM card 2 belongs in area 1.

[0163] The above describes the process of initializing the MCFG framework and loading the MBN file in a multi-SIM card scenario. The following section will describe the process of mobile communication after initialization.

[0164] S320. When SIM card 1 is the target SIM card, the mobile phone interacts with the network side based on the network parameters in the above-mentioned area-specific MBN file 2 and general MBN file 2.

[0165] As mentioned earlier, the target SIM card is a SIM card used to access the mobile network; simply put, the target SIM card is an internet access card.

[0166] S321. When SIM card 2 is the target SIM card, the mobile phone interacts with the network side based on the network parameters in the aforementioned general accompanying MBN file 3.

[0167] The implementation process of S316-S321 can be referred to the description of S309-S315 above, and will not be repeated here.

[0168] In some embodiments, during a COTA upgrade, if the phone's region information remains unchanged—for example, if the phone's region before the COTA upgrade was region 1, and the region information in the upgrade data packet received by the phone is still that of region 1—then the phone does not need to execute the implementation process described in S301-S321, thereby avoiding unnecessary loading of the MBN file and thus avoiding unnecessary resource waste. Of course, the phone can still continue to execute S301-S321, or it can skip S302-S306 and directly load the MBN file corresponding to the operator to which the SIM card information under region 1 already belongs.

[0169] It should be noted that regardless of whether SIM card 1 and SIM card 2 belong to the same operator, the mobile phone can separately determine whether a region-specific MBN file exists for each SIM card in order to load the corresponding MBN file for each SIM card. Furthermore, to avoid unnecessary checks, if SIM card 1 and SIM card 2 belong to the same operator, since the region information and operator are identical, it is only necessary to check whether a region-specific MBN file exists for either SIM card 1 or SIM card 2.

[0170] Furthermore, the area code of a mobile phone is independent of its location. For example, even when the phone is in the same location, its area code can still change.

[0171] It is understandable that the step numbers mentioned above do not necessarily represent the execution order of the steps; the execution order can be set according to requirements. For example, the phone can first generate the compiled MBN file corresponding to the carrier under region 1, or it can modify the region information first. Alternatively, the phone can concurrently compile the MBN file and modify the region information. Furthermore, the compilation of the MBN file and the modification of the region information can be performed concurrently with the MCFG framework initialization, or sequentially; simply complete the compilation of the MBN file before loading the compiled MBN file for the region and SIM card, and modify the region information before obtaining it.

[0172] Of course, the above-mentioned COTA scenario is only an exemplary scenario for triggering the phone to initialize the MCFG framework, that is, for the phone to configure the network. The phone can also trigger the MCFG framework initialization in other scenarios. For example, in the case of inserting a SIM card, such as inserting a SIM card for the first time or reinserting a SIM card after removing it, the phone will also trigger the MCFG framework initialization. For example, after inserting a SIM card, if the phone's SIM card changes, such as adding a new SIM card, the phone can determine whether there is a corresponding area-specific MBN file 4 in the phone's existing area-specific MBN files that matches the phone's latest area information and the SIM card information of the new SIM card. If it exists, the phone can load the area-specific MBN file 4 (or, as described, load the compiled file of the area-specific MBN file 4), and then the phone can continue to load the general MBN file 4 corresponding to the new SIM card information (or, as described, load the compiled file of the general MBN file 4). If it does not exist, the phone can directly load the general MBN file 4.

[0173] Optionally, the phone can determine whether to use the region-specific MBN file 4, regardless of whether the operator of the newly added SIM card is the same as that of the existing SIM card. Alternatively, the determination of whether the region-specific MBN file 4 exists can only be made if the operator of the newly added SIM card is different from that of the existing SIM card.

[0174] Optionally, in the case of multiple SIM cards, if some SIM cards are removed, although the SIM cards change, the phone does not need to reload the MBN file, i.e., it does not need to perform the above-mentioned MCFG framework initialization. Additionally, if the installation position of the SIM cards in the phone changes, since the SIM card installed in SIM slot 1 is installed in SIM slot 2, although the SIM cards change, the phone also does not need to perform the above-mentioned MCFG framework initialization.

[0175] The above primarily describes the solutions provided by the embodiments of this application from a methodological perspective. It is understood that, in order to achieve the above functions, the electronic device includes hardware structures and / or software modules corresponding to the execution of each function. Based on the units and algorithm steps of the various examples described in the embodiments disclosed in this application, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by a computer driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solutions of the embodiments of this application.

[0176] This application provides embodiments for dividing an electronic device into functional modules based on the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into a single processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the unit division in this application embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used.

[0177] like Figure 9 The diagram shown is a structural schematic of an electronic device provided in an embodiment of this application. This electronic device 1000 can be used to implement the methods executed by the electronic devices described in the above method embodiments. For example, the electronic device 1000 may include a processing unit 1001, a communication unit 1002, and a display unit 1003. The processing unit 1001 is used to support the electronic device 1000 in executing... Figures 1A to 8The electronic device described in any one of the following embodiments includes a communication unit 1002 for supporting the communication function of the electronic device 1000, and a display unit 1003 for supporting the display function of the electronic device 1000.

[0178] Optional, Figure 9 The illustrated electronic device 1000 may also include a storage unit ( Figure 9 (not shown in the image), this storage unit stores a program or instruction. When the processing unit 1001 executes the program or instruction, it causes... Figure 9 The electronic device 1000 shown can perform the method described in the above-described method embodiments.

[0179] Figure 9 The technical effects of the electronic device 1000 shown can be referred to the technical effects described in the above method embodiments, and will not be repeated here. Figure 9 The processing unit 1001 in the illustrated electronic device 1000 can be implemented by a processor or processor-related circuit components, and can be a processor or processing module. The communication unit 1002 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver module. The display unit 1003 can be implemented by display screen-related components.

[0180] This application also provides a chip system, such as... Figure 10 As shown, the chip system includes at least one processor 1101 and at least one interface circuit 1102. The processor 1101 and the interface circuit 1102 are interconnected via lines. For example, the interface circuit 1102 can be used to receive signals from other devices. As another example, the interface circuit 1102 can be used to send signals to other devices (e.g., the processor 1101). Exemplarily, the interface circuit 1102 can read instructions stored in memory and send those instructions to the processor 1101. When the instructions are executed by the processor 1101, the electronic device can perform the various steps performed by the electronic device in the above embodiments. Of course, the chip system may also include other discrete components, and this application embodiment does not specifically limit this.

[0181] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0182] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application does not specifically limit the type of memory or the arrangement of the memory and processor.

[0183] For example, the chip system may be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0184] It should be understood that each step in the above method embodiments can be completed by integrated logic circuits in the processor hardware or by instructions in software form. The method steps disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0185] This application also provides a computer storage medium storing computer instructions, which, when executed on an electronic device, cause the electronic device to perform the communication method described in the above method embodiments.

[0186] This application provides a computer program product, which includes a computer program or instructions that, when executed on an electronic device, cause the electronic device to perform the communication method described in the above method embodiments.

[0187] In addition, this application embodiment also provides an apparatus, which may specifically be a chip, component, or module. The apparatus may include a connected processor and a memory; wherein the memory is used to store computer execution instructions. When the apparatus is running, the processor can execute the computer execution instructions stored in the memory to cause the apparatus to perform the communication methods in the above-described method embodiments. The electronic devices, computer storage media, computer program products, or chips provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to in the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0188] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0189] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The embodiments can be combined with or referenced to each other without conflict. The apparatus embodiments described above are merely illustrative; for example, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0190] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0191] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0192] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0193] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: If the conditions for triggering the loading of the modem boot network MBN file are met, and if a first MBN file corresponding to the first area information of the electronic device and the user identification module SIM card information of the electronic device exists, then the first MBN file is loaded. Wherein, the first MBN file represents the configuration rules of the network parameters for mobile communication of the first operator corresponding to the SIM card information under the first area indicated by the first area information; the first area represents the area where the electronic device is currently located; Based on the first MBN file, mobile communication is conducted with network devices.

2. The method according to claim 1, characterized in that, The method further includes: If the first MBN file does not exist, then the second MBN file corresponding to the SIM card information is loaded; wherein, the second MBN file represents the general configuration rules of the first operator for the network parameters of mobile communication.

3. The method according to claim 1 or 2, characterized in that, After loading the first MBN file, the method further includes: Load the second MBN file corresponding to the SIM card information; Based on the first MBN file and the second MBN file, mobile communication is performed with the network device.

4. The method according to any one of claims 1 to 3, characterized in that, The electronic device includes multiple SIM cards; If a first MBN file exists corresponding to the first region information of the electronic device and the SIM card information of the electronic device, then loading the first MBN file includes: For each SIM card, if a first MBN file exists corresponding to the first area information and the SIM card information, then the first MBN file corresponding to the SIM card information is loaded; The step of conducting mobile communication with network devices based on the first MBN file includes: Based on the first MBN file corresponding to the SIM card information of the target SIM card, mobile communication is performed with the network device; wherein, the target SIM card is the SIM card used for accessing the mobile network among the multiple SIM cards.

5. The method according to any one of claims 1 to 4, characterized in that, The first MBN file is located in the first directory corresponding to the first region, and the first directory corresponding to the first region is used to store the MBN files corresponding to the operators in the first region. The first directory corresponding to the first region is located under the second directory, which is used to store MBN files corresponding to operators in different regions; The second MBN file belongs to the third directory, which is used to store MBN files corresponding to different operators; The second directory is listed alongside the third directory.

6. The method according to any one of claims 1 to 5, characterized in that, The conditions that trigger loading of the MBN file include the electronic device being in an over-the-air (OTA) upgrade download scenario or the SIM card of the electronic device changing.

7. The method according to claim 6, characterized in that, The conditions for triggering the loading of the MBN file include the electronic device being in an OTA upgrade scenario; Before the conditions for triggering the loading of the MBN file are met, the method further includes: In the presence of a third MBN file corresponding to the second region information and the SIM card information of the electronic device, mobile communication is performed with the network device based on the third MBN file; wherein the second region information is different from the first region information; In the absence of the third MBN file, mobile communication with the network device is performed based on the second MBN file.

8. The method according to claim 6 or 7, characterized in that, The conditions for triggering the loading of the MBN file include the electronic device being in an OTA upgrade scenario; If a first MBN file exists corresponding to the first region information of the electronic device and the SIM card information of the electronic device, then before loading the first MBN file, the method further includes: Receive upgrade data packets; wherein, the upgrade data packets include the first area information and the fourth MBN file corresponding to at least one operator under the first area; the fourth MBN file corresponding to the operator under the first area represents the network parameter configuration rules of the operator for mobile communication under the first area; The area information of the electronic device is changed from the second area information to the first area information; Wherein, the at least one operator includes the first operator, and the fourth MBN file includes the first MBN file.

9. The method according to claim 8, characterized in that, After receiving the upgrade data packet, the method further includes: Save the fourth MBN file corresponding to at least one operator in the first region in the first directory corresponding to the first region. For each of the at least one operator, compile the fourth MBN file corresponding to that operator.

10. The method according to claim 9, characterized in that, The compilation of the fourth MBN file corresponding to the operator includes: The fourth MBN file corresponding to the operator is referenced in the fifth MBN file corresponding to the operator in the third directory; wherein, the fifth MBN file corresponding to the operator represents the operator's general configuration rules for network parameters of mobile communication; During the compilation of the fifth MBN file corresponding to the operator, the fourth MBN file corresponding to the operator is also compiled.

11. The method according to any one of claims 6 to 10, characterized in that, The change in the SIM card includes the electronic device having a new SIM card installed.

12. An electronic device, characterized in that, The electronic device includes a memory, a SIM card, and one or more processors; the memory, the SIM card, and the processors are coupled; the memory is used to store computer program code, the SIM card is used for mobile communication, and the computer program code includes computer instructions; when the processor executes the computer instructions, the electronic device performs the method as described in any one of claims 1 to 11.

13. A computer-readable storage medium, characterized in that, Includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1 to 11.

14. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 11.

Images