Operation response method, terminal device and storage medium

Abstract

The present application belongs to the technical field of terminals. Disclosed are an operation response method, a terminal device and a storage medium. The method comprises: displaying a first interface, wherein the first interface comprises a desktop; receiving a first swiping operation acting on a pressure-sensitive button; and in response to the first swiping operation, pulling down from the top of the first interface to display a notification center and / or a control center. In this way, users can pull down a notification center and / or a control center by swiping on a pressure-sensitive button, thereby expanding operation modes of pulling down the notification center and / or the control center, providing the users with diversified operation modes of pulling down the notification center and the control center, and making user operation more convenient and efficient.

Description

Operation response method, terminal device and storage medium

[0001] This application claims priority to Chinese patent application filed on June 29, 2024, with application number 202410874929.0 and entitled "Operation Response Method, Terminal Equipment and Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] With the development of terminal devices, to facilitate user operation, mobile phones, tablets, and other terminal devices typically have a notification center and a control center. The notification center serves as the entry point for managing push notifications from applications on the terminal device or displaying persistent information. The control center serves as the entry point for controlling the device's status.

[0004] Currently, users can access the notification center or control center by swiping down from the top of the screen. For example, users can swipe down from the top left side of the screen to pull down the notification center and from the top right side to pull down the control center. However, this method of pulling down the notification center or control center has certain limitations and lacks flexibility. Summary of the Invention

[0005] This application provides an operation response method, terminal device, and storage medium, which can expand the operation modes of the pull-down notification center or control center, improve the diversity and flexibility of operation, and enhance the convenience of user operation. The technical solution is as follows:

[0006] In a first aspect, an operation response method is provided, the method comprising: displaying a first interface, the first interface including a desktop; receiving a first sliding operation applied to a pressure-sensitive button; and in response to the first sliding operation, pulling down from the top of the first interface to display a notification center and / or a control center.

[0007] This allows users to pull down the notification center and / or control center by sliding their fingers across the pressure-sensitive buttons, thus expanding the ways to access these notifications and providing users with diverse notification options. Moreover, compared to swiping down from the top of the screen, using pressure-sensitive buttons to pull down the notification center and / or control center is more convenient and easier, allowing for one-handed operation and improving user experience.

[0008] Pressure-sensitive buttons are buttons that operate by sensing pressure. They detect the pressure applied to the button to perform its function. For example, pressure-sensitive buttons can identify user input by detecting the pressure applied to the button, such as tapping, pressing lightly, or pressing firmly. Furthermore, pressure-sensitive buttons can also identify sliding actions by detecting pressure at different locations on the button.

[0009] In one embodiment, a first pressure-sensitive button is provided on the first side of the terminal device, and a second pressure-sensitive button is provided on the second side. For example, a left pressure-sensitive button is provided on the left side, and a right pressure-sensitive button is provided on the right side. This allows users to easily pull down the notification center and control center using the pressure-sensitive buttons on both sides, further improving the convenience of the pull-down operation.

[0010] In one embodiment, the pressure-sensitive button can be located on the metal frame on the side of the terminal device, or on the side display screen or back cover. This application embodiment does not limit the location of the pressure-sensitive button on the side.

[0011] In one embodiment, the button surface of the pressure-sensitive button can be integrally formed with the metal frame; for example, a portion of the metal frame can be formed as the button surface of the pressure-sensitive button. This avoids compromising the seamless appearance of the metal frame, improving not only the device's aesthetics but also increasing the water resistance and lifespan of the pressure-sensitive button.

[0012] In one embodiment, the side with the pressure-sensitive button does not have a physical button. That is, in this embodiment, the device may not have a physical button to increase the water resistance and lifespan of the pressure-sensitive button.

[0013] In one embodiment, in response to a first sliding operation on a first pressure-sensitive button, a notification center is displayed by pulling down from the top of the first interface; in response to a first sliding operation on a second pressure-sensitive button, a control center is displayed by pulling down from the top of the first interface.

[0014] In this way, users can pull down the notification center and control center respectively using the pressure-sensitive buttons on the two sides, further improving the convenience of the pull-down operation.

[0015] The first sliding operation can be a sliding operation along a preset direction, such as along the length or width of the pressure-sensitive button. For example, the first sliding operation is an upward sliding operation.

[0016] In one embodiment, before receiving a first sliding operation on the pressure-sensitive button, a first pressing operation on the pressure-sensitive button may also be received, and in response to a first sliding operation on the pressure-sensitive button after the first pressing operation, a notification center and / or control center are displayed from the top of the first interface.

[0017] The first press operation refers to a press operation where the press pressure meets a first preset condition and / or the press duration is greater than or equal to a first duration threshold. For example, the first press operation can be a light-long press operation. For example, the first preset condition can be that the press pressure is greater than or equal to a first preset pressure threshold, or greater than or equal to the first preset pressure threshold and less than a second preset pressure threshold. The first preset pressure threshold and the second preset pressure threshold can be set in advance as needed.

[0018] In other words, pulling down the notification center and / or control center requires a first press followed by a swipe. Users need to press and then swipe the pressure-sensitive button to pull down the notification center and / or control center. This reduces the probability of accidentally pulling down the notification center and / or control center due to accidental swipes, improving the accuracy of the pull-down process.

[0019] In one embodiment, after a user performs a first press operation on the pressure-sensitive button, a focus animation effect can also be displayed at the top of the terminal device's screen in response to the first press operation. For example, a focus animation effect can be displayed in the status bar at the top. This focus animation effect can be a highlight animation effect or other animation effects, and this application embodiment does not limit this.

[0020] By displaying a focus animation at the top of the screen, the user can be indicated to pull down the notification center and / or control center via a pressure-sensitive button.

[0021] In one embodiment, when the pressure-sensitive button is located on the left side of the terminal device, a focus animation is displayed in the first part of the status bar of the first interface, and the first part is located on the left side of the status bar; when the pressure-sensitive button is located on the right side of the terminal device, a focus animation is displayed in the second part of the status bar of the first interface, and the second part is located on the right side of the status bar.

[0022] For example, in response to a light long press on the left pressure-sensitive button, a focus animation is displayed in the left area of ​​the top status bar; in response to a light long press on the right pressure-sensitive button, a focus animation is displayed in the right area of ​​the top status bar.

[0023] Displaying a focus animation on the left side of the status bar reminds users that they can pull down the notification center using the pressure-sensitive button; similarly, displaying a focus animation on the right side of the status bar reminds users that they can pull down the control center using the pressure-sensitive button. This improves the user experience.

[0024] In one embodiment, in response to the first press operation, the pressure-sensitive button can also be controlled to provide vibration feedback to improve the user's interactive experience.

[0025] In one embodiment, after pulling down from the top of the first interface to display the notification center and / or control center, a second swipe operation can be received on a pressure-sensitive button, and in response to the second touch operation, the display of the notification center and / or control center can be canceled.

[0026] This allows users to collapse the notification center and / or control center by sliding a pressure-sensitive button after pulling it down, further improving the convenience of user operation.

[0027] The second sliding operation can be a sliding operation in the opposite direction to the first sliding operation. For example, if the first sliding operation is a downward sliding operation, the second sliding operation is an upward sliding operation.

[0028] In one embodiment, before receiving a second sliding operation on the pressure-sensitive button, a second pressing operation on the pressure-sensitive button may also be received, and in response to a second sliding operation on the pressure-sensitive button after the second pressing operation, the display of the notification center and / or control center is then cancelled.

[0029] The second pressing operation refers to a pressing operation where the pressing pressure meets a second preset condition, and / or the pressing duration is greater than or equal to a second duration threshold. For example, the second preset condition can be that the pressing pressure is greater than or equal to a third preset pressure threshold, or greater than or equal to a first preset pressure threshold and less than a fourth preset pressure threshold. The second preset pressure threshold and the fourth preset pressure threshold can be set in advance as needed.

[0030] In other words, pulling down the notification center and / or control center requires a second press followed by a second swipe. Users need to press and then swipe the pressure-sensitive button to collapse the notification center and / or control center. This reduces accidental collapse caused by accidental swiping and improves operational accuracy.

[0031] In one embodiment, control can also be achieved via pressure-sensitive buttons in audio and video playback scenarios.

[0032] As an example, a second interface can be displayed, which is an audio and video playback interface; receive sliding operations on the pressure-sensitive buttons; and in response to the sliding operations on the pressure-sensitive buttons, switch the currently playing audio and video to the previous or next audio and video.

[0033] Among them, audio and video can be either audio or video, and video can be short video or long video, etc.

[0034] This allows users to quickly switch between audio and video by sliding pressure-sensitive buttons, expanding the ways to switch audio and video and providing users with diverse operation methods. Moreover, compared to users sliding their fingers on the screen to switch audio and video, using pressure-sensitive buttons is more convenient and easier, for example, it can be done with one hand, thus making it easier for users to operate and improving the user experience.

[0035] As an example, the audio and video playback interface is a short video playback interface. In response to the third swipe operation on the pressure-sensitive button, the page of the short video is gradually moved out from the top of the second interface, and the page of the next short video is gradually moved in from the bottom of the second interface, so as to switch the short video to the next short video; in response to the fourth swipe operation on the pressure-sensitive button, the page of the short video is gradually moved out from the bottom of the second interface, and the page of the previous short video is gradually moved out from the top of the second interface, so as to switch the short video to the previous short video.

[0036] The third and fourth sliding operations are in opposite directions. For example, the third and fourth sliding operations are respectively an upward sliding operation and a downward sliding operation.

[0037] In this way, by sliding the pressure-sensitive button, the current short video page can be gradually switched to the previous or next short video page, achieving a page-turning effect for short videos.

[0038] In one embodiment, control can also be achieved via pressure-sensitive buttons during camera shooting.

[0039] As an example, a third interface is displayed, which is the camera shooting interface; it receives sliding operations on the pressure-sensitive buttons; and in response to the sliding operations on the pressure-sensitive buttons, it adjusts the camera's focus.

[0040] The camera interface can be a photo-taking interface or a shooting interface, etc.

[0041] This allows users to quickly adjust the focus by sliding the pressure-sensitive buttons, expanding the focusing operation methods and providing users with diverse focusing options. Moreover, compared to the method of focusing by spreading or pinching two fingers on the screen, using pressure-sensitive buttons to focus is more convenient and easier, for example, it can be done with one hand or one finger, thus making it easier for users to operate and improving the user experience.

[0042] In one embodiment, the camera's focal length is increased in response to a fifth sliding operation on the pressure-sensitive button; and the camera's focal length is decreased in response to a sixth sliding operation on the pressure-sensitive button.

[0043] The sixth swipe operation is in the opposite direction to the fifth swipe operation. For example, the fifth swipe operation is an upward swipe, and the sixth swipe operation is a downward swipe, respectively.

[0044] In one embodiment, control can also be achieved via pressure-sensitive buttons in an image browsing scenario.

[0045] As an example, a fourth interface can be displayed, and the fifth interface includes the first image; a sliding operation is received on the pressure-sensitive button; in response to the sliding operation on the pressure-sensitive button, the first image is scaled and displayed.

[0046] This allows users to quickly zoom in and out of images by sliding pressure-sensitive buttons, expanding the zoom options and providing users with diverse zooming operations. Moreover, compared to zooming by spreading or pinching two fingers on the screen, using pressure-sensitive buttons for zooming is more convenient and easier, as it can be done with one hand or one finger, thus improving user experience.

[0047] In one embodiment, in response to a seventh sliding operation on the pressure-sensitive button, the first image is enlarged and displayed; in response to an eighth sliding operation on the pressure-sensitive button, the first image is reduced in size. The eighth sliding operation is in the opposite direction to the seventh sliding operation. For example, the seventh and eighth sliding operations are respectively an upward sliding operation and a downward sliding operation.

[0048] In one embodiment, the operating system of the terminal device includes an input reader and a system user interface.

[0049] In response to the first swipe operation, during the process of pulling down from the top of the first interface to display the notification center and / or control center, the input reader can receive swipe data reported by the pressure-sensitive device driver corresponding to the pressure-sensitive button, and generate a screen swipe event based on the swipe data. The swipe data is the swipe data generated by the first swipe operation on the pressure-sensitive button. The input reader sends the screen swipe event to the system user interface. In response to the screen swipe event, the system user interface pulls down from the top of the first interface to display the notification center and / or control center.

[0050] In this way, the sliding operation on the pressure-sensitive button can be mapped to the sliding operation on the screen, so that the terminal device can respond to the sliding operation on the pressure-sensitive button by responding to the sliding operation on the screen, thereby improving the response performance.

[0051] In one embodiment, the input reader generates a screen swipe event based on swipe data, including: the input reader processes the swipe data according to preset mapping parameters to obtain event parameters of the screen swipe event, the preset mapping parameters being used to map the swipe event on the pressure-sensitive button to the swipe event on the screen; the input reader generates the screen swipe event based on the event parameters.

[0052] The preset mapping parameters refer to the parameters that are pre-set to map swipe events on the pressure-sensitive buttons to swipe events on the screen. For example, these parameters may include at least one of the following: starting point, swipe finger requirements (whether it's a single finger or multiple fingers, etc.), swipe direction, swipe gesture, and swipe distance mapping ratio. These mapping parameters will affect the creation of subsequent swipe events and the response to them.

[0053] As an example, different mapping parameters can be updated in different scenarios to simulate different swipe events on the pressure-sensitive button as different swipe events on the screen. For instance, in scenarios like the desktop where notifications are pulled down, the swipe event on the pressure-sensitive button is converted into a swipe event that starts from near the top of the screen and slides downwards to simulate the notification pull-down operation; in short video scenarios like TikTok, the swipe event on the pressure-sensitive button is converted into a swipe event that slides from the middle of the screen to simulate page turning; in camera scenarios, the swipe event on the pressure-sensitive button is converted into a swipe event where two fingers are spread or pinched on the screen to simulate focusing; and in scenarios like the gallery and map, the swipe event on the pressure-sensitive button is converted into a swipe event where two fingers are spread or pinched on the screen to simulate zooming and other operations.

[0054] In one embodiment, when the pressure-sensitive button is a pressure-sensitive button located on the first side of the terminal device, the screen swipe event is a swipe-down event on the left side of the screen; the system user interface can respond to the screen swipe event by pulling down from the top of the first interface to display the notification center.

[0055] In one embodiment, when the pressure-sensitive button is located on the second side of the terminal device, the screen swipe event is a swipe-down event on the right side of the screen; the system user interface responds to the screen swipe event by pulling down the control center from the top of the first interface.

[0056] In one embodiment, the operating system further includes a phone window manager. Before receiving a first swipe operation applied to the pressure-sensitive key, the pressure-sensitive key receives a first press event, where the first press operation refers to a press operation with a duration greater than or equal to a first duration threshold. An input reader receives the original key event reported by the pressure-sensitive device driver corresponding to the pressure-sensitive key, and generates a first key event based on the original key event, where the original key event is the key event generated by the first press operation applied to the pressure-sensitive key. The input reader sends the first key event to the phone window manager. The phone window manager performs gesture detection based on the first key event, and if a long press gesture is detected, sends a first notification to the system user interface, where the first notification indicates that a long press gesture has been detected on the pressure-sensitive key, where a long press gesture refers to a press gesture that is continuously pressed on the pressure-sensitive key for a duration threshold. In response to the first notification, the system user interface displays a focus animation at the top of the first interface.

[0057] In one embodiment, the first key event is a first key press event. The phone window manager performs gesture detection based on the first key event, including: if the phone window manager does not receive a first key release event corresponding to the first key press event within a first duration threshold after receiving the first key press event, it determines that a long press gesture has been detected; if the phone window manager receives a first key release event corresponding to the first key press event within the first duration threshold after receiving the first key press event, it determines that a long press gesture has not been detected.

[0058] In one embodiment, the system user interface responds to a first notification by displaying a focus animation at the top of the first interface, including: when the first notification indicates that a long press gesture is detected on a first pressure-sensitive button, displaying the focus animation in a first portion of the status bar of the first interface, wherein the first pressure-sensitive button is a pressure-sensitive button located on a first side of the terminal device, and the first portion of the status bar is located on the left side; and when the first notification indicates that a long press gesture is detected on a second pressure-sensitive button, displaying the focus animation in a second portion of the status bar of the first interface, wherein the second pressure-sensitive button is a pressure-sensitive button located on a second side of the terminal device, and the second portion of the status bar is located on the right side.

[0059] In one embodiment, the operating system also includes a vibrator management service. When the phone window manager detects a long press gesture, it can also send a second notification to the vibration management server. The second notification indicates that a long press gesture has been detected. Based on the second notification, the vibration management service controls the pressure-sensitive button to vibrate to improve the user's interactive experience.

[0060] Secondly, an operation response device is provided, which has the function of implementing the operation response method behavior described in the first aspect. The operation response device includes at least one module, which is used to implement the operation response method provided in the first aspect.

[0061] Thirdly, an operation response device is provided, comprising a processor and a memory. The memory stores a program that supports the operation response device in executing the operation response method provided in the first aspect, and stores data related to implementing the operation response method described in the first aspect. The processor is configured to execute the program stored in the memory. The operation response device may further include a communication bus for establishing a connection between the processor and the memory.

[0062] Fourthly, a computer-readable storage medium is provided, wherein instructions are stored therein, which, when executed on a computer, cause the computer to perform the operation response method described in the first aspect.

[0063] Fifthly, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the operation response method described in the first aspect above.

[0064] The technical effects achieved by the second, third, fourth, and fifth aspects mentioned above are similar to those achieved by the corresponding technical means in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0065] Figure 1 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0066] Figure 2 is a schematic side view of a terminal device provided in an embodiment of this application;

