HK40048714B - Method and apparatus for triggering identity verification in application program, device and storage medium - Google Patents

Description

Methods, devices, equipment, and storage media that trigger authentication in an application

Technical Field

This application relates to the field of computer technology, and in particular to a method, apparatus, device, and storage medium for triggering authentication in an application.

Background Technology

With the development of internet finance, more and more applications involve users' financial information and security, such as banking applications and mobile applications. Generally, these applications include user authentication functions to enhance the protection of users' assets.

In existing technologies, technicians set different authentication trigger conditions based on the application's business functions, and write code to judge these conditions in the execution code of different business functions. When the application needs to perform certain business functions, such as when a user clicks on account information in the application, the code that judges the authentication trigger conditions will be executed first to verify whether the application's status information meets the authentication trigger conditions. If the authentication trigger conditions are met, the application will use some verification methods to verify whether the person currently operating the application is the user. For example, a lock screen page will pop up, prompting the user to enter a previously set verification password. Only after successful verification can the relevant business functions of the application continue to execute.

In the process of developing this application, the inventors discovered that the prior art has at least the following problems:

Technical staff need to write statements that judge the authentication trigger conditions in the execution code of different business functions. Every time a business function is added to the application, the technical staff have to write the corresponding authentication trigger conditions in the execution code of the business function, which makes the coding process cumbersome and inefficient.

Summary of the Invention

This application provides a method, apparatus, device, and storage medium for triggering authentication in an application, which solves the problem of cumbersome and inefficient process for technicians to write corresponding authentication trigger condition code in the execution code of business functions. The technical solution is as follows:

On the one hand, a method for triggering authentication in an application is provided, the method comprising:

Within the application, monitor the display instructions for each page in the preset set of pages;

When a display instruction for a target page is detected, the target authentication trigger condition corresponding to the target page is determined based on the pre-stored correspondence between the application's pages and authentication trigger conditions.

If the current state information of the application meets the target authentication triggering condition, then user authentication processing is performed.

Optionally, the step of performing user authentication processing if the current state information of the application meets the target authentication triggering condition includes:

When the target page corresponds to multiple target authentication trigger conditions, if the current state information of the application meets all target authentication trigger conditions, then user authentication processing is performed.

Optionally, the method further includes:

Receive an update request, which carries the page to be added and the corresponding authentication conditions to be added;

It is determined that the page to be added is not included in the page set;

The page to be added is added to the page set, and the page to be added and the authentication condition to be added are added to the corresponding relationship.

Optionally, the method further includes:

Receive an update request, which carries the page to be added and the corresponding authentication conditions to be added;

Determine that the page to be added is included in the page set;

In the correspondence, the authentication condition information corresponding to the page to be added is modified to the authentication condition to be added.

Optionally, after performing user authentication processing, the method further includes:

If the user's authentication is successful, the target page is displayed; if the user's authentication is unsuccessful, the target page is refused to be displayed.

On the other hand, an apparatus for triggering authentication in an application is provided, the apparatus comprising:

The monitoring module is configured to monitor the display instructions of each page in a preset set of pages within the application.

The determination module is configured to, when a display instruction for a target page is detected, determine the target authentication trigger condition corresponding to the target page based on a pre-stored correspondence between pages of the application and authentication trigger conditions.

The processing module is configured to perform user authentication processing if the current state information of the application meets the target authentication triggering condition.

Optionally, the processing module is configured as follows:

When the target page corresponds to multiple target authentication trigger conditions, if the current state information of the application meets all target authentication trigger conditions, then user authentication processing is performed.

Optionally, the device further includes a first update module configured to:

Receive an update request, which carries the page to be added and the corresponding authentication conditions to be added;

It is determined that the page to be added is not included in the page set;

The page to be added is added to the page set, and the page to be added and the authentication condition to be added are added to the corresponding relationship.

Optionally, the device further includes a second update module configured to:

Receive an update request, which carries the page to be added and the corresponding authentication conditions to be added;

Determine that the page to be added is included in the page set;

In the correspondence, the authentication condition information corresponding to the page to be added is modified to the authentication condition to be added.

Optionally, the device further includes a display module configured to:

If the user's authentication is successful, the target page is displayed; if the user's authentication is unsuccessful, the target page is refused to be displayed.

In another aspect, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one instruction, the instruction being loaded and executed by the processor to perform the operation performed by the method for triggering authentication in an application as described above.

