Interface display methods, electronic devices and storage media

Abstract

This application relates to the field of terminal technology, and more particularly to an interface display method, electronic device, and storage medium. The method can be applied to electronic devices including a display screen. The method includes: at a first time point, displaying the interface of a first application on a first screen; then, at a second time point, in response to a preset target operation, displaying a QR code of a second application on a second screen; next, at a third time point, in response to an event that ends the display of the second screen, the second screen goes black. Between the second and third time points, the container node of the second screen is above the container node of the first screen. When the second screen goes black, the container node of the first screen can be adjusted to be above the container node of the second screen, thus enabling the focus window to switch promptly to the first screen with the container node above it. This allows the interface displayed on the first screen to respond to user operations, thereby mitigating abnormal interface response and improving the user experience.

Description

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

[0002] This application relates to the field of terminal technology, and in particular to an interface display method, electronic device, and storage medium. Background Technology

[0003] With the diversification of user demands for electronic devices, foldable screen electronic devices, which combine large screens and convenience, have become widely popular. 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 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 is in the folded state, the first screen and the second screen face opposite directions.

[0004] When a user uses an electronic device with its display folded, there are instances of abnormal interface response when using the first and second screens for display, resulting in a poor user experience. Summary of the Invention

[0005] This application provides an interface display method, electronic device, and storage medium. When the second screen is black, the container node of the first screen can be adjusted to be above the container node of the second screen. This allows the focus window to switch to the first screen with the container node above it in a timely manner, so that the interface displayed on the first screen can respond to the user's operation. This can alleviate the situation of abnormal interface response and improve the user experience.

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

[0007] Firstly, a method for displaying an interface is provided, applicable to electronic devices including displays (e.g., mobile phones, tablets, etc.); the display area of ​​the display includes a first screen and a second screen, the display of the electronic device is in a folded state, and the display orientations of the first screen and the second screen are opposite. 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), a QR code of a second application is displayed on the second screen; the second time point is later than the first time point. Between the first and second time points, 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 nodes of the first screen and the container node of the second screen are attached to a root node. At a third time point, in response to an event that ends the display of the second screen, the second screen goes black; the third time point is later than the second time point. Between the second and third 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 first application. After the third time point, the first screen displays the interface of the first application, and the container node of the first screen is above the container node of the second screen.

[0008] It is understandable that the container nodes of the first screen being above the container nodes of the second screen can also be described as the container nodes of the first screen preceding the container nodes of the second screen, or the container nodes of the first screen preceding the container nodes of the second screen, and so on. Furthermore, since there are positional relationships between the container nodes mounted on the root node, the statement that the container nodes of the first screen are above the container nodes of the second screen can be understood as the container nodes of the first screen being in a positional order that is above the container nodes of the second screen.

[0009] In this method, when the second screen is black, the electronic device can adjust the container node of the first screen to be above the container node of the second screen. This allows the focus window to switch to the first screen with the container node above it in a timely manner, so that the interface displayed on the first screen can respond to the user's operation. This can alleviate the situation of abnormal interface response and improve the user experience.

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

[0011] In this design, the electronic device can adjust the container node of the second screen to the bottom based on the event that the second screen display ends; in this way, the container node of the first screen can be located above the container node of the second screen. This can further alleviate the problem of abnormal interface response on electronic devices and improve the user experience.

[0012] In another possible design of the first aspect, between the second and third time points, the container node of the second screen is attached to the window node corresponding to the display task. The aforementioned adjustment of the container node of the second screen to the bottom includes: the electronic device removing the display task; subsequently, the electronic device adjusts the container node of the second screen to the bottom.

[0013] In another possible design of the first aspect, between the first and second time points, the focus window is the window node attached to the container node of the first screen; between the second and third time points, the focus window is the window node attached to the container node of the second screen. The method further includes: at the third time point, based on the container node of the first screen being on top of the container node of the second screen, if the update condition for the focus window is met, the electronic device sets the window node attached to the container node of the first screen as the focus window.

[0014] In this design, since the container node of the first screen is above the container node of the second screen, the execution result of the update condition for the focused window on the electronic device will pass. Once the update condition for the focused window passes, the electronic device can set the window node attached to the container node of the first screen as the focused window. In this way, the focused window of the electronic device (the window node attached to the container node of the first screen) can respond to the back operation. This can further alleviate the problem of abnormal interface response on electronic devices and improve the user experience.

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

[0016] Considering that users can switch between the first application displayed on the first screen via a back action on an electronic device, this design allows the device to switch the interface of the first application indicated by the back action on the first screen, since the focused window of the electronic device is the window node attached to the container node of the first screen. This alleviates the situation where the user-triggered back action on the first screen is unresponsive. Therefore, it further mitigates abnormal interface response on the electronic device and improves the user experience.

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

[0018] Considering that users may use the volume keys on their electronic devices to turn pages while reading ebooks, this design allows the phone to respond to user volume key presses and turn the current page of the ebook displayed on the first screen. Since the focused window of the electronic device is the window node attached to the container node of the first screen, the phone can respond to these volume key presses to turn the current page of the ebook displayed on the first screen.

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

[0020] In another possible design of the first aspect, the above-mentioned response to a preset target operation, the electronic device displays a QR code of the second application on the second screen, including: in response to the preset target operation, the electronic device displays the QR code of the second application on the second screen, and displays a second screen display control on the first screen. The above-mentioned, at a third time point, in response to an event that ends the display of the second screen, the second screen goes black, including: at the third time point, based on a removal operation of the second screen display control, the second screen goes black; after the third time point, the first screen does not display the second screen display control.

[0021] In this design, users can control the QR code displayed on the second screen to be turned on or off using the controls shown on the first screen, which can improve the user experience.

[0022] In another possible design of the first aspect, the electronic device responds to an event that ends the display of the second screen by turning the second screen black, including: the second screen turning black after the QR code of the second application has been scanned by the electronic device. Alternatively, the second screen turning black occurs when the duration for which the electronic device displays the QR code of the second application on the second screen exceeds a preset duration (e.g., 3 seconds, 5 seconds, 10 seconds).

[0023] In another possible design of the first aspect, the target operation includes a tapping action 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.

[0024] Secondly, another interface display method is provided, which can be applied to electronic devices including displays (e.g., mobile phones, tablets, etc.); the display area of ​​the display includes a first screen and a second screen, the display of the electronic device is in a folded state, and the display orientations of the first screen and the second screen are opposite. The method includes: at a fourth time point, the electronic device displays the interface of a third application on the first screen. At the fourth time point, the root node attaches a container node of the first screen. At a fifth time point, in response to a preset target operation, the electronic device displays a QR code of the fourth application on the second screen and creates a container node of the second screen attached to the root node. The fifth time point is later than the fourth time point. At a sixth time point, in response to an event that ends 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.

[0025] In the above method, the electronic device can delete the container node of the second screen when the second screen is black. This allows the focus window to switch 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. This can alleviate the situation of abnormal interface response and improve the user experience.

[0026] Thirdly, this application provides an electronic device comprising: a memory, one or more processors, and a Bluetooth module; the memory is coupled to the processor; wherein the memory stores computer program code, which includes computer instructions; when the computer instructions are executed by the processor, the electronic device performs the method provided by the first aspect and any possible design of the first aspect; or performs the method provided by the second aspect and any possible design of the second aspect.

[0027] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed on an electronic device, cause the electronic device to perform the methods provided by the first aspect and any possible design of the first aspect; or cause the electronic device to perform the methods provided by the second aspect and any possible design of the second aspect.

