Processing method for communication service circulation among multiple devices and wearable device

Abstract

The invention provides a processing method for communication service circulation among multiple devices and a wearable device, and relates to the technical field of terminals. Through the scheme, the wearable device (such as the smart watch) can be associated with the two mobile phones at the same time, the message notification or the incoming call notification of the two mobile phones associated with the smart watch can be transferred to the smart watch, and the smart watch can display the message notification or the incoming call notification of the two mobile phones. Compared with the prior art that a smart watch can only be associated with one mobile phone, the scheme of the invention can meet the requirement that services such as conversation / notification of a dual-phone user can reach the wearable device, and the user can manage services such as message notification or incoming call notification of multiple devices through one watch without worrying about missing important transactions.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a method for processing communication service transfer between multiple devices, a wearable device, an electronic device, a communication system, and a storage medium. Background Technology

[0002] Currently, due to limitations in chip capabilities and Bluetooth functionality, wearable devices such as smartwatches and smart bracelets can only wirelessly connect and communicate with one other electronic device (such as a mobile phone) logged into a fitness and health application (APP). Taking a smartwatch as an example, after a smartwatch is paired with mobile phone 1 via Bluetooth, if mobile phone 2 requests to pair with the smartwatch via Bluetooth, the smartwatch must first disconnect from mobile phone 1 and then pair with mobile phone 2. In this scenario, the wearable device can only process (receive and display) message notifications or call notifications from a single mobile phone, which cannot meet the user's need to receive and display notifications from multiple devices through a single wearable device.

[0003] There is an urgent need for a method that can receive and display notifications from multiple devices through a single wearable device. Summary of the Invention

[0004] This application provides a method for processing communication service transfer between multiple devices, a wearable device, an electronic device, a communication system, and a storage medium, which solves the problem that the prior art cannot meet the interconnection and interoperability of wearable devices with multiple devices.

[0005] In a first aspect, this application provides a method for processing communication service transfer between multiple devices. The method includes: a wearable device establishing a Bluetooth connection with a first device; the wearable device detecting nearby available devices; the wearable device displaying a first prompt message, the first prompt message indicating that the wearable device has detected a second device and whether to associate the second device with the wearable device; the first device and the second device are both mobile phones; in response to a user's confirmation operation, the wearable device displaying a second prompt message, the second prompt message indicating that the wearable device, the first device, and the second device are associated devices with the same user account; when the first device displays a first notification, the wearable device displays the first notification; when the second device displays a second notification, the wearable device displays the second notification.

[0006] Through the multi-device communication service transfer processing method provided in the embodiments of this application, a wearable device (such as a smartwatch) can be associated with two mobile phones at the same time. Message notifications or call notifications from multiple mobile phones associated with the wearable device can be transferred to the wearable device. The wearable device can simultaneously display message notifications or call notifications from any one mobile phone, thus meeting the user's need to conveniently view and process message and call notifications from multiple mobile phones through the wearable device and improving the user experience.

[0007] In this embodiment, the wearable device, the first device, and the second device log in with the same user account. The wearable device establishes a device association relationship with the first device and the second device under the same user account.

[0008] The first notification is a message notification and / or a call notification, and the second notification is a message notification and / or a call notification.

[0009] Among them, message-type notifications can include SMS messages, app messages, calendar reminders, to-do reminders, flight travel reminders, courier reminders, alarm clock reminders, note reminders, and / or YOYO suggestion reminders.

[0010] Among them, call notifications can be either incoming call notifications or missed call notifications.

[0011] Compared to other wearable devices that can only be associated with one mobile phone, the solution provided in this application can meet the needs of dual-device users to access services such as calls and notifications on the watch. It helps users manage message notifications or call notifications from multiple devices through a single watch, without worrying about missing important matters.

[0012] In this embodiment, the wearable device can be associated with two mobile phones simultaneously, and the wearable device can receive and display message notifications or call notifications for each electronic device. The message notifications or call notifications can include both message notifications and call notifications.

[0013] With this solution, incoming call notifications, app messages in the notification bar, calendar events, to-do lists, flight schedules, package tracking, alarms, notes, and YOYO suggestions from both phones can be synced to the smartwatch. When the smartwatch receives calendar events, to-do lists, or alarms, the user can tap "Turn off" or "Remind later" on the watch side, which will also turn off or postpone the phone sync. This convenience greatly enhances the user experience.

[0014] In a possible implementation of the first aspect, the method further includes: when the wearable device displays the first notification, the wearable device also displays that the first notification is a notification from the first device; and when the wearable device displays the second notification, the wearable device also displays that the second notification is a notification from the second device.

[0015] With the above solution, when the wearable device displays the first and second notifications, it will show which device each notification comes from, making it easier for users to know the source device of each notification and improving the user experience.

[0016] In one possible implementation of the first aspect, the wearable device sets the first device as the master and the second device as the slave.

[0017] In a possible implementation of the first aspect, the method further includes: when the wearable device displays an incoming call notification from the first device, the wearable device displays an answer control, a hang-up control, and a message reply control; when the wearable device displays an incoming call notification from the second device, the wearable device displays the hang-up control and the message reply control, but does not display the answer control.

[0018] Using the above solution, when the wearable device displays a call notification from the host device, it can answer, hang up, and reply to the message. When the wearable device displays a call notification from the slave device, it can hang up and reply to the message, but it does not support answering the call.

[0019] In one possible implementation of the first aspect, if the first device or the second device receives a missed call notification but does not answer it, the first device or the second device can transfer the missed call notification to a smartwatch, and the smartwatch can display the missed call notification.

[0020] This solution allows a smartwatch to be connected to two phones simultaneously. Incoming call notifications and other tasks from multiple phones connected to the smartwatch can be routed to the smartwatch. The smartwatch can simultaneously display call notifications from any of the phones. Users can answer calls from the primary phone on the smartwatch and also receive call notifications from the secondary phone, choosing to answer the call on the secondary phone, hang up the call on the smartwatch, or reply to the call notification. This satisfies users' needs for conveniently viewing and managing call notifications from multiple phones through their smartwatch.

[0021] The solution provided in this application can be applied to the following user scenarios:

[0022] User Scenario 1: The user carries a wearable device, a master device, and a slave device.

[0023] User Scenario 2: The user carries a wearable device and a main unit, but no slave unit.

[0024] User Scenario 3: The user carries a smartwatch but does not carry the master or slave device.

[0025] User Scenario 4: The user carries a smartwatch and a slave device, but not the master device.

[0026] In user scenario 1 or 2, when the user carries both the host and the wearable device, the host and the wearable device communicate via near-field communication (NFC) based on a trust ring. If the host receives a message or call notification from the base station, it can send the notification to the wearable device via NFC, and the wearable device can display the notification. When the slave device receives a message or call notification from the base station, regardless of its location, the notification can be forwarded to the wearable device via the host and displayed there. This eliminates the need for the user to carry the slave device; they can access the notifications directly through the wearable device, improving the user experience.

[0027] In user scenarios 3 or 4, when the user is carrying a wearable device, the host and wearable device communicate in the far-field based on a trust ring, and the slave and wearable device also communicate in the far-field based on a trust ring. If the host receives a message-type notification or call-type notification from the base station, it can send the notification to the wearable device via far-field communication, and the wearable device can display the notification. When the slave receives a message-type notification or call-type notification from the base station, regardless of its location, the notification can be sent to the wearable device via far-field communication and displayed thereon. This eliminates the need for the user to carry the slave device; they can receive notifications directly from it through the wearable device, improving the user experience.

[0028] In some embodiments, when the host or slave device receives an incoming call notification, the notification can be routed to the smartwatch, where it can answer or reject the call. For example, when the host and smartwatch are in a near-field environment, such as when the user is wearing both, if the host receives an incoming call notification, the smartwatch can vibrate to alert the user. The smartwatch can then respond to the user's action by hanging up the notification or rejecting it via SMS. Furthermore, the smartwatch can also respond to the user's action by answering the host's call notification. Additionally, if the host does not answer the call notification, the missed call notification (or missed call message) can be routed to the smartwatch, where it can be displayed. This solution allows message notifications or call notifications from multiple devices associated with the smartwatch to be routed to the smartwatch, fulfilling the user's need to conveniently view and manage messages and call notifications from multiple phones through a wearable device, thus improving the user experience.

[0029] In other embodiments, when the host or slave device receives an incoming call notification, the notification can be forwarded to the smartwatch, but the smartwatch does not support answering; it can support rejecting the call. For example, when the host, slave device, and smartwatch are in a near-field environment, if the slave device receives an incoming call notification, the smartwatch can vibrate to alert the user. The smartwatch can respond to user actions by hanging up the notification, or it can reject the call via SMS. It should be noted that, due to the smartwatch's single-channel Bluetooth connection to the host, the audio of incoming calls from the slave device cannot be forwarded to the smartwatch. Therefore, the smartwatch can display a hang-up button but not an answer button. Furthermore, if the slave device does not answer an incoming call notification, the missed call notification can be forwarded to the smartwatch, where it can be displayed. This solution allows message notifications or call notifications from multiple devices associated with the smartwatch to be forwarded to the smartwatch, meeting the user's need to conveniently view and manage messages and call notifications from multiple phones through a wearable device, thus improving the user experience.

[0030] In other embodiments, when the host or slave device receives an incoming call notification, the notification is not forwarded to the smartwatch. For example, when the host / slave device and the smartwatch are in a far-field environment, if the host / slave device receives an incoming call notification, the notification will not be forwarded to the smartwatch, and the notification interface will not be displayed on the smartwatch. If the host / slave device does not answer an incoming call, the notification can be forwarded to the smartwatch, where it can be displayed. This solution allows message notifications or call notifications from multiple devices associated with the smartwatch to be forwarded to the smartwatch, meeting the user's need to conveniently view and manage messages and call notifications from multiple phones via wearable devices, thus improving the user experience.

[0031] In a possible implementation of the first aspect, the wearable device and the second device establish a trust ring device association relationship based on the first user account, including: the wearable device searching for other devices with the same login account as the wearable device; if the wearable device finds the second device, displaying a first prompt message to prompt the user to associate the second device with the wearable device; and in response to the user's confirmation operation, the wearable device and the second device establish a trust ring device association relationship.

[0032] Through the solution proposed in this application, tasks such as message notifications or call notifications from multiple devices associated with a smartwatch can be transferred to the smartwatch. For example, two mobile phones associated with a smartwatch can transfer call notifications, voice notes, currently playing music, alarm clock information, and / or sports and health data to the user's smartwatch.

[0033] In a possible implementation of the first aspect, the method further includes: the wearable device engaging in near-field communication with the first device, and the first device engaging in near-field communication with the second device. In this case, the step of the wearable device displaying the first notification when the first device displays a first notification includes: when the first device displays the first notification and the first notification is a message notification, the wearable device displays the message notification; when the first device displays the first notification and the first notification is an incoming call notification, the wearable device displays the incoming call notification. Furthermore, the step of the wearable device displaying the second notification when the second device displays a second notification includes: when the second device displays the second notification and the second notification is a message notification, the wearable device displays the message notification; when the second device displays the second notification and the second notification is an incoming call notification, the wearable device displays the incoming call notification.

[0034] With the above solution, when the wearable device communicates with the first device (master) in the near field and the watch communicates with the second device (slave) in the near field, the wearable device can display message notifications synchronously with the master / slave, and can also display incoming call notifications synchronously with the master / slave, thus improving the user experience.

[0035] In a possible implementation of the first aspect, the method further includes: the wearable device communicating with the first device in the near field, and the first device communicating with the second device in the far field; when the second device displays the second notification and the second notification is an incoming call notification, the wearable device does not display the incoming call notification.

[0036] When the wearable device communicates with a first device in the near field and the first device communicates with a second device in the far field, the step of displaying the first notification on the wearable device when the first device displays the first notification includes: when the first device displays the first notification and the first notification is a message notification, the wearable device displays the message notification; when the first device displays the first notification and the first notification is an incoming call notification, the wearable device displays the incoming call notification. Furthermore, the step of displaying the second notification on the wearable device when the second device displays the second notification includes: when the second device displays the second notification and the second notification is a message notification, the wearable device displays the message notification; when the second device displays the second notification and the second notification is a missed call notification, the wearable device displays the missed call notification.

[0037] Through the above solution, when the wearable device communicates with the first device (master) in the near field and the watch communicates with the second device (slave) in the far field, the wearable device can display message notifications synchronously with the master / slave, and the wearable device can display incoming call notifications synchronously with the master, thus improving the user experience.

[0038] In a possible implementation of the first aspect, the method further includes: the wearable device communicating with the first device in a far-field communication, and the wearable device communicating with the second device in a far-field communication; when the first device displays the first notification and the first notification is an incoming call notification, the wearable device does not display the incoming call notification; when the second device displays the second notification and the second notification is an incoming call notification, the wearable device does not display the incoming call notification.