In another aspect, a computer-readable storage medium is provided, wherein at least one instruction is stored therein, the instruction being loaded and executed by a processor to perform the operations performed by the method for triggering authentication in an application as described above.

The beneficial effects of the technical solutions provided in this application are:

This application embodiment can add pages corresponding to business functions to a page collection and store the pages and their corresponding authentication trigger conditions. By monitoring the pages to be displayed in the page collection, the corresponding authentication trigger conditions are determined. Then, based on whether the application's current state information meets the authentication trigger conditions, it is determined whether to authenticate the user. In practical applications, different business functions may correspond to the same pages and the same authentication trigger conditions. Based on the above correspondence, technicians do not need to repeatedly write authentication trigger condition code in the code of different business functions, simplifying the coding process and improving efficiency.

Attached Figure Description

To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

Figure 1 is a flowchart of a method for triggering authentication in an application according to an embodiment of this application;

Figure 2 is a flowchart of a method for triggering authentication in an application according to an embodiment of this application;

Figure 3 is a schematic diagram of the device structure for triggering authentication in an application provided in an embodiment of this application;

Figure 4 is a schematic diagram of the terminal device structure provided in an embodiment of this application.

Detailed Implementation

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

The authentication method for triggering applications provided in this application can be implemented on a terminal. The terminal can have applications installed, such as banking applications for various banks, mobile payment applications, stock trading applications, etc. The terminal can have components such as a microphone, camera, and screen, and can also have modules that can identify human biometric information, such as fingerprint sensors, facial recognition sensors, and iris recognition sensors. The terminal has communication capabilities, can access the internet, and can be a mobile phone, tablet computer, smart wearable device, desktop computer, laptop computer, etc.

The method for triggering application authentication provided in this embodiment can authenticate the user operating the application during the application's operation, thereby enhancing the security of the application. This embodiment uses a banking application as an example for detailed explanation; other cases are similar and will not be described in detail here. The banking application allows users to log in to accounts created by them, and displays the bank account information corresponding to the logged-in account. Users can view their bank account balance through the banking application and complete online transfers, online payments, online fund trading, and other transactions.

When a user operates a banking application and enters certain business scenarios, such as clicking on account information within a financial application or switching from the background to the current display page, the financial application will pop up an identity verification interface to verify whether the identity of the user operating the banking application matches the identity information of the account currently logged into the financial application. The verification method can be password verification, fingerprint verification, iris verification, or facial verification, etc. The method for triggering identity verification in the application provided in this application embodiment can determine the trigger conditions for user identity verification by monitoring the display of banking business function pages, and then determine whether to perform user identity verification based on the identity verification trigger conditions.

It should be noted that this application may display prompt interfaces, pop-ups, or output voice prompts before and during the collection of user data. These prompt interfaces, pop-ups, or voice prompts are used to inform the user that their data is being collected. This ensures that the application only begins the steps for collecting user data after receiving confirmation from the user regarding the prompt interface or pop-up; otherwise (i.e., without user confirmation), the steps for collecting user data end, meaning no user data is collected. In other words, all user data collected in this application is collected with the user's consent and authorization, and the collection, use, and processing of related user data must comply with the relevant laws, regulations, and standards of the relevant regions.

Figure 1 is a flowchart of a method for triggering authentication in an application according to an embodiment of this application. Referring to Figure 1, this embodiment includes:

Step 101: In the application, monitor the display instructions of each page in the preset page set.

During the process of an application displaying a page, a series of events are triggered, in the following order: creation time, start event, visibility event, pause event, and stop event. Specifically, when the application wants to display a page on the terminal screen, it triggers the visibility event corresponding to the page to be displayed. The visibility event carries a page identifier for the page to be displayed. Visibility events carrying page identifiers can be used as display instructions for the monitored page.

In implementation, a page lifecycle listener can be set up in the application. This listener can monitor a series of events triggered during the page display process, thus detecting page display instructions. When a user clicks on a corresponding business function in the banking application, the application can display the page corresponding to that function on the terminal screen. A page set can be set up in the application based on business functions that may require authentication. This set includes page identifiers for pages corresponding to business functions that may require authentication. For example, page identifiers for pages related to account information and asset security can be added to the page set. The page lifecycle listener can monitor the pages to be displayed in the banking application in real time. When the page identifier carried in a detected visible event matches a page identifier from the page set, it can be determined that the user has selected a business function that may require authentication. For example, the page identifier for the account information page in the banking application can be added to the page set. When the page lifecycle listener detects the page identifier for the account information page, it indicates that the user has selected the account information business function.

