Display method, terminal equipment and computer readable medium

Abstract

The invention relates to the technical field of terminals, in particular to a display method, terminal equipment and a computer readable medium. According to the method, an attribute configuration for prohibiting an operation of pulling down a status bar but displaying a banner notification is added, and an attribute corresponding to the operation of pulling down the status bar by terminal equipment such as a mobile phone and the like is decoupled from an attribute corresponding to displaying the banner notification; and the requirements of the user on immersive experience and the requirements of checking important notification messages in time are balanced. Even if the terminal equipment enters the notification forbidding state, the operation of pulling down the status bar is forbidden, but the banner notification can still be displayed. Therefore, the banner notification can be displayed for reminding according to user requirements in different immersive scenes, so that important notification messages are prevented from being missed, and the user experience is improved.

Description

Display method, terminal device, and computer-readable medium Technical Field

[0001] The present invention relates to the field of terminal technology, and in particular to a display method, a terminal device, and a computer-readable medium. Background Art

[0002] The status bar of a terminal device can display notification messages to convey notifications received during the operation of the system or installed applications (APPs). When the terminal device is in use with the screen unlocked, the status bar can display notification messages in the form of a banner. After a brief pause, the message automatically pulls up and is placed in the notification queue of the top status bar. The user can then view the pulled-up notification message by pulling down the top status bar. Furthermore, the terminal device can display notification messages even when the screen is locked. This allows users to be reminded to handle important notification messages in a timely manner, preventing them from being ignored and causing inconvenience.

[0003] In some display scenarios or display modes of terminal devices, such as when a user is using the secondary screen of a foldable device for immersive operations such as taking a selfie, the terminal device will enter a notification-disabled state, also known as an immersive state. In this state, the terminal device prohibits the user from pulling down the status bar. At the same time, the terminal device's status bar cannot display notification messages in the form of banner notifications, etc., which may cause the user to miss important notification messages, resulting in a poor user experience.

[0004] Summary of the Invention

[0005] The present invention provides a display method, terminal device, and computer-readable medium that enable the terminal device to disable the pull-down status bar and display a banner notification even when the terminal device enters a notification disabled state. This allows the terminal device to display a banner notification as a reminder based on user needs in different immersive scenarios, thereby avoiding missing important notification messages and improving the user experience.

[0006] In a first aspect, the present application provides a display method, applied to a terminal device, the terminal device including a display screen, the display screen including at least a first screen, a second screen, and a first camera, wherein the first screen and the first camera of the terminal device are respectively located on opposite sides of the terminal device; and, in an unfolded state of the terminal device, the first screen and the second screen are located on the same side of the terminal device; and in a folded state of the terminal device, the first camera and the second screen are located on the same side of the terminal device; and the method includes:

[0007] Based on the terminal device being in a folded state, displaying a first interface of a first application on a first screen;

[0008] At a first time point, receiving a first notification from a second application, and displaying a banner notification of the first notification on a first screen;

[0009] At a second time point, receiving a first operation of pulling down the status bar to display a notification list, wherein the notification list includes at least one notification option;

[0010] In response to the user clicking an option in the first notification, displaying a second interface of the second application;

[0011] After the user flips the phone, the third interface of the first application is displayed on the second screen;

[0012] At a third time point, a second notification of the second application is received, and a banner notification of the second notification is displayed on the second screen;

[0013] At a fourth time point, a second operation of pulling down the status bar is received, and the notification list is not displayed.

[0014] For example, the terminal device may be a foldable screen device, such as a foldable screen mobile phone. The first screen may be the main screen of the mobile phone, and the second screen may be the secondary screen of the mobile phone. The first camera may be the rear camera of the mobile phone. The first application may be a camera application, and the second application may be a phone, WeChat, or other similar application. TM Correspondingly, the first interface of the first application displayed on the first screen can be a shooting interface of the camera application. At the first time point, the mobile phone can use a banner notification to remind the user of the phone, WeChat TM The notification message sent by the application is the first notification mentioned above. At the second time point, the mobile phone can respond to the user's operation of pulling down the status bar, such as the first operation mentioned above, and display the notification list. In other embodiments, the mobile phone can also display the control center in response to the user's operation of pulling down the status bar, which is not limited here. It is understood that the first time point and the second time point mentioned above can be the same time point, or the first time point can be earlier than the second time point.

[0015] If the phone detects that the user clicks on the first notification option in the notification list displayed above, the corresponding application such as phone, WeChat, etc. can be opened. TMIf the mobile phone detects that the user flips the phone, it can display the shooting interface on the secondary screen (i.e., the second screen mentioned above). At this time, since the size of the secondary screen may be smaller than the size of the main screen, for example, the width of the secondary screen is narrower than the width of the main screen, in order to avoid errors in the related interfaces of the notification list, when the shooting interface is displayed on the secondary screen, the user may be prohibited from pulling down the status bar, but the banner notification may be allowed to be displayed while the shooting interface is displayed. That is, at the third time point, the banner notification is displayed on the second screen, and at the fourth time point, the notification list is displayed upon receiving the operation of pulling down the status bar. In this way, the user will not miss important notification messages when operating on the shooting interface displayed on the secondary screen of the mobile phone. The third time point and the fourth time point mentioned above may be the same, or the third time point may be earlier than the fourth time point, and there is no limitation here.

[0016] In a possible implementation of the first aspect above, the method further includes: the first screen and the second screen are two display areas of the display screen; and the third interface is the interface after the first interface is adjusted to fit the size of the second screen.

[0017] It is understood that the first screen (e.g., the main screen) and the second screen (e.g., the secondary screen) can be two display areas of the same flexible display screen. The third interface of the first application displayed on the second screen can be, for example, the shooting interface of the camera application displayed on the secondary screen. The shooting interface can be drawn by the camera application by calling the system's rendering process to adapt to the secondary screen size, and will not be detailed here.

[0018] In a possible implementation of the first aspect above, the method includes: after the fourth time point, based on the terminal device being in a folded state, displaying the first interface of the first application on the second screen, and not responding to the second operation of pulling down the status bar.

[0019] It can be understood that after the fourth time point mentioned above, that is, when the user flips the phone and displays the shooting interface through the secondary screen, the phone can keep the status bar prohibited from being pulled down but allow the banner notification to be displayed.

[0020] In a possible implementation of the first aspect above, the attribute parameters of the status bar include a first attribute parameter and a second attribute parameter, wherein the first attribute parameter is used to indicate whether the interface displayed on the first screen or the second screen responds to the operation of pulling down the status bar, and indicates whether a banner notification is displayed on the interface displayed on the first screen or the second screen; the second attribute parameter is used to indicate whether the interface displayed on the first screen or the second screen responds to the operation of pulling down the status bar, and indicates whether a banner notification is displayed on the interface displayed on the first screen or the second screen.

[0021] In a possible implementation of the first aspect, the types of the first attribute parameter and the second attribute parameter include a flag attribute, and the first attribute parameter includes the attribute parameter "DISABLE_EXPAND_EXCEPT_HEADSUP", and the second attribute parameter includes the attribute parameter "DISABLE_EXPAND".

[0022] In other embodiments, the first attribute parameter and the second attribute parameter may also be attribute parameters in other forms, which are not limited here.

[0023] In a possible implementation of the first aspect, the method includes:

[0024] At a first time point, based on the value of the second attribute parameter being set to 0 and the value of the first attribute parameter being set to 0, receiving a first notification of the second application, and displaying a banner notification of the first notification on the first screen;

[0025] At a second time point, based on the value of the second attribute parameter being set to 0 and the value of the first attribute parameter being set to 0, a first operation of pulling down the status bar is received, and a notification list is displayed.

[0026] For example, in the case where the mobile phone allows the status bar to be pulled down and the banner notification to be displayed, the attribute parameters of the status bar can be set to: the value of the second attribute parameter is 0 and the value of the first attribute parameter is also 0. That is, the following function can be used:

[0027] "panelsEnabled()

[0028] (Disabled1&DISABLE_EXPAND)=0&&

[0029] (Disabled1 & Disable_Expand_Except_HeadsUp) = 0" to complete the setting.

[0030] In a possible implementation of the first aspect, the method includes:

[0031] At a third time point, based on the value of the second attribute parameter being set to 0 and the value of the first attribute parameter being set to 1, a second notification of the second application is received, and a banner notification of the second notification is displayed on the second screen;

[0032] At a fourth time point, based on the value of the second attribute parameter being set to 0 and the value of the first attribute parameter being set to 1, a second operation of pulling down the status bar is received, and the notification list is not displayed.

[0033] For example, in the case where the mobile phone prohibits pulling down the status bar but allows displaying banner notifications, the attribute parameters of the status bar can be set to: the value of the second attribute parameter is 0 and the value of the first attribute parameter is also 1. That is, the following function can be used:

[0034] "panelsEnabled()

[0035] (Disabled1&DISABLE_EXPAND)=0&&

[0036] (Disabled1 & Disable_Expand_Except_HeadsUp)! = 0" to complete the setting.

[0037] In a possible implementation of the first aspect, the method further includes:

[0038] At a fifth time point, based on the value of the second attribute parameter being set to 1, a third notification of the second application is received, and a banner notification of the third notification is not displayed on the first screen or the second screen;

[0039] At the sixth time point, based on the value of the second attribute parameter being set to 1, a third operation of pulling down the status bar is received, and the notification list is not displayed.

