A method of verifying a user's identity and an electronic device

Abstract

The embodiment of the application discloses a method for verifying user identity and an electronic device, relates to the terminal field, and can verify the identity of multiple face information collected at the same time in the identity verification process, provides the presence proof of multiple users, and thus reduces the security risks to the privacy and property of the user. The method comprises the following steps: an electronic device runs a target application and opens a multi-user joint identity verification function provided by the target application; the electronic device displays a first preview interface captured by a camera and prompts to input face information of multiple preset users in the first preview interface; the electronic device acquires N pieces of to-be-verified face information from the first preview interface, wherein N is an integer greater than 1; and if each piece of to-be-verified face information in the N pieces of to-be-verified face information is the face information of a preset user, the electronic device is allowed to continue running the target application.

Description

Technical Field

[0001] This application relates to the field of terminals, and more particularly to a method and electronic device for verifying user identity. Background Technology

[0002] Currently, methods for authenticating users by collecting their facial information are widely used in various electronic devices. For example, a mobile phone can collect the user's facial information through its camera while the screen is locked. If the collected facial information matches the pre-stored facial information of a legitimate user, the user's identity is verified, and the phone can automatically unlock the screen.

[0003] However, in some situations, it may be necessary to verify the identities of multiple users in the same scenario. For example, when signing contracts, promissory notes, or applying for documents (such as marriage certificates) or joint accounts online, multiple users need to be present to confirm the same information. In this case, if each user's facial information is collected and verified separately, even if each user passes verification, it is difficult to prove that these multiple users completed the verification of the aforementioned information at the same time and in the same place. For example, after user A completes verification using their facial information, user B's video could be used to forge user B's facial information and verify user B's identity. In this way, user A could sign the relevant contract with user B even when user B is not present. Obviously, this verification method poses a significant security risk to users' privacy and property. Summary of the Invention

[0004] This application provides a method and electronic device for verifying user identity, which can verify the identity of multiple facial information collected simultaneously during the identity verification process, provide proof of presence for multiple users, thereby reducing security risks to user privacy and property.

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

[0006] Firstly, this application provides a method for verifying user identity, comprising: an electronic device running a target application; when the multi-user joint authentication function provided in the target application is enabled, the electronic device displays a first preview interface captured by a camera and prompts the user to input facial information of multiple preset users in the first preview interface; the electronic device obtains N (N is an integer greater than 1) facial information to be verified from the first preview interface, that is, the preset multiple users need to simultaneously input facial information in the first preview interface for identity verification; if each of the N facial information to be verified is the facial information of a preset user, it indicates that the preset multiple users have completed identity authentication at the same time and place, then the electronic device can continue to run the target application, for example, the electronic device can open the target application or run the next function after successful identity authentication. If the N facial information to be verified includes facial information of a non-preset user, it indicates that the multi-user joint authentication has failed, and the electronic device can stop running the target application, thus ensuring the accuracy and security of multi-user identity authentication and reducing security risks to user privacy and property.

[0007] For example, the target application mentioned above can be a game application. By performing the aforementioned multi-user authentication when opening the game, it can be ensured that the user is using the game application with the authorization of other users, thereby improving the ability to supervise users of the game application. Alternatively, the target application mentioned above can be a payment application. By performing the aforementioned multi-user authentication when conducting property transactions, it can be ensured that multiple preset users are aware of and authorize the transaction, thereby improving the security of property transactions and reducing the probability of users' property being lost.

[0008] In one possible design approach, before the electronic device activates the multi-user authentication function provided by the target application, the method further includes: prompting the user to set the number of users to be authenticated when performing the multi-user authentication; in response to the number of users N entered by the user, the electronic device displays a second preview interface captured by the camera and obtains the facial information of N users from the second preview interface; the electronic device uses the N users as N preset users and establishes a correspondence between the target application and the facial information of the N authenticated users.

[0009] In one possible design approach, after the electronic device activates the multi-user authentication function provided by the target application, the method further includes: the electronic device acquiring the facial information of N preset users corresponding to the target application; and after the electronic device acquires the N facial information to be verified from the first preview interface, the method further includes: the electronic device comparing the N facial information to be verified with the facial information of the N preset users to determine that each facial information to be verified is the facial information of a preset user. Subsequently, each time multi-user authentication is performed in the target application, these N preset users must participate in completing the multi-user authentication to provide proof of multi-user presence when using the target application.

[0010] In one possible design approach, after the electronic device obtains the facial information of N authenticated users from the second preview interface, the method further includes: the electronic device recording the order of the facial information of the N preset users in the second preview interface; and after the electronic device obtains the facial information of N users to be verified from the first preview interface, the method further includes: the electronic device determining that the order of the N facial information to be verified in the first preview interface is the same as the order of the facial information of the N preset users in the second preview interface. Multi-user joint authentication can only be successfully passed when the order of the N facial information to be verified in the first preview interface is the same as the order of the N preset users' facial information in the second preview interface, thereby improving the accuracy of multi-user joint authentication.

[0011] In one possible design approach, the electronic device enables the multi-user authentication function provided by the target application, including: the electronic device automatically enables the multi-user authentication function when running the target application; or, the electronic device enables the multi-user authentication function in response to user input when running the target application.

[0012] In one possible design approach, the electronic device enables the multi-user authentication feature provided by the target application, including: enabling the multi-user authentication feature when the electronic device launches the target application; or enabling the multi-user authentication feature when the electronic device runs a first function provided by the target application.

[0013] In one possible design approach, if each of the N facial profiles to be verified is a preset user's facial profile, the electronic device is allowed to continue running the target application. This includes allowing the electronic device to continue running the target application for a preset time period if each of the N facial profiles to be verified is a preset user's facial profile. After the preset time period, the target application can again request the user to perform multi-user joint authentication, preventing users from becoming addicted to the target application due to prolonged use.

[0014] Secondly, this application provides a method for verifying user identity, comprising: an electronic device detecting that a user has opened a first function of a target application, the first function being a function requiring multi-user joint authentication by N users (N being an integer greater than 1); the electronic device displaying a first input interface and prompting the user to input the identity information of N users in the first input interface; the electronic device obtaining the N identity information from the first input interface; the electronic device displaying a first preview interface captured by a camera and prompting the N users to input facial information in the first preview interface; the electronic device obtaining the N facial information from the first preview interface, i.e., simultaneously obtaining the facial information of multiple users in the first preview interface for authentication; furthermore, the electronic device sending a verification request to a server, the verification request including the N identity information and the N facial information, so that the server performs multi-user joint authentication on the N users; if a message indicating successful multi-user joint authentication is received from the server, it indicates that the first function has been authorized by multiple users, and the electronic device can execute the first function.

[0015] If a message indicating a failure of multi-user authentication is received from the server, it means that the multi-user authentication has failed. The electronic device can refuse to perform the first function, ensuring the accuracy and security of multi-user authentication and reducing security risks to user privacy and property.

[0016] For example, the aforementioned target application could be an online contract signing application that performs multi-user joint authentication on all parties involved in signing the contract to provide proof of their presence and prevent subsequent contract disputes. As another example, the aforementioned target application could be an online document processing or joint account service application that performs multi-user joint authentication on all parties involved in the service to prove that all parties are present and authorize the service to be processed, preventing other users from impersonating legitimate users to process related transactions. As yet another example, the aforementioned target application could be an online application for processing jointly owned property (e.g., marital property) on multiple users, performing multi-user joint authentication on all owners of the jointly owned property to ensure that all owners are present and aware of the transaction details, thereby reducing security risks to user assets.

[0017] In one possible design approach, before the electronic device sends a verification request to the server, the method further includes: the electronic device displaying the correspondence between the N identity information and the N facial information, and prompting the user to confirm the use of the N identity information and the N facial information to perform the first function; wherein, the electronic device sending a verification request to the server includes: if the user's confirmation operation on the aforementioned N identity information and N facial information is detected, the electronic device sends the verification request to the server.

[0018] In one possible design approach, before the electronic device detects that the user has opened the first function of the target application, the following steps are also included: the electronic device obtains the identity information entered by the user in the second input interface; the electronic device obtains the facial information entered by the user in the second preview interface; the electronic device sends a registration request to the server, which includes the user's identity information and facial information, so that the server establishes a correspondence between the user's identity information and facial information, thereby completing the registration process for the multi-user joint authentication function.