Step 102: When a display instruction for the target page is detected, the target authentication trigger condition corresponding to the target page is determined based on the pre-stored correspondence between application pages and authentication trigger conditions.

The correspondence between pages and authentication trigger conditions can be a mapping between the page identifier and the authentication trigger condition. Authentication trigger conditions can be based on the state information of the banking application, such as whether an account is logged in, or whether the time interval between the banking application page appearing in the background is greater than a preset time interval.

In implementation, when the page lifecycle listener detects a page identifier in the page set, it indicates that the user has selected a business function that may require authentication. Before the banking application authenticates the user, it can determine whether the current state information of the banking application meets the conditions for triggering authentication. The conditions for triggering authentication vary depending on the business function. Technical personnel can pre-store the correspondence between page identifiers and authentication trigger conditions for each page in the page set within the application. When the page lifecycle listener detects a page identifier in the page set, it can look up the corresponding authentication trigger condition for the detected page identifier in the pre-stored correspondence. For example, the page identifier for the account information page in the banking application can correspond to an existing account login and the logged-in account being bound to a bank card. When the page lifecycle listener detects a visible event triggered by the account information page, if the current state information of the banking application shows an existing account login and the logged-in account being bound to a bank card, then the banking application can authenticate the user. The above process is illustrated in Figure 2.

Optionally, the mapping between the stored application pages and authentication trigger conditions can be set in an authentication trigger interface. The corresponding processing can be as follows: when a display instruction for the target page is detected, the authentication trigger interface is called, and the target authentication trigger condition corresponding to the target page is determined based on the pre-stored mapping between the application pages and authentication trigger conditions.

In implementation, an authentication trigger interface can be set up in the banking application. The correspondence between the pages of the banking application and the authentication trigger conditions is stored in the same authentication trigger interface. When a page identifier in the page set is detected during the page lifecycle, the authentication trigger interface can be called, and the authentication trigger condition corresponding to the detected page identifier can be determined based on the detected page identifier.

Step 103: If the current state information of the application meets the target application state conditions, then perform user authentication processing.

In implementation, after the page lifecycle listener detects a page identifier in the page collection and determines that the application's current state information matches the authentication trigger condition corresponding to that page identifier, it can then authenticate the user. Authentication can be achieved by displaying a lock screen where the user can enter a previously set verification password. Alternatively, other authentication methods can be used, such as fingerprint verification, iris verification, or facial recognition.

Optionally, when a target page corresponds to multiple target authentication trigger conditions, user authentication processing is performed if the current state information of the application meets all target authentication trigger conditions.

In implementation, after selecting a business function within a banking application, the application's state information may need to satisfy multiple authentication trigger conditions before authenticating the user. That is, the page corresponding to a business function within the banking application can correspond to multiple authentication trigger conditions. When the page lifecycle listener detects a page identifier in the page set, and that page identifier corresponds to multiple authentication trigger conditions, the banking application's state information must satisfy all authentication trigger conditions corresponding to that page identifier before authenticating the user.

Optionally, after performing step 103, the following method can be executed based on the authentication result: if the user authentication is successful, the target page is displayed; if the user authentication is unsuccessful, the target page is refused to be displayed.

In practice, users can authenticate themselves through the banking application by entering a password or similar method. If the user is successfully authenticated, the application will display the corresponding page on the terminal screen, allowing the user to select the appropriate service function. If the user fails authentication, the application may not display the corresponding page on the terminal screen. Additionally, the banking application can manage currently logged-in accounts, such as logging out of the account and sending a notification message to the account's associated mobile phone number.

This application embodiment can add pages corresponding to business functions to a page collection and store the pages and their corresponding authentication trigger conditions. By monitoring the pages to be displayed in the page collection, the corresponding authentication trigger conditions are determined. Then, based on whether the application's current state information meets the authentication trigger conditions, it is determined whether to authenticate the user. In practical applications, different business functions may correspond to the same pages and the same authentication trigger conditions. Based on the above correspondence, technicians do not need to repeatedly write authentication trigger condition code in the code of different business functions, simplifying the coding process and improving efficiency.

In this embodiment of the application, the application can update the correspondence between the application's pages and the authentication triggering conditions in real time. The corresponding processing can be as follows:

