A call notification system, method, electronic device, storage medium, and program product.

Abstract

This application discloses an incoming call notification system and electronic device, relating to the field of communications, which can improve the intelligence level of incoming call notifications and enhance user experience. The incoming call notification system includes a first device and a second device, wherein the number of first devices is one or more. The second device is used to receive incoming call requests. When a third device exists among the first devices that meets a first preset condition, the third device is used to respond to the incoming call request and notify the user of the incoming call using a preset incoming call notification method. The first preset condition includes at least one of the following: screen on state, input state, and output state. When a third device exists among the first and second devices, a fourth device among the first devices that does not meet the first preset condition is used to mute the incoming call notification.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a call notification system and an electronic device. Background Technology

[0002] With the advancement of electronic technology, terminal devices have evolved into various types, including mobile phones, tablets, computers, and watches.

[0003] Multiple types of terminal devices can establish a device trust ring by logging into the same account to facilitate collaborative work. For example, when one terminal device in the device trust ring receives an incoming call, other terminal devices in the same device trust ring can simultaneously receive a call notification. Taking a device trust ring that includes a mobile phone, tablet, and watch as an example, the mobile phone is set to ring for call notifications, while the tablet and watch are set to vibrate. When the mobile phone receives an incoming call, it rings, and the tablet and watch also vibrate.

[0004] It can be seen that in this type of call notification scheme, when one terminal device in the device trust ring receives an incoming call, other terminal devices will send call notifications indiscriminately, resulting in a low level of intelligence and affecting the user experience. Summary of the Invention

[0005] This application provides a call notification system and electronic device, which are highly intelligent, applicable to a wide range of scenarios, and offer a good user experience.

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

[0007] In a first aspect, a call notification system is provided, comprising a first device and a second device, wherein the number of first devices is one or more. The second device is used to receive call requests. When a third device exists among the first devices that meets a first preset condition, the third device is used to respond to the call request and notify the call via a preset call notification method. The first preset condition includes at least one of the following: screen on state, input state, and output state. When a third device exists among the first and second devices, a fourth device among the first devices that does not meet the first preset condition is used to mute the call notification.

[0008] Based on this scheme, if the third device meets the first preset condition, it indicates that the third device is in use. When the second device receives an incoming call request, the third device will notify the user using its preset call notification method. Other devices in the first device will mute the call notification. This ensures that the user is promptly informed of incoming calls while minimizing the disruption caused by call notifications, improving the intelligence of call notifications, and enhancing the user experience.

[0009] In one possible design, if no third device meets the first preset condition in the first and second devices, and the second device's preset call notification method is any one of ringing, vibration, or ringing, the first device is also used to silence the call notification. Based on this scheme, if no device meets the first preset condition in the call notification system, it means that no device is currently in use. In this case, if the second device receiving the call request is set to any one of ringing, vibration, or ringing as its call notification method, the user can be promptly notified of the call from the second device, therefore the first device silences the notification. This ensures that the user is promptly informed of the call while minimizing the disturbance caused by the call notification, thereby improving the intelligence of the call notification and the user experience.

[0010] In one possible design, if no third device that meets the first preset condition exists between the first and second devices, and the preset call notification method in the second device is silent, the first device is also used to notify the user of incoming calls using the preset call notification method in the first device. Based on this scheme, it can be ensured that the user can be notified of incoming calls in a timely manner.

[0011] In one possible design, the first device is further configured to determine whether it meets a second preset condition before sending an incoming call notification. If so, it will not send a notification. The second preset condition includes at least one of the following: Do Not Disturb mode, or Collaboration mode. Do Not Disturb mode indicates that the corresponding device is in Do Not Disturb mode, the device identifier of the device initiating the incoming call request is not in the Do Not Disturb mode whitelist, and the incoming call request conforms to the Do Not Disturb mode's Do Not Disturb rules. Collaboration mode includes at least one of the following: Call mode, or Multi-screen Collaboration mode. Based on this solution, the disturbance of incoming call notifications to users can be reduced, and the intelligence level of incoming call notifications and user experience can be improved.

[0012] In one possible design, the first devices are connected via a short-range communication network. The second devices are connected via a short-range communication network. The first and second devices are also connected via a short-range communication network. This scheme helps reduce the impact of network latency on the collaborative work of devices within the device trust loop, improving the timeliness of collaborative work.

[0013] In one possible design, when either the first device or the second device receives the first operation, both devices are further configured to stop sending incoming call notifications. The first operation is either an answering or rejecting operation related to the incoming call notification. Based on this scheme, after the user handles the call on the second device, other devices in the incoming call notification system will simultaneously cancel sending call notifications. The synchronization cancellation process has minimal delay, thus preventing other devices from continuing to send call notifications due to network latency or other reasons after the user has handled the call on the second device. This reduces the disturbance of incoming call notifications to the user and improves the user experience.

[0014] In one possible design, incoming call notifications also include displaying an incoming call interface. This interface includes a first control and a second control; answering the call is done via the first control, and rejecting the call is done via the second control. This approach allows users to intuitively manage incoming call notifications, thus improving the user experience.

[0015] Secondly, a method for notifying incoming calls is provided, applied to the incoming call notification system as described in the first aspect. The method includes: in response to receiving a first signaling instruction, each first device acquires static service information of each device in the incoming call notification system. The first signaling instruction is sent by a second device to each first device in response to receiving an incoming call request, and is used to instruct the first device to perform an incoming call notification. The static service information includes usage status information and a preset incoming call notification method, whereby the usage status information indicates whether the corresponding device meets a first preset condition. When a third device among the first devices meets the first preset condition, the third device performs an incoming call notification using the preset incoming call notification method. When a third device among the first and second devices meets the first preset condition, a fourth device among the first devices that does not meet the first preset condition silently performs an incoming call notification.

[0016] Based on this scheme, if the third device meets the first preset condition, it indicates that the third device is in use. When the second device receives an incoming call request, the third device will notify the user using its preset call notification method. Other devices in the first device will mute the call notification. This ensures that the user is promptly informed of incoming calls while minimizing the disruption caused by call notifications, improving the intelligence of call notifications, and enhancing the user experience.

[0017] In one possible design, the method further includes: when no third device meets the first preset condition in the first and second devices, and the preset call notification method in the second device is any one of ringing, vibration, or ringing, the first device silently notifies the user of the incoming call. Based on this scheme, when no device meets the first preset condition in the call notification system, it indicates that no device is currently in use. In this case, if the second device receiving the call request is set to any one of ringing, vibration, or ringing as its call notification method, the user can be promptly notified of the call from the second device, thus the first device silences the notification. This ensures that the user is promptly informed of the incoming call while minimizing the disturbance caused by the call notification, thereby improving the intelligence of the call notification and the user experience.

[0018] In one possible design, if no third device that meets the first preset condition exists between the first and second devices, and the preset call notification method in the second device is silent, the first device will notify the user of the incoming call using the preset call notification method in the first device. Based on this solution, it can be ensured that the user can be informed of incoming calls in a timely manner.

[0019] In one possible design, before the first device sends an incoming call notification, the method further includes: the first device determining whether it meets a second preset condition; if so, it does not send an incoming call notification. The second preset condition includes at least one of the following: Do Not Disturb mode, Collaboration mode. Do Not Disturb mode indicates that the corresponding device is in Do Not Disturb mode, the device identifier of the device initiating the incoming call request is not in the whitelist of Do Not Disturb mode, and the incoming call request conforms to the Do Not Disturb rules of Do Not Disturb mode. Collaboration mode includes at least one of the following: Call state, Multi-screen collaboration state. Based on this solution, the disturbance of incoming call notifications to users can be reduced, and the intelligence level of incoming call notifications and user experience can be improved.

