Application calling methods, devices, terminal equipment and media

Abstract

This application, applicable to the field of terminal technology, provides a method, apparatus, terminal device, and medium for invoking an application. The method includes: the terminal device parsing the installation package of an application to be installed, wherein the installation package contains a declaration tag for a target function; wherein the target function includes the function of invoking the application while the terminal device is locked; the terminal device configuring the target function of the application according to the declaration tag; and if the terminal device receives an instruction to invoke the application while locked, the terminal device invoking the application according to the instruction. This method reduces the development cost and difficulty of implementing direct access to application services while locked.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a method, apparatus, terminal device, and medium for invoking an application. Background Technology

[0002] With the development of mobile applications, new atomic services are gradually becoming one of the key points in building a new mobile application ecosystem. Direct service access, as an important application feature of new atomic services, is particularly important in some quick service scenarios (such as QR code payment, QR code bike riding, route query, photo and video recording, etc.).

[0003] Service access, based on quick entry points, allows users to directly launch certain applications with only a few steps. These quick entry points can include the lock screen, the device's negative one screen, and application platforms. In fact, the lock screen, the device's negative one screen, and application platforms are all types of mobile applications; they only differ in their presentation and location. However, service access based on different entry points can provide different user experiences. From an overall experience perspective, the user experience of the lock screen entry point is generally superior to that of the device's negative one screen and application platforms.

[0004] In existing technologies, direct access to services based on the lock screen interface often requires developers to develop specific lock screen applications or pre-establish a mapping relationship between lock screen interface verification methods and specific applications, which is difficult and costly to develop. Summary of the Invention

[0005] This application provides an application invocation method, apparatus, terminal device, and medium to reduce the development cost and difficulty of implementing direct access to application services in a locked screen state.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] Firstly, a method for invoking an application is provided, including:

[0008] The terminal device parses the installation package of the application to be installed, wherein the installation package is configured with a declaration tag for the target function; wherein, the target function includes the function of calling the application when the terminal device is locked.

[0009] The terminal device configures the target function of the application according to the declaration tag;

[0010] If the terminal device receives an instruction to invoke the application while in the locked screen state, the terminal device invokes the application according to the instruction.

[0011] In one possible implementation of the first aspect, the declaration tags configured in the installation package may include a function declaration sub-tag and an authentication type sub-tag for declaring the target function, wherein the function declaration sub-tag is used to declare that the application supports the target function, and the authentication type sub-tag can be used to characterize at least one authentication method supported by the target function.

[0012] In one possible implementation of the first aspect, when configuring the target function of an application according to the declaration tag, the terminal device may first determine at least one authentication method supported by the target function according to the authentication type sub-tag in the declaration tag; and bind the application to the determined at least one authentication method according to the function declaration sub-tag in the declaration tag; then, the terminal device configures the target function of the application bound to the above-mentioned at least one authentication method to complete the registration of the target function of the application in the terminal device.

[0013] In one possible implementation of the first aspect, the at least one authentication method supported by the target function may include at least one of fingerprint verification, gesture password verification, and digital password verification.

[0014] In one possible implementation of the first aspect, after the terminal device configures the target function of the application according to the declaration label, the terminal device can also display information on at least one authentication method supported by the target function to the user for the user to select; after the terminal device determines the authentication method selected by the user from the above at least one authentication method, the terminal device can prompt the user to enter authentication information corresponding to the selected authentication method; the terminal device can bind the application, the authentication method selected by the user, and the authentication information entered by the user according to the received authentication information.

[0015] In one possible implementation of the first aspect, when the terminal device calls the application according to the instruction, it can first determine whether the received instruction is triggered by an authentication method corresponding to the target function; if the instruction is triggered by an authentication method corresponding to the target function, the terminal device can verify the authentication information contained in the instruction; when the authentication information is verified, the terminal device can directly call the corresponding application without unlocking the screen based on the verified authentication information.

[0016] In one possible implementation of the first aspect, when the terminal device invokes an application based on authentication information, it needs to determine the application bound to the authentication information; then, the terminal device invokes the application and displays the application on the terminal device's main interface.

[0017] Secondly, an application invocation device is provided, comprising:

[0018] The parsing module is used to parse the installation package of the application to be installed, wherein the installation package is configured with a declaration tag of the target function; wherein, the target function includes the function of calling the application when the terminal device is locked.

[0019] A configuration module is used to configure the target functionality of the application based on the declaration tags;

[0020] The calling module is configured to call the application according to the instruction if it receives an instruction to call the application in the locked screen state of the terminal device.

[0021] In one possible implementation of the second aspect, the declaration tags configured in the installation package may include a function declaration sub-tag and an authentication type sub-tag for declaring the target function, wherein the function declaration sub-tag is used to declare that the application supports the target function, and the authentication type sub-tag can be used to characterize at least one authentication method supported by the target function.

[0022] In one possible implementation of the second aspect, the configuration module may include the following sub-modules:

[0023] The authentication method determination submodule is used to determine, based on the authentication type sub-label, at least one authentication method supported by the target function;

[0024] The authentication method binding submodule is used to bind the application to the at least one authentication method according to the function declaration sub-tag;

[0025] The target function configuration submodule is used to configure the target function of the application that is bound to the at least one authentication method.

[0026] In one possible implementation of the second aspect, the at least one authentication method supported by the target function may include at least one of fingerprint verification, gesture password verification, and digital password verification.

[0027] In one possible implementation of the second aspect, the device may further include the following modules:

[0028] The display module is used to display information about the at least one authentication method supported by the target function;

[0029] A determining module is used to determine the authentication method selected by the user from the at least one authentication method;

[0030] The binding module is used to receive the authentication information input by the user corresponding to the selected authentication method, and to bind the application, the selected authentication method, and the authentication information.

[0031] In one possible implementation of the second aspect, the calling module may include the following sub-modules:

[0032] The instruction judgment submodule is used to determine whether the instruction is triggered by an authentication method corresponding to the target function;

[0033] An authentication submodule is used to verify the authentication information contained in the instruction if the instruction is triggered by an authentication method corresponding to the target function.

[0034] The application calling submodule is used to call the application based on the authentication information when the authentication information is verified.

[0035] In one possible implementation of the second aspect, the application calling submodule may include the following units:

[0036] An application determination unit is used to determine the application bound to the authentication information;

[0037] The application invocation and display unit is used to invoke the application bound to the authentication information and display the application on the main interface of the terminal device.

[0038] Thirdly, a terminal device is provided, which may be any of the terminal devices in the first aspect, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the application invocation method in any of the first aspects is implemented.