[0028] Fifthly, this application provides a computer program product containing instructions that, when the computer program product is run on an electronic device, enables the electronic device to perform the methods provided by the first aspect and any possible design of the first aspect; or enables the electronic device to perform the methods provided by the second aspect and any possible design of the second aspect.

[0029] The technical effects of any of the design methods in aspects three through five can be found in the technical effects of different design methods in aspect one, and will not be repeated here. Attached Figure Description

[0030] Figures 1A-1D A schematic diagram of the form of a group of electronic devices provided in the embodiments of this application;

[0031] Figure 2 A schematic diagram illustrating a usage scenario provided in an embodiment of this application;

[0032] Figure 3 A schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application;

[0033] Figure 4 A schematic diagram of the software structure of the electronic device provided in the embodiments of this application;

[0034] Figure 5 A schematic diagram illustrating a method flow for displaying an interface according to an embodiment of this application;

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

[0036] Figure 7 A schematic diagram illustrating another interface display method flow provided in an embodiment of this application;

[0037] Figure 8 A schematic diagram illustrating the logical relationship of tree nodes provided in an embodiment of this application;

[0038] Figure 9 A schematic diagram illustrating the positional order of container nodes provided in an embodiment of this application;

[0039] Figure 10 A schematic diagram illustrating the changes in the logical relationships of tree nodes provided in an embodiment of this application;

[0040] Figure 11 A schematic diagram illustrating yet another change in the logical relationship between tree nodes provided in an embodiment of this application;

[0041] Figure 12A and Figure 12B This is a set of usage scenario diagrams;

[0042] Figure 13 A schematic diagram illustrating another interface display method flow provided in an embodiment of this application;

[0043] Figures 14A-14G A schematic diagram of a set of user graphical interfaces provided in the embodiments of this application;

[0044] Figure 15 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0045] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of the embodiments of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer 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, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0046] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0047] With the diversification of user demands for electronic devices, foldable screen electronic devices, combining large screens and convenience, have become widely popular. The foldable screen of an electronic device can be folded to form at least two display areas. For example, a foldable screen can be folded along a folding edge or 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 an outward-folding foldable screen (referred to as an outward-folding foldable screen), and the other is an inward-folding foldable screen (referred to as an inward-folding foldable screen). Taking the foldable screen forming a first screen and a second screen as an example, after an outward-folding foldable screen is folded, the display direction of the first screen and the display direction of the second screen are opposite, which is the orientation 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 aforementioned first screen and second screen are two different display areas within the same flexible screen.

[0048] The electronic devices involved in this application mainly take electronic devices with outward-folding screens as an example. Exemplarily, an outward-folding screen can include both vertical and horizontal folding methods. Vertical folding refers to folding the screen of the electronic device outwards vertically. Horizontal folding refers to folding the screen of the electronic device outwards horizontally. This application embodiment uses the horizontal outward folding of the screen of an electronic device as an example. It should be noted that the vertical and horizontal folding methods can be designed according to specific uses, and this application embodiment does not impose any limitations on them.

[0049] For example, Figure 1A The diagram shows the electronic device in its unfolded state (or simply unfolded state). As can be seen, the electronic device includes a first screen and a second screen. In the unfolded state, the first and second screens can form a relatively large display screen to show the user interface. The first and second screens can be aligned along a folding axis or folding edge (…). Figures 1A to 1D (The folding shaft is used as an example to illustrate folding.)

[0050] For example, in Figure 1A In this configuration, 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 achieve the following: Figure 1B The state shown. For example, in Figure 1B In the middle, the second screen can be folded further along the direction shown in 1c to obtain... Figure 1C The folded state shown (can be simply referred to as the folded state). Figure 1C The image shows the second screen in its folded state. The first screen in its folded state can be seen exemplarily in [reference needed]. Figure 1D .

[0051] For example, the first screen mentioned above can be called the main screen of the electronic device, and the second screen mentioned above 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 face away from each other. Generally, the first screen (main screen) faces the user and the second screen faces away from the user. Therefore, the second screen can also be called the back screen.

[0052] It is understandable that the above Figures 1A to 1D The examples shown are merely illustrative and do not constitute a limitation on the embodiments of this application. Exemplarily, in some other embodiments, in addition to the first and second screens described above, the electronic device may include other displays, and the embodiments of this application do not impose any limitations on this.

[0053] When a user uses an electronic device with its display folded, there are instances of abnormal interface response when using the first and second screens for display, resulting in a poor user experience.

[0054] For example, when a user uses the back-screen code display function on an electronic device, after the code display ends (i.e., the second screen goes black), if the user performs a back operation on the first screen of the electronic device, the device will become unresponsive. In other words, after the second screen of the electronic device goes black, if the user does not want to view the interface of the first application displayed on the first screen (e.g., the e-book reading interface of an e-book application), and the user triggers a back operation on the electronic device (e.g., clicking the back button, swiping left to go back, or swiping right to go back), the first screen of the electronic device will remain unresponsive.

[0055] In view of this, embodiments of this application provide an interface display method, the method comprising: at a first time point, an electronic device displays the interface of a first application on a first screen. At a second time point, in response to a preset target operation (e.g., a back screen tap operation), a QR code of a second application is displayed on the second screen; the second time point is later than the first time point. Between the first and second time points, 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 attached to the root node. At a third time point, in response to an event that ends the display of the second screen, the second screen goes black; the third time point is later than the second time point. Between the second and third 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 first application. After the third time point, the first screen displays the interface of the first application, and the container node of the first screen is above the container node of the second screen.

[0056] In this method, when the second screen is black, the electronic device can adjust the container node of the first screen to be above the container node of the second screen. This allows the focus window to switch to the first screen with the container node above it in a timely manner, so that the interface displayed on the first screen can respond to the user's operation. This can alleviate the situation of abnormal interface response and improve the user experience.

[0057] As you can understand, the aforementioned focus window refers to the window that is displayed in the foreground of the electronic device and receives input events (such as a back operation) directed at it. Typically, there is only one focus window on an electronic device; these focus windows can be activity windows, dialog windows, etc.

[0058] For example, see Figure 2 The interface display method provided in this application embodiment can be applied to the process of a user using 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, tablet computer, wearable device, smart screen, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), or other electronic devices with outward-folding screens; it can also be an in-vehicle computer, vehicle-mounted computer, or other in-vehicle device with an outward-folding screen; or it can be some IoT devices with outward-folding screens. This application embodiment does not impose any limitations on the product form of the electronic device.

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

[0060] For example, see Figure 3The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

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

[0062] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, memory, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0063] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

[0064] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the processor 110 may include one or more interfaces. 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, etc.

[0065] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may 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 miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

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

[0067] Pressure sensor 180A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, pressure sensor 180A may be disposed 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 based on pressure sensor 180A. Electronic device 100 may also calculate the touch position based on the detection signal from pressure sensor 180A.

[0068] For example, electronic device 100 can detect a user-triggered left swipe (swipe) back operation / right swipe (swipe) back operation via pressure sensor 180A.

[0069] The 180E accelerometer can detect the magnitude of acceleration of electronic device 100 in various directions (typically three axes). When electronic device 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the posture of electronic devices and applied to applications such as screen orientation switching and pedometers.

[0070] For example, electronic device 100 can detect a user-triggered tap on the back screen via accelerometer 180E.

