Terminal equipment, gesture operation method thereof and medium

Abstract

The invention relates to a gesture operation method. The method comprises the steps that terminal equipment starts an application program; and under the condition that the gesture supported by the application program conflicts with the default gesture of the operating system of the terminal equipment, the terminal equipment starts a standby gesture of the default gesture of the operating system with the conflict. According to the method and the device, under the scene that the gestures supported by the operating system and the application program are conflicted, a user can still use different functions defined by the operating system and the application program for the conflicting gestures.

Description

[0001] This application is a divisional application. The application number of the original application is 202010560016.3, and the original application date is June 18, 2020. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of terminals, and more specifically, to a terminal device and a gesture operation method and medium thereof. Background Art

[0003] In devices that use touch or other methods for interaction (such as smart phones, tablet computers, etc.), the operating system (OS) of the device and the application (APP) running on the OS will support some gesture operations and define various functions for different gestures. However, the gestures supported by the OS and APP may conflict, that is, the OS and APP support the same gesture, but the function corresponding to the gesture in the OS is different from the function corresponding to the APP.

[0004] At present, the main way to solve the problem of gesture conflict is: after the user provides a conflicting gesture in the APP, obtain at least two functions corresponding to the gesture, determine one of the at least two functions to respond, and set the other functions corresponding to the gesture to invalid (i.e., shielded), thereby solving the problem of gesture conflict. For example, in some reading APPs, a certain gesture conflicts with the gesture of the OS. For example, the gesture of "swiping left on the right edge" in the reading APP corresponds to the "turning page" function, and this gesture conflicts with the gesture corresponding to the "back" function in the OS. In order to solve the problem of gesture conflict, the prior art will execute the "turning page" function and shield the "back" function after detecting the user's "swiping left on the right edge" gesture.

[0005] However, this strategy of selecting only one of the multiple functions corresponding to the conflicting gesture to respond when a gesture conflict occurs has certain limitations: in a gesture conflict scenario, the user may have requirements for different functions, and this solution blocks some response strategies, resulting in the user being unable to use these blocked functions. Summary of the invention

[0006] The purpose of the present application is to provide a terminal device and a gesture operation method and medium thereof, so that in a scenario where the gestures supported by the OS and the APP conflict, the user can still use the different functions of the gestures defined by the OS and the APP.

[0007] The first aspect of the present application provides a gesture operation method, comprising: a terminal device starts an application; when a gesture supported by the application conflicts with a default gesture of an operating system of the terminal device, the terminal device enables a backup gesture of the default gesture of the conflicting operating system. In this way, when the terminal device detects a conflicting gesture, it executes the corresponding function of the application, and when the backup gesture is detected, it executes the corresponding function of the operating system, thereby solving the gesture conflict problem between the application and the operating system.

[0008] In a possible implementation of the first aspect, the method further includes: the terminal device determines that a gesture supported by the launched application program conflicts with a default gesture of an operating system of the terminal device.

[0009] In a possible implementation of the first aspect above, when the gestures supported by the application are known, the terminal device can determine whether there is a conflict by obtaining the gestures supported by the application and comparing them with the default gestures of the operating system. For example, if the terminal device finds that the gestures supported by the application are the same as the default gestures of the operating system, it determines that there is a conflict.

[0010] In a possible implementation of the first aspect, when the gestures supported by the application are unknown, the terminal device can determine whether there is a gesture conflict between the application and the operating system by monitoring gesture operation events. For example, the terminal device sets up a pre-monitor and a post-monitor for gesture operation events before and after the application, respectively, and the gesture in the gesture operation event monitored in the pre-monitor is the default gesture of the operating system, and when the post-monitor does not monitor the default gesture, there is a conflict between the default gesture of the operating system monitored in the pre-monitor and the gesture supported by the application.

[0011] In a possible implementation of the first aspect above, it is also possible to determine whether there is a conflict between the application and the operating system on the terminal device through the server. For example, the server can obtain gesture information of gestures supported by the application of the terminal device and the default gestures supported by the operating system of the terminal device, and determine whether there are the same gestures in the gestures supported by the application and the default gestures supported by the operating system of the terminal device. If there are the same gestures, it is determined that there is a gesture conflict between the gestures supported by the application and the default gestures of the operating system of the terminal device. Then, the terminal device obtains the gesture judgment result from the server.

[0012] In a possible implementation of the first aspect, the method further includes: before starting the application, the terminal device sets a backup gesture for a conflicting default gesture of the operating system, or prompts the user to set a backup gesture for a conflicting default gesture.

[0013] That is, in an embodiment of the present application, a backup gesture can be set in advance for all or part of the default gestures of the terminal device's operating system. When a gesture conflict is detected between a gesture supported by an application and the default gesture of the terminal device's OS, the backup gesture of the conflicting default gesture is directly enabled.

[0014] In a possible implementation of the first aspect, the method further includes: after starting the application, the terminal device sets a backup gesture for a conflicting default gesture of the operating system, or prompts the user to set a backup gesture for a conflicting default gesture.

[0015] That is, in an embodiment of the present application, after the application is started, if there is a conflict between the default gesture of the terminal device's operating system and the gesture supported by the application, the terminal device can enable a backup gesture corresponding to the default gesture, or prompt the user to set a backup gesture for the conflicting default gesture in the human-computer interaction interface of the application.

[0016] In a possible implementation of the first aspect above, since the terminal device is unable to fully detect all gestures supported by the application, the terminal device can, while detecting the gestures supported by the application itself, also obtain the gestures supported by the same application detected by other terminal devices from the server and store the gestures supported by these applications.

[0017] In a possible implementation of the first aspect, the method further includes: after detecting that the application program has exited, the terminal device turns off the standby gesture.

[0018] In a possible implementation of the first aspect, the terminal device may also prompt the user that the standby gesture is enabled or disabled when enabling or disabling the standby gesture. For example, the terminal device may notify the user that the standby gesture is enabled or disabled by displaying a notification message in the notification bar. The user may also be notified that the standby gesture is enabled or disabled by a pop-up window, displaying text, animation, or image on a blurred background, or the like.

