Interface display method, electronic equipment and storage medium

Abstract

The embodiment of the invention relates to the technical field of terminals, in particular to an interface display method, electronic equipment and a storage medium. The method can be applied to the electronic equipment comprising a display screen. The method comprises the steps of displaying an interface of a first application on a first screen at a first time point; then, at a second time point, in response to a preset target operation, displaying a two-dimensional code of a second application on a second screen; next, at a third time point, in response to an event of ending the display of the second screen, the second screen is blank. Between the second point in time and the third point in time, the container node of the second screen is above the container node of the first screen. According to the embodiment of the invention, the container node of the first screen can be adjusted to be above the container node of the second screen when the second screen is black, so that the focus window can be timely switched to the first screen above the container node, the interface displayed by the first screen can respond to the operation of a user, the situation of abnormal interface response can be relieved, and the user experience is improved. The use experience of a user can be improved.

Description

[0001] This application is a divisional application. The application number of the original application is 202311215864.0, and the original application date is September 19, 2023. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The embodiments of the present application relate to the field of terminal technology, and in particular to an interface display method, an electronic device, and a storage medium. Background Art

[0003] As users' demands for electronic devices are diversified, foldable screen electronic devices with large screens and convenience are widely welcomed by users. The foldable screen of an electronic device can be folded to form at least two display areas. For example, the foldable screen can be folded along a folding edge or a folding axis to form a first screen display area and a second screen display area (hereinafter referred to as the first screen and the second screen). When the display screen is in the folded state, the display directions of the first screen and the second screen are opposite to each other.

[0004] When a user uses an electronic device with a display screen in a folded state, when the first screen and the second screen are used to display an interface, the electronic device has an abnormal interface response, and the user's experience is poor. Summary of the invention

[0005] The embodiments of the present application provide an interface display method, an electronic device, and a storage medium, which can adjust the container node of the first screen to be above the container node of the second screen when the second screen is black, so that the focus window can be switched to the first screen above the container node in a timely manner, so that the interface displayed on the first screen can respond to the user's operation, thereby alleviating the abnormal interface response 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, an interface display method is provided, which can be applied to an electronic device including a display screen (such as a mobile phone, a tablet computer, etc.); the display area of ​​the display screen includes a first screen and a second screen, the display screen of the electronic device is in a folded state, and the display directions of the first screen and the second screen are opposite. The above method includes: at a first time point, the electronic device displays the interface of the first application on the first screen. At a second time point, in response to a preset target operation (such as a back screen tapping operation), the QR code of the second application is displayed on the second screen; the second time point is later than the first time point. Between the first time point and the second time point, the second screen is in a black screen state, and the container node of the first screen is above the container node of the second screen; the container node of the first screen and the container node of the second screen are mounted on the root node. At a third time point, in response to an event of ending the display of the second screen, the second screen is black; the third time point is later than the second time point. Between the second time point and the third time point, the container node of the second screen is above the container node of the first screen, and the first screen displays the interface of the first application. After the third time point, the first screen displays the interface of the first application, and the container node of the first screen is above the container node of the second screen.

[0008] It can be understood that the container node of the first screen is above the container node of the second screen, which can also be expressed as the container node of the first screen is before the container node of the second screen, the container node of the first screen is before the container node of the second screen, etc. Also, since there is a positional relationship between the container nodes mounted on the root node, the container node of the first screen is above the container node of the second screen, which can be understood as the position order of the container node of the first screen is above the position order of the container node of the second screen.

[0009] In this method, the electronic device can adjust the container node of the first screen to be above the container node of the second screen when the second screen is black, so that the focus window can be switched to the first screen above the container node in time, so that the interface displayed on the first screen can respond to the user's operation, thereby alleviating the abnormal interface response and improving the user experience.

[0010] In a possible design of the first aspect, the method further includes: based on an event of ending display of the second screen, adjusting the container node of the second screen to the bottom.

[0011] In this design, the electronic device can adjust the container node of the second screen to the bottom based on the event of ending the display of the second screen; thus, the container node of the first screen can be located above the container node of the second screen. This can further alleviate the situation where the electronic device has abnormal interface response and improve the user experience.

[0012] In another possible design of the first aspect, between the second time point and the third time point, the container node of the second screen mounts the window node corresponding to the display task. The above-mentioned adjusting the container node of the second screen to the bottom includes: the electronic device removes the display task; and then, the electronic device adjusts the container node of the second screen to the bottom.

[0013] In another possible design of the first aspect, between the first time point and the second time point, the focus window is the window node mounted on the container node of the first screen; between the second time point and the third time point, the focus window is the window node mounted on the container node of the second screen. The above method also includes: at the third time point, based on the container node of the first screen being above the container node of the second screen, the update judgment condition of the focus window is passed, and the electronic device sets the window node mounted on the container node of the first screen as the focus window.

[0014] In this design, since the container node of the first screen is above the container node of the second screen, the result of the execution of the update judgment condition of the focus window by the electronic device will be passed; when the update judgment condition of the focus window passes, the electronic device can set the window node mounted on the container node of the first screen as the focus window. In this way, the focus window of the electronic device (the window node mounted on the container node of the first screen) can respond to the return operation. This can further alleviate the abnormal response of the electronic device interface and improve the user experience.

[0015] In another possible design of the first aspect, after the third time point, in response to the return operation, the electronic device performs an interface switch of the first application indicated by the return operation on the first screen based on the window node mounted on the container node of the first screen as the focus window.

[0016] Considering that the user can control the switching of the first application displayed on the first screen through the return operation on the electronic device. In this design, since the focus window of the electronic device is the window node mounted on the container node of the first screen, the electronic device can perform the interface switching of the first application indicated by the return operation on the first screen. In this way, the situation where the return operation triggered by the user on the electronic device is unresponsive on the first screen can be alleviated. Then, the situation where the electronic device interface responds abnormally can be further alleviated, and the user experience can be improved.

[0017] In another possible design of the first aspect, the interface of the first application is an e-book display interface of an e-book application, and the e-book display interface includes a current page of the e-book. The method further includes: after the third time point, in response to pressing the volume key, the electronic device turns the current page of the e-book displayed on the first screen based on the window node mounted by the container node of the first screen as the focus window.

[0018] Considering that users may turn pages by using the volume button of the electronic device when using an e-book, in this design, since the focus window of the electronic device is the window node mounted by the container node of the first screen, the mobile phone can turn the current page of the e-book displayed on the first screen in response to the user pressing the volume button.

[0019] In yet another possible design of the first aspect, the method may further include: based on an event of ending display of the second screen, adjusting the container node of the first screen to the top.

[0020] In another possible design of the first aspect, in response to a preset target operation, the electronic device displays a QR code of the second application on the second screen, including: in response to a preset target operation, the electronic device displays the QR code of the second application on the second screen, and displays the second screen display control on the first screen. In response to an event of ending the second screen display at a third time point, the second screen is blacked out, including: at the third time point, based on a removal operation for the second screen display control, the second screen is blacked out; after the third time point, the first screen does not display the second screen display control.

[0021] In this design, the user can control the opening or closing of the QR code displayed on the second screen through the controls displayed on the first screen, which can improve the user experience.

[0022] In another possible design of the first aspect, the electronic device responds to the event of ending the display of the second screen, and the second screen is black, including: the electronic device completes scanning the QR code of the second application, and the second screen is black. Or, the electronic device displays the QR code of the second application on the second screen for a time period exceeding a preset time period (e.g., 3 seconds, 5 seconds, 10 seconds), and the second screen is black.

[0023] In another possible design of the first aspect, the target operation includes an operation of tapping from the back of the first screen to the front of the first screen. In this design, the user can easily trigger the target operation on the electronic device, which can improve the user's experience.

[0024] In a second aspect, another interface display method is provided, which can be applied to an electronic device including a display screen (such as a mobile phone, a tablet computer, etc.); the display area of ​​the display screen includes a first screen and a second screen, the display screen of the electronic device is in a folded state, and the display directions of the first screen and the second screen are opposite. The method includes: at a fourth time point, the electronic device displays the interface of the third application on the first screen. At the fourth time point, the root node mounts the container node of the first screen. At a fifth time point, in response to a preset target operation, the electronic device displays a QR code of the fourth application on the second screen, and creates a container node of the second screen mounted on the root node. The fifth time point is later than the fourth time point. At a sixth time point, the electronic device responds to an event of ending the display of the second screen, the second screen is black, and the container node of the second screen is removed, and the sixth time point is later than the fifth time point. Between the fifth time point and the sixth time point, the container node of the second screen is above the container node of the first screen, and the first screen displays the interface of the third application. After the sixth time point, the first screen displays the interface of the third application.

[0025] In the above method, the electronic device can delete the container node of the second screen when the second screen is black, so that the focus window can be switched to the first screen above the container node in time, so that the interface displayed on the first screen can respond to the user's operation, thereby alleviating the abnormal interface response and improving the user experience.

[0026] In a third aspect, the present application provides an electronic device, comprising: a memory, one or more processors, and a Bluetooth module; the memory is coupled to the processor; wherein the memory stores computer program code, and the computer program code comprises computer instructions; when the computer instructions are executed by the processor, the electronic device executes the method provided by the above-mentioned first aspect and any possible design of the first aspect; or the electronic device executes the method provided by the above-mentioned second aspect and any possible design of the second aspect.

[0027] In a fourth aspect, the present application provides a computer-readable storage medium, which stores instructions. When the computer instructions are executed on an electronic device, the electronic device executes the method provided by the first aspect and any possible design of the first aspect; or the electronic device executes the method provided by the second aspect and any possible design of the second aspect.