[0020] Thirdly, an electronic device is provided, comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories store computer instructions. When the one or more processors execute the computer instructions, the electronic device causes to perform a call notification method as described in any of the second aspects.

[0021] Fourthly, a chip system is provided, the chip including processing circuitry and an interface. The processing circuitry is used to retrieve and execute a computer program stored in a storage medium to perform an incoming call notification method as described in any of the second aspects.

[0022] Fifthly, a computer-readable storage medium is provided, the computer-readable storage medium including computer instructions that, when executed, perform a call notification method as described in any of the second aspects.

[0023] Sixthly, a computer program product is provided, the computer program product including instructions that, when the computer program product is run on a computer, enable the computer to execute a call notification method as described in any of the second aspects according to the instructions.

[0024] It should be understood that the technical features of the technical solutions provided in the third, fourth, fifth and sixth aspects mentioned above can all correspond to the call notification methods provided in the second aspect and its possible designs, so the beneficial effects that can be achieved are similar, and will not be repeated here. Attached Figure Description

[0025] Figure 1 A schematic diagram illustrating a method for establishing a device trust loop between a mobile phone and a tablet, provided in an embodiment of this application;

[0026] Figure 2 This is a schematic diagram of a device trust ring;

[0027] Figure 3 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0028] Figure 4 This application provides a schematic diagram of the software architecture of a terminal device.

[0029] Figure 5 This is a schematic diagram illustrating a method for synchronizing static service information provided in an embodiment of this application;

[0030] Figure 6 This is a schematic diagram of a method for call synchronization provided in an embodiment of this application;

[0031] Figure 7 A flowchart illustrating an incoming call notification method provided in this application embodiment;

[0032] Figure 8 A schematic diagram illustrating a tablet notifying users of an incoming call via a call UI, provided as an embodiment of this application;

[0033] Figure 9 A schematic diagram of an incoming call scenario provided in an embodiment of this application;

[0034] Figure 10 A schematic diagram illustrating yet another incoming call scenario provided in an embodiment of this application;

[0035] Figure 11 A schematic diagram illustrating yet another incoming call scenario provided in an embodiment of this application;

[0036] Figure 12 A schematic diagram illustrating yet another incoming call notification method provided in an embodiment of this application;

[0037] Figure 13A flowchart illustrating yet another incoming call notification method provided in this application embodiment;

[0038] Figure 14 A schematic diagram illustrating yet another incoming call scenario provided in an embodiment of this application;

[0039] Figure 15 A schematic diagram of an incoming call notification system provided in an embodiment of this application;

[0040] Figure 16 A schematic diagram illustrating the composition of an electronic device provided in an embodiment of this application;

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

[0042] In this application's embodiments, terms such as "first," "second," and "third" are used to distinguish different objects, not to limit a specific order. Furthermore, words such as "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application's embodiments should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0043] To facilitate understanding of the embodiments of this application, the background technology of the embodiments of this application will be introduced first.

[0044] This application provides a method for receiving incoming calls, applied to terminal devices within a device trust ring. The device trust ring includes multiple terminal devices that can collaboratively provide services such as synchronized incoming call notifications.

[0045] In this embodiment of the application, for multiple terminal devices to establish a device trust loop, each terminal device needs to simultaneously meet the following conditions:

[0046] 1. All terminal devices are connected via a near field communication (NFC) network.

[0047] Compared to connecting individual terminal devices via a wide area network, connecting them via a near-field communication network results in lower network latency and higher collaborative efficiency.

[0048] For example, the device trust ring includes terminal device 1, terminal device 2, and terminal device 3. After receiving an incoming call, terminal device 1 notifies terminal devices 2 and 3 via a near-field communication network (NFC) to notify them of the incoming call. When a user answers or rejects an incoming call on any terminal device, such as terminal device 2, terminal device 2 notifies terminal devices 1 and 3 via the NFC to stop notifying them of the incoming call. This reduces the synchronization latency between the terminal devices and improves the user experience.

[0049] 2. All terminal devices log in with the same system account.

[0050] In this embodiment, the system account can be an account provided by the operating system of the terminal device. For example, both terminal device A and terminal device B are running operating system S, and the account provided by operating system S is the system account. The account provided by operating system S can be an account registered by the user on the cloud server of operating system S.

[0051] It should be noted that the operating system S of terminal device A and the operating system S of terminal device B can be different versions. That is to say, the version number of the operating system S of terminal device A and the version number of the operating system S of terminal device B can be different.

[0052] In addition, in this embodiment, the operating system of the terminal device can be an operating system independently developed by the terminal device manufacturer, or it can be an operating system based on an existing operating system (such as...). An operating system developed using a kernel.

[0053] Based on the above description, it can be seen that for terminal device 1 and terminal device 2 connected through a near-field communication network, if terminal device 1 can verify that the system account it logs in to is the same as the system account logged in to terminal device 2, then terminal device 1 can establish a device trust ring with terminal device 2.

[0054] The following example uses a mobile phone as terminal device 1 and a tablet as terminal device 2 to illustrate a method for establishing a device trust loop between the mobile phone and the tablet. The mobile phone and tablet are connected via a near-field communication network.

[0055] Please refer to Figure 1 This is a schematic diagram illustrating a method for establishing a device trust loop between a mobile phone and a tablet, provided in an embodiment of this application. Figure 1 As shown, the method includes S101-S107.

[0056] S101. The mobile phone encrypts the broadcast message based on the public key of the first system account.

[0057] In this embodiment, the first system account is the system account logged in by the mobile phone. The broadcast message can be the first system account. That is, S101 above can be: the mobile phone encrypts the first system account using the public key of the first system account. It is understood that the broadcast message can also be other data; this is only an illustrative example and does not mean that this application is limited to this.

[0058] In this embodiment, each system account can correspond to a public key used to encrypt information related to the system account. The public key corresponding to the system account can be stored in the cloud server where the system account is registered. For example, the public key of the first system account can be stored in the cloud server where the first system account is registered. Before executing S101, the mobile phone can first obtain the public key of the first system account from the cloud server where the first system account is registered.

[0059] S102. The mobile phone broadcasts a message through the near-field communication network.

[0060] In some embodiments, the mobile phone can broadcast messages in real time via a near-field communication network.

[0061] In other embodiments, the mobile phone may also broadcast messages via the near-field communication network when a specific scenario is identified. For example, the specific scenario may include: the mobile phone changing from a stationary state to a moving state; the mobile phone's location changing; or a new terminal device being added to the near-field communication network.

[0062] S103. After receiving the broadcast message, the tablet obtains the private key corresponding to the second system account.

[0063] The second system account is the system account logged into on the tablet. In this embodiment, each system account can correspond to a private key used to decrypt information related to the system account. That is, the public and private keys of the same system account match each other; data encrypted with the public key can be decrypted using the corresponding system account's private key. The private key corresponding to the system account can be stored in the cloud server where the system account is registered. For example, the private key of the second system account can be stored in the cloud server where the second system account is registered.

[0064] In some embodiments, after receiving a broadcast message, the tablet can obtain the private key of the second system account from the cloud server that registered the second system account.

[0065] In other embodiments, after logging into the second system account, the tablet can also obtain the private key corresponding to the second system account from the cloud server that registered the second system account and store the private key in a trusted storage location. Thus, upon receiving a broadcast message, the tablet can retrieve the private key of the second system account from the aforementioned trusted storage location.

[0066] It should be noted that when logging out of the secondary system account on the tablet, the private key of the secondary system account stored in the aforementioned trusted storage location can be deleted.

