Communication methods and electronic devices

Abstract

This application provides a call method applied to an electronic device, which includes a first electronic device and a second electronic device. Both the first and second electronic devices are logged into a first account. The first and second electronic devices establish a connection based on near-field communication (NFC). In response to a message transmitted by the second electronic device after an incoming call, the first electronic device collects biometric information, compares the collected biometric information with the owner's biometric information synchronized from the second electronic device, obtains a comparison result, and transmits the comparison result to the second electronic device. In response to the second electronic device indicating that the comparison is successful, the second electronic device transmits incoming call data to the first electronic device to alert the user of the incoming call. Therefore, alerting the user of an incoming call on the first electronic device offers high convenience. Since the incoming call is only routed to the first electronic device after the owner's biometric information comparison is successful, this method improves convenience, reduces user disturbance, and saves power consumption during incoming call routing.

Description

Technical Field

[0001] This application relates to the field of electronic information technology, and in particular to a communication method and electronic device. Background Technology

[0002] In the field of electronic information technology, biometric information can be understood as biometric information (such as human body) used for authentication, such as fingerprints and facial recognition. Biometric information stored in electronic devices can be used as verification information for high-security operations such as unlocking and payment.

[0003] Making calls is a common function of electronic devices, used to make and receive calls via cellular networks. Summary of the Invention

[0004] This application provides a call method aimed at solving the problem of how to improve call functionality based on biometric information.

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

[0006] The first aspect of this application provides a call method applied to an electronic device, which includes a first electronic device and a second electronic device. Both the first and second electronic devices are logged into a first account, and a near-field communication (NFC)-based connection is established between them. The method includes: the first electronic device, in response to a message transmitted by the second electronic device after an incoming call, collecting biometric information, comparing the collected biometric information with the owner's biometric information synchronized from the second electronic device, obtaining a comparison result, transmitting the comparison result to the second electronic device, and, in response to the second electronic device indicating that the comparison is successful, transmitting incoming call data to the first electronic device to remind the user of the incoming call. It is evident that after the second electronic device receives an incoming call, it can remind the user of the incoming call on the first electronic device based on the owner's biometric information, which offers high convenience. Furthermore, the incoming call can only be transferred to the first electronic device after the owner's biometric information comparison is successful. Therefore, while improving convenience, it can reduce disturbance to the user and save power consumption during incoming call transfer.

[0007] In some implementations, the process of synchronizing the host biometric information from the second electronic device includes: the first electronic device, in response to establishing a near-field communication (NFC) connection with the second electronic device, acquires first version information and the host identification switch status of the second electronic device. The first version information includes version information of the host biometric information of the second electronic device. The first electronic device confirms that a first condition is met, including the host identification switch status indicating that the host identification function is enabled, and the first version information and the second version information being different. The second version information includes version information of the host biometric information in the first electronic device. The first electronic device then synchronizes the host biometric information from the second electronic device, and the synchronized host biometric information is used to implement the host identification function. It is evident that the prerequisites for biometric information synchronization between the two electronic devices are the establishment of NFC communication, the activation of the host identification function, and the difference in versions of the biometric information stored at both ends. Therefore, for biometric information, which is sensitive information, the synchronization method has high security and lays the foundation for the first electronic device to implement the host identification function.

[0008] In some implementations, the method provided by the first aspect further includes: the first electronic device deleting the owner's biometric information of the redundant electronic device. Since the redundant electronic device includes a device that has logged out of the first account and whose owner's biometric information is stored in the first electronic device, the redundant electronic device is very likely no longer to participate in owner identification and terminal collaboration. Therefore, deleting biometric information, which is sensitive information, can improve the security of biometric information.

[0009] In some implementations, the first electronic device synchronizes the host's biometric information from the second electronic device, including: the first electronic device receiving encrypted host biometric information transmitted by the second electronic device; encrypting the encrypted host biometric information using a key negotiated between the first and second electronic devices; and the first electronic device decrypting the encrypted host biometric information to obtain and store the host biometric information. Transmitting host biometric information via encrypted data offers high security.

[0010] In some implementations, the first condition also includes: the first electronic device has completed key negotiation with the second electronic device to further improve the security of biometric information transmission.

[0011] In some implementations, the process of the first electronic device and the second electronic device negotiating the key includes: in response to a key negotiation triggering condition, the first electronic device and the second electronic device perform key negotiation. The key negotiation triggering condition includes: the first electronic device and the second electronic device establish a connection based on near-field communication. Key negotiation is performed after the near-field communication is established, which can lay the foundation for the subsequent synchronization of biological information and reduce the latency of services based on biological information synchronization.

[0012] In some implementations, the key negotiation triggering conditions also include: the first electronic device or the second electronic device confirms that there is no key negotiation record with the other end, or the first electronic device is unable to decrypt the owner's biometric information synchronized from the second electronic device, so as to reduce the possibility of repeated key negotiation and thus save resources.

[0013] In some implementations, after the first electronic device and the second electronic device perform key negotiation, the method further includes: the first electronic device deleting the negotiated key in response to a key deletion condition, whereby the key deletion condition includes: the first electronic device and / or the second electronic device logging out of the first account. The purpose of deleting the key is to improve key security.

[0014] In some implementations, the method provided by the first aspect further includes: the first electronic device confirms that the second condition is met, and deletes the owner biometric information of the second electronic device in the first electronic device. The second condition includes at least one of the following: the owner identification switch status indicates that the owner identification function is turned off, the first electronic device logs out of the first account, the second electronic device logs out of the first account, and the first electronic device turns off the terminal collaboration function and / or biometric authentication function to improve the security of biometric information as sensitive information.

[0015] In some implementations, synchronizing the host's biometric information from the second electronic device includes: using a near-field communication (NFC) connection to synchronize the host's biometric information from the second electronic device and obtain first version information and the host identification switch status of the second electronic device; or using a cloud synchronization method based on a first account to obtain the first version information and the host identification switch status of the second electronic device. It is evident that the biometric information and the parameters of the first condition are obtained through two paths. Obtaining parameters through cloud synchronization is not limited to NFC-based connections, which not only provides greater independence and flexibility in data transmission but also improves the real-time performance of condition confirmation.

[0016] In some implementations, after the first electronic device responds to the incoming call data and alerts the user to the incoming call, the process further includes: the first electronic device responding to the operation of answering the call on its own device transmitting an answer message to the second electronic device, and responding to the status change message transmitted by the second electronic device, stopping the call alert and displaying the call interface. The status change message is transmitted by the second electronic device in response to the answer message. Therefore, this approach not only enables the flow of incoming call alerts but also the flow of answering calls, further improving convenience.

[0017] A second aspect of this application provides a call method applied to an electronic device. Both a first electronic device and a second electronic device are logged into a first account. The first and second electronic devices establish a connection based on near-field communication. The method includes: the second electronic device, in response to an incoming call notification, transmitting a message to the first electronic device. The message triggers the first electronic device to compare its collected biometric information with the owner's biometric information synchronized from the second electronic device, obtaining a comparison result. The second electronic device, in response to the comparison result transmitted by the first electronic device, determines the first electronic device as the target device. The second electronic device then transmits incoming call data to the target device, which is used by the target device to remind the user of incoming calls. Based on the owner's biometric information, incoming calls can be reminded on the first electronic device, offering high convenience. Furthermore, the incoming call is only routed to the first electronic device after the owner's biometric information comparison is successful. Therefore, while improving convenience, it reduces disturbance to the user and saves power consumption during incoming call routing.

[0018] In some implementations, before determining the first electronic device as the target device in response to the comparison result transmitted by the first electronic device, the method further includes: the second electronic device synchronizing the owner's biometric information to the first electronic device to lay the foundation for call flow based on owner identification.

[0019] In some implementations, the second electronic device synchronizes the host's biometric information with the first electronic device, including: the second electronic device encrypting the host's biometric information to obtain ciphertext of the host's biometric information, and then transmitting the ciphertext of the host's biometric information to the first electronic device. Using ciphertext transmission can improve security.

[0020] In some implementations, prior to encrypting the host's biometric information, the second electronic device, in response to a key negotiation triggering condition, engages in key negotiation with the first electronic device. The key negotiation triggering condition includes: the first electronic device and the second electronic device establishing a connection based on near-field communication.

