Interface display method, electronic device, and storage medium

Abstract

Embodiments of the present application relate to the technical field of terminals, and in particular relate to an interface display method, an electronic device, and a storage medium. The method may be applied to an electronic device comprising a display screen. The method comprises: at a first time point, displaying, on a first screen, an interface of a first application; then, at a second time point, in response to a preset target operation, displaying, on a second screen, a two-dimensional code of a second application; and then, at a third time point, in response to an event of ending display on the second screen, the second screen goes black. Between the second time point and the third time point, a container node of the second screen is above a container node of the first screen. When the second screen goes black, the container node of the first screen may be adjusted to be above the container node of the second screen, so that a focus window may be promptly switched to the first screen, the container node of which is positioned higher, thus an interface displayed by the first screen may respond to an operation of a user, alleviating interface response abnormalities and improving usage experience of the user.

Description

Interface display method, electronic device and storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on September 19, 2023, with application number 202311215864.0 and invention name “Interface display method, electronic device and storage medium”, the entire contents of which are incorporated by reference into this application. 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 diversify, 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 folded display screen, when the first screen and the second screen are used to display an interface, the electronic device may have abnormal interface response, resulting in a poor user experience.

[0005] Summary of the Invention

[0006] 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. In this way, 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.

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

[0008] In a first aspect, a method for displaying an interface is provided. The method can be applied to an electronic device (e.g., a mobile phone, tablet computer, etc.) including a display screen; 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 to each other. The method includes: at a first time point, the electronic device displays the interface of a first application on the first screen. At a second time point, in response to a preset target operation (e.g., a back-screen tap 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 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.

[0009] It is understood that the container node of the first screen is above the container node of the second screen. This 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, and so on. In addition, due to the 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. This can be understood as the positional order of the container node of the first screen is above the positional order of the container node of the second screen.

[0010] In this method, the electronic device can adjust the container node of the first screen 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.

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

[0012] 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 second screen display; thus, the container node of the first screen can be placed above the container node of the second screen. This can further alleviate the situation of abnormal interface response of the electronic device and improve the user experience.

[0013] 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 a window node corresponding to the display task. Adjusting the container node of the second screen to the bottom includes: the electronic device removing the display task; and then adjusting the container node of the second screen to the bottom.

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

[0015] 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 is passed, the electronic device can set the window node of the container node mounted on the first screen as the focus window. In this way, the focus window of the electronic device (the window node of the container node mounted on 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.

[0016] 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 with the focus window as the focus window.

[0017] 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 execute the interface switching of the first application indicated by the return operation on the first screen. In this way, it can alleviate the situation where the return operation triggered by the user on the electronic device is unresponsive on the first screen. Then, it can further alleviate the situation where the electronic device interface responds abnormally and improve the user experience.

[0018] 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 a volume button, the electronic device turning 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.

[0019] Considering that users may use the volume button on their electronic device to turn pages when using an e-book, 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 phone can respond to the user pressing the volume button to turn the current page of the e-book displayed on the first screen.

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

[0021] In another possible design of the first aspect, the electronic device displaying a QR code of a second application on the second screen in response to a preset target operation includes: in response to the preset target operation, the electronic device displaying a QR code of the second application on the second screen, and displaying a second-screen display control on the first screen. The second screen being blacked out at a third time point in response to an event that ends the display of the second screen includes: at the third time point, based on a removal operation on the second-screen display control, the second screen being blacked out; and after the third time point, no second-screen display control is displayed on the first screen.

[0022] In this design, users 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.

[0023] In another possible design of the first aspect, the electronic device, in response to an event that ends display of the second screen, blacks out the second screen, including: the electronic device completing scanning of a QR code of the second application, blacking out the second screen. Alternatively, the electronic device blacks out the second screen, based on display of the QR code of the second application on the second screen for a duration exceeding a preset duration (e.g., 3 seconds, 5 seconds, or 10 seconds).

[0024] 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 experience.

[0025] In a second aspect, another interface display method is provided. The method can be applied to an electronic device (such as a mobile phone, tablet computer, etc.) including a display screen; the display area of ​​the display screen includes a first screen and a second screen, and the display screen of the electronic device is in a folded state, with the display directions of the first screen and the second screen facing away from each other. The method includes: at a fourth time point, the electronic device displays the interface of a 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 a 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 to end the display of the second screen, the second screen goes black, and the container node of the second screen is removed. The sixth time point is later than the fifth time point. Between the fifth and sixth time points, 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.

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

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

[0028] 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 above-mentioned first aspect and any possible design of the first aspect; or causes the electronic device to execute the method provided by the above-mentioned second aspect and any possible design of the second aspect.

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

[0030] 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

[0031] FIG1A-FIG1D are schematic diagrams of a group of electronic devices provided in an embodiment of the present application;

[0032] FIG2 is a schematic diagram of a usage scenario provided by an embodiment of the present application;

[0033] FIG3 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application;

[0034] FIG4 is a schematic diagram of the software structure of an electronic device provided in an embodiment of the present application;

[0035] FIG5 is a schematic diagram of a flow chart of an interface display method provided in an embodiment of the present application;

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

[0037] FIG7 is a schematic diagram of another interface display method process provided in an embodiment of the present application;

[0038] FIG8 is a schematic diagram of a tree node logical relationship provided by an embodiment of the present application;

[0039] FIG9 is a schematic diagram of a position sequence of container nodes provided in an embodiment of the present application;

[0040] FIG10 is a schematic diagram of a tree node logical relationship change provided by an embodiment of the present application;

[0041] FIG11 is a schematic diagram of another change in the logical relationship of tree nodes provided in an embodiment of the present application;

[0042] 12A and 12B are schematic diagrams of a set of usage scenarios;

[0043] FIG13 is a schematic diagram of another interface display method process provided in an embodiment of the present application;

[0044] 14A-14G are schematic diagrams of a set of user graphical interfaces provided in an embodiment of the present application;

[0045] FIG15 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] 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 description of the association relationship of 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. In addition, 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 similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean different.

[0047] At the same time, in the embodiments of this 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 this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0048] With the development of users' diversified demands for electronic devices, foldable screen electronic devices with both 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). The folding methods of foldable screens on electronic devices can be divided into two categories. One is a foldable screen that folds outward (referred to as an outward folding screen), and the other is a foldable screen that folds inward (referred to as an inward folding screen). Among them, take the example of a foldable screen that 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.