[0067] Figure 3 is a structural schematic diagram of a pressure-sensitive button provided in an embodiment of this application;

[0068] Figure 4 is a schematic diagram of the touch operation of a pressure-sensitive button provided in an embodiment of this application;

[0069] Figure 5 is a schematic diagram of operating pressure-sensitive buttons when holding a mobile phone, according to an embodiment of this application;

[0070] Figure 6 is a schematic diagram of a continuously operating pressure-sensitive button provided in an embodiment of this application;

[0071] Figure 7 is a schematic diagram of another continuously operating pressure-sensitive button provided in an embodiment of this application;

[0072] Figure 8 is a schematic diagram of a notification center being pulled down via a pressure-sensitive button according to an embodiment of this application;

[0073] Figure 9 is a schematic diagram of canceling the display of the notification center by using a pressure-sensitive button according to an embodiment of this application;

[0074] Figure 10 is a schematic diagram of a control center provided by pulling down a pressure-sensitive button according to an embodiment of this application;

[0075] Figure 11 is a schematic diagram of canceling the display of the control center by using a pressure-sensitive button according to an embodiment of this application;

[0076] Figure 12 is a schematic diagram of increasing the camera focal length by using a pressure-sensitive button according to an embodiment of this application;

[0077] Figure 13 is a schematic diagram of reducing the camera focal length by using a pressure-sensitive button according to an embodiment of this application;

[0078] Figure 14 is a schematic diagram of switching to the next short video via a pressure-sensitive button according to an embodiment of this application;

[0079] Figure 15 is a schematic diagram of switching to the previous short video via a pressure-sensitive button according to an embodiment of this application;

[0080] Figure 16 is a schematic diagram of a method for scaling the displayed content using pressure-sensitive buttons according to an embodiment of this application;

[0081] Figure 17 is a structural schematic diagram of a terminal device provided in an embodiment of this application;

[0082] Figure 18 is a block diagram of a software system for a terminal device provided in an embodiment of this application;

[0083] Figure 19 is a logical schematic diagram of a scene recognition section provided in an embodiment of this application;

[0084] Figure 20 is a logical schematic diagram of a key event processing part provided in an embodiment of this application;

[0085] Figure 21 is a logical schematic diagram of a gesture recognition part provided in an embodiment of this application;

[0086] Figure 22 is a schematic diagram of the processing modules and related operations involved in a gesture recognition process provided in an embodiment of this application;

[0087] Figure 23 is a logical diagram of a multi-step operation part after a gesture is completed, according to an embodiment of this application;

[0088] Figure 24 is a logical schematic diagram of a mapping parameter update and sliding event processing part provided in an embodiment of this application;

[0089] Figure 25 is a schematic diagram of a process for displaying a notification center by pulling down a pressure-sensitive button according to an embodiment of this application.

[0090] Figure 26 is a flowchart illustrating a control center that is displayed by pulling down based on a touch operation on a pressure-sensitive button, according to an embodiment of this application. Detailed Implementation

[0091] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0092] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limiting purposes, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details.

[0093] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0094] It should also be understood that in the embodiments of this application, "one or more" refers to one, two, or more; "and / or" describes the relationship between the associated objects, indicating that three relationships can exist; for example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0095] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," "fourth," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0096] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0097] This application provides an operation response method applied to a terminal device equipped with pressure-sensitive buttons. This terminal device can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a mobile phone, smart TV, wearable device, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) electronic device, augmented reality (AR) electronic device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal device.

[0098] Next, we will explain the pressure-sensitive buttons in detail.

[0099] Pressure-sensitive buttons are buttons that operate by sensing pressure. They detect the pressure applied to the button to perform its function. For example, pressure-sensitive buttons can identify user input by detecting the pressure applied, such as tapping, pressing, or pressing firmly. They can also identify sliding actions by detecting pressure at different locations on the button. Furthermore, pressure-sensitive buttons can provide tactile feedback to enhance the user experience.

[0100] Pressure-sensitive buttons are triggered by touch operations. The pressure on a pressure-sensitive button refers to the pressure exerted by an external object (such as a stylus or the user's finger) on the contact point of the button. This pressure can also be referred to as intensity or contact strength. It should be understood that the external form of a pressure-sensitive button can be a physical button (such as a solid button), or it can be a specific surface or input area, etc. This application embodiment does not limit this. It should also be understood that pressure-sensitive buttons can be called intensity-sensitive surfaces, intensity-sensitive input regions, intensity-sensitive buttons, intensity-sensitive solid state buttons, pressure-sensing surfaces, or pressure-sensing input areas, etc. This application embodiment does not specifically limit the names of these function buttons.

[0101] Currently, the buttons configured on terminal devices are usually physical buttons (such as volume buttons and power buttons). Physical buttons refer to traditional mechanical buttons, which operate by connecting or disconnecting the circuit when pressed. Their function is mainly achieved by detecting fixed press and release operations. The following Table 1 will illustrate the differences between traditional physical buttons and the pressure-sensitive buttons described in the embodiments of this application.

[0102] Table 1

[0103] As shown in the comparative analysis in Table 1 above, pressure-sensitive buttons have advantages over traditional physical buttons, including longer lifespan, faster response speed, higher sensitivity, and better waterproof performance. Furthermore, the surface of pressure-sensitive buttons can be integrally molded with the device's exterior, allowing for button operation without compromising the device's aesthetics, such as providing a similar control method to physical buttons.

[0104] In one embodiment, the terminal device may provide pressure-sensitive buttons on one or more sides of the device, or on other locations such as the device's display screen or back cover. This application embodiment does not limit the location of the pressure-sensitive buttons.

[0105] Next, taking a mobile phone as an example, we will introduce terminal devices with pressure-sensitive buttons on the side of the device.

[0106] Please refer to Figure 1, which is a structural schematic diagram of a terminal device provided in an embodiment of this application. As shown in Figure 1, taking a mobile phone as an example, a long strip-shaped pressure-sensitive button is provided on the left and right sides of the mobile phone.

[0107] It should be understood that the pressure-sensitive button setting in Figure 1 is merely illustrative and does not constitute a limitation on the pressure-sensitive button setting method. For example, a mobile phone may also have pressure-sensitive buttons on only one side (such as the left or right side), or the pressure-sensitive buttons on a certain side of the mobile phone may include multiple buttons (such as two), and the shape of the pressure-sensitive buttons may also be set to other shapes. The embodiments of this application do not limit the setting position, number, shape, and distribution of pressure-sensitive buttons.

[0108] Please refer to Figure 2, which is a schematic side view of a terminal device provided in an embodiment of this application. As shown in Figure 2, taking a mobile phone as an example, the external structure of the mobile phone includes a display screen 21, a metal frame 22, and a back cover 23. The metal frame 22 is located between the display screen 21 and the back cover 23, surrounding the four sides of the mobile phone (top, bottom, left, and right), and is used to protect the internal structure between the display screen 21 and the back cover 23. Pressure-sensitive buttons are provided on both the left and right sides of the metal frame 22. As shown in the left view of Figure 2, a pressure-sensitive button 24 (i.e., the left-side pressure-sensitive button) is provided on the left side of the metal frame 22. As shown in the right view of Figure 2, a pressure-sensitive button 25 (i.e., the right-side pressure-sensitive button) is provided on the right side of the metal frame 22.

[0109] As an example, the surface of the pressure-sensitive button can be integrally formed with the metal frame; for instance, a portion of the metal frame can be used as the button surface. For example, a portion of the left side of the metal frame 22 (such as the upper area) can be used as the button surface of the pressure-sensitive button 24, and a portion of the right side of the metal frame 22 (such as the upper area) can be used as the button surface of the pressure-sensitive button 25. This avoids compromising the seamless appearance of the metal frame, improving the device's aesthetics and increasing the water resistance and lifespan of the pressure-sensitive button.

[0110] It should be understood that pressure-sensitive buttons can also be separated from their metal frame, for example, the pressure-sensitive buttons can be embedded in the metal frame. The specific implementation method can be set according to actual needs.

[0111] It should also be understood that Figure 2 only shows an example where the pressure-sensitive button is located on the metal frame 22 between the display screen 21 and the back cover 23. In other implementations, the pressure-sensitive button can also be located on other external components such as the display screen 21 or the back cover 23. For example, if the display screen 21 is a curved screen and the curved screen can extend to cover most of the side of the phone, the pressure-sensitive button can also be located on the side of the curved screen 10 (extending to cover part of the side of the phone). Similarly, the pressure-sensitive button can also be located on the side of the back cover 23 (extending to cover part of the side of the phone). This application does not limit the supporting component of the pressure-sensitive button.

[0112] Next, we will introduce the structure of the pressure-sensitive button.

[0113] Please refer to Figure 3, which is a structural schematic diagram of a pressure-sensitive button provided in an embodiment of this application.

[0114] As shown in Figure 3, a pressure-sensitive button may include a touch surface and a pressure sensor. The touch surface is the button surface on the pressure-sensitive button that allows the user to perform touch operations. The pressure sensor is used to sense the pressure on the touch surface and generate a corresponding output signal. For example, the pressure sensor can output the generated output signal to the processor of the terminal device. The pressure sensor may be located below or inside the touch surface. There may be one pressure sensor or a group of pressure sensors. The pressure sensor may be a capacitive sensor, a resistive sensor, a voltage pressure sensor, an electromagnetic pressure sensor, or a vibrating wire pressure sensor, etc. The embodiments of this application do not limit the type of pressure sensor.

[0115] In one embodiment, the pressure-sensitive button may further include a haptic feedback unit for generating haptic feedback in the pressure-sensitive button area through vibration or other means. For example, the haptic feedback unit may include a vibrator (such as a surface oscillator) capable of generating vibration to produce haptic feedback in the pressure-sensitive button area.

[0116] As an example, the haptic feedback unit can provide multiple haptic feedback modes, each corresponding to a different touch method on the pressure-sensitive button, to generate different modes of haptic feedback for different touch methods. For instance, multiple haptic feedback modes include different vibration feedback modes, each corresponding to a different touch method on the pressure-sensitive button, to generate different modes of vibration feedback for different touch methods. In one possible implementation, different vibration feedback modes can be set based on one or more of vibration amplitude, vibration duration, and vibration frequency; that is, different vibration feedback modes differ in one or more aspects of vibration amplitude, vibration duration, and vibration frequency.

[0117] In one embodiment, touch operations on the pressure-sensitive button may include basic operations such as pressing and sliding. Of course, with technological advancements, other types of touch operations may also be included, and this application does not limit this.

[0118] Next, we will explain the pressing and sliding operations in detail.

[0119] Press operation

[0120] Pressing refers to pressing on a pressure-sensitive button.

[0121] As an example, different pressure levels can be set based on the amount of pressure applied to the button surface, thus dividing the pressing operation on the pressure-sensitive button into different pressure levels. For example, depending on the pressing pressure, the pressing operation can include tap, light press, and hard press.

[0122] In one possible implementation, three pressure levels can be set. For example, a pressing operation with a pressure greater than or equal to a first pressure threshold and less than a second pressure threshold is set as a level one pressing operation; a pressing operation with a pressure greater than or equal to the second pressure threshold and less than a third pressure threshold is set as a level two pressing operation; and a pressing operation with a pressure greater than or equal to the third pressure threshold is set as a level three pressing operation. Here, the first pressure threshold is greater than or equal to 0. The second pressure threshold is greater than the first pressure threshold, and the third pressure threshold is greater than the second pressure threshold.

[0123] In one possible implementation, the first-level press operation, the second-level press operation, and the third-level press operation can be referred to as a light tap operation, a light press (also known as a light touch) operation, and a heavy press operation, respectively.

[0124] Please refer to Figure 4, which is a schematic diagram of the touch operation of a pressure-sensitive button provided in an embodiment of this application. As shown in Figure 4(a), the pressure-sensitive button can recognize three levels of pressure sensitivity. G0, G1, and G2 are three pressure thresholds with successively increasing pressure values. Pressing operations with pressure in [G0, G1) are recognized as light tap operations, pressing operations with pressure in [G1, G2) are recognized as light press operations, and pressing operations with pressure in [G2, ∞) are recognized as heavy press operations.

[0125] In one embodiment, the pressing operation on the pressure-sensitive button can also be classified according to the duration of the pressing operation, such as short press and long press. A short press is a pressing operation that is immediately released after pressing, while a long press is a pressing operation whose duration is longer than a first duration threshold.

[0126] In one embodiment, the pressing operation on the pressure-sensitive button can be categorized based on the magnitude of the pressing force and the duration. For example, it can be divided into light tap, light short press, light long press, heavy short press, heavy long press, etc.

[0127] Slide operation

[0128] A sliding operation refers to the action of sliding on a pressure-sensitive button.

[0129] In one embodiment, a sliding operation on the pressure-sensitive button may include a sliding operation along the length direction of the pressure-sensitive button, or a sliding operation along the width direction of the pressure-sensitive button, etc. It should be understood that it may also include sliding operations along other directions, and this application embodiment does not limit this.

[0130] For example, as shown in Figure 4(b), the sliding operation on the pressure-sensitive button includes an upward sliding operation and a downward sliding operation. In addition, the sliding operation can also include sliding operations in other directions, such as sliding operations in a direction perpendicular to the display screen, such as sliding forward or backward, etc., which are not limited in this application embodiment.

[0131] In one embodiment, the basic operations (single press or slide) on the pressure-sensitive button can be combined with visual, tactile, or audio feedback to achieve a continuous interactive operation. That is, the touch operation on the pressure-sensitive button can also include continuous operations composed of two or more basic operations. For example, as shown in Figure 4(b), the continuous operation includes: tap + swipe up + press.

[0132] As an example, as shown in Figure 4(b), the various tactile feedback modes of pressure-sensitive buttons include light single-tap vibration feedback, simulated feedback of existing mechanical buttons, light press feedback + continuous vibration feedback, heavy single-tap vibration feedback, heavy feedback + continuous vibration feedback, and stepless / granular vibration feedback. Different tactile feedback modes correspond to different touch methods. For example, a light tap on a pressure-sensitive button uses light single-tap vibration feedback; a light press on a pressure-sensitive button uses simulated feedback of existing mechanical buttons; a light long press on a pressure-sensitive button uses light press feedback + continuous vibration feedback; a heavy press on a pressure-sensitive button uses heavy single-tap vibration feedback; a heavy long press on a pressure-sensitive button uses heavy feedback + continuous vibration feedback; and a sliding operation on a pressure-sensitive button (such as an upward or downward swipe) uses stepless / granular vibration feedback.

[0133] Referring to the mobile phone shown in Figure 1 above, please refer to Figure 5, which is a schematic diagram of operating pressure-sensitive buttons when holding a mobile phone according to an embodiment of this application. With pressure-sensitive buttons provided on both the left and right sides of the mobile phone, the user can use the phone by holding it with either their left or right hand. When using the phone with the left hand, the user can easily operate the left-side pressure-sensitive button with their left thumb, such as by tapping or pressing the left-side pressure-sensitive button, or by sliding on the left-side pressure-sensitive button (e.g., sliding up or down). When using the phone with the right hand, the user can easily operate the right-side pressure-sensitive button with their right thumb, such as by tapping or pressing the right-side pressure-sensitive button, or by sliding on the right-side pressure-sensitive button (e.g., sliding up or down).

[0134] It should be understood that, in addition to the thumb, users can also use other parts of their hands (such as the palm, the side of the palm, or other fingers besides the thumb) to operate the left or right pressure-sensitive buttons. Users can operate the right pressure-sensitive button with their left hand or the left pressure-sensitive button with their right hand. This application does not limit the way users operate the pressure-sensitive buttons. For example, when holding the phone with the left hand, the user can use their left index or middle finger, or other fingers close to the right pressure-sensitive button, to operate it. Similarly, when holding the phone with the right hand, the user can use their right index or middle finger, or other fingers close to the left pressure-sensitive button, to operate it.

[0135] This application provides a human-computer interaction method based on pressure-sensitive buttons. The terminal device can provide visual feedback, or both visual and tactile feedback, to the user's touch operation on the pressure-sensitive buttons. Thus, the user can control the user interface of the terminal device by touching the pressure-sensitive buttons, achieving interaction with the user interface. The user interface can be a system interface such as a desktop, or an application interface such as a system application or a third-party application.

[0136] In one embodiment, the terminal device can provide different feedback for different touch operations on the pressure-sensitive button, meaning that different touch operations on the pressure-sensitive button can achieve different functions. Furthermore, the terminal device can also provide different visual feedback for the same touch operation on the pressure-sensitive button in different scenarios, meaning that the same touch operation on the pressure-sensitive button can be used to achieve different functions in different scenarios.

[0137] In one embodiment, the touch operation on the pressure-sensitive button can achieve functions including, but not limited to, one or more of the following: pulling down the notification center and / or control center, switching audio and video, adjusting the progress bar, focusing, zooming in and out of images or pages, turning pages, adjusting volume, moving the cursor, and quickly launching related services or tasks. This application embodiment does not limit the functions that can be achieved by the touch operation on the pressure-sensitive button.

[0138] As an example, quick launch of related services or tasks includes, but is not limited to, at least one of the following: quickly opening the service page of a smart service (such as launching the yoyo service), quickly starting recording, quickly bringing up the payment code, etc.

[0139] In one embodiment, the following functions can be implemented: a pull-down notification center and / or control center in desktop scenarios; switching between audio / video or adjusting the progress bar in audio / video playback scenarios (e.g., short video playback scenarios), such as switching between short videos and adjusting the progress bar in long video playback scenarios; focusing in camera scenarios (e.g., shooting or recording); zooming in content browsing scenarios (e.g., image browsing, map browsing, or page browsing); adjusting volume in scenarios such as calls, voice playback, or audio / video playback; page turning in reading scenarios; cursor movement in information recording scenarios (e.g., note-taking); and quickly launching specific services of a specific application in scenarios where a specific application is running.

[0140] It should be understood that the embodiments in this application are merely illustrative examples of the above scenarios and functions, and the above examples do not constitute a limitation on the functions implemented by the touch operation on the pressure-sensitive button in different scenarios.

[0141] In one embodiment, the functions corresponding to different touch operations can be set by default by the terminal device or by the user. This application embodiment does not limit this.

[0142] In one embodiment, the terminal device can provide users with an entry point for setting the function of pressure-sensitive buttons. Through this entry point, users can set corresponding functions for different touch operations, or set functions for the same touch operation in different scenarios.

[0143] As an example, the terminal device can display a first setting interface for the pressure-sensitive button based on user input. This first setting interface includes various touch operation options. For example, these options may include one or more basic operation options such as tap, press, long press, hard press, long press, swipe up, or swipe down. They may also include continuous operation options corresponding to any combination of two or more basic operations. The user can tap any touch operation option, and in response, a list of selectable functions is displayed, including one or more functions. The user can select at least one function from the list, and in response to this selection, an association is established between the touch operation and the selected function. Subsequently, if the touch operation on the pressure-sensitive button is detected, the corresponding function is activated.

[0144] Basic operations refer to single pressing operations (such as tapping, pressing, long press, heavy press, long press, etc.) or sliding operations (such as swiping up or swiping down). Continuous operations are combinations of two or more basic operations.

[0145] In one embodiment, the continuous operation can be set by default by the terminal device or by user-defined settings; this application embodiment does not limit this. For example, the terminal device can also provide a user-defined settings entry for continuous operations. Through this entry, the user can combine any two or more of the above-mentioned basic operations into a custom continuous operation and set corresponding functions for the custom continuous operation. For example, the terminal device can display a second settings interface based on the user's operation. The second settings interface includes multiple basic operation options. The user can select two or more basic operation options from the multiple basic operation options. In response to the user's selection, the terminal device can combine the user-selected basic operation options into a custom continuous operation. In addition, the user can specify the execution order corresponding to the selected basic operation options. Then, the terminal device can combine the basic operations corresponding to the user-selected basic operation options into a custom continuous operation according to the user-specified execution order.

[0146] Next, an example of a continuous operation provided by an embodiment of this application will be given.

[0147] The first type of continuous operation: tap + swipe down.

[0148] A light press refers to a pressing operation where the pressure is greater than or equal to the second pressure threshold but less than the second pressure threshold.

[0149] In other words, users can first lightly press the pressure-sensitive button, and then slide up and down the pressure-sensitive button.

[0150] The second type of continuous operation: long press + swipe down.

[0151] A light press refers to a press operation where the duration of the press is greater than or equal to a first duration threshold. Specifically, the press pressure must be greater than or equal to a second pressure threshold but less than a third pressure threshold, and the press duration must be greater than or equal to the second duration threshold. The second pressure threshold, third pressure threshold, and first duration threshold can all be preset according to actual needs. For example, the first duration threshold can be 200ms, 300ms, or 400ms, etc.

[0152] As an example, the second type of sequential operation can include the following two implementations:

[0153] 1) After lightly pressing to reach the first duration threshold, slide down without lifting your hand.

