Incoming call reminding system, method and electronic device

Abstract

The application provides a call reminding system, method and electronic device, relates to the technical field of terminals, and improves the problem that multiple devices indiscriminately perform call reminding for the same call request. The specific scheme is as follows: in the case that the first device and the one or more than two second devices meet a first condition, the first device receives a first call request, wherein the first condition includes an off-screen state; in response to the first call request, a third device in the one or more than two second devices and the first device perform call reminding, and a fourth device in the one or more than two second devices, except the third device, does not perform vibration and / or ringing reminding, wherein the third device is a wearable device and the third device is in a wearing state.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to an incoming call reminder system, method and electronic device. Background Technology

[0002] Currently, users own an increasing number and variety of electronic devices; for example, a user may own a smartphone, tablet, and laptop simultaneously. In some embodiments, a trust network can be established among multiple electronic devices belonging to the same user. This allows a single electronic device to identify events requiring notification, such as an incoming call on a smartphone, prompting all devices in the trust network to collaboratively issue a call notification. This improves the problem of users missing call notifications when they are not using their smartphones.

[0003] However, in real-world use, when all devices indiscriminately send call alerts, users are forced to check each device sequentially to determine if each is sending an alert for the same call. Clearly, the more electronic devices in a trusted network, the lower the efficiency of human-computer interaction in handling call alerts. Summary of the Invention

[0004] This application provides a call reminder system, method, and electronic device to solve the problem of multiple devices indiscriminately reminding each other of incoming calls in a collaborative call reminder scenario, thereby improving the intelligence level of the devices.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] In a first aspect, embodiments of this application provide an incoming call reminder system, the system including a first device, and the system further including one or more second devices. When the first device and the one or more second devices meet a first condition, the first device receives a first incoming call request, wherein the first condition includes a screen-off state; in response to the first incoming call request, a third device among the one or more second devices and the first device provide an incoming call reminder, and a fourth device among the one or more second devices other than the third device does not provide a vibration and / or ringing reminder, wherein the third device is a wearable device and the third device is in a wearable state, and the incoming call reminder method pre-configured on the fourth device is vibration and / or ringing.

[0007] In the above embodiments, both the first and second devices are in a screen-off state, indicating a scenario where no devices in the system are in use. When any device in the system is unattended, if the first device receives a first incoming call request, both the first device itself and the third device worn by the user will issue a call notification. Other devices in the system will not vibrate or ring. This not only ensures timely notification to the user of the first incoming call request but also avoids indiscriminate notifications from all devices, preventing excessive notifications from affecting the user and enhancing the intelligence of the devices.

[0008] In some embodiments, when the first device meets the second condition, the first device receives the second incoming call request, the second condition including: detecting user facial features, receiving user operation, or being in a screen-on state; when the incoming call reminder method pre-configured by the first device is vibration and / or ringing, in response to the second incoming call request, the first device provides a reminder according to the corresponding incoming call reminder method, and the one or more second devices display the incoming call notification and do not provide vibration and / or ringing reminders.

[0009] In some embodiments, when the first device meets the second condition, the first device receives a third incoming call request, the second condition including: detecting user facial features, receiving user operation, or being in a screen-on state; when the incoming call reminder mode pre-configured by the first device is a silent notification, in response to the third incoming call request, a fifth device among the one or more second devices provides an incoming call reminder; the incoming call reminder mode of the fifth device is ringing and / or vibrating.

[0010] In the above embodiments, the scenario is where the first device meets the second condition, indicating that the user is using the first device. In this scenario, when the first device receives an incoming call request, such as a second or third incoming call request, the first device is primarily responsible for providing call reminders, while the second device provides supplementary reminders, avoiding indiscriminate reminders from a large number of devices.

[0011] For example, if the first device is configured to vibrate and / or ring for incoming call notifications, then the first device will vibrate and / or ring. Regardless of whether the second device is configured to vibrate and / or ring, it will only display the incoming call notification and will not vibrate and / or ring. As another example, if the first device is configured to silent notification, it will display a silent notification. The fifth device among the second devices, configured to ring and / or vibrate, will then perform the vibration and / or ring. This ensures that when the first device receives an incoming call request, at least one device in the system can alert the user to the call request via vibration and / or ring, while preventing all devices in the system from vibrating and / or ringing indiscriminately. Users do not need to check all devices sequentially to determine if each electronic device is alerting for the same incoming call, thus improving the efficiency of human-computer interaction in handling incoming calls.

[0012] In some embodiments, when there are multiple fifth devices, the fifth device among one or more second devices providing call alerts includes: the sixth device with the highest priority among the multiple fifth devices providing call alerts.

[0013] In the above embodiments, prioritization is used to further reduce the number of devices sending call alerts. This ensures timely reminders to users of incoming call requests while avoiding excessive reminders that could negatively impact the user's human-computer interaction efficiency in handling call alerts.

[0014] In some embodiments, before the fifth device sends an incoming call notification, the fifth device determines that a third condition is not met; wherein the third condition includes any one of the following: running a first application in the foreground, the first application being an application with higher priority than the call service; executing a first task, the first task including a collaborative task and a call task; activating a first function, the first function being used to instruct to block all incoming call requests during a first time period; and the first device being included in a first list preset in the fifth device.

[0015] In some embodiments, when the first device satisfies the first condition and the seventh device among the one or more second devices satisfies the second condition, the first device receives a fourth incoming call request, the second condition including: detecting user facial features, receiving user operation, or being in a screen-on state; in response to the fourth incoming call request, the first device and the seventh device provide an incoming call reminder.

[0016] In the above embodiments, the first device satisfies the first condition, and the seventh device in the second device satisfies the second condition. This can indicate a scenario where the user is not using the first device but is using the seventh device. In this scenario, when the first device receives an incoming call request, it can enable the seventh device to provide an incoming call reminder, ensuring that the user is promptly reminded to pay attention to the incoming call request.

[0017] In some embodiments, when the first device satisfies the first condition and the seventh device among the one or more second devices satisfies the second condition, the first device receives a fourth incoming call request, the second condition including: detecting user facial features, receiving user operation, or being in a screen-on state; in response to the fourth incoming call request, the first device, the third device, and the seventh device provide an incoming call reminder.

[0018] In some embodiments, in response to the fourth incoming call request, an eighth device among the one or more second devices, other than the seventh and third devices, displays an incoming call notification.

[0019] In some embodiments, the third device is a smartwatch or Bluetooth headset.

[0020] In some embodiments, when the first device satisfies the first condition and the seventh device among one or more second devices satisfies the second condition, the first device receives a fourth incoming call request. The second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state. In response to the fourth incoming call request, the first device provides an incoming call reminder. When the priority of the seventh device is higher than that of the third device, the first device sends first information to the seventh device, the first information being used to instruct the seventh device to provide an incoming call reminder for the fourth incoming call request. Under the fourth condition, the seventh device sends first response information to the first device, indicating that it will refuse to provide an incoming call reminder for the fourth incoming call request. The call reminder occurs when: a first application is running in the foreground of the seventh device, satisfying the fourth condition, wherein the first application has a higher priority than the call service; the seventh device performs a first task, satisfying the fourth condition, wherein the first task includes a collaborative task and a call task; the seventh device activates a first function, satisfying the fourth condition, wherein the first function is used to indicate that all incoming call requests are blocked within a first time period; the seventh device includes the first device in a first list, satisfying the fourth condition; the first device responds to the first response information by sending a second message to the third device, wherein the second message is used to instruct the third device to provide a call reminder for the fourth incoming call request; and the third device provides the call reminder.

[0021] Secondly, an incoming call reminder method provided in this application embodiment is applied to a first device, the first device being part of the system provided in the first aspect. The method includes: the first device receiving a first incoming call request; when the first device and one or more second devices all meet a first condition, the first device sending third information to a third device among the one or more second devices to instruct the third device to provide an incoming call reminder for the first incoming call request, wherein the third device is a wearable device and the third device is in a wearable state, and the first condition includes a screen-off state; the first device sending fourth information to a fourth device to instruct the fourth device to display an incoming call notification and not to provide vibration and / or ringing reminders, wherein the fourth device is a device other than the third device among the one or more second devices, and the incoming call reminder method pre-configured in the fourth device is vibration and / or ringing.

[0022] In some embodiments, the method further includes: the first device receiving the second incoming call request; when the first device meets a second condition and the pre-configured incoming call alert method is vibration and / or ringing, the first device sends fourth information to the second device to instruct the second device to display an incoming call notification and not to provide vibration and / or ringing alerts; the second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state; when the pre-configured incoming call alert method is vibration and / or ringing, the first device responds to the second incoming call request by using the vibration and / or ringing to provide an alert.

[0023] In some embodiments, the method further includes: the first device receiving the third incoming call request; when the first device meets a second condition and the pre-configured incoming call reminder mode is silent notification, sending fifth information to a fifth device among the one or more second devices, the fifth information being used to instruct the fifth device to provide an incoming call reminder, the pre-configured incoming call reminder mode of the fifth device being ringing and / or vibrating, the second condition including: detecting user facial features, receiving user operation, or being in a screen-on state.

[0024] In some embodiments, when there are multiple fifth devices, sending the fifth information to one or more second devices includes: the first device sending the fifth information to the sixth device with the highest priority among the multiple fifth devices.

[0025] In some embodiments, the method further includes: the first device receiving a fourth incoming call request; and, if the first device satisfies the first condition and the seventh device among the one or more second devices satisfies the second condition, sending first information to the seventh device to instruct the seventh device to provide an incoming call reminder, wherein the second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state.

[0026] In some embodiments, the method further includes: the first device receiving first response information sent by the seventh device, the first response information being used to instruct the seventh device to refuse to provide call reminder for the fourth call request; the first device sending second information to the third device, the second information being used to instruct the third device to provide call reminder for the fourth call request.

