Network connection method and related products

Abstract

The present application relates to the field of communication technology, and provides a network connection method and related products, the method comprising: obtaining the registration status of an Internet Multimedia Subsystem (IMS) network; obtaining the bearer establishment status; if the registration status of the IMS network is unsuccessful registration, and the bearer establishment status is successful bearer establishment, instructing a modem to restart to connect to the IMS network. The above method can restore call services without user perception, thereby improving user experience.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a network connection method and related products. Background Art

[0002] With the progress of social production and people's lives, people have higher and higher requirements for communication quality. Among many communication methods, calling is one of the most common and important methods.

[0003] Usually, call connections require the terminal device to register with the corresponding network normally. For example, in the case of 2G and 3G networks, the terminal device implements call services by registering the CS domain, and in the case of 4G and 5G networks, call services can be implemented by registering the IMS. The support of call services involves a complex network connection process. During the use of terminal devices, various faults may cause the caller or the called party to be unable to make calls. In order to restore call services, it is common for users to manually operate the terminal device to enter flight mode, and then cancel the flight mode and reconnect to the network to try to restore it.

[0004] However, in some cases, even if the user sets the terminal device to enter the flight mode and then cancels the flight mode, the call service cannot be restored. In this case, the user needs to restart the terminal device to restore the call service. This operation method is cumbersome, resulting in poor user experience and a long call service recovery time. Summary of the invention

[0005] The present application provides a network connection method, device, chip, application processor, modem, electronic device, computer-readable storage medium and computer program product, which can restore call services without the user's perception and improve the user experience.

[0006] In a first aspect, a network connection method is provided, comprising: obtaining a registration status of an IMS network; obtaining a bearer establishment status; if the registration status of the IMS network is unsuccessful registration and the bearer establishment status is successful bearer establishment, instructing a modem to restart to connect to the IMS network.

[0007] The execution subject of the method may be an application processor (AP) or a modem. The modem may be called a Modem. The following is an exemplary description with the execution subject being an AP.

[0008] Optionally, the AP may continue to monitor whether the Modem has successfully registered with the IMS network to obtain a registration status of the IMS network, which may be a successful registration or an unsuccessful registration.

[0009] Optionally, the AP may collect the abnormal information reported by the modem. Optionally, the abnormal information is used to indicate that the modem is in an abnormal state, and may also indicate the specific type of the abnormal state. Optionally, a management module may be set in the AP, and the AP collects the abnormal information reported by the modem through the management module. When the IMS network fails to register successfully, it may be reported to the AP in the form of abnormal information.

[0010] If the modem side fails to initiate an IMS network registration request, which will result in failure to successfully register with the IMS network, then when the registration status of the IMS network is unsuccessful registration, but the bearer establishment status is successful bearer establishment, the AP can instruct the modem to restart to connect to the IMS network.

[0011] When the AP detects that the bearer of the modem is successfully established but has not successfully registered the IMS network, it can restore the connection to the IMS network by restarting the modem. This method can achieve network self-healing without the user having to manually restart the entire terminal device. Since the time taken for the modem to restart is short, the self-healing efficiency is high; and the method of restarting the modem alone to achieve network self-healing can restore call services without the user's awareness, improving the user experience.

[0012] In some embodiments, if the registration status of the IMS network is unsuccessful registration, and the bearer establishment status is successful bearer establishment, instructing the modem to restart, including: determining whether the registration status of the IMS network is unsuccessful registration; if the registration status of the IMS network is unsuccessful registration, determining whether the bearer establishment status is successful bearer establishment; if the bearer establishment status is successful bearer establishment, instructing the modem to restart.

[0013] In some embodiments, if the registration status of the IMS network is unsuccessful registration, and the bearer establishment status is successful bearer establishment, then instructing the modem to restart, including: if the registration status of the IMS network is unsuccessful registration, and the bearer establishment status is successful bearer establishment; then determining whether an IMS network registration request has been initiated to the IMS network; if an IMS network registration request has not been initiated to the IMS network, then instructing the modem to restart.

[0014] In some embodiments, obtaining the bearer establishment status includes: obtaining a first message, the first message is used to characterize that the bearer establishment status is successful bearer establishment; obtaining the registration status of the IMS network includes: in response to the first message, determining whether a second message is received within a preset period, the second message is used to characterize that the registration status of the IMS network is successful registration; if the registration status of the IMS network is unsuccessful registration, and the bearer establishment status is successful bearer establishment, instructing the modem to restart, including: if the second message is not received within the preset period, instructing the modem to restart.

[0015] After receiving the first message, the AP can determine that the bearer is successfully established. If the AP does not receive the second message of successful registration to the IMS network within the preset period of successful bearer establishment, it means that the IMS network registration is unsuccessful and the call service has not been restored. Therefore, the modem can be instructed to restart. The connection to the IMS network can be restored by restarting the modem. This method can achieve network self-healing without the user having to manually restart the entire terminal device. Since the time taken for the modem to restart is short, the self-healing efficiency is high; and the method of restarting the modem alone to achieve network self-healing can restore the call service without the user's perception, thereby improving the user experience.

[0016] Optionally, if the second message is not received, it is determined whether registration has been initiated with the IMS network; if registration has not been initiated with the IMS network, the modem is instructed to restart.

[0017] If the IMS network registration has not been initiated, the modem can be instructed to restart. By restarting the modem, the connection to the IMS network can be restored. If the IMS network registration has been initiated, there is no need to restart the modem immediately. You can wait and continue to monitor whether the IMS network registration is successful to avoid performing an invalid restart operation.

[0018] In some embodiments, instructing the modem to restart includes: determining whether the current state of the terminal device is an idle state; if the current state is an idle state, instructing the modem to restart; if the current state is not an idle state, executing the step of obtaining the registration state of the IMS network.

[0019] If the terminal device is in idle state, it means that the user is unlikely to use the terminal device at this time, so restarting the modem will not affect the user's use, nor will it make the user feel it, which can improve the user experience. If the terminal device is not in idle state, it means that the user is likely to use the terminal device at this time. If restarting the modem may cause service interruption, which is obviously felt by the user, so you can temporarily not restart the modem, but continue to monitor the status of the terminal device and wait for the appropriate restart time to ensure that the service is not interrupted, thereby improving the user experience.