[0019] In a possible implementation of the first aspect, when a user inputs a gesture supported by an application that conflicts with a default gesture of an operating system, the terminal device executes an operation corresponding to the gesture of the application. That is, the terminal device detects a first input of the user to the application, the first input corresponds to a gesture supported by the application that conflicts with a default gesture of the operating system; the terminal device executes the operation corresponding to the gesture supported by the application.

[0020] In a possible implementation of the first aspect, when the user inputs a backup gesture that is different from the default gesture of the operating system, the terminal device executes the backup gesture of the operating system or the operation corresponding to the conflicting default gesture. That is, the terminal device detects the second input of the user to the application, and the second input corresponds to the enabled backup gesture; the terminal device executes the operation corresponding to the backup gesture.

[0021] A second aspect of the present application provides a readable medium of a terminal device, characterized in that instructions are stored in the readable medium, and when the instructions are executed by the terminal device, the terminal device executes the gesture operation method provided in the first aspect.

[0022] A third aspect of the present application provides a terminal device, characterized in that it includes:

[0023] a memory storing instructions, and

[0024] The processor is used to read and execute instructions in the memory so that the terminal device executes the gesture operation method provided in the first aspect as described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 An example of performing a gesture operation on a device according to an embodiment of the present application is shown.

[0026] Figure 2 An example of a gesture conflict resolution system according to an embodiment of the present application is shown.

[0027] Figure 3 An example of a method for resolving gesture conflicts when gestures supported by an APP are known or pre-stored according to an embodiment of the present application is shown.

[0028] Figure 4 A UI example is shown in which a user clicks a “Reading” icon to enter a “Reading” APP.

[0029] Figure 5 A UI example is shown in which a user is notified in the form of a notification bar in the main interface of the "Reading" APP that the backup gesture has been turned on.

[0030] Figure 6 Shows the user pull down Figure 5 See the notification bar in for a UI example of detailed notification information.

[0031] Figure 7 A UI example is shown in which a book icon is clicked in the main interface of the "Reading" APP to open the book.

[0032] Fig. 8A A UI example is shown in which a user uses the conflict gesture "right edge swipe left".

[0033] Figure 8B Shows the phone Fig. 8A The responsiveness of the gesture shown.

[0034] Fig.9A A UI example is shown where a user uses the alternate gesture "swipe up on the right edge".

[0035] Fig. 9B Shows the phone Fig.9A The responsiveness of the gesture shown.

[0036] Fig. 10A A UI example is shown in which after exiting the "Reading" APP, the user is notified in the form of a notification bar that the backup gesture is closed.

[0037] Fig. 10B A UI example is shown in which the user uses the backup gesture “swipe up on the right edge” after the backup gesture is turned off.

[0038] Fig.11 An example of a method according to an embodiment of the present application is shown in which a backup gesture is not pre-set, but an OS backup gesture is set after a gesture conflict is determined between an APP and an OS.

[0039] Fig.12 The figure shows a UI example in which the user is prompted to set a backup gesture after the mobile phone determines that there is a conflict between the default gestures of the reading APP and the OS.

[0040] Fig.13 An example of an alternate gesture settings interface is shown.

[0041] Fig.14 An example of a method for monitoring a user's operation during use of an APP to obtain conflicting gestures between the APP and the OS according to an embodiment of the present application is shown.

[0042] Fig.15 An example of a method for resolving gesture conflicts when gestures supported by an APP are not pre-stored or known according to an embodiment of the present application is shown.

[0043] Fig.16 An example of the main interface after the user enters the "Reading" APP is shown when the gestures supported by the "Reading" APP are not pre-stored or known.

[0044] Fig.17 A UI example showing a user performing gesture operations in a "Reading" app.

[0045] Fig.18 The figure shows a UI example in which a prompt message pops up after the mobile phone determines that the opened APP conflicts with the default gesture of the OS.

[0046] Fig.19 A UI example is shown in which the system enables the OS backup gesture and notifies the user after the backup gesture is set.

[0047] Fig. 20 A schematic structural diagram of a terminal device 100 according to an embodiment of the present application is shown.

[0048] Fig.21 A block diagram of a system on chip (SoC) according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0049] The present application will be further described below in conjunction with specific embodiments and accompanying drawings. It will be appreciated that the specific embodiments described herein are only intended to explain the present application and are not intended to limit the present application. In addition, for ease of description, only some but not all structures or processes related to the present application are shown in the accompanying drawings. It should be noted that in this specification, similar reference numerals and letters represent similar items in the following accompanying drawings.

[0050] The illustrative embodiments of the present application include but are not limited to a terminal device and a gesture operation method and medium thereof.

[0051] With the development of smart devices, interaction with smart devices through gestures has become increasingly common. Devices that support gesture interaction include, but are not limited to, touch-screen mobile phones, tablet computers, somatosensory game consoles, etc. In various devices such as mobile phones that interact through gestures, operating systems (OS) (e.g. Both the operating system and the applications (Application, APP) running on the operating system support some gestures (for example, swipe left, swipe right, pull down, etc.), and define corresponding functions for each gesture, such as the common ones: "swipe left" corresponds to "back", "pull down" corresponds to "show menu", "swipe up" corresponds to "return to the main interface", etc. However, in some cases, the gestures supported by the OS and APP may conflict, that is, the OS and APP support the same gesture, but the definition of the corresponding function of the gesture in the OS is different from the definition of the corresponding function in the APP. For example, in a mobile phone, the OS and reading APP may both support the "swipe left on the right edge" gesture, such as Figure 1 As shown, the function of "swiping left on the right edge" defined in the OS may be "back", while the function defined in the reading app is "turn the page".

[0052] When there is a conflict between gestures in the OS and the APP, if only one of the functions is selected for response, the user's needs for different functions cannot be met. The embodiments provided in this application intend to allow users to still use the function responses supported by both the OS and the APP in the scenario where there is a conflict between the gestures supported by the OS and the APP.

[0053] Combine the following Figures 2 to 21 In the drawings of the present application, letters following a reference number, such as "100a", indicate a reference to the element with the specific reference number, while reference numbers without subsequent letters, such as "100", indicate a general reference to the implementation of the element with the reference number.

[0054] Figure 2 FIG. 1 shows a gesture conflict resolution system 10 according to an embodiment of the present application. Figure 2 As shown, the system 10 includes a terminal device 100 and a cloud server 200 .

[0055] The terminal device 100 includes a gesture management module 101 and a memory 102. The gesture management module 101 of the terminal device 100 runs on the terminal device 100 and can be implemented by hardware or by hardware executing corresponding software. The gesture management module 101 can be used to detect and handle gesture conflicts. Specifically, the gesture management module 101 has at least one of the following functions:

[0056] 1) The gesture management module 101 can detect and collect gesture information of the APP running or installed on the terminal device 100 during use of the terminal device 100, and store the gesture information of the APP running or installed on the terminal device 100 in the local memory 102 and / or send it to the cloud server 200.

