Interface display method and terminal equipment

Abstract

The invention provides an interface display method and terminal equipment, and relates to the technical field of conversation. According to the method, when the terminal equipment is in the flight mode and the target number dialed by the user is a non-emergency number, an entrance for rapidly closing the flight mode can be provided for the user, and user operation is simplified. The method comprises the steps that a first interface is displayed at a first time point, the first interface comprises a dialing button and a first icon, and the first icon indicates that the terminal equipment is in a flight mode; in response to an operation of inputting a target number on the first interface by a user, displaying the target number on the first interface, the target number being a non-emergency number; in response to an operation of clicking a dialing button on the first interface by the user, displaying a second interface, the second interface including prompt information and a first option, and the prompt information being used for prompting to close the flight mode; and in response to an operation of clicking the first option of the second interface by the user, displaying a third interface which does not include the first icon.

Description

Interface display method and terminal device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on May 26, 2023, with application number 202310615698.7 and invention name “An interface display method and terminal device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of call technology, and in particular to an interface display method and terminal device. Background Art

[0003] With the advancement of communications technology, mobile devices have become essential tools for communication. For example, if a mobile phone is in airplane mode and detects a user dialing an emergency number (such as 119 or 120), it automatically turns off airplane mode and initiates the emergency call. If the phone detects a non-emergency number, it prompts the user to turn off airplane mode to make the call. In this case, requiring the user to exit the call and automatically turn off airplane mode would reduce call efficiency and significantly impact the user experience.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide an interface display method and a terminal device for simplifying the operation of turning off the flight mode for users and improving the user experience.

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

[0007] In a first aspect, the present application provides an interface display method, applied to a terminal device, the method comprising: displaying a first interface at a first time point, the first interface including a dial button and a first icon, the first icon indicating that the terminal device is in flight mode; in response to a user inputting a target number on the first interface, displaying the target number on the first interface, the target number being a non-emergency number; in response to a user clicking the dial button on the first interface, displaying a second interface, the second interface including prompt information and a first option, the prompt information being used to prompt to turn off flight mode; after the user clicks the dial button, at a second time point, obtaining a description of the disconnection reason, the description of the disconnection reason being empty, the terminal device being in flight mode between the first time point and the second time point, and receiving only one user click on the dial button, the second time point being later than the first time point; in response to a user clicking the first option on the second interface, displaying a third interface, the third interface not including the first icon. The third interface not including the first icon is used to indicate that the terminal device is not in flight mode.

[0008] Among them, the first time point is the time point when the first interface is displayed, and the second time point is the time point when the description of the disconnection reason is obtained. The first time point and the second time point can be any time point. That is to say, when the terminal device is in flight mode and the target number dialed by the user is a non-emergency number, the terminal device can display the second interface including the first option. In this way, the user can quickly turn off the flight mode through the first option. In addition, based on the fact that the description of the disconnection reason is empty, the terminal device will not display the preset application's pop-up box for reminding the user to turn off the flight mode again, avoiding the inconvenience caused to the user by the terminal reminding the user to turn off the flight mode multiple times.

[0009] In one implementation of the first aspect, the third interface includes a target number and a second icon, wherein the second icon indicates that the terminal device is connected to the operator's network. That is, after the user clicks the dial button, the terminal device can directly display the third interface for the user to quickly redial the target number without the user having to re-enter the target number.

[0010] In one implementation of the first aspect, the method further includes: obtaining a reason value for the disconnection reason, where the reason value for the disconnection reason is POWER OFF. That is, the disconnection reason includes not only a description (value) but also a reason value. If the terminal device is in airplane mode and the destination number dialed by the user is a non-emergency number, the terminal device may set the disconnection reason to POWER OFF.

[0011] In an implementation method provided in the first aspect, the first interface is an interface of a dialing application, and in response to the user clicking a dial button on the first interface, a second interface is displayed, including: in response to the user clicking a dial button on the first interface, the second interface is displayed when the target number is a non-emergency number, the terminal device is in flight mode, and the dialing application is a preset application.

[0012] In an implementation manner provided by the first aspect, after displaying the second interface, the method further includes: setting the description in the disconnection reason to empty.

[0013] In an implementation provided by the first aspect, in response to a user clicking a dial button on the first interface, a second interface is displayed, including: creating a connection object in response to the user clicking the dial button on the first interface; generating a disconnection reason based on a failure to create the connection object, the description of the disconnection reason including prompt information; when the dialing application is a preset application, displaying the second interface based on the description of the disconnection reason.

[0014] In an implementation manner provided in the first aspect, the failure to create the connection object is based on the fact that the target number is an emergency number and the terminal device is in flight mode.

[0015] In an implementation manner provided by the first aspect, the method further includes: when the dialing application is not a preset application or the terminal device is not in airplane mode, setting the description in the disconnection reason to a preset value.

[0016] In an implementation manner provided in the first aspect, based on the description of the disconnection reason being empty, the terminal device does not display the second pop-up box, and the second pop-up box is a pop-up box of a preset application.

[0017] In a second aspect, the present application also provides an interface display method, which is applied to a terminal device, and the method includes: during a call on the terminal device, in response to receiving an operation by the user to turn on the flight mode, turning on the flight mode and ending the call; if the dialing application is a preset application, displaying a first pop-up box, the first pop-up box includes a first option; in response to the user clicking the first option, turning off the flight mode; after displaying the first pop-up box, obtaining the reason for disconnection, and the description in the reason for disconnection is empty; in response to determining that the description in the reason for disconnection is empty, not displaying the second pop-up box, and the second pop-up box does not include an option for turning off the flight mode.