[0154] For example, as shown in Figure 6, taking a first duration threshold of 300ms as an example, the user can first lightly press the pressure-sensitive button with their thumb. After the light press duration is greater than or equal to 300ms, the user can slide down from the pressing point without lifting their thumb.

[0155] 2) After pressing lightly to reach the first duration threshold, lift your finger first, and then slide your finger down on the pressure-sensitive button.

[0156] For example, as shown in Figure 7, taking a first duration threshold of 300ms as an example, the user can first lightly press the pressure-sensitive button with their thumb. After the light press duration is greater than or equal to 300ms, the user can first lift their thumb, then touch the pressure-sensitive button with their thumb and slide it down.

[0157] It should be understood that the embodiments of this application are merely illustrative examples of the above continuous operation, and the above continuous operation does not constitute a limitation on continuous operation. In other embodiments, continuous operation may also include other forms of continuous operation, such as continuous operation of pressing multiple times (e.g., two or three times).

[0158] This application does not limit the scope of the embodiments.

[0159] Next, with reference to the accompanying diagram, we will provide an example illustrating a scenario where a terminal device is controlled via touch operation on a pressure-sensitive button.

[0160] Scenario 1: Pull down the notification center and / or control center by swiping.

[0161] In one embodiment, a user can pull down the notification center and / or control center by performing a swipe operation on a pressure-sensitive button. As an example, the terminal device can, while displaying a first interface, pull down and display the notification center and / or control center in response to a swipe operation on the pressure-sensitive button. The first interface can be a specific interface such as a desktop. The swipe operation can be a swipe operation along a preset direction, such as a swipe down.

[0162] Currently, users typically pull down the notification center or control center by swiping down from the top of the screen. However, this swipe-down operation generally requires both hands, such as holding the device with one hand and using the other hand to swipe down on the screen. Therefore, this method of pulling down the notification center or control center has certain limitations; it cannot be accessed when users cannot use both hands, resulting in a lack of flexibility.

[0163] In this embodiment, by responding to a sliding operation on the pressure-sensitive button while the first interface is displayed, the notification center and / or control center are pulled down. This allows users to pull down the notification center and / or control center by sliding the pressure-sensitive button, thereby expanding the ways to pull down the notification center and / or control center and providing users with diverse notification methods. Moreover, compared to the method of pulling down notifications by swiping down from the top of the screen, the operation of using the pressure-sensitive button to pull down the notification center and / or control center is more convenient and easier, for example, it can be done with one hand, thus facilitating user operation and improving the user experience.

[0164] In one embodiment, to prevent accidental user operation, the user can also pull down the notification center and / or control center via a second consecutive operation (short press + swipe down) on the pressure-sensitive button. As an example, the terminal device can, while displaying the first interface, pull down to display the notification center and / or control center in response to the first consecutive operation on the pressure-sensitive button.

[0165] Next, referring to Figure 1 above, and taking the example of pressure-sensitive buttons on the left and right sides of the phone, we will introduce how to pull down the notification center and the control center by short press and swipe down.

[0166] The notification center serves as the entry point for managing push notifications from applications on the terminal device or displaying persistent information. It can be used to display notification messages, such as one or more notification message cards. The control center is the entry point for controlling the device status of the terminal device. It can include quick switches for various functions, such as brightness, volume, Bluetooth, and Wi-Fi, allowing users to quickly configure these settings.

[0167] 1) Pull down the notification center by performing a short press and swipe down on the pressure-sensitive button on the left side of the phone.

[0168] Please refer to Figure 8, which is a schematic diagram of pulling down the notification center via a pressure-sensitive button according to an embodiment of this application. As shown in Figure 8(a), the phone displays the desktop, which includes applications such as camera, contacts, phone, and messages. With the desktop displayed, the user lightly presses the pressure-sensitive button on the left side of the phone for 300ms. In response to the user's 300ms press of the left pressure-sensitive button, as shown in Figure 8(b), the phone displays a focus animation 81 in the left area of ​​the top status bar. It should be understood that this focus animation can be a highlight animation or other animations, and this embodiment of the application does not limit this. The focus animation indicates that the current focus is locked to the notification center, thereby instructing the user to continue performing a swipe operation on the pressure-sensitive button to pull down the notification center. As shown in Figure 8(b), after the user lightly presses the left pressure-sensitive button for 300ms, they can continue performing a swipe operation on the left pressure-sensitive button. In response to the user's swipe operation, the phone can drop down from the top to display the notification center, as shown in Figure 8(c).

[0169] Additionally, after pulling down to display the notification center, users can also collapse the notification center by performing a touch operation on the pressure-sensitive button. This touch operation can be preset or customized by the user. For example, the touch operation can be a swipe up, or a tap + swipe up, etc.

[0170] Please refer to Figure 9, which is a schematic diagram of canceling the display of the notification center by using a pressure-sensitive button according to an embodiment of this application. As shown in Figure 9(a), when the phone displays the notification center, the user can perform an upward swipe operation on the pressure-sensitive button on the left side of the phone. In response to the user's upward swipe operation, the phone can cancel the display of the already displayed notification center, as shown in Figure 9(b).

[0171] It should be understood that, in this embodiment of the application, the notification center can also be pulled down (or collapsed) via other touch operations on the pressure-sensitive button. Additionally, the notification center can also be pulled down (or collapsed) via the right-side pressure-sensitive button. The specific implementation can be set according to actual needs, such as user-defined settings; this embodiment of the application does not limit these settings.

[0172] 2) Pull down the control center by performing the first consecutive operation on the pressure-sensitive button on the right side of the phone.

[0173] Please refer to Figure 10, which is a schematic diagram of a control center being pulled down via a pressure-sensitive button according to an embodiment of this application. As shown in Figure 10(a), the phone displays a desktop, which includes applications such as camera, contacts, phone, and messages. With the desktop displayed, the user lightly presses the pressure-sensitive button on the right side of the phone for 300ms. In response to the user's 300ms press of the right pressure-sensitive button, as shown in Figure 10(b), the phone displays a focus animation 1001 in the right area of ​​the top status bar. It should be understood that this focus animation can be a highlight animation or other animations, and this embodiment of the application does not limit this. The focus animation indicates that the focus is locked to the control center, thereby instructing the user to continue performing a swipe down operation on the pressure-sensitive button to pull down the control center. As shown in Figure 10(b), after the user lightly presses the right pressure-sensitive button for 300ms, they can continue performing a swipe down operation on the right pressure-sensitive button. In response to the user's swipe down, as shown in Figure 10(c), the phone can slide down from the top to display the control center, which can include shortcut buttons for functions such as Bluetooth, Wi-Fi, mobile data, screenshot, brightness, volume, personal hotspot, and flashlight.

[0174] Additionally, after pulling down to display the control center, users can collapse it by performing a touch operation on the pressure-sensitive button. This touch operation can be preset or customized by the user. For example, the touch operation can be a swipe up, or a tap + swipe up, etc.

[0175] Please refer to Figure 11, which is a schematic diagram of canceling the display of the control center by using a pressure-sensitive button according to an embodiment of this application. As shown in Figure 11(a), when the control center is displayed on the phone, the user can perform an upward swipe operation on the pressure-sensitive button on the right side of the phone. In response to the user's upward swipe operation, the phone can cancel the display of the already displayed control center, as shown in Figure 11(b).

[0176] It should be understood that, in this embodiment of the application, the control center can also be pulled down (or collapsed) via other touch operations on the pressure-sensitive button (such as swiping up or down). Additionally, the control center can also be pulled down (or collapsed) via the left-side pressure-sensitive button or pressure-sensitive buttons located in other positions. The specific implementation can be set according to actual needs, such as user-defined settings; this embodiment of the application does not limit these settings.