[0071] Touch sensor 180K, also known as a "touch panel," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touch screen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0072] For example, electronic device 100 can detect a user-triggered left swipe (swipe) back operation / right swipe (swipe) back operation via touch sensor 180K.

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

[0074] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100.

[0075] For example, electronic device 100 can detect a user-triggered key press operation via key 190.

[0076] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This embodiment of the invention uses a layered architecture of Android. TM Taking the system as an example, the software structure of electronic device 100 is illustrated. A layered architecture divides the software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. For an example, see [link to example]. Figure 4 Android TM The system is divided into five layers, from top to bottom: the application layer, the application framework layer, the Android runtime (Android...). TM The runtime and system libraries, the hardware abstraction layer (HAL), and the kernel layer.

[0077] Understandable, Figure 4 The software architecture shown does not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer architectural layers than shown, or combine certain architectural layers, or split certain architectural layers, etc. For Android... TM The system can also be divided into other layers, such as: application layer, application framework layer, native layer, and kernel layer. Furthermore, different operating systems may have different layer divisions. Specifically, the operating system can be divided into different layers based on the actual usage scenario.

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

[0079] The application layer may further include a tap service, which can be used to display the target function code on the back screen of the electronic device. Its specific implementation can be found in the relevant description below, and will not be detailed here. For example, the target function code can be a QR code, barcode, etc.; for instance, a QR code can be a payment code, a transit code, or any identification code, etc., and this application embodiment does not impose any limitations on this.

[0080] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

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

[0082] A system server is a process that provides many subsystem services. Each subsystem service runs as a thread, waiting for requests from applications, processing the requests, and then 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).

[0083] WMS can be used for window management, window animation management, surface management, and as a relay station for input systems. NMS enables applications to display notification information in the status bar, which can be used to convey informative messages and can disappear automatically after a short pause without user interaction. AMS can be used for the startup, switching, and scheduling of system components (e.g., activities, services, content providers, and broadcast receivers), as well as the management and scheduling of application processes. IMS can be used to manage system input, such as touchscreen input, keypad input, and sensor input. IMS retrieves events from input device nodes (e.g., sensor modules, keypad modules, etc.) and, through interaction with WMS, distributes the events to windows in WMS. The media server is responsible for playing audio and video, as well as the processes of taking photos and recording videos.

[0084] The IMS (Input Event Management System) can include: an input event hub (eventub) component, an input event reader service component, and an input event dispatcher service component. The input event hub receives input events sent by the Hardware Abstraction Layer (HAL). The input event acquisition service retrieves input events from the input event hub and sends them to the input event dispatcher service. The input event dispatcher service receives input events sent by the input event acquisition service and associates them with the focus window. In this way, the WMS (Windows Management System) can obtain the input events corresponding to the focus window from the IMS. The input events can then be distributed to the focus window for processing through the interaction between the WMS and IMS.

[0085] For example, WMS can be used to manage the focus window and set the focus window in the input event dispatcher service component. The inputflinger can include the input event dispatcher service component.

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

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

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

[0089] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0090] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

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

[0092] The Hardware Abstraction Layer (HAL) is an abstraction layer that sits between the kernel layer and upper layers. It encapsulates kernel-level drivers to provide a unified interface to upper layers. This allows upper-layer applications to abstract away the underlying hardware implementation details without needing to know the specifics of how the lower-level hardware works.

[0093] The Hardware Abstraction Layer (HAL) provides a standard interface to expose device hardware functionality to higher-level application framework layers. The HAL contains multiple library modules, each implementing an interface for a specific type of hardware component. These library modules may include audio, Bluetooth, camera, sensor, and button modules. Sensor modules may include, for example, accelerometer, magnetic field, orientation, gyroscope, ambient light, pressure, temperature, and proximity sensors. When the application framework layer requests access to the device hardware, the system loads the corresponding library module for that hardware component. Manufacturers can define interfaces within the HAL.

[0094] For example, the aforementioned accelerometer module can be used to sense operations performed on an electronic device (such as a double-tap operation on the back screen). The aforementioned button module can be used to sense operations performed on buttons on an electronic device (such as pressing a button).

[0095] The kernel layer is the layer between hardware and software. At a minimum, the kernel layer contains display drivers, camera drivers, and audio drivers. It can also include sensor drivers, button drivers, and so on.

[0096] For example, the hardware of an electronic device, such as a button 190 or a touch sensor 180K, detects a user's return operation. The hardware abstraction layer of the electronic device (e.g., the button module, sensor module, etc. in the hardware abstraction layer) generates an input event for the window based on this return operation and sends the input event for the window to the IMS. Next, the input event dispatcher service component in the IMS obtains the focus window stored 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 dispatcher service component in the IMS obtains the focus window stored in the inputflinger and associates the input event for the window with the focus window. In this way, the WMS can obtain the input event for the window from the IMS and assign the input event for the window to the focus window.

[0097] Below, we will use Figure 2 In the illustrated usage scenario, taking a foldable screen mobile phone in a folded state as an example, the interface display method provided by the embodiments of this application will be described in detail with reference to the accompanying drawings. For ease of description, in the following text, a foldable screen mobile phone in a folded state can be simply referred to as a mobile phone, the first screen of the foldable screen mobile phone is referred to as the main screen, and the second screen of the foldable screen mobile phone is referred to as the back screen.

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

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

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

[0101] S500. Enable the back screen service (tap service) function on your phone.

[0102] To conveniently display a QR code while using a mobile phone, users can enable the phone's back screen service and configure related settings. Once the back screen service is enabled, users can control the display of QR codes through various operations. The back screen service function can be understood as the phone responding to a preset target operation (e.g., a back screen tap) by displaying a QR code or barcode for a preset application on the phone's back screen. This QR code can be a payment code, a transit code, or any identification code. The following embodiments of this application will use a QR code as an example, but this application does not impose limitations on this.

[0103] In some embodiments, users can enable the phone's back screen service function through the phone's settings interface.

[0104] For example, see Figure 6 The phone displays desktop 600; the user can click the settings icon 601 on desktop 600. In response to the user clicking the settings icon 601, the phone displays the settings menu interface 610. Next, the user clicks the foldable screen settings option 611 in the settings menu interface 610. In response to the user clicking the foldable screen settings option 611, the phone displays the foldable screen settings menu 620. The foldable screen settings menu 620 may include a switch 621 corresponding to "Back Screen Service". Then, the user clicks the switch 621. In response to the user clicking the switch 621, the phone displays the 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 application, BB application, CC application, etc.); and for each application, a "On / Off" switch 631 and a "Default Application" switch 632. The "On / Off" switch 631 can be used to enable / disable the function of displaying the QR code corresponding to the application. The "Default App" switch 632 is used to enable / disable the function of displaying the QR code of the app by default. For apps with the "Enable / Disable" switch 631 enabled, the phone can display their corresponding QR code through the back screen service function. For apps with the "Default App" switch 632 enabled, their corresponding QR code will be displayed by default (with priority).

[0105] The aforementioned applications that support back screen display can be understood as having the function of displaying QR codes, or as having a QR code display interface.

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

[0107] In some other embodiments, users can also activate the phone's back screen service function through the phone's voice recognition function.

[0108] For example, a user can activate the phone's voice recognition function using a wake word. Then, they can activate the phone's back screen service function using a voice command (such as "Activate back screen service function").

[0109] Understandably, in some other embodiments, the back screen service function on the phone is set up at the factory and is always on. In other words, users do not need to actively enable the back screen service function on their phones to use it.

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

