Service registration method and device, chip system and storage medium

Abstract

The invention provides a service registration method and device, a chip system and a storage medium, and the method comprises the steps: enabling a terminal device to obtain a first configuration file from a first position after the terminal device is attached to a network device in a first network, and enabling the first position to be located in a modulation-demodulation processor of the terminal device; when the first configuration file is not the configuration file of the IMS service, the terminal equipment loads a second configuration file at the first position and restarts the modulation-demodulation processor after the second configuration file is loaded, and the second configuration file is the configuration file of the IMS service; and after the modem processor is restarted and the terminal device is attached to the network device in the second network, the terminal device obtains the second configuration file from the first position, and then establishes the PDN connection corresponding to the IMS service based on the second configuration file. By implementing the application, normal registration of the IMS service can be ensured by ensuring normal establishment of the PDN connection corresponding to the IMS service.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a service registration method, device, chip system, and storage medium. Background Technology

[0002] With the gradual retirement of second-generation (2G) and third-generation (3G) networks, voice calls are increasingly relying on Internet Protocol Multimedia Subsystem (IMS) services under fourth-generation (4G) or fifth-generation (5G) networks.

[0003] Whether a terminal device can successfully register for IMS service has a significant impact on the user's call experience. For example, in areas without 2G / 3G network coverage, calls can only be made using IMS service; however, if IMS service cannot be registered properly, calls will be completely impossible. Similarly, in areas with weak 2G / 3G network coverage, calls can be made using either the 2G / 3G network or IMS service; however, if IMS service cannot be registered properly, the terminal device will be forced to revert to voice calls on the 2G / 3G network, resulting in poor call quality and a negative user experience.

[0004] Therefore, ensuring the normal registration of IMS services has become one of the urgent issues to be addressed. Summary of the Invention

[0005] This application provides a service registration method, device, chip system, and storage medium to ensure the normal registration of a first service.

[0006] In a first aspect, embodiments of this application provide a service registration method, applied to an electronic device, a chip system within an electronic device, a device used in conjunction with an electronic device, or a device for implementing the functions of an electronic device, etc. The method includes: when a terminal device attaches to a network device in a first network, the terminal device obtains a first configuration file from a first location, the first location being located in the modem processor of the terminal device; when the first configuration file is not a configuration file for an Internet Protocol Multimedia System (IMS) service, the terminal device loads a second configuration file from the first location, and restarts the modem processor after loading the second configuration file, the second configuration file being a configuration file for the IMS service; after restarting the modem processor, when the terminal device attaches to a network device in a second network, the terminal device obtains the second configuration file from the first location, the second network being the same as or different from the first network; the terminal device establishes a PDN connection corresponding to the IMS service based on the second configuration file.

[0007] When the terminal device obtains a first configuration file from a first location that is not a configuration file for the IMS service, it can reload the configuration file for the IMS service in the first location. Reloading the configuration file for the IMS service in the first location can overwrite the first configuration file in the first location, meaning that the first location no longer includes the first configuration file but includes the configuration file for the IMS service. Therefore, the terminal device can ensure that the PDN connection corresponding to the IMS service can be established normally based on the reloaded configuration file for the IMS service in the first location, thereby ensuring that the IMS service can be registered normally.

[0008] In one possible implementation, after the terminal device obtains the first configuration file from the first location, the method further includes: when the first configuration file is a configuration file for an IMS service, the terminal device establishes a PDN connection corresponding to the IMS service based on the first configuration file.

[0009] In this method, when the first configuration file obtained by the terminal device from the first location is the configuration file of the IMS service, the terminal device can directly establish the PDN connection corresponding to the IMS service based on the first configuration file.

[0010] In one possible implementation, the above method further includes: after the PDN connection corresponding to the IMS service is successfully established, the terminal device registers the IMS service based on the PDN connection corresponding to the IMS service.

[0011] In this method, when the terminal device successfully establishes a PDN connection corresponding to the IMS service according to the above method, the terminal device can normally register the IMS service based on the established PDN connection corresponding to the IMS service.

[0012] In one possible implementation, the method by which the terminal device loads the second configuration file in the first location includes: the terminal device obtaining the most recent registration status of the IMS service; when the most recent registration status indicates that the IMS service registration is successful, the terminal device loads the second configuration file in the first location.

[0013] Since the terminal device must first successfully establish a PDN connection corresponding to the IMS service before it can interact with network devices to register the IMS service, when the most recent registration status indicates successful IMS service registration, it means that the PDN connection corresponding to the IMS service was successfully established in the most recent instance, and therefore, the configuration file in the first location in the most recent instance is the configuration file for the IMS service. Thus, ensuring that the configuration file in the first location is the configuration file for the IMS service at least guarantees the normal establishment of the PDN connection corresponding to the IMS service, thereby ensuring the normal registration of the IMS service. Based on this, in this method, when the terminal device indicates that the most recent registration status indicates successful IMS service registration, attempting to reload the configuration file for the IMS service in the first location makes the reloading of the MBN file more effective.

[0014] In one possible implementation, when the most recent registration status indicates that the IMS service registration is successful, the terminal device loads the second configuration file in the first position, including: when the most recent registration status indicates that the IMS service registration is successful, determining whether the terminal device is in an idle state; when the terminal device is in an idle state, the terminal device loads the second configuration file in the first position.

[0015] In this approach, the terminal device can further reload the IMS service configuration file only when it is in an idle state, which can effectively avoid affecting the running services or functions during reloading, thereby ensuring the user experience.

[0016] In one possible implementation, the aforementioned terminal device being in an idle state includes: the terminal device's screen usage state being off and the terminal device's service state being idle.

[0017] In this approach, when the terminal device's screen is off, it indicates that the user is not currently browsing the screen. Similarly, when the terminal device's service status is idle, it means that no service data is being transmitted, and even some background service data is not being transmitted. This effectively avoids reloading the IMS service configuration file, which would otherwise impact the user experience.

[0018] In one possible implementation, the above method further includes: when the terminal device loads the second configuration file at the first location, the terminal device loads the third configuration file at the second location, the second location being located in the modem processor, the first location being different from the second location, and the third configuration file being different from the second configuration file.

[0019] In this method, the modem processor configures the binary MBN file, which includes a second configuration file and a third configuration file. The terminal device can then load the second configuration file at a first location and the third configuration file at a second location when loading the MBN file. This allows the second configuration file to be loaded at the first location by reloading the MBN file.

[0020] In one possible implementation, before the terminal device attaches to the network device in the first network, the method further includes: the terminal device loading a second configuration file at a first location; the terminal device overwriting the second configuration file in the first location based on a fourth configuration file, wherein the first configuration file is the configuration file in the first location after overwriting, and the service to which the fourth configuration file belongs is different from the service to which the second configuration file belongs.

[0021] For example, if the fourth configuration file is a data service configuration file, then this method is equivalent to the terminal device first loading the IMS service configuration file in the first location, and then overwriting the IMS service configuration file loaded in the first location based on the data service configuration file. Since the IMS service configuration file loaded in the first location is no longer complete after overwriting and does not contain the data service configuration file, the first configuration file obtained by the terminal device in the above method is not the IMS service configuration file.

[0022] In one possible implementation, the method by which the terminal device loads the second configuration file in the first location specifically includes: after the terminal device's operating system is updated and / or restarted, or after the terminal device is turned off and airplane mode is turned on, the terminal device loads the second configuration file in the first location.

[0023] In one possible implementation, the first location is located in the modem processor of the terminal device, including: the first location is the loading location corresponding to the IMS service in the encrypted file system EFS partition, and the EFS partition is located in the modem processor of the terminal device.

[0024] In a second aspect, embodiments of this application provide an electronic device, which includes one or more processors and one or more memories; wherein the one or more memories are coupled to one or more processors, and the one or more memories are used to store computer instructions, which, when the one or more processors execute the computer instructions, cause the electronic device to perform the method in the first aspect or any possible implementation thereof.

[0025] Thirdly, embodiments of this application provide a chip system applied to an electronic device. The chip system includes at least one processor and an interface for receiving computer instructions and transmitting them to the at least one processor. The at least one processor executes the computer instructions to cause the electronic device to perform the method described in the first aspect or any possible implementation thereof.

