HK1238752B - Method and apparatus for invoking function in application - Google Patents

Description

Method and device for calling functions in an application

Technical Field

The present application relates to the field of information processing technology, and in particular to a method and device for calling a function in an application.

Background Art

A key feature of smart devices like mobile phones, tablets, and smartwatches is the ability for users to customize and install a wide variety of apps, expanding their functionality. As smart devices evolve, apps are becoming increasingly powerful, with many integrating multiple functions to meet diverse user needs.

One potential problem with integrating features within an app is the increased complexity of user operations. Currently, when a user uses a smart device like a mobile phone to access an app function, the typical process is as follows: user takes out their phone → wakes it up → unlocks it → finds the desired app → runs it → navigates to the desired function's sub-screen (via menus, buttons, etc.) → performs the required operation within that sub-screen. This means that, in practice, accessing an app function requires numerous steps, which is not only inconvenient but also consumes significant user time.

Summary of the Invention

To address the above technical issues, this application provides a method and device for calling functions in an application. The technical solutions are as follows:

According to a first aspect of the present application, a method for calling a function in an application is provided, which is applied to a user device, and the method includes:

Get the user's operations on the user's device;

When the acquired operation matches a predefined user operation, a function in the application associated with the predefined user operation is called.

According to a second aspect of the present application, a barcode payment method is provided, applied to a user device, the method comprising:

Get the user's operations on the user's device;

When the acquired operation matches a predefined user operation, a payment barcode display interface in the payment application is called to display a barcode image for payment on the screen of the user device.

According to a third aspect of the present application, a device for calling a function in an application is provided, which is applied to a user equipment, and the device includes:

A detection control module is used to obtain the user's operations on the user device;

The calling control module is used to call a function in the application associated with the predefined user operation when the acquired operation matches the predefined user operation.

According to a fourth aspect of the present application, a barcode payment device is provided, applied to a user device, the device comprising:

A detection control module is used to obtain the user's operations on the user device;

The payment barcode display control module is used to call the payment barcode display interface in the payment application when the acquired operation matches the predefined user operation, so as to display the barcode image for payment on the screen of the user device.

The technical solution provided in this application utilizes predefined user operations as trigger conditions for calling functions in an application. By obtaining the user's operations, a specific function within a specific application can be automatically called when the obtained operations match the predefined user operations, thereby avoiding tedious operating steps such as waking up the device and unlocking the device, and realizing quick calling of specific functions in a specific application.

It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

FIG1 is a schematic diagram of a first flow chart of a function calling method in an application of the present application;

FIG2 is a schematic diagram of a first specific application scenario of the present application solution;

FIG3 is a schematic diagram of a second specific application scenario of the present application solution;

FIG4 is a schematic diagram of a third specific application scenario of the present application solution;

FIG5 is a schematic diagram of a fourth specific application scenario of the present application solution;

FIG6 is a schematic diagram of the structure of a function calling device in an application of the present application;

FIG7 is a schematic diagram of the structure of the QR code payment device of the present application;

FIG8 is a schematic structural diagram of a device used to configure the apparatus of the present application.

DETAILED DESCRIPTION

In order to enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be described in detail below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art should fall within the scope of protection of this application.

FIG1 is a flowchart of a method for calling a function in an application provided by the present application. The method may be executed by a mobile terminal or other device, such as a mobile phone, and the method may specifically include the following steps:

S101, obtaining the user's operation on the user device;

S102: When the acquired operation matches a predefined user operation, call a function in the application associated with the predefined user operation.

The calling scheme of the functions in the application provided by this application can be applied to user devices with a sensing module, a button, and a touch input module. The sensing module may include a gravity sensor, an acceleration sensor, a gyroscope, a distance sensor, a fingerprint sensor, and the like. The button may include a physical button or a touch-sensitive virtual button on the user device, a virtual button in a touch-screen operating system interface or a specific application interface, and the like. The user device may be a composite device such as a mobile phone, a tablet computer, a smart watch, or a single-function device such as an electronic business card or an electronic tag, and this application does not limit this.

In this application, the function in the called application can be to directly jump to display a function interface in a specific application, such as the payment barcode display interface in the payment application, the chat dialogue interface with a specific user in the instant messaging application, etc.; it can also be to directly trigger the execution of a specific function in a specific application, such as the play/pause/switch function in the media playback application, the information refresh function in the information application, etc.

In the present application, predefined user operations can be used as a quick triggering method for specific functions in specific applications, thereby realizing quick display of a specific function interface in a specific application, or quick execution of a specific function interface in a specific application. In this way, when the device is turned on, the detection result of the user operation can be obtained. If the predefined user operation can be detected, the specific function in the specific application associated with the predefined user operation can be directly called. Not only can the operations such as unlocking the device and searching for applications be avoided, but the specific function of a specific application can be directly called instead of just opening the main interface of the application, thereby further reducing the user's operation steps in the application and improving operation efficiency.

During actual use, the specific application can be pre-launched and run in the system background so that it can be quickly called when needed; or the pre-launch method can be used. In this case, the device can launch the specific application after detecting a predefined user operation and run it in the system foreground or background to achieve quick call of application functions and reduce memory resource usage.

During actual use, after detecting a predefined user operation, you can first check whether the corresponding application is already running in the system background. If so, switch directly to the application and jump to the specific function interface for displaying information images; if the application is not found running in the background, start the application and run it in the system foreground or background, and jump to the specific function interface of the application, or execute a specific function in the application.

In actual applications, an association between a predefined user operation and a "call a specific function" operation can be pre-established so that after detecting a predefined user operation, the specific function can be directly called instead of entering the main interface of the application. Specifically, relevant settings can be made in the system of the mobile terminal to establish an association between the predefined user operation and the called specific function, so that when the predefined user operation is detected, the specific function can be quickly called. Alternatively, it is also possible to set whether the specific function in the application installed in the system supports the quick call function, and if it is set to yes, it is associated with the predefined user operation. For example, in the payment application of the mobile terminal, the payment QR code interface can be set in the settings interface of the payment application to allow quick call through predefined user operations and can be associated with specific predefined user operations, or it can be set by default in the system, and the user can make settings to associate with predefined user operations. In this application, the specific application and the specific function interface can be set in advance by the user, or by the system, or by other means; the specific predefined user operation can also be set by the user.

According to a specific embodiment of the present application, quick calling of functions in an application can be implemented based on a sensing module configured on a user device. Accordingly:

The specific implementation of S101 is: obtaining the detection result of the user operation by the sensing module;

S102 is specifically implemented as follows: after detecting a predefined user operation input, calling a function in the application associated with the predefined user operation.