[0049] 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 folding modes: 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 folding modes, 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.

[0050] For example, FIG1A shows a schematic diagram of the electronic device 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 for displaying a user interface. The first screen and the second screen can be folded along a folding axis or folding edge (the folding axis is used as an example in FIG1A to FIG1D ).

[0051] For example, in FIG1A , 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 state shown in FIG1B . For example, in FIG1B , the second screen can be further folded along the direction shown in 1c to obtain the folded state shown in FIG1C (hereinafter referred to as the folded state). FIG1C shows the second screen in the folded state. The first screen in the folded state can be exemplified in FIG1D .

[0052] Exemplarily, the first screen can be called the main screen of the electronic device, and the second screen can also be called the secondary screen of the electronic device; if the electronic device is in a folded state, the first screen and the second screen are facing back to back, 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.

[0053] It is understood that the above-mentioned Figures 1A to 1D are merely examples and do not constitute a limitation on the embodiments of the present application. For example, in some other embodiments, in addition to the above-mentioned first and second screens, the electronic device may also include other display screens, which are not limited in the embodiments of the present application.

[0054] When a user uses an electronic device with a folded display screen, when the first screen and the second screen are used to display an interface, the electronic device may have abnormal interface response, resulting in a poor user experience.

[0055] 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 off, 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 the return operation on the electronic device (such as clicking the back button, swiping left to return, or swiping right to return), the interface of the first screen of the electronic device will become unresponsive.

[0056] In view of this, an embodiment of the present application provides an interface display method, the method comprising: 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 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.

[0057] In this method, the electronic device can adjust the container node of the first screen 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.

[0058] It is understood that the focus window is the window that is displayed in the front of the electronic device and receives input events (e.g., a return operation) for the window. Typically, there is only one focus window on an electronic device; these focus windows can be activity windows, dialog windows, etc.

[0059] For example, referring to FIG2 , the interface display method provided in the embodiment of the present application can be applied to the process in which a user uses an electronic device 100 with an outward-folding screen in a folded state (e.g., using the electronic device 100 to read e-books, watch videos, chat, etc.). 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 an on-board computer, an on-board computer, and other on-board 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.

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

[0061] For example, referring to Figure 3, the 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 194, and a subscriber identification module (SIM) card interface 195, etc. The sensors 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.

[0062] It should be understood that the structure illustrated in the embodiments 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, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

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

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