[0028] In a fifth aspect, the present application provides a computer program product comprising instructions. When the computer program product is run on an electronic device, the electronic device can execute the method provided by the above-mentioned first aspect and any possible design of the first aspect; or the electronic device can execute the method provided by the above-mentioned second aspect and any possible design of the second aspect.

[0029] Among them, the technical effects brought about by any design method in the third to fifth 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

[0030] Figure 1A-Figure 1D A schematic diagram of a group of electronic devices provided in an embodiment of the present application;

[0031] Figure 2 A schematic diagram of a usage scenario provided for an embodiment of the present application;

[0032] Figure 3 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application;

[0033] Figure 4 A schematic diagram of the software structure of an electronic device provided in an embodiment of the present application;

[0034] Figure 5 A schematic diagram of an interface display method process provided in an embodiment of the present application;

[0035] Figure 6 A schematic diagram of a user graphical interface provided in an embodiment of the present application;

[0036] Figure 7 A schematic diagram of another interface display method process provided in an embodiment of the present application;

[0037] Figure 8 A schematic diagram of a tree node logical relationship provided in an embodiment of the present application;

[0038] Fig. 9 A schematic diagram of the position sequence of container nodes provided in an embodiment of the present application;

[0039] Fig.10 A schematic diagram of a tree node logical relationship change provided in an embodiment of the present application;

[0040] Fig.11 A schematic diagram of another tree node logical relationship change provided in an embodiment of the present application;

[0041] Fig. 12A and Fig. 12B A set of usage scenario diagrams;

[0042] Fig.13 A schematic diagram of another interface display method process provided in an embodiment of the present application;

[0043] Figures 14A-14G A schematic diagram of a group of user graphical interfaces provided in an embodiment of the present application;

[0044] Fig.15 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] 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. Among them, in the description of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the present application is only a kind of association relationship describing the associated objects, indicating that there can be three relationships, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. And, in the description of the embodiments of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or its similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same items or similar items with substantially the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit the difference.

[0046] Meanwhile, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0047] With the development of users' diversified demands for electronic devices, folding screen electronic devices with large screens and convenience are widely welcomed by users. The folding screen of an electronic device can be folded to form at least two display areas. For example, the folding screen can be folded along a folding edge or a folding axis to form a first screen display area and a second screen display area (hereinafter referred to as the first screen and the second screen). The folding methods of the folding screen on the electronic device can be divided into two categories. One is a folding screen that folds outward (referred to as the outward folding screen), and the other is a folding screen that folds inward (referred to as the inward folding screen). Among them, take the example that the folding screen can be folded to form the first screen and the second screen. After the outward folding screen is folded, the display direction of the first screen and the display direction of the second screen are opposite, and the display direction is the direction of the front of the screen. It can be understood that the display screen of the electronic device can be a flexible screen, and the above-mentioned first screen and second screen are two different display areas in the same flexible screen.

[0048] The electronic devices involved in the embodiments of the present application are mainly based on electronic devices with outward folding screens. For example, the outward folding screen can include two ways of vertical folding and horizontal folding. Vertical folding refers to folding the screen of the electronic device outward longitudinally. Horizontal folding refers to folding the screen of the electronic device outward laterally. The embodiments of the present application are introduced by taking the screen of the electronic device folding outward laterally as an example. It should be pointed out that the two ways of vertical folding and horizontal folding can be designed according to specific uses, and the embodiments of the present application do not impose any restrictions on this.

[0049] For example, Figure 1A FIG. 1 is a schematic diagram of the electronic device when the display screen is in an unfolded state (hereinafter referred to as the unfolded state). As can be seen, the electronic device includes a first screen and a second screen. In the unfolded state, the first screen and the second screen can form a relatively large display screen to display a user interface. The first screen and the second screen can be folded along a folding axis or a folding edge ( Figures 1A to 1D Folding is shown in the figure using a folding axis as an example).

[0050] For example, in Figure 1A In the embodiment, the second screen can be folded along the direction shown in 1a, and / or the first screen can be folded along the direction shown in 1b to obtain the following Figure 1B For example, in Figure 1B In the embodiment, the second screen can be folded further along the direction shown in 1c to obtain Figure 1C The folded state shown (may be simply referred to as the folded state). Figure 1C The second screen in the folded state is shown in FIG. The first screen in the folded state can be exemplarily referred to as Figure 1D .

[0051] Exemplarily, the first screen can be called the main screen of the electronic device, and the second screen can also be called the sub-screen of the electronic device; if the electronic device is in a folded state, the first screen and the second screen are facing away from each other, generally the first screen (main screen) faces the user, and the second screen faces away from the user; therefore, the second screen can also be called the back screen.

[0052] It is understandable that the above Figures 1A to 1D The above is only an example and does not constitute a limitation on the embodiments of the present application. For example, in some other embodiments, in addition to the first screen and the second screen, the electronic device may also include other display screens, which are not limited in the embodiments of the present application.

[0053] When a user uses an electronic device with a display screen in a folded state, when the first screen and the second screen are used to display an interface, the electronic device has an abnormal interface response, and the user's experience is poor.

[0054] For example, after a user uses the back screen light-up function of an electronic device, if the user performs a return operation on the first screen of the electronic device after the back screen light-up ends, that is, after the second screen goes black, the interface of the electronic device will become unresponsive. In other words, after the second screen of the electronic device goes dark, if the user does not want to view the interface of the first application displayed on the first screen of the mobile phone (such as the e-book reading interface of the e-book application); the user triggers a return operation on the electronic device (such as clicking the return button, swiping left to return, swiping right to return), the interface of the first screen of the electronic device will become unresponsive.

[0055] In view of this, an embodiment of the present application provides an interface display method, the method comprising: at a first time point, an electronic device displays an interface of a first application on a first screen. At a second time point, in response to a preset target operation (such as a back screen tapping operation), a QR code of a second application is displayed on the second screen; the second time point is later than the first time point. Between the first time point and the second time point, the second screen is in a black screen state, and the container node of the first screen is above the container node of the second screen; the container node of the first screen and the container node of the second screen are mounted on a root node. At a third time point, in response to an event that ends the display of the second screen, the second screen is black; the third time point is later than the second time point. Between the second time point and the third time point, the container node of the second screen is above the container node of the first screen, and the first screen displays the interface of the first application. After the third time point, the first screen displays the interface of the first application, and the container node of the first screen is above the container node of the second screen.

[0056] In this method, the electronic device can adjust the container node of the first screen to be above the container node of the second screen when the second screen is black, so that the focus window can be switched to the first screen above the container node in time, so that the interface displayed on the first screen can respond to the user's operation, thereby alleviating the abnormal interface response and improving the user experience.

[0057] It is understandable that the above focus window refers to the window that is displayed in the front of the electronic device and receives input events (e.g., return operations) for the window. Usually, there is only one focus window on the electronic device; these focus windows can be activity windows, dialog windows, etc.

[0058] For example, see Figure 2 The interface display method provided in the embodiment of the present application can be applied to the process in which the user uses the electronic device 100 with an outward folding screen in a folded state (such as using the electronic device 100 to read e-books, watch videos, chat, etc.). Among them, the electronic device 100 can be a mobile phone, a tablet computer, a wearable device, a smart screen, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), and other electronic devices with an outward folding screen; it can also be a vehicle-mounted computer, a vehicle-mounted computer, and other vehicle-mounted devices with an outward folding screen; it can also be some Internet of Things devices with an outward folding screen. The embodiment of the present application does not impose any restrictions on the product form of the electronic device.

[0059] Next, the hardware structure and software architecture of the electronic device 100 will be briefly introduced.

[0060] For example, see Figure 3The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor 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 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, and the like.

[0061] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine some components, or separate 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.

[0062] 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 processor (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), etc. Different processing units may be independent devices or integrated into one or more processors.

[0063] The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

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

[0065] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

[0066] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.

[0067] The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be set on the display screen 194. The electronic device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation is applied to the display screen 194, the electronic device 100 detects the intensity of the touch operation based on the pressure sensor 180A. The electronic device 100 can also calculate the position of the touch based on the detection signal of the pressure sensor 180A.

[0068] Exemplarily, the electronic device 100 may detect a left swipe (stroke) return operation / right swipe (stroke) return operation triggered by the user through the pressure sensor 180A.

[0069] The acceleration sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in all directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the electronic device and is applied to applications such as horizontal and vertical screen switching and pedometers.

[0070] Exemplarily, the electronic device 100 may detect a back-screen tapping operation triggered by a user through the acceleration sensor 180E.

[0071] The touch sensor 180K is also called a "touch panel". The touch sensor 180K can be set on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the electronic device 100, which is different from the position of the display screen 194.

[0072] Exemplarily, the electronic device 100 may detect a left-swipe (stroke) return operation / right-swipe (stroke) return operation triggered by the user through the touch sensor 180K.

[0073] As another example, the electronic device 100 may detect a user's touch operation on the display screen 194 through the touch sensor 180K, and provide a visual output related to the touch operation through the display screen 194 .

[0074] The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.

[0075] Exemplarily, the electronic device 100 can detect a button pressing operation triggered by the user through the button 190 .

[0076] The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. TM Taking the system as an example, the software structure of the electronic device 100 is illustrated. 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 software interfaces. For example, see Figure 4 , Android TM The system is divided into five layers, from top to bottom: application layer, application framework layer, Android runtime (Android TM runtime) and system libraries, hardware abstraction layer (HAL), and kernel layer.

[0077] Understandably, Figure 4 The software structure shown does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer architecture layers than shown in the figure, or combine some architecture layers, or split some architecture layers, etc. TM The system may also have other hierarchical division methods, for example, divided into: application layer, application framework layer, native layer, kernel layer. Also, different hierarchical division methods may be used for different operating systems, etc. Specifically, the operating system may be divided into different hierarchical levels according to actual usage.

[0078] The application layer can include a series of application packages. Figure 4 As shown, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