[0027] Thirdly, an electronic device is provided in the embodiments of this application. The electronic device includes one or more processors and a memory. The memory is coupled to the processor and is used to store computer program code, which includes computer instructions. When one or more processors execute the computer instructions, the one or more processors are used to: receive a first incoming call request; when the electronic device and the one or more second devices all meet a first condition, send third information to a third device among the one or more second devices to instruct the third device to provide an incoming call reminder for the first incoming call request, wherein the third device is a wearable device and is in a wearable state, and the first condition includes a screen-off state; send fourth information to a fourth device to instruct the fourth device to display an incoming call notification, wherein the fourth device is a device other than the third device among the one or more second devices, and the incoming call reminder method pre-configured in the fourth device is vibration and / or ringing. In some embodiments, the one or more processors are configured to: receive the second incoming call request; and, if the electronic device meets a second condition and the pre-configured incoming call alert method is vibration and / or ringing, send fourth information to the second device to instruct the second device to display an incoming call notification; the second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state; and, in response to the second incoming call request, using vibration and / or ringing to provide an alert when the pre-configured incoming call alert method is vibration and / or ringing.

[0028] In some embodiments, the one or more processors are configured to: receive the third incoming call request; and when the electronic device meets the second condition and the pre-configured incoming call reminder method is silent notification, send fifth information to the fifth device among the one or more second devices, the fifth information being used to instruct the fifth device to provide an incoming call reminder, the pre-configured incoming call reminder method of the fifth device being ringing and / or vibrating, the second condition including: detecting user facial features, receiving user operation, or being in a screen-on state.

[0029] In some embodiments, when there are multiple fifth devices, the one or more processors are configured to: send the fifth information to the sixth device with the highest priority among the multiple fifth devices.

[0030] In some embodiments, the one or more processors are configured to: receive a fourth incoming call request; and, if the electronic device satisfies the first condition and the seventh device among the one or more second devices satisfies the second condition, send first information to the seventh device to instruct the seventh device to provide an incoming call reminder, wherein the second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state.

[0031] In some embodiments, the one or more processors are configured to: receive first response information sent by the seventh device, the first response information being used to instruct the seventh device to refuse to provide call reminder for the fourth call request; and send second information to the third device, the second information being used to instruct the third device to provide call reminder for the fourth call request.

[0032] Fourthly, embodiments of this application provide a computer storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the methods described in the second aspect and its possible embodiments.

[0033] Fifthly, this application provides a computer program product that, when run on the aforementioned electronic device, causes the electronic device to perform the methods described in the second aspect and its possible embodiments.

[0034] Understandably, the electronic devices, computer-readable storage media, and computer program products provided in the above aspects are all applied to the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0035] Figure 1 A schematic diagram of the structure of a collaborative system provided in an embodiment of this application;

[0036] Figure 2A One of the example diagrams of the hardware and software structure of the electronic device provided in the embodiments of this application;

[0037] Figure 2B A second example diagram illustrating the hardware and software structure of the electronic device provided in this application embodiment;

[0038] Figure 2C The third example diagram of the hardware and software structure of the electronic device provided in the embodiments of this application;

[0039] Figure 3 Example diagrams of mobile phones and PCs provided in embodiments of this application;

[0040] Figure 4 This is one of the signaling interaction diagrams corresponding to the method provided in the embodiments of this application;

[0041] Figure 5 This is the second signaling interaction diagram corresponding to the method provided in the embodiments of this application;

[0042] Figure 6A This is one of the scenario example diagrams provided in the embodiments of this application;

[0043] Figure 6B This is the second example diagram of a scenario provided in the embodiments of this application;

[0044] Figure 7 The third example diagram of a scenario provided in the embodiments of this application;

[0045] Figure 8 The fourth example diagram of a scenario provided in the embodiments of this application;

[0046] Figure 9 This is a schematic diagram of the composition of a chip system provided in an embodiment of this application. Detailed Implementation

[0047] This application provides a call reminder method, applicable to, for example, call reminder... Figure 1 The collaborative system shown is also known as an incoming call reminder system. This collaborative system includes device 1 (referred to as the first device) and at least one device 2 (referred to as the second device). Device 1 and device 2 can perform near-field communication and, based on this near-field communication, collaboratively implement various types of services, such as call services, screen mirroring services, and remote control services.

[0048] For example, the device 1 described above can be the initiator of the collaboration. For instance, device 1 can be an intelligent electronic device such as a mobile phone, tablet, handheld computer, PC, cellular phone, personal digital assistant (PDA), wearable device (such as a smartwatch), smart screen, game console, and augmented reality (AR) / virtual reality (VR) device.

[0049] For example, the device 2 described above can be a collaborative end. For instance, device 2 can be an intelligent electronic device such as a mobile phone, tablet, handheld computer, PC, cellular phone, personal digital assistant (PDA), wearable device (such as smartwatch), smart screen, game console, and augmented reality (AR) / virtual reality (VR) device.

[0050] For example, Figure 1 As shown, the collaborative system can include mobile phones, smart screens, smartwatches, tablets, PCs, etc. When any one of these devices is designated as Device 1, the others are designated as Device 2. For example, if the mobile phone is Device 1, the smart screen, smartwatch, tablet, and PC are Device 2.

[0051] In some embodiments, in addition to establishing a near-field communication connection, a trust relationship also exists between device 1 and device 2.

[0052] For example, if the system authentication accounts logged into Device 1 and Device 2 are the same, it can be determined that a trust relationship exists between Device 1 and Device 2. As another example, if Device 1 and Device 2 have already undergone mutual recognition (e.g., authorization), it can also be determined that a trust relationship exists between Device 1 and Device 2.

[0053] For example, if a near-field communication connection is established between a mobile phone and a laptop, and both the mobile phone and the laptop are logged into the same system authentication account, such as an Honor system account, it can be determined that there is a trust relationship between the mobile phone and the laptop, that is, the two belong to the same collaborative system.

[0054] In some embodiments, the devices in the collaborative system can vary. For example, a collaborative system including a mobile phone may also include a laptop computer. If the conditions for establishing near-field communication (NFC) between the mobile phone and the laptop computer are not met, such as when the distance between them exceeds the effective communication distance of NFC, the laptop computer is not included in the collaborative system. Conversely, in a scenario where a tablet computer and a mobile phone are both logged into the same system's authentication account, and the conditions for establishing a NFC connection between them are met, such as when the distance between them does not exceed the effective communication distance of NFC, a tablet computer can be added to the collaborative system.

[0055] As shown above, when the collaborative system includes device 1 and at least one device 2, device 1 and device 2 can collaborate to provide a call service. In this scenario, device 1 can be a mobile phone with a system-level calling application. Of course, device 1 can also be an electronic device with a third-party calling application installed.

[0056] For example, in a scenario where someone calls, device 1 can receive the call request information, referred to as an incoming call. It is understood that the aforementioned call can be a calling service provided by a mobile operator, or it can be a communication software (such as Changlian). TM ,WeChat TM The aforementioned telephone service can include both voice and video calls. Voice calls may be calls that transmit only voice data. Video calls may be calls that simultaneously transmit voice data and real-time video data.

[0057] When device 1 receives an incoming call, devices 1 and 2 can activate call alerts sequentially or simultaneously, such as ringing, vibrating, or displaying an alert interface. This allows the user to choose to answer the call via either device 1 or device 2.

[0058] Clearly, in scenarios with a large number of devices 2 in the collaborative system, the sequential or simultaneous activation of call alerts by devices 1 and 2 can effectively prevent users from missing calls. However, when all devices indiscriminately execute call alerts, it can also cause considerable inconvenience for users. For example, users need to determine whether the alerts from devices 2 and 1 are for the same call. Furthermore, after a user answers a call using any device (device 1 or device 2), other devices in the collaborative system will not immediately stop alerting; that is, they will continue to send call alerts for a delay. These inconveniences force users to repeatedly check and operate device 1 and multiple devices 2. Obviously, in scenarios involving collaborative communication services, the human-computer interaction efficiency for handling call alerts is low.

[0059] To address the aforementioned issues, this application provides a call reminder method applied to the aforementioned collaborative system. The collaborative system includes device 1 and multiple devices 2. Based on the actual usage of devices 1 and 2, and in conjunction with a preset device selection strategy, this method identifies device 3 from the multiple devices 2 and controls device 1 and device 3 to collaboratively perform call reminders. Thus, in scenarios where the number of devices in the collaborative system is at least three, this method improves the problem of all devices in the collaborative system indiscriminately performing call reminders, thereby increasing the human-computer interaction efficiency in handling call reminders in the collaborative system.

[0060] In other embodiments, the method may also determine device 3 from device 1 and multiple devices 2 based on the actual usage of device 1 and device 2, combined with a preset device selection strategy, and control device 3 to provide incoming call reminders.

[0061] In some embodiments, the hardware and software architecture of the devices in the above-described collaborative system may be different.

[0062] Taking mobile phones as an example, such as Figure 2A As shown, a mobile phone can include an application layer, a service layer, and a device connectivity layer.

[0063] The application layer can include a series of application packages. For example... Figure 2A As shown, the application layer can include multiple application packages such as the incall user interface (incall UI), the contacts application, and the contacts storage / synchronization application.

[0064] The service layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The service layer includes some predefined functions.

[0065] like Figure 2A As shown, the programming framework may include the Telecom AOSP calling framework. The Telecom AOSP calling framework can be used to manage audio and video calls made by the mobile phone. This includes SIM-based calls (e.g., using the Telephony framework) and VoIP calls provided by the ConnectionService API implementer.

[0066] In addition, the API can also include APIs for calling the Telephony cellular service, APIs for calling the Profile service, APIs for calling the Super Caller service, and APIs for calling the Super Terminal Control Center. In this way, installed applications can call the corresponding APIs or programming frameworks from the service layer according to actual business needs to implement the services required by the business.

[0067] In addition, the device connectivity layer includes the device virtualization layer, the hardware abstraction layer (HAL), and the hardware layer.

[0068] For example, the hardware layer includes multiple types of hardware modules, each capable of performing different functions. For instance, the hardware layer includes a modem and a Link module. The modem is used for signal translation between different devices, while the Link module is used for communication connectivity between devices.

