Method and device for realizing master screen mode and computer equipment

Abstract

The invention is applicable to the technical field of security, and provides a method and a device for realizing a master screen mode and computer equipment, the method comprises the following steps: acquiring a push message of a parameter template sent by a server, calling a download parameter service of a starter, requesting to download a parameter file, analyzing the parameter file based on the starter to obtain a package name of a master screen application, and sending the package name to the server; and starting a master screen application corresponding to the package name. According to the technical scheme, remote starting of the master screen application is achieved, physical intervention of operation and maintenance personnel is not needed, the limitation that in the prior art, master screen application starting is achieved under the condition that physical intervention is not needed is overcome, and remote configuration, updating and management of the master screen application and related settings of the master screen application are facilitated for the operation and maintenance personnel.

Description

Technical Field

[0001] The present application belongs to the field of security technology, and in particular relates to a method, device and computer equipment for implementing a screen dominance mode. Background Art

[0002] Existing technologies for managing the dominant screen mode of terminal devices, especially enabling the launch and exit of dominant screen applications without physical intervention, have certain limitations. This makes it difficult for operations personnel to remotely configure, update, and manage dominant screen applications and their related settings. Summary of the Invention

[0003] The embodiments of the present application provide a method, apparatus, and computer device for implementing a screen-dominating mode, which enables remote startup of a screen-dominating application without physical intervention by operation and maintenance personnel, thereby overcoming the limitations of the prior art in enabling startup of a screen-dominating application without physical intervention, and facilitating remote configuration, updating, and management of the screen-dominating application and its related settings by operation and maintenance personnel.

[0004] In a first aspect, an embodiment of the present application provides a method for implementing a screen dominance mode, including:

[0005] Get the push message of the parameter template sent by the server;

[0006] Call the launcher's download parameter service to request download parameter files;

[0007] Parsing the parameter file based on the launcher to obtain the package name of the screen-dominating application;

[0008] Start the screen-dominating application corresponding to the package name.

[0009] In a possible implementation of the first aspect, starting the screen-dominating application corresponding to the package name includes:

[0010] After the launcher is started, detecting whether it is in the screen dominating mode;

[0011] If in the above-mentioned screen dominating mode, call the API to disable the status bar and navigation bar, and do not load desktop icon data;

[0012] Start the screen-dominating application corresponding to the package name, and display the started interface on the desktop.

[0013] In a possible implementation of the first aspect, starting the screen-dominating application corresponding to the package name includes:

[0014] After the launcher is started, the application screen dominance function is initialized and the accessibility service permission is enabled;

[0015] Monitoring the package name of the foreground application based on the accessibility service permission;

[0016] If the package name of the foreground application matches the package name of the dominating screen application, the dominating screen mode is entered, the API is called to disable the status bar and navigation bar, and desktop icon data is not loaded;

[0017] Start the screen-dominating application corresponding to the package name, and display the started interface on the desktop;

[0018] If the package name in the foreground does not match the package name of the screen-dominating application, the regular interface will be displayed on the desktop.

[0019] In a possible implementation of the first aspect, the method further includes:

[0020] Monitoring user interface events based on the accessibility service permissions;

[0021] If a preset abnormal event is monitored, an event notification will be sent to the initiator;

[0022] After receiving the event notification, restart the screen-dominating application.

[0023] In a possible implementation of the first aspect, the preset abnormal event includes at least one of the following: an application crash pop-up window, an application unresponsive pop-up window, and the absence of a screen-dominating application process.

[0024] In a possible implementation of the first aspect, the method further includes:

[0025] After the launcher is started, the application's screen dominance function is initialized, the accessibility service permission is enabled, and the processor for exiting the screen dominance mode is initialized;

[0026] In the screen dominating mode, monitoring system events based on the accessibility service permission;

[0027] If a preset system event is monitored, the password keyboard of the screen domination mode is displayed; wherein the preset system event includes at least one of the following: a preset physical key event, a preset screen click event;

[0028] In response to a touch operation on the password keyboard, obtaining an input password;

[0029] The input password is matched with the preset password, and if they match, the screen dominating mode is exited.

[0030] In a possible implementation of the first aspect, the parameter template includes: a flag indicating whether to enable the screen dominating mode, a package name of the screen dominating application, an exit password, and an exit method.

[0031] In a second aspect, an embodiment of the present application provides a device for implementing a screen dominance mode, including:

[0032] The acquisition module is used to obtain the push message of the parameter template sent by the server;

[0033] The calling module is used to call the download parameter service of the launcher and request to download the parameter file;

[0034] A parsing module, configured to parse the parameter file based on the launcher to obtain a package name of the screen-dominating application;

[0035] The startup module is used to start the screen-dominating application corresponding to the package name.

[0036] In a third aspect, an embodiment of the present application provides a computer device comprising 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 method for implementing the screen-dominating mode described in any one of the first aspects above is implemented.

[0037] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the method for implementing the screen-dominating mode described in any one of the first aspects above.