[0057] 2) The gesture management module 101 can obtain gesture information supported by the APP that is not detected by the terminal device 100 from the cloud server 200. The gesture information can be detected by other terminal devices connected to the cloud server 200 that have the same APP installed and running.

[0058] It can be understood that in some embodiments, since the gesture management module 101 on a single terminal device 100 cannot detect all gesture information of the APP running or installed on the terminal device 100, the gesture management module 101 also needs to receive gesture information that is not fully detected from the cloud server 200. The gesture information that is not fully detected by these terminal devices 100 can be obtained by the cloud server 200 from other terminal devices that install the same APP.

[0059] 3) The gesture management module 101 can determine whether there is a gesture conflict between the OS and the APP based on the gesture information of the OS and the gesture information of the APP running or installed on the terminal device 100.

[0060] 4) When the gesture management module 101 determines that there is a gesture conflict between the OS and the APP, it can remind the user to set a backup gesture for the default gesture of the OS in which there is a conflict.

[0061] 5) The gesture management module 101 can remind the user when the terminal device 100 enables or disables the standby gesture.

[0062] The specific functions of the gesture management module 101 will be described in detail below.

[0063] Continue to refer to Figure 2 , the memory 102 is used to store the above-mentioned gesture information on the terminal device 100.

[0064] The cloud server 200 includes a gesture service module 201, which can be implemented by hardware or by executing corresponding software through hardware. Specifically, the gesture service module 201 is used to collect gesture information supported by each APP from each terminal device (including the terminal device 100), and update the gesture information supported by the APP to each terminal device. For example, the gesture information of each APP is collected from each terminal device 100 or from the developer of each APP (for example, when the APP is registered or listed in the application store, the APP developer is required to provide gesture information; for example, each terminal device 100 is requested to report the gesture information of the APP obtained by itself; etc.), and the latest collected APP gesture information is sent to the terminal device 100 based on the request of the terminal device 100 or in a regular push manner, so as to solve the problem that each terminal device 100 cannot fully detect all gesture information of the APP by itself.

[0065] In addition, in some embodiments, the gesture service module 201 is also used to determine whether there is a conflict between the OS of the terminal device 100 and the APP running on the terminal device 100, and send the determination result to the terminal device 100. For example, each terminal device 100 may be installed with the same or similar version of OS. In this case, the cloud server 200 can determine whether there is a conflict between the gestures supported by a certain version of OS and the gestures supported by one or more APPs, and directly send the determination result to the terminal device 100 installed with the corresponding APP.

[0066] In the gesture conflict resolution system, each terminal device 100 can conveniently obtain gesture information of one or more APPs from the cloud server 200, so that gesture conflicts can be predicted and handled before the APP is used or before a gesture conflict occurs between the APP and the OS; on the other hand, each terminal device 100 can also promptly report the gesture information of the APP it has collected to the cloud server 200 for sharing with other terminal devices 100.

[0067] It can be understood that in the various embodiments of the present application, the terminal device 100 can be various devices that can interact through gestures, such as: mobile phones, computers, laptop computers, tablet computers, televisions, game consoles, display devices, outdoor display screens, car terminals, music players and other devices with touch screens; or devices that can recognize gesture interactions, such as: somatosensory game consoles, etc. Users can achieve different functions through different gestures to facilitate interaction between users and devices. In some embodiments, the embodiments of the present application can also be applied to wearable devices worn by users. For example, smart watches, bracelets, jewelry (for example, devices made into decorative items such as earrings, bracelets, etc.) or glasses, etc., or as part of watches, bracelets, jewelry or glasses, etc. The structural examples of the terminal device 100 will be combined later. Fig. 20 In the following, the mobile phone 100a is used as an example of the terminal device 100. Figures 3 to 19 To explain in detail how to resolve gesture conflicts between OS and APP.

[0068] In addition, in various embodiments of the present application, the cloud server 200 may be a hardware server or may be embedded in a virtualized environment. For example, according to some embodiments of the present application, the cloud server 200 may be a virtual machine executed on a hardware server including one or more other virtual machines. According to some embodiments of the present application, the cloud server 200 may interact with the terminal device 100 through a network, for example, sending data to the terminal device 100 and / or receiving data from the terminal device 100.

[0069] In addition, it can be understood that in other embodiments of the present application, other types of servers can also be used to perform the above functions of the cloud server 200, and this is not limited here. Of course, the above-mentioned gesture conflict resolution system 10 is only a specific implementation of the present application. In some implementations, the terminal device 100 may not interact with the cloud server 200, but only detect and handle gesture conflicts by itself through its own gesture management module 101.

[0070] Figure 3 An example of a method for resolving gesture conflicts when the gestures supported by an APP are known or pre-stored is shown.

[0071] exist Figure 3In the illustrated embodiment, the information related to the gestures supported by the APP may be collected by the mobile phone 100a during the registration, installation or previous use of the APP, or may be obtained and saved by the mobile phone 100a from the cloud server 200, or may be stored in the cloud server 200 and the mobile phone 100a may query from the cloud server 200. According to some embodiments of the present application, Figure 3 The gesture operation method shown can be achieved by Figure 2 It is executed by the gesture management module 101, etc.

[0072] like Figure 3 As shown, the gesture operation method may include:

[0073] S301: The mobile phone 100a detects whether an APP is opened, and if an APP is detected to be opened, proceeds to S302. Figure 4 As shown, after the user turns on the mobile phone 100a, the user can click Figure 4 The mobile phone 100a enters the "Reading" APP by clicking the "Reading" icon 401 in the user interface (UI). When the mobile phone 100a detects that the user clicks the "Reading" icon 401, it continues to S302.