[0069] For example, the HAL provides HALs corresponding to different hardware modules, such as Audio HAL, Camera HAL, Wi-Fi HAL, etc. In this way, each HAL can drive the corresponding hardware module and implement the corresponding function of the hardware module.

[0070] In addition, the device virtualization layer can virtualize modules that perform specific functions on the basis of hardware modules. For example, the device virtualization layer can include an audio virtualization module.

[0071] In this embodiment, the HAL and its corresponding hardware modules can be referred to as underlying modules. Similarly, the modules virtualized in the device virtualization layer can also be referred to as underlying modules. It is evident that the device connectivity layer includes underlying modules that implement multiple functions. Thus, the device connectivity layer also possesses diverse capabilities, such as device profile, device network discovery, partial permission management, security, and transmission capabilities.

[0072] Understandably, the service layer can invoke one or more underlying modules in the device connectivity layer to instruct the device connectivity layer to enable different functions, such as implementing a call function. For ease of description, the underlying module used to implement the call function can be referred to as the underlying call module.

[0073] Taking watches as an example again, such as Figure 2B As shown, a watch can also include an application layer, a service layer, and a device connectivity layer. Similarly, the watch's application layer includes an incall UI, and the service layer can include APIs for calling the Super Call service. Additionally, the watch's device connectivity layer does not contain an underlying call module, but it does include an audio capability module. When a communication connection is established between the watch and the phone, the phone can share its call functionality with the watch. For example, the watch can decode call data 1 through the phone's underlying call module to obtain audio information 1. Then, it can play this audio information 1 using the audio capability module, thus enabling the watch to answer calls. Furthermore, the watch can also collect audio information 2 through its audio capability module, encode the audio information 2 through the phone's underlying call module to obtain call data 2, and send it out. This enables the watch to perform walkie-talkie functionality.

[0074] Continuing with the example of a PC, such as Figure 2C As shown, a PC can also include an application layer, a service layer, and a device connection layer. The application layer can also include multiple application packages such as incall UI, contacts application, and contacts storage / synchronization application. The PC's service layer includes APIs for calling the Profile service, APIs for calling the Super Caller service, and APIs for calling the Super Terminal Control Center. Additionally, when the PC's device connection layer does not include the underlying call module or the underlying module implementing audio capabilities (e.g., an audio virtual module), a software module for virtual audio functionality can be created, such as an audio simulation module. When a communication connection is established between the PC and the mobile phone, the mobile phone can share its call functionality with the PC. For example, the PC can decode the received call data 1 through the mobile phone's underlying call module to obtain audio information 1. Then, the PC can play this audio information 1 through the audio simulation module, thus enabling the PC to answer calls. Furthermore, the PC can also use the audio simulation module to collect audio information 2, then encode the collected audio information 2 through the mobile phone's underlying call module to obtain call data 2, and send it out. This enables the PC to perform intercom functionality.

[0075] As can be seen, even with differences in hardware and software architecture, all devices in the collaborative system support answering incoming calls, and the devices can also coordinate to send call alerts. Taking mobile phones and PCs as examples, this article explains the principle of collaborative call alerts between devices in the collaborative system.

[0076] In some embodiments, such as Figure 3 As shown, the phone includes a Super Caller ID service, a decision center, a Device Profile, and a Link module.

[0077] The mobile phone can establish a communication connection with the PC through the link module to receive data sent by the PC, such as static service information sent by the PC.

[0078] In some examples, static service information includes profile information, usage status, and near-field information. The profile information may include the profile types supported by the PC, such as supported phonebook access profile (PBAP), hands-free profile (HFP), and object push profile (OPP). The profile information may also include the profile version information supported by the PC. The near-field information includes available near-field communication types and parameters used to establish near-field communication links.

[0079] Understandably, a mobile phone can establish a service link with a PC based on the PC's profile information and near-field information. This service link is used to transmit interactive data during the service collaboration process.

[0080] Furthermore, the aforementioned usage status can be used to indicate the current working condition of the PC. The current working condition of the PC can be assessed from aspects such as whether there are applications running in the foreground and whether there is interaction with the user. For example, usage status includes active usage and inactive usage. When a foreground application is running on the PC, the PC is assessed as being in active usage. In scenarios where there is interaction between the PC and the user, the PC is assessed as being in active usage. For example, if the PC's camera recognizes the user facing the PC's screen; or if the PC's input device receives user input, it can be determined that there is interaction between the PC and the user, and the PC is assessed as being in active usage; similarly, if the PC's screen is lit, it can also be determined that there is interaction between the PC and the user, and the PC is assessed as being in active usage. In scenarios where no applications are running in the foreground and the PC does not recognize any interaction with the user, the PC is assessed as being inactive. As one implementation method, the PC can use an artificial intelligence model, combined with the PC's real-time operating data, to assess the PC's usage status.

[0081] In other embodiments, if the first device (or second device) meets a first condition, it can be determined that the first device (or second device) is in an unused state. For example, the first condition could be that the first device (or second device) is in a screen-off state. Another example is that the first device (or second device) does not contain any applications running in the foreground. Yet another example is that the first condition could be that no user operation has been received for a long period (a preset duration).

[0082] In other embodiments, if the first device (or the second device) meets a second condition, it can be determined that the first device (or the second device) is in use. The second condition includes detecting user facial features, receiving user input, or being in a screen-on state.

[0083] In other possible embodiments, static service information may also include a collaboration status. The collaboration status indicates whether the PC is currently performing a collaboration task, which may include multi-screen collaboration tasks, screen projection tasks, remote control tasks, and call collaboration tasks, collectively referred to as the first task. For example, in a scenario where the PC and tablet are performing multi-screen collaboration, the PC's collaboration status may indicate that the PC is performing a collaboration task. Similarly, in a scenario where the PC projects its interface onto a smart TV, the PC's collaboration status may also indicate that the PC is performing a collaboration task. Furthermore, in a scenario where the tablet remotely controls the PC, the PC's collaboration status may also indicate that the PC is performing a collaboration task. Finally, in a scenario where the tablet is equipped with a subscriber identity module (SIM) card and the PC is answering a call received by the tablet, the PC's collaboration status may also indicate that the PC is performing a collaboration task.

[0084] In addition, the phone has a mapping table, such as a device list. This device list can be used to maintain received static service information.

[0085] In some embodiments, when a mobile phone receives static service information 1 sent by a PC, the mapping table includes entry 1, which includes an identifier indicating the PC and the corresponding static service information 1.

[0086] In addition, the PC can periodically send static service information to the mobile phone, ensuring that the PC can update the mobile phone with real-time usage status or profile information. In this way, the entries in the mapping table can be updated in real time. For example, when the mobile phone receives a new static service information 2 sent by the PC, the mobile phone can update entry 1. After the update, entry 1 includes the identifier indicating the PC and the corresponding static service information 2.

[0087] Of course, if the conditions for near-field communication between the PC and the mobile phone are not met, such as when the actual distance between the PC and the mobile phone exceeds the effective communication distance, the mobile phone will not be able to receive the static service information sent by the PC, and the corresponding entries on the PC will not be able to be updated.

[0088] In addition, entries have a time limit. Within the time limit, an entry is valid. If an entry is updated within the time limit, the time limit is reset. Of course, if the time limit expires and it is not updated, the entry becomes invalid. For example, if the time limit is 1 minute, after the mobile phone receives static service information 1 sent by the PC, it creates entry 1, which includes an identifier indicating the PC and static service information 1. Entry 1 is valid for 1 minute after its creation. If, within 1 minute of entry 1's creation, the mobile phone receives static service information 2 sent by the PC, it updates entry 1, which includes the identifier indicating the PC and static service information 2. Furthermore, entry 1 remains valid for 1 minute after the update. If more than 1 minute has passed since the update and entry 1 is not updated again, then entry 1 becomes invalid.

[0089] Of course, the mobile phone can also receive static service information sent by other devices in the collaborative system (such as smart screens, smartwatches, and tablets) and update the device list.

[0090] In some embodiments, the service layer in the mobile phone can read the device list through the Device Profile. Understandably, the Device Profile is a service query interface used to query the services supported by other devices.

[0091] In this way, the phone can identify other devices belonging to the same collaborative system as the phone, such as PCs, smart screens, smartwatches, and tablets, by calling the Device Profile.

[0092] For example, after a mobile phone receives an incoming call, the Super Call service can obtain valid entries in the device list through the Device Profile, thereby obtaining other devices in the same collaborative system (such as device 2) and the static service information corresponding to device 2.

[0093] In some embodiments, the decision center of the mobile phone can be used to instruct the Link module to establish a connection with all devices 2 based on the static service information of device 2, such as establishing a service link, and using the service link to transmit negotiation information before the collaborative call service.

[0094] In addition, the mobile phone's decision center is also used to identify device 3 from the collaborative system.

[0095] In some embodiments, the device 3 identified by the decision center meets at least one of the following conditions:

[0096] First, it can promptly remind users to answer incoming calls. In some embodiments, the decision center can evaluate, within the collaborative system, devices that can promptly remind users to answer incoming calls based on their usage status.

[0097] Secondly, it has a high priority. The phone has a device type priority setting. For example, a smartwatch might have a higher priority than a tablet, tablets and PCs might have the same priority, and a PC might have a higher priority than a smart screen. Furthermore, the device type priority can be updated; for instance, the phone can respond to user actions and modify the device type priority.

[0098] Third, there is no collaboration conflict with mobile phones.

[0099] For example, if the mobile phone has its collaboration service disabled, it can be determined that there is a collaboration conflict with all devices. As another example, if the mobile phone's blocked list includes a PC, it can also be determined that there is a collaboration conflict between the PC and the mobile phone. The devices in the blocked list can be configured by the user. Thus, in the process of determining device 3 from device 2, the decision center can first filter out devices in device 2 that have collaboration conflicts with the mobile phone, and then determine device 3 from the filtered device 2.