[0079] The application layer may also include a back screen service (tap tap service), which can be used to pull up the display of the target function code on the back screen of the electronic device. For its specific implementation, please refer to the relevant introduction below, which will not be described in detail here. Exemplarily, the target function code can be a QR code, a barcode, etc.; for example, the QR code can be a payment code, a boarding code, or any identity identification code, etc., which is not limited in the embodiment of the present application.

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

[0081] like Figure 4 As shown, the application framework layer can be divided into two parts: system services and media services.

[0082] The system server is a process that provides many subsystem services. Each subsystem service runs in the form of a thread, waiting for requests from applications, processing the requests, and returning the results to the applications. The above subsystem services include, for example, the window manager service (WMS), notification manager service (NMS), activity manager service (AMS), and input manager service (IMS).

[0083] WMS can be used for window management, window animation management, surface management, and as a transfer station for the input system. NMS enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. AMS can be used to start, switch, and schedule system components (for example, activities, services, content providers, and broadcast receivers) and manage and schedule application processes. IMS can be used to manage system input, such as touch screen input, key input, and sensor input. IMS takes events from input device nodes (such as the sensor modules and key modules described below), and assigns events to windows in WMS through interaction with WMS. The media server is responsible for the playback of audio and video, as well as the process of taking photos and recording videos.

[0084] Among them, IMS may include: input event center (eventhub) component, input event reading (inputreader) service component, input event distribution (inputdispatcher) service component, etc. The input event center can be used to receive input events sent by the hardware abstraction layer. The input event acquisition service can be used to obtain input events from the input event center and send the input events to the input event distribution service. The input event distribution service can be used to receive input events sent by the input event acquisition service and correspond the input events to the focus window. In this way, the WMS can obtain the input event corresponding to the focus window from the IMS. The input event can be assigned to the focus window for processing through the interaction between the WMS and the IMS.

[0085] Exemplarily, WMS can be used to manage the focus window and set the focus window in an input event flinger service component, wherein input flinger can include an input event dispatcher service component.

[0086] Android Runtime TM Android runtime includes core libraries and virtual machines. TM The runtime is responsible for scheduling and management of the Android system.

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

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

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

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

[0091] 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. The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis, and layer processing, etc. The 2D graphics engine is a drawing engine for 2D drawing.

[0092] The hardware abstraction layer is an abstract structure between the kernel layer and the upper layer. It is a package of the kernel layer driver to provide a unified interface to the upper layer. It makes it unnecessary for the upper layer application to know how the lower layer hardware works, thus shielding the implementation details of the lower layer.

[0093] The hardware abstraction layer can provide a standard interface to display the device hardware functions to the higher-level application framework layer. The hardware abstraction layer contains multiple library modules, each of which is an interface implemented for a specific type of hardware component. The library modules can include audio modules, Bluetooth modules, camera modules, sensor modules, key modules, etc. The sensor modules can include, for example, accelerometer modules, magnetic field modules, orientation modules, gyroscope modules, ambient light sensors, pressure sensors, temperature sensors, and proximity sensors. When the application framework layer requires access to the device hardware, the system will load the corresponding library module for the hardware component. Manufacturers can define interfaces in the hardware abstraction layer.

[0094] Exemplarily, the acceleration sensor module can be used to sense operations on the electronic device (eg, double-clicking the back screen). The button module can be used to sense operations on buttons on the electronic device (eg, pressing a button).

[0095] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver. The kernel layer can also include sensor driver, button driver, etc.

[0096] Exemplarily, the hardware of the electronic device, such as button 190, or touch sensor 180K, etc., detects the user's return operation. The hardware abstraction layer of the electronic device (such as the button module, sensor module, etc. in the hardware abstraction layer) generates an input event for the window based on the return operation, and sends the input event for the window to the IMS. Next, the input event distribution (inputdispatcher) service component in the IMS obtains the focus window saved in the inputflinger, and sends the input event for the window to the focus window. Alternatively, after the IMS receives the input event for the window, the input event distribution (inputdispatcher) service component in the IMS obtains the focus window saved in the inputflinger, and corresponds the input event for the window to the focus window. In this way, the WMS can obtain the input event for the window from the IMS and assign the input event for the window to the focus window.

[0097] Next, we will Figure 2 In the usage scenario shown, the electronic device 100 is an external folding screen mobile phone in a folded state as an example, and the interface display method provided by the embodiment of the present application is described in detail in conjunction with the accompanying drawings. For the convenience of description, hereinafter, the external folding screen mobile phone in a folded state may be referred to as a mobile phone, the first screen of the external folding screen mobile phone is referred to as the main screen, and the second screen of the external folding screen mobile phone is referred to as the back screen.

[0098] It should be pointed out that the interface display method provided in the embodiment of the present application can also be applied to other electronic devices, such as an inward-folding screen mobile phone, an outward-folding screen mobile phone in an unfolded state, and the like; specifically, it can be set according to actual usage needs, and the embodiment of the present application does not impose any restrictions on this.

[0099] For example, see Figure 5 The interface display method provided in the embodiment of the present application may include: steps S501-S507.

[0100] Optionally, in some embodiments, before step S501, the interface display method provided in the embodiment of the present application may further include step S500.

[0101] S500. The phone turns on the back screen service (tap tap service) function.

[0102] When using a mobile phone, if the user wants to conveniently present a QR code, the user can turn on the back screen service of the mobile phone and make relevant settings in the back screen service. After the back screen service function of the mobile phone is turned on, the user can control the mobile phone to display the QR code through some operations. Among them, the back screen service function can be understood as the mobile phone responding to a preset target operation (such as a back screen tapping operation) to display a target function code such as a QR code or barcode of a preset application on the back screen of the mobile phone. The above-mentioned QR code can be a payment code, a boarding code, or any identity identification code, etc. The following embodiments of this application will be introduced as an example in which the target function code is a QR code, and the embodiments of this application are not limited to this.

[0103] In some embodiments, the user can enable the back screen service function of the mobile phone through the setting interface of the mobile phone.

[0104] For example, see Figure 6 . The mobile phone displays a desktop 600; the user can click on the settings icon 601 in the desktop 600. In response to the user clicking on the settings icon 601, the mobile phone displays a settings menu interface 610. Next, the user clicks on the folding screen settings option 611 in the settings menu interface 610. In response to the user clicking on the folding screen settings option 611, the mobile phone displays a folding screen settings menu 620. The folding screen settings menu 620 may include a switch 621 corresponding to the "back screen service". Then, the user clicks on the switch 621. In response to the user clicking on the switch 621, the mobile phone displays a back screen display application submenu 633 in the folding screen settings menu 630. In the back screen display application submenu 633, related applications that support back screen display (such as AA applications, BB applications, CC applications, etc.) are displayed; as well as an "on / off" switch 631 and a "default application" switch 632 corresponding to each application. Among them, the "on / off" switch 631 can be used to turn on / off the function of displaying the QR code corresponding to the application. The "Default Application" switch 632 is used to turn on / off the function of displaying the QR code corresponding to the application by default. For applications with the "On / Off" switch 631 turned on, the mobile phone can display its corresponding QR code through the back screen service function. For applications with the "Default Application" switch 632 turned on, the corresponding QR code will be displayed by default (displayed first).

[0105] Among them, the above-mentioned related applications supporting back screen display can be understood as that the application has the function of displaying a QR code, or it can also be understood as that the application has a QR code display interface.

[0106] like Figure 6As shown, in the folding screen setting menu 630, the "on / off" switch 631 of the AA application and the BB application is on, and the "default application" switch 632 of the AA application is on. In other words, the back screen service function of the mobile phone can display the QR code corresponding to the AA application or the BB application; and the QR code corresponding to the AA application will be displayed by the mobile phone by default (for example, in response to the back screen tapping operation, the QR code corresponding to the AA application is directly displayed).

[0107] In some other embodiments, the user can also use the voice recognition function of the mobile phone to activate the back screen service function of the mobile phone.

[0108] For example, the user can wake up the voice recognition function of the mobile phone through the wake-up word of the mobile phone. After that, the user can turn on the back screen service function of the mobile phone through a voice command (such as "turn on the back screen service function").

[0109] It is understandable that in some other embodiments, the back screen service function on the mobile phone is set when the mobile phone leaves the factory and is in a normally open state. In other words, the user does not need to actively turn on the back screen service function on the mobile phone to use the back screen service function on the mobile phone.

[0110] S501. After the user's target operation, the sensor module sends a back-screen tap event to the back-screen service.

[0111] Among them, the above-mentioned target operation can be understood as a tapping operation of the user from the back (back) of the main screen of the mobile phone to the front (front) of the main screen. For example, the user taps the back screen of the mobile phone twice in a row, or it can be a tapping operation of the user on the back screen of the mobile phone, or it can be an operation of the user sliding after tapping the back screen of the mobile phone, etc. For example, the aforementioned two consecutive tapping operations can be two tapping operations within a preset time length. The preset time length can be 0.5 seconds, 1 second or 2 seconds, etc., and the embodiments of the present application do not limit this.

[0112] It is understandable that the above-mentioned target operation can be pre-set, and specifically can be any pre-set operation; for example, it can be a tapping, sliding or dragging on the back screen of the mobile phone and any combination thereof. The specific design can be based on actual usage needs, and the embodiments of the present application do not limit this. For ease of description, in the following embodiments of the present application, the technical solution provided by the embodiments of the present application will be introduced by taking the target operation being a user's two consecutive tapping operations on the back screen of the mobile phone (hereinafter referred to as the back screen tapping operation) as an example.