Exchanging information using images such as barcodes and QR codes is a common application, with common scenarios including payment, access control, and exchanging business cards. However, using smart devices like mobile phones to exchange image information remains cumbersome. For example, using a mobile QR code for quick payment typically involves the following steps: user removes phone → wakes up → unlocks phone → finds payment app → runs app → finds QR code subpage → executes QR code display. This means that, in practice, a complete QR code display requires numerous steps, making it inconvenient and unsuitable for high-traffic scenarios like supermarkets and public transportation.

This embodiment will take the application scenario of quick payment using mobile phone barcodes (including one-dimensional barcodes, two-dimensional barcodes, etc.) as an example, that is, in the payment application, the payment interface of the payment barcode can be quickly called out through this application solution, and this application solution will be explained in detail.

Mobile phone users can pre-set an operation method as a trigger code when the payment barcode is displayed. This operation can be achieved by using the phone's gravity sensor, acceleration sensor, gyroscope, distance sensor, fingerprint sensor and other sensing modules. The following are some examples of custom user operations:

Using a gravity sensor: A gravity sensor, also known as a G-sensor, is a specialized accelerometer. Gravity sensing technology utilizes the piezoelectric effect. It determines horizontal orientation by measuring the magnitude of the gravitational force exerted by a weight inside the phone in two orthogonal directions. The default gravity sensing center is typically when the phone is horizontal. By measuring the acceleration caused by gravity, the gravity sensor can calculate the device's position relative to the horizontal plane. A typical application of a mobile phone's gravity sensor is to automatically control the switching between landscape and portrait display modes.

In the present application scheme, predefined user operations can be implemented based on the posture changes when the mobile phone screen is basically vertical and horizontal, such as the action changes of "horizontally placing the phone"/"vertically placing the phone", the action changes of "tilting the phone to the left"/"tilting the phone to the right" (the tilt angle reaches a certain threshold), etc. In actual application, it can be set that when the number of consecutive changes of the above actions reaches a preset threshold, it is considered that a predefined user operation has been input.

Using an accelerometer: An accelerometer, also known as an accelerometer or linear accelerometer, measures linear acceleration caused by various external forces, including gravity. Unlike gravity sensors, accelerometers can detect the phone's linear state of rest and motion, as well as its direction of motion, in addition to its relative position to the horizontal plane.

In the present application, predefined user operations can be implemented based on changes in the direction of the mobile phone's movement, for example, shaking the phone up and down, left and right, or shaking it in the positive and negative directions of any approximate straight line, etc. In actual application, it can be set that when the number of consecutive shakings of the above actions reaches a preset number threshold and the amplitude of the shaking reaches a preset amplitude threshold, it is considered that the predefined user operation has been input.

Using a gyroscope: A gyroscope can measure the angular velocity of an object when an external force acts on it and causes it to rotate. It can also sense the rotation/stationary state and the direction of rotation.

In the present application, predefined user operations can be implemented based on changes in the rotation direction of the mobile phone. For example, a swing operation of the mobile phone, that is, a rotation operation of the mobile phone along any axis, can be implemented. In actual application, when the number of consecutive swings of the above action reaches a preset number threshold and the swing amplitude reaches a preset amplitude threshold, it can be set that the predefined user operation has been input.

Distance sensors can measure the relative distance between the module and an object by detecting changes in physical quantities and converting the results into distance. Depending on the physical quantity being detected, distance sensing modules can include optical displacement sensors, linear proximity sensors, ultrasonic displacement sensors, and others. A common application of mobile phone distance sensors is when a user holds their phone close to their head while answering or making a call. The distance sensor measures the distance between the phone and their head, turning off the screen backlight when the distance decreases to a certain level, and then turning it back on again when the distance is removed. This prevents accidental operation during calls and saves power.

In the present application, user operations can be implemented based on the change in the distance between the mobile phone and an object (such as a palm, a wall, etc.), such as the action change of "approaching the object"/"moving away the object", where "approaching" and "leaving" are judged by a preset distance threshold. In actual application, it can be set that when the number of consecutive changes in the above-mentioned actions reaches a preset threshold, it is considered that a predefined user operation has been input. For example, if the user moves his palm close to the mobile phone screen, and shakes his palm basically parallel to the mobile phone screen in two opposite directions once, it is considered that a predefined user operation has been input.

There are many other ways to implement predefined user operations, which are not listed here. In practice, as long as the customized user operation does not conflict with other operations, it is sufficient. It is also understood that predefined user operations can be implemented by combining two or more sensing modules. For example, combining an accelerometer and a gyroscope can achieve more complex determination of the phone's posture/motion state and generate corresponding user-defined operations.

After the user enters the custom operation, the phone records and stores the key information. This application does not limit the collection algorithm for various types of user predefined operation information, and traditional information collection algorithms can be used. Of course, in some scenarios, some operations that are the default of the device system can also be used as the user's predefined operations. This application does not specifically limit the setting method of the user's predefined operations, such as whether it is system default or user-set, such as by the user in the system, or by the user in a specific application in the system.

After the predefined user operations are set, the phone can be powered on to obtain the detection results of the sensor module for the predefined user operations. If the currently detected user operation matches the predefined user operation, the user is directly redirected to the payment barcode display interface in the payment application, displaying the barcode image for payment, thereby simplifying the user operation. This application does not limit the matching algorithm for various specific operation information, and traditional matching algorithms can be used.

In the present application, when a specific function interface displays an information image, it can obtain a pre-generated static information image or generate an information image in real time. For example, in the quick display scenario of the payment barcode interface in the payment application, when the payment barcode interface is displayed, the information image of the payment barcode can be a static graphic or a graphic generated in real time and can change dynamically.

In one embodiment, the detection function of the sensing module can be in a continuously turned-on state. The sensing module detects the user's predefined user operations in real time and can report them in an interrupted manner. That is, the user device can obtain the predefined user operations detected by the sensing module in an interrupted manner, so that the user device can obtain the predefined user operations and perform corresponding processing. In this way, the user can quickly display the payment barcode on the mobile phone screen by entering the predefined user operations under any circumstances, ensuring that the user can use the predefined operations to quickly trigger the barcode display at any time. In other words, the mobile phone device will detect the predefined user operations through the sensing module in real time, and can quickly start the relevant specific function interface by collecting the predefined user operations under any circumstances.

In one embodiment, the sensing module's detection results of user operations can also be obtained when the device is not in use. This non-use state may include one or more of the following: locked, dormant, and standby. In this case, the mobile phone can obtain detection results in certain specific states, and only in these specific states will it quickly activate specific functions in related applications by obtaining the results collected by the sensing module.