[0021] In some implementations, the key negotiation triggering condition also includes: the first electronic device or the second electronic device confirming that there is no key negotiation record with the other end, so as to reduce the possibility of repeated key negotiation and thus save resources.

[0022] In some implementations, synchronizing the host's biometric information to the first electronic device includes: synchronizing the host's biometric information to the first electronic device via a near-field communication (NFC) connection. The method also includes: the second electronic device synchronizing the version information of the host's biometric information and the host identification switch status of the second electronic device to the first electronic device via cloud synchronization based on the first account. It is evident that the biometric information and the parameters of the first condition are obtained from two paths. Obtaining parameters through cloud synchronization is not limited to NFC-based connections, which not only provides greater independence and flexibility in data transmission but also improves the real-time performance of condition confirmation.

[0023] In some implementations, after transmitting incoming call data to the target, the process further includes: a second electronic device responding to an answer message transmitting a status change message to the first electronic device. This status change message triggers the first electronic device to stop call notifications and display the call interface. The answer message is triggered by the first electronic device responding to the operation of answering the incoming call on its own device. Therefore, in addition to transmitting call notifications, the system also allows answering calls on the first electronic device, further enhancing convenience.

[0024] In some implementations, before the second electronic device transmits a message to the first electronic device in response to an incoming call notification, the second electronic device further includes: enabling a device owner identification function based on the device owner's biometric information based on the user's operation on the interface, so as to facilitate the user's settings.

[0025] A third aspect of this application provides an electronic device, including: one or more processors and one or more memories, the memories storing one or more programs, which, when executed by the processor, cause the electronic device to perform the calling method provided in the first or second aspect of this application.

[0026] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform the call method provided in the first or second aspect of this application.

[0027] The fifth aspect of this application is a computer program product, which includes: computer program code, which, when run on an electronic device, causes the electronic device to perform the calling method provided in the first or second aspect of this application. Attached Figure Description

[0028] Figure 1 An example diagram showing multiple electronic devices in the same trust ring;

[0029] Figure 2 Example diagram showing how to set up terminal collaboration function;

[0030] Figure 3 Example diagram showing the implementation effect of terminal collaboration function;

[0031] Figure 4 This is an example diagram illustrating the implementation effect of terminal collaboration function based on device owner identification;

[0032] Figure 5 Example diagram of how to set up the device owner identification function;

[0033] Figure 6Example diagram of the hardware and software framework of an electronic device for implementing the call method disclosed in the embodiments of this application;

[0034] Figure 7 A flowchart illustrating the terminal collaboration function based on owner identification;

[0035] Figure 8 This is a flowchart of the call method disclosed in the embodiments of this application;

[0036] Figure 9 This is an example image of the main face of the memory chip in an electronic device;

[0037] Figure 10 A flowchart for key negotiation for electronic devices;

[0038] Figure 11 Example diagram of storing keys in an electronic device;

[0039] Figure 12 This is a structural example diagram of the electronic device disclosed in the embodiments of this application. Detailed Implementation

[0040] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions "a," "an," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, "one or more" refers to one, two, or more; "and / or" describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0041] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0042] The "multiple" mentioned in the embodiments of this application refers to two or more. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order.

[0043] Terminal collaboration can be understood as: when any electronic device on the same trust ring is using an application, other electronic devices on the same trust ring can continue using the application. It's important to understand that "terminal collaboration" is just an example; it could also be called "terminal cooperation," etc.

[0044] by Figure 1 For example, devices connected to the trust ring include mobile phone 1, laptop 2, tablet 3, smartwatch 4, and large screen 5. The conditions for electronic devices to connect to the same trust ring include: logging into the same account and establishing a connection based on near-field (and / or far-field) communication. The embodiments of this application will be illustrated using the near-field communication connection as an example.

[0045] The terminal collaboration function is set up as follows: For any electronic device (hereinafter referred to as the first electronic device), the terminal collaboration function is enabled by default in the out-of-box experience (OOBE) interface of the first electronic device, and the user needs to register an account and password and log in to the account in the OOBE interface.

[0046] If a user has disabled the terminal collaboration feature in the OOBE interface, or if the terminal collaboration feature is enabled but the user is not logged in, the user can enable the terminal collaboration feature through the settings of the electronic device.

[0047] With the first electronic device as Figure 1 Taking mobile phone 1 as an example, Figure 2 Interface A is the settings interface of mobile phone 1. Users can configure the terminal collaboration function through the terminal collaboration settings in interface A. After the user clicks the "Terminal Collaboration" control in interface A, the interface of mobile phone 1 switches to interface B. Interface B displays an introduction to the terminal collaboration function and the user agreement required to use it. Figure 1 (No restrictions are imposed). After the user clicks the "Agree" control, phone 1 will be redirected to interface C.

[0048] Interface C is the login screen. Only when mobile phone 1 is logged in can the terminal collaboration function be enabled. Understandably, if mobile phone 1 is already logged in before navigating to interface C (i.e., terminal collaboration is disabled but the account is logged in), then interface C can be hidden, and the logged-in account can be automatically entered in interface C, allowing the user to fill in the password, thus providing greater convenience.

[0049] After entering the account and password in interface C and clicking the "Next" button, phone 1 displays interface D. Interface D displays controls for various detailed functions under the terminal collaboration function. Here, we take the detailed functions "Super Call Continuation," "Super Call," "Super Notification," and "Super Keyboard and Mouse" as examples.

[0050] The Super Connect feature can be understood as allowing mobile phone 1 to continue using applications (excluding phone applications) with other electronic devices on the same trust ring. Interface D1 simply summarizes the Super Connect feature as "continuing to use applications with nearby devices." As shown in interface D1, after the "Super Connect" control is clicked, mobile phone 1 displays interface D1, which shows a toggle control k for the Super Connect feature. Turning on the toggle control k activates the Super Connect feature. To better guide the user, interface D1 displays an example of the Super Connect feature's usage: application 1 on mobile phone 1 continues to be used on laptop 2, tablet 3, and large screen 5. For example, if mobile phone 1 is playing a video, after mobile phone 1, laptop 2, and tablet 3 are connected to the same trust ring, not only will the video continue playing on mobile phone 1, but the currently playing video will also be simultaneously played on laptop 2 and tablet 3.

[0051] The Super Call function can be understood as allowing mobile phone 1 to synchronize incoming call alerts, answer incoming calls, display missed call notifications, and make calls with other electronic devices on the same trust ring. Referring to interface D2, the Super Call function can be simply summarized as "allowing nearby devices to make and receive calls." Taking interface D2 as an example, after the "Super Call" control is clicked, mobile phone 1 displays interface D2, which shows the Super Call function's on / off switch control k. Turning on switch control k enables the Super Call function. An example of the Super Call function's usage in interface D2: Mobile phone 1 has call functionality. Laptop 2, tablet 3, and large screen 5, all on the same trust ring as mobile phone 1, can alert and answer incoming calls on mobile phone 1 and display missed call notifications.

[0052] The Super Notification feature can be understood as follows: when mobile phone 1 sends a notification (such as display, ring, or vibrate), electronic devices on the same trust ring as mobile phone 1 also send notifications. Referring to interface D3, the Super Notification feature can be simply summarized as "automatic notification synchronization." Taking interface D3 as an example, after the "Super Notification" control is clicked, mobile phone 1 displays interface D3, which shows the Super Notification feature's toggle control k. Turning on toggle control k enables the Super Notification feature. Furthermore, on interface D3, the toggle controls k for each application can be used to turn Super Notifications on or off. As shown in interface D3, when the toggle controls k for applications 1 and 2 are turned on, the notifications from applications 1 and 2 are synchronized with electronic devices on the same trust ring.

[0053] Example of the Super Notification feature shown in interface D3: After mobile phone 1 receives a notification from application 2, both tablet 3 and laptop 2 on the same trust ring display the notification.

