Message notification method and electronic device

Abstract

A message notification method and an electronic device. In the method, a first electronic device can collect facial data of a user; then, on the basis of the facial data of the user, it is determined whether the first electronic device is being used only by the owner of the first electronic device, and when it is determined that the first electronic device is not being used only by the owner, a wearable device bound to the first electronic device can be instructed to issue a message notification. In this way, the intelligence of issuing message notifications across multiple devices can be improved, and the probability of missing new message notifications can be reduced.

Description

A message notification method and an electronic device

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410996879.3, filed on July 23, 2024, entitled "A Message Notification Method and Electronic Device", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of terminal technology, and in particular to a message notification method and an electronic device. Background Technology

[0004] With the development and progress of technology, the types of electronic devices have gradually become more diverse. In addition to mobile phones, wearable devices such as smartwatches, smart headphones, and smart glasses have also become increasingly popular.

[0005] When a user is using a mobile phone and at least one wearable device, it can be distracting if each message is notified on multiple devices. In some scenarios, if a message is only notified on one device, there may be issues with missing or untimely new message notifications.

[0006] Therefore, it is worth considering how to improve the intelligence of message reminders across multiple devices. Summary of the Invention

[0007] This application provides a message notification method and an electronic device to improve the intelligence of message notifications between multiple devices and reduce the probability of missing new message notifications.

[0008] In a first aspect, embodiments of this application provide a message notification method. This method can be applied to a first electronic device. In this method, facial data of a first user is collected; when a notification condition is determined to be met, a second electronic device is instructed to provide a message notification when a new message is present; wherein the notification condition includes at least one of the following: the first user's facial data fails to match the device owner's facial template data; multiple faces or multiple pairs of eyes gazing at the screen are identified from the first user's facial data; no face is identified from the first user's facial data; and the second electronic device is a wearable device bound to the first electronic device.

[0009] In this method, by collecting the user's facial data, when it is detected that someone other than the owner is using the first electronic device (such as a mobile phone), or when multiple people are looking at the mobile phone, or when no face is detected, the second electronic device (such as a watch bound to the mobile phone) can be instructed to send a message reminder. This can improve the timeliness and intelligence of message reminders between multiple devices and reduce the probability of missing new message reminders.

[0010] In another possible scenario, the method further includes: when it is determined that the reminder conditions are not met, instructing the second electronic device not to send message reminders. Optionally, the second electronic device can be instructed to only synchronize messages, which can also be understood as a silent notification method. In this way, the user can actively view new messages on the second electronic device.

[0011] In this scenario, by collecting the user's facial data, when it is detected that only the owner is using the first electronic device, the second electronic device can be instructed not to send a notification. This way, by determining whether the user is the owner, the intelligence of notifications between multiple devices can be improved, reducing the interference of dual notifications from multiple devices when only the owner is using the first electronic device.

[0012] In one possible implementation, the method further includes: performing message notification on the first electronic device using a first method, wherein the first method is a default message notification method configured for the first electronic device; or, performing message notification on the first electronic device using a second method, wherein the second method is a message notification method configured for the first electronic device when it is determined that the reminder conditions are met.

[0013] In this implementation, by collecting user facial data, different message notification methods can be used on the first electronic device depending on whether the user is the actual person or not, thereby improving the coordination of message reminders across multiple devices. It's understandable that when a message reminder is sent to the second electronic device, the number of message notification methods on the first electronic device can be reduced; for example, the intensity of the reminder can be decreased, or even a silent notification method can be used on the first electronic device, thus reducing the interference of dual reminders from multiple devices.

[0014] In one possible implementation, the second method is a notification method that meets, but is not limited to, at least one of the following conditions:

[0015] 1) Do not ring the bell;

[0016] 2) No vibration occurs;

[0017] 3) Do not send banner notifications, or send banner notifications but hide the new message content;

[0018] 4) Do not display the status bar icon;

[0019] 5) The breathing light is not displayed;

[0020] 6) Do not enable automatic screen wake-up.

[0021] In this implementation, when the second electronic device sends a message notification, the message notification methods on the first electronic device can be reduced. For example, fewer message notification methods can be retained on the first electronic device, thereby reducing the intensity of message notifications on the first electronic device. Alternatively, message notifications can be disabled on the first electronic device, which can be understood as a silent notification method. This reduces the interference of dual notifications from multiple devices.

[0022] In one possible implementation, collecting the first user's facial data includes: periodically collecting the user's facial data according to a preset period; or, collecting the user's facial data when a new message is received. For example, the preset period can be 100 milliseconds, 200 milliseconds, etc., and this application does not limit the specific value of the preset period.

[0023] In this implementation, by responding to the triggering of certain collection conditions, the user's facial data can be collected, thereby enabling the determination of whether the device owner is using the first electronic device.

[0024] In one possible implementation, in a scenario where user facial data is periodically collected according to a preset cycle, if the first moment does not meet the alert condition, a banner notification is displayed on the first electronic device along with new message content. The first moment is the moment the new message is received. Then, if the second moment meets the alert condition, the banner notification is either stopped or displayed on the first electronic device, but the new message content is hidden. The difference between the second moment and the first moment is less than a duration threshold, or the proportion of the difference to a preset duration is less than a proportion threshold. The preset duration indicates the total duration for the banner notification of new messages. At this point, the second electronic device can be instructed to issue a message alert.

[0025] In this implementation, during the process of detecting and issuing a message notification, the system updates from detecting that the reminder conditions are not met to detecting that the reminder conditions are met. This allows the second electronic device to still be instructed to issue a message reminder according to the scenario where the reminder conditions are met, even when the message notification duration is short. This reduces the probability of missing new message reminders.

[0026] In one possible implementation, in a scenario where user facial data is periodically collected according to a preset cycle, a second time is determined to meet the reminder conditions, and the first electronic device displays a banner notification but hides the new message content. Then, a third time is determined to not meet the reminder conditions, a banner notification is displayed on the first electronic device along with the new message content, and the display duration of the banner notification is extended. The third time is later than the second time. For example, the second time could be the moment the new message is received.

[0027] In this implementation, during the message notification process, the notification is updated from "the reminder conditions are met" to "the reminder conditions are not met." This can also be understood as "the notification is updated from 'not only the device owner using the first electronic device' to 'only the device owner using the first electronic device.'" This can extend the duration of the banner notification on the first electronic device, thereby improving the user's experience of viewing new messages and ensuring that the user can fully view the message content through the banner notification.

[0028] In one possible implementation, the alert condition includes when no face is recognized from the first user's face data; the alert condition also includes when the device distance between the first electronic device and the second electronic device is greater than or equal to a preset distance threshold.

[0029] In this implementation, by judging the device distance between the first electronic device and the second electronic device, when the user's facial data cannot be collected due to reasons such as the camera of the first electronic device being blocked, or when the quality of the face or image collected by the camera is poor due to lighting problems, or when the accuracy of the matching between the user's face and the owner's face template data is low, the device distance can be used as the basis for judging whether the first electronic device is used by the owner, thereby improving the flexibility of intelligent message reminders.

[0030] In one possible scenario, the message notification methods provided by the above implementations can be executed after detecting that the device is in the first display period after unlocking. The first duration can be determined based on a preset number of frames, or it can be preset. The preset number of frames can be less than or equal to 100 frames, for example, 5 frames. It can be understood that if the first electronic device is within the first 5 frames of the display after unlocking, the judgment provided by the above implementations can be omitted.

[0031] Based on the aforementioned possible scenarios, the method further includes: when it is detected that the user is within the first time period, updating the owner's face template library based on the collected second user face data; wherein, the owner's face template library includes M owner face template data, where M is less than or equal to N, and N is used to indicate a threshold number of owner face template data allowed to be included in the owner's face template library. For example, when the first electronic device is within the first 5 frames displayed after unlocking, the owner's face template library can be updated based on the collected user face data; thus, when the first electronic device displays image frames after the first 5 frames displayed after unlocking, it can collect user face data according to a preset period, thereby enabling message notifications.

[0032] In the above scenario, the confidence level of the user's facial data collected within a certain period after unlocking is relatively high. Therefore, it can be used to update the owner's facial template library, thereby improving the accuracy and diversity of the library. Furthermore, using the updated owner's facial template library to perform the message notification methods described in the above implementations can improve the accuracy of message notification processing.

[0033] In one possible implementation, in the scenario where the unlocking is based on biometrics, updating the device owner's face template library based on the collected second user's face data includes any of the following possible scenarios:

[0034] A) When N equals 1, the second user's face data is updated to the owner's face template data.

[0035] It's understandable that in scenarios where the unlock type is biometric unlock, and the owner's face template library contains at most one owner's face template data, the first electronic device can directly replace the owner's face template data included in the library with the collected user's face data. Alternatively, if the owner's face template library does not yet contain owner's face template data, the collected user's face data can be directly added to the library. In this way, updating the owner's face template library with user's face data collected in scenarios with high confidence can improve the accuracy of the library and better reflect the owner's face in the current state.

[0036] For example, biometric unlocking in this application embodiment may include, but is not limited to, face unlocking, fingerprint unlocking, palm print unlocking, iris unlocking, etc. Other embodiments are similar and will not be described in detail.

[0037] B) When N is greater than 1, if the second user's face data matches any of the M host face template data, the second user's face data replaces the first host face template data; wherein, the first host face template data is the one with the highest similarity to the second user's face data in the host face template library.

[0038] For example, the owner's face template library can include multiple owner's face template data from different angles for the same owner, such as a front view, left view, and right view of the owner. Another example is that the owner's face template library can also include owner's face template data for different owners. In this way, during matching, the owner's face template data with the highest similarity to the user's face data can be replaced, thereby updating similar owner's face template data, reducing redundancy of the same type of owner's face template data, and improving diversity. For example, if the collected user's face data is a front view of the owner, then the front view of that owner in the owner's face template library can be replaced, making the front view owner's face template data more closely match the owner's face in the current state. That is, updates can be performed separately according to different types of owner's face template data.

[0039] C) When N is greater than 1, if the second user's face data does not match any of the M host face template data, and M equals N, the second user's face data replaces the second host face template data; wherein the second host face template data is the one used the least in the host face template library.

[0040] It's understandable that when the owner's face template library contains multiple owner face templates and has reached a certain threshold (meaning the library is full), the confidence level of the collected user face data being the owner is high, given that the unlock type is biometric unlock. Therefore, when it's detected that the collected user face data doesn't match any of the owner's face templates, the collected user face data can replace the owner's face template data with the least used one. This allows for timely iteration of potentially expired owner face template data, improving the accuracy of message notifications. For example, if the second user face data doesn't match any of the M owner face templates, it might indicate a new owner has been added, in which case the new owner's face template data can be added promptly; or, it might be due to a significant difference between the current owner's face template data and the existing owner's face data, in which case the owner's face template data can be updated promptly.

