Application lock starting method and device, electronic equipment and readable storage medium

Abstract

The application relates to the technical field of electronic equipment, and provides an application lock starting method and device, electronic equipment and a readable storage medium, the method comprising the following steps: when a starting operation of a target application is detected, starting an embedded window in a currently displayed parent window according to the starting operation; when an embedded window application corresponding to the starting operation is displayed in the embedded window, obtaining a preset application lock interface display mode according to the embedded window, wherein the embedded window and the parent window are in the same level or adjacent levels, and the application displayed in the embedded window is associated with the parent window, so that the application lock interface can be displayed according to the preset application lock interface display mode, without the need of determining the form of a starting interface, and the flexibility of starting the application lock authentication interface is improved.

Description

Technical Field

[0001] This application relates to the field of electronic equipment technology, and in particular to an application lock activation method, device, electronic device, and readable storage medium. Background Technology

[0002] To protect user security, when a user launches an application, the corresponding application lock authentication interface is launched based on the application type. The user then performs an authentication operation through the application lock authentication interface, and the application is only allowed to launch after the authentication operation is successful.

[0003] However, the launch form of the app lock authentication interface must be consistent with the launch interface. For example, when the app lock interface is loaded in a floating window, picture-in-picture pip, or bubble, its interface form will naturally be a floating window, picture-in-picture, or bubble. This leads to some problems, especially in bubble and pip modes, where the input on the authentication interface is almost impossible to display completely, resulting in a poor user experience. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, and readable storage medium for launching an application lock, with the aim of avoiding the application lock authentication interface from having the same startup form and startup interface, thereby improving the flexibility of launching the application lock authentication interface.

[0005] Firstly, this application provides a method for initiating an application lock, the method comprising:

[0006] When a launch operation of the target application is detected, an embedded window is launched in the currently displayed parent window according to the launch operation;

[0007] When displaying the embedded window application corresponding to the startup operation within the embedded window, the preset display mode of the application lock interface is obtained according to the embedded window, wherein the embedded window is at the same level or adjacent level as the parent window, and the application displayed in the embedded window is associated with the parent window;

[0008] The application lock interface is displayed according to the preset display mode of the application lock interface.

[0009] In one possible implementation, the display mode includes full-screen display;

[0010] The step of displaying the application lock interface according to the preset display mode of the application lock interface includes:

[0011] Display the application lock interface in full screen.

[0012] In one possible implementation, obtaining the preset display mode of the application lock interface based on the embedded window includes:

[0013] Get the unlock method for the application lock;

[0014] The display mode of the application lock interface is determined based on the unlocking method.

[0015] In one possible implementation, determining the display mode of the application lock interface based on the unlocking method includes:

[0016] When the unlocking method is to unlock via a fixed unlock frame, the display mode of the application lock interface is determined to be full-screen display.

[0017] In one possible implementation, obtaining the preset display mode of the application lock interface includes:

[0018] Determine whether to acquire the application lock's startup flag;

[0019] When the application lock's activation flag is obtained, the preset display mode of the application lock interface is obtained based on the application lock's activation flag.

[0020] In one possible implementation, after determining whether to acquire the application lock's start flag, the method further includes:

[0021] If the application lock launch flag is not obtained, obtain the pre-set display mode of the application lock interface;

[0022] Use the preset display mode of the application lock interface as the default display mode of the application lock interface.

[0023] In one possible implementation, after detecting the launch operation of the target application, the following is also included:

[0024] Save the component information corresponding to launching the target application;

[0025] After displaying the application lock interface according to the preset display mode, the method further includes:

[0026] When the application lock is unlocked, the saved component information corresponding to launching the target application is retrieved;

[0027] The target application is launched based on the saved component information corresponding to the launch of the target application.

[0028] In one possible implementation, launching the target application includes:

[0029] The target application is launched via an embedded window.

[0030] In one possible implementation, before obtaining the preset display mode of the application lock interface from the embedded window, the method further includes:

[0031] Determine whether the target application is locked;

[0032] When the target application is locked, the step of obtaining the preset display mode of the application lock interface based on the embedded window is executed;

[0033] If the target application is not locked, start the target application directly.

[0034] In one possible implementation, determining whether the target application is locked includes:

[0035] Retrieve the pre-configured list of applications with application lock settings;

[0036] Match the target application with the applications in the application list;

[0037] When the target application matches an application in the application list, the target application is locked.

[0038] If the target application does not match any application in the application list, it is determined that the target application is not locked.