[0177] It should also be understood that Figures 8-11 are merely illustrative examples of separating the notification center and control center, using pressure-sensitive buttons to pull down the notification center and control center respectively. In other embodiments, the notification center and control center can be combined. For ease of explanation, the combined form of the notification center and control center is referred to as the notification control center, meaning the notification control center includes both the notification center and the control center. In this case, the user can also pull down the notification control center using pressure-sensitive buttons. For example, the user can pull down the notification control center by performing a first continuous operation or a swipe down operation on the left or right pressure-sensitive buttons. Additionally, when the phone displays the notification control center, the user can also collapse the notification control center by performing a swipe up operation or other touch operations on the left or right pressure-sensitive buttons.

[0178] Scenario 2: Adjust the camera focus by sliding.

[0179] In one embodiment, a user can adjust the camera focus by performing a sliding operation on a pressure-sensitive button.

[0180] As an example, when a camera application interface is displayed on a terminal device, the camera's focal length can be adjusted in response to a sliding operation (sliding up or sliding down) on a pressure-sensitive button. For instance, sliding up on the pressure-sensitive button increases the camera's focal length; sliding down on the pressure-sensitive button decreases the camera's focal length. Exemplarily, the camera application interface can be a shooting interface such as a photo-taking interface or a video-recording interface.

[0181] As an example, when adjusting the camera focus using a sliding motion on a pressure-sensitive button, the focus can be gradually adjusted based on the sliding distance. The adjustment step size can be set according to actual needs. For instance, as the upward sliding distance increases, the camera focus gradually increases; as the downward sliding distance increases, the camera focus gradually decreases.

[0182] 1) Increase the camera's focal length by swiping up on the pressure-sensitive button on the right side of the phone.

[0183] Please refer to Figure 12, which is a schematic diagram of increasing the camera focal length using a pressure-sensitive button according to an embodiment of this application. As shown in Figure 12(a), the phone displays the camera application's shooting interface, with the current focal length being 1x. If the user wants to increase the focal length, they can perform an upward swipe operation on the pressure-sensitive button on the right. In response to the user's upward swipe operation, the focal length captured by the camera application can be increased, as shown in Figure 12(b), where the focal length increases from 1x to 1.1x. If the user wants to continue increasing the focal length, they can continue to swipe upward without releasing the button. In response to the user's continued upward swipe operation, the focal length captured by the camera application can continue to increase, as shown in Figure 12(c), where the focal length increases to 1.2x. At this point, if the user stops swiping upward, the focal length will also stop increasing.

[0184] 2) Reduce the camera focal length by sliding down on the pressure-sensitive button on the right side of the phone.

[0185] Please refer to Figure 13, which is a schematic diagram of reducing the camera focal length using a pressure-sensitive button according to an embodiment of this application. As shown in Figure 13(a), the phone displays the camera application's shooting interface, with the current focal length being 1x. If the user wants to reduce the focal length, they can perform a swipe operation on the pressure-sensitive button on the right. In response to the user's swipe operation, the focal length of the camera application is reduced, as shown in Figure 13(b), where the focal length decreases from 1x to 0.9x. If the user wants to continue reducing the focal length, they can continue to swipe down without releasing the button. In response to the user's continued swipe operation, the focal length of the camera application is further reduced, as shown in Figure 13(c), where the focal length decreases to 0.8x. At this point, if the user stops swiping down, the focal length will also stop decreasing.

[0186] It should be understood that Figures 12 and 13 are only used as examples of adjusting the focal length of the camera application by means of the pressure-sensitive button on the right. In other embodiments, the focal length of the camera application can also be adjusted by means of the pressure-sensitive button on the left or by pressure-sensitive buttons located in other positions. This application does not limit this.

[0187] It should be understood that the focal length of the camera can also be adjusted through other touch operations on the pressure-sensitive button, and this application embodiment does not limit this.

[0188] Scenario 3: Switch audio and video by swiping.

[0189] In one embodiment, a user can switch between audio and video by performing a sliding motion on a pressure-sensitive button.

[0190] As an example, when a terminal device is playing audio or video, such as when an audio or video playback interface is displayed, the user can switch to the previous or next audio or video in response to a sliding operation (slide up or slide down) on the pressure-sensitive button.

[0191] As an example, taking audio and video as short videos, when the terminal device displays the short video application interface, the user switches to the next short video in response to the upward swipe operation on the pressure-sensitive button; the user switches to the previous short video in response to the downward swipe operation on the pressure-sensitive button.

[0192] As an example, when switching short videos based on a swipe operation on a pressure-sensitive button, the short videos can be switched gradually based on the swipe distance. For instance, the short videos can be switched gradually as the swipe distance increases. Exemplarily, gradually switching short videos can include: gradually moving the current short video page off the screen and gradually moving the previous / next short video page onto the screen.

[0193] 1) Swipe up on the pressure-sensitive button on the right side of your phone to switch to the next short video.

[0194] Please refer to Figure 14, which is a schematic diagram of switching to the next short video via a pressure-sensitive button according to an embodiment of this application. As shown in Figure 14(a), the mobile phone displays a short video application interface, which includes the page of the currently playing short video (the current short video). At this time, if the user wants to switch to the next short video, they can perform an upward swipe operation on the pressure-sensitive button on the right. In response to the user's upward swipe operation, the current short video can be switched to the next short video. In one embodiment, the current short video can be switched to the next short video gradually according to the upward swipe distance of the user's upward swipe operation. For example, please refer to Figures 14(b) and 14(c). Following the user's continuous upward swipe operation, the page of the current short video gradually moves out from the top of the display screen, and the page of the next short video gradually moves in from the bottom of the display screen, until the page of the current short video completely moves out and the page of the next short video completely moves in.

[0195] Please refer to Figure 15, which is a schematic diagram of switching to the previous short video via a pressure-sensitive button according to an embodiment of this application. As shown in Figure 15(a), the mobile phone displays a short video application interface, which includes the page of the currently playing short video (current short video). At this time, if the user wants to switch back to the previous short video, they can perform a swipe operation on the pressure-sensitive button on the right. In response to the user's swipe operation, the current short video can be switched to the previous short video. In one embodiment, the current short video can be switched to the previous short video gradually according to the swipe distance of the user's swipe operation. For example, please refer to Figures 15(b) and 15(c). Following the user's continuous swipe operation, the current short video page gradually moves out from the bottom of the display screen, and the previous short video page gradually moves in from the top of the display screen until the current short video page is completely moved out and the previous short video page is completely moved in.

[0196] It should be understood that Figures 14 and 15 are only examples of switching to the next short video by swiping up on the pressure-sensitive button and switching to the previous short video by swiping down. In other embodiments, the previous short video can also be switched by swiping down on the pressure-sensitive button and the next short video by swiping up. This application does not limit this.

[0197] It should also be understood that Figures 14 and 15 are only illustrative examples of switching audio and video using the right-side pressure-sensitive button. In other embodiments, audio and video can also be switched using the left-side pressure-sensitive button or pressure-sensitive buttons located in other positions. This application embodiment does not limit this. In addition, audio and video can also be switched using other touch operations on the pressure-sensitive button. This application embodiment does not limit this either.

[0198] Scenario 4: Zoom in and out of the displayed content by swiping.

[0199] In one embodiment, a user can zoom in or out on displayed content (such as a page or image) by performing a sliding motion on a pressure-sensitive button.

[0200] As an example, when a map application's map interface is displayed on a terminal device, the map interface can be zoomed in or out in response to a swipe operation (swipe up or swipe down) on a pressure-sensitive button. For instance, swiping up on the pressure-sensitive button zooms in on the map interface, while swiping down on the pressure-sensitive button zooms out on the map interface.

[0201] As an example, when scaling the displayed content based on a swipe on a pressure-sensitive button, the scaling can also be gradually adjusted based on the swipe distance. The scaling step can be set according to actual needs. For example, as the swipe distance increases, the displayed content gradually enlarges; as the swipe distance increases, the displayed content gradually shrinks.

[0202] Please refer to Figure 16, which is a schematic diagram of zooming in and out of content using a pressure-sensitive button according to an embodiment of this application. As shown in Figure 16(a), the mobile phone displays the application interface of a map application, which includes a map. If the user wants to zoom in on the map, they can perform an upward swipe operation on the pressure-sensitive button on the right. In response to the user's upward swipe operation, as shown in Figure 16(b), the map is zoomed in. Alternatively, if the user wants to zoom out on the map, they can perform a downward swipe operation on the pressure-sensitive button on the right. In response to the user's downward swipe operation, as shown in Figure 16(c), the map is zoomed out.

[0203] It should be understood that Figure 16 is only used as an example of zooming the displayed content using the pressure-sensitive button on the right. In other embodiments, the displayed content can also be zoomed using pressure-sensitive buttons located in other positions, such as the pressure-sensitive button on the left. This application embodiment does not limit this. In addition, the displayed content can also be zoomed using other touch operations on the pressure-sensitive button, and this application embodiment does not limit this either.

[0204] This application embodiment is only used as an example of controlling the device through sliding operation in the above-mentioned scenarios two, three and four. In other embodiments, the device can also be controlled by other touch operations, such as continuous operation of pressing + sliding, light long press + sliding, etc. on the pressure-sensitive button. This application embodiment does not limit this.

[0205] Furthermore, this application embodiment only uses the above four scenarios of controlling the user interface through touch operation on pressure-sensitive buttons as examples for illustration. It should be understood that controlling the user interface through touch operation on pressure-sensitive buttons can also be applied to other scenarios, and this application embodiment will not provide examples of each of them.

[0206] Before providing a detailed explanation of the operation response method provided in the embodiments of this application, the terminal involved in the embodiments of this application will be described first.

[0207] Figure 17 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Referring to Figure 17, the terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a subscriber identification module (SIM) card interface 195, and pressure-sensitive buttons, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

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

[0209] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0210] The controller can serve as the central nervous system and command center of the terminal device 100. The controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.

[0211] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from this memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

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

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

[0214] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal device 100 can be used to cover one or more 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 some other embodiments, the antennas can be used in conjunction with tuning switches.

[0215] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the terminal device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0216] The wireless communication module 160 can provide solutions for wireless communication applications on the terminal device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0217] Terminal device 100 implements display functions through a GPU, display screen 194, and application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0218] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, terminal device 100 may include one or N displays 194, where N is an integer greater than 1.

[0219] Terminal device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0220] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's image sensor. The light signal is converted into an electrical signal, and the image sensor transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimizations on image noise, brightness, and skin tone. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be integrated into the camera 193.

[0221] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the terminal device 100 may include one or N cameras 193, where N is an integer greater than 1.

[0222] A digital signal processor (DSP) is used to process digital signals. Besides digital image signals, it can also process other digital signals. For example, when terminal device 100 selects a frequency, the DSP performs Fourier transforms on the frequency energy.

[0223] Video codecs are used to compress or decompress digital video. Terminal device 100 may support one or more video codecs. Thus, terminal device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0224] NPU stands for Neural Network (NN) Computing Processor. By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in terminal devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0225] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the terminal device 100. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions, such as saving music, video, and other files on the external storage card.

[0226] Internal memory 121 can be used to store computer-executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of terminal device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created by terminal device 100 during use (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0227] Terminal device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D and application processor.

[0228] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A may be disposed on display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When a force is applied to pressure sensor 180A, the capacitance between the electrodes changes. Terminal device 100 determines the pressure intensity based on the change in capacitance.

[0229] In some embodiments, when a touch operation is applied to the touch surface of a pressure-sensitive button, the terminal device 100 can detect the intensity of the touch operation based on the pressure sensor 180A. The terminal device 100 can also calculate the touch position based on the detection signal from the pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands.

[0230] In some embodiments, when a touch operation is applied to the display screen 194, the terminal device 100 detects the intensity of the touch operation based on the pressure sensor 180A. The terminal device 100 may also calculate the touch position based on the detection signal from the pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different intensities may correspond to different operation commands. For example, when a touch operation with an intensity less than the pressure threshold is applied to the SMS application icon, a command to view an SMS message is executed. When a touch operation with an intensity greater than or equal to the pressure threshold is applied to the SMS application icon, a command to create a new SMS message is executed.

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

[0232] Button 190 includes a power button, volume buttons, etc. Button 190 can be a mechanical button or a touch button, such as the pressure-sensitive button described in the embodiments of this application. Terminal device 100 can receive button input and generate key signal inputs related to user settings and function control of terminal device 100.

[0233] An operating system runs on top of these components. Examples include Apple's iOS, Google's Android, and Microsoft's Windows. Applications can be installed and run on this operating system.

[0234] The software system of terminal device 100 will be described next.

[0235] The software system of terminal device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses a layered Android system as an example to illustrate the software system of terminal device 100.

[0236] Figure 18 is a block diagram of a software system of a terminal device 100 provided in an embodiment of this application. Referring to Figure 18, 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, from top to bottom: the application layer (also called the application layer), the application framework layer (also called the application framework layer), and the kernel layer.

[0237] The application layer can include a series of application packages. As shown in Figure 18, the application package can include system applications (System UI). The System UI is the first application visible to the user during the system startup process of an electronic device, such as the lock screen interface displayed after the electronic device is powered on, and the desktop and status bar displayed after unlocking. The System UI is a set of UI components that provide users with system-level information display and interaction, and can be used to control the display of desktop images. In the embodiments of this application, the System UI can control the display of desktop images to realize the display of focus animation effects in the status bar, the pull-down display of the notification center or control center, and the receipt of notifications from the notification center or control center, etc.

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

[0239] Please refer to Figure 18. The application framework layer may include an input reader (InputReader) 10, an input dispatcher (InputDispatcher) 20, a phone window manager (PhoneWindowManager) 30, a vibrator manager service (VibratorManagerService) 40, a window manager service (WindowManagerService) 50, a surfaceFlinger 60, and a slide manager (SlideManager) 70.

[0240] Input reader 10 is used to read the raw input events (including touch coordinates, touch operation timestamps, etc.) on the pressure-sensitive keys reported by the input device driver in the kernel layer, and convert the read raw input events into standard input events that the input system can recognize and process. Input reader 10 may include event center 11, key input mapping module 12, and swipe touch input mapping module 13, etc.

[0241] The input dispatcher 20 is used to dispatch input events reported by the input reader 10. For example, it can report key events such as tap events to the phone window manager 30, and report swipe events to the application layer's System UI.

[0242] The phone window manager 30 is used to perform gesture detection based on touch events distributed by the input dispatcher 20, such as detecting specific gestures like long press gestures.

[0243] The vibrator management service 40 is used to manage the vibrator, such as triggering the vibrator to vibrate. The vibrator can be the vibrator in the pressure-sensitive button, or it can be other vibrators configured in the terminal device besides the vibrator in the pressure-sensitive button. This application embodiment does not limit this.

[0244] Window Management Service 50 and SurfaceFlinger 60 are used to update data such as the focused application, the focused window, and the window hierarchy.

[0245] The swipe manager 70 is used to maintain swipe management information and can also update the mapping parameters in the swipe touch input mapping module 13 based on the swipe management information. Swipe management information refers to relevant information used for swipe management, which may include one or more of the following: focus application information, focus window information, window hierarchy, swipe response state, swipe strategy, and application scenario.