[0074] S302: The mobile phone 100a obtains gesture information supported by the opened APP. The information can be obtained from the local memory 102 of the mobile phone 100a or directly queried from the cloud server 200.

[0075] Then, S303: the mobile phone 100a compares the acquired gesture information of the APP with the gesture information of the local OS to determine whether there is a conflict between the opened APP and the default gesture of the OS. If there is a conflict, the process proceeds to S304.

[0076] For example, assume that the gestures supported by a reading app and the gestures supported by the OS are as shown in Table 1 below:

[0077] Table 1

[0078]

[0079] It can be seen from the example in Table 1 that the function defined by “swipe left on the right edge” in the OS is “back”, while the function defined in the reading APP is “next page”, that is, there is a conflict between the “swipe left on the right edge” gesture supported by the OS and the reading APP.

[0080] In this application, for the sake of clarity, the gestures originally supported by the OS may be referred to as default gestures to distinguish them from backup gestures.

[0081] In addition, it can be understood that in other embodiments of the present application, the cloud server 200 connected to the mobile phone 100a can also be used to determine whether the gesture of the APP conflicts with the default gesture of the OS, and the mobile phone 100a obtains the judgment result of the cloud server 200. For example, as mentioned above, the cloud server 200 obtains the gesture information of the gesture supported by the APP of the mobile phone 100a and the default gesture supported by the OS, and determines whether there is the same gesture in the gesture supported by the APP and the default gesture supported by the OS. If there is the same gesture, it is determined that there is a gesture conflict.

[0082] S304: The mobile phone 100a activates the backup gesture and notifies the user.

[0083] It can be understood that in some embodiments of the present application, a backup gesture can be set in advance for at least one of the default gestures of the OS, so that when a gesture conflict is detected, the backup gesture of the conflicting default gesture in the system can be directly enabled to fully avoid gestures supported by various apps. For example, when setting the default gesture for the OS, the backup gestures for each default gesture can be set at the same time, or after installing the OS, a backup gesture can be selected for each default gesture from the candidate gestures stored in the OS. The selection here can be random or based on a preset order. The selection order can be set according to the specific situation and is not limited here. In addition, when the mobile phone 100a is initially used, the user can be reminded to set a backup gesture for the default gesture of the OS or select a backup gesture from the candidate gestures stored in the OS.

[0084] It is understandable that a backup gesture may be pre-set for each default gesture supported by the OS, or a backup gesture may not be set for all default gestures supported by the OS, but only a part of them may be selected to set the backup gestures, for example, some gestures that are prone to conflict may be selected from all default gestures supported by the OS to set the backup gestures, or the user may selectively customize the backup gestures, etc. For example, in some embodiments, at least one backup gesture is pre-set for each default gesture supported by the OS of the mobile phone 100a, wherein the backup gesture of the default gesture may be any gesture different from the default gesture, or may be a gesture that does not conflict with the gesture of each APP or has a low probability of conflict, obtained after statistical analysis of the gesture information of each APP.

[0085] In the above example, for the gesture conflict of "swiping left on the right edge", the OS can set "swiping up on the right edge" as the backup gesture for the "back" operation when setting "swiping left on the right edge" as the default gesture for the "back" operation, as shown in Table 2. Then, if the "swiping up on the right edge" gesture is used as the back gesture instead of the "swiping left on the right edge" gesture when using the reading APP, there will be no gesture conflict between the OS and the reading APP.

[0086] Table 2

[0087]

[0088] Therefore, in S304, for the examples described in Tables 1 and 2 above, when mobile phone 100a determines that the reading APP has a gesture of "swipe left on the right edge" that conflicts with the "swipe left on the right edge" gesture supported by the OS, after the reading APP is opened, mobile phone 100a directly enables the backup gesture of "swipe up on the right edge" of the "swipe left on the right edge" gesture to execute the "back" function and notify the user of this change.

[0089] For an example of UI that notifies the user, see Figures 5 and 6 , the user clicks Figure 4 After entering the "Reading" APP by clicking the "Read" icon 401 in the "Reading" APP, the mobile phone 100a can display a notification message at the notification bar 501 above the UI interface of the "Reading" APP to notify the user that the standby gesture is turned on. In some other implementations, the mobile phone 100a can also notify the user that the standby gesture is turned on in other ways, such as a pop-up window, displaying text, animation or images on a blurred background, etc.

[0090] Users can pull down Figure 5 501 in the notification bar for detailed information 601 (see Figure 6 ). In some embodiments, a gesture management portal may be provided while providing detailed information 601, such as Figure 6 As shown, users can click Figure 6 Click the “Click to enter gesture management” button 602 to enter the gesture management page (not shown) to set and manage gestures, for example, reset the standby gestures, turn off the standby gestures, etc.

[0091] After the backup gesture is activated, when the user performs a conflicting gesture, the corresponding function of the APP will be implemented in response to the conflicting gesture, while the corresponding function of the OS cannot respond. However, the corresponding function of the OS can be implemented through the backup gesture. Figure 7 As shown, after the user clicks the "Book 1" icon 701 in the "Read" APP to open Book 1 (see Fig. 8A ),exist Fig. 8A In the interface shown, if the user uses the conflict gesture "right edge swipe left" 801, the function response of the reading APP takes effect, and the book is turned to the next page (i.e., from Fig. 8A Turn to page 5 shown Figure 8B 6 as shown), and the "fallback" function defined by the original OS does not respond.

[0092] However, users can use alternative gestures to "go back". For example, if the user performs the following on page 5 of "Book 1" Fig.9AIn the “right edge swipe up” gesture 901 shown in FIG. 1 , the OS will respond to the gesture by executing the “back” function (i.e., from Fig.9A The content of page 5 shown falls back to Fig. 9B The bookshelf interface of the reading app shown).

[0093] Then, by using "swipe up on the right edge" as the backup OS gesture for "swipe left on the right edge", the "back" function defined by the OS and the "next page" function defined by the reading APP can be responded to respectively. The user can use the "swipe left on the right edge" gesture to realize the "page turning" function, and can use the "swipe up along the right edge of the screen" gesture to realize the "back" function.