[0038] In a fifth aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on a computer device, it enables the computer device to execute the method for implementing the screen-dominating mode described in any one of the above-mentioned first aspects.

[0039] Compared with the prior art, the beneficial effects of the embodiments of the present application are: obtaining a push message of the parameter template sent by the server, calling the download parameter service of the launcher, requesting to download the parameter file, parsing the parameter file based on the launcher to obtain the package name of the screen-dominating application, and starting the screen-dominating application corresponding to the package name. Among them, the device can obtain the parameter file based on the parameter template information pushed by the server, and automatically download and parse the parameter file through the launcher, and finally start the specified screen-dominating application. This process not only improves the flexibility and adaptability of the device, but also reduces the need for manual intervention, improves the operation and maintenance efficiency and the operation stability of the device. At the same time, this remote configuration and dynamic update mechanism overcomes the limitations of the prior art in realizing the startup and management of screen-dominating applications without physical intervention, and provides a more convenient and efficient management method for operation and maintenance personnel.

[0040] It can be understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0042] Figure 1 This is a flowchart of a method for implementing the screen dominance mode provided in one embodiment of the present application;

[0043] Figure 2 This is a flow chart of parameter template push parsing and setting provided by an embodiment of the present application;

[0044] Figure 3 This is a flowchart for starting the screen dominance mode provided by an embodiment of the present application;

[0045] Figure 4 This is a flowchart of a method for implementing the screen dominance mode provided in one embodiment of the present application;

[0046] Figure 5 This is a schematic diagram of the process of handling abnormal events provided by an embodiment of the present application;

[0047] Figure 6 This is a schematic diagram of the process of entering and exiting the screen dominating mode provided in an embodiment of the present application;

[0048] Figure 7 This is a flowchart of installing and automatically starting a screen-dominating application to enter screen-dominating mode according to an embodiment of the present application;

[0049] Figure 8 Schematic diagram of the structure of the device for implementing the screen dominance mode provided in an embodiment of the present application;

[0050] Figure 9 It is a structural diagram of the computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] In the following description, specific details such as specific system structures and techniques are provided for purposes of illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obscuring the description of the present application with unnecessary detail.

[0052] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or collections thereof.

[0053] It will also be understood that the term "and / or" used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

[0054] As used in this specification and the appended claims, the term "if" can be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.

[0055] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0056] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.

[0057] Figure 1 A schematic flowchart of a method for implementing a screen dominating mode provided in an embodiment of the present application is shown.

[0058] S101, obtaining a push message of a parameter template sent by a server.