[0018] In a third aspect, the present application provides an interface display method, which is applied to a terminal device, and the method includes: displaying a dialing interface, which is an interface of a dialing application, and the dialing interface includes a dialing button and a target number entered by the user; in response to the user clicking the dialing button, when the target number is a non-emergency number, the terminal device is in flight mode, and the dialing application is a preset application, a first pop-up box is displayed, and the first pop-up box includes a first option; in response to the user clicking the first option, the flight mode is turned off; after displaying the first pop-up box, the disconnection reason is obtained, and the description in the disconnection reason is empty; in response to determining that the description in the disconnection reason is empty, the second pop-up box is not displayed, and the second pop-up box does not include an option for turning off the flight mode.

[0019] In an implementation provided by the third aspect, the method further includes: creating a connection object in response to the user clicking a dial button; and generating a disconnection reason when the creation of the connection object fails.

[0020] In an implementation manner provided by the third aspect, the failure to create the connection object includes: the failure to create the connection object when the target number is an emergency number and the terminal device is in flight mode.

[0021] In an implementation provided by the third aspect, generating a disconnection reason includes: when the dial-up application is a preset application, setting the description in the disconnection reason to empty.

[0022] In an implementation provided by the third aspect, generating a disconnection reason further includes: when the dialing application is not a preset application or the terminal device is not in airplane mode, setting the description in the disconnection reason to a preset value.

[0023] In an embodiment provided in the third aspect, in response to the user clicking the dial button, when the target number is a non-emergency number, the terminal device is in flight mode and the dial application is a preset application, a first pop-up window is displayed, including: in response to the user clicking the dial button, a call interface is displayed; wherein, when the target number is a non-emergency number, the terminal device is in flight mode and the dial application is a preset application, the call interface includes a first pop-up window.

[0024] In a fourth aspect, the present application also provides a terminal device, comprising: a memory, one or more processors; the memory is coupled to the processor; wherein the memory is used to store computer program code, and the computer program code includes computer instructions; when the computer instructions are executed by the processor, the terminal device executes the method of any one of the embodiments of the first to third aspects.

[0025] In a fifth aspect, the present application also provides a computer-readable storage medium comprising computer instructions, which, when executed on a terminal device, enables the terminal device to execute the method of any one of the embodiments of the first to third aspects.

[0026] In a sixth aspect, the present application provides a computer program product, which, when executed on a terminal device, enables the terminal device to execute the method of any one of the embodiments of the first to third aspects.

[0027] In a seventh aspect, the present application provides a chip system comprising one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via a circuit. The chip system can be applied to a terminal device comprising a communication module and a memory. The interface circuit is configured to receive a signal from the memory of the terminal device and send the received signal to the processor, the signal comprising a computer instruction stored in the memory. When the processor executes the computer instruction, the terminal device can execute the method of any one of the embodiments of aspects 1 to 3.

[0028] Among them, the technical effects brought about by any implementation method in the second to seventh aspects can refer to the technical effects brought about by different design methods in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] FIG1 is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0030] FIG2 is a schematic diagram of a process of disabling airplane mode according to an embodiment of the present application;

[0031] FIG3 is a schematic structural diagram of a terminal device provided in an embodiment of the present application;

[0032] FIG4 is a block diagram of a software architecture of a terminal device provided in an embodiment of the present application;

[0033] FIG5 is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0034] FIG6 is a schematic diagram of an interface provided in an embodiment of the present application;

[0035] FIG7 is a schematic diagram of another application scenario provided by an embodiment of the present application;

[0036] FIG8 is a flow chart of a method for displaying an interface according to an embodiment of the present application;

[0037] FIG9 is a second flow chart of an interface display method provided in an embodiment of the present application;

[0038] FIG10 is a schematic structural diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The technical solutions in the embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and claims of the present application, the singular expressions "a", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one or more (including two). The term "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist; for example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0040] References to "one embodiment" or "some embodiments" etc. described in this specification mean that the specific features, structures or characteristics described in conjunction with the embodiment are included in one or more embodiments of the present application. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in another way. The term "connected" includes direct and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

[0041] In the embodiments of this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

[0042] When the phone is in airplane mode, if the phone detects that the user is calling a non-emergency number, it will remind the user to turn off airplane mode before making the call. TM The dial pad (Google Dialer) requires users to exit the call and turn off the airplane mode in the above scenario before they can dial non-emergency numbers normally, which is very inconvenient for users. TM The dial pad is an application with dialing, calling and contact functions. TM When the dialer detects that the user is dialing a non-emergency number while in airplane mode, a pop-up window will be displayed to remind the user to turn off airplane mode. TM The dial pad may also be called the first dial pad, native dial pad, default application, etc.

[0043] The following describes the application scenarios of this application with reference to the accompanying drawings. As shown in FIG1 (a), the mobile phone can display an interface 101, which can be a Google TMDialing interface of the dial pad. In addition, the icon 102 in the interface 101 indicates that the mobile phone is in flight mode; the interface 101 also includes a dial button 103 and a non-emergency number entered by the user (for example, 152****0000). Optionally, the interface 101 may also include a dial pad for the user to enter a number. In response to the user's operation on the dial button 103, the mobile phone may display an interface 104. As shown in (b) in Figure 1, the interface 104 includes a pop-up box 105, which includes a reminder message 105a and a cancel option 105b. The reminder message 105a is used to remind the user to turn off the flight mode to make a call, and the cancel option 105b is used to cancel the call and close the pop-up box 105. In response to the user's operation on the cancel option 105b, the mobile phone can close the pop-up box 105 and redisplay the Google TM The dial pad interface, the Google TM The dial pad interface may be the interface 106 shown in (c) of Figure 1. Comparing the interface 106 with the interface 101, it can be seen that the interface 106 does not include non-emergency numbers input by the user.