[0094] S305: The mobile phone detects the exit of the current APP. After the current APP is exited (for example, returning to the main interface, or switching to other APPs), it continues to S306: closing the system standby gesture and reminding the user.

[0095] For example, in mobile phone 100a from Fig. 9B The bookshelf interface shown returns Fig. 10A After the main interface shown in the figure is displayed, a notification message may be displayed at the notification bar 1001 above the main interface to notify the user that the standby gesture is closed. Fig. 10B In some other embodiments, the mobile phone 100a may also notify the user that the standby gesture is closed in other ways, such as a pop-up window, displaying text, animation or image on a blurred background, etc.

[0096] Furthermore, it is understandable that although Figure 3 In the illustrated embodiment, after detecting that the APP is opened, the mobile phone 100a needs to determine whether there is a conflict between the opened APP and the default gesture of the OS, and enable the backup gesture when it is determined that there is a conflict. However, in other embodiments of the present application, since the mobile phone 100a or the cloud server 200 can detect once whether there is a conflict between the default gesture of the APP and the OS, and after detecting that there is a conflict, a backup gesture can be set for the default gesture with a conflict. Therefore, after subsequently detecting that the APP is opened, the mobile phone 100a can directly set a backup gesture for the default gesture with a conflict, or directly open the default gesture with a conflict to set a backup gesture, without having to perform a conflict judgment every time it detects that the APP is opened.

[0097] Combined with the above Figures 3 to 10B This article describes an example of a solution to gesture conflicts when the gestures supported by the APP are known or pre-stored. By setting an OS backup gesture, the user can still use the gesture function responses of both the OS and the APP in the scenario of OS and APP gesture conflicts. In some embodiments of the present application, Figure 3 The operation of S301 only needs to be performed once, and the backup gesture can be used continuously after it is set.

[0098] According to other embodiments of the present application, it is also possible not to pre-set a backup gesture, but to perform the operation of setting the OS backup gesture after determining that there is a gesture conflict between the APP and the OS. In this case, the user can be reminded to set a backup gesture for the conflicting gesture only, without setting a backup gesture for all OS default gestures. The specific process is as follows: Fig.11 shown.

[0099] First, S1101, the APP in the mobile phone 100a is opened, for example, in the main interface of the mobile phone 100a (see Figure 4 ), the user clicks Figure 4 The “Reading” icon 401 in the UI shown enters the “Reading” APP.

[0100] Then, the operations from S1102 to S1103 are the same as Figure 3 The operations from S303 to S304 in are similar and will not be described in detail. In S1103, if the mobile phone 100a determines that the default gestures of the reading APP and the OS conflict, the process proceeds to S1104: the mobile phone 100a prompts the user to set a backup gesture.

[0101] For example, Fig.12 As shown, after entering the "Reading" APP, if the mobile phone 100a determines that the default gesture of the Reading APP conflicts with that of the OS, a prompt message 1201 may pop up in the UI interface of the "Reading" APP, prompting the user that the Reading APP conflicts with the OS and asking the user to set a backup gesture. The user clicks Fig.12 The pop-up prompt message 1201 in the image may enter the alternate gesture setting interface. An example of the alternate gesture setting interface is as follows: Fig.13 As shown, after entering the backup gesture setting page, the user can select the backup gestures provided by the system, such as Fig.13 The “swipe up on the right edge” 1301 or “long press the lower right corner” 1302 shown in the figure, or the “back” gesture can be customized 1303.

[0102] In some embodiments, the Fig.12 Prompt the user in ways other than the pop-up window shown, such as through a notification bar, by displaying text, animation or images on a blurred background, etc.

[0103] After the user sets the standby gesture, S1105: the system activates the standby gesture set by the user.

[0104] In this case, according to some embodiments of the present application, the backup gesture set by the user can be saved by the mobile phone 100a so that it can be directly used without re-setting when the same gesture conflict occurs during the subsequent use of the APP or other APPs. According to other embodiments of the present application, the backup gesture may not be saved, but the user may be reminded to set it each time a conflict occurs.

[0105] Back to Fig.12 , when the user thinks that there is no need to set a backup gesture, the user can directly click the pop-up window close button 1202 to skip the backup gesture setting and directly use the reading APP. At this time, the gesture conflict still exists, and after detecting the user's conflicting gesture, the mobile phone 100a can execute the corresponding operation of the gesture in the reading APP. For example, for the above-mentioned "right edge swipe left" gesture, after detecting the user's "right edge swipe left" gesture, the "page turn" function of the reading APP is executed instead of the "back" function of the OS.

[0106] The operations from S1106 to S1107 are similar to those from S306 to S307. The mobile phone detects the exit of the current APP. After the current APP is exited (for example, returning to the main interface, or switching to other APPs), the system standby gesture is turned off and the user is reminded.

[0107] In addition, it can be understood that in other embodiments of the present application, in the above S1104, the mobile phone 100a can also select a backup gesture for the conflicting default gesture from the candidate gestures stored on the mobile phone 100a. The selection here can be a random selection or a selection based on a pre-set order. The selection order can be set according to the specific situation and is not limited here.

[0108] Furthermore, it is understandable that although Fig.11 In the illustrated embodiment, after detecting that the APP is opened, the mobile phone 100a needs to determine whether there is a conflict between the opened APP and the default gesture of the OS. However, in other embodiments of the present application, since the mobile phone 100a or the cloud server 200 can detect once whether there is a conflict between the default gesture of the APP and the OS, after subsequently detecting that the APP is opened, the mobile phone 100a can directly remind the user to set a backup gesture for the conflicting default gesture, without having to perform a conflict judgment every time the APP is detected to be opened.

[0109] Combined with the above Figures 3 to 13 This article introduces an example of how to resolve gesture conflicts when the gestures supported by the app are known or pre-stored. By setting a backup gesture in advance or setting a backup gesture when the app is opened, both the gesture functions defined by the system and the gesture functions defined by the app can be responded to.

[0110] However, in some cases, the gestures supported by the APP may not be pre-stored or known. In this case, the user's operations can be monitored or detected directly during the use of the APP. If the functions corresponding to certain system gestures cannot be triggered during the use of the APP, it means that there is a gesture conflict.