[0019] Thirdly, this application provides a method for verifying user identity, comprising: a server receiving a verification request sent by an electronic device, the verification request including N identity information and N face information to be verified; the server obtaining N registered face information corresponding to each of the N identity information, the server storing the correspondence between the identity information and face information of each registered user; the server determining that the N registered face information and the N face information to be verified correspond one-to-one; and the server sending a message to the electronic device that the multi-user joint authentication has been successful.

[0020] In one possible design approach, before the server receives the verification request sent by the electronic device, the method further includes: the server receiving a registration request sent by the electronic device, the registration request containing the user's identity information and facial information; and the server establishing a correspondence between the user's identity information and facial information.

[0021] In one possible design approach, before the server establishes the correspondence between the user's identity information and facial information, it also includes: the server queries a preset database to find that the user's identity information is correct, thus preventing unauthorized users from registering for multi-user joint authentication.

[0022] In one possible design approach, the user's identity information includes the user's avatar information; wherein, after the server receives the registration request sent by the electronic device, the process further includes: the server determining that the avatar information in the identity information corresponds to the facial information, thereby ensuring the authenticity and validity of the facial information and identity information uploaded by the user.

[0023] Fourthly, this application provides an electronic device, comprising: a processing unit for running a target application and enabling a multi-user authentication function provided by the target application; a display unit for displaying a first preview interface captured by a camera and prompting the user to input facial information of multiple preset users in the first preview interface; an acquisition unit for acquiring N facial information to be verified from the first preview interface, where N is an integer greater than 1; and a processing unit further configured to allow the electronic device to continue running the target application if each of the N facial information to be verified is a facial information of a preset user.

[0024] In one possible design approach, the aforementioned display unit is further configured to prompt the user to set the number of users to be authenticated when performing multi-user joint authentication; the display unit is further configured to display a second preview interface captured by the camera in response to the number of users N entered by the user, and to obtain the facial information of N users from the second preview interface; the processing unit is further configured to establish a correspondence between the target application and the facial information of the N authenticated users as N preset users.

[0025] In one possible design method, the acquisition unit is further configured to acquire the facial information of N preset users corresponding to the target application; the processing unit is further configured to determine that each facial information to be verified is the facial information of a preset user by comparing the N facial information to be verified with the facial information of the N preset users.

[0026] In one possible design approach, the processing unit is further configured to record in the memory the order of the facial information of the N preset users in the second preview interface; and to determine that the order of the facial information of the N to be verified in the first preview interface is the same as the order of the facial information of the N preset users in the second preview interface.

[0027] In one possible design approach, the aforementioned processing unit is specifically configured to automatically enable the multi-user authentication function when the target application is running; or, when the target application is running, to enable the multi-user authentication function in response to user input.

[0028] In one possible design approach, the aforementioned processing unit is specifically configured to enable the multi-user authentication function when the target application is launched; or, to enable the multi-user authentication function when the first function provided by the target application is run.

[0029] In one possible design approach, if each of the N face information to be verified is the face information of a preset user, then the above processing unit is specifically used to allow the electronic device to continue running the target application within a preset time period.

[0030] Fifthly, this application provides an electronic device, comprising: an acquisition unit, configured to detect a user opening a first function of a target application, the first function being a function requiring multi-user joint authentication by N users, where N is an integer greater than 1; a display unit, configured to display a first input interface and prompt the user to input the identity information of N users in the first input interface; display a first preview interface captured by a camera and prompt the N users to input facial information in the first preview interface; the acquisition unit is further configured to acquire the N identity information from the first input interface; and acquire the N facial information from the first preview interface; a communication unit, configured to send a verification request to a server, the verification request including the N identity information and the N facial information, so that the server performs multi-user joint authentication on the N users; and a processing unit, configured to execute the first function if a message indicating successful multi-user joint authentication is received from the server.

[0031] In one possible design approach, the display unit is further configured to display the correspondence between the N identity information and the N facial information, and prompt the user to confirm the use of the N identity information and the N facial information to perform the first function; if the user's confirmation operation of the N identity information and the N facial information is detected, the communication unit sends the verification request to the server.

[0032] In one possible design approach, the aforementioned acquisition unit is further configured to acquire the identity information entered by the user in the second input interface; acquire the facial information entered by the user in the second preview interface; and the communication unit is further configured to send a registration request to the server, the registration request containing the user's identity information and facial information, so that the server can establish a correspondence between the user's identity information and facial information.

[0033] Sixthly, this application provides a server, comprising: a communication unit for receiving a verification request sent by an electronic device, the verification request including N identity information and N face information to be verified; a processing unit for acquiring N registered face information corresponding to the N identity information respectively, the server storing the correspondence between the identity information and face information of each registered user; determining that the N registered face information and the N face information to be verified correspond one-to-one; and the communication unit further for sending a message of successful multi-user joint authentication to the electronic device.

[0034] In one possible design approach, the communication unit is further configured to receive a registration request sent by an electronic device, the registration request containing the user's identity information and facial information; the processing unit is further configured to establish a correspondence between the user's identity information and facial information.

[0035] In one possible design approach, the aforementioned processing unit is further configured to query a preset database to confirm that the user's identity information is correct.

[0036] In one possible design approach, the user's identity information includes the user's avatar information; the aforementioned processing unit is further configured to determine whether the avatar information in the identity information corresponds to the facial information.

[0037] In a seventh aspect, this application provides an electronic device, including a processor, a communication module, an input device, an output device, and a memory, all coupled to the processor, as well as one or more computer programs; the one or more computer programs are stored in the memory, and when the electronic device is running, the processor executes the one or more computer programs stored in the memory to cause the electronic device to perform the method for verifying user identity as described in any one of the first or second aspects above.

[0038] For example, the processor is configured to: run the target application and enable the multi-user authentication function provided by the target application; the output device is configured to: display a first preview interface captured by the camera and prompt the user to input facial information of multiple preset users in the first preview interface; the input device is configured to: obtain N facial information to be verified from the first preview interface, where N is an integer greater than 1; the processor is further configured to: if each of the N facial information to be verified is the facial information of a preset user, then allow the electronic device to continue running the target application.

[0039] For example, the input device is used to: detect a user opening a first function of a target application, where the first function requires multi-user authentication by N users, and N is an integer greater than 1; the output device is used to: display a first input interface and prompt the user to input the identity information of N users in the first input interface; display a first preview interface captured by a camera and prompt the N users to input facial information in the first preview interface; the processor is used to: obtain N identity information from the first input interface; obtain N facial information from the first preview interface; instruct the communication module to send a verification request to the server, the verification request including the N identity information and the N facial information, so that the server performs multi-user authentication on the N users; if a message indicating successful multi-user authentication is received from the server, the first function is executed.

[0040] Eighthly, this application provides a server, including a processor, a communication module and a memory coupled to the processor, and one or more computer programs; the one or more computer programs are stored in the memory, and when the server is running, the processor executes the one or more computer programs stored in the memory to cause the server to perform the method for verifying user identity as described in any of the third aspects above.

[0041] For example, the communication module is configured to: receive a verification request sent by an electronic device, the verification request including N identity information and N face information to be verified; the processor is configured to: acquire N registered face information corresponding to the N identity information respectively, the memory storing the correspondence between the identity information and face information of each registered user; determine that the N registered face information and the N face information to be verified correspond one-to-one; the communication module is further configured to: send a message to the electronic device that the multi-user joint authentication has been successful.

[0042] Ninthly, this application provides a computer storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform a method for verifying user identity as described in any one of the first or second aspects.

[0043] In a tenth aspect, this application provides a computer storage medium including computer instructions that, when executed on a server, cause the server to perform a method for verifying user identity as described in any one of the first and third aspects.

[0044] In one aspect, this application provides a computer program product that, when run on an electronic device, causes the electronic device to perform a method for verifying user identity as described in any one of the first or second aspects.

[0045] In a twelfth aspect, this application provides a computer program product that, when run on a server, causes the server to perform the method for verifying user identity as described in any of the third aspects.

[0046] It is understood that the electronic devices described in the fourth, fifth, and seventh aspects, the servers described in the sixth and eighth aspects, the computer storage media described in the ninth and tenth aspects, and the computer program products described in the eleventh and twelfth aspects are all used to perform the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0047] Figure 1A schematic diagram of the structure of an electronic device provided in this application embodiment. Figure 1 ;

[0048] Figure 2 An architecture diagram of an operating system in an electronic device provided in an embodiment of this application;