[0020] In some embodiments, if the current state is an idle state, the modem is instructed to restart, including: if the current state is an idle state, determining whether the current moment and the last self-healing moment are within the self-healing inhibition period, the last self-healing moment being the moment of the most recent modem restart from the current moment; if the current moment and the last self-healing moment are within the self-healing inhibition period, executing the step of obtaining the registration status of the IMS network; if the current moment and the last self-healing moment are not within the self-healing inhibition period, the modem is instructed to restart.

[0021] When the terminal device is in an idle state, if the terminal device is currently in the self-healing inhibition period, that is, the time difference between the current moment and the last self-healing moment (the moment of restarting the Modem) is less than the preset self-healing inhibition period, in order to avoid the operation of repeatedly restarting the Modem causing other faults to be covered up and unable to be identified, it can be determined that the restart condition is not met, so the restart instruction is not issued temporarily, but the state of the terminal device is continuously monitored until the self-healing inhibition period expires, or the restart condition is met, and then the restart instruction is issued. This method can avoid the operation of repeatedly restarting the Modem causing other faults to be covered up and unable to be identified, and is highly reasonable.

[0022] In some embodiments, the idle state includes: a screen-off state, and / or an idle state (IDLE state).

[0023] The idle state is a state in which the network is registered but not connected, which can be recorded as the IDLE state.

[0024] In some embodiments, the method further includes: recording a restart event and a restart time of restarting the modem; and / or reporting a restart event and a restart time of restarting the modem.

[0025] The AP can also record the restart event and / or restart time of the current Modem so that it can be read when needed. For example, when the AP determines whether to issue a restart instruction next time, it can determine whether it is in the self-healing inhibition period based on the restart time recorded this time.

[0026] In some embodiments, instructing the modem to restart includes: determining whether the current state of the terminal device meets a preset restart condition; if so, instructing the modem to restart; if not, monitoring the state of the terminal device until the state of the terminal device meets the restart condition, and then instructing the modem to restart.

[0027] By setting the restart conditions to determine the appropriate restart time, it is possible to avoid restarting during user use and ensure that network self-healing can be tried without the user's awareness. This is highly reasonable and improves the user experience.

[0028] In some embodiments, the restart conditions include: the screen state is off, the terminal device is in idle state (IDLE state), the card has not been reinserted, the network status has not changed, no modem-related services are executed, the network supports IMS services, and is not in the self-healing inhibition period. Any one or more of the following.

[0029] The above restart condition includes any one of the multiple conditions, and may also include a combination of any two, three or four of the multiple conditions. The restart condition can be set as needed to meet different usage scenarios and user needs, with high flexibility.

[0030] In a second aspect, a network connection device is provided, comprising a unit composed of software and / or hardware, wherein the unit is used to execute any one of the methods in the technical solution described in the first aspect.

[0031] In a third aspect, a chip is provided, comprising a processor; the processor is used to read and execute a computer program stored in a memory to perform any one of the methods in the technical solution described in the first aspect.

[0032] In some embodiments, the processor is a modem.

[0033] In some embodiments, the processor is an application processor.

[0034] In some embodiments, the chip further includes a memory, and the memory is connected to the processor via a circuit or wire.

[0035] Further optionally, the chip also includes a communication interface.

[0036] In a fourth aspect, an electronic device is provided, comprising: a processor, a memory and an interface; the processor, the memory and the interface cooperate with each other so that the electronic device executes any one of the methods in the technical solution described in the first aspect.

[0037] In a fifth aspect, an electronic device is provided, comprising the chip described in the third aspect.

[0038] In a sixth aspect, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the processor executes any one of the methods in the technical solution described in the first aspect.

[0039] In a seventh aspect, a computer program product is provided, the computer program product comprising: a computer program code, when the computer program code is run on an electronic device, the electronic device executes any one of the methods in the technical solution described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 is a schematic diagram of the structure of a terminal device 100 provided in an embodiment of the present application;

[0041] Figure 2 is a software structure block diagram of the terminal device 100 provided in an embodiment of the present application;

[0042] Figure 3 This is a schematic diagram of an IMS registration process provided in an embodiment of the present application;

[0043] Figure 4 This is a software architecture diagram of restarting a modem provided in an embodiment of the present application;

[0044] Figure 5 It is a flowchart of a network connection method provided in an embodiment of the present application;

[0045] Figure 6 This is a flowchart of another network connection method provided in an embodiment of the present application;

[0046] Figure 7 is an interaction diagram of a network connection method provided in an embodiment of the present application;

[0047] Figure 8 is an interaction diagram of another network connection method provided in an embodiment of the present application;

[0048] Fig. 9 This is a software architecture diagram of a network connection method provided in an embodiment of the present application;

[0049] Fig.10 It is a structural diagram of a network connection device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0051] In the following, the terms "first", "second", and "third" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first", "second", and "third" may explicitly or implicitly include one or more of the features.

[0052] The network connection method provided in the embodiments of the present application can be applied to terminal devices such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA), etc. The embodiments of the present application do not impose any restrictions on the specific types of terminal devices.

[0053] For example, Figure 1 1 is a schematic diagram of the structure of an example of a terminal device 100 provided in an embodiment of the present application. The terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0054] It is understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

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

[0056] The software system of the terminal device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The present application embodiment takes the Android system of the layered architecture as an example to exemplify the software structure of the terminal device 100.

[0057] Figure 2 1 is a software structure diagram of the terminal device 100 of the embodiment of the present application. The layered architecture divides the software into several layers, each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, namely, the application layer, the application framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer. The application layer can include a series of application packages.

[0058] like Figure 2 As shown, the application package may include camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

[0059] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0060] like Figure 2 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

[0061] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0062] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0063] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

[0064] The phone manager is used to provide communication functions of the terminal device 100, such as management of call status (including connection, disconnection, etc.).

[0065] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0066] The notification manager enables applications to display notification information in the status bar, which can be used to convey notification-type messages and disappear automatically after a short stay without user interaction.

[0067] Android runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

[0068] The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.

[0069] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0070] The system library may include multiple functional modules, such as surface manager, media libraries, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0071] The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