[0039] Fourthly, a computer storage medium is provided, which stores computer instructions that, when executed on a terminal device, cause the terminal device to execute the application invocation method described in any of the first aspects.

[0040] Fifthly, a computer program product is provided that, when the computer program product is run on a computer, causes the computer to execute the application invocation method of any of the first aspects above.

[0041] Sixthly, a chip is provided, comprising a processor, which can be a general-purpose processor or a special-purpose processor. The processor is used to support a terminal device in executing the application invocation method described in any of the first aspects above.

[0042] Compared with the prior art, the application invocation method, apparatus, terminal device, and medium provided in this application embodiment have the following advantages:

[0043] By parsing the installation package of the application to be installed, the terminal device can confirm whether the installation package contains a declaration tag for the target function. If the terminal device confirms that the installation package contains a declaration tag for the target function, it indicates that the application has the function to be invoked in the lock screen state. Therefore, the terminal device can configure the target function of the application according to the above declaration tag, and complete the registration of the target function on the terminal device. When the terminal device receives an instruction to invoke an application in the lock screen state, the terminal device can invoke the application according to the instruction. Through the method provided by the embodiments of this application, developers do not need to develop a lock screen application separately for the terminal device to realize the service access function of the application, reducing development costs and development difficulty; secondly, by pre-configuring the declaration tag supporting service access in the application installation package, this method allows users to choose whether to enable the service access function of each application, solving the problem in the prior art that it does not support users to customize which applications provide direct access services; thirdly, this method provides multiple forms of authentication to trigger the activation of the service access function, which improves the security of application direct access services compared to the prior art using methods such as clicking application shortcut icons. Attached Figure Description

[0044] Figure 1 This is a schematic diagram of the structure of the terminal device provided in the embodiments of this application;

[0045] Figure 2 This is a schematic diagram of the software structure of the terminal device provided in the embodiments of this application;

[0046] Figure 3 This is a flowchart illustrating the steps of an application invocation method provided in an embodiment of this application;

[0047] Figure 4 This is a flowchart illustrating the steps for enabling a target function of an application, as provided in an embodiment of this application.

[0048] Figure 5 This is a schematic diagram of the system architecture to which an application invocation method provided in this application embodiment applies;

[0049] Figure 6 This is a schematic diagram of the development process of an application invocation method provided in an embodiment of this application;

[0050] Figure 7This is a schematic diagram of the installation state process of an application invocation method provided in an embodiment of this application;

[0051] Figure 8 This is a schematic diagram of the user-mode process of an application invocation method provided in an embodiment of this application;

[0052] Figure 9 This is a schematic diagram of an application invocation device provided in an embodiment of this application. Detailed Implementation

[0053] To facilitate understanding, we will first introduce several possible implementation methods for direct service access based on the lock screen interface entry.

[0054] 1. Implementation scheme based on shortcut icons on the lock screen interface.

[0055] Service access via shortcut icons on the lock screen first requires developers to create a lock screen application and integrate shortcut icons for different applications onto its interface. Examples include camera, calculator, flashlight, weather, and quick contacts. Then, when a user is using the device, they can close the system's built-in lock screen application and install the developer's version. Each time the screen is turned on, the installed lock screen application is the first thing the user sees. Users can then directly open the corresponding application by clicking the shortcut icon displayed on the screen. For example, clicking the camera icon on the lock screen application will take them directly to the camera interface.

[0056] Accessing applications directly by clicking their shortcut icons on the lock screen is one of the most common solutions for providing direct service access. The core of this solution lies in developing a lock screen application to replace the system's built-in one. The implementation process may include the following steps:

[0057] Step 1: Create a lock screen application at the application level. This lock screen application needs to have a broadcast receiver added to listen for broadcast notifications when the screen is on (Screen_ON) and off (Screen_OFF).

[0058] Step 2: Lock screen applications need to disable the functions of the terminal's home button and back button to prevent users from bypassing the lock screen interface and directly entering the terminal's main interface using the home and back buttons.

[0059] Step 3: Add the application's icon (button) to the lock screen application's interface, that is, bind the application package name to the button's event handler.

[0060] Step 4: The user closes the system's built-in lock screen application and installs the newly developed lock screen application. At this point, the user can quickly access the bound application while the screen is locked.

[0061] 2. Implementation scheme based on lock screen swipe gestures.

[0062] Similar to the implementation of shortcut icons on the lock screen, the swipe gesture-based implementation also requires developers to create a lock screen application. However, the swipe gesture solution does not require integrating application shortcut icons into the lock screen application's interface. Instead, it adds touch event response methods to the lock screen application, establishing a mapping relationship between the duration of the user's finger touch on the screen and the direction of the swipe, thus directly opening the corresponding application when the user performs different swipe gestures. For example, a user can open the calculator application by drawing a circle on the lock screen.

[0063] The core idea behind using different swipe gestures to launch corresponding applications is to develop a lock screen application to replace the system's built-in lock screen application. The implementation process of this solution may include the following steps:

[0064] Step 1: Create a lock screen application at the application level. This lock screen application needs to have a broadcast receiver added to listen for broadcast notifications when the screen is on (Screen_ON) and off (Screen_OFF).

[0065] Step 2: Lock screen applications need to disable the functions of the terminal's HOME and Back buttons to prevent users from bypassing the lock screen interface and directly entering the terminal's main interface using the HOME and Back buttons.

[0066] Step 3: Parse the swipe gesture in the lock screen application's touch event, that is, bind the application package name to the gesture recognition event.

[0067] Step 4: The user closes the system's built-in lock screen application and installs the newly developed lock screen application. At this point, the user can quickly access the bound application while the screen is locked.

[0068] 3. Implementation scheme for fingerprint verification based on lock screen interface.

[0069] Compared to the previous two technologies, fingerprint verification offers higher security. However, it's also more difficult for ordinary developers to implement this solution, as it's challenging to pre-map fingerprints to applications within the lock screen app. Currently, some devices support binding certain payment applications, such as wallets, to the fingerprint management module. By enabling quick payment in the wallet within the fingerprint management module, users can quickly open the bound wallet after verifying a specific fingerprint on the lock screen. In other words, the user is automatically redirected to the wallet app after unlocking the device with their fingerprint. However, other applications do not support this quick fingerprint unlock feature on the lock screen, meaning users cannot customize fingerprint verification to open other applications.

[0070] The above-described solution of using fingerprint verification on the lock screen to invoke applications is one of the most secure and practical solutions for direct service access. The core of this solution lies in modifying the system's fingerprint management module and integrating the ability to launch applications requiring direct service access into the fingerprint management module. The implementation process of this solution may specifically include the following steps:

[0071] Step 1: Add a fingerprint verification call management module for preferred applications in the fingerprint management module.

[0072] Step 2: Add an interface to read the fingerprint list in the fingerprint verification call management module to display the current fingerprint list in real time. Each fingerprint is identified by a unique fingerprint ID.

[0073] Step 3: Select a specific fingerprint from the fingerprint list for use in calling the preferred application, that is, bind a specific fingerprint ID to the preferred application.

[0074] Step 4: Modify the fingerprint verification logic in the fingerprint management module. After the fingerprint certificate is verified, return the specific fingerprint ID.

[0075] Step 5: When verifying a user's fingerprint, the fingerprint management module determines whether the current fingerprint ID is bound to a preferred application. If the fingerprint ID is bound to an application, the fingerprint management module initiates a call request to the activity manager service (AMS); otherwise, it enters the main interface of the terminal.

[0076] The aforementioned solution based on shortcut icons or swipe gestures on the lock screen provides users with quick access to specific applications. However, this solution requires developers to create new lock screen applications to replace the system's built-in lock screen application. In other words, this solution cannot reuse the system's lock screen application, resulting in relatively high development costs and technical barriers. Secondly, this solution cannot allow users to customize their preferred services directly; it relies entirely on which applications the developer has integrated into the lock screen application, leading to a poor user experience. Thirdly, for some systems, the system developer may prohibit third-party developers from blocking the HOME button. For such systems, developers cannot create new lock screen applications. Furthermore, from a security perspective, preferred applications accessed via shortcut icons or swipe gestures on the lock screen should avoid being sensitive applications, such as those enabling QR code payments or providing transit / payment codes. Otherwise, the user's privacy, information, or asset security cannot be guaranteed.

[0077] While fingerprint verification based on the lock screen can effectively ensure security, this solution cannot provide direct access to services customized by the user and depends on which applications the developer has integrated into the lock screen application. Furthermore, for some systems that prohibit third-party developers from disabling the HOME button, developers are also unable to create new lock screen applications based on those systems.

[0078] To address the problems of the aforementioned solutions, this application provides a method for invoking applications. This method involves adding a service access declaration, service configuration, and polymorphic identity management to the manifest file of the application installation package. Developers only need to pre-declare the service access in the manifest file when developing the application. When the application is installed on a terminal device, the package management service module on the terminal device can automatically complete the service access configuration by parsing the installation package. When using applications installed on the terminal device, users can select an application from the service access list and bind the selected application with the authentication method and authentication information to achieve service access support in lock screen mode. Using this method, there is no need to develop new lock screen applications, reducing the cost and difficulty of service access development. In addition, users can also configure their preferred applications to have service access capabilities, enhancing the user experience.

[0079] The following describes the method for invoking the application provided in this application, with reference to specific embodiments.

[0080] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and purpose. For example, "first application," "second application," "third application," etc., are merely used to distinguish different applications and do not limit their number or execution order.

[0081] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0082] The business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0083] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0084] The steps involved in the application invocation method provided in this application embodiment are merely examples. Not all steps are mandatory, nor are all contents of each piece of information or message required. They can be added or removed as needed during use.

[0085] In this application, the same step or a step or message with the same function can be referenced and learned from each other in different embodiments.

[0086] The application invocation method provided in this application embodiment can be applied to terminal devices. Figure 1A schematic diagram of the terminal device 100 is shown. The terminal device 100 can be a mobile phone, tablet computer, wearable device, in-vehicle device, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), etc. This application embodiment does not limit the specific type of the terminal device 100.

[0087] It should be noted that, Figure 1 The structure of the terminal device 100 shown is designed to meet the requirements for operation within the terminal device 100. Taking the system as an example, we will introduce the structure of the terminal device 100. Of course, based on... Figure 1 The terminal device 100 has a structure that allows it to run other types of operating systems, such as... system, Systems, etc.

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

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

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

[0091] The controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.

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

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

[0094] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments of this application, the processor 110 may include multiple I2C buses. The processor 110 can couple to the touch sensor 180K, charger, flash, camera 193, etc., through different I2C bus interfaces. For example, the processor 110 can couple to the touch sensor 180K through the I2C interface, enabling the processor 110 and the touch sensor 180K to communicate through the I2C bus interface, thereby realizing the touch function of the terminal device 100.

[0095] The I2S interface can be used for audio communication. In some embodiments of this application, the processor 110 may include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to realize communication between the processor 110 and the audio module 170. In some embodiments of this application, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface to realize the function of answering phone calls through a Bluetooth headset.

[0096] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments of this application, the audio module 170 and the wireless communication module 160 can be coupled via the PCM bus interface. In some embodiments of this application, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering phone calls through a Bluetooth headset.

[0097] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments of this application, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments of this application, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface to enable music playback via Bluetooth headphones.

[0098] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display 194 and the camera 193. The MIPI interface includes the camera serial interface (CSI) and the display serial interface (DSI).

[0099] In some embodiments of this application, the processor 110 and the camera 193 communicate via a CSI interface to enable the shooting function of the terminal device 100. The processor 110 and the display screen 194 communicate via a DSI interface to enable the display function of the terminal device 100.

[0100] The GPIO interface can be configured via software. It can be configured as a control signal or a data signal. In some embodiments of this application, the GPIO interface can be used to connect the processor 110 to a camera 193, a display screen 194, a wireless communication module 160, an audio module 170, a sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0101] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, or USB Type-C port. USB port 130 can be used to connect a charger to charge terminal device 100, and can also be used for data transfer between terminal device 100 and peripheral devices. USB port 130 can also be used to connect headphones for audio playback. This interface can also be used to connect other terminal devices, such as AR devices.

[0102] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the terminal device 100. In other embodiments of this application, the terminal device 100 may also adopt different interface connection methods or a combination of multiple interface connection methods as described in the above embodiments.

[0103] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the terminal device 100. While charging the battery 142, the charging management module 140 can also supply power to the terminal device via the power management module 141.

[0104] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, internal memory 121, display screen 194, camera 193, wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance).

[0105] In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may also be located in the same device.

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

[0107] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

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