[0067] S104. The tablet decrypts broadcast messages using the private key of the second system account.

[0068] Understandably, successful decryption means the private key of the second system account matches the public key of the first system account. In other words, the second system account and the first system account belong to the same system. Decryption failure means the private key of the second system account does not match the public key of the first system account. In other words, the second system account and the first system account do not belong to the same system.

[0069] S105. If decryption is successful, the tablet will add the phone to the first trusted device list.

[0070] S106. The tablet sends a first feedback message to the phone. This first feedback message indicates that the tablet has successfully decrypted the broadcast message.

[0071] If the tablet can successfully decrypt the broadcast message, it indicates that the tablet and the phone are logged into the same system account. Since the tablet and phone are connected via a near-field communication network, they meet the prerequisite for establishing a device trust ring. In this embodiment, the terminal devices in the first device trust list are those in the same device trust ring as the tablet. When the tablet adds the phone to the first device trust list, it means the tablet is adding the phone to the device trust ring where the tablet is located.

[0072] It should be noted that before the tablet sends the first feedback message to the phone, it can encrypt the first feedback message using the public key of the second system account. When the phone receives the encrypted first feedback message, it can decrypt it using the private key of the first system account, thus improving the security of the data interaction process.

[0073] In some embodiments, if decryption fails, the tablet can send a second feedback message to the phone, which indicates that the tablet failed to decrypt the broadcast message.

[0074] In other embodiments, if decryption fails, the tablet may not respond to broadcast messages, that is, it may not send any messages to the phone.

[0075] S107. After receiving the first feedback message, the mobile phone adds the tablet to the second trusted device list.

[0076] The terminal devices in the second device trust list are those that are in the same device trust ring as the mobile phone. When the mobile phone adds the tablet to the second device trust list, it means that the mobile phone is adding the tablet to the device trust ring that the mobile phone belongs to.

[0077] Through the above steps S101-S107, mobile phones and tablets can be placed in the same device trust ring.

[0078] It should be noted that within the same device trust ring where the aforementioned mobile phones and tablets reside, the terminal devices can include all terminal devices in the first device trust list and all terminal devices in the second device trust list. In other words, the terminal devices in the first trust device list and the second device trust list are the same.

[0079] When within the same device trust ring, mobile phones and tablets can provide synchronized call notification services. For example, when a mobile phone receives an incoming call, both the phone and tablet will simultaneously initiate call notifications, such as vibration, ringing, or displaying a notification interface. This allows users to easily choose which terminal to answer the call on.

[0080] It is understandable that when there are a large number of terminal devices in the device trust ring, indiscriminately sending call notifications to each terminal device can disturb users.

[0081] For example, please refer to Figure 2 This is a schematic diagram of a device trust ring. For example... Figure 2 As shown, the device trust ring includes a mobile phone, tablet, and watch. In traditional call notification schemes, when a mobile phone receives an incoming call, the mobile phone, tablet, and watch all send a notification. For example, the call notification method for the mobile phone, tablet, and watch is a ringtone. When the mobile phone receives a call while playing a movie, all three devices will ring to notify the user. However, in this scenario, since the user is watching a movie on their mobile phone, the ringtone is sufficient to inform the user of the incoming call. Therefore, the ringtones from the tablet and watch are redundant and can be disruptive, affecting the user experience.

[0082] It can be seen that traditional call notification solutions have limited applicability, low intelligence, and negatively impact user experience.

[0083] To address the aforementioned issues, this application provides a method for intelligently notifying users of incoming calls, thereby meeting user needs in various scenarios and improving the user experience.

[0084] In this embodiment, the terminal device can be a portable terminal with communication capabilities, such as a mobile phone, tablet computer, wearable device (e.g., smartwatch), in-vehicle device, etc. Exemplary embodiments of the portable terminal include, but are not limited to, carrying... Alternatively, it can be a portable terminal with another operating system. The aforementioned portable terminal can also be a laptop computer, such as one with a touch-sensitive surface (e.g., a touch panel). It should also be understood that in some other embodiments, the aforementioned terminal can also be a desktop computer with a touch-sensitive surface (e.g., a touch panel). As an example, please refer to... Figure 3 This is a structural schematic diagram of a terminal device 300 provided in an embodiment of this application. The call notification methods provided in this application can all be applied to, for example... Figure 3 The terminal device 300 shown.

[0085] like Figure 3 As shown, the terminal device 300 may include a processor 301, a display screen 303, a communication module 302, etc.

[0086] The processor 301 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, memory, a video stream codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors 301.

[0087] The controller can serve as the nerve center and command center of the terminal device 300. The controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.

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

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

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

[0091] Display screen 303 is used to display images, video streams, etc.

[0092] The communication module 302 may include antenna 1, antenna 2, mobile communication module 302A, and / or wireless communication module 302B. Taking an example where the communication module 302 simultaneously includes antenna 1, antenna 2, mobile communication module 302A, and wireless communication module 302B.

[0093] The wireless communication function of the terminal device 300 can be implemented through antenna 1, antenna 2, mobile communication module 302A, wireless communication module 302B, modem processor, and baseband processor.

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

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

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

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

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

[0099] like Figure 3 As shown, in some implementations, the terminal device 300 may also include an external memory interface 310, an internal memory 304, a universal serial bus (USB) interface, a charging management module 312, a power management module 313, a battery 314, an audio module 306, a speaker 306A, a receiver 306B, a microphone 306C, a headphone jack 306D, a sensor module 305, buttons 309, a motor, an indicator 308, a camera 307, and a subscriber identification module (SIM) card interface, etc.

[0100] The charging management module 312 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 312 receives charging input from the wired charger via a USB interface 311. In some wireless charging embodiments, the charging management module 312 receives wireless charging input via the wireless charging coil of the terminal device 300. While charging the battery 314, the charging management module 312 can also supply power to the terminal device 300 via the power management module 313.

[0101] The power management module 313 connects the battery 314, the charging management module 312, and the processor 301. The power management module 313 receives input from the battery 314 and / or the charging management module 312, providing power to the processor 301, internal memory 304, external memory, display screen 303, camera 307, and wireless communication module 302B. The power management module 313 can also monitor parameters such as battery 314 capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 313 may be located within the processor 301. In other embodiments, the power management module 313 and the charging management module 312 may be located in the same device.

[0102] The external storage interface 310 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the terminal device 300. The external storage card communicates with the processor 301 through the external storage interface 310 to perform data storage functions. For example, music, video streams, and other files can be saved on the external storage card.

[0103] Internal memory 304 can be used to store computer executable program code, which includes instructions. Processor 301 executes various functional applications and data processing of terminal device 300 by running the instructions stored in internal memory 304.

[0104] The internal memory 304 may also store one or more computer programs corresponding to the incoming call notification method provided in the embodiments of this application.

[0105] Terminal device 300 can implement audio functions such as music playback and recording through audio module 306, speaker 306A, receiver 306B, microphone 306C, headphone jack 306D, and application processor 301.

[0106] Buttons 309 include a power button, volume buttons, etc. Buttons 309 can be mechanical buttons or touch-sensitive buttons. Terminal device 300 can receive input from buttons 309 and generate key signal inputs related to user settings and function control of the terminal device 300.

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

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

[0109] The sensor module 305 in the terminal device 300 may include components such as touch sensors, pressure sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, accelerometers, distance sensors, proximity sensors, ambient light sensors, fingerprint sensors, temperature sensors, and bone conduction sensors to achieve the function of sensing and / or acquiring different signals.

[0110] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the terminal device 300. In other embodiments, the terminal device 300 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0111] The above has been approved. Figure 3 The hardware structure of the terminal device provided in the embodiments of this application is introduced below, using a layered architecture. Taking the system as an example, the software architecture of the terminal device provided in the embodiments of this application is illustrated.