[0072] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0073] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0074] A 2D graphics engine is a drawing engine for 2D drawings.

[0075] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

[0076] With the progress of social production and people's lives, people have higher and higher requirements for communication quality. Among many communication methods, calling is one of the most common and important methods.

[0077] Normally, call connections require that the terminal device register with the corresponding network normally. For example, in the case of 2G and 3G networks, the terminal device implements call services by registering the CS domain, and in the case of 4G and 5G networks, call services can be implemented by registering the IMS. The support of call services involves a complex network connection process. During the use of terminal devices, various faults may cause the caller or the called party to be unable to make calls. In order to restore call services, it is common for users to manually operate the terminal device to enter flight mode, and then cancel the flight mode and reconnect to the network to try to restore it.

[0078] However, in some cases, even if the user sets the terminal device to enter the flight mode and then cancels the flight mode, the terminal device cannot resume the call service. In this case, the user needs to restart the terminal device to resume the call service. This operation method is cumbersome, resulting in a poor user experience and a long call service recovery time.

[0079] In order to clearly describe the implementation principle of the technical solution provided by this application, firstly Figure 3 The process shown is used to illustrate the specific situation when the calling or called party fails to connect during a call on the terminal device. Figure 3 Interaction flow chart for registering a terminal device with the IMS network. Figure 3 The interactive objects include: modem, application processor (AP) of terminal equipment and network (NW) side equipment as an example for description. Among them, the modem includes non-access stratum (NAS) module, data service (DS) module and IMS module. The NAS module is used for information transmission on the control plane between the terminal equipment and the mobility management entity (MME); the DS module can establish a bearer with the NW side equipment after successful network registration; the IMS module is used to continue to register the IMS network based on the successful bearer establishment to support call services. Optionally, the above-mentioned AP can also be replaced by a multimedia application processor (MAP). The specific registration process may include the following steps:

[0080] S301. The NAS module initiates a registration request to the NW side device (if it is 5G, it can be recorded as Registration Req, if it is 4G, it can be recorded as Attach Req).

[0081] Typically, when a terminal device is turned on or starts searching for a network, the NAS module initiates a registration request to the NW test device to register the network, such as registering a 4G network or a 5G network.

[0082] S302. The NW-side device returns a registration success message (remembered as Registration Accept) to the NAS module.

[0083] Specifically, when the NW side device module receives the registration request sent by the NAS module, if the NW side device is ready and the network status is normal, the subsequent registration process can be continued to complete the registration of the basic network. The terminal device that successfully registers can provide basic network support for subsequent data services and call services.

[0084] S303: The NAS module sends a notification of successful registration to the DS module.

[0085] S304. The NAS module also sends a notification of successful registration to the IMS module.

[0086] Specifically, when the NAS module receives the registration success message returned by the NW side device, it determines that the NW side device is in a ready state and the network state is normal, and then the registration success message can be notified to the DS module and the IMS module.

[0087] S305. The IMS module sends an instruction message for initiating bearer establishment to the DS module.

[0088] Specifically, after the IMS module receives the notification of successful registration sent by the NAS module, it may send an instruction message of establishing an IMS bearer to the DS module to continue registering the call service.

[0089] S306. The DS module sends a request to establish a bearer to the NW side device.

[0090] Specifically, the DS module responds to the trigger of the indication message for establishing a bearer sent by the IMS module, and sends a protocol data unit (PDU) bearer request for establishing IMS to the NW side device (for example, in the registered 5G network, it is recorded as PDU SESSION SETUP REQ for IMS).

[0091] S307. The NW-side device returns a response message (for example, recorded as PDUSESSION SETUP ACCEPT) to the DS module to indicate that it accepts the request to establish the bearer.

[0092] Specifically, if the 5G network is registered, when the NW side device receives the request sent by the DS module to establish the PDU bearer of the IMS, if the status of the NW side device is normal and the PDU bearer can be established, the NW side device will feedback the return message of accepting the bearer establishment to the DS module, thereby establishing the PDU bearer. If the 4G network is registered, when the NW side device receives the request sent by the DS module to establish the package data network (PDN) bearer of the IMS, if the status of the NW side device is normal and the PDN bearer can be established, the NW side device will feedback the return message of accepting the bearer establishment to the DS module, thereby establishing the PDN bearer.

[0093] When the bearer is successfully established, the terminal device can register with the IMS network.

[0094] Under normal circumstances, after receiving the return message of accepting the bearer establishment request, the DS module will continue to execute S308 and subsequent steps to register the IMS network.

[0095] It should be noted that the execution process of the above S306 and S307 is also forwarded by the NAS module (not shown in the figure), which will not be repeated here.

[0096] S308: The DS module sends a bearer establishment success event to the IMS module.

[0097] When the bearer is successfully established, the DS module may send a bearer establishment success event to the IMS module based on the return message of accepting the bearer establishment request, for example, send 200event to the IMS module to notify the IMS module that the bearer has been successfully established.

[0098] S309, the IMS module reports an activation message for activating the registered IMS network to the AP;

[0099] Specifically, after receiving the bearer establishment success event, the IMS module may report an activation message (remembered as IMS PDN Activate or IMS PDU Activate) for activating the registration IMS network to the AP, so as to request activation of the IMS registration process.

[0100] S310. The AP feeds back an activation success message to the IMS module.

[0101] When the AP receives the activation message for activating the registration of the IMS network reported by the IMS module, the AP may activate the IMS network registration, that is, return an activation success message to the IMS module.

[0102] Under the instruction of the activation success message, the IMS module requests the NW side device to register the IMS network. For details, please refer to S311 and subsequent steps:

[0103] S311. The IMS module sends an IMS network registration request (referred to as IMS Register) to the NW side device.

[0104] S312. The IMS module receives the authentication information fed back by the NW-side device.

[0105] The NW-side device responds to the IMS network registration request and feeds back authentication information to the IMS module, for example, returning 401, for performing two-way authentication with the terminal device.

[0106] S313. The IMS module sends an IMS network registration request to the NW-side device again.

[0107] S314. The IMS module receives an IMS network registration success message returned by the NW-side device.