[0049] Figure 3 A flowchart illustrating a method for verifying user identity provided in this application embodiment. Figure 1 ;

[0050] Figure 4 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 1 ;

[0051] Figure 5 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 2 ;

[0052] Figure 6 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 3 ;

[0053] Figure 7 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 4 ;

[0054] Figure 8 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 5 ;

[0055] Figure 9 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 6 ;

[0056] Figure 10 A flowchart illustrating a method for verifying user identity provided in this application embodiment. Figure 2 ;

[0057] Figure 11 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 7 ;

[0058] Figure 12 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 8 ;

[0059] Figure 13 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 9 ;

[0060] Figure 14 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 10 ;

[0061] Figure 15 A flowchart illustrating a method for verifying user identity provided in this application embodiment. Figure 3 ;

[0062] Figure 16 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 10 one;

[0063] Figure 17 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 10 two;

[0064] Figure 18 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 10 three;

[0065] Figure 19 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 10 Four;

[0066] Figure 20 A flowchart illustrating a method for verifying user identity provided in this application embodiment. Figure 4 ;

[0067] Figure 21 A flowchart illustrating a method for verifying user identity provided in this application embodiment. Figure 5 ;

[0068] Figure 22 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 10 five;

[0069] Figure 23 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 10 six;

[0070] Figure 24 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 10 seven;

[0071] Figure 25 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 10 eight;

[0072] Figure 26 A scenario illustration of a method for verifying user identity provided in this application embodiment. Figure 10 Nine;

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

[0074] Figure 28 A schematic diagram of the structure of an electronic device provided in this application embodiment. Figure 3 ;

[0075] Figure 29 A schematic diagram of the structure of a server provided in this application embodiment. Figure 1 ;

[0076] Figure 30 A schematic diagram of the structure of a server provided in this application embodiment. Figure 2 . Detailed Implementation

[0077] The implementation of this embodiment will now be described in detail with reference to the accompanying drawings.

[0078] The method for verifying user identity provided in this application embodiment can be applied to mobile phones, tablets, desktops, laptops, notebook computers, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, personal digital assistants (PDAs), wearable electronic devices, virtual reality devices, etc. The specific form of the electronic device is not specifically limited in the following embodiments.

[0079] Figure 1 A schematic diagram of the structure of the electronic device 100 is shown.

[0080] Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc.

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

[0082] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0083] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

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

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

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

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

[0088] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, internal memory 121, external memory, display screen 194, camera 193, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

[0089] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

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

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

[0092] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

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

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

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

[0096] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

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

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

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

[0100] In this embodiment of the application, the camera 193 can send the captured image to a processor (e.g., a GPU processor), and the processor can extract one or more facial information from the image using a certain face recognition algorithm.

[0101] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when electronic device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.

[0102] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. Thus, electronic device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0103] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

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

[0105] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

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

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

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

[0109] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the electronic device 100 answers a telephone call or voice message, the receiver 170B can be brought close to the ear to listen to the voice.

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

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

[0112] The sensor module 180 may specifically include one or more of the following: pressure sensor, gyroscope sensor, barometric pressure sensor, magnetic sensor, accelerometer, distance sensor, proximity sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor, or bone conduction sensor. This application embodiment does not impose any limitations on this.

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

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

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

[0116] The software system of the aforementioned electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses the layered architecture Android system as an example to exemplify the software structure of the electronic device 100.

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

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

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

[0120] The application package can include applications such as camera, gallery, calendar, call, map, navigation, Bluetooth, music, video, and SMS.

[0121] In the embodiments of this application, such as Figure 2 As shown, the application layer can also include target applications that require simultaneous authentication of multiple users.

[0122] For example, the target application mentioned above could be a game application. When the user of the game application is under a certain age (e.g., 13 years old), the identity of the user and their guardian can be verified at the same time when the game application is opened, thereby ensuring that the user is using the game application with the permission or accompaniment of their guardian.

[0123] For example, the target application mentioned above could be a payment application. When a user uses a payment application to make a large transaction, the payment application can require all relevant personnel involved in the transaction to undergo identity verification, thereby ensuring that the relevant personnel are aware of the transaction.

[0124] For example, the aforementioned target applications could also be online applications released by government agencies for handling related business. For instance, when transferring vehicle ownership, both the old and new owners are required to be present to complete the transfer procedures; in this case, the application can be used to verify the identities of the old and new owners. Similarly, when applying for a marriage certificate, both the man and woman are required to be present to complete the relevant procedures; in this case, the application can be used to verify the identities of both parties. Furthermore, when signing a contract, both Party A and Party B are required to be present to confirm the contract contents; in this case, the application can be used to verify the identities of Party A and Party B.

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

[0126] like Figure 2As shown, the application framework layer can include an authentication service, which provides multi-user federated authentication functionality to the target application. For example, the target application can call the authentication service to obtain users' facial information for registration, authentication, and other processes. For instance, the authentication service can use a driver to call image sensors such as cameras to collect facial information containing multiple users' faces. Furthermore, the authentication service can calculate the number of faces in the collected facial information and perform liveness detection. Additionally, the authentication service can extract facial features from each face in the facial information and compare these extracted features with the facial features of registered users to determine whether the multiple users currently undergoing authentication are legitimate.

[0127] It should be noted that the above authentication service can run in a rich execution environment (REE), or in a more secure environment such as a trusted execution environment (TEE) or a secure element (SE). Of course, a portion of the authentication service can run in an REE, and another portion in a TEE; this application does not impose any restrictions on this.

[0128] In addition, the application framework layer may also include drawing services (such as SurfaceFlinger), window managers, content providers, phone managers, resource managers, notification managers, etc.

[0129] The drawing service can be used to construct the application's display pages. A display page can consist of one or more views. For example, a display page including a text message notification icon can include a view displaying text and a view displaying images. The window manager manages window programs. The window manager can obtain the screen size, determine if a status bar is present, lock the screen, capture the screen, etc. The content provider stores and retrieves data, making this data accessible to applications. This data can include videos, images, audio, dialed and received calls, browsing history and bookmarks, phone books, etc. The phone manager provides communication functions for the electronic device 100. For example, it manages call status (including connection, hang-up, etc.). The resource manager provides various resources to the application, such as localized strings, icons, images, layout files, video files, etc. The notification manager allows applications to display notification information in the status bar. It can be used to convey informational messages and can disappear automatically after a short pause without user interaction. For example, the notification manager is used to notify of download completion, message reminders, etc. The notification manager can also display notifications as icons or scrollbar text in the system's top status bar, such as notifications from background applications, or as dialog windows on the screen. For example, displaying text messages in the status bar, emitting notification sounds, causing electronic devices to vibrate, or flashing indicator lights.

[0130] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

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

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

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

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

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

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

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

[0138] The kernel layer is the layer between hardware and software. The kernel layer includes at least display drivers, camera drivers, audio drivers, sensor drivers, etc., but this application embodiment does not impose any limitations on this.

[0139] For example, before a target application in electronic device 100 needs to authenticate multiple users simultaneously, each user who needs to be authenticated must register their identity information and facial information in electronic device 100.

[0140] Taking a mobile phone as an electronic device 100 as an example, the user of the mobile phone can be one or more family members. To facilitate subsequent use of the multi-user authentication function provided by the target application on the mobile phone by each user, each family member can register their identity information and facial information on the mobile phone through the following steps S301-S305. For example... Figure 3 As shown, steps S301-S305 specifically include:

[0141] S301, The mobile phone prompts the user to enter identity information.

[0142] For example, a mobile phone may prompt a user to enter identity information when the user installs or uses the target application for the first time. Taking a game app as an example, such as... Figure 4 As shown in (a), after a user opens the registration function of the game app on their mobile phone, the phone can display the registration interface 401. The registration interface 401 has options for filling in the user's name, age, gender, mobile phone number, and ID card number, prompting the user to enter the corresponding identity information in the registration interface 401.

[0143] Alternatively, the user-entered identity information may not be directly associated with the target application. For example, the phone could offer a multi-user authentication feature in its system settings. When the system detects that a user has activated this feature for the first time, such as... Figure 4As shown in (b) above, the mobile phone can display the registration interface 402. Similar to the registration interface 401 described above, the registration interface 402 can also set options for filling in one or more identity information such as the registered user's name, age, gender, mobile phone number, and ID card number. This application embodiment does not impose any restrictions on this.