[0044] In one implementation, a user can turn off airplane mode. For example, the user can pull down the top of interface 106. In response to the user pulling down the top of interface 106, the phone may display a pull-down notification bar 107. As shown in FIG2(a), pull-down notification bar 107 includes icons for options such as mute, Bluetooth, and airplane mode 108. The airplane mode icon 108 indicates that airplane mode is on. The phone may receive a user's action on airplane mode 108 and, in response, turn airplane mode off. Furthermore, as shown in FIG2(b), the phone may also update the airplane mode icon 108 to indicate that airplane mode is off. The user can then close pull-down notification bar 107 (e.g., by swiping up on it) and redial the call. For example, in response to the user closing pull-down notification bar 107, the phone may redisplay the dial pad interface. For example, the dial pad interface may be interface 109 shown in FIG2(c), which allows the user to redial the number. The icon 110 in the interface 109 is used to indicate that the mobile phone has been connected to the operator's network, that is, the flight mode of the mobile phone has been turned off.

[0045] It can be seen that in the above scenario, if the user turns off the flight mode and redials the call, he or she needs to go through at least four steps: closing the pop-up window 105, entering the entrance to set the flight mode (for example, pulling down the notification bar 107), turning off the flight mode, and returning to the dialing interface. The operation is relatively cumbersome.

[0046] In view of this, an embodiment of the present application provides an interface display method. When a terminal device is in airplane mode and receives a user's call to a non-emergency number, a first pop-up window can be displayed. This first pop-up window includes a close option. In response to the user's operation of closing the close option, the terminal device can directly close airplane mode so that the user can continue the call operation. This embodiment of the present application directly closes airplane mode through this close option, thereby simplifying user operations and improving the user experience.

[0047] It should be noted that the terminal device provided in the embodiment of the present application can be a mobile phone, a tablet computer, a computer, a laptop computer, a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, a vehicle-mounted device, a smart home device and / or a smart city device, etc. The embodiment of the present application does not impose any special restrictions on the specific type of the terminal device.

[0048] FIG3 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. As shown in FIG3, the terminal device 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 194, and a subscriber identification module (SIM) card interface 195, etc.

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

[0050] The controller can be the nerve center and command center of the terminal device. The controller can generate operation control signals based on instruction opcodes and timing signals to complete the control of instruction fetching and execution.

[0051] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

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

[0053] It is understood that the interface connection relationship between the modules illustrated in this embodiment is only for illustrative purposes and does not constitute a structural limitation on the terminal device. In other embodiments, the terminal device may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0054] The charging management module 140 is used to receive charging input from a charger. The charger can be a wireless charger or a wired charger. While charging the battery 142, the charging management module 140 can also power the terminal device through the power management module 141.

[0055] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160. In some embodiments, the power management module 141 and the charging management module 140 can also be provided in the same device.

[0056] The wireless communication function of the terminal device can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor. In some embodiments, antenna 1 and mobile communication module 150 of the terminal device are coupled, and antenna 2 and wireless communication module 160 are coupled, so that the terminal device can communicate with the network and other devices through wireless communication technology.

[0057] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the terminal device can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0058] Mobile communication module 150 can provide wireless communication solutions for terminal devices, including 2G / 3G / 4G / 5G. It can include at least one filter, switch, power amplifier, and low-noise amplifier (LNA). Mobile communication module 150 receives electromagnetic waves from antenna 1, filters and amplifies the received electromagnetic waves, and transmits them to the modem processor for demodulation.

[0059] The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0060] The wireless communication module 160 can provide wireless communication solutions applied to terminal devices, including WLAN (such as wireless fidelity, Wi-Fi network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication technology (NFC), infrared technology (IR), etc.

[0061] Wireless communication module 160 can be one or more devices that integrate at least one communication processing module. Wireless communication module 160 receives electromagnetic waves via antenna 2, frequency-modulates and filters the electromagnetic wave signals, and transmits the processed signals to processor 110. Wireless communication module 160 can also receive signals to be transmitted from processor 110, frequency-modulate and amplify them, and then convert them into electromagnetic waves for radiation via antenna 2.

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

[0063] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel.

[0064] The terminal device can implement a camera function through an ISP, camera 193, video codec, GPU, display 194, and application processor. The ISP is responsible for processing data fed back by camera 193. Camera 193 is responsible for capturing still images or videos. In some embodiments, the terminal device may include one or N cameras 193, where N is a positive integer greater than 1.

[0065] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

[0066] The internal memory 121 can be used to store computer executable program code, which includes instructions. The processor 110 executes various functional applications and data processing of the terminal device by running the instructions stored in the internal memory 121. For example, in an embodiment of the present application, the processor 110 can execute instructions stored in the internal memory 121, and the internal memory 121 can include a program storage area and a data storage area.

[0067] The program storage area can store an operating system, at least one application required for a function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created during the use of the terminal device (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 can include a high-speed random access memory and a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0068] The terminal device can implement audio functions through the audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor, etc. For example, music playback, recording, etc. Buttons 190 include a power button, volume button, etc. Buttons 190 can be mechanical buttons. Or they can be touch buttons. Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts or for touch vibration feedback. Indicator 192 can be an indicator light that can be used to indicate charging status, power changes, messages, missed calls, notifications, etc. SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to and separated from the terminal device by inserting or removing it from the SIM card interface 195. The terminal device can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc.

[0069] Among them, the above-mentioned sensor module 180 may include sensors such as pressure sensor, gyroscope sensor, air pressure sensor, magnetic sensor, acceleration sensor, distance sensor, proximity light sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor and bone conduction sensor.

[0070] It should be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the terminal device. In other embodiments, the terminal device may include more or fewer components than shown, or may combine or separate certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0071] The software system of the terminal device can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. Here, the software structure of the terminal device is exemplified.

