WO2021104401A1

WO2021104401A1 - Electronic device and method for logging in operating system

Info

Publication number: WO2021104401A1
Application number: PCT/CN2020/131915
Authority: WO
Inventors: 冯鹏; 刘明进; 敖敏; 庾能国
Original assignee: 华为技术有限公司
Priority date: 2019-11-30
Filing date: 2020-11-26
Publication date: 2021-06-03
Also published as: CN111125664B; CN111125664A

Abstract

An electronic device and an method for logging in operating system, wherein the electronic device comprises a power key and a fingerprint sensor (102), and the fingerprint sensor (102) and power key are integrated in one. The electronic device further comprises an EC (107), and a CPU (105). When a user's finger presses the power key, the fingerprint sensor (102) may also acquire the user's fingerprint, and the fingerprint is transmitted to the EC (107) for encryption and caching. After the CPU (105) loads and starts the operating system, it obtains the fingerprint from the EC (107) to perform user identity authentication according to the fingerprint from the EC (107), which can support the user to quickly log in the operating system. Moreover, the architecture of the electronic device no longer needs an MCU provided by a fingerprint sensor manufacturer, can reduce the cost, and improve the integration level.

Description

Electronic equipment and method for logging in to operating system

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201911212056.2, and the application name is "An electronic device and a method for logging in to an operating system" on November 30, 2019, the entire content of which is incorporated by reference In this application.

Technical field

This application relates to the field of electronic technology, and in particular to an electronic device and a method for logging in to an operating system.

Background technique

With the rapid development of information technology, the use of electronic devices such as notebook computers has become more and more popular. In order to improve the security of user information, when the user logs in to the operating system, the notebook computer can provide the user with security authentication. Security authentication can be password verification, fingerprint verification or face verification, etc. The traditional way to log in to the operating system is: the user presses the power button to turn on, then enters the password/fingerprint unlocking/face scan and other methods for security authentication, and finally logs into the operating system. This traditional method has the problems of low login efficiency and cumbersome user operations.

Summary of the invention

This application provides an electronic device and a method for logging in to an operating system, which can perform user identity authentication while the electronic device is turned on to log in to the operating system of the electronic device, which can improve login efficiency and simplify user operations. Moreover, the architecture of the electronic device no longer requires the MCU provided by the fingerprint sensor manufacturer, which can reduce costs and improve integration.

In the first aspect, an electronic device is provided. As shown in FIG. 5 exemplarily, the electronic device may include a power button, a fingerprint sensor 102, an EC 107, and a CPU 105. among them,

The fingerprint sensor 102 and the power button 101 are integrated. For example, the fingerprint sensor 102 can be pasted or printed on the surface of the power button 101. This surface can touch the user's finger when the user presses the power button 101. In this way, it can be realized that while the user presses the power button 101, the fingerprint sensor 102 can collect the user's fingerprint.

EC 107 is a separate processor. The EC 107 can be connected to the fingerprint sensor 102, and the EC 107 and the fingerprint sensor 102 can communicate through an SPI interface. For example, the EC 107 sends a fingerprint acquisition request to the fingerprint sensor 102, and the fingerprint sensor 102 transmits the collected fingerprint to the EC 107. The firmware program of fingerprint encryption module can be loaded in EC 107. The fingerprint encryption module may be responsible for encrypting the fingerprint from the fingerprint sensor 102. The EC 107 may have a memory, which can store the encrypted fingerprint, and transmit the encrypted fingerprint to the CPU 105 in response to subsequent fingerprint entry instructions and fingerprint verification instructions from the CPU 105.

EC 107 can be connected to CPU 105. The EC 107 and CPU 105 can communicate through the GPIO interface. Such communication may include: the EC 107 sends an interrupt signal (such as notification) to the CPU 105 through a certain pin or pins of the GPIO, and the CPU 105 sends an interrupt signal (such as a notification) to the EC 107 through a certain pin or some pins. The communication efficiency based on the GPIO interface is very high. In order to realize the transmission of user fingerprints between EC 107 and CPU 105, a software communication interface is introduced, which can be used to communicate user fingerprints between EC 107 and CPU 105. This software communication interface may be referred to as the first interface. The first interface can realize the communication between the EC 107 and the CPU 105 based on the shared memory. Both EC 107 and CPU 105 can be connected to the shared memory through but not limited to the enhanced SPI interface to write data to or read data from the shared memory through ESPI.

The fingerprint sensor driver is loaded in the CPU 105. The CPU 105 loaded with the fingerprint sensor driver can communicate with the EC 107 through the first interface. For example, the CPU 105 sends a fingerprint entry instruction or a fingerprint verification instruction to the EC 107, and the EC 107 transmits the fingerprint cached in the memory of the EC 107 to the CPU 105. The CPU 105 can be used to perform user identity verification based on the fingerprint from the EC 107. If the fingerprint from the EC 107 is consistent with the fingerprint template pre-entered and stored in the notebook computer 100, the verification is passed; otherwise, the verification fails.

When the power button 101 is pressed by the user's finger, the EC 104 notifies the fingerprint sensor 102 and the CPU 105 to power on. The fingerprint sensor 102 after power-on can collect the user's fingerprint, and the fingerprint is transmitted to the EC 104 for encryption and buffering. After the CPU 105 loads and starts the operating system, it obtains the fingerprint from the EC 104 through the first interface to perform user identity verification based on the fingerprint from the EC 104. If the verification is passed, the CPU 105 can instruct the display screen (not shown) to display the system desktop shown in FIG. 3B.

It can be seen that the electronic device provided in the first aspect can realize one-click power-on and identity authentication, and can support users to quickly log in to the operating system. Moreover, the electronic equipment provided by the first aspect can reduce costs and improve integration, which is conducive to miniaturization of notebook computers.

In the second aspect, a method for logging in to an operating system is provided, and the method is applied to the electronic device provided in the first aspect. The method may include: the EC detects that the power button is pressed by the user's finger, and obtains the user's fingerprint collected by the fingerprint sensor. The fingerprint sensor collects fingerprints when the power button is pressed by the user's finger. EC encrypts user fingerprints, and stores the encrypted user fingerprints in the internal storage space of EC. Then, the EC obtains the fingerprint verification instruction from the CPU through the first interface. In response to the fingerprint verification instruction, the EC transmits the encrypted user fingerprint to the CPU through the first interface. The CPU performs user identity verification according to the user's fingerprint, and if the verification is passed, it logs in to the operating system of the electronic device.

It can be seen that in the method provided by the second aspect, by pressing the power button, the notebook computer in the shutdown state (S5) can be turned on and logged in to the operating system, which is simple and efficient. Moreover, the electronic equipment no longer needs the MCU provided by the fingerprint sensor manufacturer (MCU 103 in Figure 4), which can reduce costs, improve integration, and facilitate the miniaturization of notebook computers.

With reference to the second aspect, in some embodiments, before communicating between the EC and the CPU through the first interface, the BIOS notifies the EC and the CPU of the address of the shared memory. The shared memory is used for subsequent exchange of data between the EC and the CPU. In this way, the EC and the CPU can exchange data (such as fingerprints, fingerprint verification instructions, fingerprint entry instructions, etc.) through the shared memory according to the address of the shared memory to realize communication.

With reference to the second aspect, in some embodiments, in order to further improve user information security, after transmitting the encrypted user fingerprint to the CPU through the first interface, the EC may delete the user fingerprint stored in the EC. In other words, after the EC writes the user fingerprint into the shared memory, the user fingerprint stored in the EC is deleted. In this way, the information security of fingerprint registered users can be improved, and other users can be prevented from logging in to the operating system through the fingerprints of registered users left in the EC. Here, a fingerprint registered user refers to a user who has entered a fingerprint template in advance.

In combination with the second aspect, in some embodiments, in order to further improve the security of user information, if the EC saves the user's fingerprint for more than a certain period of time (such as 3 seconds) and has not received a fingerprint verification instruction from the fingerprint sensor driver, the EC The user fingerprint can be deleted. This specific duration can be referred to as the first time.

With reference to the second aspect, in some embodiments, before the EC obtains the fingerprint verification instruction from the CPU through the first interface, the CPU writes the fingerprint verification instruction into the shared memory. Specifically, the operating system running on the CPU sends a fingerprint verification request to the fingerprint sensor driver running on the CPU. Then, in response to the fingerprint verification request, the fingerprint sensor driver running on the CPU writes a fingerprint verification instruction to the shared memory.

With reference to the second aspect, in some embodiments, the CPU and the EC can also communicate through a universal input and output interface GPIO interface. After the CPU writes the fingerprint verification instruction to the shared memory, the CPU sends the first notification to the EC through the GPIO interface. The first notification can be used to notify the EC to read the fingerprint verification instruction from the shared memory.

With reference to the second aspect, in some embodiments, the EC obtains the fingerprint verification instruction from the CPU through the first interface, which may specifically include: the EC can read from the shared memory through the first interface the fingerprint verification written by the CPU to the shared memory instruction.

With reference to the second aspect, in some embodiments, the EC transmits the encrypted user fingerprint to the CPU through the first interface, which may specifically include: the EC writes the encrypted user fingerprint into the shared memory through the first interface. Then, the CPU reads the encrypted user fingerprint from the shared memory.

Specifically, the CPU reading the encrypted user fingerprint from the shared memory may include: a fingerprint sensor driver running on the CPU reads the encrypted user fingerprint from the shared memory. The fingerprint sensor driver running on the CPU sends the encrypted user fingerprint to the operating system running on the CPU.

With reference to the second aspect, in some embodiments, the CPU and the EC also communicate via a universal input and output interface GPIO interface. After the EC writes the encrypted user fingerprint into the shared memory through the first interface, the EC sends a second notification to the CPU through the GPIO interface. The second notification is used to notify the CPU to read the encrypted user fingerprint from the shared memory.

With reference to the second aspect, in some embodiments, the CPU performs user identity verification based on the user's fingerprint. If the verification is passed, logging in to the operating system may specifically include: the CPU determining whether the user's fingerprint is related to the fingerprint template in the first storage area of the electronic device If they are consistent, the verification is passed and the operating system is logged in.

In a third aspect, a chip system is provided. The chip system may include an embedded controller and a processor CPU. The embedded controller and the processor CPU are integrated in the electronic device described in the first aspect. The electronic device may also include Power button, fingerprint sensor. The power button and fingerprint sensor are integrated. among them,