Among the above-mentioned non-use states, the locked state can represent a restriction on the user's device operation permissions, while the sleep and standby states can be descriptions of the working status of the device's software or hardware modules, and there is no clear division in the definition. In some cases, the above-mentioned non-use states can exist simultaneously in a device. For example, some devices will automatically lock after being in standby or sleep for a period of time, or automatically switch specific software and hardware modules to standby or sleep after being locked for a period of time. In short, the common feature of the above states is that if the device is currently in these states, it will be cumbersome for the user to use conventional barcode display operations. The application of this application solution can enable users to directly display the barcode in these cases without having to wake up the device, unlock the device, and other operating steps. It can also reduce the activation time of the function of obtaining predefined user operation detection results to reduce the power consumption of the device.

In one embodiment, the sensing module may be configured to detect predefined user operations only when the sensing module is not in use, thereby avoiding power consumption caused by long-term activation of the sensing module.

In one embodiment, based on the typical "wake up, then unlock" operation sequence of typical smart devices, the timing for obtaining detection results from the sensing module can be set to "after the user device is awakened from sleep and before it is unlocked." This can reduce the time it takes to obtain detection results, thereby reducing device power consumption.

In one embodiment, the sensing module can also be set to detect predefined user operations only when "the user device is awakened from sleep mode and is not unlocked". When the mobile phone is in a locked and black screen state, the detection function of the sensing module can be turned off. After the mobile phone is awakened, the sensing module can be started to perform predefined user operation detection, thereby further reducing the power consumption caused by the sensing module.

That is, when the phone is not in use most of the time (for example, when it is in a pocket or bag), the function of obtaining the predefined user operation detection results or the detection function of the sensing module can be disabled. When the phone is awakened by other means (such as the power button, volume button, etc.), the corresponding function is activated. Based on the detection results of the predefined user operation, the following situations may occur:

1) The user enters a predefined user operation to quickly display the payment interface of the payment barcode. In addition to displaying the payment interface, the phone can be unlocked or kept locked, which is not limited in this application.

2) The user unlocks the phone normally (via a password, gesture, etc.). After successful unlocking, the phone enters the use state and the detection function of the sensing module is turned off.

3) The user does not enter any information, which may be caused by an incorrect operation. After a period of time, the phone returns to sleep mode and the detection function of the sensing module is turned off.

It can be seen that by applying the solution of this application, the activation time of the sensing module can be further shortened while adapting to the basic operating habits of the user, thereby reducing the power consumption of the device.

In this application, there are no specific limitations on the operating mode of the sensing module, such as whether the sensing module is always in a state capable of detecting predefined user operations after the user device is turned on, whether the sensing module is in a state capable of detecting predefined user operations within a set time, whether the predefined user operation detection module uses an interrupt to report predefined user operations, or whether the processor in the mobile phone actively calls the sensing module to operate. The specific operating mode of the sensing module can be controlled or set according to specific needs.

In one embodiment, if no other user operations on the device are detected within a period of time after the barcode display interface is called, the display of the barcode image can be stopped. This prevents the barcode image from being secretly photographed or stolen, thereby improving the security of information use. The time threshold for controlling the cessation of displaying the barcode image can be set according to actual needs, such as 30 seconds, 60 seconds, etc. The specific implementation method of stopping the display of the barcode image can be to exit the function call interface of a specific application, exit a specific application, return to the system standby interface, or restore the device to a locked state, a dormant state, etc. This application does not limit this.

Figure 2 is a schematic diagram of a specific implementation scenario for applying the present application solution to merchant payments. When the mobile phone is in a dormant and locked non-use state, the user shakes the mobile phone in any direction for more than three times continuously, and the shaking amplitude meets a certain requirement. The acceleration sensor detects the operation and matches it with the predefined user operation for authentication. After authentication is passed, the payment barcode (including one-dimensional barcode and two-dimensional barcode) image in the payment application is triggered to be displayed on the mobile phone screen. If the user does not perform other operations on the mobile phone for more than 60 seconds, the payment barcode image displayed on the mobile phone screen disappears.

In another specific implementation scenario of the present application, predefined user operations can be used to quickly display a specific merchant interface in a payment application or shopping application. Before using this function, the user pre-sets the association between a predefined operation (such as a shaking operation, etc.) and the "current merchant interface display" function in the payment application or shopping application. When using this function, the user enters a merchant's business premises, takes out the mobile phone, and enters the predefined operation that has been associated with the aforementioned association. The mobile phone matches the operation with the predefined operation for authentication. After the authentication is passed, the positioning function of the mobile phone (such as a positioning function based on WIFI, GPS, or Bluetooth) is called to obtain the current location of the mobile phone. Based on the obtained location information, the merchant corresponding to the location is further calculated, and then the relevant information of the merchant (such as product information, discount information, etc.) is displayed on the mobile phone screen.

According to the solution of the present application, predefined user operation detection can also be combined with other methods to implement the call of a specific application. For example, the detection result of the user operation by the sensing module can be obtained when a predefined button is pressed.

The user can pre-specify one or more buttons as one of the triggering conditions for calling functions in the application. The button can be a physical button or a touch-sensitive virtual button on the mobile phone, or a virtual button in the touch-screen operating system interface or a specific application interface. When the user needs to quickly call a function in the application, he needs to input the predefined operation while pressing the predefined button. For the device side, in addition to obtaining the detection results of the predefined user operation by the sensing module, it is also necessary to determine whether the predefined button is pressed. Only when the two conditions of "predefined user operation is detected" and "predefined button is pressed" are met at the same time, will the subsequent function call in the application be triggered.

Taking the mobile payment barcode application scenario as an example, based on user habits, users can designate the "Volume Down" button as a predefined key. While holding down the "Volume Down" button, they shake the phone. The phone detects that both conditions are met and then calls the app to display the payment barcode.

For quick operations involving user privacy, such as displaying a payment barcode, certain security requirements may be required. When using predefined operations such as the above-mentioned ones in conjunction with predefined buttons to implement specific function calls in specific applications, since the "predefined buttons" are also the user's personal private information (predefined by the user), this method can effectively confirm that the current operator of the user device is a legitimate user, avoiding losses caused by illegal users operating the user device. In some cases, it can also avoid misoperations. For example, when a mobile phone is placed in a bag, it may trigger the quick call of the application function due to excessive shaking or excessive frequency. Combining it with predefined buttons can effectively avoid or reduce the occurrence of such non-user-intentional triggering situations.

To improve user security, other security verification mechanisms can be added. For example, after detecting predefined user input and before invoking a function in the application, the user may be asked to enter one or more authentication information. The authentication information can be in the form of a text password, fingerprint, gesture, facial information, etc. If the authentication information entered by the user is correct, the function in the application is invoked. Conversely, if the authentication information entered by the user is incorrect, the function in the application is not invoked.