[0026] Fourthly, embodiments of this application provide a computer-readable storage medium applied to an electronic device. The computer-readable storage medium stores computer instructions, which, when executed by a processor, cause the electronic device to perform the method described in the first aspect or any possible implementation thereof.

[0027] Fifthly, embodiments of this application provide a computer program product containing computer instructions, which, when run on an electronic device, causes the electronic device to perform the method described in the first aspect or any possible implementation thereof. Attached Figure Description

[0028] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0029] Figure 2 This is a schematic diagram of the hardware architecture of an electronic device provided in an embodiment of this application;

[0030] Figure 3 This is a schematic diagram of the hardware and software structure of an electronic device provided in an embodiment of this application;

[0031] Figure 4 This is a schematic diagram of a normal IMS service registration process provided in an embodiment of this application;

[0032] Figure 5 This is a schematic diagram of the hardware and software interaction of a business registration method provided in an embodiment of this application;

[0033] Figure 6 This is a schematic diagram of the configuration files in profile1 to profile3 of a terminal device provided in an embodiment of this application;

[0034] Figure 7This is a schematic diagram of the configuration files in profile1 to profile3 in another terminal device provided in this application embodiment;

[0035] Figure 8 This is a schematic diagram of the hardware and software interaction of a business registration method provided in an embodiment of this application;

[0036] Figure 9 This is a schematic diagram of the overall process of business registration provided in an embodiment of this application;

[0037] Figure 10 This is a schematic diagram of an interface provided in an embodiment of this application. Detailed Implementation

[0038] In the description of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, "at least one" can refer to one or more, and "multiple" can refer to two or more. "First," "second," etc., do not limit the quantity or order of execution, and "first," "second," etc., are not necessarily different.

[0039] The embodiments of this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The embodiments of this application can also be applied to future communication systems, such as 6th generation (6G) mobile communication systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0040] Figure 1 A schematic diagram of the architecture of a communication system provided in an embodiment of this application is shown. Figure 1As shown, the communication system includes network device 110 and terminal device 120. It should be noted that the communication system may also include other devices, but this embodiment does not limit this.

[0041] Network device 110 is a device that connects terminal device 120 to a wireless network. Network device 110 can be a node in a wireless access network, also known as a base station, or a radio access network (RAN) node (or device). The base station can be a distributed antenna system, and the terminal device can communicate with a radio frequency head end of the base station. For example, network equipment 110 may include evolved base stations (NodeBs or eNBs or eNodeBs) in LTE systems or evolved LTE systems (LTE-Advanced, LTE-A), such as traditional macro base stations (eNBs) and micro base stations (eNBs) in heterogeneous network scenarios; or it may include next-generation node Bs (gNBs) in 5G systems, or it may include transmission reception points (TRPs), home base stations (e.g., home evolved NodeBs, or home Node Bs, HNBs), base band units (BBUs), base band pools (BBU pools), or wireless fidelity (Wi-Fi) access points (APs); or it may be base station equipment in 5G or network equipment in future evolved public land mobile networks (PLMNs); or it may be wearable devices or vehicle-mounted devices; or it may include centralized units (CUs) and distributed units (DUs); or it may include non-terrestrial networks. Network devices in NTN (Network Network, NTN) can be deployed on high-altitude platforms or satellites, but this application does not limit the scope of the embodiments.

[0042] Terminal equipment 120, also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a device that includes wireless communication capabilities (providing voice / data connectivity to users). Examples include handheld devices with wireless connectivity or in-vehicle devices. For instance, terminal equipment 120 can be a mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in vehicle networking, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, or wireless terminal in smart home, etc.

[0043] Figure 2 This illustration shows a hardware architecture diagram of an electronic device according to an embodiment of this application. The electronic device can be... Figure 1 Network device 110 or terminal device 120.

[0044] For example, the electronic device may include: a processor, an external memory interface, internal memory, a universal serial bus (USB) interface, a charging management module, a power management module, a battery, antenna 1, antenna 2, a mobile communication module, a wireless communication module, a sensor module, buttons, a motor, an indicator, a camera, a display screen, and a SIM card slot, etc. The audio module may include a speaker, a receiver, a microphone, a headphone jack, etc., and the sensor module may include a pressure sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer, a proximity sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

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

[0046] The processor may include one or more processing units, such as an application processor (AP), a modem (also known as a baseband processor), a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), and / or a neural network processing unit (NPU). Different processing units can be independent devices or integrated into one or more processors. The processor is the nerve center and command center of the terminal. The controller generates operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0047] The wireless communication function of an electronic device can be implemented through antenna 1, antenna 2, a mobile communication module, a wireless communication module, and a modem. In some embodiments, antenna 1 is coupled to the mobile communication module, and antenna 2 is coupled to the wireless communication module, enabling the electronic device to communicate with other devices via wireless communication technology.

[0048] Furthermore, an operating system runs on top of the aforementioned components. Examples include iOS and Android. The operating system of an electronic device can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application uses the layered architecture of the Android system as an example to exemplify the software structure of an electronic device. It should be noted that although this application uses the Android system as an example, its basic principles are equally applicable to electronic devices using other operating systems.

[0049] Figure 3 This illustration shows a schematic diagram of the hardware and software structure of an electronic device according to an embodiment of this application. Figure 3 As shown, the electronic devices include the access point (AP) and the modem.

[0050] The AP runs the Android system, and its software architecture can be layered using the Android system's layered architecture. For example... Figure 3As shown, the software structure of AP is divided into five layers, from top to bottom: application layer, application framework layer, Android runtime and system library, hardware abstraction layer (HAL) and kernel layer.

[0051] Specifically, the application layer can include a series of application packages. These application packages can include applications (apps) such as camera, gallery, calendar, call, map, WLAN, Bluetooth, music, video, and SMS. The application layer can also include the system UI, which is used for displaying the interface, such as displaying the signal icon corresponding to the SIM card or the call interface on the terminal device. The application framework layer provides application programming interfaces (APIs) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions. For example, the application framework layer can include a window manager, content provider, view system, phone manager, resource manager, and notification manager. The phone manager is used to provide the terminal's call functionality, such as managing call status (including connection, hang-up, etc.). Figure 3 The application framework layer is represented by a telephony. It can also include a radio interface layer (RIL), through which the modem can interact with the telephony. The hardware abstraction layer (HAL) is the interface layer between the operating system kernel and the hardware circuitry, its purpose being to abstract the hardware. It hides the hardware interface details of a specific platform, providing the operating system with a virtual hardware platform. For example, the HAL includes display HAL, camera HAL, audio HAL, sensor HAL, etc. The kernel layer includes the drivers corresponding to each HAL in the hardware abstraction layer, such as the display driver for the display HAL, the camera driver for the camera HAL, and the sensor driver for the sensor HAL.

[0052] A modem can be divided into multiple functional modules according to the different functions it performs. For example... Figure 3As shown, the software structure of a modem includes a configuration loading module, a network registration module, a connection establishment module, and an Internet Protocol Multimedia Subsystem (IMS) service registration module. These modules can call the non-access stratum (NAS) layer, radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, medium access control (MAC) layer, and physical (PHY) layer to implement their corresponding functions.

[0053] To introduce the functions of these modules in the modem, the following section first introduces some configuration files involved in the embodiments of this application:

[0054] 1. Carrier configuration file: The carrier configuration file is a configuration file used to ensure that the terminal device connects to the carrier's network and implements various functions according to the carrier's network.

[0055] Depending on the functions implemented by the configuration file, the operator's configuration file may include one or more of the following: a configuration file for network standard registration, a configuration file for data services, and a configuration file for IMS services. Specifically, the configuration file for network standard registration can be used to implement the network standard registration process, for example, the registration process for a 4G network or a 5G network; the configuration file for data services can be used to establish the corresponding packet data network (PDN) connection for the data service and register the data service, for example, data services include, but are not limited to, one or more of messaging services (such as SMS and MMS), entertainment services (such as ringtones, music, and games), and information services (such as news and weather); the configuration file for IMS services can be used to establish the corresponding PDN connection for the IMS service and register the IMS service, for example, the IMS service can be Voice over Long-Term Evolution (VOTE) service, Voice over New Radio (VONR) service, or Enhanced Packet System Fallback (EPSFB) service.