[0072] The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through interfaces. In some embodiments, the terminal device may include an application layer, an application framework layer, and a hardware abstraction layer (HAL). It should be noted that the embodiments of the present application are used as examples to illustrate that in different operating systems (such as Android TM system, IOS system, etc.), as long as the functions implemented by each functional module are similar to the embodiments of the present application, the solution of the present application can also be implemented.

[0073] The application layer can include a range of applications. As shown in Figure 4, the application layer can include applications such as a dialer, a telecom service, and a teleservice. Optionally, the application layer can also include settings, a gallery, a calendar, and a call application, which are not limited in this application.

[0074] Among them, the dial pad is an application with dialing, calling, and contact functions. Users can use this application to dial, call, manage contacts, and perform other operations.

[0075] The call management service is used to manage calls (also called calls), such as caller ID, answering calls, hanging up calls, etc.

[0076] The call service can interact with the HAL layer to implement basic call functions. The call service can also interact with the call management service to receive dial requests initiated by the dial pad through the call management service, or send incoming call information reported by the underlying modem to the dial pad through the call management service.

[0077] The application framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The application framework layer includes predefined functions. For example, it may include a telecom framework and a teleservice framework. The telecom framework provides services and interfaces related to call management, while the teleservice framework provides interfaces and services related to call services.

[0078] The HAL layer encapsulates the Linux kernel driver, providing an interface to the upper layer and shielding the implementation details of the underlying hardware. In an embodiment of the present application, the HAL layer may include a radio interface layer (RIL). The RIL is an abstract layer between the call service framework and the modem, and can be responsible for reliable data transmission, managing the response between the call service framework and the modem, controlling the modem's driver, and transmitting information and instructions actively reported by the modem.

[0079] The hardware layer includes a modem, which is used to implement functions such as making calls and surfing the Internet.

[0080] The following uses a mobile phone as an example to illustrate the interface display method provided in the embodiment of the present application.

[0081] In an optional embodiment, the mobile phone can display a dialing interface (also referred to as a first interface), which is an interface of a dialing application (also referred to as a dial pad). The dialing interface includes a dial button and a target number input by the user.

[0082] In response to a user clicking a dial button, if the target number is a non-emergency number, the terminal device is in airplane mode, and the dialing application is a preset application, a first pop-up window is displayed, the first pop-up window including a first option that can be used to turn off airplane mode.

[0083] For example, the dialing interface may be the interface 501 shown in FIG5(a), which may be a Google TMThe dialer (i.e., dialer application) interface. Additionally, icon 502 (also referred to as the first icon) in interface 501 indicates that the phone is in airplane mode. Interface 501 also includes a dial button 503, a non-emergency number for user input (e.g., 152****0000), and a dial pad for user number input. In response to the user's operation on dial button 503, the phone may display interface 504 (also referred to as the second interface). As shown in FIG5(b), interface 504 includes a pop-up window 505 (i.e., the first pop-up window), which includes a reminder message 505a, a cancel option 505b, and a close option 505c (i.e., the first option). The user can turn off airplane mode by clicking on close option 505c. In response to the user clicking on close option 505c, interface 506 (also referred to as the third interface) is displayed. As shown in FIG5(c), interface 506 includes an icon 507, a dial pad 508, and dial button 503. Icon 507 indicates that the phone is connected to the carrier's network. Interface 506 does not include icon 502, indicating that the phone has turned off airplane mode (not in airplane mode). The user can re-enter the target number via dial pad 508 and press dial button 503 to call the target number. If the user clicks on the close option 505c, the phone will turn off airplane mode.

[0084] Optionally, in response to the user's operation on the off option 505c, the mobile phone turns off the airplane mode and displays the interface 601 shown in (a) of Figure 6. The difference between the interface 601 and the interface 506 is that the interface 601 also includes the non-emergency number in the interface 501, so that the user can call directly without re-entering the number, simplifying the user's dialing operation.

[0085] Optionally, in response to the user selecting the off option 505c, the phone turns off airplane mode and calls the non-emergency number previously entered by the user. Furthermore, the phone may display interface 602 shown in FIG6(b), indicating that the phone is calling the non-emergency number entered by the user. This method eliminates the need for the user to re-enter the number and redial, making it simpler and more convenient.

[0086] It should be noted that after the mobile phone detects the user's operation on the close option 505c, it can also display other interfaces. There is no specific limitation here, as long as the mobile phone can turn off the airplane mode in response to the user's operation on the close option 505c.

[0087] In another optional embodiment, if the mobile phone receives an operation from the user to turn on the airplane mode while a call is in progress, the mobile phone may also display a first pop-up window, where the call is between the local number and a non-emergency number.

[0088] For example, as shown in FIG7 (a), the mobile phone may display interface 701, which indicates that the mobile phone is calling a target number (e.g., 152****0000). Optionally, interface 701 may also include icons for options such as recording, waiting, adding, and hanging up. In response to a user pulling down on the top of interface 701, the mobile phone may display a pull-down notification bar 702. As shown in FIG7 (b), pull-down notification bar 702 includes icons for options such as mute, Bluetooth, and airplane mode 703. The airplane mode icon 703 indicates that airplane mode is not enabled on the mobile phone. In response to a user's operation on the airplane mode icon 703, the mobile phone may enable airplane mode, hang up the call, and display interface 704. As shown in FIG7 (c), interface 704 is the interface of a dial pad application and also includes a pop-up window 705 (i.e., the first pop-up window) containing a reminder message 705a, a cancel option 705b, and a close option 705c. In response to the user clicking the close option 705c, the mobile phone turns off the airplane mode.

[0089] It can be seen that the interface display method provided in the embodiment of the present application can be applied to dialing scenarios and call scenarios. The following will illustrate the specific implementation methods of the interface display method provided in the embodiment of the present application in dialing scenarios and call scenarios with reference to the accompanying drawings.