[0059] Among them, the above-mentioned server represents the Terminal Management System (TMS) server. Configure the parameter template on the TMS server. The parameter template may include a flag indicating whether to enable the dominance mode, the package name of the dominance application (a unique identifier used to identify the dominance application), an exit password (used to verify the user's identity when exiting the dominance mode), and an exit method (a method for triggering the exit from the dominance mode, such as a physical button combination or a screen click event). Among them, the flag indicating whether to enable the dominance mode is a key parameter, which determines whether the device enters the dominance mode when it starts.

[0060] The TMS client obtains the push message of the parameter template sent by the server.

[0061] S102: calling the download parameter service of the initiator to request download of the parameter file.

[0062] The launcher, which can be called the "home screen" or "desktop manager," is the first interface for users to interact with Android devices (hereinafter referred to as devices). Its main function is to provide an interactive interface for users, responsible for displaying desktop icons, launching applications, and other functions. In this application, the launcher can also be extended to parse parameter files and launch dominant applications.

[0063] In this embodiment of the present application, after receiving a push message, the initiator's parameter download service is invoked, and a parameter file download request is sent to the TMS server via the established communication connection. After receiving the download request, the TMS server determines the parameter file to be sent. The TMS server then sends the parameter file back to the initiator.

[0064] The parameter file is a specific configuration file generated based on a parameter template. It contains parameter values ​​customized for a specific device or application scenario. The parameter file is typically generated by the TMS server based on the parameter template and the user's specific configuration. After the operations and maintenance personnel configure the parameter template on the TMS server, the TMS server generates a specific parameter file based on these configurations. The launcher parses the parameter file to obtain the specific configuration information for the dominance mode, thereby correctly launching and controlling the dominance application. The parameter template is the basis for generating the parameter file. The TMS server generates the parameter file based on the parameter template and the user's specific configuration information. The parameter file is a specific instance of the parameter template and contains parameter values ​​customized for a specific device or application scenario. The parameter template defines the configuration requirements for the dominance mode, while the parameter file concretizes these configuration requirements so that they can be understood and executed by the launcher on the device. The parameter file is a specific application of the parameter template, converting abstract configuration requirements into specific configuration instructions.

[0065] S103: Parse the parameter file based on the launcher to obtain the package name of the screen-dominating application.

[0066] In the Android system, a package name is a string that uniquely identifies an application. It's like an application's "ID number" and must be unique across the entire system. For apps that dominate the screen, the package name is particularly important, as it ensures the device can accurately identify and launch the correct app.

[0067] In this embodiment of the present application, the package name of the dominating application is dynamically configured using a parameter file pushed by the server. This means that operations personnel can modify the package name of the dominating application on the server and push it to the device via the parameter file. The device's launcher parses the parameter file, obtains the latest package name of the dominating application, and launches the corresponding dominating application based on that package name.

[0068] Optionally, package name uniqueness and dynamic configuration mechanisms ensure that only authorized screen-dominating apps can be launched on the device. This prevents unauthorized apps from being launched, thereby enhancing device security.

[0069] S104: Start the screen-dominating application corresponding to the package name.

[0070] In an embodiment of the present application, the launcher checks the package name in the parameter file when it starts, and starts the specified screen-dominating application by calling the API of the Android system.

[0071] In an embodiment of the present application, a push message of a parameter template sent by the server is obtained, the download parameter service of the launcher is called, a request is made to download a parameter file, the parameter file is parsed based on the launcher to obtain the package name of the screen-dominating application, and the screen-dominating application corresponding to the package name is started. Among them, the device can obtain the parameter file based on the parameter template information pushed by the server, and automatically download and parse the parameter file through the launcher, and finally start the specified screen-dominating application. This process not only improves the flexibility and adaptability of the device, but also reduces the need for manual intervention, improves the operation and maintenance efficiency and the operation stability of the device. At the same time, this remote configuration and dynamic update mechanism overcomes the limitations of the existing technology in realizing the startup and management of screen-dominating applications without physical intervention, and provides a more convenient and efficient management method for operation and maintenance personnel.

[0072] For the push of parameter templates, please refer to Figure 2 The following is a flow chart of the parameter template push parsing and setting process. Figure 2As shown, the device implementing the screen domination mode may include a TMS server and a device. The device may include a launcher, a TMS client, and a screen domination application. It is understood that the TMS server may refer to an application running on the server, and the TMS client and launcher may refer to applications running on the device. The TMS client maintains a communication connection with the TMS server, receives instructions (such as push messages), and provides feedback on device status. Through the linkage between the TMS client and the TMS server, the screen domination mode can be controlled.

[0073] The push process may mainly include steps a to g, which are described in detail below.

[0074] Step a: The user configures the parameter template on the TMS server.

[0075] On the TMS server, users (such as operations personnel) configure parameter templates through the management interface. Users can create multiple different parameter templates and store them on the TMS server. Parameter templates include a flag indicating whether to enable the dominance mode, the package name of the dominance application, and the exit password and method.

[0076] Step b: The TMS server sends a push message of the parameter template to the TMS client.

[0077] In some implementations, the TMS server may periodically send push messages. In other embodiments, the TMS server sends a push message to the TMS client upon detecting a change in the parameter template.

[0078] Step c: In response to the received push message, the TMS client invokes the download parameter service of the initiator to request download of the parameter file.

[0079] In step d, the initiator requests the TMS server to download the parameter file.

[0080] In some implementations, parameter files can be pushed using a reliable network transmission protocol, such as Hypertext Transfer Protocol Secure (HTTPS). A retry mechanism can be implemented in the TMS client to ensure that parameter files can be re-requested when the network is unstable. In other implementations, a message queue or push service can be used to ensure that parameter files are pushed to the launcher in a timely manner and that the launcher can correctly receive and parse the parameter files.

[0081] In step e, the TMS server returns the parameter file to the initiator.

[0082] In step f, the initiator performs parsing and storage of the parameter file.

[0083] In some implementations, parameter parsing logic is implemented in the launcher to ensure that the parameter file can be correctly parsed. For example, the parameter file can be parsed using Extensible Markup Language (XML). Local storage (such as SharedPreferences or SQLite database) can be used to store the parsed remote configuration parameters for subsequent use.

[0084] Step g: The launcher starts the screen-dominating application corresponding to the package name based on the package name of the screen-dominating application obtained after parsing the parameter file.

[0085] In an embodiment of the present application, through the linkage between the TMS server and the TMS client, the operation and maintenance personnel can flexibly configure and update the parameter template of the dominance mode on the server, and push it to the device in real time. This dynamic configuration mechanism enables the device to run the dominance mode according to the latest parameter settings without manual intervention, which greatly improves management efficiency and flexibility. In addition, the device can adjust the settings of the dominance mode according to the parameter template information received from the server. The same device can quickly switch between different dominance applications according to different usage scenarios or needs, which enhances the adaptability and scalability of the device. For example, the same device can run a payment application in a retail payment scenario and switch to a ticketing application in a transportation ticketing scenario. In addition, through dynamic configuration and automated management, the device can quickly respond to instructions from the server and switch to the correct dominance application in a timely manner. This seamless switching mechanism reduces user waiting time and improves user experience.

[0086] In an optional embodiment, S104 starting the screen-dominating application corresponding to the package name specifically includes:

[0087] Step a1: After the launcher is started, detect whether it is in the screen dominating mode.

[0088] In the embodiment of the present application, the launcher checks the locally stored configuration information (such as the "flag indicating whether to enable the dominance mode" obtained by parsing the parameter file downloaded from the TMS server) when it starts. By checking the flag, the device can determine whether it needs to enter the dominance mode, avoiding unnecessary operations.

[0089] The flag indicating whether to enable or disable Dominate Screen mode is a key parameter that determines whether the device enters Dominate Screen mode at startup. The specific process is as follows: The device parses the "Dominate Screen mode enable flag" from the parameter file downloaded from the server. The launcher checks the value of this flag at startup. If the flag is true, the launcher disables the status bar and navigation bar, does not load desktop icon data, and launches the designated Dominate Screen application, entering Dominate Screen mode. If the flag is false, the launcher loads the normal desktop interface, and the device does not enter Dominate Screen mode.

[0090] Step a2: If the device is in the screen dominating mode, call the API to disable the status bar and navigation bar, and do not load desktop icon data.

[0091] In an embodiment of the present application, after confirming that the device is in the screen-dominating mode, the launcher can call a preset API (the API can be a pre-customized interface by the manufacturer) to disable the status bar and navigation bar. At the same time, the launcher does not load desktop icon data to ensure that the user cannot access other applications or system settings. Among them, by disabling the status bar and navigation bar, the user cannot exit the screen-dominating application or access other applications in a conventional way, thereby enhancing the security of the device. The device interface is simplified to only display the screen-dominating application, and the user can only focus on the current task, reducing the possibility of misoperation. Not loading desktop icon data prevents users from launching other applications through desktop icons, further limiting the user's operating scope and preventing malicious operations.

[0092] Step a3: start the screen-dominating application corresponding to the package name, and display the started interface on the desktop.

[0093] In an embodiment of the present application, the launcher starts the specified dominating screen application according to the parsed dominating screen application package name. After startup, the dominating screen application interface will cover the desktop and become the currently displayed interface. Among them, the device can automatically start the specified dominating screen application according to the configuration without the need for manual operation by the user, thereby improving the degree of automation of the device. The interface of the dominating screen application is directly displayed on the desktop, and the user can enter the application without additional operation, thereby improving the user experience. Through the automatic startup mechanism, the device can immediately enter the dominating screen mode after powering on or restarting, reducing startup failures or delays caused by manual operations.

[0094] In an optional embodiment, combined with Figure 3 The startup flow chart of the screen dominating mode shown in FIG. 1 shows, S104 starts the screen dominating application corresponding to the package name and specifically includes:

[0095] Step b1: The user turns on the computer, the system starts, and the launcher starts.

[0096] In an embodiment of the present application, the user presses the power button of the device, the system completes startup, and the launcher is loaded and started as a desktop manager.

[0097] Among them, after the launcher is started, the application screen dominance function is initialized and the accessibility service permission is enabled.

[0098] In an embodiment of the present application, after the launcher is started, the application screen dominance function is initialized and the accessibility service permission is enabled.

[0099] Initialize the dominance screen function, and the launcher loads the configuration information related to the dominance screen mode, such as the package name of the dominance screen application.

[0100] Enable the accessibility service permission. The launcher requests and obtains the accessibility service permission. The accessibility service is a service provided by the Android system to assist users in operating the device, such as obtaining specific events, including package name changes of the foreground application and crash pop-ups.

[0101] Step b2: monitor the package name of the foreground application based on the accessibility service permission and determine whether the dominance mode has been entered, that is, check whether the dominance mode is enabled.

[0102] In an embodiment of the present application, the launcher monitors the package name of the application currently in the foreground through the accessibility service, compares the package name of the foreground application with the package name of the screen-dominating application parsed from the parameter file, and determines whether they match.

[0103] Step b3: If the package name in the foreground matches the package name of the screen-dominating application, enter the screen-dominating mode (i.e., the screen-dominating mode is enabled), call the preset API to disable the status bar and navigation bar, and do not load desktop icon data.

[0104] In this embodiment of the present application, if the package name of the foreground application matches the package name of the dominating application, the launcher confirms that the device needs to enter dominating mode. The launcher calls a preset API to disable the status bar and navigation bar, preventing the user from exiting the dominating application or accessing other applications through these interfaces. The launcher does not load desktop icon data, restricting the user from accessing other applications and ensuring that the device is focused on running the dominating application.

[0105] Step b4: start the screen-dominating application corresponding to the package name, and display the started interface on the desktop.

[0106] In this embodiment of the application, the application dominance function is initialized first, and then the launcher can start the specified dominance application through Intent based on the parsed dominance application package name. After the dominance application is started, its interface covers the desktop and becomes the currently displayed interface. The user can only interact with the dominance application.

[0107] Step b5: If the package name in the foreground does not match the package name of the screen-dominating application, the regular interface is displayed on the desktop.

[0108] In an embodiment of the present application, if the package name of the foreground application does not match the package name of the dominant application, the launcher confirms that the device does not need to enter dominant mode. The launcher loads and displays the normal desktop interface, and the user can use the desktop icons and other applications like a normal device.

[0109] Through these operations, the device dynamically decides whether to enter dominant screen mode based on parameters pushed from the server. When in dominant screen mode, it disables the status bar and navigation bar and loads the designated dominant screen application, ensuring the device is fully focused on running the specific application. This mechanism is suitable for a variety of unattended application scenarios, such as retail payment, transportation ticketing, and public services, effectively ensuring the secure operation and efficient management of the device.

[0110] In an optional embodiment, the method for implementing the screen-dominating mode also includes: monitoring events of the user interface based on the accessibility service permission; if a preset abnormal event is monitored, sending an event notification to the launcher; after receiving the event notification, restarting the screen-dominating application.

[0111] Among them, the preset abnormal events include at least one of the following: application crash pop-up window, application unresponsive pop-up window, and non-existence of the screen-dominating application process.

[0112] In order to facilitate the understanding of the solution of this embodiment, Figure 4 The flowchart of the implementation method of the dominance mode is described in detail. This flowchart shows the complete logic of the dominance mode from startup to exit, including key steps such as exception handling and application installation. Specifically:

[0113] 1) The user presses the power button on the device and the system begins booting. After the system finishes booting, the launcher starts.