[0066] Display screen 194 is used to display images, videos, and the like. 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 (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-oLed, or a quantum dot light-emitting diode (QLED). In some embodiments, electronic device 100 can include one or N display screens 194, where N is a positive integer greater than one.

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

[0068] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A may be located on display screen 194. Electronic device 100 determines the intensity of pressure based on changes in capacitance. When a touch operation is applied to display screen 194, electronic device 100 detects the intensity of the touch operation using pressure sensor 180A. Electronic device 100 may also calculate the location of the touch based on the detection signal from pressure sensor 180A.

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

[0070] Accelerometer 180E can detect the magnitude of acceleration of electronic device 100 in all directions (generally three axes). It can also detect the magnitude and direction of gravity when electronic device 100 is stationary. It can also be used to identify the electronic device's posture, enabling applications such as switching between landscape and portrait modes and pedometers.

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

[0072] The touch sensor 180K is also called a "touch panel." The touch sensor 180K can be disposed on the display screen 194. 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 applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the electronic device 100, in a location different from that of the display screen 194.

[0073] For example, the electronic device 100 may detect a left swipe (swipe) return operation / right swipe (swipe) return operation triggered by the user through the touch sensor 180K.

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

[0075] The buttons 190 include a power button, a volume button, and the like. The buttons 190 may be mechanical buttons or touch buttons. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100.

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

[0077] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel 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 layer (Android TM runtime) and system libraries, hardware abstraction layer (HAL), and kernel layer.

[0078] It is understood that the software structure shown in FIG4 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 can also be divided into other layers, for example, into the application layer, the application framework layer, the native layer, and the kernel layer. Different operating systems can also have different layer divisions. Specifically, the operating system can be divided into different layers based on actual usage.

[0079] The application layer can include a series of application packages. As shown in Figure 4, the application package can include camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

[0080] The application layer may also include a back-screen service (tap service), which can be used to pull up the display of a target function code on the back screen of the electronic device. The specific implementation of this service can be seen in the relevant introduction below and will not be described in detail here. For example, the target function code can be a QR code, barcode, etc.; for example, the QR code can be a payment code, a boarding code, or any identity identification code, etc., and this embodiment of the application does not limit this.

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

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

[0083] The system server is a process that provides many subsystem services. Each subsystem service runs as a thread, waiting for requests from applications, processing them, and returning the results to the applications. These subsystem services include, for example, the Window Manager Service (WMS), the Notification Manager Service (NMS), the Activity Manager Service (AMS), and the Input Manager Service (IMS).

[0084] WMS can be used for window management, window animation management, surface management, and as a transit 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 automatically disappear after a short stay without user interaction. AMS can be used to start, switch, and schedule system components (such as 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 mentioned below), and assigns events to windows in WMS through interaction with WMS. The media server is responsible for playing audio and video, as well as taking photos and recording videos.

[0085] 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 events corresponding to the focus window from the IMS. The input events can be assigned to the focus window for processing through the interaction between the WMS and the IMS.

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

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

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

[0089] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

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

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

[0092] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. It supports a variety of audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG. The 3D graphics processing library implements 3D graphics drawing, image rendering, compositing, and layer processing. The 2D graphics engine is a drawing engine for 2D graphics.

[0093] The Hardware Abstraction Layer (HAL) is an abstract structure between the kernel layer and upper layers. It encapsulates kernel-layer drivers and provides a unified interface to upper layers. This shields upper-layer applications from the detailed operation of the underlying hardware, thus shielding them from the underlying implementation details.

[0094] The hardware abstraction layer (HAL) provides a standard interface that exposes device hardware capabilities to the higher-level application framework layer. The HAL contains multiple library modules, each of which implements an interface for a specific type of hardware component. These library modules may include audio, Bluetooth, camera, sensor, and keypad modules. Sensor modules may include, for example, accelerometer, magnetic field, orientation, gyroscope, light, pressure, temperature, and proximity sensors. When the application framework layer requests access to device hardware, the system loads the corresponding library module for that hardware component. Manufacturers can define interfaces in the HAL.

[0095] For example, 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).

[0096] The kernel layer is the layer between hardware and software. The kernel layer includes at least the display driver, camera driver, and audio driver. The kernel layer can also include sensor drivers, button drivers, and more.

[0097] Exemplarily, the hardware of the electronic device, such as button 190 or touch sensor 180K, 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.

[0098] Below, the interface display method provided by the embodiment of the present application will be described in detail with reference to the accompanying drawings, taking the usage scenario shown in FIG2 as an example, where the electronic device 100 is a folded external folding screen mobile phone. For ease of description, the folded external folding screen mobile phone will be referred to as a mobile phone, the first screen of the external folding screen mobile phone will be referred to as the main screen, and the second screen of the external folding screen mobile phone will be referred to as the back screen.

[0099] 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, etc.; specifically, it can be set according to actual usage needs, and the embodiment of the present application does not impose any restrictions on this.

[0100] Exemplarily, referring to FIG. 5 , the interface display method provided in the embodiment of the present application may include: steps S501 - S507 .

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

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