[0090] FIG8 is a flow chart of an interface display method provided in an embodiment of the present application. The interface display method can be executed by the terminal device shown in FIG3 , and specifically illustrates a specific implementation method in the dialing scenario shown in FIG5 . As shown in FIG8 , the interface display method includes:

[0091] S801: In response to a user's dialing operation, the dial pad sends a dialing request to a telecom (call management) service.

[0092] The dial request carries the target number called by the user.

[0093] Illustratively, the dialing operation of the user may be a click operation of the user on the dial button 503 in FIG. 5 ( a ).

[0094] It should be noted that, in the embodiment of the present application, the dial pad can implement the transmission of the dial request by function calling.

[0095] S802: The telecom service adds a new call object and records the status of the call object.

[0096] In response to a dial request, the telecom service can create a new call object (i.e., a call object). A new call object is created to add a new call. The call object has the ability to manage a call, including answering, rejecting, holding, and hanging up. The call object's status can include the call state, such as dialing, not connected, connected, or hung up. The call object's status also includes whether to notify the UI refresh and whether the connection is established.

[0097] Optionally, the telecom service may also assign a call ID to the call object to facilitate management of the state of the call object.

[0098] S803: The telecom service sends a command to the dial pad to create a call interface.

[0099] The instruction to create a call interface includes the target number and call status, which is used to notify the dialer to create the call interface. Optionally, the instruction to create a call interface may also include a call ID. In an optional embodiment, the telecom service may notify the dialer to create the call interface through the onSuccessfulOutgoingCall() function.

[0100] S804: The dial pad creates a call interface and displays the call interface.

[0101] In response to receiving the instruction to create a call interface, the dial pad can create a call interface according to the target number and the call status and display the call interface. The call interface is used to indicate that the number called by the terminal device is the target number and the call status is dialing.

[0102] S805: The telecom service sends a request to the teleservice (call service) to initiate a call.

[0103] The call initiation request carries a target number for instructing the teleservice to call the target number. In an optional implementation, the telecom service may pass the call initiation request to the teleservice via a placeoutgoingcall() function.

[0104] It should be noted that the timing between S803 to S804 and S805 is independent of each other, that is, S803 to S804 can be executed before S805, or after S805, or synchronously with S805, and no specific limitation is made here.

[0105] In response to receiving a request to initiate a call, the teleservice may create a connection object so that the teleservice can send a dialing instruction to the modem through the RIL, causing the modem to call the target number. In this embodiment of the present application, the process of the teleservice creating the connection object may include S806 to S809. S806 is used to determine whether the connection object can be created, and S807 to S809 are used to describe the process of creating a disconnection reason (DisconnectCause) if the connection object creation fails. S806 to S809 will be described separately below.

[0106] S806, teleservice determines whether the target number is an emergency number and whether the terminal device is in flight mode.

[0107] Among them, emergency numbers are some emergency rescue telephone numbers set up to facilitate the public to respond to some emergency situations, such as 110, 119, 120, etc. Flight mode is a mode of a terminal device. When the terminal device turns on flight mode, it will not actively send paging signals to the base station and will not respond to the user's dialing request. Among them, the terminal device turning on flight mode can be understood as the terminal device is in flight mode, and the terminal device not turning on (or off) flight mode can be understood as the terminal device is not in flight mode.

[0108] In an embodiment of the present application, teleservice can determine whether a connection object can be created by judging whether the target number is an emergency number and whether the terminal device is in flight mode.

[0109] If the target number is not an emergency number (or is a non-emergency number) and the terminal device is in airplane mode, TeleService fails to create the connection object. If the target number is an emergency number or the terminal device is not in airplane mode, TeleService successfully creates the connection object. TeleService can further send a dialing instruction to the modem through the call service framework and RIL, which carries the target number. In response to receiving the dialing instruction, the modem calls the target number.

[0110] Among them, the target number is an emergency number or the terminal device is not in flight mode, which may include three situations: (1) the target number is not an emergency number and the terminal device is not in flight mode; (2) the target number is an emergency number and the terminal device is not in flight mode; (3) the target number is an emergency number and the terminal device is in flight mode.

[0111] In an optional embodiment, emergency number information is pre-stored in the terminal device, including emergency numbers pre-configured on the terminal device and / or emergency numbers provided by the operator after the terminal device accesses the operator's network. Teleservice can determine whether the target number can be found in the emergency number information. If the teleservice can find the target number from the emergency number information, the target number can be determined to be an emergency number. If the teleservice cannot find the target number from the emergency number information, the target number can be determined to be a non-emergency number.

[0112] In addition, teleservice can also determine whether the terminal device has turned on flight mode based on the flight mode status information. For example, the flight mode status information may include "radio on" and "radio off". If the flight mode status information is "radio on", it means that the terminal device has not turned on flight mode; if the flight mode status information is "radio off", it means that the terminal device has turned on flight mode. In other embodiments, other information can also be used to represent "radio on" and "radio off". For example, "0" can be used to represent "radio off" and "1" can be used to represent "radio on", and no specific limitation is made here.

[0113] It should be noted that S806 indicates that the teleservice needs to determine whether the target number is an emergency number and whether the terminal device is in airplane mode. This does not restrict the order in which these two determinations are performed. For example, the teleservice may determine whether the target number is an emergency number and whether the terminal device is in airplane mode. Alternatively, the teleservice may first determine whether the target number is an emergency number and then determine whether airplane mode is enabled. Alternatively, the teleservice may first determine whether airplane mode is enabled and then determine whether the target number is an emergency number. This is not a specific limitation.