[0113] In some embodiments, the mobile phone can detect the back-screen tapping operation through an accelerometer. For example, the mobile phone can call the driver of the accelerometer through the system so that the accelerometer receives the back-screen tapping operation. After that, the mobile phone calls the sensor module of the hardware abstraction layer through the system, and identifies the back-screen tapping operation through the back-screen tapping (tap tap) algorithm to obtain a back-screen tapping event. Then, the sensor module sends the back-screen tapping event to the back-screen service.

[0114] S502. In response to receiving the back-screen tap event, the back-screen service calls the SDK of the target application to send a message to pull up the target QR code.

[0115] The target application may be a default application set by the user in the back screen display application submenu in the folding screen setting menu, such as the AA application described above. The target QR code may be a QR code of the target application, such as the QR code of the AA application described above.

[0116] It is understandable that a software development kit (SDK) can be a collection of development tools for creating application software for a software package, software framework, hardware platform or operating system. SDK can be an SDK used by an application program. SDK facilitates the creation of applications through a compiler, debugger or software framework. Alternatively, SDK can provide some files of application program interfaces for a certain programming language, or may also include complex hardware that can communicate with a certain embedded system. In an embodiment of the present application, the above-mentioned target QR code can be pulled up by calling the SDK of the above-mentioned target application.

[0117] Exemplarily, the back screen service may be provided through the SDK of the target application, and then a message for pulling up the target QR code may be sent to the target application through the interface of the SDK.

[0118] S503. The target application sends a message to the AMS to pull up the target QR code.

[0119] It is understandable that the target QR code may be a QR code of a target application, such as the payment QR code of the AA application. The target application may display the user interface of the target QR code on the back screen of the mobile phone by starting an application activity.

[0120] Exemplarily, the message of pulling up the target QR code may be carried by an intent parameter. The intent parameter specifies the activity to be started (hereinafter referred to as the target activity), that is, the intent parameter includes a data description of the target activity. AMS can create a corresponding application activity record by parsing the intent parameter, so that the target application can start the target activity.

[0121] As another example, the target QR code is required to be displayed on the back screen of the mobile phone. The message for pulling up the target QR code also carries the identification information of the back screen service (such as the application name or a preset unique number, etc.). Therefore, after receiving the message, the AMS can determine whether the information is related to the back screen service based on the identification information of the sender in the message. If so, adjust the display area associated with the target activity and set the display area of ​​the target activity to the back screen. As a result, when a window is subsequently created based on the target activity to display the target QR code, the display area of ​​the window is the back screen.

[0122] S504. The AMS sends a notification to start the target activity to the target application based on the message.

[0123] After AMS creates an application activity record based on the message of pulling up the target QR code, it can first determine whether the application process indicated by the application activity record (such as the process of the target application mentioned above) exists. If not, the target application process can be started first, and then a notification to start the target activity can be sent to the target application. If the target application process exists, a notification to start the target activity is directly sent to the target application.

[0124] S505. The target application starts the target activity based on the notification.

[0125] After the target application receives the notification, the target application creates an application activity thread (ActivityThread), thereby starting the target activity.

[0126] Exemplarily, the application activity thread can start the target Activity by calling functions such as onCreate() and onResume().

[0127] S506. The target application instructs the WMS to create a view tree for the back screen display window based on the target activity.

[0128] The target activity can draw a user interface based on the view tree of the back screen display window, so that the target QR code is displayed on the back screen of the mobile phone. For the convenience of the following description, the view tree of the back screen display window can be referred to as the back screen window. For the introduction of the back screen window, please refer to the following Figure 8 The corresponding description is not described in detail here.

[0129] In this way, after the target application instructs WMS to create a back screen window through the target activity, the target application can draw a user graphical interface in the back screen window and display the target QR code through the interface mapping service, display management service, etc. Specifically, it can be designed according to actual usage requirements, and the embodiment of the present application does not impose any restrictions on this.

[0130] In some embodiments, in step S506, the target service can also instruct the WMS to create a floating capsule window based on the target activity. The floating capsule window is used to display a back screen display control on the main screen of the mobile phone, and the back screen display control can be used to switch the QR code displayed on the back screen by the back screen service function. For example, the control can switch the QR code displayed on the back screen by the back screen service function by switching the above-mentioned target application (such as switching the target application AA to the target application BB).

[0131] Exemplarily, the target service may also send the target activity to the back screen service, and the back screen service instructs the WMS to create a floating capsule window based on the activity.

[0132] In some embodiments, see Figure 7 , the above step S506 may include steps S5061-S5063.

[0133] S5061. In response to receiving the target activity, the WMS determines whether there is a container node corresponding to the back screen window based on the target activity. If there is a container node corresponding to the back screen window, step S5063 is executed; if there is no container node corresponding to the back screen window, steps S5062-S5063 are executed.

[0134] Among them, the container node (display) can also be called a display container node. One container node corresponds to a real or virtual display device (display area); and is used to manage the window (window) under the display device (display area).

[0135] For ease of description, the container node corresponding to the back screen window may be referred to as the target container node in the following text. The target container node may be understood as the container node on which the back screen window is mounted. Specifically, the correspondence between the back screen window and the container node is recorded in the above target activitiy.

[0136] It can be understood that WMS can manage windows through hierarchical management. A window can also be called a window node, which has a parent node and several child nodes, and is used to manage elements in the interface displayed on the mobile phone display (such as text size, color, image transparency, image contrast, dynamic special effects, etc.). WMS manages windows through hierarchical management, which can improve the efficiency of WMS's management of windows. In some embodiments, a window can also be called a task display area. Among them, a task can be understood as a stack of multiple activities, and the activity at the top of the stack corresponds to the window and is displayed on the display of the mobile phone. In other words, a task and a window will have a corresponding relationship. Since the window is mounted on a container node, the task can also be mounted on a container node.

[0137] In some embodiments, the WMS may manage windows through a tree node structure, wherein the tree node structure may include: a root node (root), a container node (display), and a window (window).

[0138] Among them, the root node (root), which can also be called the root window display container (root window container), is the top-level part of the tree node structure. Root is mainly used to manage the container nodes (display) mounted below it; for example, managing the position order of the container nodes mounted below it (such as being at the top (top) position, or at the bottom (bottom) position), adding / deleting container nodes, etc. The container node, mounted on the root node (root), is used to accept the management of the root node (root) and manage the windows (window) mounted below it; for example, managing the position order of windows, adding / deleting windows, etc. It should be pointed out that the container node has a corresponding relationship with the display area on the mobile phone, such as a container node corresponds to a display area of ​​the mobile phone. For example, see Figure 8 , container node 0 (display0) and container node 1 (display1) are mounted under the root node; they correspond to the main screen and back screen of the mobile phone respectively. For example, display0 can correspond to the main screen, and display1 can correspond to the back screen.

[0139] It is understandable that for mobile phones with the back screen service function turned on, since the mobile phone needs to display on the back screen, in order to distinguish between the main screen and the back screen, the mobile phone will set container nodes (display) corresponding to the main screen and the back screen in WMS respectively. And by mounting different windows under the container nodes, it manages the display content on the main screen / back screen of the mobile phone (such as the interface displayed on the main screen / back screen, elements in the interface, etc.).

[0140] It should be pointed out that Figure 8 This is only a logical schematic diagram, which can be designed according to actual usage requirements, and the embodiments of the present application do not impose any limitations on this.

[0141] In a possible implementation, the container nodes may exist in the mobile phone in the form of an array. For example, see Fig. 9 , Fig. 9 The position order of display0 and display1 is shown in the order from top to bottom. As can be seen from the figure, display0 is at the top position, and display0 is above display1. In some other embodiments, the above "display0 is above display1" can also be expressed as display0 is before display1, display0 is before display1, and so on. It can be understood that if the order from top to bottom is modified to the order from bottom to top, then display0 is below display1; or, display0 is after display1, display0 is after display1, and so on. Specifically, it can be designed according to actual usage requirements, and this does not impose any restrictions on this.

[0142] See again Fig. 9 , display0 corresponds to index 0, and display1 corresponds to index 1. In some embodiments, the relationship between display0 and display1 can be determined by the size of the indexes corresponding to display0 and display1. Exemplarily, if index 0 is greater than index 1, it can be considered that display0 is above display1 in the order from top to bottom. And the above display0 is above display1, which can also be expressed as the position order of display0 is above display0.

[0143] Specifically, in step S5061, assuming that the container node corresponding to the back screen window is display1, the WMS can search under the root node (root) to see whether display1 exists, and if so, execute step S5063, and if not, execute steps S5062-S5063.

[0144] It is understandable that in the scenario of using the back screen service function for the first time, the target container node of the mobile phone may not exist. The scenario of using the back screen service function for the first time can be understood as the first time the back screen service function is used after the mobile phone is turned on, and the target QR code is displayed on the back screen of the mobile phone. Or, after the back screen service function was used last time, the mobile phone removed the target container node after the target QR code was displayed on the back screen of the mobile phone; then, when the back screen service function is used this time, the target container node of the mobile phone may also not exist.

[0145] S5062.WMS adds the target container node.

[0146] For example, assuming that the back screen window corresponds to display1, that is, the target container node is display1, the WMS can create a new display1 and mount display1 on the root node (root).

[0147] S5063.WMS creates a background screen window and mounts the background screen window on the target container node.

[0148] Exemplarily, the WMS may create a background screen window and mount the background screen window to display1.

[0149] Among them, the above-mentioned back screen display window may include Figure 8 Window D in the Figure 8 Specifically, the design can be performed according to actual use requirements, and the embodiment of the present application does not impose any limitation on this.

[0150] Exemplarily, assume that the back screen display window includes window D. Window D may correspond to the user interface of the target application, and the user interface includes the target QR code. For example, if the target QR code is an AA payment code, then window D corresponds to the AA payment code interface. Assume that the back screen display window includes window D and window E, window D corresponds to the user interface of the target application, and window E corresponds to an auxiliary interface, which is used to be displayed together with the user interface of the target application to improve the display effect of the user interface of the target application. Among them, the auxiliary interface can be the following Fig. 14B 404 of the description 4032 of the QR code of the second application, for details, see the following about Fig. 14B Related introduction of .