[0111] The aforementioned target operation can be understood as a tapping operation performed by the user from the back of the phone's main screen towards the front. For example, this could be two consecutive taps on the back of the phone, a single tap, or a tap followed by a swipe. Exemplarily, the aforementioned two consecutive taps could be two taps within a preset duration. This preset duration could be 0.5 seconds, 1 second, or 2 seconds, etc., and this embodiment does not impose any limitations on this.

[0112] It is understood that the aforementioned target operation can be pre-set, and specifically, it can be any pre-set operation; for example, it can be a tapping, swiping, or dragging operation on the back screen of the mobile phone, or any combination thereof. The specific design can be tailored to actual usage needs, and this application embodiment does not impose any limitations on this. For ease of description, in the following embodiments of this application, the technical solution provided by this application embodiment will be described using the target operation of two consecutive taps on the back screen of the mobile phone (hereinafter referred to as the back screen tapping operation) as an example.

[0113] In some embodiments, the mobile phone can detect the back-screen tap operation using an accelerometer. For example, the mobile phone can use a system call to enable the accelerometer driver to receive the back-screen tap operation. Then, the mobile phone uses a system call to the sensor module of the hardware abstraction layer to identify the back-screen tap operation using a back-screen tap algorithm to obtain the back-screen tap event. The sensor module then sends the back-screen tap event to the back-screen service.

[0114] S502. The back screen service responds to the back screen tap event by calling the target application's SDK to send a message to pull up the target QR code.

[0115] The target application can be the default application set by the user in the back screen display application submenu of the foldable 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.

[0116] Understandably, a software development kit (SDK) can be a collection of development tools for creating application software, such as software packages, software frameworks, hardware platforms, or operating systems. An SDK can be the SDK used by an application. An SDK facilitates application creation through compilers, debuggers, or software frameworks. Alternatively, an SDK can be a collection of files providing application programming interfaces for a programming language, or it may include complex hardware capable of communicating with an embedded system. In this embodiment, the target QR code can be retrieved by calling the SDK of the target application.

[0117] For example, the back screen service can use the target application's SDK, and then send a message to the target application to pull up the target QR code through the SDK's interface.

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

[0119] Understandably, the target QR code mentioned above could be the QR code of the target application, such as the payment 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 phone by launching an application activity.

[0120] For example, the message that triggers the target QR code can be carried via an intent parameter. This intent parameter specifies the activity to be launched (hereinafter referred to as the target activity), meaning it includes a data description of the target activity. AMS can create a corresponding application activity record (activityrec ord) by parsing this intent parameter, thus enabling the target application to launch the target activity.

[0121] For example, the target QR code is required to be displayed on the back screen of the phone. The message that pulls 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). Therefore, after receiving the message, the AMS can determine whether the information is related to the back screen service based on the sender's identification information in the message. If so, it adjusts the display area associated with the target activity, setting the display area of ​​the target activity to the back screen. This ensures that when a window is subsequently created based on the target activity to display the target QR code, the display area of ​​that window is the back screen.

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

[0123] 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 process of the target application mentioned above) exists. If it does not exist, 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 can directly send a notification to the target application to start the target activity.

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

[0125] After the target application receives the notification, it creates an application activity thread (ActivityThread) to launch the target activity.

[0126] For example, the application activity thread mentioned above can launch the target Activity by calling functions such as onCreate() and onResume().

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

[0128] The target activity can draw its user interface based on the view tree of the aforementioned back-screen display window, so that the target QR code is displayed on the phone's back screen. For ease of description below, the view tree of the back-screen display window can be simply referred to as the back-screen window. For a more detailed introduction to the back-screen window, please refer to the following... Figure 8 The corresponding description will not be detailed here.

[0129] Thus, after the target application instructs WMS to create a background window through the target activity, the target application can draw the user's graphical interface in the background window and display the aforementioned target QR code through interface mapping services, display management services, etc. Specifically, the design can be tailored to actual usage requirements; this application embodiment does not impose any limitations in this regard.

[0130] In some embodiments, in step S506, the target service may also instruct the WMS to create a floating capsule window based on the target activity. This floating capsule window is used to display a back-screen display control on the phone's home screen. This back-screen display control can be used to switch the QR code displayed on the back screen for the back-screen service function. For example, this control can switch the QR code displayed on the back screen for the back-screen service function by switching the target application (e.g., switching the target application from AA to BB).

[0131] For example, the target service can also send the target activity to the back screen service, which instructs the WMS to create a floating capsule window based on the activity.

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

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

[0134] Among them, the container node (display), also known as the display container node, corresponds to a real or virtual display device (display area); it is used to manage the windows under that display device (display area).

[0135] For ease of explanation, the container node corresponding to the background window will be referred to as the target container node in the following text. The target container node can be understood as the container node that mounts the background window. Specifically, the correspondence between the background window and the container node is recorded in the target activity mentioned above.

[0136] It's understandable that WMS can manage windows in a hierarchical manner. A window, also known as a window node, has a parent node and several child nodes, used to manage elements displayed on the phone's screen (such as text size, color, image transparency, image contrast, dynamic effects, etc.). WMS's hierarchical window management improves its efficiency. In some embodiments, a window can also be called a task display area. A task can be understood as a stack of multiple activities, with the top activity corresponding to a window and displayed on the phone's screen. In other words, there is a correspondence between tasks and windows. Since windows are mounted on container nodes, tasks can also be mounted on container nodes.

[0137] In some embodiments, WMS can manage windows using a tree node structure. This tree node structure can include: a root node, a display node, and a window.

[0138] The root node, also known as the root window container, is the top-level part of the tree node structure. The root node primarily manages the container nodes (displays) attached to it; for example, managing the order of these container nodes (e.g., placing them at the top or bottom), adding / removing container nodes, etc. Container nodes, attached to the root node, are managed by the root node and also manage the windows attached to them; for example, managing the order of windows, adding / removing windows, etc. It should be noted that container nodes correspond to specific display areas on the phone; one container node corresponds to one display area on the phone. See the example below. Figure 8 The root node has two container nodes, display0 and display1, attached to it; these correspond to the phone's home screen and back screen, respectively. For example, display0 can correspond to the home screen, and display1 can correspond to the back screen.

[0139] Understandably, for phones with the back screen service enabled, since the phone needs to display content on the back screen, it sets up separate container nodes (display) in WMS to distinguish between the main screen and the back screen. Different windows are then attached to these container nodes to manage the content displayed on the phone's main screen / back screen (e.g., the interface displayed on the main screen / back screen, the elements within the interface, etc.).

[0140] It should be pointed out that Figure 8 This is merely a logical diagram; the actual design can be tailored to specific usage requirements, and this application does not impose any limitations on the embodiments thereof.

[0141] In one possible implementation, container nodes can exist as an array within the phone. For example, see... Figure 9 , Figure 9 The diagram illustrates the positional order of display0 and display1 from top to bottom. As can be seen, display0 is at the top, above display1. In other embodiments, "display0 above display1" can also be expressed as display0 preceding display1, or display0 preceding display1, etc. It is understood that if the top-to-bottom order is changed to bottom-to-top, then display0 will be below display1; or display0 will be after display1, or display0 following display1, etc. Specifically, the design can be tailored to actual usage requirements, and no restrictions are imposed here.

[0142] See you again 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 their corresponding indices. For example, if index 0 is greater than index 1, then display0 is considered to be above display1 in a top-to-bottom order. Furthermore, the statement that display0 is above display1 can also be expressed as display0 being in the correct position order.

