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 application date of the original application is June 18, 2020. The entire content of the original application is incorporated herein by reference. Technical Field

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

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

[0004] Currently, the main way to solve the gesture conflict problem is: after the user provides a conflicting gesture in the APP, obtain at least two functions corresponding to this gesture, determine one of them to respond, and set the other functions corresponding to this gesture to be invalid (that is, blocked), so as to solve the gesture conflict problem. 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 function of "turning the page", and this gesture conflicts with the gesture corresponding to the "going back" function in the OS. In order to solve this gesture conflict problem, the prior art will, after detecting the gesture of the user "swiping left on the right edge", execute the "turning the page" function and block the "going back" function.

[0005] However, this strategy of only selecting one of the multiple functions corresponding to the conflicting gesture to respond when there is a gesture conflict has certain limitations: in the 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 this application is to provide a terminal device, a gesture operation method thereof, and a medium, so that in the 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, including: a terminal device starts an application; in a case where there is a conflict between the gestures supported by the application and the default gestures of the operating system of the terminal device, the terminal device enables an alternative gesture for the default gesture of the operating system with which there is a conflict. In this way, when the terminal device detects a conflicting gesture, it executes the corresponding function of the application, and when it detects the alternative gesture, it executes the corresponding function of the operating system, solving the problem of gesture conflicts between the application and the operating system.

[0008] In a possible implementation of the above first aspect, it further includes: the terminal device determines that there is a conflict between the gestures supported by the started application and the default gestures of the operating system of the terminal device.

[0009] In a possible implementation of the above first aspect, in a case where 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, when there is a gesture in the obtained gestures supported by the application that is the same as the default gesture of the operating system, it is determined that there is a conflict.

[0010] In a possible implementation of the above first aspect, in a case where 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 listening for gesture operation events. For example, the terminal device sets a pre-listening and a post-listening for gesture operation events before and after the application respectively, and when the gesture in the gesture operation event is the default gesture of the operating system in the pre-listening, and the default gesture is not detected in the post-listening, there is a conflict between the default gesture of the operating system detected in the pre-listening and the gestures supported by the application.

[0011] In a possible implementation of the above first aspect, it is also possible to determine whether there is a conflict between the application and the operating system on the terminal device through a server. For example, the server can obtain the gesture information of the gestures supported by the application on the terminal device and the default gestures supported by the operating system of the terminal device, and determine whether there are the same gestures among the gestures supported by the application and the default gestures supported by the operating system of the terminal device. In a case where 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 above first aspect, it further includes: before starting the application, the terminal device sets an alternative gesture for the default gesture of the operating system with which there is a conflict, or prompts the user to set an alternative gesture for the conflicting default gesture.

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

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

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

[0016] In a possible implementation of the first aspect above, since the terminal device has the problem that it cannot fully detect all the gestures supported by the application, when the terminal device itself detects the gestures supported by the application, it can also obtain from the server the gestures supported by the same application detected by other terminal devices and store these gestures supported by the application.

[0017] In a possible implementation of the first aspect above, it further includes: after the terminal device detects that the application exits, it turns off the alternative gesture.

[0018] In a possible implementation of the first aspect above, it further includes: when the terminal device enables or disables the alternative gesture, it prompts the user that the alternative gesture has been enabled or disabled. For example, the terminal device can notify the user that the alternative gesture has been enabled or disabled by displaying a notification message in the notification bar. It can also notify the user that the alternative gesture has been enabled or disabled in the form of a pop-up window, displaying text, animation or image on a blurred background, etc.

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

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

[0021] The second aspect of the present application provides a readable medium for a terminal device, characterized in that the readable medium stores instructions, and when the instructions are run by the terminal device, the terminal device executes the gesture operation method provided in the foregoing first aspect.

[0022] The third aspect of the present application provides a terminal device, characterized by including:

[0023] a memory storing instructions therein, and

[0024] a processor configured to read and execute the instructions in the memory so that the terminal device executes the gesture operation method provided in the foregoing first aspect. Description of the Drawings

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

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

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

[0028] Figure 4 Shows a UI example where the user clicks on the "Read" icon to enter the "Read" APP.

[0029] Figure 5 Shows a UI example of notifying the user that the alternative gesture has been enabled in the form of a notification bar on the main interface of the "Read" APP.

[0030] Figure 6 Shows the user pulling down Figure 5 the notification bar in to obtain detailed notification information in the UI example.

[0031] Figure 7 Shows a UI example of clicking on the book icon to open the book on the main interface of the "Read" APP.

[0032] Figure 8A Shows a UI example of the user using the conflicting gesture "swipe left from the right edge".