[0151] After WMS creates the back screen window, the target application can draw a graphical interface in the back screen window through the interface mapping service, display management service, etc., to display the above target QR code. In addition, the back screen service can also draw some graphical interfaces (such as the above auxiliary interface) in the back screen window to display the above target QR code on the mobile phone together to enhance the display effect of the target QR code. Specifically, it can be designed according to actual usage requirements, and the embodiments of this application do not impose any restrictions on this.

[0152] It is understandable that WMS will cooperate with IMS to maintain the focus window on the mobile phone. Specifically, WMS can update the window information through the updateInputFocusRequest process, and update the focus window information to inputflinger through the setFocusedWindow function. After that, IMS can send the input event to the focus window after receiving the input event.

[0153] Among them, inputflinger is the process used to manage input event distribution in IMS. Inputflinger includes input event distribution (inputdispatcher) service component. When input events appear on the mobile phone, they will be distributed to the corresponding focus window for processing via inputdispatcher. In other words, WMS is used to maintain the focus window in inputflinger.

[0154] Next, the maintenance process of the focus window in the inputflinger by the WMS during steps S501 to S506 is introduced.

[0155] In some embodiments, the WMS may determine the focus window by the position order of the windows; after the WMS determines the focus window, the WMS updates the focus window to the inputflinger. For example, the WMS may use the topmost window as the focus window.

[0156] For example, see Fig.10 , the figure shows the position sequence from left to right, from top to bottom. Fig.10As shown in part A, before step S501, it is assumed that display0 and display1 exist in WMS. display0 is the container node for the main screen, and display1 is the container node for the back screen. The interface is being displayed on the main screen of the mobile phone, and window A, window B, and window C are mounted under display0 in order from top to bottom; since the back screen of the mobile phone does not display the screen off state, no window is mounted under display1. WMS will set the topmost window under the root as the focus window (e.g., the window at the top position mounted under the container node at the top position is set as the focus window.) For example, set window A as the focus window.

[0157] Specifically, WMS obtains that window A is a window at the top position mounted under the container node (display0) at the top position. After that, WMS can update the window information by calling the updateInputFocusRequest process to update the focus window (such as window A) to inputflinger. In the updateInputFocusRequest process, WMS can execute the mDisplayContent.isOnTop() judgment condition. After the judgment condition passes, it executes the setFocusedWindow() function to update the focus window information to inputflinger; if the judgment condition does not pass, the process ends, that is, the focus window is not updated. Among them, the input parameter of the above judgment condition is the window identifier.

[0158] It is understandable that after the WMS determines the focus window, the WMS may also verify the focus window (by verifying the focus window according to the above judgment conditions), which may improve the accuracy of the focus window setting.

[0159] For example, the judgment condition of mDisplayContent.isOnTop() is as follows:

[0160] parent! = null&&parent.getTopChild() == this&&parent.isOnTop()Expression 1

[0161] In expression 1, "!" means logical negation, "&&" means logical AND, and "==" means judging whether the two ends of the equation are the same; "parent!=null" means judging whether the parent node is not empty. If the parent node is not empty, 1 is returned, and if the parent node is empty, 0 is returned. "this" means the identifier input in the judgment condition mDisplayContent.isOnTop(); "parent.getTopChild()" is a function for getting the child node at the top position under the parent node; "parent.isOnTop()" means judging whether the parent node is at the top. Specifically, you can execute "parent!=null&&parent.getTopChild()==this" on its parent node to judge whether its parent node is at the top. It can be understood that the above parent node and child node can be understood as the relative relationship between mounting and being mounted. For example, the parent node of window A is display0, and window A is the child node of display0.

[0162] For example, WMS executes mDisplayContent.isOnTop(window a) to determine whether window A meets the determination condition; wherein "window a" is the identifier of window A.

[0163] When WMS executes mDisplayContent.isOnTop(window a), based on the priority of the operators in the expression, WMS first executes "parent.getTopChild()==this". Since the child node at the top position under the parent node of window A is window A, "parent.getTopChild(window a)" outputs window A, and "this" is "window a". The value of "parent.getTopChild(window a)==this" is 1. Next, since window A has a parent node such as display0, the value of "parent!=null" is 1. Then, WMS executes "parent.isOnTop(window a)" to determine whether the parent node display0 of window A is at the top.

[0164] During the process of WMS executing "parent.isOnTop(window a)", WMS executes "parent.getTopChild(Display0)==this", where "Display_0" is the identifier of display0; at this time, "this" is "Display_0", and since the child node at the top position under the parent node of display0 is display0, the output of "parent.getTopChild(Display_0)" is display0, that is, the value of "parent.getTopChild(Display_0)==this" is 1. Then, WMS executes "parent!=null", and since the parent node of display0 is not null, the value of "parent!=null" is 1. Therefore, the execution result of WMS executing "parent.isOnTop(window a)" is 1, that is, the execution result of WMS executing mDisplayContent.isOnTop(window a) is 1&&1&&1, and its execution result is 1, and the judgment condition is passed.

[0165] After WMS executes mDisplayContent.isOnTop(window a) and determines that window A meets the judgment conditions, WMS executes the setFocusedWindow(window a) function and updates the focus window to window A in inputflinger.