[0246] Next, for ease of understanding, the above modules in the application framework layer will be explained in blocks.

[0247] First, scene recognition section

[0248] In one embodiment, the pressure-sensitive button can have different functions in different scenarios. The scenario recognition unit can identify different scenarios and then update different sliding strategies according to different scenarios.

[0249] In one embodiment, the scene recognition component may perform scene recognition based on one or more of the following data: focused application, focused window, and window hierarchy.

[0250] Please refer to Figure 19, which is a logical schematic diagram of a scene recognition part provided in an embodiment of this application. As shown in Figure 19, the scene recognition part includes some modules of window management service 50, SurfaceFlinger 60, sliding manager 70, and input distributor 20.

[0251] When an application switches interfaces or changes a window, the window management service 50 will synchronize the window data and application data to SurfaceFlinger 60. SurfaceFlinger 60 can then update the input dispatcher 20 with data such as the focus application information, focus window information, and window hierarchy based on the data synchronized by the window management service 50.

[0252] As an example, the input distributor 20 can obtain the aforementioned focus application information, focus window information, window hierarchy, and other scene information through the relevant interfaces of SurfaceFlinger 60. Additionally, the input distributor 20 can synchronize data such as focus application, focus window, and window hierarchy to the sliding manager 70.

[0253] The swipe manager 70 is used to maintain swipe management information and can also update the mapping parameters in the swipe touch input mapping module 13 based on the swipe management information. The swipe manager 70 can be a newly added module in the system services.

[0254] In one embodiment, the sliding management information may include one or more of the following: focus application information, focus window information, window hierarchy, sliding response state, sliding strategy, and scene information.

[0255] Next, we will explain each of these pieces of information.

[0256] The slide response state indicates whether to listen for and process slide events on the pressure-sensitive button. For example, the slide response state can include an on state and an off state. When the slide response state is on, the terminal device can listen for and process slide events on the pressure-sensitive button; when the slide response state is off, the terminal device does not listen for and process slide events on the pressure-sensitive button.

[0257] In one embodiment, the swipe manager can update the swipe response status to "on" when the device status meets preset conditions. These preset conditions include receiving a third notification, the focused window being a notification center window or a control center window, etc. Conversely, the phone window manager can update the swipe response status to "off" when the device status does not meet the preset conditions, thereby reducing the probability of accidental touches by the user.

[0258] Scenes are used to indicate the current usage scenario of the device. For example, scenes can include pull-down notification scenarios (such as desktop scenarios), audio and video playback scenarios (such as short video scenarios like TikTok), camera scenarios, map scenarios, gallery scenarios, etc. Different swiping strategies can be used to manipulate the user interface for different scenarios.

[0259] A swipe strategy indicates the conditions that must be met for a swipe operation to control the user interface; that is, what kind of swipe operation should be used to control the user interface. For example, a swipe strategy may include one or more of the following: swipe direction, swipe finger requirements (e.g., single finger or two fingers), pressure-sensitive button identifiers (e.g., left or right pressure-sensitive button), and swipe distance requirements. For instance, for a control scheme that uses a swipe down on the left pressure-sensitive button to pull down the notification center, the swipe strategy may include: swipe down, single-finger operation, and left pressure-sensitive button identifiers.

[0260] Mapping parameters refer to the parameters used to map swipe events on pressure-sensitive buttons to swipe events on the screen. For example, they may include at least one of the following parameters: starting point, swipe finger requirements (whether it's a single finger or multiple fingers, etc.), swipe direction, swipe gesture, and swipe distance mapping ratio. These mapping parameters will affect the creation of subsequent swipe events and the response to them.

[0261] As an example, different mapping parameters can be updated in different scenarios to simulate different swipe events on the pressure-sensitive button as different swipe events on the screen. For instance, in scenarios like the desktop where notifications are pulled down, the swipe event on the pressure-sensitive button is converted into a swipe event that starts from near the top of the screen and slides downwards to simulate the notification pull-down operation; in short video scenarios like TikTok, the swipe event on the pressure-sensitive button is converted into a swipe event that slides from the middle of the screen to simulate page turning; in camera scenarios, the swipe event on the pressure-sensitive button is converted into a swipe event where two fingers are spread or pinched on the screen to simulate focusing; and in scenarios like the gallery and map, the swipe event on the pressure-sensitive button is converted into a swipe event where two fingers are spread or pinched on the screen to simulate zooming and other operations.

[0262] Second, the key event handling section.

[0263] The key event handling section generates standard key events that the input system can recognize and process, based on the raw key events reported by the pressure-sensitive device driver. This part of the logic, along with the pressure-sensitive device driver, mainly listens for the user's light touch operations on the pressure-sensitive buttons, encapsulating the down and up operations into down and up type key events.

[0264] Please refer to Figure 20, which is a logical schematic diagram of a key event processing section provided in an embodiment of this application. As shown in Figure 20, the key event processing section includes an event center 11 and a key input mapping 12 in the input reader 10.

[0265] Event Center 11 is used to receive raw input events reported by the pressure-sensitive device driver in the kernel layer, and report the raw input events to different processing modules according to the event type of the raw input events. The event types can include key events and sliding events, etc.

[0266] In one embodiment, the event center 11 is used to receive raw input events reported by the pressure-sensitive device driver in the kernel layer. If the raw input event is a key event, the raw key event is reported to the key input mapping module 12 for processing. If the raw input event is a swipe event, the swipe data of the raw swipe event is reported to the swipe touch input mapping module 13 for processing.

[0267] The key input mapping module 12 is used to process the raw key events on the pressure-sensitive keys, such as processing the raw key events to generate standard key events.

[0268] In one embodiment, a key event can include both a down event and an up event. Taking a key event where the original key event is a light touch (press) operation as an example, for the original down event of a pressure-sensitive key, the key input mapping module 12 can process the original down event to generate a standard light touch down event. For the original up event of a pressure-sensitive key, the key input mapping module can process the original up event to generate a standard light touch up event. After generating the standard light touch event, the key input mapping module 12 can also report the light touch event to the input distributor 20.

[0269] Third, the gesture recognition part.

[0270] The gesture recognition section is mainly used to recognize gestures based on button events, such as recognizing specific gestures like long presses. A long press refers to a light press that lasts for a certain duration.

[0271] Please refer to Figure 21, which is a logical schematic diagram of a gesture recognition part provided in an embodiment of this application. As shown in Figure 21, this part includes an input distributor 20 and a telephone window manager 30.

[0272] Input distributor 20 can distribute key events, such as tap events, reported by the input reader. For example, key events can be reported to the phone window manager 30. The phone window manager 30 is used to perform gesture detection based on key events, such as tap events, reported by the input distributor 20, including specific gestures like long press gestures.

[0273] In one embodiment, the phone window manager 30 may include an event acquisition interface and a long-press gesture detection module. The event acquisition interface is used to acquire touch events reported by the event dispatcher, and the event acquisition interface may be a queue pre-interception interface, etc. The long-press gesture detection module is used to detect long-press gestures based on touch events.

[0274] As an example, gesture detection can be implemented through relevant interfaces, such as those provided by SingleKeyGestureDetector. For instance, the key values ​​of the left and right pressure-sensitive buttons can be defined as VOLUME_TICKL and POWER_TICKLE respectively, and the SlideVoluemKeyRule and SlidePowerKeyRule can be defined using the interfaces provided by SingleKeyGestureDetector, which are then used in the interface methods of SingleKeyGestureDetector.SingleKeyRule.

[0275] As an example, taking a long press gesture as a light press operation gesture with a duration of 300ms, the processing modules and related operations involved in the gesture recognition process after the user presses the pressure-sensitive button can be shown in Figure 22.

[0276] Fourth, the multi-step operation after the gesture is completed.

[0277] Please refer to Figure 23, which is a logical schematic diagram of a multi-step operation part after a gesture is completed according to an embodiment of this application. As shown in Figure 23, this part may include a phone window manager 30, a vibrator management service 40, and a swipe manager 70.

[0278] 1) When a specific gesture is detected, the Telephone Window Manager 30 can send a notification to the System UI indicating that a specific gesture has been detected, so that the System UI can respond to the specific gesture based on the notification.

[0279] For example, when the System UI receives a notification that a long press gesture has been detected, it can display a focus animation at the top (such as the top status bar). For instance, for a long press gesture on the left pressure-sensitive button, a focus animation can be displayed on the top left; for a long press gesture on the right pressure-sensitive button, a focus animation can be displayed on the top right.

[0280] 2) When the telephone window manager 30 detects a specific gesture, it can send a notification instructing the vibrator to vibrate to the vibrator management service 40, so that the vibration management service can trigger the vibrator to vibrate according to the notification. For example, the vibration management service can trigger the vibrator to vibrate slightly according to the notification.

[0281] As an example, the phone window manager 30 can notify the vibrator to vibrate through the relevant interface of the vibration service.

[0282] 3) When the phone window manager 30 detects a specific gesture, it can send a notification to the swipe manager 70 indicating that the tap is complete, so that the swipe manager 70 can update swipe management information such as swipe response status, swipe strategy, and scene based on the notification. For example, the swipe manager 70 can switch the swipe response status to the on state based on the notification.

[0283] As an example, input distributor 20 can also send a touch start notification to slide manager 70 after receiving a touch press event reported by input reader 10. Phone window manager 30 can also send a notification indicating touch completion to slide manager 70 upon receiving a touch release event. When slide response is in the off state, slide manager 70 can switch slide response to the on state when the touch duration is determined to have reached a certain duration (e.g., 300ms) based on the touch start and touch completion notifications.

[0284] Fourth, the mapping parameter update and sliding event handling section.

[0285] Figure 24 is a logical schematic diagram of a mapping parameter update and sliding event processing part provided in an embodiment of this application. Referring to Figure 24, this part includes a sliding touch input mapping module 13, which is used to process the sliding data of the original sliding event. For example, it can process the sliding data of the original sliding event to generate a standard sliding event that the input system can recognize and process.

[0286] The sliding window management 70 can update the mapping parameters in the sliding touch input mapping module 13 according to relevant sliding management information, such as updating them to mapping parameters corresponding to the desktop scene.

[0287] The mapping parameters refer to the parameters used to map the sliding events on the pressure-sensitive buttons to the sliding events on the screen. For example, they may include the starting point, and may also include at least one of the following parameters: sliding finger requirements (whether it is a single finger or multiple fingers, etc.), sliding direction, sliding gesture, and sliding distance mapping ratio, etc.

[0288] As an example, for the mapping parameters updated after a long press gesture on a pressure-sensitive button, the starting point in these parameters can indicate the starting point of a swipe on the screen. This starting point can include the starting point for an upward swipe and the starting point for a downward swipe.

[0289] The starting point for the upward swipe can be located at the top of the screen or at a preset distance from the top, so that the downward swipe operation of the pressure-sensitive button is mapped to a swipe operation starting from near the top of the screen. Additionally, for the left-side pressure-sensitive button, the starting point for the upward swipe can also be located on the left side of the screen, so that the downward swipe operation of the pressure-sensitive button is mapped to a swipe operation starting from the top left side of the screen. For example, this starting point could be located at 1 / 3 of the screen width (i.e., the distance from the left side of the screen is 1 / 3 of the distance from the right side of the screen), or at 1 / 4 of the screen width (i.e., the distance from the left side of the screen is 1 / 3 of the distance from the right side of the screen). As an example, the screen coordinates of this starting point in the screen coordinate system include X-axis coordinates and Y-axis coordinates, with the X-axis at 1 / 3 of the screen width and the Y-axis at 20. The screen coordinate system is a coordinate system with the top-left corner of the screen as the origin, the width direction of the screen as the X-axis, and the height direction of the screen as the Y-axis.

[0290] The starting point for a swipe down can be a relatively low position on the screen, such as the bottom half or the center line of the top and bottom sections, so that a swipe down operation on the pressure-sensitive button is mapped to a swipe up operation starting from a relatively low position on the screen. Additionally, for the left-side pressure-sensitive button, the starting point for the swipe down can also be located on the left side of the screen, so that a swipe up operation on the pressure-sensitive button is mapped to a swipe up operation on the left side of the screen. For example, this starting point could be located at 1 / 3 of the screen width (i.e., the distance from the left side of the screen is 1 / 3 of the distance from the right side), or at 1 / 4 of the screen width (i.e., the distance from the left side of the screen is 1 / 3 of the distance from the right side). As an example, the screen coordinates of this starting point in the screen coordinate system include X-axis coordinates and Y-axis coordinates, with the X-axis coordinate at 1 / 3 of the screen width and the Y-axis coordinate at the center line of the top and bottom sections of the screen.

[0291] In one embodiment, the sliding touch input mapping module 13 can map the original sliding event on the pressure-sensitive button to a sliding event on the screen (hereinafter referred to as screen sliding event), and report the generated screen sliding event to the input distributor 20, so that the input distributor 20 can report the screen sliding event to the System UI.

[0292] For example, the swipe touch input mapping module 13 can maintain mapping parameters and a screen matrix. The screen matrix can include screen information such as screen orientation and width / height. For the raw swipe event reported by the event center 11, the swipe touch input mapping module 13 can preprocess the swipe data of the raw swipe event, and then calculate the swipe event parameters based on the stored mapping parameters, the screen matrix, and the preprocessed swipe data. Based on the calculated swipe event parameters, the swipe event of the screen is generated.

[0293] In addition, the swipe touch input mapping module 13 can also report the generated swipe events to the System UI, so that the System UI can pull down the notification center or control center based on the swipe event. For example, the notification center can be pulled down based on the swipe event of the left pressure-sensitive button, and the control center can be pulled down based on the swipe event of the right pressure-sensitive button.

[0294] The kernel layer is the layer between hardware and software. The kernel layer contains at least a pressure-sensitive device driver, and may also include display drivers, sensor drivers, camera drivers, and audio drivers. The pressure-sensitive device driver is used to report the raw touch events generated by the user's touch operations on the pressure-sensitive buttons, such as reporting raw key events (or key data) and raw swipe events (or swipe data).

[0295] Here, "slide data" refers to the data generated by sliding operations on the pressure-sensitive button, which may include the offset value of the pressure-sensitive button. Subsequent slide events can be generated based on the offset value of the pressure-sensitive button. For example, the offset value of the pressure-sensitive button can be between 0 and 200.

[0296] The hardware layer includes at least one pressure-sensitive button, which can be one or more. Users can perform touch operations such as pressing or swiping on the pressure-sensitive buttons. The hardware layer may also include a display screen, etc., but this application embodiment does not limit this.

[0297] It should be noted that the layers in the software structure shown in Figure 18, and the components contained in each layer, do not constitute a specific limitation on the terminal device. In other embodiments, the terminal device may include more layers than shown in the figure, such as system libraries and hardware abstraction layer (HAL) layers. Furthermore, each layer may include more or fewer components than shown in the figure; this application does not impose any limitations.

[0298] It should be understood that the embodiment in Figure 18 is only used as an example to illustrate how the System UI receives and responds to swipe events reported by the swipe touch input driver and the input dispatcher. In other embodiments, the System UI may also directly listen to the raw swipe events or swipe data reported by the pressure-sensitive device driver, convert the raw swipe events or swipe data into swipe events on the screen, and respond to the swipe events.

[0299] It is understood that, in order to implement the operation response method in the embodiments of this application, the terminal device includes hardware and / or software modules that perform various functions. Based on the algorithm steps of the examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments.