[0144] S302. In response to user A's input operation, the mobile phone obtains user A's identity information.

[0145] Taking the above registration interface 402 as an example, such as Figure 5 As shown, users wishing to register (e.g., user A) can enter their name, age, gender, mobile phone number, and ID card number in the corresponding fields on the registration interface 402. If the system detects that the user clicks the "Next" button 403 on the registration interface 401, the mobile phone can save the identity information entered by the user on the registration interface 401 as user A's identity information locally.

[0146] S303: The phone prompts the user to enter facial information.

[0147] For example, after detecting that the user clicks the "Next" button 403, the phone can access its camera (e.g., the front-facing camera) to capture the currently captured preview interface and use a preset face detection algorithm to detect whether facial information exists in the preview interface. Figure 6 As shown, the mobile phone can display the content captured by the camera in the preview interface 601. For example, the mobile phone can display the content captured by the camera in a preset area 602 of the preview interface 601. The mobile phone can prompt the user to adjust the position of the face in the preview interface 601 so that the mobile phone can detect the user's face in the preset area 602 of the preview interface 601.

[0148] S304. The mobile phone uses its camera to obtain the facial information input by user A.

[0149] like Figure 7 As shown, when user A completely places their face into the preset area 602 of the preview interface 601, the mobile phone can recognize the facial information within the preset area 602 and save the recognized facial information locally. For example, after detecting a face within the preset area 602, the mobile phone can extract corresponding facial features based on the image information within the preset area 602. For instance, the extracted facial features can be a feature matrix, which the mobile phone can save locally.

[0150] After obtaining user A's facial information, it is still like... Figure 7As shown, the phone can also display a 701 message indicating successful facial recognition registration. Subsequently, the phone can use the facial information registered by user A during registration to authenticate user A's identity. Furthermore, after obtaining user A's facial information, it will still... Figure 7 As shown, the phone can also display a back button 702 and a next button 703. If the user clicks the back button 702, the phone can delete the facial information acquired this time and return to the preview interface 601 to recapture and detect facial information. If the user clicks the back button 703, it means that the user confirms the use of the facial information entered this time as the basis for subsequent identity verification, and the phone can continue to execute step S305.

[0151] Of course, if the phone fails to recognize the face information within the preset area 602 within the preset time, or repeatedly detects that the face information entered by the user is incomplete, the phone may display a registration failure message and exit the registration process.

[0152] S305. The mobile phone establishes a correspondence between user A's identity information and facial information, and prompts user A that the registration is successful.

[0153] In step S305, as Figure 8 As shown, the mobile phone can display the user A's identity information and facial information obtained in steps S302 and S304 respectively on the touchscreen and prompt the user for confirmation. If the user clicks the confirmation button 801, it means that the user agrees to bind the entered identity information with the facial information, and the mobile phone can establish a correspondence between user A's identity information and facial information in a preset database. For example, a facial feature database and an identity information database can be set up in the mobile phone in advance. The mobile phone can save the obtained user A's facial information in the facial feature database and generate a facial feature index for that facial information. Then, the mobile phone can store the correspondence between user A's facial feature index and user A's identity information in the identity information database. In this way, when performing user authentication later, the mobile phone can find the facial feature index corresponding to the identity information in the identity information database based on the user's entered identity information, and then find the corresponding facial information in the facial feature database based on the facial feature index. Of course, if the user clicks the confirmation button 801, it means that the user agrees to bind the entered identity information with the facial information, and then finds the corresponding facial information in the facial feature database based on the facial feature index. Figure 8 The back button 802 shown in the figure allows the phone to return to the previous menu, enabling the user to modify the entered identity information and / or facial information. This application embodiment does not impose any restrictions on this.

[0154] Additionally, after detecting that the user clicked the confirmation button 801, such as Figure 9As shown, the phone can also display a message 901 indicating that user A has successfully registered. Furthermore, the phone can display an option 902 to add other registered users. If the phone detects that a user clicks option 902, it can continue with steps S301-S305 to register other users (e.g., user B and user C) who can use the multi-user authentication function.

[0155] In this way, different users can complete the registration process for the multi-user joint authentication function on their mobile phones through the above steps S301-S305. Each registered user will establish a correspondence between their identity information and facial information on their mobile phone. Subsequently, when the mobile phone needs to authenticate multiple users simultaneously to provide proof of their presence, the mobile phone can authenticate multiple facial information appearing in the same captured image separately. When multiple facial information appearing in the same image are all registered users, the mobile phone can determine that the multi-user joint authentication has passed, indicating that these multiple users have completed identity authentication at the same time and place, ensuring the accuracy and security of multi-user identity authentication.

[0156] After multiple users have registered for the multi-user authentication function on the aforementioned mobile phones, before using the multi-user authentication function, users can enable the multi-user authentication function in the target application through the following steps S1001-S1006. Of course, if users do not need to use the multi-user authentication function in the target application (such as the aforementioned game app), for example, if parents do not need their guardians to accompany them when using the game app, users can skip the following steps S1001-S1006 to open the game app.

[0157] For example, such as Figure 10 As shown, steps S1001-S1006 specifically include:

[0158] S1001. After detecting that the user has enabled the multi-user authentication function in the target application, the mobile phone prompts the user to select the number of users for multi-user authentication.

[0159] Taking a game app as an example, such as Figure 11 As shown in (a), when the phone detects that a user has opened a game app, if the multi-user authentication function in the game app is not enabled, the phone can display an enable button 1101 to enable the multi-user authentication function. After detecting that the user has clicked the enable button 1101, it indicates that the user subsequently wants to enable the multi-user authentication function to prove that they are using the game app accompanied by someone else. At this time, if... Figure 11 As shown in (b), the mobile phone can prompt the user to enter the number of users who will subsequently participate in multi-user joint authentication.

[0160] In some embodiments, the phone can also automatically enable multi-user authentication for the user in the target application. For example, when it detects that a user has opened a game app, the phone can automatically activate the front-facing camera to capture an image of the user using the game app. If the user image indicates that the user is young (e.g., under 10 years old), the phone can automatically enable multi-user authentication and prompt the user to select the number of users for multi-user authentication.

[0161] S1002. When the number of users is N (N>1), the mobile phone prompts the user to enter N facial information in the preview interface.

[0162] For example, if a user selects two users for multi-user authentication, the phone will detect the user's selection of two users and then... Figure 12 As shown, the mobile phone can use its camera (such as the front-facing camera) to capture and display the currently captured preview interface 1201. Furthermore, the mobile phone can prompt the user to input the facial information of user 1 and user 2 at designated locations on the preview interface 1201.

[0163] For example, when a user selects two users for joint authentication, the phone can mark two areas in the preview interface 1201 based on that number of users. Figure 12 The images show areas 1202 and 1203. These two areas are used to collect the facial information of user 1 and user 2, respectively. Thus, users A and B participating in multi-user joint authentication can adjust their positions in preview interface 1201 according to the prompts, enabling the mobile phone to detect the facial information of user 1 (e.g., user A) in area 1202 of preview interface 1201, and also detect the facial information of user 2 (e.g., user B) in area 1202 of preview interface 1201.

[0164] S1003: The mobile phone obtains N facial information from the preview interface.

[0165] S1004. The mobile phone confirms that the above N facial information are all facial information of registered users.

[0166] like Figure 13As shown, after the phone detects facial information in both areas 1202 and 1203 of the preview interface 1201, it can determine that the number of faces is the same as the number of users set by the user (i.e., 2). The phone can then check whether the facial information in areas 1202 and 1203 belongs to a registered user. If the number of facial images collected is different from the number of users set by the user, the phone can prompt the user that the number of faces entered in the preview interface 1201 is incorrect and return to the preview interface 1201 to re-collect facial information.

[0167] For example, the mobile phone can match the facial information extracted from area 1202 with the facial information of registered users A, B, and C in the facial feature database. If the facial information in area 1202 matches the facial information of user A, it means that the face captured in area 1202 is the face of user A, and the mobile phone can find the identity information of user A in the identity information database based on the facial feature index of user A.

[0168] Similarly, the mobile phone can match the facial information extracted from area 1203 with the facial information of registered users A, B, and C in the facial feature database. If the facial information in area 1203 matches user B's facial information, it means that the face captured in area 1203 is user B's face. The mobile phone can then search for user B's identity information in the identity information database based on user B's facial feature index. In this way, the mobile phone can determine that the two facial information pieces collected in preview interface 1201 are both from registered users.