[0100] For example, when a mobile phone recognizes that it is in use and receives an incoming call, the decision center can retrieve multiple devices 2 from the device list, such as PCs, smart screens, smartwatches, and tablets that are on the same collaborative system as the mobile phone. Then, based on the device type priority (e.g., smartwatches have higher priority than tablets, tablets and PCs have the same priority, and PCs have higher priority than smart screens), the decision center determines that the smartwatch has the highest priority among devices 2. In this way, the decision center can identify the smartwatch as device 3.

[0101] In a possible embodiment, the static service information of device 2 also includes an identifier indicating the reminder mode of device 2, such as an identifier indicating whether the ringing mode is enabled. It is understood that during the ringing mode, device 2 is in a ringing state; that is, device 2 will use vibration, ringing, or other methods to remind users of matters, such as call reminders, message reminders, calendar reminders, task reminders, etc. Of course, the user can choose the actual reminder method used in the ringing mode from vibration / ringing and ringing. For example, if the user configures the reminder method corresponding to the ringing mode as vibration, then during the ringing mode, when a reminder occurs, it will be reminded by vibration. Similarly, if the user configures the reminder method corresponding to the ringing mode as ringing, then during the ringing mode, when a reminder occurs, it will be reminded by ringing.

[0102] In addition, non-ringing mode (also known as silent mode) and ringing mode are mutually exclusive reminder modes. When device 2 is in silent mode, device 2 is in a silent state. That is, device 2 will use silent notification to remind you of the task, such as displaying a reminder notification, but without ringing or vibrating.

[0103] Based on this, in determining device 3, the decision center can consider not only device type priority but also the reminder mode of device 2. For example, the decision center can select the highest-priority device from among devices 2 that have enabled ringing mode as device 3. For instance, if the PC and smart screen in device 2 have ringing mode enabled, while the smartwatch and tablet have not (i.e., are in silent mode), then device 3 can be selected from the PC and smart screen based on device type priority; that is, the PC is selected as device 3.

[0104] In other possible embodiments, the static service information of device 2 may also include an identity identifier. This identity identifier can be used to indicate the user of device 2, wherein the user is the current user of device 2.

[0105] For example, device 2 stores multiple biometric information (such as facial features, fingerprint features, iris features, etc.) and their corresponding identity identifiers. After receiving an operation from the user, device 2 determines that it is in active use and can simultaneously collect biometric information. The collected biometric information is then compared with the preset correspondences to determine the corresponding identity identifier.

[0106] Thus, in some embodiments, during the process of determining device 3 from device 2, the decision center also needs to consider the identity identifier in the static service information. For example, the decision center can determine device 4 from device 2, where the identity identifier carried in the static service information of device 4 matches the system authentication account logged in by the mobile phone (e.g., system authentication account 1). For instance, the identity identifier corresponding to device 4 is the same as the identity identifier bound to system authentication account 1. Then, the decision center further considers the usage status and device type priority of device 4 to determine device 3 from device 4.

[0107] For example, when the smartwatch is in use, after the mobile phone receives an incoming call, it can identify the smartwatch as device 3. In this way, the mobile phone and the smartwatch can work together to provide call notifications.

[0108] Of course, the same principle applies when tablets, PCs, and smart screens are in use, so we won't go into detail here. If all devices in the collaborative system are inactive, and a smartwatch is detected as the user, it can be identified as device 3.

[0109] In other embodiments, in a scenario where at least one device in the collaborative system is in use and the user is identified as wearing a smartwatch, in addition to identifying the device in use as device 3, the smartwatch can also be identified as device 3.

[0110] In other possible embodiments, device 2 also includes device 5, which is another device in device 2 besides device 3. While the mobile phone instructs device 3 to coordinate incoming call alerts, it can also send a notification command to device 5. Device 5 can then display notification information indicating the incoming call based on the notification command; that is, device 5 only provides a display alert and does not need to provide an audio or vibration alert. It is understood that even if device 5 is in vibration mode and its configured alert method is ringing or vibration, device 5 does not need to perform ringing or vibration when coordinating with the mobile phone for incoming call alerts.

[0111] In other embodiments, after receiving an incoming call, the mobile phone can also determine device 3 from the collaborative system based solely on priority. For example, the collaborative system to which the mobile phone belongs may also include PCs, smart screens, smartwatches, and tablets. If the smartwatch has the highest priority in the collaborative system, the mobile phone can identify the smartwatch as device 3 and collaborate with device 3 to perform incoming call notifications.

[0112] After identifying device 3, the decision center also sends a ringing signal to the Super Caller Service. This ringing signal includes an identifier for device 3, such as the PC's identifier. Upon receiving the ringing signal, the Super Caller Service can instruct the Link module to send a ringing command to the PC. This ringing command is a request for the PC and the mobile phone to coordinate incoming call notifications.

[0113] In other embodiments, when multiple devices 3 are identified, the decision center can send resonance commands to each device 3 sequentially according to the priority order among the multiple devices 3.

[0114] As one implementation method, the Super Call service also includes Incallservice, a co-ring strategy / conflict handling module, a signaling / data status near-field transmission module, and a service registration / device management module.

[0115] The service registration / device management module is used to write the received static service information into the device list via Device Profile. Additionally, this module is also used to query the device list by calling Device Profile to obtain the static service information corresponding to device 2.

[0116] The aforementioned resonance strategy / conflict handling module is used to instruct the decision center to identify device 3, and also to receive resonance information sent by the decision center. This resonance information includes the identifier of device 3.

[0117] The Incallservice mentioned above is a service interface for non-native InCallUI devices to call the phone's call reservation framework. In other words, through this Incallservice, other devices can operate on the phone's incoming calls (e.g., answer or hang up the phone) and be aware of changes in the phone's call status.

[0118] For example, the Incall service is used to generate a synchronization command based on the synchronization information. Each synchronization command corresponds to one device 3. Finally, the signaling / data status near-field transmission module instructs the link module to send the synchronization command to device 3.

[0119] Continuing with the example of a PC receiving a simultaneous ringing command from a mobile phone, the PC's Super Call service includes a signaling / data status near-field transmission module, a simultaneous ringing strategy / conflict handling module, and a service invocation module.

[0120] The aforementioned signaling / data status near-field transmission module is used to receive ringing commands via the Link module. This signaling / data status near-field transmission module is also used to instruct the ringing strategy / conflict handling module to activate the call UI. The aforementioned call UI is used to display the interface reminding users of incoming calls, referred to as the incoming call interface UI.

[0121] In some embodiments, before the call UI pulls up the call interface UI, the co-ring strategy / conflict handling module is also used to indicate whether the PC currently has the conditions for co-ring call notification.

[0122] Understandably, multiple scenario conditions 1 can be pre-configured in the PC, which can indicate scenarios where the PC cannot coordinate call services.

[0123] For example, scenario condition 1 includes the PC enabling application 1, where application 1 is an application pre-configured to be uninterrupted by call services, also known as the first application. The first application set on different devices may be different, and there is no specific limitation on this. It is understood that after the PC responds to the user's operation and selects application 1, the PC can adjust the priority of the application service corresponding to that application to be higher than the call service. For example, if the user configures a video conferencing application as application 1, then the PC will prioritize the conferencing service corresponding to the video conferencing application to be higher than the call service. Thus, while the PC is running the video conferencing application, that is, when providing conferencing services, the PC does not coordinate call-related services; that is, scenario condition 1 includes the PC running a video conferencing application.

[0124] For example, scenario condition 1 includes the PC not having collaborative permissions for the call service enabled. For instance, if the PC disables the collaborative function of the call service, it can reject all call collaboration requests sent by devices.

[0125] As another example, scenario condition 1 also includes the PC performing a collaborative task, such as the PC engaging in multi-screen collaboration with a tablet, the PC casting its screen to a smart TV, or the tablet remotely controlling the PC.

[0126] In this way, the PC's co-ring strategy / conflict handling module determines that the PC does not currently meet the conditions for collaborative call notification when it detects that application 1 is running in the foreground, does not have collaborative permissions for call service enabled, detects that the PC is already in collaborative mode, or is in screen mirroring mode. Conversely, it determines that the PC currently meets the conditions for collaborative call notification.

[0127] In some embodiments, if the PC includes a decision center, the ringing policy / conflict handling module can instruct the decision center to determine whether the PC currently meets the conditions for collaborative call alerts. Additionally, if the decision center is not ready, the PC's ringing policy / conflict handling module can also preliminarily assess whether the conditions for call alerts are met. For example, the ringing policy / conflict handling module detects whether the decision center has registered a ringing service. This ringing service could be a service registered with the decision center after the PC receives an incoming call, or after collaborating with other devices on a call, indicating that the PC is currently on a call or collaborating on a call. If a registered ringing service already exists, a preliminary assessment can be made that the conditions for call alerts are not met. If it is determined that the conditions for call alerts are not met, the PC can refuse to collaborate with the mobile phone to provide call alerts.

[0128] In other embodiments, the call UI also includes a local do-not-disturb policy module, which can also access pre-configured scenario condition 1. Thus, in cases where the PC does not include a decision center, the co-ring policy / conflict handling module can instruct the local do-not-disturb policy module to determine whether the PC currently meets the conditions for coordinated incoming call alerts.

[0129] Additionally, the local do-not-disturb policy module also uses a pre-configured device list 1, also known as the first list, to assess whether the mobile phone has the permission to instruct the PC to perform collaborative call service tasks. This device list 1 includes device identifiers, with different identifiers indicating different electronic devices. Furthermore, after determining that the conditions for collaborative call reminders are met, the system can also query device list 1 to determine whether the mobile phone has the permission to perform collaborative call services with the PC. If device list 1 includes the mobile phone's identifier, then the mobile phone is determined not to have the permission to perform collaborative call services with the PC; conversely, if device list 1 does not include the mobile phone's identifier, then the mobile phone is determined to have the permission to perform collaborative call services with the PC. Of course, the contents of the first list can differ for different devices.

[0130] After confirming that the phone has permission to use the PC-based collaborative calling service, the call UI can pull up the call interface UI and provide call notification.