[0039] In one possible implementation, before matching the target application with applications in the application list, the method further includes:

[0040] Determine if a screen-off event has occurred;

[0041] When a screen-off event occurs, the pre-configured list of applications with application lock settings is retrieved again to obtain an updated list of applications.

[0042] The step of matching the target application with applications in the application list includes:

[0043] The target application is matched with applications in the updated application list.

[0044] Secondly, this application provides an activation device for an application lock, comprising:

[0045] The startup module is used to launch an embedded window in the currently displayed parent window according to the startup operation when a startup operation of the target application is detected.

[0046] The acquisition module is used to acquire a preset application lock interface display mode according to the embedded window when the embedded window application corresponding to the startup operation is displayed in the embedded window, wherein the embedded window is at the same level or adjacent level as the parent window, and the application displayed in the embedded window is associated with the parent window.

[0047] The display module is used to display the application lock interface according to the preset display mode of the application lock interface.

[0048] Thirdly, this application provides an electronic device, comprising:

[0049] One or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions that, when executed by the electronic device, cause the electronic device to perform an application lock initiation method as described in any one of the first aspects or possible implementations of the first aspect above.

[0050] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform an application lock initiation method as described in any one of the first aspects or possible implementations of the first aspect.

[0051] Fifthly, this application provides a chip, the chip including a processor and a data interface, the processor reading instructions stored in a memory through the data interface to execute the application lock startup method described in any one of the first aspects or possible implementations of the first aspect.

[0052] Optionally, as one possible implementation, the chip may further include a memory storing instructions, and the processor is configured to execute the instructions stored in the memory. When the instructions are executed, the processor is configured to execute the application lock initiation method according to any one of the first aspects or possible implementations of the first aspect. Attached Figure Description

[0053] Figure 1a , Figure 1b A schematic scenario diagram illustrating the processing of existing technology applications;

[0054] Figure 2 A schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0055] Figure 3 A software structure block diagram of an electronic device provided in an embodiment of this application;

[0056] Figure 4 A flowchart illustrating an application lock initiation method according to an embodiment of this application;

[0057] Figure 5 A schematic diagram of the display interface of an embedded window provided in one embodiment of this application;

[0058] Figure 6 A module interaction diagram for launching an embedded window provided in another embodiment of this application;

[0059] Figure 7 A schematic diagram illustrating other applications of the embedded window shown in this application;

[0060] Figure 8 A schematic diagram showing the embedded window covering the input interface of this application example;

[0061] Figure 9 A module interaction diagram for launching an application lock window, provided as another embodiment of this application;

[0062] Figure 10 A flowchart illustrating an application lock initiation method provided in another embodiment of this application;

[0063] Figure 11a , Figure 11b A schematic diagram illustrating the interface lock for another embodiment of the application lock activation method provided in this application;

[0064] Figure 12 A schematic diagram of fingerprint unlocking provided for another embodiment of this application;

[0065] Figure 13 A schematic diagram of the overall process of an application lock activation method provided in another embodiment of this application;

[0066] Figure 14 A flowchart illustrating an application lock initiation method provided in another embodiment of this application;

[0067] Figure 15 This is a schematic diagram of the structure of an application lock activation device provided in this application. Detailed Implementation

[0068] The terms "first," "second," and "third," etc., used in this application specification, claims, and drawings are used to distinguish different objects, not to limit a specific order.

[0069] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is 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. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0070] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to an implementation scheme of an electronic device is first given:

[0071] Currently, the launch form of the application lock authentication interface can only be consistent with the launch interface. For example, when the application lock interface is loaded in a floating window, picture-in-picture pip, or bubble, its interface form will naturally be a floating window, picture-in-picture, or bubble. Figure 1a The picture-in-picture mode shown applies to the lock interface and, as shown, the application lock interface. Figure 1b The example shown is an app lock interface in floating window mode. However, if you need to use the input method from the app lock unlock screen, the input interface cannot be fully displayed in the app lock interface if the window size is small. Figure 1a Figure 1b This is a schematic scene diagram illustrating the application of lock interfaces in existing technologies.

[0072] To address the problems existing in the above-mentioned technical solutions, this application provides an application lock launch method. When a launch operation of a target application is detected, an embedded window is launched in the currently displayed parent window according to the launch operation. When the embedded window application corresponding to the launch operation is displayed within the embedded window, a preset application lock interface display mode is obtained according to the embedded window. The embedded window and the parent window are at the same or adjacent levels, and the application displayed in the embedded window is associated with the parent window. The application lock interface is displayed according to the preset application lock interface display mode. This allows the application lock interface to be displayed based on the preset display mode without needing to be determined based on the form of the launch interface, thus improving the flexibility of launching the application lock authentication interface.