[0114] 2) Initialization of the application screen dominance function in the launcher (also known as Figure 4 Initialize the dominance mode (initialize the dominance mode), enable accessibility service permissions for auxiliary functions, such as monitoring changes in the foreground application. Initialize the exit dominance mode processor, which is used to handle the logic of exiting the dominance mode.

[0115] 3) The accessibility service within the launcher monitors changes in the foreground app's package name and determines whether to enter dominant mode. If the foreground app's package name matches the preset dominant app's package name, the launcher determines that dominant mode is necessary. The launcher calls a preset API to disable the status bar and navigation bar to prevent the user from exiting the dominant app through these interface elements. Simultaneously, the launcher does not load desktop icon data, preventing the user from accessing desktop icons and further restricting user operations.

[0116] 4) If the foreground app is not the dominant screen app, the launcher does not perform any dominant screen mode-related operations, allowing the user to use the device normally.

[0117] 5) After entering the dominance mode, the launcher starts the designated dominance application, and the dominance application starts and displays the interface. When the dominance application already exists, the accessibility service monitors application abnormal events and sends event notifications to the launcher. The launcher processes the abnormal events after detecting them. That is, if the dominance application crashes, becomes unresponsive, or other abnormalities occur, the dominance application can be restarted. At the same time, the accessibility service monitors physical button triggers and screen click triggers, and sends event notifications to the launcher. After detecting the corresponding events, the launcher prompts the user to enter a password, and exits the dominance mode after verifying that the password is correct. If the dominance application does not exist, the launcher processes the installation logic of the dominance application. After the dominance application is installed, it performs the corresponding logic processing and starts the application.