EC can be used to detect that the power button is pressed by the user's finger, and obtain the user's fingerprint collected by the fingerprint sensor. The fingerprint sensor collects fingerprints when the power button is pressed by the user's finger. EC can also be used to encrypt user fingerprints, and the encrypted user fingerprints are stored in the internal storage space of EC. The EC can also be used to obtain fingerprint verification instructions from the CPU through the first interface. In response to the fingerprint verification instruction, the EC can transmit the encrypted user fingerprint to the CPU through the first interface. The CPU can be used to perform user identity verification based on the user's fingerprint, and if the verification is passed, log in to the operating system of the electronic device.

It can be seen that the chip system provided by the third aspect is integrated into the electronic device described in the first aspect, which can realize one-key boot and login, and can make the electronic device no longer need the MCU provided by the fingerprint sensor manufacturer (as shown in Figure 4) MCU 103), which can reduce costs and improve integration, which is conducive to the miniaturization of notebook computers.

With reference to the third aspect, in some embodiments, the BIOS may be used to notify the EC and the CPU of the address of the shared memory before the communication between the EC and the CPU through the first interface. The shared memory is used for subsequent exchange of data between the EC and the CPU. In this way, the EC and the CPU can exchange data (such as fingerprints, fingerprint verification instructions, fingerprint entry instructions, etc.) through the shared memory according to the address of the shared memory to realize communication.

In combination with the third aspect, in some embodiments, in order to further improve user information security, the EC can be used to delete the user fingerprint stored in the EC after transmitting the encrypted user fingerprint to the CPU through the first interface. In other words, after the EC writes the user fingerprint into the shared memory, the user fingerprint stored in the EC is deleted. In this way, the information security of fingerprint registered users can be improved, and other users can be prevented from logging in to the operating system through the fingerprints of registered users left in the EC. Here, a fingerprint registered user refers to a user who has entered a fingerprint template in advance.

In combination with the third aspect, in some embodiments, in order to further improve the security of user information, EC can be used if the EC saves the user's fingerprint for more than a certain period of time (for example, 3 seconds), and has not received fingerprint verification from the fingerprint sensor driver. Command, delete the user's fingerprint.

With reference to the third aspect, in some embodiments, the CPU may be used to write the fingerprint verification instruction to the shared memory before the EC obtains the fingerprint verification instruction from the CPU through the first interface. Specifically, the operating system running on the CPU sends a fingerprint verification request to the fingerprint sensor driver running on the CPU. Then, in response to the fingerprint verification request, the fingerprint sensor driver running on the CPU writes a fingerprint verification instruction to the shared memory.

With reference to the third aspect, in some embodiments, the CPU and the EC can also communicate through a universal input and output interface GPIO interface. The CPU can be used to send a first notification to the EC through the GPIO interface after the CPU writes a fingerprint verification instruction to the shared memory. The first notification can be used to notify the EC to read the fingerprint verification instruction from the shared memory.

With reference to the third aspect, in some embodiments, the EC may be specifically used to read the fingerprint verification instruction written by the CPU into the shared memory from the shared memory through the first interface.

With reference to the third aspect, in some embodiments, the EC may be specifically used to write the encrypted user fingerprint into the shared memory through the first interface. Then, the CPU reads the encrypted user fingerprint from the shared memory.

With reference to the third aspect, in some embodiments, the CPU and the EC also communicate via a universal input and output interface GPIO interface. The EC can be used to send a second notification to the CPU through the GPIO interface after the EC writes the encrypted user fingerprint into the shared memory through the first interface. The second notification is used to notify the CPU to read the encrypted user fingerprint from the shared memory.

With reference to the third aspect, in some embodiments, the CPU may be specifically used to determine whether the user fingerprint is consistent with the fingerprint template in the first storage area of the electronic device. If they are consistent, the verification is passed and the operating system is logged in.

In a fourth aspect, a computer-readable storage medium is provided, and instructions are stored on the readable storage medium, and the instructions run in the processor CPU of the electronic device described in the first aspect. The electronic device also includes a power button, a fingerprint sensor, and an embedded controller EC; the power button and the fingerprint sensor are integrated. Among them, the EC is connected to the fingerprint sensor; the EC and the CPU communicate through a first interface, and the first interface is a software communication interface created based on the shared memory between the EC and the CPU.

When the instruction runs in the processor CPU of the electronic device, the processor CPU can be made to execute the following steps:

CPU transmits fingerprint verification instructions to EC;

The CPU receives the encrypted user fingerprint sent by the EC;

The CPU performs user identity verification according to the user's fingerprint, and if the verification is passed, it logs in to the operating system of the electronic device.

Wherein, the CPU transmits the fingerprint verification instruction to the EC, which may specifically include: the CPU writes the fingerprint verification instruction into the shared memory.

Wherein, the CPU receiving the encrypted user fingerprint sent by the EC may specifically include: the CPU reads the encrypted user fingerprint from the shared memory.

In a fifth aspect, a computer program product containing instructions is provided, and the computer program product runs in the processor CPU of the electronic device described in the first aspect. The electronic device also includes a power button, a fingerprint sensor, and an embedded controller EC; the power button and the fingerprint sensor are integrated. Among them, the EC is connected to the fingerprint sensor; the EC and the CPU communicate through a first interface, and the first interface is a software communication interface created based on the shared memory between the EC and the CPU.

When the computer program product runs on the processor CPU of the electronic device described in the first aspect, the processor CPU can be caused to execute the following steps:

CPU transmits fingerprint verification instructions to EC;

The CPU receives the encrypted user fingerprint sent by the EC;

Description of the drawings

FIG. 1A exemplarily shows a typical electronic device provided by an embodiment of the present application;

FIG. 1B exemplarily shows the settings of the power button and fingerprint sensor of the electronic device shown in FIG. 1A;

Figures 2A-2D exemplarily show the booting and operating system login process of a traditional notebook computer;

3A-3B exemplarily show the booting and system login process of the notebook computer shown in FIG. 1A;

FIG. 4 exemplarily shows an existing hardware architecture applied to the notebook computer shown in FIG. 1A;

FIG. 5 exemplarily shows that the present application provides a new hardware architecture applied to the notebook computer shown in FIG. 1A;

FIG. 6 shows a software architecture applied to the notebook computer shown in FIG. 1A based on the hardware architecture shown in FIG. 5;

FIG. 7 exemplarily shows a solution for implementing the operating system login method provided by this application in the notebook computer 100;

FIG. 8 shows a method for logging in to an operating system provided by an embodiment of the present application;

FIG. 9 shows a method for logging in to an operating system provided by another embodiment of the present application;

FIG. 10 shows a method for logging in to an operating system provided by another embodiment of the present application;

Figure 11 exemplarily shows the "incorrect shutdown interface";

FIG. 12 shows a method for logging in to an operating system provided by another embodiment of the present application;

FIG. 13 shows the method of fingerprint template entry provided by this application;

Figures 14A-14B exemplarily show a fingerprint entry window of "one-key login";

15A-15B exemplarily show another fingerprint entry window of "one-key login";

Figure 16 exemplarily shows another fingerprint entry window of "one-click login";

Figure 17 exemplarily shows another fingerprint entry window of "one-key login";

FIG. 18 exemplarily shows another typical electronic device provided by an embodiment of the present application;

Fig. 19 exemplarily shows the booting and unlocking process of the electronic device shown in Fig. 18.

Detailed ways

In order to make the purpose, technical solutions, and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings.

This application provides an electronic device that has an integrated power button and a fingerprint sensor. The electronic device can be a notebook computer, a desktop computer, a tablet computer, a smart phone, and other types of electronic devices. This application also provides a method for logging in to the operating system, which can be applied to the electronic device provided in this application, and can realize user identity authentication when the electronic device is turned on, so as to log in to the operating system of the electronic device, which can improve Login efficiency and simplify user operations.

In the embodiments of the present application, the operating system of the electronic device may refer to a computer program that manages computer hardware and software resources. The operating system needs to deal with basic tasks such as managing and configuring memory, determining the priority of system resource supply and demand, controlling input devices and output devices, operating the network, and managing the file system. The operating system also provides an operation interface that allows users to interact with the system. The operating system has configured a set of user names and passwords for each user, and users can use their own user names and passwords to log in to the operating system. After the login is successful, the user can legally use the capabilities of the account. For example, mailbox users can send and receive mail, view/change the address book, and so on. There are many types of passwords, such as digital passwords, fingerprint passwords, facial feature passwords, and so on.

FIG. 1A exemplarily shows a typical electronic device: a notebook computer 100 provided by an embodiment of the present application. As shown in FIG. 1A, the notebook computer 100 may include a power button 101 and a fingerprint sensor 102, wherein,

The fingerprint sensor 102 may be an optical fingerprint sensor, an ultrasonic fingerprint sensor, or other types of fingerprint sensors. The fingerprint sensor 102 and the power button 101 are integrated. For example, as shown in FIG. 1B, the fingerprint sensor 102 may be pasted or printed on the surface of the power button 101. This surface can touch the user's finger when the user presses the power button 101. In this way, it can be realized that while the user presses the power button 101, the fingerprint sensor 102 can collect the user's fingerprint.

In order to distinguish between the electronic equipment provided in this application and the traditional electronic equipment, the following briefly introduces the booting and operating system login process of the notebook computer 100 shown in FIG. 1A, as well as the traditional notebook computer (such as the notebook computer shown in FIGS. 2A-2D). 200) booting and operating system login process.

2A-2D exemplarily show the booting and operating system login process of the traditional notebook computer 200. among them,

As shown in Figures 2A-2D, although the traditional notebook computer 200 also includes a power button 201 and a fingerprint sensor 202, the power button 201 and the fingerprint sensor 202 are generally provided separately; or, the fingerprint sensor 202 can also be integrated in the notebook On the touch module 203 of the computer 200.

As shown in FIG. 2A, when the user presses the power button 201 of the notebook computer 200, the notebook computer 201 can start up in response to the user's pressing operation on the power button 201, and display the user account icon 204 and the icon shown in FIG. 2B. The operating system login interface of the user password input box 205 is for the user to enter the user password or wait for the user to enter the user's fingerprint information through the fingerprint sensor 202 to log in to the operating system of the notebook computer 200.

As shown in FIG. 2C, when a user touches the fingerprint sensor 202 of the notebook computer 200, the fingerprint sensor 202 can collect the fingerprint of the user, so that the notebook computer 200 can perform user identity authentication. If the authentication is passed, the notebook computer 200 will display the system desktop as shown in FIG. 2D. So far, the user successfully logs in to the operating system of the notebook computer 200.