[0073] The provided application lock activation method is applicable to mobile phones, tablets, desktops, laptops, notebooks, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, personal digital assistants (PDAs), wearable electronic devices, smartwatches, and other electronic devices. Among these, the electronic devices using this application lock activation method can have the following structure: Figure 2 As shown.

[0074] like Figure 2 As shown, Figure 2 The following is an example diagram illustrating the composition of an electronic device provided in this application. The electronic device 200 may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, a sensor module 280, buttons 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc. The sensor module 280 may include a pressure sensor 280A, a gyroscope sensor 280B, a barometric pressure sensor 280C, a magnetic sensor 280D, an accelerometer sensor 280E, a distance sensor 280F, a proximity sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone conduction sensor 280M, etc.

[0075] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 200. In other embodiments, the electronic device 200 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.

[0076] Processor 210 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0077] The controller can serve as the central nervous system and command center of the electronic device 200. The controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.

[0078] The processor 210 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. This memory can store instructions or data that the processor 210 has just used or that are used repeatedly. If the processor 210 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 210, and thus improves the efficiency of the system.

[0079] In some embodiments, the processor 210 may include one or more interfaces. 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.

[0080] It is understood that the interface connection relationships between the modules illustrated in this embodiment are merely illustrative and do not constitute a structural limitation on the electronic device 200. In other embodiments of this application, the electronic device 200 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0081] The wireless communication function of electronic device 200 can be implemented through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor.

[0082] The wireless communication module 260 can provide solutions for wireless communication applications on the electronic device 200, 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 260 can be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 210. The wireless communication module 260 can also receive signals to be transmitted from processor 210, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0083] In some embodiments, antenna 1 of electronic device 200 is coupled to mobile communication module 250, and antenna 2 is coupled to wireless communication module 260, enabling electronic device 200 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).

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

[0085] The display screen 294 of the electronic device 200 can display a series of graphical user interfaces (GUIs), which serve as the main screen of the electronic device 200. Generally, the size of the display screen 294 of the electronic device 200 is fixed, and only a limited number of controls can be displayed on the display screen 294. A control is a GUI element, a software component contained in an application, that controls all data processed by the application and interactive operations related to that data. Users can interact with controls through direct manipulation, thereby reading or editing information related to the application. Generally, controls can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets. For example, in this embodiment, the display screen 291 can display virtual buttons (one-click arrangement, start arrangement, scene arrangement).

[0086] Electronic device 200 can perform shooting functions through ISP, camera 293, video codec, GPU, display screen 294 and application processor.

[0087] Electronic device 200 can implement audio functions such as music playback and recording through audio module 270, speaker 270A, receiver 270B, microphone 270C, headphone jack 270D, and application processor.

[0088] In addition, an operating system runs on top of the aforementioned components. Examples include HarmonyOS, iOS, Android (open-source operating system), and Windows. Applications can be installed and run on this operating system.

[0089] Figure 3 This is a software structure block diagram of an electronic device provided in an embodiment of this application.

[0090] 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 software architecture of an electronic device includes at least three layers, from top to bottom: the application layer, the application framework layer, and the hardware abstraction layer.

[0091] The application layer may include a series of application packages. These application packages may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and SMS. In some embodiments of this application, the application layer may also include embedded window services, embedded window modules, and embedded window interface modules.

[0092] The embedded window module is used to implement the main functions of embedded window display interaction, including start / exit control, window display control, state synchronization, and event transmission.

[0093] The embedded window interface module is used to encapsulate the embedded window capability interface and provide it for the host process to call.

[0094] 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. For example... Figure 3 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc. The window manager is used to manage window programs. The window manager can obtain the screen size, determine if a status bar exists, lock the screen, capture the screen, etc. In some embodiments of this application, the application framework layer also includes an AMS module, a WMS module, and an embedded window interface set.

[0095] The AMS module is used to implement embedded Activity startup and lifecycle management.

[0096] The WMS module is used to implement embedded task management, control activity transitions within tasks, focus and visibility management of embedded window scenes, and configuration update and compatibility management.

[0097] The embedded window interface set is used to provide the system application with its own interface.

[0098] 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.

[0099] 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.