[0109] In some embodiments of this application, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments of this application, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0110] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through audio devices (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194.

[0111] In some embodiments of this application, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

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

[0113] In some embodiments of this application, antenna 1 of terminal device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling terminal device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

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

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

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

[0117] The ISP is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and skin tone. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments of this application, the ISP can be set in the camera 193.

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

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

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

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

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

[0123] The internal memory 121 can be used to store computer executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the terminal device 100 (such as audio data, phonebook, etc.).

[0124] In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory. For example, at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0125] The processor 110 executes various functional applications and data processing of the terminal device 100 by running instructions stored in the internal memory 121 and / or in the memory set in the processor.

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

[0127] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments of this application, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0128] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The terminal device 100 can listen to music or make hands-free calls through the speaker 170A.

[0129] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the terminal device 100 answers a phone call or voice message, the receiver 170B can be brought close to the listener's ear to hear the voice.

[0130] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Terminal device 100 may be equipped with at least one microphone 170C. In some embodiments, terminal device 100 may be equipped with two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, terminal device 100 may be equipped with three, four, or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc.

[0131] The 170D headphone jack is used to connect wired headphones. The 170D headphone jack can be a USB 130 interface, or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, or a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

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

[0133] In some embodiments of this application, touch operations applied to the same touch location but with different touch intensity can correspond to different operation commands. For example, when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS message is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS message is executed.

[0134] The gyroscope sensor 180B can be used to determine the motion attitude of the terminal device 100. In some embodiments of this application, the gyroscope sensor 180B can determine the angular velocity of the terminal device 100 around three axes (i.e., the x, y, and z axes). The gyroscope sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the shaking of the terminal device 100, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to counteract the shaking of the terminal device 100 through reverse movement, thus achieving image stabilization. The gyroscope sensor 180B can also be used in navigation and motion-sensing game scenarios.

[0135] The barometric pressure sensor 180C is used to measure air pressure. In some embodiments of this application, the terminal device 100 calculates altitude, assists in positioning, and navigates using the air pressure value measured by the barometric pressure sensor 180C.

[0136] The magnetic sensor 180D includes a Hall sensor. The terminal device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip cover. In some embodiments of this application, when the terminal device 100 is a flip phone, the terminal device 100 can detect the opening and closing of the flip cover using the magnetic sensor 180D, and then set features such as automatic flip unlocking based on the detected opening and closing state of the cover or the flip cover.

[0137] The 180E accelerometer can detect the magnitude of acceleration of the terminal device 100 in various directions (typically three axes). When the terminal device 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the attitude of the terminal device, and can be applied to applications such as landscape / portrait switching and pedometers.

[0138] A distance sensor 180F is used to measure distance. The terminal device 100 can measure distance via infrared or laser. In some embodiments of this application, such as in a shooting scenario, the terminal device 100 can utilize the distance sensor 180F for distance measurement to achieve fast focusing.

[0139] The proximity sensor 180G may include, for example, a light-emitting diode (LED) and a light detector, such as a photodiode. The LED may be an infrared LED. The terminal device 100 emits infrared light outward through the LED. The terminal device 100 uses the photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the terminal device 100. When insufficient reflected light is detected, the terminal device 100 can determine that there is no object near the terminal device 100. The terminal device 100 may use the proximity sensor 180G to detect when a user holds the terminal device 100 close to their ear for a call, so as to automatically turn off the screen to save power. The proximity sensor 180G can also be used in holster mode and pocket mode for automatic unlocking and screen locking.

[0140] The ambient light sensor 180L is used to sense the ambient light intensity. The terminal device 100 can adaptively adjust the brightness of the display screen 194 based on the sensed ambient light intensity. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also work with the proximity sensor 180G to detect whether the terminal device 100 is in a pocket to prevent accidental touches.

[0141] The fingerprint sensor 180H is used to collect fingerprints. The terminal device 100 can use the characteristics of the collected fingerprints to achieve fingerprint unlocking, accessing application locks, taking photos with fingerprints, and answering calls with fingerprints.

[0142] Temperature sensor 180J is used to detect temperature. In some embodiments of this application, terminal device 100 uses the temperature detected by temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, terminal device 100 reduces the performance of the processor located near temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is below another threshold, terminal device 100 heats battery 142 to prevent abnormal shutdown of terminal device 100 due to low temperature. In still other embodiments, when the temperature is below yet another threshold, terminal device 100 boosts the output voltage of battery 142 to prevent abnormal shutdown due to low temperature.

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

[0144] The bone conduction sensor 180M can acquire vibration signals. In some embodiments of this application, the bone conduction sensor 180M can acquire vibration signals from vibrating bone fragments in the human vocal cords. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure signals.

[0145] In some embodiments of this application, the bone conduction sensor 180M can also be incorporated into headphones to form bone conduction headphones. The audio module 170 can analyze the vibration signal of the sound-vibrating bone block acquired by the bone conduction sensor 180M to extract the voice signal and realize the voice function. The application processor can analyze the heart rate information based on the blood pressure fluctuation signal acquired by the bone conduction sensor 180M to realize the heart rate detection function.

[0146] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch buttons. Terminal device 100 can receive button input and generate key signal inputs related to user settings and function control of terminal device 100.

[0147] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can correspond to touch operations performed on different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations performed on different areas of the display screen 194. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

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

[0149] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the terminal device 100. The terminal device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The terminal device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments of this application, the terminal device 100 uses an eSIM (i.e., an embedded SIM card). The eSIM card can be embedded in the terminal device 100 and cannot be separated from the terminal device 100.

[0150] The software system of terminal device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses a layered architecture. Taking the system as an example, the software structure of the terminal device 100 is illustrated.

[0151] Figure 2 This is a software structure block diagram of the terminal device 100 according to an embodiment of this application.

[0152] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments of this application, The system is divided into four layers, from top to bottom: application layer, application framework layer, ... runtime ( runtime and system libraries, as well as the kernel layer.

[0153] The application layer can include a series of application packages.

[0154] like Figure 2 As shown, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and SMS.

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

[0156] like Figure 2As shown, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0157] The window manager is used to manage windowed applications. It can retrieve screen size, determine if a status bar is present, lock the screen, and capture screenshots, among other things.

[0158] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0159] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0160] The phone manager is used to provide communication functions for terminal device 100. For example, it manages call status (including connection, hang-up, etc.).

[0161] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and so on.

[0162] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating the device, and flashing indicator lights.

[0163] Runtime includes core libraries and a virtual machine. runtime is responsible for System scheduling and management.

[0164] The core library consists of two parts: one part contains the functionalities that the Java language needs to call, and the other part is... The core library.

[0165] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0166] System libraries can include multiple functional modules. For example, a surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0167] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0168] The media library supports playback and recording of various commonly used audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0169] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0170] A 2D graphics engine is a graphics engine for 2D drawing.