[0039] In the case of far-field communication between the wearable device and a first device, and between the wearable device and a second device, the step of displaying the first notification on the wearable device when the first device displays a first notification includes: when the first device displays the first notification and the first notification is a message notification, the wearable device displays the message notification; when the first device displays the first notification and the first notification is a missed call notification, the wearable device displays the missed call notification. Furthermore, the step of displaying the second notification on the wearable device when the second device displays a second notification includes: when the second device displays the second notification and the second notification is a message notification, the wearable device displays the message notification; when the second device displays the second notification and the second notification is a missed call notification, the wearable device displays the missed call notification.

[0040] With the above solution, when the wearable device communicates with the first device (master) in the far field and the watch communicates with the second device (slave) in the far field, the wearable device can synchronously display message notifications with the master / slave, thus improving the user experience.

[0041] In a possible implementation of the first aspect, when the wearable device communicates with the first device in the near field and the first device communicates with the second device in the near field, message notifications, incoming call notifications, or missed call notifications from the first device are directly forwarded to the wearable device, and message notifications, incoming call notifications, or missed call notifications from the second device are forwarded by the first device and then forwarded to the wearable device.

[0042] Through the above solution, notifications from the first device and message or call notifications from the second device can be transferred to the wearable device and displayed there, making it convenient for users to view.

[0043] In a possible implementation of the first aspect, when the wearable device communicates with the first device in the near field and the first device communicates with the second device in the far field, message notifications, incoming call notifications, or missed call notifications from the first device are directly forwarded to the wearable device, and message notifications or missed call notifications from the second device are forwarded by the first device to the wearable device.

[0044] In a possible implementation of the first aspect, when the wearable device communicates with the first device and with the second device in a far-field communication, message notifications or missed call notifications from the first device are directly forwarded to the wearable device, and message notifications or missed call notifications from the second device are also directly forwarded to the wearable device.

[0045] This solution allows message notifications or call notifications from multiple devices associated with a smartwatch to be routed to the smartwatch, fulfilling users' desire to conveniently view and manage message and call notifications from multiple phones through wearable devices and improving the user experience.

[0046] In a possible implementation of the first aspect, after the wearable device establishes a device association relationship under the same user account with the first device and the second device respectively, the method further includes: the wearable device obtaining a first distance value between the wearable device and the first device; and the wearable device establishing a trust ring communication link among the wearable device, the first device and the second device based on the first distance value.

[0047] In a possible implementation of the first aspect, the wearable device establishes a trust loop communication link among the wearable device, the first device, and the second device based on the first distance value, including: when the first distance value is less than a first threshold, the wearable device establishes a trust loop near-field communication link with the first device, and the wearable device instructs the first device to establish a trust loop communication link with the second device; when the first distance value is greater than or equal to the first threshold, the wearable device establishes far-field communication links with the first device and the second device respectively.

[0048] The first threshold can be the maximum distance at which the wearable device and the first device can communicate in the near field (such as Bluetooth or Wi-Fi).

[0049] In a possible implementation of the first aspect, the wearable device instructs the first device to establish a trust loop communication link with the second device, comprising: the wearable device acquiring a second distance value between the wearable device and the second device; if the second distance value is less than a first threshold, the wearable device instructs the first device to establish a trust loop near-field communication link with the second device; if the second distance value is greater than or equal to the first threshold, the wearable device instructs the first device to establish a trust loop far-field communication link with the second device.

[0050] In a possible implementation of the first aspect, establishing the trust ring near-field communication link includes: establishing the trust ring near-field communication link via short-range wireless communication; the short-range wireless communication method includes Bluetooth communication or high-fidelity Wi-Fi communication. Establishing the trust ring far-field communication link includes: establishing the trust ring far-field communication link via cloud services.

[0051] This solution allows wearable devices to be connected to two mobile phones simultaneously, establishing a trust loop communication link between the wearable device, the two mobile phones, and so on. As a result, message notifications or call notifications from multiple mobile phones connected to the smartwatch can be transferred to the smartwatch. The smartwatch can simultaneously display message notifications or call notifications from any one of the mobile phones, thus meeting the user's need to conveniently view and process message and call notifications from multiple mobile phones through the wearable device.

[0052] In a possible implementation of the first aspect, the wearable device establishes a device association relationship with the first device and the second device under the same user account, including: the wearable device and the first device pairing via Bluetooth with the same first user account; after the wearable device and the first device are connected via Bluetooth pairing, the wearable device and the second device establish a trust ring device association relationship based on the first user account.

[0053] In a possible implementation of the first aspect, the method further includes: the wearable device setting the first device as the host and the second device as the slave. Through this solution, in some cases, message notifications or call notifications from the slave device can be forwarded to the wearable device via the host, thereby enabling the management of message notifications or call notifications from multiple devices through a single watch. Users do not need to worry about missing important events, thus improving the user experience.

[0054] In a possible implementation of the first aspect, after the wearable device sets the first device as a host and the second device as a slave, the method further includes: the wearable device assigning a first data forwarding permission to the first device having a host role; wherein the second data forwarding permission includes the first device having a host role and the second device having a slave role, and when a communication link is established between the second device and the first device, the second device is allowed to send message-type notifications or call-type notifications from the second device to the first device having a host role.

[0055] In a possible implementation of the first aspect, after the wearable device sets the first device as a host and the second device as a slave, the method further includes: the wearable device assigning a second data forwarding permission to the second device with the slave role. The first data forwarding permission includes the first device as a host and the second device as a slave; when a near-field communication link is established between the first device and the wearable device, the first device is permitted to forward message-type notifications or call-type notifications from the second device with the slave role to the wearable device.

[0056] Secondly, this application provides a method for processing communication service transfer between multiple devices, including: establishing a device association relationship under the same user account for a first device, a wearable device, and a second device; wherein the user accounts logged in by the wearable device, the first device, and the second device are the same, and the first device and the second device are mobile phones respectively; the first device and the wearable device perform near-field communication; the first device receives a first notification from the network side, displays the first notification, and sends the first notification to the wearable device through a near-field communication link, the first notification including a message notification or an incoming call notification; the first device receives a second notification from the second device, and forwards the second notification to the wearable device through a near-field communication link, the second notification being a message notification or an incoming call notification received by the second device from the network side.

[0057] The message notifications include SMS messages, application messages, calendar reminders, to-do reminders, flight reminders, express delivery reminders, alarm reminders, note reminders, and / or YOYO suggestion reminders; the call notifications are incoming call notifications or missed call notifications.

[0058] In a possible implementation of the second aspect, the method further includes: the first device communicating with the wearable device in the far field; the first device receiving a third notification from the network side and sending the third notification to the wearable device via the far field communication link, the third notification including a message notification.

[0059] In a possible implementation of the second aspect, the first device receiving a second notification from the second device includes: the first device and the second device engaging in near-field communication; the first device receiving the second notification from the second device via a near-field communication link, wherein the second notification is a message notification, an incoming call notification, or a missed call notification; or, the first device and the second device engaging in far-field communication; the first device receiving the second notification from the second device via a far-field communication link, wherein the second notification is a message notification or a missed call notification.

[0060] In a possible implementation of the second aspect, the method further includes: the first device receiving a first data forwarding permission assigned by the wearable device;

[0061] The first data forwarding permission includes the first device as the host and the second device as the slave. When a near-field communication link is established between the first device and the wearable device, the first device is allowed to forward message-type notifications or call-type notifications from the second device, which has the slave role, to the wearable device.

[0062] In a possible implementation of the second aspect, the method further includes: the first device receiving first indication information sent by the wearable device; in response to the first indication information, the first device establishing a trust loop near-field communication link with the wearable device; or, the first device receiving second indication information sent by the wearable device; in response to the second indication information, the first device establishing a trust loop communication link with the second device; or, the first device receiving third indication information sent by the wearable device; in response to the third indication information, the first device establishing a trust loop far-field communication link with the wearable device.

[0063] Thirdly, this application provides a method for processing communication service transfer between multiple devices, including: establishing a device association relationship under the same user account for a second device, a wearable device, and a first device, wherein the first device and the second device are both mobile phones; wherein the user accounts logged in by the wearable device, the first device, and the second device are the same; the second device receives a second notification, which is a message notification or a call notification sent by the network side; when the second device and the first device establish a trust ring near-field communication link, the second device sends the message notification or call notification to the wearable device, which then forwards it to the wearable device; when the second device and the first device establish a trust ring far-field communication link, the second device sends the message notification to the wearable device, which then forwards it to the wearable device; when the second device and the wearable device establish a trust ring far-field communication link, the second device directly sends the message notification to the wearable device.

[0064] The message notifications include SMS messages, application messages, calendar reminders, to-do reminders, flight reminders, express delivery reminders, alarm reminders, note reminders, and / or YOYO suggestion reminders; the call notifications are incoming call notifications or missed call notifications.

[0065] In a possible implementation of the third aspect, the method further includes: the second device receiving a second data forwarding permission; wherein the second data forwarding permission includes the first device as a host and the second device as a slave, and when a communication link is established between the second device and the first device, the second device is allowed to send message-type notifications or call-type notifications from the second device with the slave role to the first device.

[0066] In a possible implementation of the third aspect, the method further includes: the second device receiving fourth indication information; in response to the fourth indication information, the second device establishing a trust loop near-field communication link with the first device; or, the second device receiving fifth indication information; in response to the fifth indication information, the second device establishing a trust loop far-field communication link with the first device; or, the second device receiving sixth indication information; in response to the sixth indication information, the second device establishing a trust loop far-field communication link with the wearable device.

[0067] Fourthly, this application provides a wearable device, the wearable device comprising: one or more processors, and a memory; the memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors calling the computer instructions to cause the wearable device to perform the method described in the first aspect above.

[0068] Fifthly, this application provides an electronic device comprising: one or more processors, and a memory; the memory is coupled to the one or more processors, the memory storing computer program code, the computer program code including computer instructions, wherein the one or more processors invoke the computer instructions to cause the electronic device to perform the method described in the second aspect above. The electronic device is a first device having a host role.

[0069] Sixthly, this application provides an electronic device comprising: one or more processors, and a memory; the memory is coupled to the one or more processors, the memory storing computer program code including computer instructions, and the one or more processors invoking the computer instructions to cause the electronic device to perform the method described in the third aspect above. The electronic device is a second device having a slave role.

[0070] In a seventh aspect, this application provides a communication system comprising the wearable device described in the fourth aspect, the electronic device described in the fifth aspect (a first device having a host role), and the electronic device described in the sixth aspect (a second device having a slave role).

[0071] Eighthly, this application provides a processing apparatus for inter-device communication service transfer, the apparatus including units for performing the method described in the first aspect above. This apparatus can correspond to performing the method described in the first aspect above; for a brief description of the units within the apparatus, please refer to the description in the first aspect above, and will not be repeated here.

[0072] The method described in the first aspect above can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. For example, a processing module or unit, a display module or unit, etc.

[0073] Ninthly, this application provides a computer-readable storage medium having a computer program (also referred to as instructions or code) stored thereon for implementing the method of the first aspect. For example, when the computer program is executed by a computer, it enables the computer to perform the method of the first aspect, or the second aspect, or the third aspect.

[0074] In a tenth aspect, this application provides a chip including a processor. The processor is configured to read and execute a computer program stored in a memory to perform the methods of the first aspect and any possible implementation thereof. Optionally, the chip further includes a memory connected to the processor via a circuit or wire.

[0075] Eleventhly, this application provides a chip system including a processor. The processor is used to read and execute a computer program stored in a memory to perform the methods in the first aspect and any possible implementation thereof. Optionally, the chip system further includes a memory connected to the processor via a circuit or wire.

[0076] In a twelfth aspect, this application provides a computer program product comprising a computer program (also referred to as instructions or code), which, when executed by an electronic device, causes the electronic device to implement the method of the first aspect.

[0077] It is understood that the beneficial effects of aspects two through twelfth above can be found in the relevant descriptions in aspect one above, and will not be repeated here. Attached Figure Description

[0078] Figure 1 A schematic diagram illustrating application scenarios for smartwatches interacting with mobile phones;

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

[0080] Figure 3A A flowchart illustrating the processing method for inter-device communication service transfer provided in this application embodiment;

[0081] Figure 3B A schematic diagram illustrating an application scenario for the processing method of inter-device communication service transfer provided in the embodiments of this application;

[0082] Figure 4A A schematic diagram illustrating the process of associating a smartwatch with a host and a slave device in the multi-device communication service transfer method provided in this application embodiment;

[0083] Figure 4B A schematic diagram of the interface for sharing notifications between a smartwatch and a host and slave device in the multi-device communication service transfer processing method provided in the embodiments of this application;