[0056] Depending on where the configuration files are stored, operator configuration files include those for the access point (AP) and the modem. The AP's configuration file is stored in the AP's code, and the modem's configuration file is stored in the modem's code. Both the AP's and modem's operator configuration files can include the configuration files that implement the various functions mentioned above. For example, the AP's configuration file may include one or more of the following: network standard registration configuration file, data service configuration file, and IMS service configuration file. Similarly, the modem's configuration file may include one or more of the following: network standard registration configuration file, data service configuration file, and IMS service configuration file.

[0057] Compared to the carrier configuration file for the modem, the carrier configuration file for the access point (AP) contains some carrier-customized parameters to adapt to the carrier's actual network environment and requirements. The following explanation uses the IMS service configuration files for the AP and modem as examples: In the IMS service configuration file for the modem, the Internet Protocol (IP) type for the IMS service can be the default type, for example, Internet Protocol version 4 (IPv4). However, if the carrier supports IMS service data transmission using Internet Protocol version 6 (IPv6) in a real-world application scenario, the IP type for the IMS service can be customized to IPv6 in the IMS service configuration file for the AP. This way, when the IMS service configuration file for the AP overrides the one for the modem, the terminal device can transmit IMS service data based on IPv6, avoiding the situation where data transmission is impossible based on IPv4.

[0058] 2. Modem Configuration Binary (MBN) File: The MBN file is a configuration file stored in the modem's code and loaded by the modem. The MBN file includes the operator's configuration file corresponding to the modem, specifically one or more of the network standard registration configuration file, data service configuration file, and IMS service configuration file. Of course, the MBN file may also include other files besides the operator's configuration file corresponding to the modem, and this application embodiment does not impose any limitations on this.

[0059] The following describes the functions of each module in a modem:

[0060] The configuration loading module is used to load the MBN file. In this embodiment, loading the MBN file can also be understood as performing a write operation on the MBN file, such as writing the MBN file to a corresponding location, which refers to a storage location, storage area, or memory location. Optionally, the configuration loading module can also load the operator configuration file corresponding to the AP issued by the AP. The terminal device has one or more locations for loading the MBN and the operator configuration file corresponding to the AP, referred to as loading locations. For example, the terminal device has three loading locations, which can be named according to the index of the configuration file (profile): that is, the names of the three loading locations are profile1, profile2, and profile3, respectively. For ease of description, "profile" in the following content refers to the name corresponding to the loading location.

[0061] The network registration module is used to execute the network-based registration process.

[0062] The connection establishment module is used to establish PDN connections corresponding to services, such as PDN connections for IMS services and PDN connections for data services. The connection establishment module can also be called a data service (DS) module, etc., but this application embodiment does not limit it to that.

[0063] The registration module for IMS services is used to execute the registration process for IMS services based on the PDN connection corresponding to the IMS service.

[0064] It should be understood that the software architecture of the modem in this application embodiment may also include modules with other functions, and is not limited to the modules mentioned above, such as a data service registration module, etc.

[0065] Based on the above description of electronic devices, after a terminal device powers on, restarts, or undergoes a system update, it will perform the following steps. The following example, using the power-on scenario, illustrates the steps the terminal device needs to perform:

[0066] After powering on, the terminal device needs to load the operator's configuration files, including the MBN and AP's corresponding operator configuration files. Then, based on these loaded configuration files, the terminal device registers with the network standard. After network standard registration is complete, it establishes a PDN connection corresponding to the IMS service based on these configuration files. After establishing the IMS service PDN connection, it registers the IMS service based on the loaded configuration files. Once IMS service registration is complete, the user can make voice calls using the registered IMS service. Figure 4 As shown, the process includes, but is not limited to, the following steps ①-⑤:

[0067] ① Configure the loading module to load the MBN file.

[0068] Taking the MBN file, which includes configuration files for network standard registration, data services, and IMS services, as an example, when loading the MBN file, the configuration loading module first loads the configuration files for each service into their corresponding profiles. For instance, the configuration file for network standard registration is loaded into the profile corresponding to network standard registration, the configuration file for data services is loaded into the profile corresponding to data services (e.g., profile1), and the configuration file for IMS services is loaded into the profile corresponding to IMS services (e.g., profile2).

[0069] It should be noted that during the iteration of mobile communication networks, data services are the basic services provided by the mobile communication network, while IMS services are a value-added service that emerged after 4G. Therefore, before the advent of IMS services, there was no profile corresponding to IMS services, but there was a profile corresponding to data services. Furthermore, to prevent the already loaded data service configuration files from being overwritten later, the design involved locking profile1 after loading the data service configuration file from the MBN file. After the advent of IMS services, profile2 was designated as the profile corresponding to IMS services, while retaining the design of locking profile1 after loading the data service configuration file. Therefore, after executing step ①, profile1 is locked, and the configuration file in profile1 cannot be overwritten. Simultaneously, data services are always loaded before IMS services; that is, the terminal device always loads the data service configuration file in profile1 first, and then loads the IMS service configuration file in profile2.

[0070] ② Configure the loading module to notify the network registration module, connection establishment module, and IMS service registration module.

[0071] After step ① is completed, the configuration loading module executes step ② to notify the network registration module, connection establishment module, and IMS service registration module that the MBN file has been successfully loaded.

[0072] It should be understood that the network registration module, connection establishment module, and IMS service registration module can obtain the corresponding configuration file when the relevant process is triggered after receiving the notification, rather than obtaining it immediately after receiving the notification. Furthermore, obtaining the corresponding configuration file can also be understood as reading the corresponding configuration file.

[0073] For example, after receiving the above notification from the configuration loading module, the connection establishment module can obtain the configuration file in profile2 when initiating the PDN connection establishment process for IMS service. After receiving the above notification from the configuration loading module, the IMS service registration module can obtain the configuration file in profile2 when initiating the IMS service registration process.

[0074] ③ The AP loads the corresponding carrier configuration file.

[0075] ④ The network registration module initiates the network-based registration process.

[0076] ⑤ The connection establishment module initiates the process of establishing a PDN connection corresponding to the IMS service, and the IMS service registration module initiates the registration process of the IMS service.

[0077] Steps ① and ② above are executed sequentially, meaning step ① is executed before step ②. However, steps ① and ② can be performed asynchronously with step ③. In the first case, step ③ is executed after steps ① and ② are completed; in this case, steps ④ and ⑤ are executed after step ③ is completed. In the second case, step ③ is executed after step ① but before step ② is completed; in this case, step ② is executed after step ③ is completed, and then steps ④ and ⑤ are executed after step ② is completed.

[0078] Taking the operator configuration files corresponding to the AP, including the configuration files for data services and the configuration files for IMS services, as examples, the implementation methods of steps ③ to ⑤ in these two cases are explained below:

[0079] Regarding the first scenario:

[0080] After step ② is completed, step ③ is executed. The specific method of step ③ is as follows:

[0081] First, the AP sends the corresponding carrier configuration file to the connection establishment module in the modem;

[0082] Then, when the connection establishment module receives the notification as in step ② above, the connection establishment module determines that the MBN file has been successfully loaded. Therefore, after receiving the operator configuration file corresponding to the AP, the connection establishment module can query whether there is a configuration file for the same service in each profile. For example, the connection establishment module can find that there is a loaded data service configuration file in profile1 and a loaded IMS service configuration file in profile2.

[0083] Furthermore, the connection establishment module sends the operator configuration file corresponding to the AP and the instruction information to the configuration loading module. The instruction information instructs the configuration loading module to overwrite the data service configuration file loaded in profile1 based on the data service configuration file in the operator configuration file corresponding to the AP, and to overwrite the IMS service configuration file loaded in profile2 based on the IMS service configuration file in the operator configuration file corresponding to the AP.

[0084] Finally, after receiving the operator configuration file corresponding to the AP and the indication information, the configuration loading module first loads the data service configuration file in the operator configuration file corresponding to the AP. Since it is recognized that profile1 indicated by the indication information is locked, profile2 indicated by the indication information is used to overwrite the IMS service configuration file, and profile3 is not locked, the data service configuration file in the operator configuration file corresponding to the AP is loaded in profile3. Then, the configuration loading module loads the IMS service configuration file in the operator configuration file corresponding to the AP. Since it is recognized that profile2 indicated by the indication information is not locked, the IMS service configuration file loaded in profile2 can be overwritten based on the IMS service configuration file in the operator configuration file corresponding to the AP.