[0103] 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 is turned on on the mobile phone, 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) and displaying 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. In the following embodiments of this application, the target function code will be introduced as a QR code as an example, and the embodiments of this application are not limited to this.

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

[0105] For example, see Figure 6 . A mobile phone displays a desktop 600; a user can click a settings icon 601 on the desktop 600. In response to the user clicking the settings icon 601, the mobile phone displays a settings menu interface 610. Next, the user clicks a foldable screen settings option 611 on the settings menu interface 610. In response to the user clicking the foldable screen settings option 611, the mobile phone displays a foldable screen settings menu 620. The foldable screen settings menu 620 may include a switch 621 corresponding to "back screen service." The user then clicks the switch 621. In response to the user clicking the switch 621, the mobile phone displays a back screen display application submenu 633 in the foldable screen settings menu 630. The back screen display application submenu 633 displays related applications that support back screen display (e.g., AA applications, BB applications, CC applications, etc.); as well as an "on / off" switch 631 and a "default application" switch 632 for each application. 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 App" switch 632 is used to turn on / off the default display of the QR code corresponding to the application. For applications with the "On / Off" switch 631 turned on, the phone can display its corresponding QR code through the back screen service function. Applications with the "Default App" switch 632 turned on will have their corresponding QR code displayed by default (with priority display).

[0106] Among them, the above-mentioned related applications that support 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.

[0107] As shown in Figure 6, in the foldable screen settings menu 630, the "On / Off" switches 631 for the AA app and the BB app are on, and the "Default App" switch 632 for the AA app is on. This means that the phone's back screen service function can display the QR code corresponding to the AA app or the BB app; and the QR code corresponding to the AA app will be displayed by default on the phone (e.g., in response to a back screen tap, the QR code corresponding to the AA app will be directly displayed).

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

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

[0110] It is understood 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.

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

[0112] 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 once, 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.

[0113] 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, etc. The specific operation can be designed according to actual usage needs, and the embodiments of the present application do not limit this. For ease of expression, 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.

[0114] 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 algorithm to obtain a back-screen tapping event. Then, the sensor module sends the back-screen tapping event to the back-screen service.

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

[0116] The target application can be the default application set by the user in the back screen display application submenu in the folding screen settings menu; for example, the AA application mentioned above. The target QR code can be the QR code of the target application, such as the QR code of the AA application mentioned above.

[0117] It is understandable that a software development kit (SDK) can be a collection of development tools for creating application software for software packages, software frameworks, hardware platforms or operating systems. SDK can be an SDK used by an application. SDK facilitates the creation of applications through compilers, debuggers or software frameworks. Alternatively, SDK can provide some files of application program interfaces for a certain programming language, or it 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.

[0118] Exemplarily, the back screen service may use the SDK of the target application and then send a message to pull up the target QR code to the target application through the interface of the SDK.

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

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

[0121] For example, the message that pulls up the target QR code can be carried in an intent parameter. This intent parameter specifies the activity to be launched (hereinafter referred to as the target activity), that is, the intent parameter includes data describing the target activity. AMS can parse this intent parameter to create a corresponding application activity record (activityrecord), which allows the target application to launch the target activity.

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

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

[0124] After AMS creates an application activity record based on the message that pulls up the target QR code, it can first determine whether the application process indicated by the application activity record (such as the target application process described above) exists. If not, it can first start the target application process and then send a notification to the target application to start the target activity. If the target application process exists, it directly sends a notification to the target application to start the target activity.

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

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

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

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

[0129] The target activity can draw a user interface based on the view tree of the back-screen display window, causing the target QR code to be displayed on the phone's back screen. For ease of description below, the view tree of the back-screen display window will be referred to as the back-screen window. For more information about the back-screen window, see the description corresponding to Figure 8 below and will not be discussed in detail here.

[0130] In this way, after the target application instructs the 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, the design can be based on actual usage requirements, and the present embodiment does not impose any restrictions on this.

[0131] In some embodiments, in step S506, the target service may further 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. 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 switching the target application described above (e.g., switching the target application from AA to BB).

[0132] Exemplarily, the target service may further 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.

[0133] In some embodiments, referring to FIG. 7 , the above-mentioned step S506 may include steps S5061 - S5063 .

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

[0135] Among them, the container node (display) can also be called a display container node. A 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).

[0136] For ease of description, the container node corresponding to the back-screen window can be referred to as the target container node below. The target container node can 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 target activity.

[0137] 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 mobile phone's display. 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.

[0138] In some embodiments, the WMS can 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).

[0139] Among them, the root node (root), which can also be called the root window display container (root window container), is the top 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, referring to Figure 8, container node 0 (display0) and container node 1 (display1) are mounted under the root node; the two 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.