[0169] Additionally, if the phone determines that one or more facial images collected this time do not belong to a registered user, the phone can display a registration button to prompt unregistered users to register their identity and facial information on the phone. If the phone detects that a user has clicked the registration button, it can register the new user's identity and facial information through the steps S301-S305 described above.

[0170] In some embodiments of this application, after the mobile phone detects facial information in areas 1202 and 1203, it can also perform liveness detection on the facial information in areas 1202 and 1203, that is, confirm that the facial image captured by the mobile phone belongs to a real, live user, and is not a fake facial information such as a picture or video. For example, the mobile phone can use a temperature sensor to detect whether the temperature distribution in areas 1202 and 1203 matches the surface temperature distribution of a face. If it matches the surface temperature distribution of a face, then it can be considered that the liveness detection has passed. As another example, the mobile phone can also ask the user to blink, open their mouth, or read a passage of text to identify whether the user in areas 1202 and 1203 is a live user. This application embodiment does not impose any limitations on this.

[0171] S1005. The mobile phone prompts the user to confirm the correspondence between the above N facial information and the corresponding N identity information.

[0172] S1006. If a user's confirmation operation is detected, the mobile phone establishes a correspondence between the target application, the aforementioned N facial information, and the aforementioned N identity information.

[0173] For example, after the mobile phone determines that the facial information in areas 1202 and 1203 are the facial information of registered user A and registered user B respectively, as follows: Figure 14 As shown, the mobile phone can display the facial and identity information of user A and user B on the touchscreen to prompt the user for confirmation. If the user clicks the confirmation button 1401, it means that the user agrees to multi-user joint authentication by user A and user B when running the game app subsequently. Therefore, the mobile phone can establish a correspondence between the game app, user A's facial and identity information, and user B's facial and identity information.