[0041] D) When N is greater than 1, and M is less than N, the newly added second user's face data is the owner's face template data.

[0042] In this scenario, when the number of templates in the owner's face template library is insufficient (or the library is not full), the electronic device can bypass the need to match the user's face data with the owner's face template library. Since the unlock type is biometric unlock, the confidence level that the collected user's face data belongs to the owner is high. Therefore, the collected user's face data can be directly added as new owner face template data. This not only increases the number of templates but also ensures that the owner's face template data more closely matches the owner's face in the current state.

[0043] In another possible implementation, in the scenario where the unlock is a biometric unlock, before updating the owner's face template library based on the collected second user's face data, the method further includes: determining that the second user's face data is unobstructed user face data; wherein, the owner's face template library includes M1 unobstructed owner's face template data, M1 is less than or equal to N1, and N1 is used to indicate a threshold number of unobstructed owner's face template data allowed to be included in the owner's face template library. Updating the owner's face template library based on the collected second user's face data includes any of the following possible scenarios:

[0044] A) When N1 equals 1, the second user's face data is updated to the unobstructed owner's face template data.

[0045] B) When N1 is greater than 1, if the second user's face data matches any of the M1 unobstructed owner's face template data, the second user's face data replaces the first unobstructed owner's face template data; wherein, the first unobstructed owner's face template data is the one with the highest similarity to the second user's face data in the owner's face template library.

[0046] C) When N1 is greater than 1, if the second user's face data does not match any of the M1 unobstructed owner's face template data and M1 is equal to N1, the second user's face data replaces the second unobstructed owner's face template data; wherein, the second unobstructed owner's face template data is the one used the least among the unobstructed owner's face template data included in the owner's face template library.

[0047] D) If N1 is greater than 1, and M1 is less than N1, the newly added second user face data is the unobstructed owner face template data.

[0048] The beneficial effects of various possible scenarios included in this implementation method can be found in the beneficial effects of the previous implementation method. Furthermore, by classifying the user's facial template data into different categories based on occlusion levels, this implementation method can improve matching accuracy by matching the user's facial data with the user's facial template data of the same category.

[0049] In addition, compared to the above-mentioned biometric unlocking scenarios, in the scenario where the unlocking is non-biometric (such as password), when it is detected that the owner's face template library is empty, the first electronic device can process subsequent message reminders according to the existing intelligent message reminder logic; or, the first electronic device can also add the collected unobstructed user face data as the owner's face template data, which can ensure that there is at least one owner's face template data in the owner's face template library, so as to facilitate subsequent matching of message reminders based on the owner's face template data.

[0050] In another possible implementation, before updating the owner's face template library based on the collected second user's face data, the method further includes: determining that the second user's face data is occluded user face data; wherein, the owner's face template library includes M2 occluded owner's face template data, M2 is less than or equal to N2, and N2 is used to indicate a threshold number of occluded owner's face template data allowed to be included in the owner's face template library. Updating the owner's face template library based on the collected second user's face data includes any of the following possible scenarios:

[0051] A) When N2 equals 1 and the unlocking is a face unlock, the second user's face data is updated to the occluded owner's face template data.

[0052] For example, when the unlock type is face unlock, if the owner's face template library does not include occluded owner's face template data, the second user's face data can be directly added as occluded owner's face template data. Alternatively, if the owner's face template library already includes occluded owner's face template data, the second user's face data can be directly replaced with occluded owner's face template data.

[0053] B) When N2 equals 1 and the unlocking is non-face unlocking, if M2 is less than N2, the newly added second user face data is the occluded owner's face template data. Alternatively, if M2 equals N2, it is not necessary to replace the occluded owner's face template data with the second user face data.

[0054] For example, when the unlock type is non-face unlock (such as fingerprint unlock or password unlock), the second user's face data is only added as the occluded owner's face template data if the owner's face template library does not include occluded owner's face template data. Conversely, if the owner's face template library already includes occluded owner's face template data, there is no need to update the occluded owner's face template data; that is, the second user's face data will not be replaced with the occluded owner's face template data.

[0055] It's understandable that, given the high confidence level of facial recognition, when the number of templates is insufficient, the collected user facial data can be directly added as a new template, and when the number of templates is full, the collected user facial data can replace the old template. On the other hand, the confidence level of fingerprint or password unlocking is lower than that of facial recognition. Templates can only be added when the template library does not contain a template, which facilitates subsequent matching for message notification judgment. When the template library already contains a template, there is no need to replace the old template.

[0056] Furthermore, given the increased difficulty of facial recognition in scenarios with occluded faces, this application typically uses user facial data captured by a camera in low-power mode for updating the owner's facial template, which has lower confidence than facial data captured by a normal camera. In contrast, facial unlock typically uses facial data captured by a normal camera, which has higher confidence. Therefore, considering that the collected user facial data is occluded, when the unlock type is facial unlock, due to the higher confidence, it can be used to update the template, such as adding a new template or replacing an old one. However, when the unlock type is non-facial unlock, other unlocking methods may be used due to facial recognition failure, resulting in lower confidence. Therefore, a new template is only added when the owner's facial template library does not include an occluded owner's facial template, rather than replacing an old one. This ensures that the owner's facial template library includes at least an occluded owner's facial template, facilitating subsequent message notification judgment.

[0057] C) When N2 is greater than 1, if the second user's face data matches any of the M2 occluded owner's face template data and the unlocking is a face unlock, the second user's face data replaces the first occluded owner's face template data; wherein, the first occluded owner's face template data is the one with the highest similarity to the second user's face data in the owner's face template library.

[0058] D) When N2 is greater than 1, if the second user's face data does not match any of the M2 occluded owner's face template data, the unlocking is a face unlock, and M2 equals N2, the second user's face data replaces the second occluded owner's face template data; wherein, the second occluded owner's face template data is the one with the lowest usage frequency among the occluded owner's face template data included in the owner's face template library.

[0059] The beneficial effects of each possible scenario included in this implementation can be found in the beneficial effects of the previous implementation, and will not be repeated here.

[0060] For example, the occluded face template data of the human owner can typically be one or more, and this application does not limit this.

[0061] In one alternative example, the sum of M1 and M2 is M, and the sum of N1 and N2 is N. In another alternative example, M1 is M and N1 is N; or, M2 is M and N2 is N.

[0062] In one possible design, the user's facial template library is updated within the first 5 frames displayed after unlocking. During this period, user facial data can be collected once or multiple times. When updating the user's facial template library according to the above possible implementations, the judgment can be made based on each collected user facial data, or the user facial data with the best or better collection effect can be selected from multiple collected user facial data for judgment.

[0063] Based on the above design, in the aforementioned implementation methods, the second user's face data does not match any of the M (or M1 or M2) host face template data. This can be implemented such that each time the user's face data is collected, it does not match any of the M (or M1 or M2) host face template data. Alternatively, it can be implemented such that the user's face data with the best or better collection effect does not match any of the M (or M1 or M2) host face template data.

[0064] In one possible design, the method further includes: counting the number of times each host's face template data is used.

[0065] In this implementation, by statistically analyzing the number of times the owner's face template data is used, infrequently used owner's face template data can be aged out in a timely manner.

[0066] Secondly, embodiments of this application provide a message notification method. This method can be applied to a first electronic device. The method, applied to the first electronic device, includes: receiving a new message; when a message notification of the new message is detected using a first method, instructing a second electronic device to provide a message notification; wherein the first method includes: providing a banner notification but hiding the content of the new message.

[0067] This method utilizes the output of artificial intelligence (AI) information protection functions, which can then be reused for message notifications. This enhances the flexibility of intelligent message alerts, enabling the protection of message content when the user is not using the primary electronic device and reducing missed message notifications.

[0068] In another possible scenario, the method further includes: when a message notification for the new message is detected using a second method, instructing a second electronic device not to provide a message reminder; wherein the second method includes: providing a banner notification and displaying the new message content.

[0069] In one possible implementation, the new message is received at a first moment. Before detecting that the new message is notified using the first method, the method further includes: detecting that the new message is notified using the second method at the first moment. Detecting that the new message is notified using the first method includes: detecting that the new message is notified using the first method at a second moment; wherein the difference between the second moment and the first moment is less than a duration threshold, or the proportion of the difference to a preset duration is less than a proportion threshold, the preset duration being used to indicate the total duration of the banner notification for the new message.

[0070] Thirdly, embodiments of this application provide a message notification method. This method can be applied to a first electronic device. In this method, when it is detected that the device is within a first display period after unlocking, the device owner's face template library is updated based on the collected second user's face data. The device owner's face template library includes M device owner face template data, where M is less than or equal to N, and N indicates a threshold number of device owner face template data allowed to be included in the device owner's face template library, i.e., the maximum number of templates.

[0071] In one possible implementation, in the scenario where the unlocking is based on biometrics, updating the device owner's face template library based on the collected second user's face data includes any of the following possible scenarios:

[0072] A) When N equals 1, the second user's face data is updated to the owner's face template data.

[0073] B) When N is greater than 1, if the second user's face data matches any of the M host face template data, the second user's face data replaces the first host face template data; wherein, the first host face template data is the one with the highest similarity to the second user's face data in the host face template library.

[0074] C) When N is greater than 1, if the second user's face data does not match any of the M host face template data, and M equals N, the second user's face data replaces the second host face template data; wherein the second host face template data is the one used least frequently in the host face template library; or...

[0075] D) When N is greater than 1, and M is less than N, the newly added second user's face data is the owner's face template data.

[0076] In another possible implementation, in the scenario where the unlock is a biometric unlock, before updating the owner's face template library based on the collected second user's face data, the method further includes: determining that the second user's face data is unobstructed user face data; wherein, the owner's face template library includes M1 unobstructed owner's face template data, M1 is less than or equal to N1, and N1 is used to indicate a threshold number of unobstructed owner's face template data allowed to be included in the owner's face template library. Updating the owner's face template library based on the collected second user's face data includes any of the following possible scenarios:

[0077] A) When N1 equals 1, the second user's face data is updated to the unobstructed owner's face template data.

[0078] B) When N1 is greater than 1, if the second user's face data matches any of the M1 unobstructed owner's face template data, the second user's face data replaces the first unobstructed owner's face template data; wherein, the first unobstructed owner's face template data is the one with the highest similarity to the second user's face data in the owner's face template library.

[0079] C) When N1 is greater than 1, if the second user's face data does not match any of the M1 unobstructed owner's face template data and M1 is equal to N1, the second user's face data replaces the second unobstructed owner's face template data; wherein, the second unobstructed owner's face template data is the one with the lowest usage frequency among the unobstructed owner's face template data included in the owner's face template library.

[0080] D) If N1 is greater than 1, and M1 is less than N1, the newly added second user face data is the unobstructed owner face template data.