[0054] The Super Keyboard and Mouse function can be understood as electronic devices on the same trust ring sharing input devices. Since laptop 2 typically has a keyboard and touchpad, interface D4 simply summarizes the Super Keyboard and Mouse function as "sharing input devices with nearby laptops." Taking interface D4 as an example, after the "Super Keyboard and Mouse" control is clicked, phone 1 displays interface D4, which shows the Super Notification function's toggle control k. Turning on toggle control k activates the Super Keyboard and Mouse function. An example of the Super Keyboard and Mouse function's usage shown in interface D4: Phone 1 and tablet 3 on the same trust ring can share the laptop 2's keyboard and touchpad.

[0055] Understandably, the above-mentioned terminal collaboration functions are beneficial to improving the convenience of electronic devices, but some problems still exist.

[0056] Taking the Super Call function as an example, such as Figure 3 As shown, when mobile phone 1 receives call 1, in addition to mobile phone 1 itself displaying a call notification, laptop 2, tablet 3, smartwatch 4, and large screen 5, all within the same trust ring as mobile phone 1, also display call notifications. It is understandable that the call notification methods for each device can be preset. Figure 3 For example, both China and Israel display at least an incoming call notification interface.

[0057] During their research, the inventors discovered that the terminal collaboration function allows any application used by an electronic device connected to the same trust ring to continue on other electronic devices within the same trust ring. In certain scenarios, this indiscriminate connection across multiple devices presents the following problems: Firstly, it can cause significant interference to the user. For example, at home, a user might have multiple electronic devices, such as a mobile phone 1, a laptop 2, a tablet 3, a smartwatch 4, and a large screen 5, all logged into the same account and connected via near-field communication. However, the user might only be using one electronic device at a time, for example, using laptop 2. In this scenario, if… Figure 3 The multiple incoming call notifications from various devices can be quite disruptive to the user. Furthermore, since phone 1 needs to transmit incoming call data to laptop 2, tablet 3, smartwatch 4, and large screen 5 to ensure that multiple devices simultaneously notify the user of incoming call 1, this results in higher power consumption for phone 1.

[0058] To address the aforementioned issues, a device owner identification function can be added to the terminal collaboration feature. Taking the Super Call function as an example again... Figure 4 This is an example of the effect of the super call function based on device owner identification. Figure 4 In this scenario, assuming the user is using laptop 2, although tablet 3, smartwatch 4, and large screen 5 are in the same trust ring as mobile phone 1 and laptop 2, after receiving call 1, mobile phone 1 only displays the call notification interface on the laptop 2 that the user is using, while tablet 3, smartwatch 4, and large screen 5 do not notify the user of call 1 (e.g., they remain unchanged). This achieves terminal collaboration while reducing disturbance to the user and lowering the power consumption of electronic devices.

[0059] Understandably, in order to realize the super call function based on the owner identification, it is necessary to synchronize the biometric information used to identify the owner between electronic devices in the same trust ring. Because biometric information is sensitive information, the synchronization of biometric information has high security requirements.

[0060] The following will describe the call method provided in the embodiments of this application in the context of a super call service scenario based on owner identification.

[0061] Combination Figure 2 , Figure 5 Here is an example of setting up the owner identification function: Click the settings control f for more functions in interface D, and then click the "Extend Services" control in the pop-up window. The first electronic device will then switch to interface E, where the toggle control k for the owner identification function is displayed. The owner identification function can be turned on or off using the toggle control k.

[0062] In some implementations, terminal collaboration is enabled via the OOBE interface or via... Figure 2 After enabling any function under the terminal collaboration feature (such as Super Call or Super Notification) in the interface shown, the owner identification function is enabled by default. Users can disable or re-enable the owner identification function through interface E.

[0063] It is understood that the biometric information used to identify the owner includes, but is not limited to, human biometric information such as fingerprints, voiceprints, facial images, and irises. In some implementations, in order to make owner identification more user-unobtrusive and intelligent, biometric information that can be collected without user operation can be selected, such as facial images and irises. In the following embodiments of this application, facial images are used as an example for illustration.

[0064] It is understandable that some electronic devices without image acquisition capabilities, such as smartwatches, can use other biometric information for owner identification, which is outside the scope of this application.

[0065] It is understandable that to achieve terminal collaboration based on device owner identification, it is necessary to synchronize the device owner's facial image across multiple electronic devices. Given the unique nature of mobile phone owners, in the following embodiments of this application, the user's facial image stored in the mobile phone is used as an example of the device owner's facial image to be synchronized.

[0066] In this case, combined Figure 1 As shown, to achieve terminal collaboration based on device owner recognition, the device owner's facial image in mobile phone 1 needs to be synchronized to other electronic devices.

[0067] The following section will provide a detailed explanation of the call method based on facial images, using the terminal collaboration function based on device owner identification as an example.