It can be seen that during the booting of the traditional notebook computer 200 and the system login process, the user needs to press the power button 201 to start the notebook computer 200, and then touch the fingerprint sensor 202 to enter the fingerprint information, that is, the user needs to press the power button respectively Only with fingerprint sensor can be used for user identity authentication and login to the operating system. The traditional notebook computer 200 has the problems of cumbersome user operations and low login efficiency during the booting and system login process.

3A-3B exemplarily show the booting and system login process of the notebook computer 100 shown in FIG. 1A. among them,

As shown in FIG. 3A, when a user's finger presses the power button 101 of the notebook computer 100, the user's finger will also touch the fingerprint sensor 102 integrated on the power button 101. In response to the pressing operation of the user's finger on the power button 101, the notebook computer 100 can be powered on, and at the same time, the fingerprint sensor 102 can collect the user's fingerprint, so that the notebook computer 100 can perform user identity authentication. If the authentication is passed, the notebook computer 100 will display the system desktop as shown in FIG. 3B. So far, the user successfully logs in to the operating system of the notebook computer 100.

It can be seen that the notebook computer 100 provided by the embodiment of the present application can realize "one-key power-on login", that is, the user's finger presses the power button 101 once to complete the power-on and identity authentication, and quickly log in to the operating system.

At present, in order to achieve one-click completion of booting and identity authentication, and quick login to the operating system, an existing hardware architecture implemented in the notebook computer 100 can be exemplarily shown in FIG. 4. As shown in FIG. 4, the hardware architecture applied to the notebook computer 100 may include: a microcontroller processing unit (microcontroller unit, MCU) 103, an embedded controller (embedded controller, EC) 104 (also known as an embedded processing unit) Processor), central processing unit (CPU) 105.

The MCU 103 is connected to the fingerprint sensor 102. The MCU 103 and the fingerprint sensor 102 may communicate through a serial peripheral interface (SPI) interface. For example, the MCU 103 sends a fingerprint acquisition request to the fingerprint sensor 102, and the fingerprint sensor 102 transmits the collected fingerprint to the MCU 103. The MCU 103 may be responsible for encrypting the fingerprint from the fingerprint sensor 102. The MCU 103 may have a memory, which can store the encrypted fingerprint, and transmit the encrypted fingerprint to the CPU 105 in response to the subsequent fingerprint entry instruction or fingerprint verification instruction sent by the CPU 105.

The CPU 105 is connected to the MCU 103. The CPU 105 and the MCU 103 can communicate through the SPI interface. The fingerprint sensor driver is loaded in the CPU 105. The fingerprint sensor driver is a driver program of the fingerprint sensor 102. The CPU 105 loaded with the fingerprint sensor driver can communicate with the MCU 103 through the SPI interface. For example, the CPU 105 sends a fingerprint entry instruction or fingerprint verification instruction to the MCU 103, and the MCU 103 transmits the fingerprint cached in the memory of the MCU 103 to the CPU 105. The CPU 105 can be used to perform user identity verification based on the fingerprint from the MCU 103. If the fingerprint from the MCU 103 is consistent with the fingerprint template pre-entered and stored in the notebook computer 100, the verification is passed; otherwise, the verification fails. The fingerprint template refers to a user fingerprint entered in advance and stored in the notebook computer 100, which is equivalent to a password set by the user in advance to log in to the operating system. The following content will describe the implementation of fingerprint registration in detail, so I won't go into details here.

MCU 103 and CPU 105 are also connected to EC 104. EC 104 is a separate processor. The EC 104 and the CPU 105 can communicate through a general purpose input output (GPIO) interface. The EC 104 and MCU 103 can communicate through the SPI interface. During the startup of the operating system of the notebook computer 100, the EC 104 controls the timing of most important signals. When the notebook computer 100 is in the shutdown state, the EC 104 keeps running and waits for the user's power-on signal. After the notebook computer 100 is turned on, the EC 104 can be used as a controller for devices such as the fingerprint sensor 102, keyboard, charging indicator, and fan. The EC 104 can also control the standby and hibernation states of the system. After detecting that the user presses the power button 101, the EC 104 will notify the entire notebook computer 100 to power on.

When the power button 101 is pressed by the user's finger, the EC 104 notifies the MCU 103, the fingerprint sensor 102, and the CPU 105 to power on. After power-on, the fingerprint sensor 102 can collect the user's fingerprint, and the fingerprint is transmitted to the MCU 103 for encryption. After the CPU 105 loads and starts the operating system, it requests the MCU 103 to enter the fingerprint, so as to perform user authentication based on the fingerprint from the MCU 103. If the verification is passed, the CPU 105 can instruct the display screen (not shown) to display the system desktop shown in FIG. 3B. So far, the architecture shown in Figure 4 has achieved one-key boot and identity authentication, which can support users to quickly log in to the operating system.

However, the architecture of the notebook computer 100 shown in FIG. 4 requires an additional MCU to be configured for the fingerprint sensor: MCU 103. This will not only increase the cost, but also requires a larger internal design space, which is not conducive to the miniaturization of notebook computers.

FIG. 5 exemplarily shows that the present application provides a new hardware architecture applied to the notebook computer 100, which can not only realize one-key boot and identity authentication, simplify user login operations, but also overcome the existence of the hardware architecture shown in FIG. 4 The problem.

As shown in FIG. 5, the new hardware architecture applied to the notebook computer 100 may include: EC 107, CPU 105. among them,

EC 107 can be connected to CPU 105. The EC 107 and CPU 105 can communicate through the GPIO interface. Such communication may include: the EC 107 sends an interrupt signal (such as notification) to the CPU 105 through a certain pin or pins of the GPIO, and the CPU 105 sends an interrupt signal (such as a notification) to the EC 107 through a certain pin or some pins. The communication efficiency based on the GPIO interface is very high. In order to realize the transmission of user fingerprints between EC 107 and CPU 105, a software communication interface is introduced, which can be used to communicate user fingerprints between EC 107 and CPU 105. This software communication interface may be referred to as the first interface. The first interface can realize the communication between the EC 107 and the CPU 105 based on the shared memory. Both the EC 107 and the CPU 105 can be connected to the shared memory through, but not limited to, an enhanced SPI (ESPI) interface, so as to write data to or read data from the shared memory through ESPI. Regarding the specific implementation of the first interface, the follow-up content will be introduced in detail, so I won't go into details here.

When the power button 101 is pressed by the user's finger, the EC 104 notifies the fingerprint sensor 102 and the CPU 105 to power on. The fingerprint sensor 102 after power-on can collect the user's fingerprint, and the fingerprint is transmitted to the EC 104 for encryption and buffering. After the CPU 105 loads and starts the operating system, it obtains the fingerprint from the EC 104 through the first interface to perform user identity verification based on the fingerprint from the EC 104. If the verification is passed, the CPU 105 can instruct the display screen (not shown) to display the system desktop shown in FIG. 3B. At this point, the hardware architecture shown in Figure 5 has achieved one-key boot and identity authentication, which can support users to quickly log in to the operating system. Moreover, the hardware architecture shown in FIG. 5 can also overcome the problems of the hardware architecture shown in FIG. 4.

Based on the hardware architecture shown in FIG. 5, the present application provides a software architecture applied to the notebook computer 100. As shown in Figure 6, the software architecture may include: operating system 201 running on CPU 105, fingerprint sensor driver 202 loaded by operating system 201, basic input-output system (BIOS) 205, loaded on EC Fingerprint library 203 in 107. among them,

The operating system 201 is responsible for managing hardware resources and software resources. Hardware resources include CPU 105, memory 108, graphics card, network card, sound card, hard disk, and so on. Software resources include various programs, such as various hardware drivers. The operating system 201 is also responsible for abstracting the interface of the hardware driver to form a simple software interface for the upper application.

The fingerprint sensor driver 202 can be used to initialize the fingerprint sensor 102 and provide a hardware resource access interface for the fingerprint sensor 102.

BIOS 205 is integrated in a read only memory (ROM) on the motherboard of the notebook computer 100, which mainly stores basic input and output programs, system information setting programs, power-on self-check programs, and system startup boot programs, etc. . BIOS 205 can be regarded as a piece of software permanently recorded in ROM, which is a part of the input and output management system of the operating system. Before being executed by the CPU 105, the BIOS 205 can be loaded into the memory 108. The memory 108 may be a random access memory (RAM). The BIOS 205 can be mainly used to start the notebook computer 100, control and drive important hardware, and provide basic calls for high-level software. The BIOS 205 can be used to initialize the memory 108 after the laptop 100 is powered on, and inform the EC 107 and the fingerprint sensor driver 202 of the address of the shared memory used for communication between the EC 107 and the fingerprint sensor driver 202. The interface for communication between the EC 107 and the fingerprint sensor driver 202 based on shared memory may be referred to as the first interface.

The fingerprint library 203 provides multiple types of software interfaces, such as service interfaces, control interfaces, interrupt service interfaces, and read-write interfaces. Among them, the service interface can be used by the EC 107 to receive input-output (IO) instructions issued by the fingerprint sensor driver 202 and the EC 107 to send notifications to the fingerprint sensor driver 202 (for example, to notify that the fingerprint has been written to the shared memory); the control interface is available The EC 107 sends an interrupt signal to the fingerprint sensor driver 202 through the GPIO interface; the interrupt service interface can be used by the EC 107 to process the interrupt signal sent by the fingerprint sensor driver 202; the read-write interface can be used by the EC 107 to respond to the IO commands sent by the fingerprint sensor driver 202 And read commands written by the fingerprint sensor driver 202 from the shared memory (such as fingerprint entry instructions, fingerprint verification instructions), and can be used by the EC to respond to the fingerprint entry instructions or fingerprint verification instructions written by the fingerprint sensor driver 202 to the shared memory. The user fingerprint collected by the fingerprint sensor 102 is written into the shared memory.

When the power button 101 is pressed by the user's finger, the EC 104 notifies the fingerprint sensor 102 and the CPU 105 to power on. The fingerprint sensor 102 after power-on can collect user fingerprints, and the user fingerprints are transmitted to the EC 104 for encryption and buffering. After the operating system 201 is started, the operating system 201 loads the fingerprint sensor driver 202. The EC 107 can receive the specific IO command sent by the fingerprint sensor driver 202 through the service interface in the fingerprint library 203 (that is, the first notification mentioned in the subsequent embodiments). In response to the specific IO command, the EC 107 can pass the fingerprint library 203 The read-write interface reads the fingerprint sensor drive commands (such as fingerprint entry instructions, fingerprint verification instructions) written by the fingerprint sensor driver 202 from the shared memory. Then, the EC 107 can write user fingerprints into the shared memory through the read-write interface in the fingerprint library 203, and send a notification to the fingerprint sensor driver 202 through the service interface in the fingerprint library 203 (that is, the second Notification) to notify the user that the fingerprint has been written into the shared memory. Finally, the fingerprint sensor driver 202 will read the user's fingerprint from the shared memory according to the notification. So far, the fingerprint sensor driver 202 obtains the user fingerprint collected by the fingerprint sensor 102, and sends the user fingerprint to the operating system 201, so that the operating system 201 performs user identity verification based on the user fingerprint.