[0084] Figure 4C A schematic diagram illustrating a scenario where a slave device is replaced on the smartwatch side in the multi-device communication service transfer processing method provided in this application embodiment;

[0085] Figure 4D A schematic diagram illustrating a scenario where the host is replaced on the smartwatch side in the multi-device communication service transfer processing method provided in this application embodiment;

[0086] Figure 4E This is a schematic diagram illustrating a scenario in which the smartwatch, host, and slave are in the same trust ring in the multi-device communication service transfer processing method provided in the embodiments of this application.

[0087] Figure 4F A schematic diagram of the interface for canceling notification sharing in the processing method for inter-device communication service flow provided in the embodiments of this application;

[0088] Figure 4G A schematic diagram of the interface for setting up notification sharing on the mobile phone side in the processing method for multi-device communication service flow provided in the embodiments of this application;

[0089] Figure 5A A flowchart illustrating the processing method for inter-device communication service transfer provided in the embodiments of this application. Figure 1 ;

[0090] Figure 5B A flowchart illustrating the processing method for inter-device communication service transfer provided in the embodiments of this application. Figure 2 ;

[0091] Figure 6A A schematic diagram illustrating a near-field communication scenario between a smartwatch and a host / slave device, provided in an embodiment of this application.

[0092] Figure 6B A schematic diagram illustrating the interaction process between a smartwatch and a host / slave device for near-field communication, provided in an embodiment of this application.

[0093] Figure 7A A schematic diagram illustrating a scenario of near-field communication between a smartwatch and a host, and far-field communication between a host and a slave device, provided in an embodiment of this application.

[0094] Figure 7B A schematic diagram illustrating the interaction process between a smartwatch and a host for near-field communication and between a host and a slave for far-field communication, provided in an embodiment of this application.

[0095] Figure 8A A schematic diagram illustrating a scenario of far-field communication between a smartwatch and a host / slave device, provided in an embodiment of this application;

[0096] Figure 8B A schematic diagram illustrating the interaction process between a smartwatch and a host / slave device for far-field communication, provided in an embodiment of this application.

[0097] Figure 9A A schematic diagram illustrating an application scenario for the processing method of inter-device communication service transfer provided in the embodiments of this application;

[0098] Figures 9B to 9C A schematic diagram of an incoming call scenario in the multi-device communication service transfer processing method provided in the embodiments of this application;

[0099] Figure 10 A schematic diagram of the structure of a processing device for inter-device communication service transfer provided in an embodiment of this application;

[0100] Figure 11 This is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation

[0101] The embodiments of this application will be further described in detail below with reference to specific examples and the accompanying drawings.

[0102] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0103] The term "user interface (UI)" used in the following embodiments of this application refers to the medium interface through which an application or operating system interacts and exchanges information with the user. It realizes the conversion between the internal form of information and the form that the user can accept. The user interface is source code written in a specific computer language such as Java or Extensible Markup Language (XML). The interface source code is parsed and rendered on the electronic device, ultimately presenting content that the user can recognize. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be visible interface elements such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets displayed on the screen of an electronic device.

[0104] Currently, due to limitations in chip capabilities and Bluetooth functionality, wearable devices such as smartwatches and smart bracelets can only interconnect with one electronic device (such as a mobile phone) via wireless networks (e.g., Bluetooth or Wi-Fi). For example, after a smartwatch is paired with mobile phone 1 via Bluetooth, if mobile phone 2 requests to pair with the smartwatch via Bluetooth, the smartwatch must first disconnect from mobile phone 1 via Bluetooth before pairing with mobile phone 2. In this scenario, the wearable device can only receive and display message notifications or call notifications from one mobile phone.

[0105] In real life, many users own one wearable device and two mobile phones, hoping to receive and display message notifications or call notifications from multiple devices through a single wearable device. However, current technology cannot meet this need.

[0106] Therefore, there is an urgent need for a method that can receive and display message notifications or call notifications from multiple devices through a single wearable device.

[0107] To address the aforementioned issues, this application provides a method and electronic device for processing communication service transfer between multiple devices. The method includes: a wearable device establishing device association relationships under the same user account with a first device and a second device; wherein the user accounts logged in by the wearable device, the first device, and the second device are the same, and the first device and the second device are both mobile phones; the wearable device performs near-field communication with the first device; the wearable device receives a first notification from the first device and displays the first notification; the first notification is a message notification or a call notification from the first device; the wearable device receives a second notification from the first device and displays the second notification; the second notification is a message notification or a call notification from the second device.

[0108] Through the multi-device communication service transfer processing method provided in the embodiments of this application, wearable devices (such as smartwatches) can be associated with two mobile phones at the same time. Message notifications or call notifications from multiple mobile phones associated with the smartwatch can be transferred to the smartwatch. The smartwatch can simultaneously display message notifications or call notifications from any mobile phone, meeting the user's need to conveniently view and process message and call notifications from multiple mobile phones through the smartwatch, and improving the user experience.

[0109] It should be noted that the aforementioned user account can refer to the account of the system software or the application software installed on the device.

[0110] To better understand the embodiments of this application, the embodiments of this application will be briefly described below:

[0111] refer to Figure 1 As shown, compared with the wearable devices of related technologies that can only be associated with one mobile phone, in the improved solution of this application, the wearable device 100 can be associated with two mobile phones at the same time, and simultaneously display message notifications or call notifications of either mobile phone, which meets the user's need to conveniently view message and call notifications of multiple mobile phones through the wearable device 100 and improves the user experience.

[0112] The solution provided in this application can meet the needs of dual-device users to have their calls / notifications and other services reach the watch. It helps users manage message notifications or call notifications from multiple devices through a single watch, without worrying about missing important events.

[0113] For example, a user owns a wearable device and two mobile phones, one (phone 1) primarily used for work and the other (phone 2) primarily used for personal life. Phone 1 may include work communication apps and document apps, while phone 2 may include lifestyle service apps and fitness apps. This application's solution allows a single wearable device to receive and display message notifications and call notifications from both phones.

[0114] The multi-device communication service transfer processing method provided in this application can be applied to incoming / outgoing call scenarios as well as message sending and receiving scenarios. Users can receive messages / calls from two mobile phones on the same watch, ensuring that all important content is not missed or omitted.

[0115] In this embodiment, the wearable device can be associated with two mobile phones simultaneously, and the wearable device can receive and display message notifications or call notifications for each electronic device. The message notifications or call notifications can include both message notifications and call notifications.

[0116] For example, message notifications may include application messages, schedules, to-do lists, flight bookings, delivery notifications, alarm reminders, notes, YOYO suggestions, and other notifications in the notification bar.

[0117] For example, call notifications may include incoming call notifications and missed call notifications.

[0118] Through the solution proposed in this application, tasks such as message notifications or call notifications from multiple devices associated with a smartwatch can be transferred to the smartwatch. For example, two mobile phones associated with a smartwatch can transfer call notifications, voice notes, currently playing music, alarm clock information, and / or sports and health data to the user's smartwatch.

[0119] This application's solution leverages system-level interconnectivity to build a secure, reliable, and rapidly interconnected multi-device trust ring connection.

[0120] For example, User A wears a smartwatch and uses two mobile phones (Phone 1 and Phone 2). All three devices are logged into the same user account, and are authenticated as mutually trusted devices, forming a trust loop. The user pairs the smartwatch with Phone 1 through the fitness app on Phone 1, with Phone 1 acting as the host, or in other words, the host connected to the smartwatch. Message notifications or call notifications from Phone 1 will reach the smartwatch. Based on the trust loop's smart interconnection function, the smartwatch recognizes the presence of another phone with the same account (Phone 2) and asks the user if they want to connect Phone 2 to the smartwatch. Upon confirmation from the user on the smartwatch, the smartwatch connects to Phone 2. In this case, Phone 2 acts as the slave device connected to the smartwatch.

[0121] In some cases, the master and slave device information can be displayed in the smartwatch's settings -> Smart Connect menu. After the smartwatch is connected to both phone 1 and phone 2, it can receive message and call notifications from both phone 1 and phone 2. The specific principles and processes of call service flow between phone 1 and phone 2 will be explained in detail below.

[0122] With this solution, incoming call notifications, app messages in the notification bar, calendar events, to-do lists, flight schedules, package tracking, alarms, notes, and YOYO suggestions from both phones can be synced to the smartwatch. When the smartwatch receives calendar events, to-do lists, or alarms, the user can tap "Turn off" or "Remind later" on the watch side, which will also turn off or postpone the phone sync. This convenience greatly enhances the user experience.

[0123] It should also be noted that this embodiment uses the example of one smartwatch connected to two mobile phones for illustrative purposes. In actual implementation, this embodiment can also connect one smartwatch to three or more electronic devices, and is not limited to connecting mobile phones. For example, one smartwatch can connect to one mobile phone and one tablet; as another example, one smartwatch can connect to two mobile phones and one tablet.

[0124] The following description, in conjunction with the accompanying drawings, illustrates the wearable device to which the multi-device communication service transfer processing method provided in this application is applied. For example, the wearable device in this application embodiment can be an electronic device such as a smartwatch or smart bracelet; this application embodiment does not impose any special limitations on the specific form of the wearable device.

[0125] Figure 2This illustration shows a hardware structure diagram of a wearable device 100 according to an embodiment of this application. For example, a smartwatch is used as an example of a wearable device. Figure 2 As shown, wearable devices may include: processor 110, internal memory 120, sensor module 130, display screen 140, wireless communication module 150, audio module 160, speaker 160A, receiver (i.e., earpiece) 160B, microphone 160C, headphone jack 160D, etc.

[0126] Processor 110 may include one or more processing units, which may be independent devices or integrated into one or more processors. Processor 110 may also include memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that processor 110 has just used or that is used repeatedly. If processor 110 needs to reuse the instruction or data, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of processor 110, and thus improves system efficiency.

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

[0128] In this embodiment, the wearable device can be implemented by the processor 110 as follows: the wearable device establishes a device association relationship with the first device and the second device under the same user account; the wearable device performs near-field communication with the first device; the wearable device receives a first notification from the first device and triggers the display screen 140 to display the first notification; the first notification is a message notification or a call notification from the first device; the wearable device receives a second notification from the first device and triggers the display screen 140 to display the second notification; the second notification is a message notification or a call notification from the second device.

[0129] Internal memory 120 can be used to store computer executable program code, including instructions. Internal memory 120 may include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function, etc. The data storage area may store data created during the use of the electronic device, etc. Furthermore, internal memory 120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 110 executes various functional applications and data processing of the wearable device by running instructions stored in internal memory 120 and / or instructions stored in memory disposed in the processor. For example, in this embodiment, processor 110 can execute instructions stored in internal memory 120.

[0130] The display screen 140 is used to display images, videos, etc. In this embodiment, the display screen 140 can display message notifications or incoming call notifications.

[0131] The wireless communication function of wearable devices can be realized through the wireless communication module 150. The wireless communication module 150 can provide solutions for wireless communication applications in wearable devices, 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) technology.

[0132] The wireless communication module 150 can be one or more devices integrating at least one communication processing module. The wireless communication module 150 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signal, and sends the processed signal to processor 110. The wireless communication module 150 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0133] Of course, the aforementioned wireless communication module 150 can also support voice communication for wearable devices. For example, a wearable device can access a Wi-Fi network through the wireless communication module 150 and then use any application that provides voice communication services to interact with other devices, providing voice communication services to the user. For example, the application that provides voice communication services could be an instant messaging application.

[0134] Wearable devices can achieve audio functions such as music playback and recording through an audio module 160, a speaker 160A, a receiver (i.e., earpiece) 160B, a microphone 160C, a headphone jack 160D, and an application processor.

[0135] The above is a detailed description of the embodiments of this application using wearable device 100 as an example. It should be understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on wearable device 100. Wearable device 100 may have more or fewer components than shown in the figures, may combine two or more components, or may have different component configurations. The various components shown in the figures can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0136] The execution subject of the multi-device communication service transfer processing method provided in this application embodiment can be the aforementioned wearable device, or it can be a functional module and / or functional entity within the wearable device capable of implementing the multi-device communication service transfer processing method. Furthermore, the solution of this application can be implemented through hardware and / or software, and the specific implementation can be determined according to actual usage requirements; this application embodiment does not impose any limitations. The following description uses a wearable device as an example, combined with the accompanying drawings, to exemplarily illustrate the multi-device communication service transfer processing method provided in this application embodiment.

[0137] The embodiments of this application will be described below with reference to the accompanying drawings and through several exemplary embodiments. The methods in the following embodiments can all be implemented in a wearable device having the above-described hardware structure and software architecture. The hardware structure diagram of the wearable device can be as follows: Figure 2 As shown, the embodiments of this application are not limited to this. For ease of explanation, the wearable device used in the embodiments of this application is a smartwatch.