[0166] See again Fig.10 ,like Fig.10 As shown in part B of FIG. 5 , after step S505, since WMS creates a back screen window ( Fig.10 In the figure, the mobile phone displays a QR code on the back screen; WMS adjusts the position order of the container node and the window. WMS can adjust the focus window, such as by calling the updateInputFocusRequest process to update the window information and update the focus window (such as window D) to inputflinger.

[0167] Exemplarily, after the WMS passes the execution judgment condition mDisplayContent.isOnTop(window d), it updates the focus window to window D in inputflinger through setFocusedWindow(window d). Wherein, "window d" is the identifier of window D. Specifically, the process of WMS executing the judgment condition mDisplayContent.isOnTop(window d) can be seen above, and the description of WMS executing the judgment condition mDisplayContent.isOnTop(window a) is not repeated here.

[0168] Next, after the mobile phone executes step S506, the mobile phone executes step S507.

[0169] S507. In response to the event of ending the back screen display, the back screen service calls the WMS to remove the back screen window.

[0170] The event of ending the back screen display can also be called the back screen end event, which is used to indicate that the mobile phone ends the back screen service function and the back screen of the mobile phone stops displaying the target QR code. The back screen end event can be sent to the back screen service by the target application, or generated by the back screen service, or sent to the back screen service by other modules in the mobile phone such as the timer module; it can be specifically designed according to actual usage needs, and the embodiments of the present application do not impose any restrictions on this.

[0171] In some embodiments, after the target QR code is scanned, the target application sends a back screen end event to the back screen service.

[0172] Exemplarily, after the target QR code is scanned, the target application can send a back screen end event to the back screen service to notify the back screen service that the scanning of the target QR code displayed on the back screen of the mobile phone is completed.

[0173] In some further embodiments, after the target QR code display times out, the timer module generates and sends a back screen end event to the back screen service.

[0174] Exemplarily, after WMS successfully creates the back screen window, WMS can start a timer whose timing period can be a preset timing period (such as 5 seconds, 10 seconds, etc.). After the timer reaches the timing period, the timer can send a back screen end event to WMS.

[0175] In some solutions, in response to the event of ending the back screen display, the back screen service can directly remove the back screen window through WMS. In this way, since the back screen window is removed, the mobile phone will stop displaying the target QR code on the back screen, and the back screen will be turned off.

[0176] For example, see Fig.11 In response to the event that the back screen ends display, the back screen service sends a notification to remove the back screen window to WMS. WMS receives the notification and removes each task corresponding to the back screen window through the removeImmediately() function.

[0177] After WMS removes the back screen window, WMS will determine and update the focus window again because the window in WMS has changed. WMS will take the top window under root as the focus window. Fig.11As can be seen in the figure, since the container node at the top position is a mounted window, WMS can set the window at the top position that is mounted under the container node behind the container node at the top position as the focus window. For example, window A is set as the focus window.

[0178] Exemplarily, WMS can update the window information through the updateInputFocusRequest process, and update the focus window to window A in the inputflinger. In the updateInputFocusRequest process, WMS can execute the mDisplayContent.isOnTop(window a) judgment condition. If the judgment condition passes, WMS executes the setFocusedWindow(window a) function to update the focus window information to the inputflinger; if the judgment condition does not pass, the updateInputFocusRequest process ends, and WMS does not update the focus window. Among them, the mDisplayContent.isOnTop() judgment condition can refer to the above expression 1.

[0179] For example, when WMS executes "parent.isOnTop()" in the judgment condition of mDisplayContent.isOnTop(window a), because the parent node of window A, display0, is not the container node at the top of the root node, the container node at the top of the root node is display1. This will cause the value of "parent.getTopChild(Display_0)==this" to be 0, resulting in the execution result of the judgment condition being 1&&1&&0; the judgment condition fails. WMS does not update the focus window to inputflinger, that is, window A.

[0180] That is to say, the focus window in inputflinger is still window D updated by WMS before step S507. In this case, if the functional module located in the hardware abstraction layer of the mobile phone (such as button module, sensor module, etc.) generates an input event for the window in response to the user's return operation. Next, the functional module located in the hardware abstraction layer of the mobile phone (such as button module, sensor module, etc.) sends the input event for the window to IMS. Since the focus window in the inputflinger of ISM is window D, but window D in WMS has been removed, this will lead to unreasonable focus window setting (WMS failed to update the focus window to window A in the inputflinger of IMS). Then, the input event for the window fails to be sent to the focus window. This will cause the input event for the window to be unresponsive on the mobile phone, which will affect the user experience.

[0181] Among them, the above-mentioned input events for the window may include: return operation (such as clicking the back button operation, swiping left to return operation, swiping right to return operation, etc.), key operation (such as pressing the volume increase button operation, pressing the volume decrease button operation, etc.).

[0182] For example, see Fig. 12A , suppose that after WMS removes the back screen window and the back screen of the mobile phone turns off, the user triggers a return operation on the mobile phone (such as clicking the back button, swiping left to return, or swiping right to return). The user controls the mobile phone to switch the currently displayed page (such as the e-book display page) to display other pages (such as the mobile phone desktop) through the return operation; the IMS of the mobile phone will receive the return operation sent by the key module. And pass the return operation to the focus window in the inputflinger of IMS. Based on the above Fig.11 From the corresponding description, we can see that WMS has not updated the focus window to inputflinger, which is window A. The focus window in IMS's inputflinger is still window D. IMS will distribute the return operation to window D in WMS. However, since window D does not exist in WMS, window D is removed by WMS. Then the return operation cannot be passed to the focus window. Then, the mobile phone cannot respond to the return operation and the mobile phone becomes unresponsive.

[0183] It is understandable that if the user triggers the volume button operation on the mobile phone, the mobile phone will also perform the above Fig. 12A The corresponding process is similar to the process, and the mobile phone will also be unresponsive. This will reduce the user experience.

[0184] Therefore, in other technical solutions provided by the embodiments of the present application, after WMS removes the back screen window and the back screen of the mobile phone is turned off, WMS can adjust the position order of the container nodes, so that after WMS removes the back screen window, WMS can successfully update the focus window to the inputflinger of IMS. Then, the focus window can receive input events for the window, and the input events for the window will generate a response on the mobile phone, which can improve the user experience.

[0185] For example, see Fig. 12B After WMS removes the back screen window and the back screen of the mobile phone goes off, WMS adjusts the position order of the container nodes (e.g., adjusts the container node corresponding to the back screen window to the bottom). The user triggers the return operation on the mobile phone. The user controls the mobile phone to switch the currently displayed page (e.g., the e-book display page) to display other pages (e.g., the desktop of the mobile phone) through the return operation; the IMS of the mobile phone will receive the return operation sent by the key module. And pass the return operation to the focus window in the inputflinger of IMS. Because WMS adjusts the position order of the container nodes, so that WMS can update the focus window to window A in the inputflinger, the focus window in the inputflinger of IMS is window A. IMS will distribute the return operation to window A. In this way, window A will receive the return operation, and the mobile phone can respond to the return operation and display the desktop of the mobile phone.

[0186] Alternatively, after WMS removes the back screen window and the back screen of the mobile phone goes out, WMS adjusts the position order of the container nodes (e.g., adjusts the container node corresponding to the back screen window to the bottom). The user triggers the operation of pressing the volume button on the mobile phone, and the user controls the mobile phone to switch the page displayed in the e-book by pressing the volume button (e.g., switching the current page to the next page); the IMS of the mobile phone will receive the operation of pressing the volume button sent by the button module. And pass the operation to the focus window in the inputflinger of IMS. Because WMS adjusts the position order of the container nodes, so that WMS can update the focus window to window A in the inputflinger, the focus window in the inputflinger of IMS is window A. IMS will distribute the return operation to window A. In this way, window A will receive the operation of pressing the volume button, and the mobile phone can respond to the operation and turn the e-book page displayed on the main screen.

[0187] In some embodiments, see Fig.13 , the above step S507 may include steps S5070-S5073, and step S5074A.

[0188] S5070. In response to the event of ending the back screen display, the back screen service sends a message to the WMS to remove the back screen window.

[0189] S5071. WMS receives the message and obtains the identifier of the target container node.

[0190] Exemplarily, the WMS may obtain the identifier of the target container node through the getDisplayContentOrCreate function.

[0191] For example, the WMS may obtain the identifier of the target container node (eg, Display_1) through getDisplayContentOrCreate(window d).

[0192] S5072.WMS creates a back-screen window list, obtains the ID of each task under the target container node through the ID of the target container node, and adds the ID of each task to the above-mentioned back-screen window list.

[0193] For example, WMS uses the displayContent.forAllRootTasks function to mount the identifier of each task on the target container node, and adds the identifier of each task to the background screen window list.

[0194] S5073.WMS traverses the task identifiers in the back screen window list and removes the traversed identifiers.

[0195] Exemplarily, the WMS can remove the traversed identifier through the removeImmediately function.

[0196] For example, WMS can search for the identifier of the window node from the back screen window list, use the re moveImmediately function on the identifier obtained by the search, and remove the identifier using the removeImmediately function from the list until the back screen window list is empty, that is, the back screen window list does not include the window node identifier.

[0197] It is understandable that for a task mounted under a window node, if the task is removed, the window node is also removed. Therefore, in some embodiments, the back screen window can be removed by a task.

[0198] S5074A.WMS moves the position of the target container node to the bottom in sequence.

[0199] Exemplarily, the WMS may use the positionChildAt() function to sequentially move the position of the target container node in the WMS to the bottom.

[0200] For example, WMS can move the position of the target container node in WMS to the bottom through the positionChildAt(POSITION_BOTTOM,Display_1,false) interface.

[0201] In this way, since WMS moves the target container node to the bottom in the WMS sequence, the process of WMS updating the focus window will not be affected by the target container node, and WMS can successfully set the focus window.

[0202] Exemplarily, after step S5074A, WMS can update the window information through the updateInputFocusRequest process, and update the focus window to window A in the inputflinger. In the updateInputFocusRequest process, WMS can execute the mDisplayContent.isOnTop(window a) judgment condition. If the judgment condition passes, WMS executes the set FocusedWindow(window a) function to update the focus window information to the inputflinger; if the judgment condition does not pass, the updateInputFocusRequest process ends, and WMS does not update the focus window. Among them, the mDisplayContent.isOnTop() judgment condition can refer to the above expression 1.

[0203] For example, when WMS executes "parent.isOnTop()" in the judgment condition of mDisplayContent.isOnTop(window a), since WMS moves the position of display1 to the bottom in step S5074A, display0 is the container node at the top position under the root node. In this way, the value of "parent.getTopChild(Display_0)==this" is 1, resulting in the execution result of the judgment condition being 1&&1&&1; the judgment condition passes. WMS updates the focus window to inputflinger, which is window A.

[0204] In this way, after the WMS removes the back screen window and the back screen of the mobile phone turns off, the input event for the window can be transmitted to the focus window through the IMS. In this way, the mobile phone can respond to the user's return operation and switch the page currently displayed by the mobile phone (for example, switch the e-book display page to the mobile phone desktop).

[0205] In some embodiments, the execution process of the above steps S5071A-S5074A can also be encapsulated into a function, such as a removeAllTaskForDisplay() function, which can instruct the WMS to remove the back screen window. The input parameter of the removeAllTaskForDisplay() function is the identifier (displayID) of the back screen, such as Display_0 above. In this way, the back screen service can instruct the WMS to remove the back screen window by calling the removeAllTaskForDisplay() function.

[0206] In some embodiments, the above step S507 may include steps S5070-S5073, and step S5074B.

[0207] S5074B.WMS moves the position order of the non-target container node to above the position order of the target container node.

[0208] Exemplarily, WMS obtains all container nodes mounted under the root node (root), and then obtains container nodes other than the target container node among all container nodes, that is, non-target container nodes. Afterwards, WMS moves up each non-target container node until the position order of each non-target container node is above the position order of the target container node.

[0209] In this way, since the position order of the target container node is moved down, WMS can update the focus window to inputflinger by judging the condition through mDisplayContent.isOnTop() (that is, the result of mDisplayContent.isOnTop() is 1) during the updateInputFocusRequest process.

[0210] In some embodiments, step S5074A or 5074B may be executed first, and then steps S5071-S5073 may be executed.

[0211] In some embodiments, after executing step S5070, the WMS does not execute steps S5071-S5073; the WMS may remove the target container node based on the message for removing the back screen window.

[0212] In this way, since the target container node is removed, WMS can update the focus window to inputflinger by judging the condition through mDisplayContent.isOnTop() (that is, the result of mDisplayContent.isOnTop() is 1) during the updateInputFocusRequest process.

[0213] Exemplarily, WMS can obtain the identifier of the target container node through the getDisplayContentOrCreate function. After that, WMS removes the target container node through the removeImmediately() function. It can be understood that for the window mounted under the container node, if the container node is removed, the window mounted under the container node will also be removed together. In this way, since the target container node is removed, when WMS updates the focus window in inputflinger, it will not fail to pass the judgment condition due to the interference of the target container node. WMS can update the focus window to inputflinger. Then, the input event for the window can be passed to the focus window.

[0214] In some embodiments, after step S5070, the WMS may not execute the updateInputFocusRequest process, but directly update the focus window to window a in the inputflinger through the setFocusedWindow(window a) function.

[0215] Next, we will Figure 2 In the scenario shown, taking a user using a mobile phone to read an e-book as an example, the user interface displayed on the mobile phone in the process of implementing the interface display method provided in the embodiment of the present application is introduced.

[0216] At the first time point, the main screen of the mobile phone displays the first interface 401 of the first application, and the back screen of the mobile phone is off.

[0217] The first application can be an application that the user is currently using on the phone, and the second application can be the target application. For example, if the user is reading an e-book on the phone, the first application can be an e-book application, and the second application can be the target application that the user is currently using on the phone. Figure 6 The back screen displays the default application (eg, AA application) set in the application submenu 633.

[0218] For example, the user interfaces of the main screen and the back screen can be respectively referred to Fig.14A (a) and (b) in . Fig.14A In (a), the main screen of the mobile phone displays the first interface 401 of the first application (eg, the e-book viewing interface of the e-book application). Fig.14A In (b), the back screen of the mobile phone is off, that is, the user interface of any application is not displayed.

[0219] It is understandable that in some embodiments, at the first time point, the back screen of the mobile phone may not be turned off, and a pure black user interface may be displayed.

[0220] Afterwards, at the second time point, the mobile phone responds to the user's target operation and displays the QR code of the second application on the back screen of the mobile phone. Among them, the second time point is later than the above-mentioned first time point, and the target operation can be a back screen tapping operation. For the introduction of the target operation, please refer to the above description, which will not be repeated here. Specifically, the specific steps of this process can be referred to the relevant description of the above-mentioned steps S501-S506, which will not be repeated here.

[0221] For example, see Fig. 14B (a) and (b) in . Fig. 14B In (a), the main screen of the mobile phone displays the first interface 401 of the first application (eg, the e-book viewing interface of the e-book application). Fig. 14B In (b), the back screen displays the QR code 4032 of the second application (e.g., the QR code of the AA application). In some embodiments, at the second time point, the main screen of the mobile phone may also display a notification 4011 of the back screen display. The notification 4011 may include text indicating that the back screen of the mobile phone is displaying a QR code (e.g., back screen displaying).

[0222] It should be pointed out that in the interface display method provided in the embodiment of the present application, the above-mentioned first application can be the same as the second application, such as both are AA applications, and the embodiment of the present application does not impose any restrictions on this.

[0223] It is understandable that in some embodiments, at the second time point, the back screen of the mobile phone may also display some information related to the second application (eg, AA application) to prompt the user. Fig. 14B ,exist Fig. 14B In (b), the area 403 displaying the QR code of the second application is white. The area 403 may include a payment barcode 4031 and a payment QR code 4032. As another example, the back screen of the mobile phone may also display a description 404 about the QR code 4032 of the second application. The description 404 may include an icon 4041 of the second application and a name 4042 of the displayed QR code. The name 4042 of the QR code may be, for example, "AA application QR code", etc. The embodiment of the present application does not limit the text description of the name of the QR code. For example, assuming that the QR code of the AA application is a boarding code, then the name 4042 of the QR code may be "AA application boarding code". For another example, assuming that the QR code of the AA application is a payment code, then the name 4042 of the QR code may be "AA application payment code".

[0224] Then, at the third time point, in response to the event of ending the back screen display, the back screen of the mobile phone turns off. The third time point is later than the second time point.

[0225] For details, please refer to the above Fig.13 Corresponding description; and, the user graphical interface displayed by the mobile phone at the third time point can refer to the above Fig.14A And the related description will not be repeated here.

[0226] Among them, the first time point mentioned above can be called the first time point in some embodiments, or the fourth time point; the second time point mentioned above can be called the second time point in some embodiments, or the fifth time point; the third time point mentioned above can be called the third time point in some embodiments, or the sixth time point. It should be pointed out that between the first time point and the second time point, the back screen of the mobile phone is off. Also, see the above Fig.10 As described in Part A of , between the first time point and the second time point, the container node of the main screen (e.g., display0) is above the container node of the back screen (e.g., display1). Between the second time point and the third time point, see the above Fig.10 As described in Part B, the container node of the back screen (such as display1) is above the container node of the main screen (such as display0). After the third time point, because the mobile phone executes steps S5070-S5073 and step S5074A or executes steps S5070-S5073 and step S5074B, the position order of the container nodes is adjusted; for example, the position order of the target container node (such as the container node of the back screen) is moved to the bottom, or the position order of the non-target container node (such as the container node of the main screen) is moved above the position order of the target container node. This will cause the container node of the main screen (such as display0) to be above the container node of the back screen (such as display1), so that the WMS can execute the updateInputFocusRequest process to set the focus window to the IMS. In this way, the input event for the window can be given to the focus window.

[0227] It is understandable that, since at the third time point, the mobile phone executes the above steps S5070-S5073 and step S5074A or executes steps S5070-S5073 and step S5074B. Then, the container node of the main screen (e.g., display0) is above the container node of the back screen (e.g., display1), for example, see the above Fig. 9That is to say, based on the back screen end event occurring at the third time point, the mobile phone can adjust the relationship between the main screen container node and the back screen container node so that the relationship between the two is as follows: Fig. 9 shown.

[0228] In this method, the electronic device can adjust the container node of the first screen to be above the container node of the second screen when the second screen is black, so that the focus window can be switched to the first screen above the container node in time, so that the interface displayed on the first screen can respond to the user's operation, thereby alleviating the abnormal interface response and improving the user experience.

[0229] Exemplarily, assume that the user triggers a return operation on the mobile phone after the third time point. Since the container node of the main screen (such as display0) is above the container node of the back screen (such as display1), the mobile phone can meet the update judgment condition of the focus window (such as the judgment condition corresponding to the above expression 1), and then the mobile phone can set the window node mounted under the container node of the main screen as the focus window. In this way, the return operation triggered by the user can be passed to the focus window. The main screen of the mobile phone will switch interfaces in response to the return operation (such as switching from the interface of the first application to the main interface; or switching from the current interface of the first application to other interfaces of the first application).

[0230] As another example, assume that the first application is a reading application (such as an e-book application), and the interface of the first application is a reading interface. In other words, the main screen of the mobile phone displays the reading interface of the reading application. Since most reading interfaces have a volume key page turning function. After the third time point, the user triggers the operation of pressing the volume button on the mobile phone. Since the container node of the main screen (such as display0) is above the container node of the back screen (such as display1), the mobile phone can meet the update judgment condition of the focus window (such as the judgment condition corresponding to the above expression 1), and then the mobile phone can set the window node mounted under the container node of the main screen as the focus window. In this way, the operation of pressing the volume button triggered by the user can be passed to the focus window. The reading interface of the reading application displayed on the main screen of the mobile phone can respond to the operation of pressing the volume button to perform page turning operations (such as turning the current page to the next page, or turning the current page to the previous page).

[0231] In some embodiments, at the third time point, in response to the event of ending the back screen display, the back screen of the mobile phone turns off. The WMS in the mobile phone can remove the container node of the back screen. In this way, since the target container node is removed, when the WMS updates the focus window in the inputflinger, it will not fail the judgment condition due to the interference of the target container node. The WMS can update the focus window to the inputflinger. Then, the input event for the window can be passed to the focus window.

[0232] Exemplarily, in the scenario where the back screen service function is used for the first time, if before the second time point, the mobile phone does not have the target container node (that is, the container node of the back screen), the mobile phone can establish the container node of the back screen at the second time point through steps S501-S505, and steps S5061, S5062 and S5063. Then, in this scenario, before the second time point, there is a container node for the main screen on the mobile phone, and there is no container node for the back screen. Between the second time point and the third time, the container node of the back screen is above the container node of the main screen. At the third time point, if the mobile phone removes the container node of the back screen, there is a container node for the main screen on the mobile phone, and there is no container node for the back screen; if the mobile phone does not remove the container node of the back screen (such as the mobile phone executes the above steps S5070-S5073 and step S5074A or step S5074B), the container node of the main screen is above the container node of the back screen.

[0233] In some other embodiments, the mobile phone can also assist the back screen service function by displaying the back screen display control on the main screen. Fig. 14C (a1) and (b), at the second time point, the mobile phone displays the QR code of the second application on the back screen of the mobile phone in response to the user's target operation; and displays the back screen display control 402B on the main screen of the mobile phone. The back screen display control 402B includes indication information 4022 that the back screen is displaying the QR code of the second application. And / or, the back screen display control 402B includes the icon 4021 of the second application. For another example, see Fig. 14C (a2) and (b), at the second time point mentioned above, the mobile phone displays the QR code of the second application on the back screen of the mobile phone in response to the user's target operation; and displays the hidden back screen display control 402A on the main screen of the mobile phone. In response to the user's click operation on the hidden back screen display control 402A, the mobile phone displays the non-hidden back screen display control on the main screen (such as the back screen display control 402B in (a1) of 14C). At the third time point mentioned above, in response to the event of ending the back screen display, the back screen of the mobile phone is turned off; and the back screen display control 402B is not displayed on the main screen of the mobile phone.

[0234] The event for ending the back screen display may be generated by the back screen service or sent by the target application (AA application) to the back screen service.

[0235] When the mobile phone assists the back screen service function by displaying the back screen display control on the main screen, the user can use the back screen display control to close the QR code of the second application displayed on the back screen of the mobile phone. In other words, the above-mentioned event of ending the back screen display can be generated by the back screen service.

[0236] For example, see Fig.14D (a) in the figure. In response to the user's long press operation on the back screen display control 402B, the delete icon 4013 is displayed in the first area 4012 on the main screen of the mobile phone, and the back screen display control 402B becomes movable. It can be understood that the back screen display control 402B in the movable state can follow the user's touch movement on the main screen of the mobile phone. Among them, the above-mentioned first area 4012 can be any preset area on the main screen of the mobile phone, such as the middle area at the bottom of the main screen, or the middle area at the top of the main screen. And, the above-mentioned delete icon 4013 can also be an icon of a preset shape, such as an icon in the shape of a trash can, etc. Specifically, the above-mentioned first area 4012 and the delete icon 4013 can be set according to actual usage requirements, and the embodiment of the present application does not impose any restrictions on this. Afterwards, in response to the user moving the back screen display control 402B in the movable state to the above-mentioned first area 4012, the back screen service generates an event that the back screen ends display. After the back screen service generates an event that the back screen ends display, the QR code of the second application displayed on the back screen of the mobile phone will be closed, such as by Fig.14D (b1) in the example is changed to (b2); for details, please refer to the above step S507. In this way, the user can actively trigger the QR code of the second application displayed on the back screen of the mobile phone on the main screen of the mobile phone to turn off the QR code. Considering that the user may sometimes trigger the target operation by mistake, the back screen of the mobile phone displays the QR code; at this time, the user can see that the QR code displayed on the back screen of the mobile phone can be turned off by a simple operation on the main screen, thereby improving the user experience.

[0237] In some embodiments, after the QR code displayed on the back screen of the mobile phone is scanned successfully, the target application of the mobile phone sends an event to end the back screen display to the back screen service.

[0238] In some embodiments, the above Fig. 14B After the QR code shown in (b) is successfully scanned, the mobile phone can display information such as "Scanning completed" or "Payment successful" on the back screen to indicate that the QR code has been successfully scanned. Optionally, the successful scanning of the QR code can also indicate the completion of the corresponding operation (such as payment operation, etc., which is not limited in this embodiment of the application). For example, you can refer to Fig.14F and Fig.14EThe QR code is scanned successfully or the scanning is completed, which means that the QR code is successfully scanned by other devices.

[0239] Fig.14E Shown Fig. 14B After the QR code shown in (b) is scanned successfully, the interface jumps to the user interface displayed on the back screen. It can be seen that the user interface after the jump may include the icon 4034 of the first application, the words "Payment successful" 4035, the payment amount (100 yuan is shown as an example) 4036, the payment method 4037 and the payee 4038 and other information.

[0240] Fig.14F Shown Fig. 14B After the QR code shown in (b) is scanned successfully, the interface jumps to the user interface displayed on the back screen. It can be seen that the user interface after the jump can display the message 407 of "scanning completed".

[0241] Understandably, Fig.14F and Fig.14E The above is only an example and does not constitute a limitation on the embodiments of the present application. In a specific implementation, the interface that jumps to after the QR code is successfully scanned may be other user interfaces, which is not limited in the embodiments of the present application. Alternatively, the user interface after the jump may display other interface elements, which is not limited in the embodiments of the present application.

[0242] In some embodiments, at the third time point, in response to the target application sending an event to end the back screen display, the back screen of the mobile phone turns off; and a message indicating that the code scanning is completed is displayed in the back screen display control 402B of the main screen of the mobile phone. Fig. 14B The QR code shown in (b) is scanned successfully, and the mobile phone can prompt the user in the back screen display control of the main screen that the QR code displayed on the back screen of the mobile phone is scanned successfully.

[0243] For example, see Figure 14G , Fig.14F for Fig. 14B Schematic diagram of the user interface of the main screen after the QR code shown in (b) is successfully scanned. It can be seen that a floating window 402C is displayed in the user interface. The floating window 402C may include an icon 402C1 of the AA application, text 402C2 indicating that the payment has been completed, etc. For example, the text 402C2 indicating that the payment has been completed may also indicate that the amount of the payment is "x yuan".

[0244] It is understandable that in order to implement the above functions, the electronic device includes hardware and / or software modules corresponding to the execution of each function. In combination with the 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. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of the present application.

[0245] In this embodiment, the electronic device can be divided into functional modules 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 module can be implemented in the form of hardware. It should be noted that the division of modules in this embodiment is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0246] The present application also provides an electronic device, such as Fig.15 As shown, the electronic device may include one or more processors 2001 , a memory 2002 and a communication interface 2003 .