[0100] A phone manager is used to provide communication functions for electronic devices. For example, it manages call status (including connection and disconnection).

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

[0102] 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 completed downloads 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 electronic devices, and flashing indicator lights.

[0103] The hardware abstraction layer is the interface layer between the operating system kernel and the hardware circuit of the electronic device 200, and its purpose is to abstract the hardware.

[0104] For ease of understanding, the following embodiments of this application will be described using the following methods: Figure 2 and Figure 3 Taking the electronic device 200 with the structure shown as an example, and in conjunction with the accompanying drawings and application scenarios, the method for starting the application lock provided in this application embodiment will be specifically described.

[0105] Figure 4 This is a flowchart illustrating an application lock initiation method according to an embodiment of this application.

[0106] like Figure 4 As shown, the above-mentioned method for initiating the application lock may include:

[0107] Step S10: When a startup operation of the target application is detected, launch the embedded window in the currently displayed parent window according to the startup operation.

[0108] It should be noted that the launch operation can be to open the application by touch, gesture, or embedded window. The preset application lock interface can be displayed in full screen or according to the preset window size. Taking opening the application through an embedded window as an example, we will explain the operation.

[0109] In general, when users use high-frequency quick services such as scanning QR codes and payment codes, the operation is cumbersome. For example, they need to unlock the phone, open the application, and then select the corresponding service. When users use quick services while the screen is off, locked, or in application use, such as in online meetings or video calls, the operation is inconsistent and inconvenient. This embodiment provides embedded window display capabilities to the application window, supporting quick task cards to achieve efficient quick task window display. That is, during use, users can open the application through the embedded window by preset operations and directly use the quick service. The window system provides embedded window display and interaction capabilities, supports quick task cards, and facilitates users to use quick tasks efficiently.

[0110] In the specific implementation, in order to enable opening the application through an embedded window, such as... Figure 5 The diagram shows the display interface of an embedded window, where 10 represents the embedded window with the application loaded, and 20 represents the parent window. Figure 6 The diagram showing the module interaction of the embedded window startup process demonstrates that when the startup operation of the target application is detected, the host process business is triggered. The host process sends a request to establish a connection with the embedded window service to the embedded window service. The embedded window service sends a request to obtain the embedded window cross-process communication instance to the embedded window module. The embedded window module returns the embedded window cross-process communication instance to the embedded window service, and the embedded window service returns the embedded window cross-process communication instance to the host process, thereby realizing direct communication between the host process and the embedded window module.

[0111] After establishing a communication connection between the host process and the embedded window module, the host process first initializes and completes the drawing of the parent window. The specific drawing process is as follows: the host process sends an add parent window request to WMS, which includes placeholder image information and sends the window size of the parent window to the Graphics drawing module for window drawing. The host process also sends layer information to SurfaceFlinger for parent window layer composition. After the layer composition is completed, the parent window is displayed. Then, the host process sends a request to start the embedded window to the embedded window module. The request also includes startup parameters, including target window, window size, stack mode, touch mode, and Back mode. The target window represents the window of the corresponding application to be launched. The window size represents the size of the embedded window. The stack mode includes the application processing method in the embedded window, including new stack, unstack, and main stack reuse modes. The touch mode indicates whether the embedded window needs to have touch interactive controls. The Back mode indicates the application return processing method in the embedded window.

[0112] The embedded window module configures the target window, window mode, window size, embedded window flag, and stack mode based on the received startup parameters. The window mode indicates the display mode of the embedded window, including multi-window, picture-in-picture, or floating window modes. The embedded window flag identifies the window as embedded. The embedded window module sends the target window, window mode, window size, embedded window flag, and stack mode to the AMS module. The AMS module, based on the target window, sends the window mode and window size to the embedded application to launch the window. Then, it sends the embedded window flag and stack mode to the WMS module. The embedded application sends the window size to the WMS module to add the window. The WMS module then draws the window based on the window size and dimensions. The process of drawing the embedded window using the WMS module includes: the embedded application sends the window size to the Graphics drawing module; the Graphics drawing module notifies the WMS module after drawing is complete; the WMS module notifies the embedded window module that it has been created and transfers stack control to the embedded window module; the embedded window module then transfers stack control to the host process; and the host process performs layer composition to display the window. Specifically, the host process attaches a stack layer under SurfaceView and sends a configuration request to the SurfaceFlinger module to make the embedded application's stack layer visible. The SurfaceFlinger module then performs layer composition and, after completion, notifies the interaction module to display the interface, thus completing the startup of the embedded window.