[0081] In another possible implementation, before updating the owner's face template library based on the collected second user's face data, the method further includes: determining that the second user's face data is occluded user face data; wherein, the owner's face template library includes M2 occluded owner's face template data, M2 is less than or equal to N2, and N2 is used to indicate a threshold number of occluded owner's face template data allowed to be included in the owner's face template library. Updating the owner's face template library based on the collected second user's face data includes any of the following possible scenarios:

[0082] A) When N2 equals 1 and the unlocking is a face unlock, the second user's face data is updated to the occluded owner's face template data.

[0083] B) When N2 equals 1 and the unlocking is non-face unlocking, if M2 is less than N2, the newly added second user face data is the occluded owner's face template data. Alternatively, if M2 equals N2, it is not necessary to replace the occluded owner's face template data with the second user face data.

[0084] C) When N2 is greater than 1, if the second user's face data matches any of the M2 occluded owner's face template data and the unlocking is a face unlock, the second user's face data replaces the first occluded owner's face template data; wherein, the first occluded owner's face template data is the one with the highest similarity to the second user's face data in the owner's face template library.

[0085] D) When N2 is greater than 1, if the second user's face data does not match any of the M2 occluded owner's face template data, the unlocking is a face unlock, and M2 equals N2, the second user's face data replaces the second occluded owner's face template data; wherein, the second occluded owner's face template data is the one with the lowest usage frequency among the occluded owner's face template data included in the owner's face template library.

[0086] For example, the occluded face template data of the human owner can typically be one or more, and this application does not limit this.

[0087] In one alternative example, the sum of M1 and M2 is M, and the sum of N1 and N2 is N. In another alternative example, M1 is M and N1 is N; or, M2 is M and N2 is N.

[0088] In one possible design, the user's facial template library is updated within the first 5 frames displayed after unlocking. During this period, user facial data can be collected once or multiple times. When updating the user's facial template library according to the above possible implementations, the judgment can be made based on each collected user facial data, or the user facial data with the best or better collection effect can be selected from multiple collected user facial data for judgment.

[0089] Based on the above design, in the aforementioned implementation methods, the second user's face data does not match any of the M (or M1 or M2) host face template data. This can be implemented such that each time the user's face data is collected, it does not match any of the M (or M1 or M2) host face template data. Alternatively, it can be implemented such that the user's face data with the best or better collection effect does not match any of the M (or M1 or M2) host face template data.

[0090] In one possible design, the method further includes: counting the number of times each host's face template data is used.

[0091] In this implementation, by statistically analyzing the number of times the owner's face template data is used, infrequently used owner's face template data can be aged out in a timely manner.

[0092] Based on the aforementioned update to the owner's face template library, the first electronic device can determine how to send message notifications to multiple electronic devices when a new message is sent.

[0093] In one possible design, the method further includes: collecting face data of a first user; and when it is determined that the reminder conditions are met, instructing a second electronic device to provide a message reminder when a new message is present; wherein the reminder conditions include at least one of the following: the first user's face data fails to match the owner's face template data, multiple faces or multiple pairs of eyes looking at the screen are identified from the first user's face data, or no face is identified from the first user's face data, and the second electronic device is a wearable device bound to the first electronic device.

[0094] In another possible design, the method further includes: when it is determined that the reminder condition is not met, instructing the second electronic device not to send a message reminder.

[0095] In one possible design, the method further includes: performing message notification on the first electronic device using a first method, wherein the first method is the default message notification method configured for the first electronic device; or, performing message notification on the first electronic device using a second method, wherein the second method is the message notification method configured for the first electronic device when it is determined that the reminder conditions are met.

[0096] In one possible design, the second method is a message notification method that has at least one of the following conditions: no ringing; no vibration; no banner notification, or a banner notification but hiding the new message content; no status bar icon; no breathing light; no automatic screen wake-up.

[0097] In one possible design, collecting the first user's facial data includes: periodically collecting the first user's facial data according to a preset period. Alternatively, collecting the first user's facial data when a new message is detected.

[0098] In one possible design, before determining that the reminder condition is met, the method further includes: determining that the reminder condition is not met at a first moment, and displaying a banner notification and new message content on the first electronic device, wherein the first moment is the moment when the new message is received. Determining that the reminder condition is met includes: determining that the reminder condition is met at a second moment. The method further includes: ceasing to display banner notifications on the first electronic device, or displaying banner notifications but hiding the new message content; wherein the difference between the second moment and the first moment is less than a duration threshold, or the proportion of the difference to a preset duration is less than a proportion threshold, wherein the preset duration is used to indicate the total duration of the banner notification for the new message.

[0099] In one possible design, determining that the reminder condition is met includes: determining that the reminder condition is met at a second time. The method further includes: displaying a banner notification on the first electronic device but hiding the new message content; determining that the reminder condition is not met at a third time, displaying a banner notification on the first electronic device and showing the new message content, and extending the display duration of the banner notification, wherein the third time is later than the second time.

[0100] In one possible design, the alert condition includes when no face is recognized from the first user's face data; the alert condition also includes when the device distance between the first electronic device and the second electronic device is greater than or equal to a preset distance threshold.

[0101] In one possible design, before collecting the first user's facial data, the method further includes: detecting a first duration after unlocking and displaying the information. This can also be understood as the first electronic device updating the user's facial template library before executing the message notification process.

[0102] Fourthly, this application provides an electronic device comprising a plurality of functional modules; the plurality of functional modules interact to implement the methods performed by the first electronic device in any of the above aspects and their respective embodiments. The plurality of functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the plurality of functional modules can be arbitrarily combined or divided based on specific implementations.

[0103] Fifthly, this application provides an electronic device including at least one processor and at least one memory, wherein the at least one memory stores computer program instructions, and when the electronic device is running, the at least one processor executes the method executed by the first electronic device in any of the above aspects and embodiments.

[0104] Sixthly, this application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, causes the computer to perform the method executed by the first electronic device in any of the above aspects and their possible implementations.

[0105] In a seventh aspect, this application provides a computer program product comprising: a computer program (also referred to as code or instructions), and a method for causing a computer to perform any of the above aspects and their possible implementations as an electronic device when the computer program is run.

[0106] Eighthly, this application also provides a chip for reading a computer program stored in a memory and executing the method executed by the first electronic device in any of the above aspects and their possible implementations.

[0107] Ninthly, this application also provides a chip system including a processor for supporting a computer device in implementing the methods executed by the first electronic device in any of the above aspects and their possible implementations. In one possible implementation, the chip system further includes a memory for storing programs and data necessary for the computer device. The chip system may be composed of chips or may include chips and other discrete devices.

[0108] In a tenth aspect, embodiments of this application also provide a graphical user interface on an electronic device, the electronic device having a display screen, one or more memories, and one or more processors, the one or more processors being configured to execute one or more computer programs stored in the one or more memories, the graphical user interface including a graphical user interface displayed by a first electronic device when the electronic device executes any of the above aspects and their possible implementations.

[0109] For details on the beneficial effects of any of the second to tenth aspects and their possible implementations, please refer to the beneficial effects of the various possible implementations in the first aspect above; they will not be repeated here. Attached Figure Description

[0110] Figure 1 is a schematic diagram of the settings interface for intelligent message reminders;

[0111] Figure 2 is a schematic diagram of the hardware structure of a possible electronic device provided in an embodiment of this application;

[0112] Figure 3 is a software architecture block diagram of an electronic device provided in an embodiment of this application;

[0113] Figure 4 is a schematic diagram of a message notification method provided in an embodiment of this application;

[0114] Figure 5 is a schematic diagram of the settings interface of a message notification method provided in an embodiment of this application;

[0115] Figure 6 is a schematic diagram of the process for obtaining or updating the host's face template library provided in an embodiment of this application;

[0116] Figure 7 is a schematic diagram of another scenario of a message notification method provided in an embodiment of this application;

[0117] Figure 8 is a flowchart illustrating a message notification method provided in an embodiment of this application. Detailed Implementation

[0118] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0119] The embodiments of this application can be applied to the field of terminal technology, and specifically can be applied to intelligent message reminder scenarios based on multiple devices.

[0120] For example, Figure 1 is a schematic diagram of the message smart notification settings interface. As shown in interface 101 of Figure 1, this is the message notification settings interface on the mobile phone. On interface 101, you can enable the message notification function, enable the message smart notification function, and set different message notification methods for different applications. On interface 101, when the mobile phone detects that the user clicks on the "Learn More" control related to the message smart notification function, interface 102 can be displayed.

[0121] As shown in interface 102, when the smart message notification function is enabled, different message notification logic can be configured for different mobile phone usage scenarios and watch (band) wearing situations. When the smart message notification function is disabled, the message notification logic can be configured to send message notifications on both the mobile phone and the watch (band).

[0122] For example, a combination of multiple devices, namely a mobile phone and a smartwatch (which may also be referred to as "watch" in the following embodiments, and the watch in this application embodiment is a watch with some smart functions), is used as an example. The message smart reminder logic between the mobile phone and the watch can be as shown in Table 1 below:

[0123] Table 1

[0124] As shown in Table 1 above, if the phone is unlocked and the watch is worn, when a new message is an emergency (such as an incoming call, an alarm, or other notification that requires immediate attention), the smart notification logic can alert both the phone and the watch. This ensures the timeliness of notifications for emergency events.

[0125] If the phone is unlocked and the watch is worn, in the case of a new message notification, the smart notification logic can be that the phone notifies the user, while the watch only syncs the message (this can also be understood as a silent message notification). This means that when the phone is unlocked, message notifications can be maintained on the phone while reducing notifications on the watch, thus avoiding the disturbance of double reminders for the user. Silent message notifications mean that the user will not be aware of the new message but can actively view it, for example, by pulling down the notification bar.

[0126] If the phone is locked and the watch is worn, when a new message is an urgent event (such as an incoming call, an alarm, or other notification that requires immediate attention), the smart notification logic can alert both the phone and the watch. This ensures timely notification for urgent events.

[0127] If the phone is locked and the watch is worn, in the case of a new message notification, the smart notification logic can be configured so that the phone does not send a notification, but the watch does. This is understandable, as the user is generally not using the phone when it is locked, so notifying the user of new messages only through message notifications on the watch is a timely way to notify them.

[0128] The above intelligent message notification logic can reduce user disruption in some scenarios. However, there may still be instances where new message notifications are missed.

[0129] In view of this, embodiments of this application provide a message notification method. In this method, a first electronic device collects user facial data. If, based on the collected user facial data, it is determined that the user's facial data fails to match the device owner's facial template data, multiple faces or multiple pairs of eyes looking at the screen are identified from the collected user facial data, or no face is identified, then a message notification can be sent to a second electronic device when a new message is received. This allows the user to promptly perceive the existence of a new message, reducing the likelihood of missed notifications. This method supplements the intelligent message notification logic for new message notification scenarios, improving the intelligence of message notifications and reducing the probability of missed notifications.