[0140] Understandably, for phones with the back screen service enabled, since the phone needs to display on the back screen, the phone will set up container nodes (display) corresponding to the main screen and the back screen respectively in the WMS to distinguish between the main screen and the back screen. By mounting different windows under the container nodes, the display content on the phone's main screen and back screen (such as the interface displayed on the main screen and the elements within the interface, etc.) is managed.

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

[0142] In one possible implementation, the container nodes may exist in the mobile phone in the form of an array. For example, see Figure 9, which shows the position order of display0 and display1 in an order from top to bottom. As can be seen from the figure, display0 is at the top position, and display0 is above display1. In 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, this can be designed according to actual usage requirements, and this does not impose any restrictions on this.

[0143] Referring again to Figure 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. For example, if index 0 is greater than index 1, then display0 is considered to be above display1 in the top-to-bottom order. Furthermore, the phrase "display0 is above display1" can also be expressed as display0 being above display0 in the order of position.

[0144] 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. If so, step S5063 is executed; if not, steps S5062-S5063 are executed.

[0145] It's understandable that the target container node on the phone may not exist when the back screen service feature is used for the first time. This first-time use of the back screen service feature can be understood as the first time the phone is turned on and uses the back screen service feature, displaying the target QR code on the back screen. Alternatively, if the target container node was removed after the target QR code was displayed on the back screen the previous time the back screen service feature was used, the target container node may not exist when the back screen service feature is used this time.

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

[0147] 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).

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

[0149] For example, the WMS may create a background screen window and mount the background screen window to display1.

[0150] The back screen display window may include window D in Figure 8 or may include window D and window E in Figure 8. Specifically, the design may be made according to actual use needs, and the embodiment of the present application does not impose any limitation on this.

[0151] Exemplarily, it is assumed 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 the 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 description 4032 of the QR code of the second application in 404 of Figure 14B below. For details, see the relevant introduction to Figure 14B below.

[0152] 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., and display the above-mentioned target QR code. In addition, the back screen service can also draw some graphical interfaces (such as the above-mentioned auxiliary interface) in the back screen window to display the above-mentioned 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.

[0153] As you can understand, WMS and IMS work together to maintain the focused window on the phone. Specifically, WMS can update window information through the updateInputFocusRequest process and update the focused window information in the inputflinger through the setFocusedWindow function. After that, IMS can send input events to the focused window after receiving them.

[0154] Inputflinger is the process used in IMS to manage the distribution of input events. It includes the input event dispatcher service component. Input events on the phone are dispatched to the corresponding focused window via the input dispatcher for processing. In other words, WMS is responsible for maintaining the focused window in inputflinger.

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

[0156] In some embodiments, the WMS can 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 can set the topmost window as the focus window.

[0157] For example, see Figure 10, which shows the position order from top to bottom in order from left to right. As shown in part A of Figure 10, before step S501, it is assumed that display0 and display1 exist in WMS. Display0 is the container node of the main screen, and display1 is the container node of the back screen. The interface is being displayed on the main screen of the mobile phone. Under display0, window A, window B and window C are mounted 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, window A is set as the focus window.

[0158] Specifically, WMS obtains that window A is a window at the top position mounted under the container node (display0) at the top position. Afterwards, WMS can update the window information by calling the updateInputFocusRequest process and 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.

[0159] It is understandable that after the WMS determines the focus window, the WMS may further 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.

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

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

[0162] In expression 1, "!" represents logical negation, "&&" represents logical AND, and "==" indicates whether both ends of an equation are identical. "parent!= null" indicates that the parent node is not null. If so, 1 is returned, and if not, 0 is returned. "this" represents the identifier entered in the judgment condition mDisplayContent.isOnTop(). "parent.getTopChild()" is a function that retrieves the child node at the top position under the parent node.

[0163] "parent.isOnTop()" determines whether the parent node is at the top. Specifically, you can execute "parent!=null && parent.getTopChild()==this" on the parent node to determine whether its parent node is at the top. It can be understood that the parent node and child node described above can be understood as the relative relationship between the mount and the mounted. For example, the parent node of window A is display0, and window A is the child node of display0.

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

[0165] 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 of window A, display0, is at the top.

[0166] 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". 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". Since the parent node of display0 is not empty, 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.

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

[0168] Referring again to Figure 10 , as shown in Section B of Figure 10 , after step S505 , the WMS creates the back-screen windows (represented as windows D and E in Figure 10 ), and the phone displays the QR code on the back-screen. The WMS adjusts the order of the container nodes and windows. The WMS can adjust the focus window, such as by calling the updateInputFocusRequest process to update window information and update the focus window (e.g., window D) to the inputflinger.