[0247] The memory 2002 and the communication interface 2003 are coupled to the processor 2001. For example, the memory 2002, the communication interface 2003 and the processor 2001 may be coupled together via a bus 2004.

[0248] The communication interface 2003 is used for data transmission with other devices. The memory 2002 stores computer program codes. The computer program codes include computer instructions. When the computer instructions are executed by the processor 2001, the electronic device performs the device authentication in the embodiment of the present application.

[0249] Among them, the processor 2001 can be a processor or a controller, for example, it can be a central processing unit (CPU), a general processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the present disclosure. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of DSP and microprocessors, and the like.

[0250] The bus 2004 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus 2004 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.15 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0251] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program code is stored. When the processor executes the computer program code, the electronic device executes the relevant method steps in the method embodiment.

[0252] The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, it enables the computer to execute the relevant method steps in the above method embodiment.

[0253] Among them, the electronic device, computer-readable storage medium or computer program product provided in this application is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be repeated here.

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

[0255] In the 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 the modules or units is only a logical function division. 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, which can be electrical, mechanical or other forms.

[0256] The units described as separate components may or may not be physically separated, 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 different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

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

[0258] 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 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 method described in each embodiment 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.

[0259] 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 changes or substitutions within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. An interface display method, characterized in that: The method is applied to an electronic device, the electronic device includes a display screen, the display area of ​​the display screen includes a first screen and a second screen, the display screen is in a folded state, and the display directions of the first screen and the second screen are opposite to each other, and the method includes: At a first time point, displaying an interface of a first application on the first screen; At a second time point, in response to the target operation, displaying an interface of a second application on the second screen; the second time point is later than the first time point; Between the first time point and the second time point, the second screen is in a black screen, and the container node of the first screen is above the container node of the second screen; the container node of the first screen and the container node of the second screen are mounted on a root node; At a third time point, in response to an event of ending the display of the second screen, controlling the second screen to become a black screen; the third time point is later than the second time point; Between the second time point and the third time point, the container node of the second screen is above the container node of the first screen, and the first screen displays the interface of the first application; After the third time point, the first screen displays the interface of the first application, and the container node of the first screen is above the container node of the second screen.