[0114] In the embodiment of the present application, if the target number is not an emergency number and the terminal device is in flight mode, teleservice may execute S807.

[0115] In the embodiment of the present application, if the target number is not an emergency number and the terminal device is in airplane mode, the teleservice fails to create the connection object. In the case of failure to create the connection object, the teleservice needs to further create a disconnection reason (DisconnectCause).

[0116] In the embodiment of the present application, the disconnection reason (DisconnectCause) includes a code (code) and a description (description).

[0117] The code (code) refers to the code of the disconnection reason, which is used to indicate the specific reason for the disconnection / failure to establish a connection. For example, the code can be any one of the codes such as "UNKOWN", "ERROR", "LOCAL", "RESTRICTED", etc. The code "UNKOWN" indicates that the connection is disconnected due to an unknown or unspecified reason; the code "ERROR" indicates that the connection is disconnected due to an error (such as a network problem); the code "LOCAL" indicates that the connection is disconnected due to an operation initiated by the local user (such as hanging up); the code "RESTRICTED" indicates that the connection is disconnected due to restrictions on making calls, such as dialing in airplane mode. Different codes can be represented by different values, for example, 0 represents "UNKOWN", 1 represents "ERROR", 2 represents "LOCAL", 8 represents "RESTRICTED", etc.

[0118] The description refers to a localized description displayed to the user to explain the disconnection, such as "Turn off airplane mode to call a phone number." In an embodiment of the present application, the terminal device can first set the description to a preset value, such as "Turn off airplane mode to call a phone number," so that the dialer can subsequently display a pop-up reminder based on the description.

[0119] Optionally, the disconnection reason (DisconnectCause) may also include information such as a label and a reason value. The label is a localized label displayed to the user to explain the disconnection, which can be displayed in the user interface. The reason value is the reason for the disconnection, such as "making a call in airplane mode."

[0120] In this embodiment of the present application, the process of creating a disconnection reason by TeleService may include S807 to S809. S807-S808 determine whether to create and display a first pop-up window, which reminds the user to turn off airplane mode to make a call and provides a quick way to turn off airplane mode. S809 describes how TeleService sets various information in the disconnection reason. S807-S809 are described separately below.

[0121] However, in practice, the teleservice may create a DisconnectCause not only when it determines that the target number is not an emergency number and the terminal device is in airplane mode, but also in many other situations. For example, the teleservice may disconnect and create a DisconnectCause in response to a network failure (i.e., the teleservice creates a DisconnectCause in response to determining a network failure); or disconnect and create a DisconnectCause in response to the user's hang-up action (i.e., the teleservice creates a DisconnectCause in response to the user's hang-up action).

[0122] And the first pop-up box in this application is required in the dial pad for Google TM The pop-up box is displayed only when the dial pad is on and the terminal device is in airplane mode. Therefore, when creating the disconnection reason, TeleService can first determine whether the conditions for displaying the first pop-up box are met.

[0123] S807, teleservice determines whether the dial pad is Google TM Check whether the dial pad and the terminal device are in airplane mode.

[0124] Among them, Google TM Although a pop-up box will be displayed on the dial pad when the target number is not an emergency number and the terminal device is in flight mode, the pop-up box does not include an option for the user to turn off flight mode, such as the pop-up box 105 in Figure 1.

[0125] In an optional implementation, teleservice can read the system configuration information to obtain the dial pad identifier, and use the dial pad identifier to determine whether the dial pad is Google TM Dial pad. For example, the dial pad may include Google TM Dial pad and manufacturer's own dial pad, including Google TM The dial pad identifier can be "1", and the manufacturer's self-developed dial pad identifier can be "0". If the dial pad identifier obtained by teleservice is "1", it can be determined that the dial pad is Google TM Dial pad; if the dial pad identifier obtained by teleservice is "0", it can be determined that the dial pad is not Google TM A dial pad (for example, a dial pad developed by a manufacturer).

[0126] In addition, the teleservice also needs to determine whether the terminal device is in flight mode. The process of determining whether the terminal device is in flight mode can be found in S806 and will not be described in detail here.

[0127] In the embodiment of the present application, if the dial pad is Google TM dial pad and the terminal device is in flight mode, teleservice can execute S808; if the dial pad is not Google TM If the dial pad or terminal device is not in airplane mode, teleservice can execute S809.

[0128] S808: Teleservice displays the first pop-up window on the call interface.

[0129] In response to determining that the dial pad is Google TM When the dial pad is on and airplane mode is enabled on the terminal device, TeleService displays a first pop-up window on the call screen. This first pop-up window includes a reminder message, a cancel option, and a close option. The reminder message prompts the user to turn off airplane mode to make the call, the close option turns off airplane mode, and the cancel option closes the first pop-up window.

[0130] For example, the first pop-up window may be the pop-up window 505 shown in (b) of FIG5 , the reminder information may be the reminder information 505a, the close option may be the close option 505c, and the cancel option may be the cancel option 505b. In response to the user clicking the close option 505c, the terminal device turns off the flight mode, for example, the flight mode status information may be set to "radio off". In response to the user clicking the cancel option 505b, the terminal device displays the Google TM The dial pad interface is, for example, the interface 106 shown in (c) of Figure 1. In addition, after the user clicks the cancel option 505b, the terminal device closes the pop-up box 505, that is, the pop-up box 505 is not displayed.

[0131] In an embodiment of the present application, the teleservice may display the first pop-up window based on a description of the disconnection reason. The reminder message on the first pop-up window may be a description of the disconnection reason, such as "turn off airplane mode to make a call."

[0132] S809: Teleservice sets the description in the disconnection reason to null.

[0133] That is, if the dial pad is Google TM If the dial pad is used and the terminal device turns on airplane mode, the terminal device can also set the description in the disconnection reason to be empty (null) to avoid the dial pad pop-up window reminding the user to turn off airplane mode again.