[0138] The following describes the processing method for inter-device communication service transfer provided in this application, with reference to specific embodiments.

[0139] Figure 3A This is a flowchart illustrating the processing method for inter-device communication service transfer provided in an embodiment of this application. (Refer to...) Figure 3A As shown, the method includes the following steps.

[0140] S301, The wearable device and the first device are logged into the same account and connected via Bluetooth pairing.

[0141] The first device can log in to a user account through the Sports & Health app, where an "Add Device" option is displayed on the device interface. Responding to the user's action of selecting the "Add Device" option, the first device can scan for nearby devices via Bluetooth wireless communication technology. If the first device finds a wearable device logged in with the same user account, it will pair with the wearable device via Bluetooth, completing the Bluetooth connection between the two devices.

[0142] In some embodiments, the sports and health app supports login on multiple devices with the same account.

[0143] In some embodiments, the first device has enabled the smart interconnection service.

[0144] S302. Enable notification sharing function for wearable devices.

[0145] In some embodiments, the wearable device has enabled smart connectivity services. Smart connectivity services include notification sharing functionality.

[0146] In some embodiments, the wearable device may enable notification sharing in response to user actions.

[0147] In other embodiments, the wearable device may automatically enable notification sharing by default after powering on.

[0148] In other embodiments, the wearable device has an activated electronic SIM (eSIM) service, enabling it to connect to the internet. The eSIM function can be automatically activated when the wearable device disconnects from devices such as mobile phones via Bluetooth, allowing the wearable device to connect to the internet.

[0149] In other embodiments, the wearable device has the far-field messaging switch turned on.

[0150] S303: Wearable devices can detect if there are other devices with the same account nearby.

[0151] In some embodiments, when the wearable device has notification sharing enabled, the wearable device can detect whether there are any mobile phones with the same account as the wearable device nearby.

[0152] It should be noted that this example illustrates how wearable devices can detect nearby devices with the same account. In actual implementation, mobile phones can also be used to detect nearby devices with the same account, thus enabling wireless interconnection between mobile phones and wearable devices.

[0153] For example, in some embodiments, when the phone has notification sharing enabled, the phone can detect if there are any wearable devices nearby with the same account as the phone. If the phone detects a wearable device, it can prompt the user to connect the phone to the wearable device, for example, by making the phone a slave device connected to the wearable device, or the phone can send a notification to the wearable device, allowing the user to operate on the wearable device. In response to the user's operation, the wearable device will make the phone a slave device connected to the wearable device.

[0154] For example, in some embodiments, the mobile phone and wearable device simultaneously detect whether there are any devices with the same account nearby, which can discover devices with the same account more quickly.

[0155] For example, in some embodiments, when the mobile phone detects whether there are devices with the same account nearby, the wearable device may not need to perform the detection, which can reduce the power consumption of the wearable device.

[0156] S304. When a wearable device detects a second device with the same account nearby, it prompts the user to add the second device as an associated device of the wearable device.

[0157] In some embodiments, the second device has enabled the smart connectivity service.

[0158] In some embodiments, the wearable device detects a second device with the same account in the vicinity via a smart connectivity service.

[0159] S305. In response to the user's confirmation of the addition operation, the wearable device simultaneously associates the first device and the second device, and sets the first device as the master and the second device as the slave.

[0160] In this embodiment of the application, wearable devices, host devices, and slave devices logged into the same user account can form a trust ring network (hereinafter referred to as a trust ring). In other words, the wearable devices, host devices, and slave devices are on the trust ring.

[0161] When the distance between the wearable device and the host is less than a distance threshold, the wearable device and the host can conduct near-field communication based on a trust loop. For example, near-field communication includes short-range communication based on Bluetooth or Wi-Fi. For ease of understanding, the trust loop here can be called a near-field trust loop.

[0162] When the distance between the wearable device and the host is greater than or equal to a distance threshold, the wearable device and the host can conduct far-field communication based on a trust ring. For example, far-field communication includes long-distance communication based on mobile networks. For ease of understanding, the trust ring here can be called a far-field trust ring.

[0163] It is understandable that when the distance between the wearable device and the host is less than a distance threshold, they can be considered to be on a near-field trust loop. When the distance between the wearable device and the host is greater than or equal to the distance threshold, they can be considered to be on a far-field trust loop.

[0164] S306. Wearable devices, based on the Trust Ring Communication Protocol, receive message-type notifications or call-type notifications for the host and for the slave devices.

[0165] S307. Wearable devices display message-type notifications or call-type notifications for the host / slave device.

[0166] In this embodiment, based on the trust ring communication protocol, trusted interconnection of multiple devices across systems can be achieved, enabling intelligent flow and sharing of services between devices. The trust ring communication protocol can define service flow rules, which include:

[0167] (1) When the wearable device and the host are on the near-field trust ring, the message-type notification or call-type notification received by the host can be sent to the wearable device through near-field communication; the message-type notification or call-type notification received by the slave device can be sent to the host, which will then forward (transfer) it to the wearable device.

[0168] Among them, message-type notifications or call-type notifications received by the host refer to message-type notifications or call-type notifications sent by the base station to the host.

[0169] Among them, message-type notifications or call-type notifications received by the slave device refer to message-type notifications or call-type notifications sent by the base station to the slave device.

[0170] (2) When the wearable device and the host are on a far-field trust ring, the message-type notifications or call-type notifications received by the host can be sent to the wearable device through far-field communication; the message-type notifications or call-type notifications received by the slave device can be sent directly to the wearable device through far-field communication (e.g., a cloud server based on a trust ring). In other words, the message-type notifications or call-type notifications received by the slave device are not forwarded by the host.

[0171] With the solution proposed in this application, a wearable device can be connected to two mobile phones at the same time, and can receive and display message-type notifications or call-type notifications for each electronic device.

[0172] For example, message notifications may include application messages, schedules, to-dos, YOYO suggestions, and other notification reminders in the notification bar.

[0173] For example, call notifications may include incoming call notifications and missed call notifications.

[0174] With this solution, message notifications or call notifications received by the host device will be synchronized to the watch and vibrate to alert the user; message notifications or call notifications received by the slave device will also be synchronized to the watch and vibrate to alert the user.

[0175] Compared to other wearable devices that can only be associated with one mobile phone, the wearable device in this application can be associated with two mobile phones simultaneously, displaying message notifications or call notifications from either phone at the same time. This satisfies users' desire to conveniently view message and call notifications from multiple mobile phones through wearable devices, thus improving the user experience.

[0176] Figure 3B This illustration shows a schematic diagram of a trust-ring-based communication connection between a smartwatch and two mobile phones, as provided in an embodiment of this application.

[0177] like Figure 3B As shown in (a), the host and smartwatch are connected via a trust ring near-field connection, while the host and slave are connected via a trust ring far-field / near-field connection. Message-type notifications or call-type notifications received by the host can be sent to the wearable device via the trust ring near-field connection. Message-type notifications or call-type notifications received by the slave can be sent to the host via the trust ring far-field or near-field connection, and then forwarded (transferred) by the host to the wearable device.

[0178] like Figure 3B As shown in (b), the host and the smartwatch establish a far-field connection based on the cloud server of the trust ring (referred to as cloud service), and the slave and the smartwatch also establish a far-field connection based on the cloud service. Message-type notifications or call-type notifications received by the host can be sent to the wearable device through the trust ring far-field cloud service. Message-type notifications or call-type notifications received by the slave can also be sent to the wearable device through the trust ring far-field cloud service.

[0179] It should be noted that the host only performs bridging at the technical level. When notifications / call messages or incoming call notifications from the slave device are transmitted to the wearable device through the host, the host does not display the notifications / call messages or incoming call notifications from the slave device.

[0180] It should also be noted that the embodiments of this application use the example of a smartwatch connected to two mobile phones for illustrative purposes. In actual implementation, the embodiments of this application can also enable a smartwatch to connect to three or more electronic devices, and are not limited to connecting to mobile phones.

[0181] Through this application, notifications / call messages or incoming call notifications from multiple devices associated with the smartwatch can be transferred to the smartwatch. For example, the content of voice notes on phone 1, the music playing on the tablet, the alarm clock information on phone 2, and sports and health data can all be transferred to the user's smartwatch.

[0182] The above illustrates the overall flowchart of the multi-device communication service transfer method provided in the embodiments of this application. The following specific embodiments illustrate the process of associating a wearable device with a host and a slave device, the communication service transfer method between the wearable device and the host / slave device, the application of the inter-device communication service transfer method to specific user scenarios, the display of message-type notifications or call-type notifications from the host / slave device by the wearable device, and the possible response methods of the wearable device to call notifications.

[0183] Example 1: Wearable device association with host and slave devices

[0184] The following explanation uses a smartwatch as the wearable device, mobile phone 1 as the first device, and mobile phone 2 as the second device.

[0185] Figure 4A This is a schematic diagram illustrating the interaction between a smartwatch, mobile phone 1, and mobile phone 2 in the multi-device communication service transfer processing method provided in this application embodiment. (Refer to...) Figure 4A As shown, the method includes the following steps.

[0186] First, it should be noted that the smartwatch, phone 1, and phone 2 are logged into the same account.

[0187] S401. Enable the notification sharing function in the Smart Connect service on your smartwatch.

[0188] After enabling notification sharing on a smartwatch, the smartwatch can be linked to two phones and can receive message or call notifications from both phones.

[0189] S402. Smartwatch and Mobile Phone 1 are paired and connected via Bluetooth. The smartwatch can be discovered and added in the Health & Fitness app interface of Mobile Phone 1, thus enabling Bluetooth pairing and connection between the smartwatch and Mobile Phone 1.

[0190] S403: The smartwatch discovers nearby mobile phones with the same account through the smart interconnection service.

[0191] S404 The smartwatch displays a prompt message, such as a prompt that the phone 2 can be linked to the smartwatch.

[0192] S405. In response to user operation, the smartwatch connects to both mobile phone 1 and mobile phone 2 simultaneously, with mobile phone 1 designated as the master and mobile phone 2 as the slave.

[0193] Figure 4B This is a schematic diagram illustrating a scenario in the multi-device communication service transfer processing method provided in this application, where a smartwatch, mobile phone 1, and mobile phone 2 are associated. For example... Figure 4B As shown in (a), multiple devices logged into the same user account include a smartwatch, mobile phone 1, and mobile phone 2.

[0194] like Figure 4B As shown in (b), the smartwatch is paired and connected to the mobile phone 1 via Bluetooth.

[0195] like Figure 4B As shown in (c) of the interface, the smartwatch discovers a mobile phone 2 with the same account nearby through the smart interconnection service. The interface displays the prompt message "New device detected. The watch currently supports connecting to a second mobile phone to receive notifications and make calls. Do you want to go to settings to connect?". The interface also displays controls to go to settings and clear controls.

[0196] The smartwatch receives a user's tap to access the settings controls. Figure 4B As shown in (d), in response to the user's click to go to the settings control, the smartwatch displays a notification sharing interface, which includes a notification sharing switch, which is in the "on" state. With notification sharing enabled, the smartwatch can receive notifications from the phone and can connect to another device besides the main device. In this case, phone 1 acts as the main device. The smartwatch receives the user's selection of phone 2. Figure 4B As shown in (e), in response to the user's selection of phone 2, the smartwatch sets phone 2 as a slave device. Thus, the smartwatch is simultaneously connected to both phone 1 and phone 2, and can receive notifications (message notifications or call notifications) from both phone 1 and phone 2.

[0197] In one possible implementation, when the smartwatch detects the mobile phone 2, the smartwatch can automatically set the mobile phone 2 as a slave device.

[0198] The above example illustrates one possible implementation of adding a master and slave device to a smartwatch: the smartwatch establishes a connection with mobile phone 1, and mobile phone 1 is set as the master device connected to the smartwatch by default; then, when the smartwatch detects mobile phone 2, the smartwatch prompts the user to set mobile phone 2 as a slave device, and after the user confirms, mobile phone 2 is set as a slave device connected to the smartwatch; or, when the smartwatch detects mobile phone 2, the smartwatch can automatically set mobile phone 2 as a slave device.

[0199] It should be noted that, in actual implementation, the embodiments of this application may also adopt other possible implementation methods to achieve the purpose of adding a master and slave device to the smartwatch.

[0200] In some embodiments, when the smartwatch detects both mobile phone 1 and mobile phone 2 simultaneously, the smartwatch can add the mobile phone that the user uses more frequently to the trust ring as the master, and add the mobile phone that the user uses less frequently to the trust ring as the slave.

[0201] In some embodiments, if the smartwatch detects mobile phone 1 first, the smartwatch sets mobile phone 1 as the master. When the smartwatch detects mobile phone 2, the smartwatch can automatically set mobile phone 2 as the slave.