[0112] Please refer to Figure 4 This is a schematic diagram of the software architecture of a terminal device provided in an embodiment of this application. Figure 4As shown, the software architecture of the terminal device 300 can be divided into three layers, from top to bottom: application layer 401, service layer 402, and device connection layer 403.

[0113] like Figure 4 As shown, application layer 401 may include applications such as an Incall UI program, a contacts application, a contacts storage application, and a contacts synchronization application. For example, when a terminal device receives an incoming call, it can launch the Incall UI program to display the Incall UI, prompting the user to answer the call.

[0114] Service layer 402 provides an application programming interface (API) and programming framework for the application in application layer 401. The service layer includes some predefined functions.

[0115] The programming framework may include the Telecom AOSP (Android Open-Source Project) call framework. The Telecom AOSP call framework can be used to manage audio and video calls on terminal devices, including SIM-based (Subscriber Identity Module) calls (e.g., using the Telephony framework) and VoIP calls provided by the ConnectionService API implementer.

[0116] In addition, the API can also include APIs for calling the Telephony cellular service, APIs for calling the Profile information 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.

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

[0118] 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. The Link module is used for communication connectivity between devices, etc.

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

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

[0121] 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 access control, security, and transmission capabilities.

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

[0123] For example, the tablet's service layer can read or update the tablet's trusted device list by calling Device Profile. The tablet's trusted device list includes the identifiers of other terminal devices in the same device trust ring as the tablet, as well as static service information.

[0124] Static service information may include profile information, device usage status information, and call notification methods, etc.

[0125] Profile information may include the profile types supported by the corresponding terminal device, such as supported phonebook access profile (PBAP), hands-free profile (HFP), and object push profile (OPP). This profile information may also include profile version information supported by the corresponding terminal device.

[0126] Device usage status information indicates whether the corresponding terminal device is currently in a working state. As an example, a terminal being in a working state can include at least one of the following: screen-on state, input state, output state, etc. The input state indicates that the terminal device is receiving information input, which can be achieved through keyboard input, mouse input, touch input, audio / video data input, etc. The output state indicates that the terminal device is outputting information, which can be achieved through audio / video output, display screen output, etc.

[0127] Incoming call notification methods can include silent notification, ringing, vibration, and vibration and ringing (ringing). Among them, silent notification can be: displaying the incoming call notification interface in silence.

[0128] Terminal devices within the same device trust ring can establish near-field communication (NFC) connections through their respective Link modules. These NFC connections enable data exchange between the devices. For example, when a mobile phone and a tablet are in the same device trust ring, the mobile phone can access the tablet's static service information, and vice versa.

[0129] Terminal devices in a device trust ring can synchronize static service information from other terminal devices in real time or periodically. This allows other terminal devices to be promptly notified of changes to their profiles, usage status, or call notification methods, thus improving the efficiency of collaborative work among them.

[0130] The following example, using a device trust ring that includes a mobile phone and a tablet, illustrates the process of synchronizing static service information between the aforementioned terminal devices.

[0131] Please refer to Figure 5 This is a schematic diagram illustrating a method for synchronizing static service information provided in an embodiment of this application. Figure 5 As shown, the scheme includes the following S501-S505.

[0132] S501, The mobile phone's Super Call Service sends a first instruction to the mobile phone's Link module, which instructs the mobile phone's Link module to send the mobile phone's static service information to the tablet's Link module.

[0133] As mentioned above Figure 4 According to the relevant instructions, in terminal devices, the Link module is used to realize communication connectivity with other terminal devices. Mobile phones and tablets connect via a near-field communication (NFC) network; that is, the Link modules of the mobile phone and the tablet are connected via the NFC network. Mobile phones and tablets can exchange data through their respective Link modules.

[0134] S502, In response to receiving the first instruction, the Link module of the mobile phone obtains the static service information of the mobile phone.

[0135] For example, the Link module of a mobile phone can obtain static service information of the mobile phone from the phone's memory.

[0136] S503: The phone's Link module sends the phone's static service information to the tablet's Link module.

[0137] S504, the tablet's Link module sends static service information from the phone to the tablet's Device Profile.

[0138] As mentioned above Figure 4 The Device Profile is located in the tablet's device connection layer and serves as a service interface that can be invoked by the service layer. For example, the tablet's service layer can read or update the tablet's trusted device list by calling the Device Profile. The tablet's trusted device list includes the identifiers and static service information of other terminal devices within the same device trust ring as the tablet.

[0139] The S505 tablet's Device Profile updates the tablet's list of trusted devices based on the phone's static service information.

[0140] In other words, the tablet's Device Profile adds the received static service information from the phone to the tablet's trusted device list and deletes the static service information of the phone that was originally stored in the tablet's trusted device list, thereby ensuring the timeliness of the trusted device list.

[0141] When a phone receives an incoming call, it can synchronize the call to the tablet based on the tablet's static service information in the phone's device trust list. Please refer to [link / reference]. Figure 6 This is a schematic diagram illustrating a method for call synchronization provided in an embodiment of this application. Figure 6 As shown, the incoming call synchronization process may include the following steps S601-S613.

[0142] S601. In response to receiving an incoming call, the phone's Super Call service sends a first request to the phone's Device Profile. The first request is used to query the phone's trusted device list. This trusted device list includes the tablet identifier and the tablet's static service information.

[0143] Please refer to the above. Figure 4 The related explanations state that the Super Call service on a mobile phone is a service provided by the service layer within the phone. The Device Profile service on a mobile phone is a service provided by the device connectivity layer within the phone.

[0144] S602. In response to receiving the first request, the phone's Device Profile sends the phone's list of trusted devices to the phone's Super Call service.

[0145] S603, the mobile phone's Super Call service sends a tablet identifier and a second request to the mobile phone's decision center. This second request is used to request registration and / or subscription to the tablet's resonance service in the decision center.

[0146] Please refer to the above. Figure 4 According to the relevant explanation, the decision-making center of a mobile phone can be located in the super terminal center of the mobile phone.

[0147] For example, the mobile phone's decision center can register and / or subscribe to the tablet's simultaneous ringing service based on the tablet's identifier. After successful registration and / or subscription, the tablet can receive the simultaneous ringing signaling sent by the mobile phone after receiving a call, so as to synchronously notify the user of the incoming call.

[0148] S604. In response to receiving the second request, the mobile phone's decision center registers and / or subscribes to the tablet's resonance service.

[0149] S605: The phone's decision center sends a ringing signal to the phone's Super Call service. This ringing signal may include the tablet's identifier.

[0150] S606: The mobile phone's Super Call Service generates a simultaneous ringing signaling message based on the simultaneous ringing information. This simultaneous ringing signaling message is used to instruct the tablet and mobile phone to simultaneously notify the user of incoming calls.

[0151] The simultaneous ringing signaling can include a mobile phone identifier, so that when the tablet receives the simultaneous ringing signaling, it can identify the mobile phone and request the tablet to simultaneously notify the incoming call.

[0152] S607, the phone's Super Call service will send the same ring signal to the phone's Link module.

[0153] S608, the phone's Link module sends the same ring signal to the tablet's Link module.

[0154] S609, the tablet's Link module will send the same ring signaling to the tablet's Super Call service.

[0155] S610, the tablet's Super Calling service sends a third request to the tablet's decision center based on the co-ring signaling. This third request is used to request registration and / or subscription to the phone's co-ring service in the tablet's decision center.