[0174] For example, the mobile phone can pre-store an authentication registration table as shown in Table 1. This authentication registration table is used to record the correspondence between each application that enables multi-user joint authentication and its corresponding multiple preset users. In this embodiment, the multiple preset users corresponding to the application can be referred to as the application's authenticated users. For example, the authenticated users of a game app include user A and user B. If a user clicks... Figure 14 The confirmation button 1401 shown allows the phone to record the game app's ID (e.g., the app's package name) and the relevant information (e.g., identity information and facial information) of the authenticated users (i.e., user A and user B) in the authentication registration table. This way, when the phone detects that a user has opened the game app, it can determine whether the user currently undergoing authentication is a user recorded in the authentication registration table, as shown in Table 1.

[0175] Application ID Identity information Facial information Game App ID User A's identity information User A's facial information User B's identity information User B's facial information Payment App ID User B's identity information User B's facial information User C's identity information User C's facial information

[0176] It should be noted that the process of enabling multi-user authentication in the target application on the mobile phone (i.e., S1001-S1006 above) only needs to be completed once by the user in the target application. In other words, after the user sets user A and user B as the authenticated users for multi-user authentication in the target application through S1001-S1006 above, each subsequent time multi-user authentication is performed in the target application, user A and user B must participate in completing the multi-user authentication together to provide proof of multi-user presence when using the target application.

[0177] Of course, users can also change the authenticated users performing multi-user federated authentication in the target application through the above steps S1001-S1006. For example, by enabling the multi-user federated authentication function, the authenticated users can be changed from user A and user B to user A and user C. This application embodiment does not impose any restrictions on this.

[0178] After a user sets user A and user B as authenticated users by enabling multi-user authentication in the target application, if the phone detects that the user has enabled multi-user authentication in the target application, it can perform the following steps S1501-S1505 to perform multi-user authentication. For example, as shown... Figure 15 As shown, steps S1501-S1505 specifically include:

[0179] S1501. After detecting that a user has enabled the multi-user authentication function in the target application, the mobile phone determines the authenticated user corresponding to the target application.

[0180] Using the aforementioned game app as an example, the phone can display a verification button for multi-user authentication when entering the game app, or it can display the verification button when accessing a specific function within the game app. For example... Figure 16 As shown, after detecting that the user has opened the game APP, if the user has already enabled the multi-user authentication function in the target application (i.e., S1001-S1006 above), the phone can display the verification button 1601 to prompt the user to perform multi-user authentication.

[0181] In some embodiments, the mobile phone can also automatically enable multi-user authentication in certain scenarios. For example, after detecting that a user has opened a game app, the phone can ask the user to enter their age. If the user is young (e.g., under 10 years old), the phone can automatically enable the multi-user authentication function in the game app. Alternatively, the user can set the phone to child mode. If the phone is in child mode when the user opens the game app, the phone can automatically enable the multi-user authentication function in the game app. Or, the phone can monitor the game app's runtime. When the game app's runtime on the phone exceeds a preset time (e.g., 2 hours), the phone can automatically enable the multi-user authentication function in the game app.

[0182] After enabling the multi-user authentication function of a game app on a mobile phone, the phone can retrieve the relevant information of the authenticated users corresponding to the game app from the authentication registration table shown in Table 1, based on the game app's ID. For example, the authenticated users corresponding to the game app include user A and user B. Then, the phone can retrieve the corresponding facial feature index from the identity information database based on user A's identity information, and subsequently, retrieve user A's facial information from the facial feature database based on user A's facial feature index. Similarly, the phone can retrieve the corresponding facial feature index from the identity information database based on user B's identity information, and subsequently, retrieve user B's facial information from the facial feature database based on user B's facial feature index.

[0183] S1502. The mobile phone prompts the user to enter the facial information of N (N>1) authenticated users in the preview interface.

[0184] After the mobile phone identifies the verified users corresponding to the game app as user A and user B, such as Figure 17 As shown, the phone can use its camera (e.g., the front-facing camera) to capture and display the currently captured preview interface 1701. Furthermore, since the phone has already determined that the game app corresponds to two authenticated users, it will still... Figure 17 As shown, the phone can mark two areas (i.e., area 1702 and area 1703) in the preview interface 1701 to prompt the user to enter the facial information of each authenticated user in these two areas respectively.

[0185] Furthermore, the phone can prompt the user to input facial information in the preview interface 1701 according to the positional relationship of multiple authenticated users when the multi-user authentication function is enabled. The phone can then determine whether the multi-user authentication has succeeded based on the positional relationship of each facial information in the preview interface 1701. For example, when the multi-user authentication function is enabled, user A's facial information is on the left side of the preview interface, and user B's facial information is on the right side. Therefore, during the actual multi-user authentication process, user A needs to input their facial information on the left side of the preview interface (i.e., area 1702), and user B needs to input their facial information on the right side of the preview interface (i.e., area 1703); otherwise, the phone can determine that the multi-user authentication has failed.

[0186] S1503: The mobile phone obtains N facial information from the preview interface.

[0187] S1504. The mobile phone confirms that the above N facial information are all facial information of the authenticated user.

[0188] If the phone extracts facial information in areas 1702 and 1703 of the preview interface 1701, the phone can determine that the number of people currently undergoing identity verification is the same as the number of verified users. Then, the phone can determine one by one whether the facial information in areas 1702 and 1703 is the facial information of the verified users (i.e., user A and user B).

[0189] For example, if the authenticated user corresponding to area 1702 is user A, then the mobile phone can compare the facial information collected in area 1702 with the facial information of user A. When the similarity between the facial information in area 1702 and the facial information of user A is greater than a preset value, it can be determined that the facial information in area 1702 is the facial information of the authenticated user A.

[0190] Similarly, if the authenticated user corresponding to area 1703 is user B, then the mobile phone can compare the facial information collected in area 1703 with the facial information of user B. When the similarity between the facial information in area 1703 and the facial information of user B is greater than a preset value, it can be determined that the facial information in area 1703 is the facial information of the authenticated user B. In this way, the mobile phone can determine that the two facial information collected in the preview interface 1701 are the facial information of the two authenticated users preset by the user in steps S1001-S1006, and the positional relationship of these two facial information in the preview interface 1701 also conforms to the positional relationship set by the user in steps S1001-S1006.

[0191] S1505: The phone displays a message indicating successful multi-user authentication and continues running the target application.

[0192] like Figure 18 As shown in (a), if the N facial images collected by the mobile phone during this multi-user authentication process correspond one-to-one with the facial images of the N authenticated users of the game app, the mobile phone can display message 1801 indicating successful multi-user authentication. Of course, successful multi-user authentication means the user has permission to use the game app, and the mobile phone can continue to run the target application (i.e., the game app). For example, the mobile phone can automatically open the game app and enter its homepage.

[0193] Alternatively, if the phone determines that one or more facial images collected during this multi-user joint authentication process do not belong to the authenticated user, then... Figure 18 As shown in (b), the phone may display a message indicating that multi-user authentication failed. In this case, the user does not have permission to use the game app, and the phone cannot access the game app's homepage to continue running the game app.

[0194] Furthermore, after successful multi-user authentication, the phone can set a validity period for the successful authentication. For example, with a validity period of 2 hours, after a user successfully authenticates in a game app, the phone allows the user to use the game app for 2 hours. If the phone detects that the game app is still running in the foreground after 2 hours, it can prompt the user to perform multi-user authentication again. In other words, when the game app's running time exceeds the aforementioned validity period, the phone can repeatedly execute steps S1501-S1505 to perform multi-user authentication, preventing users from becoming addicted to the game.

[0195] Furthermore, the above embodiments use a game app as the target app for illustration. It is understood that the mobile phone can also set up multi-user authentication functionality in other applications to simultaneously verify the identities of multiple users, thereby providing proof of presence for multiple users when implementing a certain function on the mobile phone. For example, the target app could also be a payment app. If the user sets the authentication users for the multi-user authentication function in the payment app as user B and user C through the above steps S1001-S1006, then, as... Figure 19 As shown, when the mobile phone detects that the transaction amount in the payment app exceeds a preset limit (e.g., 20,000), the phone may prompt users B and C to enter their facial information for multi-user joint authentication. If users B and C pass the multi-user joint authentication in the payment app, it means that the authenticated users (i.e., users B and C) bound to the payment app have been aware of and authorized this large transaction. The phone can then proceed with completing the transaction, thereby improving the security of financial transactions and reducing the probability of users suffering financial losses.

[0196] In other words, if multi-user authentication is enabled when opening the target application, then after multi-user authentication, the phone can continue to run the target application because the phone can open the target application and enter its display interface; if multi-user authentication is enabled when running a certain function of the target application (such as the payment function mentioned above), then after multi-user authentication, the phone can continue to run the target application because the phone can continue to execute that function.

[0197] It should be noted that the above embodiments illustrate the example of registering, enabling, and implementing multi-user authentication locally on the mobile phone. It is understood that the mobile phone can also complete the registration and verification process for multi-user authentication by interacting with a server.

[0198] For example, similar to steps S301-S305 above, before using the multi-user authentication function provided by the target application, the mobile phone can register the user's identity information and facial information in the server through the following steps S2001-S2008. Figure 20 As shown, steps S2001-S2008 specifically include:

[0199] S2001, The mobile phone prompts the user to enter identity information.

[0200] S2002. In response to user A's input operation, the mobile phone obtains user A's identity information.

[0201] S2003, The mobile phone prompts the user to enter facial information.

[0202] S2004. The mobile phone uses its camera to obtain the facial information input by user A.

[0203] The implementation process of steps S2001-S2004 is the same as that of steps S301-S304 in the above embodiment, so it will not be described again here.

[0204] S2005. The mobile phone sends a registration request to the server. The registration request includes user A's identity information and facial information.

[0205] After the mobile phone obtains user A's facial information and identity information, it can encrypt the facial information and identity information and send them to the server in the registration request. The server will then perform the following steps S2006-S2008 to complete user A's registration process.

[0206] S2006. The server determines that user A's identity information is valid.

[0207] After receiving user A's identity information and facial information, the server can first check if it stores the same identity information or facial information. If no match is found, it means that the identity information and facial information of user A sent at this time have not been registered with the server.

[0208] Therefore, the server can verify whether user A's identity information is authentic and valid through the Ministry of Public Security or other authoritative identity databases. For example, the identity information sent by user A via mobile phone includes user A's name and ID number. The server can request the aforementioned identity database to query whether there is a user whose name and ID number match user A's. If a user whose name and ID number match user A can be found in the identity database, it means that the identity information entered by user A on the mobile phone is authentic and valid. Otherwise, it means that the identity information entered by user A on the mobile phone is incorrect, and the server can send a registration failure result to the mobile phone.

[0209] In some embodiments of this application, the identity information of user A sent by the mobile phone may include user A's facial information. For example, when prompting the user to enter identity information, the mobile phone may require the user to enter a photo of their ID card, which generally contains the user's portrait. In this case, the identity information collected by the mobile phone is the information on user A's ID card, which also includes user A's facial information. Therefore, before the server verifies user A's identity information with the identity database, the server can compare the facial information in user A's identity information with the facial information collected by the mobile phone. If the similarity between the two facial information is greater than a threshold, it indicates that the identity information and facial information uploaded by user A correspond. Furthermore, the server can verify with the identity database whether user A's identity information is valid, thereby ensuring the authenticity and validity of the facial information and identity information uploaded by user A.

[0210] S2007. The server establishes a correspondence between user A's identity information and facial information.

[0211] If the identity information entered by user A on their mobile phone is determined to be valid, the server can store user A's identity information and facial information on the server, establishing a correspondence between them. Through this registration method, the server can store the correspondence between the identity information and facial information of multiple users. Subsequently, the server can find the corresponding facial information based on the user's identity information, and then verify the user's identity based on that facial information.

[0212] S2008. The server sends the registration result of user A's successful registration to the mobile phone so that the mobile phone can display the registration result.

[0213] After the server establishes the correspondence between user A's identity information and facial information, it indicates that user A has completed registration on the server. At this point, the server can send a registration result to the mobile phone indicating that user A has successfully registered. Upon receiving the registration result, the mobile phone can display a message indicating successful registration to the user.

[0214] Unlike steps S301-S305 described above, since the user's identity information and facial information are stored on the server, each user can complete the registration process using different mobile phones through steps S2001-S2008. For example, user B can register their identity information and facial information on the server using their own mobile phone; user C can also register their identity information and facial information on the server using their own mobile phone.

[0215] Subsequently, when the target application on the phone needs to authenticate multiple users simultaneously to provide proof of their presence, the phone can capture images containing multiple facial images and send them to the server. The server then performs multi-user joint authentication on the collected facial images based on the registered user's facial information. If the multi-user joint authentication passes, it means that these multiple users have completed identity authentication at the same time and place, ensuring the accuracy and security of multi-user identity authentication.

[0216] After multiple users participating in multi-user authentication have successfully registered their identity and facial information with the server via their mobile phones, if it is detected that a user has enabled the multi-user authentication function in the target application, the mobile phone can perform the following steps S2101-S2108 to perform multi-user authentication. For example, as shown... Figure 21 As shown, steps S2101-S2108 specifically include:

[0217] S2101. After detecting that a user has enabled the multi-user authentication function in the target application, the mobile phone prompts M (M>1) users participating in the multi-user authentication function to enter their identity information respectively.

[0218] S2102. The mobile phone obtains M identity information input by M users respectively.

[0219] In this embodiment, a multi-user authentication function can be set in the target application. For example, when the target application is a game app, multi-user authentication can be performed when the game app is opened. As another example, when the target application is a payment app, multi-user authentication can be performed when large transactions are conducted. Yet another example, when the target application is an application related to online document processing, multi-user authentication can be performed on multiple users related to the document processing.

[0220] Taking a vehicle management app as an example, this app provides users with the function of handling vehicle transfer procedures online. For instance... Figure 22 As shown, the vehicle management app displays a "Transfer Ownership" button (2201) on its homepage. If a user clicks the "Transfer Ownership" button (2201), it means that the user (e.g., user A) wishes to transfer ownership of their vehicle to another user (e.g., user B). In this case, the vehicle management app needs to perform multi-user joint authentication on both users involved in the vehicle transfer to ensure that there is no dispute between them regarding the transfer.

[0221] Therefore, if a user clicks the transfer button 2201, it means the user has enabled the multi-user authentication function in the vehicle management app. At this time, as follows... Figure 23 As shown in (a), the mobile phone can redirect to the input interface 2301 of the vehicle management APP. In input interface 2301, the mobile phone prompts the previous owner (i.e., the old owner) to enter their identity information. After User A, as the old owner, enters their identity information in input interface 2301, they can click the "Confirm" button 2302 to submit their identity information. If the phone detects that the user has clicked the "Next" button 2302, it can retrieve the identity information entered by User A in input interface 2301.

[0222] Additionally, after detecting that the user clicked the OK button 2302 on the input interface 2301, as follows: Figure 23 As shown in (b), the mobile phone can jump to the input interface 2303 of the vehicle management APP. In the input interface 2303, the mobile phone can prompt the new owner (i.e., the new owner) to enter their identity information. After User B, as the old owner, enters their identity information in the input interface 2303, they can click the next button 2304 to submit their identity information. If the mobile phone detects that the user has clicked the next button 2304 in the input interface 2303, it can obtain the identity information entered by User B in the input interface 2303.

[0223] The above embodiment illustrates the use of a mobile phone to obtain the identity information of two users, A and B. In different application scenarios, the number of users participating in the multi-user joint authentication function can vary. For example, when signing a tripartite agreement online in the target application, the mobile phone needs to obtain the identity information of three users.

[0224] S2103, The mobile phone prompts M users participating in the multi-user joint authentication function to enter their facial information on the same preview interface.

[0225] Taking the aforementioned vehicle management app as an example, after the mobile phone obtains the identity information of the new car owner (User A) and the old car owner (User B), such as... Figure 24 As shown, the mobile phone can use its camera (e.g., the front-facing camera) to capture and display the currently captured preview interface 2401. Furthermore, the mobile phone can mark the input area 2402 for the new car owner's facial information and the input area 2403 for the old car owner's facial information in the preview interface 2401, thereby prompting user A and user B to input their facial information in the preview interface 2401.

[0226] S2104. The mobile phone obtains M facial information to be verified from the preview interface.

[0227] After the phone displays the preview interface 2401, it can detect in real time whether a face exists in input areas 2402 and 2403. When a face is detected in input areas 2402 and 2403, the phone can extract the facial information from input areas 2402 and 2403. Both of these facial information are used for subsequent multi-user joint authentication.

[0228] In other words, when multiple users need to be authenticated, the verification method provided in this application can collect the facial information of these multiple users in the same preview interface, thereby ensuring that these multiple users are aware of and confirm certain information (such as the aforementioned transfer procedures) at the same time and in the same scenario. Such a verification method provides proof of presence for multiple users, which can reduce the security risks caused by information asymmetry in transactions involving multiple users.

[0229] S2105. The mobile phone sends a verification request to the server. The verification request includes the above M identity information and M facial information to be verified.

[0230] After obtaining the identity information of the new car owner (User A) and the old car owner (User B), as well as the facial information of Users A and B to be verified, the mobile phone can encrypt this identity information and facial information using an encryption method agreed upon with the server. Then, the mobile phone can send the encrypted M pieces of identity information and M pieces of facial information to be verified in a verification request to the server, avoiding the security risk of information leakage during the interaction between the mobile phone and the server.

[0231] In some embodiments, such as Figure 25 As shown, before sending a verification request to the server, the mobile phone can first display the collected identity and facial information of the new and old car owners to the user, allowing the user to confirm whether to use the collected identity and facial information for vehicle transfer. If the user clicks on... Figure 25If the confirmation button 2401 is shown, the mobile phone can send the above verification request to the server.

[0232] For example, after detecting that the user clicks the confirmation button 2401, the mobile phone can use the collected facial information and the vehicle transfer operation confirmed by the user to generate a digest of the verification request through cryptographic algorithms such as hash algorithms. Then, the mobile phone can send the encrypted operation content, identity information, facial information, and digest to the server in the verification request.

[0233] S2106. The server finds the corresponding M registered facial information based on the M identity information.

[0234] S2107. The server determines that the above M registered facial information corresponds one-to-one with the above M unverified facial information.

[0235] In step S2106, after the server receives the verification request sent by the mobile phone, if the verification request is encrypted, the server can use the corresponding decryption algorithm to decrypt the verification request and obtain the identity information and the face information to be verified carried in the verification request.

[0236] For example, the server can use a corresponding decryption algorithm to decrypt the operation content, identity information, facial information, and digest carried in this verification request. Then, the server can verify the integrity of the received facial information and operation content through the digest, ensuring that the information received by the server has not been tampered with and that the user is aware of the operation content corresponding to this authentication (i.e., vehicle transfer operation). This prevents attackers from intercepting the user's facial information and using it for authentication applications for other operations without the user's knowledge.

[0237] After receiving the M identity information pieces from the verification request, the server can further determine whether all users undergoing multi-user authentication are registered users already registered on the server. Since each user stores their identity information and corresponding facial information on the server during registration, the server can check if it has the identity information of user A and user B stored locally. If user A and user B's identity information is stored, it means that both user A and user B requesting multi-user authentication are registered users. Then, the mobile phone can find the facial information corresponding to user A's identity information and the facial information corresponding to user B's identity information—that is, the registered facial information.

[0238] In step S2107, after the mobile phone obtains the registered facial information corresponding to user A's identity information, the mobile phone can compare the registered facial information with the facial information to be verified entered by user A in the verification request. If the similarity between the two is greater than a threshold, it means that user A's identity verification in this multi-user joint authentication is successful.

[0239] Similarly, after the mobile phone obtains the registered facial information corresponding to User B's identity information, it can compare this registered facial information with the facial information entered by User B in the verification request. If the similarity is greater than a threshold, it indicates that User B's identity verification for this multi-user joint authentication is successful. If both User A and User B's identity verification is successful, then the multi-user joint authentication is confirmed to be successful. This multi-user joint authentication provides proof of presence for User A and User B, thereby ensuring that User A and User B authorized and confirmed the transfer procedures at the same time and in the same scenario, preventing other users from impersonating User A or User B to complete the transfer procedures and causing financial losses to the users.

[0240] S2108. The server sends a message to the mobile phone indicating that the multi-user joint authentication has been successful.

[0241] After both User A and User B have successfully authenticated, the server can send a message to the mobile phone confirming successful multi-user authentication. At this point, if... Figure 26 As shown, the mobile phone can display a message indicating successful multi-user authentication. Furthermore, the phone can automatically redirect to the next step in the vehicle transfer process (such as the online license plate selection interface), allowing the user to continue completing other procedures.

[0242] Furthermore, if user A and / or user B fail to authenticate during the multi-user authentication process, the server determines that the multi-user authentication has failed. The server can then send a multi-user authentication failure message to the mobile phone. The mobile phone will also display the multi-user authentication failure message. At this point, the mobile phone will not be able to proceed to the next step of the vehicle transfer procedure, preventing unauthorized users from impersonating legitimate users and endangering users' property security.

[0243] It should be noted that the above embodiments use a vehicle management app as an example. It is understood that the identity verification method provided in this application can also be applied to other scenarios requiring simultaneous verification of multiple user identities. For example, when using an online contract signing application, the above identity verification method can be used to perform multi-user joint identity verification on multiple parties involved in signing the contract, providing proof of their presence to avoid subsequent contract disputes. As another example, when processing marriage certificates or joint accounts online, the above identity verification method can be used to perform multi-user joint identity verification on multiple parties involved in the process, proving that all parties are present and authorize the process, preventing other users from impersonating legitimate users. As yet another example, when processing jointly owned property (e.g., marital property) online, the above identity verification method can be used to perform multi-user joint identity verification on all owners of the jointly owned property, ensuring that all owners are present and aware of the transaction details, thereby reducing security risks to user property.

[0244] In some embodiments, Figure 27 A possible structural schematic diagram of the electronic device involved in the above embodiments is shown. The electronic device includes: an acquisition unit 2701, a processing unit 2702, a display unit 2703, and a communication unit 2704.

[0245] The acquisition unit 2701 is used to support the electronic device in performing operations. Figure 3 Processes S302 and S304 in the process, and Figure 10 In process S1003, and Figure 15 In process S1503, and Figure 20 Processes S2002 and S2004 in the process, and Figure 21 Processes S2102 and S2104 are described in the text; the processing unit 2702 is used to support the electronic device in performing these processes. Figure 3 In process S305, and Figure 10 Processes S1004-S1006 in the process, and Figure 15 The processes S1504-S1505 are described in detail; the display unit 2703 is used to support the execution of electronic devices. Figure 3 Processes S301 and S303 in the process, and Figure 10 The processes S1001-S1002, and Figure 15 The processes S1501, S1502, and S1505, and Figure 20 The processes S2001 and S2003, and Figure 21 The processes S2101 and S2103 are described in the text; the communication unit 2704 is used to support the electronic device in performing these processes. Figure 20 Processes S2005 and S2008, and Figure 21 The processes S2105 and S2108 are described above. All relevant content regarding each step in the above method embodiments can be found in the functional descriptions of the corresponding functional modules, and will not be repeated here.

[0246] In other embodiments, Figure 28 A schematic diagram of a possible structure of the electronic device involved in the above embodiments is shown. The electronic device includes a processor 2801, a memory 2802, an input device 2803, an output device 2804, and a communication module 2805. The number of processor 2801, memory 2802, input device 2803, output device 2804, and communication module 2805 can be one or more. Figure 28 (Taking quantity as an example), they can communicate with each other via bus 2806.

[0247] Specifically, processor 2801 can be... Figure 1 The processor 110 is shown. Processor 2801 can be used to control and manage the operation of electronic devices. For example, processor 2801 can be a central processing unit (CPU), GPU, general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of DSP and microprocessor, etc.

[0248] The memory 2802 can specifically be Figure 1 The internal memory 121 and external memory 120 are shown. Memory 2802 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as disk storage devices, flash memory devices or other volatile solid-state storage devices.

[0249] Input device 2803 can be Figure 1 The microphone 170C shown or the touch sensor in the sensor module 180, etc., are devices that receive information input by the user.

[0250] Output device 2804 can be a display or other device used to display information input by the user, information provided to the user, and various menus of electronic devices. Specifically, it can be configured as a liquid crystal display (LCD), organic light-emitting diode (OLED), or similar device. For example, output device 2804 can be... Figure 1 The speaker 170A or display screen 194 is shown. Additionally, a touch sensor may be integrated on the display screen 194 to collect touch events on or near it and send the collected touch information to other devices (such as a processor).

[0251] The communication module 2805 can be a transceiver, transceiver circuit, or communication interface, etc. For example, it can be a Bluetooth device, a Wi-Fi device, or a peripheral interface. For instance, the communication module 2805 can specifically be... Figure 1 The radio frequency module 150 and communication module 160 shown are examples of these.

[0252] In some embodiments, Figure 29 A possible structural diagram of the server involved in the above embodiments is shown. The server includes: a communication unit 2901, a processing unit 2902, and a determination unit 2903.

[0253] Communication unit 2901 is used to support server execution Figure 20 Processes S2005 and S2008, and Figure 21 Processes S2105 and S2108 are described in the text; processing unit 2902 is used to support server execution. Figure 20 In process S2007, and Figure 21 The process S2106; the determination unit 2903 is used to support server execution. Figure 20 In process S2006, and Figure 21 The process S2107 is described above. All relevant content regarding each step in the above method embodiment can be found in the functional descriptions of the corresponding functional modules, and will not be repeated here.

[0254] In other embodiments, Figure 30 A schematic diagram of a possible structure of the server involved in the above embodiments is shown. The server includes a processor 3001, a memory 3002, and a communication module 3003. The number of processors 3001, memory 3002, and communication modules 3003 can be one or more. Figure 28 (Taking quantity as an example), they can communicate with each other via bus 3004.

[0255] The processor 3001 can be used to control and manage the operation of electronic devices. For example, the processor 3001 can be a central processing unit (CPU), GPU, general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0256] The memory 3002 is used to store the server's program code and data. For example, the memory 3002 may include high-speed random access memory (RAM), and may also include non-volatile memory, such as disk storage devices, flash memory devices, or other volatile solid-state storage devices.