[0130] The first electronic device can be a mobile phone, tablet computer, etc., and the second electronic device can be a wearable device attached to the first electronic device, such as a watch, bracelet, or earphones. It is understood that a communication connection is established between the second electronic device and the first electronic device. It is also understood that this application does not impose any restrictions on the specific types of the first and second electronic devices.

[0131] The technical solutions in this application embodiment can be applied to a first electronic device. The first electronic device determines the message notification method; then, while sending a new message to a second electronic device via a communication link, it carries indication information for indicating the message notification method (e.g., at least one of vibration, ringing, automatic screen lighting, etc.). Alternatively, the first electronic device can also upload the message notification method to a cloud server, and one or more second electronic devices can obtain the message notification method from the cloud server.

[0132] The technical solutions in this application embodiment can also be applied to a message notification system, which may include a first electronic device and one or more second electronic devices.

[0133] The technical solutions in this application embodiment can also be applied to cloud servers. The cloud server can determine the message notification method and proactively send it to the first electronic device and the second electronic device, or send it in response to a request from the first electronic device or the second electronic device. Optionally, the cloud server can carry an indication of the message notification method while sending a new message to the first electronic device and the second electronic device. Alternatively, the cloud server can send the new message and the message notification method separately.

[0134] The electronic devices to which this application's embodiments can be applied include, but are not limited to, those equipped with... Alternatively, it can be an electronic device running another operating system. For example, the electronic device described in the foregoing embodiments can be used.

[0135] Figure 2 illustrates a possible hardware structure diagram of an electronic device. The electronic device 200 includes components such as a radio frequency (RF) circuit 210, a power supply 220, a processor 230, a memory 240, an input unit 250, a display unit 260, an audio circuit 270, a communication interface 280, and a wireless fidelity (Wi-Fi) module 290. Those skilled in the art will understand that the hardware structure of the electronic device 200 shown in Figure 2 does not constitute a limitation on the electronic device 200. The electronic device 200 provided in this application embodiment may include more or fewer components than shown, may combine two or more components, or may have different component configurations. The various components shown in Figure 2 can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0136] The following is a detailed description of each component of the electronic device 200 with reference to Figure 2:

[0137] The RF circuit 210 can be used for receiving and transmitting data during communication or a call. Specifically, after receiving downlink data from the base station, the RF circuit 210 sends it to the processor 230 for processing; additionally, it sends uplink data to be transmitted to the base station. Typically, the RF circuit 210 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier (LNA), a duplexer, etc.

[0138] Furthermore, the RF circuit 210 can also communicate with other devices via a wireless communication network. The wireless communication can use any communication standard or protocol, including but not limited to Global System for Mobile Communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, and Short Message Service (SMS).

[0139] Wi-Fi technology is a short-range wireless transmission technology. The electronic device 200 can connect to an access point (AP) via the Wi-Fi module 290, thereby enabling access to the data network. The Wi-Fi module 290 can be used for receiving and sending data during communication.

[0140] The electronic device 200 can physically connect to other devices through the communication interface 280. Optionally, the communication interface 280 can be connected to the communication interfaces of other devices via a cable to enable data transmission between the electronic device 200 and other devices.

[0141] The electronic device 200 can also perform communication services and interact with other electronic devices. Therefore, the electronic device 200 needs to have data transmission capabilities, meaning it needs to include a communication module. Although Figure 2 shows the RF circuit 210, the Wi-Fi module 290, and the communication interface 280, it is understood that the electronic device 200 contains at least one of the aforementioned components or other communication modules (such as a Bluetooth module) for data transmission.

[0142] For example, when the electronic device 200 is a mobile phone, the electronic device 200 may include the RF circuit 210, and may also include the Wi-Fi module 290, or may include a Bluetooth module, a flash module, etc. (not shown in Figure 2); when the electronic device 200 is a tablet computer, the electronic device 200 may include the Wi-Fi module, or may include a Bluetooth module, a flash module, etc. (not shown in Figure 2); when the electronic device 200 is a smart home device, the electronic device 200 may include the Wi-Fi module 290, or may include a Bluetooth module, a flash module, etc. (not shown in Figure 2).

[0143] The memory 240 can be used to store software programs and modules. The processor 230 executes various functional applications and data processing of the electronic device 200 by running the software programs and modules stored in the memory 240. Optionally, the memory 240 may mainly include a program storage area and a data storage area. The program storage area may store the operating system (mainly including software programs or modules corresponding to the kernel layer, system layer, application framework layer, and application layer). In this embodiment, the memory 240 may, for example, store a user owner face template library, which may include at least one user owner face template data to facilitate matching by the electronic device 200 based on the collected user face data. Optionally, the user owner face template library stored in the memory 240 may also be divided into occluded user owner face template data and unoccluded user owner face template data; for example, the user owner face template library may include at least one unoccluded user owner face template data and at least one occluded user owner face template data.

[0144] In addition, the memory 240 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0145] The input unit 250 can be used to receive editing operations on various types of data objects, such as numbers or characters, input by the user, and to generate key signal inputs related to user settings and function control of the electronic device 200. Optionally, the input unit 250 may include a touch panel 251 and other input devices 252.

[0146] The touch panel 251, also known as a touchscreen, can collect user touch operations on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 251), and drive corresponding connection devices according to a pre-set program. In this embodiment, the touch panel 251 can collect user operations on or near it. For example, when the electronic device 200 is a mobile phone, the user operation can be a swipe operation to pull down the notification bar to view messages in the notification bar; or, the user operation can also be an operation to set the message notification function, etc.

[0147] Optionally, the other input device 252 may include, but is not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), mouse, joystick, etc.

[0148] The display unit 260 can be used to display information input by the user or information provided to the user, as well as various menus of the electronic device 200. The display unit 260 is the display system of the electronic device 200, used to present the interface and realize human-computer interaction. The display unit 260 may include a display panel 261. Optionally, the display panel 261 can be configured as a liquid crystal display (LCD), organic light-emitting diode (OLED), or the like. In this embodiment, the display unit 260 can be used to display a user interface. For example, the display unit 260 can display a message notification interface corresponding to when a message notification is required based on the method provided in this embodiment. Another example is that when a message notification is not required, the display unit 260 can display the notification bar interface in response to a user's pull-down notification bar swipe operation. Yet another example is that the display unit 260 can also display a settings interface for the message notification function provided in this embodiment.

[0149] The processor 230 is the control center of the electronic device 200. It connects various components via various interfaces and lines, and executes software programs and / or modules stored in the memory 240, as well as calling data stored in the memory 240, to perform various functions and process data of the electronic device 200, thereby enabling various services based on the electronic device 200. In this embodiment, the processor 230 can be used to implement a message notification method provided in this embodiment, used to determine the logic for intelligent message notification by the first and second electronic devices, and also used to instruct the first and second electronic devices to perform intelligent message notification according to the logic.

[0150] The electronic device 200 also includes a power supply 220 (such as a battery) for supplying power to various components. Optionally, the power supply 220 can be logically connected to the processor 230 through a power management system, thereby enabling the power management system to manage functions such as charging, discharging, and power consumption.

[0151] As shown in Figure 2, the electronic device 200 also includes an audio circuit 270, a microphone 271, and a speaker 272, providing an audio interface between the user and the electronic device 200. The audio circuit 270 converts audio data into signals recognizable by the speaker 272 and transmits the signals to the speaker 272, where the speaker 272 converts them into sound signals for output. The microphone 271 collects external sound signals (such as human speech or other sounds) and converts the collected external sound signals into signals recognizable by the audio circuit 270, sending them to the audio circuit 270. The audio circuit 270 can also convert the signals transmitted by the microphone 271 into audio data, and then output the audio data to the RF circuit 210 for transmission to, for example, another electronic device, or output the audio data to the memory 240 for further processing.

[0152] Although not shown, the electronic device 200 may also include a camera, at least one sensor, etc., which will not be described in detail here. At least one sensor may include, but is not limited to, a pressure sensor, a barometric pressure sensor, an accelerometer, a distance sensor, a fingerprint sensor, a touch sensor, a temperature sensor, etc. For example, the camera may include a front-facing camera and a rear-facing camera. In this embodiment, the electronic device 200 may use a camera on the side of the screen primarily used for displaying content in its current state to collect user facial data; wherein, the side of the screen primarily used for displaying content can also be understood as the side of the screen facing the user. For example, when the electronic device 200 is a candybar phone, the camera on the side of the screen used for displaying content can be understood as a front-facing camera. As another example, when the electronic device 200 is a foldable phone, when the phone is folded, the camera on the side of the screen used for displaying content can be understood as a camera on the outer screen; when the phone is unfolded, the camera on the side of the screen used for displaying content can be understood as a camera on the inner screen.

[0153] Optionally, the camera required in this application embodiment can collect user face data in a low-power mode, thereby reducing the power consumption of the electronic device 200 while satisfying the user's face data matching requirements.

[0154] The operating system (OS) involved in this application embodiment is the most basic system software running on the electronic device 200. The software system of the electronic device 200 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment takes an operating system adopting a layered architecture as an example to illustrate the software architecture of the electronic device 200.

[0155] Figure 3 is a software architecture block diagram of an electronic device provided in an embodiment of this application. As shown in Figure 3, the software architecture of the electronic device can be a layered architecture. For example, the software can be divided into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the operating system is divided into five layers, from top to bottom: the application layer, the application framework layer (framework, FWK), the runtime and system library, the kernel layer, and the hardware layer.

[0156] The application layer can include a series of application packages. As shown in Figure 3, the application layer can include a user interface (UI), camera, settings, skin modules, third-party applications, etc. Third-party applications may include, for example, wireless local area network (WLAN), music, call, Bluetooth, video, etc.

[0157] In one possible implementation, the application can be developed using Java, by calling the application programming interface (API) provided by the application framework layer. Developers can then interact with the underlying operating system layers (such as the hardware layer and kernel layer) to develop their own applications. This application framework layer primarily consists of a series of services and management systems within the operating system.

[0158] The application framework layer provides application programming interfaces and a programming framework for applications within the application layer. The application framework layer includes some predefined functions. As shown in Figure 3, the application framework layer may include a view system, activity manager, window manager, content provider, phone manager, resource manager, notification manager, etc.

[0159] The Activity Manager manages the lifecycle of each application and provides commonly used navigation and back functions, offering an interactive interface for all program windows.

[0160] The window manager is used to manage windowed applications. It can obtain the screen size, determine if a status bar is present, lock the screen, and capture screenshots. The content provider stores and retrieves data, making this data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0161] A view system includes both visual and non-visual controls, such as controls that display text and controls that display images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text message notification icon could include views that display text and views that display images.

[0162] A phone manager is used to provide communication functions for electronic devices. For example, it manages call status (including connection and disconnection).