[0171] The kernel layer is the layer between hardware and software. The kernel layer includes at least display drivers, camera drivers, audio drivers, and sensor drivers.

[0172] The following example, using a scene of capturing a photograph, illustrates the workflow of the software and hardware of the terminal device 100.

[0173] When touch sensor 180K receives a touch operation, a corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, timestamp of the touch operation, etc.). The raw input event is stored in the kernel layer. The application framework layer retrieves the raw input event from the kernel layer and identifies the control corresponding to the input event. Taking a single touch operation as an example, where the corresponding control is the camera application icon, the camera application calls the interface of the application framework layer to launch the camera application, and then calls the kernel layer to launch the camera driver, capturing still images or videos through camera 193.

[0174] like Figure 3 The diagram shown is a flowchart illustrating the steps of an application invocation method according to an embodiment of this application. This method can be applied to a terminal device 100 having the above-described structure and / or software structure. Specifically, the method may include the following steps:

[0175] S301. The terminal device parses the installation package of the application to be installed, wherein the installation package is configured with a declaration tag of the target function; wherein, the target function includes the function of calling the application when the terminal device is locked.

[0176] The application to be installed can be of any type. For example, social applications, payment applications, etc. This application embodiment does not limit the type of application.

[0177] Before installing an application, a terminal device can download the application's installation package from an application market; alternatively, the terminal device can receive the downloaded application's installation package through other channels. This application embodiment does not limit the source of the application's installation package.

[0178] In this embodiment of the application, the installation package of the application may be configured with a declaration tag for a target function. This target function may refer to a function of a certain application that allows the user to directly call the function of the application when the terminal device is in a locked state, without the need to unlock the terminal device in advance. Typically, this function is also referred to as the application's direct service access function.

[0179] In this embodiment, the aforementioned declaration tag can be configured in advance by the developer when developing the application. This declaration tag can be used to declare that the application supports the aforementioned target functions. For example, it can declare that the application supports direct service access.

[0180] In a practical implementation, the declaration tag can be a slot tag written in the Profile manifest file of the installation package. The package management service module in the terminal device can have the ability to parse the above slot tags, so that the terminal device can determine in a timely manner whether the application supports the service direct access function when installing any application.

[0181] In one embodiment of this application, the aforementioned declaration tag may include a function declaration sub-tag for the target function and an authentication type sub-tag. The function declaration sub-tag can be used to characterize that the application supports service direct access functionality, while the authentication type sub-tag can be used to characterize at least one authentication method supported by the target function. The aforementioned at least one authentication method may refer to the authentication method that triggers the application to perform the service direct access operation.

[0182] In specific implementations, the aforementioned authentication methods may include at least one of fingerprint verification, gesture password verification, and digital password verification. Fingerprint verification refers to interaction between a terminal device and a user via fingerprint recognition and verification. When the terminal device successfully verifies a specific fingerprint, it can perform direct service access to an application based on the verified fingerprint. Gesture password verification refers to a method where a user triggers verification by drawing a specific shaped gesture. Digital password verification refers to a method where the terminal device verifies a string of numbers entered by the user.

[0183] As an example of an embodiment of this application, when developing an application, the developer can first create project files. Then, the developer configures the feature declaration sub-tag and authentication type sub-tag in the manifest file and binds these two sub-tags to declare that the application supports direct service access functions and the supported authentication types. Of course, after performing the above operations, the developer also needs to complete the development of other matters according to the business functions of the application. After development is completed, the above files can be packaged into an installation package of the application for download and installation by terminal devices.

[0184] S302. The terminal device configures the target function of the application according to the declaration tag.

[0185] In this embodiment, when a terminal device installs an application, if it confirms by parsing the application's installation package that the installation package contains a declaration tag for service direct access, the terminal device can determine that the application supports service direct access. Therefore, the terminal device can configure the application's service direct access function based on this declaration tag. The purpose of this configuration is to complete the registration of the application's service direct access function on the terminal device.

[0186] In one possible implementation of this application, when configuring the application's service to directly access the target function, the terminal device can first determine at least one authentication method supported by the target function based on the authentication type sub-tag in the declaration tag. For example, fingerprint verification, gesture password verification, and / or numeric password verification.

[0187] Then, the terminal device can bind the application to at least one identified authentication method based on the function declaration sub-tag in the declaration tag. For example, if the terminal device determines that the target function supports fingerprint verification, it can bind the application to the fingerprint verification method so that the user can subsequently enable the application's direct service access function through fingerprint verification.

[0188] It should be noted that there should be an overlap between the at least one authentication method supported by the target function and the authentication methods that the terminal device can actually provide, so that the terminal device can bind the application to the authentication method supported by the target function according to the function declaration sub-tag.

[0189] For example, if the target function supports authentication methods including fingerprint verification, gesture password verification, and numeric password verification, but the terminal device itself only supports gesture password verification and numeric password verification and does not support fingerprint verification, then when configuring the target function of the application, the terminal device can only bind the application with gesture password verification and / or numeric password verification. Subsequently, users can only enable the application's service access function through gesture password verification and / or numeric password verification.

[0190] After binding an application and an authentication method, the terminal device can configure the target functions of the application that is bound to at least one authentication method to complete the registration of the target functions of the application.

[0191] It should be noted that the configuration of the target functions of the application on the terminal device can be done during the application installation process. After the application is installed, the application's direct service access function can be triggered based on user actions.

[0192] like Figure 4 As shown, in one possible implementation of this application embodiment, the target function of the application can be enabled in the following way:

[0193] S3021. The terminal device displays information about at least one authentication method supported by the target function.

[0194] In this embodiment of the application, when the target function of the application is enabled, the terminal device can first display the authentication methods supported by the target function to the user, so that the user can choose which authentication method to use to trigger the target function of the application.

[0195] Of course, before allowing users to choose an authentication method, the terminal device can display all applications that support the target function to the user, allowing the user to select one or more applications to enable the target function.

[0196] For example, the terminal device may have three applications installed that support direct service access: a first application, a second application, and a third application. The terminal device can first display these three applications to the user through a list or other similar format, informing the user to enable the direct service access function for these applications.

[0197] Users can select one or more of the above applications to enable the service direct access feature for that application. Typically, if a user wishes to enable service direct access for multiple applications, they should do so separately, enabling the service direct access feature for each application one by one.

[0198] If a user chooses to enable the service access function of the first application, the terminal device can display to the user the authentication methods supported by the service access function of the application. These authentication methods should be the authentication methods that the terminal device can actually provide.