FIG. 7 exemplarily shows a solution for implementing the operating system login method provided by this application in the notebook computer 100. As shown in Figure 7, the solution presents a combination of software architecture and hardware architecture, which can be divided into two parts: the device layer, the application, and the kernel layer.

1. The device layer may include devices connected to the CPU 105: local storage 206, BIOS 205, EC 107, fingerprint sensor 102, and power button 101. among them,

The local storage 206 can be used to store a fingerprint template, that is, a fingerprint entered in advance by a user to log in to the operating system 201.

The firmware program of fingerprint encryption module can be loaded in EC 107. The fingerprint encryption module may be responsible for encrypting the fingerprint from the fingerprint sensor 102. EC 107 can have a memory, which can store encrypted fingerprints. The key KEY_A can be preset in the BIOS 205. The key KEY_B can be preset in EC 107. The EC 107 can use the key KEY_B to encrypt the user fingerprint collected by the fingerprint sensor 102.

BIOS 205 refers to ROM with integrated BIOS. The key KEY_A is used by the fingerprint sensor driver 202, and the fingerprint sensor driver 202 can carry the key KEY_A in the fingerprint entry instruction or fingerprint verification instruction. Then, the EC 107 receiving the fingerprint entry instruction or fingerprint verification instruction will verify the key KEY_A, and if the verification is passed, the encrypted user fingerprint temporarily stored in the EC 107 will be transmitted to the fingerprint sensor driver 202 through the first interface. The fingerprint sensor driver 202 can obtain the key KEY_A through the advanced configuration and power management interface device-specific method (ACPI DSM) provided by the BIOS 205.

The communication between the fingerprint sensor driver 202 running in the CPU 105 and the fingerprint encryption module in the EC 107 belongs to cross-chip communication. In order to ensure the security of fingerprint transmission, a communication link can be established between the two based on the Transport Layer Security Protocol (TLS).

2. The application and kernel layer may include various software programs running on the CPU 105: user login application (APP) 211, fingerprint management application (APP) 212, fingerprint recognition framework 210, storage adapter (storage adapter) 207, engine An engine adapter 208, a fingerprint recognition sensor adapter 209, a fingerprint recognition sensor driver 202, and a power management program 213. among them:

The user login APP 211 is responsible for the login management of the operating system 201, can prompt the user to enter a password, and perform user identity verification based on the fingerprint or other forms of password entered by the user. For example, if the result of the user identity verification is that the verification is passed, the user logs in to the APP 211 to display the system desktop as shown in FIG. 3B.

The fingerprint management APP 212 may be responsible for entering a fingerprint template, that is, responsible for setting the fingerprint entered by the user in advance to log in to the operating system 201. The fingerprint management APP 212 can generally be integrated in a setting application.

The fingerprint recognition framework 210 may include various application programming interfaces (APIs) that may be used when building applications involving fingerprint recognition, and a service interface that allows consistent development and management of the fingerprint sensor 102, facilitating application development Personnel can carry out efficient development.

The storage adapter 207 may provide an interface for storing or accessing fingerprint templates, and may be used for storing or accessing fingerprint templates.

The engine adapter 208 may be responsible for fingerprint security management and run fingerprint processing algorithms. Specifically, the engine adapter 208 can manage or calculate the user fingerprint acquired by the fingerprint sensor driver 202 in an encrypted trusted execution area of the memory. The engine adapter 208 may specifically include two modules: fingerprint collection 208A and fingerprint authentication 208B. The fingerprint collection 208A can be used to obtain a user's fingerprint from the fingerprint sensor adapter 209. The fingerprint authentication 208B can be used to verify whether the user fingerprint obtained by the fingerprint collection 208A is consistent with the fingerprint template accessed by the storage adapter 207. If they are consistent, the user identity verification passes; otherwise, the user identity verification fails.

The fingerprint sensor adapter 209 can be responsible for setting the fingerprint sensor 102 and reading the user's fingerprint from the fingerprint sensor driver 202.

The fingerprint sensor driver 202 can be used to initialize the fingerprint sensor 102 and provide the operating system 201 with an access interface for the hardware resources of the fingerprint sensor 102.

Based on the aforementioned software architecture and hardware architecture of the notebook computer 100, the method for logging in to the operating system provided by the present application will be described in detail below.

First, introduce several operating states of the notebook computer 100:

(1) Working state (marked as S0): The notebook computer 100 is working normally, and all hardware devices are in a power-on state.

(2) Sleep state (marked as S1 or S3): The CPU stops executing instructions, and the things in the memory remain in the memory as they are. Among them, S1 is also called power on suspend (POS) state, which is a low power consumption state. In the S1 state, the CPU stops working at this time, the display screen is off, and other hardware devices are in a low power consumption working state. S3 has also become a suspend to RAM (STR) state. In the S3 state, the running data is written into the memory, and most hardware devices except the memory are turned off.

(3) Hibernation state (marked as S4): Most of the characteristics of hibernation state and sleep state are the same, the difference is: the information left in the memory in the original sleep state is written to the hard disk as it is, and the system itself after the hibernation is completed Enter a zero power consumption state; when the system is woken up, the memory image in the hard disk is loaded into the memory as it is, and the system resumes operation.

(4) Shutdown state (marked as S5): also known as soft shutdown (soft off). Most of the hardware devices of the notebook computer 100 are powered off, but some components are still powered, so that the notebook computer 100 can still be awakened by the keyboard, clock, modem (phone wakeup), local area network (LAN) module, and USB devices.

Next, the user will press the power button around the user's finger to illustrate how to log in to the operating system in several operating states of the notebook computer 100.

Example 1

In Embodiment 1, when the user's finger presses the power button, the notebook computer 100 is in the shutdown state (S5). At this time, the CPU and other hardware devices of the notebook computer 100 are in a power-off state. The user's finger pressing the power button will trigger the notebook computer 100 to switch from the shutdown state (S5) to the working state (S0).

FIG. 8 exemplarily shows the method for logging in to the operating system provided in Embodiment 1. As shown in Figure 8, the method may include the following steps:

S101, the notebook computer 100 detects that the power button is pressed.

Specifically, the EC of the notebook computer 100 is responsible for detecting whether the power button is pressed.

In S102, the EC determines that when the user's finger presses the power button, the notebook computer 100 is in a shutdown state. EC is responsible for managing the operating status of the laptop.

S103: After the power button is pressed, the notebook computer 100 starts to be powered on. Specifically, the EC in the notebook computer 100 may power on various hardware devices (such as a fingerprint sensor, BIOS, CPU, display screen, etc.) according to a power sequence. In the shutdown state, the EC keeps running and waits for a power-on signal (such as a high-level pulse signal generated by the power button being pressed).

After the CPU is powered on, it will run the operating system and load the fingerprint sensor driver. Then, the operating system will request the fingerprint sensor driver to provide the user's fingerprint. There are several purposes for the operating system to obtain user fingerprints: 1. Enter the fingerprint template; 2. Perform user identity verification. This embodiment relates to the first purpose.

S104, the EC is initialized. While controlling the power on of each hardware device, set the pin status of hardware devices such as memory and chips necessary for the operation of the operating system to initialize the internal environment.

S105, the EC sends the fingerprint sensor configuration to the fingerprint sensor to enable the fingerprint sensor. The configuration of the fingerprint sensor can be, for example, parameters such as the size of the fingerprint image and the resolution of the fingerprint image.

S106: The BIOS initializes the memory. The BIOS waits for the EC to initialize the internal hardware devices before starting to run.

S107: When the user's finger presses the power button, the fingerprint sensor integrated with the power button can detect the touch of the user's finger and collect the user's fingerprint. Specifically, the data representation form of the user's fingerprint may be a fingerprint image.

If the time for the user's finger to press the power button is too short, shorter than the execution time of S102-S104, the user's finger will leave the fingerprint sensor before the fingerprint sensor is enabled. This will cause the fingerprint sensor to fail to collect the user's finger and fail to log into the operating system. At this time, the laptop computer can display the operating system login interface including the user account icon 204 and the user password input box 205 as shown in FIG. 2B for the user to input the user password or wait for the user to touch the fingerprint sensor to input the fingerprint again to log in to the laptop. Operating system.

S108: After collecting the user's fingerprint, the fingerprint sensor may notify the EC to obtain the user's fingerprint.

S109-S110, in response to the fingerprint sensor's notification, the EC may send a request to the fingerprint sensor to request the user's fingerprint. Then, the fingerprint sensor returns the user fingerprint collected by the fingerprint sensor to the EC.

Communication between EC and fingerprint sensor is through SPI interface. In other words, S104, S108, and S109-S110 are implemented based on the SPI interface. For example, the EC sends a request to the fingerprint sensor based on the SPI interface, and also reads the user's fingerprint in the fingerprint sensor based on the SPI interface.

S109-S110 can be executed multiple times to obtain a complete user fingerprint. Because the amount of data that can be interacted in one communication based on the SPI interface is limited, it is usually impossible to transmit a complete fingerprint image. The complete fingerprint image refers to the fingerprint image actually collected by the fingerprint sensor.

S111, every time the EC reads the fingerprint data from the fingerprint sensor, it will be stored in the internal memory of the EC. The firmware program of the fingerprint encryption module can be loaded in the EC. EC can encrypt user fingerprints stored in it through the fingerprint encryption module.

S112: After the BIOS performs memory initialization, the BIOS may notify the EC of the shared memory address.

Not shown, the BIOS can also notify the fingerprint sensor driver running in the CPU of the shared memory address. The shared memory can be used for data communication between the fingerprint encryption module loaded in the EC and the fingerprint sensor driver running in the CPU.

Not limited to the timing shown in FIG. 8, S112 can also occur before S111, or even before S106.

S113: The fingerprint sensor driver running in the CPU can write a fingerprint verification instruction to the shared memory. Before S113, the fingerprint sensor driver received a fingerprint verification request from the operating system. Refer to S119. The fingerprint verification request may specifically come from a user logging in to the APP running on the operating system. In response to the fingerprint verification request from the operating system, the fingerprint sensor driver writes a fingerprint verification instruction to the shared memory to notify the EC to write the user's fingerprint collected by the fingerprint sensor into the shared memory. The fingerprint verification instruction may be a specific command in the drive command set driven by the fingerprint sensor.