[0163] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0164] The notification manager allows applications to display notification information in the status bar. It can be used to convey informational messages and can disappear automatically after a short pause without user interaction. For example, the notification manager can be used to notify of download completion or message alerts. The notification manager can also appear as an icon or scrolling text in the system's top status bar, such as notifications from background applications, or as a dialog window on the screen. Examples include displaying text messages in the status bar, emitting alert sounds, vibrating electronic devices, and flashing indicator lights. In this embodiment, the notification manager can send message notifications based on the message intelligent reminder logic determined by the method provided in this embodiment. Message notifications can include message alerts and silent notifications.

[0165] The runtime includes the core libraries and the virtual machine. The runtime is responsible for the scheduling and management of the operating system.

[0166] The core library consists of two parts: one part contains the functionalities that the Java language needs to call, and the other part contains the core libraries of the operating system. The application layer and application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0167] A system library can include multiple functional modules. For example: a surface manager, a media framework, a 3D graphics processing library (e.g., OpenGL ES), a 2D graphics engine (e.g., SGL), etc.

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

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

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

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

[0172] In some embodiments, a 3D graphics processing library can be used to draw 3D motion images, and a 2D graphics engine can be used to draw 2D motion images.

[0173] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0174] The hardware layer can include various types of sensors, such as accelerometers, gravity sensors, and touch sensors.

[0175] Typically, electronic devices 200 can run multiple applications simultaneously. In a simpler scenario, one application corresponds to one process; in a more complex scenario, one application can correspond to multiple processes. Each process has a unique process ID.

[0176] It should be understood that in the embodiments of this application, "at least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or multiple. "Multiple" refers to two or more. "And / or" is used to describe the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing 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.

[0177] Furthermore, it should be understood that in the description of this application, terms such as "first" and "second" are used only for distinguishing descriptive purposes and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order. For example, in the following embodiments, "first operation" and "second operation" are only used to distinguish and describe operations in different scenarios and are not used to limit specific operation methods, etc.

[0178] It should be understood that the hardware structure of the electronic device can be as shown in Figure 2, and the software system architecture can be as shown in Figure 3. The software programs and / or modules corresponding to the software system architecture in the electronic device can be stored in the memory 240, and the processor 230 can run the software programs and applications stored in the memory 240 to execute the flow of a message reminder method provided in the embodiments of this application.

[0179] The following describes the terms that may be used in the embodiments of this application:

[0180] (1) Message reminders are a type of message notification, which refers to message notifications that allow users to perceive them in real time.

[0181] For example, message notifications on a mobile phone may include, but are not limited to, at least one of the following notification methods: vibration, ringing, banner notification, lock screen notification, status bar icon, breathing light, automatic screen wake-up, and badge.

[0182] For example, message notifications on a watch can include, but are not limited to, at least one of the following notification methods: vibration, ringing, lock screen notification, status bar icon, automatic screen wake-up, badge, etc.

[0183] It should be noted that the specific notification method for messages on a mobile phone or watch can be determined based on system configuration or user settings, and this application does not impose any limitations on this. For example, users can set the notification method for the phone to vibrate, ring, or display a banner notification in the message notification settings interface.

[0184] (2) Silent message notification (or simply "silent notification") is also a type of message notification. It refers to a message notification method that allows users to receive notifications without being aware of them in real time, thus reducing disturbance to users. It can generally refer to only synchronizing messages, or it can be understood as not sending message reminders.

[0185] Silent notifications can include, but are not limited to, at least one of the following methods: synchronized messages (in which case users can actively view new synchronized messages by pulling down the notification bar).

[0186] (3) The owner of the device can be understood as the owner of the electronic device. The owner's information can be defined by pre-configuration, and there can be one owner or multiple owners.

[0187] For example, an electronic device can store owner face template data. This owner face template data can be obtained by recording facial data during face unlock of the electronic device, or it can be acquired within a preset time period after successful face unlock. The following embodiments provide a detailed description of acquiring owner face template data, which will not be elaborated upon here.

[0188] (4) User facial data refers to the current facial data collected by the electronic device. For example, the electronic device can use a camera on the side of the screen primarily used for displaying content in the current state of the electronic device to collect the user's facial data; whereby the side of the screen primarily used for displaying content in the current state of the electronic device can also be understood as the side of the screen facing the user. For example, when the electronic device is a candybar phone, the camera can be the front-facing camera of the candybar phone. As another example, when the electronic device is a foldable phone and the foldable phone is in a folded state, the camera can be the camera on the outer screen of the foldable phone; or, when the foldable phone is in an unfolded state, the camera can be the camera on the inner screen of the foldable phone.

[0189] Once it is determined that the user's facial data matches the owner's facial template data, it can be confirmed that the user is the owner of the device.

[0190] If it is determined that the user's facial data does not match the device owner's facial template data, it can be concluded that the user is not the device owner. For example, the electronic device may be being used by a family member or someone else.

[0191] (5) The user's face template library (which can also be simply referred to as the "template library" in this embodiment) may include M templates (which can also be simply referred to as "templates" in this embodiment), and may include at most N templates. It can be understood that when M is less than N, it indicates that the template library is not full, and the electronic device can add the collected user face data as a template based on certain conditions to update the template library; when M equals N, it indicates that the template library is full, and the electronic device can replace the stored templates based on the collected user face data based on certain conditions to update the template library. The specific implementation method of updating the template library will be described in detail later.

[0192] In some possible scenarios, the template library can also be divided into templates with occluded faces and templates without occluded faces; the threshold for the number of templates with occluded faces can be N1 (N1 is generally ≥2, for example, N1 can be 3), and the threshold for the number of templates without occluded faces can be N2 (N2 ≥1, for example, N2 can be 1).

[0193] The implementation process of the method provided in this application will be described below with reference to Figures 4 to 6. For ease of understanding, several possible application scenarios may be involved in using the method provided in this application. It should be noted that the following embodiments use a mobile phone as the first electronic device and a watch as the second electronic device as examples. For the implementation of other types of electronic devices, please refer to the implementation of message notification between a mobile phone and a watch. Other types of electronic devices can be, for example, a mobile phone and a wristband, a mobile phone and headphones, a tablet computer and headphones, etc., which will not be described again in this application.

[0194] For example, Figure 4 is a schematic diagram of a message notification method provided in an embodiment of this application. As shown in Figure 4, a communication link is established between the mobile phone and the watch, enabling them to coordinate message notifications. This communication link can be established through, but is not limited to, the following methods: Bluetooth, Wi-Fi, and GPS.

[0195] For example, based on the scenarios shown in Table 1 where the phone is unlocked and the watch is worn, or where the phone is locked and the watch is worn, this embodiment of the application can further configure more detailed intelligent message reminder logic by combining the recognition results of the collected user facial data. One possible intelligent message reminder logic is shown in Table 2 below:

[0196] Table 2

[0197] As can be seen from Table 2, based on the different recognition results of the user's facial data, two scenarios can be distinguished:

[0198] (1) The first scenario can also be understood as the scenario where only the owner of the phone uses the phone.

[0199] For example, when it is determined that the collected user's face data matches the owner's face (that is, the user's face is the owner's face) and no multiple faces are detected, it can be understood that only the owner is using the phone. In this case, the message intelligent reminder logic can keep the phone in the message notification mode configured by the system and remind the user, while the watch does not remind the user (this can also be referred to as "no reminder" in this application embodiment).

[0200] This avoids message interference caused by dual message notifications. Alternatively, while the watch doesn't send notifications, it can sync messages, which can be understood as a silent notification method, allowing users to actively check new messages via their watch. This satisfies various user needs for viewing new messages. These new messages can include, but are not limited to, the following types: conversation messages, service notifications, content information, and marketing campaigns.

[0201] In one alternative implementation, the mobile phone sends an indication message to the watch, which instructs the watch not to send message notifications. For example, the indication message may be sent to the watch along with a new message.

[0202] Optionally, the indication message may include, but is not limited to, the following conditions: no ringing; no vibration; no banner notification, or a banner notification but with the new message content hidden; no status bar icon; no breathing light; no automatic screen wake-up. For example, each condition can correspond to an indicator bit, and setting the indicator bit to "0" indicates that the corresponding reminder should not be executed. In addition, the indication message may also include the following condition: syncing messages in the notification bar.

[0203] Alternatively, the instruction message can include only the conditions that the watch needs to perform: syncing the message in the notification bar.

[0204] (2) The second scenario is any scenario other than the first scenario. This scenario may have the following possible recognition results:

[0205] 2-1) When it is determined that the collected user's facial data does not match the owner's face, that is, the user's face is not the owner's face, it can be understood that someone other than the owner is using the phone.

[0206] 2-2) When multiple faces or multiple pairs of eyes looking at the screen are identified from the collected user facial data, it can be understood that it is not only the phone owner who is using the phone; for example, the owner may be using the phone with family members. Furthermore, it is possible to detect whether multiple pairs of eyes are looking at the phone. Only when eyes are looking at the phone is it confirmed that an eye has been identified; otherwise, it is confirmed that no eye has been identified. For example, the phone can use gaze tracking technology to detect whether eyes are looking at the phone.

[0207] 2-3) If a face cannot be identified from the collected user facial data, it can be understood that it cannot be determined whether only the phone owner is using the phone. For example, if the collected user facial data is blurry or incomplete, it may lead to the inability to accurately identify the face. Another example is that the camera may be blocked by a hand, preventing the camera from collecting user facial data.

[0208] In this scenario, regarding message notification methods for the watch: the message reminder logic can be to display message reminders on the watch itself, for example, by displaying the message reminder interface shown in interface 401 of Figure 4. Additionally, the watch can also use ringing, vibration, or other methods to send message reminders. This way, when the phone detects that it's not a scenario where only the owner is using the phone, it can use the watch to send a reminder, reducing the possibility of the owner missing new messages. Similar to the first scenario, the phone can send an instruction message to the watch; the difference is that the instruction message can be used to instruct the watch to send message reminders. The specific conditions for the message reminder indicated in the instruction message can be determined based on pre-configuration; it can also be determined based on different watch states. For example, when the watch is in power-saving mode, the message reminder can only include vibration, thus reducing the watch's power consumption while still sending message reminders.

[0209] In addition, regarding the message notification methods for mobile phones:

[0210] One possible implementation is that the phone can maintain the system-configured message notification method for reminders. This means that the phone's message notification method can remain the same regardless of whether it's in the first or second scenario.

[0211] Another possible implementation is that the mobile phone can also use a message notification method pre-configured for the second scenario. This pre-configured message notification method can be one that meets at least one of the following conditions: no ringing, no vibration, no banner notification or banner notification but hiding the new message content, no status bar icon, no breathing light, and no automatic screen wake-up. This application does not limit the pre-configured message notification method. For example, a user can set the controls for multiple notification methods included in the message notification settings interface to a closed state, such as setting the control for indicating ringing to a closed state, and the control for indicating vibration to a closed state, etc.

[0212] For example, a message notification interface like interface 402A can be displayed on the mobile phone. The phone can use banner notifications and display new message content to notify users of messages. Additionally, the phone can also use ringtones, vibrations, and other methods to notify users of messages.