[0300] It should be noted that although the embodiments of this application are illustrated using the Android system as an example, the basic principles are equally applicable to terminal devices based on operating systems such as iOS or Windows.

[0301] The following example illustrates the workflow of the software and hardware of terminal device 100 by showing a user performing a light press and swipe down operation on a pressure-sensitive button in a desktop scenario.

[0302] When a pressure-sensitive button receives a touch operation, the corresponding hardware interrupt is sent to the pressure-sensitive device driver in the kernel layer. The pressure-sensitive device driver processes the touch operation into a raw input event (including touch coordinates, touch operation timestamp, etc.). The raw input event is stored in the kernel layer. The application framework layer obtains the raw input event from the kernel layer; for example, the event center in the input reader included in the application framework layer can obtain the raw input event. If the touch operation is a tap (light press), the event center reports the raw input event to the key input mapping module, which processes the raw input event, generates a tap press event, and reports it to the input dispatcher for distribution. The input dispatcher can distribute the tap press event when the focused application is a specific application such as a desktop application. The phone window manager can obtain the tap press event distributed by the input dispatcher through relevant interfaces (queue pre-interception interface, etc.) and perform long press gesture detection on the tap press event. If a user presses and releases a pressure-sensitive button for a certain duration (e.g., 300ms), the Phone Window Manager can determine that a press gesture was detected if no release event is detected within that duration (e.g., 300ms). Upon detecting the press gesture, the Manager sends a press gesture notification to the System UI, which then displays a focus animation in the status bar based on this notification. For example, if the pressure-sensitive button is on the left side, the System UI can display a focus animation on the left side of the status bar to indicate that the user can pull down the notification center using the pressure-sensitive button.

[0303] The input dispatcher can also synchronize information such as the focused application to the swipe manager. The swipe manager can identify the current application scenario as a desktop scenario based on the focused application and update the corresponding swipe strategy (such as a single-finger swipe down strategy) accordingly. After recognizing a long press gesture or receiving a tap-to-release event, the phone window manager sends a tap-to-complete notification to the swipe manager. Upon receiving this notification, the swipe manager updates its swipe response state to the enabled state. Additionally, the swipe manager can update mapping parameters based on swipe management information such as swipe strategies. Then, when the pressure-sensitive button receives a swipe-up operation, the corresponding hardware interrupt is sent to the pressure-sensitive device driver in the kernel layer. The pressure-sensitive device driver reports the swipe data of the swipe-up operation to the event center, which then reports the swipe data to the swipe touch input mapping module. The swipe touch input mapping module can preprocess the swipe data, and then, based on the mapping parameters and the screen matrix, process the preprocessed swipe data to generate event parameters, and generate a swipe event on the screen based on these event parameters. The swipe event on the screen is then reported to the input dispatcher, which in turn reports it to the System UI. The System UI then pulls down to display the notification center based on the swipe event.

[0304] The execution subject of the operation response method provided in this application embodiment can be the aforementioned terminal device, or it can be a functional module and / or functional entity in the terminal device that can implement the video processing method. Furthermore, the solution of this application can be implemented through hardware and / or software, and the specific implementation can be determined according to actual usage requirements; this application embodiment does not impose any limitations. The following description uses a terminal device as an example, combined with the accompanying drawings, to exemplarily illustrate the video processing method provided in this application embodiment.

[0305] Next, referring to Figure 18 above, we will provide an illustrative explanation of the process of pulling down the notification center via the pressure-sensitive button.

[0306] Figure 25 is a schematic diagram illustrating a process of pulling down to display a notification center based on a touch operation on a pressure-sensitive button, according to an embodiment of this application. As an example, the diagram describes a terminal device including a pressure-sensitive button on the left side, where the user pulls down the notification center by performing a long press and swipe down operation on the left pressure-sensitive button in a desktop scenario.

[0307] Step 2501: With the desktop displayed on the terminal device, the user lightly presses the pressure-sensitive button on the left side of the terminal device.

[0308] It should be understood that the embodiments of this application are only illustrated using a desktop scenario as an example. In other embodiments, the terminal device may also pull down or collapse the notification center according to the touch operation on the pressure-sensitive button when displaying other specific interfaces. The embodiments of this application do not limit this.

[0309] Step 2502: The pressure-sensitive device driver sends the original light touch press event 1 of the left pressure-sensitive button to the event center of the input reader.

[0310] After the pressure-sensitive button on the left receives a light press operation, the corresponding hardware interrupt is sent to the pressure-sensitive device driver in the kernel layer. The pressure-sensitive device driver can process the light press operation into a raw light touch press event 1, and then send the raw light touch press event 1 to the event center of the input reader.

[0311] In one embodiment, for a touch operation on a pressure-sensitive button, the pressure-sensitive device driver can process it into a corresponding raw touch event. This raw touch event may include the identifier of the pressure-sensitive button to indicate that the raw touch event is a raw touch event on that pressure-sensitive button. For example, the identifier of the pressure-sensitive button may be the key code corresponding to that pressure-sensitive button. Additionally, the raw touch event may also include touch coordinates, operation timestamps, etc., but this embodiment does not limit this information.

[0312] As an example, for the original tap press event 1 of the left pressure-sensitive button, the original tap press event 1 can include the identifier of the left pressure-sensitive button to indicate that the original tap press event 1 is an original tap press event on the left pressure-sensitive button. For example, the identifier of the left pressure-sensitive button can be the key value corresponding to the left pressure-sensitive button. For example, for easy identification, the key values ​​of the left pressure-sensitive button and the right pressure-sensitive button can be VOLUME_TICKL and POWER_TICKLE, respectively.

[0313] In one embodiment, for a press operation on a pressure-sensitive button, the pressure-sensitive device driver can first determine the type of the press operation based on the pressing force, and then process the press operation into different types of raw press events. For example, the type of press operation may include tap, light press, hard press, etc., and this application embodiment does not limit this.

[0314] In one embodiment, the pressure-sensitive device driver may report the original tap press event 1 to the event hub. Alternatively, the pressure-sensitive device driver may store the original tap press event 1, which can then be read from the pressure-sensitive device driver by the event hub.

[0315] Step 2503: The event center of the input reader sends a raw tap press event 1 to the key input mapping module.

[0316] After receiving the original tap press event 1, the event center can send the original tap press event 1 to the key input mapping module for processing.

[0317] The key input mapping module is used to handle raw touch events such as raw press events and raw release events. For any raw touch event, the event center can send it to the key input mapping module for processing.

[0318] Step 2504: The key input mapping module processes the original light touch press event 1 and generates light touch press event 1.

[0319] Among them, tap-press event 1 is a standard tap-press event that the input system can recognize and process. The key input mapping module can process the raw tap-press event to convert it into a standard tap-press event.

[0320] In one embodiment, the key input mapping module can also process other raw touch events, such as raw tap-to-release events, to convert them into corresponding standard touch events. For example, if a raw tap-to-release event is received from the event center, it can also process the raw tap-to-release event to generate a tap-to-release event.

[0321] Step 2505: The key input mapping module sends a light touch press event 1 to the input distributor.

[0322] Step 2506: Input distributor synchronizes focus application information and focus window information to the sliding manager.

[0323] The input dispatcher can obtain information such as focused application information, focused window information, and window hierarchy, and synchronize this information to the sliding manager.

[0324] In one embodiment, the input distributor can synchronize the changed information to the sliding manager whenever any of the above information changes.

[0325] In one embodiment, the input distributor can obtain the above information through the relevant interfaces of SurfaceFlinger.

[0326] Step 2507: The input distributor sends touch-down event 1 to the phone window manager.

[0327] In one embodiment, the input dispatcher can dispatch the tap-down event 1. The phone window manager can retrieve the tap-down event 1 dispatched by the input dispatcher through the event retrieval interface. The event retrieval interface is used to retrieve tap events reported by the event dispatcher and can be an interceptKeyBeforeQueueing interface, etc.

[0328] In one embodiment, the input dispatcher may dispatch the tap press event 1 if it determines, based on the focus application information, that the current focus application is a specific application such as a desktop application. If it determines that the current focus application is not a specific application, then no dispatch is made.

[0329] Step 2508: The phone window manager performs a long press gesture detection based on the tap press event 1.

[0330] Among them, a long press gesture refers to a light press gesture whose duration is greater than or equal to a first duration threshold.

[0331] The phone window manager can determine the duration of the tap corresponding to tap press event 1. If the tap duration reaches a first duration threshold (e.g., 300ms), a long press gesture is detected. If the tap duration does not reach the first duration threshold, a long press gesture is not detected.

[0332] In one embodiment, the phone window manager can determine whether a touch-up event corresponding to the touch-down event 1 has been received within a first duration threshold after the touch-down event 1 is received. If the touch-up event is received, it means that the touch duration has not reached the first duration threshold, and it can be determined that no long-press gesture has been detected. If the touch-up event is not received, it means that the touch duration has reached the first duration threshold, and it can be determined that a long-press gesture has been detected.

[0333] Step 2509: After detecting a long press gesture, the phone window manager sends notification 1 to the vibration management server.

[0334] Notification 1 is used to indicate that a long press gesture has been detected.

[0335] Additionally, Notification 1 can instruct the vibration management server to trigger vibration.

[0336] Step 2510: The vibration management server triggers the vibrator to vibrate according to notification 1.

[0337] In one embodiment, the vibration management server triggers the vibrator to perform different vibration modes under different circumstances. For example, it can trigger the vibrator to perform different vibration modes based on different notifications.

[0338] Step 2511: After detecting a long press gesture, the phone window manager sends a notification 2 to the System UI.

[0339] Notification 2 is used to indicate that a long press gesture has been detected.

[0340] Additionally, Notification 2 can indicate that a long press gesture has been detected on the left pressure-sensitive button, so that the System UI can respond differently depending on the long press gesture on different pressure-sensitive buttons.

[0341] Step 2512: In response to notification 2, the System UI displays a focus animation in the left area of ​​the status bar.

[0342] By displaying a focus animation in the left area of ​​the status bar, users can be instructed to pull down the notification center via a pressure-sensitive button.

[0343] Step 2513: After detecting a long press gesture, the phone window manager sends a notification 3 to the swipe manager.

[0344] Notification 3 can indicate that the tap duration has reached a first duration threshold, or indicate that the tap is complete.

[0345] In one embodiment, when the duration of the tap reaches a first duration threshold, the phone window manager may send notification 3 to the swipe manager upon receiving the first duration threshold after the tap press event 1, or it may send notification 3 to the swipe manager after receiving the tap release event corresponding to the tap press event 1. This embodiment of the application does not limit this.

[0346] Step 2514: The swipe manager updates the swipe response state and calculates the mapping parameters based on notification 3.

[0347] The sliding response status is used to indicate whether the terminal device listens to and processes the sliding operation on the pressure-sensitive button. For example, it can indicate whether the sliding touch input mapping module processes the original sliding event or sliding data.

[0348] The swipe manager maintains a swipe response state. Upon receiving notification 3, the swipe response state can be switched to the on state. For example, before receiving notification 3, the swipe response state maintained by the swipe manager might be off. Upon receiving notification 3, the swipe response state can be switched from off to on to respond to subsequent swipe operations.

[0349] In one embodiment, the swipe manager can update the swipe response state to "on" when the device status meets preset conditions. These preset conditions include receiving notification 3, the focused window being a notification center window or control center window, etc. Conversely, the phone window manager can update the swipe response state to "off" when the device status does not meet the preset conditions, thereby reducing the probability of accidental touches by the user.