[0085] It should be understood that when configuring the loading module for overriding, some default parameters in the MBN file already loaded in the profile can be rewritten to customized parameters. For example, in the IMS service configuration file of the MBN file, the IP type of the IMS service is IPv4 by default. However, in the IMS service configuration file of the operator corresponding to the AP, the IP type of the IMS service is customized to IPv6. Therefore, when overriding, the configuration loading module will rewrite the IP type of the IMS service in profile2 from IPv4 to IPv6.

[0086] After step ③ is completed, step ④ is executed. The specific implementation method of step ④ is as follows:

[0087] When initiating the network standard registration process, the network registration module first obtains the network standard registration configuration file from the profile corresponding to the network standard registration, and then interacts with the network device based on the obtained network standard registration configuration file to achieve network standard registration.

[0088] After step ④ is completed, step ⑤ is executed. The specific implementation method of step ⑤ is as follows:

[0089] After successfully registering with the network standard, the terminal device can request services provided by that network standard, i.e., request IMS services. Therefore, the connection establishment module can first initiate the process of establishing a PDN connection corresponding to the IMS service. In this process, the connection establishment module first obtains the IMS service configuration file from the corresponding profile (profile2), and then interacts with the network device based on the obtained IMS service configuration file to establish the IMS service PDN connection. After successfully establishing the IMS service PDN connection, the IMS service registration module can initiate the IMS service registration process based on this connection. In this process, the IMS service registration module first obtains the IMS service configuration file from profile2, and then interacts with the network device based on the obtained configuration file and the established IMS service PDN connection to complete the IMS service registration.

[0090] Regarding the second scenario:

[0091] Step ③ is executed after step ① has been completed but before step ② has been executed. The specific method of step ③ is as follows:

[0092] First, the AP sends the corresponding carrier configuration file to the connection establishment module in the modem;

[0093] Then, since the connection establishment module did not receive the notification as in step ② above, the connection establishment module determined that the MBN file had not been successfully loaded. Therefore, after receiving the operator configuration file corresponding to the AP, the connection establishment module sent the operator configuration file corresponding to the AP to the configuration loading module.

[0094] Furthermore, after receiving the operator configuration file corresponding to the AP, the configuration loading module first loads the data service configuration file from the operator configuration file corresponding to the AP. Since it recognizes that profile1 is locked, profile2 is unlocked, and profile3 is unlocked, it will overwrite the IMS service configuration file loaded in profile2 based on the data service configuration file in the operator configuration file corresponding to the AP. Then, when loading the IMS service configuration file in the operator configuration file corresponding to the AP, since it recognizes that profile1 is locked and profile2 is used to load the data service configuration file in the operator configuration file corresponding to the AP, while profile3 is unlocked, it will load the IMS service configuration file in the operator configuration file corresponding to the AP into profile3. Optionally, overwriting the IMS service configuration file loaded in profile2 can be done by completely or partially overwriting the IMS service configuration file. Regardless of whether it is completely or partially overwritten, the IMS service configuration file in profile2 will be incomplete after overwriting, resulting in an incomplete IMS service configuration file in profile2 after step ③ is executed. For example, when the IMS service configuration file in profile2 is completely overwritten, the overwritten profile2 includes the data service configuration file but no longer includes the IMS service configuration file. For ease of description, the following content uses the example of the IMS service configuration files in profile2 being completely overwritten.

[0095] After step ③ is completed, step ② is executed. The specific method of step ② is as described above and will not be repeated here.

[0096] After step ② is completed, step ④ is executed. The specific implementation of step ④ is described above and will not be repeated here.

[0097] After step ④ is completed, step ⑤ is executed. The specific implementation method of step ⑤ is as follows:

[0098] After successful network standard registration, the connection establishment module initiates the process of establishing the PDN connection corresponding to the IMS service. During this process, the connection establishment module first retrieves the configuration file from the profile (profile2) corresponding to the IMS service. Since the configuration file in profile2 has been overwritten with the data service configuration file, the connection establishment module considers the IMS service profile creation to have failed, and therefore determines that establishing the PDN connection corresponding to the IMS service has failed. When the connection establishment module fails to establish the PDN connection corresponding to the IMS service, the IMS service registration module cannot initiate the IMS service registration process based on the PDN connection, thus preventing normal IMS service registration. This failure to register the IMS service prevents terminal devices from making voice calls based on the IMS service, impacting the user's call experience.

[0099] To ensure the normal registration of IMS services, this application provides a service registration method. The following describes the method in conjunction with... Figure 3 The software architecture shown below provides a detailed explanation of the two business registration methods proposed in this application's embodiments:

[0100] Figure 5 The diagram illustrates the hardware and software interaction of the first service registration method: In this service registration method, when the terminal device determines that the creation of the IMS service profile (hereinafter referred to as IMS profile) has failed or the establishment of the PDN connection corresponding to the IMS service has failed, the modem actively reloads the MBN file and restarts the modem after reloading the MBN file. After the modem restarts, it establishes the PDN connection corresponding to the IMS service and realizes the normal registration of the IMS service.

[0101] Specifically, the software architecture of this terminal device can be referred to the description of terminal device 120 above. This service registration method includes steps 501 to 514:

[0102] 501. Configure the loading module to load the MBN file.

[0103] The MBN file includes the configuration file for the IMS service. For example, the IMS service configuration file includes, but is not limited to, one or more of the following: the identifier of the IMS service configuration file, the IP type of the IMS service, the access point name (APN) of the IMS service, or the IP address of that APN. The IP type includes, but is not limited to, IPv4 and / or IPv6.

[0104] Optionally, the MBN file may also include one or more of the following: a configuration file for network standard registration or a configuration file for data services.

[0105] When the configuration loading module loads the MBN file, it can load the IMS service configuration file at the loading location corresponding to the IMS service. For example, the loading location corresponding to the IMS service is a location within an Encrypting File System (EFS) partition. Assuming the EFS partition includes three loading locations named profile1, profile2, and profile3, and the loading location corresponding to IMS is named profile2, then the configuration loading module loads the IMS service configuration file from the MBN file in profile2.

[0106] Optionally, when the configuration loading module loads the MBN file, it can also load the configuration file for the data service at the loading location corresponding to the data service. For example, load the configuration file for the data service in profile1, and load the configuration file for network standard registration at the loading location corresponding to the network standard. Optionally, referring to the above description of profile1, profile1 can be locked in subsequent processes.

[0107] For example, Figure 6 The diagram illustrates the configuration files for profiles 1 through 3, as shown below. Figure 6 As shown, before loading the MBN file, profile1, profile2, and profile3 are all empty. After loading the MBN file and before loading the operator configuration file corresponding to the AP, profile1 includes the configuration file for data services, profile2 includes the configuration file for IMS services, profile3 is empty, and profile1 is locked.

[0108] 502. The AP loads the carrier configuration file corresponding to the AP.

[0109] After step 501 is completed, step 502 is executed. The operator configuration file corresponding to the AP includes, but is not limited to, one or more of the following: network standard registration configuration file, IMS service configuration file, data service configuration file, etc.

[0110] Optionally, compared to the MBN file, the operator configuration file corresponding to the AP contains some operator-customized parameters. For example, in the MBN file, the IP type for IMS service can be the default type, and the APN name for data service can be the default name; while in the operator configuration file corresponding to the AP, the IP type for IMS service can be a customized type, and the APN name for data service can be a customized name.

[0111] Specifically, the process of the AP loading its corresponding carrier configuration file is as follows: the AP sends its corresponding carrier configuration file to the connection establishment module, which then forwards it to the configuration loading module. (Reference) Figure 4 Regarding the second scenario, when the configuration loading module has not yet notified the connection establishment module that the MBN file has been loaded, the connection establishment module assumes that the MBN file has not been fully loaded. In this case, the connection establishment module will directly send the operator configuration file corresponding to the AP to the configuration loading module without instructing the configuration loading module to load it into which profile. Therefore, following the order in which the configuration loading module first loads the data service configuration file in the operator configuration file corresponding to the AP, and then loads the IMS service configuration file in the operator configuration file corresponding to the AP, the configuration loading module may load the data service configuration file in the operator configuration file corresponding to the AP into profile2, causing the IMS service configuration file loaded in profile2 to be overwritten by the data service configuration file.