Figure 3 is a schematic diagram of a specific implementation scenario of applying the solution of the present application to merchant payment. When the mobile phone is in black screen, locked screen or standby state, the user holds the mobile phone and swings it continuously for more than 2 times based on any approximate axis, and the swing amplitude meets certain requirements. The gyroscope detects the operation and matches it with the predefined user operation for authentication. After the authentication is passed, the payment application is called, the currently used payment method is displayed on the screen (the user can modify it according to needs), and the user is prompted to enter one or more authentication information.

For example, for some third-party payment applications, if the user has not turned on the "login-free" function, after the shake authentication is passed, the user will be further required to enter the login password of the payment application. The login password can be in the form of a text password, fingerprint, gesture, facial information, etc. After the user enters the login password, the mobile phone side authenticates the password locally or sends it to the network side. After the authentication is passed, the payment barcode is displayed on the mobile phone screen.

In another embodiment, after the shake authentication is passed, the payment method selection interface of the payment application is displayed on the mobile phone screen, and the user is prompted to enter the unlock password (including fingerprint and digital password). After the user enters the correct unlock password, clicks on a payment method logo to display the corresponding payment barcode.

It is understood that the quick call of the payment barcode interface in the embodiment of this application is only used to schematically illustrate "quick call of application functions." It should not be understood as limiting the specific implementation scheme and application scenarios of this application. In addition, different sensing module-based operations can be used to associate different functions in the same application, or to associate functions in multiple different applications, thereby achieving quick call of multiple different application functions.

According to a specific embodiment of the present application, quick call of application functions can be implemented based on the fingerprint module configured on the user device. The fingerprint module here can refer to a general term for modules including a series of functions such as fingerprint collection, matching operation, authentication or recognition judgment, etc. Accordingly:

The specific implementation of S101 is: obtaining the fingerprint input by the user on the fingerprint module;

S102 is specifically implemented as follows: after detecting the input of fingerprint information, calling a function in the application associated with the predefined user operation.

Instant messaging is a frequently used application feature. However, using smart devices like mobile phones to conduct instant messaging chats is currently quite cumbersome. The typical process is as follows: user takes out their phone → wakes it up → unlocks it → finds the instant messaging app → runs the app → taps the chat partner's icon to enter the chat sub-screen → starts chatting. As can be seen, in practice, a complete chat operation requires multiple steps.

This embodiment will take the instant messaging chat application scenario as an example to explain the present application scheme in detail. That is, in the instant messaging application, the present application scheme can quickly call up the chat interface with a specific friend.

In actual applications, an association between fingerprint information and the operation of "calling a specific friend chat interface" can be established in advance, so that after the fingerprint information is detected, it is possible to jump directly to the specific friend chat interface instead of the main interface. Specifically, relevant settings can be made in the system of the mobile terminal to establish an association relationship between fingerprint information and the called specific friend chat interface, so that when the fingerprint information is detected, the specific friend chat interface can be quickly called. Alternatively, it can be set in the application installed in the system whether the specific friend chat interface supports the quick call function, and if it is set to yes, it is associated with the fingerprint information. For example, in the settings interface of the instant messaging application, the interface of the specific friend chat interface is set to be quickly called through fingerprint information and can be associated with specific fingerprint information, or it can be set by default in the system, and the user can set the associated fingerprint. In this application, the specific friend chat interface can include multiple, and can be distinguished by associating different finger fingerprints.

In one implementation, when a fingerprint module detects fingerprint information, a user verification mechanism can be incorporated into the fingerprint module's authentication processing function to enhance security. Specifically, after fingerprint information is detected, it is matched against a preset fingerprint. If a match occurs, a quick display of a specific friend chat interface is invoked. The aforementioned association of fingerprint information with invoking a specific friend chat interface can involve setting a specific fingerprint as a trigger condition for quickly invoking the specific friend chat interface. Specifically, the device user is required to pre-enter one or more of their fingerprints, and the fingerprint module generates and stores authentication fingerprint information. In actual use, after the fingerprint module of the user device detects fingerprint information, it further determines whether the detected fingerprint information matches the pre-stored authentication fingerprint information. Only if the fingerprint information matches is the specific friend chat interface displayed. Conversely, if the fingerprint information does not match (which may include no fingerprint information being detected), the specific friend chat interface will not be displayed on the user device screen. This triggering mechanism effectively confirms that the current user of the user device is a legitimate user, preventing adverse consequences caused by unauthorized users operating the user device. This application does not limit the specific fingerprint collection and authentication algorithm; conventional fingerprint collection and authentication algorithms can be used.

In one embodiment, the detection function of the fingerprint module can be in a continuously turned-on state. The fingerprint module detects the user's fingerprint information in real time and can report it in an interrupted manner. That is, the user device can obtain the fingerprint information detected by the fingerprint module in an interrupted manner so that the user device can obtain the fingerprint information and perform corresponding processing. In this way, the user can quickly display a specific friend chat interface on the mobile phone screen by inputting fingerprint information under any circumstances, ensuring that the user can use the fingerprint to quickly trigger the display of the specific friend chat interface at any time. In other words, the mobile phone device will detect fingerprint information through the fingerprint module in real time, and can quickly start the relevant specific friend chat interface by collecting fingerprint information under any circumstances.

In one embodiment, the detection result of the fingerprint information by the fingerprint module can also be obtained when the device is in a non-use state. The non-use state here may include one or more of the following states: locked state, dormant state, standby state, etc. In this case, the mobile phone can collect fingerprint information in certain specific states, and only in these specific states will it quickly start the specific friend chat interface in the relevant application by collecting fingerprint information. For the description of the "non-use state", please refer to the previous embodiment, and the description will not be repeated in this embodiment. The application of this application scheme can enable users to omit the steps of waking up the device, unlocking the device, etc. in these cases and directly display the specific friend chat interface. It can also reduce the activation time of the fingerprint detection result acquisition function to reduce the power consumption of the device.

In one embodiment, the fingerprint module can be configured to detect fingerprint information only when not in use, thereby avoiding power consumption caused by the fingerprint module being turned on for a long time. For example, when the phone is locked and the screen is black, the fingerprint module detection function can be disabled, and the fingerprint module can be activated to detect fingerprints after the phone is awakened.

In one embodiment, based on the typical "wake up first, then unlock" operation sequence of typical smart devices, the timing for obtaining detection results from the fingerprint module can be set to "after the user device is awakened from sleep mode and before it is unlocked." This can reduce the time it takes to obtain fingerprint detection results, thereby reducing device power consumption.