[0040] For example, in the case where the mobile phone prohibits pulling down the status bar and prohibiting the display of banner notifications, the attribute parameters of the status bar can be set to: the value of the second attribute parameter is 1. That is, the following function can be used:

[0041] "panelsEnabled()

[0042] (Disabled1 & Disable_Expand) = 1" to complete the setting.

[0043] In a possible implementation of the first aspect, the value of the second attribute parameter is set to 1, including:

[0044] receiving a value set by the first application for the second attribute parameter, and setting the value of the second attribute parameter to 1; or,

[0045] A setting operation corresponding to a second attribute parameter in a setting interface by the user is received, and a value of the second attribute parameter is set to 1.

[0046] For example, a camera application can prohibit the pull-down status bar and the display of banner notifications in the phone's system settings according to its own business needs. Users can also prohibit the pull-down status bar and the display of banner notifications in the camera application's shooting interface or other application interfaces through the settings interface provided by the settings application.

[0047] In a possible implementation of the first aspect, the operation of pulling down the status bar includes:

[0048] A fourth operation in which the user slides downward on the touch area near the first side at the top of the screen displaying the first screen or the second screen, wherein the fourth operation can cause the terminal device to display a notification list; or a fifth operation in which the user slides downward on the touch area near the second side at the top of the screen displaying the first screen or the second screen, wherein the fifth operation can cause the terminal device to display a control center, wherein the first side and the second side are different sides of the top of the screen of the first screen or the second screen.

[0049] In a second aspect, the present application provides a terminal device comprising: one or more processors; one or more memories; one or more memories storing one or more programs, wherein when one or more programs are executed by one or more processors, the terminal device executes the display method provided in the above-mentioned first aspect and various possible implementations of the first aspect.

[0050] In a third aspect, the present application provides a computer-readable medium having instructions stored thereon. When the instructions are executed on a computer, the computer executes the display method provided in the first aspect and various possible implementations of the first aspect.

[0051] In a fourth aspect, an embodiment of the present application provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the display method provided in the above-mentioned first aspect and various possible implementations of the first aspect.

[0052] The beneficial effects of the second to fourth aspects mentioned above can be found in the relevant descriptions of the first aspect and various possible implementations of the first aspect, and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] FIG1a is a schematic diagram showing an application scenario in which a foldable screen device displays an application interface based on different display screens.

[0054] FIG1b shows a schematic diagram of the folding-unfolding configuration of a folding screen device.

[0055] Figure 1c shows a schematic diagram of the folding-unfolding form of another folding screen device.

[0056] FIG2 a is a schematic diagram of an interface that allows a pull-down status bar operation, provided in an embodiment of the present application.

[0057] FIG2 b is a schematic diagram of an interface for prohibiting the pull-down status bar operation provided in an embodiment of the present application.

[0058] FIG3 is a schematic diagram showing an implementation flow of a display method provided in an embodiment of the present application.

[0059] FIG4 is a schematic diagram showing an interface of a mobile phone displaying a banner notification according to an embodiment of the present application.

[0060] FIG5 is a schematic diagram showing the software structure of an operating system of a terminal device provided in an embodiment of the present application.

[0061] FIG6 is a schematic diagram showing an interactive process for implementing a display method provided in an embodiment of the present application.

[0062] FIG7 a shows a schematic diagram of a shooting interface displayed on a main screen and a prompt interface displayed on a secondary screen of a mobile phone provided in an embodiment of the present application when the mobile phone is in a folded state.

[0063] FIG7 b shows a schematic diagram of a shooting interface displayed on a main screen and a shooting interface displayed on a secondary screen of a mobile phone provided in an embodiment of the present application when the mobile phone is in a folded state.

[0064] FIG8 is a schematic diagram showing the principle of implementing a display method provided in an embodiment of the present application within an operating system.

[0065] FIG9 is a schematic diagram showing an implementation flow of responding to user operations related to a banner notification provided in an embodiment of the present application.

[0066] Figure 10a is a schematic diagram of an interface for performing a click operation on a displayed banner notification provided in an embodiment of the present application.

[0067] Figure 10b is a schematic diagram of an interface for performing left and right sliding operations on a displayed banner notification provided in an embodiment of the present application.

[0068] Figure 10c is a schematic diagram of an interface for sliding up and down on a displayed banner notification provided in an embodiment of the present application.

[0069] Figure 10d is a schematic diagram of an interface displayed corresponding to a left swipe operation on a displayed banner notification provided in an embodiment of the present application.

[0070] FIG11 is a schematic diagram showing the hardware structure of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0071] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described in detail below with reference to the accompanying drawings and specific implementation methods.

[0072] Figure 1a shows a schematic diagram of an application scenario in which a foldable screen device displays an application interface based on different display screens.

[0073] As shown in Figure 1a, the mobile phone 100 is a foldable screen device, including a display screen 101, a display screen 102 and a camera module 103. The display screen 101 and the display screen 102 can be two display areas of the same flexible display screen. The display screen 101 can also be called the "main screen" and the display screen 102 can also be called the "sub-screen", where the sub-screen size, for example, the width can be smaller than the width of the main screen size, that is, the sub-screen can be narrower than the main screen. In addition, in the unfolded state, the display direction of the main screen and the sub-screen of the mobile phone 100 is the same, that is, the display contents on the display screens 101 and 102 face the same direction. In the folded state, the display directions of the main screen and the sub-screen of the mobile phone 100 are opposite, and the display contents on the display screens 101 and 102 face opposite directions. In the folded state, the display screen 102 can be located on the same side as the camera module 103.

[0074] When the mobile phone 100 enters the folded state from the unfolded state, if the mobile phone 100 uses the display screen 101 to display the shooting interface, the shooting interface 104 shown in FIG. 1a may be displayed. If the mobile phone 100 uses the display screen 102 to display the shooting interface, the shooting interface 105 shown in FIG. 1a may be displayed. As shown in FIG. 1a , the operation method for the mobile phone 100 to enter the folded state can be an outward folding method in which the display screen 102 is flipped outward.

[0075] At this time, if the user takes a photo through the camera module 103, that is, the mobile phone 100 enters the rear selfie mode, the mobile phone 100 can automatically enter the notification disabled state while displaying the shooting interface 105, that is, the above-mentioned immersive state. That is, at this time, the mobile phone 100 prohibits the operation of pulling down the status bar, but because the drop-down panel corresponding to the status bar and the banner notification belong to the same window or interface (view), the mobile phone 100 also prohibits the display of the banner notification in this state. The operation of pulling down the status bar can refer to the operation ① shown in Figure 2a or Figure 2b, where the user drags the status bar downward from the top left or top right of the screen. When the user clicks the switch control 106 on the shooting interface 105 to switch to the home screen, the mobile phone 100 can switch to the home screen and exit the notification disabled state. At this time, the status bar of the mobile phone 100 can allow the user to pull down the status bar and display the banner notification. After exiting the notification disabled state, even if the user has set not to display notification messages, the mobile phone 100 can respond to the user's operation ① performed on the top right and display the control center interface shown in Figure 2b.

[0076] It can be understood that the folding-unfolding form of the mobile phone 100 shown in Figure 1a is only an example provided in this application. In other embodiments, the folding-unfolding form of the folding screen mobile phone 100 may also be the folding-unfolding form shown in Figure 1b or Figure 1c. Referring to Figure 1b, the operating method for the mobile phone 100 to enter the folding state may also be an inward folding method of flipping the display screen inward, wherein the side where the display screen 102 is located may have a camera module. Referring to Figure 1c, the operating method for the mobile phone 100 to enter the folding state may also be a folding method in which the display screen of a multi-fold folding device such as a tri-fold is folded together, wherein the side where the display screen 102 is located may also have a camera module, which is not limited here.

[0077] Specifically, referring to FIG2a, the mobile phone 100 may allow the operation of pulling down the status bar when displaying the shooting interface using the main screen 101. For example, when the user performs the above operation ① on the top right side of the screen, the mobile phone 100 may respond to the operation ① and display the control center interface shown in FIG2a.

[0078] Referring to FIG. 2b , when the mobile phone 100 enters rear-facing selfie mode and uses the secondary screen 102 to display the shooting interface, it may enter a notification disabled state. In this notification disabled state, if the user performs the above-mentioned operation ① on the top left or top right side of the screen, the mobile phone 100 may display the unresponsive interface shown in FIG. 2b , for example, not displaying the above-mentioned control center interface or not displaying the notification list folded to the status bar.

[0079] Therefore, in the above scenario, if the mobile phone 100 enters the folded state and uses the secondary screen to display the shooting interface, the status bar is prohibited from being pulled down and the banner notification is not displayed, that is, the mobile phone 100 is set to enter the notification disabled state, then the user may easily miss some important notification messages in this interface. If the mobile phone 100 enters the folded state and uses the secondary screen to display the shooting interface, the status bar is allowed to be pulled down or the notification list in the status bar is clicked to open the relevant application, etc., because the size of the secondary screen is inconsistent with the size of the main screen, for example, it is narrower than the width of the main screen, this may cause the mobile phone 100 to display the notification list or the relevant application interface, etc., and ultimately lead to a poor user experience.

[0080] In order to solve the above problems, the present application provides a display method. Specifically, the method decouples the attributes corresponding to the operation of pulling down the status bar and displaying the banner notification on mobile phones and other terminal devices by adding an attribute configuration that prohibits the operation of pulling down the status bar but displays the banner notification, so as to balance the user's demand for immersive experience and the need to view important notification messages in a timely manner. Even if the terminal device enters the notification prohibition state and prohibits the operation of pulling down the status bar, the terminal device can still display the banner notification. In this way, it is possible to display banner notifications as reminders according to user needs in different immersive scenarios, thereby avoiding missing important notification messages and improving user experience.