[0111] Combine the following Fig.14 and Fig.15 A method for monitoring or detecting user operations during the use of an APP to obtain conflicting gestures between the APP and the OS and resolve the conflicting gestures is described.

[0112] According to some embodiments of the present application, the conflicting gestures between the APP and the OS can be obtained by monitoring the response process of the gesture operation event. In various devices that can interact through gestures, such as mobile phones, after the user performs a gesture operation on the device, a gesture operation event will be generated, which will be transmitted layer by layer and responded to at the appropriate stage. Fig.14 It shows the response process of gesture operation events after the APP in a mobile phone or other device is opened.

[0113] First, 1401: APP is opened. For example Figure 4 As shown, the user clicks Figure 4 The “Reading” icon 401 in the UI shown enters the “Reading” APP.

[0114] Then, 1402: Detect and process gesture operation events. After the user performs a gesture operation, the hardware layer of the device detects the gesture operation and reports it as an event. The main control system of the device will call the relevant program to process the gesture operation event. For example, in a mobile phone, when the APP is open, the touch sensor of the mobile phone detects the user's gesture operation, and the OS will call the relevant program to perform preliminary processing on the gesture operation event: according to the user's specific gesture action, a specific gesture operation event and the parameters corresponding to the gesture operation event are generated.

[0115] Then, 1403: the gesture operation event is sent to the APP. If the gesture is supported by the APP, the APP will respond to the event and trigger the corresponding function, and the gesture operation event ends.

[0116] If the gesture is not a gesture supported by the APP, the APP will not respond to the event, then 1404: the gesture operation event is further passed to the OS. If the gesture is the default gesture of the OS, the OS will respond to the gesture and trigger the corresponding function. If the gesture is not the default gesture of the OS, the event ends.

[0117] Therefore, if a gesture is both a gesture supported by the APP and a default gesture of the OS, the gesture will be intercepted and responded to by the APP, while the OS will not be able to respond to the gesture.

[0118] Therefore, in order to determine whether a gesture is a conflicting gesture, two monitoring points can be inserted into the original gesture operation event processing flow, and the insertion points are before and after the event is delivered to the APP. According to some embodiments of the present application, these two monitoring points can be respectively referred to as pre-monitoring and post-monitoring, such as Fig.14 As shown. Under the action of the front monitor 1405 and the rear monitor 1406, if a gesture is the default gesture of the OS, and the front monitor 1405 monitors the gesture operation event but the rear monitor 1406 does not monitor the gesture operation event, it can be said that the gesture is responded to and ended by the APP and is not further transmitted to the OS, that is, it means that the gesture is also a gesture supported by the APP, and then the gesture conflicts between the OS and the APP.

[0119] According to some embodiments of the present application, Fig.14 The functions of the pre-monitor 1405 and the post-monitor 1406 in the embodiment can be implemented by hardware, or by hardware executing corresponding software. The hardware or software may include one or more modules corresponding to the above functions. These modules may be Figure 2 A part of the gesture management module 101 in, that is, Fig.14 The method shown for detecting gesture conflicts can be Figure 2 The gesture management module 101 is used to execute.

[0120] In the case where the gestures supported by the APP may not be pre-stored or known, you can use Fig.14 The solution shown in the figure dynamically detects gestures during the APP operation period. If a conflict is detected, the backup gesture is enabled and the user is prompted. After exiting the APP, the backup gesture is disabled. The specific process is as follows: Fig.15 shown.

[0121] First, S1501, the APP is opened, for example, in the main interface of the mobile phone 100a (see Figure 4 ), the user clicks Figure 4 The “Reading” icon 401 in the UI shown enters the “Reading” APP.

[0122] Then, S1502: mobile phone 100a passes Fig.14 The operations shown below monitor the user's gesture events. Fig.16 As shown, after the user enters the "Reading" APP, he can click "Book 1" to open Book 1 for reading and perform various gesture operations, such as Fig.17As shown, during this process, the mobile phone 100a continuously monitors the user's gesture operations.

[0123] S1503: According to the monitoring result of S1502, it is determined whether there is a conflict between the opened APP and the default gesture of the OS. If there is no conflict, return to S1502 to continue monitoring; if there is a conflict, enter S1504: detect whether there is a backup gesture for the gesture function in the OS.

[0124] In the case where there is a backup gesture (determined as YES in S1504 ), the process proceeds to S1506 : enabling the OS backup gesture and prompting the user.

[0125] When there is no backup gesture (No in S1504), the process proceeds to S1505: the mobile phone 100a prompts the user to set a backup gesture for the OS.

[0126] For example, in this embodiment, if the gestures supported by the OS and APP of the mobile phone 100a are still as shown in Table 1 above, then, Fig.17 The "right edge swipe left" gesture 1701 shown is a conflicting gesture, and its function defined in the OS is "back", while its function defined in the reading APP is "next page". When the user performs this gesture, the mobile phone 100a will monitor the gesture conflict.

[0127] At this time, a prompt message 1801 may pop up in the current UI interface, prompting the user that the gesture conflicts between the reading APP and the OS, and asking the user to set a backup gesture for the "rollback" function of the operating system, such as Fig.18 As shown. User clicks Fig.18 The pop-up prompt 1801 in the image may enter the alternate gesture setting interface. An example of the alternate gesture setting interface is as follows: Fig.13 As shown, after entering the backup gesture setting page, the user can select the backup gestures provided by the system, such as Fig.13 The “right edge swiping up” 1301 or “long pressing the lower right corner” 1302 shown in the figure, or the “back” gesture can be customized 1303. In some embodiments, other than Fig.18 Prompt the user in a manner other than the pop-up window shown, such as through a notification bar, by displaying text, animation or images on a blurred background, etc.

[0128] Back to Fig.18 When the user thinks that there is no need to set a backup gesture, the user can directly click the pop-up window close button 1802 to skip the backup gesture setting. For example, in some embodiments, the reading APP defines a gesture corresponding to the "back" function. In this case, the user does not need to set a backup gesture for the "back" function, but can directly use the gesture defined by the reading APP.