[0257] The communication module 3003 is used to support communication between the server and other network entities. For example, the communication module 3003 may be a transceiver, transceiver circuit, or communication interface.

[0258] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0259] In the embodiments of this application, the functional units can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0260] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as flash memory, portable hard disk, read-only memory, random access memory, magnetic disk, or optical disk.

[0261] The above description is merely a specific implementation of the embodiments of this application, but the protection scope of the embodiments of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the embodiments of this application should be covered within the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of this application should be determined by the protection scope of the claims.

Claims

1. A method of verifying the identity of a user, characterized by, The method comprises the following steps: an electronic device runs a target application; the electronic device prompts a user to set a number N of users to be authenticated when performing multi-user joint authentication; in response to the user inputting the number N of users, the electronic device displays a second preview interface captured by a camera and acquires face information of N users from the second preview interface; the electronic device establishes a corresponding relationship between the target application and the face information of the N authentication users by taking the N users as N preset users; the electronic device records the order between the face information of the N preset users in the second preview interface; the electronic device opens a multi-user joint authentication function provided by the target application; the electronic device displays a first preview interface captured by the camera and prompts to input face information of a plurality of preset users in the first preview interface; the electronic device acquires N pieces of to-be-verified face information from the first preview interface, N being an integer greater than 1; if each piece of to-be-verified face information in the N pieces of to-be-verified face information is face information of a preset user, and the electronic device determines that the order between the N pieces of to-be-verified face information in the first preview interface is the same as the order between the face information of the N preset users in the second preview interface, the electronic device is allowed to continue running the target application.