[0213] For example, a message notification interface as shown in interface 402B can be displayed on the mobile phone. The phone can also use a banner notification method that hides the new message content, in which case the banner notification only indicates that there is a new SMS message in the SMS application. It is understood that while displaying the message notification interface as shown in interface 402B, a ringing sound may or may not be activated; this application does not limit the specific combination of message notification methods.

[0214] Alternatively, for example, the phone could display an interface as shown in interface 402C. In this case, the phone would send message notifications without displaying banners, which can be understood as maintaining the original display interface when a new message is received. It's also possible that while displaying an interface as shown in interface 402C, the phone could choose not to ring or vibrate; for example, a silent notification method could be used, synchronizing new messages only in the notification bar. The user would only see the new message when actively checking the notification bar. This application does not limit the specific combination of message notification methods.

[0215] The logic of the intelligent message reminder described in Figure 4 can be configured in the message notification settings interface. Figure 5 is a schematic diagram of the settings interface of a message reminder method provided in this application embodiment. As shown in interface 501, the face recognition control 500A can be set to the enabled state in the settings interface. Alternatively, as shown in interface 502, the face recognition control 500B can be set to the enabled state in the next level settings interface of the message notification settings interface; wherein, interface 500A is the next level interface of the intelligent message reminder function, and more controls can be triggered to display through the intelligent message reminder function.

[0216] For example, in response to a user operation on either the "Learn More" control corresponding to the face recognition function included in interface 501 or the "Learn More" control corresponding to the face recognition function included in interface 502, the mobile phone can display interface 503. In interface 503, the user can set the message notification method on the mobile phone when it detects the second scenario as described in Table 2. As shown in interface 503, the message notification method on the mobile phone in the second scenario includes, but is not limited to, one or a combination of the following: no ringing, no vibration, banner notification but hiding new message content, no display of status bar icon, no display of breathing light, and no automatic screen wake-up.

[0217] Based on the content described in Figures 4 and 5 above, for the scenario in the second scenario where the mobile phone fails to recognize a face, the mobile phone can also combine other information to configure the intelligent message reminder logic. For example, other information could be the device distance between the mobile phone and the watch. The device distance can be determined by at least one piece of information such as the signal strength of wireless signals (e.g., Wi-Fi, Bluetooth, Wi-Fi, etc.) and ultra-wideband (UWB) technology. Based on the device distance between the mobile phone and the watch, the following intelligent message reminder logic can be configured, as shown in Table 3 below:

[0218] Table 3

[0219] As can be seen from Table 3, when the device distance is less than the preset distance threshold, it can be determined that the owner is using the phone. In this case, the message smart reminder logic can be to remind the phone but not the watch.

[0220] When the device distance is greater than or equal to a preset distance threshold, it can be determined that someone other than the owner is using the phone. In this case, the smart notification logic can be to not send notifications to the phone, but to send notifications to the watch. It should be noted that the watch must be worn.

[0221] In this way, by judging the distance between the phone and the watch, the flexibility of intelligent message reminders can be improved when the phone's camera cannot collect user facial data due to reasons such as being blocked, or when the quality of the face or image captured by the camera is poor due to lighting issues, or when the accuracy of matching the user's face with the template is low. This can protect the security of message content when the owner is not using the phone and reduce the omission of message reminders.

[0222] In some possible implementations, the mobile phone can periodically collect the user's facial data according to a preset schedule. Alternatively, the mobile phone can also collect the user's facial data when it receives a new message.

[0223] When a mobile phone periodically collects the user's facial data, it may detect a switch between a first scene and a second scene within the duration of a new message notification. For example, it might detect the first scene at one moment and the second scene at another. Based on this, another possible intelligent message notification logic is shown in Table 4 below:

[0224] Table 4

[0225] As can be seen from Table 4, during the new message notification process, when the phone detects a switch between different scenarios, it can also provide different message reminders based on the different switching scenarios.

[0226] For example, when changing from the first scenario to the second scenario, it can be understood as switching from the phone being used solely by the owner to being used by multiple users. In some possible implementations, in response to the change from the first scenario to the second scenario, the phone can change from displaying a banner notification and showing new message content to hiding the new message content. This allows the phone's message notification method to promptly match the current scenario. In some possible implementations, in response to the change from the first scenario to the second scenario, the phone can instruct the watch to use one of the following methods to provide message alerts, the specific method depending on the user's settings:

[0227] (1) The watch does not give a reminder.

[0228] (2) The watch will remind you if the preset conditions are met; otherwise, the watch will not remind you.

[0229] The preset conditions can be, for example, that the banner display duration has not reached the duration threshold, such as the banner display duration being 2 seconds (s) and the duration threshold being 4 seconds; or that the proportion of the banner display duration to the total banner display duration is less than the preset proportion, such as the total banner display duration being 5 seconds, the banner display duration being 2 seconds, the proportion of the banner display duration to the total banner display duration being 0.4, and the preset proportion being 0.8.

[0230] (3) Watch reminder.

[0231] Another example is the shift from the second scenario to the first scenario, which can be understood as a change from the phone being used by someone other than the owner to being used only by the owner. In some possible implementations, in response to the shift from the second scenario to the first scenario, the phone can switch from displaying a banner notification while hiding the new message content to displaying the new message content; this allows the phone's message notification method to promptly match the current scenario. Additionally, the phone can extend the banner notification duration, allowing the user to view the new message content more completely through the banner notification, thereby improving the efficiency of viewing new messages. In some possible implementations, in response to the shift from the second scenario to the first scenario, the phone can instruct the watch to provide a message reminder, thus reducing the probability of the owner missing new message notifications.

[0232] In the aforementioned scenarios, the mobile phone needs to use templates from the template library as the basis for determining whether the currently collected user's face is the owner's face.

[0233] In some possible embodiments, the mobile phone can pre-store a template library; wherein the template library may include M templates, and may include at most N templates. It is understood that when M is less than N, it indicates that the template library is not full; when M equals N, it indicates that the template library is full. M is greater than or equal to 0, and N is greater than or equal to 1.

[0234] In some possible scenarios, the template library does not distinguish between template types and can include a variety of possible templates.

[0235] In other possible scenarios, the template library can also classify templates by type, such as templates with occluded faces and templates without occluded faces. Based on this, different types of templates can be maintained separately. For example, the threshold for the number of templates with occluded faces can be N1 (e.g., N1≥2, or N1 can be 3), and the threshold for the number of templates without occluded faces can be N2 (e.g., N2≥1, or N2 can be 1).

[0236] Taking the classification of template types as an example, Figure 6 is a schematic diagram of the process for obtaining or updating the template library provided in an embodiment of this application. This process may include the following steps:

[0237] Step 601: Collect user facial data. For example, when the phone detects unlocking, it can trigger the camera to collect user facial data. For example, the camera in this embodiment can collect user facial data in low-power mode. The camera in this embodiment can be a screen-side camera primarily used for displaying content in the current state; details can be found in the preceding description and will not be repeated here.

[0238] Step 602: Is this the template registration stage? If yes, proceed to step 603; otherwise, continue monitoring.

[0239] For example, the template registration phase can be understood as the period within which the phone is displayed after unlocking, during which the template library can be updated. This first period can be a pre-set duration; alternatively, it can be a duration determined by a preset number of frames, such as less than 100 frames, for example, 5 frames. In this way, based on the high confidence that the user's face captured when the phone is just unlocked is the owner's face, adding or updating templates during this phase can improve the accuracy of the templates included in the template library.

[0240] In some possible implementations, the mobile phone can collect multiple frames of user face data during the template registration stage. The following processing can be performed on each frame of user face data, or the best user face data can be selected from multiple frames of user face data. This application does not limit this.

[0241] In some possible scenarios, the phone can perform the message notification method provided in this application embodiment after the template registration stage, or after the phone has been in the first display period after unlocking. For example, when the preset frame count is 5 frames, the phone will perform the message notification based on the message notification method provided in this application embodiment 5 frames after unlocking. It can be understood that based on the update of the template library during the template registration stage, the phone can match the collected user face data with the updated template library during the message notification processing, which can improve the accuracy of the matching results and thus ensure the accuracy of the message notification.

[0242] Step 603: Is the captured user face unobstructed? If yes, continue with steps 608-615; otherwise, proceed to steps 604-607. It can be understood that whether the captured user face is obstructed or not can be used to update different types of templates; these templates can include: unobstructed face templates and obstructed face templates.

[0243] Optionally, if the mobile phone detects that the collected user's facial data is unobstructed, it can update the unobstructed facial template based on that data. The unobstructed facial template can include one or more, and typically includes multiple templates.

[0244] Alternatively, if the mobile phone detects that the collected user's facial data is occluded, it can update the occluded face template based on that data. The unoccluded face template can include one or more, typically multiple templates; the occluded face template can also include one or more, typically one template.

[0245] (a) Updates to face templates that are obscured may include the following steps 604 to 607:

[0246] Step 604: Is face unlock enabled? If yes, proceed to step 607; otherwise, proceed to step 605.

[0247] Given the high difficulty of facial recognition in scenarios with occluded faces, this application typically uses user facial data collected by a camera in low-power mode for updating the owner's facial template, which has a lower confidence level than facial data collected by a normal camera; while facial unlocking typically uses facial data collected by a normal camera, which has a higher confidence level.

[0248] Therefore, considering that the collected user face data is occluded, when the unlock type is face unlock, due to the high confidence level, it can be used to update the template, such as adding a new template or replacing an old template, for example, by executing step 607.

[0249] When the unlock type is non-face unlock, other unlocking methods may be used due to face recognition failure. In this case, the confidence level is not high. Therefore, the template is only updated when the owner's face template library does not include a template that obscures the owner's face, i.e., a new template is added instead of replacing the old one. For example, steps 605 to 607 are executed. This ensures that the owner's face template library includes at least one template that obscures the owner's face, which is helpful for subsequent message notification judgment.

[0250] Step 605: Is it a non-face unlock? Non-face unlock could be, for example, fingerprint unlock or password unlock. If yes, proceed to step 606; otherwise, end the process.

[0251] Step 606: Does the template library contain any occluded face templates? If yes, proceed to step 607; otherwise, terminate the process. It can be understood that when the template library includes occluded face templates, no template replacement is needed in non-face unlock scenarios, thus ensuring template accuracy. Conversely, when the template library does not contain occluded face templates, adding them as templates in non-face unlock scenarios updates the library from one that does not contain occluded face templates to one that does, facilitating the subsequent processing of the message notification method described in this embodiment.

[0252] In addition, since only one occluded face template is usually needed in the template library, the probability of not having an occluded face template stored in the template library can be reduced through the processing in steps 605 to 607 above.

[0253] Step 607: Update the face template with obscured features.

[0254] Optionally, based on the high confidence level of face unlock, the collected user face data can be directly updated to an occluded face template. For example, when the threshold for the number of occluded face templates is one, if an occluded face template is already stored in the template library, the user face data can replace the existing occluded face template; if no occluded face template is stored in the template library, the user face data can be added as an occluded face template.