[0131] For example, after the PC receives the vibration command from the mobile phone, the vibration strategy / conflict handling module can obtain the mobile phone's static service information from the Device Profile. Understandably, during the process of the PC sending static service information to the mobile phone, the mobile phone will also periodically send its own static service information to the PC. Thus, in scenarios where the mobile phone's static service information indicates that the phone is in use and the PC determines to coordinate with the mobile phone for incoming call notifications, the PC will provide a silent notification. In scenarios where the mobile phone's static service information indicates that the phone is not in use and the PC determines to coordinate with the mobile phone for incoming call notifications, the PC will provide an incoming call notification according to the configured notification method (vibration, ringing, dialing, etc.).

[0132] In addition, after the PC brings up the call interface UI, the user can instruct the PC to answer the call by operating the PC.

[0133] After the PC receives a user instruction to answer the incoming call, the service invocation module can schedule the underlying call module to work with the phone's underlying call module to answer the call received by the phone. For example, after the PC receives the user instruction to answer the call, it notifies the phone. Upon receiving the notification, the phone receives the call data 1 corresponding to the incoming call, then invokes the Telecom AOSP call framework and the Telephony cellular call service to activate the phone's underlying call module, decodes call data 1, obtains audio information 1, and then sends this audio information 1 to the PC. After receiving audio information 1, the service invocation module in the Super Call service can invoke the PC's underlying call module to play the audio information 1. Additionally, the PC can also use the service invocation module to invoke the underlying call module to collect audio information 2 and send it to the phone. In this way, the phone can use the underlying call module to encode audio information 2, obtain call data 2, and send it.

[0134] Of course, in scenarios where users choose to answer incoming calls on their phones, such as... Figure 3 As shown, incall UI can be enabled after the phone receives an incoming call. Once incall UI is enabled, it displays the incoming call interface. Additionally, it can utilize call frameworks such as the Telecom AOSP call framework or Telephony cellular service to schedule the underlying call module, allowing the user to answer the call directly on their phone.

[0135] In summary, after receiving an incoming call request, the mobile phone can determine how other devices in the collaborative system should provide call notifications based on the usage, device status (e.g., configured notification methods), and priorities of each device (including the mobile phone) in the collaborative system.

[0136] The following table shows the responses of mobile phones, smart screens, smartwatches, tablets, and PCs to incoming call requests received by mobile phones in different usage scenarios, using a collaborative system that includes mobile phones, smart screens, smartwatches, tablets, and PCs as examples:

[0137] Table 1

[0138]

[0139]

[0140] Table 1 shows some examples of multi-device collaborative call alerts according to this application, but this application is not limited to these. The smartwatch mentioned above is only an example of a wearable device. The wearable device in the collaborative system can also be referred to as a third device, such as a Bluetooth headset. In addition, other devices in the collaborative system besides the third device and the first device can also be referred to as a fourth device. When all devices in the collaborative system meet the first condition (i.e., no one is using the device), and the first device receives an incoming call (e.g., referred to as the first call request), regardless of whether the call alert method pre-configured by the fourth device is ringing, vibrating, or ringing, it will not ring and / or vibrate. For example, the fourth device can not respond at all, or it can only display the call notification. In addition, the first device can also send a vibration command (i.e., a third message) to the third device, instructing the third device to provide a call alert in response to the first call request.

[0141] The following describes the implementation process of the method provided in the embodiments of this application, taking device 1 as a mobile phone as an example.

[0142] In this embodiment, the mobile phone needs to detect surrounding electronic devices and determine whether a trust relationship exists between it and these devices. For example, in a scenario where a user carries their mobile phone into a room containing a PC, ... Figure 4 As shown, the above method includes the following steps:

[0143] S101-1, The mobile phone uses the public key of system authentication account 1 to encrypt broadcast information.

[0144] S101-2, the mobile phone sends a broadcast message.

[0145] In some embodiments, a mobile phone can use near-field communication (NFC) technology to send broadcast information, ensuring that electronic devices located close to the mobile phone can receive the broadcast information. The implementation of NFC technology can be found in related technologies and will not be elaborated upon here.

[0146] In addition, the broadcast message sent by the mobile phone includes an encrypted system authentication account 1, which is the system authentication account that the mobile phone is currently logging into.

[0147] In some embodiments, the aforementioned system authentication account can be a registered account provided by a cloud server. Each system authentication account can correspond to a public key used to encrypt information associated with the system authentication account. All public keys of system authentication accounts can be stored on the cloud server. For example, the cloud server stores public key 1 corresponding to system authentication account 1. Additionally, the mobile phone can interact with the cloud server to obtain public key 1 corresponding to system authentication account 1.

[0148] For example, if a mobile phone is logged into with a system-authenticated account 1, the corresponding public key 1 can be obtained by sending a public key request to the cloud server. The mobile phone can then use public key 1 to encrypt the system-authenticated account 1 to obtain the aforementioned broadcast information. For instance, the account could be a Honor account. The mobile phone can first obtain the public key corresponding to the logged-in Honor account from the Honor cloud server, then use the public key to encrypt the Honor account, and finally generate a broadcast message.

[0149] In some embodiments, the mobile phone can broadcast information to the outside world in real time. In other instances, the mobile phone can initiate the broadcasting of information after identifying a specific scenario. For example, the specific scenario could be that the mobile phone detects a change from a stationary state to a moving state. Another example is that the specific scenario could be that the mobile phone's location has changed. Yet another example is that the specific scenario could be that the mobile phone receives message 1 sent by router 1. Here, router 1 is the wireless access point currently connected to the mobile phone, and message 1 is a notification message sent by router 1 to the connected mobile phone after detecting the access of another device.

[0150] S102, after receiving the broadcast information, the PC obtains the private key 2 corresponding to the system authentication account 2.

[0151] In this context, system authentication account 2 is the currently logged-in system authentication account on the PC. Furthermore, it's understandable that the cloud server stores not only the public key corresponding to the system authentication account but also its private key. The public and private keys for the same account match; in other words, data encrypted with the public key can be decrypted using the private key corresponding to the same account.

[0152] In some examples, after a PC logs into system authentication account 2, it can obtain the private key 2 corresponding to system authentication account 2 from the cloud server and store the obtained private key 2 in a trusted storage location, such as storage area 1. In this way, the PC can query and use private key 2 according to business needs. Of course, after the PC logs into other system authentication accounts, it can also delete private key 2 from storage area 1 and download the private key of the other system authentication account from the cloud server. The newly downloaded private key can also be stored in storage area 1.

[0153] Thus, in this embodiment, after receiving the broadcast information, the PC determines that the broadcast information contains encrypted content. Then, the PC can read the stored private key from storage area 1, for example, read private key 2. After reading private key 2, the process proceeds to S103.

[0154] S103, the PC uses private key 2 to decrypt the broadcast message.

[0155] In some embodiments, if system authentication account 1 and system authentication account 2 are the same account, then private key 2 matches public key 1. In this case, the PC can successfully decrypt the broadcast message using private key 2. If system authentication account 1 and system authentication account 2 are not the same account, then private key 2 does not match public key 1, and the PC cannot decrypt the broadcast message using private key 2.

[0156] In some embodiments, after successfully decoding the broadcast message, the PC can determine that a trust relationship exists between it and the mobile phone. The PC can then add the mobile phone to a list of trusted devices. All devices in the trusted device list are trusted devices of the PC. When the mobile phone is included in this list, the PC can securely receive data sent by the mobile phone, reducing the possibility of unauthorized data access.

[0157] S104, In the scenario where the broadcast information is successfully decrypted, the PC sends feedback information 1 to the mobile phone to indicate that the PC has successfully decrypted the broadcast information.

[0158] In some embodiments, the feedback information 1 may carry an identifier indicating successful decryption. Alternatively, it may carry the system authentication account currently logged into the PC, such as system authentication account 2.

[0159] Alternatively, in the event that the broadcast message was not successfully decrypted, the PC may choose not to respond to the broadcast message, that is, not to send any information to the mobile phone. Or, the PC may send feedback message 2 to the mobile phone to indicate that the decryption of the broadcast message failed. This feedback message 2 may carry an indicator indicating that decryption was unsuccessful.

[0160] In other embodiments, before sending feedback information 1, the PC can also use the public key corresponding to the system authentication account 2 to encrypt the feedback information 1, thereby improving the security of the feedback information 1.

[0161] S105, if the mobile phone receives feedback information 1, it confirms that a trust relationship exists between it and the PC.

[0162] In some embodiments, when the mobile phone receives feedback information 1, it can determine that a trust relationship exists between the mobile phone and the PC. Based on this, the mobile phone can add the PC to the list of trusted devices.

[0163] Furthermore, in the scenario where feedback information 1 is encrypted, the mobile phone can decrypt feedback information 1 using the private key 2 corresponding to system authentication account 1. Upon successful decryption of feedback information 1, the mobile phone confirms the existence of a trust relationship with the PC and adds the PC to its trusted device list. With the PC included in the mobile phone's trusted device list, the mobile phone can securely receive data sent by the PC, reducing the possibility of unauthorized data access.

[0164] In the embodiments of this application, when there is a trust relationship between the mobile phone and the PC, and the distance between them meets the requirements of near-field communication, the mobile phone and the PC can automatically establish a mutually trusted near-field communication connection, that is, a trusted connection, when they need to interact with each other.

[0165] In some examples, before each trusted connection is established, the existence of a trust relationship between the phone and the PC is determined by querying the trusted device list. In other examples, before each trusted connection is established, the existence of a trust relationship between the phone and the PC needs to be determined through steps S101 to S105. Of course, in other examples, if the trust relationship between the phone and the PC has already been determined through steps S101 to S105, then repeated confirmation of the trust relationship is unnecessary if the phone and / or PC do not change their system authentication accounts. Of course, if the phone changes its system authentication account, the trusted device list can be cleared, and the trust relationship can be re-established with nearby devices.