[0202] It should be noted that in some scenarios, after the smartwatch has been set as the master, the smartwatch may detect multiple mobile phones. The smartwatch can determine one of the multiple mobile phones as a slave phone according to preset rules and automatically add that mobile phone as a slave phone.

[0203] The preset rules can be to determine the slave device according to the order in which they are added to the trust ring, for example, the device that is added to the trust ring first is determined as the slave device; or to randomly select one phone from multiple phones as the slave device.

[0204] The above describes the possible implementations of adding master and slave devices to a smartwatch. The following describes the possible implementations of replacing the slave device when a master and slave device have already been added to the smartwatch. The process of replacing the slave device on the smartwatch side is illustrated below with reference to the accompanying drawings.

[0205] For example, Figure 4C This illustration shows a schematic diagram of the interface for changing the slave device on the smartwatch side, provided in an embodiment of this application.

[0206] like Figure 4C As shown in (a), the smartwatch detects a new device, phone 3, and displays the message "New device detected. Phone 3 has joined the smart connection. The watch currently only supports sharing notifications between two phones. Phone 1 and Phone 2 are currently enabled. Do you want to change the settings?", and displays "Go to settings controls" and "Clear controls".

[0207] like Figure 4C As shown in (b), in response to the user clicking "Go to Settings Controls," the smartwatch redirects to the notification sharing settings interface. The notification sharing settings interface displays the selected devices: Phone 1 as the master and Phone 2 as the slave. The notification sharing settings interface also displays the option to select a device: Phone 3.

[0208] like Figure 4C As shown in (c), in response to the user clicking the option for phone 3, the smartwatch sets phone 3 as the slave device, and phone 2 is no longer used as a slave device. That is, the newly added phone 3 will replace phone 2 as the slave device. Furthermore, the selected devices in the notification sharing settings interface are updated to: phone 1 as the master device and phone 3 as the slave device. The selected device bar in the notification sharing settings interface is updated to: phone 2 option.

[0209] Or, in front Figure 4BIn the illustrated embodiment, the smartwatch discovers multiple phones with the same account. After the user selects phone 2 and the smartwatch identifies phone 2 as the slave phone, if the user continues to select phone 3, the smartwatch can set phone 3 as the slave phone, and phone 2 will not be used as the slave phone. That is, phone 3 will replace phone 2 as the slave phone.

[0210] The above explains the possible ways to replace a slave device when a master and slave device have been added to a smartwatch. The following explains the possible ways to replace a master device when a master and slave device have been added to a smartwatch.

[0211] In some embodiments, a user can trigger a change of the host device connected to the smartwatch via their mobile phone. For example, the connected device information is displayed in the device interface of the fitness app on phone 1: phone 1 and the smartwatch are connected. The user can trigger a disconnection between phone 1 and the smartwatch from their mobile phone. After the smartwatch is disconnected from phone 1, the user can repeat the discovery and connection process in the fitness app on another phone, thereby setting the other phone as the host device paired with the smartwatch.

[0212] In other embodiments, the user can operate from the smartwatch side to trigger the replacement of the host connected to the smartwatch. Figure 4D This illustration shows a schematic diagram of replacing the master device in a smartwatch where both a master and slave device have been added, as provided in an embodiment of this application. Figure 4D As shown in (a), the notification sharing settings interface of the smartwatch can display master and slave information: phone 1 corresponds to the master option, and phone 2 corresponds to the slave option. Figure 4D As shown in (b), when the user selects the host option, the notification sharing settings interface displays a prompt message: "Change host device? And yes or no options." Figure 4D As shown in (c), when the user selects the "yes" option, phone 2 is set as the master and phone 1 as the slave. Alternatively, when the user selects the "yes" option, the smartwatch can also provide multiple phones to choose from, and the user selects a new phone as the master.

[0213] Alternatively, if the user selects the host option, the notification sharing settings interface will display a prompt asking "Delete host device? with a yes / no option." If the user selects yes, the smartwatch will delete phone 1 and set phone 2 as the host. Alternatively, if the user selects yes, the smartwatch will delete phone 1, and the user can then select a new phone and connect it as the host in the smartwatch's settings app.

[0214] It should be noted that the above exemplifies one implementation method of triggering host replacement by operating on the smartwatch side. In actual implementation, other methods can be used to trigger host replacement, and this application embodiment does not limit this.

[0215] Figure 4E This illustration shows a schematic diagram of a smartwatch associated with two mobile phones, as provided in an embodiment of this application. Figure 4E As shown, the smartwatch, phone 1, and phone 2 are logged into the same user account, forming a trust loop. The smartwatch has notification sharing enabled. First, phone 1 establishes a Bluetooth connection with the smartwatch, forming a trust loop device. Then, phone 2 connects to the smartwatch using the same account, forming a trust loop device with phone 1, phone 2, and the smartwatch. In this scenario, the smartwatch sets phone 1 as the master and phone 2 as the slave.

[0216] In some embodiments, smartwatches may have notification sharing enabled by default.

[0217] In some embodiments, the smartwatch can enable or disable notification sharing based on user actions. Figure 4F This illustration shows a schematic diagram of a user-operated function to disable notification sharing, as provided in an embodiment of this application. Figure 4F The interface shown in (a) is the watch's system settings interface, where the smartwatch receives a user's notification sharing switch being turned off. Figure 4F As shown in (b), in response to user interaction, the smartwatch displays the message "After turning it off, notifications, calls, and other information will no longer be shared with your mobile device. Do you want to turn it on?". The smartwatch can also display a cancel control and a confirm control. The smartwatch receives the user's confirmation control input. Figure 4F As shown in (c), in response to the user's action on the confirmation control, the smartwatch disables the notification sharing function.

[0218] The above embodiments exemplify the process of scanning and discovering nearby mobile phones with the same account through a wearable device, and the process of the wearable device simultaneously associating with two mobile phones after user confirmation. In actual implementation, other methods can also be used to achieve the simultaneous association of a wearable device with two mobile phones. For example, users can manually add the two mobile phones by operating on their mobile phones.

[0219] In some embodiments, a notification sharing function can be set on the mobile phone side.

[0220] For example, Figure 4G This illustration shows a user setting up a notification sharing function on their mobile phone, triggering the smartwatch to receive message or call notifications from the mobile phone, as provided in an embodiment of this application. Figure 4GAs shown in (a), the phone displays the Smart Connect page, which can be a page in the system settings. The Smart Connect page includes notification sharing options.

[0221] The phone receives the user's action regarding notification sharing options. For example... Figure 4G As shown in (b), in response to the user's action on the notification sharing option, the phone displays a notification sharing page, which includes a notification sharing toggle. The phone receives the user's action on the notification sharing toggle. Figure 4G As shown in (c), the phone enables notification sharing in response to the user's operation of the notification sharing switch. After enabling notification sharing, the phone displays two settings panels: Tablet and PC settings panel and Watch settings panel. The Tablet and PC settings panel satisfies the notification sharing needs between the phone and the tablet / computer. The Watch settings panel satisfies the notification sharing needs between the phone and the watch.

[0222] Among them, such as Figure 4G As shown in (c), the tablet and computer settings include notification sharing switches for multiple applications. When the notification sharing switch for application 1 is turned on, messages from that application can flow between the phone and the tablet / computer. For example, when the phone receives a message from application 1, the phone displays the message, and the phone can also send the message to the tablet / computer for display, thus achieving notification sharing between multiple devices.

[0223] Among them, such as Figure 4G As shown in (d), the watch settings include a smart notification switch. When the smart notification switch is on, messages received on the phone can be routed to the watch. For example, when the phone receives a message or call notification, the phone displays the notification, and the phone can also send the notification to the watch for display, thus achieving notification sharing across multiple devices.

[0224] In some embodiments, after the smart reminder switch on the watch is turned on, the reminder device can be intelligently selected according to the phone's usage status. When the phone is in use, notifications will not be displayed on the watch, thus avoiding unnecessary disturbances.

[0225] In some embodiments, mobile phones 1 and 2 automatically enable notification sharing by default, and the smartwatch also automatically enables notification sharing by default. Therefore, users do not need to manually enable notification sharing on their phones or watches, which improves the user experience.

[0226] This solution allows the smartwatch to connect to two phones and receive notifications from both phones, including app messages, schedules, to-do lists, YOYO suggestions, and incoming / missed calls, once the smartwatch is connected, smart reminders are enabled, and notification sharing is activated on both phones. Even without the phone, the smartwatch can still receive notifications based on far-field trust loop technology, ensuring no important information is missed.

[0227] Example 2: Communication service flow process between wearable devices and host / slave devices

[0228] After a wearable device is associated with a host and a slave device, the wearable device, the host, and the slave device are on the same trust ring. Based on the trust ring communication protocol, the wearable device, the host, and the slave device can achieve trusted interconnection of multiple devices across systems, enabling services to flow and be shared intelligently between devices.

[0229] The following description, in conjunction with the accompanying drawings, illustrates the communication service flow process between the wearable device and the host / slave device provided in the embodiments of this application.

[0230] Figure 5A A flowchart illustrating the communication service flow between the wearable device and the host / slave device of this application is shown. Figure 5A The steps are Figure 3A Possible implementations of S306 and S307.

[0231] S501, The wearable device detects whether the first distance value between the wearable device and the host is less than the first threshold.

[0232] The first threshold can be the maximum distance at which the wearable device and the host can communicate in the near field (such as Bluetooth or Wi-Fi).

[0233] In some embodiments, a first distance value is defined between the wearable device and the host, and it is determined whether the first distance value is less than a first threshold.

[0234] In some embodiments, the host can detect a first distance value between the wearable device and the host, and send the first distance value to the wearable device, which then determines whether the first distance value is less than a first threshold.

[0235] In other embodiments, the host can detect a first distance value between the wearable device and the host, determine whether the first distance value is less than a first threshold, and then send the determination result to the wearable device.

[0236] S502, When the first distance value is less than the distance threshold, the wearable device communicates with the host in the near field, and the host communicates with the slave device.

[0237] In some embodiments, when a first distance value between the wearable device and the host is less than a first threshold and a second distance value between the wearable device and the slave is less than a second threshold, the host and the slave perform near-field communication.

[0238] The second threshold can be the maximum distance at which the wearable device and the slave device can conduct near-field communication (e.g., Bluetooth or Wi-Fi communication). In some embodiments, the first threshold can be equal to the second threshold.

[0239] In some embodiments, when a first distance value between the wearable device and the host is less than a first threshold and a second distance value between the wearable device and the slave device is greater than or equal to a second threshold, the host and the slave device perform far-field communication.

[0240] S503, when the first distance value is greater than or equal to the first threshold, the wearable device communicates with the host in the far field and with the slave device in the far field.

[0241] After S502, continue executing S504 or S505.

[0242] S504. When the host receives a message-type notification or a call-type notification, the host sends the message-type notification or call-type notification to the wearable device via near-field communication.

[0243] S505. When the slave device receives a message-type notification or a call-type notification, the slave device sends the message-type notification or call-type notification to the master device, which then forwards it to the wearable device.

[0244] In some embodiments, when the slave device receives a message-type notification or call-type notification from the base station, if the host and slave device have established a near-field communication connection, the slave device sends the message-type notification or call-type notification to the host via near-field communication, and the host forwards it to the wearable device.

[0245] In other embodiments, when the slave device receives a message-type notification or call-type notification from the base station, if the master and slave devices have established a far-field communication connection, the slave device sends the message-type notification or call-type notification to the master device via far-field communication, and the master device forwards it to the wearable device.

[0246] After S503, continue executing S506 or S507.

[0247] S506. When the host receives a message-type notification, the host sends the message-type notification directly to the wearable device via far-field communication.

[0248] S507. When the slave device receives a message-type notification, the slave device sends the message-type notification directly to the wearable device via far-field communication.

[0249] After S504 or S506, continue with S508.

[0250] S508. The wearable device receives a message-type notification or call-type notification from the host and displays the message-type notification or call-type notification to the host.

[0251] After S505 or S507, continue with S509.

[0252] S509. The wearable device receives a message-type notification or call-type notification for the slave device and displays the message-type notification or call-type notification for the slave device.

[0253] In some scenarios, wearable devices receive message-type notifications or call-type notifications directly from the slave device. In other scenarios, wearable devices receive message-type notifications or call-type notifications from the master device; that is, message-type notifications or call-type notifications from the slave device are forwarded to the wearable device by the master device.

[0254] The above describes the process by which a wearable device receives message notifications or call notifications from the host / slave device. The following, with reference to the accompanying drawings, describes the process by which message notifications or call notifications from the slave device are transferred to the wearable device via the host.