[0081] In addition, users can also set the notification prohibition state according to personal preferences to continue using the control mode of prohibiting the pull-down status bar operation and prohibiting the display of banner notifications. For example, users can enable the above-mentioned notification prohibition state through the relevant control settings displayed on the setting interface corresponding to the "Notification and Status Bar" of the settings application.

[0082] It can be understood that the operation configuration of the above-mentioned drop-down status bar and the attribute configuration of the banner notification on terminal devices such as mobile phones can be achieved by setting the flag attribute parameters of the corresponding interface (view). For example, by setting the value of the attribute parameter "DISABLE_EXPAND" corresponding to whether the drop-down status bar operation is allowed in the flag attribute, it is possible to control whether the operation of the drop-down status bar is allowed or prohibited. In the existing scheme, if the value of the attribute parameter is "1", it means that the operation of the drop-down status bar is prohibited, and the system of the terminal device such as the mobile phone will also prohibit the display of the banner notification. Conversely, if the value of the attribute parameter is "0", it means that the operation of the drop-down status bar is allowed, and the system also displays the banner notification.

[0083] In an embodiment of the present application, by adding another attribute parameter "DISABLE_EXPAND_EXCEPT_HEADSUP" to the flag attribute and combining it with the above-mentioned attribute parameter "DISABLE_EXPAND", it is possible to implement the attribute configuration of prohibiting the operation of pulling down the status bar but displaying a banner notification at the same time. For example, when the value of the above-mentioned attribute parameter "DISABLE_EXPAND" is "1", terminal devices such as mobile phones can determine whether to display a banner notification while prohibiting the operation of pulling down the status bar based on whether the attribute parameter "DISABLE_EXPAND_EXCEPT_HEADSUP" is 1. If the value of "DISABLE_EXPAND_EXCEPT_HEADSUP" is "1", the banner notification can be displayed. If the value of "DISABLE_EXPAND_EXCEPT_HEADSUP" is "0", the banner notification is prohibited from being displayed. The specific setting process will be described in detail below in conjunction with the relevant flow chart, and will not be repeated here.

[0084] In other embodiments, configuration states such as disabling the pull-down status bar operation while displaying a banner notification can be set by configuring other attribute parameters different from the flag attribute and / or configuring the corresponding attribute parameters to other values. For example, the value of "DISABLE_EXPAND_EXCEPT_HEADSUP" can be set to "true" or "false", and / or the value of "DISABLE_EXPAND" can be set to "true" or "false", etc., and the above configuration states are not limited here.

[0085] It can be understood that the display method provided in the embodiments of the present application is applicable to terminals including but not limited to mobile phones, tablet computers, desktop computers, laptop computers, handheld computers, netbooks, as well as augmented reality (AR) / virtual reality (VR) devices, smart TVs, smart watches and other wearable devices, servers, car equipment, portable game consoles, portable music players, reader devices, and other terminal devices embedded or coupled with one or more processors or capable of accessing the network.

[0086] Continuing with the foldable screen device mobile phone 100 in the application scenario shown in FIG1a above as an example, the following describes the specific process of displaying a banner notification when the rear-mounted selfie mode of the camera application is activated, using the display method provided by this application, while the status bar is disabled from being pulled down. It is understood that in some embodiments, the rear-mounted selfie mode may also be referred to as a "super selfie mode" or other modes, which is not limited here.

[0087] It can be understood that for the foldable screen device mobile phone 100 in the application scenario shown in Figure 1a, the above-mentioned rear selfie mode refers to a shooting mode in which the rear camera of the mobile phone 100 (refer to the camera provided by the camera module 103 shown in Figure 1a) is used to shoot and the user is performing a shooting operation on the shooting interface displayed on the secondary screen. The camera application running on the mobile phone 100 may also support a rear shooting mode, in which the user can operate the shooting operation on the main screen or the unfolded full screen of the mobile phone 100, which is not limited here.

[0088] Figure 3 shows a schematic diagram of an implementation process of a display method according to an embodiment of the present application. It is understood that the execution subject of each step in the process shown in Figure 3 can be the above-mentioned mobile phone 100, or other terminal electronic devices applicable to the display method provided by the present application, without limitation.

[0089] Specifically, as shown in FIG3 , the implementation process includes:

[0090] 301: Display the interface of the first application.

[0091] For example, in an embodiment of the present application, the interface of the first application may be a camera application shooting interface that triggers the mobile phone 100 to notify the disabled state, such as a rear-mounted selfie mode shooting interface displayed on the secondary screen of the foldable screen mobile phone 100. The specific process of the mobile phone 100 responding to the user operation using the rear-mounted selfie mode shooting interface displayed on the secondary screen, etc., can be referred to the description below in conjunction with the relevant drawings, and will not be repeated here.

[0092] In other embodiments, the interface of the first application may also be another interface that can cause the mobile phone to enter the notification disabled state. The reason for the interface of the first application to trigger the mobile phone to enter the notification disabled state may be based on the user's settings for "Notification and Status Bar" or may be a default setting based on the need to improve the user experience of the mobile phone 100 system or related applications. This is not limited here.

[0093] 302: Obtain the value of the first attribute parameter corresponding to the banner notification setting in the current display mode.

[0094] Exemplarily, the first attribute parameter corresponding to the banner notification setting may be, for example, “DISABLE_EXPAND_EXCEPT_HEADSUP” or other parameters capable of setting banner notification attributes, which are not limited here.

[0095] For example, the value of the first attribute parameter can be set by a heads-up coordinator or a folding screen management module in the operating system of the mobile phone 100. The setting process can be implemented by calling a function, and the corresponding function called can be, for example, StatusBarManager.disable() or other functions with similar functions, which are not limited here.

[0096] 303: Get the value of the second attribute parameter corresponding to the status bar drop-down panel setting in the current display mode.

[0097] For example, the second attribute parameter corresponding to the status bar drop-down panel setting may be, for example, "DISABLE_EXPAND" or other attribute parameters capable of setting a user operation of disabling the status bar from being pulled down, which is not limited herein.

[0098] For example, the operating system of the mobile phone 100 can set the value of the second attribute parameter by calling a function interface provided by the horizontal status bar management module (status bar manager), or by calling a function interface provided by the horizontal status bar management module through the folding screen management module. The setting process can also be implemented by calling the function StatusBarManager.disable() or the corresponding function call process of other functions with similar functions, which is not limited here.

[0099] 304: Receive a notification message sent by the second application.

[0100] It is understandable that the second application that sends the notification message may be different from the application to which the interface of the first application belongs. In other embodiments, the second application that sends the notification message may also be the same as the application to which the interface of the first application belongs, which is not limited here.

[0101] 305: Determine whether the value of the second attribute parameter is a status value corresponding to prohibiting the pull-down status bar.

[0102] If the judgment result is yes, the following step 306 is executed to prohibit the user from pulling down the status bar and not display the banner notification;

[0103] If the judgment result is no, then continue to execute the judgment process performed on the value of the first attribute parameter in step 307 below.

[0104] For example, the value of the second attribute parameter may be, for example, the status value corresponding to the "DISABLE_EXPAND" setting. In the embodiment of the present application, the preset attribute parameter "DISABLE_EXPAND" may have a value of 1, which indicates true, i.e., prohibiting the user from pulling down the status bar. In this case, the result of the mobile phone 100 executing step 305 is yes. Conversely, the value of "DISABLE_EXPAND" may have a value of 0, which indicates false, i.e., allowing the user to pull down the status bar. In this case, the result of the mobile phone 100 executing step 305 is no.

[0105] It is worth noting here that the first application running on the mobile phone 100, such as the above-mentioned camera application or the settings application run by the system, can set the value of the second attribute parameter "DISABLE_EXPAND" corresponding to the status bar drop-down panel to 0 by default, that is, the default status bar drop-down panel is in a state that allows the status bar to be pulled down, and the mobile phone 100 is also allowed to display banner notifications. When the above-mentioned first application responds to the user's setting operation or in order to adapt to its own business needs, for example, the user sets the camera application to enter the notification prohibition state when running through the settings application, or when the camera application is set to enter the notification prohibition state when the user uses the above-mentioned rear selfie mode in order to achieve a better user experience, the mobile phone 100 first performs the judgment of this step 305 to ensure that the following step 306 is performed first according to the user's needs or the business needs of the application.

[0106] When it is determined that the first application has not modified the default value of the second attribute parameter, that is, when the mobile phone 100 executes the judgment result of step 305 as no, it can continue to execute the following steps 307 to 309 and continue to execute other control processes for pulling down the status bar and displaying banner notifications.

[0107] 306: Do not display banner notifications and do not respond to user operations when the user pulls down the status bar.

[0108] For example, when the mobile phone 100 determines that the value of the second attribute parameter, such as "DISABLE_EXPAND," is "1," i.e., a status value that prohibits pulling down the status bar, the mobile phone 100 can control the display of the first application interface to indicate that the mobile phone 100 prohibits pulling down the status bar in the current display mode. At the same time, since the attribute parameter "DISABLE_EXPAND" for prohibiting pulling down the status bar is associated with banner notifications by default, the mobile phone 100 will also prohibit the display of banner notifications, i.e., will not display banner notifications.

[0109] It is understood that the above-mentioned banner notification is usually used to display the above-mentioned second application (such as phone or WeChat) TM Notification messages sent by