[0113] Alternatively, the embedded window can launch as a floating window, then overlay the system card pack window on top, with a "hole" in the card pack window revealing the application interface underneath. This solution doesn't require additional window capabilities and achieves the card display effect with relatively little effort, but it has three main problems:

[0114] (1) Hierarchical Issues. There are other types of windows between the third-party application window and the card pack window; if these windows pop up, they will disrupt the card display. For example... Figure 7 The diagram shows other applications covering the embedded window. However, in this embodiment, since application switching is done through an embedded window, the third-party application window and the card pack window are basically at the same level, thus solving the layering problem.

[0115] (2) Task Management Issues. Directly using the main Task stack of third-party applications for card-style display causes interference between the Activity states in both card-style and full-screen modes, resulting in a poor user experience. For example, a user is chatting in WeChat and then brings up their wallet to display a WeChat payment code. The system switches WeChat to card mode and launches the payment code interface in the WeChat main Task stack. When the user completes the payment and returns to WeChat, it reverts to the home screen. This is because after WeChat exits card mode, the main Task is cleared to avoid remaining on the payment code interface, but this prevents the user from returning to their previous chat task.

[0116] In this embodiment, after the window is drawn, the control of the embedded window is forwarded to the host process through the embedded window module. The parent window determines the stack mode of the embedded window to ensure the normal use of the embedded window.

[0117] (3) Synchronization issues between system and application windows. Because the system card window and the third-party application window are "two separate entities" and lack necessary connections, it is not easy to perform association processing. If the adaptation is not comprehensive, some scenarios may experience state mismatch. As shown in Figure 8, there is a schematic diagram of the input interface covering the embedded window.

[0118] In this embodiment, after the window is drawn, the control of the embedded window is forwarded to the host process through the embedded window module. The parent window determines the window mode of the embedded window, ensuring the normal use of the embedded window.

[0119] Step S20: When displaying the embedded window application corresponding to the startup operation in the embedded window, obtain the preset display mode of the application lock interface according to the embedded window, wherein the embedded window is at the same level or adjacent level as the parent window, and the application displayed in the embedded window is associated with the parent window.

[0120] In this embodiment, the display mode of the application lock interface, i.e., the window mode, is specified by the embedded window module, such as... Figure 9 The module interaction diagram for launching the application lock window shown is basically the same as that for launching the embedded window. However, in this embodiment, the embedded window module obtains the preset display mode of the application lock interface, i.e., the window mode, specifies the display mode according to the configuration, and launches the embedded window through the AMS module. The AMS module then sends the display mode and window size to the embedded application to launch the embedded application window. This avoids determining the application lock interface based on the form of the launch interface, but instead displays the application lock interface through the preset display mode of the application lock interface, improving the flexibility of launching the application lock authentication interface.

[0121] Step S30: Display the application lock interface according to the preset display mode of the application lock interface.

[0122] In this embodiment, when the launch operation of the target application is detected, a preset display mode of the application lock interface is obtained according to the embedded window; the application lock interface is displayed according to the preset display mode of the application lock interface, so that the application lock interface can be displayed according to the preset display mode of the application lock interface without having to determine it according to the form of the launch interface, thereby improving the flexibility of the application lock authentication interface launch.

[0123] Figure 10 A flowchart illustrating an application lock initiation method provided in another embodiment of this application is shown below. Figure 10 As shown, the above-mentioned application lock activation method is based on the first embodiment, and the display mode includes full-screen display; step S30 includes:

[0124] Step S301: Display the application lock interface in full screen.

[0125] To avoid the app lock interface being incomplete, we've configured it for full-screen display to ensure proper viewing. Figure 11a The example shown demonstrates how to display a lock interface in full screen within an embedded window application, such as... Figure 11b The application lock interface shown is displayed in full screen.

[0126] In one possible implementation, step S10 includes:

[0127] Obtain the unlocking method of the application lock; determine the display mode of the application lock interface based on the unlocking method.

[0128] It should be noted that the interface of the app lock differs depending on the unlocking method. For example, fingerprint unlocking displays the fingerprint input interface in a fixed position, and unlocking is completed through the fingerprint input interface. Password unlocking also requires the display of an input box, which necessitates a larger input interface. Gesture unlocking is another example. Therefore, the corresponding display mode is determined based on the unlocking method to ensure the normal display of the app lock interface.

[0129] In one possible implementation, step S10 includes:

[0130] When the unlocking method is to unlock via a fixed unlock frame, the display mode of the application lock interface is determined to be full-screen display.

[0131] It's understandable that fingerprint unlocking, using a fixed unlock frame, is a viable unlocking method. Since the fingerprint unlock interface is displayed in a fixed position during fingerprint unlocking, if this interface isn't within an embedded window, it's impossible to guarantee that fingerprint unlocking events will be passed to the embedded window. Therefore, when fingerprint unlocking is the preferred method, the application lock interface's display mode is set to full-screen to ensure that fingerprint unlocking events are transmitted to the embedded window. Figure 12 The fingerprint unlock diagram shown shows that 30 represents the full-screen application lock interface, and 40 represents the fingerprint unlock interaction control.

[0132] In one possible implementation, obtaining the preset display mode of the application lock interface includes:

[0133] Determine whether to acquire the application lock launch flag; if the application lock launch flag is acquired, acquire the preset application lock interface display mode based on the application lock launch flag; if the application lock launch flag is not acquired, acquire the preset application lock interface display mode; and use the preset application lock interface display mode as the preset application lock interface display mode.

[0134] In this embodiment, the application lock interface can be displayed through the application lock display mode given by the Launcher of the quick service card, or through the preset display mode in the embedded window module. Alternatively, the preset application lock interface display mode can be obtained through other means. This embodiment does not limit this, and the application lock display mode given by the Launcher and the preset display mode in the embedded window module are used as examples for explanation.

[0135] In the specific implementation, the display mode is determined by the application lock's activation flag, indicating whether it is the application lock display mode given by the Launcher or the preset display mode in the embedded window module. If the application lock's activation flag is obtained, it means that the display mode is given by the Launcher; if the application lock's activation flag is not obtained, it means that the display mode is the preset display mode in the embedded window module. This improves the flexibility of the application lock interface display and meets the needs of different users.

[0136] In one possible implementation, after detecting the launch operation of the target application, the following is also included:

[0137] Save the component information corresponding to launching the target application; when the application lock is unlocked, retrieve the saved component information corresponding to launching the target application; launch the target application according to the saved component information corresponding to launching the target application.

[0138] It is understandable that, such as Figure 13As shown, when starting the application, it first determines whether the application is locked. If the application is locked, the startup Intent is saved and the application lock authentication interface is launched. If the application is unlocked, the application interface is launched directly. After the application lock authentication interface is launched and the authentication interface is successfully unlocked, the saved startup Intent is obtained and the application interface is launched through the saved startup Intent.

[0139] In one possible implementation, the target application is launched through an embedded window. For details, please refer to the description of opening the application through an embedded window above, thereby ensuring that the application lock interface is updated synchronously with the parent window.

[0140] Figure 14 A flowchart of an application lock initiation method provided in another embodiment of this application is shown below. Figure 14 As shown, the above-described application lock activation method is based on the first embodiment. Before step S20, it further includes:

[0141] Step S201: Determine whether the target application is locked.

[0142] It should be noted that not all applications have an application lock set when starting an application. When starting an application without an application lock, the application interface is launched directly. When starting an application with an application lock, the application lock interface is then set, thereby improving application processing efficiency.

[0143] In the specific implementation, to determine whether a target application is locked, a pre-configured list of applications with application locks is obtained; the target application is matched with the applications in the application list; when the target application matches the applications in the application list, the target application is determined to be locked; when the target application does not match the applications in the application list, the target application is determined to be unlocked. The pre-configured list of applications with application locks can also be in other forms, and this embodiment does not limit this, and the application list can be flexibly adjusted according to actual business needs.

[0144] In one possible implementation, before matching the target application with applications in the application list, the method further includes:

[0145] Determine if a screen-off event exists; if a screen-off event exists, re-acquire the pre-configured list of applications with application lock settings to obtain an updated list of applications; match the target application with the applications in the updated list of applications.

[0146] It should be noted that the pre-configured list of applications with application lock settings can be adjusted in real time according to user needs. The pre-configured list of applications with application lock settings can be used continuously during screen-on time. However, after a screen-off event, the pre-configured list of applications with application lock settings needs to be retrieved again to achieve real-time updates of the application list and ensure the accuracy of the determination of whether an application is locked.

[0147] When the target application is locked, step S20 is executed; when the target application is unlocked, step S202 is executed to directly start the target application.