[0143] Specifically, in step S5061, assuming the container node corresponding to the back screen window is display1, WMS can search under the root node to see if display1 exists. If it exists, step S5063 is executed; otherwise, steps S5062-S5063 are executed.

[0144] Understandably, the target container node on the phone may not exist when using the back screen service for the first time. This scenario can be understood as the phone being powered on for the first time and the target QR code being displayed on the back screen. Alternatively, if the target container node was removed after the phone displayed the QR code during the previous use of the back screen service, then the target container node may also not exist during this subsequent use.

[0145] Add the target container node in S5062.WMS.

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

[0147] S5063.WMS creates a back screen window and attaches it to the target container node.

[0148] For example, WMS can create a back screen window and mount the back screen window to display1.

[0149] The aforementioned back screen display window may include Figure 8 Window D in the middle can also include Figure 8 Windows D and E are shown in the diagram. Specifically, the design can be tailored to actual usage needs; this embodiment does not impose any limitations on this.

[0150] For example, suppose the back screen display window includes window D. Window D may correspond to the user interface of the target application, which includes the target QR code. For instance, if the target QR code is an AA payment code, then window D corresponds to the AA payment code interface. Suppose 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. This auxiliary interface is used to display together with the user interface of the target application to improve the display effect of the user interface. The auxiliary interface may be as follows: Figure 14B Regarding the 404 error and 4032 explanation of the QR code for the second application, please refer to the following for details. Figure 14B Related information.

[0151] After the background window is created in WMS, the target application can use interface mapping services, display management services, etc., to draw a graphical interface in the background window and display the target QR code. Additionally, the background window service can also draw other graphical interfaces (such as the auxiliary interfaces mentioned above) in the background window to display the target QR code on the phone, thereby improving the display effect of the target QR code. Specifically, the design can be tailored to actual usage needs, and this application embodiment does not impose any limitations in this regard.

[0152] This is understandable, as WMS works in conjunction with IMS 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. Then, after receiving an input event, IMS can send the input event to the focused window.

[0153] InputFlinger is the process within IMS used to manage the distribution of input events. InputFlinger includes the InputDispatcher service component; when an input event occurs on the phone, it is distributed to the corresponding focus window for processing via the InputDispatcher. In other words, WMS is used to maintain the focus window within InputFlinger.

[0154] Next, we will introduce the process by which WMS maintains the focus window in inputflinger during steps S501-S506.

[0155] In some embodiments, the WMS can determine the focus window based on the window's position order; after determining the focus window, the WMS updates the focus window to the inputflinger. For example, the WMS can designate the topmost window as the focus window.

[0156] For example, see Figure 10 The diagram shows the positional order from left to right, from top to bottom. Figure 10As shown in Part A of the diagram, 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 main screen of the phone is displaying an interface. Under display0, windows A, B, and C are mounted in order from top to bottom. Since the back screen of the phone is off, no windows are mounted under display1. WMS will set the topmost window under 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.

[0157] Specifically, WMS determines that window A is the top-positioned window mounted under the container node (display0). Then, WMS can update the window information by calling the updateInputFocusRequest process, updating the focused window (e.g., window A) to the inputflinger. In the updateInputFocusRequest process, WMS can execute the mDisplayContent.isOnTop() condition. If this condition is met, the setFocusedWindow() function is executed to update the focused window information to the inputflinger; if the condition is not met, the process ends, meaning the focused window is not updated. The input parameter for the aforementioned condition is the window's identifier.

[0158] Understandably, after determining the focus window, WMS can also validate the focus window (by verifying the focus window according to the above judgment conditions), which can improve the accuracy of the focus window setting.

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

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

[0161] In expression 1, "!" represents logical NOT, "&&" represents logical AND, and "==" checks if both sides of the equation are the same. "parent != null" means checking if the parent node is not null; if it is, it returns 1, otherwise it returns 0. "this" represents the identifier entered in the condition `mDisplayContent.isOnTop()`. "parent.getTopChild()" is a function that retrieves the top child node of the parent node. "parent.isOnTop()" checks if the parent node is at the top; specifically, it can be executed on the parent node: "parent != null && parent.getTopChild() == this" to determine if the parent node is at the top. The parent and child nodes mentioned above can be understood as a relative relationship of mounting and being mounted. For example, the parent node of window A is `display0`, and window A is a child node of `display0`.

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

[0163] During the execution of `mDisplayContent.isOnTop(window a)` in WMS, based on the operator precedence in the expression, WMS first executes `parent.getTopChild() == this`. Since the top child node of window A's parent node 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 window A's parent node `display0` is at the top.

[0164] During the execution of "parent.isOnTop(window a)" by WMS, WMS executes "parent.getTopChild(Display0) == this"; where "Display_0" is the identifier of display0; at this time, "this" is "Display_0". Since the top child node under the parent node of display0 is display0, "parent.getTopChild(Display_0)" outputs display0, meaning the value of "parent.getTopChild(Display_0) == this" is 1. Then, WMS executes "parent != null". Since the parent node of display0 is not null, the value of "parent != null" is 1. Therefore, the execution result of WMS executing "parent.isOnTop(window a)" is 1. In other words, the execution result of WMS executing mDisplayContent.isOnTop(window a) is 1&&1&&1, which is 1, and the condition is met.

[0165] After WMS executes mDisplayContent.isOnTop(window a), and determines that window A meets the condition, WMS executes the setFocusedWindow(window a) function to update the inputflinger with window A as the focus window.