[0169] For example, after the WMS passes the judgment condition mDisplayContent.isOnTop(window d), it updates the focus window to window D in the inputflinger through setFocusedWindow(window d). Here, "window d" is the identifier of window D. Specifically, the process of WMS executing the judgment condition mDisplayContent.isOnTop(window d) can be found above. The description of WMS executing the judgment condition mDisplayContent.isOnTop(window a) is not repeated here.

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

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

[0172] The event that ends the back screen display, also known as the back screen end event, is used to indicate that the phone has ended the back screen service function and stopped displaying the target QR code on the back screen. The back screen end event can be sent to the back screen service by the target application, generated by the back screen service, or sent to the back screen service by other modules in the phone, such as the timer module. The specific design can be based on actual usage needs and is not limited in this embodiment of the application.

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

[0174] For example, 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.

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

[0176] For example, after WMS successfully creates the back screen window, WMS can start a timer, and the timing period of the timer 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.

[0177] 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 phone will stop displaying the target QR code on the back screen and the back screen will turn off.

[0178] For example, referring to FIG11 , 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 the WMS. The WMS receives the notification and removes each task corresponding to the back screen window through the removeImmediately() function.

[0179] After the WMS removes the back-screen window, the WMS re-determines and updates the focus window due to changes in the WMS window. The WMS sets the topmost window under the root as the focus window. As shown in Figure 11, since the top container node is the mounted window, the WMS can set the top window, which is mounted under the container node behind the top container node, as the focus window. For example, Window A is set as the focus window.

[0180] For example, WMS can update 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 be referred to the above expression 1.

[0181] For example, when WMS executes the "parent.isOnTop()" check in the mDisplayContent.isOnTop(window a) check, Window A's parent, display0, is not the top container node under the root node. The top container node under the root node is display1. This results in the value of "parent.getTopChild(Display_0) == this" being 0, resulting in the check result being 1&&1&&0; the check fails. WMS does not update the input flinger that the focus window is Window A.

[0182] 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 result in an 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.

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