[0110] 307: Determine whether the value of the first attribute parameter is a status value corresponding to prohibiting the pull-down status bar but allowing the display of the banner notification.

[0111] If the result of the judgment is yes, the following step 308 is executed to prohibit the operation of pulling down the status bar but display the banner notification;

[0112] If the result of the determination is no, the following step 309 is executed to allow the operation of pulling down the status bar and display a banner notification.

[0113] For example, the value of the first attribute parameter may be the status value corresponding to the setting of "DISABLE_EXPAND_EXCEPT_HEADSUP". In the embodiment of the present application, the preset attribute parameter "DISABLE_EXPAND_EXCEPT_HEADSUP" may be set to a value of 1 to indicate true, i.e., the user operation of pulling down the status bar is prohibited but the banner notification can be displayed. In this case, the result of the mobile phone 100 executing step 307 is yes. Conversely, the value of "DISABLE_EXPAND_EXCEPT_HEADSUP" is set to 0 to indicate false, i.e., the user operation of pulling down the status bar is not prohibited or allowed, but the banner notification can also be displayed. In this case, the result of the mobile phone 100 executing step 307 is no.

[0114] It is understood that after the mobile phone 100 determines in the judgment process of step 305 that the relevant application has not changed / set the default value of the attribute parameters related to the notification prohibition state, it can further perform this step to determine whether a state is set for the interface of some applications that prohibits pulling down the status bar but allows the display of banner notifications, or a state that allows pulling down the status bar but allows the display of banner notifications. The latter can also be described as not setting the notification prohibition state in some embodiments, which is not limited here.

[0115] As an example, FIG4 shows a schematic diagram of an interface for displaying a banner notification on a mobile phone according to an embodiment of the present application.

[0116] As shown in FIG4 , when the foldable screen mobile phone 100 enters the immersive state and displays the shooting interface 410 in the rear selfie mode, it can also display a banner notification 411 when receiving an incoming call, or display a banner notification 412 when receiving a text message, etc. In this way, the mobile phone 100 can promptly notify users of important notification messages such as incoming call reminders and instant messaging messages, which is conducive to improving the user experience and providing users with a moderate immersive state.

[0117] In some embodiments, the terminal device used by the user may also be a tablet computer or a notebook, etc., which is not limited here.

[0118] It is understood that for the banner notification displayed by the terminal device such as the mobile phone 100, the user can further click to view the detailed content, or swipe left or right to delete, ignore, etc., or pull down to view part of the content, or pull up to collapse it to the notification list in the status bar. The specific implementation process of the mobile phone 100 responding to these user operations on the banner notification can be referred to the detailed description in conjunction with the relevant flow chart below, and will not be repeated here.

[0119] 308: Display a banner notification and respond to user actions when the user pulls down the status bar.

[0120] For example, if the mobile phone 100 determines that the value of the second attribute parameter is a status value corresponding to prohibiting the pull-down status bar but allowing the display of a banner notification based on the execution of the above step 307, the mobile phone 100 can respond to the user's operation of pulling down the status bar to display the notification list or control center. Moreover, while the mobile phone 100 displays the interface of the above first application, the mobile phone 100 can also display notification messages sent by other applications through banner notifications, such as phone calls, WeChat, etc. TM There are no restrictions on incoming call reminders, instant messaging messages, etc. from applications such as WhatsApp.

[0121] In this way, the mobile phone 100 can respond to the needs of certain specific applications, either based on application settings or user settings, to achieve the goal of preventing users from accidentally pulling down the status bar when displaying the interface of the first application, thereby disrupting their immersive experience, while also maintaining timely reminders of important notification messages, namely banner notifications. In this way, the above two user needs can be balanced, which is conducive to improving the user experience of terminal devices such as mobile phones.

[0122] 309: Display a banner notification and respond to user actions when the user pulls down the status bar.

[0123] For example, when the mobile phone 100 displays the interface of the first application, it can respond to the user pulling down the status bar to view the notification and control center operation and display a banner notification at the same time. Similarly, the banner notification can display notification messages sent by other applications, such as phone calls, WeChat, etc. TM There are no restrictions on incoming call reminders, instant messaging messages, etc. from applications such as WhatsApp.

[0124] In an embodiment of the present application, when the value of the first attribute parameter set by the mobile phone 100 is "1" based on the above, the status bar on the interface of the first application has a state that prohibits the user from pulling down the status bar but can display a banner notification, which can be recorded as the "first state". When the value of the second attribute parameter set by the mobile phone 100 is "1" based on the above, the status bar on the interface of the first application has a state that prohibits the user from pulling down the status bar and does not display a banner notification, which can be recorded as the "second state". In addition, when the value of the second attribute parameter set by the mobile phone 100 is "0" based on the above and the value of the first attribute parameter is also "0", the status bar on the interface of the first application has a state that allows the user to pull down the status bar and can display a banner notification, which can be recorded as the "third state" for distinction.

[0125] Based on the execution process of steps 301 to 309 shown in Figure 3 above, the mobile phone 100 can, based on user settings or business requirements of related applications, control the status bar of some application interfaces to have the above-mentioned "first state", control the status bar of some application interfaces to have the above-mentioned "second state", or control the status bar of the application interface to have the above-mentioned "third state". This can meet the different usage experience requirements of users and can also be more adaptable to different business requirements of related applications.

[0126] Figure 5 shows a schematic diagram of the operating system software structure of a terminal device according to an embodiment of the present application. It is understood that the terminal device can be the mobile phone 100 described above or a terminal electronic device such as a tablet computer or laptop. The following continues to use mobile phone 100 as an example to describe in detail the operating system software structure of the terminal device.

[0127] As shown in Figure 5, the operating system of mobile phone 100 can adopt a layered architecture. The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer. For ease of description, the system layer and each layer structure will be numbered when introducing the system software structure below.

[0128] As shown in reference figure 5, the application layer 510 may include a series of application packages. The application package may include applications such as camera 511, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, short message and system user interface (SystemUI) 512. Among them, SystemUI 512 can be used to receive and store the values ​​of attribute parameters corresponding to the window or interface set by the folding screen management module 521, including setting the values ​​of relevant attribute parameters such as whether to allow the status bar to be pulled down and whether to display a banner notification. Furthermore, when the relevant window or interface needs to display a notification reminder, or when the user's operation on the status bar drop-down panel is detected, it can be determined whether to respond to the user operation or whether to display a banner notification based on the value of the set attribute parameter.

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

[0130] The application framework layer may include a folding screen management module (FSM) 521, a window management module (WMS) 522, a view system, a phone management module, a resource management module, and a notification management module (NMS) 523, etc.

[0131] The folding screen management module 521, which may also be referred to as a folding screen management service or a folding screen manager, is used to manage the windows or interfaces of the folding screen device, including managing the display content of the windows or interfaces in the corresponding display modes according to the different display modes of the folding screen device, including setting whether the windows or interfaces in the corresponding display modes allow user operations on the status bar drop-down panel and whether to display banner notifications, etc. In an embodiment of the present application, the folding screen management service 521 can implement the settings of whether the window or interface allows the status bar to be pulled down, whether a banner notification is displayed, etc. through the StatusBarManager.disable() function. In some embodiments, the calling interface corresponding to the above function can be a system interface, or it can be a calling interface provided by the status bar management service or the status bar management module, etc., which is not limited here.

[0132] The window management module 522, which may also be referred to as a window management service or a window manager, is used to manage window programs. The window management module 522 can obtain the size of the display screen, determine whether there is a status bar, lock the screen, capture the screen, etc. In an embodiment of the present application, the window management module 522 can interact with applications such as the camera application, obtain messages about the shooting interface or window that has switched to the corresponding display mode, and notify the folding screen management module 521 of changes in the device status. For details, please refer to the detailed description below and will not be repeated here.

[0133] The notification management module 523, also known as the notification management service or notification manager, is used to enable applications to display notification information in the status bar. It can be used to convey notification-type messages and can automatically disappear after a short period of time without user interaction. For example, the notification management module 523 is used to notify the completion of downloads, message reminders, etc. The notification management module 523 can also be a notification that appears in the system top status bar in the form of an icon or scrolling text bar, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, the terminal vibrates, the indicator light flashes, etc.

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

[0135] The call management module is used to provide communication functions of the mobile phone 100, such as management of call status (including answering, hanging up, etc.).

[0136] The resource management module provides various resources for the application, such as localized strings, icons, images, layout files, video files, etc.

[0137] The system library 530 may include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (e.g., OpenGL ES), and a 2D graphics engine (e.g., SGL). The surface manager manages the display subsystem and provides fusion of 2D and 3D layers for multiple applications.

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

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

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

[0141] The Android Runtime 540 includes a core library and a virtual machine. The Android Runtime 540 is responsible for scheduling and management of the Android system.

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

[0143] The application layer 510 and the application framework layer 520 run in a virtual machine. The virtual machine executes the Java files in the application layer and the application framework layer as binary files. The virtual machine is responsible for performing functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0144] The kernel layer 550 is a layer between hardware and software. The kernel layer 550 includes at least a display driver, a camera driver, an audio driver, and a sensor module 551. Optionally, the sensor module 551 can be a functional module that is part of a driver or a program. In an embodiment of the present application, the sensor module 551 can report the data collected by the gyroscope sensor, acceleration sensor, etc. of the mobile phone 100 corresponding to the determined flip event, etc. to the calling application, such as the camera application 511, etc., to detect the user's operation of flipping the phone or unfolding the folding screen, and then trigger the camera application 511 to switch the front / rear camera to the corresponding shooting mode. For details, please refer to the relevant description below and will not be repeated here.