S114: The fingerprint sensor driver sends a first notification (specific IO command) to the EC to trigger the EC to read the fingerprint verification command written by the fingerprint sensor driver from the shared memory. Specifically, the fingerprint sensor driver may send the first notification to the EC through the GPIO interface. The transmission of the first notification based on the GPIO interface can improve the transmission efficiency of the first notification, thereby increasing the efficiency of fingerprint interaction between the EC and the CPU.

S115. In response to the first notification, the EC 107 can read the fingerprint verification instruction written by the fingerprint sensor driver from the shared memory through the first interface (specifically, the read interface).

S116. In response to the fingerprint verification instruction, the EC can write the encrypted user fingerprint into the shared memory through the first interface (specifically, the write interface).

S117: After writing the user's fingerprint into the shared memory, the EC may send a second notification (specific IO command) to the fingerprint sensor driver to notify the fingerprint sensor that the user's fingerprint has been written into the shared memory. Specifically, the EC may send the second notification to the fingerprint sensor driver through the GPIO interface. The transmission of the second notification based on the GPIO interface can improve the transmission efficiency of the second notification, thereby increasing the efficiency of fingerprint interaction between the EC and the CPU.

S118: The fingerprint sensor driver may read the user's fingerprint from the shared memory according to the second notification.

So far, the fingerprint sensor driver has obtained the user fingerprint collected by the fingerprint sensor, and can send the user fingerprint to the operating system to support the operating system to perform user identity verification based on the user fingerprint.

S120: The fingerprint sensor driver sends the user's fingerprint to the operating system.

In S121-S122, the operating system performs user identity verification according to the user's fingerprint. If the verification result is that the verification is passed, the notebook computer will display the operating system desktop as shown in FIG. 3B. At this point, the user has successfully logged in to the operating system of the laptop.

Specifically, the operating system may compare the user fingerprint with the fingerprint template in the local storage 206, and if the user fingerprint is consistent with the fingerprint template, the verification result is determined to be verified; otherwise, the verification result is determined to be failed.

If the verification result is that the verification fails, the notebook computer will display the operating system login interface including the user account icon 204 and the user password input box 205 as shown in FIG. 2B for the user to enter the user password or wait for the user to enter the user through the fingerprint sensor Fingerprint to log into the operating system of the laptop.

It can be seen that in the method for logging in to the operating system provided in Embodiment 1, by pressing the power button, the notebook computer 100 in the shutdown state (S5) can be turned on and logged in to the operating system, which is simple and efficient. Moreover, Embodiment 1 no longer needs the MCU provided by the fingerprint sensor manufacturer (MCU 103 in FIG. 4), which can reduce the cost, improve the integration level, and facilitate the miniaturization of the notebook computer.

In order to further improve the security of user information, the method for logging in to the operating system provided in Embodiment 1 may further include: after S116, the EC deletes the user fingerprint stored in the EC. In other words, after the EC writes the user fingerprint into the shared memory, the user fingerprint stored in the EC is deleted. In this way, the information security of fingerprint registered users can be improved, and other users can be prevented from logging in to the operating system through the fingerprints of registered users left in the EC. Here, a fingerprint registered user refers to a user who has entered a fingerprint template in advance.

In order to further improve the security of user information, the method for logging in to the operating system provided in Embodiment 1 may further include: if the EC saves the user's fingerprint for more than a certain period of time (for example, 3 seconds), the fingerprint verification instruction from the fingerprint sensor driver has not been received. , The EC can delete the user's fingerprint.

Because the operating system may not be able to send fingerprint verification requests to the fingerprint sensor driver in time due to system failures or other reasons, resulting in the fingerprint sensor driver not being able to send fingerprint verification instructions to the EC in time. Or, the operating system sends the fingerprint verification request to the fingerprint sensor driver in time, but the fingerprint sensor driver fails to send the fingerprint verification instruction to the EC in time. In this way, it will lead to the failure to log in to the operating system in time, and the login process will be prolonged. A fingerprint-registered user may leave the laptop while waiting to log in to the operating system. If the user successfully logs in to the operating system after the user leaves, the user's information may be viewed or stolen by other users.

Example 2

In Embodiment 2, when the user's finger presses the power button, the notebook computer 100 is in a sleep state (S1 or S3), or a hibernation state (S4). At this time, the CPU of the notebook computer 100 is in the off state, and other hardware devices are in a low power consumption working state, for example, the screen is off (or called a black screen). The operation of the user's finger pressing the power button will trigger the notebook computer 100 to switch from the sleep state or the hibernation state to the working state.

FIG. 9 exemplarily shows the method for logging in to the operating system provided in Embodiment 2. As shown in Figure 9, the method may include the following steps:

S201: The notebook computer 100 detects that the power button is pressed. For details, refer to S101 in Embodiment 1, which will not be repeated here.

S202: When the user's finger presses the power button, some hardware devices in a low-power working state will be awakened, for example, the screen will be lit, the fingerprint sensor will start to collect fingerprints, and so on. At this time, the fingerprint sensor integrated with the power button can detect the user's finger touch and collect the user's fingerprint. Specifically, the data representation form of the user's fingerprint may be a fingerprint image. For details, refer to S107 in Embodiment 1, which will not be repeated here.

When the user's finger presses the power button, the notebook computer 100 is in a sleep state or a hibernation state, the EC is initialized, the fingerprint sensor is in a low-power working state, is not powered off, and can collect user fingerprints. Therefore, Embodiment 2 provides It is no longer necessary to power on the fingerprint sensor and initialize the EC in the method of logging in to the operating system.

In S203, the EC determines that when the user's finger presses the power button, the notebook computer 100 is in a dormant state or a sleep state. EC is responsible for managing the operating status of the laptop.

S204: After the power button is pressed, the EC will control the CPU to power on.

S205: After collecting the user's fingerprint, the fingerprint sensor may notify the EC to obtain the user's fingerprint.

S206-S207, in response to the fingerprint sensor's notification, the EC may send a request to the fingerprint sensor to request the user's fingerprint. Then, the fingerprint sensor returns the user fingerprint collected by the fingerprint sensor to the EC.

For details, please refer to S109-S110 in Embodiment 1, which will not be repeated here.

S208, the EC encrypts the acquired user fingerprint. For details, refer to S111 in Embodiment 1, which will not be repeated here.

S210: The fingerprint sensor driver running in the CPU writes a fingerprint verification instruction to the shared memory. Before S210, the fingerprint sensor driver received a fingerprint verification request from the operating system. Refer to S209. The fingerprint verification request may specifically come from a user logging in to the APP running on the operating system. In response to the fingerprint verification request, the fingerprint sensor driver writes a fingerprint verification instruction to the shared memory to notify the EC to write the user's fingerprint collected by the fingerprint sensor into the shared memory. The fingerprint verification instruction may be a specific command in the drive command set driven by the fingerprint sensor.

Because before the notebook computer enters the hibernation state or the sleep state, the BIOS in the notebook computer that is still working at that time has already initialized the memory and notified the EC and the CPU of the shared memory address. Therefore, the BIOS can no longer notify the EC and CPU of the shared memory address.

S211: The fingerprint sensor driver sends a first notification (specific IO instruction) to the EC to trigger the EC to read the fingerprint verification instruction written by the fingerprint sensor driver from the shared memory. Specifically, the fingerprint sensor driver may send the first notification to the EC through the GPIO interface.

S212. In response to the first notification, the EC 107 may read the fingerprint verification instruction written by the fingerprint sensor driver from the shared memory through the first interface (specifically, the read interface).

S213. In response to the fingerprint verification instruction, the EC may write the encrypted user fingerprint into the shared memory.

S214: After writing the user's fingerprint into the shared memory, the EC may send a second notification (specific IO command) to the fingerprint sensor driver to notify the fingerprint sensor that the user's fingerprint has been written into the shared memory. Specifically, the EC may send the second notification to the fingerprint sensor driver through the GPIO interface.

S215: The fingerprint sensor driver may read the user's fingerprint from the shared memory according to the second notification.

S216: The fingerprint sensor driver sends the user's fingerprint to the operating system.

In S217-S218, the operating system performs user identity verification based on the user's fingerprint. If the verification result is that the verification is passed, the notebook computer 100 will display the operating system desktop as shown in FIG. 3B. So far, the user successfully logs in to the operating system of the notebook computer 100.

It can be seen that in the method for logging in to the operating system provided in Embodiment 2, by pressing the power button, the notebook computer 100 in the dormant state or the sleeping state can be turned on and logged in to the operating system, which is simple and efficient. Moreover, Embodiment 2 no longer needs the MCU provided by the fingerprint sensor manufacturer (MCU 103 in FIG. 4), which can reduce the cost, improve the integration level, and facilitate the miniaturization of the notebook computer.

In order to further improve the security of user information, the method for logging in to the operating system provided in Embodiment 2 may further include: if the EC saves the user's fingerprint for more than a certain period of time (for example, 3 seconds), the fingerprint verification instruction from the fingerprint sensor driver has not been received , The EC can delete the user's fingerprint.

Example 3

In Embodiment 3, when the notebook computer 100 is in the sleep state (marked as S1 or S3) or the sleep state (S4), if the user's finger presses the power button for more than a certain period of time (for example, 5 seconds), that is, the user's finger presses the power button for a long time. Key, the notebook computer 100 can be triggered to shut down, and the notebook computer 100 will enter the shutdown state.

In order to prevent users other than the registered fingerprint user from pressing the power button of the device to turn off the device, causing unsaved information in the device (such as editing and unsaved documents in the device) to be lost due to the forced shutdown of the device, the login provided in Example 3 The method of operating system can be as shown in Figure 10, including:

S301: The notebook computer 100 detects that the power button is long pressed by the user's finger.

Specifically, the EC of the notebook computer 100 is responsible for detecting whether the power button is pressed, and the length of time the power button is pressed. Here, the long press means that the power button is pressed for longer than the first time period (for example, 5 seconds).

S302: When the user's finger presses the power button, some hardware devices in a low-power working state will be awakened, for example, the screen will be lit, the fingerprint sensor will start to collect fingerprints, and so on. At this time, the fingerprint sensor integrated with the power button can detect the user's finger touch and collect the user's fingerprint. Specifically, the data representation form of the user's fingerprint may be a fingerprint image. For details, refer to S202 in Embodiment 2, which will not be repeated here.