[0033] Figure 8B Shows the response effect of the mobile phone to Figure 8A the gesture shown.

[0034] Figure 9A Shows a UI example where the user uses the alternative gesture "swipe up on the right edge".

[0035] Figure 9B Shows the response effect of the mobile phone to Figure 9A the gesture shown.

[0036] Figure 10A Shows a UI example that notifies the user of the closure of the alternative gesture in the form of a notification bar after exiting the "Reading" APP.

[0037] Figure 10B Shows a UI example where the user uses the alternative gesture "swipe up on the right edge" after the alternative gesture is closed.

[0038] Figure 11 Shows an example of a method of not presetting an alternative gesture according to an embodiment of the present application, but setting an OS alternative gesture after determining that there is a gesture conflict between the APP and the OS.

[0039] Figure 12 Shows a UI example that prompts the user to set an alternative gesture after the mobile phone determines that there is a conflict between the default gesture of the Reading APP and the OS.

[0040] Figure 13 Shows an example of an alternative gesture setting interface.

[0041] Figure 14 Shows an example of a method of monitoring the user's operations during the use of the APP to obtain the conflicting gestures between the APP and the OS according to an embodiment of the present application.

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

[0043] Figure 16 Shows an example of the main interface after the user enters the "Reading" APP when the gestures supported by the "Reading" APP are not pre-stored or known.

[0044] Figure 17 Shows a UI example where the user performs a gesture operation in the "Reading" APP.

[0045] Figure 18 Shows a UI example where a prompt message pops up after the mobile phone determines that there is a conflict between the opened APP and the default gesture of the OS.

[0046] Figure 19 Shows a UI example where after the alternative gesture is set up, the system enables the OS alternative gesture and notifies the user.

[0047] Figure 20 Shows a schematic structural diagram of a terminal device 100 according to an embodiment of the present application.

[0048] Figure 21 Shows a block diagram of a system on chip (SoC) according to an embodiment of the present application. Detailed implementation manners

[0049] The present application will be further described below in conjunction with specific embodiments and the accompanying drawings. It can be understood that the specific embodiments described herein are only for explaining the present application, rather than limiting the present application. In addition, for the convenience of description, only parts related to the present application rather than all structures or processes are shown in the accompanying drawings. It should be noted that in this specification, similar reference numerals and letters denote similar items in the following drawings.

[0050] Exemplary embodiments of the present application include, but are not limited to, terminal devices and their gesture operation methods and media, etc.

[0051] With the development of intelligent devices, interacting with intelligent devices through gestures has become increasingly widespread. Devices that support gesture interaction include, but are not limited to, touchscreen mobile phones, tablet computers, motion-sensing game consoles, etc. Among various devices that interact through gestures such as mobile phones, the operating system (OS) (such as etc.) and application programs (APPs) running on the operating system will support some gestures (for example, swiping left, swiping right, pulling down, etc.), and define corresponding functions for each gesture respectively. For example, commonly: "swiping left" corresponds to "going back", "pulling down" corresponds to "displaying the menu", "swiping up" corresponds to "returning to the home screen", etc. However, in some cases, the gestures supported by the OS and the APP may conflict, that is, the OS and the APP support the same gesture, but the definition of the function corresponding to this gesture in the OS is different from the definition of the function corresponding to it in the APP. For example, in a mobile phone, the OS and a reading APP may both support the gesture of "swiping left from the right edge". As Figure 1 shown, however, the function defined for "swiping left from the right edge" in the OS may be "going back", while the function defined in the reading APP is "turning the page".

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

[0053] The following will Figures 2 to 21 be described in detail with reference to some embodiments of the present application for the gesture operation method. In the drawings of the present application, the letters following the reference numerals, such as "100a", represent references to elements having that specific reference numeral, and reference numerals without subsequent letters, such as "100", represent general references to embodiments of elements with that reference numeral.

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

[0055] Among them, 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 the gesture information of the APPs running or installed on the terminal device 100 during the use of the terminal device 100, and store the gesture information of the APPs 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 from the cloud server 200 the gesture information supported by the APPs that the terminal device 100 has not detected. These gesture information can be detected by other terminal devices that are connected to the cloud server 200 and have the same APP installed and running.

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