[0112] Optionally, overwriting the IMS service configuration file loaded in profile2 can mean completely or partially overwriting the IMS service configuration file. Regardless of whether it's completely or partially overwritten, the IMS service configuration file loaded in profile2 will be incomplete. For ease of description, Figure 6 This explanation uses the example of the IMS service configuration files in profile2 being completely overwritten. Figure 6 As shown, assuming that the operator configuration file corresponding to the AP includes the configuration file for data services, after loading the MBN file first and then loading the operator configuration file corresponding to the AP, profile1 includes the configuration file for data services, profile2 includes the configuration file for data services but no longer includes the configuration file for IMS services, and profile3 is empty.

[0113] 503. The configuration loading module notifies the network registration module, connection establishment module, and IMS service registration module that the MBN file loading is complete.

[0114] After step 502 is completed, step 503 is executed. In this step, the configuration loading module sends a notification instruction to the network registration module, the connection establishment module, and the IMS service registration module, informing these modules that the MBN file loading is complete. Upon receiving the notification, these modules can retrieve the configuration file from the profile corresponding to the service they are responsible for when initiating the relevant process. For example, the network registration module retrieves the configuration file from the profile corresponding to network standard registration when initiating the network standard registration process; the connection establishment module retrieves the configuration file from profile2 when initiating the process of establishing a PDN connection corresponding to the IMS service; and the IMS service registration module retrieves the configuration file from profile2 when initiating the IMS service registration process. (Reference) Figure 6 For example, since the configuration file in profile2 is overwritten with the configuration file for the data service after step 502, the connection establishment module and the IMS service registration module can obtain the configuration file for the data service from profile2 but cannot obtain the configuration file for the IMS service.

[0115] 504. The network registration module initiates the network-based registration process.

[0116] After step 503 is completed, step 504 is executed. Specifically, in the network standard registration process, the network registration module first obtains the configuration file from the profile corresponding to the network standard registration, and then determines whether the content of the obtained configuration file is the configuration file for network standard registration. When it is determined to be the configuration file for network standard registration, the network registration module interacts with the network device based on the configuration file for network standard registration, thereby performing network standard registration.

[0117] For example, the network standard can be a 4G network. The registration process for a 4G network can be called a 4G attach process or an LTE attach process, etc. Specifically, the 4G network registration process includes: the network registration module first obtains a configuration file from the profile corresponding to the network standard registration, then confirms that the obtained configuration file is the configuration file for network standard registration. Next, the network registration module sends an attach request message to the network device based on the configuration file for network standard registration. The network device responds to the attach request message by authenticating the terminal device. After successful authentication of the terminal device, the network device assigns corresponding address information and identity identifiers to the terminal device and sends an attach accept message to the terminal device. Finally, the network registration module sends an attach complete message to the network device.

[0118] Alternatively, for example, the network standard could be a 5G network. The 5G network registration process specifically includes: the network registration module first obtains the configuration file from the profile corresponding to the network standard registration, then determines that the obtained configuration file is the configuration file for network standard registration, and then the network registration module sends a network standard registration request message to the network device. The network device responds to the registration request message by performing authentication and other operations on the terminal device; after the terminal device is successfully authenticated, the network device assigns the corresponding address information and identity identifier to the terminal device, and sends a registration acceptance message to the terminal device.

[0119] It should be understood that the registration process for network standards is not limited to the above example. Under other network standards, the names of the above messages may vary, and there are no restrictions on this.

[0120] 505. After the connection establishment module initiates the process of establishing a PDN connection corresponding to the IMS service, it listens in the process to see whether the IMS profile has been created successfully or whether the PDN connection corresponding to the IMS service has been established successfully.

[0121] If the terminal device successfully registers the network standard in step 504, the connection establishment module proceeds to step 505. In the process of establishing a PDN connection corresponding to the IMS service, the connection establishment module first obtains the configuration file from the profile (e.g., profile2) corresponding to the IMS service, and then determines whether the configuration file is the configuration file for the IMS service based on its contents.

[0122] For example, it determines whether the configuration file identifier is the identifier for an IMS service configuration file, and / or whether the configuration file's APN name is the APN name for an IMS service, and so on. If the configuration file identifier is the identifier for an IMS service configuration file, and / or the configuration file's APN name is the APN name for an IMS service, then the configuration file is determined to be an IMS service configuration file. Conversely, if the configuration file identifier is not the identifier for an IMS service configuration file, and / or the configuration file's APN name is not the APN name for an IMS service, then the configuration file is determined not to be an IMS service configuration file.

[0123] Furthermore, if the configuration file is determined to be for an IMS service, it means that the configuration file for the IMS service has been successfully loaded into the corresponding loading location, and the connection establishment module determines that the IMS profile creation was successful. Conversely, if the configuration file is determined not to be for an IMS service, it means that the configuration file for the IMS service has not been successfully loaded into the corresponding loading location, and the connection establishment module determines that the IMS profile creation failed.

[0124] In some embodiments, the connection establishment module can further determine the failure of PDN connection establishment corresponding to the IMS service based on the failure of IMS profile creation.

[0125] Furthermore, the connection establishment module can listen to whether the IMS profile has been created, or whether the PDN connection corresponding to the IMS service has been successfully established, and determine whether to execute step 506 and the steps after step 506 based on the listened result.

[0126] For example, if the connection establishment module detects that the IMS profile creation has failed or that the PDN connection establishment corresponding to the IMS service has failed, then step 506 and the steps following step 506 are executed. Conversely, if the connection establishment module detects that the IMS profile creation has succeeded, then it interacts with the network device to establish the PDN connection corresponding to the IMS service. If the connection establishment module detects that the PDN connection corresponding to the IMS service has been successfully established, then the IMS service registration module registers the IMS service based on the established PDN connection corresponding to the IMS service.

[0127] For example, the process of interacting with network devices to establish a PDN connection corresponding to an IMS service specifically includes: the connection establishment module sending a PDN connection establishment request message corresponding to the IMS service to the network device; after the network device allocates the corresponding PDN connection for the terminal device's IMS service, it sending an establishment reply message to the terminal device, indicating that the PDN connection corresponding to the IMS service has been successfully established. The establishment request message and establishment reply message can be sent based on a registered 4G network or 5G network, etc.

[0128] 506. The registration module of IMS service obtains the most recent registration status of IMS service.

[0129] If the connection establishment module fails to establish an IMS profile or the PDN connection corresponding to the IMS service fails to establish in step 505, the IMS service registration module executes step 506 to obtain the most recent registration status of the IMS service.

[0130] For example, the registration module of the IMS service can store a record of whether the registration of the IMS service was successful each time it was registered. For instance, the registration status of the IMS service is represented by "0" or "1", where "0" indicates that the IMS service registration failed and "1" indicates that the IMS service registration was successful. Then the terminal device can store the record <"2024.08.20.12:31", "1">, which indicates that the IMS service registration was successful at the time "2024.08.20.12:31".

[0131] 507. The registration module for IMS services determines whether the most recent registration status indicates that the IMS service registration was successful.

[0132] After step 506 is completed, step 507 is executed. If the most recent registration status indicates that the IMS service registration was successful, then step 508 and the steps following step 508 are executed. Conversely, if the most recent registration status indicates that the IMS service registration failed, the terminal device cannot complete the IMS service registration process, and the user cannot make voice calls based on the IMS service; the user can make voice calls based on 2G or 3G.

[0133] 508. Configure the loading module to reload the MBN file.

[0134] The configuration loading module can reload the MBN file according to the implementation method of step 501 above. It should be understood that when reloading the MBN file, the profiles corresponding to the configuration files of each service in the MBN file will be temporarily unlocked, so the MBN file can be reloaded according to the implementation method of step 501 above.

[0135] For example, Figure 7 The diagram shows the configuration files in profile1 to profile3 after reloading the MBN file. After reloading the MBN file, profile1 includes the configuration file for data services, profile2 includes the configuration file for IMS services, and profile1 is locked again.

[0136] 509. Modem restart.