[0156] For example, the tablet's decision center can register and / or subscribe to a mobile phone's simultaneous ringing service based on the mobile phone identifier in the simultaneous ringing signaling. After registering and / or subscribing to the mobile phone's simultaneous ringing service, the tablet can synchronously send call notifications based on the simultaneous ringing signaling sent by the mobile phone after receiving a call.

[0157] S611. In response to receiving a third request, the tablet's decision center registers and / or subscribes to the phone's resonance service.

[0158] S612, The tablet's decision center sends a first notification to the tablet's Super Call service, which indicates that the tablet's decision center has successfully registered and / or subscribed to the phone's simultaneous ringing service.

[0159] S613. In response to receiving the first notification, the tablet's Super Call service will send a synchronous signaling message to the tablet's decision center.

[0160] The above S601-S613, using a device trust ring including a mobile phone and a tablet as an example, describes the process of a mobile phone synchronizing incoming calls to a tablet. In some embodiments, the device trust ring may also include other terminal devices, such as PCs, watches, headphones, etc. The process of a mobile phone synchronizing incoming calls to these terminal devices is similar to the above S601-S613, and will not be repeated here.

[0161] After receiving the co-oscillation signaling, the decision center of the tablet can determine the method of incoming call notification through the incoming call notification method provided in the embodiments of this application, so as to perform the incoming call notification.

[0162] The incoming call notification method provided in the embodiments of this application is described below. The incoming call notification method provided in the embodiments of this application can be applied to any first device in a device trust ring. The device trust ring may include a first device and a second device. The second device is the terminal device that receives the incoming call, and the first device is any other terminal device in the device trust ring besides the second device. The number of first devices can be one or more.

[0163] For example, the first device may include a tablet, computer, watch, earphones, etc., and the second device may be a mobile phone, a tablet with calling function, a watch with calling function, etc. After receiving an incoming call, the second device will send the synchronous signaling to the decision center of the first device through the incoming call synchronization process of S601-S613 described above.

[0164] It should be noted that when the second device receives an incoming call, it will notify the caller through a pre-set call notification method.

[0165] In some embodiments, the pre-set call notification method may be that, before the terminal device sends a call notification, the terminal device receives an operation instruction from the user and sets the call notification method according to the user's operation instruction.

[0166] In other words, the pre-set call notification method can be the call notification method that the user sets locally on the terminal device before the terminal device sends a call notification. Taking a tablet as an example, if the user sets the tablet's call notification method to ring before the tablet sends a call notification, then the pre-set call notification method for the tablet is ringing.

[0167] In other embodiments, the pre-set call notification method may also be the call notification method defaulted to by the terminal device's operating system.

[0168] In the embodiments of this application, the pre-set incoming call notification method can also be referred to as the preset incoming call notification method.

[0169] Please refer to Figure 7 This is a flowchart illustrating a call notification method provided in an embodiment of this application. Figure 7 As shown, the incoming call notification method may include S701-S705. Here, S705 includes S705a and S705b.

[0170] S701, In response to the co-vibration signaling sent by the second device, obtain the static service information of each terminal device in the device trust ring.

[0171] The simultaneous ringing signaling, also known as the first signaling, is used to instruct the first device to notify of an incoming call. For details regarding the simultaneous ringing signaling, please refer to S601-S613 above; it will not be repeated here.

[0172] Taking a device comprising a tablet, a computer, and a watch as the first device, and a mobile phone as the second device, the call notification method provided in this application embodiment is applied to the tablet in the first device as an example. S701 above is as follows: The decision center of the tablet, in response to receiving a simultaneous ringing signaling message sent by the mobile phone, obtains the static service information of the computer, the static service information of the watch, and the static service information of the mobile phone.

[0173] Please refer to Figure 4 The relevant documentation describes static service information. Static service information for a terminal device may include the device's profile, device usage status, and call notification methods, among other things.

[0174] Device usage status information indicates whether the corresponding terminal device is currently in a working state. As an example, a terminal device being in a working state can include at least one of the following: screen-on state, input state, output state, etc. The input state indicates that the terminal device is receiving information input, which can be achieved through keyboard input, mouse input, touch input, audio / video data input, etc. The output state indicates that the terminal device is outputting information, which can be achieved through audio / video output, display screen output, etc.

[0175] Incoming call notification methods can include silent notification, ringing, vibration, and vibration and ringing (ringing). Silent notification can be: displaying the incoming call notification interface while silent. That is, a silent notification will display the incoming call notification interface but will not ring, vibrate, or ring.

[0176] In this embodiment of the application, the device being in a working state can also be referred to as the device meeting the first preset condition.

[0177] In some embodiments, the tablet's decision center can obtain static service information for the computer, watch, and mobile phone by querying the tablet's trusted device list. Referring to S505 above, the tablet's trusted device list stores static service information for terminal devices within the same device trust ring as the tablet.

[0178] In other embodiments, the decision center of the tablet can also obtain static service information of the computer, the watch, and the mobile phone by performing the steps S501-S505 described above.

[0179] S702. Based on the static service information of each terminal device, determine whether there is a terminal device in the device trust ring that is in a working state. If it exists, and the terminal device in the working state includes itself, execute S703a; if it exists, and the terminal device in the working state does not include itself, execute S703b; if it does not exist, execute S703c.

[0180] In this embodiment of the application, when there is a device among the first device and the second device that meets the first preset condition, the device that meets the first preset condition can be referred to as the third device. When there is a device among the first device and the second device that meets the first preset condition, the device in the first device that does not meet the first preset condition can be referred to as the fourth device.

[0181] Continuing with the example in S701, where the first device includes a tablet, a computer, and a watch, the call notification method provided in this embodiment is applied to the tablet within the first device. Exemplarily, the tablet's decision center determines whether a terminal device in a working state exists in the device trust ring based on the static service information of the computer, the watch, and the mobile phone. If the tablet itself is in a working state, S703a is executed; if at least one of the computer, watch, and mobile phone is in a working state, but the tablet itself is not in a working state, S703b is executed; if none exists, S703c is executed.

[0182] S703a, The incoming call is notified via a pre-set call notification method.

[0183] Using the example from S701 again, and assuming the tablet's pre-set incoming call notification method is ringing, if the tablet's decision center determines that the tablet is in working condition, it sends a ringing instruction to the tablet's call UI; the tablet's call UI will then display the incoming call interface UI based on this ringing instruction and ring to notify of the incoming call. The incoming call interface UI can also be referred to as the call UI.

[0184] S703b, Silent notification of incoming call.

[0185] Using the example from S701 again, if the tablet's decision center determines that there is a working terminal device in the device trust ring, and the tablet itself is not working, it sends a mute instruction to the tablet's call UI; the tablet's call UI will display the incoming call interface UI according to the mute instruction and mute the incoming call.

[0186] Incoming calls can be silenced via banner notifications, bubble notifications, or UI notifications, etc. Please refer to [link / reference]. Figure 8 This is a schematic diagram illustrating how a tablet notifies users of an incoming call via a call UI, as provided in an embodiment of this application. Figure 8 As shown, the incoming call UI can include accept controls, reject controls, and text displaying relevant call information. This text can include the caller's number, caller's location, the name of the calling device, and remarks, etc. No specific limitations are specified here.

[0187] In this embodiment, the accept control can also be referred to as the first control, and the reject control can also be referred to as the second control. The user's operation on the first control can be an answering operation, and the user's operation on the second control can be a rejecting operation.

[0188] It should be noted that in this case, the tablet's pre-set call notification methods might be ringing, vibrating, or simply ringing. The tablet will not send call notifications through the pre-set methods.