[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 it is determined that there is a gesture conflict between the OS and the APP, the gesture management module 101 can remind the user to set an alternative gesture for the default gesture of the conflicting OS.

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

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

[0063] Continue to refer below Figure 2 , and the memory 102 is used to store the above 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 hardware executing corresponding software. Specifically, the gesture service module 201 is used to collect the 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, collect the gesture information of each APP from each terminal device 100 or from the developers of each APP (for example, when the APP is registered or listed in the application store, require the APP developer to provide gesture information; again, request each terminal device 100 to report the gesture information of the APP it has obtained; etc.), and send the latest collected APP gesture information to the terminal device 100 in a manner based on the request of the terminal device 100 or regular push, so as to solve the problem that each terminal device 100 cannot completely detect all the gesture information of the APP by itself.

[0065] In addition, in some embodiments, the gesture service module 201 is further 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 the OS. In this case, the cloud server 200 can determine whether there is a conflict between the gestures supported by a certain version of the 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 this gesture conflict resolution system, each terminal device 100 can conveniently obtain gesture information of one or more APPs from the cloud server 200, so as to predict and handle gesture conflicts 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 report to the cloud server 200 in a timely manner the gesture information of the APPs it has collected, so that other terminal devices 100 can share it.

[0067] It can be understood that in the embodiments of the present application, the terminal device 100 can be various devices capable of interacting through gestures, such as: mobile phones, computers, laptop computers, tablet computers, TVs, game consoles, display devices, outdoor display screens, vehicle-mounted terminals, music players, and other devices with touch screens; or devices capable of recognizing gesture interactions, such as: motion-sensing game consoles, etc. Users can achieve different functions through different gestures to facilitate the interaction between the user and the device. 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 (such as devices made into decorative items such as earrings, bracelets, etc.) or glasses, etc., or as part of watches, bracelets, jewelry or glasses. The structural example of the terminal device 100 will be described later in combination with Figure 20 description. Below, taking the mobile phone 100a as an example of the terminal device 100, in combination with Figures 3 to 19 to describe in detail the method for resolving gesture conflicts between the OS and the APP.

[0068] In addition, in the embodiments of the present application, the cloud server 200 can be a hardware server or can be implanted in a virtualized environment. For example, according to some embodiments of the present application, the cloud server 200 can be a virtual machine running on a hardware server including one or more other virtual machines. According to some embodiments of the present application, the cloud server 200 can interact with the terminal device 100 through a network, such as 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, which is not limited here. Of course, the above gesture conflict resolution system 10 is only a specific implementation manner of the present application. In some embodiments, the terminal device 100 can also not interact with the cloud server 200, but only detect and handle gesture conflicts by its own gesture management module 101.

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

[0071] In Figure 3In the illustrated embodiment, the relevant information about the gestures supported by the APP can be collected by the mobile phone 100a during the registration, installation, or previous use of the APP, or can be obtained and saved by the mobile phone 100a from the cloud server 200, or can also be stored at the cloud server 200 and the mobile phone 100a can query it from the cloud server 200. According to some embodiments of the present application, Figure 3 The illustrated gesture operation method can be executed by Figure 2 the gesture management module 101 and the like in

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

[0073] S301: The mobile phone 100a detects whether an APP is opened. If it is detected that an APP is opened, proceed to S302. For example, as Figure 4 shown, after the user turns on the mobile phone 100a, the user can enter the "Reading" APP by clicking the "Reading" icon 401 in the user interface (UI) in Figure 4 . When the mobile phone 100a detects the operation of the user clicking the "Reading" icon 401, proceed to S302.

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

[0075] Subsequently, S303: The mobile phone 100a determines whether there is a conflict between the opened APP and the default gestures of the OS by comparing the obtained gesture information of the APP with the gesture information of the local OS. If there is a conflict, enter S304.

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

[0077] Table 1

[0078]

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

[0080] In the present application, for clarity, the gestures originally supported by the OS can be referred to as default gestures to distinguish them from the alternative gestures.

[0081] In addition, it can be understood that in other embodiments of the present application, it is also possible to determine whether there is a conflict between the gestures of the APP and the default gestures of the OS through the cloud server 200 connected to the mobile phone 100a, and the mobile phone 100a obtains the judgment result of the cloud server 200. For example, as described above, the cloud server 200 obtains the gesture information of the gestures supported by the APP of the mobile phone 100a and the default gestures supported by the OS, and determines whether there are the same gestures among the gestures supported by the APP and the default gestures supported by the OS. In the case where there are the same gestures, it is determined that there is a gesture conflict.

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

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

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

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

[0086] Table 2

[0087]

[0088] Therefore, in S304, for the examples described in Table 1 and Table 2 above, when the mobile phone 100a determines that there is a conflict between a gesture "swipe left from the right edge" of the reading APP and the "swipe left from the right edge" gesture supported by the OS, after the reading APP is opened, the mobile phone 100a directly enables the alternative gesture "swipe up from the right edge" of the "swipe left from the right edge" gesture to execute the "back" function and notifies the user of this change.

[0089] For an example of the UI for notifying the user, see Figures 5 to 6 , after the user clicks the Figure 4 "Read" icon 401 in to enter the "Read" APP, the mobile phone 100a can display a notification message at the notification bar 501 above the UI interface of the "Read" APP to notify the user that the alternative gesture is enabled. In some other embodiments, the mobile phone 100a can also notify the user that the alternative gesture is enabled in other ways, such as a pop-up window, displaying text, an animation, or an image on a blurred background, etc.

[0090] The user can pull down the Figure 5 notification bar 501 in to view the detailed information 601 (see Figure 6 ). In some embodiments, an entry for gesture management can be provided while providing the detailed information 601. As shown in Figure 6 , the user can click the Figure 6 "Click to enter gesture management" button 602 in to enter a gesture management page (not shown) to set and manage gestures. For example, reset the alternative gesture, turn off the alternative gesture, etc.

[0091] After the alternative gesture is activated, when the user executes a conflicting gesture, the corresponding function of the APP will be realized in response to the conflicting gesture, while the corresponding function of the OS will not respond. However, the corresponding function of the OS can be realized through the alternative gesture. For example, as shown in Figure 7 , after the user opens Book 1 by clicking the "Book 1" icon 701 in the "Read" APP (see Figure 8A ), on the interface shown in Figure 8A , if the user uses the conflicting gesture "swipe left from the right edge" 801, the function response of the reading APP takes effect and the book is turned to the next page (i.e., from the Figure 8A shown Page 5 to the Figure 8B shown Page 6), while the originally defined "back" function of the OS does not respond.

[0092] However, the user can perform "back" through the alternative gesture. For example, if the user executes on Page 5 of the opened "Book 1" as shown in Figure 9AFor the "swipe up on the right edge" gesture 901 shown, the OS will execute the "go back" function in response to this gesture (i.e., go back from the Figure 9A content of page 5 shown to Figure 9B the bookshelf interface of the reading APP shown).

[0093] Then, by taking "swipe up on the right edge" as an alternative OS gesture to "swipe left on the right edge", both the "go back" function defined by the OS and the "next page" function defined by the reading APP can be respectively responded to. The user can use the "swipe left on the right edge" gesture to implement the "page turning" function, and at the same time can use the "swipe up along the right edge of the screen" gesture to implement the "go back" function.

[0094] S305: The mobile phone detects the exit of the current APP. After the current APP exits (for example, returns to the home screen or switches to another APP), it then proceeds to S306: Turn off the system alternative gesture and notify the user.

[0095] For example, after the mobile phone 100a returns from the Figure 9B bookshelf interface shown to the Figure 10A home screen shown, notification information can be displayed at the notification bar 1001 above the home screen to notify the user that the alternative gesture is turned off. At this time, if the user then executes the alternative gesture "swipe up on the right edge" 1002 in the manner shown in Figure 10B , the system will not respond. In some other embodiments, the mobile phone 100a can also notify the user that the alternative gesture is turned off in other ways, such as through a pop-up window, displaying text, animation or images on a blurred background, etc.

[0096] In addition, it can be understood that although in the Figure 3 embodiment shown, 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 alternative gesture in the case of determining that there is a conflict. However, in other embodiments of the present application, since the mobile phone 100a or the cloud server 200 can know whether there is a conflict between the APP and the default gesture of the OS by detecting once, and after detecting that there is a conflict, an alternative gesture can be set for the conflicting default gesture. Therefore, after detecting that the APP is opened subsequently, the mobile phone 100a can directly set an alternative gesture for the conflicting default gesture, or directly turn on the alternative gesture set for the conflicting default gesture, without having to perform a conflict judgment every time the APP is detected to be opened.

[0097] The above describes an example of a method for resolving gesture conflicts in the case where the gestures supported by the APP are known or have been pre-stored. By setting the OS alternative gesture, in the scenario of OS and APP gesture conflicts, users can still use the gesture function responses of both the OS and the APP. In some embodiments of the present application, Figures 3 to 10B ...Figure 3 The operation of S301 only needs to be executed once. After the alternative gesture is set, it can be used continuously later.

[0098] According to some other embodiments of the present application, it is also possible not to preset the alternative gesture in advance, but to perform the operation of setting the alternative gesture of the OS after it is determined that there is a gesture conflict between the APP and the OS. In this case, the user can be reminded only to set an alternative gesture for the conflicting gesture, without setting an alternative gesture for all the default gestures of the OS. The specific process is as Figure 11 shown.

[0099] First, in S1101, the APP in the mobile phone 100a is opened. For example, on the home screen of the mobile phone 100a (see Figure 4 ), the user enters the "Reading" APP by clicking on the "Reading" icon 401 in the UI shown in Figure 4 .

[0100] Subsequently, the operations of S1102 to S1103 are similar to the operations of S303 to S304 in Figure 3 , and will not be elaborated here. In S1103, if the mobile phone 100a determines that there is a conflict between the Reading APP and the default gesture of the OS, it continues to S1104: The mobile phone 100a prompts the user to set an alternative gesture.

[0101] For example, as shown in Figure 12 , after entering the "Reading" APP, if the mobile phone 100a determines that there is a conflict between the Reading APP and the default gesture of the OS, a prompt message 1201 can pop up in the UI interface of the "Reading" APP, prompting the user that there is a gesture conflict between this Reading APP and the OS, and asking the user to set an alternative gesture. The user clicks on the popped-up prompt message 1201 in Figure 12 , and can enter the alternative gesture setting interface. An example of the alternative gesture setting interface is shown in Figure 13 . After entering the alternative gesture setting page, the user can select an alternative gesture provided by the system, such as selecting the "Swipe up on the right edge" 1301 or "Long press the lower right corner" 1302 shown in Figure 13 , or can also customize the "Back" gesture 1303.

[0102] In some embodiments, it is also possible to prompt the user in a way other than the pop-up window shown in Figure 12 , such as through the notification bar, by displaying text, animations or images on a blurred background, etc.

[0103] After the user sets the alternative gesture, in S1105: The system enables the alternative gesture set by the user.

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

[0105] Return to Figure 12 , when the user deems it unnecessary to set backup gestures, 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 "swipe left on the right edge" gesture, after detecting the user's "swipe left on the right edge" gesture, the "page turning" function of the reading APP is executed instead of the "back" function of the OS.

[0106] The operations of S1106 to S1107 are similar to the operations of S306 to S307. The mobile phone detects the exit of the current APP. After the current APP exits (for example, returns to the home screen or switches to other APPs), the system backup gestures are closed and the user is reminded.

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

[0108] In addition, it can be understood that although in Figure 11 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 gestures of the OS. However, in other embodiments of the present application, since the mobile phone 100a or the cloud server 200 can know whether there is a conflict between the APP and the default gestures of the OS after one detection, after detecting that the APP is opened subsequently, 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] As described above in combination with Figures 3 to 13 examples of solutions to gesture conflicts are introduced in the case where the gestures supported by the APP are known or have been pre-stored. By pre-setting backup gestures or setting backup gestures 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 such cases, the operations of the user can be directly monitored or detected during the use of the APP. If, during the use of the APP, the functions corresponding to certain system gestures cannot be triggered, it indicates that there is a gesture conflict.