In one embodiment, the fingerprint module can also be set to detect fingerprint information only when "the user device is awakened from sleep mode and is not unlocked". For example, when the mobile phone is in a locked and black screen state, the detection function of the fingerprint module can be turned off, and the fingerprint module can be started after the mobile phone is awakened to perform fingerprint detection, thereby further reducing the power consumption caused by the fingerprint module.

That is to say, when the phone is not in use most of the time (for example, when it is in a pocket or bag), the fingerprint detection result acquisition function or the fingerprint module detection function can be disabled. When the phone is awakened by other means (such as the power button, volume button, etc.), the corresponding function is activated. Depending on the fingerprint detection results, the following situations may occur:

1) The user enters the fingerprint information and quickly displays the chat interface of a specific friend. In order to facilitate the user's subsequent chat operations, the phone can be further unlocked.

2) The user unlocks the phone normally (via a password, gesture, etc.). After successful unlocking, the phone enters the use state and the fingerprint module detection function is turned off.

3) The user did not enter any information, which may be caused by an incorrect operation. After a period of time, the phone returns to sleep mode and the fingerprint module detection function is turned off.

It can be seen that by applying the solution of this application, the activation time of the fingerprint module can be further shortened while adapting to the basic operating habits of the user, thereby reducing the power consumption of the device.

In this application, there are no specific restrictions on the operating mode of the fingerprint module, such as whether the fingerprint detection module is always in a state of detecting fingerprints after the user device is turned on, whether the fingerprint detection module is in a state of detecting fingerprints within a set time, whether the fingerprint detection module uses an interrupt method to report fingerprints, or whether the processor in the mobile phone actively calls the fingerprint module to operate, etc. The specific operating mode of the fingerprint module can be controlled or set according to specific needs.

Figure 4 is a schematic diagram of a specific implementation scenario of applying the present application solution to a specific function call in an instant messaging application. When the mobile phone is in a dormant and locked non-use state, the user places his finger on the fingerprint collector on the back of the mobile phone. The fingerprint module collects the fingerprint information and authenticates the fingerprint information. After the authentication is passed, the chat interface image of a specific friend in the instant messaging application is triggered to be displayed on the mobile phone screen, and the user can directly start chatting with the specific friend (Xiaomei).

In one embodiment, the device can also be unlocked using fingerprint information. In this case, the "unlock using fingerprint" function and the "quickly display a specific friend chat interface using fingerprint" function can be distinguished as follows:

The user can pre-enter the authentication fingerprint information for displaying a specific friend chat interface (hereinafter referred to as "display fingerprint") and the authentication fingerprint information for unlocking the user device (hereinafter referred to as "unlock fingerprint"), and establish an association between the "display fingerprint" and the "call a specific friend chat interface display interface in a specific instant application" operation, and establish an association between the "unlock fingerprint" and the "unlock user device" operation. Furthermore, when the user device is locked, after the fingerprint module detects the fingerprint information input by the user, it performs different processing based on the matching between the currently detected fingerprint information and the pre-stored fingerprint information. The specific processing methods are as follows:

When the user device is locked, the fingerprint module detects the fingerprint information;

If no fingerprint information is detected, no action is performed. If fingerprint information is detected:

If the detected fingerprint information matches the "display fingerprint", a chat function with a specific friend in a specific friend chat interface application is called to display the specific friend chat interface on the screen of the user device.

If the detected fingerprint information matches the "unlock fingerprint", the user device unlocking operation is performed.

For example, based on usage habits, users can register the fingerprint of their right index finger as the "unlock fingerprint" and the fingerprint of their right middle finger as the "display fingerprint." In actual use, the user takes out their phone, wakes it up, and the phone screen displays an unlock prompt. If the user needs to quickly display a specific friend chat interface, they place their middle finger on the fingerprint collector. After a successful match, the app is called and the specific friend chat interface is displayed. If the user needs to use other phone functions, they place their index finger on the fingerprint collector. After a successful match, the phone is unlocked by default. This method effectively distinguishes between "quick display" and "fingerprint unlock" without affecting the user's normal usage habits.

In one embodiment, the same fingerprint can also be used to implement the function of using fingerprint to unlock and the function of using fingerprint to quickly display a specific friend chat interface. That is, the same fingerprint information of the user can be entered as the fingerprint for unlocking and the fingerprint for quickly displaying a specific friend chat interface. The fingerprint collection time can be set to distinguish whether the collected fingerprint is used for unlocking or for quickly displaying a specific friend chat interface. For example, the fingerprint detection module collects the user's fingerprint information and records the time the user's fingerprint stays on the fingerprint sensor. If the time is less than 1 second, it is considered to be the unlocking fingerprint and the device is unlocked. If the time is more than 1 second, it is considered to be the fingerprint for quickly displaying a specific friend chat interface (such as a specific friend chat interface page in an instant messaging application), and the specific friend chat interface is quickly called. Of course, in some other scenarios, there can be different implementation methods to achieve the same fingerprint to unlock or quickly display a specific friend chat interface. For example, the fingerprint sensor can be integrated with the pressure sensor to distinguish whether to unlock or quickly display a specific friend chat interface by detecting the pressure condition during fingerprint collection, etc.

It is understandable that, in one embodiment, different fingerprints or different operating methods of the same fingerprint (such as different dwell time of the finger on the fingerprint collector, different pressure, etc.) can also be used to distinguish different friends, so as to quickly display the chat interface of different specific friends.

In one embodiment, fingerprint information detection can also be combined with other methods to implement the call of a specific friend chat interface in a specific application. For example, the user can pre-specify one or more buttons as the trigger password when the specific friend chat interface is displayed. The button can be a physical button or a touch-sensitive virtual button on the mobile phone, or a virtual button in the touch-screen operating system interface or a specific application interface. When the user needs to quickly display a specific friend chat interface, in addition to entering the fingerprint information, he also needs to press a custom button at the same time. For the device side, in addition to obtaining the fingerprint module's detection result of the fingerprint information, it is also necessary to determine whether the predefined button is pressed. Only when the two conditions of "fingerprint information is detected" and "predefined button is pressed" are met at the same time, will the subsequent specific friend chat interface display operation be triggered.

For example, based on usage habits, users can designate the "Volume Down" button as a predefined button. In actual use, the user takes out the phone, places a finger (such as the right index finger) on the fingerprint sensor, and simultaneously presses the "Volume Down" button with another finger (such as the right thumb). When the phone detects that both conditions are met, it calls the instant messaging app to display the chat interface for a specific friend.