[0255] Figure 5B This illustration shows a flowchart of the process by which message notifications or call notifications from a slave device are transferred to a wearable device via a host device, as provided in an embodiment of this application. Figure 5B The steps are Figure 5A Possible implementations of S501 and S502.

[0256] S501, The wearable device detects whether the first distance value between the wearable device and the host is less than the first threshold.

[0257] S5021. When the first distance value is less than the first threshold, the wearable device communicates with the host in the near field.

[0258] S5022, The wearable device detects whether the second distance value between the wearable device and the slave device is less than the second threshold.

[0259] S5023. When the second distance value is greater than or equal to the second threshold, the host and the slave perform far-field communication.

[0260] S5024. When the second distance value is less than the second threshold, the host and the slave perform near-field communication.

[0261] After S6023, continue executing S5025.

[0262] S5025. When the slave device receives a message-type notification, the slave device sends the message-type notification to the master device via far-field communication, and the master device forwards it to the wearable device.

[0263] After S5024, continue executing S5026.

[0264] S5026. When the slave device receives a message-type notification or a call-type notification, the slave device sends the message-type notification or call-type notification to the master device via near-field communication, and the master device forwards it to the wearable device.

[0265] Example 3: Application of the inter-device communication service transfer method to a specific user scenario

[0266] The above describes a flowchart illustrating the communication service flow between the wearable device and the host / slave device provided in the embodiments of this application. The following describes various scenario diagrams illustrating the communication service flow between the wearable device and the host / slave device in conjunction with the accompanying drawings.

[0267] User Scenario 1: The user carries a smartwatch, a master unit, and a slave unit.

[0268] In user scenario 1, message notifications, incoming call notifications, and missed call notifications from the host device can be directly transmitted to the smartwatch via a near-field communication (NFC) link for display. Similarly, message notifications, incoming call notifications, and missed call notifications from the slave device can be transmitted to the host device via the NFC link, then forwarded by the host to the smartwatch for display.

[0269] The following is combined with Figure 6A and Figure 6B The process of communication service flow between devices in Scenario 1 is explained.

[0270] Figure 6A This diagram illustrates the communication service flow between devices in a scenario where a user carries a smartwatch, a master device, and a slave device. (For example...) Figure 6A As shown, the user scenario involves a user carrying a smartwatch, a host, and a slave device. At this time, the smartwatch, host, and slave device are relatively close to each other and are within a local area network, i.e., in a near-field environment. These three devices are on a near-field trust ring, with the smartwatch communicating with the host and the host communicating with the slave device. Figure 6B This diagram illustrates the interaction of communication services between the smartwatch, the host, and the slave device in user scenario 1 described above. For example... Figure 6B As shown, in user scenario 1, the slave device and the master device are in a near-field connection state, and the master device and the smartwatch are in a near-field connection state.

[0271] Scenario 1: Communication service flow from host to smartwatch

[0272] S610, The host receives a message-type notification or an incoming call notification. The host can display the received message-type notification or incoming call notification.

[0273] S611: The host sends message notifications or incoming call notifications to the smartwatch via a near-field communication link (such as a Bluetooth channel or a Wi-Fi channel).

[0274] S612. The smartwatch receives a message notification or a call notification and displays the message notification or call notification.

[0275] In scenario 1, if the host receives a message-type notification or call-type notification from the base station, the host can send the message-type notification or call-type notification to the wearable device via near-field communication, and the wearable device can display the message-type notification or call-type notification from the host.

[0276] In some embodiments, when a user answers or hangs up an incoming call notification from the host on a wearable device, in response to the user's operation, the wearable device can send an instruction to answer or hang up the incoming call notification via near-field communication, and the host will execute the action of answering or hanging up the incoming call notification according to the instruction.

[0277] In some embodiments, a user replies to a message from the host on a wearable device. In response to the user's action, the wearable device can send the reply message to the host via near-field communication, and the slave device can then send the reply message to the base station.

[0278] Scenario 2: Communication service flow from slave device to smartwatch

[0279] S613. The slave device receives a message-type notification or an incoming call notification. The slave device can display the received message-type notification or incoming call notification.

[0280] S614. The slave device sends message-type notifications or call-type notifications to the master device via a near-field communication link (such as a Bluetooth channel or a Wi-Fi channel).

[0281] S615: The host forwards message notifications or call notifications to the smartwatch via a near-field communication link (such as a Bluetooth channel or a Wi-Fi channel).

[0282] S616: The smartwatch receives a message notification or a call notification and displays the message notification or call notification.

[0283] In scenario 2, if the slave device receives a message or call notification from the network side, it can send the message or call notification to the host via near-field communication. The host then forwards the message or call notification to the wearable device via near-field communication. The wearable device can vibrate to indicate that a message or call notification has been received and display the message or call notification from the slave device.

[0284] In some embodiments, due to the limitation that the smartwatch is connected to the host via a single Bluetooth connection, the audio of incoming calls from the slave device cannot be transmitted to the smartwatch. Therefore, an incoming call notification interface can be displayed on the smartwatch side, which displays a hang-up button but not an answer button.

[0285] In some embodiments, if the slave device receives a missed call notification but does not answer it, the slave device can forward the missed call notification to the smartwatch via the host, and the smartwatch can display the missed call notification.

[0286] In some embodiments, users wearing wearable devices can feel vibration alerts and see the wearable device screen light up to display an incoming call notification interface, thus becoming aware that there is an incoming call notification from the slave device. In this case, users can choose to answer the call on the slave device, thereby avoiding missing the call; or they can choose to hang up the incoming call notification from the slave device on the wearable device, which is convenient.

[0287] In other embodiments, when a user hangs up an incoming call notification from a slave device on the wearable device, the wearable device can respond to the user's operation by sending a hang-up instruction to the host via near-field communication. The host then forwards the instruction to the slave device, which then performs the action of answering or hanging up the incoming call notification according to the instruction.

[0288] In some embodiments, a user can reply to messages from a slave device on the wearable device. In response to the user's action, the wearable device can send the reply message to the master device via near-field communication (NFC), which then forwards it to the slave device via NFC. The slave device then sends the reply message to the network side.

[0289] User Scenario 2: The user carries a smartwatch and the main unit, but not the slave unit.

[0290] In user scenario 2, message notifications, incoming call notifications, and missed call notifications from the host device can be directly transmitted to the smartwatch via a near-field communication link for display. Message notifications and missed call notifications from the slave device can be transmitted to the host device via a far-field communication link, then forwarded by the host to the smartwatch for display. It should be noted that incoming call notifications from the slave device are not transmitted to either the host or the smartwatch.

[0291] The following is combined with Figure 7A and Figure 7B The process of inter-device communication service transfer in user scenario 2 is explained.

[0292] Figure 7A This diagram illustrates the communication service flow between devices in a scenario where the user carries a smartwatch and a master device, but not a slave device. (For example...) Figure 7AAs shown, the smartwatch and the host are close to each other and on the same local area network (LAN), while the slave device is not on the same LAN. In this case, the smartwatch and the host are on a near-field trust ring, and the slave device is on a far-field trust ring. Accordingly, the smartwatch communicates with the host in the near field, and the host communicates with the slave device in the far field. Figure 7B As shown, in user scenario 2, the slave and master devices are in a far-field connection state, while the master device and the smartwatch are in a near-field connection state.

[0293] Scenario 1: Communication service flow from host to smartwatch

[0294] S620: The host receives a message-type notification or an incoming call notification. The host can display the received message-type notification or incoming call notification.

[0295] S621: The host sends message notifications or incoming call notifications to the smartwatch via a near-field communication link (such as a Bluetooth channel or a Wi-Fi channel).

[0296] S622: The smartwatch receives a message notification or a call notification and displays the message notification or call notification.

[0297] In scenario 1, if the host receives a message-type notification or call-type notification from the base station, the host can send the message-type notification or call-type notification to the wearable device via near-field communication, and the wearable device can display the message-type notification or call-type notification from the host.

[0298] In some embodiments, a user can hang up or answer an incoming call notification from the host on a wearable device. In response to the user's operation, the wearable device can send a command to hang up the incoming call notification to the host via near-field communication, and the host will execute the action of hanging up or answering the incoming call notification according to the command.

[0299] In some embodiments, a user can reply to messages from the host on a wearable device. In response to the user's action, the wearable device can send the reply message to the host via near-field communication, and the host will then send the reply message to the network side.

[0300] In some embodiments, if the host receives an incoming call notification but does not answer it, the host can forward the missed call notification to the smartwatch, and the smartwatch can display the missed call notification from the host.

[0301] Scenario 2: Communication service flow from slave device to smartwatch

[0302] S623, The slave device receives a message-type notification. The slave device can display the received message-type notification.

[0303] S624. The slave device sends message-type notifications to the master device through the far-field communication link.

[0304] Among them, the far-field communication link can be implemented with the help of a trust ring-based cloud server and / or a mobile network provided by a base station.

[0305] Among them, cloud servers based on trust rings can achieve far-field communication based on eSIM functionality.

[0306] S625: The host forwards message notifications to the smartwatch via a near-field communication link (such as a Bluetooth channel or a Wi-Fi channel).

[0307] S626: The smartwatch receives and displays message notifications.

[0308] S627. The slave device receives and displays an incoming call notification. This notification is not forwarded to the host device or the smartwatch.

[0309] S628. The slave device did not answer the incoming call notification, and the message "No call notification received" is displayed.

[0310] S629. The slave device sends a missed call notification to the master device via the far-field communication link.

[0311] S630: The host sends missed call notifications to the smartwatch via a near-field communication link.

[0312] S631: The smartwatch receives and displays a missed call notification.

[0313] In scenario 2, message notifications from the slave device can be transmitted to the smartwatch via the master device. Incoming call notifications from the slave device are not transmitted to the master device and therefore do not reach the smartwatch; as a result, the incoming call notification interface is not displayed on the smartwatch.

[0314] In some embodiments, if the slave device receives a message notification, it can send the message notification to the master device via far-field communication. The master device then forwards the message notification to the wearable device via near-field communication, and the wearable device can display the message notification from the slave device.

[0315] In some embodiments, a user replies to a message from a slave device on a wearable device. In response to the user's action, the wearable device can send the reply message to the host via near-field communication, and the host can forward it to the slave device via far-field communication. The slave device then sends the reply message to the network side.

[0316] In some embodiments, if the slave device receives a missed call notification but does not answer it, the slave device can forward the missed call notification to the smartwatch via the host, and the smartwatch can display the missed call notification.

[0317] It should be noted that the common feature of user scenario 1 and user scenario 2 is that the distance between the host and the smartwatch is less than the first threshold, the host and the smartwatch conduct near-field communication, and regardless of the distance between the slave and the smartwatch, the slave's communication service can be transferred to the smartwatch through the host.

[0318] In this embodiment, when the user carries both the host and the wearable device, the host and the wearable device communicate near-fieldly based on a trust ring. When the slave device receives a message-type notification or call-type notification from the base station, regardless of the slave device's location, the message-type notification or call-type notification can be forwarded to the wearable device via the host and displayed by the wearable device. In this way, the user does not need to carry the slave device; they can obtain the message-type notification or call-type notification from the slave device through the wearable device, thus improving the user experience.

[0319] User Scenario 3: The user carries a smartwatch but no master or slave device; and User Scenario 4: The user carries a smartwatch... It can function as a watch and a slave device, but does not carry a master unit.

[0320] In user scenarios 3 and 4, messages and missed call notifications from the master device can be directly transmitted to the smartwatch via the far-field communication link and displayed on the smartwatch. Similarly, messages and missed call notifications from the slave device can also be directly transmitted to the smartwatch via the far-field communication link and displayed on the smartwatch. It should be noted that incoming call notifications received by either the master or slave device will not be transmitted to the smartwatch.

[0321] The following is combined with Figure 8A and Figure 8B The process of inter-device communication service flow in user scenario 3 and user scenario 4 is explained.

[0322] Figure 8A This diagram illustrates the communication service flow between devices in a scenario where the user carries a smartwatch but not the master or slave devices. Figure 8A As shown in (a), the user scenario involves a user carrying a smartwatch but not the master or slave device. The smartwatch is relatively far from both the master and slave devices. In this case, the smartwatch, master, and slave devices are on a far-field trust loop. Accordingly, the smartwatch communicates far-field with the master device and with the slave device. For example... Figure 8A As shown in (b), the user scenario involves a user carrying a smartwatch and a slave device, but not the master device. The smartwatch is relatively far from the master device, while the smartwatch is relatively close to the slave device. In this case, the smartwatch and slave device are on a near-field trust ring, while the master device is on a far-field trust ring. The smartwatch communicates with the master device in the far field. It should be noted that although the smartwatch and slave device are physically close, they still communicate in the far field. Figure 8B As shown, in user scenario 3 or 4, the host and smartwatch are in a far-field connection state, and the slave and smartwatch are in a far-field connection state.