[0137] After step 508 is completed, step 509 is executed to restart the modem. Since the modem restart process is short, the user is almost unaware of it and it will not affect the user's use of other terminal device functions. Furthermore, since the profiles corresponding to the data services and the IMS services are both stored in non-volatile memory, and the AP will not reissue configurations after the modem restart, the modem restart will not affect the configuration files in the profiles corresponding to the IMS services. That is, the IMS service configuration files reloaded in profile2 will not be lost or overwritten again.

[0138] 510. The configuration loading module notifies the network registration module, connection establishment module, and IMS service registration module that the MBN file loading is complete.

[0139] After step 509 is completed, step 510 is automatically triggered. During this step, the configuration loading module sends a notification to the network registration module, connection establishment module, and IMS service registration module, informing them that the MBN file loading is complete. Upon receiving the notification, these modules can retrieve the configuration file from the profile corresponding to the service they are responsible for when re-initiating the relevant process. For example, when the network registration module re-initiates the network standard registration process, it retrieves the configuration file from the profile corresponding to network standard registration; when the connection establishment module re-initiates the process of establishing the PDN connection corresponding to the IMS service, it retrieves the configuration file from profile2; and when the IMS service registration module re-initiates the IMS service registration process, it retrieves the configuration file from profile2. Since the configuration file in profile2 is reloaded as the IMS service configuration file after step 508, the connection establishment module and the IMS service registration module can obtain the IMS service configuration file.

[0140] 511. The network registration module initiates the network-based registration process.

[0141] The implementation method of step 511 can refer to the implementation method of step 504, and will not be repeated here.

[0142] 512. When the connection establishment module initiates the process of establishing a PDN connection corresponding to the IMS service, it listens in the process to see whether the IMS profile has been created successfully or whether the PDN connection corresponding to the IMS service has been established successfully.

[0143] If step 511 successfully registers the network standard, then step 512 is executed following the implementation method of step 505. Since the configuration file obtained by the connection establishment module in step 510 is the configuration file for the IMS service, the connection establishment module listens for successful IMS profile creation in this step, and then executes steps 513 and 514 after completing this step; alternatively, the connection establishment module listens for successful PDN connection establishment corresponding to the IMS service in this step, and then does not need to execute step 513 after completing this step, but can execute step 514.

[0144] 513. The connection establishment module interacts with network devices to establish the PDN connection corresponding to the IMS service.

[0145] For example, the connection module interacts with the network device based on the obtained IMS service configuration file to establish a PDN connection corresponding to the IMS service. The interaction process with the network device can be referred to the corresponding description in step 505, and will not be repeated here. After the PDN connection corresponding to the IMS service is established, step 514 can be executed.

[0146] 514. The registration module for IMS services initiates the registration process for IMS services.

[0147] In the IMS service registration process, the IMS service registration module first obtains the configuration file from the profile corresponding to the IMS service (e.g., profile2). Then, based on the content of the configuration file, it determines whether the configuration file is the IMS service configuration file. The determination method can refer to the determination method of the connection establishment module in step 505 above. Since the configuration file in the profile corresponding to the IMS service is reloaded as the IMS service configuration file after step 508, the IMS service registration module determines that the obtained configuration file is the IMS service configuration file. Therefore, the IMS service registration module interacts with the network device based on the PDN connection corresponding to the IMS service established in step 513 to realize the normal registration of the IMS service.

[0148] For example, the registration process for IMS services specifically includes: the IMS service registration module sending an IMS service registration message to the network device; then the network device obtaining the terminal device's subscription information and verifying the terminal device's identity (or authenticating the terminal device) based on the terminal device's subscription information; once the terminal device's identity verification is successful, the network device returns a confirmation message (such as a 200 OK response message) to the terminal device to indicate that the IMS service registration was successful.

[0149] based on Figure 5In the described embodiment, the modem in the terminal device can actively reload the MBN file in the event of an IMS profile creation failure or a PDN connection establishment failure corresponding to the IMS service failure. Based on the IMS service configuration file in the reloaded MBN file, it can ensure that the PDN connection corresponding to the IMS service can be established normally, thereby ensuring that the IMS service can be registered normally.

[0150] Figure 8 The diagram illustrates the hardware and software interaction of the second service registration method: In this method, when the terminal device determines that the creation of the IMS service profile has failed or the establishment of the PDN connection corresponding to the IMS service has failed, the AP controls the modem to reload the MBN file, and restarts the modem after reloading the MBN file. After the modem restarts, it establishes the PDN connection corresponding to the IMS service and achieves normal registration of the IMS service.

[0151] Specifically, the software architecture of this terminal device can be referred to the description of terminal device 120 above. This service registration method includes steps 801 to 814:

[0152] 801. Configure the loading module to load the MBN file.

[0153] 802. The AP loads the carrier configuration file corresponding to the AP.

[0154] 803. The configuration loading module notifies the network registration module, connection establishment module, and IMS service registration module that the MBN file loading is complete.

[0155] 804. The network registration module initiates the network-based registration process.

[0156] 805. After the connection establishment module initiates the process of establishing a PDN connection corresponding to the IMS service, it listens in the process to see whether the IMS profile has been created successfully or whether the PDN connection corresponding to the IMS service has been established successfully.

[0157] Steps 801 to 805 can be implemented in the same way as steps 501 to 505 above.

[0158] 806. The connection establishment module notifies the AP that the IMS profile creation failed or the PDN connection establishment corresponding to the IMS service failed.

[0159] If, in step 805, the connection establishment module detects an IMS profile creation failure or a PDN connection establishment failure corresponding to the IMS service, the connection establishment module notifies the AP of the IMS profile creation failure or the PDN connection establishment failure corresponding to the IMS service through the interface defined between the AP and the modem, for example, the ICD interface. Optionally, when notifying the AP of the IMS profile creation failure or the PDN connection establishment failure corresponding to the IMS service failure, the module can also notify the AP of the reason for the failure, indicating that the failure was caused by the loading location corresponding to the IMS service being overwritten by the configuration file of another service.

[0160] 807. The AP calls the registration module of the IMS service to obtain the most recent registration status of the IMS service.

[0161] After receiving the notification in step 806, the AP can call the IMS service registration module through the interface defined between the AP and the modem to obtain the most recent registration status of the IMS service. The registration status can be referred to the corresponding description in step 506.

[0162] 808. AP determines whether the most recent registration status indicates that the IMS service registration was successful.

[0163] After step 807 is completed, step 808 is executed. For example, if the most recent registration status indicates successful IMS service registration, then step 809 and subsequent steps are executed. Conversely, if the most recent registration status indicates failed IMS service registration, the terminal device cannot complete the IMS service registration process, and the user cannot make voice calls based on the IMS service; the user can make voice calls based on 2G or 3G.

[0164] Optionally, if the most recent registration status indicates successful IMS service registration, the AP can also obtain the screen usage status and service status of the terminal device before executing step 809. The screen usage status is either on or off, and the service status is either idle or non-idle. In the idle state (e.g., Idel state), no service data is transmitted; in the non-idle state, service data is transmitted. When the AP determines that the screen usage status is off and the service status is idle, the terminal device is in an idle state. Executing step 809 and subsequent steps in the idle state will not affect the user experience, such as causing service delays. Therefore, when the screen usage status is off and the service status is idle, step 809 and subsequent steps are executed.

[0165] In one possible implementation, the AP first obtains the service status, and when the service status is idle, it obtains the screen usage status. Then, when the screen usage status is off, it executes step 809 and the steps after step 809.

[0166] In another possible implementation, the AP can first obtain the screen usage status, and when the screen usage status is off, obtain the service status. Then, when the service status is idle, it can execute step 809 and the steps after step 809.

[0167] In another possible implementation, after obtaining both the screen usage status and the service status, the AP determines whether the screen usage status is off and whether the service status is idle; then, if the screen is off and the service status is idle, it executes step 809 and the steps after step 809.

[0168] This application does not impose any restrictions on the order of obtaining and judging screen usage status and business status.

[0169] 809. The AP calls the modem, instructing the configuration loading module to reload the MBN file, and instructs the modem to restart after loading the MBN file.

[0170] Specifically, the AP can call the configuration loading module in the modem to reload the MBN file through the interface defined between the AP and the modem; then, after loading the MBN file, the modem is restarted. After the modem restarts, step 810 and the steps after step 810 can be triggered, and the specific implementation process is the same as that of steps 508 to 509 above.