In some embodiments, fingerprint information can also be used as a trigger to quickly display a specific friend chat interface, without the need to actually authenticate the detected fingerprint information. In other words, any fingerprint information can trigger the quick display of a specific friend chat interface. For example, when using the above-mentioned predefined button to display a specific friend chat interface in a specific application, since the "predefined button" is also the user's personal private information (predefined by the user), this method can be used to launch the specific friend chat interface without comparing the currently detected fingerprint information with the authenticated fingerprint information, thus ensuring the security of the chat and not affecting the fingerprint matching unlocking mechanism. Of course, in some other scenarios, a specific function interface of a specific application can be called after fingerprint information is detected, without performing a fingerprint matching and authentication process. For example, when a mobile device is in operation, if fingerprint information is detected, that is, when the user places the fingerprint on the fingerprint collector, the specific friend chat interface in the instant messaging application can be called.

It is understandable that the quick call to the specific friend chat interface in the embodiment of the present application is only used to illustrate the "quick call of the function in the application". It should not be understood as a limitation on the specific implementation plan and application scenario of the present application. In addition, different fingerprints, or different operation modes of the same fingerprint (such as different dwell time and pressure of the finger on the fingerprint collector), in addition to being associated with different functions in the same application, can also be associated with functions in multiple different applications, thereby realizing quick call to multiple different application functions.

According to a specific embodiment of the present application, quick call of application functions can be implemented based on the buttons, touch input modules, etc. configured on the user device. The touch input module here can include an independent touch input module such as a touch screen or a touchpad. Accordingly:

S101 is specifically implemented as follows: obtaining an operation on the user device, where the operation may be a pressing operation on a device button, or a touch gesture inputted by the touch input module.

S102 is specifically implemented as follows: when the acquired operation matches an operation of pressing a predefined key or a predefined touch gesture, calling a function in the application associated with the predefined user operation.

Media playback is a frequently used application feature. Currently, the typical process for controlling media playback is as follows: Take out your phone → Wake it up → Unlock it → Find the media playback app → Run the app → Click the Play/Pause/Switch button to control the media playback. This means that in practice, each media playback control requires multiple steps.

This embodiment will take the instant media playback control application scenario as an example to explain the present application scheme in detail. That is, in a media playback application, the present application scheme can be used to quickly control media playback.

In actual applications, an association between an operation mode and a specific playback control function (such as play, pause, stop, switch to the previous media file, switch to the next media file, etc.) in a media playback application can be pre-established, so that after detecting a predefined user operation, the function can be directly triggered instead of calling the main interface of the application. Specifically, relevant settings can be made in the system of the mobile terminal to establish an association relationship between fingerprint information and the specific playback control function called, or, it can also be set in the application installed in the system whether the specific playback control function supports the quick call function, and if it is set to yes, it is associated with the predefined user operation. For example, in the settings interface of the media playback application, the specific playback control function is set to be able to be quickly called through a predefined user operation, and can be associated with a specific predefined user operation, or it can be set by default in the system, and the user can be allowed to set the association predefined user operation. In this application, the specific playback control function can include multiple types, and can be distinguished by associating different predefined user operations.

Mobile phone users can pre-set one or more operation methods as trigger commands when calling specific playback control functions. These operations can be implemented using physical buttons on the phone (such as the power button, volume up button, volume down button, etc., the Home button on iOS phones, and any button on keyboard phones) or touch-sensitive virtual buttons (such as the Home button, Back button, and Menu button on Android phones). They can also be implemented using virtual buttons in the operating system interface or specific application interface of touch-screen phones, or specific touch gestures. The following are some examples of customized user operations:

Clicking a button: On some mobile phones or operating systems, one or more buttons without pre-set functions are provided, and users can define their own functions for these buttons, such as taking a screenshot, muting the sound, launching a specific application, etc. Such buttons can be directly used to implement the customized user operations of the present application solution;

Long press a button: including the physical buttons on the mobile phone, touch-sensitive virtual buttons, or virtual buttons in the mobile phone interface. The standard of "long press" is based on the configuration parameters of the operating system and is not limited in this application.

Press two or more buttons simultaneously: This can be a combination of buttons of the same type, such as pressing the power button and volume down button (both physical buttons) at the same time; or a combination of buttons of different types, such as pressing the power button (physical button) and the back button (touch-sensitive virtual button) at the same time.

Press two or more keys in a certain order: this can be a combination of keys of the same type, such as a password sequence, or a combination of keys of different types, such as . In addition, the input can be limited to be completed within a certain time.

Specific touch gestures: By combining multiple touch gestures, such as click/long press/swipe, single finger/multi-finger gestures, and specific screen positions, you can create a variety of touch gestures. These gestures include double-clicking the screen, swiping from the bottom to the top, and a three-finger long press anywhere on the screen. These gestures can all be used as custom user actions. Furthermore, you can also use specific swipe paths as custom user actions, such as swiping a "Z" or "V" on the screen. Touch gestures can be implemented on a touchscreen or on a separate touch device such as a touchpad.

Regarding customized user operations, there are many other implementation methods, which are not listed one by one in this application. In actual application, as long as the customized user operation does not conflict with other operations, it can be used. After the user enters the customized operation, the mobile phone side records and stores the key information. Of course, in some scenarios, some operations that are the default of the device system can also be used as the user's predefined operations. This application does not specifically limit the setting method of the user's predefined operations, such as whether it is system default or set by the user, such as set by the user in the system, or set by the user in a specific application in the system.

In one embodiment, to ensure that users can quickly trigger specific playback control functions at any time using predefined operations, the function of detecting user input behavior can be set to be in a continuously enabled state. This allows users to quickly trigger specific playback control functions by inputting predefined operation information in any situation.

In one embodiment, user input can also be detected when the device is not in use; this non-use state may include one or more of the following: locked, dormant, and standby. For a description of "non-use state," please refer to the previous embodiment and will not be repeated in this embodiment. Applying this solution allows users to directly access specific playback control functions in these situations without having to wake up or unlock the device, while also avoiding the power consumption caused by the long-term activation of the input detection function.

In one embodiment of the present application, based on the "wake up first, then unlock" operation sequence of general smart devices, the timing for detecting user input behavior can also be set to the period "after the user device is awakened from sleep mode and not unlocked." In other words, the input behavior detection function can be disabled during most of the time when the phone is not in use (for example, when it is in a pocket or bag). When the phone is awakened by other means (such as the power button, volume button, etc.), the input detection function is activated, and the following situations may occur:

1) The user inputs a predefined user operation to call a specific playback control function in the media playback application. In addition to calling the function, the phone can be unlocked or locked at the same time, which is not limited in this application.

2) The user unlocks the phone normally (via a password, gesture, etc.). After successful unlocking, the phone enters the use state and the input behavior detection function is disabled.

3) The user did not enter any information, which may be caused by an incorrect operation. After a period of time, the phone returns to sleep mode and the input behavior detection function is turned off.

It can be seen that by applying the above solution, the activation time of the input behavior detection function can be further shortened while adapting to the user's basic operating habits, thereby reducing the power consumption of the device.