[0108] After receiving 401, the IMS module calculates and authenticates according to the authentication parameters carried in the authentication information. Once the authentication is passed, the IMS network registration request can be sent to the NW side device again. The IMS network registration request carries the relevant user authentication response parameters (expected user response, XRES).

[0109] When the authentication is passed again, the IMS network can be successfully registered, and the NW side device can return a registration success code to the IMS module, for example: register 200OK.

[0110] S315. The IMS module sends a message to the AP indicating that the IMS network has been registered.

[0111] The IMS module can also report to the AP that the IMS network has been registered. At this time, the terminal device can support call services and can receive paging (Paging) or invitation (Invite) initiated by the network side.

[0112] Above Figure 3 The process shown is the process of terminal equipment registering IMS network under normal circumstances. However, in some abnormal situations, Figure 3The process shown cannot be fully executed, and the dotted steps are steps that will not be executed under abnormal circumstances. For example, when the memory of the DS module is exhausted, resulting in an abnormal socket path between the DS module and the IMS module, the two cannot communicate normally. In other words, even after the bearer is successfully established, the DS module cannot output the 200event event to the IMS module, that is, the DS module cannot execute the above-mentioned S308 step, then the IMS module cannot be informed of the current successful bearer establishment, resulting in the IMS module not reporting the activation message of the successful bearer establishment to the AP, and the subsequent IMS network registration process cannot be carried out. Then, in the case that the IMS network cannot be registered normally, the IMS domain will not know the existence of the user of the terminal device, and call services cannot be provided, and the called party and the calling party will not be able to connect.

[0113] Based on this, the embodiment of the present application provides a network connection method. When a fault occurs inside the Modem, for example, the memory of the DS module is exhausted, resulting in the inability to communicate normally between the DS module and the IMS module, the terminal device can restore the connection of the IMS network by restarting the Modem, thereby realizing the self-healing of the IMS network. When the Modem is restarted, the memory of the DS module in the Modem will be cleared, and some other faults can also be restored together, so that the normal registration process can be re-executed, the IMS network can be successfully registered, and the call service can be restored. Optionally, in the case of an internal fault in the Modem, the Modem can send the abnormal information characterizing the fault to the AP, and the AP triggers the restart of the Modem; or the Modem itself collects the internal state, and restarts to realize network self-healing when an internal fault is found. The method can realize network self-healing without the user manually entering the flight mode and canceling the flight mode, and without restarting the entire terminal device. Since the time taken for the Modem restart is short, the self-healing efficiency is high; and the method of restarting the Modem alone to realize network self-healing can restore the call service without the user being easily perceived, which greatly improves the user experience.

[0114] The implementation logic of the network connection method provided in the embodiment of the present application can also be found in Figure 4 When a modem fails, the abnormal information representing the failure can be reported to the abnormal monitoring module of the application layer through the protocol conversion layer (Radio interface layer, RIL). After the abnormal monitoring module receives the abnormal information, it can instruct the restart module of the application layer to issue a restart instruction of the modem. Figure 4The restart module in the system can also be called a self-healing module. The restart instruction is generated by the restart module and transmitted to the modem via the RIL to instruct the modem to restart. The abnormal monitoring module can also report abnormal information to the cloud server so that the cloud server can perform statistics. Optionally, a configuration file can also be set at the application layer. The configuration file can be a file in XML format, and the timing of issuing the restart instruction can be set in the configuration file.

[0115] The principles of the technical solutions involved in the embodiments of the present application are summarized in the foregoing. Next, the technical solutions of the present application are described in detail with reference to the accompanying drawings.

[0116] The execution entity of the embodiment of the present application may be an AP. Figure 5 The description is based on the execution subject AP. It includes:

[0117] S501: Obtain the registration status of the IMS network.

[0118] Optionally, the AP may continue to monitor whether the Modem has successfully registered with the IMS network to obtain a registration status of the IMS network, which may be a successful registration or an unsuccessful registration.

[0119] Optionally, the AP may collect the abnormal information reported by the modem. Optionally, the abnormal information is used to indicate that the modem is in an abnormal state, and may also indicate the specific type of the abnormal state. Optionally, a management module may be set in the AP, and the AP collects the abnormal information reported by the modem through the management module. When the IMS network fails to register successfully, it may be reported to the AP in the form of abnormal information.

[0120] S502: Obtain bearer establishment status.

[0121] Specifically, the AP can also monitor the establishment of the bearer of the Modem through the management module, for example, whether the PDU bearer or PDN bearer is successfully established. Taking the registration of the 5G network as an example, when the PDU bearer is successfully established, the DS module will receive a return message from the NW side device accepting the request to establish the bearer, and the return message can be recorded as the first message.

[0122] When the bearer is successfully established, the AP can continue to monitor whether the modem has successfully registered the IMS network. Optionally, the AP can monitor whether the modem has successfully registered the IMS network through the management module. It should be noted that the AP can monitor whether the bearer of the modem is successfully established by monitoring the status of the DS module, and the AP can monitor whether the IMS network registration of the modem is successful by monitoring the status of the IMS module.

[0123] S503: If the registration status of the IMS network is unsuccessful registration and the bearer establishment status is successful bearer establishment, instruct the modem to restart to connect to the IMS network.

[0124] If the modem side fails to initiate an IMS network registration request, which will result in failure to successfully register with the IMS network, then when the registration status of the IMS network is unsuccessful registration, but the bearer establishment status is successful bearer establishment, the AP can instruct the modem to restart to connect to the IMS network.

[0125] For example, after the bearer is successfully established, the Modem fails to successfully register with the IMS network. For example, if the management module monitors that the Modem does not receive a message of successful registration with the IMS network within a preset period of time after the bearer is successfully established, it means that the Modem has failed to successfully register with the IMS network (unsuccessful registration). This may be due to a fault inside the Modem. For example, when the socket path between the DS module and the IMS module is blocked, even if the bearer is successfully established, the DS module cannot send a bearer establishment success event to the IMS module, causing the IMS module to be unable to execute the subsequent process of registering the IMS network. At this time, the AP can send a restart command to the Modem, instructing the Modem to restart and achieve network self-healing.