In S303, the EC determines that when the user's finger presses the power button, the notebook computer 100 is in a sleep state or a sleep state. EC is responsible for managing the operating status of the laptop.

S304: After the power button is pressed, the EC will control the CPU to power on. For details, refer to S204 in Embodiment 2, which will not be repeated here.

S305: After collecting the user's fingerprint, the fingerprint sensor may notify the EC to obtain the user's fingerprint.

S306-S307, in response to the notification from the fingerprint sensor, the EC may send a request to the fingerprint sensor to request the user's fingerprint. Then, the fingerprint sensor returns the user fingerprint collected by the fingerprint sensor to the EC.

For details, refer to S206-S207 in Embodiment 2, which will not be repeated here.

S308, the EC encrypts the acquired user fingerprint. For details, refer to S208 in Embodiment 2, which will not be repeated here.

S309, the EC can write the encrypted user fingerprint into the shared memory.

S310: After writing the user fingerprint into the shared memory, the EC may send a third notification to the fingerprint sensor driver to notify the fingerprint sensor driver that the user fingerprint has been written into the shared memory, and notify the fingerprint sensor driver to trigger the operating system to perform user authentication. Specifically, the EC may send the third notification to the fingerprint sensor driver through the GPIO interface. The third notification is transmitted based on the GPIO interface, which can improve the transmission efficiency of the third notification, thereby improving the efficiency of fingerprint interaction between the EC and the CPU.

In S311, in response to the third notification, the fingerprint sensor driver sends a fingerprint verification request to the operating system to request the operating system to perform user identity verification.

It can be seen from S309-S311 that after obtaining the user's fingerprint, the EC proactively informs and requests the operating system to perform user identity verification, so as to prevent users other than the registered fingerprint user from forcibly shutting down the laptop 100, thereby avoiding the registered fingerprint user's Unsaved data is lost due to this forced shutdown operation.

S312. In response to the third notification, the fingerprint sensor driver also reads the user's fingerprint from the shared memory.

S313, the fingerprint sensor driver sends the user fingerprint to the operating system.

In S314-S315, the operating system can perform user identity verification according to the user fingerprint sent by the fingerprint sensor driver, and if the verification result is passed, the shutdown process will be executed. Specifically, the operating system can trigger components such as the EC and the power management unit to cooperate to complete the shutdown process.

Wherein, if the verification result is that the verification fails, the operating system can control the notebook computer 100 to enter the sleep state. If the verification result is that the verification fails, the operating system can also show the "incorrect shutdown interface" as shown in Figure 11.

Exemplarily, if the verification result indicates that the fingerprint verification is not passed, the device may enter the sleep mode and display the "incorrect shutdown interface" as shown in FIG. 11. For example, the "Inadvertent Shutdown Interface" shown in FIG. 11 may display prompt messages of "The device is locked" and "No personnel other than the owner of the machine should continue to operate" 2001.

It can be seen that the method for logging in to the operating system provided in the third embodiment can prevent users other than the registered fingerprint user from pressing the power button of the device to turn off the device, and the device does not appear to be in the dormant state or the sleeping state of the notebook computer 100. The saved information (such as the document being edited and unsaved in the device) is lost due to the forced shutdown of the device.

Example 4

In Embodiment 4, when the user's finger presses the power button, the notebook computer 100 is in the power-on state (S0). At this time, pressing the power button can have the following situations: 1. Short press the power button to sleep; 2. Long press the power button to shut down. Here, a long press means that the power key has been pressed for more than a specific time period (for example, 5 seconds), and a short press means that the power key has been pressed for no longer than the specific time period.

Among them, for the first case, the EC can trigger the notebook computer 100 to sleep, and the notebook computer 100 will enter the sleep state. For the second case, the EC can trigger the notebook computer 100 to shut down, and the notebook computer 100 will enter the shutdown state.

In order to prevent users other than the registered fingerprint user from pressing the power button of the device to turn off the device, causing unsaved information in the device (such as editing and unsaved documents in the device) to be lost due to the forced shutdown of the device, the login provided in Example 4 The method of operating system can be shown in Figure 12, including:

S401: The notebook computer 100 detects that the power button is long pressed by the user's finger. For details, please refer to S301 in Embodiment 3, which will not be repeated here.

S402: When the user's finger presses the power button, the fingerprint sensor integrated with the power button can detect the touch of the user's finger and collect the user's fingerprint. For details, refer to S302 in Embodiment 3, which will not be repeated here.

In S403, the EC determines that the notebook computer 100 is in a working state when the user's finger presses the power button. EC is responsible for managing the operating status of the laptop.

Because the notebook computer 100 is in a working state, therefore, after the power button is pressed, there is no need to power on the CPU and other hardware devices, such as power on the screen and the fingerprint sensor.

S405: After collecting the user's fingerprint, the fingerprint sensor may notify the EC to obtain the user's fingerprint.

S406-S407, in response to the notification from the fingerprint sensor, the EC may send a request to the fingerprint sensor to request the user's fingerprint. Then, the fingerprint sensor returns the user fingerprint collected by the fingerprint sensor to the EC.

For details, please refer to S306-S307 in Embodiment 3, which will not be repeated here.

S408, the EC encrypts the acquired user fingerprint. For details, refer to S308 in Embodiment 3, which will not be repeated here.

In S409, the EC can write the encrypted user fingerprint into the shared memory.

In S410, after writing the user's fingerprint into the shared memory, the EC may send a notification to the fingerprint sensor driver to notify the fingerprint sensor driver that the user's fingerprint has been written into the shared memory.

S411 In response to the notification, the fingerprint sensor driver sends a fingerprint verification request to the operating system to request the operating system to perform user identity verification.

S412. In response to the notification, the fingerprint sensor driver also reads the user's fingerprint from the shared memory.

S413: The fingerprint sensor driver sends the user's fingerprint to the operating system.

S414: The operating system judges whether the notebook computer 100 is in a locked screen state. If the screen is locked, it means that the fingerprint-registered user has left the notebook computer 100, and S415 can be executed, that is, the user's identity needs to be verified before the shutdown process can be performed. If it is not in the lock screen state, it means that the fingerprint registered user is using the laptop 100, and there is no need to verify the user identity, and S416 can be executed, that is, the shutdown process will be executed directly.

S415: The operating system may perform user identity verification according to the user fingerprint sent by the fingerprint sensor driver. If the verification result is that the verification is passed, S416 may be executed, that is, the shutdown process may be executed. If the verification result is that the verification fails, the operating system can control the notebook computer 100 to enter the sleep state. If the verification result is that the verification fails, the operating system can also show the "incorrect shutdown interface" as shown in Figure 11.

S416: The operating system executes a shutdown process. Specifically, the operating system can trigger components such as the EC and the power management unit to cooperate to complete the shutdown process.

It can be seen that the method for logging in to the operating system provided in Embodiment 4 is for the laptop 100 in a working state. When the laptop 100 is locked, it can prevent users other than the registered fingerprint user from pressing the power button of the device to turn off the device. However, there is a problem that unsaved information in the device (such as editing and unsaved documents in the device) is lost due to the forced shutdown of the device.

In addition, when the notebook computer 100 is in a working state, a dormant state, or a sleeping state, the fingerprint-registered user may accidentally touch the power button, which may cause the fingerprint sensor to collect the user's fingerprint and save the user's fingerprint in the EC. In order to prevent other users from using the user fingerprint for user identity verification in this case, and to further improve user information security, the method for logging in to the operating system provided in this embodiment of the application may further include: if the EC saves the user fingerprint for more than a certain period of time (For example, 3 seconds), the EC can delete the user's fingerprint if it has not detected that the power button has been pressed.

The previous embodiments respectively describe the method of triggering one-key startup and login by the user's finger pressing the power button when the notebook computer 100 is in different operating states. The foregoing various embodiments can be implemented in combination. Specifically, the operating state of the notebook computer 100 when the user's finger presses the power button, or the length of time the user's finger presses the power source (short press or long press), can be determined to implement the foregoing embodiment 1. To the method of logging in to the operating system provided by a certain embodiment in embodiment 4. For example, when the user's finger presses the power button, if the running state of the notebook computer 100 is the shutdown state, the method for logging in to the operating system provided in Embodiment 1 can be executed. For another example, if the operating state of the notebook computer 100 is the sleep state or the sleep state when the user's finger presses the power button, the method for logging in to the operating system provided in Embodiment 2 can be executed.

The user identity verification mentioned in the previous embodiments is implemented by comparing the fingerprint template with the user fingerprint collected by the fingerprint sensor. The following describes the entry process of the fingerprint template.

In the case that the login password is not set in the notebook computer 100, when the user presses the power button of the notebook computer 100, the CPU runs the operating system after being powered on, and the operating system desktop shown in FIG. 3B can be directly displayed. In other words, in this case, the user can turn on the notebook computer 100 by pressing the power button, and directly log in to the operating system without passing identity verification.

In order to facilitate the user to enter a fingerprint template to protect personal information, the notebook computer 100 may display a "one-key login" fingerprint entry window 601 as shown in FIG. 14A on the operating system desktop shown in FIG. 3B. As shown in Figure 13, the fingerprint template entry process can include:

S501: The notebook computer 100 detects that the power button is pressed.

S502: After the power button is pressed, the notebook computer 100 starts to be powered on. Specifically, the EC in the power-on state can power on various hardware devices (such as fingerprint sensors, BIOS, and CPU) according to the power-on sequence.

After the CPU is powered on, it will run the operating system and load the fingerprint sensor driver. Then, the operating system will request the fingerprint sensor driver to provide the user's fingerprint. There are several purposes for the operating system to obtain user fingerprints: 1. Enter the fingerprint template; 2. Perform user identity verification. This embodiment relates to the second purpose.

S503, the EC is initialized.

S504, the EC sends the fingerprint sensor configuration to the fingerprint sensor to enable the fingerprint sensor.

S505, the BIOS initializes the memory. The BIOS waits for the EC to initialize the internal hardware devices before starting to run.

S506: When the user's finger presses the power button, the fingerprint sensor integrated with the power button can detect the touch of the user's finger and collect the user's fingerprint.

S507: After collecting the user's fingerprint, the fingerprint sensor may notify the EC to obtain the user's fingerprint.

S508-S509, in response to the fingerprint sensor's notification, the EC may send a request to the fingerprint sensor to request the user's fingerprint. Then, the fingerprint sensor returns the user fingerprint collected by the fingerprint sensor to the EC.