[0111] The following will be combined with Figure 14 and Figure 15 to illustrate the method of monitoring or detecting the operations of the user during the use of the APP to obtain the conflicting gestures between the APP and the OS and resolve the gesture conflict.

[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 such as mobile phones that can interact through gestures, after the user performs a gesture operation on the device, a gesture operation event will be generated, and this gesture operation event will be passed layer by layer and responded at an appropriate stage. Figure 14 Shows the response process of the gesture operation event after the APP in a device such as a mobile phone is opened.

[0113] First, 1401: The APP is opened. For example Figure 4 as shown, the user enters the "Reading" APP by clicking on the "Reading" icon 401 in the UI shown in Figure 4 the figure.

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

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

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

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

[0118] Therefore, in order to determine whether a gesture is a conflicting gesture, two listening points can be inserted into the original gesture operation event handling process. The insertion points are before and after the event is passed to the APP. According to some embodiments of the present application, these two listeners can be respectively referred to as a pre-listening and a post-listening, as Figure 14 shown. Under the action of the pre-listening 1405 and the post-listening 1406, if a gesture is a default gesture of the OS, and the pre-listening 1405 detects this gesture operation event while the post-listening 1406 does not detect this gesture operation event, it can be explained that this gesture is responded to and ended by the APP and does not continue to be passed to the OS, that is, it is explained that this gesture is also supported by the APP. Then, this gesture conflicts between the OS and the APP.

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

[0120] can be executed by the gesture management module 101 in Figure 14 In the case where the gestures supported by the APP may not be pre-stored or understood, the scheme shown in Figure 15 can be used to dynamically detect gestures during the operation of the APP. If a conflict is detected, a backup gesture is enabled and the user is prompted. After exiting the APP, the backup gesture is turned off. The specific process is as

[0121] shown. First, S1501, the APP is opened. For example, on the main interface of the mobile phone 100a (see Figure 4 ), the user enters the "Reading" APP by clicking the "Reading" icon 401 in the UI shown in Figure 4 .

[0122] Subsequently, S1502: The mobile phone 100a listens for the user's gesture operation events through the operation shown in Figure 14 . For example, as shown in Figure 16 , after the user enters the "Reading" APP, the user can open Book 1 to read by clicking "Book 1" and perform various gesture operations, such as Figure 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, determine 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 an alternative gesture for this gesture function in the OS.

[0124] If there is an alternative gesture (judged as yes in S1504), enter S1506: Enable the OS alternative gesture and prompt the user.

[0125] If there is no alternative gesture (judged as no in S1504), enter S1505: The mobile phone 100a prompts the user to set the alternative gesture of 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, Figure 17 The "swipe left on the right edge" gesture 1701 shown is a conflicting gesture. Its defined function in the OS is "go back", while its defined function in the reading APP is "next page". When the user operates this gesture, the mobile phone 100a will detect a gesture conflict.

[0127] At this time, a prompt message 1801 can be popped up in the current UI interface, prompting the user that this gesture conflicts in the reading APP and the OS, and asking the user to set an alternative gesture for the "go back" function of the operating system, such as Figure 18 shown. When the user clicks on Figure 18 the popped-up prompt message 1801, the alternative gesture setting interface can be entered. An example of the alternative gesture setting interface is as Figure 13 shown. After entering the alternative gesture setting page, the user can select an alternative gesture provided by the system, such as selecting Figure 13 the "swipe up on the right edge" 1301 or "long press the lower right corner" 1302 shown in Figure 18 or can also customize the "go back" gesture 1303. In some embodiments, other methods than the

[0128] pop-up window method shown in Figure 18 can also be used to prompt the user, such as through the notification bar, by displaying text, animations or images on a blurred background, etc.

[0129] After the user sets the alternative gesture, continue to S1506: The system enables the OS alternative gesture and notifies the user.

[0130] For example Figure 19 As shown, the mobile phone 100a can respond to the "next page" function corresponding to the "swipe left on the right edge" gesture defined by the "Reading" APP, and from Figure 18 the 4th page shown in Figure 19 turn to the 5th page shown in Figure 6 and display a notification message at the notification bar 1901 above the UI interface of the "Reading" APP to notify the user that the OS alternative gesture is enabled. In some embodiments, the user can pull down the notification bar 1901 or other means to view detailed information or manage gestures, etc., which is similar to

[0131] After the alternative gesture is activated, when the user performs a conflicting gesture again, the corresponding function of the APP will be realized in response to the conflicting gesture, while the corresponding function of the original OS cannot respond, but the corresponding function of the OS can be realized through the alternative gesture. For example, on the interface of the 5th page of "Book 1", if the user uses Figure 8A the conflicting gesture "swipe left on the right edge" 801 shown in Figure 8A the function response of the Reading APP takes effect and the book is turned to the next page (i.e., from Figure 8B the 5th page shown in Figure 9A turn to the 6th page shown in Figure 9A ); and if the user performs the "swipe up on the right edge" gesture 901 shown in Figure 9B on the 5th page, the OS will respond to this gesture and execute the "back" function (i.e., from

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

[0133] According to some embodiments of the present application, alternative gestures can also be set in advance for all gestures supported by the OS to fully avoid the 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 an alternative gesture in advance, the operations of S1504 and S1505 can be skipped, and directly execute S1506: Enable the alternative gesture and notify the user.

[0135] Subsequently, return to the monitoring operation of S1502. In some embodiments, the mobile phone can continuously monitor gesture operation events throughout the entire usage process of the APP to handle gesture conflicts at any time.

[0136] S1507: The mobile phone detects the exit of the current APP. After the current APP exits (for example, returns to the home screen or switches to another APP), continue to S1508: Turn off the system standby gesture and remind the user; otherwise, continuously monitor gesture operation events.

[0137] For example, after the mobile phone 100a returns from Figure 9B the bookshelf interface shown in Figure 10A to the home screen shown in Figure 10B a notification message can be displayed at the notification bar 1001 above the home screen to notify the user that the standby gesture is turned off. At this time, if the user then performs the standby gesture "swipe up on the right edge" 1002 in the manner shown in

[0138] The above describes, in combination with Figure 15 etc., an example of a method for resolving gesture conflicts when the gestures supported by such an APP are not pre-stored or understood. This method also enables users to still use the gesture function responses of both the OS and the APP in the scenario of OS and APP gesture conflicts by setting the OS standby gesture.

[0139] Figure 20 FIG. shows a schematic structural diagram of a terminal device 100 according to an embodiment of the present application.

[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, a headphone 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. Among them, the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric 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 can be understood that the structure illustrated in the embodiments 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 those illustrated, or combine certain components, or split certain components, or have different component arrangements. The illustrated components 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 Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and / or a Neural-Network Processing Unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0143] The controller may generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.

[0144] A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory may save the instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can directly call it from the memory. This avoids repeated accesses, 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 interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0146] It can be understood that the interface connection relationships between the modules illustrated in the embodiments of the present application are only illustrative descriptions and do 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 a charging input from a 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 inputs from the battery 142 and / or the charging management module 140 to supply power to the processor 110, the internal memory 121, the display screen 194, the camera 193, the wireless communication module 160, etc. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance).

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

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

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