[0126] Optionally, the order in which the AP determines the registration status of the IMS network and determines the bearer establishment status is not limited, as long as the result can be correctly determined. For example, the AP can first determine the registration status of the current IMS network. If the registration status of the IMS network is unsuccessful registration, it continues to determine whether the bearer is successfully established. If the bearer is successfully established, it means that there may be a fault inside the modem, so the modem is restarted for self-healing. If the bearer is not successfully established, but fails to be established, it means that restarting the modem may not be able to self-heal, so there is no need to restart the modem.

[0127] Optionally, the AP may first determine whether the bearer is successfully established. If established successfully, the AP continues to determine the registration status of the current IMS network. If the registration status of the IMS network is unsuccessful registration, the Modem may be restarted to achieve self-healing.

[0128] In some embodiments, the AP determines whether the modem has successfully registered with the IMS network by starting a timer when the AP monitors a first message indicating that the modem's bearer has been successfully established. If the AP does not monitor a second message indicating that the modem has successfully registered with the IMS network within a preset period after the timer is started, or monitors a message indicating that the modem has not successfully registered with the IMS network, it means that the modem has not successfully registered with the IMS network. At this time, the AP can continue to monitor whether the modem's bearer has been successfully established, or can continue to monitor whether the modem has successfully registered with the IMS network. If the AP monitors that the modem has successfully registered with the IMS network within a preset period after starting the timer, there is no need to restart the modem.

[0129] Figure 5 In the method shown in the embodiment, when the AP monitors that the bearer of the Modem is successfully established but has not successfully registered the IMS network, it can restore the connection of the IMS network by restarting the Modem. This method can achieve network self-healing without the user having to manually restart the entire terminal device. Since the time taken by the Modem restart is short, the self-healing efficiency is high; and the method of restarting the Modem alone to achieve network self-healing can restore the call service without the user's perception, thereby improving the user experience.

[0130] Optionally, the failure to successfully register with the IMS network, that is, the failure to receive the second message, may be due to the fact that the modem side has not initiated an IMS network registration request. If the second message is not received, and it is determined that no registration has been initiated to the IMS network (sending an IMS network registration request). At this time, the modem can be restarted if the bearer is successfully established. If the modem side has initiated an IMS network registration request, but has not received a correct response from the network side, it cannot successfully register with the IMS network. At this time, it may be a problem on the network side. Restarting the modem cannot restore the IMS network, so there is no need to restart the modem.

[0131] In some embodiments, when the AP receives abnormal information indicating that the Modem has failed reported by the Modem, or when the AP monitors abnormal information indicating that the Modem has failed, the AP will not directly issue a restart instruction to instruct the Modem to restart, but will determine whether it is appropriate to restart the Modem in combination with the current state of the terminal device. Optionally, the terminal device can monitor its current state. If it is found that the current state meets the preset restart condition, it means that restarting the Modem at this time will not affect the user's use of the terminal device, or will not be perceived by the user. The AP can issue a restart instruction to restart the Modem after obtaining the abnormal information of the Modem. If the current state does not meet the preset restart condition, it means that if the Modem is restarted at this time, it will affect the user's use of the terminal device and will be perceived by the user, so it is not appropriate to perform the restart operation of the Modem. The AP can continue to monitor the state of the terminal device, and only issue a restart instruction to instruct the Modem to restart when the state meets the restart condition, thereby restoring the network. In other words, the terminal device can choose a suitable time to restart the Modem according to the restart condition, realize network self-healing, do not affect user use, thereby avoiding being perceived by the user, and improving user experience.

[0132] Next, the situation where the restart conditions are met is described. The restart conditions may include: the screen is off, the terminal device is in the IDLE state, the terminal device is not performing any service involving the modem, the terminal device is not in the self-healing suppression period at the current moment, the card is not reinserted, the network status has not changed, and the network supports any one or more of the following combinations.

[0133] Optionally, when the screen of the terminal device is off, it is considered that the possibility that the user is currently using the terminal device is relatively small, so it can be determined that the restart condition is met, and a restart instruction is issued; if the screen is on, it is considered that the possibility that the user is currently using the terminal device is relatively high. If restarting the modem is easily perceived by the user, it is determined that the restart condition is not met. The restart instruction may not be issued temporarily, but the status of the terminal device may continue to be monitored until the restart condition is met.

[0134] Optionally, when the terminal device is in the ILDE state, it is determined that the restart condition is met and a restart instruction is issued; if the terminal device is not in the ILDE state, but in a non-ILDE state such as a data service state, it is determined that the restart condition is not met, and the restart instruction may not be issued temporarily, but the status of the terminal device continues to be monitored until the restart condition is met.

[0135] Optionally, if the terminal device is not currently performing any service related to the modem, it can be determined that the restart condition is met and a restart instruction is issued. If the terminal device is currently performing any service related to the modem, such as playing a video or music, it can be determined that the restart condition is not met. Therefore, the restart instruction is not issued temporarily, but the status of the terminal device is continuously monitored until the restart condition is met.

[0136] Optionally, if the current moment is not within the self-healing inhibition period, it means that the operation of restarting the Modem has not been performed within a period of self-healing inhibition period, then it can be determined that the restart condition is met and a restart instruction is issued. If the terminal device is currently within the self-healing inhibition period, that is, the time difference between the current moment and the last self-healing moment (the moment of restarting the Modem) is less than the preset self-healing inhibition period. In order to avoid repeated restarts of the Modem that cause other faults to be masked and unrecognizable, it can be determined that the restart condition is not met, so the restart instruction is not issued temporarily, but the status of the terminal device continues to be monitored until the restart condition is met.

[0137] Optionally, if the terminal device detects that the card, such as the Subscriber Identity Module (SIM), has not been reinserted, for example, there is no record of inserting the card within a preset period after the timer is started, indicating that the user has not manually performed the self-healing operation of pulling out and inserting the card, it can be determined that the restart condition is met, and then a restart instruction is issued. If the terminal device detects that the card has been reinserted, for example, there is a record of inserting the card within a preset period after the timer is started, indicating that the user has manually performed the self-healing operation of pulling out and inserting the card. In order to avoid repeated self-healing networks, the restart instruction may not be issued temporarily, and the status of the terminal device continues to be monitored until the restart condition is met.