[0199] For example, if the first application's service access function supports fingerprint verification, gesture password verification, and numeric password verification, but the terminal device only supports gesture password verification and numeric password verification and does not support fingerprint verification, then the terminal device can provide the user with both gesture password verification and numeric password verification methods for the user to choose from.

[0200] S3022, The terminal device determines the authentication method selected by the user from the at least one authentication method.

[0201] In this embodiment, the user can select one of at least one authentication method displayed on the terminal device as the authentication method to trigger the direct service access function. Typically, there should only be one authentication method to trigger the direct service access function of an application.

[0202] For example, a user can choose between gesture password verification and numeric password verification provided by the terminal device as the verification method to trigger the direct access function of the first application service.

[0203] S3023, The terminal receives the authentication information input by the user corresponding to the selected authentication method, and binds the application, the selected authentication method, and the authentication information.

[0204] After determining the authentication method selected by the user, the terminal device can prompt the user to enter the authentication information corresponding to that authentication method.

[0205] For example, for the user-selected gesture password verification method, the terminal device can display a gesture password input box on the screen, prompting the user to enter the corresponding gesture password. Typically, for user-entered authentication information, the terminal device can require the user to enter that information at least twice to ensure the validity of the authentication information.

[0206] After the user enters the authentication information, the terminal device can bind the authentication method, the authentication information corresponding to the authentication method, and the current application to complete the configuration of the application's target function.

[0207] S303. If the terminal device receives an instruction to invoke the application while in the locked screen state, the terminal device invokes the application according to the instruction.

[0208] In this embodiment, the target function configured for the application on the terminal device is to directly invoke the application's function while the terminal is locked. Therefore, if the terminal device receives an instruction to invoke an application while the terminal device is locked, the terminal device can directly invoke the application without unlocking the screen.

[0209] In one possible implementation of this application, the terminal device receiving an instruction to invoke an application may be triggered by certain operations performed by the user on the terminal device. However, since the user's operations on the terminal device may include various types, when the terminal device listens for an instruction generated by the user's operation, it can first determine whether the instruction is triggered by an authentication method corresponding to the target function of an application.

[0210] If the instruction is triggered by an authentication method corresponding to the application's target function—for example, if the authentication method triggering the first application's service access function is gesture password verification, and the user operation detected by the current terminal device is also a gesture performed by the user on the terminal device—then the terminal device can verify the authentication information contained in the listened-to instruction. For example, the terminal device verifies the gesture to determine if the resulting graphic and gesture sequence are the same as pre-stored information. If they are the same, the terminal device can determine that the authentication information has been verified. Then, the terminal device can invoke the application based on the verified authentication information to achieve service access without unlocking the terminal device screen.

[0211] In one possible implementation of this application, when a terminal device calls an application based on the authentication information contained in the instruction, the terminal device can first determine which application is bound to the authentication information, and then call the application bound to the authentication information and display the application on the main interface of the terminal device.

[0212] In this embodiment, the terminal device can confirm whether the installation package of the application to be installed contains a declaration tag for the target function by parsing the installation package. If the terminal device confirms that the installation package contains a declaration tag for the target function, it indicates that the application has the function to be invoked in the lock screen state. Therefore, the terminal device can configure the target function of the application according to the above declaration tag and complete the registration of the target function on the terminal device. When the terminal device receives an instruction to invoke an application in the lock screen state, the terminal device can invoke the application according to the instruction. Through the method provided by this embodiment, developers do not need to develop a lock screen application separately for the terminal device to realize the service access function of the application, reducing development costs and development difficulty; secondly, by pre-configuring the declaration tag supporting service access in the application installation package, this method allows users to choose whether to enable the service access function of each application, solving the problem in the prior art that it does not support users to customize which applications provide the service access; thirdly, this method provides multiple forms of authentication to trigger the activation of the service access function, which improves the security of application access to services compared with the prior art using methods such as clicking application shortcut icons.

[0213] To facilitate understanding, the following section describes the application invocation method provided in this application embodiment, in conjunction with a specific system architecture and specific examples of each stage of implementing this method based on that system architecture.

[0214] The application invocation method provided in this application embodiment can be applied to various types of terminal platforms, such as... Platforms such as [platform name missing]. When this method is applied to [platform name missing]... When using a platform, the terminal device in this application embodiment may have Figure 1 The structure shown and Figure 2 The software architecture shown; when this method is applied to other platforms, the terminal device can have the same... Figure 1 The same structure, or the terminal device can also be in Figure 1 Based on this, the result obtained by adding or removing some units or components is similar to Figure 1 Different structures; when this method is applied to other platforms, the terminal device can adopt a different architecture. Figure 2 Different software architectures.

[0215] This application embodiment reduces the development cost for developers and enables users to access services directly under the lock screen by adding a slot management module and a polymorphic identity management module to the various terminal platforms mentioned above, and adding a declaration tag (slot tag) for the target function to the manifest file.

[0216] like Figure 5The diagram shown is a schematic diagram of the system architecture to which an application invocation method provided in this application embodiment applies. Figure 5 The system architecture shown mainly consists of four parts: target function service (direct access service), application framework, system services, and system kernel.

[0217] The direct access service includes a profile file, assets files, pages, and libs executable files. Developers can declare that their application supports the direct access service feature by configuring slot tags in the profile file.

[0218] The application framework includes a slot module and a polymorphic identity management module. The slot module is used to configure the service access function and complete the registration of the application's service access function on the terminal device. The polymorphic identity management module is used for the entry and verification of user authentication information.

[0219] The system services of the terminal device can provide package management services and service management services. The package management service can provide the ability to parse newly added slot tags to determine whether the currently installed applications support the service direct access function. The service management service can enable the startup of direct access services.

[0220] Based on the above system framework, developers can declare the slot tag in the Profile manifest file when developing applications, indicating that the application supports direct access to services under the lock screen. The authentication types supported by the application's direct access function can include fingerprint, digital, and gesture, where: digital is numeric password verification, gesture is gesture password verification, and fingerprint is fingerprint verification.

[0221] After installing various applications that support the service direct access function on the terminal device, users can select an application from the service direct access list to enable service direct access on the lock screen according to their preferences. When this function is enabled, the terminal device can display the corresponding authentication information entry dialog box according to the authentication type declared in the slot tag in the manifest file, allowing users to enter fingerprints, numeric passwords, or gesture passwords, etc.

[0222] According to the above system architecture, the method for calling the application in the embodiments of this application can include three stages: development state, installation state, and user state. The implementation process of each stage will be described below.