[0166] See you again Figure 10 ,like Figure 10 As shown in part B, after step S505, because WMS creates a back screen window ( Figure 10 The code is represented as window D and window E in the diagram, and the phone displays the QR code on the back screen. WMS adjusts the position order of container nodes and windows. 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 inputflinger.

[0167] For example, after the WMS executes the condition `mDisplayContent.isOnTop(window d)` and passes, it updates the focused window to window D in the inputflinger using `setFocusedWindow(window d)`. Here, "window d" is the identifier of window D. Specifically, the process of WMS executing the condition `mDisplayContent.isOnTop(window d)` can be found in the above description of WMS executing the condition `mDisplayContent.isOnTop(window a)`, and will not be repeated here.

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

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

[0170] The event that ends the back screen display, also known as the back screen end event, is used to indicate that the mobile phone ends the back screen service function, and the mobile phone back screen stops displaying the target QR code. The back screen end event can be sent by the target application to the back screen service, generated by the back screen service, or sent by other modules in the mobile phone, such as the timer module; the specific design can be made according to actual usage needs, and this application embodiment does not impose any restrictions on this.

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

[0172] 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 phone's back screen is complete.

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

[0174] For example, after WMS successfully creates the background window, WMS can start a timer. The timer's timing period can be a preset timing period (e.g., 5 seconds, 10 seconds, etc.). After the timer reaches the timing period, the timer can send a background end event to WMS.

[0175] In some solutions, in response to an event that ends the back screen display, the back screen service can directly remove the back screen window via WMS. Thus, because 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.

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

[0177] After WMS removes the background window, because the window in WMS has changed, WMS will re-identify and update the focus window. WMS will then set the topmost window under root as the focus window. Figure 11As can be seen, since the container node at the top position has mounted windows, WMS can set the window at the top position that is mounted under the container node following the container node at the top position as the focus window. For example, window A can be set as the focus window.

[0178] For example, WMS can update window information through the updateInputFocusRequest process, updating the focused window to window A in the inputflinger. Within the updateInputFocusRequest process, WMS can execute the conditional statement `mDisplayContent.isOnTop(window a)`. If this condition is met, WMS executes the `setFocusedWindow(window a)` function to update the focused window information in the inputflinger; if the condition is not met, the updateInputFocusRequest process ends, and WMS does not update the focused window. The conditional statement for `mDisplayContent.isOnTop()` can be found in Expression 1 above.

[0179] For example, when WMS executes the condition "parent.isOnTop()" in `mDisplayContent.isOnTop(window a)`, the parent node of window A, `display0`, is not the top container node under the root node; the top container node under the root node is `display1`. This causes the value of "parent.getTopChild(Display_0) == this" to be 0, resulting in a conditional result of 1 && 1 && 0; the condition fails. WMS does not update the inputflinger to show window A as the focused window.

[0180] In other words, the focus window in the inputflinger is still window D, which was updated by WMS before step S507. In this case, if a functional module in the phone's hardware abstraction layer (such as a button module, sensor module, etc.) generates an input event for the window in response to the user's return operation, and then sends this input event to IMS, the focus window setting becomes unreasonable because window D is the focus window in the IMS's inputflinger. This results in the WMS failing to update the focus window to window A in the IMS's inputflinger. Consequently, the input event for the window fails to be sent to the focus window. This leads to the input event for the window not responding on the phone, which affects the user experience.

[0181] The input events for the window mentioned above can include: return operations (such as clicking the return button, swiping left to return, swiping right to return, etc.) and key operations (such as pressing the volume up button, pressing the volume down button, etc.).

[0182] For example, see Figure 12A Assuming the back screen window is removed by WMS and the phone's back screen goes black, the user triggers a back operation on the phone (e.g., tapping the back button, swiping left to go back, swiping right to go back). The user uses this back operation to switch the currently displayed page (e.g., the e-book display page) to another page (e.g., the phone's desktop). The phone's IMS receives the back operation sent by the button module and passes it to the focused window in the IMS's inputflinger. From the above... Figure 11 As the description indicates, WMS did not update the focused window (window A) to the inputflinger, and the focused window in IMS's inputflinger remained window D. IMS would dispatch the return operation to window D in WMS. However, since window D does not exist in WMS, it has been removed by WMS. Therefore, the return operation failed to reach the focused window. Consequently, the phone cannot respond to the return operation, and the phone becomes unresponsive.

[0183] Understandably, if a user presses a volume button on their phone, the phone will also perform the actions described above. Figure 12A For processes with similar characteristics, the phone may also become unresponsive. This will degrade the user experience.

[0184] Therefore, in some other technical solutions provided in the embodiments of this application, after WMS removes the back screen window and the phone's back screen goes out, WMS can adjust the position order of the container nodes. This allows WMS to successfully update the focused window to the IMS's inputflinger after removing the back screen window. The focused window can then receive input events for that window, which will trigger a response on the phone, improving the user experience.

[0185] For example, see Figure 12B After WMS removes the back screen window and the phone's back screen goes out, WMS adjusts the order of container nodes (e.g., moving the container node corresponding to the back screen window to the bottom). When a user triggers a back operation on the phone, controlling the phone to switch between the currently displayed page (e.g., the e-book display page) and other pages (e.g., the phone's desktop), the phone's IMS receives the back operation from the button module and passes it to the focused window in the IMS's inputflinger. Because WMS has adjusted the order of container nodes, allowing it to update the focused window (window A) to the inputflinger, window A becomes the focused window in the IMS's inputflinger. The IMS then distributes the back operation to window A. Thus, window A receives the back operation, and the phone responds by displaying the desktop.

[0186] Alternatively, after WMS removes the back screen window and the phone's back screen goes black, WMS adjusts the order of container nodes (e.g., moving the container node corresponding to the back screen window to the bottom). When a user presses a volume button on the phone, controlling the phone to switch ebook pages (e.g., switching from the current page to the next page), the phone's IMS receives the volume button press notification from the button module and passes it to the focused window in the IMS's inputflinger. Because WMS has adjusted the container node order, allowing it to update the focused window (Window A) to the inputflinger, Window A becomes the focused window in the IMS's inputflinger. The IMS then distributes the return operation to Window A. Thus, Window A receives the volume button press notification, and the phone can respond by turning the ebook page displayed on the main screen.

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

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

[0189] Upon receiving this message, S5071.WMS obtains the identifier of the target container node.

[0190] For example, WMS can obtain the identifier of the target container node through the getDisplayContentOrCreate function.

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

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

[0193] For example, WMS uses the displayContent.forAllRootTasks function to assign the identifier of each task mounted on the target container node and add the identifier of each task to the aforementioned back screen window list.

[0194] S5073.WMS iterates through the task identifiers in the back screen window list and removes the identified identifiers.

[0195] For example, WMS can remove the traversed identifiers using the removeImmediately function.

[0196] For example, WMS can search for window node identifiers in the back screen window list, apply the `removeImmediately` function to the found identifiers, and remove the identifiers that used the `removeImmediately` function from the list until the back screen window list is empty, meaning the back screen window list does not include window node identifiers.

[0197] Understandably, for a task attached to a window node, if the task is removed, the window node is also removed. Therefore, in some embodiments, a background window can be removed using a task.

[0198] S5074A.WMS moves the target container node to the bottom position sequentially.

[0199] For example, WMS can use the positionChildAt() function to move the target container node sequentially to the bottom in WMS.

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

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

[0202] For example, after step S5074A, the WMS can update the window information through the updateInputFocusRequest procedure, updating the focused window to window A in the inputflinger. In the updateInputFocusRequest procedure, the WMS can execute the condition mDisplayContent.isOnTop(window a). If the condition is met, the WMS executes the setFocusedWindow(window a) function to update the focused window information in the inputflinger; if the condition is not met, the updateInputFocusRequest procedure ends, and the WMS does not update the focused window. The condition mDisplayContent.isOnTop() can be found in expression 1 above.

[0203] For example, when WMS executes the condition "parent.isOnTop()" in the `mDisplayContent.isOnTop(window a)` condition, because WMS moved the position of `display1` to the bottom in step S5074A, `display0` is the container node at the top of the root node. Thus, the value of "parent.getTopChild(Display_0) == this" is 1, resulting in a conditional result of 1&&1&&1; the condition passes. WMS then updates the focused window, window A, to the inputflinger.