[0171] 810. The configuration loading module notifies the network registration module, connection establishment module, and IMS service registration module that the MBN file loading is complete.

[0172] 811. The network registration module initiates the network-based registration process.

[0173] 812. The connection establishment module initiates the process of establishing a PDN connection corresponding to the IMS service, and listens for whether the IMS profile is successfully created or whether the PDN connection corresponding to the IMS service is successfully established during the process.

[0174] 813. The connection establishment module interacts with network devices to establish the PDN connection corresponding to the IMS service.

[0175] 814. The registration module for IMS services initiates the registration process for IMS services.

[0176] Steps 810 and 814 can be implemented in the same way as steps 510 to 514 above, and will not be repeated here.

[0177] based on Figure 8 In the described embodiment, the modem in the terminal device can reload the MBN file and restart under the control of the AP in scenarios where IMS profile creation fails or the PDN connection corresponding to the IMS service fails to be established. Based on the IMS service configuration file in the reloaded MBN file, this ensures that the PDN connection corresponding to the IMS service can be established normally, thereby ensuring that the IMS service can be registered normally. Furthermore, in this method, the AP controls the loading of the MBN file and the restart of the modem through the interface between the AP and the modem, without requiring any changes to the modem, effectively reducing overhead.

[0178] Regarding the two business registration methods mentioned above, Figure 9 A schematic diagram of the overall process is shown, such as Figure 9 As shown:

[0179] Figure 9 The diagram shows an overall flowchart of a business registration method proposed in an embodiment of this application. The subject of this method can be a terminal device, a chip in the terminal device, or other types of products. Those skilled in the art can make further extensions based on the content disclosed in the specification. Figure 9 The method shown uses a terminal device as an example; the terminal device can be found in the description of terminal device 120 above. Figure 9 As shown, the method includes steps 901 to 903.

[0180] in:

[0181] 901. The terminal device loads the IMS service configuration file from the MBN file in the first location.

[0182] In this embodiment, the first location refers to the loading location corresponding to the configuration file of the IMS service. For example, the first location may be a location within an encrypted file system (EFS) partition.

[0183] The terminal device loading the IMS service configuration file from the MBN file at the first location can be understood as: the terminal device loading the IMS service configuration file from the MBN file into the first location, or the terminal device configuring the IMS service configuration file from the MBN file in the first location, or the terminal device writing the IMS service configuration file from the MBN file into the first location, etc. For example, the first location is profile2 in the above method embodiment.

[0184] In one possible implementation, the terminal device loads the IMS service configuration file from the MBN file in a first location by loading the MBN file.

[0185] The IMS service configuration file in the MBN file includes configuration information for establishing the PDN connection corresponding to the IMS service, and configuration information for registering the IMS service. For example, the IMS service configuration file in the MBN file includes, but is not limited to, one or more of the following: the identifier of the IMS service configuration file, the IP type of the IMS service, the access point name (APN) of the IMS service, or the IP address of the APN, etc. The IP type includes, but is not limited to, IPv4 and / or IPv6.

[0186] In the first possible implementation, the terminal device can load the IMS service configuration file from the MBN file in the first location after the operating system is updated and restarted. For example, if the terminal device detects the existence of a new version of the operating system, it can update the operating system after obtaining user permission. For instance, the terminal device can prompt the user via a pop-up window that the operating system can be updated, and update the operating system after receiving the user's consent. Alternatively, the terminal device can automatically trigger the operating system update. For example, the terminal device can automatically update the operating system after the screen-off time exceeds a preset duration, or it can automatically update the operating system at a preset update time, such as between 2 AM and 6 AM. It should be understood that the triggering scenarios for operating system updates are not limited to the above examples. Then, after updating the operating system, the terminal device can restart the operating system, and after the operating system restarts, step 901 is executed.

[0187] In the second possible implementation, the terminal device can load the IMS service configuration file from the MBN file at the first location after the operating system has not been updated but has restarted. For example, the terminal device receives a user-initiated operation to restart the operating system, and in response, restarts the operating system; or, the terminal device first receives a user-initiated operation to shut down the operating system, shuts down the operating system in response, and then receives a user-initiated operation to start the operating system, and starts the operating system in response; the terminal device executes step 901 after restarting or starting the operating system. It should be understood that in this method, restarting / starting / shutting down the operating system can also be understood as restarting / starting / shutting down the terminal device, or as restarting / powering on / powering off.

[0188] In a third possible implementation, the terminal device can load the IMS service configuration file from the MBN file at a first location after airplane mode is turned off. For example, the terminal device first receives a user-initiated operation to turn off airplane mode, and in response, interrupts network connections and data transmission for various services and stops searching for networks; then, it receives a user-initiated operation to turn on airplane mode and executes step 901 in response.

[0189] It should be understood that the triggering scenario for step 901 is not limited to the example above.

[0190] 902. In the event that the creation of the IMS service profile fails or the establishment of the PDN connection corresponding to the IMS service fails, the terminal device reloads the configuration file of the IMS service in the MBN file in the first location.

[0191] In this embodiment, the terminal device can monitor whether the IMS service profile has been successfully created or whether the PDN connection corresponding to the IMS service has been successfully established. The method by which the terminal device monitors whether the IMS service profile has been successfully created or whether the PDN connection corresponding to the IMS service has been successfully established can refer to the implementation of step 505 above. When it is detected that the IMS service profile creation has failed or the PDN connection establishment corresponding to the IMS service has failed, the terminal device reloads the IMS service configuration file in the first location.

[0192] The following section explains how to detect failures in IMS service profile creation or PDN connection establishment for IMS services:

[0193] In one possible implementation, referring to steps 501 to 503 or 801 to 803 above, after the terminal device loads the IMS service configuration file from the MBN file in the first location, it first loads the configuration file for the second service in the first location. The second service is different from the IMS service, such as a data service. Then, it notifies the network registration module, connection establishment module, and IMS service registration module in the terminal device. In this case, the first configuration file loaded in the first location by the terminal device may be overwritten by the configuration file for the second service, resulting in an incomplete IMS service configuration file loaded in the first location. This, in turn, causes the connection establishment module to detect that the IMS service profile creation has failed, or detects that the PDN connection establishment corresponding to the IMS service has failed.

[0194] It should be noted that the terminal device can also initiate a network standard registration process first, and then, after successful network standard registration, initiate a PDN connection establishment process corresponding to the IMS service. During the PDN connection establishment process corresponding to the IMS service, the connection establishment module listens for either a failure to create the IMS service profile or a failure to establish the PDN connection corresponding to the IMS service. For specific implementation methods, refer to steps 504 to 505, or the implementation methods of steps 804 to 805 above.

[0195] The following describes how the terminal device reloads the first configuration file in the first location when it detects that the IMS service profile creation has failed or the corresponding PDN connection establishment has failed:

[0196] In one possible implementation, when the IMS service profile creation fails or the PDN connection establishment corresponding to the IMS service fails, the terminal device obtains the most recent registration status of the IMS service; then, when the most recent registration status indicates that the IMS service registration is successful, the configuration file of the IMS service in the MBN file is reloaded in the first location.

[0197] In this embodiment, the terminal device must first successfully establish a PDN connection corresponding to the IMS service. This PDN connection is equivalent to the data transmission channel for the IMS service. Then, it interacts with the network device based on this data transmission channel to register the IMS service. Therefore, when the most recent registration status indicates successful IMS service registration, it means the PDN connection corresponding to the IMS service was successfully established previously, and consequently, the profile creation for the most recent IMS service was successful. Thus, ensuring successful profile creation for the IMS service guarantees at least the normal establishment of the PDN connection and the normal registration of the IMS service. Since the failure to create the IMS service profile this time was due to the IMS service configuration file in the MBN file in the first location being overwritten, the terminal device can attempt to reload the IMS service configuration file in the MBN file in the first location to achieve successful profile creation for the IMS service.

[0198] Referring to the implementation methods of steps 508 to 510 above, or steps 809 to 810, the terminal device can reload the configuration file of the IMS service in the MBN file at the first location by reloading the MBN file, and then restart the modem after reloading the MBN file, and then notify the network registration module, connection establishment module and IMS service registration module again after restarting.