[0255] Alternatively, based on the low confidence level of non-face unlock or non-face unlock, it is only used to update to an occluded face template when the phone does not have an occluded face template stored; in other words, if the phone has an occluded face template stored, the stored occluded face template will not be replaced.

[0256] (ii) Updating the unobstructed face template may include the following steps 608 to 615:

[0257] Step 608: Is it a biometric unlock? If yes, continue to step 609; otherwise, execution can end. Alternatively, in non-biometric unlock scenarios, determine if the template library contains no occluded face templates. If empty, add the collected user face data as an occluded face template, ensuring the template library contains at least one occluded face template. Furthermore, since the template library typically contains multiple occluded face templates, the probability of scenarios without occluded face templates is low. However, in non-biometric unlock scenarios, adding templates by detecting scenarios without occluded face templates can further reduce the probability of the template library not containing any occluded face templates. Biometric unlock can include, but is not limited to: face unlock, fingerprint unlock, palm print unlock, iris unlock, etc.

[0258] It is understandable that unlocking types have priorities, for example, face unlock has the priority > fingerprint unlock has the priority > password unlock has the priority.

[0259] Given the high confidence level of biometric unlocking methods such as facial recognition or fingerprint unlocking, when the unlock type is biometric, the collected user facial data can be used to update the template; when the unlock type is non-biometric, the collected user facial data can be excluded from template replacement. In this way, by judging the unlock type, only when the unlock type meets the conditions will the data be used to update the template library, thereby improving the confidence level of the registered templates.

[0260] Alternatively, step 608 can simply determine whether the unlock type is face unlock. This way, the template library update is only performed when the unlock type is face unlock, further ensuring the confidence level of registered or updated templates.

[0261] Step 609: Does it match the template? If yes, proceed to step 610; otherwise, proceed to step 612.

[0262] Optionally, when the collected user facial data matches the template, the face can be identified as the owner of the device. Based on this, the template can be updated using the latest collected owner's face.

[0263] Alternatively, if the collected user's facial data does not match the template, the collected face may not be the owner's face, or the matching may fail due to factors such as the collection process. Based on this, further judgment can be made in step 612.

[0264] Step 610: Update to a template; or select the template with the highest similarity among multiple templates and replace it.

[0265] Optionally, when the template library includes a threshold number of unobstructed face templates of one, the user's face data can be directly used to replace the stored unobstructed face template. Alternatively, when no unobstructed face templates are stored, the user's face data can be added as a new unobstructed face template.

[0266] Alternatively, when the template library includes a threshold number of unobstructed face templates, and the user's face data matches at least one of these templates, the user can be identified as the device owner. Considering that the collected user face data is the most up-to-date data for the device owner's face, a similarity comparison can be performed between the collected user face data and multiple unobstructed face templates. Unobstructed face templates with higher similarity have smaller differences from the collected user face data, which can be interpreted as having the most similar angle, or, if multiple device owners are included, indicating the same device owner. Unobstructed face templates with lower similarity have larger differences from the collected user face data, which can be interpreted as having the largest difference in angle, or, if multiple device owners are included, indicating different device owners. Therefore, the collected user face data can replace the unobstructed face template with the highest similarity. This allows for iterative selection of similar unobstructed face templates using the collected user face data, reducing redundancy in scenarios where diversity among multiple unobstructed face templates is maintained. For example, if the collected user face data is a front view, the user face data can replace the unobstructed face template of the front view.

[0267] Step 611: Increase the number of times this template is used by 1, and / or decrease the number of times other templates are used by 1.

[0268] It is understandable that after replacing the collected user facial data with a template, the number of times the template is used can be counted. Optionally, the number of times the template is used can be increased, or the number of times other templates are used can be decreased, or the number of times the template is used can be increased while the number of times other templates are used is decreased. This application does not limit the specific statistical method.

[0269] Therefore, by counting the number of times a template is used, we can also identify the template with the highest similarity to the current user's face, which can then be used as a method for updating templates. It can be understood that a higher usage frequency indicates a higher similarity to the current user's face, and vice versa.

[0270] Step 612: Is the template library full? If yes, proceed to step 613; otherwise, proceed to step 614.

[0271] It's understandable that a mobile phone can pre-configure a threshold for the number of unobstructed face templates, for example, three. When it detects that three unobstructed face templates are stored in the phone, it can be determined that the template library is full; in other words, when it detects that fewer than three unobstructed face templates are stored in the phone, it can be determined that the template library is not full.

[0272] Step 613: Select the unobstructed face template with the lowest usage frequency among multiple templates and replace it.

[0273] For example, based on steps such as 611, the number of times the unobstructed face template is used can be counted. The unobstructed face template with the fewest uses can be understood as the template with the greatest difference from the current user's face. Therefore, by replacing the unobstructed face template with the fewest uses, the matching degree between the template and the current user's face can be improved, thereby ensuring the accuracy of message notifications.

[0274] Step 614: Add as a new template.

[0275] When neither the user's facial data nor the template matches, the confidence level of unlocking based on biometrics is relatively high, and the template library can also be updated based on the user's facial data. Optionally, when the template library is full, infrequently used or never used unobstructed facial templates can be replaced. Alternatively, when the template library is not full, new unobstructed facial templates can be directly added.

[0276] Step 615: Increase the usage count of this template by 1, and / or decrease the usage count of other templates by 1. This step is explained in the description of Step 611 and will not be repeated here.

[0277] It should be noted that Figure 6 is only one possible implementation of the update template library provided in the embodiments of this application, and this application does not limit the above implementation.

[0278] For example, the template library may not differentiate between different types of user face templates.

[0279] For example, when the template library is not full, it is not necessary to match the user's facial data with the template. In biometric unlocking scenarios, the new template can be added directly. Or, for example, Figure 6 uses a threshold of 1 for the number of occluded face templates as an example. The threshold for the number of occluded face templates can also be 2 or more. In this case, the method of updating occluded face templates can refer to the method of updating unoccluded face templates. For example, when the template library is full, the user's facial data can replace the template with the least frequent use among multiple occluded face templates.

[0280] For example, in scenarios where the template library does not differentiate between user face templates, when the unlock type is biometric unlock, updating the template library based on the collected user face data can include any of the following possible scenarios:

[0281] A) If the template library contains a threshold of 1 template, update the user's facial data with the template. Optionally, if the template library contains templates, replace the existing template with the user's facial data. Alternatively, if the template library does not contain templates, add the user's facial data as a new template.

[0282] B) The template library includes a threshold number of templates greater than 1. When a user's facial data matches any template in the template library, the user's facial data replaces the first template. The first template is the one in the template library with the highest similarity to the user's facial data.

[0283] For example, the template library may include multiple templates from different angles for the same user, such as the user's front view, left view, right view, etc.

[0284] Another example is that the template library may also include templates from different owners.

[0285] In this way, when matching, the template with the highest similarity to the user's facial data can be replaced, thereby updating similar templates, reducing redundancy of the same type of templates, and improving diversity.

[0286] For example, if the collected user's facial data is a frontal view of the device owner, then the frontal view of that device owner in the template library can be replaced, allowing the frontal view template to better match the device owner's face in the current state. In other words, updates can be performed separately according to different template types.

[0287] C) The template library includes a threshold number of templates greater than 1. When the user's face data does not match any of the templates in the template library and the template library is full, the user's face data is replaced with a second template. The second template is the one used the least in the template library.

[0288] It is understandable that when the template library can include multiple templates and is full, the confidence level of the user's facial data collected at this time is high, based on the unlock type being biometric unlock.

[0289] Therefore, when a mismatch is detected between the collected user facial data and the template, the collected user facial data can replace the template with the least used one. This allows for timely iteration of potentially outdated templates, thereby improving the accuracy of message notifications.

[0290] D) The template library includes a threshold of template quantity greater than 1. When the template library is not full, newly added user face data will be used as a new template.

[0291] In this scenario, when the number of templates in the template library is insufficient, the electronic device can bypass the need to match the user's facial data with the template library. Since the unlock type is biometric unlock, the confidence level that the collected user facial data belongs to the device owner is high. Therefore, the collected user facial data can be directly updated with a new template, increasing the number of templates and ensuring that the templates better match the current user's face.

[0292] In another possible embodiment, Figure 7 is a schematic diagram of another scenario of a message notification method provided by an embodiment of this application. As shown in interface 701 of Figure 7, the mobile phone can also provide the user with a control 700A for protecting artificial intelligence (AI) information. Alternatively, as shown in interface 702 of Figure 7, the AI ​​information protection control 700B can also be set in the next level interface of message intelligent notification, and users can access interface 702 through the more information controls corresponding to the message intelligent notification function.

[0293] When a phone detects that the AI ​​information protection feature is enabled, it can hide notification content and trigger message content protection if it detects a face other than the owner's, multiple pairs of eyes looking at the screen, or no face is recognized. Alternatively, when the phone detects that the AI ​​information protection feature is enabled, it can display notification content when it detects the owner's face and a pair of eyes. In this way, AI-powered message content protection can safeguard the security of message content.

[0294] Based on the scenario shown in Figure 7, the AI ​​information protection function can also be used as a reference to configure more detailed intelligent message reminder logic. For example, please refer to Table 5 below:

[0295] Table 5

[0296] As can be seen from Table 5, AI-based information protection functions can include a variety of possible scenarios:

[0297] Scenario A: When a banner notification is detected on the phone and a new message is displayed, it can be understood that the phone owner is using the phone and only one pair of eyes are detected. In other words, it can be determined that only the phone owner is using the phone. Therefore, the logic for message smart reminders in this case is that the watch can choose not to send a reminder.

[0298] Scenario B: When a banner notification is detected on the phone but the new message content is hidden, this can be interpreted as someone other than the phone owner using the phone, or multiple pairs of eyes looking at the screen being detected. In other words, it can be determined that not only the phone owner is using the phone, or someone other than the phone owner is using the phone. In this case, the message notification logic can be adapted to remind the user via a smartwatch. This reduces the probability of missed message notifications.

[0299] Scenario C: When a banner notification is detected on the phone and new message content is displayed, the new message content is changed to be hidden. This can be understood as a change from only the phone owner using the phone to multiple users using the phone. In this case, the message intelligent notification logic can be one of the following methods, which can be determined according to the user's settings:

[0300] (1) The watch does not give a reminder.

[0301] (2) The watch will remind you if the preset conditions are met; otherwise, the watch will not remind you.

[0302] The preset conditions can be, for example, that the banner display duration has not reached the duration threshold, such as the banner display duration being 2 seconds (s) and the duration threshold being 4 seconds; or that the proportion of the banner display duration to the total banner display duration is less than the preset proportion, such as the total banner display duration being 5 seconds, the banner display duration being 2 seconds, the proportion of the banner display duration to the total banner display duration being 0.4, and the preset proportion being 0.8.