[0204] In this way, after WMS removes the back screen window and the phone's back screen goes out, input events for the window can be passed to the focused window via IMS. This allows the phone to respond to the user's back operation and switch the currently displayed page (e.g., switching the e-book display page to the phone's desktop).

[0205] In some embodiments, the execution process of steps S5071A-S5074A described above can also be encapsulated into a function, such as the 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 mentioned above. In this way, the back screen service can instruct the WMS to remove the back screen window by calling the removeAllTaskForDisplay() function.

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

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

[0208] For example, WMS obtains all container nodes mounted under the root node, and then obtains the container nodes other than the target container node, i.e., non-target container nodes. WMS then moves each non-target container node up until the position of each non-target container node is above the position of the target container node.

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

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

[0211] In some embodiments, after performing step S5070, WMS does not perform steps S5071-S5073; WMS can remove the target container node based on the message to remove the back screen window.

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

[0213] For example, WMS can obtain the identifier of the target container node using the `getDisplayContentOrCreate` function. Then, WMS removes the target container node using the `removeImmediately()` function. Understandably, for windows attached to a container node, if the container node is removed, the windows attached to it will also be removed. Thus, because the target container node is removed, WMS will not fail the condition check when updating the focused window in the inputflinger due to interference from the target container node. WMS can then update the focused window in the inputflinger. Therefore, input events for the window can be passed to the focused window.

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

[0215] Next, we will use Figure 2 The scenario shown is an example of a user reading an e-book on a mobile phone. This article describes the user interface displayed on the mobile phone during the implementation of the interface display method provided in the embodiments of this application.

[0216] At the first point in time, the phone's main screen displays the first interface 401 of the first application, and the phone's back screen goes out.

[0217] The first application can be an application the user is currently using on their phone, and the second application can be the aforementioned target application. For example, suppose the user is using their phone to read an ebook; the first application could be an ebook application, and the second application could be the application the user is currently using on their phone. Figure 6 The default application (e.g., AA application) is set in the application submenu 633 on the back screen display.

[0218] For example, the user interfaces for the main screen and the back screen can be found separately. Figure 14A (a) and (b) in the text. Figure 14A In (a), the phone's home screen displays the first interface 401 of the first application (e.g., the e-book viewing interface of an e-book application). Figure 14A In (b), the back screen of the phone is off, meaning that no user interface of any application is displayed.

[0219] Understandably, in some embodiments, at the first time point, the back screen of the phone may remain on, displaying a pure black user interface.

[0220] Subsequently, at the second time point, the phone responds to the user's target operation by displaying the QR code of the second application on the phone's back screen. The second time point is later than the first time point mentioned above, and the target operation can be a tap on the back screen. For an explanation of the target operation, please refer to the description above; it will not be repeated here. Specifically, the detailed steps of this process can be found in the descriptions of steps S501-S506 above; they will not be repeated here.

[0221] For example, see Figure 14B (a) and (b) in the text. Figure 14B In (a), the phone's home screen displays the first interface 401 of the first application (e.g., the e-book viewing interface of an e-book application). Figure 14B In (b), the back screen displays a QR code 4032 for the second application (e.g., the QR code for application AA). In some embodiments, at the second time point, the main screen of the phone may also display a notification 4011 indicating that the QR code is being displayed on the back screen. This notification 4011 may include text indicating that the QR code is being displayed on the back screen (e.g., "Back screen displaying").

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

[0223] Understandably, in some embodiments, at the second time point, the phone's back screen may also display information related to the second application (e.g., application AA) to prompt the user. See again for examples. Figure 14B ,exist Figure 14B In (b), the area 403 displaying the QR code of the second application is white. This area 403 may include a payment barcode 4031 and a payment QR code 4032. Alternatively, the back screen of the phone may also display a description 404 about the QR code 4032 of the second application. This description 404 may include the icon 4041 of the second application and the name 4042 of the displayed QR code. The name 4042 of the QR code may, for example, be "QR code of AA application," etc. This embodiment of the application does not limit the textual description of the QR code's name. For example, assuming the QR code of the AA application is a transit code, then the name 4042 of the QR code could be "AA application transit code." As another example, assuming the QR code of the AA application is a payment code, then the name 4042 of the QR code could be "AA application payment code."

[0224] Then, at time point 3, in response to the event of ending the back screen display, the phone's back screen turns off. This third time point is later than the second time point mentioned above.

[0225] Specifically, the detailed steps of this process can be found above. Figure 13 The corresponding descriptions; and the user graphical interface displayed on the mobile phone at time point 3 can be referred to above. Figure 14A The details and related descriptions will not be repeated here.

[0226] In some embodiments, the first time point mentioned above may be referred to as the first time point or the fourth time point; the second time point mentioned above may be referred to as the second time point or the fifth time point; and the third time point mentioned above may be referred to as the third time point or the sixth time point. It should be noted that between the first and second time points, the phone's back screen is off. And, see above... Figure 10 Regarding the description in Part A, between time point 1 and time point 2, the container node of the main screen (e.g., display0) is above the container node of the back screen (e.g., display1). Between time point 2 and time point 3, see the above. Figure 10 As described in Part B, the container node of the back screen (e.g., display1) is above the container node of the main screen (e.g., display0). After the third time point, because the phone executes steps S5070-S5073 and S5074A or steps S5070-S5073 and S5074B, the position order of the container nodes is adjusted; for example, the position order of the target container node (e.g., the container node of the back screen) is moved to the bottom, or the position order of the non-target container node (e.g., the container node of the main screen) is moved above the position order of the target container node. This results in the container node of the main screen (e.g., display0) being above the container node of the back screen (e.g., display1), so WMS can execute the updateInputFocusRequest process to set the focus window in IMS. In this way, input events for the window can be given to the focus window.

[0227] Understandably, because at time point 3, the phone executes steps S5070-S5073 and S5074A or steps S5070-S5073 and S5074B, the container node of the main screen (e.g., display0) will be above the container node of the rear screen (e.g., display1), as described above. Figure 9In other words, based on the back screen end event that occurs at time point 3, the phone can adjust the relationship between the main screen container node and the back screen container node, making their relationship as follows: Figure 9 As shown.

[0228] In this method, when the second screen is black, the electronic device can adjust the container node of the first screen to be above the container node of the second screen. This allows the focus window to switch to the first screen with the container node above it in a timely manner, so that the interface displayed on the first screen can respond to the user's operation. This can alleviate the situation of abnormal interface response and improve the user experience.

[0229] For example, suppose a user triggers a back action on the phone after time point 3. Since the container node of the main screen (e.g., display0) is above the container node of the back screen (e.g., display1), the phone can satisfy the update condition for the focus window (e.g., the condition corresponding to expression 1 above). The phone can then set the window node under the container node of the main screen as the focus window. In this way, the user-triggered back action can be passed to the focus window. The phone's main screen will then respond to the back action by switching interfaces (e.g., switching from the interface of the first application to the main interface; or switching from the current interface of the first application to another interface of the first application).

[0230] For example, suppose the first application mentioned above is a reading application (e.g., an e-book application), and its interface is a reading interface. That is, the phone's home screen displays the reading interface of the reading application. Since most reading interfaces have volume button page-turning functionality, after time point 3, the user triggers a volume button press on the phone. Because the home screen's container node (e.g., display0) is above the back screen's container node (e.g., display1), the phone can satisfy the focus window update condition (e.g., the condition corresponding to expression 1 above). The phone can then set the window node attached to the home screen's container node as the focus window. Thus, the user's volume button press can be passed to the focus window. The reading interface of the reading application displayed on the phone's home screen can then respond to the volume button press by performing page-turning operations (e.g., turning the current page to the next page or turning the current page to the previous page).

[0231] In some embodiments, at a third time point, in response to an event indicating the end of the back screen display, the phone's back screen turns off. The WMS in the phone can remove the container node from the back screen. Thus, because the target container node is removed, when WMS updates the focused window in the inputflinger, it will not fail the condition check due to interference from the target container node. WMS can then update the focused window in the inputflinger. Therefore, input events for the window can be passed to the focused window.

[0232] For example, in a 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 phone before time point 2, the phone can establish the back-screen container node at time point 2 through steps S501-S505, and steps S5061, S5062, and S5063. In this scenario, before time point 2, the phone has a main screen container node but no back-screen container node. Between time point 2 and time point 3, the back-screen container node is above the main screen container node. At time point 3, if the phone removes the back-screen container node, then the phone has a main screen container node but no back-screen container node; if the phone does not remove the back-screen container node (e.g., the phone executes steps S5070-S5073 and steps S5074A or S5074B), then the main screen container node is above the back-screen container node.

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

[0234] The event that ends the back screen display can be generated by the back screen service or sent by the target application (AA application) to the back screen service.

[0235] When a phone uses a back-screen display control on the main screen to assist with back-screen service functions, the user can use this control to close the QR code of a second application displayed on the phone's back screen. In other words, the event that ends the back-screen display can be generated by the back-screen service.

[0236] For example, see Figure 14D In (a) of the diagram, in response to a long press operation by the user on the back screen display control 402B, a delete icon 4013 is displayed in the first area 4012 of the phone's main screen, and the back screen display control 402B becomes movable. It is understood that the movable back screen display control 402B can follow the user's touch on the phone's main screen. The first area 4012 can be any preset area on the phone's main screen, such as the middle area at the bottom of the main screen or the middle area at the top of the main screen. The delete icon 4013 can also be an icon of a preset shape, such as a trash can icon. Specifically, the first area 4012 and the delete icon 4013 can be set according to actual usage needs, and this embodiment does not impose any restrictions on this. Subsequently, in response to the user moving the movable back screen display control 402B to the first area 4012, the back screen service generates an event indicating that the back screen display has ended. After the back screen service generates an event indicating the end of back screen display, the QR code for the second application displayed on the phone's back screen will be closed, for example, by... Figure 14D (b1) in the diagram changes to (b2); specifically, please refer to step S507 above. In this way, the user can actively trigger the QR code for the second application displayed on the back screen of the phone from the phone's home screen. Considering that users may sometimes accidentally trigger the target operation, the QR code is displayed on the back screen of the phone; at this time, the user can easily turn off the QR code displayed on the back screen through a simple operation on the home screen, improving the user experience.

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

[0238] In some embodiments, the above Figure 14B After the QR code shown in (b) is successfully scanned, the mobile phone can display information such as "Scan completed" or "Payment successful" on the back screen to indicate that the QR code has been successfully scanned. Optionally, successful scanning of the QR code can also indicate that the corresponding operation has been completed (such as a payment operation, which is not limited in this embodiment). For example, see [link to relevant documentation]. Figure 14F and Figure 14EAs shown. "Scanned successfully" or "scanning completed" means that the QR code has been successfully scanned by another device.

[0239] Figure 14E As shown Figure 14B After the QR code shown in (b) is successfully scanned, the user interface displayed on the back screen will redirect. As can be seen, the user interface after the redirection may include the icon of the first application 4034, the words "Payment Successful" 4035, the payment amount (for example, 100 yuan) 4036, the payment method 4037, and the recipient 4038, etc.

[0240] Figure 14F As shown Figure 14B After the QR code shown in (b) is successfully scanned, the interface redirects to the user interface displayed on the back screen. It can be seen that this redirected user interface displays the message "Scan completed" 407.

[0241] Understandable, Figure 14F and Figure 14E The examples shown are merely illustrative and do not constitute a limitation on the embodiments of this application. In specific implementations, the interface that appears after the QR code is successfully scanned can be other user interfaces, and this application embodiment does not impose any restrictions on this. Alternatively, the user interface after the jump can display other interface elements, and this application embodiment also does not impose any restrictions on this.

[0242] In some embodiments, at the third time point mentioned above, in response to an event sent by the target application to end the back screen display, the phone's back screen turns off; and information indicating that the QR code scanning is complete is displayed in the back screen display control 402B on the phone's main screen. That is, in response to... Figure 14B If the QR code shown in (b) is successfully scanned, the phone can display a notification to the user in the back screen control of the main screen that the QR code displayed on the back screen of the phone has been successfully scanned.

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

[0244] It is understood that, in order to achieve the above functions, the electronic device includes hardware and / or software modules that perform the respective functions. Based on the algorithmic steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by 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 conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.

[0245] This embodiment can divide the electronic device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0246] This application also provides an electronic device, such as... Figure 15 As shown, the electronic device may include one or more processors 2001, memory 2002, and communication interfaces 2003.

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