[0166] In some embodiments, after receiving an incoming call, the mobile phone can use a trusted connection to instruct a trusted device (e.g., a PC) to collaboratively provide call notification. Figure 5 As shown, the above method may further include:

[0167] S201-1, Super Call Service 13 instructs Link module 11 to send static service information 1 to the mobile phone.

[0168] In some embodiments, the Super Call Service 13 described above is a service provided by the PC's service layer. The Super Call Service 13 sends static service information to the mobile phone periodically by sending instruction signaling.

[0169] S201-2, Link module 11 sends static service information 1 to Link module 23.

[0170] S201-3, Link module 23 forwards static service information 1 to Device Profile.

[0171] The Link module 11 mentioned above is the underlying module in the PC that implements communication functions, used to establish communication connections and perform data interaction with other devices. The Link module 23 is the underlying module in the mobile phone that implements communication functions, used to establish communication connections and perform data interaction with other devices. That is, data interaction between the mobile phone and the PC can be achieved through the Link module 11 and the Link module 23. Of course, the above is only one way for the PC and the mobile phone to perform data interaction (e.g., transmit static service information). In other embodiments, the PC and the mobile phone can also indirectly perform data interaction through a cloud server.

[0172] In some embodiments, under the instruction of the Super Call Service 13, the Link module 11 can periodically send static service information to the Link module 23, such as sending static service information 1, which is then forwarded by the Link module 23 to the device profile of the mobile phone.

[0173] As one implementation, Link module 23 can forward static service information 1 to the phone's Device Profile through the service registration / device management module. In this way, the static service information 1 sent by the PC can be maintained by DeviceProfile, such as by writing it into the device list.

[0174] As another implementation, Link module 23 can also directly forward static service information 1 to the phone's Device Profile.

[0175] S202, Device Profile update device list. After the update, the device list includes PCs and corresponding static service information 1.

[0176] The Device Profile mentioned above can be a service interface provided by the mobile phone's service layer.

[0177] In some embodiments, after the mobile phone receives static service information 1, it schedules the Device Profile to update the device list based on the static service information 1. The implementation process is described in the foregoing embodiments and will not be repeated here.

[0178] In other embodiments, the aforementioned Device Profile can also be a service interface provided by the service layer of the cloud server. That is, in a scenario where the PC determines that near-field communication can be performed between the PC and the mobile phone, the Super Call service 13 can instruct the Link module 11 to periodically send static service information to the cloud server, and the Device Profile in the cloud server can update the device list corresponding to the mobile phone based on the static service information.

[0179] Additionally, after the phone receives an incoming call, the process proceeds to S203-1. Understandably, even after the process enters S203-1, the phone can still receive static service information from other devices (including a PC) and update the device list.

[0180] S203-1, Super Call Service 21 Dispatch Device Profile, used to query the device list.

[0181] In some embodiments, the Super Calling Service 21 described above is a service provided by the service layer in the mobile phone. When the Device Profile is configured within the mobile phone, the Super Calling Service 21 can schedule the Device Profile through the service registration / device management module to query the latest device list. When the Device Profile is configured on a cloud server, the Super Calling Service 21 can send query information 1 to the cloud server. This query information 1 carries the mobile phone's identifier, instructing the cloud server to schedule the Device Profile and query the latest device list corresponding to the mobile phone.

[0182] S203-2, Device Profile reports the device list to Super Call Service 21.

[0183] As shown in the aforementioned embodiment, the device list includes the identifier of device 2 and the corresponding static service information of device 2, such as the identifier of the PC and the corresponding static service information 1. The device list is updated in real time to ensure that all devices 2 indicated in the device list can establish near-field communication connections with the mobile phone.

[0184] As one implementation method, Device Profile can also send a list of devices to Super Call Service 21 through the service registration / device management module.

[0185] S204, Super Call Service 21 sends instruction information 1 to Decision Center 22.

[0186] In some embodiments, the decision center 22 is a program module configured in a mobile phone. The instruction information 1 is used to instruct the decision center 22 to determine the device 3 from the collaborative system for the currently received incoming call.

[0187] Super Call Service 21 registers / subscribes to the resonance service in Decision Center 22 by sending instruction message 1. After registering for the resonance service, Decision Center 22 begins to execute the task "Identify Device 3".

[0188] In other embodiments, before registering / subscribing to the same-ringing service, that is, before S204, the Super Calling Service 21 can also monitor whether the mobile phone currently meets the same-ringing requirements, such as whether the function of requesting other devices to ring together is enabled. If the same-ringing requirements are met, the process proceeds to S204.

[0189] Additionally, after registering / subscribing to the resonance service, the aforementioned instruction information 1 can also instruct the decision center 22 to identify device 3 from device 2 indicated in the device list. In this way, the process can proceed to S205.

[0190] S205, Decision Center 22 responds to Instruction Message 1 and identifies PC as Device 3.

[0191] In some embodiments, the process of determining device 3 from devices 2 indicated in the device list can refer to the foregoing embodiments, that is, device 3 can be determined from devices 2 based on the usage status, priority, and reminder mode of device 2. It is understood that the device 3 determined by the decision center 22 is not limited to one, and determining PC as device 3 is only an example and is not intended to limit the embodiments of this application.

[0192] For example, such as Figure 6A As shown in (a), device 2 includes a tablet, a laptop, a smart screen, and a smartwatch. The mobile phone can receive user operations and pre-configure the priorities between different types of devices. For example, the priority of the smartwatch is configured to be higher than that of the tablet, the priority of the tablet and the PC are the same, and the priority of the PC is higher than that of the smart screen.

[0193] In scenarios where a user is using the phone, such as when the phone receives a user interaction, an application is running in the foreground, or facial feature information is collected, it can be determined that the phone is in active use. In these scenarios, if the phone is in silent mode, and if... Figure 6A As shown in (b), the PC and smart screen are in ringing mode, while the watch and tablet are in silent mode. When the mobile phone receives an incoming call, the PC, which is in ringing mode and has a higher priority, is identified as device 3. That is, the PC is determined to coordinate the incoming call reminder, such as ringing the phone.

[0194] For example, the mobile phone enables ring mode and is configured to use a ringing method for notifications. While the user is using the phone, if the phone receives an incoming call, regardless of whether other devices have ring mode enabled (e.g., ...), Figure 6BAs shown, the PC and smart screen are in ring mode, while the watch and tablet are in silent mode. The phone can identify the tablet, laptop, smart screen, and smartwatch as device 3. Of course, with the phone in ring mode and the user actively using it, the phone ringing the caller's name helps to alert the user to the incoming call and prompt them to handle it. In this scenario, device 3 does not need to ring; however, the phone can instruct device 3 (tablet, laptop, smart screen, and smartwatch) to display the call notification.

[0195] For example, such as Figure 7 As shown in (a), in scenarios where a user is using the smartwatch, such as when the smartwatch receives user input or captures facial features, it can be determined that the smartwatch is in use. In this scenario, the smartwatch can be identified as device 3. Additionally, tablets, laptops, and smart screens are not considered device 3 because they do not detect user activity.

[0196] Additionally, when the phone determines that the user is wearing a smartwatch, the smartwatch has higher priority than other devices in the collaborative system, and can therefore be identified as device 3. In other examples, after the phone receives an incoming call, regardless of whether it is currently in use, it can identify the highest priority device among tablets, laptops, smart screens, and smartwatches, such as the smartwatch, as device 3.

[0197] S206, the decision center 22 sends a resonance information to the super call service 21, which includes an identifier indicating the PC.

[0198] In some embodiments, when the decision center 22 determines multiple devices 3, the resonance information may also include an identifier indicating multiple devices 3. When the determined device 3 includes a PC, the resonance information includes an identifier indicating a PC.

[0199] S207, the decision center 22 sends instruction information 2 to the Link module 23 to instruct for communication connection with the PC.

[0200] Among them, Link module 23 is the underlying module in the mobile phone that implements communication functions, and is used to establish communication connections with other devices and perform data interaction.

[0201] In some embodiments, the Link module 23 can interact with the PC via signaling according to the profile information in the static service information 1, thereby establishing a communication connection, i.e., a service link, between the PC and the mobile phone. Of course, when the resonance information indicates multiple devices 3, communication connections can be established with multiple devices 3 sequentially. During the establishment of a communication connection with each device 3, the mobile phone can send the corresponding resonance command to that device 3. The following description continues with the example of device 3 being a PC.

[0202] S208-1, Super Call Service 21 instructs Link module 23 to send a resonant command to PC.

[0203] S208-2, Link module 23 sends a resonance command to Link module 11.

[0204] In some embodiments, after a communication connection is established between the mobile phone and the PC, the Super Call Service 21 instructs the Link module 23 to send a synchronized ringing command to the PC, for example, to the Link module 11. This synchronized ringing command includes an identifier for the mobile phone, so that upon receiving the command, the PC can recognize that the mobile phone is requesting call service collaboration.

[0205] S208-3, Link module 11 sends a resonance command to Super Call Service 13.