[0138] Optionally, if the network status of the terminal device has not changed, for example, the call service on the 5G network is not supported, and the current network status is still in the 5G network, it means that the network has not rolled back, then it can be determined that the restart condition is met and a restart instruction is issued. If the network status of the terminal device has changed, for example, the call service on the 5G network is not supported, and the network status at this time is registered with the 4G network; or, the call service on the 4G network is not supported, and the network status at this time is registered with the 2G or 3G network, it means that the terminal device has rolled back the network. In some cases, the rollback network can restore the call service, so there is no need to restart the modem to repeat the self-healing network, so it can be determined that the restart condition is not met and there is no need to issue a restart instruction.

[0139] Optionally, if the terminal device detects that the network side does not support call services, for example, the user of the terminal device is in arrears and the operator has stopped the call service of the terminal device, then even if the modem is restarted, the call service cannot be restored. It can be determined that the restart condition is not met and there is no need to issue a restart instruction; if the terminal device detects that the network supports call services and there is no arrears that caused the operator to stop the call service, it can be determined that the restart conditions are met and a restart instruction is issued.

[0140] Optionally, the restart condition may also be met when the terminal device detects that the current state satisfies any two, three or more combinations of the following states: the screen is off, the terminal device is in IDLE state, the terminal device is not performing any modem-related services, the terminal device is not in the self-healing suppression period, the card has not been reinserted, the network status has not changed, and the network supports IMS services. In this case, it can be determined that the restart condition is met and a restart instruction is output.

[0141] Figure 6 A flowchart of a network connection method provided in an embodiment of the present application. The method uses the restart conditions including: the screen is off, the terminal device is in the IDLE state, and the terminal device is not in the self-healing inhibition period as an example, including:

[0142] S601: Obtain a first message indicating that a bearer is successfully established.

[0143] For details of this step, please refer to Figure 5 The relevant description about establishment of monitoring bearer in the embodiment will not be repeated here.

[0144] S602: Start the timer.

[0145] When the bearer is successfully established, the timer can be started.

[0146] S603: Determine whether the timer has timed out.

[0147] When the bearer is successfully established, if the timer exceeds the preset period T, it means that the timer has timed out.

[0148] S604: Determine whether IMS registration has not been initiated. If yes, execute S605.

[0149] Specifically, the AP can confirm whether IMS registration has been initiated. If IMS registration has not been initiated, it can be determined that the modem is likely to be faulty and needs to be restarted. If IMS registration has been initiated, you can wait for IMS registration and implement call services after IMS registration is successful without restarting the modem.

[0150] S605: Determine whether the current screen is in the off state and in the IDLE state. If yes, execute S606; if no, execute S604.

[0151] When the modem needs to be restarted, the AP will not directly send a restart command to the modem, but can be combined with the current state of the terminal device. If the screen of the terminal device is off and the terminal device is in the IDLE state, it means that the user is not using the terminal device at this time, and the modem can be restarted. Optionally, when the screen is off and the terminal device is in the IDLE state, step S606 can be continued. If the screen is on, or the terminal device is not in the IDLE state, but in a business state such as a data service, it means that this is not the right time to restart, so you can return to the step of S604 and wait for the arrival of the restart time.

[0152] S606: Determine whether the current state is in the self-healing inhibition period according to the last self-healing time. If yes, return to S604; if no, execute S607.

[0153] S607: Issue a restart instruction.

[0154] When the screen of the terminal device is off and the terminal device is in the IDLE state, the AP can also obtain the last self-healing time, and then determine whether the current moment is in the self-healing inhibition period based on the last self-healing time. Optionally, the last self-healing time can be stored in a non-volatile memory (NV) so that it can be read when needed. Optionally, the self-healing inhibition period can be set according to user needs, such as three days, seven days, and other periods. Taking the self-healing inhibition period of seven days as an example, if the last self-healing time was three days ago, it means that the current moment is still in the self-healing inhibition period, so the Modem will not be restarted temporarily. If the last self-healing time was eight days ago, it means that the current moment is no longer in the self-healing inhibition period, then it is determined that the restart condition is currently met, so a restart instruction is issued to instruct the Modem to restart.

[0155] Optionally, the AP can determine whether the current state of the terminal device meets the restart condition by first determining whether it is in the self-healing inhibition period, then determining whether it is in the screen-off state, and finally determining whether the terminal device is in the IDLE state. That is, the above steps S605 and S606 can be interchanged. When the restart conditions include multiple single conditions such as the screen is in the screen-off state, the terminal device is in the IDLE state, the terminal device is not performing services involving the modem, the terminal device is not in the self-healing inhibition period, the card has not been reinserted, the resident state has not changed, and the network supports IMS services, the embodiment of the present application does not limit the judgment order of each single condition in the restart condition. As long as it is determined one by one that the preset restart conditions are met, it can be determined that the restart timing is met. The modem can be restarted when the IMS network registration fails to succeed to achieve network self-healing.

[0156] Optionally, the restart conditions can be written into a configuration file in XML format and then stored in the application layer of the terminal device for reading. Optionally, the user can also modify the configuration file in XML format as needed to modify the restart conditions, such as adding new conditions, deleting or modifying existing conditions to meet the needs of different scenarios.

[0157] S608: Record the restart time and / or restart event.

[0158] Optionally, the AP can report the restart event and restart time to the application layer, and then report it to the cloud server through the corresponding abnormal monitoring module set in the application layer, so that the cloud server can perform fault statistics, self-healing statistics and subsequent adjustment of the modem management strategy.

[0159] Optionally, the AP can also record the restart event and / or restart time of this Modem, and write the restart event and / or restart time into NV so that it can be read when needed. For example, when the AP determines whether it needs to issue a restart instruction next time, it can determine whether it is in the self-healing inhibition period based on the restart time recorded this time. Optionally, the restart event and / or restart time can also be stored in other locations, which is not limited in the embodiments of the present application.

[0160] Above Figure 6 In the illustrated embodiment, step S608 may be performed or not performed as required.