[0248] The communication interface 2003 is used for data transmission with other devices. The memory 2002 stores computer program code. The computer program code includes computer instructions, which, when executed by the processor 2001, cause the electronic device to perform device authentication as described in this embodiment.

[0249] The processor 2001 can 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 can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with this disclosure. The processor can also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0250] The bus 2004 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The aforementioned bus 2004 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 15 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0251] This application also provides a computer-readable storage medium storing computer program code. When the processor executes the computer program code, the electronic device executes the relevant method steps in the above method embodiments.

[0252] This application also provides a computer program product that, when run on a computer, causes the computer to execute the relevant method steps described in the above method embodiments.

[0253] The electronic devices, computer-readable storage media, or computer program products provided in this application are all used to perform the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0254] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0255] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0256] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0257] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0258] If the integrated unit is implemented as 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 embodiments of this application, in essence, or the part that contributes, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0259] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for displaying an interface, characterized in that, The method is applied to an electronic device, the electronic device including a display screen, the display area of ​​the display screen including a first screen and a second screen, the display screen being in a folded state, the display orientations of the first screen and the second screen being opposite, and the method including: At the first point in time, the interface of the first application is displayed on the first screen; At a second time point, in response to the target operation, the interface 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 attached to the root node; At a third time point, in response to an event that ends the display on the second screen, the second screen is controlled to turn 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.

2. The method according to claim 1, characterized in that, The method further includes: Based on the event that ends the display of the second screen, the container node of the second screen is moved 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 is attached to the window node corresponding to the display task; The step of adjusting the container node of the second screen to the bottom includes: Remove the displayed task; Move the container node of the second screen to the bottom.

4. The method according to any one of claims 1-3, characterized in that, Between the first time point and the second time point, the focus window is the window node attached to the container node of the first screen; Between the second time point and the third time point, the focus window is the window node attached to the container node of the second screen; The method further includes: At the third time point, since the container node of the first screen is above the container node of the second screen, the update condition of the focus window is met, 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 includes: After the third time point, in response to the return operation, the interface of the first application displayed on the first screen is switched based on the window node attached to the container node of the first screen as the focus window.

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

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

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

9. The method according to any one of claims 1-3, characterized in that, The interface of the second application includes a QR code for the second application; the step of controlling the second screen to turn black in response to an event that ends the display of the second screen includes: Once the QR code for the second application has been scanned, the second screen is controlled to turn black. Alternatively, if the duration for which the QR code of the second application is displayed on the second screen exceeds a preset duration, the second screen can be controlled to turn black.

10. The method according to any one of claims 1-3, characterized in that, The target operation includes tapping from the back of the first screen to the front of the first screen.

11. A method for displaying an interface, characterized in that, The method is applied to an electronic device, the electronic device including a display screen, the display area of ​​the display screen including a first screen and a second screen, the display screen being in a folded state, and the display directions of the first screen and the second screen being opposite; the method includes: At the fourth time point, the interface of the 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 the 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 is created and mounted on the root node; the fifth time point is later than the fourth time point. At the sixth time point, in response to the event of ending the display of the second screen, the second screen is controlled to turn black; the sixth time point is later than the fifth time point. Between the fifth time point and the sixth time point, the container node of the second screen is above the container node of the first screen, and the first screen displays the interface of the third application. After the sixth time point, the first screen displays the interface of the third application.

12. The method according to claim 11, characterized in that, The method further includes: Based on the event that ends 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 is attached to the window node corresponding to the display task; The removal of the container node from the second screen includes: Remove the container node of the second screen that has the window node corresponding to the display task mounted.

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

15. A computer-readable storage medium, characterized in that, Includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1-13.

Images