[0151] The wireless communication module 160 may provide solutions for wireless communications applied to the terminal device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (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, enabling the terminal device 100 to communicate with the network and other devices through wireless communication technologies. The wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite based augmentation systems (SBAS).

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

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

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

[0156] The internal memory 121 can be used to store computer-executable program codes, and the executable program codes include instructions. The internal memory 121 can include a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function (such as a sound playback function, an image playback function, etc.). The data storage area can store data created during the use of the terminal device 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 can include a high-speed random access memory, and can 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 the instructions stored in the internal memory 121 and / or the instructions stored in the memory provided in the processor.

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

[0158] The touch sensor 180K, also known as the "touch control device". The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also known as the "touch control screen". The touch sensor 180K is used to detect touch operations acting thereon or nearby. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In some other embodiments, the touch sensor 180K can also be disposed on the surface of the terminal device 100, at a different position from the display screen 194.

[0159] The keys 190 include a power-on key, volume keys, etc. The keys 190 can be mechanical keys or touch keys. The terminal device 100 can receive key inputs and generate key signal inputs related to the user settings and function control of the terminal device 100.

[0160] The motor 191 can generate vibration prompts.

[0161] The indicator 192 can be an indicator light, which can be used to indicate the charging state, power change, and can also be used to indicate messages, missed calls, notifications, etc.

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

[0163] According to some embodiments of the present application, the software system of the terminal device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservices architecture, or cloud architecture. In the embodiments of the present application, taking the Android system with a layered architecture as an example, the software structure of the terminal device 100 is exemplarily described.

[0164] According to the embodiments of the present application, Figure 21 A block diagram of a SoC (System on Chip) 1000 is shown. In Figure 21 wherein, the dashed box is an optional feature of the SoC. In Figure 21In this case, the SoC 1000 includes: an interconnect unit 1050, which is coupled to the application processor 1010; a system agent unit 1070; a bus controller unit 1080; an integrated memory controller unit 1040; one or a group of one or more coprocessors 1020, which may include integrated graphics logic, an image processor, an audio processor, and a video processor; 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, and so on.

[0165] The various embodiments disclosed in this application may be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of this 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 memories and / or storage elements), at least one input device, and at least one output device.