[0323] Scenario 1: Communication service flow from host to smartwatch

[0324] S632, The host receives a message-type notification. The host can display the received message-type notification.

[0325] S633: The host sends message-type notifications to the smartwatch via a far-field communication link.

[0326] S634. The smartwatch receives and displays message notifications.

[0327] S635: The host receives and displays an incoming call notification. This notification is not forwarded to the smartwatch.

[0328] S636, The host did not answer the incoming call notification, and the system displays "No call notification received".

[0329] S637: The host sends missed call notifications to the smartwatch via a far-field communication link.

[0330] S638: The smartwatch receives and displays a missed call notification.

[0331] In this scenario, message notifications from the host can be routed to the smartwatch; incoming call notifications from the host will not be routed to the smartwatch, therefore the incoming call notification interface will not be displayed on the smartwatch.

[0332] In some embodiments, if the host receives a message notification from the network side, the host can send the message notification to the wearable device via far-field communication, and the wearable device can display the message notification from the host.

[0333] In some embodiments, a user replies to a message from the host on a wearable device. In response to the user's action, the wearable device can send the reply message to the host via far-field communication, and the host will then send the reply message to the base station.

[0334] In some embodiments, if the host receives an incoming call notification but does not answer it, the host can forward the missed call notification to the smartwatch, and the smartwatch can display the missed call notification from the host.

[0335] Scenario 2: Communication service flow from slave device to smartwatch

[0336] S639. The slave device receives and displays a message-type notification.

[0337] S640: The slave device sends message-type notifications to the smartwatch via a far-field communication link.

[0338] S641. The smartwatch receives and displays message notifications.

[0339] S642. The slave device receives and displays an incoming call notification. This notification is not forwarded to the host device or the smartwatch.

[0340] S643. The slave device did not answer the call notification, and the message "No call notification received" is displayed.

[0341] S644: The slave device sends missed call notifications to the smartwatch via the far-field communication link.

[0342] S645: The smartwatch receives and displays missed call notifications.

[0343] In scenario 2, message notifications from the slave device can be forwarded to the smartwatch; missed call notifications from the slave device can be forwarded to the smartwatch; incoming call notifications from the slave device will not be forwarded to the smartwatch, therefore the incoming call notification interface will not be displayed on the smartwatch.

[0344] In some embodiments, if the slave device receives a message notification from the network side, the slave device can send the message notification to the wearable device via far-field communication, and the wearable device can display the message notification from the slave device.

[0345] In some embodiments, a user replies to a message from a slave device on a wearable device. In response to the user's action, the wearable device can send the reply message to the slave device via far-field communication, and the slave device can then send the reply message to the network side.

[0346] In some embodiments, if the slave device receives a missed call notification but does not answer it, the slave device can forward the missed call notification to the smartwatch, and the smartwatch can display the missed call notification from the slave device.

[0347] It should be noted that in user scenarios 3 and 4, the host, slave, and smartwatch all have mobile data networks enabled. The host and smartwatch communicate with the remote cloud via the trust ring and through the mobile data network, while the slave and smartwatch communicate with the remote cloud via the trust ring and through the mobile data network.

[0348] Comparing the various user scenarios above, it can be seen that, in Figure 6A and Figure 6B In user scenario 1, the communication service of the slave device is transferred to the smartwatch via the host device. Figure 7A and Figure 7B In user scenario 2, the communication service of the slave device is transferred to the smartwatch via the host device. Figure 8A and Figure 8B In user scenarios 3 and 4, the slave device's communication service directly reaches the smartwatch without going through the host device.

[0349] Example 4: Wearable devices display message notifications or call notifications from the host / slave unit, as well as notifications for incoming calls. Notification response methods

[0350] Figure 9A This illustration shows a smartwatch, according to an embodiment of this application, receiving and displaying message notifications or call notifications from two mobile phones. Figure 9A As shown, both mobile phone 1 and mobile phone 2 are connected to a smartwatch. Message notifications or incoming call notifications from mobile phone 1 (shown as new message 1 in the diagram) can be transmitted to the smartwatch for display; similarly, message notifications or incoming call notifications from mobile phone 2 (shown as new message 2 in the diagram) can also be transmitted to the smartwatch for display. For example, message notifications may include application messages, schedules, to-do lists, YOYO suggestions, and other notifications from the phone's notification bar. Incoming call notifications may include incoming call notifications and missed call notifications from the phone.

[0351] When displaying message or call notifications, the smartwatch can also show the phone's identifier, making it easy for users to identify which phone the notification or call is from. Figure 9A As shown, the smartwatch displays new message 1 from phone 1 and new message 2 from phone 2.

[0352] Figure 9B This demonstrates the features supported by the smartwatch in the context of an incoming call.

[0353] Incoming call scenario during near-field communication between the host and the smartwatch

[0354] When the host and smartwatch are in a near-field environment, such as when the user is wearing both the smartwatch and the host, the host and smartwatch communicate with each other via near-field communication. If the host receives an incoming call notification, the notification can be relayed to the smartwatch via a near-field communication link (such as a Bluetooth or Wi-Fi channel). In this scenario, the smartwatch can support the following functions.

[0355] 1) The smartwatch can display incoming call notifications and vibrate to alert the user. In some cases, the smartwatch vibrates together with the main unit (i.e., resonates).

[0356] 2) The smartwatch can display hang-up, answer, and SMS reject buttons in the call notification interface. Responding to the user's action of the hang-up button, the smartwatch can hang up the call. Responding to the user's action of the answer button, the smartwatch can answer the call. Responding to the user's action of the SMS reject button, the smartwatch can hang up the call and reply to the SMS, for example, with a message such as "In a meeting, will contact you later."

[0357] 3) The smartwatch can display an answer button in the incoming call notification interface. In response to the user's action of pressing the answer button, the smartwatch can answer the call.

[0358] 4) If the host does not answer the call, the missed call notification from the host can be transmitted to the smartwatch via the near field communication link, and the missed call notification can be displayed on the smartwatch.

[0359] 5) After hanging up the call, rejecting the call via SMS, ending the call after answering, or receiving a missed call notification, the smartwatch can display the call log, which includes information such as the call number and call duration, or the call log includes the missed call number and the time of the call.

[0360] like Figure 9C As shown in (a), the smartwatch is connected to both the master and slave devices. When the master and the smartwatch are in a near-field environment, when the master receives an incoming call notification, the smartwatch can display the master's incoming call notification. The smartwatch can also respond to user operations by answering or hanging up the call or replying to an SMS message.

[0361] Incoming call scenario during near-field communication between the slave device and the smartwatch

[0362] When the slave device and the smartwatch are in a near-field environment, such as when the user is wearing the smartwatch, master device, and slave device simultaneously, the slave device communicates with the smartwatch via the master device. If the slave device receives an incoming call notification, the notification can be relayed to the smartwatch via the master device through a near-field communication link (such as a Bluetooth or Wi-Fi channel). In this scenario, the smartwatch can support the following functions.

[0363] 1) The smartwatch can display an incoming call notification interface and can vibrate to alert the user. In some cases, the smartwatch vibrates together with the slave device (i.e., resonates).

[0364] 2) The smartwatch can display a hang-up button and an SMS rejection button in the incoming call notification interface. Responding to the user's action of the hang-up button, the smartwatch can hang up the call. Responding to the user's action of the SMS rejection button, the smartwatch can hang up the call and reply to the SMS, for example, with a message such as "In a meeting, will contact you later".

[0365] 3) On the smartwatch side, the answer button is not displayed in the incoming call notification interface.

[0366] 4) When the slave device does not answer the call, the missed call notification from the slave device can be transmitted to the smartwatch via the near field communication link through the host, and the missed call notification can be displayed on the smartwatch.

[0367] 5) Call logs are not displayed on the smartwatch side.

[0368] like Figure 9CAs shown in (b), the smartwatch is connected to both the master and slave devices. When the slave device and the smartwatch are in a near-field environment, when the slave device receives an incoming call notification, the smartwatch can display the incoming call notification from the slave device. The smartwatch can also respond to user operations by hanging up the call or replying to an SMS message.

[0369] Incoming call scenario during far-field communication between the host and the smartwatch

[0370] When the host and the smartwatch are in a far-field environment, such as when the user is wearing the smartwatch but not the host, the host and the smartwatch communicate in the far field. If the host receives an incoming call notification, the call notification will not be forwarded to the smartwatch. Therefore, the smartwatch will not display the incoming call notification interface, will not resonate, and will not be able to hang up / reject SMS calls or answer calls from the host. In addition, the smartwatch will not display the call log.

[0371] It should be noted that if the host does not answer the call, the missed call notification can be directly transmitted to the smartwatch via a far-field communication link (such as a cloud server based on a trust ring or a mobile network provided by a base station), and the missed call notification can be displayed on the smartwatch.

[0372] Incoming call scenario during far-field communication between slave device and smartwatch

[0373] When the slave device and the smartwatch are in a far-field environment, such as when the user is carrying the smartwatch and the slave device but not the master device, or when the user is carrying the smartwatch but not the master device and the slave device, the slave device communicates with the smartwatch in the far field. If the slave device receives an incoming call notification, the incoming call notification will not be forwarded to the smartwatch. Therefore, the smartwatch will not display the incoming call notification interface, will not resonate, and will not be able to hang up / reject SMS calls or answer calls from the slave device. In addition, the smartwatch will not display the call log.

[0374] It should be noted that if the slave device does not answer an incoming call, the missed call notification from the slave device can be directly transmitted to the smartwatch via a far-field communication link (such as a cloud server based on a trust ring or a mobile network provided by a base station), and the missed call notification from the slave device can be displayed on the smartwatch.

[0375] It should be noted that in the embodiments of this application, "greater than" can be replaced with "greater than or equal to", "less than or equal to" can be replaced with "less than", or "greater than or equal to" can be replaced with "greater than", and "less than" can be replaced with "less than or equal to".

[0376] The various embodiments described herein can be independent solutions or combinations thereof based on their inherent logic, and all such solutions fall within the protection scope of this application.

[0377] The foregoing mainly describes the solutions provided by the embodiments of this application from the perspective of method steps. It is understood that, in order to achieve the above functions, the electronic device implementing this method includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should recognize that, in conjunction with the units and algorithm steps of the various examples described in 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 protection of this application.

[0378] This application embodiment can divide an electronic device into functional modules based on the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, other feasible division methods may exist. The following description uses the division of functional modules according to each function as an example.

[0379] Figure 10 This is a schematic block diagram of a processing apparatus 1000 for inter-device communication service transfer provided in an embodiment of this application. The apparatus 1000 can be used to perform the actions performed by the wearable device in the above method embodiments. The apparatus 1000 includes a networking unit 1001 and a display unit 1002.

[0380] The networking unit 1001 is used to enable the wearable device to establish a Bluetooth connection with the first device; and to enable the detection of nearby available devices.

[0381] Display unit 1002 is used to display first prompt information on the wearable device. The first prompt information is used to prompt the wearable device to detect a second device and whether to associate the second device with the wearable device. The first device and the second device are mobile phones.

[0382] The display unit 1002 is also used to respond to the user's confirmation operation by displaying a second prompt message on the wearable device. The second prompt message is used to indicate that the wearable device, the first device, and the second device are associated devices with the same user account.

[0383] The display unit 1002 is also configured to enable the wearable device to display the first notification when the first device displays the first notification.

[0384] The display unit 1002 is also configured to enable the wearable device to display the second notification when the second device displays the second notification.

[0385] Wherein, the first notification is a message notification and / or a call notification, and the second notification is a message notification and / or a call notification.

[0386] The message notifications include SMS messages, application messages, calendar reminders, to-do reminders, flight reminders, express delivery reminders, alarm reminders, note reminders, and / or YOYO suggestion reminders.

[0387] The incoming call notifications are either incoming call notifications or missed call notifications.

[0388] The multi-device communication service transfer processing device provided in this application embodiment can realize that: a wearable device can be associated with two mobile phones at the same time, and message notifications or call notifications from multiple devices associated with a smartwatch can be transferred to the smartwatch. The smartwatch can simultaneously display message notifications or call notifications from any one device, which meets the user's need to conveniently view and process message and call notifications from multiple mobile phones through the wearable device and improves the user experience.

[0389] The apparatus 1000 according to the embodiments of this application can correspond to the execution of the method described in the embodiments of this application, and the above and other operations and / or functions of the units in the apparatus 1000 are respectively for implementing the corresponding process of the method, which will not be described again here for the sake of brevity.

[0390] This application also provides a chip coupled to a memory, which is used to read and execute computer programs or instructions stored in the memory to perform the methods in the above embodiments.