[0223] like Figure 6 The diagram shown is a schematic representation of the development state process of an application invocation method according to an embodiment of this application. According to... Figure 6 The process shown can include the following steps in the development phase of an application:

[0224] Step 1: Create the application project file.

[0225] Step 2: Configure the service access feature declaration tags in the manifest file (Profile). Declaration tags include the feature declaration sub-tag (slot tag) and the authentication type sub-tag (type tag). The slot tag declares that the application supports the service access feature, and the type tag declares the authentication type bound to the service access feature.

[0226] Step 3: Develop other functions of the application based on the project's business functions.

[0227] Step 4: Package the developed application into an installer and distribute it. The installer can be published on various app stores for users to download.

[0228] like Figure 7 The diagram shown is a schematic representation of the installation state process of an application invocation method according to an embodiment of this application. According to... Figure 7 The process shown, in which the application is installed, may include the following steps:

[0229] Step 1: The terminal device downloads and installs the application; the package management service parses the application's installation package.

[0230] Step 2: During the parsing process, the package management service determines whether the application's manifest file (Profile) declares a service direct access slot tag.

[0231] Step 3: If the slot tag is declared in the manifest file Profile, the package management service registers the application support service access and the identity type that needs to be bound with the slot management module.

[0232] Step 4: The application installation is complete. Users can open the application or enable the application's direct service access function.

[0233] like Figure 8 The diagram shown is a user-mode process illustration of an application invocation method provided in an embodiment of this application. User mode refers to the process by which a user activates the service access function of a specific application through operations on a terminal device. Figure 8 The process shown can include the following steps in the user space of the application:

[0234] Step 1: The terminal device displays a list of applications that support direct access to the service.

[0235] In this step, users can access the aforementioned list by clicking the "Settings" button on their terminal device's screen. This list allows users to view all applications on their terminal device that support the direct service access feature. For example, the list may include the first application, the second application, the third application, and so on.

[0236] The applications displayed in the list on the terminal device can be icons of the applications that support the direct service access function, or the names of the applications. Alternatively, the terminal device can display both the icons and names of the applications in the list.

[0237] Step 2: Users select an application based on their personal preferences to directly access the service.

[0238] In this step, the user can select any application to trigger its direct service access function. For example, the user can click the icon of the first application in the application list above. At this time, the terminal device will prompt the user through a pop-up window "Do you want to enable the direct service access function for the first application?" The user can click "Yes" in the pop-up window to confirm enabling the direct service access function for the first application; or, the user can click "No" in the pop-up window to exit this process and return to the application list to reselect and enable the direct service access function for other applications.

[0239] Step 3: The terminal device reads the authentication type configured in the application's claim tag.

[0240] In this step, when the application's service access function is enabled, the terminal device can read the authentication type declared in the application's type tag from the slot management module. For example, the terminal device can confirm that the authentication types supported by the first application include fingerprint verification, gesture password verification, and numeric password verification by reading the authentication type declared in the first application's type tag.

[0241] Step 4: The terminal device displays a pop-up dialog box for authentication methods, allowing the user to select a specific authentication method.

[0242] In this step, the polymorphic identity management module in the terminal device can pop up a dialog box based on the authentication type declared in the type tag, allowing the user to select which authentication method to use to enable the application's service direct access function.

[0243] It should be noted that the authentication methods offered to users by the terminal device should be based on the actual authentication methods supported by the terminal device's hardware. For example, if the terminal device's hardware supports fingerprint verification, then for the three authentication types supported by the first application mentioned above, the terminal device can prompt the user through a pop-up window to choose one of the three authentication methods—fingerprint verification, gesture password verification, and numeric password verification—as the authentication method bound to the first application. If the terminal device's hardware does not support fingerprint verification, then for the three authentication types supported by the first application mentioned above, the terminal device can prompt the user through a pop-up window to choose one of the two authentication methods—gesture password verification and numeric password verification—as the authentication method bound to the first application.

[0244] Step 5: The terminal device prompts the user to enter authentication information that matches the selected authentication method.

[0245] In this step, when a user selects an authentication method, the terminal device can display a dialog box matching the selected authentication method, allowing the user to enter the corresponding authentication information. For example, if the user selects fingerprint verification, the terminal device can display a fingerprint verification dialog box, prompting the user to enter their fingerprint; if the user selects gesture password verification, the terminal device can display a gesture password dialog box, prompting the user to draw specific gesture shapes on the terminal device in sequence.

[0246] Step Six: The user enters their authentication information to complete the binding of the application service direct access function with authentication.

[0247] In this step, after the user enters the authentication information that matches the selected authentication method, the terminal device can prompt the user to enter the same information again as the previously entered authentication information to complete the secondary verification of the authentication information and ensure the security and accuracy of the authentication information.

[0248] After the user completes the entry of identity verification information, the terminal device can prompt the user that the service direct access function of the current application has been enabled.

[0249] Step 7: The terminal device enters lock screen mode. While in lock screen mode, the user performs the operation of entering identity verification information.

[0250] In this step, if the terminal device wants to call an application while the terminal device is in a locked state, and if the application has the service access function enabled, the user can trigger the terminal device to call the application directly in the locked state by entering pre-bound authentication information, without having to unlock the terminal device in advance.

[0251] For example, suppose the authentication method bound to the first application with the service direct access function enabled is fingerprint verification. When the terminal device is in the locked screen state, if the user wants to call the first application, the user can press the lock screen interface with a finger. The terminal device can collect the user's fingerprint when the user presses the lock screen interface and verify the fingerprint.

[0252] Step 8: Based on the verified information, the terminal device brings the application to the foreground.

[0253] In this step, if the fingerprint collected by the terminal device is authentication information bound to the application's service access function, the terminal device can directly call the application to the foreground in the locked screen state for the user to use; if the collected fingerprint is the terminal device's unlock fingerprint, the terminal device completes device unlocking and enters the system homepage; if the collected fingerprint does not match any verification method, the terminal device will not respond to the fingerprint, or will prompt the user that the current fingerprint cannot be recognized and that the correct fingerprint information should be re-entered.