[0199] Alternatively, the terminal device can reload only the IMS service configuration file in the MBN file, then restart the modem, and subsequently notify the network registration module, connection establishment module, and IMS service registration module again. For example, the terminal device only reloads the IMS service configuration file on profile2 in the above method embodiment. This eliminates the need for the terminal device to load the entire MBN file, effectively improving loading efficiency and reducing the impact on user experience.

[0200] 903. The terminal device re-establishes the PDN connection corresponding to the IMS service based on the configuration file in the first location, and registers the IMS service after the PDN connection corresponding to the IMS service is established.

[0201] In this embodiment of the application, referring to steps 511 to 514 or steps 811 to 812 above: after the terminal device reloads the first configuration file, it can first initiate the network standard registration process, and then initiate the PDN connection establishment process corresponding to the IMS service after the network standard registration is successful. In the PDN connection establishment process corresponding to the IMS service, since the connection establishment module does not detect the failure of IMS service profile creation or the failure of PDN connection establishment corresponding to the IMS service, the connection establishment module can interact with the network device and successfully establish the PDN connection corresponding to the IMS service. After the PDN connection corresponding to the IMS service is established, the terminal device can normally register the IMS service.

[0202] based on Figure 6 In the described embodiment, if the terminal device fails to establish a PDN connection corresponding to the IMS service based on the configuration file in the first location, it can reload the first configuration file in the first location, thereby ensuring that the PDN connection corresponding to the IMS service can be established normally based on the reloaded first configuration file in the first location, and thus ensuring that the IMS service can be registered normally.

[0203] It should be noted that in the above method embodiments, the configuration file for the IMS service in the MBN file can also be called the second configuration file, and the other configuration files in the MBN file besides the configuration file for the IMS service can also be called the third configuration file, and the loading location corresponding to the third configuration file can also be called the second location.

[0204] For example, after the terminal device loads the MBN file and then loads the operator configuration file corresponding to the AP, but before reloading the MBN file, the configuration file in the first location can also be called the first configuration file.

[0205] For example, when the terminal device loads the operator configuration file corresponding to the AP, the configuration file for data services in the operator configuration file corresponding to the AP can also be called the fourth configuration file. That is, the terminal device may overwrite the second configuration file in the first position based on the fourth configuration file.

[0206] Furthermore, the network type most recently registered by the terminal device before reloading the MBN file can be called the first network, and the network type re-registered after reloading the MBN file can be called the second network. The first network and the second network can be the same or different.

[0207] In the above method embodiments, after the terminal device detects that the IMS service profile creation has failed or the PDN connection establishment corresponding to the IMS service has failed, it can trigger the terminal device to not display the relevant icons for the IMS service. Then, after the IMS service registration is successful, the terminal device displays the relevant icons for the IMS service.

[0208] For example, such as Figure 10 As shown, taking a user making a phone call as an example: Under normal circumstances, after successful IMS service registration, the terminal device displays interface 1010 when making a call based on the IMS service. Interface 1010 includes a prompt bar area and a call display area. The prompt bar area includes icons such as icon 1001, and the call display area includes controls such as call controls, including icon 1002. Both icons 1001 and 1002 are icons with the letter "HD," indicating that the terminal device currently supports IMS service for calls. In scenarios where IMS profile creation fails or the PDN connection corresponding to the IMS service fails to be established, the terminal device displays interface 1020, which does not include icons 1001 and 1002. For example, before step 514 or step 814 above, the terminal device displays interface 1020, and then after successful IMS service registration, the terminal device displays interface 1010.

[0209] It should be understood that icons 1001 and 1002 above are merely examples.

[0210] This application also provides a chip system applied to the aforementioned terminal device. The chip system includes at least one processor and an interface. The interface is used to receive computer instructions and transmit them to the at least one processor. The at least one processor executes the computer instructions to cause the terminal to perform the aforementioned service registration method. The chip system may be a modem, or a system-on-a-chip (SoC) including a modem, meaning the aforementioned service registration method can be implemented by a modem.

[0211] This application also provides a computer-readable storage medium storing computer instructions, which, when run on a processor, enable the implementation of the method flow described in the above method embodiments.

[0212] This application provides a computer program product, which includes computer instructions. When the computer instructions are executed by a processor, the method flow of the above method embodiment is implemented.

[0213] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some operations can be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0214] The descriptions of the various embodiments provided in this application can be referenced mutually. Each embodiment has its own emphasis, and parts not described in detail in a certain embodiment can be referred to the relevant descriptions of other embodiments. For the sake of convenience and brevity, for example, the functions and operations of the various devices and equipment provided in the embodiments of this application can be referred to the relevant descriptions of the method embodiments of this application. The method embodiments and the device embodiments can also be referenced, combined or cited from each other.

[0215] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive (SSD)).

Claims

1. A business registration method, characterized in that, Applied to a terminal device, the method includes: After the terminal device attaches to a network device in the first network, the terminal device obtains a first configuration file from a first location, the first location being located in the modem processor of the terminal device; When the first configuration file is not the configuration file for the Internet Protocol Multimedia System (IMS) service, the terminal device loads the second configuration file at the first location and restarts the modem processor after loading the second configuration file. The second configuration file is the configuration file for the IMS service. After the modem processor is restarted, when the terminal device attaches to a network device in the second network, the terminal device obtains the second configuration file from the first location. The second network may be the same as or different from the first network. The terminal device establishes a PDN connection corresponding to the IMS service based on the second configuration file.

2. The method according to claim 1, characterized in that, After the terminal device obtains the first configuration file from the first location, the method further includes: When the first configuration file is a configuration file for an IMS service, the terminal device establishes a PDN connection corresponding to the IMS service based on the first configuration file.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Once the PDN connection corresponding to the IMS service is successfully established, the terminal device registers the IMS service based on the PDN connection corresponding to the IMS service.

4. The method according to any one of claims 1-3, characterized in that, The terminal device loads a second configuration file at the first location, including: The terminal device obtains the most recent registration status of the IMS service; When the most recent registration status indicates that the IMS service registration is successful, the terminal device loads the second configuration file at the first location.

5. The method according to claim 4, characterized in that, When the most recent registration status indicates that the IMS service registration was successful, the terminal device loads the second configuration file at the first location, including: When the most recent registration status indicates that the IMS service registration was successful, determine whether the terminal device is in an idle state; When the terminal device is in an idle state, the terminal device loads the second configuration file at the first location.

6. The method according to claim 5, characterized in that, The term "idle state" for a terminal device includes: the screen of the terminal device being in an off state and the service status of the terminal device being in an idle state.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: When the terminal device loads the second configuration file at the first position, the terminal device loads the third configuration file at the second position. The second position is located in the modem processor. The first position is different from the second position, and the third configuration file is different from the second configuration file.

8. The method according to any one of claims 1-7, characterized in that, Before the terminal device attaches to a network device in the first network, the method further includes: The terminal device loads the second configuration file at the first location; The terminal device overwrites the second configuration file in the first location based on the fourth configuration file. The first configuration file is the configuration file in the first location after overwriting. The service to which the fourth configuration file belongs is different from the service to which the second configuration file belongs.

9. The method according to claim 8, characterized in that, The terminal device loads the second configuration file at the first location, including: After the terminal device's operating system is updated and / or restarted, or after the terminal device is turned off and airplane mode is turned on, the terminal device loads the second configuration file at the first location.

10. The method according to any one of claims 1-9, characterized in that, The first location is in the modem processor of the terminal device, including: The first location is the loading location corresponding to the IMS service in the Encrypted File System (EFS) partition, and the EFS partition is located in the modem processor of the terminal device.

11. An electronic device, characterized in that, include: One or more processors, one or more memories; wherein the one or more memories are coupled to one or more processors, the one or more memories being used to store computer instructions that, when the one or more processors execute the computer instructions, cause the electronic device to perform the method as described in any one of claims 1-10.

12. A chip system, characterized in that, The chip system, applied to an electronic device, includes at least one processor and an interface for receiving computer instructions and transmitting them to the at least one processor; the at least one processor executes the computer instructions to cause the electronic device to perform the method as described in any one of claims 1-10.

13. A computer-readable storage medium, characterized in that, Applied to an electronic device, wherein the computer-readable storage medium stores computer instructions that, when executed by a processor, cause the electronic device to perform the method as described in any one of claims 1-10.

Images