[0161] To clearly describe Figure 6 The timing of the embodiment can be Figure 6 The technical solution is explained in combination with the timing interaction diagram. For details, please refer to Figure 7 shown. Figure 7In the process, after the terminal device is powered on, the bearer (PDU / PDN) establishment status can be obtained by monitoring the events of the interface of the maintenance and measurement event, and the IMS registration status can also be monitored. At this time, the terminal device executes the normal registration process, such as executing S301 to S307. When the channels of the DS module and the IMS module fail, although S308 cannot be executed normally, the management module can still obtain the bearer establishment status from the interface of the maintenance and measurement event. If the bearer is established successfully, the management module can obtain the message that the PDU / PDN is successfully established. Then, steps S603 to S608 can be executed to achieve network self-healing.

[0162] Optionally, the management module may be a functional module set at the FWK layer. The management module obtains various states of the terminal device through various probes at the application layer, and then determines the restart timing in combination with the various states of the terminal device, for example, executing Figure 6 Technical solutions of embodiments and related embodiments.

[0163] The above embodiments are described with AP as the execution subject, and the technical solution of the present application can also be implemented with Modem as the execution subject. Specifically, a management module similar to that in the above embodiments can be set in the Modem to collect abnormal information inside the Modem, and determine whether to restart the Modem according to the specific situation of the abnormal information, as shown in FIG8, including:

[0164] S801. Obtain the first message of successful bearer establishment.

[0165] S802: Start the timer.

[0166] S803: Determine whether the timer has timed out.

[0167] S804: Determine whether IMS registration has not been initiated. If yes, execute step S805.

[0168] The detailed description of the above S801 to S804 can be found in S601 to S604, which will not be repeated here.

[0169] S805: Determine whether the current state of the terminal device meets a preset restart condition.

[0170] The restart conditions in this embodiment can be found in the relevant description in the previous text, and will not be repeated here.

[0171] S806. Restart.

[0172] The management module can instruct the Modem to restart to achieve network self-healing.

[0173] Above Figure 8In the illustrated embodiment, when the management module in the modem determines that a fault has occurred inside the modem based on abnormal information detected by itself, such as abnormal information that a bearer is established but the IMS network is not successfully registered, the modem may be instructed to restart.

[0174] Optionally, the above Figure 8 In the embodiment, it is also possible to choose whether to execute step S608 as needed.

[0175] Optionally, no matter whether the AP or the Modem is the executor, the above-mentioned management module can be set in the FWK layer. The management module can obtain the status of the terminal device detected by the application layer, for example: whether the screen is off or on, whether the terminal device is in the IDLE state, whether the terminal device is performing services involving the Modem, whether the terminal device is in the self-healing inhibition period at the current moment, whether the card is reinserted, whether the resident status changes, and whether the network supports any one or more combinations of IMS services. Optionally, the management module can also monitor whether the bearer is successfully established and whether the IMS network is registered. In other words, the two conditions of whether the bearer is successfully established and whether the IMS network is registered can also be used as part of multiple restart conditions, and then combined with other conditions to determine whether the Modem needs to be restarted. The management module makes a self-healing decision based on the preset self-healing strategy, that is, it decides whether the Modem needs to be restarted, and instructs the Modem to restart at an appropriate restart time, thereby achieving network self-healing. Optionally, the software architecture diagram of this embodiment can be found in Fig. 9 Specifically including:

[0176] The application layer of the terminal device can set various probes to detect the status of the terminal device (also known as the status of the system). The relevant information of these statuses can be transmitted to the management module 1 in the FWK layer. The management module 1 makes a self-healing decision based on the preset self-healing strategy and the acquired status. Optionally, if the management module 1 determines that the bearer has not been successfully established, it means that the fault at this time is more serious and may not be solved by restarting the Modem alone. Therefore, the self-healing operation of stage 1 can be performed, such as restarting the terminal device (restarting the Radio). If the bearer is successfully established and the IMS network registration fails, it can be judged based on other status whether the current status meets the restart conditions. If it does, the self-healing operation of stage 2 can be performed, that is, restarting the Modem. When the Modem needs to be restarted, the management module can send a restart instruction to the Modem through the restart interface of the RIL layer. It should be noted that a management module 2 needs to be set up on the modem side. The management module 2 can report the abnormal information on the modem side, such as the first message, to the RIL layer through the corresponding interface (such as QMI or AT), and then transmit it to the management module 1 of the FWK layer through the relevant interface (IMS / NAS / UIM) of the RIL layer to realize self-healing judgment.

[0177] The above describes in detail an example of the method provided by the present application. It is understandable that, in order to implement the above functions, the corresponding device includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

[0178] The present application can divide the network connection device into functional modules according to the above method examples. For example, each function can be divided into each functional module, or two or more functions can be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0179] Fig.10 The schematic diagram of the structure of a network connection device provided by the present application is shown. The device 1000 includes:

[0180] The acquisition module 1001 is used to acquire the registration status of the IMS network and acquire the bearer establishment status.

[0181] The restart module 1002 is configured to instruct the modem to restart to connect to the IMS network when the registration status of the IMS network is unsuccessful registration and the bearer establishment status is successful bearer establishment.

[0182] In some embodiments, the restart module 1002 is specifically used to determine whether the registration status of the IMS network is unsuccessful registration; if the registration status of the IMS network is unsuccessful registration, determine whether the bearer establishment status is successful bearer establishment; if the bearer establishment status is successful bearer establishment, instruct the modem to restart.

[0183] In some embodiments, the restart module 1002 is specifically used to determine whether an IMS network registration request has been initiated to the IMS network if the registration status of the IMS network is unsuccessful registration and the bearer establishment status is successful bearer establishment; if the IMS network registration request has not been initiated to the IMS network, instruct the modem to restart.

[0184] In some embodiments, the acquisition module 1001 is specifically used to acquire a first message, where the first message is used to indicate that the bearer establishment status is bearer establishment success, and in response to the first message, determine whether a second message is received within a preset period, where the second message is used to indicate that the registration status of the IMS network is registration success;

[0185] The restart module 1002 is specifically configured to instruct the modem to restart if the second message is not received within the preset period.

[0186] In some embodiments, the restart module 1002 is specifically used to determine whether the current state of the terminal device is an idle state; if the current state is the idle state, instruct the modem to restart; if the current state is not the idle state, execute the step of obtaining the registration state of the IMS network.