[0350] The mapping parameters are parameters used to map swipe events on pressure-sensitive buttons to swipe events on the screen. These may include a starting point, and at least one of the following parameters: swipe finger requirements (whether it's a single finger or multiple fingers), swipe direction, swipe gesture, and swipe distance mapping ratio.

[0351] In one embodiment, for the mapping parameters corresponding to the desktop scene, the starting point in the mapping parameters is mapped to a sliding starting point on the screen. This starting point can include an upward sliding starting point and a downward sliding starting point. The upward sliding starting point can be located at the top of the screen or at a preset distance from the top of the screen, so that the downward sliding operation of the pressure-sensitive button is mapped to a sliding operation starting from near the top of the screen. Additionally, for the left-side pressure-sensitive button, the upward sliding starting point can also be located on the left side of the screen, so that the downward sliding operation of the pressure-sensitive button is mapped to a sliding operation starting from the top left side of the screen. The downward sliding starting point can be a relatively low position on the screen, such as the lower half of the screen or the center line of the upper and lower parts, so that the downward sliding operation of the pressure-sensitive button is mapped to an upward sliding operation starting from a relatively low position on the screen. Additionally, for the left-side pressure-sensitive button, the downward sliding starting point can also be located on the left side of the screen, so that the upward sliding operation of the pressure-sensitive button is mapped to an upward sliding operation on the left side of the screen.

[0352] Step 2515: The telephone window manager sends an update command to the swipe touch input mapping module of the input reader. The update command includes the updated swipe response state and the mapping parameters.

[0353] Step 2516: The swipe touch input mapping module updates the swipe response state and mapping parameters according to the update instruction.

[0354] It should be understood that the embodiments of this application are only used as examples to illustrate the updating of the sliding response state and mapping parameters of the sliding touch input mapping module. In other embodiments, only the mapping parameters may be updated without updating the sliding response state. The embodiments of this application do not limit this.

[0355] Step 2517: The user performs a downward sliding operation on the pressure-sensitive button on the left.

[0356] Step 2518: The pressure-sensitive device driver sends the raw swipe event 1 on the left pressure-sensitive button to the event center of the input reader.

[0357] In one embodiment, the pressure-sensitive device driver can also send the sliding data of the original swipe event 1 on the left pressure-sensitive button to the event center.

[0358] Step 2519: The event center of the input reader sends the sliding data of the original swipe event 1 to the swipe touch input mapping module.

[0359] Step 2520: The swipe touch input mapping module generates event parameter 1 based on the screen matrix, the updated mapping parameters, and the swipe data.

[0360] The screen matrix indicates the screen orientation and screen dimensions. Screen orientation can include landscape and portrait orientations. Screen dimensions indicate the screen's pixel size.

[0361] The swipe touch input mapping module can process the swipe data according to the screen matrix and the updated mapping parameters, so as to map the swipe data into event parameter 1 of the swipe-down event on the screen.

[0362] Event parameter 1 can include the starting point of the swipe on the screen. This starting point can be the top of the screen or a position at a preset distance from the top, so that the downward swipe operation of the pressure-sensitive button is mapped to a swipe operation starting from near the top of the screen. Additionally, for the downward swipe operation of the left-side pressure-sensitive button, the starting point can also be located on the left side of the screen, so that the downward swipe operation of the pressure-sensitive button is mapped to a swipe operation starting from the top of the left side of the screen. For example, the starting point can be located at 1 / 3 of the screen width (i.e., the distance from the left side of the screen is 1 / 3 of the distance from the right side of the screen), or at 1 / 4 of the screen width (i.e., the distance from the left side of the screen is 1 / 3 of the distance from the right side of the screen).

[0363] As an example, the screen coordinates of this starting point in the screen coordinate system include X-axis and Y-axis coordinates. The X-axis coordinate is located at 1 / 3 of the screen width, and the Y-axis coordinate is 20. The screen coordinate system is a coordinate system with the top-left corner of the screen as the origin, the width direction of the screen as the X-axis, and the height direction of the screen as the Y-axis.

[0364] In one embodiment, before generating event parameter 1 based on the screen matrix, the updated mapping parameters, and the sliding data, the sliding touch input mapping module may first preprocess the sliding data, and then generate event parameter 1 based on the screen matrix, the updated mapping parameters, and the preprocessed sliding data.

[0365] As an example, preprocessing could include validating the swipe data to check its correctness and whether it's a false touch. If the validation passes, the operation of generating event parameters based on the screen matrix, updated mapping parameters, and the swipe data is then performed. If the validation fails, no further operations are executed.

[0366] Step 2521: The swipe touch input mapping module generates a swipe-down event 1 on the screen based on event parameter 1.

[0367] The swipe touch input mapping module can encapsulate this event parameter as a swipe-down event on the screen.

[0368] Step 2522: The swipe touch input mapping module sends a swipe event 1 to the input distributor.

[0369] Step 2523: The input dispatcher sends the down event 1 to the System UI.

[0370] Step 2524: The System UI responds to swipe down event 1 and pulls down to display the notification center.

[0371] Step 2525: The user performs an upward swipe operation on the pressure-sensitive button on the left.

[0372] Step 2526: The pressure-sensitive device driver sends the original swipe-up event 1 on the left pressure-sensitive button to the event center of the input reader.

[0373] In one embodiment, the pressure-sensitive device driver can also send the sliding data of the original swipe-up event 1 on the left pressure-sensitive button to the event center.

[0374] Step 2527: The event center of the input reader sends the sliding data of the original swipe-up event 1 to the swipe touch input mapping module.

[0375] Step 2528: The swipe touch input mapping module generates event parameter 2 based on the screen matrix, the updated mapping parameters, and the swipe data.

[0376] The swipe touch input mapping module can process the swipe data according to the screen matrix and the updated mapping parameters, so as to map the swipe data into event parameter 2 of the swipe-up event on the screen.

[0377] Event parameter 2 can include a starting point for the swipe on the screen. This starting point can be a relatively low position on the screen, such as the lower half of the screen or the center line of the top and bottom sections, so that a downward swipe operation of the pressure-sensitive button is mapped to an upward swipe operation starting from a relatively low position on the screen. Additionally, for an upward swipe operation of the left-side pressure-sensitive button, this starting point can also be located on the left side of the screen, so that an upward swipe operation of the pressure-sensitive button is mapped to an upward swipe operation on the left side of the screen. For example, this starting point could be located at 1 / 3 of the screen width (i.e., the distance from the left side of the screen is 1 / 3 of the distance from the right side of the screen), or at 1 / 4 of the screen width (i.e., the distance from the left side of the screen is 1 / 3 of the distance from the right side of the screen).

[0378] As an example, the screen coordinates of this starting point in the screen coordinate system include X-axis and Y-axis coordinates. The X-axis coordinate is located at 1 / 3 of the screen width, and the Y-axis coordinate is located at the center line of the top and bottom parts of the screen. The screen coordinate system is a coordinate system with the top-left corner of the screen as the origin, the width direction of the screen as the X-axis, and the height direction of the screen as the Y-axis.

[0379] In one embodiment, before generating event parameters based on the screen matrix, the updated mapping parameters, and the swipe data, the swipe touch input mapping module may preprocess the swipe data and then generate event parameters based on the screen matrix, the updated mapping parameters, and the preprocessed swipe data.

[0380] As an example, preprocessing could include validating the swipe data to check its correctness and whether it's a false touch. If the validation passes, the operation of generating event parameters based on the screen matrix, updated mapping parameters, and the swipe data is then performed. If the validation fails, no further operations are executed.

[0381] Step 2529: The swipe touch input mapping module generates an upward swipe event 1 on the screen based on event parameter 2.

[0382] Step 2530: The swipe touch input mapping module sends an up swipe event 1 to the input distributor.

[0383] Step 2531: The input dispatcher sends the swipe-up event 1 to the System UI.

[0384] Step 2532: The System UI responds to swipe-up event 1 and collapses the notification center.

[0385] In response to swipe-up event 1, the System UI can either directly cancel the display of the notification center or gradually move the notification center towards the top of the screen to achieve a gradually collapsing effect. This application embodiment does not limit this.

[0386] Figure 26 is a schematic diagram illustrating a process of pulling down to display a control center based on a touch operation on a pressure-sensitive button, according to an embodiment of this application. As an example, the diagram describes a terminal device including a pressure-sensitive button on the right side, where the user pulls down the control center by performing a light press and swipe down operation on the right pressure-sensitive button in a desktop scenario.

[0387] Step 2601: With the desktop displayed on the terminal device, the user lightly presses the pressure-sensitive button on the right side of the terminal device.

[0388] It should be understood that the embodiments of this application are only illustrated using a desktop scenario as an example. In other embodiments, the terminal device may also pull down or collapse the control center according to the touch operation on the pressure-sensitive button when displaying other interfaces. The embodiments of this application do not limit this.

[0389] Step 2602: The pressure-sensitive device driver sends the original light touch press event 2 of the right pressure-sensitive button to the event center of the input reader.

[0390] After the pressure-sensitive button on the right receives a light press operation, the corresponding hardware interrupt is sent to the pressure-sensitive device driver in the kernel layer. The pressure-sensitive device driver can process the light press operation into a raw light touch press event 2, and then send the raw light touch press event 2 to the event center of the input reader.

[0391] In one embodiment, for a touch operation on a pressure-sensitive button, the pressure-sensitive device driver can process it into a corresponding raw touch event. This raw touch event may include the identifier of the pressure-sensitive button to indicate that the raw touch event is a raw touch event on that pressure-sensitive button. For example, the identifier of the pressure-sensitive button may be the key code corresponding to that pressure-sensitive button. Additionally, the raw touch event may also include touch coordinates, operation timestamps, etc., but this embodiment does not limit this information.

[0392] As an example, for the original tap press event 2 of the right pressure-sensitive button, the original tap press event 2 can include the identifier of the right pressure-sensitive button to indicate that the original tap event 2 is an original tap press event on the right pressure-sensitive button. For example, the identifier of the right pressure-sensitive button can be the key value corresponding to the right pressure-sensitive button. For example, for easy identification, the key values ​​of the left and right pressure-sensitive buttons can be VOLUME_TICKL and POWER_TICKLE, respectively.

[0393] In one embodiment, for a press operation on a pressure-sensitive button, the pressure-sensitive device driver can first determine the type of the press operation based on the pressing force, and then process the press operation into different types of raw press events. For example, the type of press operation may include tap, light press, hard press, etc., and this application embodiment does not limit this.

[0394] In one embodiment, the pressure-sensitive device driver may report the original tap press event 2 to the event hub. Alternatively, the pressure-sensitive device driver may store the original tap press event 2, which can then be read from the pressure-sensitive device driver by the event hub.

[0395] Step 2603: The event center of the input reader sends the raw touch press event 2 to the key input mapping module.

[0396] After receiving the original tap press event 2, the event center can send the original tap press event 2 to the key input mapping module for processing.

[0397] The key input mapping module is used to handle raw touch events such as raw press events and raw release events. For any raw touch event, the event center can send it to the key input mapping module for processing.

[0398] Step 2604: The key input mapping module processes the original light touch press event 2 and generates light touch press event 2.

[0399] Among them, touch press event 2 is a standard touch press event that the input system can recognize and process. The key input mapping module can process the raw touch press event to convert it into a standard touch press event.

[0400] In one embodiment, the key input mapping module can also process other raw touch events, such as raw tap-to-release events, to convert them into corresponding standard touch events. For example, if a raw tap-to-release event is received from the event center, it can also process the raw tap-to-release event to generate a tap-to-release event.

[0401] Step 2605: The key input mapping module sends a light touch press event 2 to the input distributor.

[0402] Step 2606: Input distributor synchronizes focus application information and focus window information to the sliding manager.

[0403] The input dispatcher can obtain information such as focused application information, focused window information, and window hierarchy, and synchronize this information to the sliding manager.

[0404] In one embodiment, the input distributor can synchronize the changed information to the sliding manager whenever any of the above information changes.

[0405] In one embodiment, the input distributor can obtain the above information through the relevant interfaces of SurfaceFlinger.

[0406] Step 2607: The input distributor sends the touch press event 2 to the phone window manager.

[0407] In one embodiment, the input dispatcher can dispatch the tap-down event 2. The phone window manager can retrieve the tap-down event 2 dispatched by the input dispatcher through the event retrieval interface. The event retrieval interface is used to retrieve tap events reported by the event dispatcher and can be a pre-queue interception interface, etc.

[0408] In one embodiment, the input dispatcher may dispatch the tap press event 2 if it determines, based on the focus application information, that the current focus application is a specific application such as a desktop application. If it determines that the current focus application is not a specific application, then no dispatch is made.

[0409] Step 2608: The phone window manager performs a long press gesture detection based on the tap press event 2.

[0410] Among them, a long press gesture refers to a light press gesture whose duration (greater than or equal to) reaches a first duration threshold.

[0411] The phone window manager can determine the duration of the tap corresponding to tap press event 2. If the tap duration reaches a first duration threshold (e.g., 300ms), a long press gesture is detected. If the tap duration does not reach the first duration threshold, a long press gesture is not detected.

[0412] In one embodiment, the phone window manager can determine whether a touch-up event corresponding to the touch-down event 2 has been received within a first duration threshold after the touch-down event 2 is received. If the touch-up event is received, it means that the touch duration has not reached the first duration threshold, and it can be determined that no long-press gesture has been detected. If the touch-up event is not received, it means that the touch duration has reached the first duration threshold, and it can be determined that a long-press gesture has been detected.

[0413] Step 2609: The phone window manager sends a notification 4 to the vibration management server upon detecting a long press gesture.

[0414] Notification 4 is used to indicate that a long press gesture has been detected.

[0415] Additionally, notification 4 can instruct the vibration management server to trigger vibration.

[0416] Step 2610: The vibration management server triggers the vibrator to vibrate according to notification 4.

[0417] In one embodiment, the vibration management server triggers the vibrator to perform different vibration modes under different circumstances. For example, it can trigger the vibrator to perform different vibration modes based on different notifications.

[0418] Step 2611: The phone window manager sends a notification 5 to the System UI upon detecting a long press gesture.

[0419] Notification 5 is used to indicate that a long press gesture has been detected.

[0420] Additionally, Notification 5 can indicate that a long press gesture has been detected on the right-side pressure-sensitive button, so that the System UI can respond differently depending on the long press gesture on the different pressure-sensitive buttons.

[0421] Step 2612: In response to notification 5, the System UI displays a focus animation on the left side of the status bar.

[0422] Step 2613: When the duration of the tap reaches the first duration threshold, the phone window manager sends a notification 6 to the swipe manager.

[0423] Notification 6 can indicate that the tap duration has reached a first duration threshold, or indicate that the tap is complete.

[0424] In one embodiment, when the duration of the tap reaches a first duration threshold, the phone window manager may send notification 6 to the swipe manager upon receiving the first duration threshold after the tap press event 2, or it may send notification 6 to the swipe manager after receiving the tap release event corresponding to the tap press event 2. This embodiment does not limit this.

[0425] Step 2614: Based on notification 6, the phone window manager updates the swipe response state to the enabled state and calculates the mapping parameters.

[0426] The sliding response status is used to indicate whether the terminal device listens to and processes the sliding operation on the pressure-sensitive button. For example, it can indicate whether the sliding touch input mapping module processes the original sliding event or sliding data.

[0427] The swipe manager maintains a swipe response state. Upon receiving notification 3, the swipe response state can be switched to the on state. For example, before receiving notification 3, the swipe response state maintained by the swipe manager might be off. Upon receiving notification 3, the swipe response state can be switched from off to on to respond to subsequent swipe operations.

[0428] In one embodiment, the swipe manager can update the swipe response state to "on" when the device status meets preset conditions. These preset conditions include receiving notification 3, the focused window being a notification center window or control center window, etc. Conversely, the phone window manager can update the swipe response state to "off" when the device status does not meet the preset conditions, thereby reducing the probability of accidental touches by the user.

[0429] The mapping parameters are parameters used to map swipe events on pressure-sensitive buttons to swipe events on the screen. These may include a starting point, and at least one of the following parameters: swipe finger requirements (whether it's a single finger or multiple fingers), swipe direction, swipe gesture, and swipe distance mapping ratio.

[0430] In one embodiment, for the mapping parameters corresponding to the desktop scene, the starting point in the mapping parameters is mapped to a sliding starting point on the screen. This starting point can include an upward sliding starting point and a downward sliding starting point. The upward sliding starting point can be located at the top of the screen or at a preset distance from the top of the screen, so that the downward sliding operation of the pressure-sensitive button is mapped to a sliding operation starting from near the top of the screen. Additionally, for the left-side pressure-sensitive button, the upward sliding starting point can also be located on the left side of the screen, so that the downward sliding operation of the pressure-sensitive button is mapped to a sliding operation starting from the top left side of the screen. The downward sliding starting point can be a relatively low position on the screen, such as the lower half of the screen or the center line of the upper and lower parts, so that the downward sliding operation of the pressure-sensitive button is mapped to an upward sliding operation starting from a relatively low position on the screen. Additionally, for the left-side pressure-sensitive button, the downward sliding starting point can also be located on the left side of the screen, so that the upward sliding operation of the pressure-sensitive button is mapped to an upward sliding operation on the left side of the screen.

[0431] Step 2615: The telephone window manager sends an update command to the swipe touch input mapping module of the input reader. The update command includes the updated swipe response state and the mapping parameters.

[0432] Step 2616: The swipe touch input mapping module updates the swipe response state and mapping parameters according to the update instruction.

[0433] It should be understood that the embodiments of this application are only illustrative examples of updating the sliding response state and mapping parameters of the sliding touch input mapping module. In other embodiments, only the mapping parameters may be updated without updating the sliding response state. The embodiments of this application do not limit this.

[0434] Step 2617: The user performs a downward sliding operation on the pressure-sensitive button on the right.

[0435] Step 2618: The pressure-sensitive device driver sends the original downward slide event 2 on the right pressure-sensitive button to the event center of the input reader.

[0436] In one embodiment, the pressure-sensitive device driver can also send the sliding data of the original swipe event 2 on the right-side pressure-sensitive button to the event center.

[0437] Step 2619: The event center of the input reader sends the sliding data of the original swipe event 2 to the swipe touch input mapping module.

[0438] Step 2620: The swipe touch input mapping module generates event parameters based on the screen matrix, the updated mapping parameters, and the swipe data.

[0439] The screen matrix indicates the screen orientation and screen dimensions. Screen orientation can include landscape and portrait orientations. Screen dimensions indicate the screen's pixel size.

[0440] The swipe touch input mapping module can process the swipe data according to the screen matrix and the updated mapping parameters to map the swipe data into event parameter 3 of the swipe-down event on the screen.

[0441] Event parameter 3 can include the starting point of the swipe on the screen. This starting point can be the top of the screen or a position at a preset distance from the top, so that the downward swipe operation of the pressure-sensitive button is mapped to a swipe operation starting from near the top of the screen. Additionally, for the downward swipe operation of the left-side pressure-sensitive button, the starting point can also be located on the left side of the screen, so that the downward swipe operation of the pressure-sensitive button is mapped to a swipe operation starting from the top of the left side of the screen. For example, the starting point can be located at 1 / 3 of the screen width (i.e., the distance from the left side of the screen is 1 / 3 of the distance from the right side of the screen), or at 1 / 4 of the screen width (i.e., the distance from the left side of the screen is 1 / 3 of the distance from the right side of the screen).

[0442] As an example, the screen coordinates of this starting point in the screen coordinate system include X-axis and Y-axis coordinates. The X-axis coordinate is located at 1 / 3 of the screen width, and the Y-axis coordinate is 20. The screen coordinate system is a coordinate system with the top-left corner of the screen as the origin, the width direction of the screen as the X-axis, and the height direction of the screen as the Y-axis.

[0443] In one embodiment, before generating event parameter 3 based on the screen matrix, the updated mapping parameters, and the sliding data, the sliding touch input mapping module may first preprocess the sliding data, and then generate event parameter 3 based on the screen matrix, the updated mapping parameters, and the preprocessed sliding data.

[0444] As an example, preprocessing can validate the swipe data to check its correctness and whether it's accidental touch data. If the validation passes, the operation of generating event parameters based on the screen matrix, updated mapping parameters, and the swipe data is then performed. If the validation fails, subsequent operations are not executed.

[0445] Step 2621: The swipe touch input mapping module generates an upward swipe event 2 on the screen based on the event parameter 3.

[0446] The swipe touch input mapping module can encapsulate this event parameter as a swipe-down event on the screen.

[0447] Step 2622: The swipe touch input mapping module reports the swipe event to the input distributor.

[0448] Step 2623: The input dispatcher sends the swipe-up event to the System UI.

[0449] Step 2624: The System UI responds to the swipe-up event by pulling down to display the control center.

[0450] Step 2625: The user performs an upward swipe operation on the pressure-sensitive button on the left.

[0451] Step 2626: The pressure-sensitive device driver sends the original swipe-up event 2 on the right pressure-sensitive button to the event center of the input reader.

[0452] In one embodiment, the pressure-sensitive device driver can also send the sliding data of the original swipe-up event 2 on the right pressure-sensitive button to the event center.

[0453] Step 2627: The event center of the input reader sends the sliding data of the original swipe-up event 2 to the swipe touch input mapping module.

[0454] Step 2528: The swipe touch input mapping module generates event parameter 4 based on the screen matrix, the updated mapping parameters, and the swipe data.

[0455] The swipe touch input mapping module can process the swipe data according to the screen matrix and the updated mapping parameters, so as to map the swipe data into the event parameter 4 of the swipe-up event on the screen.

[0456] Event parameter 4 can include a starting point for the swipe on the screen. This starting point can be a relatively low position on the screen, such as the lower half of the screen or the center line of the top and bottom sections, so that the downward swipe operation of the pressure-sensitive button is mapped to an upward swipe operation starting from a relatively low position on the screen. Additionally, for the upward swipe operation of the right-side pressure-sensitive button, this starting point can also be located on the right side of the screen, so that the upward swipe operation of the pressure-sensitive button is mapped to an upward swipe operation on the right side of the screen. For example, this starting point can be located at 1 / 3 of the screen width (i.e., a distance of 1 / 3 from the right side of the screen), or at 1 / 4 of the screen width (i.e., a distance of 1 / 3 from the right side of the screen).

[0457] As an example, the screen coordinates of this starting point in the screen coordinate system include X-axis and Y-axis coordinates. The X-axis coordinate is located at 1 / 3 of the screen width, and the Y-axis coordinate is located at the center line of the top and bottom parts of the screen. The screen coordinate system is a coordinate system with the top-left corner of the screen as the origin, the width direction of the screen as the X-axis, and the height direction of the screen as the Y-axis.

[0458] In one embodiment, before generating event parameters based on the screen matrix, the updated mapping parameters, and the swipe data, the swipe touch input mapping module may preprocess the swipe data and then generate event parameters based on the screen matrix, the updated mapping parameters, and the preprocessed swipe data.

[0459] As an example, preprocessing could include validating the swipe data to check its correctness and whether it's a false touch. If the validation passes, the operation of generating event parameters based on the screen matrix, updated mapping parameters, and the swipe data is then performed. If the validation fails, no further operations are executed.

[0460] Step 2629: The swipe touch input mapping module generates an upward swipe event 2 on the screen based on event parameter 4.

[0461] Step 2630: The swipe touch input mapping module sends swipe-up event 2 to the input distributor.

[0462] Step 2631: The input dispatcher sends the swipe-up event 2 to the System UI.

[0463] Step 2632: The System UI responds to swipe-up event 2 and collapses the control center.

[0464] In response to swipe-up event 2, the System UI can either directly cancel the display of the control center or gradually move the control center towards the top of the screen to achieve a gradually collapsing effect. This application embodiment does not limit this.

[0465] This application also provides a chip coupled to a memory, which is used to read and execute computer programs or instructions stored in the memory to perform the methods described in the above embodiments.

[0466] This application also provides an electronic device including a chip for reading and executing computer programs or instructions stored in a memory, causing the methods in the various embodiments to be performed.

[0467] This embodiment also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the aforementioned method steps to implement the business processing method described in the above embodiment.

[0468] This embodiment also provides a computer program product. The computer-readable storage medium stores program code. When the computer program product is run on a computer, it causes the computer to perform the above-mentioned related steps to implement the business processing method in the above embodiment.

[0469] In addition, embodiments of this application also provide an apparatus, which may specifically be a chip, component, or module. The apparatus may include a connected processor and a memory; wherein the memory is used to store computer execution instructions, and when the apparatus is running, the processor may execute the computer execution instructions stored in the memory to cause the chip to execute the business processing methods in the above-described method embodiments.

[0470] In this embodiment, the electronic device, computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0471] This application does not specifically limit the structure of the execution subject of the method provided in this application embodiment. As long as a program containing the code of the method provided in this application embodiment can be run to perform video processing according to the method provided in this application embodiment, it is acceptable. For example, the execution subject of the method provided in this application embodiment can be an electronic device, or a functional module in an electronic device that can call and execute a program.

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

[0473] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

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

[0475] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium and includes several instructions that cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0476] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An operation response method, characterized in that, Applied to a terminal device, wherein the terminal device has a pressure-sensitive button on its side, the method includes: Display a first interface, which includes a desktop; Receives a first sliding operation applied to the pressure-sensitive button; In response to the first swipe operation, the notification center and / or control center are displayed by pulling down from the top of the first interface.