2. The method of claim 1, wherein, After the electronic device opens the multi-user joint authentication function provided by the target application, the method further comprises the following steps: the electronic device acquires face information of N preset users corresponding to the target application; after the electronic device acquires N pieces of to-be-verified face information from the first preview interface, the method further comprises the following steps: the electronic device determines that each piece of to-be-verified face information is face information of a preset user by comparing the N pieces of to-be-verified face information with the face information of the N preset users.

3. The method according to claim 1 or 2, characterized in that, The electronic device opens the multi-user joint authentication function provided by the target application, comprising: the electronic device automatically opens the multi-user joint authentication function when running the target application; or the electronic device opens the multi-user joint authentication function in response to user input when running the target application.

4. The method according to claim 1 or 2, characterized in that, The electronic device opens the multi-user joint authentication function provided by the target application, comprising: the electronic device opens the multi-user joint authentication function when starting the target application; or the electronic device opens the multi-user joint authentication function when running a first function provided by the target application.

5. The method according to claim 1 or 2, characterized in that, If each piece of to-be-verified face information in the N pieces of to-be-verified face information is face information of a preset user, the electronic device is allowed to continue running the target application, comprising: If each piece of to-be-verified face information in the N pieces of to-be-verified face information is face information of a preset user, the electronic device is allowed to continue running the target application within a preset time period.

6. An electronic device, comprising: The electronic device comprises a processor, an input device, an output device and a memory which are all coupled with the processor; wherein The processor is configured to run a target application, and prompt a user to set a number N of authenticated users when performing multi-user joint identity verification; The input device is configured to receive the number N of users input by the user; The output device is configured to display a second preview interface captured by a camera; The processor is configured to obtain face information of N users from the second preview interface, take the N users as N preset users, establish a correspondence between the target application and the face information of the N authenticated users, and record an order between the face information of the N preset users in the second preview interface in the memory; The processor is further configured to open a multi-user joint identity verification function provided by the target application; The output device is further configured to display a first preview interface captured by the camera, and prompt input of face information of a plurality of preset users in the first preview interface; The input device is further configured to obtain N pieces of to-be-verified face information from the first preview interface, where N is an integer greater than 1; The processor is further configured to allow the electronic device to continue running the target application, if each piece of the N pieces of to-be-verified face information is face information of a preset user, and an order between the N pieces of to-be-verified face information in the first preview interface is the same as an order between the face information of the N preset users in the second preview interface.

7. The electronic device of claim 6, wherein The processor is further configured to obtain face information of N preset users corresponding to the target application, and determine that each piece of to-be-verified face information is face information of a preset user by comparing the N pieces of to-be-verified face information with the face information of the N preset users.

8. The electronic device of claim 6 or 7, wherein The processor is specifically configured to open the multi-user joint identity verification function when starting the target application, or open the multi-user joint identity verification function when running a first function provided by the target application.

9. The electronic device of claim 6 or 7, wherein The processor is specifically configured to allow the electronic device to continue running the target application within a preset time period, if each piece of the N pieces of to-be-verified face information is face information of a preset user.

10. A computer-readable storage medium having stored therein instructions, the computer-readable storage medium comprising: When the instructions are run on the electronic device, the electronic device is caused to perform the method of verifying a user identity according to any one of claims 1-5.

11. A computer program product comprising instructions, characterized in that, When the computer program product is run on the electronic device, the electronic device is caused to perform the method of verifying a user identity according to any one of claims 1-5.

Images