[0166] The program code may be applied to the input instructions to perform the various functions described in this application and generate output information. The output information may 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] The program code may be implemented in a high-level procedural language or an object-oriented programming language in order to communicate with the processing system. When necessary, the program code may also be implemented in assembly language or machine language. In fact, the mechanisms described in this application are not limited to the scope of any specific programming language. In any case, the language may 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 and the like. When the instructions or programs are run by a machine, the machine may perform the various methods described above. For example, the instructions may be distributed via a network or other computer-readable media. Thus, machine-readable media may include, but are not limited to, any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), such as a floppy disk, an optical disk, a compact disc 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 or optical card, or a flash memory or tangible machine-readable memory for transmitting network information by electrical, optical, acoustic, or other forms of signals (e.g., carrier waves, infrared signals, digital signals, etc.). Thus, machine-readable media include any form of machine-readable media suitable for storing or transmitting electronic instructions or machine (e.g., computer) readable information.

[0169] Accordingly, the embodiments of the present application also include non-transient tangible machine-readable media that contain instructions or contain design data, such as a 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 terms such as "first", "second", etc. may be used herein to describe various features, these features should not be limited by these terms. These terms are only used for distinction and should not be construed as indicating or implying relative importance. For example, without departing from the scope of the exemplary embodiments, a first feature may be referred to as a second feature, and similarly, a second feature may be referred to as a first feature.