[0145] Based on the system software structure shown in FIG5 , the interactive implementation process of a notification management method provided by the present application will be described in detail below in conjunction with FIG6 .

[0146] Figure 6 shows a schematic diagram of an interactive process for implementing a display method according to an embodiment of the present application. It is understood that the entities involved in each step of the interactive process may include the sensor module 551, the SystemUI 512, the notification management module 523, the window management module 522, the folding screen management module 521, the camera application 511, and other applications that generate notification messages.

[0147] Specifically, as shown in FIG6 , the interaction process may include the following steps:

[0148] 601: The folding screen management module 521 registers a device status listener with the window management module 522.

[0149] Exemplarily, the folding screen management module 521 can set a device status listener to the window management module 522 through the function "DevicePreStateListener" to monitor the screen status used by the mobile phone 100 to display the interface of the relevant application. The screen status can also be used to determine the display mode adopted by the mobile phone 100. In an embodiment of the present application, taking the folding screen device as an example, the screen status or display mode used by the mobile phone 100 to display the interface of the relevant application may include full-screen display, main screen display or sub-screen display. Based on the device status listener set above, the folding screen management module 521 of the mobile phone 100 can monitor from the window management module 522 to obtain what device status or display mode the mobile phone 100 uses to display the current interface in full-screen display, main screen display or sub-screen display. The current interface can be, for example, the shooting interface of the camera application, or the interface of other applications, which is not limited here.

[0150] It is understood that when the mobile phone 100 runs the camera application, if it detects that the screen currently viewed or operated by the user is the main screen or full screen of the mobile phone 100, the mobile phone 100 can currently display the corresponding shooting interface on the main screen or full screen. If the mobile phone 100 detects that the user has turned the mobile phone 100 over and is viewing or operating the interface displayed on the secondary screen, the mobile phone 100 can also currently display the corresponding shooting interface on the secondary screen. This is not limited here.

[0151] 602: The camera application 511 detects a user operation of starting a rear-mounted selfie mode.

[0152] Exemplarily, the above-mentioned user operation of starting the rear-camera selfie mode may include the user clicking the control corresponding to "Switch to sub-screen" on the shooting interface of the camera application to start the rear-camera selfie mode, or may include the user flipping the phone, etc. The user operation of starting the rear-camera selfie mode can trigger the start of the rear-camera selfie mode, which is not limited here.

[0153] In some embodiments, the user can click the "flip" control on the shooting interface of the camera application 511 or switch to the shooting control operation corresponding to the rear selfie mode to start the rear selfie mode. Correspondingly, the camera application 511 running on the mobile phone 100 can detect the operation of starting the rear selfie mode. It can be understood that after the user performs the above operation to select the rear selfie mode, if the mobile phone 100 detects that the user is still using the main screen or full screen, and is not using the secondary screen to view the displayed content or perform related operations, the mobile phone 100 can display a prompt message at this time, prompting the user to flip or fold the mobile phone 100 and use the secondary screen to perform shooting operations or other related operations.

[0154] As an example, when the mobile phone 100 is running a camera application, if the mobile phone 100 is in a folded state, the mobile phone 100 can display the shooting interface 710 shown in Figure 7a on the main screen in response to the user clicking the flip camera to switch to the rear selfie mode. The shooting interface 710 and the camera interface 710 can also display a prompt icon 712 of "switch to the main screen", etc., which are not limited here. At the same time, the mobile phone 100 can also display a prompt interface 711 on the secondary screen, and the interface 711 can display content such as "Please flip the phone and use the super selfie" to prompt the user to flip the phone. If the user flips the phone according to the prompt, the super selfie function of the camera application 511 running on the mobile phone 100 can be used.

[0155] If the mobile phone 100 is in the folded state and the user is viewing the content displayed on the main screen, switching to the camera on the main screen to shoot, or performing touch operations on the main screen, the mobile phone 100 can use the main screen to display the shooting interface 720 shown in Figure 7b. A switching control 721 can be displayed on the shooting interface, and the switching control 721 can prompt the user to switch to the secondary screen display to use the rear selfie mode. The user can click the switching control 721 to switch to the secondary screen to use the rear selfie mode. Correspondingly, the mobile phone 100 enters the rear selfie mode or super selfie mode.

[0156] In other embodiments, the mobile phone 100 may also detect the user's flipping of the mobile phone 100 while the camera application 511 is running. For example, the sensor module 551 of the mobile phone 100 may transmit a flipping event determined based on sensor data detected by a gyroscope sensor, an accelerometer, etc. to the camera application 511. Based on the received sensor data, the camera application 551 may recognize the user's flipping action of the mobile phone and switch the current shooting mode to the rear selfie mode.

[0157] When the user flips the phone 100 so that the secondary screen faces them, the phone 100 can use the secondary screen to display the shooting interface 730 shown in Figure 7b. The switch control 731 on the shooting interface 730 now changes to a corresponding "switch to main screen" operation control. At this time, the user can use the phone's super selfie function to take a selfie or a group photo.

[0158] 603: The camera application 511 notifies the window management module 522 to switch to the secondary screen display.

[0159] For example, after executing step 602 and detecting the user operation of starting the rear selfie mode, the camera application 511 can call the function "SetDisplayMode()" to set the display mode or device status parameters to be switched, thereby notifying the window management module 522 located in the application framework layer 520 to switch the display mode (display mode) of the window displaying the shooting interface to the corresponding display mode. For example, when executing step 603, the camera application 511 can pass the device status parameter "DisplayModeSub" corresponding to the secondary screen display through the function "SetDisplaymode(3)". Based on this function, the camera application 511 can notify the window management module 522 to switch the display window corresponding to the shooting interface to the secondary screen display state or secondary screen display mode, that is, the display mode adapted to the size of the secondary screen.

[0160] Accordingly, when executing step 609, the camera application 511 may pass the device status parameter "DisplayModeMain" corresponding to the main screen display via the function "SetDisplaymode(2)", or pass the device status parameter "DisplayModeFull" corresponding to the main screen display via the function "SetDisplaymode(1)". In other embodiments, the camera application 511 may also execute the notification switching process of step 603 and step 609 by calling other functions with similar setting functions, which is not limited here.

[0161] It can be understood that when the camera application 511 of the mobile phone 100 notifies the window management module 522 to switch to the secondary screen display mode, the user can flip the mobile phone 100 to the device state with the secondary screen facing himself, or continue to keep the device state with the main screen facing himself. For example, the user clicks the "switch to secondary screen" control on the shooting interface displayed on the main screen of the mobile phone 100 but does not flip the phone. At this time, the window management module 522 of the mobile phone 100 can control the continued display of relevant icons or information prompting the user to flip the phone on the shooting interface of the camera application, and can continue to monitor changes in the device status. When the window management module 522 monitors that the screen currently displaying the shooting interface has switched from the main screen to the secondary screen display, it can execute the following step 604 to send changes in the device status to the folding screen management module 521.

[0162] 604: The window management module 522 sends a message to the folding screen management module 521 indicating that the device status has changed.

[0163] For example, the window management module 522 can pass the parameter value after the current device state changes, such as the parameter value corresponding to full (full screen), main (main screen) or sub (sub-screen) through the callback function "OnScreenDisplayModeChange", and send a message that the device state has changed to the folding screen management module 521. At the same time, the window management module 522 can notify the camera application 511 of the message that the corresponding device state has changed through the callback function "OnConfigChange". The camera application 511 can call the system rendering process to draw the application interface corresponding to the corresponding device state.

[0164] It is understood that the above-mentioned change in device status may include switching the shooting interface of the camera application from being displayed on the main screen or full screen to being displayed on the secondary screen, etc., and is not limited here.

[0165] 605: The folding screen management module 521 determines whether the current device status is secondary screen display.

[0166] If the judgment result is yes, then continue to execute the following step 606;

[0167] If the judgment result is no, the execution ends.

[0168] For example, the folding screen management module 521 can determine whether the current display mode used by the mobile phone 100 is the secondary screen display based on the monitored device status sent by the window management module 522 and the device status change notified by the window management module 522. In other embodiments, the folding screen management module 521 of the mobile phone 100 can also determine whether the current device state is the secondary screen display based on the screen device identification information of the current shooting interface obtained from the system by the window management module 522.

[0169] For example, if the foldable screen management module 521 determines that the mobile phone 100 is currently using the secondary screen to display the shooting interface, the corresponding judgment result is yes, and the following step 606 can be continued to set the relevant attribute parameters of the secondary screen display shooting interface. Conversely, if the foldable screen management module 521 determines that the mobile phone 100 is currently using the full screen display or the main screen to display the shooting interface, the corresponding judgment result is no, and no further steps need to be performed, and the execution can be terminated.

[0170] 606: The folding screen management module 521 calls the status bar management function and sets the value of the attribute parameter corresponding to prohibiting the status bar from being pulled down but allowing the banner notification to be displayed to the SystemUI 512.

[0171] For example, the value corresponding to the first attribute parameter "DISABLE_EXPAND_EXCEPT_HEADSUP" is set by calling the status bar management function StatusBarManager.disable(). For example, the value corresponding to "DISABLE_EXPAND_EXCEPT_HEADSUP" is set to "1" or not equal to 0, that is, "DISABLE_EXPAND_EXCEPT_HEADSUP!=0". Referring to the relevant description in the above step 302, it can be seen that this first attribute parameter is the attribute parameter corresponding to the banner notification setting of "disabling the status bar from being pulled down but allowing the banner notification to be displayed".