2. The method according to claim 1, characterized in that The method further comprises: Based on the event of ending the display of the second screen, the container node of the second screen is adjusted to the bottom.

3. The method according to claim 2, characterized in that Between the second time point and the third time point, the container node of the second screen mounts the window node corresponding to the display task; The step of adjusting the container node of the second screen to the bottom includes: removing the display task; Adjust the container node of the second screen to the bottom.

4. The method according to any one of claims 1 to 3, characterized in that: Between the first time point and the second time point, the focus window is the window node mounted on the container node of the first screen; Between the second time point and the third time point, the focus window is a window node mounted on the container node of the second screen; The method further comprises: At the third time point, based on the fact that the container node of the first screen is above the container node of the second screen, the update judgment condition of the focus window is passed, and the window node mounted on the container node of the first screen is set as the focus window.

5. The method according to claim 4, characterized in that The method further comprises: After the third time point, in response to a return operation, based on the focus window being a window node mounted on the container node of the first screen, the interface of the first application displayed on the first screen is switched.

6. The method according to claim 4, characterized in that The electronic device further includes a volume button, the interface of the first application is an e-book display interface of an e-book application, and the e-book display interface includes a current page of the e-book; and the method further includes: After the third time point, in response to the operation of triggering the volume key, based on the focus window being the window node mounted on the container node of the first screen, the current page of the electronic book displayed on the first screen is turned.

7. The method according to claim 1, characterized in that The method further comprises: Based on the event of ending the display of the second screen, the container node of the first screen is adjusted to the top.

8. The method according to any one of claims 1 to 7, characterized in that: The interface of the second application includes a QR code of the second application; The step of displaying the interface of the second application on the second screen in response to the target operation includes: In response to the target operation, displaying the QR code of the second application on the second screen, and displaying the second screen display control on the first screen; At a third time point, in response to the event of ending the display of the second screen, controlling the second screen to become a black screen includes: At the third time point, based on the removal operation of the second-screen display control, the second screen is controlled to become a black screen; after the third time point, the first screen does not display the second-screen display control.

9. The method according to any one of claims 1 to 7, characterized in that: The interface of the second application includes a QR code of the second application; and in response to the event of ending the display of the second screen, controlling the second screen to become a black screen includes: Based on the scanning of the QR code of the second application, controlling the second screen to become a black screen; Alternatively, based on the fact that the time duration for which the second screen displays the QR code of the second application exceeds a preset time duration, the second screen is controlled to become a black screen.

10. The method according to any one of claims 1 to 9, characterized in that: The target operation includes an operation of tapping from the rear of the first screen to the front of the first screen.

11. An interface display method, characterized in that: The method is applied to an electronic device, the electronic device comprises a display screen, the display area of ​​the display screen comprises a first screen and a second screen, the display screen is in a folded state, and the display directions of the first screen and the second screen are opposite to each other; the method comprises: At a fourth time point, an interface of a third application is displayed on the first screen; at the fourth time point, the root node mounts the container node of the first screen; At a fifth time point, in response to the target operation, the interface of the fourth application is displayed on the second screen, and a container node of the second screen mounted on the root node is created; the fifth time point is later than the fourth time point; At a sixth time point, in response to an event of ending the display of the second screen, controlling the second screen to become a black screen; the sixth time point is later than the fifth time point; Between the fifth time point and the sixth time point, the container node of the second screen is above the container node of the first screen, and the first screen displays an interface of the third application; After the sixth time point, the first screen displays the interface of the third application.

12. The method according to claim 11, characterized in that The method further comprises: Based on the event of ending the display of the second screen, the container node of the second screen is removed.

13. The method according to claim 12, characterized in that Between the fifth time point and the sixth time point, the container node of the second screen mounts the window node corresponding to the display task; The removing the container node of the second screen includes: The container node of the second screen on which the window node corresponding to the display task is mounted is removed.

14. An electronic device, characterized in that: The electronic device includes a memory and one or more processors, wherein the memory is coupled to the processor; wherein computer program code is stored in the memory, and the computer program code includes computer instructions; when the computer instructions are executed by the processor, the electronic device executes the method as described in any one of claims 1-13.

15. A computer-readable storage medium, characterized in that: The method comprises computer instructions, which, when executed on an electronic device, cause the electronic device to execute the method according to any one of claims 1 to 13.

Images