[0134] In an optional embodiment, if the dial pad is not Google TMIf the dialer or terminal device is not in airplane mode, TeleService may not reset the description in the disconnection reason. That is, it may keep the description in the disconnection reason as the default value, so that the dialer can pop up a reminder based on the description in the future.

[0135] Optionally, teleservice may set the reason value in the disconnection reason to POWER OFF (power interruption), where POWER OFF is used to indicate that the modem is in a powered-off state.

[0136] In an optional implementation, the disconnection cause (DisconnectCause) may be expressed in the form of [Code:()Label:()Description:()Reason:(radio off)]. For example, teleservice may create a DisconnectCause whose content is [Code:(RESTRICTED)Label:()Description:()Reason:(POWER OFF)], where the DisconnectCause indicates that the disconnection code is "RESTRICTED", the cause value is "POWER OFF", and both Label and Description are empty.

[0137] S810: teleservice sends a call status update instruction to telecom service.

[0138] The instruction for updating the call status includes the disconnection reason and the call ID.

[0139] S811: The telecom service updates the status of the call partner.

[0140] In response to receiving the connection response, the telecom service may update the status of the corresponding call object according to the disconnection reason and the call ID.

[0141] It should be noted that the telecom service can print a log after receiving a connection response, and the log can record the disconnection reason received by the telecom service.

[0142] S812, the telecom service sends the disconnection reason to the dialer.

[0143] In the embodiment of the present application, the telecom service may transmit the disconnection reason to the dial pad by calling back the dial pad.

[0144] S813, the dialer determines whether the code in the disconnection reason is a preset code and whether the description in the disconnection reason is empty.

[0145] Currently, Google TM The native logic of the dial pad is: when the code of the disconnection reason is "ERROR" or "RESTRICTED" and the description in the disconnection reason is not empty, a second pop-up box is displayed. The second pop-up box is, for example, the pop-up box 105 shown in (b) of Figure 1. In the embodiment of the present application, the preset code can be "ERROR" and "RESTRICTED".

[0146] That is, the dial pad determines whether to display the second pop-up box by judging whether the code in the disconnection reason is a preset code and whether the description in the disconnection reason is empty.

[0147] If the code in the disconnection reason is a preset code and the description in the disconnection reason is not empty, the dial pad displays a second pop-up window, which includes the description in the disconnection reason. For example, the second pop-up window can be the pop-up window 105 shown in Figure 1 (b), and the reminder information 105a in the pop-up window 105 can be the description in the disconnection reason.

[0148] If the code in the disconnection reason is not a preset code, or the description in the disconnection reason is empty, the dialer executes S814 (ie, the second pop-up box is not displayed).

[0149] S814, the dial pad does not display the second pop-up window.

[0150] In this embodiment of the present application, since the teleservice sets the description of the disconnection reason to be empty in S809, the dialer can determine that the description of the disconnection reason is empty in S814 and thus not display the second pop-up window. This can avoid the user experience caused by the terminal device displaying multiple pop-up windows.

[0151] FIG9 is a second flow chart of an interface display method provided in an embodiment of the present application. The interface display method can be executed by the terminal device shown in FIG3 , and specifically illustrates a specific implementation method in the call scenario shown in FIG7 . As shown in FIG9 , the interface display method includes:

[0152] S901 : In response to a user operation of turning on airplane mode, the configuration application sends a power-off instruction to a modem.

[0153] Exemplarily, the user's operation of turning on the airplane mode may be the user's operation on the airplane mode icon 703 in the pull-down notification bar 702 , or the user's operation of turning on the airplane mode in a settings application.

[0154] The configuration application may send a power-off instruction to the modem through the application framework layer and the RIL.

[0155] S902: The modem determines whether the terminal device is currently in a call.

[0156] In an optional implementation, the modem can determine whether there is a call object in the call list. If there is a call object in the call list, it means that the terminal device is currently in a call; if there is no call object in the call list, it means that the terminal device is not in a call.

[0157] If the terminal device is currently in a call, the modem may execute S903; if the terminal device is not currently in a call, the modem may be directly powered off.

[0158] S903: The modem hangs up the call and generates status change information.

[0159] The status change information includes a call ID and a hang-up reason. In the embodiment of the present application, the call is hung up because the airplane mode is turned on, and the hang-up reason can be set to "radio off".

[0160] S904: The modem sends status change information to the teleservice.

[0161] The modem may send status change information to the teleservice via the call service framework of the RIL and application framework layers.

[0162] S905, teleservice determines whether the dial pad is Google TM The dial pad and whether the terminal device is in airplane mode. In response to receiving the status change information, the teleservice can further create a disconnection reason (DisconnectCause). As mentioned above, many situations will cause the teleservice to create DisconnectCause, and the first pop-up box only needs to be displayed in specific scenarios. Therefore, the teleservice needs to determine whether the dial pad is Google TM Dial pad and determine whether the terminal device is in flight mode.

[0163] Among them, teleservice determines whether the dial pad is Google TMThe process of whether the dial pad and the terminal device are in flight mode can be found in S806 and S807, which will not be described in detail here.

[0164] S906: Teleservice displays the first pop-up window on the call interface.

[0165] S907: Teleservice sets the description in the disconnection reason to null.

[0166] S908: teleservice sends a call status update instruction to telecom service.

[0167] S909: The telecom service updates the status of the call partner.

[0168] S910, the telecom service sends the disconnection reason to the dialer.

[0169] S911: The dialer determines whether the code in the disconnection reason is a preset code and whether the description in the disconnection reason is empty.

[0170] S912, the dial pad does not display the second pop-up window.