[0184] For example, referring to Figure 12A, suppose that after the WMS removes the back screen window and the back screen of the mobile phone goes off, the user triggers the return operation on the mobile phone (such as clicking the back button operation, swiping left to return operation, swiping right to return operation). The user controls the mobile phone through the return operation to switch the currently displayed page (such as the e-book display page) to display other pages (such as the mobile phone's desktop); 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 the IMS. From the description corresponding to Figure 11 above, it can be seen that the WMS did not update the focus window to window A in the inputflinger, and the focus window in the inputflinger of the IMS is still window D. The IMS will distribute the return operation to window D in the WMS. However, since window D does not exist in the WMS, window D is removed by the WMS. Then the return operation fails to be passed to the focus window. Then, the mobile phone cannot respond to the return operation, and the mobile phone is unresponsive.

[0185] It is understandable that if the user triggers a volume button operation on the mobile phone, the mobile phone will also execute a process similar to the process corresponding to Figure 12A above, and the mobile phone will also be unresponsive, which will reduce the user experience.

[0186] Therefore, in some other technical solutions provided by the embodiments of the present application, after the WMS removes the back screen window and the phone's back screen goes off, the WMS can adjust the position order of the container nodes. In this way, after the WMS removes the back screen window, the WMS can successfully update the focus window to the IMS inputflinger. Then, the focus window can receive input events for the window, and the input events for the window will generate a response on the phone, which can improve the user experience.

[0187] For example, referring to FIG12B , 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 return operation on the mobile phone, and 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 the 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 the 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 display the desktop of the mobile phone in response to the return operation.

[0188] Alternatively, 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 operation of pressing the volume button on the mobile phone. The user controls the mobile phone to switch the page displayed on 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 then the mobile phone can respond to the operation and turn the e-book page displayed on the main screen.

[0189] In some embodiments, referring to FIG. 13 , the above-mentioned step S507 may include steps S5070 - S5073 , and step S5074A.

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

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

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

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

[0194] 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 back screen window list.

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

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

[0197] For example, the WMS can remove the traversed identifier through the removeImmediately function.

[0198] For example, WMS can search for the identifier of the window node from the back screen window list, use the removeImmediately 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.

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

[0200] S5074A.WMS moves the target container node to the bottom in sequence.

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

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

[0203] In this way, since WMS moves the target container node to the bottom in the WMS order, 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.

[0204] For example, 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 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 be referred to the above expression 1.

[0205] For example, when WMS executes the "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.

[0206] 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 inputflinger that the focus window is window A.

[0207] In this way, after the WMS removes the back screen window and the phone's back screen goes off, input events for the window can be passed to the focus window through IMS. In this way, the phone can respond to the user's return operation and switch the page currently displayed on the phone (for example, switching the e-book display page to the phone's desktop).

[0208] In some embodiments, the execution process of 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 of the back screen (displayID), 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.

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

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

[0211] For example, the WMS obtains all container nodes mounted under the root node (root), and then obtains the container nodes other than the target container node, namely the non-target container nodes. The WMS then moves each non-target container node up until the position order of each non-target container node is above the position order of the target container node.

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

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

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

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

[0216] Exemplarily, WMS can obtain the identifier of the target container node through the getDisplayContentOrCreate function. Afterwards, 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 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.

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

[0218] Next, taking the scenario shown in FIG2 , in which a user uses a mobile phone to read an e-book, as an example, the user interface displayed on the mobile phone during the process of implementing the interface display method provided in the embodiment of the present application will be introduced.

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

[0220] The first application may be an application currently being used by the user on the mobile phone, and the second application may be the target application. For example, assuming that the user is reading an e-book on the mobile phone, the first application may be an e-book application, and the second application may be the default application (e.g., AA application) set by the user in the back screen display application submenu 633 in FIG. 6 .

[0221] For example, the user interfaces of the main screen and back screen can be seen in (a) and (b) of Figure 14A, respectively. In Figure 14A (a), the main screen of the mobile phone displays the first interface 401 of the first application (e.g., the e-book viewing interface of the e-book application). In Figure 14A (b), the back screen of the mobile phone is off, that is, no user interface of any application is displayed.

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

[0223] Afterwards, at a second time point, the phone responds to the user's target operation by displaying the QR code of the second application on the back screen of the phone. The second time point is later than the first time point, and the target operation may be a back screen tap. For an introduction to the target operation, please refer to the above description and will not be repeated here. Specifically, the specific steps of this process can be referred to the relevant descriptions of steps S501-S506 above and will not be repeated here.

[0224] For example, see (a) and (b) in Figure 14B. In (a) of Figure 14B, the main screen of the mobile phone displays the first interface 401 of the first application (e.g., the e-book viewing interface of the e-book application). In (b) of Figure 14B, 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 displayed on the back screen. 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").

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

[0226] It will be appreciated 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 (e.g., the AA application) to prompt the user. For example, referring again to FIG. 14B , in FIG. 14B (b), area 403 displaying the QR code of the second application is white. 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 of the QR code 4032 of the second application. This description 404 may include an icon 4041 of the second application and the name 4042 of the displayed QR code. The name 4042 of the QR code may be, for example, "AA application QR code." This embodiment of the present application does not limit the textual 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."

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

[0228] Specifically, the specific steps of this process can refer to the relevant description corresponding to Figure 13 above; and the user graphical interface displayed on the mobile phone at the third time point can refer to Figure 14A above and its relevant description, which will not be repeated here.

[0229] Among them, the above-mentioned first time point can be called the first time point in some embodiments, or the fourth time point; the above-mentioned second time point can be called the second time point in some embodiments, or the fifth time point; the above-mentioned third time point 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, referring to the relevant description in Part A of FIG10 above, between the first time point and the second time point, the container node of the main screen (such as display0) is above the container node of the back screen (such as display1). Between the second time point and the third time point, referring to the relevant description in Part B of FIG10 above, 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.

[0230] It is understandable that, since the mobile phone executed steps S5070-S5073 and step S5074A or steps S5070-S5073 and step S5074B at the third time point, the main screen container node (e.g., display0) is placed above the back screen container node (e.g., display1), as shown in Figure 9. In other words, 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, such that the relationship between the two is as shown in Figure 9.

[0231] In this method, the electronic device can adjust the container node of the first screen 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.

[0232] For example, suppose 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 the interface 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).

[0233] As another example, assume that the first application mentioned above 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 under the container node mounted on 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 perform a page turning operation in response to the operation of pressing the volume button (such as turning the current page to the next page, or turning the current page to the previous page).

[0234] 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, because 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 interference from the target container node. The WMS can update the focus window in the inputflinger. Then, input events for the window can be delivered to the focus window.

[0235] For example, in the scenario where the back screen service function is used for the first time, if the target container node (i.e., the back screen container node) does not exist on the mobile phone before the second time point, the mobile phone can establish the back screen container node at the second time point through steps S501-S505, and steps S5061, S5062, and S5063. Then, in this scenario, before the second time point, the mobile phone has a container node for the main screen, but no container node for the back screen. Between the second time point and the third time point, the back screen container node is above the main screen container node. At the third time point, if the mobile phone removes the back screen container node, the mobile phone has a container node for the main screen, but no container node for the back screen. If the mobile phone does not remove the back screen container node (e.g., the mobile phone executes the above steps S5070-S5073 and step S5074A or step S5074B), the main screen container node is above the back screen container node.

[0236] In some other embodiments, the mobile phone can also assist the back screen service function by displaying a back screen display control on the main screen. For example, referring to (a1) and (b) of Figure 14C, 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 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 an icon 4021 of the second application. For another example, referring to (a2) and (b) of Figure 14C, 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 back screen display control 402A in a hidden state on the main screen of the mobile phone. In response to the user clicking on the hidden back screen display control 402A, the phone displays the non-hidden back screen display control (e.g., back screen display control 402B in (a1) of FIG14C ) on the main screen. At the third time point, in response to the event of ending the back screen display, the back screen of the phone turns off, and the back screen display control 402B is not displayed on the main screen of the phone.

[0237] The event of 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.

[0238] When the phone assists the back screen service function by displaying a 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 phone. In other words, the event of ending the back screen display can be generated by the back screen service.

[0239] For example, see (a) in Figure 14D. 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 to end the back screen display, the QR code of the second application displayed on the back screen of the mobile phone will be turned off, such as changing from (b1) to (b2) in Figure 14D; 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. Considering that the user may sometimes accidentally trigger the target operation, the QR code is displayed on the back screen of the mobile phone; at this time, the user can turn off the QR code displayed on the back screen of the mobile phone through a simple operation on the main screen, thereby improving the user experience.

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

[0241] In some embodiments, after the QR code shown in (b) of FIG. 14B is successfully scanned, the mobile phone may display information such as "Scan Completed" or "Payment Successful" on the back screen. This indicates that the QR code has been successfully scanned. Alternatively, the successful scanning of the QR code back screen may also indicate the completion of the corresponding operation (such as a payment operation, etc., which is not limited in this embodiment of the present application). For example, see FIG. 14F and FIG. 14E. The successful scanning or scanning completion of the QR code means that the QR code has been successfully scanned by other devices.

[0242] Figure 14E shows the user interface displayed on the back screen after the QR code shown in Figure 14B (b) is successfully scanned. As can be seen, the user interface after the jump may include information such as the first application icon 4034, the words "Payment Successful" 4035, the payment amount (using 100 yuan as an example) 4036, the payment method 4037, and the payee 4038.

[0243] FIG14F shows the user interface displayed on the back screen after the QR code shown in FIG14B(b) is successfully scanned. As can be seen, the user interface after the jump may display a message 407 of "Scanning completed".

[0244] It is understood that Figures 14F and 14E are merely examples and do not limit the embodiments of the present application. In a specific implementation, the interface that jumps to after the QR code is successfully scanned can be another user interface, and the embodiments of the present application do not limit this. Alternatively, the user interface after the jump can display other interface elements, and the embodiments of the present application do not limit this.

[0245] In some embodiments, at the third time point described above, 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 complete is displayed in the back screen display control 402B on the main screen of the mobile phone. In other words, in response to the successful scanning of the QR code shown in FIG14B(b), the mobile phone can prompt the user in the back screen display control on the main screen that the QR code displayed on the back screen of the mobile phone has been successfully scanned.

[0246] For example, referring to FIG14G , FIG14F illustrates the user interface of the main screen after the QR code shown in FIG14B (b) is successfully scanned. As can be seen, a floating window 402C is displayed in the user interface. This floating window 402C may include the AA application icon 402C1, text 402C2 indicating that payment has been completed, and so on. For example, this text 402C2 indicating that payment has been completed may also indicate that the payment amount is "x yuan."

[0247] 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 this application.

[0248] In this embodiment, the electronic device can be divided into functional modules according to the above-mentioned method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into a single processing module. The above-mentioned integrated modules can be implemented in the form of hardware. It should be noted that the module division in this embodiment is illustrative and is only a logical functional division. In actual implementation, other division methods may be used.

[0249] An embodiment of the present application also provides an electronic device, as shown in FIG15 , which may include one or more processors 2001 , a memory 2002 and a communication interface 2003 .

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

[0251] The communication interface 2003 is used to transmit data with other devices. The memory 2002 stores computer program code. The computer program code includes 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.

[0252] The processor 2001 may be a processor or controller, such as a central processing unit (CPU), a general-purpose 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 may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the present disclosure. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0253] 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 illustration, FIG15 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

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

[0255] An embodiment of the present application further provides a computer program product, which, when executed on a computer, enables the computer to execute the relevant method steps in the above method embodiment.

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

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

[0258] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

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

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

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

Claims

1. An interface display method, characterized in that: 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