[0189] This section explains S703a and S703b in the context of a specific incoming call scenario. Please refer to [link / reference]. Figure 9 This is a schematic diagram illustrating an incoming call scenario provided in an embodiment of this application. In this scenario, the device trust ring includes a mobile phone, tablet, computer, and watch, where the mobile phone is the terminal device receiving the incoming call, i.e., the second device. The tablet, computer, and watch are the first devices. The tablet is playing a movie, i.e., it is in working mode. The mobile phone, computer, and watch are not in working mode. The mobile phone and computer are preset to silent call notification mode, the tablet is preset to ring call notification mode, and the watch is preset to vibration call notification mode.

[0190] When the mobile phone receives an incoming call, it will send the same ringing signal to the computer, tablet, and watch respectively.

[0191] When the computer receives the same ring signal, it determines through S701-S702 that the tablet is in working condition and that the computer itself is not in working condition. In this case, the computer will mute the incoming call.

[0192] Upon receiving the synchronous signaling, the tablet determines that it is in a working state based on the steps S701-S702 described above. The tablet will then notify the incoming call via a pre-set call notification method, i.e., ringing the phone. For example, as follows... Figure 9 As shown, the tablet can display the incoming call UI on top of the movie being played and ring to notify the caller.

[0193] When the watch receives the same ring signal, it determines through S701-S702 that the tablet is in working condition and that it is not in working condition. In this case, the watch will mute the incoming call.

[0194] The phone itself will notify the incoming call through a pre-set call notification method, which is to silence the call.

[0195] In other words, when a phone receives an incoming call, if the tablet is active, all other devices in the device trust loop besides the tablet and phone, regardless of their pre-set call notification methods, will only silently notify the user of the call. Only the phone and tablet will notify the user of the call through their pre-set call alert methods. This ensures that users are promptly informed of incoming calls while minimizing the disruption caused by call notifications.

[0196] S703c, Method for obtaining incoming call notifications from a second device.

[0197] As mentioned above Figure 4 According to the relevant instructions, the incoming call notification method of a terminal device can be stored in the static service information of that terminal device. This incoming call notification method is the one preset by the corresponding terminal device. Terminal devices within the same device trust ring can exchange static service information based on near-field communication connections. In other words, terminal devices within the same device trust ring can obtain the preset incoming call notification method of the peer device by acquiring the peer device's static service information.

[0198] Using the example from S701 again, if the tablet's decision center determines that there is no active terminal device in the device trust ring, it can obtain the phone's incoming call notification method based on the phone's static service information. After obtaining the phone's incoming call notification method, the tablet's decision center can determine its own incoming call notification method based on the phone's method. The phone's incoming call notification method is the one pre-set by the phone.

[0199] S704. Determine the call notification method of the second device. If the call notification method of the second device is any one of vibration, ringing, or ringing, execute S705a; if the call notification method of the second device is silent, execute S705b.

[0200] S705a, Silent notification for incoming calls.

[0201] Using the example from S701, if the tablet's decision center determines that the incoming call notification method is any of vibration, ring, or ringing, it will send a mute instruction to the tablet's call UI; the tablet's call UI will then display the incoming call interface UI according to the mute instruction and mute the incoming call.

[0202] In this way, the phone's call notification is sufficient to inform the user of the incoming call, and the tablet's silent call notification can reduce the disturbance of the call notification to the user.

[0203] This section explains the S705a in the context of a specific incoming call scenario. Please refer to [link / reference]. Figure 10 This is a schematic diagram illustrating another incoming call scenario provided in an embodiment of this application. In this scenario, the device trust ring includes a mobile phone, tablet, computer, and watch, where the mobile phone is the terminal device receiving the incoming call, i.e., the second device. The tablet, computer, and watch are the first devices. None of the mobile phone, tablet, computer, or watch are in a working state. The mobile phone is pre-set to ring for incoming call notification, the computer and tablet are pre-set to ring for incoming call alerts, and the watch is pre-set to vibrate for incoming call alerts.

[0204] When the mobile phone receives an incoming call, it will send the same ringing signal to the computer, tablet, and watch respectively.

[0205] When the computer, tablet, and watch receive the same ring signal, they determine through S701-S704 that the phone, tablet, computer, and watch are not in working condition, and the phone's pre-set call notification method is ringing. Then, the computer, tablet, and watch will all mute the call notification.

[0206] The phone itself will notify the incoming call via a pre-set call notification method, that is, by ringing the phone.

[0207] In other words, when a phone receives an incoming call, if the phone, tablet, computer, and watch are all not in working order, and the phone's pre-set call notification method is ring, then all terminal devices in the device trust loop other than the phone, regardless of their pre-set call notification methods, will only silence the call. Only the phone will notify the user of the incoming call through its pre-set call alert method. This ensures that the user is promptly informed of incoming calls while minimizing the inconvenience of call notifications.

[0208] S705b: Notify the incoming call via a pre-set call notification method.

[0209] Using the example from S701, and assuming the tablet's default call notification method is ringing, if the tablet's decision center determines that the phone, tablet, computer, and watch are all not in working order, and the phone's default call notification method is silent, it will send a ringing instruction to the tablet's call UI. The tablet's call UI will then display the incoming call interface UI based on this ringing instruction and ring to notify the caller.

[0210] This section explains the S705b in the context of a specific incoming call scenario. Please refer to [link / reference]. Figure 11 This is a schematic diagram illustrating another incoming call scenario provided in an embodiment of this application. In this scenario, the device trust ring includes a mobile phone, tablet, computer, and watch, where the mobile phone is the terminal device receiving the incoming call, i.e., the second device. The tablet, computer, and watch are the first devices. The mobile phone, tablet, computer, and watch are all not in a working state. The mobile phone is preset to silent call notification, the computer and tablet are preset to ring call alerts, and the watch is preset to vibration call alerts.

[0211] When the mobile phone receives an incoming call, it will send the same ringing signal to the computer, tablet, and watch respectively.

[0212] When the computer receives the same ring signal, it determines through S701-S704 that the mobile phone, tablet, computer and watch are not in working state, and the mobile phone is set to silent call notification mode. Then the computer will notify the caller through the pre-set call notification mode, that is, ringing.

[0213] When the tablet receives the same ring signal, it determines through S701-S704 that the mobile phone, tablet, computer and watch are not in working state, and the mobile phone's preset incoming call notification method is silent. Then the tablet will notify the incoming call through the preset incoming call notification method, that is, ringing.

[0214] When the watch receives the same vibration signal, it determines through S701-S704 that the mobile phone, tablet, computer and watch are not in working state, and the mobile phone is set to silent call notification mode. Then the watch will notify the caller through the pre-set call notification mode, that is, vibration.

[0215] The phone itself will notify the incoming call through a pre-set call notification method, which is to silence the call.

[0216] In other words, when a phone receives an incoming call, if the phone, tablet, computer, and watch are all not in working order, and the phone's pre-set call notification method is silent, then all terminal devices in the device trust loop will notify the user of the incoming call through their pre-set call notification method. This ensures that the user is promptly notified of incoming calls even when the phone is silent.

[0217] When the first device receives a simultaneous ringing signal, if it is already in a call—for example, answering a call from another terminal device, making a call to another device, or engaging in multi-screen collaboration with other terminal devices—sending a call notification will interfere with the incoming call or the ongoing multi-screen collaboration. The terminal device being in a call or engaging in multi-screen collaboration can be referred to as being in a collaborative state. Both being in a call and engaging in multi-screen collaboration can be collectively referred to as being in a collaborative state.