2. The method as described in claim 1, characterized in that, A first pressure-sensitive button is provided on the first side of the terminal device, and a second pressure-sensitive button is provided on the second side of the terminal device; The response to the first swipe operation, pulling down from the top of the first interface to display the notification center and / or control center, includes: In response to the first sliding operation applied to the first pressure-sensitive button, the notification center is displayed by pulling down from the top of the first interface; In response to the first sliding operation applied to the second pressure-sensitive button, the control center is displayed by pulling down from the top of the first interface.

3. The method as described in claim 1 or 2, characterized in that, Prior to the first sliding operation on the pressure-sensitive button, the receiving process also includes: The first pressing operation is received on the pressure-sensitive button. The first pressing operation refers to a pressing operation in which the pressing pressure meets a first preset condition and / or the pressing duration is greater than or equal to a first duration threshold. The response to the first swipe operation, pulling down from the top of the first interface to display the notification center and / or control center, includes: In response to the first sliding operation performed on the pressure-sensitive button after the first pressing operation, the notification center and / or control center are displayed by pulling down from the top of the first interface.

4. The method as described in claim 3, characterized in that, The method further includes: In response to the first press operation, a focus animation is displayed at the top of the first interface.

5. The method as described in claim 4, characterized in that, The step of displaying a focus animation at the top of the first interface includes: When the pressure-sensitive button is located on the left side of the terminal device, a focus animation effect is displayed in the first part of the status bar of the first interface, and the first part is located on the left side of the status bar. When the pressure-sensitive button is located on the right side of the terminal device, a focus animation effect is displayed in the second part of the status bar of the first interface, and the front area of ​​the second part is located on the right side of the status bar.

6. The method according to any one of claims 3-5, characterized in that, The method further includes: In response to the first press operation, the pressure-sensitive button is controlled to provide vibration feedback.

7. The method according to any one of claims 1-6, characterized in that, After responding to the first swipe operation and pulling down from the top of the first interface to display the notification center and / or control center, the method further includes: The second sliding operation is received on the pressure-sensitive button, and the sliding direction of the second sliding operation is opposite to that of the first sliding operation; In response to the second swipe operation, the notification center and / or control center are de-displayed.

8. The method as described in claim 7, characterized in that, Prior to receiving the second sliding operation on the pressure-sensitive button, the method further includes: Receive a second pressing operation on the pressure-sensitive button, the second pressing operation refers to a pressing operation in which the pressing pressure meets a second preset condition and / or the pressing duration is greater than or equal to a second duration threshold. The step of canceling the display of the notification center and / or control center in response to the second touch operation includes: In response to the second sliding operation performed on the pressure-sensitive button after the second pressing operation, the display of the notification center and / or control center is cancelled.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: The second interface is displayed; the second interface is the video playback interface. Receives sliding operations applied to the pressure-sensitive button; In response to a sliding operation on the pressure-sensitive button, the currently playing video is switched to the previous or next video.

10. The method as described in claim 9, characterized in that, The video playback interface is a short video playback interface, and the video is a short video; the step of switching the currently playing video to the previous or next video in response to the sliding operation on the pressure-sensitive button includes: In response to a third sliding operation on the pressure-sensitive button, the page of the short video is gradually moved out from the top of the second interface, and the page of the next short video is gradually moved in from the bottom of the second interface, so as to switch the short video to the next short video. In response to a fourth sliding operation on the pressure-sensitive button, the page of the short video is gradually moved out from the bottom of the second interface, and the previous short video is gradually moved in from the top of the second interface, so as to switch the short video to the previous short video. The sliding direction of the third sliding operation is opposite to that of the fourth sliding operation.

11. The method according to any one of claims 1-10, characterized in that, The method further includes: The third interface is displayed, which is the camera shooting interface; Receives sliding operations applied to the pressure-sensitive button; The camera's focus is adjusted in response to a sliding operation on the pressure-sensitive button.

12. The method as described in claim 11, characterized in that, The adjustment of the camera's focus in response to a sliding operation on the pressure-sensitive button includes: In response to a fifth sliding operation on the pressure-sensitive button, the focal length of the camera is increased; In response to a sixth sliding operation on the pressure-sensitive button, the focal length of the camera is reduced. The sixth sliding operation is in the opposite direction to the fifth sliding operation.

13. The method according to any one of claims 1-12, characterized in that, The method further includes: A fourth interface is displayed, the fourth interface including the first image; Receives sliding operations applied to the pressure-sensitive button; In response to a sliding operation on the pressure-sensitive button, the first image is scaled and displayed.

14. The method as described in claim 13, characterized in that, The scaling of the first image in response to a sliding operation on the pressure-sensitive button includes: In response to a seventh sliding operation on the pressure-sensitive button, the first image is magnified and displayed. In response to an eighth sliding operation performed on the pressure-sensitive button, the first image is displayed in a smaller size, the eighth sliding operation being in the opposite direction to the seventh sliding operation.

15. The method according to any one of claims 1-14, characterized in that, The side of the terminal device equipped with the pressure-sensitive button does not include a physical button.

16. The method according to any one of claims 1-15, characterized in that, The operating system of the terminal device includes an input reader and a system user interface; The response to the first swipe operation, pulling down from the top of the first interface to display the notification center and / or control center, includes: The input reader receives sliding data reported by the pressure-sensitive device driver corresponding to the pressure-sensitive button, and generates a screen sliding event based on the sliding data. The sliding data is the sliding data generated by the first sliding operation on the pressure-sensitive button. The input reader sends the screen swipe event to the system user interface; The system user interface responds to the screen swipe event by pulling down from the top of the first interface to display the notification center and / or control center.

17. The method as described in claim 16, characterized in that, The input reader generates screen swipe events based on the swipe data, including: The input reader processes the sliding data according to preset mapping parameters to obtain the event parameters of the screen sliding event. The preset mapping parameters are used to map the sliding event on the pressure-sensitive button to the sliding event on the screen. The input reader generates the screen swipe event based on the event parameters.

18. The method as described in claim 16 or 17, characterized in that, When the pressure-sensitive button is a pressure-sensitive button located on the first side of the terminal device, the screen swipe event is a swipe-down event on the left side of the screen; The system user interface responds to the screen swipe event by pulling down from the top of the first interface to display a notification center and / or control center, including: The system user interface responds to the screen swipe event by pulling down from the top of the first interface to display the notification center.

19. The method as described in claim 16 or 17, characterized in that, When the pressure-sensitive button is a pressure-sensitive button located on the second side of the terminal device, the screen swipe event is a swipe-down event on the right side of the screen; The system user interface responds to the screen swipe event by pulling down from the top of the first interface to display a notification center and / or control center, including: The system user interface responds to the screen swipe event by pulling down the control center from the top of the first interface.

20. The method according to any one of claims 16-19, characterized in that, The operating system also includes a telephone window manager, and prior to the receiving of the first sliding operation on the pressure-sensitive key, it also includes: The pressure-sensitive button receives a first press operation, which is a press operation with a press duration greater than or equal to a first duration threshold. The input reader receives the original key event reported by the pressure-sensitive device driver corresponding to the pressure-sensitive button, and generates a first key event based on the original key event. The original key event is the key event generated by the first pressing operation on the pressure-sensitive button. The input reader sends the first key press event to the telephone window manager; The telephone window manager performs gesture detection based on the first key event, and sends a first notification to the system user interface when a long press gesture is detected. The first notification is used to indicate that the long press gesture is detected on the pressure-sensitive button. The long press gesture refers to a press gesture that continuously presses the pressure-sensitive button for a first duration threshold. The system user interface responds to the first notification by displaying a focus animation at the top of the first interface.

21. The method as described in claim 20, characterized in that, The first key event is a first key press event. The phone window manager performs gesture detection based on the first key event, including: If the telephone window manager does not receive the first key release event corresponding to the first key press event within a first duration threshold after receiving the first key press event, it determines that the long press gesture has been detected. If the telephone window manager receives a first key release event corresponding to the first key press event within a first duration threshold after receiving the first key press event, it determines that the long press gesture has not been detected.

22. The method as described in claim 20 or 21, characterized in that, The system user interface responds to the first notification by displaying a focus animation at the top of the first interface, including: When the first notification indicates that the long press gesture is detected on the first pressure-sensitive button, a focus animation effect is displayed in the first part of the status bar of the first interface. The first pressure-sensitive button is a pressure-sensitive button located on the first side of the terminal device, and the first part is located on the left side of the status bar. When the first notification indicates that the long press gesture is detected on the second pressure-sensitive button, a focus animation effect is displayed in the second part of the status bar of the first interface. The second pressure-sensitive button is a pressure-sensitive button located on the second side of the terminal device, and the second part is located on the right side of the status bar.

23. The method according to any one of claims 20-22, characterized in that, The operating system also includes a vibrator management service; the method further includes: Upon detecting the long press gesture, the phone window manager sends a second notification to the vibration management server, the second notification indicating that the long press gesture has been detected. The vibration management service controls the pressure-sensitive button to vibrate according to the second notification.

24. A terminal device, characterized in that, The terminal device includes: one or more processors, and a memory; The memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the terminal device to perform the method as described in any one of claims 1 to 23.

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

Images