[0171] In addition, the various operations will be described as multiple discrete operations in a manner most conducive to understanding the illustrative embodiments; however, the order of description should not be construed as implying that these operations must be dependent on the order of description, and many of these operations may be performed in parallel, concurrently, or simultaneously. In addition, the order of the operations may also be rearranged. When the described operations are completed, the processing may be terminated, but there may also be additional operations not included in the drawings. The processing may correspond to a method, function, procedure, subroutine, subprogram, etc.

[0172] References in the specification to "one embodiment", "an embodiment", "an illustrative embodiment", etc., mean that the described embodiment may include a particular feature, structure, or characteristic, but every embodiment may or may not necessarily include the particular feature, structure, or characteristic. Moreover, these phrases are not necessarily referring to the same embodiment. Further, when a particular feature is described in connection with a specific embodiment, the knowledge of those skilled in the art can affect the combination of that feature with other embodiments, whether or not such embodiments are explicitly described.

[0173] Unless the context otherwise requires, the terms "comprise", "have", and "include" are synonyms. 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, as part of it, 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 a processor (shared, dedicated, or group), combinational logic circuitry, and / or other suitable components that provide the said functionality.

[0175] In the drawings, some structural or method features may be shown in a particular arrangement and / or order. However, it should be understood that such a particular arrangement and / or ordering is not necessary. Rather, in some embodiments, these features may be illustrated in a manner and / or order different from that shown in the illustrative drawings. Additionally, the structural or method features included in a particular drawing 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 have been described in detail above in conjunction with the accompanying drawings. However, the use of the technical solutions of the present application is not limited to the various applications mentioned in the embodiments of this patent. Various structures and variations can be easily implemented with reference to the technical solutions of the present application to achieve the various beneficial effects mentioned herein. Within the scope of knowledge possessed by those of ordinary skill in the art, various changes made without departing from the gist of the present application shall fall within the scope covered by the patent of the present application.