Figure 5 is a schematic diagram of a specific implementation scenario in which the solution of the present application is applied to a media playback scenario. When the mobile phone is in a dormant and locked non-use state, the user draws a "Z"-shaped pattern on the mobile phone screen using gestures. The mobile phone side matches and authenticates the pattern with a pre-stored custom operation gesture. After the authentication is passed, the "play" function in the media playback application is triggered.

To improve the security of certain application functions (such as payment QR code display), other security verification mechanisms can be further added. For example, after detecting a predefined user operation input and before calling a specific function, the user can be required to enter one or more authentication information. The authentication information can be in the form of a text password, fingerprint, gesture, etc. If the authentication information entered by the user is correct, the specific function is called. If the authentication information entered by the user is incorrect, the above-mentioned specific function is not called.

In one embodiment, the device can also be unlocked using a predefined user operation. In order to distinguish between the "unlock using a predefined user operation" function and the "quickly invoke a specific playback control function using a predefined user operation" function, this application provides the following solution:

The user can pre-enter a predefined user operation for invoking a specific playback control function (hereinafter referred to as the "call operation") and a predefined user operation for unlocking the user device (hereinafter referred to as the "unlock operation"). Furthermore, an association is established between the "call operation" and the "calling a specific playback control function in the media playback application," and an association is established between the "unlock operation" and the "unlock user device process." Furthermore, when the user device is locked, after the input behavior detection function detects the user's current input operation, different processing is performed based on the match between the currently detected operation and the pre-stored predefined user operation. The specific processing methods are as follows:

Detect user input behavior when the user device is locked;

If no user operation is detected, no processing is performed. In the case of a user operation being detected:

If the currently detected user operation matches the "call operation", a specific playback control function in a specific application is called.

If the currently detected user operation matches the "unlock operation", the user device is unlocked.

For example, if a phone uses a graphic unlock method, based on user habits, the user can record the gesture drawing graphic "N" as the "unlock operation" and the gesture drawing graphic "Z" as the "call operation." In actual use, the user takes out the phone, performs the wake-up operation, and the phone screen displays the unlock prompt. At this time, if the user needs to quickly access a specific playback control function, they can draw the graphic "Z" on the screen. After a successful match, the specific playback control function in the media playback application is called. If the user needs to use other functions of the phone, they can draw the graphic "N" on the screen. After a successful match, the phone is unlocked according to the default method.

In one embodiment, assuming a phone is unlocked using a numeric password, based on user habits, the user can enter the password "1111" as the "unlock operation" and the password "2222" as the "call operation." In actual use, the user takes out the phone and performs the wake-up operation. The phone screen will display the unlock prompt. At this time, if the user needs to quickly access a specific playback control function, they can enter the password "2222". After a successful match, the specific playback control function in the media playback application will be called. If the user needs to use other functions of the phone, they can enter the password "1111". After a successful match, the phone will be unlocked in the default manner.

It can be seen that by using the above method, the two operations of "quick call" and "unlock" can be effectively distinguished without affecting the user's normal usage habits.

It is understandable that, in one embodiment, different predefined operations (such as different gestures, different passwords, etc.) can also be used to distinguish different playback control functions. For example, "swipe left" is associated with the "switch to the previous media file" function, "swipe right" is associated with the "switch to the next media file" function, "swipe up" is associated with the "pause" function, and "swipe down" is associated with the "stop" function, thereby realizing quick call of different playback control functions.

It is understood that the quick call to a specific playback control function in the embodiments of this application is only used to illustrate the "quick call to a function in an application". It should not be understood as a limitation on the specific implementation scheme and application scenarios of this application. In addition, different buttons, operation gestures, etc., in addition to being associated with different functions in the same application, can also be associated with functions in multiple different applications, thereby realizing quick calls to functions in multiple different applications.

Corresponding to the above method embodiment, the present application also provides a device for calling a function in an application, as shown in FIG6 , which may include:

A detection control module 110 is used to obtain user operations on the user device;

The calling control module 120 is configured to call a function in an application associated with a predefined user operation when the acquired operation matches the predefined user operation.

In a specific embodiment of the present application, a sensing module is configured on the user equipment;

The detection control module 110 may be specifically configured to: obtain the detection result of the sensing module on the user operation;

The calling control module 120 may be specifically configured to: after detecting a predefined user operation input, call a function in an application associated with the predefined user operation.

In a specific embodiment of the present application, the detection control module 110 can be specifically used to: obtain the detection results of the sensing module on the user operation when the user device is in a non-use state; the non-use state may include: a locked state, a sleep state, and/or a standby state.

In a specific embodiment of the present application, the detection control module 110 may be specifically configured to obtain a detection result of a user operation by the sensing module after the user device is awakened from a dormant state and is not unlocked.

In a specific embodiment of the present application, the detection control module 110 may be specifically configured to obtain a detection result of a user operation by the sensing module when a predefined key is pressed.

In a specific embodiment of the present application, the call control module 120 can be specifically used to: after detecting a predefined user operation input, further determine whether the user has entered correct authentication information, and if so, call a function in the application associated with the predefined user operation.

In a specific embodiment of the present application, the sensing module is an acceleration sensor; the predefined user operation is: shaking the user device; the number and amplitude of the shaking operation are not less than a preset threshold.

In a specific embodiment of the present application, the sensing module is a gyroscope; the predefined user operation is: a shaking operation on the user device; the number and amplitude of the shaking operation are not less than a preset threshold value.

In a specific embodiment of the present application, a button is configured on the user device;

The detection control module 110 may be specifically configured to: obtain a user's pressing operation on a button of a user device;

The predefined user operation may specifically include: an operation of pressing a predefined button.

In a specific embodiment of the present application, a touch input module is configured on the user device;

The detection control module 110 may be specifically configured to: obtain a touch gesture input by a user in the touch input module;

The predefined user operation may specifically include: an operation of inputting a predefined touch gesture.

In a specific embodiment of the present application, a fingerprint module is configured on the user device.

The detection control module 110 can be specifically used to: obtain the fingerprint input by the user on the fingerprint module,

The predefined user operation may specifically include: inputting preset fingerprint information.

In a specific implementation of the present application, the call control module 120 may be specifically used to:

The information image display function interface in the application where the information image is located is called to display the information image on the screen of the user device.

The present application also provides a barcode payment device, which is applied to a user device having an induction module. As shown in FIG7 , the device may include:

A detection control module 210 is used to obtain user operations on the user device;

The payment barcode display control module 220 is configured to call the payment barcode display interface in the payment application to display a barcode image for payment on the screen of the user device when the acquired operation matches a predefined user operation.

In a specific embodiment of the present application, a sensing module is configured on the user equipment;