[0172] It is understood that the above "DISABLE_EXPAND_EXCEPT_HEADSUP" cannot be used as a limitation on the above first attribute parameter. In other embodiments, other attribute parameters for setting "disable the pull-down status bar but allow the display of banner notifications" can also be preset in terminal devices such as mobile phone 100, and are not limited here.

[0173] 607: The SystemUI 512 saves the received attribute parameter value corresponding to the current device state.

[0174] Exemplarily, SystemUI 512 can receive the first attribute parameter and value corresponding to the setting when the folding screen management module 521 executes the above step 606, and save it corresponding to the current device state (or display mode). For the above example, the folding screen management module 521 calls the status bar management function to set the attribute parameter value corresponding to the setting of prohibiting the pull-down status bar but allowing the display of banner notifications in the "secondary screen display" state. SystemUI 512 can save the attribute parameter and value of the above setting in the "secondary screen display" state as "DISABLE_EXPAND_EXCEPT_HEADSUP!=0".

[0175] In an embodiment of the present application, SystemUI 512 can save the value of the first attribute parameter set above corresponding to the current "secondary screen display" state or mode, so that while the mobile phone 100 displays the shooting interface of the rear selfie mode, notification messages sent to other applications can be displayed to the user through a banner notification based on the above-mentioned saved attribute parameters.

[0176] 608: The camera application 511 detects a user operation of exiting post-camera shooting.

[0177] For example, the user operation of exiting the rear selfie mode may include the user clicking a control on the camera application's shooting interface to switch to the home screen. The operation of exiting the rear selfie mode may also include the user flipping the phone over, or switching the phone 100 from a folded state to an unfolded state, etc., without limitation.

[0178] It is understood that when the user flips the mobile phone 100 from the state where the shooting interface is displayed on the secondary screen to the state where the shooting interface is displayed on the main screen, the sensor module 551 of the mobile phone 100 can correspondingly transmit the sensor data detected by the gyroscope sensor, acceleration sensor, etc. to the camera application 511, so that the camera application 511 can recognize the user's flipping action. When the user switches the mobile phone 100 from the folded state to the unfolded state, the sensor module 551 of the mobile phone 100 can correspondingly transmit the sensor data detected by the gyroscope sensor, acceleration sensor, Hall sensor, etc. to the camera application 511, so that the camera application 511 can recognize the user's operation of unfolding the screen of the foldable screen device.

[0179] 609 : The camera application 511 notifies the window management module 522 to switch to the main screen or full screen display.

[0180] For example, after detecting a user exit from the rear-mounted selfie mode during step 608, camera application 511 may notify window management module 522 in application framework layer 520, triggering window management module 522 to switch the window display mode of the capture interface to either main screen display or full screen display. The specific process by which camera application 511 calls the "SetDisplayMode()" function to set the desired display mode or device state parameters can be found in the description of step 603 above and is not further elaborated here.

[0181] 610: The window management module 522 sends a message to the folding screen management module 521 indicating that the device status has changed.

[0182] For example, the window management module 522 can send a status parameter or status information indicating that the device state has changed to the folding screen management module 521 through the callback function "OnScreenDisplayModeChange" or other functions, so as to notify the folding screen management module 521 that the current device state has changed. For details, please refer to the relevant description in the above step 604 and will not be repeated here.

[0183] 611: The folding screen management module 521 determines whether the current device status is secondary screen display.

[0184] If the result of the judgment is no, then continue to execute the following step 612;

[0185] If the judgment result is yes, the execution ends.

[0186] For example, the foldable screen management module 521 of the mobile phone 100 can determine whether the current device status used by the mobile phone 100 is the secondary screen display based on the device status change corresponding to the execution of the aforementioned step 610 by the window management module 522, as well as information such as the device status change notification received before the execution of the aforementioned step 610. In other embodiments, the foldable screen management module 521 of the mobile phone 100 can also determine whether the current device status is the secondary screen display based on the screen device identification information of the current shooting interface obtained from the system by the window management module 522.

[0187] For example, if the foldable screen management module 521 determines that the mobile phone 100 is currently using the main screen or the secondary screen to display the shooting interface, the corresponding judgment result is no, and the following step 612 can be continued to set the relevant attribute parameters of the main screen display or full screen display shooting interface. Conversely, if the foldable screen management module 521 determines that the mobile phone 100 is currently using the secondary screen to display the shooting interface, the corresponding judgment result is no, and no further steps need to be performed, and the execution can be terminated.

[0188] 612: The folding screen management module 521 calls the status bar management function and sets the values ​​of the attribute parameters corresponding to allowing pull-down and displaying banner notifications to the SystemUI 512.

[0189] Exemplarily, the folding screen management module 521 of the mobile phone 100 can set the value corresponding to the above-mentioned second attribute parameter "DISABLE_EXPAND" by calling the function StatusBarManager.disable(). For example, the value corresponding to "DISABLE_EXPAND" is set to "1" or "0". When the value corresponding to "DISABLE_EXPAND" is "0", it means that the operation of pulling down the status bar is allowed and the display of banner notifications is allowed. In other embodiments, if the value corresponding to "DISABLE_EXPAND" is set to "1", it can indicate that the operation of pulling down the status bar is prohibited and the display of banner notifications is prohibited.

[0190] It is understood that the above "DISABLE_EXPAND_EXCEPT_HEADSUP" cannot be used as a limitation on the above second attribute parameter. In other embodiments, other attribute parameters for setting "disable the pull-down status bar and prohibit the display of banner notifications" can also be preset in the terminal device such as mobile phone 100, and are not limited here.

[0191] 613: The SystemUI 512 saves the received attribute parameter value corresponding to the current device state.

[0192] Exemplarily, by calling the status bar management function StatusBarManager.disable(), the value corresponding to the second attribute parameter "DISABLE_EXPAND" is set. For example, the value corresponding to "DISABLE_EXPAND_EXCEPT_HEADSUP" is set to "0" by default, which allows the user to pull down the status bar in the main screen or full-screen display state and display banner notifications by default. At this time, SystemUI 512 can save the value "0" of the second attribute parameter corresponding to the main screen display state or full-screen display state of the foldable screen mobile phone 100.

[0193] In addition, if the application prohibits the user from pulling down the status bar and does not display a banner notification for the shooting interface or other application interface in response to the user's setting operation or actual business needs, the SystemUI 512 can also respond to the settings of the camera application 511 and other applications through the folding screen management module 521 and save the values ​​of the relevant attribute parameters in correspondence with the corresponding display state or display mode. In this way, the SystemUI 512 can prohibit the user from pulling down the status bar while the mobile phone 100 displays the shooting interface through the main screen, and does not display banner notifications for notification messages sent by other applications.

[0194] It is understood that in this embodiment of the present application, SystemUI 512 can perform the judgment process of steps 304 to 308 and the execution process of the corresponding judgment results based on the value of the first attribute parameter saved in step 607 and the value of the second attribute parameter saved in step 613. For details, please refer to the relevant description of step 616 below and will not be repeated here.

[0195] It can be understood that after completing the above steps 601 to 613, the above structures in the operating system of the mobile phone 100 can continue to execute the following steps 614 to 616 to control the process of displaying banner notifications on the corresponding interface under different display modes or device states.

[0196] 614 : Other applications send notification messages to the notification management module 523 .

[0197] 615 : The notification management module 523 sends a notification message to the SystemUI 512 .

[0198] 616: The SystemUI 512 determines whether to allow the status bar to be pulled down and whether to display the received notification message using a banner notification based on the saved values ​​of the first attribute parameter and the second attribute parameter.

[0199] Exemplarily, SystemUI 512 may call a related function in a command queue to execute the content determined based on the values ​​of the first attribute parameter and the second attribute parameter. For example, SystemUI 512 may call the function panelsEnabled() in the command queue to execute the following content to determine whether the operation of pulling down the status bar is allowed and whether a banner notification can be displayed:

[0200] "panelsEnabled()

[0201] (Disabled1&DISABLE_EXPAND)=0&&

[0202] (Disabled1&DISABLE_EXPAND_EXCEPT_HEADSUP)=0”

[0203] The above "Disabled1" indicates setting the attribute parameter "DISABLE_EXPAND" to a constant value of 1. Thus, if the value of the attribute parameter "DISABLE_EXPAND" is "0," then "(Disabled1 & Disable_EXPAND) = 0." If the value of the attribute parameter "DISABLE_EXPAND_EXCEPT_HEADSUP" is "0," then "(Disabled1 & Disable_EXPAND_EXCEPT_HEADSUP) = 0." Furthermore, the attribute parameters set by the above function "panelsEnabled()" indicate that the status bar can be pulled down and a banner notification can be displayed.

[0204] For another example, the SystemUI 512 may call the function panelsEnabled() in the command queue to execute the following content to determine whether to disable the operation of pulling down the status bar but to display the banner notification:

[0205] "panelsEnabled()

[0206] (Disabled1&DISABLE_EXPAND)=0&&

[0207] (Disabled1&DISABLE_EXPAND_EXCEPT_HEADSUP)! =0”

[0208] If the value of the attribute parameter DISABLE_EXPAND_EXCEPT_HEADSUP is not equal to 0 (i.e., != 0), then (Disabled1 & DISABLE_EXPAND_EXCEPT_HEADSUP) != 0. Furthermore, the attribute parameter set by the above function "panelsEnabled()" can indicate that the status bar is not allowed (i.e., prohibited) from being pulled down, but the banner notification can be displayed.