[0129] After the user sets the backup gesture, the process proceeds to S1506: the system enables the OS backup gesture and notifies the user.

[0130] For example Fig.19 As shown, the mobile phone 100a can respond to the "next page" function corresponding to the "right edge left slide" gesture defined by the "reading" APP, Fig.18 Page 4 shown turns to Fig.19 The 5th page shown in the figure is displayed, and a notification message is displayed at the notification bar 1901 above the UI interface of the "Reading" APP, notifying the user that the OS backup gesture is turned on. In some embodiments, the user can learn detailed information or manage gestures by pulling down the notification bar 1901, etc. Figure 6 Similar, no further description is given here.

[0131] After the backup gesture is activated, when the user performs a conflicting gesture again, the corresponding function of the APP will respond to the conflicting gesture and the corresponding function of the original OS will not respond. However, the corresponding function of the OS can be implemented through the backup gesture. For example, on the interface of page 5 of "Book 1", if the user uses Fig. 8A The conflicting gesture "slide left on the right edge" 801 shown, the function response of the reading APP takes effect, and the book is turned to the next page (i.e., from Fig. 8A Turn to page 5 shown Figure 8B 6 as shown); if the user executes on page 5 Fig.9A In the “right edge swipe up” gesture 901 shown in FIG. 1 , the OS will respond to the gesture by executing the “back” function (i.e., from Fig.9A The content of page 5 shown falls back to Fig. 9B The bookshelf interface of the reading app shown).

[0132] According to some embodiments of the present application, the backup gesture set by the user in operation S1505 can be saved by the mobile phone 100a so that it can be directly used without re-setting when the same gesture conflict occurs during the subsequent use of the APP or other APPs. According to other embodiments of the present application, the backup gesture may not be saved, but the user may be reminded to set it each time a conflict occurs.

[0133] According to some embodiments of the present application, backup gestures may also be set in advance for all gestures supported by the OS to fully avoid gestures supported by various APPs, as shown in Table 2 above.

[0134] In the case where the conflicting gesture monitored in S1503 has been set with a backup gesture in advance, the operations of S1504 and S1505 can be skipped and S1506 can be directly executed: enabling the backup gesture and notifying the user.

[0135] Then, the process returns to the monitoring operation of S1502. In some implementations, the mobile phone can continuously monitor gesture operation events during the entire use of the APP, so as to handle gesture conflicts at any time.

[0136] S1507: The mobile phone detects the exit of the current APP. After the current APP is exited (for example, returning to the main interface, or switching to other APPs), it continues to S1508: turning off the system standby gesture and reminding the user; otherwise, it continues to monitor gesture operation events.

[0137] For example, in mobile phone 100a from Fig. 9B The bookshelf interface shown returns Fig. 10A After the main interface shown in the figure is displayed, a notification message may be displayed at the notification bar 1001 above the main interface to notify the user that the standby gesture is closed. Fig. 10B If the backup gesture "right edge swipe up" 1002 is performed in the manner shown, the system will not respond.

[0138] Combined with the above Fig.15 etc. describe an example of a solution to gesture conflicts when the gestures supported by the APP are not pre-stored or known. This method also sets an OS backup gesture so that in the scenario where the OS and APP gestures conflict, the user can still use the gesture function responses of both the OS and the APP.

[0139] Fig. 20 A schematic structural diagram of a terminal device 100 according to an embodiment of the present application is shown.

[0140] 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, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0141] It is understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

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

[0143] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0144] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

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

[0146] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0147] The charging management module 140 is used to receive charging input from the charger. The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, the internal memory 121, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc.

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

[0149] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals.

[0150] The mobile communication module 150 can provide wireless communication solutions including 2G / 3G / 4G / 5G etc. applied on the terminal device 100 .

[0151] The wireless communication module 160 can provide wireless communication solutions for application in 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 technology (NFC), infrared technology (IR), etc.

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

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

[0154] The terminal device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0155] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as storing music, video and other files in the external memory card.

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

[0157] The terminal device 100 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

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

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

[0160] Motor 191 can generate vibration prompts.

[0161] Indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0162] The SIM card interface 195 is used to connect a SIM card.

[0163] According to some embodiments of the present application, the software system of the terminal device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The present application embodiment takes the Android system of the layered architecture as an example to exemplify the software structure of the terminal device 100.

[0164] According to an embodiment of the present application, Fig.21 A block diagram of a SoC (System on Chip) 1000 is shown. Fig.21 In the figure, the dashed boxes are optional features of the SoC. Fig.21In the embodiment, SoC 1000 includes: an interconnect unit 1050, which is coupled to an application processor 1010; a system agent unit 1070; a bus controller unit 1080; an integrated memory controller unit 1040; a group or one or more coprocessors 1020, which may include integrated graphics logic, image processors, audio processors, and video processors; a static random access memory (SRAM) unit 1030; and a direct memory access (DMA) unit 1060. In one embodiment, the coprocessor 1020 may include a dedicated processor, such as, for example, a network or communication processor, a compression engine, a GPGPU, a high throughput MIC processor, or an embedded processor, etc.

[0165] The various embodiments disclosed in the present application may be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application may be implemented as a computer program or program code executed on a programmable system, which may include at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0166] Program code can be applied to input instructions to perform the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

[0167] Program code can be implemented with high-level programming language or object-oriented programming language to communicate with the processing system. When necessary, program code can also be implemented with assembly language or machine language. In fact, the mechanism described in this application is not limited to the scope of any specific programming language. In either case, the language can be a compiled language or an interpreted language.

[0168] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented in the form of instructions or programs carried or stored on one or more transient or non-transient machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors, etc. When the instructions or programs are run by the machine, the machine may perform the aforementioned various methods. For example, the instructions may be distributed via a network or other computer-readable medium. Therefore, the machine-readable medium may include, but is not limited to, any mechanism for storing or transmitting information in a machine (e.g., computer) readable form, such as a floppy disk, an optical disk, a compact disk read-only memory (CD-ROMs), a magneto-optical disk, a read-only memory (ROM), a random access memory (RAM), an erasable programmable read-only memory (EPROM), an electronically erasable programmable read-only memory (EEPROM), a magnetic card or an optical card, or a flash memory or a tangible machine-readable memory for transmitting network information via electrical, optical, acoustic, or other forms of signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, machine-readable media includes any form of machine-readable media suitable for storing or transmitting electronic instructions or information readable by a machine (eg, a computer).