Receive an update request, which includes the page to be added and the corresponding authentication condition to be added; determine that the page to be added is not included in the page set; add the page to be added to the page set, and add the page to be added and the authentication condition to be added to the corresponding relationship.

In implementation, when the authentication conditions for business functions in a banking application may need to be changed, or when new authentication conditions may need to be added for new business functions, technical personnel can pre-write update requests. These update requests can carry the page identifier of the page corresponding to the business function and the corresponding authentication trigger conditions. The update request is then sent from the server to the banking application on the terminal. Upon receiving the update request, the terminal can update the original mapping between page identifiers and authentication trigger conditions (i.e., the mapping between page identifiers and authentication trigger conditions before receiving the update request) based on the page identifiers and authentication trigger conditions carried in the update request. If the page identifier carried in the update request is not present in the original page set (i.e., the page set before receiving the update request), the page identifier carried in the update request is added to the original page set, resulting in the updated page set. The mapping between page identifiers and authentication trigger conditions is then updated by adding the page identifier and authentication trigger conditions carried in the update request.

If the original page set includes the page identifier carried in the update request, the corresponding processing can be as follows: determine if the page set includes the page to be added; in the correspondence, modify the authentication condition information corresponding to the page to be added to the authentication condition to be added.

In implementation, if the page identifier carried in the update request exists in the original page set, the authentication triggering condition in the correspondence between the original page identifier and the authentication triggering condition is modified to the authentication triggering condition carried in the update request, thus completing the modification of the authentication triggering condition corresponding to the page identifier.

All of the above-mentioned optional technical solutions can be combined in any way to form optional embodiments of this disclosure, and will not be described in detail here.

This application provides a device for triggering authentication in an application. This device can be the terminal described in the above embodiments. Referring to FIG3, the device includes:

The monitoring module 310 is configured to monitor the display instructions of each page in a preset set of pages in the application.

The determination module 320 is configured to, when a display instruction for a target page is detected, determine the target authentication trigger condition corresponding to the target page based on a pre-stored correspondence between pages of the application and authentication trigger conditions.

The processing module 330 is configured to perform user authentication processing if the current state information of the application meets the target authentication triggering condition.

Optionally, the processing module 330 is configured to:

When the target page corresponds to multiple target authentication trigger conditions, if the current state information of the application meets all target authentication trigger conditions, then user authentication processing is performed.

Optionally, the device further includes a first update module 340, configured to:

Receive an update request, which carries the page to be added and the corresponding authentication conditions to be added;

It is determined that the page to be added is not included in the page set;

The page to be added is added to the page set, and the page to be added and the authentication condition to be added are added to the corresponding relationship.

Optionally, the device further includes a second update module 350, configured to:

Receive an update request, which carries the page to be added and the corresponding authentication conditions to be added;

Determine that the page to be added is included in the page set;

In the correspondence, the authentication condition information corresponding to the page to be added is modified to the authentication condition to be added.

Optionally, the device further includes a display module 360, configured to:

If the user's authentication is successful, the target page is displayed; if the user's authentication is unsuccessful, the target page is refused to be displayed.

It should be noted that the above embodiments of the device for authenticating identity in the application triggering authentication are only illustrative examples of the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the device for authenticating identity in the application triggering authentication provided in the above embodiments and the method embodiments for authenticating identity in the application triggering authentication belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.

Figure 4 shows a structural block diagram of a terminal 400 provided in an exemplary embodiment of this application. The terminal 400 may be a smartphone, tablet computer, MP3 player (Moving Picture Experts Group Audio Layer III), MP4 player (Moving Picture Experts Group Audio Layer IV), laptop computer, or desktop computer. The terminal 400 may also be referred to as a user device, portable terminal, laptop terminal, desktop terminal, or other names.

Typically, terminal 400 includes a processor 401 and a memory 402.

Processor 401 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 401 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 401 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 401 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 401 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

Memory 402 may include one or more computer-readable storage media, which may be non-transitory. Memory 402 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in memory 402 is used to store at least one instruction, which is executed by processor 401 to implement the method for triggering authentication in an application provided in the method embodiments of this application.

In some embodiments, the terminal 400 may also optionally include a peripheral device interface 403 and at least one peripheral device. The processor 401, memory 402, and peripheral device interface 403 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 403 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency circuit 404, a touch display screen 405, a camera 406, an audio circuit 407, a positioning component 408, and a power supply 409.