[0118] Among them, combined Figure 5 The figure shows a flowchart of the processing flow of preset abnormal events, which describes in detail the steps of how to handle application abnormal situations after the device enters the dominance screen mode.

[0119] 1) The user launches the dominating app by clicking on a desktop icon or in the recent apps list. Upon receiving the user's action, the launcher launches the dominating app. After the dominating app launches, it sends a confirmation message to the launcher, indicating that the app has been launched. After confirming the launch of the dominating app, the launcher enters dominating mode.

[0120] 2) In Dominate Screen mode, the launcher detects abnormalities in the app, including:

[0121] Crash handling: After the launcher detects the app crash pop-up window, it restarts the screen-dominating app. After the screen-dominating app restarts, it sends a confirmation message to the launcher.

[0122] No response (ANR) processing: After the launcher detects that the application has no response pop-up window, it restarts the screen-dominating application. After the screen-dominating application restarts, it sends a confirmation message to the launcher.

[0123] Process survival detection: The launcher checks whether the dominating application process is alive at regular intervals. If it detects that the dominating application process does not exist, the launcher will restart the dominating application. After the dominating application is restarted, it will send a confirmation message to the launcher.

[0124] Launcher fallback page detection: The launcher launches a fallback page to restart the dominating app when it exits. If the dominating app exits, the fallback page calls its onResume method. Upon detecting the dominating app's exit, the fallback page restarts it. After the dominating app restarts, it sends a confirmation message to the launcher. This fallback page detection is based on the Android Activity back stack and Activity lifecycle mechanisms. When the dominating app exits, the onResume lifecycle method of the launcher fallback page is triggered. Upon detecting this event, the fallback page immediately calls the dominating app.

[0125] Among them, in the dominance mode, the accessibility service monitors physical button triggers and screen click triggers, and sends event notifications to the launcher. After the launcher detects the corresponding event, the launcher controls the pop-up of the password keyboard to exit the dominance mode.