[0068] The call method provided in this application is applied to an electronic device. In some embodiments, the electronic device may be a mobile phone (e.g., Figure 12 (As shown), tablets, desktops, laptops, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, personal digital assistants (PDAs), wearable electronic devices, smartwatches, and other devices.

[0069] by Figure 1 Taking mobile phone 1 and laptop computer 2 on the same trust ring as an example, Figure 6 The diagram shows the framework for implementing the super call function based on device owner identification.

[0070] like Figure 6 As shown, mobile phone 1 includes an application layer, an application framework layer, a kernel layer, and a hardware layer. The application layer is used to run applications. For example... Figure 6 As shown, examples of applications related to this application include Incall UI, ringtone, vibration, interface, settings, and cloud account.

[0071] Incall UI provides the interface during an incoming call. Ringing and vibration are used to ring the phone according to a pre-configured pattern upon receiving a call or notification. Vibration is used to vibrate according to a pre-configured pattern upon receiving a call or notification. The interface provides various displays for the electronic device. Settings provide settings for various functions; it is understood that settings may be combined with the interface to provide a settings interface. An example of a settings interface is shown below. Figure 2 as well as Figure 5 As shown. Cloud accounts are used to provide functions such as account login, updates, deletion, and synchronization for cloud servers. It can be understood that cloud accounts can be combined with the interface to provide... Figure 1 The account login interface is shown in C, which is an example of the interface in the example.

[0072] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The service layer includes predefined functions. For example... Figure 6 As shown, the modules operating at the service layer related to this application include terminal collaboration service, device profile service, biometric information sharing service, facial recognition service, and sensing service. The service layer of the mobile phone 1 with cellular communication capabilities also includes the TelecomAOSP calling framework and the Telephony cellular calling service.

[0073] Terminal collaboration services include Super Connection Service, Super Call Service, Super Notification Service, and Super Keyboard and Mouse Service. Super Connection Service provides Super Connection functionality; Super Call Service provides Super Call functionality; Super Notification Service provides Super Notification functionality; and Super Keyboard and Mouse Service provides Super Keyboard and Mouse functionality. For the effects and settings of each super function, please refer to the documentation for... Figure 2 The relevant explanations will not be repeated here.

[0074] The kernel layer includes drivers for the various hardware modules in the hardware layer.

[0075] The hardware layer includes a modem module for implementing cellular communication and a Link module for implementing near-field communication. Figure 6 The Link module, which includes WLAN and Bluetooth, is used as an example.

[0076] The laptop computer 2 includes a PC manager, a camera, and a Link module. The PC manager runs terminal collaboration services, device profile services, biometric information sharing services, facial recognition services, and sensing services.

[0077] In this embodiment, taking the Super Call function as an example, since mobile phone 1 has cellular calling function, it is the source device for transferring calls to other devices or the execution device for responding to the operation of other devices to call the other end of the cellular communication device. Therefore, the perception service of mobile phone 1 is used to request the facial comparison result from laptop computer 2. The perception service of laptop computer 2 is used to use the facial image obtained from mobile phone 1 as a reference image. By comparing the facial image captured by the camera of laptop computer 2 with the reference image, the facial recognition result is obtained and the recognition result is transmitted to mobile phone 1.

[0078] The facial recognition service on both laptop 2 and mobile phone 1 is used to provide facial recognition functionality. Understandably, the facial recognition service may not be included in the PC manager of laptop 2, but can be implemented by the PC manager calling the facial recognition application on laptop 2.

[0079] The device profile service is used to store and synchronize some static information about the device to the cloud, including but not limited to: the on / off status of functions, image version information, and account status.

[0080] The biometric information sharing service is used to transmit facial images from mobile phone 1 to laptop computer 2 based on static information in the device profile service. To enhance the security of facial image transmission, the general key management service of mobile phone 1 and laptop computer 2 negotiate the transmission key for the facial image. The general key management service of mobile phone 1 is also used to encrypt the facial image to be transmitted using the negotiated key, and the general key management service of laptop computer 2 is also used to decrypt the received facial image ciphertext.

[0081] The Telecom AOSP calling framework and Telephony cellular calling service of mobile phone 1 can be used to manage audio and video calls of mobile phone 1. This includes SIM-based calls (e.g., using the Telephony framework) and VoIP calls provided by the ConnectionService API implementer.

[0082] Taking answering an incoming call as an example, after the user answers the call on laptop 2, laptop 2 notifies mobile phone 1 that the call has been answered. Alternatively, after the user answers the call on mobile phone 1, mobile phone 1 calls the Telecom AOSP call framework and Telephony cellular call service, activates the underlying call module of mobile phone 1, decodes the call data, obtains the audio information, and then sends or plays the audio information locally to laptop 2.

[0083] The application scenarios of the call method provided in this application include, but are not limited to, establishing a connection between electronic devices based on near-field communication. It is understood that, in scenarios where the terminal collaboration function based on device owner identification is enabled, nearby electronic devices can automatically establish a connection based on near-field communication.

[0084] In embodiments of this application, near-field communication includes, but is not limited to: Wireless Local Area Networks (WLAN), Bluetooth, Bluetooth Low Energy (BLE), Wireless Fidelity (WIFI), and Near Field Communication (NFC). Figure 12 As shown, the corresponding module may be included in the wireless communication module 160.

[0085] based on Figure 6 The call flow implemented by the framework shown is as follows: Figure 7 As shown, for ease of description, the module in mobile phone 1 will be referred to as "first..." and the module in laptop computer 2 will be referred to as "second...".

[0086] Figure 7 The process includes the following steps:

[0087] S101. In response to an incoming call notification, the first super call service transmits a query message about the device used by the user to the first perception service.

[0088] In some implementations, Figure 4 The facial image stored in mobile phone 1, one of the electronic devices shown, used for identity authentication, is used as the owner's facial image. It is understood that facial images used for identity authentication in other electronic devices besides mobile phones can also be used as the owner's facial image.

[0089] The device used by the owner can be understood as the device that the owner is currently using.

[0090] S102, the first sensing service responds to the query message from the device owner and transmits an authentication message to the first Link module.

[0091] S103, The first Link module transmits the authentication message to the second Link module.

[0092] S104, The second Link module transmits the authentication message to the second sensing service.

[0093] It is understood that in this embodiment, the names of messages such as "authentication message" and the names of instructions are merely examples and not intended to be limiting.

[0094] S105, The second sensing service transmits facial recognition messages to the second facial recognition service.

[0095] S106. The second facial recognition service responds to the facial recognition message by comparing the facial image of the host obtained from mobile phone 1 with the locally collected facial image to obtain the authentication result.

[0096] In some implementations, the comparison between two images is achieved by comparing the features extracted from the two images.

[0097] It is understood that the authentication result indicates whether the images are the same or not, but the specific content and format of the authentication result are not limited. The authentication result includes the comparison results obtained from the comparison images.

[0098] S107. The second facial recognition service transmits the authentication result to the second perception service.

[0099] S108, The second sensing service transmits the authentication result to the second Link module.

[0100] S109. The second Link module transmits the authentication result to the first Link module.

[0101] S110, the first Link module transmits the authentication result to the first perception service.

[0102] Combination Figure 4 As shown, other electronic devices such as tablet 2 are in the same trust ring as mobile phone 1 and laptop 2. It is understandable that mobile phone 1 obtains authentication results from other electronic devices in the same trust ring, except laptop 2, in a similar way to S101-S110, which will not be described in detail here.

[0103] After obtaining the authentication result of the electronic device in the same trust ring, mobile phone 1 executes S111.

[0104] S111. Based on the authentication result, the first perception service determines that laptop 2 is the device receiving the current transfer, referred to as the target device.

[0105] In some implementations, the first perception service searches for the authentication result indicating the same facial image from the authentication results of multiple electronic devices as the target authentication result, and takes the electronic device corresponding to the target authentication result as the target electronic device. It can be understood that each authentication result carries information about the corresponding electronic device.

[0106] S112, The first perception service transmits information about the target device to the first super call service.

[0107] S113. The first super call service responds to the information from the target device and transmits a transfer message to the first Link module.

[0108] In some implementations, the message flow includes call parameters, such as the phone number and corresponding contact information. The purpose of these call parameters is to alert the target device to incoming calls, such as displaying the caller's information.

[0109] S114. The first Link module transmits the transfer message to the second Link module.

[0110] S115, the second Link module transmits the transfer message to the second super call service.

[0111] S116, the second super call service responds to the flow message and transmits the incoming call reminder message to the incoming call reminder module of the laptop 2.

[0112] S117, the call reminder module of laptop 2 provides call reminders.

[0113] In some implementations, the call notification module of laptop 2 includes, but is not limited to, Figure 6 The Incall UI, ringing, and vibration are shown. It's understood that an incoming call alert message, including call parameters, can be transmitted to the Incall UI to instruct it to display the call alert interface, showing the caller's phone number and corresponding contact information. Incoming call alert messages can also be transmitted to the ringing and vibration modules. The ringing and vibration modules respond to these messages based on pre-configured settings. For example, if a ringing but not vibration is pre-configured, the ringing application will ring in response to the call alert message, while the vibration module will not.

[0114] In some implementations, mobile phone 1 responds to an incoming call by providing a pre-configured notification, such as displaying a call notification interface and vibrating. When mobile phone 1 provides the call notification, to minimize disruption to the user, laptop 2 only displays the call notification interface and stops ringing and vibrating. That is, the second super call service only transmits the call notification message, including the call parameters, to the Incall UI, and no longer transmits the call notification message for ringing and vibration. Because laptop 2 has captured the user's facial image, it indicates that the user is using laptop 2; therefore, the call notification interface can effectively notify the user of incoming calls.

[0115] There are no restrictions on the style, display location, or display content of the incoming call notification interface on the laptop 2.

[0116] Combination Figure 4 As shown, other electronic devices on the trust ring, besides mobile phone 1 and laptop 2, do not alert for incoming calls because they do not recognize the owner's face.

[0117] It is understood that the user (owner) can answer a call using either mobile phone 1 or laptop 2. In this embodiment, the process triggered by answering a call using mobile phone 1 will not be described in detail. The process triggered by answering a call using laptop 2 is as follows.

[0118] S118, the Incall UI of the laptop 2 responds to the operation of answering an incoming call and transmits the answer message to the second Link module.

[0119] S119, The second Link module transmits the answer message to the first Link module.

[0120] S120, the first Link module transmits the answer message to the first super call service.

[0121] S121, The first super call service receives and processes call data.

[0122] It is understood that call data includes, but is not limited to, call audio data or call audio and video data.

[0123] In some implementations, call data is collected by the audio module of the laptop 2 and transmitted to the first super call service via the Link module, etc. The first super call service then sends the received call data to the other end of the call via the modem, etc.

[0124] In other implementations, mobile phone 1 receives call data from the other end via a modem or similar device, and transmits it to laptop computer 2 via a Link module or similar device, whereby laptop computer 2 plays the call data.

[0125] In this embodiment, after receiving downlink call data through the Modem module, mobile phone 1 transmits the downlink call data to the second Link module of laptop computer 2 through the first Link module, that is, it transmits downlink call data to laptop computer 2 using wireless communication. After laptop computer 2 collects uplink call data, it transmits uplink call data to the first Link module of mobile phone 1 through the second Link module. Mobile phone 1 transmits uplink call data to wireless devices such as base stations in the cellular network through the Modem module.

[0126] S122, The first super call service transmits status change messages to the second link module through the first link module.

[0127] Status change messages indicate changes in the status of an incoming call, such as a change from a call alert status to a call being answered. Understandably, status change messages include status parameters, such as call duration, for use in the interface of laptop 2 to display the current status.

[0128] S123, The second Link module transmits a status change message to the second super call service.

[0129] S124, the second super call service transmits a refresh command to the incoming call reminder module of the laptop 2.

[0130] The refresh command carries a status change message.

[0131] S125, Incall UI switches from the incoming call notification interface to the call interface.

[0132] Understandably, the call interface displays the phone number being called and parameters such as call duration.

[0133] In addition to switching interfaces, the system also needs to stop the ringing or vibration of the laptop 2.

[0134] from Figure 7 As shown in the process, the super call function based on owner identification uses facial recognition to confirm that the electronic device used by the owner is the target device, and only provides call notifications on the target device. This not only enables call notifications on devices within the same trust ring as the phone, but also reduces interference with the user and lowers the phone's power consumption.

[0135] Understandably, for other terminal collaboration functions such as Super Notification, and... Figure 7 Similarly, it can also be achieved based on owner identification.

[0136] Understandably, before comparing the facial image obtained from mobile phone 1 with the locally acquired facial image to obtain the authentication result, laptop 2 needs to first obtain the owner's facial image from mobile phone 1. The call method provided in this application embodiment also includes a process capable of synchronizing the owner's facial image from mobile phone 1 to other electronic devices.

[0137] Figure 8 The process for sharing the user's facial image between a mobile phone 1 and a laptop computer 2, as provided in this application embodiment, includes the following steps:

[0138] S201a, The first biometric information sharing service transmits the version information of the host's facial image and the switch status information to the first device profile service.

[0139] The switch status information refers to the status information of the master identification function, indicating whether the master identification function is on or off. This can be understood as combining... Figure 2 As shown, with the owner identification function enabled, the terminal collaboration function is always enabled. The switch status information can also refer to the on / off status of both the owner identification function and the terminal collaboration function.

[0140] Understandably, after a change in the user's facial image (such as when a user registers or deletes a facial image), relevant modules in mobile phone 1, such as the first facial recognition module, can transmit information about the newly added or deleted user's facial image to the first biometric information sharing service. The first biometric information sharing service monitors changes in the on / off state of mobile phone 1, such as changes in the value of a field identifying the on / off state.

[0141] In some implementations, the first biometric information sharing service periodically transmits the latest version information of the host's facial image and the on / off status information to the first device profile service.

[0142] In some other implementations, the first biometric information sharing service periodically obtains the host's facial image version information (referred to as historical version information) and switch status information (referred to as historical switch status information) stored in the device profile service from the device profile service, and compares whether the latest host facial image version information is the same as the historical version information. If they are different, the latest host facial image version information is transmitted to the device profile service, and the latest switch status information is compared with the historical switch status information. If they are different, the latest switch status information is transmitted to the device profile service.

[0143] S201b, The second biometric information sharing service transmits the version information of the host's facial image and the switch status information to the second device profile service.

[0144] For details on the implementation, please refer to the specific implementation of S201a.

[0145] S202. The first device profile service and the second device profile service perform cloud synchronization of profile information for devices under the same account.

[0146] Devices with the same account refer to electronic devices that are logged into the same account.

[0147] Profile information can be understood as information managed by the device profile service, including the version information of the owner's facial image and the on / off status information.

[0148] Cloud synchronization can be understood as the synchronization of local and cloud data between the device profile service and the cloud. After cloud synchronization, the first device profile service obtains the version information and on / off status information of the owner's facial image managed by the second device profile service from the cloud, and the second device profile service obtains the version information and on / off status information of the owner's facial image managed by the first device profile service from the cloud.

[0149] It is understandable that the execution order of S201a, S201b and S202 is not limited, and they can all be executed multiple times, for example, multiple times with the same or different cycles.

[0150] S203a, The first bio-information sharing service transmits a monitoring command for near-field communication device connection to the first Link module.

[0151] S203b, the second bio-information sharing service transmits a monitoring command for near-field communication device connection to the second Link module.

[0152] It is understandable that the execution order of S203a and S203b is not limited, nor is the execution order of S203a and S203b with S201a-S202.

[0153] S204. The first Link module and the second Link module establish a connection based on near-field communication.

[0154] S205, The second Link module transmits information about the mobile phone 1 that has established a near-field communication connection with the local machine to the second bio-information sharing service.

[0155] That is, the information from mobile phone 1 is the listening result of the second Link module.

[0156] It is understandable that the first Link module will also transmit information about the laptop 2 that has established a near-field communication connection with the local machine to the first biometric information sharing service. Because this embodiment uses the facial image used for authentication in the mobile phone 1 as the owner's facial image as an example, therefore... Figure 8 Taking the example of a laptop computer 2 actively acquiring the user's facial image from a mobile phone 1.

[0157] It is understandable that the execution order of S204 and S201a-S203b is not limited.

[0158] S206, The second biometric information sharing service transmits a query message to the second device profile service, which contains information about the owner identification switch status and facial image version of mobile phone 1.

[0159] S207. The second device profile service transmits the owner identification switch status and facial image version information of mobile phone 1 to the second biometric information sharing service.

[0160] Understandably, if the second device profile service cannot find the owner recognition switch status and facial image version information of mobile phone 1, it can initiate cloud synchronization with the cloud server to obtain the owner recognition switch status and facial image version information of mobile phone 1.

[0161] In some implementations, if the second device profile service still cannot find the owner recognition switch status and facial image version information of mobile phone 1 after initiating cloud synchronization, it means that mobile phone 1 is very likely not logged in to an account, and the subsequent steps will not be executed.

[0162] S2081. The second biometric information sharing service confirms that the first condition is met and adds the information of mobile phone 1 to the list to be synchronized.

[0163] In some implementations, the first condition includes: the owner identification switch of mobile phone 1 changes from off to on, and the facial image version information of mobile phone 1 is different from the owner facial image version information in the local (i.e., in laptop computer 2).

[0164] In some implementations, the second device profile service sends the host identification switch status of mobile phone 1 to the second biometric information sharing service as a static state of "on" or "off". The second biometric information sharing service compares the most recently acquired host identification switch status of mobile phone 1 with the most recently acquired host identification switch status of mobile phone 1 to obtain the dynamic status. In this case, it indicates that the laptop 2 already stored the information of mobile phone 1 before the laptop 2 last acquired the host identification status.

[0165] In some implementations, the on / off status information of mobile phone 1 obtained by the second device profile service from the cloud is considered a dynamic status. In this case, the laptop 2 may not yet contain information about mobile phone 1, so the first condition can also include the presence of mobile phone 1 information on the laptop 2.

[0166] It is understandable that encrypted transmission can be used to increase the security of subsequent facial image transmission. Therefore, mobile phone 1 needs to negotiate the key with laptop 2. Thus, the first condition also includes: laptop 2 has completed key negotiation with mobile phone 1.

[0167] It is understandable that the difference between the owner's facial image version information on mobile phone 1 and the local owner's facial image version information could be due to two scenarios: 1. The owner's facial image and version information are stored locally (i.e., can be retrieved), but the version information retrieved locally differs from the owner's facial image version information on mobile phone 1. This means that laptop 2 previously synchronized facial images and version information used for owner recognition from the mobile phone, but it is not the latest version. 2. The owner's facial image and version information are not found locally.

[0168] It is understandable that the owner's facial image and related information stored locally on laptop 2 are for owner identification purposes. This facial image may be the same as or different from the facial image used by laptop 2 itself for authentication such as facial unlocking. Even if they are the same, they need to be distinguished using an identifier. It is also understandable that, for enhanced security, the facial image used for owner identification is stored in a Trusted Execution Environment (TEE) on phone 1, and after being synchronized from phone 1 to laptop 2, it is also stored in laptop 2's TEE. On laptop 2, the facial image used for owner identification and other facial images can be stored in the same storage space, such as within the TEE, or in different storage spaces.

[0169] S2082. The second biometric information sharing service confirms that the second condition is met and adds the information of mobile phone 1 to the list to be deleted.

[0170] In some implementations, the second condition includes: the owner identification switch of mobile phone 1 changes from on to off.

[0171] It is understandable that the switch state changes from "on" to "off," so it is very likely that the laptop 2 had already synchronized the facial image from the phone 1 when the owner recognition switch was "on." Therefore, after it changes to "off," it needs to be deleted. It is evident that compared to the static state "off," the dynamic state "from on to off" provides a more precise determination condition for deleting stored information. Of course, the static state information "on" or "off" can also be used instead of the dynamic state information; this embodiment does not impose any limitations. Furthermore, it is understood that the switch state information is used to indicate whether the owner recognition function is on or off; as long as this function is achieved, it is acceptable. This embodiment does not limit the specific content of the switch state information.

[0172] The second condition is determined in a similar way to the first condition; either the dynamic state can be obtained by the second biometric information sharing service based on two static states, or the dynamic state can be obtained directly. The second condition may also include the presence of information about mobile phone 1 in laptop 2.

[0173] S209. The second biometric information sharing service responds that the list to be synchronized is not empty, and transmits a message to the first biometric information sharing service to obtain the owner's facial image through the laptop 2 and the first Link module.

[0174] S210, the first biometric information sharing service transmits the host's facial image to the second biometric information sharing service via mobile phone 1 and the second Link module.

[0175] In some implementations, mobile phone 1 stores multiple facial images, each of which is identified according to its purpose. The first biometric information sharing service queries the host's facial images based on these identifiers.

[0176] S211. The second biometric information sharing service stores facial images and version information of devices in the list to be synchronized.

[0177] In some implementations, a list or similar format is used to represent the facial images and version information stored on the device.

[0178] It is understandable that, in addition to phone 1, there might also be phone 6 (not shown in the diagram) on the same trust ring. In this case, the laptop needs to obtain the facial image of the owner of phone 1 and the corresponding version information, as well as the facial image of the owner of phone 6 and the corresponding version information, in order to... Figure 9 For example, laptop 2 synchronizes the owner's facial image and version information of mobile phones 1 and 6 respectively. Given that each phone's owner's facial image contains both the owner's face and a backup face, laptop 2 needs to synchronize both the owner's face and the backup face. It's understandable that the owner's face and the backup face could be the same person's face with different accessories, such as different hairstyles. Figure 9The information includes the storage device, face, and face version information in the laptop 2.

[0179] S212, The second biometric information sharing service responds to the fact that the list to be deleted is not empty, and deletes the owner's facial image and related information of the device in the list to be deleted.

[0180] In some implementations, the relevant information includes, but is not limited to: the device key in the list to be deleted and the version information of the owner's facial image.

[0181] return Figure 9 For example, assuming that the information of mobile phone 1 exists in the list to be deleted, then laptop 2 will delete the primary and backup faces, as well as the corresponding version information, key, and account of the source device ID A000011 from the list.

[0182] As can be seen, S206-S212 is the process by which the laptop 2 updates the local owner's facial image and corresponding information in response to establishing a near-field communication connection with the mobile phone 1.

[0183] Because device access to the trust loop requires both establishing a near-field communication connection and logging into the same account, even if a near-field communication connection is established between mobile phone 1 and laptop 2, the terminal collaboration function of mobile phone 1 will not work if mobile phone 1 and laptop 2 are not logged into the same account. In this case, it is necessary to avoid storing the facial image of the owner of mobile phone 1 on laptop 2 to reduce the possibility of laptop 2 performing meaningless facial image comparisons later. For this purpose, S213-S216 are executed.

[0184] S213, The second biometric information sharing service transmits a message to the second device profile service to query the mobile phone that is logged into the same account as the laptop 2.

[0185] S214. The second device profile service transmits information about the mobile phone that is logged into the same account as the laptop 2 to the second biometric information sharing service.

[0186] S215. The second biometric information sharing service will add information about mobile phones that exist locally but are not found in the information of mobile phones logged in with the same account to the redundancy list.

[0187] return Figure 9 For example, if the identifier B000012 of mobile phone 2 does not exist in the identifiers of mobile phones that log in to the same account as laptop 2, then B000012 is added to the redundancy list.

[0188] Understandably, for a mobile phone logged into the same account as the laptop, laptop 2 will not execute S615. Electronic devices whose information is stored in a redundancy list can be called redundant electronic devices.

[0189] S216, Laptop 2 responds to the redundancy list not being empty by deleting the host face image and related information of the mobile phone from the redundancy list.

[0190] At this point, in response to the establishment of a near-field communication connection with mobile phone 1 and the query result of whether mobile phone 1 is logged into an account, laptop 2 updates the local storage of the host's facial image and related information.

[0191] It is understandable that the various electronic devices located on the same trust ring may change, for example, a new electronic device may be added to the trust ring, or an electronic device currently on the trust ring may be taken offline (i.e., no longer on the trust ring). Therefore, the laptop 2 updates the local owner's facial image and related information through the following steps S217-S222.

[0192] S217, The second biometric information sharing service transmits messages to the second device profile service regarding the owner identification switch status and changes in the owner's facial image version of the subscribed mobile phone 1.

[0193] S218. In response to a change in the owner identification switch status and / or the owner's facial image version of mobile phone 1, the second device profile service transmits the changed owner identification switch status and / or owner's facial image version information to the second biometric information sharing service.

[0194] S219. The second biometric information sharing service updates at least one of the lists to be synchronized and to be deleted based on the changed owner identification switch status and / or facial image version information, and updates the local device information based on the updated lists to be synchronized and to be deleted.

[0195] For details on how to update at least one of the lists to be synchronized and to be deleted, please refer to S2081-S2082. For details on how to update local device information, please refer to S209-S212. These will not be elaborated here.

[0196] S220, the second biometric information sharing service transmits a message to the second device profile service that the subscribed mobile phone has logged out of the same account.

[0197] Understandably, the subscription is for messages from accounts logged out of the laptop 2 that were previously recorded on the laptop 2.

[0198] S221. In response to a mobile phone logging out of the same account, the second device profile service transmits information about the mobile phone that logged out of the same account to the second biometric information sharing service.

[0199] S222, The second biometric information sharing service updates the redundancy list based on the information of mobile phones that have logged out of the same account, and updates the local device information based on the updated redundancy list.

[0200] For details on how to update the redundancy list, please refer to S215-S216. For details on how to update local device information, please refer to S216. These details will not be repeated here.

[0201] Figure 8 The process shown responds to the establishment of near-field communication connections between devices and the login and logout status of devices, enabling timely and flexible synchronization of the owner's facial images.

[0202] based on Figure 8 The illustrated process, as can be understood, requires the following conditions for synchronization of the owner's facial image: 1. The terminal collaboration switch and owner identification switch are turned on on both mobile phone 1 and laptop 2. 2. Mobile phone 1 and laptop 2 are logged into the same account and are in near-field networking, i.e., within the same trust ring. 3. The versions of the owner's facial image stored on mobile phone 1 and laptop 2 are different. 4. Mobile phone 1 and laptop 2 have negotiated a key (optional) for transmitting the owner's facial image.

[0203] The conditions for deleting the owner's facial image include: 1. The mobile phone or laptop has either the terminal collaboration switch or the owner recognition switch turned off. It is understandable that, based on... Figure 2 As shown in the configuration, in this embodiment, if the terminal collaboration switch is turned off, then the owner identification switch is also turned off. 2. Mobile phone 1 logs out of the account logged in on laptop 2.

[0204] In addition, if Laptop 2 logs out of the account, it is considered to have exited the trust loop, and Laptop 2 must delete the owner's facial image to ensure its security. Furthermore, if Laptop 2's facial recognition function is disabled, it means Laptop 2 cannot provide facial image authentication results; therefore, to ensure the security of the owner's facial image, the acquired facial image can also be deleted. Additionally, if Laptop 2 disables its terminal collaboration function, to ensure the security of the owner's facial image, the acquired facial image can also be deleted.

[0205] Combination Figure 7 as well as Figure 8It is understandable that the synchronization of the owner's facial image can occur before an incoming call, that is, after the biometric information sharing service is started (e.g., automatically started upon power-on), the synchronization of the owner's facial image will be performed as long as the conditions (e.g., S205 and S207) are met. Alternatively, the synchronization of the owner's facial image can occur after an incoming call, such as before S106 when the laptop 2 has not yet acquired the owner's facial image, at which point S206 and subsequent steps can be performed to synchronize the owner's facial image from the mobile phone 1.

[0206] Understandable Figure 8 The method shown, which enables devices within the same trust ring to obtain the owner's facial image version information and on / off status information of the peer through cloud synchronization based on the same account, is merely an example. Alternatively, interaction can be achieved through the Link module. For instance, after S205, the second biometric information sharing service of laptop 2 obtains the owner's facial image version information and on / off status information of mobile phone 1 from the first biometric information sharing module through both the second Link module and the first Link module.

[0207] In some implementations, to improve the security of transmitting the owner's facial image, a key is used to encrypt the owner's facial image. Therefore, electronic devices transmitting the owner's facial image need to negotiate the key first.

[0208] Figure 10 The process for key negotiation between mobile phone 1 and laptop computer 2 includes the following steps:

[0209] S301. The first bio-information sharing service transmits a monitoring command for near-field communication device connection to the first Link module. S302. The first Link module and the second Link module establish a near-field communication-based connection.

[0210] It is understandable that the execution order of S301 and S302 is not a limitation.

[0211] S303, The first Link module transmits information about the device that has established near-field communication with the local machine to the first bio-information sharing service.

[0212] In this embodiment, the device that establishes near-field communication with the local machine is also exemplified by laptop computer 2.

[0213] S304. The first biometric information sharing service determines whether there is a key negotiation record with laptop computer 2.

[0214] Key negotiation records can be understood as data that records information related to key negotiation, such as key negotiation logs.

[0215] It is understandable that S302 can establish a near-field communication (NFC) connection between mobile phone 1 and laptop 2 for the first time. In this case, mobile phone 1 and laptop 2 have not performed key negotiation. S302 may also establish a NFC connection between mobile phone 1 and laptop 2 again after establishing the NFC connection for the first time. In this case, mobile phone 1 and laptop 2 may have already performed key negotiation.

[0216] In some implementations, to improve security, an expiration date can be set for the negotiated key. Once this date is exceeded, the key is considered expired, and the key negotiation record is deleted.

[0217] If a key negotiation record exists, it means that mobile phone 1 and laptop 2 have negotiated a key, and the key can be used to encrypt the owner's facial image to be transmitted. Therefore, the following process does not need to be performed.

[0218] If there is no key negotiation record, it means that mobile phone 1 has not negotiated the key with laptop 2 and does not specify the conditions for transmitting the owner's facial image. Therefore, the key negotiation process is executed, such as S305-S325.

[0219] S305, The first biometric information sharing service transmits a challenge number request to the first facial recognition service.

[0220] S306. The first facial recognition service transmits a key negotiation request to the first general key management service.

[0221] S307, The first general key management service transmits the challenge number to the first facial recognition service.

[0222] Understandably, the number of challenges is a random value.

[0223] S308, The first bio-information sharing service transmits a key negotiation request carrying a challenge number to the first Link module.

[0224] S309. The first Link module transmits a key negotiation request carrying a challenge number to the second biometric information sharing service via the second Link module.

[0225] S310, the second biometric information sharing service transmits a key negotiation request carrying a challenge number to the second general key management service via the second facial recognition service.

[0226] S311, The second general key management service generates business key certificate 1 (public key 1), business key 1 (private key 1), certificate chain 1 and signature 1.

[0227] In some implementations, certificate chain 1 is obtained by concatenating the device certificate of laptop 2 and business key certificate 1. Signature 1 is obtained by signing string 1 using business key 1, and string 1 consists of a challenge number and certificate chain 1.

[0228] S312, the second general key management service transmits an Attestation request to the second biometric information sharing service via the second facial recognition service.

[0229] The Attestation request carries certificate chain 1 and signature 1.

[0230] S313, the second bio-information sharing service transmits an Attestation request to the first bio-information sharing service via the second Link module and the first Link module.

[0231] S314. The first biometric information sharing service transmits an Attestation request to the first general key management service via the first facial recognition service.

[0232] S315, The first general key management service verifies certificate chain 1 and verifies signature 1.

[0233] It is understandable that electronic devices with terminal collaboration capabilities and located in the same trust ring have the same device root certificate. In some implementations, the device certificate of laptop 2 in certificate chain 1 is verified using the device certificate of mobile phone 1. As long as the root certificates of the two are the same, the certificate chain verification passes.

[0234] The signature 1 generated by signing with business key 1 (private key 1) is verified using business key 1 certificate 1 (public key 1) in certificate chain 1. The challenge number in signature 1 is compared with the locally generated challenge number. If they are the same, the signature verification is successful.

[0235] S316. The first general key management service generates business key certificate 2 (public key 2), business key 2 (private key 2), certificate chain 2 and signature 2, and generates a negotiation key based on the business key certificate (business key certificate 1) of laptop computer 2 and the business key certificate (business key certificate 2) of mobile phone 1.

[0236] In some implementations, certificate chain 2 is obtained by concatenating the device certificate of mobile phone 1 and business key certificate 2. Signature 2 is obtained by signing string 2 using business key 2, and string 2 consists of challenge number and certificate chain 2.

[0237] S317. The first general key management service transmits an Attestation request to the first biometric information sharing service via the first facial recognition service.

[0238] The Attestation request carries certificate chain 2 and signature 2.

[0239] S318, the first biometric information sharing service transmits an Attestation request carrying certificate chain 2 and signature 2 to the second biometric information sharing service via the first Link module and the second Link module.

[0240] S319, The second biometric information sharing service transmits an Attestation request carrying certificate chain 2 and signature 2 to the second general key management service through the second facial recognition service.

[0241] S320, the second general key management service verifies certificate chain 2 and verifies signature 2.

[0242] It is understandable that electronic devices with terminal collaboration capabilities and located in the same trust ring have the same device root certificate. In some implementations, the device certificate of mobile phone 1 in certificate chain 1 is verified using the device certificate of laptop 2. As long as the root certificates of the two are the same, the certificate chain verification passes.

[0243] The signature 2 generated by signing with business key 2 (private key 2) is verified using business key 2 certificate 2 (public key 2) in certificate chain 2. The challenge number in signature 2 is compared with the challenge number that has been received and stored (carried in the key negotiation request). If they are the same, the signature verification is successful.

[0244] S321. The second general key management service generates a negotiated key based on the business key certificates of the peer (mobile phone 1) and the local (laptop 2).

[0245] In some implementations, after mobile phone 1 and laptop 2 generate a negotiation key, the negotiation key can be stored along with the information of the peer devices participating in the key negotiation. It is understood that any electronic device can negotiate different keys with different electronic devices. Figure 11 For example, mobile phone 1 stores information about laptop 2 (PC1) and the negotiation key Key_2, and tablet 3 stores information about tablet 3 (Pad3) and the negotiation key Key_1. Laptop 2 stores information about mobile phone 1 (Mobile Phone 1) and the negotiation key Key_2.

[0246] At this point, mobile phone 1 and laptop computer 2 have completed key negotiation.

[0247] Figure 10 The key negotiation process shown enables devices to negotiate keys when establishing near-field communication, laying the foundation for secure transmission of the host's facial image.

[0248] Understandable Figure 10Taking the example of mobile phone 1 actively triggering the key negotiation process (S301-S309), in addition, laptop computer 2 can also actively trigger the key negotiation process (similar to S301-S309). Furthermore, it can be combined with... Figure 8 As shown, during the execution of S2082 by the laptop, it is confirmed that key negotiation has not yet been carried out with mobile phone 1. For example, in some implementations, it is impossible to decrypt the owner's facial image synchronized from mobile phone 1. In this case, the laptop 2 actively triggers the password negotiation process (similar to S305-S309).

[0249] The conditions for deleting the negotiation key on mobile phone 1 and laptop computer 2 include at least one of the following: mobile phone 1 logs out of its account, and laptop computer 2 logs out of its account. Since the negotiation key is used to transmit the user's facial image, the conditions for deleting the negotiation key may also include: mobile phone 1 and / or laptop computer 2 deleting the user's facial image.

[0250] Optionally, similar to the deletion conditions for the owner's facial image, the conditions for deleting the negotiated key may also include: at least one of the following: the mobile phone 1 and / or laptop 2 disables the terminal collaboration function and the owner identification function.

[0251] Understandably, after the biometric information sharing service on mobile phone 1 or laptop 2 is started, it can first execute in response to the initial establishment of a near-field communication connection. Figure 10 The key negotiation process shown will then be executed. Figure 7 The steps related to facial image synchronization in the illustrated biometric information sharing process (such as S206 and subsequent steps). Alternatively, during the execution Figure 7 In the facial image synchronization process within the illustrated biometric information sharing workflow, if the negotiated key expires, laptop 2 detects the need to re-negotiate the key and then executes... Figure 10 The S305 process and subsequent steps are initiated by the laptop 2.

[0252] Figure 12The illustration shows an example of the hardware structure of an electronic device disclosed in this application. Taking a mobile phone as an example, the mobile phone may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

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

[0254] 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, video codec, digital signal processor (DSP), audio signal processor (ADSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

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

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

[0257] The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface to enable the function of answering phone calls through a Bluetooth headset.

[0258] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via the PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering phone calls through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0259] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface to enable music playback through Bluetooth headphones.

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

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

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

[0263] The mobile communication module 150 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G in electronic devices. 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 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.

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

[0265] This application also discloses a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform the call method described in the above embodiments.

[0266] Embodiments of this application also disclose a computer program product comprising: computer program code, which, when executed on an electronic device, causes the electronic device to perform the call method disclosed in the embodiments of this application.

Claims

1. A method for making a call, characterized in that, Applied to electronic devices, where both a first electronic device and a second electronic device are logged into a first account, and the first electronic device and the second electronic device establish a connection based on near-field communication, the method includes: The first electronic device collects biological information in response to a message transmitted by the second electronic device after a call is received; The first electronic device compares the collected biometric information with the owner biometric information synchronized from the second electronic device to obtain a comparison result. The process of synchronizing the owner biometric information from the second electronic device includes: in response to establishing a near-field communication-based connection with the second electronic device, obtaining first version information and the owner identification switch status of the second electronic device. The first version information includes the version information of the owner biometric information of the second electronic device. After confirming that a first condition is met, the owner biometric information is synchronized from the second electronic device. The first condition includes the owner identification switch status indicating that the owner identification function is enabled, and the first version information is different from the second version information. The second version information includes the version information of the owner biometric information in the first electronic device. The first electronic device transmits the comparison result to the second electronic device; The first electronic device responds to incoming call data to alert the user to an incoming call. The incoming call data is transmitted from the second electronic device to the first electronic device in response to the comparison result indicating that the comparison has passed.

2. The method according to claim 1, characterized in that, Also includes: The first electronic device deletes the owner's biometric information from the redundant electronic device, which includes devices that have logged out of the first account and whose owner's biometric information is stored in the first electronic device.

3. The method according to any one of claims 1-2, characterized in that, The first electronic device synchronizes host biometric information from the second electronic device, including: The first electronic device receives encrypted biometric information of the device owner transmitted by the second electronic device, and the encrypted biometric information of the device owner is encrypted using a key negotiated between the first electronic device and the second electronic device; The first electronic device decrypts the encrypted biometric information of the device owner, obtains and stores the biometric information of the device owner.

4. The method according to any one of claims 1-2, characterized in that, The first condition also includes: The first electronic device has completed key negotiation with the second electronic device.

5. The method according to claim 4, characterized in that, The process of the first electronic device and the second electronic device negotiating the key includes: In response to a key negotiation triggering condition, the first electronic device and the second electronic device perform key negotiation, wherein the key negotiation triggering condition includes: the first electronic device and the second electronic device establishing a connection based on near-field communication.

6. The method according to claim 5, characterized in that, The key negotiation triggering conditions also include: The first electronic device or the second electronic device confirms that there is no key negotiation record with the other end; or, The first electronic device is unable to decrypt the owner's biometric information synchronized from the second electronic device.

7. The method according to claim 5, characterized in that, After the first electronic device and the second electronic device perform key negotiation, the process further includes: In response to a key deletion condition, the first electronic device deletes the negotiated key, wherein the key deletion condition includes: the first electronic device and / or the second electronic device logging out of the first account.

8. The method according to any one of claims 1-2, characterized in that, Also includes: Once the first electronic device confirms that the second condition is met, it deletes the owner's biometric information of the second electronic device from the first electronic device. The second condition includes at least one of the following: The status of the device owner identification switch indicates that the device owner identification function is off; the first electronic device logs out of the first account; the second electronic device logs out of the first account; the first electronic device disables the terminal collaboration function and / or biometric authentication function.

9. The method according to any one of claims 1-2, characterized in that, The synchronization of master bio-information from the second electronic device includes: Based on the near-field communication-based connection, the host's biological information is synchronized from the second electronic device; The acquisition of the first version information and the owner identification switch status of the second electronic device includes: The first version information and the owner identification switch status of the second electronic device are obtained from the second electronic device through cloud synchronization based on the first account.

10. The method according to any one of claims 1-2, characterized in that, After the first electronic device responds to the incoming call data and alerts the user to the incoming call, the system further includes: In response to an operation of answering an incoming call on the first electronic device, the first electronic device transmits an answer message to the second electronic device; In response to the status change message transmitted by the second electronic device, the first electronic device stops the incoming call reminder and displays the call interface, wherein the status change message is transmitted by the second electronic device in response to the answer message.

11. A method for making a call, characterized in that, Applied to electronic devices, where both a first electronic device and a second electronic device are logged into a first account, and the first electronic device and the second electronic device establish a connection based on near-field communication, the method includes: The second electronic device synchronizes the host biometric information to the first electronic device. This synchronization is triggered by the first electronic device after confirming that a first condition is met. The first condition includes the host identification switch status indicating that the host identification function is enabled, and the first version information being different from the second version information. The first version information includes the version information of the host biometric information of the second electronic device, and the second version information includes the version information of the host biometric information of the first electronic device. The first version information and the host identification switch status of the second electronic device are obtained by the first electronic device in response to establishing a near-field communication-based connection with the second electronic device. In response to an incoming call notification, the second electronic device transmits a message to the first electronic device. The message triggers the first electronic device to compare the collected biometric information with the owner's biometric information synchronized from the second electronic device, and obtain a comparison result. The second electronic device, in response to the comparison result transmitted by the first electronic device, determines that the first electronic device is the target device; The second electronic device transmits incoming call data to the target device, and the incoming call data is used by the target device to remind the target device of incoming calls.

12. The method according to claim 11, characterized in that, The second electronic device synchronizes the owner's biometric information with the first electronic device, including: The second electronic device encrypts the owner's biometric information to obtain ciphertext of the owner's biometric information; The second electronic device transmits the encrypted biometric information of the device owner to the first electronic device.

13. The method according to claim 12, characterized in that, Before encrypting the owner's biometric information, the following is also included: In response to a key negotiation triggering condition, the second electronic device performs key negotiation with the first electronic device. The key negotiation triggering condition includes: the first electronic device and the second electronic device establishing a connection based on near-field communication.

14. The method according to claim 13, characterized in that, The key negotiation triggering conditions also include: The first electronic device or the second electronic device confirms that there is no key negotiation record with the other end.

15. The method according to any one of claims 11-14, characterized in that, The step of synchronizing the owner's biological information to the first electronic device includes: Based on the near-field communication-based connection, the host's biological information is synchronized to the first electronic device; The method further includes: The second electronic device synchronizes the version information of the owner's biometric information and the owner identification switch status of the second electronic device to the first electronic device via cloud synchronization based on the first account.

16. The method according to any one of claims 11-14, characterized in that, After transmitting the incoming call data to the target, the method further includes: In response to the answer message, the second electronic device transmits a status change message to the first electronic device. The status change message is used to trigger the first electronic device to stop the incoming call reminder and display the call interface. The answer message is triggered by the first electronic device in response to the operation of answering an incoming call on the first electronic device.

17. The method according to any one of claims 11-14, characterized in that, Before the second electronic device transmits a message to the first electronic device in response to an incoming call notification, the method further includes: The second electronic device activates the owner identification function based on the owner's biometric information based on the user's operation on the interface.

18. An electronic device, characterized in that, include: One or more processors; One or more memory units; The memory stores one or more programs, which, when executed by the processor, cause the electronic device to perform the call method according to any one of claims 1-17.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to perform the call method according to any one of claims 1-17.

Images