[0171] In summary, in the embodiments of the present application, if a mobile phone receives a call from a user to a non-emergency number while in airplane mode, or if a mobile phone receives a call from a user to turn on airplane mode while on a call with a non-emergency number, the mobile phone may display a first pop-up window in response to the call. The first pop-up window includes a "off" option, which allows the user to quickly turn off airplane mode without having to access the settings app, pull-down menu, or other interfaces to turn off airplane mode. This simplifies user operations and improves the user experience.

[0172] The present application also provides a terminal device comprising a memory and one or more processors; wherein the memory is used to store computer program code, and the computer program code comprises computer instructions; when the computer instructions are executed by the processor, the terminal device performs the functions or steps of the above-described method embodiment. The structure of the terminal device can refer to the structure of the terminal device shown in Figure 3.

[0173] An embodiment of the present application also provides a chip system, as shown in Figure 10, which includes at least one processor 1001 and at least one interface circuit 1002. The processor 1001 and the interface circuit 1002 can be interconnected via lines. For example, the interface circuit 1002 can be used to receive signals from other devices (such as the memory of a terminal device). For another example, the interface circuit 1002 can be used to send signals to other devices (such as the processor 1001). Exemplarily, the interface circuit 1002 can read instructions stored in the memory and send the instructions to the processor 1001. When the instructions are executed by the processor 1001, the terminal device can execute the various steps in the above embodiments. Of course, the chip system can also include other discrete components, which is not specifically limited in the embodiment of the present application.

[0174] An embodiment of the present application also provides a computer storage medium, which includes computer instructions. When the computer instructions are executed on the above-mentioned terminal device, the terminal device executes each function or step executed by the mobile phone in the above-mentioned method embodiment.

[0175] An embodiment of the present application further provides a computer program product, which, when executed on a terminal device, enables the terminal device to execute the various functions or steps executed by the mobile phone in the above method embodiment.

[0176] It is understandable that the terminal device provided in the embodiment of the present application includes a hardware structure and / or software module for performing each function in order to realize the above functions. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiment disclosed herein, the embodiment of 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 a hardware or computer software driven hardware manner 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 exceed the scope of the embodiment of the present application.

[0177] The embodiment of the present application can divide the functional modules of the terminal device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing 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 embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0178] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0179] In the several embodiments provided in this 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 merely schematic. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, 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, which can be electrical, mechanical or other forms.

[0180] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0181] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0182] 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 and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0183] The above content is only a specific embodiment of this application, but the scope of protection of this application is not limited to this. Any changes or replacements within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. An interface display method, characterized in that: Applied to a terminal device, the method comprises: Displaying a first interface at a first time point, the first interface including a dial button and a first icon, the first icon indicating that the terminal device is in flight mode; In response to a user inputting a target number on the first interface, displaying the target number on the first interface, wherein the target number is a non-emergency number; In response to the user clicking the dial button on the first interface, displaying a second interface, the second interface including prompt information and a first option, the prompt information being used to prompt turning off the flight mode; After the user clicks the dial button, at a second time point, a description of the disconnection reason is obtained, the description of the disconnection reason is empty, between the first time point and the second time point, the terminal device is in flight mode, and only receives one operation of the user clicking the dial button, and the second time point is later than the first time point; In response to a user clicking on the first option of the second interface, a third interface is displayed, and the third interface does not include the first icon.

2. The method according to claim 1, characterized in that The third interface includes the target number and a second icon, and the second icon indicates that the terminal device is connected to the operator network.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: A reason value of the disconnection reason is acquired, where the reason value of the disconnection reason is POWER OFF.

4. The method according to any one of claims 1 to 3, characterized in that: The first interface is an interface of a dialing application, and in response to the user clicking the dialing button on the first interface, displaying the second interface includes: In response to the user clicking the dial button on the first interface, the second interface is displayed when the target number is a non-emergency number, the terminal device is in flight mode, and the dial application is a preset application.

5. The method according to any one of claims 1 to 4, characterized in that After displaying the second interface, the method further includes: Set the description in the disconnect reason to empty.

6. The method according to claim 5, characterized in that The step of displaying the second interface in response to the user clicking the dial button on the first interface comprises: In response to the user clicking the dial button on the first interface, creating a connection object; Based on the failure to create the connection object, generating the disconnection reason, the description of the disconnection reason including the prompt information; In a case where the dial-up application is a preset application, the second interface is displayed based on the description of the disconnection reason.

7. The method according to claim 6, characterized in that The failure to create the connection object is based on the target number being an emergency number and the terminal device being in airplane mode.

8. The method according to any one of claims 1 to 7, characterized in that: Because the description of the disconnection reason is empty, the terminal device does not display a reminder pop-up box, and the reminder pop-up box is a pop-up box of a preset application.

9. An interface display method, characterized in that: Applied to a terminal device, the method comprises: During a call on the terminal device, in response to receiving an operation by a user to turn on the flight mode, turning on the flight mode and ending the call; If the dialing application is a preset application, a first pop-up box is displayed, wherein the first pop-up box includes a first option; In response to the user clicking the first option, turning off the flight mode; After the first pop-up window is displayed, a disconnection reason is obtained, where the description in the disconnection reason is empty; In response to determining that the description in the disconnection reason is empty, not displaying the second pop-up box, and the second pop-up box does not include an option for turning off the airplane mode.

10. A terminal device, characterized in that: The terminal device comprises: a memory and one or more processors; the memory is coupled to the processor; The memory is used to store computer program code, and the computer program code includes computer instructions; when the computer instructions are executed by the processor, the terminal device executes the method as described in any one of claims 1-9.

11. A computer-readable storage medium, characterized in that: The method comprises computer instructions, which, when executed on a terminal device, cause the terminal device to execute the method according to any one of claims 1 to 9.

Images