[0209] It is understood that in step 613, if the application, based on the user's settings or business needs, prohibits the pull-down status bar and the display of the banner notification through the folding screen management module 521, the camera application and other applications can set the value of the second attribute parameter to "1" in the SystemUI 512. Correspondingly, the SystemUI 512 can also call the function panelsEnabled() in the command queue to perform the following operations to determine the prohibition of the pull-down status bar operation and the display of the banner notification:

[0210] "panelsEnabled()

[0211] (Disabled1&DISABLE_EXPAND)=1”

[0212] If the value of the attribute parameter DISABLE_EXPAND is 1, then (Disabled1 & DISABLE_EXPAND) = 1. The attribute parameters set by the above function "panelsEnabled()" can indicate that the status bar cannot be pulled down and the banner notification cannot be displayed.

[0213] Based on the implementation process of steps 601 to 616 in the interaction process shown in Figure 6 above, the display method provided in this application corresponds to the implementation principle in the operating system of terminal devices such as mobile phone 100, which can be summarized below in conjunction with Figure 8.

[0214] FIG8 is a schematic diagram showing the principle of implementing a display method within an operating system according to an embodiment of the present application.

[0215] As shown in Figure 8, the camera application 511 located in the application layer 510 can call the function interface provided by the status bar management module through the folding screen management module 521 of the application framework layer 520, call the StatusBarManager.disable() function, and set the attribute parameters of prohibiting the pull-down status bar but allowing the display of banner notifications to the SystemUI 512 located in the application layer 510. In the embodiment of the present application, the above-mentioned first attribute parameter, second attribute parameter, etc. can be parameters set for the flag attribute of the interface (view). In other embodiments, the above-mentioned attribute parameters can also be parameters set by adjusting other attributes of the interface display effect, which are not limited here.

[0216] Continuing with reference to FIG8 , the process of setting the attribute parameters of disabling the status bar from being pulled down but allowing the banner notification to be displayed to the SystemUI 512 can be completed by executing the relevant parameters of the corresponding function in the command queue of the SystemUI 512. For example, the folding screen management module 521 can call StatusBarManager.disable() to set the value of the attribute parameters "DISABLE_EXPAND_EXCEPT_HEADSUP" and "DISABLE_EXPAND" to the SystemUI 512. After the setting is completed, the SystemUI 512 can execute the function in the command queue:

[0217] "panelsEnabled()

[0218] (Disabled1&DISABLE_EXPAND)=0&&

[0219] (Disabled1 & DISABLE_EXPAND_EXCEPT_HEADSUP)! = 0" to control the user operation of pulling down the status bar on the interface displayed on the current screen, but allow the banner notification to be displayed to remind the user.

[0220] In this way, based on the display method provided by this application, mobile phones and other terminal devices can set whether to prohibit the user operation of pulling down the status bar and whether to allow the display of banner notifications to remind users according to the needs of user experience or the business needs of the application. For example, in some immersive scenarios where interruption is not allowed, the status bar can be prohibited from being pulled down and the banner notification can be not displayed to disturb the user, thereby improving the user experience. In other immersive scenarios where interruption is appropriate, the status bar can be prohibited from being pulled down but the banner notification can be allowed to be displayed to prevent the user from missing some important notification messages, which is also conducive to improving the user experience.

[0221] It is understood that if banner notifications are allowed to be displayed, users can view or set banner notifications displayed on mobile devices and other terminal devices, and perform other related operations. Some of these user operations can also complete the process of setting attribute parameters for whether to display banner notifications. Specifically, the following is a detailed description with reference to the flowchart shown in Figure 9.

[0222] Figure 9 illustrates a schematic diagram of an implementation process for responding to user operations related to a banner notification according to an embodiment of the present application. It is understood that the execution entity of each step in the implementation process shown in Figure 9 can continue to be the aforementioned mobile phone 100. In other embodiments, the execution entity of each step in the implementation process shown in Figure 9 can also be other terminal electronic devices, which is not limited here.

[0223] As shown in Figure 9, the implementation process may include the following steps:

[0224] 901: Receive user action on banner notification.

[0225] 902: Determine whether the user operation is a click operation or a slide operation.

[0226] If the judgment result is a click operation, the following step 903 may be continued to respond to the click operation.

[0227] If the judgment result is a sliding operation, the judgment process of step 904 described below may be continued.

[0228] As an example, the above-mentioned click operation can refer to operation ② of clicking the banner notification display content shown in Figure 10a, the above-mentioned sliding operation can refer to operation ③ of sliding left and operation ④ of sliding right shown in Figure 10b, and can also refer to operation ⑤ of sliding down and operation ⑥ of sliding up shown in Figure 10c. The execution process triggered by specific user operations can be referred to the relevant description of the corresponding steps below, which will not be repeated here.

[0229] 903: In response to a click operation on the banner notification, open an interface of a related application.

[0230] As an example, referring to FIG10 a, the user can click on the display content of the banner notification 011 displayed on the mobile phone 100. Correspondingly, the mobile phone 100 can open the relevant interface of the calendar application to which the notification message displayed in the banner notification 011 belongs.

[0231] In other embodiments, as shown in FIG10 a , the user can click on the displayed content of the banner notification 012 displayed on the mobile phone 100 to answer or reject the call, etc. This is not limited here.

[0232] 904: Determine whether the direction of the sliding operation is the x direction or the y direction.

[0233] If the judgment result is the x direction, that is, the user operation is a left or right sliding operation, the following step 905 can be continued to execute the corresponding triggering process.

[0234] If the judgment result is the y direction, that is, the user operation is an up and down sliding operation, the judgment process of the following step 906 can be continued.

[0235] 905: Execute the process of deleting the notification triggered by the left or right sliding operation.

[0236] As an example, referring to operation ③ shown in FIG10b, a user swipes left on the banner notification 011 displayed on the mobile phone 100 to display the banner notification setting interface 013 shown in FIG10d. Referring to operation ④ shown in FIG10b, a user swipes right on the banner notification 012 displayed on the mobile phone 100 to delete the notification message.

[0237] In some embodiments, the left swiping operation performed by the user can also call out the setting control. Referring to the setting control 131 shown in Figure 10d, the user can click the setting control 131 to set whether to display the notification message silently or whether to display the notification message on top, etc. There is no restriction here.

[0238] 906: Determine whether the direction of the sliding operation is upward or downward.

[0239] If the judgment result is upward, that is, the user operation is an upward sliding operation, the following steps 907 to 908 can be continued to execute the corresponding trigger setting process.

[0240] If the result of the judgment is downward, that is, the user operation is a pull-down sliding operation, the following step 909 can be continued to be executed.

[0241] 907: Set the notification message displayed by the banner notification to a silent notification.

[0242] 908: Fold the notification message upwards.

[0243] As an example, referring to operation ⑥ shown in FIG10c , a user swipes upward on a banner notification 012 displayed on the mobile phone 100, which triggers the notification message displayed by the banner notification to be set to silent notification mode and triggers the upward collapse of the notification message displayed by the banner notification. It can be understood that after the banner notification 012 is collapsed, it will not block the shooting interface displayed on the mobile phone 100, and the user can continue to perform other shooting operations on the shooting interface to meet the user's needs.

[0244] 909: Does not respond to downward pull-down swipe operations.

[0245] As an example, referring to operation ⑤ shown in Figure 10c, a user swipes down on the banner notification 011 displayed on the phone 100. This operation causes the phone 100 to display more content of the notification message displayed by the banner notification. However, under the setting that prohibits pulling down the status bar but allows the display of banner notifications, the phone 100 cannot respond to the user's downward swipe operation of swiping down the banner notification, that is, it does not respond to the downward swipe operation. This can prevent the user from accidentally causing the phone 100 to exit the shooting interface or causing the shooting interface displayed on the phone 100 to be obscured by the larger banner notification window.

[0246] It is understood that if the user wishes to display more notification message content on the shooting interface shown in FIG10c above, the user can also set the SystemUI 512 through the settings application or the camera application 511 to allow the status bar to be pulled down and the banner notification to be displayed when the shooting interface is displayed on the secondary screen. The specific setting process can be referred to the relevant description of step 606 or step 612 in the interaction process shown in FIG6 above, and will not be repeated here.

[0247] Figure 11 shows a schematic diagram of the hardware structure of a terminal device according to an embodiment of the present application. The terminal device can be, for example, the foldable screen device mobile phone 100 described above. As a terminal electronic device that implements the display method provided by the present application, there is no limitation here. The following is an introduction using mobile phone 100 as an example.

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

[0249] It should be understood that the illustrated structure of the embodiment of the present invention does not constitute a specific limitation on the mobile phone 100. In other embodiments of the present application, the mobile phone 100 may include more or fewer components than shown, or some components may be combined or separated, or arranged differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

[0251] The controller can generate an operation control signal based on the instruction opcode and timing signal to complete the control of instruction fetching and execution. In the embodiment of the present application, the mobile phone 100 can use the processor 110 to run the camera application to set the shooting interface in the rear selfie mode to prohibit the operation of pulling down the status bar and whether to allow the display of banner notifications and other related codes or instructions, and generate an operation control signal through the controller to complete the instruction fetching, and then execute the relevant steps in the implementation process of the display method provided in the embodiment of the present application. The specific execution process can refer to the relevant description of Figures 1a to 10d above, which will not be repeated here.

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

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