[0206] After the Super Call Service 13 (i.e., the service provided by the PC's service layer) receives the ringing instruction, the PC can assess whether the device corresponding to the ringing instruction, such as a mobile phone, has the authority to instruct the PC to perform a collaborative task. Thus, if the mobile phone has the authority to instruct collaboration, the PC can determine to coordinate with the mobile phone to provide call notifications. In other words, after the Super Call Service 13 receives the ringing instruction, the process proceeds to S209.

[0207] S209, Super Call Service 13 sends instruction information 3 to Decision Center 12.

[0208] In some embodiments, the decision center 12 may be a software module provided by the PC service layer. The Super Caller Service 13 sends instruction message 3 to the decision center 12, instructing it to register a simultaneous ringing service for the incoming call on the mobile phone in the decision center 12. Subsequently, the decision center 12 may respond to the instruction message 3 and assess whether the coordination requested by the simultaneous ringing instruction will cause a conflict.

[0209] S210, Decision Center 12 confirms that there is no conflict in the resonance command.

[0210] In some embodiments, the decision center 12 can assess whether the coordination requested by the received resonance command will cause a conflict by detecting whether the PC meets the scenario condition 1 described above.

[0211] For example, scenario condition 1 may include the PC performing a special task, such as answering other calls, participating in multi-screen collaboration, or coordinating services requested by other devices. Another example is that scenario condition 1 may include the PC activating Do Not Disturb mode (also known as enabling the first function) and entering a corresponding Do Not Disturb period (also known as the first period). In this scenario, when the PC activates Do Not Disturb mode and the system time falls within the corresponding Do Not Disturb period, the PC blocks all call requests. These call requests include incoming call requests received by the PC itself and ringing commands received by the PC. In other words, during the Do Not Disturb period, the PC does not respond to received incoming call requests and ringing commands; for example, it does not display the incoming call interface or notifications, nor does it vibrate, ring, or ring. Of course, the PC can record received call requests, and after the system time changes from the Do Not Disturb period to a non-Do Not Disturb period, the PC can display the call requests received during the Do Not Disturb period through a notification. Additionally, during the Do Not Disturb period, the PC can also respond to user instructions to display a blocking message by displaying the call requests received during the Do Not Disturb period through a notification. Alternatively, during the Do Not Disturb period, if the PC receives a user's instruction to turn off Do Not Disturb mode, it can also display call requests received during the Do Not Disturb period via a notification.

[0212] As another example, scenario condition 1 may include the PC using application 1 (i.e., the first application), where application 1 is an application with a higher priority than the call service. When the decision center 12 recognizes that application 1 is running in the foreground, it determines that application 1 is being used.

[0213] Thus, after the PC receives the ringing command, the Super Calling Service 13 registers the ringing service with the decision center 12. After the ringing service is registered, if the decision center 12 detects that the PC meets any of the preset scenario condition 1, it determines that the ringing command is conflicting, and the PC will not continue to respond to the ringing command. If the decision center 12 detects that the PC does not meet the preset scenario condition 1, it determines that the ringing command is not conflicting, and the process proceeds to S211.

[0214] S211, the decision center 12 sends instruction information 4 to the super call service 13 to notify that the evaluation result is non-conflicting.

[0215] S212, Super Call Service 13 sends instruction information 5 to the call UI, instructing the call interface UI to be pulled up.

[0216] In some embodiments, before the call UI pulls up the call interface UI, a local do-not-disturb policy can be used to further determine whether the PC can coordinate to provide call notification. For example, the local do-not-disturb policy can check whether the device identifier corresponding to the mobile phone is included in the preset device list 1 on the PC. The device list 1 records the device identifier, and the electronic device indicated by the device identifier does not have the permission to instruct the PC to perform call service coordination tasks.

[0217] Understandably, the aforementioned local do-not-disturb strategy can achieve device-level blocking of co-oscillation commands, while the aforementioned do-not-disturb mode can achieve time-level blocking of co-oscillation commands.

[0218] In other possible embodiments, if the PC does not include a decision center 12, the method provided in this embodiment may not include S209-S211. After S208-3, that is, after the Super Call Service 13 determines that it has received the simultaneous ringing instruction, the process proceeds to S212. In S212, before the call UI pulls up the call interface UI, it can also detect whether the PC meets the pre-configured scenario condition 1. If it is determined that the PC does not meet scenario condition 1 and is not restricted by the local do-not-disturb policy, the process proceeds to S213.

[0219] S213, the call UI confirms that it does not conflict with the local do-not-disturb policy.

[0220] S214, the call UI displays the incoming call interface.

[0221] In some embodiments, the PC can provide call notifications while the caller ID is displayed. In some examples, the PC can provide call notifications according to its own configured notification method. In other embodiments, the PC can obtain the phone's static service information before providing call notifications. When the phone's static service information indicates that the phone is in use, call notifications are provided by simply displaying the caller ID. Furthermore, the caller ID can be a display specifically for incoming calls, or it can be an interface displaying call notifications.

[0222] For example, such as Figure 6A As shown in (b), the collaborative system includes mobile phones, PCs, tablets, smartwatches, and smart screens. When a user is using a mobile phone, the mobile phone, tablet, and smartwatch are all in silent mode (that is, the pre-configured incoming call notification method is silent notification), while the PC and smart screen are in ring mode. The PC and smart screen in ring mode can also be referred to as the fifth device.

[0223] Furthermore, the PC has higher priority than the smart screen. In this scenario, after the mobile phone receives an incoming call (referred to as a third call request), it sends a ringing command to the PC (see S208-1 to S208-3), that is, it sends the fifth message. After the PC receives the ringing command, it determines that the ringing command does not conflict (see S209 to S211), that is, the PC determines that the third condition is not met. Then, the PC will provide an incoming call reminder according to the pre-configured reminder method (e.g., ringing, vibration, ringing). For example, if the PC is pre-configured to ring, the PC will start ringing.

[0224] In addition, the third condition mentioned above may include at least one of the following: (1) running a first application in the foreground, the first application being an application with higher priority than the call service. (2) executing a first task, the first task including a collaborative task and a call task. (3) activating a first function, the first function being used to instruct the blocking of all incoming call requests during a first time period; the first device is included in the first list preset in the fifth device.

[0225] In other possible embodiments, such as Figure 6B As shown, the collaborative system includes a mobile phone, PC, tablet, smartwatch, and smart screen. The mobile phone is in ring mode and configured to ring for notifications. When the user receives an incoming call (referred to as a second call request), the phone can send a simultaneous ringing command (also known as a fourth message) to the smartwatch, tablet, laptop, and smart screen respectively. This simultaneous ringing command includes an indicator to display a notification. After receiving the simultaneous ringing command, the smartwatch, tablet, laptop, and smart screen determine that the commands do not conflict and then display a notification for the incoming call. Simultaneously, the mobile phone will also ring when it receives an incoming call.

[0226] In other words, under the second condition—that is, when the user is using the phone and receives a second incoming call request—if the phone's pre-configured call alert method is vibration and / or ringing, the phone will respond to the second incoming call request by alerting the user according to the corresponding call alert method. Additionally, other devices in the collaborative system besides the phone (i.e., the second device) can display the call notification. It is understandable that in this scenario, the second device will not ring or vibrate, regardless of whether its pre-configured call alert method is vibration and / or ringing.

[0227] In other embodiments, when multiple devices 3 are involved, such as a tablet, a smart screen, a laptop, and a smartwatch, the mobile phone can send resonance commands to each device 3 sequentially according to priority, until one device 3 coordinates to perform the call reminder. For example, the smartwatch has the highest priority, so the mobile phone sends a resonance command to the smartwatch first (see S207, S208-1, S208-2, and S208-3 for the implementation process). If the smartwatch determines that the resonance command does not conflict and pulls up the caller ID interface (see S209 to S214 above for the implementation process), then the smartwatch sends resonance response information 1 to the mobile phone to notify the mobile phone that the smartwatch has started to coordinate to perform the call reminder. After receiving resonance response information 1, the mobile phone will not send a resonance command to the next device 3. If the smartwatch determines that the resonance command conflicts, then the smartwatch sends resonance response information 2 to the mobile phone to notify the mobile phone that the smartwatch cannot coordinate to perform the call reminder. After the phone receives the resonance response information 2, it determines that the tablet's priority is lower than the smartwatch but higher than other devices. Then, the phone continues to send resonance commands to the tablet. Similarly, the tablet can determine whether to send resonance response information 1 or 2 back to the phone based on whether the resonance command conflicts. In this way, the phone can also determine whether to send the resonance command to the next device 3.

[0228] In other embodiments, when there are multiple devices 3, a synchronous vibration command can be sent to all devices 3 to instruct all devices 3 to coordinate to provide call reminders.

[0229] For example, such as Figure 7 As shown in (b), the mobile phone, PC, smart screen, and smartwatch all have ring mode enabled and are configured with ringing as the notification method. The tablet is in silent mode. While the user is using the smartwatch, if the mobile phone receives an incoming call (e.g., a fourth call request), the phone can ring. Additionally, the mobile phone can send a synchronized ring command to the smartwatch. Upon receiving the synchronized ring command, the smartwatch determines that the commands do not conflict and then begins to ring.

[0230] Additionally, in the above scenarios, the user's device is a tablet, and the mobile phone can also send a vibration command to the tablet to instruct it to ring. In the same scenario, the user's device is a smart screen, and the mobile phone can also send a vibration command to the smart screen to instruct it to ring. Finally, in the same scenario, the user's device is a laptop, and the mobile phone can also send a vibration command to the laptop to instruct it to ring.

[0231] In other words, in the collaborative system, the device used by the user, besides the mobile phone, can be referred to as the seventh device. While the wearable device (i.e., the third device) in the collaborative system is being worn, and the user is using the seventh device, if the third device and the seventh device are not the same device, the mobile phone can send a simultaneous ringing command to both the third and seventh devices respectively. In some embodiments, the mobile phone can send the commands according to the priority order of the third and seventh devices. For example, if the seventh device has a higher priority than the third device, then the simultaneous ringing command (referred to as the first message) is sent to the seventh device first. Under the fourth condition, the seventh device can send a first response message to the mobile phone (i.e., the first device) to instruct the seventh device to reject the simultaneous ringing command. For example, the fourth condition is satisfied when the first application is running in the foreground on the seventh device, and the first application has a higher priority than the call service; the fourth condition is satisfied when the seventh device performs a first task, which includes a collaborative task and a call task; the fourth condition is satisfied when the seventh device activates a first function, which is used to indicate that all incoming call requests are blocked during a first time period; and the fourth condition is satisfied when the first device is included in the first list of the seventh device.

[0232] After receiving the first response message, the mobile phone continues to send a ringing command (referred to as the second message) to the third device. Additionally, other devices in the collaborative system besides the first, third, and seventh devices can be referred to as the eighth device. After the first device receives the fourth incoming call request, it can also instruct the eighth device to display an incoming call notification for that fourth request.

[0233] In other embodiments, such as Figure 8 As shown, the mobile phone, PC, smart screen, and smartwatch all have ring mode enabled, and the notification method is set to ring. The tablet is in silent mode. When the user is using the smartwatch, the mobile phone will ring upon receiving an incoming call. Additionally, the mobile phone can send a synchronized ring command to the smartwatch. After the smartwatch receives the synchronized ring command and confirms that the commands do not conflict, the smartwatch will respond to the synchronized ring command and ring. Furthermore, the mobile phone can instruct the PC, smart screen, and tablet to display incoming call notifications.

[0234] Afterwards, the PC can receive instructions from the user to answer or hang up the call. Taking the instruction to answer as an example, the process can proceed to S215.

[0235] S215-1, The call UI instructs the Link module 11 to send an answer command to the mobile phone.

[0236] In some embodiments, the PC's call UI can notify the Super Call Service 13 that it has received a user instruction to answer the call. Then, the Super Call Service 13 sends the answer instruction to the mobile phone via the Link module 11.

[0237] S215-2, Link module 11 sends an answer command to Link module 23.

[0238] S215-3, Link module 23 sends an answer command to Super Caller Service 21.

[0239] In some embodiments, Link module 11 sends an answer instruction to Super Call service 21 via Link module 23. This allows the PC to receive the instruction to answer the call and synchronize it to the mobile phone. After Super Call service 21 on the mobile phone receives the answer instruction, the process proceeds to S216.

[0240] S216, Super Caller Service 21 receives and processes call data.

[0241] S217-1, Super Caller Service 21 instructs Link module 23 to send status change information to PC.

[0242] S217-2, Link module 23 sends status change information to Link module 11.

[0243] S217-3, Link module 11 sends status change information to Super Call Service 13 to indicate that the call status has been changed to "in answering".

[0244] In some embodiments, after the PC's Super Call Service 13 receives the status change information, the process proceeds to S218.

[0245] S218, Super Call Service 13 sends a refresh command to the call UI.

[0246] S219, the call UI changes to the incoming call interface.

[0247] In some embodiments, the call UI can be changed from the incoming call interface to the incoming call answering interface, which is used to indicate that the PC is cooperating in answering the incoming call corresponding to the mobile phone.

[0248] In some embodiments, when device 3 is a smart screen, if the smart screen does not have the Super Call function enabled or does not have Do Not Disturb mode enabled, it will not respond to any ringing commands sent by any device. If the smart screen only has the call stream routing function of the Super Call function enabled, then the smart screen can only route calls; that is, it does not support actively answering / hanging up calls through the smart screen, but it can display call reminders. If the smart screen has the Super Call function enabled, then the smart screen, similar to a PC, can coordinate call reminders and answer calls, etc.

[0249] This application also provides a chip system that can be applied to the electronic devices described in the foregoing embodiments. For example... Figure 9 As shown, the chip system includes at least one processor 2201 and at least one interface circuit 2202. The processor 2201 may be a processor in the aforementioned electronic device. The processor 2201 and the interface circuit 2202 are interconnected via a circuit. The processor 2201 can receive and execute computer instructions from the memory of the aforementioned electronic device through the interface circuit 2202. When the computer instructions are executed by the processor 2201, the electronic device can perform the various steps in the above embodiments. Of course, the chip system may also include other discrete components, and this application embodiment does not specifically limit this.

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

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

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

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

Claims

1. A call reminder system, the system comprising a first device, and further comprising two or more second devices, characterized in that, When the first device and the two or more second devices meet the first condition, the first device receives the first call request, wherein the first condition includes a screen-off state; In response to the first incoming call request, the third device among the two or more second devices and the first device provide an incoming call reminder, and the fourth device among the two or more second devices, other than the third device, displays an incoming call notification but does not provide vibration and / or ringing reminders. The third device is a wearable device and is in a wearable state. The incoming call reminder method pre-configured on the fourth device is vibration and / or ringing. In response to a user answering an incoming call through the third device, the third device instructs the first device to receive and process the call data corresponding to the first incoming call request. The first device instructs the third device to display an interface indicating that an incoming call is being answered.

2. The system according to claim 1, characterized in that, If the first device meets the second condition, the first device receives the second incoming call request. The second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state. When the incoming call reminder mode of the first device is pre-configured as vibration and / or ringing, in response to the second incoming call request, the first device provides a reminder according to the corresponding incoming call reminder mode, and the two or more second devices display the incoming call notification without providing vibration and / or ringing reminders.

3. The system according to claim 1, characterized in that, If the first device meets the second condition, the first device receives the third incoming call request. The second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state. When the incoming call reminder mode of the first device is set to silent notification, in response to the third incoming call request, the fifth device among the two or more second devices will provide an incoming call reminder; the incoming call reminder mode of the fifth device is ringing and / or vibrating.

4. The system according to claim 3, characterized in that, When there are multiple fifth devices, the fifth device among the two or more second devices may provide call reminders, including: the sixth device with the highest priority among the multiple fifth devices may provide call reminders.

5. The system according to claim 3, characterized in that, Before the fifth device sends an incoming call reminder, the fifth device determines that the third condition is not met; The third condition includes any one of the following: The first application runs in the foreground, and this first application has a higher priority than the call service. Perform the first task, which includes a collaborative task and a communication task; Enable the first function, which is used to indicate that all incoming call requests are blocked during a first time period. The first device is included in the first list pre-set in the fifth device.

6. The system according to claim 1, characterized in that, If the first device meets the first condition and the seventh device among the two or more second devices meets the second condition, the first device receives the fourth incoming call request. The second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state. In response to the fourth incoming call request, the first device and the seventh device provide an incoming call notification.

7. The system according to claim 1, characterized in that, If the first device meets the first condition and the seventh device among the two or more second devices meets the second condition, the first device receives the fourth incoming call request. The second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state. In response to the fourth incoming call request, the first device, the third device, and the seventh device provide an incoming call notification.

8. The system according to claim 7, characterized in that, In response to the fourth incoming call request, an eighth device, other than the seventh and third devices, displays an incoming call notification.

9. The system according to any one of claims 1-8, characterized in that, The third device is a smartwatch or Bluetooth headset.

10. The system according to claim 1, characterized in that, If the first device meets the first condition and the seventh device among the two or more second devices meets the second condition, the first device receives the fourth incoming call request. The second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state. In response to the fourth incoming call request, the first device provides an incoming call notification; When the priority of the seventh device is higher than that of the third device, the first device sends a first message to the seventh device, the first message being used to instruct the seventh device to provide a call reminder for the fourth call request; Under the fourth condition, the seventh device sends a first response message to the first device to indicate that it will refuse to provide call reminders for the fourth incoming call request. Specifically, the fourth condition is met when the seventh device is running a first application in the foreground, and the first application has a higher priority than call services; the fourth condition is met when the seventh device is performing a first task, which includes collaborative tasks and call tasks; the fourth condition is met when the seventh device activates a first function, which indicates that all incoming call requests will be blocked within a first time period; and the fourth condition is met when the first device is included in the first list of the seventh device. In response to the first response information, the first device sends a second message to the third device, the second message being used to instruct the third device to provide a call reminder for the fourth call request; The third device provides call notifications.

11. A method for reminding incoming calls, characterized in that, Applied to a first device, the first device being a system as described in any one of claims 1-10, the method comprises: The first device receives the first incoming call request; When the first device and the two or more second devices all meet the first condition, the first device sends third information to the third device among the two or more second devices to instruct the third device to provide a call reminder for the first call request, wherein the third device is a wearable device and the third device is in a wearable state, and the first condition includes a screen-off state. The first device sends a fourth message to the fourth device, which instructs the fourth device to display an incoming call notification and not to vibrate and / or ring. The fourth device is a device other than the third device among the two or more second devices, and the incoming call notification method pre-configured in the fourth device is vibration and / or ring. In response to a user answering an incoming call through the third device, the third device instructs the first device to receive and process the call data corresponding to the first incoming call request. The first device instructs the third device to display an interface indicating that an incoming call is being answered.

12. The method according to claim 11, characterized in that, The method further includes: The first device receives the second incoming call request; If the first device meets the second condition and the pre-configured incoming call notification method is vibration and / or ringing, the first device sends a fourth message to the second device to instruct the second device to display the incoming call notification and not to provide vibration and / or ringing notification; the second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state; When the pre-configured incoming call reminder method is vibration and / or ringing, the first device responds to the second incoming call request by using the vibration and / or ringing to provide a reminder.

13. The method according to claim 11, characterized in that, The method further includes: The first device receives a third incoming call request; When the first device meets the second condition and the pre-configured incoming call reminder method is silent notification, a fifth message is sent to the fifth device among the two or more second devices. The fifth message is used to instruct the fifth device to provide an incoming call reminder. The pre-configured incoming call reminder method of the fifth device is ringing and / or vibrating. The second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state.

14. The method according to claim 13, characterized in that, When there are multiple fifth devices, sending the fifth information to the fifth device among the two or more second devices includes: the first device sending the fifth information to the sixth device with the highest priority among the multiple fifth devices.

15. The method according to claim 11, characterized in that, The method further includes: The first device received the fourth incoming call request; If the first device meets the first condition and the seventh device among the two or more second devices meets the second condition, a first message is sent to the seventh device to instruct the seventh device to provide a call reminder. The second condition includes: detecting user facial features, receiving user operation, or being in a screen-on state.

16. The method according to claim 15, characterized in that, The method further includes: The first device receives a first response message sent by the seventh device, the first response message being used to instruct the seventh device to refuse to provide a call reminder for the fourth call request; The first device sends a second message to the third device, the second message being used to instruct the third device to provide a call reminder in response to the fourth call request.

17. An electronic device, characterized in that, An electronic device includes one or more processors and a memory; the memory is coupled to the processor and is used to store computer program code, the computer program code including computer instructions, wherein when the one or more processors execute the computer instructions, the one or more processors are used to perform the method as described in any one of claims 11-16.

18. A computer storage medium, characterized in that, Includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 11-16.

19. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 11-16.

Images