Peripheral device interface 403 can be used to connect at least one I/O (Input/Output) related peripheral device to processor 401 and memory 402. In some embodiments, processor 401, memory 402 and peripheral device interface 403 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 401, memory 402 and peripheral device interface 403 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

The radio frequency (RF) circuit 404 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 404 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 404 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 404 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 404 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: metropolitan area networks (MANs), various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks (WLANs), and/or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 404 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

Display screen 405 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 405 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 401 for processing. In this case, display screen 405 can also be used to provide virtual buttons and/or a virtual keyboard, also known as soft buttons and/or a soft keyboard. In some embodiments, there may be one display screen 405, which serves as the front panel of terminal 400; in other embodiments, there may be at least two display screens, respectively disposed on different surfaces of terminal 400 or in a folded design; in still other embodiments, display screen 405 may be a flexible display screen, disposed on a curved or folded surface of terminal 400. Furthermore, display screen 405 may be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. Display screen 405 may be made of materials such as LCD (Liquid Crystal Display) or OLED (Organic Light-Emitting Diode).

The camera assembly 406 is used to acquire images or videos. Optionally, the camera assembly 406 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 406 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash is a combination of a warm-light flash and a cool-light flash, which can be used for light compensation at different color temperatures.

The audio circuit 407 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting them into electrical signals that are input to the processor 401 for processing, or to the radio frequency circuit 404 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each positioned at a different location on the terminal 400. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 401 or the radio frequency circuit 404 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 407 may also include a headphone jack.

The positioning component 408 is used to locate the current geographic location of the terminal 400 in order to enable navigation or LBS (Location Based Service). The positioning component 408 can be a positioning component based on the US GPS (Global Positioning System), China's BeiDou system, Russia's Grenas system, or the European Union's Galileo system.

Power supply 409 is used to power the various components in terminal 400. Power supply 409 can be AC power, DC power, a disposable battery, or a rechargeable battery. When power supply 409 includes a rechargeable battery, the rechargeable battery can support wired charging or wireless charging. The rechargeable battery can also be used to support fast charging technology.

In some embodiments, the terminal 400 further includes one or more sensors 410. The one or more sensors 410 include, but are not limited to: an accelerometer 411, a gyroscope 412, a pressure sensor 413, a fingerprint sensor 414, an optical sensor 415, and a proximity sensor 416.

Accelerometer 411 can detect the magnitude of acceleration on the three coordinate axes of a coordinate system established with terminal 400. For example, accelerometer 411 can be used to detect the components of gravitational acceleration on the three coordinate axes. Processor 401 can control touch screen 405 to display the user interface in landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 411. Accelerometer 411 can also be used for games or for acquiring user motion data.

The gyroscope sensor 412 can detect the orientation and rotation angle of the terminal 400. The gyroscope sensor 412, in conjunction with the accelerometer sensor 411, can collect 3D motion data from the user on the terminal 400. Based on the data collected by the gyroscope sensor 412, the processor 401 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

The pressure sensor 413 can be disposed on the side bezel of the terminal 400 and/or on the lower layer of the touch display screen 405. When the pressure sensor 413 is disposed on the side bezel of the terminal 400, it can detect the user's grip signal on the terminal 400, and the processor 401 can perform left/right hand recognition or quick operation based on the grip signal collected by the pressure sensor 413. When the pressure sensor 413 is disposed on the lower layer of the touch display screen 405, the processor 401 can control the operable controls on the UI interface based on the user's pressure operation on the touch display screen 405. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

The fingerprint sensor 414 is used to collect the user's fingerprint. The processor 401 identifies the user's identity based on the fingerprint collected by the fingerprint sensor 414, or the fingerprint sensor 414 identifies the user's identity based on the collected fingerprint. When the user's identity is identified as trusted, the processor 401 authorizes the user to perform relevant sensitive operations, including unlocking the screen, viewing encrypted information, downloading software, making payments, and changing settings. The fingerprint sensor 414 can be located on the front, back, or side of the terminal 400. When the terminal 400 has physical buttons or a manufacturer's logo, the fingerprint sensor 414 can be integrated with the physical buttons or manufacturer's logo.

An optical sensor 415 is used to collect ambient light intensity. In one embodiment, the processor 401 can control the display brightness of the touch screen 405 based on the ambient light intensity collected by the optical sensor 415. Specifically, when the ambient light intensity is high, the display brightness of the touch screen 405 is increased; when the ambient light intensity is low, the display brightness of the touch screen 405 is decreased. In another embodiment, the processor 401 can also dynamically adjust the shooting parameters of the camera assembly 406 based on the ambient light intensity collected by the optical sensor 415.