[0187] In some embodiments, the first restart module 1002 is specifically used to determine, if the current state is the idle state, whether the current moment and the last self-healing moment are within the self-healing inhibition period, and the last self-healing moment is the moment when the modem was restarted most recently from the current moment; if the current moment and the last self-healing moment are within the self-healing inhibition period, then execute the step of obtaining the registration status of the IMS network; if the current moment and the last self-healing moment are not within the self-healing inhibition period, then instruct the modem to restart.

[0188] In some embodiments, the idle state includes: a screen-off state, and / or an idle state.

[0189] In some embodiments, the apparatus 1000 further comprises a processing and recording module, the recording module being used to record a restart event and a restart time of the restart modem; and / or, to report a restart event and a restart time of the restart modem.

[0190] In some embodiments, the restart conditions include: the screen state is off, the terminal device is in idle state, the card has not been reinserted, the network status has not changed, no modem-related services are executed, the network supports IMS services, and is not in the self-healing inhibition period. Any one or more of the following.

[0191] The specific manner in which the network connection device executes the network connection method and the beneficial effects produced can be found in the relevant description in the method embodiment, which will not be repeated here.

[0192] An embodiment of the present application further provides a chip, comprising a processor; the processor is used to read and execute a computer program stored in a memory to perform a method as described in any one of the aforementioned embodiments.

[0193] Optionally, the chip may be an application processor (AP) or a modem.

[0194] An embodiment of the present application also provides a modem, which is used to execute the method as described in any of the above embodiments.

[0195] An embodiment of the present application further provides an application processor, which is used to execute the method as described in any one of the aforementioned embodiments.

[0196] The present application also provides an electronic device, including the above processor. The electronic device provided by this embodiment can be Figure 1 The terminal device 100 shown is used to perform the above-mentioned network connection method. In the case of an integrated unit, the terminal device may include a processing module, a storage module and a communication module. Among them, the processing module can be used to control and manage the actions of the terminal device, for example, it can be used to support the terminal device to execute the steps performed by the display unit, the detection unit and the processing unit. The storage module can be used to support the terminal device to execute and store program codes and data, etc. The communication module can be used to support the communication between the terminal device and other devices.

[0197] Among them, the processing module can be a processor or a controller. It can implement or execute various exemplary logic boxes, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of digital signal processor (DSP) and a microprocessor, etc. The storage module can be a memory. The communication module can specifically be a device that interacts with other terminal devices, such as a radio frequency circuit, a Bluetooth chip, a Wi-Fi chip, etc.

[0198] In one embodiment, when the processing module is a processor and the storage module is a memory, the terminal device involved in this embodiment may be a Figure 1 Device of the structure shown.

[0199] An embodiment of the present application also provides an electronic device, comprising the above chip.

[0200] An embodiment of the present application also provides an electronic device, including the above-mentioned modem.

[0201] An embodiment of the present application also provides an electronic device, including the above-mentioned application processor.

[0202] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the processor executes the network connection method described in any of the above embodiments.

[0203] The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer is caused to execute the above-mentioned related steps to implement the network connection method in the above-mentioned embodiment.

[0204] Among them, the electronic device, computer-readable storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above and will not be repeated here.

[0205] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, the replaced units may or may not be physically separated, and the components displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment.

[0206] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0207] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0208] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A network connection method, characterized in that: include: Obtaining the registration status of the Internet Multimedia Subsystem IMS network; Get the bearer establishment status; If the registration status of the IMS network is unsuccessful registration, and the bearer establishment status is successful bearer establishment, determining whether an IMS network registration request has been initiated to the IMS network; If the IMS network registration request has not been initiated to the IMS network, the modem is instructed to restart to connect to the IMS network.

2. The method according to claim 1, characterized in that The acquiring the bearer establishment status includes: Obtaining a first message, where the first message is used to indicate that the bearer establishment status is bearer establishment success; The obtaining of the registration status of the Internet Multimedia Subsystem IMS network includes: In response to the first message, determining whether a second message is received within a preset period, the second message being used to indicate that the registration status of the IMS network is successful registration; If the registration status of the IMS network is unsuccessful registration, and the bearer establishment status is bearer establishment success, instructing the modem to restart, comprising: If the second message is not received within the preset period, the modem is instructed to restart.

3. The method according to claim 2, characterized in that The instructing the modem to restart comprises: Determine whether the current state of the terminal device is an idle state; If the current state is the idle state, instructing the modem to restart; If the current state is not the idle state, the step of obtaining the registration state of the IMS network is performed.

4. The method according to claim 3, characterized in that If the current state is the idle state, instructing the modem to restart, comprising: If the current state is the idle state, determining whether the current time and the last self-healing time are within the self-healing inhibition period, the last self-healing time being the time when the modem was restarted most recently from the current time; If the current moment and the last self-healing moment are within the self-healing inhibition period, executing the step of obtaining the registration status of the IMS network; If the current time and the last self-healing time are not within the self-healing inhibition period, the modem is instructed to restart.

5. The method according to claim 3, characterized in that: The idle state includes: a screen-off state, and / or an idle state (IDLE state).

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: recording a restart event and / or a restart time of restarting the modem; and / or, Reporting the restart event and / or the restart time of restarting the modem.

7. The method according to any one of claims 2 to 5, characterized in that The instructing the modem to restart comprises: Determine whether the current state of the terminal device meets the preset restart condition; If satisfied, instructing the modem to restart; If not, the state of the terminal device is monitored until the state of the terminal device meets the restart condition, and the modem is instructed to restart.

8. The method according to claim 7, characterized in that The restart conditions include: The screen status is any one or more of the following: the screen is off, the terminal device is in idle state (IDLE state), the card has not been reinserted, the network status has not changed, no services involving the modem are executed, the network supports IMS services, and is not in a self-healing inhibition period.

9. A chip, characterized in that: The device comprises a processor; the processor is used to read and execute a computer program stored in a memory to perform the method according to any one of claims 1 to 8.

10. The chip according to claim 9, characterized in that: The processor is a modem.

11. An electronic device, characterized in that: include: Processors, memory, and interfaces; The processor, the memory and the interface cooperate with each other so that the electronic device performs the method according to any one of claims 1 to 8; Alternatively, the electronic device comprises the chip as claimed in claim 9 or 10.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 8.

Images