[0126] Among them, in the dominance mode, the launcher detects abnormal events and handles them. That is, if the dominance application crashes, becomes unresponsive, or encounters other abnormalities, the launcher will automatically try to restore the dominance application to ensure the stability of the application.

[0127] Among them, in the screen dominating mode, the launcher regularly checks whether the process of the screen dominating application is still running. If it is detected that the process of the screen dominating application does not exist, the launcher will automatically restart the screen dominating application.

[0128] Among them, in the screen-dominating mode, the launcher detects the system's application installation events. Once it detects that the screen-dominating application is installed, the launcher will configure the system to achieve self-starting after the application is installed.

[0129] In the embodiment of the present application, the above process ensures that the device can automatically enter the dominating screen mode after booting up, start the specified dominating screen application, and automatically handle when an abnormality occurs in the dominating screen application. By detecting the crash, unresponsiveness and process survival status of the application, it can respond and restart the dominating screen application in time, thereby ensuring that the user experience during use is not affected.

[0130] In an optional embodiment, the implementation method of the dominance mode also includes: after the launcher is started, initializing the application dominance function and enabling the accessibility service permission and initializing the exit of the dominance mode processor; in the dominance mode, monitoring system events based on the accessibility service permission; if a preset system event is monitored, displaying the password keyboard of the dominance mode; wherein the preset system event includes at least one of the following: a preset physical key event, a preset screen click event; the launcher obtains the input password in response to the touch operation of the password keyboard; and matches the input password with the preset password, and if they match, exits the dominance mode.

[0131] For ease of understanding, here we combine Figure 6 The diagram of the process of entering and exiting the dominance mode is shown. After the dominance mode is turned on, the user clicks on the desktop icon or the recent application list page in the launcher to start the dominance application. After the dominance application is started, the accessibility service monitors the change of the foreground application package name and sends an event notification to the launcher. The launcher detects that the foreground application is a dominance application, enters the dominance mode, and disables the status bar and navigation bar. In the dominance mode, the accessibility service sends an event notification to the launcher. The launcher detects the corresponding event, such as the volume plus and minus buttons are pressed simultaneously for more than a certain time, and the dominance mode password keyboard pops up. In the dominance mode, the launcher detects a click event in the middle of the status bar. If the continuous click exceeds a certain number of times, the dominance mode password keyboard pops up. In the dominance mode, the user enters a password. If the password is correct, the dominance mode is exited.

[0132] The specific technical implementation methods are as follows:

[0133] 1) Launching a dominating app: The user launches the dominating app by clicking its desktop icon or the recent apps list in the launcher. After launching the dominating app, the accessibility service detects changes in the foreground app's package name and sends an AccessibilityEvent notification to the launcher. The launcher, upon detecting that the foreground app is the dominating app, enters dominating mode and calls a pre-defined API to disable the status bar and navigation bar.

[0134] 2) Volume button trigger: In Dominate Screen mode, the accessibility service sends a KeyEvent event notification to the launcher. The launcher detects the corresponding event, such as the volume up and down buttons being pressed simultaneously. If the volume up and down buttons are pressed for more than a certain period of time, the Dominate Screen mode password keyboard pops up.

[0135] 3) Other key triggers: In Dominate Screen mode, the accessibility service sends a KeyEvent event notification to the launcher, and the launcher detects that a specific key has been pressed. If a specific key is pressed, the Dominate Screen mode password keyboard pops up.

[0136] 4) Status bar click trigger: In the dominance mode, the launcher detects a click event in the middle of the status bar. If the number of consecutive clicks exceeds a certain number, the dominance mode password keyboard will pop up.

[0137] 5) Password verification: The user enters the password, and the launcher verifies the password. If the password is correct, the system exits the dominance mode.

[0138] In an embodiment of the present application, after receiving an event, the launcher identifies the foreground application as a screen-dominating application, automatically enters the screen-dominating mode, and calls a preset API to disable the status bar and navigation bar without manual intervention, thereby achieving automation and rapid switching of the screen-dominating mode and improving the user experience.

[0139] Furthermore, in Domination mode, the launcher pops up the Domination mode password keypad by detecting various trigger events, including: volume button trigger (pressing the volume up and down buttons simultaneously for a certain period of time), other button trigger (pressing a specific button), and status bar click trigger (continuously clicking the center of the status bar for a certain number of times). These flexible trigger mechanisms provide users with multiple ways to exit Domination mode while preventing accidental exits caused by misoperation. By configuring different trigger methods, the needs of different scenarios can be met, enhancing the system's adaptability and security.

[0140] In addition, in the dominance mode, the launcher uses password verification to ensure that only authorized users can exit the dominance mode, enhancing the security of the system and preventing unauthorized access and operation.

[0141] pass Figure 6 As shown in the schematic diagram of the process of entering and exiting the screen-dominating mode, combined with the specific technical implementation method, this solution realizes the automated management of the screen-dominating mode, provides a flexible exit mechanism, enhances the security and stability of the system, improves the user experience, and simplifies operation and maintenance management.