[0218] Before step S701 above, that is, before the first device obtains the static service information of each terminal device in the device trust ring, the first device can first determine whether it is in a collaborative state, and determine whether to send an incoming call notification based on the determination result. Please refer to [link to relevant documentation]. Figure 12 This is a schematic diagram illustrating another incoming call notification method provided in an embodiment of this application. Figure 12 As shown, in Figure 7 Before S701 shown, the incoming call notification method provided in this application embodiment also includes S1201-S1202.

[0219] S1201. In response to the resonance signal sent by the second device, determine whether it is in a coordinated state. If yes, execute S1202. If no, execute S701.

[0220] S1202. If yes, then no call notification will be sent. That is, when the first device determines that it is in a collaborative state, it can choose not to send a call notification to reduce disturbance to the user. For example, the first device is a tablet. Before executing S701 above, the tablet can determine whether it is currently in a call or whether it is in multi-screen collaboration with other terminal devices. If yes, no call notification will be sent. This reduces the disturbance of incoming calls to the user and improves the user experience. It should be noted that in this embodiment, not sending a call notification is completely different from silent notification. Not sending a call notification means that the terminal device does not send a notification in any way, while silent call notifications can include banner notifications, bubble notifications, pop-up notifications, etc. In other embodiments, the terminal device can also be set to a do-not-disturb mode. Do-not-disturb mode is a working mode of the terminal device. The terminal device can receive user operation commands to enter do-not-disturb mode. When the terminal device is in do-not-disturb mode, call notifications, SMS notifications, message notifications, and other functions will be disabled.

[0221] Do Not Disturb mode allows you to set a whitelist, which can include applications, phone numbers, or identifiers of other devices. When a device is in Do Not Disturb mode, incoming call notifications, SMS notifications, or message notifications from whitelisted applications, phone numbers, or other devices will not be disabled.

[0222] Do Not Disturb mode also allows you to set Do Not Disturb rules. When a terminal device is in Do Not Disturb mode, phone numbers or incoming call notifications from the terminal device that do not meet the Do Not Disturb rules will not be disabled. For example, if the terminal device's Do Not Disturb rule includes receiving fewer than 3 calls within 5 minutes, then when the terminal device receives a call from the same terminal device for the third time within 5 minutes, an incoming call notification will be sent.

[0223] In this embodiment, after determining the method of incoming call notification, the first device can determine whether it is in Do Not Disturb mode, whether the whitelist includes the device identifier of the third device that initiated the call, and whether the incoming call from the third device complies with the Do Not Disturb rules. The device identifier of the third device can be included in the aforementioned co-ring signaling.

[0224] The first device can determine whether to send a call notification based on the judgment result, which will be explained in detail below.

[0225] Please refer to Figure 13 This is a flowchart illustrating another incoming call notification method provided in an embodiment of this application. Figure 13 As shown, in Figure 7 Before S705a and after S704, the incoming call notification method provided in this application embodiment also includes S1301-S1304.

[0226] S1301. Determine if the device is in Do Not Disturb mode. If yes, proceed to S1302. If no, proceed to S705a.

[0227] S1302. Determine whether the whitelist for Do Not Disturb mode includes the device identifier of a third device. If not, proceed to S1303. If yes, proceed to S705a.

[0228] S1303. Determine whether the incoming call from the third device complies with the Do Not Disturb rule. If yes, proceed to S1304. If no, proceed to S705a.

[0229] S1304, No call notification will be sent.

[0230] This section explains S1301-S1304 in the context of a specific incoming call scenario. Please refer to [link / reference]. Figure 14 This is a schematic diagram illustrating another incoming call scenario provided in an embodiment of this application. In this scenario, the device trust ring includes a mobile phone 1, a tablet, a computer, and a watch, where mobile phone 1 is the terminal device receiving the incoming call, i.e., the second device. The tablet, computer, and watch are the first devices. The third device sending the call to mobile phone 1 is mobile phone 2.

[0231] Phone 1, the computer, and the watch are not in Do Not Disturb mode. The tablet is playing a movie and is in Do Not Disturb mode. The tablet's Do Not Disturb whitelist does not include the identifier of the third device. The Do Not Disturb rule for the tablet is less than 3 incoming calls within 5 minutes. Phone 1's preset call notification method is ringing.

[0232] When mobile phone 1 receives the first call from mobile phone 2 within 5 minutes, it will send the same ring signal to the computer, tablet and watch respectively.

[0233] When the tablet receives the co-ring signal, it will determine that it is in Do Not Disturb mode through S1301, determine that the whitelist does not include the identifier of the third device through S1302, and determine through S1303 that the incoming call from the mobile phone 2 meets the Do Not Disturb rules, so the tablet will not send an incoming call notification for the call.

[0234] When the computer and watch receive the same ring signal, they determine through S1301 that they are not in Do Not Disturb mode. Then, the computer and watch will execute S705a, that is, mute the incoming call notification.

[0235] The phone itself will notify the incoming call via a pre-set call notification method, that is, by ringing the phone.

[0236] In other words, when a phone receives an incoming call, if the tablet is in Do Not Disturb mode and the third device is not on the whitelist, and the call also meets the Do Not Disturb rules, then the tablet will not send an incoming call notification, regardless of its pre-set call notification method. This reduces the disruption caused by incoming call notifications and improves the intelligence of the notification process.

[0237] It is understandable that S1301-S1304 can also be executed before S705b and after S704. In this case, S1301-S1304 and S705a in the related description should all be replaced with S705b. Similarly, S1301-S1304 can also be executed before S703a and after S702. In this case, S1301-S1304 and S705a in the related description should all be replaced with S703a. Finally, S1301-S1304 can also be executed before S703b and after S702. In this case, S1301-S1304 and S705a in the related description should all be replaced with S703b.

[0238] The above describes the incoming call notification method provided in the embodiments of this application. It is understood that, in conjunction with the above description, the incoming call notification method provided in the embodiments of this application can ensure that users are promptly notified of incoming calls while minimizing disturbance to users, exhibiting a high degree of intelligence and wide applicability.

[0239] The incoming call notification system provided in the embodiments of this application is described below.

[0240] The incoming call notification system provided in this application includes a first device and a second device, wherein the number of first devices is one or more. The second device is used to receive incoming call requests. When a third device exists among the first devices that meets a first preset condition, the third device is used to respond to the incoming call request and notify the user of the incoming call using a preset incoming call notification method. The first preset condition includes at least one of the following: screen on, input state, and output state. When a third device exists among the first and second devices, a fourth device among the first devices that does not meet the first preset condition is used to mute the incoming call notification.

[0241] Please refer to Figure 15 This is a schematic diagram of a call notification system provided in an embodiment of this application. For ease of illustration, Figure 15 The second device is a mobile phone, and the first device includes computers, tablets, and watches. It is understood that the first and second devices can also be other terminal devices; this is merely illustrative and does not imply that this application is limited thereto.

[0242] in addition, Figure 15In the first preset condition, the phone's default call notification method is ring. The computer meets the first preset condition; its default call notification method is ring. Tablets and watches do not meet the first preset condition.

[0243] like Figure 15 As shown, after receiving an incoming call request, the mobile phone will ring to notify the user. In the first device, a computer that meets the first preset condition will ring to notify the user. However, tablets and watches, regardless of their preset call notification methods, will only send call notifications silently. This ensures that users are promptly informed of incoming calls while minimizing the disturbance caused by call notifications, improving the intelligence of call notifications and enhancing the user experience.

[0244] The specific functions of the first and second devices can be found in the description of the incoming call notification method above, and will not be repeated here.