[0148] In this embodiment, a pre-configured list of applications with application locks is obtained; the target application is matched with the applications in the list; when the target application matches the applications in the list, the target application is locked; when the target application does not match the applications in the list, the target application is unlocked. When starting an application without an application lock, the application interface is launched directly; when starting an application with an application lock, the application lock interface is determined, thereby improving application processing efficiency.

[0149] Figure 15 A schematic diagram of the structure of an application lock activation device 900 provided in this application is shown. The application lock activation device 900 provided in this application includes:

[0150] The startup module 901 is used to launch an embedded window in the currently displayed parent window according to the startup operation when a startup operation of the target application is detected.

[0151] The acquisition module 902 is used to acquire a preset application lock interface display mode according to the embedded window when the embedded window application corresponding to the startup operation is displayed in the embedded window, wherein the embedded window is at the same level or adjacent level as the parent window, and the application displayed in the embedded window is associated with the parent window.

[0152] The display module 903 is used to display the application lock interface according to the preset display mode of the application lock interface.

[0153] The application lock startup method provided in this application, in this embodiment, involves launching an embedded window in the currently displayed parent window when a startup operation of a target application is detected; when the embedded window application corresponding to the startup operation is displayed in the embedded window, a preset display mode of the application lock interface is obtained according to the embedded window, wherein the embedded window and the parent window are at the same level or adjacent level, and the application displayed in the embedded window is associated with the parent window; the application lock interface is displayed according to the preset display mode of the application lock interface, thereby enabling the application lock interface to be displayed according to the preset display mode of the application lock interface without needing to determine it based on the form of the startup interface, thus improving the flexibility of launching the application lock authentication interface.

[0154] In one possible implementation, the display mode includes full-screen display;

[0155] The display module 903 is also used to display the application lock interface in full screen.

[0156] In one possible implementation, the acquisition module 901 is further configured to acquire the unlocking method of the application lock;

[0157] The display mode of the application lock interface is determined based on the unlocking method.

[0158] In one possible implementation, the acquisition module 901 is further configured to determine that the display mode of the application lock interface is full-screen display when the unlocking method is unlocking through a fixed unlock frame.

[0159] In one possible implementation, the acquisition module 901 is further configured to determine whether to acquire the application lock's startup flag;

[0160] When the application lock's activation flag is obtained, the preset display mode of the application lock interface is obtained based on the application lock's activation flag.

[0161] In one possible implementation, the acquisition module 901 is further configured to acquire a pre-set display mode of the application lock interface when the application lock launch flag is not acquired.

[0162] Use the preset display mode of the application lock interface as the default display mode of the application lock interface.

[0163] In one possible implementation, the application lock activation device 900 further includes a activation module, which is used to store component information corresponding to the activation of the target application;

[0164] When the application lock is unlocked, the saved component information corresponding to launching the target application is retrieved;

[0165] The target application is launched based on the saved component information corresponding to the launch of the target application.

[0166] In one possible implementation, the startup module is further configured to launch the target application via an embedded window.

[0167] In one possible implementation, the acquisition module 901 is further configured to determine whether the target application is locked;

[0168] When the target application is locked, the step of obtaining the preset display mode of the application lock interface based on the embedded window is executed;

[0169] If the target application is not locked, start the target application directly.

[0170] In one possible implementation, the acquisition module 901 is further configured to acquire a pre-configured list of applications with application lock settings;

[0171] Match the target application with the applications in the application list;

[0172] When the target application matches an application in the application list, the target application is locked.

[0173] If the target application does not match any application in the application list, it is determined that the target application is not locked.

[0174] In one possible implementation, the acquisition module 901 is further configured to determine whether a screen-off event exists;

[0175] When a screen-off event occurs, the pre-configured list of applications with application lock settings is retrieved again to obtain an updated list of applications.

[0176] The target application is matched with applications in the updated application list.

[0177] It should be understood that the electronic equipment described here is embodied in the form of functional modules. The term "module" here can be implemented in software and / or hardware, without specific limitation. For example, a "module" can be a software program, hardware circuit, or a combination of both that implements the above-described functions. The hardware circuit may include application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors) and memory for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components that support the described functions.

[0178] This application also provides an electronic device, comprising: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions that, when executed by the electronic device, cause the electronic device to perform an application lock initiation method as described in any one of the first aspects or possible implementations of the first aspect above.

[0179] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform an application lock initiation method as described in any one of the first aspects or possible implementations thereof.

[0180] This application also provides a chip, the chip including a processor and a data interface, the processor reading instructions stored in a memory through the data interface to execute the application lock initiation method as described in any one of the first aspects or possible implementations of the first aspect.