S510, every time the EC reads fingerprint data from the fingerprint sensor, it will be stored in the internal memory of the EC. The firmware program of the fingerprint encryption module can be loaded in the EC. EC can encrypt the user's fingerprints stored in it through the pattern encryption module.

S511: After the BIOS performs memory initialization, the BIOS may notify the EC of the shared memory address. Not shown, the BIOS can also notify the fingerprint sensor driver running in the CPU of the shared memory address.

S512: After the CPU is powered on and started, the operating system will run. After the fingerprint sensor driver is loaded, the operating system can display the operating system desktop as shown in FIG. 3B exemplarily.

S513: The operating system may display a fingerprint entry window on the desktop of the operating system.

Exemplarily, the operating system may display a fingerprint entry window 610 as shown in FIG. 14A on the desktop of the operating system. The fingerprint entry window 610 may be a user interface provided by a fingerprint management APP. As shown in FIG. 14A, the fingerprint entry window 610 may include a "fingerprint usage list" 611 and a "fingerprint list" 614. Wherein, the "fingerprint usage list" 611 may include at least one fingerprint usage option and its option switch. For example, the “fingerprint usage list” 611 may include the “operating system login” option and its option switch 612 and the “one-key boot login” option and its option switch 613. The "fingerprint list" 614 may include an "add fingerprint" option 615.

Among them, the user can limit the use of user fingerprints added subsequently by turning on the option switch corresponding to the fingerprint use option in the "fingerprint use list" 611. For example, as shown in FIG. 14A, because the option switch 613 of the "one-key power-on login" option in the "fingerprint usage list" 611 is in the on state, and the other option switches in the other "fingerprint usage list" 611 are in the off state; therefore 14A, when the user controls the cursor 620 to move to the “add fingerprint” option 615, click on the “add fingerprint” option 615 and perform subsequent fingerprint entry operations. The entered user fingerprint can be used to perform the “one” of the notebook computer 100. Key to boot and login".

S514: In response to the user's input command in the fingerprint entry window, the operating system sends a fingerprint entry request to the fingerprint sensor driver. The fingerprint entry request may specifically come from a fingerprint management APP running on the operating system.

Wherein, the fingerprint entry request is used to instruct the fingerprint sensor to drive to obtain the user fingerprint collected by the fingerprint sensor.

S515: In response to the fingerprint entry request from the operating system, the fingerprint sensor driver running in the CPU writes a fingerprint entry instruction to the shared memory to notify the EC to write the user fingerprint collected by the fingerprint sensor into the shared memory.

S516: The fingerprint sensor driver sends a fifth notification (specific IO command) to the EC to trigger the EC to read the fingerprint entry command written by the fingerprint sensor driver from the shared memory. Specifically, the fingerprint sensor driver may send the fifth notification to the EC through the GPIO interface.

S517. In response to the fifth notification, the EC may read the fingerprint entry instruction written by the fingerprint sensor driver from the shared memory.

S518: In response to the fingerprint entry instruction, the EC can write the encrypted user fingerprint into the shared memory.

S519: After writing the user's fingerprint into the shared memory, the EC may send a sixth notification to the fingerprint sensor driver to notify the fingerprint sensor driver that the user's fingerprint has been written into the shared memory.

S520, the fingerprint sensor driver may read the user fingerprint from the shared memory according to the sixth notification.

So far, the fingerprint sensor driver has obtained the user fingerprint collected by the fingerprint sensor, and can send the user fingerprint to the operating system to support the operating system to set a fingerprint template according to the user fingerprint.

S521: The fingerprint sensor driver sends the user fingerprint to the operating system.

S521: The operating system may save the user fingerprint as a fingerprint template. Specifically, the operating system may store the user fingerprint in a preset storage area in the local storage 206. The preset storage area may be referred to as the first storage area.

Exemplarily, as shown in FIG. 14A, when the user controls the cursor 620 to move to the "add fingerprint" option 615, and after clicking the "add fingerprint" option 615, the operating system can send a fingerprint entry instruction to the fingerprint sensor driver (ie, execute S514) , And display the first prompt information 630 in the fingerprint entry window 610 as shown in FIG. 14B. For example, the first prompt information 630 may include "Use fingerprints instead of passwords to implement device'one-key boot login'" and "First, Please put your thumb or other fingers on the "power button"" prompt text. Subsequently, as shown in FIG. 15A, when the user's mobile phone touches the "power button" 101, the fingerprint sensor 102 can collect the user's fingerprint, and the EC can also obtain and save the user fingerprint collected by the fingerprint sensor 102, that is, execute S506-S510 . In addition, the fingerprint sensor driver may obtain the user fingerprint collected by the fingerprint sensor 102 from the EC after receiving the fingerprint entry instruction (that is, execute S515-S520).

In another possible implementation, after the fingerprint sensor collects the user fingerprint, the EC may not obtain the user fingerprint immediately, but waits for the aforementioned specific IO command sent by the fingerprint sensor driver, and then obtains it from the fingerprint sensor User fingerprint.

Exemplarily, as shown in FIG. 15A, when the user's mobile phone touches the "power button" 101, the operating system may display the second prompt message 640 and the fingerprint filling window 650 in the fingerprint entry window 610 as shown in FIG. 15B. For example, as shown in FIG. 15B, the second prompt message 640 may be an instruction text including "Put your finger on the'power button'" and then remove, repeat this operation." After the user follows the prompt of the second prompt message 640, In the process of repeating the action of "put your finger on the'power button' and then remove it", the fingerprint filling window 650 can display a dynamic image in which the fingerprint lines in the fingerprint filling window 650 are gradually being filled.

After the fingerprint sensor driver receives the user fingerprint sent by the EC and saves the user fingerprint as a fingerprint template, the operating system can display a fingerprint entry window 610 as shown in FIG. 16. At this time, the fingerprint entry window 610 may display the third prompt information 660 and the fingerprint filling window and 650 filled with fingerprint lines. For example, as shown in FIG. 16, the third prompt message 660 may include an instruction text that "fingerprints have been entered, you can only enter your fingerprints to achieve "one-key startup and login" of the device".

Further, the operating system may also display a fingerprint entry window 610 as shown in FIG. 17 after the fingerprint entry is completed. Among them, the "fingerprint list" 614 of the fingerprint entry window 610 shown in FIG. 17 is increased by "fingerprint 1" 616 compared to the "fingerprint list" 614 of the fingerprint entry window 610 shown in FIG. 14A. The "fingerprint 1" 616 can be used to implement "one-key startup and login" of the device.

Through the fingerprint template entry process described in Figure 13 and Figures 14A-14B, Figure 15A-15B, and Figure 16-17, the user can enter multiple fingerprints of different fingers in the notebook computer 100, which is convenient for Use different fingers to press the power button of the notebook computer 100 to realize the "one-key power-on login" of the notebook computer 100.

In order to further improve user information security, the fingerprint template entry process can also include: If the EC saves the user’s fingerprint for more than a certain period of time (such as 3 seconds) and has not received a fingerprint entry instruction from the fingerprint sensor driver, the EC can be deleted The user's fingerprint.

Because the operating system may not be able to send fingerprint entry instructions to the fingerprint sensor driver in time due to system failures or other reasons, resulting in the fingerprint sensor driver being unable to send fingerprint entry instructions to the EC in time. Or, the operating system sends the fingerprint entry instruction to the fingerprint sensor driver in time, but the fingerprint sensor driver fails to send the fingerprint entry instruction to the EC in time. In this way, the operating system will not be able to enter the fingerprint template in time, and there is a risk of confusion or theft of the fingerprint template entry.

The previous embodiments described the method for logging in to the operating system provided by this application by taking a laptop computer as an example. The method is not limited to a laptop computer. The method provided by this application can also be applied to other types of electronic devices, such as mobile phones.

FIG. 18 exemplarily shows a mobile phone 700 to which the method for logging in to an operating system provided by this application is applied. As shown in FIG. 18, the mobile phone 700 may include a power button 701 and a fingerprint sensor 702, and the power button 701 and the fingerprint sensor 702 are integrated. The hardware architecture and software architecture of the mobile phone 700 can be implemented with reference to FIGS. 5-7. The EC in the aforementioned notebook computer 100 may be a boot circuit corresponding to the mobile phone 700, such as a power integrated circuit (IC). The boot circuit may be It has strong computing power and can encrypt user fingerprints.

As shown in FIG. 19, the power button 701 of the mobile phone 700 in the shutdown state is pressed by the user's finger. When the user's finger presses the power button 701, the user's finger will definitely touch the fingerprint sensor 702. Therefore, when it is detected that the user's finger presses the power button 701, the fingerprint sensor 702 of the mobile phone 700 can collect the user's fingerprint. In response to the user's finger pressing the power button 701, the mobile phone 700 starts up, and at the same time, the user's fingerprint collected by the fingerprint sensor can be directly used for user identity verification. If the verification is passed, the mobile phone is unlocked and the home screen shown in 703 (home screen) interface.

It can be seen from FIG. 19 that by pressing the power button, the mobile phone 700 in the off state can be turned on and logged into the operating system, which is simple and efficient. Moreover, the integration level can be improved, which is conducive to the miniaturization of mobile phones.

The foregoing mainly introduces the solution provided by the embodiment of the present application from the perspective of the process of the user's finger pressing the power button of the electronic device to start the electronic device. It can be understood that, in order to implement the above-mentioned functions, the device includes functional modules corresponding to each function. Those skilled in the art should easily realize that in combination with the terminals and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

The embodiments of the present application may divide devices according to the foregoing method examples. For example, each module or unit may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware, or in the form of software modules or units. Among them, the division of modules or units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.

The embodiment of the present invention also provides a computer storage medium, the computer storage medium stores computer program code, when the processor of the electronic device executes the computer program code, the device executes the relevant method steps in any of the foregoing embodiments. The device booting method in the above embodiment.

The embodiment of the present invention also provides a computer program product, which when the computer program product runs on a computer, causes the computer to execute the relevant method steps in any of the foregoing embodiments to implement the device booting method in the foregoing embodiment.

Among them, the electronic device, computer storage medium or computer program product provided in the embodiments of the present invention are all used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the corresponding method provided above The beneficial effects in the process will not be repeated here.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above-mentioned functional modules is used as an example. In practical applications, the above-mentioned functions can be allocated according to needs. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the above-described system, device, and unit, reference may be made to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be It can be combined or integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of 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 technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any change or replacement within the technical scope disclosed in this application shall be covered by the protection scope of this application. . Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for logging in to an operating system, which is applied to an electronic device, characterized in that the electronic device includes a power button, a fingerprint sensor, an embedded controller EC, and a central processing unit CPU; the power button and the fingerprint The sensor is integrated; wherein the EC is connected to the fingerprint sensor; the EC and the CPU communicate through a first interface, and the first interface is based on the sharing between the EC and the CPU Software communication interface created by memory;