[0245] Please refer to Figure 16 This is a schematic diagram illustrating the composition of an electronic device 1600 provided in an embodiment of this application. The electronic device 1600 can be any of the electronic devices described in the above examples; for example, the electronic device 1600 can be a mobile phone, a computer, etc. For example, as shown... Figure 16 As shown, the electronic device 1600 may include a processor 1601 and a memory 1602. The memory 1602 is used to store computer execution instructions. Exemplarily, in some embodiments, when the processor 1601 executes the instructions stored in the memory 1602, the electronic device 1600 may perform any of the functions of the electronic device in the above embodiments to implement any of the incoming call notification methods in the above examples.

[0246] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0247] Figure 17 A schematic diagram of a chip system 1700 is shown. This chip system 1700 can be installed in an electronic device, such as a mobile phone. Exemplarily, the chip system 1700 may include a processor 1701 and a communication interface 1702, used to support the electronic device in implementing the functions involved in the above embodiments. In one possible design, the chip system 1700 also includes a memory for storing necessary program instructions and data of the electronic device. This chip system can be composed of chips or may include chips and other discrete devices. It should be noted that in some implementations of this application, the communication interface 1702 may also be referred to as an interface circuit.

[0248] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0249] This application also provides a computer storage medium storing computer instructions. When the computer instructions are executed on a terminal device, the terminal device performs the aforementioned method steps to implement the methods described in the above embodiments.

[0250] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the methods described in the above embodiments.

[0251] In addition, embodiments of this application also provide an apparatus, which may specifically be a chip, component, or module. The apparatus may include a connected processor and a memory; wherein the memory is used to store computer execution instructions, and when the apparatus is running, the processor may execute the computer execution instructions stored in the memory to cause the chip to execute the methods in the above-described method embodiments.

[0252] In this application, the terminal device, computer storage medium, computer program product or chip provided in the embodiments are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0253] The foregoing primarily describes the solutions provided by the embodiments of this application from the perspective of electronic devices. To achieve the aforementioned functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0254] This application embodiment can divide the device involved into functional modules according to the above method examples. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0255] The functions, actions, operations, or steps in the above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented using software programs, they can be implemented, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or include one or more data storage devices such as servers and data centers that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0256] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A call notification system, characterized in that, The system includes a first device and a second device, wherein the number of the first devices is multiple; The second device is used to receive incoming call requests; The fifth device in the first device is used to receive a first signaling sent by the second device, the first signaling being used to indicate that the fifth device has a new incoming call; The fifth device is also used to acquire static service information of multiple devices, including the fifth device and other devices in the first device that are different from the fifth device; the static service information includes at least the usage status information and incoming call notification method of the corresponding device; the usage status information is used to indicate whether the corresponding device meets a first preset condition; the first preset condition includes at least one of the following: screen on state, input state, output state; The fifth device is also used to provide call reminders based on the static service information obtained from the multiple devices; Wherein, if the static service information of the plurality of devices indicates that at least one device meets the first preset condition, and the at least one device meeting the first preset condition includes the fifth device, the fifth device is further configured to provide call reminders through a call notification method pre-set in the fifth device; If the static service information of the plurality of devices indicates that at least one device meets the first preset condition, and the at least one device meeting the first preset condition does not include the fifth device, the fifth device is further used to provide call reminders via a silent notification. If the static service information of the multiple devices indicates that there is no device that meets the first preset condition, the fifth device is also used to provide call reminders according to the call notification method of the second device.

2. The call notification system according to claim 1, characterized in that, When the static service information of the multiple devices indicates that there is no device that meets the first preset condition, and the preset call notification method of the second device is any one of ringing, vibration, or ringing, the fifth device is also used to mute the call notification.

3. The call notification system according to claim 1, characterized in that, When the static service information of the plurality of devices indicates that there is no device that meets the first preset condition, and the preset call notification method in the second device is silent, the fifth device is further used to send a call notification through the preset call notification method in the fifth device.

4. The call notification system according to claim 1, characterized in that, The first device is also used to determine whether it meets the second preset condition before making an incoming call notification; if so, it will not make an incoming call notification. The second preset condition includes at least one of the following: Do Not Disturb mode, Collaboration mode; The Do Not Disturb status is used to indicate that the corresponding device is in Do Not Disturb mode, the device identifier of the device initiating the incoming call request is not in the whitelist of the Do Not Disturb mode, and the incoming call request conforms to the Do Not Disturb rules of the Do Not Disturb mode; The collaborative state includes at least one of the following: call state, multi-screen collaborative state.

5. The call notification system according to any one of claims 1-4, characterized in that, The preset call notification methods include: ringing, vibration, ringing, and silent.

6. The call notification system according to claim 1, characterized in that, The first devices are connected to each other via a short-range communication network; the first device and the second device are connected to each other via a short-range communication network.

7. The call notification system according to claim 6, characterized in that, When either the first device or the second device receives the first operation, the first device and the second device are further configured to stop sending incoming call notifications; wherein, the first operation is an answering operation or a rejecting operation for the incoming call notification.

8. The call notification system according to claim 7, characterized in that, The method of notifying incoming calls also includes displaying the incoming call interface; The incoming call interface includes a first control and a second control. The answering operation is an operation on the first control, and the rejecting operation is an operation on the second control.

9. A method for notifying incoming calls, characterized in that, Applied to a fifth device, said fifth device being included in the call notification system as described in any one of claims 1-8; the method includes: In response to receiving a first signaling, the fifth device obtains static service information of each device in the incoming call notification system; the first signaling is sent by the second device to the fifth device in response to receiving an incoming call request, and the first signaling is used to instruct the fifth device to perform incoming call notification; the static service information includes usage status information and a preset incoming call notification method, and the usage status information is used to indicate whether the corresponding device meets the first preset condition. The fifth device provides call reminders based on the static service information obtained from the multiple devices. Wherein, if the static service information of the plurality of devices indicates that at least one device meets the first preset condition, and the at least one device meeting the first preset condition includes the fifth device, the fifth device will provide call reminders through a call notification method pre-set in the fifth device; If the static service information of the multiple devices indicates that at least one device meets the first preset condition, and the at least one device meeting the first preset condition does not include the fifth device, the fifth device will provide a call reminder via a silent notification. If the static service information of the multiple devices indicates that there is no device that meets the first preset condition, the fifth device will send a call reminder according to the call notification method of the second device.

10. The call notification method according to claim 9, characterized in that, The method further includes: When the static service information of the multiple devices indicates that there is no device that meets the first preset condition, and the preset call notification method of the second device is any one of ringing, vibration, or ringing, the fifth device will mute the call notification.

11. The call notification method according to any one of claims 9-10, characterized in that, When the static service information of the multiple devices indicates that there is no device that meets the first preset condition, and the preset call notification method in the second device is silent, the fifth device will send a call notification through the preset call notification method in the fifth device.

12. The call notification method according to claim 9, characterized in that, Before the first device notifies the user of an incoming call, the method further includes: The first device determines whether it meets the second preset condition. If it does, it will not send a call notification. The second preset condition includes at least one of the following: Do Not Disturb mode, Collaboration mode; The Do Not Disturb status is used to indicate that the corresponding device is in Do Not Disturb mode, the device identifier of the device initiating the incoming call request is not in the whitelist of the Do Not Disturb mode, and the incoming call request conforms to the Do Not Disturb rules of the Do Not Disturb mode; The collaborative state includes at least one of the following: call state, multi-screen collaborative state.

13. An electronic device, characterized in that, The electronic device includes one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories store computer instructions. When the one or more processors execute the computer instructions, the electronic device performs the call notification method as described in any one of claims 9-12.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer instructions that, when executed, perform the call notification method as described in any one of claims 9-12.

15. A computer program product, characterized in that, The computer program product includes instructions that, when the computer program product is run on a computer, cause the computer to execute the incoming call notification method as described in any one of claims 9-12 according to the instructions.

Images