[0181] Optionally, the chip may further include a memory storing instructions, and the processor is configured to execute the instructions stored in the memory. When the instructions are executed, the processor is configured to execute the application lock initiation method according to any one of the first aspects or possible implementations of the first aspect.

[0182] The memory can be read-only memory (ROM), other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types of dynamic storage devices that can store information and instructions. It can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices. Alternatively, it can be any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0183] In this embodiment, "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, the simultaneous existence of A and B, or the existence of B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following associated objects are in an "or" relationship. "At least one of the following" and 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, and c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0184] Those skilled in the art will recognize that the units and algorithm steps described in the embodiments disclosed herein can be implemented using electronic hardware, computer software, or a combination of electronic hardware and software. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0185] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0186] In the several embodiments provided in this application, any function, if implemented as a software functional unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0187] The above description is merely a specific embodiment of this application. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application. The protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for initiating an application lock, characterized in that, The method for initiating the application lock includes: When a launch operation of the target application is detected, an embedded window is launched in the currently displayed parent window according to the launch operation; When the target application corresponding to the launch operation is displayed in the embedded window, the display mode of the preset application lock interface is obtained according to the embedded window. The display mode of the preset application lock interface is different from the display mode of the embedded window. The display mode of the preset application lock interface is full screen display. The embedded window and the parent window are at the same level or adjacent level, and the target application displayed in the embedded window is associated with the parent window. Display the application lock interface in full screen; After successfully unlocking the application lock interface, the target application is launched through the embedded window, and the application interface of the target application is displayed in the embedded window.

2. The method for activating the application lock as described in claim 1, characterized in that, The process of obtaining the preset display mode of the application lock interface includes: Determine whether to acquire the application lock's startup flag; When the application lock's activation flag is obtained, the preset display mode of the application lock interface is obtained based on the application lock's activation flag.

3. The method for activating the application lock as described in claim 2, characterized in that, After determining whether to acquire the application lock's startup flag, the process further includes: If the application lock launch flag is not obtained, obtain the pre-set display mode of the application lock interface; Use the preset display mode of the application lock interface as the default display mode of the application lock interface.

4. The method for initiating an application lock as described in claim 1, characterized in that, After detecting the launch operation of the target application, the process further includes: Save the component information corresponding to launching the target application; When the application lock is unlocked, the saved component information corresponding to launching the target application is retrieved; The target application is launched based on the saved component information corresponding to the launch of the target application.

5. The method for activating the application lock as described in any one of claims 1 to 4, characterized in that, Before obtaining the preset display mode of the application lock interface based on the embedded window, the method further includes: Determine whether the target application is locked; When the target application is locked, the step of obtaining the preset display mode of the application lock interface based on the embedded window is executed; If the target application is not locked, start the target application directly.

6. The method for activating the application lock as described in claim 5, characterized in that, The determination of whether the target application is locked includes: Retrieve the pre-configured list of applications with application lock settings; Match the target application with the applications in the application list; When the target application matches an application in the application list, the target application is locked. If the target application does not match any application in the application list, it is determined that the target application is not locked.

7. The method for activating the application lock as described in claim 6, characterized in that, Before matching the target application with applications in the application list, the method further includes: Determine if a screen-off event has occurred; When a screen-off event occurs, the pre-configured list of applications with application lock settings is retrieved again to obtain an updated list of applications. The step of matching the target application with applications in the application list includes: The target application is matched with applications in the updated application list.

8. A locking device, characterized in that, The activation device for the application lock includes: The startup module is used to launch an embedded window in the currently displayed parent window according to the startup operation when a startup operation of the target application is detected. The acquisition module is used to acquire a preset application lock interface display mode according to the embedded window when the target application corresponding to the launch operation is displayed in the embedded window. The preset application lock interface display mode is different from the display mode of the embedded window. The preset application lock interface display mode is full-screen display. The embedded window and the parent window are at the same level or adjacent level, and the target application displayed in the embedded window is associated with the parent window. The display module is used to display the application lock interface in full screen, and after successfully unlocking the application lock interface, launch the target application through the embedded window and display the application interface of the target application in the embedded window.

9. An electronic device, characterized in that, include: One or more processors; Memory; And one or more computer programs, wherein the one or more computer programs are stored in the memory, the one or more computer programs including instructions that, when executed by the electronic device, cause the electronic device to perform the application lock activation method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to perform the application lock initiation method according to any one of claims 1 to 7.

Images