[0142] In an optional embodiment, combined with Figure 7 The diagram below illustrates the process of entering Dominant Mode after a Dominant App is installed and automatically launched. It describes the process: the user installs the Dominant App. After installation, the launcher detects the app installation event and launches the Dominant App. After the Dominant App is launched, the accessibility service monitors for changes in the foreground app's package name and sends an event notification. The launcher detects that the foreground app is the Dominant App and enters Dominant Mode.

[0143] The specific technical implementation methods are as follows:

[0144] 1) The user installs a screen-dominating app. The launcher detects the screen-dominating app installation event by registering the LauncherApps app change callback. The launcher then starts the screen-dominating app.

[0145] 2) After launching the dominant app, the accessibility service monitors changes in the foreground app's package name and sends an AccessibilityEvent notification. If the launcher detects that the foreground app is the dominant app, it enters dominant mode.

[0146] In the embodiment of the present application, the above operations achieve automatic installation and startup of the screen-dominating application, as well as automatic entry into the screen-dominating mode. This automated process improves the ease of use and management efficiency of the device, especially in scenarios where screen-dominating applications need to be quickly deployed and used. The collaborative work of the accessibility service and the launcher ensures that the screen-dominating application can run stably in the foreground, providing a safe, stable, and user-friendly screen-dominating solution.

[0147] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0148] Corresponding to the implementation method of the screen dominance mode described in the above embodiment, Figure 8 A structural block diagram of an implementation device for the screen dominance mode provided in an embodiment of the present application is shown. For ease of explanation, only the parts related to the embodiment of the present application are shown.

[0149] Reference Figure 8 , the implementation device of the screen dominating mode includes:

[0150] The acquisition module is used to obtain the push message of the parameter template sent by the server;

[0151] The calling module is used to call the download parameter service of the launcher and request to download the parameter file;

[0152] A parsing module, configured to parse the parameter file based on the launcher to obtain a package name of the screen-dominating application;

[0153] The startup module is used to start the screen-dominating application corresponding to the package name.

[0154] In a possible implementation, the startup module is configured to:

[0155] After the launcher is started, detecting whether it is in the screen dominating mode;

[0156] If in the above-mentioned screen dominating mode, call the API to disable the status bar and navigation bar, and do not load desktop icon data;

[0157] Start the screen-dominating application corresponding to the package name, and display the started interface on the desktop.

[0158] In a possible implementation, the startup module is configured to:

[0159] After the launcher is started, the application screen dominance function is initialized and the accessibility service permission is enabled;

[0160] Monitoring the package name of the foreground application based on the accessibility service permission;

[0161] If the package name of the foreground application matches the package name of the dominating screen application, the dominating screen mode is entered, the API is called to disable the status bar and navigation bar, and desktop icon data is not loaded;

[0162] Start the screen-dominating application corresponding to the package name, and display the started interface on the desktop;

[0163] If the package name in the foreground does not match the package name of the screen-dominating application, the regular interface will be displayed on the desktop.

[0164] In a possible implementation, the device for implementing the screen dominating mode further includes a restart module, which is configured to:

[0165] Monitoring user interface events based on the accessibility service permissions;

[0166] If a preset abnormal event is monitored, an event notification will be sent to the initiator;

[0167] After receiving the event notification, restart the screen-dominating application.

[0168] In a possible implementation, the preset abnormal event includes at least one of the following: an application crash pop-up window, an application unresponsive pop-up window, and the absence of a screen-dominating application process.

[0169] In a possible implementation, the device for implementing the screen dominating mode further includes an exit module, which is configured to:

[0170] After the launcher is started, the application's screen dominance function is initialized, the accessibility service permission is enabled, and the processor for exiting the screen dominance mode is initialized;

[0171] In the screen dominating mode, monitoring system events based on the accessibility service permission;

[0172] If a preset system event is monitored, the password keyboard of the screen domination mode is displayed; wherein the preset system event includes at least one of the following: a preset physical key event, a preset screen click event;

[0173] In response to a touch operation on the password keyboard, obtaining an input password;

[0174] The input password is matched with the preset password, and if they match, the screen dominating mode is exited.

[0175] In a possible implementation, the parameter template includes: a flag indicating whether to enable the screen dominating mode, the package name of the screen dominating application, an exit password, and an exit method.

[0176] It should be noted that the information interaction, execution process and other contents between the above modules are based on the same concept as the method embodiment of this application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0177] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0178] An embodiment of the present application also provides a computer device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor implements the steps of any of the above-mentioned method embodiments when executing the computer program.

[0179] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned various method embodiments can be implemented.

[0180] An embodiment of the present application provides a computer program product. When the computer program product is run on a computer device, the computer device can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0181] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the process of the above-mentioned method embodiment by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, it can implement the steps of each of the above-mentioned method embodiments. The computer program includes computer program code, which can be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium can at least include: any entity or device capable of carrying computer program code to the camera / terminal device, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal, and software distribution medium. For example, a USB flash drive, mobile hard drive, magnetic disk, or optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals or telecommunication signals.