[0303] (3) Watch reminder.

[0304] Scenario D: When a banner notification is detected on the phone but the new message content is hidden, the notification is changed to display the new message content. This can be understood as a change from the phone being used by multiple users to being used only by the phone owner. The watch can provide a reminder when the banner notification hides the new message content, and the watch can maintain this reminder. Additionally, it should be noted that changing the banner notification from hiding to displaying the new message content can extend the display time of the new message content. For example, if the total banner display time is 5 seconds, and hiding the new message content has already taken 2 seconds, the remaining banner display time, originally 3 seconds, can be extended to 5 seconds when the banner notification is changed to display, meaning the actual total banner display time is 7 seconds.

[0305] As illustrated in Figure 7, the mobile phone can reuse the output of the AI ​​information protection function for message notifications. Based on the message intelligent reminder logic shown in Table 5, different message notification methods can be determined according to the output of different AI information protection functions. This improves the flexibility of message intelligent reminders, enabling the protection of message content when the phone is not in use and reducing missed message notifications.

[0306] Based on the above descriptions of various scenarios, the message notification method provided in this application embodiment can expand the application scenarios for intelligent message notifications between mobile phones and watches, thereby protecting the privacy of information when the owner is not using the mobile phone and reducing the probability of missed message notifications.

[0307] Based on the same or similar inventive concept as described above, Figure 8 is a flowchart illustrating a message notification method provided in an embodiment of this application. This method can be applied to a first electronic device; wherein, the first electronic device can be, for example, the mobile phone described in the foregoing embodiments. The process of this method may include the following steps:

[0308] Step 801: Collect the face data of the first user. For example, the face data of the first user can be detected by the first electronic device after a first period of time following the unlocking and display.

[0309] Step 802: When the reminder conditions are met, instruct the second electronic device to send a message reminder when a new message is received; wherein the reminder conditions include at least one of the following: the first user's face data fails to match the device owner's face template data, multiple faces or multiple pairs of eyes looking at the screen are identified from the first user's face data, or no face is identified from the first user's face data, and the second electronic device is a wearable device bound to the first electronic device. The second electronic device may, for example, be a watch as described in the preceding embodiments.

[0310] The specific implementation process of steps 801 and 802 can be found in the foregoing embodiments, and will not be repeated in this application.

[0311] Based on the above embodiments, this application also provides an electronic device, which includes multiple functional modules; the multiple functional modules interact to realize the functions performed by the electronic device in the methods described in the embodiments of this application. The multiple functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules can be arbitrarily combined or divided based on specific implementations. For example, steps 601 to 615 are performed by the mobile phone in the embodiment shown in FIG. 6. Alternatively, steps 801 to 802 are performed by the first electronic device in the embodiment shown in FIG. 8.

[0312] Based on the above embodiments, this application also provides an electronic device, which includes at least one processor and at least one memory, wherein the at least one memory stores computer program instructions. When the electronic device is running, the at least one processor performs the functions performed by the electronic device in the various methods described in the embodiments of this application. For example, steps 601 to 615 performed by the mobile phone in the embodiment shown in FIG. 6. Alternatively, steps 801 to 802 performed by the first electronic device in the embodiment shown in FIG. 8.

[0313] Based on the above embodiments, this application can also provide a message notification system, which may include a first electronic device and at least one second electronic device. The first electronic device may be, for example, a mobile phone as described in the foregoing embodiments, and the second electronic device may be, for example, a watch as described in the foregoing embodiments.

[0314] Based on the above embodiments, this application also provides a computer program product, which includes a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods described in the embodiments of this application.

[0315] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, causes the computer to perform the methods described in the embodiments of this application.

[0316] Based on the above embodiments, this application also provides a chip for reading computer programs stored in a memory to implement the methods described in the embodiments of this application.

[0317] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the methods described in the embodiments of this application. In one possible implementation, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete devices. Those skilled in the art will understand that the embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0318] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0319] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0320] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0321] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A message alerting method, characterized by, The method is applied to a first electronic device, and comprises: collecting first user face data; when it is determined that a reminding condition is met, instructing a second electronic device to perform message reminding when there is a new message; wherein the reminding condition comprises at least one of the following: the first user face data fails to match a master face template data, multiple faces are identified from the first user face data or multiple pairs of eyes that are gazing at a screen are identified from the first user face data, no face is identified from the first user face data, and the second electronic device is a wearable device bound to the first electronic device.

2. The method of claim 1, wherein, The method further comprises: when it is determined that the reminding condition is not met, determining to instruct the second electronic device not to perform message reminding.

3. The method of claim 1, wherein, The method further comprises: performing message notification on the first electronic device in a first manner, wherein the first manner is a default message notification manner configured for the first electronic device; or performing message notification on the first electronic device in a second manner; wherein the second manner is a message notification manner configured for the first electronic device when it is determined that the reminding condition is met.

4. The method of claim 3, wherein, The second manner is a message notification manner that meets at least one of the following conditions: no ringing is performed; no vibration is performed; no banner notification is performed, or banner notification is performed but the content of the new message is hidden; no status bar icon is displayed; no breathing light is displayed; no automatic screen turning on is performed.

5. The method according to any one of claims 1 to 4, characterized in that, The collecting of the first user face data comprises: periodically collecting the first user face data according to a preset period.

6. The method of claim 5, wherein, before the determining that the reminding condition is met, the method further comprises: determining that a first time does not meet the reminding condition, performing banner notification on the first electronic device and displaying the content of the new message, the first time being a time when the new message is received; the determining that the reminding condition is met comprises: determining that a second time meets the reminding condition; the method further comprises: no longer performing banner notification on the first electronic device, or performing banner notification but hiding the content of the new message; wherein a difference between the second time and the first time is less than a time threshold, or a proportion of the difference in a preset time length is less than a proportion threshold, the preset time length being used to indicate a total time length of the new message performing banner notification.

7. The method of claim 5, wherein, the determining that the reminding condition is met comprises: determining that a second time meets the reminding condition; the method further comprises: performing banner notification on the first electronic device but hiding the content of the new message; determining that a third time does not meet the reminding condition, performing banner notification on the first electronic device and displaying the content of the new message, and prolonging a display time length of the banner notification, the third time being later than the second time.

8. The method according to any one of claims 1 to 7, characterized in that, when the reminding condition comprises that no face is identified from the first user face data; the reminding condition further comprises: a device distance between the first electronic device and the second electronic device is greater than or equal to a preset distance threshold.

9. The method according to any one of claims 1 to 8, characterized in that, before the collecting of the first user face data, the method further comprises: detecting that a first time length after display after unlocking is reached.

10. The method of claim 9, wherein, the method further comprises: When it is detected that the first time length is within, the second user face data is collected, and the host face template library is updated; wherein, the host face template library includes M host face template data, and M is less than or equal to N, and N is used to indicate the number threshold of host face template data allowed to be included in the host face template library.

11. The method of claim 10, wherein, The unlocking is a biological feature unlocking. The second user face data is collected, and the host face template library is updated. N is equal to 1, the second user face data is updated as host face template data; or, N is greater than 1, when the second user face data matches any host face template data in the M host face template data, the second user face data replaces the first host face template data; wherein, the first host face template data is the highest similarity in the host face template library with the second user face data; or, N is greater than 1, when the second user face data does not match the M host face template data, and M is equal to N, the second user face data replaces the second host face template data; wherein, the second host face template data is the lowest use frequency in the host face template library; or, N is greater than 1, when M is less than N, the second user face data is added as host face template data.

12. The method of claim 10, wherein, The unlocking is a biological feature unlocking. Before the second user face data is collected, and the host face template library is updated, the method further includes: The second user face data is determined as unobstructed user face data; wherein, the host face template library includes M1 unobstructed host face template data, and M1 is less than or equal to N1, and N1 is used to indicate the number threshold of unobstructed host face template data allowed to be included in the host face template library; The second user face data is collected, and the host face template library is updated. N1 is equal to 1, the second user face data is updated as unobstructed host face template data; or, N1 is greater than 1, when the second user face data matches any unobstructed host face template data in the M1 unobstructed host face template data, the second user face data replaces the first unobstructed host face template data; wherein, the first unobstructed host face template data is the highest similarity in the host face template library with the second user face data; or, N1 is greater than 1, when the second user face data does not match the M1 unobstructed host face template data, and M1 is equal to N1, the second user face data replaces the second unobstructed host face template data; wherein, the second unobstructed host face template data is the lowest use frequency in the unobstructed host face template data included in the host face template library; or, The N1 is greater than 1, when the M1 is less than the N1, the second user face data is added as the non-occluded machine owner face template data.

13. The method of claim 10, wherein, Before the machine owner face template library is updated according to the collected second user face data, the method further comprises: determining that the second user face data is the occluded user face data; wherein the machine owner face template library comprises M2 occluded machine owner face template data, the M2 is less than or equal to N2, and the N2 is used to indicate a quantity threshold of the occluded machine owner face template data allowed to be included in the machine owner face template library; updating the machine owner face template library according to the collected second user face data comprises: the N2 is equal to 1, and the unlocking is the face unlocking, the second user face data is updated as the occluded machine owner face template data; or, the N2 is equal to 1, and the unlocking is the non-face unlocking, when the M2 is less than the N2, the second user face data is added as the occluded machine owner face template data.

14. A message alerting method characterized by, Applied to a first electronic device, comprising: receiving a new message; when detecting that the new message is notified in a first mode, instructing a second electronic device to perform message reminding; wherein the first mode comprises performing banner notification but hiding new message content.

15. The method of claim 14, wherein, The method further comprises: when detecting that the new message is notified in a second mode, instructing the second electronic device not to perform message reminding; wherein the second mode comprises performing banner notification and displaying new message content.

16. The method according to claim 14 or 15, characterized in that The new message is received at a first time; Before the detecting that the new message is notified in the first mode, the method further comprises: detecting that the new message is notified in the second mode at the first time; The detecting that the new message is notified in the first mode comprises: detecting that the new message is notified in the first mode at a second time; wherein a difference between the second time and the first time is less than a time threshold, or a proportion of the difference in a preset time length is less than a proportion threshold, and the preset time length is used to indicate a total time length of banner notification of new messages.

17. An electronic device, comprising: The at least one processor is coupled with the at least one memory, and is used to read a computer program stored in the at least one memory, so as to execute the method in any one of claims 1 to 13, or execute the method in any one of claims 14 to 16.

18. A computer-readable storage medium, characterized in that, The computer readable storage medium stores instructions, when the instructions are run on a computer, causing the computer to execute the method in any one of claims 1 to 13, or causing the computer to execute the method in any one of claims 14 to 16.

19. A computer program product comprising instructions, characterized in that, When the computer program product is run on a computer, causing the computer to execute the method in any one of claims 1 to 13, or causing the computer to execute the method in any one of claims 14 to 16.

Images