[0254] In this embodiment, by configuring a declaration that the application supports direct service access in the application's manifest file, the development difficulty and cost of direct service access in the terminal device's lock screen state can be reduced. Developers only need to focus on the development of business functions, without having to develop a new lock screen application separately for the direct service access function. Secondly, in this embodiment, the slot management module receives the application's service access function registration information during application installation and can manage all applications in the system that support the service access function, including the package name, bound authentication method, and authentication information of each application. Users can select one or more applications from the application list to enable service access support in the lock screen state, solving the problem in the prior art that users cannot customize direct access services. Thirdly, the polymorphic identity management module in this embodiment can be used for the input and verification of biometric passwords (fingerprints), gesture passwords, and numeric passwords. Multiple passwords of each modality can be entered, each password has a unique identity ID, and each identity ID can be bound to a lock screen direct access service. When the terminal device is in the lock screen state, after the polymorphic identity management module verifies and passes the received authentication information, the terminal device can return the identity ID corresponding to the current password, ensuring the security of the application.

[0255] This application embodiment can divide the terminal device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or one or more functions can be integrated into a single functional module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The following description uses the example of dividing each function into a separate functional module.

[0256] Reference Figure 9 The diagram illustrates an application invocation device according to an embodiment of this application, which can be applied to... Figure 1 The terminal device shown may include a parsing module 901, a configuration module 902, and a calling module 903, wherein:

[0257] The parsing module is used to parse the installation package of the application to be installed, wherein the installation package is configured with a declaration tag of the target function; wherein, the target function includes the function of calling the application when the terminal device is locked.

[0258] A configuration module is used to configure the target functionality of the application based on the declaration tags;

[0259] The calling module is configured to call the application according to the instruction if it receives an instruction to call the application in the locked screen state of the terminal device.

[0260] In this embodiment of the application, the declaration tag may include a function declaration sub-tag and an authentication type sub-tag for the target function, wherein the authentication type sub-tag may be used to characterize at least one authentication method supported by the target function.

[0261] In this embodiment of the application, the configuration module may include the following sub-modules:

[0262] The authentication method determination submodule is used to determine, based on the authentication type sub-label, at least one authentication method supported by the target function;

[0263] The authentication method binding submodule is used to bind the application to the at least one authentication method according to the function declaration sub-tag;

[0264] The target function configuration submodule is used to configure the target function of the application that is bound to the at least one authentication method.

[0265] In this application embodiment, the at least one authentication method may include at least one of fingerprint verification, gesture password verification, and digital password verification.

[0266] In this embodiment of the application, the device may further include the following modules:

[0267] The display module is used to display information about the at least one authentication method supported by the target function;

[0268] A determining module is used to determine the authentication method selected by the user from the at least one authentication method;

[0269] The binding module is used to receive the authentication information input by the user corresponding to the selected authentication method, and to bind the application, the selected authentication method, and the authentication information.

[0270] In this embodiment of the application, the calling module may include the following sub-modules:

[0271] The instruction judgment submodule is used to determine whether the instruction is triggered by an authentication method corresponding to the target function;

[0272] An authentication submodule is used to verify the authentication information contained in the instruction if the instruction is triggered by an authentication method corresponding to the target function.

[0273] The application calling submodule is used to call the application based on the authentication information when the authentication information is verified.

[0274] In this embodiment of the application, the application calling submodule may include the following units:

[0275] An application determination unit is used to determine the application bound to the authentication information;

[0276] The application invocation and display unit is used to invoke the application bound to the authentication information and display the application on the main interface of the terminal device.

[0277] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0278] This application also provides a terminal device, which may be the terminal device in the foregoing embodiments, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the application invocation method in the above embodiments.

[0279] This application also provides a computer storage medium storing computer instructions. When these computer instructions are executed on a terminal device, the terminal device performs the aforementioned method steps to implement the application invocation method described in the above embodiments.

[0280] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the application invocation method described above.

[0281] This application also provides a chip including a processor, which can be a general-purpose processor or a dedicated processor. The processor is used to support a terminal device in executing the aforementioned steps to implement the application invocation method described in the above embodiments.

[0282] Optionally, the chip also includes a transceiver, which is used to receive control from the processor to support the terminal device in performing the above-mentioned steps to implement the application invocation method in the above embodiments.

[0283] Optionally, the chip may also include a storage medium.

[0284] It should be noted that the chip can be implemented using the following circuits or devices: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0285] Finally, it should be noted that the above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for invoking an application, characterized in that, include: The terminal device parses the installation package of the application to be installed, wherein the installation package is configured with a declaration tag for a target function; wherein the declaration tag includes an authentication type sub-tag for characterizing at least one authentication method supported by the target function, and the target function includes the function of calling the application when the terminal device is locked. The terminal device determines the at least one authentication method supported by the target function based on the authentication type sub-tag, binds the application to the at least one authentication method, and configures the target function of the application bound to the at least one authentication method; If the terminal device receives an instruction to invoke the application while in the locked screen state, the terminal device invokes the application according to the instruction.

2. The method according to claim 1, characterized in that, The declaration tag also includes a function declaration sub-tag for the target function, which is used to declare that the application supports the target function.

3. The method according to claim 1, characterized in that, The at least one authentication method includes at least one of fingerprint verification, gesture password verification, and digital password verification.

4. The method according to any one of claims 1-3, characterized in that, Binding the application to the at least one authentication method includes: The terminal device displays information about at least one authentication method supported by the target function; The terminal device determines the authentication method selected by the user from the at least one authentication method; The terminal receives the authentication information input by the user corresponding to the selected authentication method, and binds the application, the selected authentication method, and the authentication information.

5. The method according to claim 4, characterized in that, The terminal device invokes the application according to the instruction, including: The terminal device determines whether the instruction is triggered by an authentication method corresponding to the target function; If the instruction is triggered by an authentication method corresponding to the target function, the terminal device verifies the authentication information contained in the instruction; When the authentication information is successfully verified, the terminal device invokes the application based on the authentication information.

6. The method according to claim 5, characterized in that, The terminal device invokes the application based on the authentication information, including: The terminal device identifies the application bound to the authentication information; The terminal device invokes the application bound to the authentication information and displays the application on the main interface of the terminal device.

7. An application invocation device, characterized in that, include: The parsing module is used to parse the installation package of the application to be installed, wherein the installation package is configured with a declaration tag for the target function; wherein the declaration tag includes an authentication type sub-tag for characterizing at least one authentication method supported by the target function, and the target function includes the function of calling the application when the terminal device is locked. A configuration module is used to determine, based on the authentication type sub-tag, the at least one authentication method supported by the target function and bind the application to the at least one authentication method, and configure the target function of the application bound to the at least one authentication method; The calling module is configured to call the application according to the instruction if it receives an instruction to call the application in the locked screen state of the terminal device.

8. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the application invocation method as described in any one of claims 1-6.

9. A computer-readable storage medium storing computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the application invocation method as described in any one of claims 1-6.

Images