[0182] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0183] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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.

[0184] In the embodiments provided in this application, it should be understood that the disclosed apparatus / computer equipment and methods can be implemented in other ways. For example, the apparatus / computer equipment embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of the apparatus or unit, which can be electrical, mechanical or other forms.

[0185] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0186] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

[0187] Figure 9 This is a schematic diagram of the structure of a computer device provided in one embodiment of the present application. Figure 9 As shown, the computer device of this embodiment includes: at least one processor 20 ( Figure 9 Only one is shown), a memory 21, and a computer program 22 stored in the memory 21 and executable on the at least one processor 20, wherein the processor 20 implements the steps in the above-mentioned implementation method of any of the above-mentioned screen dominating modes when executing the computer program 22.

[0188] The computer device may include, but is not limited to, a processor 20 and a memory 21. Those skilled in the art will understand that Figure 9 The computer device is merely an example and does not constitute a limitation on the computer device. The computer device may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the computer device may also include input and output devices, network access devices, etc.

[0189] The processor 20 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor or any conventional processor.

[0190] In some embodiments, the memory 21 may be an internal storage unit of the computer device, such as a hard disk or memory of the computer device. In other embodiments, the memory 21 may also be an external storage device of the computer device, such as a plug-in hard disk equipped on the computer device, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Furthermore, the memory 21 may also include both an internal storage unit of the computer device and an external storage device. The memory 21 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as the program code of the computer program. The memory 21 may also be used to temporarily store data that has been output or is to be output.

[0191] The relevant user personal information that may be involved in the various embodiments of this application is strictly in accordance with the requirements of laws and regulations, following the principles of legality, legitimacy and necessity, and based on the reasonable purposes of business scenarios, to process the personal information that users actively provide during the use of products / services or generated due to the use of products / services, as well as the personal information obtained with the user's authorization.

Claims

1. A method for implementing a screen dominance mode, characterized in that: include: Get the push message of the parameter template sent by the server; Call the launcher's download parameter service to request download parameter files; Parsing the parameter file based on the launcher to obtain the package name of the screen-dominating application; Start the screen-dominating application corresponding to the package name.

2. The method for implementing the screen dominating mode according to claim 1, wherein: The starting of the screen-dominating application corresponding to the package name includes: After the launcher is started, detecting whether it is in the screen dominating mode; If in the above-mentioned screen dominating mode, call the API to disable the status bar and navigation bar, and do not load desktop icon data; Start the screen-dominating application corresponding to the package name, and display the started interface on the desktop.

3. The method for implementing the screen dominating mode according to claim 1, wherein: The starting of the screen-dominating application corresponding to the package name includes: After the launcher is started, the application screen dominance function is initialized and the accessibility service permission is enabled; Monitoring the package name of the foreground application based on the accessibility service permission; If the package name of the foreground application matches the package name of the dominating screen application, the dominating screen mode is entered, the API is called to disable the status bar and navigation bar, and desktop icon data is not loaded; Start the screen-dominating application corresponding to the package name, and display the started interface on the desktop; If the package name in the foreground does not match the package name of the screen-dominating application, the regular interface will be displayed on the desktop.

4. The method for implementing the screen dominating mode according to claim 3, wherein: The method further comprises: Monitoring user interface events based on the accessibility service permissions; If a preset abnormal event is monitored, an event notification will be sent to the initiator; After receiving the event notification, restart the screen-dominating application.

5. The method for implementing the screen dominating mode according to claim 4, wherein: The preset abnormal events include at least one of the following: application crash pop-up window, application unresponsive pop-up window, and non-existence of the screen-dominating application process.

6. The method for implementing the screen dominating mode according to claim 1, wherein: The method further comprises: After the launcher is started, the application's screen dominance function is initialized, the accessibility service permission is enabled, and the processor for exiting the screen dominance mode is initialized; In the screen dominating mode, monitoring system events based on the accessibility service permission; If a preset system event is monitored, the password keyboard of the screen domination mode is displayed; wherein the preset system event includes at least one of the following: a preset physical key event, a preset screen click event; In response to a touch operation on the password keyboard, obtaining an input password; The input password is matched with the preset password, and if they match, the screen dominating mode is exited.

7. The method for implementing the screen dominating mode according to claim 1, wherein: The parameter template includes: a flag indicating whether to enable the screen dominating mode, the package name of the screen dominating application, an exit password, and an exit method.

8. A device for implementing a screen dominance mode, characterized in that: include: The acquisition module is used to obtain the push message of the parameter template sent by the server; The calling module is used to call the download parameter service of the launcher and request to download the parameter file; A parsing module, configured to parse the parameter file based on the launcher to obtain a package name of the screen-dominating application; The startup module is used to start the screen-dominating application corresponding to the package name.

9. A computer device, characterized in that: The method comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images