Lock screen control methods, devices, equipment and storage media
By storing a lock screen command table in electronic devices, the lock screen state is automatically controlled according to the operating system type, solving the problem of complex operation caused by different lock screen shortcut keys for different operating systems, realizing convenient one-click lock screen and improving user experience.
Patent Information
- Application Number
- CN202310343052.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-03-31
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-03-31
AI Technical Summary
Because different operating systems have different lock screen shortcuts, users need to confirm the operating system running on their electronic devices and then look up the corresponding keyboard commands, which makes the operation complicated and inconvenient.
By pre-storing a lock screen instruction table, the lock screen state is automatically controlled according to the type of operating system running on the first device, including receiving lock screen trigger information, determining the target lock screen instruction, and controlling the device to enter the lock screen state.
It enables one-click screen locking without requiring user confirmation of operating system type, improving user experience, offering high convenience, and simplifying the operation process.
Smart Images

Figure CN116700647B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a screen lock control method, apparatus, device and storage medium. Background Technology
[0002] Currently, electronic devices can be powered on / off, restarted, and have their screens locked via a Keyboard Video Mouse (KVM) control platform. Locking the screen requires the user to input keyboard commands corresponding to the operating system on the KVM display interface.
[0003] However, since different operating systems have different lock screen shortcuts, the operator needs to confirm the operating system running on the electronic device in order to look up the corresponding keyboard commands, which is complicated and inconvenient. Summary of the Invention
[0004] This application provides a screen lock control method, device, equipment, and storage medium that can pre-store the type of operating system running on a first device, thereby automatically controlling the first device to lock the screen based on the type of operating system, which is highly convenient and improves the user experience.
[0005] In a first aspect, embodiments of this application provide a screen lock control method, the method comprising:
[0006] Determine the screen lock trigger information;
[0007] Based on the screen lock trigger information and the pre-stored screen lock instruction table, a target screen lock instruction corresponding to the operating system type currently running on the first device is determined; the screen lock instruction table indicates the screen lock instructions corresponding to different operating system types.
[0008] Based on the target screen lock command, the first device is controlled to enter the screen lock state.
[0009] According to this solution, by pre-storing a lock screen command table, lock screen commands corresponding to different operating system types can be stored. Furthermore, given the lock screen trigger information, based on the type of operating system currently running on the first device and the lock screen command table, the recognizable lock screen commands of the operating system running on the first device can be determined, thereby automatically controlling the first device to enter the system lock screen state. This method offers high convenience and improves the user experience.
[0010] In one possible implementation, determining the screen lock trigger information includes:
[0011] The system receives screen lock trigger information from a second device. This screen lock trigger information is generated when the user interacts with the screen lock controls displayed on the second device. The screen lock trigger information is used to indicate screen lock.
[0012] In this way, the system can automatically control the first device to enter the system lock screen state with one click, which is highly convenient and improves the user experience.
[0013] In one possible implementation, determining the screen lock trigger information includes:
[0014] When the duration of the first device's display interface remaining stationary exceeds a threshold, screen lock trigger information is determined.
[0015] In this way, the duration of the same static interface displayed on the first device can be used to automatically control the first device to enter the system lock screen state, which is highly convenient and improves the user experience.
[0016] In one possible implementation, the method further includes:
[0017] During the power-on process of the first device, the type of operating system currently running on the first device is determined;
[0018] Store the type of operating system currently running on the first device.
[0019] In this way, the type of operating system running on the first device can be determined during the power-on process of the first device, and then stored. This allows the first device to be controlled to enter the lock screen state based on the type of operating system running on the first device when the lock screen trigger information is determined. This is highly convenient and improves the user experience.
[0020] In one possible implementation, determining the type of operating system that the first device will run includes:
[0021] Displays the selection options for the multiple operating systems;
[0022] Based on user input, the operating system running on the first device is determined from the multiple operating system selection options;
[0023] Based on the operating system running on the first device, determine the type of operating system currently running on the first device.
[0024] Thus, when the first device has multiple operating systems installed, the user selects the operating system to be run on the first device, thereby determining the type of operating system and storing the type of operating system running on the first device. This allows the first device to enter the lock screen state based on the type of operating system running on the first device when the lock screen trigger information is determined, which is highly convenient and improves the user experience.
[0025] In one possible implementation, the method further includes:
[0026] Display the lock screen command configuration interface, which is used to display parameter configuration options for various types of operating systems;
[0027] Based on the user's configuration input, the corresponding lock screen command for each type of operating system is determined to obtain the lock screen command table.
[0028] Secondly, embodiments of this application provide a screen lock control method, including:
[0029] Display user interface, the user interface including lock screen control;
[0030] Received user input for the lock screen control;
[0031] In response to the user's operation, a screen lock trigger message is sent to the first device to cause the first device to enter a screen lock state.
[0032] According to this solution, users can remotely control the first device to enter the system lock screen state with one click, which is highly convenient and improves the user experience.
[0033] Thirdly, embodiments of this application provide a screen lock control device, the device comprising:
[0034] The information determination module is used to determine the screen lock trigger information;
[0035] The instruction determination module is used to determine the target lock screen instruction corresponding to the operating system type currently running on the first device based on the lock screen trigger information and a pre-stored lock screen instruction table; the lock screen instruction table indicates the lock screen instructions corresponding to different operating system types.
[0036] The control module is used to control the first device to enter the lock screen state based on the target lock screen command.
[0037] According to this solution, by pre-storing a lock screen command table, lock screen commands corresponding to different operating system types can be stored. Furthermore, given the lock screen trigger information, based on the type of operating system currently running on the first device and the lock screen command table, the recognizable lock screen commands of the operating system running on the first device can be determined, thereby automatically controlling the first device to enter the system lock screen state. This method offers high convenience and improves the user experience.
[0038] In one possible implementation, the determining module is used to receive screen lock trigger information sent by the second device. The screen lock trigger information is information generated by the user operating the screen lock control displayed on the second device, and the screen lock trigger information is used to indicate screen lock.
[0039] In this way, the system can automatically control the first device to enter the system lock screen state with one click, which is highly convenient and improves the user experience.
[0040] In one possible implementation, the determining module is used to determine screen lock trigger information when the duration of the detected static state of the first device's display interface exceeds a threshold.
[0041] In this way, the duration of the same static interface displayed on the first device can be used to automatically control the first device to enter the system lock screen state, which is highly convenient and improves the user experience.
[0042] In one possible implementation, the device further includes:
[0043] The type determination module is used to determine the type of the operating system currently running on the first device during the power-on process of the first device;
[0044] The storage module is used to store the type of operating system currently running on the first device.
[0045] In this way, the type of operating system running on the first device can be determined during the power-on process of the first device, and then stored. This allows the first device to be controlled to enter the lock screen state based on the type of operating system running on the first device when the lock screen trigger information is determined. This is highly convenient and improves the user experience.
[0046] In one possible implementation, the determining module is configured to:
[0047] Displays the selection options for the multiple operating systems;
[0048] Based on user input, the operating system running on the first device is determined from the multiple operating system selection options;
[0049] Based on the operating system running on the first device, determine the type of operating system currently running on the first device.
[0050] Thus, when the first device has multiple operating systems installed, the user selects the operating system to be run on the first device, thereby determining the type of operating system and storing the type of operating system running on the first device. This allows the first device to enter the lock screen state based on the type of operating system running on the first device when the lock screen trigger information is determined, which is highly convenient and improves the user experience.
[0051] In one possible implementation, the device further includes:
[0052] The display module is used to display the lock screen command configuration interface, which is used to display parameter configuration options for various types of operating systems;
[0053] The instruction determination module is used to determine the lock screen instruction corresponding to each type of operating system based on the user's configuration input, so as to obtain the lock screen instruction table.
[0054] Fourthly, embodiments of this application provide a screen lock control device, including:
[0055] A display module is used to display a user interface, which includes a lock screen control.
[0056] A receiving module is used to receive user operations on the lock screen control;
[0057] The sending module is used to respond to the user operation by sending screen lock trigger information to the first device so that the first device enters the screen lock state.
[0058] According to this solution, users can remotely control the first device to enter the system lock screen state with one click, which is highly convenient and improves the user experience.
[0059] Fifthly, embodiments of this application provide an electronic device, including:
[0060] At least two memory locations are required for storing the program;
[0061] At least two processors are configured to execute a program stored in the memory, wherein when the program stored in the memory is executed, the processors are configured to perform the method provided in the first aspect.
[0062] Sixthly, embodiments of this application provide a screen lock control device that executes computer program instructions to perform the methods provided in the first aspect or the second aspect. Exemplarily, the device may be a chip or a processor.
[0063] In one example, the device may include a processor that may be coupled to memory, read instructions from the memory, and execute the methods provided in the first aspect or the second aspect according to those instructions. The memory may be integrated into the chip or processor, or it may be independent of the chip or processor.
[0064] In a seventh aspect, embodiments of this application provide a computer storage medium storing instructions that, when executed on a computer, cause the computer to perform the method provided in the first aspect or the method provided in the second aspect.
[0065] Eighthly, embodiments of this application provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the method provided in the first aspect or the method provided in the second aspect. Attached Figure Description
[0066] Figure 1 This is a schematic diagram illustrating a control server entering the system lock screen according to an embodiment of this application;
[0067] Figure 2 This is a schematic diagram of the architecture of a screen lock control system provided in an embodiment of this application;
[0068] Figure 3 This is a flowchart illustrating a screen lock control method provided in an embodiment of this application;
[0069] Figure 4a This is a schematic diagram of a one-click screen lock interface provided in an embodiment of this application;
[0070] Figure 4b This is a schematic diagram of the interface of a first device entering the system lock screen according to an embodiment of this application;
[0071] Figure 4c This is a schematic diagram of an interface for configuring lock screen commands provided in an embodiment of this application;
[0072] Figure 5 This is a flowchart illustrating another screen lock control method provided in an embodiment of this application;
[0073] Figure 6 This is a flowchart illustrating another screen lock control method provided in an embodiment of this application;
[0074] Figure 7 This is a flowchart illustrating another screen lock control method provided in an embodiment of this application;
[0075] Figure 8a This is a schematic diagram of the structure of a screen lock control device provided in an embodiment of this application;
[0076] Figure 8b This is a schematic diagram of another screen lock control device provided in an embodiment of this application;
[0077] Figure 9 This is a schematic diagram of the structure of a first device provided in an embodiment of this application. Detailed Implementation
[0078] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings.
[0079] In the description of the embodiments of this application, the words "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the words "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a specific manner.
[0080] In the description of the embodiments in this application, the term "and / or" is merely a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, B existing alone, and A and B existing simultaneously. Furthermore, unless otherwise stated, the term "multiple" means two or more. For example, multiple systems refer to two or more systems, and multiple terminals refer to two or more terminals.
[0081] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. The terms "comprising," "including," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.
[0082] like Figure 1As shown, in some application scenarios, users can power on or off the operating system of the first device 102 through the virtual KVM control platform 101. The virtual KVM control platform communicates with the Baseboard Management Controller (BMC) 102-1 in the first device 102 via a network. Users send a screen lock command to the BMC via a screen lock shortcut key through the virtual KVM control platform. The BMC sends a keyboard combination event to the operating system via a Universal Serial Bus (USB), thereby controlling the first device to enter a system screen lock state. For example, if a user sends the Win+L key combination to a Microsoft Windows operating system running on a server, the server will enter a system screen lock state. The operating system sends encoded data through a Digital Visual Interface (DVI), causing the BMC to send data to the KVM terminal. The operating system information is then displayed on the second device where the KVM client is located. Users communicate with the BMC through the KVM terminal to control the operating system.
[0083] However, since different operating systems have different lock screen shortcuts, users need to confirm the operating system running on the first device in order to look up the corresponding keyboard commands, which is not very convenient.
[0084] Based on this, embodiments of this application provide a screen lock control method, apparatus, device, and storage medium. By pre-storing a screen lock command table, the screen lock commands corresponding to different operating system types are determined. Furthermore, given the screen lock trigger information, based on the type of operating system currently running on the first device and the screen lock command table, the recognizable screen lock commands of the operating system currently running on the first device can be determined, thereby automatically controlling the first device to enter the system screen lock state. This offers high convenience and improves the user experience. This is merely a brief description of the method; for detailed information, please refer to the description below.
[0085] The following section introduces the lock screen control system to which the lock screen control method provided in the embodiments of this application may be applied. Figure 2 This diagram illustrates an example architecture of a screen lock control system provided in an embodiment of this application. The screen lock control method provided in this application can be applied to, for example... Figure 2 In the lock screen control system shown. For example... Figure 2 As shown, the screen lock control system includes a first device 21 and a second device 22 where the KVM client is located.
[0086] Users can lock the screen of the first device 21 with one click through the second device 22. After receiving the one-click screen lock command sent by the second device 22, the first device 21 converts the one-click screen lock command according to the type of operating system running on the first device 21, converting the one-click screen lock command into a command that the operating system can recognize, thereby automatically controlling the first device to enter the system screen lock state.
[0087] In some embodiments, such as Figure 2 As shown, the hardware of the first device 21 includes an out-of-band controller 211, a processor 212, a storage unit 213, and memory 214. The software of the first device includes an out-of-band management module, processor firmware, an operating system (OS) management unit, and an operating system. The out-of-band management module is located within the out-of-band controller, the OS management unit is located within the processor, and the processor firmware may be located within the processor (e.g.,...). Figure 1 (as shown), or the processor firmware can also be located on a firmware chip outside the processor ( Figure 1 (Not shown in the image) The operating system resides in the storage unit. The out-of-band management module can be a management unit for non-business modules. For example, the out-of-band management module can remotely maintain and manage the first device through a dedicated data channel. This out-of-band management module is completely independent of the first device's operating system and can communicate with the Basic Input Output System (BIOS) and the OS (or OS management unit) through the first device's out-of-band management interface.
[0088] Exemplarily, the processor firmware (also known as the processor firmware program) can be firmware, basic input output system (BIOS), management engine (ME), microcode, or intelligent management unit (IMU), etc. It should be noted that the specific form of the processor firmware in this application is not limited; the above is merely illustrative. In the following embodiments, only the BIOS as the processor firmware is used as an example for explanation.
[0089] Here, the BIOS is a set of programs embedded in the processor. The BIOS stores the basic input / output programs for the first device, the power-on self-test (POST) program, and the system boot program. The BIOS can read and write system configuration information. The main function of the BIOS is to provide low-level hardware settings and control for the first device. For example, in the following embodiment, the BIOS can determine the types of all operating systems installed on the first device.
[0090] Exemplary examples show that an out-of-band management module may include a management unit for the operating status of a computer device, a management system in a management chip outside the processor, a baseboard management controller (BMC), a system management mode (SMM), etc. It should be noted that the specific form of the out-of-band management module is not limited in the embodiments of this application; the above is merely illustrative. In the following embodiments, only a BMC is used as an example of an out-of-band management module for explanation.
[0091] BMC is a small operating system independent of the primary device's operating system. BMC has its own firmware system with its own Internet Protocol Address (IP). The primary device typically uses BMC commands for large-scale unattended operations, including remote management, monitoring, installation, and restarting of servers.
[0092] In this embodiment of the application, the out-of-band management controller can call the BMC to perform one of the steps (such as S504 and S505) in the following embodiments.
[0093] For example, the storage unit may include multiple disks. At least one operating system is installed in the storage unit. When the first device is running, the processor invokes the operating system to control the operation of software and hardware resources in the first device, thereby implementing corresponding functions. For example, this could be a system software program that organizes human-computer interaction with the user.
[0094] In this application embodiment, the first device 202 may be, but is not limited to, a server, etc. Exemplary embodiments of the first device involved in this solution include, but are not limited to, a first device running iOS, Android, Windows, Harmony OS, or other operating systems. This application embodiment does not specifically limit the type of the first device.
[0095] In one example, the server involved in this solution can be used to provide cloud services. It can be a server capable of establishing communication connections with other devices and providing computing and / or storage functions for those devices, or a hyperterminal. The server involved in this solution can be a hardware server or embedded in a virtualization environment. For example, the server involved in this solution can be a virtual machine running on a hardware server that includes one or more other virtual machines.
[0096] The second device 22 communicates with the first device 21 via a network. The network can be a wired network or a wireless network. For example, a wired network can be a cable network, a fiber optic network, a Digital Data Network (DDN), etc., while a wireless network can be a telecommunications network, an intranet, the Internet, a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a Metropolitan Area Network (MAN), a Public Service Telephone Network (PSTN), a Bluetooth network, a ZigBee network, a Global System for Mobile Communications (GSM), a CDMA (Code Division Multiple Access) network, a CPRS (General Packet Radio Service) network, etc., or any combination thereof. Understandably, a network can use any known network communication protocol to enable communication between different client layers and gateways. These network communication protocols can be various wired or wireless communication protocols, such as Ethernet, Universal Serial Bus (USB), FireWire, 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), New Radio (NR), Bluetooth, Wireless Fidelity (Wi-Fi), and other communication protocols.
[0097] The above describes one possible implementation of the screen lock control system provided in the embodiments of this application. The screen lock control system provided in the embodiments of this application can also be implemented in other ways, such as including only the first device.
[0098] Next, the screen lock control method provided in the embodiments of this application will be described in detail.
[0099] Figure 3 This is a flowchart illustrating a screen lock control method provided in an embodiment of this application. The screen lock control method provided in this embodiment can be applied to a first device, such as a BMC within that device. Figure 3 As shown, the screen lock control method provided in this application embodiment may include the following steps S301, S302 and S303.
[0100] S301, confirm screen lock trigger information.
[0101] The screen lock trigger information is used to indicate that the first device needs to enter the system screen lock state.
[0102] In some embodiments, the screen lock trigger information may be screen lock trigger information received from a second device.
[0103] In one example of this embodiment, the second device displays a user interface including a lock screen control. The second device receives user input to the lock screen control and sends lock screen trigger information to the first device. Optionally, the second device has a client installed, which is used to run functions related to the first device, such as the KVM function of the BMC in the first device. For example, ... Figure 4a As shown, the interface of the second device can display the lock screen control 41. The second device displays the system parameters of the first device. When the user clicks the lock screen control 41, the first device can receive the target lock screen event, thereby completing the one-click lock screen. The first device enters the system lock screen state, and the second device turns off the screen and no longer displays the interface related to the client's functions.
[0104] In another example based on this embodiment, the second device detects that the duration for which the display interface of the first or second device has been in a static state exceeds a threshold, determines screen lock trigger information, and sends the screen lock trigger information to the first device. Here, "static state" refers to a state without user operation. Even if the second device (or the first device) has no user operation but its dynamic wallpaper or clock changes produce "dynamic" effects, this also constitutes a static state. For example, such as... Figure 4b As shown, if the interface displaying system parameters on the second device has not been operated by the user for more than 15 minutes and has been in a static state for 15 minutes, then the second device determines the screen lock trigger information and sends it to the first device, and the first device receives the screen lock trigger information.
[0105] In other embodiments, the screen lock trigger information can be determined when the first device detects that the display interface of the first device or the second device has been in a static state for a duration exceeding a threshold. In response to this screen lock trigger information, the first device is instructed to enter a screen lock state. Here, a static state refers to a state without user operation. Even if the second device (or the first device) has no user operation but its dynamic wallpaper or clock changes create a "dynamic" effect, this also constitutes a static state. For example, if the first device detects that the second device displays the parameter configuration interface of the first device's operating system for more than 15 minutes, and that the parameter configuration interface has not been operated by the user and remains static for those 15 minutes, then the first device determines the screen lock trigger information.
[0106] Optionally, if the first device is in a system lock screen state, the second device will not display an interface related to the client's functions.
[0107] S302, based on the lock screen trigger information and the pre-stored lock screen instruction table, determine the target lock screen instruction corresponding to the operating system type currently running on the first device; the lock screen instruction table indicates the lock screen instructions corresponding to different operating system types.
[0108] The first device stores a screen lock command table, which records the screen lock commands corresponding to different operating system types. In other words, the screen lock command table indicates the correspondence between operating system types and screen lock commands. For example, a screen lock command can be a single command, as shown in Table 1. Specifically, the screen lock command for SUSE is Ctrl+Alt+L, for Windows it is Win+L, for Ubuntu it is Super+L, for Red Hat it is Ctrl+Alt+L, and for the Community Enterprise Operating System (CentOS) it is Ctrl+Alt+L.
[0109] Table 1
[0110] operating system Lock screen commands SUSE ctrl+alt+l Windows Win+L Ubuntu Super + L REDHAT ctrl+alt+l centos ctrl+alt+l
[0111] When pre-configured trigger conditions are met, the first device determines the target lock screen command corresponding to the running operating system from the lock screen command table, based on the type of the running operating system. For example, if the operating system running on the first device is not Windows, then the target lock screen command is Win+L.
[0112] In this embodiment, the lock screen command table is pre-configured in the first device. As one possible implementation, the first device can display a lock screen command configuration interface via a second device. This interface includes parameter configuration options for various operating systems. Users can configure different lock screen commands for different operating systems via the second device, thereby obtaining the lock screen command table. For example, as shown... Figure 4c As shown, the second device displays parameter configuration options for various types of operating systems. The user fills in the lock screen command corresponding to each operating system into the parameter configuration options, thereby causing the first device to generate a lock screen command table, as shown in Table 1.
[0113] In some embodiments, the BMC determines the target screen lock command based on the type of the operating system. For example, the BMC stores a screen lock command table and the type of the running operating system. When the BMC receives a one-click screen lock command sent by the virtual KVM control platform, it determines the corresponding screen lock command for that operating system from the screen lock command table based on the type of the operating system.
[0114] In other embodiments, the operating system in the first device may be configured with an agent program to control the operating system's screen lock. Upon meeting pre-configured triggering conditions, the agent program determines the target screen lock command based on the operating system type. For example, the first device stores a screen lock command table, and the agent program stores a pre-configured parameter for the operating system type. When the operating system receives a one-click screen lock command, the agent program can call the screen lock command table to convert the one-click screen lock command into a command that the operating system can recognize, thereby causing the first device to enter a system screen lock state.
[0115] In some embodiments, prior to S301, the first device can obtain the type of the operating system currently running. Specifically, when the first device is powered on, it determines the type of the operating system to be started, and the started operating system is the operating system that the first device wants to run.
[0116] As one possible implementation, the first device guides the user to select the operating system to boot. Specifically, after the first device powers on, a second device displays multiple operating system selection options, allowing the user to choose the desired operating system. For example, after the first device powers on, the BIOS can poll all disks with installed operating systems to obtain the type information of the operating systems installed on the first device, and send this information to the second device, which then displays multiple operating system options.
[0117] After receiving the user's target input, the first device can then determine the type of operating system to be launched. Here, the target input may carry an operating system identifier, representing the user's selection of the operating system type. Once the first device determines the operating system type, it stores the operating system type as a variable within the first device, such as in the BMC (Browser Control Center).
[0118] For example, when the first device is powered on, the BIOS obtains the type of the operating system being booted and sends it to the BMC via the Intelligent Platform Management Interface (IPMI). This allows the BMC to store the type of the operating system running on the first device as a variable. Thus, when pre-configured trigger conditions are met, the BMC can determine the target lock screen command corresponding to that operating system from the lock screen command table based on the stored operating system type.
[0119] S303 controls the first device to enter the lock screen state according to the target lock screen command.
[0120] The first device can transmit a target lock screen command to the operating system, thereby controlling the first device to enter the system lock screen state. Specifically, the target lock screen command is a command that the operating system can recognize, and upon receiving the target lock screen command, the operating system responds to the target lock screen command and enters the system lock screen state.
[0121] According to the embodiments of this application, a lock screen command table is pre-stored to store lock screen commands corresponding to different operating system types. Furthermore, given the lock screen trigger information, based on the type of operating system currently running on the first device and the lock screen command table, the recognizable lock screen commands of the operating system currently running on the first device can be determined, thereby automatically controlling the first device to enter the system lock screen state. This provides high convenience and improves the user experience.
[0122] Based on the above embodiments, the following will be carried out... Figure 2 The lock screen control system shown herein provides a detailed description of exemplary embodiments of the lock screen control method provided in this application.
[0123] Figure 5 This is a flowchart illustrating a screen lock control method provided in an embodiment of this application. The screen lock control scheme provided in this embodiment can be applied to... Figure 2 In the lock screen control system of the corresponding embodiment. For example... Figure 5 As shown, the screen lock control method provided in this application embodiment includes the following steps S501 to S508.
[0124] S501, the first device has at least one operating system installed.
[0125] The first device can have at least one operating system installed. Different operating systems can be installed on the same disk, on different disks, or some operating systems can be installed on the same disk.
[0126] In this embodiment, a user can control the first device to install an operating system via a second device. For example, the second device can display an interface for installing the operating system, and the user can control the first device to install the operating system through this interface. For example, the second device can display disks that can be used to install the operating system. The user can select the disk to install the operating system on via the second device.
[0127] Here, during the installation of the operating system on the disk, the first device can generate operating system type information and save it to the disk where the operating system is installed. This operating system type information indicates the type of operating system installed on the disk, such as the operating system version.
[0128] As one possible implementation, the type information can be recorded in a file, for example, in an EFI format file.
[0129] S502, when the first device is powered on, the BIOS determines the type of operating system to boot.
[0130] In some embodiments, when the first device is powered on, the user can select the type of operating system to be booted via the second device, thereby enabling the BIOS to determine the type of operating system to be booted.
[0131] Specifically, during power-up, the BIOS polls all disks to obtain information about the type of operating system installed on each disk. The BIOS sends this information to the BMC (Browser Control Center), which then displays multiple operating system options via a second device. These options represent different types of operating systems. The user selects the desired operating system from these options. Based on the user's selection, the BMC sends the selected operating system type back to the BIOS, allowing the BIOS to determine the type of operating system to boot.
[0132] As one possible implementation, the BIOS can communicate with the BMC through the IPMI interface to exchange information, such as sending all operating system type information to the BMC through the IPMI interface.
[0133] S503, the BIOS sends the type of operating system to be booted to the BMC.
[0134] After the first device is powered on, the operating system selected by the user starts, and then the BIOS sends feedback to the BMC about the type of operating system to be started.
[0135] S504, the type of operating system running in the BMC storage first device.
[0136] The operating system that is started is the operating system that the first device will run.
[0137] S505, BMC receives a one-click screen lock command sent by the second device.
[0138] Users can send a one-click screen lock command to the BMC via a second device.
[0139] S506, upon receiving a one-click screen lock command, the BMC retrieves the screen lock command table based on the type of operating system running on the first device to determine the target screen lock command.
[0140] The lock screen command table shows the correspondence between the operating system type and the lock screen commands.
[0141] Lock screen command list and Figure 3 The screen lock command table involved in S301 in the embodiments is the same. For details, please refer to the detailed description of the screen lock command table in the specific description of S301. It will not be repeated here.
[0142] As one possible implementation, the lock screen commands corresponding to different operating system types in the lock screen command table can be information pre-configured by the user. For example, the user can configure lock screen commands corresponding to various operating systems through a second device, and then configure the lock screen command table into the BMC.
[0143] The pre-configured trigger conditions are the same as those involved in S301. For details, please refer to the detailed description of S301 for the specific explanation of the trigger conditions. They will not be repeated here.
[0144] Here, users do not need to confirm the type of operating system running in their system; they can simply send a screen lock command to the BMC with a single click.
[0145] S507, BMC sends a target screen lock command to the operating system running on the first device.
[0146] S508, the operating system running in the first device responds to the target lock screen command and enters the system lock screen state.
[0147] According to the embodiments of this application, users can enter the system lock screen state by locking the screen with one click, without having to confirm the operating system type in the first device or remember the keyboard events corresponding to different types of operating systems, thus improving convenience.
[0148] Here, S501-S508 are merely exemplary descriptions of the screen lock control method provided in the embodiments of this application. The screen lock control method provided in the embodiments of this application may also include other possible implementations, which can be found in the following documents. Figure 3 The detailed descriptions of S301 to S303 in the embodiments will not be repeated here.
[0149] Figure 6 This is a flowchart illustrating a screen lock control method provided in an embodiment of this application. The screen lock control method provided in this embodiment can be applied to... Figure 2 In the lock screen control system of the corresponding embodiment. For example... Figure 6 As shown, the screen lock control method provided in this application embodiment includes the following steps S601 to S604. Here, before S601, the screen lock control method provided in this application embodiment further includes S501 to S504, which can be found in detail below. Figure 5 The detailed descriptions of S501 to S504 in the corresponding embodiments will not be repeated here.
[0150] S601, BMC detects the duration for which the target interface is displayed on the first device.
[0151] S602, if the duration of the first device displaying the target interface exceeds a preset duration threshold, the BMC retrieves the lock screen instruction table based on the type of the operating system being run to obtain the target event instruction.
[0152] S603, BMC sends the target time instruction to the operating system.
[0153] S604, the operating system running in the first device responds to the target lock screen command and enters the system lock screen state.
[0154] In this application, the BMC can automatically control whether the operating system enters the system lock screen state by detecting the duration of the first device's display interface, solving the problem that users need to remember complicated system lock screen key combinations, which is highly convenient and improves the user experience.
[0155] Figure 7 This is a flowchart illustrating a screen lock control method provided in an embodiment of this application. The screen lock control method provided in this embodiment can be applied to... Figure 2 In the lock screen control system of the corresponding embodiment. For example... Figure 7 As shown, the screen lock control method provided in this application embodiment includes the following steps S701 to S705.
[0156] S701, BMC receives a one-click screen lock command sent by the second device.
[0157] The second device can communicate with the BMC, allowing the user to send a one-click screen lock command to the BMC via the second device.
[0158] S702, BMC forwards the one-click screen lock command to the agent program in the operating system.
[0159] In S703, the agent program in the operating system responds to the one-click screen lock command by calling the screen lock command table.
[0160] The lock screen command table can be configured in the agent program or in other components on the first device capable of storing information. After receiving a one-click lock screen command, the agent program runs and invokes the lock screen command table. Here, the lock screen command table is related to... Figure 3 The lock screen command table involved in the corresponding embodiments is the same; please refer to [link / reference] for details. Figure 3 The detailed description of the screen lock command table in the embodiments will not be repeated here.
[0161] As one possible implementation, the lock screen instruction table can be pre-collected and configured in the agent.
[0162] As another possible implementation, the lock screen command table can be stored in the BMC; for details, please refer to [link / reference needed]. Figure 5 The detailed description of S506 in the embodiments will not be repeated here. The agent program in the operating system can request to call the screen lock command table from the BMC.
[0163] S704, the agent program in the operating system determines the lock screen commands that the operating system can recognize from the lock screen command table.
[0164] In S705, the agent program in the operating system controls the first device to lock the system screen.
[0165] According to the embodiments of this application, when a user locks the screen with one click on the terminal, the screen locking operation can be performed through the agent program at the bottom layer of the operating system. Thus, the user only needs to trigger the screen lock with one click to achieve the purpose of locking the system screen, which is convenient and improves the user experience.
[0166] Based on the same concept as the embodiments of the method in this application, this application also provides a screen lock control device. The screen lock control device includes several modules, each module being used to execute various steps in the screen lock control method provided in the embodiments of this application. The division of modules is not limited here. Those skilled in the art will clearly understand that in practical applications, the various steps in the screen lock control method provided in the embodiments of this application can be assigned to different modules as needed, that is, the internal structure of the device can be divided into different modules to complete all or part of the functions described above. The modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more modules can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the modules in the above device can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.
[0167] For example, the screen lock control device is used to perform the actions described in the embodiments of this application. Figure 3 The corresponding implementation provides a screen lock control method.
[0168] Figure 8a This is a schematic diagram of the screen lock control device provided in an embodiment of this application. The screen lock control device provided in this embodiment is applied to a first device. Figure 8a As shown, the screen lock control device provided in this application embodiment includes an information determination module 801, an instruction determination module, and a control module 803.
[0169] Information determination module 801 is used to determine screen lock trigger information;
[0170] The instruction determination module 802 is used to determine the target lock screen instruction corresponding to the operating system type currently running on the first device based on the lock screen trigger information and the pre-stored lock screen instruction table; the lock screen instruction table indicates the lock screen instructions corresponding to different operating system types;
[0171] The control module 803 is used to control the first device to enter the lock screen state based on the target lock screen command.
[0172] According to this solution, by storing the type of operating system running in the first device, under certain triggering conditions, the solution can determine the lock screen command that the operating system can recognize based on the type of the operating system, and then automatically control the electronic device to enter the system lock screen state. This solution is highly convenient and improves the user experience.
[0173] In one possible implementation, the determining module is used to receive screen lock trigger information sent by the second device. The screen lock trigger information is information generated by the user operating the screen lock control displayed on the second device, and the screen lock trigger information is used to indicate screen lock.
[0174] In this way, the system can automatically control the first device to enter the system lock screen state with one click, which is highly convenient and improves the user experience.
[0175] In one possible implementation, the determining module is used to determine screen lock trigger information when the duration of the detected static state of the first device's display interface exceeds a threshold.
[0176] In this way, the duration of the same static interface displayed on the first device can be used to automatically control the first device to enter the system lock screen state, which is highly convenient and improves the user experience.
[0177] In one possible implementation, the device further includes:
[0178] The type determination module is used to determine the type of the operating system currently running on the first device during the power-on process of the first device;
[0179] The storage module is used to store the type of operating system currently running on the first device.
[0180] In this way, the type of operating system running on the first device can be determined during the power-on process of the first device, and then stored. This allows the first device to be controlled to enter the lock screen state based on the type of operating system running on the first device when the lock screen trigger information is determined. This is highly convenient and improves the user experience.
[0181] In one possible implementation, the determining module is configured to:
[0182] Displays the selection options for the multiple operating systems;
[0183] Based on user input, the operating system running on the first device is determined from the multiple operating system selection options;
[0184] Based on the operating system running on the first device, determine the type of operating system currently running on the first device.
[0185] Thus, when the first device has multiple operating systems installed, the user selects the operating system to be run on the first device, thereby determining the type of operating system and storing the type of operating system running on the first device. This allows the first device to enter the lock screen state based on the type of operating system running on the first device when the lock screen trigger information is determined, which is highly convenient and improves the user experience.
[0186] In one possible implementation, the device further includes:
[0187] The display module is used to display the lock screen command configuration interface, which is used to display parameter configuration options for various types of operating systems;
[0188] The instruction determination module is used to determine the lock screen instruction corresponding to each type of operating system based on the user's configuration input, so as to obtain the lock screen instruction table.
[0189] Figure 8b This is a schematic diagram of the screen lock control device provided in an embodiment of this application. The screen lock control device provided in this embodiment is applied to a second device. Figure 8b As shown, the screen lock control device provided in this application embodiment includes a display module 811, a receiving module 812, and a sending module 813.
[0190] Display module 811 is used to display a user interface, the user interface including a lock screen control;
[0191] The receiving module 812 is used to receive user operations on the lock screen control;
[0192] The sending module 813 is used to send screen lock trigger information to the first device in response to the user operation, so that the first device determines the target screen lock instruction corresponding to the operating system type currently running on the first device according to the screen lock trigger information and a pre-stored screen lock instruction table, and controls the first device to enter the screen lock state based on the target screen lock instruction. The screen lock instruction table indicates the screen lock instructions corresponding to different operating system types.
[0193] According to this solution, users can remotely control the first device to enter the system lock screen state with one click, which is highly convenient and improves the user experience.
[0194] Based on the same concept as the method embodiments of this application, embodiments of this application also provide an electronic device. This electronic device can be as follows: Figure 2 The first device shown can also be as follows: Figure 2 The second device where the client is located is shown.
[0195] Figure 9This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.
[0196] like Figure 9 As shown, the electronic device 900 includes a processor 901, a memory 902, and a network interface 903.
[0197] The processor 901 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.
[0198] The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).
[0199] For example, a computer program may be stored on the memory 902, and when the processor 901 executes the computer program, it implements the steps in the above-described screen lock control method embodiment, for example... Figure 3The steps S301 to S303 are shown. Alternatively, when the processor 901 executes the computer program, it implements the functions of each module in the above-described device embodiment. For example, the computer program can be divided into one or more modules / units, which can be a series of computer program instruction segments capable of performing a specific function. One or more modules / units are stored in the memory 902 and executed by the processor 901 to complete this application. For example, the computer program can be divided into an acquisition module 901, an analysis module 902, and a feedback module 903; the specific functions of each module are described above.
[0200] The network interface 903 is used to send and receive data, for example, to send data processed by the processor 901 to other electronic devices, or to receive data sent by other electronic devices.
[0201] Of course, for the sake of simplicity, Figure 9 Only some of the components of the electronic device 900 relevant to this application are shown, omitting components such as buses, input / output interfaces, etc. In addition, the electronic device 900 may include any other suitable components depending on the specific application. Furthermore, the electronic device may be a desktop computer, laptop, handheld computer, cloud server, or other computing device. Those skilled in the art will understand that... Figure 9 This is merely an example of electronic device 900 and does not constitute a limitation on the electronic device. It may include more or fewer components than illustrated, or combine certain components, or use different components. For example, the electronic device may also include input devices, output devices, network access devices, buses, etc. For example, the input device may be a microphone array, and may also include, for example, a keyboard, mouse, etc. For example, the output device may output various information to the outside, and may include, for example, a display, speaker, printer, and communication network and its connected remote output devices, etc.
[0202] In addition to the methods, apparatus, and electronic devices described above, embodiments of this application may also provide a computer program product, comprising computer program instructions. When executed by a processor, these computer program instructions cause the processor to perform the steps of the screen lock control methods of the various embodiments of this application described in the "Methods" section of this specification. The computer program product can be written in any combination of one or more programming languages to execute the operations of the embodiments of this application. The programming languages include object-oriented programming languages such as Java and C++, as well as conventional procedural programming languages such as C or similar languages. The computer program code can be in source code form, object code form, executable file, or some intermediate form. The computer program code can be executed entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.
[0203] Furthermore, embodiments of this application may also provide a computer-readable storage medium storing computer program instructions thereon, which, when executed by a processor, cause the processor to perform the steps in the display control methods according to various embodiments of this application described in the "Method" section above. The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may include, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. It should be noted that the content contained in the computer-readable medium may be appropriately added to or subtracted according to the requirements of legislation and patent practice in a jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, a computer-readable medium may not include electrical carrier signals and telecommunication signals.
[0204] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can reside in an ASIC.
[0205] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).
[0206] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0207] It should be understood that the sequence number of each step in the above embodiments does not imply 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.
[0208] The basic principles of this application have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this application are merely examples and not limitations, and should not be considered as essential features of each embodiment of this application. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the application to the necessity of employing the aforementioned specific details for implementation.
[0209] The block diagrams of devices, apparatuses, devices, and systems involved in this application are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.
[0210] It should also be noted that in the apparatus, equipment, and methods of this application, the components or steps can be disassembled and / or recombined. These disassemblies and / or recombinations should be considered as equivalent solutions of this application.
[0211] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this application to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.
[0212] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application.
Claims
1. A screen lock control method, characterized in that, The method, applied to an out-of-band management controller (BMC) of a first device, includes: Receive screen lock trigger information sent by the second device; Based on the screen lock trigger information and the pre-stored screen lock instruction table, a target screen lock instruction corresponding to the operating system type currently running on the first device is determined. The screen lock instruction table indicates screen lock instructions corresponding to different operating system types. Based on the target lock screen command, the target lock screen command is converted into a keyboard combination event and sent to the operating system of the first device to control the first device to enter the lock screen state.
2. The method according to claim 1, characterized in that, The information used to determine the screen lock trigger includes: When the duration of the first device's display interface remaining stationary exceeds a threshold, screen lock trigger information is determined.
3. The method according to any one of claims 1-2, characterized in that, The method further includes: During the power-on process of the first device, the type of operating system currently running on the first device is determined; Store the type of operating system currently running on the first device.
4. The method according to claim 3, characterized in that, The determination of the operating system type currently running on the first device includes: Displays the selection options for the multiple operating systems; Based on user input, the operating system running on the first device is determined from the multiple operating system selection options; Based on the operating system running on the first device, determine the type of operating system currently running on the first device.
5. The method according to any one of claims 1-2, characterized in that, The method further includes: Display the lock screen command configuration interface, which is used to display parameter configuration options for various types of operating systems; Based on the user's configuration input, the corresponding lock screen command for each type of operating system is determined to obtain the lock screen command table.
6. A screen lock control method, characterized in that, Applied to a second device, the method includes: Display user interface, the user interface including lock screen control; Received user input for the lock screen control; In response to the user operation, a screen lock trigger information is sent to the out-of-band management controller (BMC) of the first device, so that the BMC determines the target screen lock command based on the pre-stored screen lock command table, converts the target screen lock command into a keyboard combination event, sends it to the operating system of the first device, and controls the first device to enter the screen lock state.
7. An electronic device, characterized in that, include Memory, used to store programs; A processor for executing a program stored in the memory, wherein when the program stored in the memory is executed, the processor is configured to perform the method as described in any one of claims 1-5, or to perform the method as described in claim 6.
8. A screen lock control device, characterized in that, The device executes computer program instructions to perform the method as described in any one of claims 1-5, or to perform the method as described in claim 6.
9. A computer storage medium, characterized in that, The computer storage medium stores instructions that, when executed on the computer, cause the computer to perform the method as described in any one of claims 1-5, or the method as described in claim 6.