Claims

1. A gesture operation method, characterized in that, it includes: The terminal device starts an application; Obtain the first gesture operation event; Based on the gesture operation event, determine whether there is a conflict between the gestures supported by the application and the default gestures of the operating system of the terminal device; If there is a conflict, the terminal device enables the alternative gesture of the default gesture of the operating system.

2. The gesture operation method according to claim 1, characterized in that, it further includes: The terminal device determines that there is a conflict between the gestures supported by the started application and the default gestures of the 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 gestures supported by the application and the default gestures of the operating system in the following manner: The terminal device obtains the gestures supported by the application and the default gestures of the operating system; When there is a gesture in the obtained gestures supported by the application that is the same as the default gesture of the operating system, the terminal device determines that there is such a conflict.

4. The gesture operation method according to claim 2, characterized in that, The terminal device determines that there is a conflict between the gestures supported by the application and the default gestures of the operating system in the following manner: The terminal device sets a pre-listening and a post-listening of gesture operation events before and after the application; The terminal device monitors that the gesture in the gesture operation event in the pre-listening is the default gesture of the operating system, while the default gesture is not monitored in the post-listening; The terminal device determines that there is a conflict between the default gesture of the operating system monitored in the pre-listening and the gestures supported by the application.

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

6. The gesture operation method according to claim 1, characterized in that, it further includes: Before starting the application, the terminal device sets the alternative gesture for the default gesture of the operating system with a conflict, or prompts the user to set the alternative gesture for the default gesture with a conflict.

7. The gesture operation method according to claim 1, characterized in that, it further includes: After starting the application, the terminal device sets the alternative gesture for the default gesture of the operating system with a conflict, or prompts the user to set the alternative gesture for the default gesture with a conflict.

8. The gesture operation method according to claim 1, characterized in that, The gestures supported by the application are stored on the terminal device, where the stored gestures include the gestures detected by the terminal device for the application and the gestures supported by the application detected by another terminal device received by the terminal device from the server.

9. The gesture operation method according to claim 1, It is characterized in that further comprising: after the terminal device detects that the application exits, the standby gesture is turned off.

10. The gesture operation method according to claim 9, it is characterized in that further comprising: when the terminal device enables or disables the standby gesture, the user is prompted that the standby gesture has been enabled or disabled.

11. The gesture operation method according to claim 1, it is characterized in that further comprising: the terminal device detects a first input from the user to the application, and the first input corresponds to a gesture supported by the application that conflicts with the default gesture of the operating system; the terminal device performs an operation corresponding to the gesture supported by the application.

12. The gesture operation method according to claim 11, it is characterized in that further comprising: the terminal device detects a second input from the user to the application, and 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, it is characterized in that the readable medium stores instructions, and when the instructions are run by the terminal device, the terminal device executes the gesture operation method according to any one of claims 1-12.

14. A terminal device, it is characterized in that comprising: a memory that stores instructions, and a processor configured to read and execute the instructions in the memory so that the terminal device executes the gesture operation method according to any one of claims 1-12.

Images