[0169] Therefore, the embodiments of the present application also include non-transitory tangible machine-readable media containing instructions or containing design data, such as hardware description language (HDL), which defines the structures, circuits, devices, processors and / or system features described herein. These embodiments are also referred to as program products.

[0170] It should be understood that although the terms "first", "second", etc. may be used herein to describe various features, these features should not be limited by these terms. These terms are used only to distinguish and should not be understood as indicating or implying relative importance. For example, a first feature may be referred to as a second feature, and similarly a second feature may be referred to as a first feature without departing from the scope of the exemplary embodiments.

[0171] In addition, various operations will be described as multiple separate operations in a manner that is most helpful for understanding the illustrative embodiments; however, the order of description should not be interpreted as implying that these operations must rely on the order of description, and many of the operations can be implemented in parallel, concurrently, or simultaneously. In addition, the order of the operations can also be rearranged. When the described operations are completed, the process can be terminated, but there can also be additional operations not included in the drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0172] References in the specification to "one embodiment," "an embodiment," "an illustrative embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or property, but each embodiment may or may not necessarily include the particular feature, structure, or property. Moreover, these phrases are not necessarily directed to the same embodiment. In addition, when particular features are described in conjunction with a specific embodiment, the knowledge of those skilled in the art can affect the combination of these features with other embodiments, whether or not these embodiments are explicitly described.

[0173] Unless the context dictates otherwise, the terms "comprising," "having," and "including" are synonymous. The phrase "A / B" means "A or B." The phrase "A and / or B" means "(A), (B), or (A and B)."

[0174] As used herein, the term "module" may refer to, be part of, or include: a memory (shared, dedicated, or group) for running one or more software or firmware programs, an application-specific integrated circuit (ASIC), an electronic circuit and / or processor (shared, dedicated, or group), a combinational logic circuit, and / or other suitable components that provide the described functionality.

[0175] In the accompanying drawings, some structural or method features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order is not required. Instead, in some embodiments, these features may be described in a manner and / or order different from that shown in the illustrative drawings. In addition, the structural or method features included in a specific figure do not mean that all embodiments need to include such features. In some embodiments, these features may not be included, or these features may be combined with other features.

[0176] The embodiments of the present application are described in detail above in conjunction with the accompanying drawings, but the use of the technical solution of the present application is not limited to the various applications mentioned in the embodiments of the present patent. Various structures and variations can be easily implemented with reference to the technical solution of the present application to achieve the various beneficial effects mentioned herein. Various changes made within the knowledge of ordinary technicians in the field without departing from the purpose of the present application should all fall within the scope of the patent application.

Claims

1. A gesture operation method, characterized in that: include: The terminal device starts the application; In the case that there is a conflict between the gesture supported by the application and the default gesture of the operating system of the terminal device, the terminal device enables a backup gesture of the conflicting default gesture of the operating system.

2. The gesture operation method according to claim 1, characterized in that: Also includes: The terminal device determines that a gesture supported by the launched application conflicts with a default gesture of an operating system of the terminal device.

3. The gesture operation method according to claim 2, characterized in that: The terminal device determines that there is a conflict between the gesture supported by the application and the default gesture of the operating system in the following manner: The terminal device acquires gestures supported by the application and default gestures of the operating system; The terminal device determines that the conflict exists when there is a gesture that is the same as a default gesture of the operating system among the gestures supported by the acquired application.

4. The gesture operation method according to claim 2, characterized in that: The terminal device determines that there is a conflict between the gesture supported by the application and the default gesture of the operating system in the following manner: The terminal device sets a pre-monitor and a post-monitor for gesture operation events before and after the application respectively; The terminal device detects in the gesture operation event in the pre-monitoring that the gesture is a default gesture of the operating system, but does not detect the default gesture in the post-monitoring; The terminal device determines that there is a conflict between the default gesture of the operating system monitored in the pre-monitoring and the gesture supported by the application.

5. The gesture operation method according to claim 1, characterized in that: Also includes: The terminal device obtains a gesture determination result from a server, wherein the gesture determination result indicates that there is a conflict between a gesture supported by the application and a default gesture of an operating system of the terminal device.

6. The gesture operation method according to claim 1, characterized in that: Also includes: Before starting the application, the terminal device sets the backup gesture for the conflicting default gesture of the operating system, or prompts the user to set the backup gesture for the conflicting default gesture.

7. The gesture operation method according to claim 1, characterized in that: Also includes: After starting the application, the terminal device sets the backup gesture for the conflicting default gesture of the operating system, or prompts the user to set the backup gesture for the conflicting default gesture.

8. The gesture operation method according to claim 1, characterized in that: The terminal device stores gestures supported by the application, wherein the stored gestures include gestures obtained by the terminal device detecting the application, and gestures supported by the application detected by another terminal device and received by the terminal device from a server.

9. The gesture operation method according to claim 1, characterized in that: Also includes: After detecting that the application program has exited, the terminal device turns off the standby gesture.

10. The gesture operation method according to claim 9, characterized in that: Also includes: When the standby gesture is enabled or disabled, the terminal device prompts the user that the standby gesture has been enabled or disabled.

11. The gesture operation method according to claim 1, characterized in that: Also includes: The terminal device detects a first input of a user to the application, where the first input corresponds to a gesture supported by the application that conflicts with a default gesture of the operating system; The terminal device executes the operation corresponding to the gesture supported by the application.

12. The gesture operation method according to claim 11, characterized in that: Also includes: The terminal device detects a second input of the user to the application, where the second input corresponds to the enabled standby gesture; The terminal device performs an operation corresponding to the standby gesture.

13. A readable medium of a terminal device, characterized in that: The readable medium stores instructions, and when the instructions are executed by a terminal device, the terminal device executes the gesture operation method according to any one of claims 1 to 12.

14. A terminal device, characterized in that: include: a memory storing instructions, and A processor is used to read and execute instructions in the memory so that the terminal device executes the gesture operation method as described in any one of claims 1-12.

Images