The method includes:

The EC detects that the power button is pressed by the user's finger, and acquires the user fingerprint collected by the fingerprint sensor; the fingerprint sensor collects the fingerprint when the power button is pressed by the user's finger;

The EC encrypts the user fingerprint, and stores the encrypted user fingerprint in the internal storage space of the EC;

The EC obtains the fingerprint verification instruction from the CPU through the first interface;

In response to the fingerprint verification instruction, the EC transmits the encrypted user fingerprint to the CPU through the first interface;

The CPU performs user identity verification according to the user fingerprint, and if the verification is passed, logs in to the operating system of the electronic device.
The method according to claim 1, wherein the CPU is used to run a basic input output system (BIOS); the method further comprises: the BIOS notifies the EC and the CPU of the address of the shared memory.
The method according to any one of claims 1-2, further comprising:

After transmitting the encrypted user fingerprint to the CPU through the first interface, the EC deletes the user fingerprint stored in the EC.
The method according to any one of claims 1-3, further comprising:

If the time for the EC to store the encrypted user fingerprint exceeds the first time, and the fingerprint verification instruction sent from the CPU has not been received through the first interface, the EC is deleted and stored in the The user fingerprint inside the EC.
The method according to any one of claims 1 to 4, further comprising: the CPU writing the fingerprint verification instruction into the shared memory.
The method of claim 5, wherein the CPU and the EC also communicate through a general-purpose input and output interface GPIO interface; the method further comprises: writing to the shared memory on the CPU After entering the fingerprint verification instruction, the CPU sends a first notification to the EC through the GPIO interface; the first notification is used to notify the EC to read the fingerprint verification instruction from the shared memory.
The method according to claim 5 or 6, wherein the EC obtains the fingerprint verification instruction from the CPU through the first interface, which specifically includes: the EC obtains the fingerprint verification instruction from the shared computer through the first interface The fingerprint verification instruction written by the CPU into the shared memory is read from the memory.
7. The method of any one of claims 5-7, wherein the operating system is loaded with a fingerprint sensor driver; and the CPU writing the fingerprint verification instruction to the shared memory specifically includes:

The operating system running on the CPU sends a fingerprint verification request to the fingerprint sensor driver running on the CPU;

In response to the fingerprint verification request, the fingerprint sensor driver running on the CPU writes the fingerprint verification instruction into the shared memory.
7. The method according to any one of claims 1-7, wherein the EC transmitting the encrypted user fingerprint to the CPU through the first interface comprises:

The EC writes the encrypted user fingerprint into the shared memory through the first interface;

The CPU reads the encrypted user fingerprint from the shared memory.
The method according to claim 9, characterized in that the communication between the CPU and the EC is also through a universal input and output interface GPIO interface; further comprising:

After the EC writes the encrypted user fingerprint into the shared memory through the first interface, the EC sends a second notification to the CPU through the GPIO interface; the second notification is used for Notifying the CPU to read the encrypted user fingerprint from the shared memory.
The method of claim 9, wherein the CPU reading the encrypted user fingerprint from the shared memory specifically includes:

The fingerprint sensor driver running on the CPU reads the encrypted user fingerprint from the shared memory;

The fingerprint sensor driver running on the CPU sends the encrypted user fingerprint to the operating system running on the CPU.
The method according to any one of claims 1-11, wherein the CPU performs user identity verification based on the user fingerprint, and if the verification is passed, logging in to the operating system, comprising:

The CPU determines whether the user fingerprint is consistent with the fingerprint template in the first storage area of the electronic device, and if they are consistent, the verification is passed and the operating system is logged in.
An electronic device, comprising: a power button, a fingerprint sensor, an embedded controller EC, and a central processing unit CPU; the power button and the fingerprint sensor are integrated; wherein the EC is connected to the fingerprint Sensor; the EC and the CPU communicate through a first interface, the first interface being a software communication interface created based on the shared memory between the EC and the CPU;

The EC is used to detect that the power button is pressed by the user's finger, and obtain the user fingerprint collected by the fingerprint sensor; the fingerprint sensor collects the fingerprint when the power button is pressed by the user's finger;

The EC is used to encrypt the user fingerprint, and the encrypted user fingerprint is stored in the internal storage space of the EC;

The EC is used to obtain a fingerprint verification instruction from the CPU through the first interface;

The EC is configured to respond to the fingerprint verification instruction and transmit the encrypted user fingerprint to the CPU through the first interface;

The CPU is configured to perform user identity verification according to the user fingerprint, and if the verification is passed, log in to the operating system of the electronic device.
The electronic device according to claim 13, wherein the CPU is used to run a basic input output system (BIOS); the BIOS is used to notify the EC and the CPU of the address of the shared memory.
The electronic device according to any one of claims 13-14, wherein the EC is further configured to delete the encrypted user fingerprint after transmitting the encrypted user fingerprint to the CPU through the first interface The user fingerprint inside the EC.
The electronic device according to any one of claims 13-15, wherein the EC is further configured to: if the time for the EC to store the encrypted user fingerprint exceeds the first time, pass the first time If an interface has not received the fingerprint verification instruction sent from the CPU, the user fingerprint stored in the EC is deleted.
15. The electronic device according to any one of claims 13-15, wherein the CPU is further configured to write the fingerprint verification instruction into the shared memory.
The electronic device according to claim 17, wherein the CPU and the EC also communicate through a general-purpose input and output interface GPIO interface; the CPU is also used to communicate between the CPU and the shared memory After the fingerprint verification instruction is written in, a first notification is sent to the EC through the GPIO interface; the first notification is used to notify the EC to read the fingerprint verification instruction from the shared memory.
The electronic device according to claim 17 or 18, wherein the EC is specifically used to read from the shared memory through the first interface all the information written by the CPU to the shared memory. Describe fingerprint verification instructions.
The electronic device according to any one of claims 13-19, wherein the EC is specifically configured to write the encrypted user fingerprint into the shared memory through the first interface; the CPU It is used to read the encrypted user fingerprint from the shared memory.
The electronic device according to claim 20, wherein the CPU and the EC also communicate through a universal input/output interface GPIO interface; the EC is specifically used to communicate with the EC through the first After the interface writes the encrypted user fingerprint into the shared memory, it sends a second notification to the CPU through the GPIO interface; the second notification is used to notify the CPU to read from the shared memory The encrypted user fingerprint.
The electronic device according to any one of claims 13-21, wherein the CPU is specifically configured to determine whether the user fingerprint is consistent with the fingerprint template in the first storage area of the electronic device, if If they are consistent, the verification is passed and the operating system is logged in.
A chip system, characterized in that, the chip system includes: an embedded controller and a processor CPU, the embedded controller and the processor CPU are integrated in an electronic device, and the electronic device also includes a power button, a fingerprint Sensor; the power button and the fingerprint sensor are integrated; wherein, the EC is connected to the fingerprint sensor; communication between the EC and the CPU through a first interface, the first interface is based on The software communication interface created by the shared memory between the EC and the CPU;

The EC is used to detect that the power button is pressed by the user's finger, and obtain the user fingerprint collected by the fingerprint sensor; the fingerprint sensor collects the fingerprint when the power button is pressed by the user's finger;

The EC is used to encrypt the user fingerprint, and the encrypted user fingerprint is stored in the internal storage space of the EC;

The EC is used to obtain a fingerprint verification instruction from the CPU through the first interface;

In response to the fingerprint verification instruction, the EC transmits the encrypted user fingerprint to the CPU through the first interface;

The CPU is configured to perform user identity verification according to the user fingerprint, and if the verification is passed, log in to the operating system of the electronic device.
The chip system according to claim 23, wherein the EC is further configured to delete all the user fingerprints stored in the EC after the encrypted user fingerprint is transmitted to the CPU through the first interface. Describe the user's fingerprint.
The chip system according to claim 23 or 24, wherein the EC is also used to, if the time for the EC to store the encrypted user fingerprint exceeds the first time, the first interface has not been used yet. When the fingerprint verification instruction sent from the CPU is received, the user fingerprint stored in the EC is deleted.
22. The chip system according to any one of claims 23-25, wherein the CPU is further configured to write the fingerprint verification instruction into the shared memory.
The chip system according to claim 26, wherein the CPU and the EC also communicate through a general-purpose input and output interface GPIO interface; the CPU is also used to communicate between the CPU and the shared memory After the fingerprint verification instruction is written in, a first notification is sent to the EC through the GPIO interface; the first notification is used to notify the EC to read the fingerprint verification instruction from the shared memory.
The chip system according to claim 26 or 27, wherein the EC is specifically used to read from the shared memory through the first interface all the CPU writes to the shared memory. Describe fingerprint verification instructions.
The chip system according to any one of claims 23-28, wherein the EC is specifically configured to write the encrypted user fingerprint into the shared memory through the first interface; the CPU It is used to read the encrypted user fingerprint from the shared memory.
The chip system according to claim 29, wherein the CPU and the EC also communicate through a general-purpose input and output interface GPIO interface; the EC is specifically used for, when the EC passes through the first After the interface writes the encrypted user fingerprint into the shared memory, it sends a second notification to the CPU through the GPIO interface; the second notification is used to notify the CPU to read from the shared memory The encrypted user fingerprint.
A computer-readable storage medium, including instructions, characterized in that the instructions run in the processor CPU of an electronic device; the electronic device further includes a power button, a fingerprint sensor, and an embedded controller EC; the power button Integrated with the fingerprint sensor; wherein, the EC is connected to the fingerprint sensor; the EC and the CPU communicate through a first interface, and the first interface is based on the EC and the CPU Software communication interface created between shared memory;

When the instruction runs in the processor CPU of the electronic device, the processor CPU is caused to execute the following steps:

The CPU transmits the fingerprint verification instruction to the EC;

Receiving, by the CPU, the encrypted user fingerprint sent by the EC;

The CPU performs user identity verification according to the user fingerprint, and if the verification is passed, logs in to the operating system of the electronic device.
The computer-readable storage medium of claim 31, wherein the CPU transmitting the fingerprint verification instruction to the EC specifically includes:

The CPU writes the fingerprint verification instruction into the shared memory.
The computer-readable storage medium according to claim 31 or 32, wherein the CPU receiving the encrypted user fingerprint sent by the EC specifically includes:

The CPU reads the encrypted user fingerprint from the shared memory.