[0391] This application also provides an electronic device, namely a first device having a host role, the electronic device including a chip for reading and executing computer programs or instructions stored in a memory, such that the methods in the various embodiments are executed.

[0392] This application also provides an electronic device, namely a second device having a slave role, the electronic device including a chip for reading and executing computer programs or instructions stored in a memory, such that the methods in the various embodiments are executed.

[0393] This application provides a communication system, which includes a wearable device, a first device having a host role, and a second device having a slave role.

[0394] Figure 11 This is a schematic block diagram of a communication system provided in an embodiment of this application. Figure 11As shown, the communication system 1100 includes a wearable device 1101, a first device 1102 with a host role, and a second device 1103 with a slave role. This communication system can realize the flow of communication services between multiple devices.

[0395] This embodiment also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the aforementioned method steps to implement the multi-device communication service transfer processing method described in the above embodiment.

[0396] This embodiment also provides a computer program product. The computer-readable storage medium stores program code. When the computer program product is run on a computer, it causes the computer to perform the above-mentioned related steps to realize the processing method for the flow of communication services between multiple devices in the above embodiment.

[0397] In this embodiment, the electronic device, computer-readable storage medium, computer program product or chip 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 of the corresponding methods provided above, and will not be repeated here.

[0398] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0399] In this article, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The symbol " / " in this article indicates that the related objects are in an "or" relationship; for example, A / B means A or B.

[0400] The terms "first" and "second," etc., used in the specification and claims herein are used to distinguish different objects, not to describe a specific order of objects. In the description of embodiments in this application, unless otherwise stated, "multiple" means two or more; for example, multiple processing units refer to two or more processing units, etc.; multiple elements refer to two or more elements, etc.

[0401] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for processing communication service transfer between multiple devices, characterized in that, include: The wearable device establishes a Bluetooth connection with the first device; The wearable device detects nearby available devices; The wearable device displays a first prompt message, which prompts the wearable device to detect a second device and whether to associate the second device with the wearable device. The first device and the second device are both mobile phones; In response to the user's confirmation, the wearable device displays a second prompt message, which indicates that the wearable device, the first device, and the second device are associated devices with the same user account. When the first device displays the first notification, the wearable device displays the first notification; When the second device displays the second notification, the wearable device displays the second notification.

2. The method according to claim 1, characterized in that, The first notification is a message notification and / or a call notification, and the second notification is a message notification and / or a call notification; The message notifications include SMS messages, application messages, calendar reminders, to-do reminders, flight reminders, express delivery reminders, alarm reminders, note reminders, and / or YOYO suggestion reminders; The incoming call notifications are either incoming call notifications or missed call notifications.

3. The method according to claim 1 or 2, characterized in that, The method further includes: When the wearable device displays the first notification, the wearable device also displays that the first notification is a notification from the first device; When the wearable device displays the second notification, the wearable device also displays that the second notification is a notification from the second device.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: When the wearable device displays the incoming call notification from the first device, the wearable device displays an answer control, a hang-up control, and a message reply control; When the wearable device displays the incoming call notification from the second device, the wearable device displays hang-up and message reply controls, but does not display answer controls.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The wearable device communicates with the first device in the near field, and the first device communicates with the second device in the near field. Wherein, the step of the wearable device displaying the first notification when the first device displays the first notification includes: when the first device displays the first notification and the first notification is a message notification, the wearable device displays the message notification; when the first device displays the first notification and the first notification is an incoming call notification, the wearable device displays the incoming call notification. The step of displaying the second notification on the wearable device when the second device displays the second notification includes: when the second device displays the second notification and the second notification is a message notification, the wearable device displays the message notification; when the second device displays the second notification and the second notification is an incoming call notification, the wearable device displays the incoming call notification.

6. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The wearable device communicates with the first device in the near field, and the first device communicates with the second device in the far field. When the second device displays the second notification and the second notification is an incoming call notification, the wearable device does not display the incoming call notification; Wherein, the step of the wearable device displaying the first notification when the first device displays the first notification includes: when the first device displays the first notification and the first notification is a message notification, the wearable device displays the message notification; when the first device displays the first notification and the first notification is an incoming call notification, the wearable device displays the incoming call notification. The step of displaying the second notification on the wearable device when the second device displays the second notification includes: when the second device displays the second notification and the second notification is a message notification, the wearable device displays the message notification; when the second device displays the second notification and the second notification is a missed call notification, the wearable device displays the missed call notification.

7. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The wearable device communicates with the first device in the far field, and the wearable device communicates with the second device in the far field. When the first device displays the first notification and the first notification is an incoming call notification, the wearable device does not display the incoming call notification; When the second device displays the second notification and the second notification is an incoming call notification, the wearable device does not display the incoming call notification; Wherein, the step of the wearable device displaying the first notification when the first device displays the first notification includes: when the first device displays the first notification and the first notification is a message notification, the wearable device displays the message notification; when the first device displays the first notification and the first notification is a missed call notification, the wearable device displays the missed call notification. The step of displaying the second notification on the wearable device when the second device displays the second notification includes: when the second device displays the second notification and the second notification is a message notification, the wearable device displays the message notification; when the second device displays the second notification and the second notification is a missed call notification, the wearable device displays the missed call notification.

8. The method according to any one of claims 1 to 7, characterized in that, When the wearable device communicates with the first device and the first device communicates with the second device, message notifications, incoming call notifications or missed call notifications from the first device are directly forwarded to the wearable device, and message notifications, incoming call notifications or missed call notifications from the second device are forwarded by the first device and then forwarded to the wearable device. When the wearable device communicates with the first device in the near field and the first device communicates with the second device in the far field, message notifications, incoming call notifications or missed call notifications from the first device are directly forwarded to the wearable device, and message notifications or missed call notifications from the second device are forwarded by the first device and then forwarded to the wearable device. When the wearable device communicates with the first device and the second device in a far-field communication, message notifications or missed call notifications from the first device are directly forwarded to the wearable device, and message notifications or missed call notifications from the second device are also directly forwarded to the wearable device.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: The wearable device acquires a first distance value between itself and the first device; The wearable device establishes a trust ring communication link among itself, the first device, and the second device based on the first distance value.

10. The method according to claim 9, characterized in that, The wearable device establishes a trust-loop communication link among itself, the first device, and the second device based on the first distance value, including: When the first distance value is less than the first threshold, the wearable device establishes a trust loop near-field communication link with the first device, and the wearable device instructs the first device to establish a trust loop communication link with the second device; When the first distance value is greater than or equal to the first threshold, the wearable device establishes a far-field communication link with the first device and the second device respectively.

11. The method according to claim 10, characterized in that, The wearable device instructs the first device and the second device to establish a trust ring communication link, including: The wearable device acquires a second distance value between itself and the second device; If the second distance value is less than the first threshold, the wearable device instructs the first device to establish a trust loop near-field communication link with the second device; If the second distance value is greater than or equal to the first threshold, the wearable device instructs the first device to establish a trust loop far-field communication link with the second device.

12. The method according to claim 11, characterized in that, The establishment of the trust loop near-field communication link includes: establishing the trust loop near-field communication link through short-range wireless communication; the short-range wireless communication method includes Bluetooth communication or wireless high-fidelity Wi-Fi communication; The establishment of the trust ring far-field communication link includes: establishing the trust ring far-field communication link through cloud services.

13. The method according to any one of claims 1 to 12, characterized in that, The method further includes: The wearable device sets the first device as the host and the second device as the slave.

14. The method according to claim 13, characterized in that, After the wearable device sets the first device as the host and the second device as the slave, the method further includes: The wearable device assigns a first data forwarding permission to the first device, which has a host role. The wearable device assigns a second data forwarding permission to the second device, which has a slave role; Wherein, the second data forwarding permission includes the first device as the host role and the second device as the slave role. When a communication link is established between the second device and the first device, the second device is allowed to send message-type notifications or call-type notifications from the second device to the first device with the host role. The first data forwarding permission includes the first device as the host and the second device as the slave. When a near-field communication link is established between the first device and the wearable device, the first device is allowed to forward message-type notifications or call-type notifications from the second device, which has the slave role, to the wearable device.

15. A method for processing communication service transfer between multiple devices, characterized in that, include: The first device, the wearable device, and the second device establish a device association relationship under the same user account; wherein, the user accounts logged in by the wearable device, the first device, and the second device are the same; the first device and the second device are both mobile phones; The first device communicates with the wearable device in the near field. The first device receives a first notification from the network side, displays the first notification, and sends the first notification to the wearable device via a near-field communication link. The first notification includes message notifications or incoming call notifications. The first device receives a second notification from the second device and forwards the second notification to the wearable device via a near-field communication link. The second notification is a message-type notification or a call-type notification received by the second device from the network side. The first device communicates with the wearable device in the far field; the first device receives a third notification from the network side and sends the third notification to the wearable device through the far field communication link, the third notification being a message notification or a missed call notification; The message notifications include SMS messages, application messages, calendar reminders, to-do reminders, flight reminders, express delivery reminders, alarm reminders, note reminders, and / or YOYO suggestion reminders; The incoming call notifications are either incoming call notifications or missed call notifications.

16. The method according to claim 15, characterized in that, The first device receives a second notification from the second device, including: The first device communicates with the second device via near-field communication. The first device receives the second notification from the second device through the near-field communication link. The second notification is a message notification, an incoming call notification, or a missed call notification; or... The first device communicates with the second device in the far field. The first device receives the second notification from the second device through the far field communication link. The second notification is a message notification or a missed call notification.

17. The method according to claim 15 or 16, characterized in that, The method further includes: The first device receives the first data forwarding permission assigned by the wearable device; The first data forwarding permission includes the first device as the host and the second device as the slave. When a near-field communication link is established between the first device and the wearable device, the first device is allowed to forward message-type notifications or call-type notifications from the second device, which has the slave role, to the wearable device.

18. The method according to any one of claims 15 to 17, characterized in that, The method further includes: The first device receives a first indication message sent by the wearable device; in response to the first indication message, the first device establishes a trust-loop near-field communication link with the wearable device; or... The first device receives a second indication message sent by the wearable device; in response to the second indication message, the first device establishes a trust loop communication link with the second device; or... The first device receives a third indication message sent by the wearable device; in response to the third indication message, the first device establishes a trust-loop far-field communication link with the wearable device.

19. A method for processing communication service transfer between multiple devices, characterized in that, include: The second device, the wearable device, and the first device establish a device association relationship under the same user account; wherein, the user accounts logged in by the wearable device, the first device, and the second device are the same; the first device and the second device are both mobile phones; The second device receives a second notification from the network side, which is either a message notification or a call notification; When the second device establishes a trust loop near-field communication link with the first device, the second device sends the message-type notification or call-type notification to the first device, which then forwards it to the wearable device. When the second device establishes a trust ring far-field communication link with the first device, the second device sends the message-type notification to the first device, which then forwards it to the wearable device. When the second device establishes a trust ring far-field communication link with the wearable device, the second device will directly send the message-type notification to the wearable device; The message notifications include SMS messages, application messages, calendar reminders, to-do reminders, flight reminders, express delivery reminders, alarm reminders, note reminders, and / or YOYO suggestion reminders; The incoming call notifications are either incoming call notifications or missed call notifications.

20. The method according to claim 19, characterized in that, The method further includes: The second device receives the second data forwarding permission; The second data forwarding permission includes the first device as the host and the second device as the slave. When a communication link is established between the second device and the first device, the second device is allowed to send message-type notifications or call-type notifications from the second device with the slave role to the first device.

21. The method according to claim 19 or 20, characterized in that, The method further includes: The second device receives a fourth indication message; in response to the fourth indication message, the second device establishes a trust-loop near-field communication link with the first device; or, The second device receives the fifth indication information; in response to the fifth indication information, the second device establishes a trust-loop far-field communication link with the first device; or, The second device receives a sixth instruction message; in response to the sixth instruction message, the second device establishes a trust ring far-field communication link with the wearable device.

22. A wearable device, characterized in that, The wearable device includes: one or more processors, and a memory; the memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the wearable device to perform the method as described in any one of claims 1 to 14.

23. An electronic device, characterized in that, The electronic device includes: one or more processors, and a memory; the memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the electronic device to perform the method as described in any one of claims 15 to 18.

24. An electronic device, characterized in that, The electronic device includes: one or more processors, and a memory; the memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the electronic device to perform the method as described in any one of claims 19 to 21.

25. A communication system, characterized in that, The communication system includes the wearable device as claimed in claim 22, the electronic device as claimed in claim 23, and the electronic device as claimed in claim 24.

26. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when executed on an electronic device, cause the electronic device to perform the method as claimed in any one of claims 1 to 14, or the method as claimed in any one of claims 15 to 18, or the method as claimed in any one of claims 19 to 21.

Images