The proximity sensor 416, also known as a distance sensor, is typically located on the front panel of the terminal 400. The proximity sensor 416 is used to detect the distance between the user and the front of the terminal 400. In one embodiment, when the proximity sensor 416 detects that the distance between the user and the front of the terminal 400 is gradually decreasing, the processor 401 controls the touchscreen display 405 to switch from a screen-on state to a screen-off state; when the proximity sensor 416 detects that the distance between the user and the front of the terminal 400 is gradually increasing, the processor 401 controls the touchscreen display 405 to switch from a screen-off state to a screen-on state.

Those skilled in the art will understand that the structure shown in FIG4 does not constitute a limitation on terminal 400, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

In an exemplary embodiment, a computer-readable storage medium is also provided, such as a memory including instructions executable by a processor in a terminal to complete the method for triggering authentication in an application. The computer-readable storage medium may be non-transitory. For example, the computer-readable storage medium may be ROM (Read-Only Memory), RAM (Random Access Memory), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

The above description is only a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims (7)

1. A method for triggering authentication in an application, characterized in that the method comprises: In the application, set the authentication trigger interface; The authentication triggering interface stores the correspondence between the application's pages and authentication triggering conditions; In the application, the display instructions of each page in the preset page set are monitored. The page set is a collection of page settings corresponding to business functions that require authentication. Different business functions may correspond to the same page. When a display instruction for a target page is detected, the authentication trigger interface is invoked, and the target authentication trigger condition corresponding to the target page is determined based on the correspondence stored in the authentication trigger interface. When the target page corresponds to multiple target authentication trigger conditions, if the current state information of the application satisfies all target authentication trigger conditions, then user authentication processing is performed. Receive an update request, which carries the page to be added and the corresponding authentication conditions to be added; It is determined that the page to be added is not included in the page set; The page to be added is added to the page set, and the page to be added and the authentication trigger condition to be added are added to the corresponding relationship. 2. The method according to claim 1, characterized in that the method further comprises: Receive an update request, which carries the page to be added and the corresponding authentication conditions to be added; Determine that the page to be added is included in the page set; In the correspondence, the authentication trigger condition corresponding to the page to be added is modified to the authentication trigger condition to be added. 3. The method according to claim 1, characterized in that, after the user authentication process, the method further includes: If the user's authentication is successful, the target page is displayed; if the user's authentication is unsuccessful, the target page is refused to be displayed. 4. A device for triggering authentication in an application, characterized in that the device comprises: The module is configured to set up an authentication trigger interface in the application; The determining module is configured to store the correspondence between the application's pages and the authentication triggering conditions in the authentication triggering interface; The monitoring module is configured to monitor the display instructions of each page in a preset page set in the application. The page set is a collection of page settings corresponding to business functions that require authentication; wherein different business functions may correspond to the same page. The determination module is configured to call the authentication trigger interface when a display instruction for the target page is detected, and determine the target authentication trigger condition corresponding to the target page based on the correspondence stored in the authentication trigger interface; The processing module is configured to perform user authentication processing if the current state information of the application satisfies all target authentication trigger conditions when the target page corresponds to multiple target authentication trigger conditions. The first update module is configured to receive update requests, which carry the page to be added and the corresponding authentication trigger conditions to be added. The first update module is configured to determine that the page to be added is not included in the page set; The first update module is configured to add the page to be added to the page set, and add the page to be added and the authentication condition to be added to the corresponding relationship. 5. The apparatus according to claim 4, wherein the apparatus further comprises a second update module configured to: Receive an update request, which carries the page to be added and the corresponding authentication conditions to be added; Determine that the page to be added is included in the page set; In the correspondence, the authentication trigger condition corresponding to the page to be added is modified to the authentication trigger condition to be added. 6. A computer device, characterized in that the computer device includes a processor and a memory, the memory storing at least one instruction, the instruction being loaded and executed by the processor to perform the operation performed by the method for triggering authentication in an application as described in any one of claims 1 to 3. 7. A computer-readable storage medium, characterized in that the storage medium stores at least one instruction, which is loaded and executed by a processor to perform the operation performed by the method for triggering authentication in an application as described in any one of claims 1 to 3.