[0254] The USB interface 130 is an interface that complies with USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the mobile phone 100 and to transfer data between the mobile phone 100 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect to other terminals, such as AR devices.

[0255] It is understood that the interface connection relationship between the modules illustrated in the embodiment of the present invention is merely an illustrative illustration and does not constitute a structural limitation on the mobile phone 100. In other embodiments of the present application, the mobile phone 100 may also adopt a different interface connection method from the above embodiment, or a combination of multiple interface connection methods.

[0256] The charging management module 140 is configured to receive charging input from a charger. The power management module 141 is configured to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, and the wireless communication module 160.

[0257] The wireless communication function of the mobile phone 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

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

[0259] The mobile communication module 150 can provide wireless communication solutions including 2G / 3G / 4G / 5G applied on the mobile phone 100.

[0260] The wireless communication module 160 can provide wireless communication solutions for application on the mobile phone 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication technology (NFC), infrared technology (IR), etc.

[0261] In some embodiments, the antenna 1 of the mobile phone 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the mobile phone 100 can communicate with the network and other devices through wireless communication technologies. The above-mentioned wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The above-mentioned GNSS may include the global positioning system (GPS), the global navigation satellite system (GLONASS), the Beidou navigation satellite system (BDS), the quasi-zenith satellite system (QZSS) and / or the satellite based augmentation system (SBAS).

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

[0263] Display screen 194 is used to display images, videos, and application interfaces. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Mini-LED, a Micro-LED, a Micro-OLED, or a quantum dot light-emitting diode (QLED). In some embodiments, mobile phone 100 may include one or N display screens 194, where N is a positive integer greater than one.

[0264] The mobile phone 100 can realize the shooting function through the ISP, camera 193, video codec, GPU, display screen 194 and application processor. Among them, the ISP is used to process the data fed back by the camera 193. The camera 193 is used to capture static images or videos. The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. The video codec is used to compress or decompress digital videos. The mobile phone 100 can support one or more video codecs. In this way, the mobile phone 100 can play or record videos in multiple encoding formats, such as: Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

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

[0266] The internal memory 121 can be used to store computer executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store an operating system, at least one application required for a function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the mobile phone 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the mobile phone 100 by running the instructions stored in the internal memory 121 and / or the instructions stored in the memory provided in the processor, such as running the applications installed on the terminal and the synchronization services preset on the terminal, interacting with the cloud to achieve the purpose of notification management, etc.

[0267] The mobile phone 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0268] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be set in the processor 110, or some functional modules of the audio module 170 can be set in the processor 110. The speaker 170A, also known as the "speaker", is used to convert audio electrical signals into sound signals. The receiver 170B, also known as the "earpiece", is used to convert audio electrical signals into sound signals. The microphone 170C, also known as the "microphone" or "microphone", is used to convert sound signals into electrical signals. The headphone jack 170D is used to connect wired headphones.

[0269] The pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, the pressure sensor 180A can be set on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor can be a device comprising at least two parallel plates with conductive material. When force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The mobile phone 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation is applied to the display screen 194, the mobile phone 100 detects the intensity of the touch operation based on the pressure sensor 180A. The mobile phone 100 can also calculate the position of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions.

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

[0271] The ambient light sensor 180L is used to sense the brightness of the ambient light.

[0272] The fingerprint sensor 180H is used to collect fingerprints.

[0273] The temperature sensor 180J is used to detect temperature.

[0274] The touch sensor 180K is also called a "touch device." The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor 180K is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the mobile phone 100, in a location different from that of the display screen 194.

[0275] Keys 190 include a power button, a volume button, etc. Keys 190 may be mechanical keys or touch keys. Mobile phone 100 may receive key inputs and generate key signal inputs related to user settings and function control of mobile phone 100.

[0276] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0277] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0278] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or disconnected from the mobile phone 100 by inserting or removing the SIM card into or from the SIM card interface 195.

[0279] References in the specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one exemplary implementation or technique disclosed according to the embodiment of the present application. The appearances of the phrase "in one embodiment" in various places in the specification do not necessarily all refer to the same embodiment.

[0280] The disclosure of the embodiments of the present application also relates to an operating device for executing the text. The device can be constructed specifically for the required purpose or it can include a general-purpose computer that is selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer-readable medium, such as, but not limited to, any type of disk, including a floppy disk, an optical disk, a CD-ROM, a magneto-optical disk, a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic or optical card, an application-specific integrated circuit (ASIC) or any type of medium suitable for storing electronic instructions, and each can be coupled to a computer system bus. In addition, the computer mentioned in the specification can include a single processor or can be an architecture involving multiple processors for increased computing power.

[0281] In addition, the language used in this specification has been primarily selected for readability and instructional purposes and may not be selected to describe or limit the disclosed subject matter. Therefore, the present disclosure of embodiments is intended to illustrate, not to limit, the scope of the concepts discussed herein.

Claims

1. A display method, applied to a terminal device, characterized in that: The terminal device comprises a display screen, the display screen comprises at least a first screen, a second screen and a first camera, wherein the first screen and the first camera of the terminal device are respectively located on two sides of the terminal device; and When the terminal device is in an unfolded state, the first screen and the second screen are located on the same side of the terminal device; In a folded state of the terminal device, the first camera and the second screen are located on the same side of the terminal device; and the method includes: Based on the terminal device being in a folded state, displaying a first interface of a first application on a first screen; At a first time point, receiving a first notification of a second application, and displaying a banner notification of the first notification on the first screen; At a second time point, receiving a first operation of pulling down the status bar to display a notification list, wherein the notification list includes at least one notification option; In response to the user clicking on an option of the first notification, displaying a second interface of a second application; After the user flips the phone, the third interface of the first application is displayed on the second screen; At a third time point, receiving a second notification of the second application, and displaying a banner notification of the second notification on the second screen; At a fourth time point, a second operation of pulling down the status bar is received, and the notification list is not displayed.

2. The method according to claim 1, characterized in that The first screen and the second screen are two display areas of the display screen; and, The third interface is the interface after the first interface is adjusted to fit the size of the second screen.

3. The method according to claim 1, characterized in that The method comprises: After the fourth time point, based on the terminal device being in the folded state, the first interface of the first application is displayed on the second screen, and the second operation of pulling down the status bar is not responded to.

4. The method according to any one of claims 1 to 3, characterized in that The attribute parameters of the status bar include a first attribute parameter and a second attribute parameter, wherein: The first attribute parameter is used to indicate whether the interface displayed on the first screen or the second screen responds to the operation of pulling down the status bar, and indicates whether a banner notification is displayed on the interface displayed on the first screen or the second screen; The second attribute parameter is used to indicate whether the interface displayed on the first screen or the second screen responds to the operation of pulling down the status bar, and indicates whether a banner notification is displayed on the interface displayed on the first screen or the second screen.

5. The method according to claim 4, characterized in that The types of the first attribute parameter and the second attribute parameter include a flag attribute, and The first attribute parameter includes an attribute parameter “DISABLE_EXPAND_EXCEPT_HEADSUP”, and the second attribute parameter includes an attribute parameter “DISABLE_EXPAND”.

6. The method according to claim 5, characterized in that The method comprises: At the first time point, based on the value of the second attribute parameter being set to 0 and the value of the first attribute parameter being set to 0, receiving a first notification of a second application, and displaying a banner notification of the first notification on the first screen; At the second time point, based on the value of the second attribute parameter being set to 0 and the value of the first attribute parameter being set to Set to 0, receive the first operation of pulling down the status bar, and display the notification list.

7. The method according to claim 5, characterized in that The method comprises: At the third time point, based on the value of the second attribute parameter being set to 0 and the value of the first attribute parameter being set to 1, receiving a second notification of the second application, and displaying a banner notification of the second notification on the second screen; At the fourth time point, based on the value of the second attribute parameter being set to 0 and the value of the first attribute parameter being set to 1, the second operation of pulling down the status bar is received, and the notification list is not displayed.

8. The method according to claim 5, characterized in that The method further comprises: At a fifth time point, based on the value of the second attribute parameter being set to 1, a third notification of the second application is received, and a banner notification of the third notification is not displayed on the first screen or the second screen; At a sixth time point, based on the value of the second attribute parameter being set to 1, a third operation of pulling down the status bar is received, and the notification list is not displayed.

9. The method according to claim 8, characterized in that The setting of the value of the second attribute parameter to 1 includes: receiving a value set by the first application for the second attribute parameter, and setting the value of the second attribute parameter to 1; or, A setting operation corresponding to the second attribute parameter in a setting interface by the user is received, and a value of the second attribute parameter is set to 1.

10. The method according to any one of claims 1 to 9, characterized in that The operation of pulling down the status bar includes: A fourth operation in which the user slides downward on the touch area near the first side at the top of the screen displaying the first screen or the second screen, wherein the fourth operation enables the terminal device to display a notification list; or A fifth operation is performed in which the user slides downward on a touch area near a second side at the top of the screen displaying the first screen or the second screen, wherein the fifth operation enables the terminal device to display a control center, wherein the first side and the second side are different sides of the top of the screen of the first screen or the second screen.

11. A terminal device, characterized in that: include: one or more processors; One or more memories; the one or more memories store one or more programs, and when the one or more programs are executed by the one or more processors, the terminal device executes the display method described in any one of claims 1 to 10.

12. A computer readable medium, characterized in that The readable medium stores instructions, which, when executed on a computer, enable the computer to execute the display method according to any one of claims 1 to 10.

Images