The detection control module 210 may be specifically used to: obtain the detection result of the sensing module on the user operation;

The payment barcode display control module 220 may be specifically configured to: after detecting a predefined user operation input, call the payment barcode display interface in the payment application to display a barcode image for payment on the screen of the user device.

It can be understood that the barcode payment device can be an implementation of the function calling device in the aforementioned application in a specific application environment. Therefore, the specific implementation principle of the function calling device and method embodiments in the aforementioned application will not be repeated in this embodiment.

In addition, the implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.

The function-calling device or barcode payment device provided in the above application can be applied to devices such as mobile phones, tablet computers, and smart watches. FIG7 shows a schematic diagram of the hardware structure of a device provided in the present application for configuring the above device. The device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input/output interface 1030, and the communication interface 1040 are connected to each other within the device via the bus 1050.

The processor 1010 can be implemented using a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in this application.

The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage devices, dynamic storage devices, etc. The memory 1020 can store an operating system and other application programs. When the technical solution provided in this application is implemented through software or firmware, the relevant program code is stored in the memory 1020 and is called and executed by the processor 1010.

The input/output interface 1030 is used to connect input/output modules to implement information input and output. The input/output modules can be configured as components within the device (not shown in the figure) or can be externally connected to the device to provide corresponding functions. Input devices may include a keyboard, mouse, touch screen, microphone, various sensors, etc., and output devices may include a display, speaker, vibrator, indicator light, etc.

The communication interface 1040 is used to connect to a communication module (not shown) to enable communication between the device and other devices. The communication module can communicate via a wired method (such as USB, network cable, etc.) or a wireless method (such as mobile network, WiFi, Bluetooth, etc.).

The bus 1050 comprises a path for transmitting information between the various components of the device (eg, the processor 1010 , the memory 1020 , the input/output interface 1030 , and the communication interface 1040 ).

It should be noted that although the above device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040, and the bus 1050, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will understand that the above device may only include the components necessary to implement the solution of the present application, and does not necessarily include all the components shown in the figure.

Through the description of the above embodiments, it can be seen that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which can be stored in a storage medium such as ROM/RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present application or certain parts of the embodiments.

Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The device embodiment described above is merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the functions of each module can be implemented in the same one or more software and/or hardware when implementing the scheme of this application. It is also possible to select some or all of the modules according to actual needs to achieve the purpose of the scheme of this embodiment. A person of ordinary skill in the art can understand and implement it without paying any creative work.

The above is only a specific implementation method of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims (12)

1. A method for invoking a function in an application, applied to a user equipment, characterized in that the user equipment is equipped with at least one sensing module, the at least one sensing module including at least one of a gravity sensor, an acceleration sensor, a gyroscope, and a distance sensor, the method comprising: When the user device is woken from sleep mode but not unlocked, the detection function of at least one sensing module is activated to detect user operations; after the device is successfully unlocked or returns to sleep mode, the detection function of at least one sensing module is deactivated. When a predefined button is pressed, the detection result of the user operation by the at least one sensing module is obtained; Upon detecting a predefined user action input, a function in the application associated with the predefined user action is invoked. 2. The method according to claim 1, characterized in that, after detecting a predefined user operation input, invoking a function in the application associated with the predefined user operation includes: After detecting a predefined user operation input, it further determines whether the user has entered the correct authentication information. If so, it invokes the function in the application associated with the predefined user operation. 3. The method according to claim 1, wherein the at least one sensing module is an acceleration sensor; the predefined user operation is a shaking operation on the user equipment; and the number and amplitude of the shaking operation are both not less than preset thresholds. 4. The method according to claim 1, wherein the at least one sensing module is a gyroscope; the predefined user operation is a swinging operation on the user device; and the number and amplitude of the swinging operation are not less than preset thresholds. 5. The method according to claim 1, wherein the invocation of a function in the application associated with the predefined user operation comprises: Invoke the information image display function interface of the application containing the information image to display the information image on the user's device screen. 6. A barcode payment method applied to a user equipment, characterized in that the user equipment is equipped with at least one sensing module, the at least one sensing module including at least one of a gravity sensor, an accelerometer, a gyroscope, and a distance sensor, the method comprising: When the user device is woken from sleep mode but not unlocked, the detection function of at least one sensing module is activated to detect user operations; after the device is successfully unlocked or returns to sleep mode, the detection function of at least one sensing module is deactivated. When a predefined button is pressed, the detection result of the user operation by the at least one sensing module is obtained; Upon detecting a predefined user input, the payment barcode display interface in the payment application is invoked to display a barcode image for payment on the user's device screen. 7. A function invocation device in an application, applied to a user equipment, characterized in that the user equipment is equipped with at least one sensing module, the at least one sensing module including at least one of a gravity sensor, an acceleration sensor, a gyroscope, and a distance sensor, the device comprising: The power-saving module activates the detection function of at least one sensing module to detect user operations when the user device is woken from sleep mode but not unlocked; after the device is successfully unlocked or returns to sleep mode, the detection function of at least one sensing module is turned off. The detection control module is used to acquire the detection results of the user operation by the at least one sensing module when a predefined button is pressed. The call control module is used to invoke functions in the application associated with the predefined user operation after detecting a predefined user operation input. 8. The apparatus according to claim 7, wherein the call control module is specifically used for: After detecting a predefined user operation input, it further determines whether the user has entered the correct authentication information. If so, it invokes the function in the application associated with the predefined user operation. 9. The apparatus according to claim 7, wherein the at least one sensing module is an acceleration sensor; the predefined user operation is a shaking operation on the user equipment; and the number and amplitude of the shaking operation are both not less than preset thresholds. 10. The apparatus according to claim 7, wherein the at least one sensing module is a gyroscope; the predefined user operation is a swinging operation on the user device; and the number and amplitude of the swinging operation are not less than preset thresholds. 11. The apparatus according to claim 7, wherein the call control module is specifically used for: Invoke the information image display function interface of the application containing the information image to display the information image on the user's device screen. 12. A barcode payment device, applied to a user equipment, characterized in that the user equipment is equipped with at least one sensing module, the at least one sensing module including at least one of a gravity sensor, an acceleration sensor, a gyroscope, and a distance sensor, the device comprising: The power-saving module activates the detection function of at least one sensing module to detect user operations when the user device is woken from sleep mode but not unlocked; after the device is successfully unlocked or returns to sleep mode, the detection function of at least one sensing module is turned off. The detection control module acquires the detection results of the user operation by the at least one sensing module when a predefined button is pressed. The payment barcode display control module is used to call the payment barcode display interface in the payment application after detecting a predefined user operation input, so as to display the barcode image used for payment on the screen of the user's device.