A multi-device networking system, method and terminal device

By enabling collaborative control and distributed database updates among terminal devices, the problem of insufficient interaction capabilities of terminal devices is solved, thereby improving the user's operating experience and ecosystem experience.

CN117811947BActive Publication Date: 2026-11-10HUAWEI TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202211216793.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-09-30
Publication Date
2026-11-10
Estimated Expiration
2042-09-30

AI Technical Summary

Technical Problem

In existing multi-device networking systems, the interaction capabilities between terminal devices are insufficient, resulting in high operation complexity, poor user experience, and difficulty in meeting the collaborative needs of multiple scenarios.

Method used

The system detects and responds to user operations through a single terminal device, sends instruction messages to enable collaborative control among multiple terminal devices, displays a control interface to perceive a larger network ecosystem, supports the updating and synchronization of a distributed database, and refreshes the interface in a timely manner to reflect structural changes.

Benefits of technology

It reduces the complexity of operation, improves the user's operating experience, enables collaborative management of terminal devices and task flow in more scenarios, and provides a better ecosystem experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117811947B_ABST
    Figure CN117811947B_ABST
Patent Text Reader

Abstract

The application relates to the terminal field and discloses a multi-device networking system, a multi-device networking method and a terminal device, which are used for providing multi-device networking across terminal devices, thereby improving the interactive capability of the networking terminal device and providing a better terminal device ecological experience for a user. The system can at least include a first terminal device, a second terminal device and a third terminal device. The first terminal device can display a control interface according to a two-level networking formed by a plurality of terminal devices. Based on this, the first terminal device can detect a user operation of a user on the terminal device displayed on the control interface; and in response to the user operation, the collaborative management between other terminal devices in connection in the networking can be realized. Therefore, the application can conveniently realize the collaborative control between terminal devices through the control interface, such as realizing the collaboration between the connected second terminal device and the third terminal device, so that the multi-device collaboration in more scenes can be met.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a multi-device networking system, method and terminal device. Background Technology

[0002] In recent years, with the rapid development of the electronics industry and communication technology, smart terminal devices are taking on increasingly diverse forms, such as mobile phones, smart TVs, smart speakers, and smart bracelets, making people's lives increasingly intelligent. To facilitate more convenient interaction between devices, collaborative management applications based on multi-device networking are becoming increasingly widespread, such as those based on… A "super terminal" consisting of multiple devices operating the system.

[0003] Currently, multi-device networks typically consist of a terminal device and at least one other terminal device connected to it; it is understandable that networks composed of different terminal devices will have different characteristics. Therefore, improving the interaction capabilities of terminal devices in distributed networking is of significant research importance. Summary of the Invention

[0004] This application provides a multi-device networking system, method, and terminal device to enable multi-device networking across terminal devices. Through one terminal device in the multi-device network, collaborative control among other connected terminal devices within the network can be easily achieved, thereby meeting the needs of terminal device collaboration in more scenarios and providing users with a better ecosystem experience.

[0005] Firstly, this application provides a multi-device networking system. The system may include at least a first terminal device, a second terminal device, and a third terminal device. The first terminal device is configured to display a first interface, which includes multiple terminal device identifiers, including the identifier of the second terminal device and the identifier of the third terminal device; wherein the second terminal device and the third terminal device are connected. The first terminal device is further configured to detect and respond to a first operation on the first interface by sending a first instruction message to the second terminal device, the first instruction message instructing the second terminal device to cooperate with the third terminal device. The second terminal device is configured to receive the first instruction message and cooperate with the third terminal device according to the first instruction message.

[0006] In this system, a control interface can be displayed on the first terminal device. This interface can be tailored to the multi-level network in which the first terminal device is located. Compared to implementations where the first terminal device can only perceive directly connected terminal devices, this system allows the first terminal device to perceive terminal devices further connected to directly connected terminal devices, thus forming a larger network ecosystem to meet a wider range of multi-device collaboration scenarios. Furthermore, the control interface on the first terminal device not only enables collaboration between the first terminal device and connected terminal devices, but also allows for collaborative control between other connected terminal devices besides the first terminal device. This reduces operational complexity in some scenarios and improves the user experience.

[0007] In one possible design, the first terminal device is further configured to: display a second interface when it is determined that the second terminal device and the third terminal device have collaborated, the second interface indicating that the second terminal device and the third terminal device have collaborated. Optionally, the second terminal device may determine that it can collaborate with the third terminal device based on a first instruction message from the first terminal device; in this scenario, the second terminal device may return a collaboration success response message to the first terminal device, so that the first terminal device can update to the second interface in a timely manner based on the response message. Alternatively, after determining that it can collaborate with the third terminal device, the second terminal device may also update its distributed database and synchronize the updated distributed database to the first terminal device, so that the first terminal device can update to the second interface based on the updated distributed database. It should be understood that the terminal device can support the display of the user interface based on the distributed database, and can also update the distributed database in response to user operations on the user interface, thereby enabling distributed networking of more terminal devices based on the distributed database.

[0008] In this design, the first terminal device can refresh the control interface in a timely manner based on the collaborative results of the second and third terminal devices, so that users can be informed of the structural changes of the distributed network in a timely manner, so as to achieve more accurate business processing and ensure user experience.

[0009] In one possible design, the first terminal device can display a first interface in various ways. The first interface includes a first network structure composed of the identifiers of the multiple terminal devices. The first network structure may include, for example, the identifier of the first terminal device and the identifiers of the terminal devices connected to it, wherein the terminal devices connected to the first terminal device may include a second terminal device; alternatively, it may include the identifier of the second terminal device and the identifiers of the terminal devices connected to it, wherein the terminal devices connected to the second terminal device may include a third terminal device. In the first network structure, the second terminal device is the central device, and the devices connected to the second terminal device are peripheral devices of the second terminal device. If the second terminal device is a peripheral device of the first terminal device, the first terminal device can also obtain the identifiers of the devices connected to the second terminal device and also consider the devices connected to the second terminal device as peripheral devices of the first terminal device, thereby controlling the two peripheral devices connected to each other among the peripheral devices of the first terminal device to coordinate. For ease of understanding, the first terminal device can act as a super central device in the first network structure, and can obtain the identifiers of the peripheral devices of other central devices that are its peripheral devices. For example, the first terminal device can obtain the identifier of its connected third terminal device through the second terminal device.

[0010] Based on the first network structure described above, the first terminal device can display a first interface, including but not limited to one of the following display methods:

[0011] Display method A: The first interface of the first terminal device may include: the identifier of the second terminal device and the identifier of the terminal device connected to the second terminal device; wherein, the terminal device connected to the second terminal device includes the third terminal device.

[0012] Optionally, the first interface may only include the identifier of the second terminal device and the identifier of the terminal device connected to the second terminal device, wherein the terminal device connected to the second terminal device includes the third terminal device. For example, in a scenario where collaborative control of the second terminal device and its connected terminal devices is required, the system can implement a control interface based on the first terminal device, displaying only the identifier of the second terminal device and the identifier of its connected terminal devices, so as to facilitate convenient control of the collaborative relationship between the second terminal device and its connected terminal devices from the first terminal device. It should be understood that in this scenario, the first interface may also include controls for returning to the interface displayed on the first terminal device, such as a back control, a gesture operation to return to the previous level display interface, or a voice command.

[0013] Alternatively, the first interface may not include a device connected to the first terminal device but not to the second terminal device. For example, the first interface may display the identifier of the second terminal device in the center, and the identifier of the terminal device connected to the second terminal device may be displayed around the identifier of the second terminal device. It should be understood that the first terminal device may also be a terminal device connected to the second terminal device, and its identifier may be displayed in the first interface. This allows the user to more quickly return to the control interface displayed on the first terminal device by operating on the identifier of the first terminal device.

[0014] It is understood that before displaying the first interface, the first terminal device may also display a third interface, which may include the identifier of the first terminal device and the identifier of a terminal device connected to the first terminal device; wherein, the terminal device connected to the first terminal device includes the second terminal device. In this case, on the third interface, the first terminal device can be used to display the first interface when an operation acting on the identifier of the second terminal device is detected. This facilitates switching between displays for different collaborative scenarios.

[0015] This method allows for more precise display of scenario-related terminal devices based on the needs of collaborative scenarios, enabling faster retrieval of terminal devices used for collaboration within that scenario.

[0016] Display method B: The first interface of the first terminal device may include: the identifier of the second terminal device, and the identifier of the terminal device connected to the second terminal device; wherein the terminal device connected to the second terminal device includes the third terminal device. Furthermore, the first interface may also include: the identifier of the first terminal device, and the identifier of the terminal device connected to the first terminal device; wherein the terminal device connected to the first terminal device includes the second terminal device.

[0017] Optionally, before displaying the first interface, the first terminal device may also display a third interface, which includes the identifier of the first terminal device and the identifier of a terminal device connected to the first terminal device; wherein the terminal device connected to the first terminal device includes the second terminal device. In this scenario, when the first terminal device displays the first interface, it is specifically used to display the first interface upon detecting an operation applied to the identifier of the second terminal device. For example, a user can double-click the identifier of the second terminal device to expand and display the identifier of the terminal device connected to the second terminal device. It can be understood that this scenario allows for a more accurate display of collaborative scenarios, avoiding interference with collaborative operations.

[0018] Alternatively, the first interface displayed by the first terminal device can also display a relatively complete network structure. For example, the first interface can display not only the identifier of the first terminal device and the identifiers of terminal devices directly connected to the first terminal device (such as the identifier of the second terminal device), but also the identifiers of terminal devices indirectly connected to the first terminal device (such as the identifier of the third terminal device). For instance, the first interface could display the first terminal device in the center, the second terminal device around it, and the third terminal device around it. This scenario allows for a more comprehensive display of the network structure, providing a more intuitive understanding of the connection status of the terminal devices within the network.

[0019] It is understandable that the first terminal device can choose how to display the first interface based on information such as business scenarios and user needs. For example, if the number of terminal devices included in the network is less than a preset data threshold, a more complete network structure can be displayed (which can be understood as an expanded display mode); if the number of terminal devices included in the network is greater than or equal to the preset threshold, only the identifier of the first terminal device and the identifiers of the terminal devices directly connected to the first terminal device can be displayed (which can be understood as a collapsed display mode). Furthermore, when responding to an operation applied to one of the terminal devices (such as the second terminal device), the identifier of the second terminal device and the identifiers of the terminal devices connected to the second terminal device can be switched to be displayed, or the identifiers of the terminal devices connected to the second terminal device can be expanded and displayed on the current display interface.

[0020] Based on various control interfaces of the first terminal device, the first terminal device can respond to user operations to realize collaborative management between terminal devices, such as initiating collaboration and discontinuing collaboration. Scenarios for collaboration between terminal devices may include, but are not limited to:

[0021] In one possible scenario, the first interface is also used to indicate that the first terminal device and the second terminal device have collaborated. In this scenario, by further implementing collaboration between the second terminal device and the third terminal device, collaborative scenarios can be obtained, including collaboration between the first terminal device and the second terminal device, and collaboration between the second terminal device and the third terminal device.

[0022] In another possible scenario, the first terminal device is further configured to: detect a second operation, the second operation being used to instruct a first coordinating device combination to further collaborate with the first terminal device, the first coordinating device combination being used to indicate the already collaborating second terminal device and the third terminal device; and, in response to the second operation, display a fourth interface, the fourth interface being used to indicate that the first terminal device has further collaborated with the first coordinating device combination. Optionally, if the first interface includes the identifier of the first terminal device, the second operation can be detected in the first interface. Alternatively, if the first interface displays the identifier of the second terminal device in the middle position, the system can first return to the interface where the identifier of the first terminal device is displayed in the middle position (e.g., in response to a user operation or user instruction acting on the identifier of the first terminal device in the first interface), and detect the second operation in that interface; it can be understood that the second terminal device and the third terminal device have already collaborated in that interface.

[0023] Through the aforementioned scenarios, the control interface of the first terminal device not only enables collaboration between two terminal devices, but also allows for collaboration between more terminal devices based on existing collaborative combinations, thereby facilitating the flow of collaborative tasks across more terminal devices. Therefore, this application can satisfy more collaborative scenarios, and the control interface on the first terminal device facilitates the management of collaboration between more terminal devices, resulting in a better ecosystem user experience.

[0024] Furthermore, when the first terminal device displays various control interfaces according to the first network structure to which the first terminal device is located, the first network structure can be obtained through, but is not limited to, the following methods:

[0025] Method A: In response to a user search operation, a device scan is performed based on preset scanning rules; based on the device scan results, the first network structure is displayed on the first interface. For example, the preset scanning rules may be one or more of information such as user account, device type, and wireless communication network type. Furthermore, after scanning for a terminal device, the first terminal device can establish a connection with the scanned terminal device; for example, after scanning for a second terminal device, the first terminal device can establish a connection with the second terminal device; similarly, after scanning for a third terminal device, the second terminal device can establish a connection with the third terminal device.

[0026] Method B: Detect and respond to user operations on any control interface of the first terminal device, and display a settings interface; wherein the settings interface is used to provide an entry point for manually adding terminal devices; detect and respond to the user's manual addition of a terminal device on the settings interface, and display a control interface after updating the first network structure; wherein the updated first network structure includes the identifier of the manually added terminal device.

[0027] For example, the first terminal device can also receive user feedback on the structural relationship of newly added terminal devices in the first network structure to obtain a more accurate network structure. In the updated first network structure, the structural relationship between the identifiers of the terminal devices and the identifiers of the first terminal devices is a preset structural relationship. For instance, the first terminal device can determine the structural relationship of the newly added terminal devices based on the corresponding control interface. For example, on an interface displaying the identifiers of the first terminal device and its connected terminal devices, the structural relationship of the newly added terminal device could be "connected to the first terminal device." Similarly, on an interface displaying the identifiers of the second terminal device and its connected terminal devices, the structural relationship of the newly added terminal device could be "connected to the second terminal device." Alternatively, the addition operation can also be used to indicate the target structural relationship of the terminal devices in the updated first network structure. The updated first network structure also includes the identifiers of the terminal devices displayed based on the target structural relationship. For example, in the settings interface, not only can the device identifier of the newly added terminal device be added, but also the terminal devices connected to the newly added terminal device can be added.

[0028] Method C: Detect and respond to a third operation on any control interface of the first terminal device, and display a settings interface; wherein the settings interface is used to provide an entry point for manually updating scanning rules; detect and respond to an addition operation by the user on the settings interface for updating scanning rules, and display a control interface after updating the first network structure; wherein the updated first network structure includes the identifiers of terminal devices scanned based on the updated scanning rules.

[0029] Based on the above implementation methods, the first terminal device can achieve multi-level networking through automatic scanning or receiving manual additions, and display the multi-level networking structure on the control interface of the first terminal device to show to the user.

[0030] Based on the existing collaboration between multiple terminal devices, these devices can perform collaborative processing of services, which may include the following processing scenarios:

[0031] In a possible collaborative scenario, where the first terminal device and the second terminal device have already collaborated, and the second terminal device and the third terminal device have already collaborated, the first terminal device is further configured to: if a first instruction for instructing the processing of the first task is detected, in response to the first instruction, execute a first sub-task of the first task through the first collaborative device; the second terminal device is further configured to: receive task data of the first sub-task, and execute the first sub-task collaboratively through the second terminal device and the third terminal device.

[0032] In this design, based on user operations implemented on the control interface of the first terminal device, the first terminal device, when in collaboration, can achieve collaborative processing of business according to the current business scenario. This improves the user experience across multiple terminal devices.

[0033] In another possible collaborative scenario, the second terminal device is further configured to: if a first event for processing the second task is detected, in response to the first event, execute a second sub-task of the second task through the third terminal. Specifically, when the second terminal device detects the first event for processing the second task, it is configured to: detect a first user operation on a first display interface of the second terminal device, where the first user operation is used to generate the second task, in a scenario where the second terminal device and the third terminal device are already collaborating; or, in a scenario where the first terminal device and the second terminal device are already collaborating, and the second terminal device and the third terminal device are already collaborating, receive task information from the first terminal device, where the task information is used to indicate task data for the second task.

[0034] Wherein, the second terminal device is a device with display function, and the third terminal device is a device with audio playback function; the second task is a playback task; the second subtask is the audio playback task of the playback task; the second terminal device is further configured to, in response to the first event, display the display data of the playback task, and send the audio data of the playback task to the third terminal device, so that the third terminal device can execute the audio playback task of the audio data; the third terminal device is further configured to receive the audio data and play the audio data.

[0035] In this design, the second terminal device can receive collaborative control from the user on the control interface of the first terminal device, enabling collaboration with the third terminal device. Furthermore, the second terminal device can also act as a collaborative device with the first terminal device. Based on this, the second terminal device can collaboratively process tasks from the first terminal device, and can also have collaborative tasks and its own tasks processed collaboratively by the third terminal device. Therefore, this enhances the user experience across multiple terminal devices.

[0036] In one possible design, before displaying the first interface, the first terminal device is further configured to: obtain, via the second terminal device, an identifier of a terminal device connected to the second terminal device, wherein the terminal device connected to the second terminal device includes the third terminal device. Specifically, when the first terminal device obtains the identifier of the terminal device connected to the second terminal device via the second terminal device, it can be implemented by: sending a request message to the second terminal device; and receiving, via the second terminal device, the identifier of the terminal device connected to the second terminal device sent according to the request message; for example, the request message could be a synchronization request message, used to request the second terminal device to synchronize a distributed database.

[0037] In this design, the first terminal device can obtain the identifier of the further connected terminal device through the connected terminal device, which makes it easier for the first terminal device to obtain the network structure, thereby enabling more accurate control in the network.

[0038] In one possible design, the first terminal device is further configured to: before displaying the first interface, update a distributed database on the first terminal device based on the identifier of the scanned terminal device and the identifier of the terminal device connected to the second terminal device obtained through the second terminal device, wherein the distributed database is used to indicate the structural relationships between multiple terminal devices; it is understood that if the distributed database does not exist on the first terminal device, it can be created first. When the first terminal device displays the first interface, it is specifically configured to: display the first interface according to the structural relationships.

[0039] In this design, the first terminal device can display a control interface through updates to the distributed database. Therefore, the system can support multi-level distributed networking through distributed data support.

[0040] In one possible design, before updating the distributed database on the first terminal device, the first terminal device is further configured to: perform a device scan, wherein the scanned devices include the second terminal device, and send a synchronization request message to the second terminal device. The second terminal device is further configured to: after receiving the synchronization request message, send a first database synchronization message to the first terminal device; or, it may initiate a device scan based on the synchronization request message, first write the detected terminal devices into the distributed database of the second terminal device, and send a first database synchronization message to the first terminal device, wherein the first database synchronization message includes the identifiers of the terminal devices in the distributed database on the second terminal device, wherein the distributed database on the second terminal device includes the identifiers of the terminal devices connected to the second terminal device. Then, the first terminal device is further configured to: receive the first database synchronization message sent by the second terminal device. When updating the distributed database on the first terminal device, the first terminal device is specifically configured to: update the identifiers of the terminal devices connected to the second terminal device in the first database synchronization message, as well as the connection relationship between the identifiers of the terminal devices connected to the second terminal device and the second terminal device, to the distributed database on the first terminal device.

[0041] In this design, in a distributed network, the first terminal device can synchronize a distributed database with the connected terminal devices. This allows the first terminal device to promptly perceive changes in the structural relationships of the connected terminal devices, and thus update the control interface in a timely manner based on the synchronized distributed database, avoiding any impact on the user's collaborative experience.

[0042] In one possible design, when the first terminal device displays the first interface, it is specifically configured to: display the first interface based on a distributed database on the first terminal device, wherein the distributed database indicates the structural relationships between multiple terminal devices. When the first terminal device displays the second interface, it is specifically configured to: receive a second database synchronization message sent by the second terminal device, wherein the second database synchronization message indicates that the second terminal device and the third terminal device have collaborated; update the distributed database based on the second database synchronization message; and display the second interface based on the updated distributed database.

[0043] In this design, in the distributed network, when a terminal device connected to the first terminal device updates the distributed database due to reasons such as collaboration or device shutdown, the distributed database can be synchronized with the first terminal device after each update or periodically. This allows the first terminal device to promptly perceive changes in the structural relationships of the connected terminal devices, and thus update the control interface in a timely manner based on the synchronized distributed database, avoiding impact on the user's collaborative experience.

[0044] In one possible design, the system further includes a fourth terminal device and a fifth terminal device; the first terminal device is further configured to display a fifth interface, the fifth interface including multiple terminal device identifiers, the multiple terminal device identifiers including the identifier of the fourth terminal device and the identifier of the fifth terminal device; wherein the fourth terminal device and the fifth terminal device are connected; the first terminal device is further configured to detect a third operation on the fifth interface, the third operation being used to instruct the fourth terminal device and the fifth terminal device to cooperate; the first terminal device is further configured to display a sixth interface when it is determined that the fourth terminal device and the fifth terminal device cannot cooperate, the sixth interface being used to indicate that the cooperation between the fourth terminal device and the fifth terminal device has failed.

[0045] In this design, when controlling the collaboration of other terminal devices through the control interface of the first terminal device, there may be scenarios where collaboration succeeds, as described above, and scenarios where collaboration fails. When the first terminal device determines that collaboration has failed in response to user operation, it can prompt the user on the control interface to avoid affecting the user experience. Furthermore, since the first terminal device in this system can sense the device status of connected terminal devices, it can promptly remind the user and avoid conflicts with existing collaborations, such as preempting a collaborating terminal device and causing the ongoing collaboration to be interrupted.

[0046] In one possible design, the first terminal device is used to determine that the fourth terminal device and the fifth terminal device cannot cooperate when the first terminal device is used to: determine that the fourth terminal device and the fifth terminal device cannot cooperate based on one or more of the following information: the device type of the fourth terminal device, the device status of the fourth terminal device, the device type of the fifth terminal device, or the device status of the fifth terminal device.

[0047] In this design, based on the type or status of the connected terminal device perceived by the first terminal device, the user can be promptly notified or the terminal device's business processing can be avoided when reasons such as type conflict, device busy, or disconnection are determined.

[0048] In one possible design, the first terminal device is specifically configured to: determine that the fourth terminal device and the fifth terminal device cannot cooperate when the fourth terminal device is already in a cooperative state based on the device state of the fourth terminal device; or, determine that the fourth terminal device and the fifth terminal device cannot cooperate when the fifth terminal device is already in a cooperative state based on the device state of the fifth terminal device.

[0049] In this design, a single terminal device can be scanned and connected to multiple terminal devices in different network structures (e.g., multiple super-center devices belonging to different networks). This allows for faster initiation of business processing when needed. Furthermore, based on the first terminal device's ability to sense the device status of connected terminal devices, the system can promptly notify the user of the collaboration results even when connected terminal devices are occupied by other networks, thus ensuring a smooth user experience.

[0050] In one possible design, the identifier of the fourth terminal device included in the fifth interface is displayed with a preset effect; and / or, the identifier of the fifth terminal device included in the fifth interface is displayed with a preset effect; wherein, the preset effect is used to indicate that the terminal device is in a non-cooperative state. For example, it can be displayed using a preset display method (gray background, blurring effect, etc.); or the preset effect is used to indicate that the first network structure does not include the identifier of the second terminal device or the third terminal device.

[0051] In this design, the control interface of the first terminal device can present the structural relationship of the terminal devices in the network to the user through different display effects, ensuring the user's collaborative operation experience.

[0052] In one possible design, when the first terminal device determines that the fourth terminal device and the fifth terminal device cannot cooperate, it is specifically configured to: in response to the first operation, send a first indication message to the fourth terminal device, the first indication message being used to instruct the fourth terminal device and the fifth terminal device to cooperate; receive information from the fourth terminal device indicating that the fourth terminal device and the fifth terminal device have failed to cooperate, and determine that the fourth terminal device and the fifth terminal device have failed to cooperate based on the information indicating that the cooperation has failed.

[0053] In this design, the first terminal device can directly sense the device status of connected terminal devices, and can also indirectly sense the device status of connected terminal devices through the connected terminal devices. Therefore, the indication information returned by the connected terminal devices to indicate the collaboration results can also promptly prompt the user about the collaboration results even when the connected terminal devices are occupied by other network segments, thus ensuring the user experience.

[0054] In one possible design, the first terminal device is a mobile phone, tablet, or laptop; the second terminal device is a device with display capabilities, such as a smart TV; and the third terminal device is a device with audio playback capabilities, such as a speaker or headphones. This design allows for collaborative task processing across multiple terminal devices, thereby achieving a better user experience based on the different types of terminal devices.

[0055] In one possible design, the first instruction message is also used to indicate the collaboration mode between the second terminal device and the third terminal device; wherein the collaboration mode includes, but is not limited to, any one of the following: screen mirroring, application mirroring, audio projection, and task relay.

[0056] In this design, the system provided in this application can not only achieve collaborative control between other terminal devices through the first terminal device, but also control the collaborative mode between other terminal devices based on at least one of the following information: user operation, device type, device status, etc. This also meets the user's needs for collaborative modes in collaborative scenarios.

[0057] In addition, before displaying the first interface, the first terminal device is also used to determine the super center device in the first network structure through any of the following methods, so as to determine the first network structure mentioned above:

[0058] Method 1: Negotiate with at least one terminal device obtained through device scanning of the first terminal device, and determine the first terminal device as the super central device based on the negotiation result. For example, if the first terminal device scans for a second terminal device, the first and second terminal devices can negotiate to determine that the first terminal device will be the super central device. The terminal device can determine the super central device based on a preset negotiation rule.

[0059] Method 2: Receive the super center device indication information from the seventh terminal device, and determine the first terminal device as the super center device based on the super center device indication information; wherein, the seventh terminal device is a terminal device among at least one terminal device obtained by the first terminal device through device scanning.

[0060] Method 3: Display the super center device selection interface; receive and respond to the selection operation on the super center device selection interface, and determine the first terminal device as the super center device, wherein the selection operation is used to instruct the user to select the first terminal device as the super center device.

[0061] Through the methods described above, the system provided in this application allows for the determination of super center equipment based on actual needs, thereby obtaining a network structure that better suits the required scenarios and meets more collaborative needs.

[0062] Secondly, this application also provides a multi-device networking system. This system may include at least a first terminal device, a second terminal device, and a third terminal device. Similar to the system provided in the first aspect, the first terminal device can display a first interface and detect a first operation on the first interface. The difference from the system provided in the first aspect is that the first terminal device is further configured to display a seventh interface when it is determined that the second terminal device and the third terminal device cannot coordinate. This seventh interface indicates that the coordination between the second terminal device and the third terminal device has failed. It can be understood that, in conjunction with the content described in the first aspect, when performing collaborative control, the first terminal device can obtain the coordination result based on the device status of the connected terminal devices, thereby achieving a more accurate coordination scenario.

[0063] In one possible design, the first terminal device is used to determine when the second terminal device and the third terminal device cannot cooperate, specifically by: determining that the second terminal device and the third terminal device cannot cooperate based on one or more of the following information: the device type of the second terminal device, the device status of the second terminal device, the device type of the third terminal device, or the device status of the third terminal device.

[0064] Based on the above design, the first terminal device is specifically used to: determine that the second terminal device and the third terminal cannot cooperate when the second terminal device is already in a cooperative state based on the device status of the second terminal device; or, determine that the second terminal device and the third terminal cannot cooperate when the third terminal device is already in a cooperative state based on the device status of the third terminal device.

[0065] In one possible design, the identifier of the second terminal device included in the first interface is displayed with a preset effect; and / or, the identifier of the third terminal device included in the first interface is displayed with a preset effect; wherein the preset effect is used to indicate that the terminal device is in a non-cooperative state. In this design, the structural relationship of the terminal devices in the network can be presented to the user through different display effects in the control interface of the first terminal device, ensuring the user's experience in collaborative operation.

[0066] It is understood that the display method of the first interface of the first terminal device, the collaborative control method based on the control interface of the first terminal device, the acquisition method of the first network structure to which the first terminal device is located, and the updating of the distributed database, etc., can be referred to the introduction in the first aspect, and will not be repeated here.

[0067] Thirdly, this application also provides a multi-device networking method. This method is applied to a first terminal device and includes: displaying a first interface; wherein the first interface includes multiple terminal device identifiers, the multiple terminal device identifiers including an identifier of a second terminal device and an identifier of a third terminal device; wherein the second terminal device and the third terminal device are connected; detecting and responding to a first operation on the first interface, sending a first instruction message to the second terminal device, the first instruction message being used to instruct the third terminal device to cooperate with the second terminal device.

[0068] In one possible design, the method further includes: displaying a second interface when it is determined that the second terminal device and the third terminal device have collaborated, the second interface being used to indicate that the second terminal device and the third terminal device have collaborated.

[0069] In one possible design, the first interface includes a first network structure composed of the plurality of terminal device identifiers, the plurality of terminal device identifiers including the identifier of the second terminal device and the identifier of the terminal device connected to the second terminal device; wherein, the terminal device connected to the second terminal device includes the third terminal device.

[0070] In one possible design, the plurality of terminal device identifiers may also include the identifier of the first terminal device and the identifier of the terminal device connected to the first terminal device; wherein the terminal device connected to the first terminal device includes the second terminal device.

[0071] In one possible design, before displaying the first interface, the first terminal device is further configured to display a third interface, the third interface including an identifier of the first terminal device and an identifier of a terminal device connected to the first terminal device; wherein, the terminal device connected to the first terminal device includes the second terminal device;

[0072] When the first terminal device displays the first interface, it is specifically configured to: display the first interface when an operation acting on the identifier of the second terminal device is detected.

[0073] In one possible design, the first terminal device is further configured to: detect a second operation, the second operation being configured to instruct a first cooperating device combination to further cooperate with the first terminal device, the first cooperating device combination being configured to indicate the second terminal device and the third terminal device that have already cooperated; and in response to the second operation, display a fourth interface, the fourth interface being configured to indicate that the first terminal device has further cooperated with the first cooperating device combination.

[0074] In one possible design, the first terminal device is further configured to: if a first instruction for instructing the processing of a first task is detected, in response to the first instruction, execute a first sub-task of the first task in combination with the first coordinating device.

[0075] In one possible design, before displaying the first interface, the first terminal device is further configured to: obtain the identifier of a terminal device connected to the second terminal device via the second terminal device, wherein the terminal device connected to the second terminal device includes the third terminal device.

[0076] In one possible design, the first terminal device is further configured to: before displaying the first interface, update a distributed database on the first terminal device based on the identifier of the scanned terminal device and the identifier of the terminal device connected to the second terminal device obtained through the second terminal device, wherein the distributed database is used to indicate the structural relationship between multiple terminal devices; when the first terminal device displays the first interface, it is specifically configured to: display the first interface based on the structural relationship.

[0077] In one possible design, before updating the distributed database on the first terminal device, the first terminal device is further configured to: perform a device scan, wherein the scanned devices include the second terminal device, and send a synchronization request message to the second terminal device. The first terminal device is further configured to: receive a first database synchronization message sent by the second terminal device according to the synchronization request message. When updating the distributed database on the first terminal device, the first terminal device is specifically configured to: update the distributed database on the first terminal device with the identifier of the terminal device connected to the second terminal device, and the connection relationship between the identifier of the terminal device connected to the second terminal device and the second terminal device, as found in the first database synchronization message.

[0078] In one possible design, when the first terminal device is used to display the first interface, it is specifically used to: display the first interface based on a distributed database on the first terminal device, wherein the distributed database is used to indicate the structural relationship between multiple terminal devices; when the first terminal device is used to display the second interface, it is specifically used to: receive a second database synchronization message sent by the second terminal device, wherein the second database synchronization message is used to indicate that the second terminal device and the third terminal device have collaborated; update the distributed database based on the second database synchronization message, and display the second interface based on the updated distributed database.

[0079] In one possible design, the method further includes: receiving information from the second terminal device indicating that the second terminal device and the third terminal device have failed to coordinate; determining that the second terminal device and the third terminal device have failed to coordinate based on the information indicating that the coordination has failed; and displaying a seventh interface when it is determined that the second terminal device and the third terminal device have failed to coordinate, the seventh interface being used to indicate that the coordination between the second terminal device and the third terminal device has failed.

[0080] In one possible design, the method further includes: displaying a fifth interface, the fifth interface including multiple terminal device identifiers, the multiple terminal device identifiers including a fourth terminal device identifier and a fifth terminal device identifier; wherein the fourth terminal device and the fifth terminal device are connected; detecting a third operation on the fifth interface, the third operation being used to instruct the fourth terminal device and the fifth terminal device to cooperate; and when it is determined that the fourth terminal device and the fifth terminal device cannot cooperate, displaying a sixth interface, the sixth interface being used to indicate that the cooperation between the fourth terminal device and the fifth terminal device has failed.

[0081] In one possible design, the first terminal device is used to determine that the fourth terminal device and the fifth terminal device cannot cooperate when the first terminal device is used to: determine that the fourth terminal device and the fifth terminal device cannot cooperate based on one or more of the following information: the device type of the fourth terminal device, the device status of the fourth terminal device, the device type of the fifth terminal device, or the device status of the fifth terminal device.

[0082] In one possible design, the first terminal device is specifically configured to: determine that the fourth terminal device and the fifth terminal device cannot cooperate when the fourth terminal device is already in a cooperative state based on the device state of the fourth terminal device; or, determine that the fourth terminal device and the fifth terminal device cannot cooperate when the fifth terminal device is already in a cooperative state based on the device state of the fifth terminal device.

[0083] In one possible design, the identifier of the fourth terminal device included in the fifth interface is displayed as a preset effect; and / or, the identifier of the fifth terminal device included in the fifth interface is displayed as a preset effect; wherein the preset effect is used to indicate that the terminal device is in an uncooperative state.

[0084] In one possible design, when the first terminal device determines that the fourth terminal device and the fifth terminal device cannot cooperate, it is specifically configured to: in response to the first operation, send a first indication message to the fourth terminal device, the first indication message being used to instruct the fourth terminal device and the fifth terminal device to cooperate; receive information from the fourth terminal device indicating that the fourth terminal device and the fifth terminal device have failed to cooperate, and determine that the fourth terminal device and the fifth terminal device have failed to cooperate based on the information indicating that the cooperation has failed.

[0085] In one possible design, the first terminal device is a mobile phone, tablet computer, or laptop computer; the second terminal device is a terminal device with display function, such as a smart TV; and the third terminal device is a terminal device with audio playback function, such as a speaker or headphones.

[0086] Fourthly, this application also provides a multi-device networking method. This method is applied to a second terminal device and includes: receiving a first indication message sent by a first terminal device, the first indication message being used to instruct the third terminal device to cooperate with the second terminal device; and cooperating with the third terminal device according to the first indication message.

[0087] In one possible design, the second terminal device is further configured to: receive task data of the first sub-task, and execute the first sub-task collaboratively by the second terminal device and the third terminal device.

[0088] In one possible design, the second terminal device is further configured to: if a first event for processing a second task is detected, in response to the first event, execute a second sub-task of the second task through the third terminal. Specifically, when the second terminal device detects the first event for processing the second task, it is configured to: detect a first user operation on a first display interface of the second terminal device, the first user operation being used to generate the second task; or, receive task information from the first terminal device, the task information being used to indicate task data for the second task.

[0089] For example, the second terminal device is a device with display function, and the third terminal device is a device with audio playback function; the second task is a playback task; and the second subtask is the audio playback task of the playback task. In this example, the second terminal device is further configured to, in response to the first event, display the display data of the playback task and send the audio data of the playback task to the third terminal device, so that the third terminal device can execute the audio playback task of the audio data.

[0090] In one possible design, the second terminal device is further configured to: after receiving the synchronization request message, send a first database synchronization message to the first terminal device, the first database synchronization message including the identifier of the terminal device in the distributed database on the second terminal device, wherein the distributed database on the second terminal device includes the identifier of the terminal device connected to the second terminal device;

[0091] Fifthly, this application also provides a multi-device networking method. This method is applied to a first terminal device and includes: displaying a first interface, the first interface including multiple terminal device identifiers, the multiple terminal device identifiers including the identifier of the second terminal device and the identifier of the third terminal device; wherein the second terminal device and the third terminal device are connected; detecting a first operation on the first interface, the first operation being used to instruct the second terminal device and the third terminal device to cooperate; when it is determined that the second terminal device and the third terminal device cannot cooperate, displaying a seventh interface, the seventh interface being used to indicate that the cooperation between the second terminal device and the third terminal device has failed.

[0092] In one possible design, determining that the second terminal device and the third terminal device cannot work together includes: determining that the second terminal device and the third terminal device cannot work together based on one or more of the following information: the device type of the second terminal device, the device status of the second terminal device, the device type of the third terminal device, or the device status of the third terminal device.

[0093] In one possible design, the first terminal device is specifically configured to: determine that the second terminal device and the third terminal cannot cooperate when the second terminal device is already in a cooperative state based on the device state of the second terminal device; or, determine that the second terminal device and the third terminal cannot cooperate when the third terminal device is already in a cooperative state based on the device state of the third terminal device.

[0094] In one possible design, the identifier of the second terminal device included in the first interface is displayed as a preset effect; and / or, the identifier of the third terminal device included in the first interface is displayed as a preset effect; wherein the preset effect is used to indicate that the terminal device is in an uncooperative state.

[0095] It is understood that the display method of the first interface of the first terminal device, the collaborative control method based on the control interface of the first terminal device, the acquisition method of the first network structure to which the first terminal device is located, and the updating of the distributed database, etc., can be referred to the methods introduced in the third aspect, and will not be repeated here.

[0096] Sixthly, this application also provides a terminal device, including: one or more processors; one or more memories; the one or more memories for storing one or more computer programs and data information; wherein the one or more computer programs include instructions; when the instructions are executed by the one or more processors, the terminal device performs a method executable by a first terminal device in any possible design of the fourth aspect above, or performs a method executable by a second terminal device in any possible design of the fifth aspect above, or a method executable by a first terminal device in any possible design of the sixth aspect above.

[0097] Seventhly, this application also provides a terminal device, including a module / unit for executing the method of any of the possible designs in the third aspect, the fourth aspect, or the fifth aspect. These modules / units can be implemented in hardware or by hardware executing corresponding software.

[0098] Eighthly, this application also provides a multi-device networking system, including multiple terminal devices as described in the sixth aspect above, or multiple terminal devices as described in the seventh aspect above, for example, including a first terminal device, a second terminal device, and a third terminal device. The multiple terminal devices as described in the sixth aspect above, or multiple terminal devices as described in the seventh aspect above, jointly execute the method described in any possible design of the third aspect above; or, the multiple terminal devices as described in the sixth aspect above, or multiple terminal devices as described in the seventh aspect above, jointly execute the method described in any possible design of the fourth aspect above; or, the multiple terminal devices as described in the sixth aspect above, or multiple terminal devices as described in the seventh aspect above, jointly execute the method described in any possible design of the fifth aspect above.

[0099] Ninthly, this application provides a computer-readable storage medium storing a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the method in any of the possible implementations of the third aspect above, or to perform the method in any of the possible implementations of the fourth aspect above, or to perform the method in any of the possible implementations of the fifth aspect above.

[0100] In a tenth aspect, this application provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when executed, causes a computer to perform a method in any of the possible implementations of the third aspect, or in any of the possible implementations of the fourth aspect, or in any of the possible implementations of the fifth aspect.

[0101] Eleventhly, this application also provides a graphical user interface on a terminal device, the terminal device having a display screen, one or more memories, and one or more processors, the one or more processors being used to execute one or more computer programs stored in the one or more memories, the graphical user interface including the graphical user interface displayed when the terminal device executes any possible implementation of the third aspect, or any possible implementation of the fourth aspect, or any possible implementation of the fifth aspect of this application.

[0102] For details on the beneficial effects of any of the third to eleventh aspects mentioned above, please refer to the beneficial effects of the various possible designs in the first or second aspects mentioned above; they will not be repeated here. Attached Figure Description

[0103] Figure 1a This is a schematic diagram of a radar image for a multi-device network.

[0104] Figure 1b This is a schematic diagram of a multi-device network topology.

[0105] Figure 1c This is a schematic diagram of a multi-device networking scenario;

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

[0107] Figure 3 A software structure block diagram of a terminal device provided in an embodiment of this application;

[0108] Figure 4a This is one of the radar diagrams illustrating a multi-device network provided in an embodiment of this application;

[0109] Figure 4b A second radar diagram illustrating a multi-device network, provided as an embodiment of this application;

[0110] Figure 5 This is the third radar diagram illustrating a multi-device network, provided as an embodiment of this application.

[0111] Figure 6 Fourth of a radar diagram illustrating a multi-device network provided in this application embodiment;

[0112] Figure 7 An interactive flowchart illustrating a multi-device networking method provided in an embodiment of this application;

[0113] Figure 8 This is a schematic diagram of a multi-device network topology provided in an embodiment of this application. Detailed Implementation

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

[0115] The embodiments of this application can be applied to the field of terminal technology, and specifically to application scenarios involving multiple terminal devices. In one possible scenario, Figure 1a This is a schematic diagram of a radar image for a multi-device network. Figure 1a In the scenario shown, using a mobile phone as the central device as an example, the mobile phone can form a distributed network with many terminal devices (such as forming a "super terminal"), such as... Figure 1a Personal computers (PCs), headsets 1 and 2, tablets, speakers, and other terminal devices can be used as peripherals for mobile phones; among them, Figure 1aThe mobile phone, PC, and headset 1 are already working together. The central device refers to the terminal device that the user actively initiates to connect to peripheral devices; it can be understood that the connected devices are peripheral devices, and the central device can act as... Figure 1a The control center of the distributed network shown.

[0116] As the number and types of terminal devices increase, the distributed networking of these devices becomes increasingly complex. Central devices typically switch between different scenarios (e.g., a central device can be a mobile phone, tablet, PC, smart TV (e.g., smart screen), cockpit, or watch), and different central devices can detect different peripheral devices. Figure 1b As shown, where Figure 1b 11 in the diagram shows a distributed network 1 consisting of a central device, mobile phone A, and peripheral devices, such as speakers and headphones; Figure 1b The diagram at 12 shows a distributed network 2 consisting of a central device, a smart screen (also known as a "large screen"), and peripheral devices such as headphones, speakers, and watches.

[0117] In one possible scenario, the networking characteristics of each distributed network are based on a central device and its directly connected devices; in other words, the central device can only detect surrounding devices but cannot perceive their network connection status. This scenario can easily lead to business conflicts. For example... Figure 1c As shown, suppose phone A is projecting its screen onto a large screen. If phone B is also present, it cannot perceive the network connection status of the large screen. If phone B directly projects its screen onto the large screen, phone A's service transmission will be interrupted, and phone A will not receive any notifications, thus affecting the user experience. Furthermore, in some distributed networks, there may be drawbacks such as inconvenient touch control of the central device, for example... Figure 1b In the distributed network 2 shown in Figure 12, the smart screen, as the central device, usually cannot be touched and needs to be controlled by a remote control device. In this scenario, the networking process of distributed network 2 is relatively complicated and it is not convenient for interaction after networking.

[0118] In view of this, embodiments of this application provide a multi-device networking method. In this method, a multi-level network structure can be constructed based on a distributed database. In this network structure, terminal devices in the distributed network can perceive not only the basic information of the terminal devices they are connected to, but also the terminal devices further connected to those connected terminal devices, thus forming a larger, multi-level distributed network. Furthermore, in this network, collaborative control between other terminal devices can be achieved on the first terminal device, thereby providing users with more multi-device collaborative scenarios and further improving the user experience.

[0119] The embodiments of this application can be applied to terminal devices such as mobile phones, PCs, tablets, wearable devices (e.g., watches, bracelets, etc.), in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), and smart home devices (e.g., smart TVs, smart speakers, etc.). It is understood that the embodiments of this application do not impose any limitations on the specific type of terminal device.

[0120] The terminal devices to which this application's embodiments can be applied include, but are not limited to, those equipped with... Alternatively, it could be a terminal device running another operating system. The aforementioned portable electronic devices can also be other portable electronic devices, such as laptops with touch-sensitive surfaces (e.g., touch panels).

[0121] Figure 2 A schematic diagram of a possible hardware structure for a terminal device is shown. The terminal device 200 includes components such as a radio frequency (RF) circuit 210, a power supply 220, a processor 230, a memory 240, an input unit 250, a display unit 260, an audio circuit 270, a communication interface 280, and a wireless-fidelity (Wi-Fi) module 290. Those skilled in the art will understand that... Figure 2 The hardware structure of the terminal device 200 shown in the figure does not constitute a limitation on the terminal device 200. The terminal device 200 provided in the embodiments of this application may include more or fewer components than shown, may combine two or more components, or may have different component configurations. Figure 2 The various components shown 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.

[0122] The following is combined Figure 2 The various components of the terminal device 200 are described in detail below:

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

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

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

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

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

[0128] For example, when the terminal device 200 is a mobile phone, the terminal device 200 may include the RF circuit 210, and may also include the Wi-Fi module 290, or may include a Bluetooth module. Figure 2 (Not shown in the image); when the terminal device 200 is a computer, the terminal device 200 may include the communication interface 280, and may also include the Wi-Fi module 290, or may include a Bluetooth module (not shown in the image); Figure 2 (Not shown in the image); when the terminal device 200 is a tablet computer, the terminal device 200 may include the Wi-Fi module, or may include a Bluetooth module (not shown in the image); Figure 2 (Not shown in the image).

[0129] The memory 240 can be used to store software programs and modules. The processor 230 executes various functional applications and data processing of the terminal device 200 by running the software programs and modules stored in the memory 240. Optionally, the memory 240 may mainly include a program storage area and a data storage area. The program storage area may store the operating system (mainly including the software programs or modules corresponding to the kernel layer, system layer, application framework layer, and application layer).

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

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

[0132] The touch panel 251, also known as a touch screen, can collect user touch operations on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 251), and drive the corresponding connection device according to a pre-set program. In this embodiment, the display unit 260 can display a relevant editing interface corresponding to the multi-device network (such as a control interface displayed on the first terminal device, which may include a radar chart to illustrate the multi-device network structure). The touch panel 251 can collect user operations based on the relevant editing interface, such as drag-and-drop operations. The user can trigger changes in the network structure relationship between multiple devices through drag-and-drop operations, such as enabling or disabling collaboration between terminal devices.

[0133] Optionally, the other input device 252 may include, but is not limited to, one or more of the following: a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, a joystick, etc. For example, if the central device in the distributed network is a smart screen, the other input device 252 may be, for example, a smart remote control device.

[0134] The display unit 260 can be used to display information input by the user or information provided to the user, as well as various menus of the terminal device 200. The display unit 260 is the display system of the terminal device 200, used to present the interface and realize human-computer interaction. The display unit 260 may include a display panel 261. Optionally, the display panel 261 may be configured as a liquid crystal display (LCD), organic light-emitting diode (OLED), or similar form. In this embodiment, the display unit 260 can be used to display a multi-device networking related editing interface for the user, such as the interface including... Figure 1a The radar diagram of the "HyperTerminal" is shown.

[0135] The processor 230 is the control center of the terminal device 200. It connects various components via various interfaces and lines, and executes software programs and / or modules stored in the memory 240, as well as calling data stored in the memory 240, to perform various functions and process data of the terminal device 200, thereby realizing multiple services based on the terminal device 200. In this embodiment, the processor 230 can be used to implement the multi-device networking method provided in this embodiment.

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

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

[0138] Although not shown, the terminal device 200 may also include a camera, at least one sensor, etc., which will not be described in detail here. The at least one sensor may include, but is not limited to, a pressure sensor, a barometric pressure sensor, an accelerometer, a distance sensor, a fingerprint sensor, a touch sensor, a temperature sensor, etc.

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

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

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

[0142] In this embodiment, the application layer can be used to implement the presentation of the editing interface (such as a UI), provide UI interaction, present device status, and execute commands. The UI can provide a display interface for the user, which can be used to implement user operations in the multi-device networking scenario that is the focus of this embodiment. For example, it can be the display interface of the "Super Terminal" involved in this embodiment, and may include radar charts, cards, and feature ability (FA) lists; wherein the FA list is used to indicate features such as device lists, so as to facilitate application in scenarios such as cross-device lists. "Super Terminal" can also be understood as an application that can be displayed in pages such as the notification bar.

[0143] For example, in the embodiments of this application, the application layer can realize the presentation of device management capabilities; wherein, device management capabilities may include, for example, the presentation of information such as device discovery (such as displaying the peripheral devices discovered by the terminal device in a radar chart), device binding, device collaboration (such as displaying the device collaboration effect with other terminal devices in response to the user's drag operation), status management, device negotiation (such as displaying a prompt pop-up window when the connection fails).

[0144] In another example, the application layer in this application embodiment can implement distributed data management functions, such as supporting screen mirroring between devices, distributed cameras, and distributed device connection status information.

[0145] As another example, in this embodiment of the application, the application layer can also implement external interaction functions, such as task management, external service access, and device data provision.

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

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

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

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

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

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

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

[0153] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating the device, and flashing indicator lights.

[0154] In this embodiment, the application framework layer can also provide a data discovery framework and a collaboration framework. The data discovery framework provides data discovery functionality in multi-device networking scenarios and may include: a decision system (DS) for context awareness and trusted device reporting; a device manager (DM) for device online / offline notifications; and a device profile (DP) for storing basic device information. The collaboration framework provides collaboration capabilities between devices, and collaboration methods may include, but are not limited to, the following: distributed multi-mode sensing data platform (DMSDP), OneHop, and distributed camera controllers.

[0155] Another example, although Figure 3 As not shown in the diagram, in this embodiment of the application, the application layer sequence framework layer can also be used to implement the All-Connect cloud network; wherein, the All-Connect cloud network is responsible for device status subscription, device status reporting, device connection disconnection, and device service registration, etc.

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

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

[0158] The system library (also known as the "system service layer") can include multiple functional modules. For example: surface manager, media framework, 3D graphics processing library (e.g., OpenGL ES), 2D graphics engine (e.g., SGL), etc.

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

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

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

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

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

[0164] In this embodiment, the system layer can be used to shield the differences between protocols and communications, providing unified system device discovery, connection, authentication, networking, transmission, cross-device command scheduling, and data synchronization capabilities. For example, the system layer may also include a soft bus; wherein the soft bus is responsible for discovery, connection, authentication, networking, and data transmission, so as to support the device discovery and data channel capabilities of terminal devices.

[0165] although Figure 3 As not shown in the diagram, in this embodiment, the system layer may further include: a distributed data management service, a tag service, a distributed execution framework (or "distributed scheduling") (DEF), HiChain, etc. The distributed data management service is responsible for system-level data synchronization capabilities to achieve highly reliable, low-latency distributed data interaction.

[0166] The kernel layer is the layer between hardware and software. The kernel layer includes at least display drivers, camera drivers, audio drivers, and sensor drivers. In this embodiment, the kernel layer can also be understood as a protocol adaptation layer, which can be used to adapt to different protocols to facilitate access to different terminal devices, such as WLAN protocol, Bluetooth protocol, Bluetooth Low Energy (BLE) protocol, and Ethernet protocol.

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

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

[0169] It should be understood that in the embodiments of this application, "at least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or multiple. "Multiple" refers to two or more. "And / or" 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, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0170] In addition, it should be understood that in the description of this application, the words "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance or order.

[0171] It should be understood that the hardware structure of a terminal device can be as follows: Figure 2 As shown, the software system architecture can be as follows: Figure 3 As shown, the software programs and / or modules corresponding to the software system architecture in the terminal device can be stored in the memory 240, and the processor 230 can run the software programs and applications stored in the memory 240 to execute the process of a multi-device networking method provided in the embodiments of this application.

[0172] To facilitate understanding of the multi-device networking method provided in this application, the following is combined with... Figures 4a to 8 The content shown describes the implementation process of the method provided in this application.

[0173] This application's embodiments are applicable to scenarios involving distributed networking of multiple terminal devices (also known as "multi-device networking"). Multi-device networking implemented through the method provided in this application's embodiments can achieve hierarchical networking of multiple terminal devices, facilitating the construction of more terminal devices within the same network and expanding the scenarios for collaboration between terminal devices. Furthermore, it can also realize more layers of business processes based on the constructed network. Additionally, terminal devices with touch functionality within the network can be preferentially designated as super-central devices, thereby enabling more convenient construction of multi-device networks on the super-central device. The super-central device can obtain the identifiers of peripheral devices of other central devices acting as its peripheral devices. For example, as described below, mobile phone A can serve as the super-central device in the first network structure, and mobile phone B can serve as the super-central device in the second network structure. In a distributed network, taking a first terminal device, a second terminal device, and a third terminal device as an example, the multi-level network structure provided in this application is described. For the first terminal device, it is the central device, and the devices connected to it are its peripheral devices. For the second terminal device, it is the central device, and the devices connected to it are its peripheral devices. If the second terminal device is a peripheral device of the first terminal device, the first terminal device can also obtain the identifier of the device connected to it and consider the connected device as a peripheral device of the first terminal device as well. This allows the first terminal device to control the collaboration between two interconnected peripheral devices.

[0174] Among them, "connected between terminal devices" can mean that a communication link has been established between terminal devices through wireless or wired means. For example, a Bluetooth link can be established through Bluetooth, a Wi-Fi communication link can be established through Wi-Fi, or a connection can be established through a wired link.

[0175] The methods provided in the embodiments of this application will be described below with reference to several examples. It should be understood that the embodiments of this application are not limited to the following examples or application scenarios.

[0176] Step 1: Trigger the multi-device networking process. Taking mobile phone A as an example, this application can be implemented as follows: Figure 4aInterface 41 shows a notification bar page with a "Super Terminal" service card configured as a shortcut to trigger multi-device networking functionality. "Super Terminal" can be used to enable multi-device networking and collaborative processing capabilities between terminal devices. It is understood that the specific implementation is not limited to defining multi-device networking capabilities as "Super Terminal," but can be defined by other possible names. Furthermore, besides configuring the "Super Terminal" shortcut in the notification bar page of phone A, it can also be accessed through the "Settings" app on phone A, the application icon on the main interface, other pages (such as the negative one screen), or by voice command activation.

[0177] In interface 41, users can access functions such as control 401. Figure 4a The "Super Terminal" display interface shown in interface 42 is shown in the image. Interface 42 can display a more detailed and comprehensive "Super Terminal" radar display interface (or simply "radar chart"), which includes the identifiers (e.g., icons and / or names) of multiple terminal devices included in the "Super Terminal" network. Alternatively, in interface 41, users can directly perform device scanning or device networking through control 402. Furthermore, since interface 41 is a notification bar page, it can also include other quick switches, such as "WLAN," "Bluetooth," "Mobile Data," "Silent / Vibrate / Ring," "Auto Rotate," etc.; it can also include a progress bar for adjusting the display brightness of phone A; it can also include date information, "Quick Switch" editing controls, "Settings" controls; and the top area can include a status bar (which can include mobile network, wireless network, time information, and remaining battery power). It is understood that although not shown in interface 41, the notification bar interface can also include other quick switches, service cards, notification information bars, etc.; the status bar can also include the operator's name, Bluetooth icon, etc.

[0178] It should be noted that the methods for triggering the multi-device networking process can differ across different types of terminal devices. For example, on mobile phone A, the multi-device networking process can be initiated through the notification bar page, or on a PC, it can be initiated through the "PC Manager" app, etc. This application does not limit this. It is understood that... Figure 4a The scenario shown is merely one possible example; in the implementation of this application, it is not limited to... Figure 4a The radar chart shown in the image illustrates the distributed network structure, but it can also be represented by other forms such as lists and topology diagrams.

[0179] Step 2: Device Scanning and Device Discovery. Taking mobile phone A as the central device of the "Super Terminal" as an example, through device scanning and device discovery, the identifiers of multiple discovered terminal devices can be displayed on the radar chart of the "Super Terminal," as shown in interface 42. It should be noted that this application does not limit the display method of the terminal device identifiers; it can be one or a combination of icons indicating the type of terminal device, the name of the terminal device, etc. It should be noted that, compared to... Figure 1a The radar chart shown in interface 42 shows that the identifiers of multiple terminal devices discovered by mobile phone A can form a distributed network structure and can exhibit hierarchical characteristics.

[0180] For example, mobile phone A, as the central device, can form a distributed network with multiple peripheral devices; among them, the peripheral devices of mobile phone A have multi-level characteristics. Mobile phone A can scan and discover multiple terminal devices directly connected to it, which can serve as first-level peripheral devices. For example, the earphones 1, speaker 1, earphones 2, smart screen, and watch included in interface 42 are first-level peripheral devices of mobile phone A. Furthermore, the first-level peripheral devices of mobile phone A can also be peripheral devices of mobile phone A's peripheral devices (which can also be referred to as "second-level peripheral devices" in this embodiment) through device scanning and device discovery. For example, earphones 3 and speaker 2 in interface 42 are first-level peripheral devices of the smart screen and second-level peripheral devices of mobile phone A, and the treadmill and jump rope in interface 42 are first-level peripheral devices of the watch and second-level peripheral devices of mobile phone A. Although not shown in interface 42, in practice, the second-level peripheral devices of mobile phone A can continue to scan and discover the third-level peripheral devices, and so on. Thus, a network structure with at least two levels can be displayed on mobile phone A. It can be understood that, apart from the first-level peripheral devices, other levels of peripheral devices represent terminal devices indirectly connected to the central device through at least one terminal device. For example, a second-level peripheral device is a terminal device indirectly connected to the central device through one terminal device, and a third-level peripheral device is a terminal device indirectly connected to the central device through two terminal devices.

[0181] In another example, when mobile phone A scans and discovers multiple terminal devices as its first-level peripheral devices, if the discovered terminal devices have already established a distributed network as the central device (e.g., the smart screen in interface 42, which had already established a distributed network with earphone 3 and speaker 2 before being discovered by mobile phone A), then when mobile phone A scans and discovers the smart screen, it can use the smart screen as its first-level peripheral device, and the original peripheral devices of the smart screen can further serve as the second-level peripheral devices of mobile phone A. It can be understood that in this example, during the creation of the "super terminal," mobile phone A can integrate with the existing distributed network to form a larger distributed network, enabling collaboration in more scenarios. For example, when performing network control on the smart screen, the smart screen can still control the distributed network with the smart screen as the central device and earphone 3 and speaker 2 as peripheral devices.

[0182] Among them, mobile phone A can scan and discover devices through Bluetooth, Wi-Fi or wired means, and establish a communication link with the discovered device after successfully discovering the device; wherein, the communication link can be a Bluetooth link, Wi-Fi link or wired link, etc.

[0183] In addition, in interface 42, the terminal device can also receive user operations on control 403 to manually add the required terminal devices.

[0184] For example, a user can manually add other unscanned terminal devices to mobile phone A using control 403. For instance, assuming mobile phone A's device scanning rule is for terminal devices logged into the same user account, control 403 can be used to manually add mobile phone B, which is logged into another user account and cannot be scanned. This can be achieved by adding information such as mobile phone B's Media Access Control (MAC) address or Internet Protocol (IP) address. Optionally, based on the embodiments of this application, a multi-level network structure can be provided. In the scenario where a user manually adds mobile phone B to the network structure of mobile phone A, the manually added mobile phone B can be defaulted to being a first-level peripheral device of mobile phone A. Alternatively, when adding information such as mobile phone B's MAC address or IP address, the structural relationship of mobile phone B in the network structure of mobile phone A can be added simultaneously. For example, mobile phone B can be used as a peripheral device of a smart screen (i.e., a second-level peripheral device of mobile phone A). Additionally, assuming a user actively adds phone B on phone A via control 403, to ensure device security, verification information can be sent to phone B; for example, the trust between phone A and phone B can be verified by displaying a pop-up window on phone B or by entering a personal identification number (PIN).

[0185] In another example, the user can also update the device scanning rules for mobile phone A based on control 403, such as manually adding account information of other user accounts (e.g., family members' user accounts) or wireless network information (e.g., other WLAN networks used in a home setting), so that mobile phone A can obtain more terminal devices through device scanning, thereby realizing multi-user, multi-device networking in a home setting. Optionally, to ensure device security, after the terminal device performs device scanning and discovery based on the updated device scanning rules, it can also send verification information to the discovered terminal devices. Only after successful verification can multi-device networking be completed.

[0186] It is understandable that after receiving and responding to the user's manual addition operation, mobile phone A can also store relevant terminal device information or user account information, so that it can perform device scanning and device discovery based on the stored information when forming a multi-device network again. Optionally, for the information manually added by the user, mobile phone A can also be configured with a certain verification period. During the verification period, user authentication is not required. If the verification period is exceeded, secondary authentication by the user is required, such as re-entering the user account password or sending an authentication request to the other party's terminal device or any terminal device logged into by the other party's user account.

[0187] Alternatively, in interface 42, the terminal device can also provide the user with control 404 to enable the user to make relevant settings for the "Super Terminal". For example, the terminal device can detect and respond to user operations on control 404 (such as click operations, voice commands, etc.) and provide the user with a settings interface. The settings interface can include scanning rules for terminal devices that the user can scan. For example, the user can set one or a combination of user account information and wireless network information that the terminal device can scan on the settings interface, so that the terminal device can scan and discover devices logged into the user account information and / or the wireless network information. Optionally, to ensure device security, the user account information and wireless network information can be verified when setting scanning rules (e.g., verifying account passwords, wireless network passwords, etc.). If the verification is successful, device scanning and discovery can continue. Alternatively, to further enhance device security, device verification can be performed after scanning a terminal device before multi-device networking can be completed.

[0188] It should be noted that when users make settings through the interface corresponding to control 403 or the settings interface corresponding to control 404, in addition to manually entering relevant user account information and wireless network information, they can also use automatic scanning or automatic filling to achieve quick settings. For example, on the settings interface corresponding to control 404, when adding wireless network information, the terminal device can scan the surrounding WLANs and provide the user with a list of scan results so that the user can select the wireless network information to be added based on the list of scan results.

[0189] Furthermore, based on the foregoing description, this application embodiment does not limit the form in which the distributed network structure is displayed on mobile phone A. For example, Figure 4b This is another interface diagram illustrating a distributed network structure provided in an embodiment of this application. Figure 4a The interface 42 is different in the middle. Figure 4bInterface 421 can display the terminal devices connected to mobile phone A. Terminal devices further connected to these connected devices can be displayed in a collapsed manner. For example, based on the network structure described in interface 42, the smart screen and watch have further connected terminal devices. Interface 421 may not display these further connected terminal devices, and a label 405 can be displayed on the icons of the smart screen and watch. This label 405 can indicate the number of other terminal devices connected to the user's device, thus reminding the user that the smart screen and watch have other further connected terminal devices. Label 405 may include, but is not limited to, numerical labels and small icons (e.g., the smart screen's label 405 could be small icons for headphones 3 and speakers 2, which are only used as a prompt and cannot be dragged). Furthermore, in specific implementations, the form of prompting for further connected terminal devices is not limited to the form of label 405 in interface 421. It can also be text prompts or icon display effects (e.g., if there are further connected terminal devices, the icon outline can be bolded, or filled with different colors, etc.) to provide the prompt.

[0190] On interface 421, if mobile phone A detects an operation on the smart screen icon (such as double-tap operation, long-press operation, or voice command, etc.), it can switch to display interface 422 or interface 423.

[0191] In interface 422, the smart screen icon can be displayed in the center, while icons of connected terminal devices (such as headphones 3, speaker 2, and phone A) can be displayed around it. Phone A, as the central device at the next higher level (i.e., the super central device in the current network structure), can be distinguished from the peripheral devices (headphones 3 and speaker 2) connected to the smart screen, allowing users to easily return to the previous level of the network structure. It's understandable that interface 422 could omit displaying other terminal devices connected to phone A; for example, identifier 5 could indicate that phone A has four other connected terminal devices. Alternatively, although... Figure 4b As not shown in the diagram, in another display method, in interface 422, the icon of mobile phone A may not be displayed. Instead, only the icon of the smart screen and the identifiers of multiple terminal devices connected to the smart screen are displayed in the center.

[0192] In interface 423, the terminal devices connected to the smart screen can be expanded and displayed based on interface 421, with mobile phone A still displayed in the middle of interface 423. In this scenario, mobile phone A can respond to user operations and expand and display more terminal devices according to user needs.

[0193] In addition, optional, except Figure 4a or Figure 4bIn addition to the central device (phone A) shown in the image, Figure 4a or Figure 4b On other terminal devices included (such as smart screens, earphones 2, speakers 1, watches, etc.), if these other terminal devices have peripheral devices, a multi-device network display interface centered on the device itself can be displayed on those other terminal devices. For example, if the other terminal devices are... Figure 4a or Figure 4b The smart screen shown can display a network radar diagram with the smart screen as the central device and speakers 2 and headphones 3 as peripheral devices of the smart screen. For example, if the other terminal devices are... Figure 4a or Figure 4b The watch shown can display a network radar diagram with the watch as the central device and the treadmill and jump rope as peripheral devices.

[0194] Alternatively, on other terminal devices besides mobile phones, a complete multi-device network radar diagram centered on the mobile phone can also be displayed. Or, in other optional scenarios, in... Figure 4a Other terminal devices included in the network (such as smart screens, earphones 2, speakers 1, watches, etc.) can also switch the central device through the displayed network radar diagram. For example, the smart screen can display a complete multi-device network radar diagram with mobile phone A as the central device (e.g., displayed as interface 421 or interface 42). The smart screen can receive user operations to switch the central device, thereby switching the network structure from mobile phone A as the central device to the smart screen as the central device (e.g., interface 422). It is understood that, in the implementation of this application, the implementation method of displaying the network topology on peripheral devices is not limited.

[0195] It should be noted that, optionally, in the radar diagram shown in interface 42, the terminal device can also receive and respond to user operations on peripheral devices (such as double-click operations, long-press operations, etc.), and execute actions to fold or unfold the peripheral devices. For example, the user can fold and hide speaker 2 and headphones 3 by double-clicking the smart screen in interface 42; and the user can unfold the folded speaker 2 and headphones 3 by double-clicking the smart screen in interface 42 again. The unfolding and folding scenarios of peripheral devices can be distinguished by different display states, which is not limited in this application. It is understood that, depending on the business scenario, the network topology of the central device can also be folded or unfolded. For example, assuming the complete network topology is displayed on the peripheral devices, other peripheral devices of the central device can be folded, retaining only the network topology diagram related to the current peripheral device. This provides users with a radar diagram that better suits their habits, facilitating device interaction in multi-device networking.

[0196] Furthermore, while the above example directly uses mobile phone A as the central device, it should be noted that in this embodiment, the central device can be set according to the actual scenario. Optionally, the central device can be determined through negotiation among multiple terminal devices. Alternatively, the central device can be determined by a control device among multiple terminal devices. Or, the central device can also be determined in response to user operations or selections; the specific implementation will be described in detail in subsequent embodiments and will not be elaborated here.

[0197] Step 3: Device interaction process based on multi-device networking. During the implementation of this application, different terminal devices may be in different device states, thus different processing scenarios may exist, including but not limited to the following:

[0198] In scenario one, based on the devices discovered in interface 42, the terminal device can receive user operations for device collaboration (such as drag-and-drop operations) and for task transfer between devices. For example, interface 42 can display a prompt message "Drag and drop devices to this machine to establish collaboration or initiate task transfer," prompting the user to perform device collaboration or task transfer through user operations on interface 42. The following embodiments mainly use device collaboration scenarios to illustrate the multi-device networking method provided in this application.

[0199] For example, a user can drag speaker 2 to the smart screen in interface 42 to achieve collaboration between speaker 2 and the smart screen, as shown in interface 43. At this time, the icons of the smart screen and speaker 2 are snapped together, indicating that the smart screen and speaker 2 have already collaborated. Then, the user can also drag the smart screen to mobile phone A in interface 43 to achieve collaboration between mobile phone A and the smart screen, as shown in interface 44. At this time, the icons of mobile phone A and the smart screen are snapped together, indicating that mobile phone A and the smart screen have already collaborated. At the same time, the icons of the smart screen and speaker 2 are snapped together, indicating that the smart screen and speaker 2 have already collaborated. It can be understood that, based on the collaboration between the smart screen and speaker 2, the smart screen can further collaborate with mobile phone A. For example, it can realize a scenario where video data on mobile phone A is projected onto the smart screen, and audio data is further distributed and played through speaker 2. Thus, based on the method provided in this application embodiment, collaboration between multiple levels of devices can be conveniently realized, and it has the characteristics of simple operation.

[0200] Or, another example, based on Figure 4bThe current network structure is displayed in a way that allows users to drag speaker 2 from interface 422 to the smart screen to enable collaboration between speaker 2 and the smart screen, as shown in interface 431. At this point, the icons for the smart screen and speaker 2 snap together, indicating that they are now working together. Then, phone A can first detect user actions (such as double-tap, long-press, or voice commands) on its icon in interface 431, and respond to these actions by displaying interface 432. Alternatively, if the control interface does not display phone A's icon, phone A can also detect and respond to user actions, gestures, or voice commands on the control 406 that returns to the previous screen, and display interface 432. At this point, interface 432 switches back to displaying phone A in the center and the connected terminal devices around it. It can be understood that in interface 432, the smart screen and speaker 2 are now working together. Then, in interface 432, the user can continue to drag the smart screen to phone A to achieve collaboration between phone A and the smart screen, as shown in interface 441. At this time, the icons of phone A and the smart screen snap together, indicating that phone A and the smart screen have collaborated. At the same time, the icons of the smart screen and speaker 2 snap together, indicating that the smart screen and speaker 2 have collaborated. It can be understood that in interface 432 or interface 441, indicator 405 can also prompt the user that the smart screen has another connected terminal device.

[0201] In another exemplary embodiment of this application, the collaboration between the smart screen and the speaker 2 can also be achieved in a scenario where the mobile phone and the smart screen are already working together. This application does not limit the order in which multiple terminal devices are sequentially collaborated.

[0202] Among them, the collaboration between terminal devices is used to indicate that multiple terminal devices can jointly process a task, that is, multiple terminal devices have the ability to collaboratively process tasks; task collaboration can be used to indicate that for a task to be processed, multiple terminal devices can collaboratively process it.

[0203] For example, task collaboration scenarios may include, but are not limited to: screen mirroring scenarios, application screen mirroring scenarios, and productivity desktop modes. For instance, screen mirroring scenarios can project the phone's desktop display onto a smart screen for mirrored display; application screen mirroring scenarios can project video data from a video application on the phone onto the smart screen for display; productivity desktop modes can project the phone's desktop onto the smart screen and adaptively match it. Furthermore, the ways in which terminal devices collaborate may include, but are not limited to: collaboration based on the task currently being processed by the terminal device (e.g., one or a combination of foreground and background tasks), such as a phone projecting a playing video onto a smart screen for playback; collaboration based on device type, such as the smart screen projecting audio data onto a speaker for playback if it determines the collaborating device has audio playback capabilities; and collaboration based on user operations, such as a user projecting the phone screen mirror data onto the smart screen for display.

[0204] For example, Figure 4a In the scenario shown on interface 43 where the smart screen and speaker 2 are working together, if the user is playing a video on the smart screen or has started playing a video, the smart screen can project the audio data of the video onto speaker 2 for playback.

[0205] For example, Figure 4a In the scenario shown in interface 44, where mobile phone A and the smart screen are already in sync, and the smart screen and speaker 2 are also in sync, if a user performs a user operation on mobile phone A to start playing a video and cast it to the smart screen, mobile phone A can project the data of the video to be played onto the smart screen for video display, and the smart screen can also project the audio data of the video to be played onto speaker 2 for audio playback. From these two examples, it can be seen that the smart screen projecting audio data onto speaker 2 for playback can be implemented based on a playback task generated by the smart screen in a scenario where the smart screen and speaker 2 are in sync; it can also be implemented based on task information sent by the mobile phone in a scenario where both the mobile phone and the smart screen are in sync, and the smart screen and speaker 2 are in sync. This application does not limit this to either approach.

[0206] It is understood that when this application is implemented, the radar chart displayed on the mobile phone can not only realize the collaboration between peripheral devices and the central device (mobile phone), but also assist in realizing the collaboration between peripheral devices (such as the second-level peripheral device - speaker 2) and peripheral devices (such as the first-level peripheral device - smart screen). Therefore, it can facilitate users to easily realize the collaboration between multiple terminal devices based on a mobile phone with touch capabilities.

[0207] Additionally, it's understandable that users can also disconnect already coordinated terminal devices from each other using the radar chart displayed on their mobile phones. For example, by dragging the speaker 2 icon away from the smart screen icon in interface 43, the speaker 2 and smart screen icons will no longer be attached together, thus disconnecting the speaker 2 from the smart screen. Other coordination scenarios and specific implementation processes will not be elaborated upon; please refer to the content described in the foregoing embodiments.

[0208] Scenario 2, such as Figure 5 As shown, assuming there is a mobile phone B, device scanning on mobile phone B can also discover speaker 1, the smart screen, and the smart screen's peripheral devices (earphone 3 and speaker 2); in addition, mobile phone B can also discover speaker 3. This is understandable. Figure 5 The network structure shown is a second network structure with mobile phone B as the super central device. Combined with... Figure 4a and Figure 5 As shown, a terminal device can be discovered and connected to by different terminal devices during the device scanning process. For example, a smart screen can not only be discovered and connected to mobile phone A, but also be discovered and connected to mobile phone B.

[0209] For example, if the user is Figure 5 On interface 51, users can drag and drop speaker 1 onto phone B, enabling collaboration between speaker 1 and phone B. Figure 5 As shown in interface 52, although speaker 1 is connected to mobile phone A, it is not in a coordinated state; therefore, speaker 1 can be considered to be in a preemptible state. At this time, mobile phone B can preempt speaker 1. After detecting user interaction on interface 51, mobile phone B can notify mobile phone A so that mobile phone A displays the following... Figure 5 The pop-up message "Notification: The connection with speaker 1 has been lost" is displayed to promptly inform the user of mobile phone A about the status of speaker 1.

[0210] Additionally, in this scenario, after phone A receives a notification from phone B, it can also set speaker 1 to display a preset effect, such as... Figure 5 As shown in interface 46, speaker 1 can be displayed as a blurred effect to indicate that speaker 1 has been preempted by other terminal devices and is in an uncooperative state in the network structure managed by mobile phone A. It is understood that in actual implementation, other preset effects can be set, such as a gray background, or the speaker 1 icon can be hidden from display on mobile phone A; this application does not limit this. Optionally, in response to dragging the blurred speaker 1 icon on mobile phone A, mobile phone A can also display a pop-up notification to remind the user that speaker 1 is in an uncooperative state and cannot be coordinated in the network structure managed by mobile phone A.

[0211] Scenario 3, such as Figure 6 As shown in interface 53, if mobile phone B detects the user's operation of dragging speaker 2 to the smart screen, since speaker 2 and smart screen are cooperating with mobile phone A, it can be considered that speaker 2 and smart screen are in an unpreemptible state. Therefore, mobile phone B cannot achieve the collaboration between speaker 2 and smart screen. At this time, a prompt pop-up window as shown in interface 54 can be displayed: "Alarm: Connection failed, smart screen is being occupied!", so as to promptly remind the user of mobile phone B that the collaboration failed.

[0212] As can be understood, referring to the content described in Scenario 2, on phone A, if speaker 2 and smart screen are already working together, after phone B receives a notification from phone A, smart screen, or speaker 2, it can also update the display effect of the speaker 2 and smart screen identifiers in the network structure displayed on phone B. For example, it can display them with a gray background, a blurred effect, or no longer display the smart screen identifier. The notification can be an instruction message indicating a change in device status; or it can be a database synchronization message, which is a synchronization message sent from the terminal device (e.g., smart screen) to the database of the relevant terminal device (e.g., phone A or phone B) after updating distributed data based on the change in device status.

[0213] Scenario 4, despite Figure 6 As not shown in the diagram, if mobile phone B detects a user's action of dragging speaker 3 to the phone, assuming that speaker 3 is only in a connected state with mobile phone B at this time (which can also be understood as an idle state, i.e., not connected to other central devices and not in a coordinated state), then mobile phone B can respond to the user's action and achieve coordination between speaker 3 and mobile phone B.

[0214] It is understandable that, based on the content described in the aforementioned scenarios, during the interaction process of multi-device networking, peripheral devices (including first-level peripheral devices, second-level peripheral devices, etc.) may exist in, but are not limited to, the following states: idle state (e.g., ... Figure 6 3) Speakers in the middle, connected but preemptible (e.g.) Figure 5 The speaker in the middle 1) is in a non-preemptive state (such as Figure 6 (Speaker 2 in the middle). Among them, peripheral devices in the idle state can usually achieve successful device collaboration; peripheral devices in the connected but preemptible state can usually also achieve successful device collaboration and can promptly notify the connected terminal devices to display prompt information on mobile phone A as shown in interface 45; peripheral devices in the non-preemptible state cannot perform collaboration, and alarm information such as shown in interface 54 can be displayed to the user.

[0215] Based on the scenarios and examples described above, the method provided by this application can be applied to more application scenarios to meet the needs of users in more intelligent scenarios. Furthermore, in scenarios where the central device is a touch-enabled terminal device, it can meet the user's need for more convenient device interaction, and can also enable device interaction between peripheral devices based on the central device. This allows for better multi-device interaction and control based on the central device's excellent control capabilities, thereby improving the user experience.

[0216] It is understood that the various scenarios described above can be combined with each other, and this application is not limited to the above scenarios in its implementation.

[0217] Based on the foregoing description of the interface processing effects achievable using the methods provided in this application across multiple scenarios, the following describes the implementation process of the multi-device networking method provided in this application, to illustrate how the methods provided in this application can achieve the aforementioned results. Figures 4a to 6 The interface processing effect shown allows for collaboration between more terminal devices in more scenarios. (See also...) Figure 7 This is a flowchart illustrating a possible embodiment of a multi-device networking method provided in this application. This method can be applied to terminal devices (such as mobile phones, tablets, PCs, etc.) and may include the following steps:

[0218] Step 701: The user triggers "HyperTerminal" on the first terminal device.

[0219] The first terminal device may include at least several functional units of key interest in this application's embodiments: a "super terminal," a distributed database, a DEF (Distributed Electronic Function), and a soft bus. It should be noted that these functional units are merely logical functional divisions; their implementation can take any form, such as integration into a single module or independent configuration. This application does not impose any limitations on this. The "super terminal" (or "Hiplay") primarily provides an interactive interface for the user on the display panel and can serve as a trigger entry point for multi-device networking services. The distributed database is primarily responsible for the creation, updating, and synchronization of distributed data among multiple devices, facilitating timely acquisition of device information, capabilities, network connection status, and online / offline status. The DEF is primarily responsible for distributed task scheduling, sending and receiving cross-terminal device commands, and processing. The soft bus is responsible for device discovery and establishing data channels.

[0220] For example, a user triggering "HyperTerminal" on a first terminal device can be implemented as follows: Figure 4a The implementation method in interface 41 allows users to enter the multi-device networking process through the "HyperTerminal" service card included in the notification bar page of the first terminal device.

[0221] Step 702: The first terminal device initiates device scanning. For example, the first terminal device can discover nearby terminal devices based on a soft bus, such as via Bluetooth or Wi-Fi.

[0222] Step 703: The first terminal device discovers the second terminal device. For example, the first terminal device discovers a terminal device (such as the second terminal device) after scanning via a soft bus. It should be noted that this example uses the first terminal device discovering the second terminal device as an example; the processing flow for the first terminal device discovering other terminal devices can be referred to the processing flow for the second terminal device, and will not be repeated here. Furthermore, after the first terminal device discovers the second terminal device, it can establish a communication link with the second terminal device, such as a Bluetooth link, a Wi-Fi link, etc.; for example, if the first terminal device discovers the second terminal device via Bluetooth, it can establish a Bluetooth link with the second terminal device.

[0223] Step 704: The first terminal device creates a distributed database. For example, the first terminal device creates a distributed database based on the discovered second terminal device and its device information. It can be understood that if the first terminal device has already created a distributed database, the device information of the second terminal device can be directly updated in the already created distributed database.

[0224] In this embodiment, the created distributed database can be used to store the network connection relationships (also understood as the "structural relationships" in the network structure) between multiple terminal devices, such as the discovery results and network connection status between terminal devices. This facilitates the display of the corresponding "Super Terminal" interface based on the created distributed database, supporting the implementation of multi-device networking. It can be understood that the distributed network structure included in the "Super Terminal" interface can be obtained based on the structural relationships between multiple terminal devices stored in the distributed database.

[0225] Step 705: The first terminal device issues a cross-terminal device discovery command. The "SuperTerminal" can send this cross-terminal device discovery command to the second terminal device via DEF. This command instructs the second terminal device to perform device discovery, enabling faster and more efficient acquisition of the distributed network. This avoids requiring the user to perform a device scan on the second terminal device before initiating the scan, thus saving scanning time. Alternatively, the cross-terminal device discovery command can be a synchronization request message, which can be used to request synchronization of the distributed database from the second terminal device.

[0226] Step 706: The second terminal device triggers "HyperTerminal". For example, after receiving a cross-device discovery instruction from the first terminal device, the second terminal device triggers entry into "HyperTerminal" in response to the cross-device discovery instruction.

[0227] Similar to the first terminal device, the second terminal device may also include at least several functional units of particular interest in this application embodiment: a "super terminal," a distributed database, a DEF (Decentralized Electronic Function), and a soft bus. The main functions of each unit will not be elaborated here.

[0228] Step 707: The second terminal device initiates a device scan. For example, the second terminal device can also discover nearby terminal devices based on a soft bus, such as via Bluetooth or Wi-Fi.

[0229] Step 708: The second terminal device performs device discovery. For example, the second terminal device can also discover other terminal devices (assuming a third terminal device) based on device scanning. Optionally, if the second terminal device can also discover the third terminal device, in a scenario where the first terminal device is the central device in a multi-device network, the second terminal device can act as a first-level peripheral device of the first terminal device, and the third terminal device can further act as a second-level peripheral device of the first terminal device. It is understood that, although... Figure 7 As not shown in the diagram, the second terminal device can also send cross-terminal device discovery commands to the third terminal device. The processing procedure of the third terminal device can be found in the second terminal device documentation, and will not be repeated here. Furthermore, during the device scanning and discovery process, multiple devices can be discovered sequentially until no further peripheral devices at the next level are found. In this way, a larger distributed network can be built.

[0230] Alternatively, in a scenario where the second terminal device serves as the central device in a multi-device network, the first terminal device can serve as a peripheral device of the second terminal device, and the third terminal device can serve as another peripheral device of the second terminal device.

[0231] Step 709: The second terminal device updates the distributed database. For example, similar to the processing flow of the first terminal device, after device discovery, the second terminal device can also update the already created distributed database; or, if the second terminal device does not have an existing distributed database, it can create one.

[0232] Optionally, when updating the distributed database, the first terminal device and the second terminal device can perform updates using incremental updates, such as incremental additions, incremental deletions, or incremental changes. This improves update efficiency because the amount of data being changed is small; and because updates to the distributed database can be triggered in response to device discovery results from the terminal devices, synchronization performance is high.

[0233] Step 710: The second terminal device synchronizes distributed data with the first terminal device. For example, the second terminal device can send a database synchronization message to the first terminal device. Through distributed data synchronization, the first terminal device can promptly obtain information such as the network connection status and online / offline notifications of each terminal device in the distributed network, enabling more accurate multi-device networking. For instance, in a scenario where the second terminal device discovers a third terminal device, it can promptly synchronize the updated distributed data to the first terminal device, allowing the first terminal device to obtain the network connection information of the second terminal device. In this way, the first terminal device can not only establish a connection with the second terminal device but also obtain information about the network connection status of the second terminal device (e.g., peripheral devices connected to the second terminal device) based on the distributed database data synchronization, thereby enabling the creation of a distributed network containing more terminal devices. It should be noted that the second terminal device can send a database synchronization message to the first terminal device after each update of the distributed database or periodically, so that the first terminal device can promptly synchronize and update the distributed database.

[0234] Step 711: Display the first interface based on synchronized distributed data. For example, if the second terminal device discovers the third terminal device, the first terminal device can update the radar chart based on the synchronized distributed data of the second terminal device, meaning the third terminal device can also be displayed in the radar chart. Optionally, if the first terminal device is the central device, the third terminal device is displayed as a peripheral device of the second terminal device (i.e., a second-level peripheral device of the first terminal device) on the radar chart of the first terminal device. Alternatively, if the second terminal device is the central device, the third terminal device and the first terminal device are simultaneously displayed as two peripheral devices of the second terminal device on the radar chart of the first terminal device. It can be understood that the first terminal device can obtain the identifier of the terminal device connected to the second terminal device, such as the identifier of the third terminal device, through the second terminal device.

[0235] Step 712: The first terminal device detects a first operation on the first interface. For example, in conjunction with the foregoing... Figure 4aThe content described uses mobile phone A as the first terminal device, smart screen as the second terminal device, and speaker 2 as the third terminal device as an example. Mobile phone A can detect the user's first operation of dragging speaker 2 to smart screen.

[0236] Step 713: The first terminal device sends a first instruction message to the second terminal device. For example, after detecting the first operation, the mobile phone, in response to the first operation, can instruct the smart screen and speaker 2 to coordinate.

[0237] For example, mobile phone A can also determine whether the smart screen and speaker 2 can successfully collaborate based on data in a distributed database. Optionally, if speaker 2 is in an idle state, the smart screen can successfully collaborate with speaker 2, and the first instruction message can be used to instruct the smart screen and speaker 2 to perform collaborative processing. In this scenario, when mobile phone A sends the first instruction message to the smart screen, it can also carry the collaboration method in the first instruction message. Optionally, mobile phone A can determine the collaboration method between the smart screen and speaker 2 based on information such as user operation, device type, or device operating status; wherein, the collaboration method can include, but is not limited to, any of the following methods: screen mirroring, application projection, audio projection, and task relay. For example, mobile phone A can display a pop-up window to the user on the first interface, which can be used to instruct the user to select the collaboration method between the smart screen and speaker 2, such as selecting to project the device audio data of the smart screen onto speaker 2 for playback, or selecting to project the currently playing application audio data onto speaker 2 for playback. In another example, mobile phone A can instruct the smart screen to project audio data onto speaker 2 for playback, based on whether speaker 2 is a device with audio playback capabilities. Yet another example, mobile phone A can instruct the smart screen to project the audio data of a video currently playing on a video app onto speaker 2 for playback.

[0238] In another example, mobile phone A can also directly send a first instruction message to the smart screen. In this case, the first instruction message instructs the smart screen user to request the smart screen to collaborate with speaker 2. In this example, the smart screen can determine whether it can collaborate with speaker 2 based on data stored in a distributed database. Optionally, if the smart screen determines that it can collaborate with speaker 2, it can return a collaboration success instruction message to mobile phone A. Alternatively, if the smart screen determines that it cannot collaborate with speaker 2, it can return a collaboration failure instruction message to mobile phone A. Thus, mobile phone A can update the control interface to show that the icons for the smart screen and speaker 2 have collaborated based on the collaboration success instruction message; or, mobile phone A can also display a prompt message in the control interface indicating that the collaboration between the smart screen and speaker 2 has failed, based on the collaboration failure instruction message.

[0239] Furthermore, it's understandable that phone A, based on data from a distributed database, determines that the collaboration between the smart screen and speaker 2 has failed. In this case, a second interface can be directly displayed on phone A. For example, if speaker 2 is in a non-preemptible state, and phone A determines that the collaboration between the smart screen and speaker 2 has failed, phone A can directly display a second interface to the user, indicating the failure of the collaboration between the smart screen and speaker 2. It's understandable that in this scenario, the smart screen can be unaware of the collaboration failure.

[0240] Step 714: The second terminal device performs collaborative processing. For example, if the first instruction message is used to instruct the smart screen and speaker 2 to perform collaborative processing when mobile phone A determines that the smart screen and speaker 2 have successfully collaborated, the smart screen can project audio data onto the speaker 2 for audio playback based on the first instruction message. In another example, if the first instruction message is used to instruct the smart screen to determine whether it can collaborate with speaker 2, the smart screen can project audio data onto speaker 2 for audio playback when it determines that it can collaborate with speaker 2. Here, based on the connection between the smart screen and speaker 2, a communication link is established between the smart screen and speaker 2. When the smart screen determines that it is collaborating with speaker 2, it can start transmitting service data through the established communication link with speaker 2. The statement that the smart screen and speaker 2 are collaborating indicates that the smart screen can send service data that can be processed by speaker 2 to speaker 2. For example, if the smart screen is playing a video, it can send the video's audio data to speaker 2 so that speaker 2 can play the audio data. It is understandable that if the user only performs user operations on the browsing interface of the smart screen, the smart screen does not send any business data to speaker 2; and when the smart screen has audio data, it sends it to speaker 2 for playback.

[0241] Step 715: The second terminal device updates the distributed database. For example, the smart screen can update the network connection status of its collaboration with speaker 2 into the distributed database.

[0242] Step 716: The second terminal device synchronizes distributed data with the first terminal device. For example, the smart screen can promptly synchronize the updated distributed database to the connected terminal devices (e.g., to the first terminal device) to promptly notify the super central device within the distributed network of changes in the network connection status between the terminal devices within the network. This allows the super central device to promptly obtain the latest network structure and avoid business conflicts.

[0243] It's understandable that in a distributed network, when the network connection status of any terminal device changes, the distributed database can be updated and synchronized to connected terminal devices within the network. Optionally, peripheral devices within the network can send synchronization information to the central device, which then updates the distributed data.

[0244] Step 717: The first terminal device displays a second interface based on synchronized distributed data. For example, the second interface differs from the first interface in that, on the first interface, the smart screen and speaker 2 are connected but not in a coordinated state; on the second interface, the smart screen and speaker 2 are in a coordinated state. The first interface is as follows: Figure 4a As shown in interface 42, the second interface is as follows: Figure 4a The interface shown in 43 is shown in the image.

[0245] It is understood that the first terminal device can also receive other user operations, and the response process for these other user operations is as described in steps 712 to 717, and will not be repeated here. The first terminal device can be, for example, a mobile phone, tablet computer, or laptop computer; the second terminal device can be a terminal device with a display function, such as a smart TV; the third terminal device can be a terminal device with audio playback function, such as a speaker or headphones; or, the second terminal device can also be a terminal device with auxiliary control functions, such as a watch, and the third terminal device can be a terminal device with specific functions, such as a jump rope or a treadmill.

[0246] Based on the aforementioned processing flow, in the process of multi-device networking, the constructed network is typically a multi-level distributed network consisting of a central device, at least one peripheral device of the central device, and at least one peripheral device of the peripheral device. The central device within the network can also be understood as a super central device, capable of obtaining the identifiers of the peripheral devices of other central devices that serve as its peripheral devices.

[0247] For example, Figure 8 The topology diagram shown depicts a network with mobile phone A as the central device; speaker 1, earphone 1, and smart screen as first-level peripheral devices; and earphone 2, speaker 2, and watch as peripheral devices of the smart screen, and also as second-level peripheral devices of mobile phone A. These peripheral devices are identified through device scanning and discovery using terminal devices. For example, multiple terminal devices can discover peripheral devices, resulting in a distributed network with multiple central devices, such as... Figure 4aInterface 42 shows two distributed networks: one centered on a smart screen and the other centered on a smartwatch. How to determine the central device during device scanning and discovery on mobile phone A is also worth studying.

[0248] In one alternative example, multiple terminal devices can negotiate to determine a central device. For example, mobile phone A, smart screen and watch in interface 42 can collaboratively determine mobile phone A as the central device to obtain a radar chart as shown in interface 42.

[0249] Optionally, one possible negotiation rule may include, but is not limited to, the following principles:

[0250] Principle 1: Use touch-enabled terminal devices as central devices. For example, to facilitate user touch control, touch-enabled terminal devices can be prioritized as central devices. These could include mobile phones, tablets (PADs), in-vehicle computers, watches, etc. For instance, in the mobile phone A, smart screen, and watch shown in interface 42, the touch-enabled terminal devices are mobile phone A and the watch. Therefore, in the implementation of this application, mobile phone A and the watch can be prioritized as central devices in a multi-device network.

[0251] If multiple terminal devices that meet the conditions can be obtained based on principle 1, then the following principles can be used to make a judgment.

[0252] Principle 2: Designate higher-priority terminal devices as central devices. For example, different weight factors or priorities can be pre-configured for different terminal devices; then, the priority of each terminal device in a multi-device network can be determined based on the weight factors or priorities.

[0253] For example, in the implementation of this application, different weight factors or priorities are assigned to different terminal devices based on the different types of terminal devices involved in different application scenarios (such as the major scenarios shown in Table 1 below). Table 1 is as follows:

[0254] Table 1

[0255] Scene Terminal equipment involved Smart Home Mobile phones, tablets, smart screens, speakers, cameras, door locks Audio-visual entertainment Mobile phones, tablets, smart screens, headphones, AI, speakers Smart Office Mobile phones, PCs, tablets, smart screens, speakers Sports and Health Mobile phones, watches, fitness trackers, smart screens, treadmills Smart Mobility Mobile phones, tablets, and in-vehicle computers …… ……

[0256] Based on the five main application scenarios shown in Table 1, different weighting factors or priorities can be assigned to different terminal devices according to the number of scenarios involved. Optionally, one possible allocation of weighting factors is as follows: mobile phone (weighting factor 5) > PAD (weighting factor 4) = smart screen (weighting factor 4) > speaker (weighting factor 3) > PC (weighting factor 1) = headphones (weighting factor 1) = in-vehicle computer (weighting factor 1) = watch (weighting factor 1)...

[0257] Optionally, to ensure user data security and enhance user privacy when using the "Super Terminal" network, this embodiment may also allocate weight factors based on the privacy of the terminal device. For example, mobile phones, as personal devices, are generally considered to have higher privacy, and therefore can be assigned a larger weight factor; smart screens, as general-purpose devices, have lower privacy than mobile phones, and therefore can be assigned a smaller weight factor. Based on this, in implementing this application, terminal devices with better privacy can be preferentially selected as the central device to better protect user data security.

[0258] It is understandable that if there are weighting factors allocated based on multiple factors (such as terminal device type, privacy, etc.), the central device can be selected based on the weighted sum value.

[0259] For example, in a multi-device networking scenario, multiple negotiating terminal devices can choose the terminal device with the highest priority (or the highest weighted sum value) as the central device; for example, in interface 42, mobile phone A, smart screen and watch, based on principle 1, mobile phone A and watch are preferentially selected as the central devices in the multi-device networking, and based on principle 2, mobile phone A with a higher weight factor can be selected as the central device in the multi-device networking according to the weight factor.

[0260] Principle 3: Use the user-controlled terminal device as the central device. For example, in scenarios where some terminal devices have the same weight factor (or priority) as in Principle 2, such as both the PAD and the smart screen having a weight factor of 4, in a multi-device network scenario with both PADs and smart screens, the user-controlled terminal device can be further selected as the central device. For example, if a user triggers "Super Terminal" on the PAD and discovers the smart screen through device scanning and discovery, the user can select the PAD they are currently operating as the central device from both the PAD and the smart screen, allowing the user to perform drag-and-drop operations based on a multi-device network centered on the PAD.

[0261] In another optional example, when implementing this application, a terminal device, a terminal device of a specified type, or a terminal device of a specified rule can be designated as the control device for multi-device networking (also known as a "super center"); then, the terminal device acting as the "super center" can be used to designate a central device or determine the central device based on preset rules, etc.

[0262] For example, assuming a PC is used as the "super center," in a multi-device network scenario, if a PC is present, the PC can determine the central device based on all terminal devices discovered in the multi-device network scenario and the terminal device that triggered the device scan. For instance, assuming a mobile phone triggers device scan and device discovery, obtaining a PC, a PAD, and a smart screen, then in a distributed network scenario including a mobile phone, PC, PAD, and smart screen, the PC can determine which terminal device to use as the central device. Optionally, the PC can also determine the central device based on principles 1 to 3 described in the aforementioned example; another option is that the PC can also specify the central device based on the network connection status of each terminal device. For example, if the PC determines based on a distributed database that the mobile phone has many peripheral devices, it can prioritize specifying the mobile phone as the central device; yet another example is that the PC can also determine the central device based on other preset rules, which this application does not limit.

[0263] In this way, by setting up a "super center" in a multi-device network, compared to the multi-device negotiation method, the amount of data exchanged between devices can be reduced, avoiding the occupation of bandwidth resources. The "super center" can determine the central device through decision-making, and then notify the central device. It can be understood that the "super center" can select terminal devices with strong processing capabilities (such as mobile phones, PCs, or tablets), thus avoiding the occupation of processing performance on terminal devices with weaker processing capabilities. Furthermore, the implementation method of determining the central device based on the "super center" can better align with user intent, thereby improving the user experience.

[0264] In another possible example, in this embodiment of the application, a selection interface for the central device can also be displayed on the user-operated terminal device (e.g., mobile phone A). On the selection interface of mobile phone A, if a user's selection operation for choosing a central device is detected, mobile phone A can also respond to this selection operation to determine the central device of the distributed network to which mobile phone A belongs. It can be understood that mobile phone A can synchronize the determined central device to other terminal devices within the network through a distributed database.

[0265] Furthermore, in a multi-device network scenario established based on the aforementioned content, if a terminal device needs to disconnect, and if the terminal device is a peripheral device, the peripheral device can send a request message to the central device. After the central device agrees to disconnect, the device will be taken offline from the multi-device network (e.g., no longer displayed in the radar chart, or displayed with the default display effect). If the terminal device is a central device, the central device can actively disconnect from the peripheral devices. In this case, the connection between the central device and the first-level peripheral devices in the multi-device network scenario is disconnected, while the first-level peripheral devices can continue to maintain connections with the second-level peripheral devices and peripheral devices at more levels. At this time, the original distributed network can be divided into one or more distributed networks with peripheral devices at different levels as central devices.

[0266] Understandable, such as Figure 8 The smart screen can serve as the central device for the earphones 2, speaker 2, and watch. The implementation method for determining the smart screen as the central device among the smart screen, earphones 2, speaker 2, and watch can be found in the previously introduced process of determining the central device, and will not be repeated here.

[0267] The method provided in this application embodiment can construct a distributed network that includes more terminal devices, covers a wider range of scenarios, and collaboratively associates more terminal devices, and has hierarchical characteristics. Based on the combination of the UI on the terminal devices and the distributed database, multi-device interaction across terminal devices can be achieved. On the one hand, based on the updates and synchronization of the distributed database, terminal devices can promptly perceive the online or offline status of other terminal devices, as well as the network connection status (e.g., idle state, connected but preemptible state, and non-preemptible state), thereby supporting timely display of the user interface and interactive operations on the user interface, thus avoiding issues such as... Figure 1a The scenario illustrated presents a potential business interruption issue due to business conflicts. On the other hand, based on a hierarchical distributed network, touch operation between more terminal devices can be facilitated. For example, collaboration between peripheral devices at different levels can be achieved on a central device with touch capabilities (e.g.,...). Figure 4a The collaboration between speaker 2 and smart screen shown in interface 42 provides greater convenience for touch control compared to the collaborative processing method in related technologies that requires remote control on the smart screen, making it easier to intelligently control terminal devices in a distributed network.

[0268] Based on the above embodiments, this application also provides a terminal device, which includes at least one processor and at least one memory. The at least one memory stores computer program instructions. When the terminal device is running, the at least one processor executes the functions performed by the terminal device in the various methods described in the embodiments of this application. For example, when executing... Figure 7 In the illustrated embodiment, the first terminal device executes steps 701 to 705, steps 710 to 713, and steps 716 to 717; or executes... Figure 7 Steps 705 to 710 and 713 to 716 are performed by the second terminal device in the illustrated embodiment.

[0269] Based on the above embodiments, this application also provides a multi-device networking system, which includes multiple terminal devices as described in the above embodiments, such as at least including Figure 7 The first terminal device and the second terminal device may also include the third terminal device mentioned in the above embodiments.

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

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

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

[0273] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the methods described in the embodiments of this application. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete devices.

[0274] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

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

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

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

Claims

1. A multi-device networking system, characterized in that, This includes a first terminal device, a second terminal device, and a third terminal device; The first terminal device is used to display a first interface, the first interface including multiple terminal device identifiers, the multiple terminal device identifiers including the identifier of the second terminal device and the identifier of the third terminal device; wherein, the second terminal device and the third terminal device are connected; The first terminal device is further configured to detect and respond to a first operation on the first interface, and send a first instruction message to the second terminal device, the first instruction message being used to instruct the second terminal device to cooperate with the third terminal device; The second terminal device is configured to receive the first instruction message and coordinate with the third terminal device according to the first instruction message.

2. The system according to claim 1, characterized in that, The first terminal device is further configured to: When it is determined that the second terminal device and the third terminal device have collaborated, a second interface is displayed, which is used to indicate that the second terminal device and the third terminal device have collaborated.

3. The system according to claim 1 or 2, characterized in that, The first interface includes a first network structure composed of the plurality of terminal device identifiers, the plurality of terminal device identifiers including the identifier of the second terminal device and the identifier of the terminal device connected to the second terminal device; wherein, the terminal device connected to the second terminal device includes the third terminal device.

4. The system according to claim 3, characterized in that, The plurality of terminal device identifiers also include the identifier of the first terminal device and the identifier of the terminal device connected to the first terminal device; wherein, the terminal device connected to the first terminal device includes the second terminal device.

5. The system according to claim 3 or 4, characterized in that, Before displaying the first interface The first terminal device is further configured to display a third interface, the third interface including an identifier of the first terminal device and an identifier of a terminal device connected to the first terminal device; wherein, the terminal device connected to the first terminal device includes the second terminal device; When the first terminal device displays the first interface, it is specifically configured to: display the first interface when an operation acting on the identifier of the second terminal device is detected.

6. The system according to claim 1, characterized in that, The first terminal device is further configured to: A second operation is detected, the second operation being used to instruct the first cooperating device combination to further cooperate with the first terminal device, the first cooperating device combination being used to instruct the second terminal device and the third terminal device that have already cooperated; In response to the second operation, a fourth interface is displayed, which indicates that the first terminal device has been combined with the first collaborating device for further collaboration.

7. The system according to claim 6, characterized in that, The first terminal device is further configured to: if a first instruction for instructing the processing of a first task is detected, in response to the first instruction, execute a first sub-task of the first task in combination with the first coordinating device; The second terminal device is further configured to: receive task data of the first sub-task, and execute the first sub-task collaboratively with the third terminal device.

8. The system according to any one of claims 1 to 7, characterized in that, The second terminal device is further configured to: if a first event for processing the second task is detected, in response to the first event, execute a second sub-task of the second task through the third terminal device; The second terminal device, when detecting a first event for processing a second task, is specifically configured to: detect a first user operation on a first display interface of the second terminal device, the first user operation being used to generate the second task; or, receive task information from the first terminal device, the task information being used to indicate task data for the second task. Wherein, the second terminal device is a device with display function, and the third terminal device is a device with audio playback function; the second task is a playback task; the second subtask is the audio playback task of the playback task; the second terminal device is further configured to, in response to the first event, display the display data of the playback task, and send the audio data of the playback task to the third terminal device, so that the third terminal device can execute the audio playback task of the audio data; the third terminal device is further configured to receive the audio data and play the audio data.

9. The system according to any one of claims 1 to 8, characterized in that, Before displaying the first interface, the first terminal device is further configured to: The identifier of the terminal device connected to the second terminal device is obtained through the second terminal device, and the terminal device connected to the second terminal device includes the third terminal device.

10. The system according to claim 9, characterized in that, The first terminal device is further configured to: before displaying the first interface, update the distributed database on the first terminal device according to the identifier of the scanned terminal device and the identifier of the terminal device connected to the second terminal device obtained through the second terminal device, wherein the distributed database is used to indicate the structural relationship between multiple terminal devices; When the first terminal device is used to display the first interface, it is specifically used to: display the first interface according to the structural relationship.

11. The system according to claim 10, characterized in that, Before updating the distributed database on the first terminal device The first terminal device is further configured to: perform device scanning, wherein the scanned devices include the second terminal device, and send a synchronization request message to the second terminal device; The second terminal device is further configured to: after receiving the synchronization request message, send a first database synchronization message to the first terminal device, wherein the first database synchronization message includes the identifier of the terminal device in the distributed database on the second terminal device, and wherein the distributed database on the second terminal device includes the identifier of the terminal device connected to the second terminal device; The first terminal device is further configured to: receive the first database synchronization message sent by the second terminal device; When the first terminal device updates the distributed database on the first terminal device, it is specifically used to: update the identifier of the terminal device connected to the second terminal device, the identifier of the terminal device connected to the second terminal device, and the connection relationship between the second terminal device and the second terminal device in the first database synchronization message to the distributed database on the first terminal device.

12. The system according to claim 2, characterized in that, When the first terminal device is used to display the first interface, it is specifically used to: display the first interface according to a distributed database on the first terminal device, wherein the distributed database is used to indicate the structural relationship between multiple terminal devices; When the first terminal device displays the second interface, it is specifically configured to: receive a second database synchronization message sent by the second terminal device, the second database synchronization message indicating that the second terminal device and the third terminal device have collaborated; update the distributed database according to the second database synchronization message, and display the second interface according to the updated distributed database.

13. The system according to any one of claims 1 to 12, characterized in that, The system also includes a fourth terminal device and a fifth terminal device; The first terminal device is further configured to display a fifth interface, the fifth interface including multiple terminal device identifiers, the multiple terminal device identifiers including the identifier of the fourth terminal device and the identifier of the fifth terminal device; wherein, the fourth terminal device and the fifth terminal device are connected; The first terminal device is further configured to detect a third operation on the fifth interface, the third operation being configured to instruct the fourth terminal device and the fifth terminal device to cooperate; The first terminal device is further configured to display a sixth interface when it is determined that the fourth terminal device and the fifth terminal device cannot cooperate, the sixth interface being used to indicate that the fourth terminal device and the fifth terminal device have failed to cooperate.

14. The system according to claim 13, characterized in that, The first terminal device is configured to determine when the fourth terminal device and the fifth terminal device cannot coordinate, specifically for: Based on one or more of the following information: the device type of the fourth terminal device, the device status of the fourth terminal device, the device type of the fifth terminal device, or the device status of the fifth terminal device, it is determined that the fourth terminal device and the fifth terminal device cannot cooperate.

15. The system according to claim 14, characterized in that, The first terminal device is specifically used for: If it is determined from the device status of the fourth terminal device that the fourth terminal device is already in a collaborative state, it is determined that the fourth terminal device and the fifth terminal device cannot collaborate. or, If the fifth terminal device is determined to be in a collaborative state based on its device status, then the fourth terminal device and the fifth terminal device are determined to be unable to collaborate.

16. The system according to any one of claims 14 to 15, characterized in that, The identifier of the fourth terminal device included in the fifth interface is displayed as a preset effect; and / or, The identifier of the fifth terminal device included in the fifth interface is displayed as a preset effect; The preset effect is used to indicate that the terminal device is in a non-cooperative state.

17. The system according to any one of claims 14 to 16, characterized in that, The first terminal device is configured to determine when the fourth terminal device and the fifth terminal device cannot coordinate, specifically for: In response to the first operation, a first instruction message is sent to the fourth terminal device, the first instruction message being used to instruct the fourth terminal device and the fifth terminal device to cooperate. The fourth terminal device receives information indicating that the collaboration between the fourth terminal device and the fifth terminal device has failed, and determines that the collaboration between the fourth terminal device and the fifth terminal device has failed based on the collaboration failure information.

18. The system according to any one of claims 1 to 17, characterized in that, The first terminal device is a mobile phone, tablet computer, or laptop computer; the second terminal device is a smart TV; and the third terminal device is a speaker or headphones.

19. A multi-device networking system, characterized in that, This includes a first terminal device, a second terminal device, and a third terminal device; The first terminal device is used to display a first interface, the first interface including multiple terminal device identifiers, the multiple terminal device identifiers including the identifier of the second terminal device and the identifier of the third terminal device; wherein, the second terminal device and the third terminal device are connected; The first terminal device is further configured to detect a first operation on the first interface, the first operation being configured to instruct the second terminal device and the third terminal device to cooperate; The first terminal device is further configured to display a seventh interface when it is determined that the second terminal device and the third terminal device cannot cooperate, the seventh interface being used to indicate that the second terminal device and the third terminal device have failed to cooperate.

20. The system according to claim 19, characterized in that, The first terminal device is configured to determine when the second terminal device and the third terminal device cannot coordinate, specifically for: Based on one or more of the following information: the device type of the second terminal device, the device status of the second terminal device, the device type of the third terminal device, or the device status of the third terminal device, it is determined that the second terminal device and the third terminal device cannot work together.

21. The system according to claim 20, characterized in that, The first terminal device is specifically used for: If it is determined that the second terminal device is already in a collaborative state based on the device status of the second terminal device, it is determined that the second terminal device and the third terminal device cannot collaborate. or, If the device status of the third terminal device determines that the third terminal device is already in a collaborative state, it is determined that the second terminal device and the third terminal device cannot collaborate.

22. The system according to any one of claims 19 to 21, characterized in that, The identifier of the second terminal device included in the first interface is displayed as a preset effect; and / or, The identifier of the third terminal device included in the first interface is displayed as a preset effect; The preset effect is used to indicate that the terminal device is in a non-cooperative state.

23. A method for networking multiple devices, characterized in that, Applied to the first terminal device, including The first interface is displayed; wherein the first interface includes multiple terminal device identifiers, the multiple terminal device identifiers include the identifier of a second terminal device and the identifier of a third terminal device; wherein the second terminal device and the third terminal device are connected; Detecting and responding to a first operation on the first interface, a first instruction message is sent to the second terminal device, the first instruction message being used to instruct the third terminal device to cooperate with the second terminal device.

24. The method according to claim 23, characterized in that, The method further includes: When it is determined that the second terminal device and the third terminal device have collaborated, a second interface is displayed, which is used to indicate that the second terminal device and the third terminal device have collaborated.

25. The method according to claim 24, characterized in that, The method further includes: Receive information from the second terminal device indicating that the second terminal device and the third terminal device have failed to cooperate, and determine that the second terminal device and the third terminal device have failed to cooperate based on the information indicating that the cooperation has failed; When it is determined that the second terminal device and the third terminal device have failed to cooperate, a seventh interface is displayed, which is used to indicate that the second terminal device and the third terminal device have failed to cooperate.

26. The method according to claim 23 or 24, characterized in that, The method further includes: The fifth interface is displayed, which includes multiple terminal device identifiers, including the identifier of the fourth terminal device and the identifier of the fifth terminal device; wherein the fourth terminal device and the fifth terminal device are connected. A third operation was detected on the fifth interface, the third operation being used to instruct the fourth terminal device and the fifth terminal device to cooperate; When it is determined that the fourth terminal device and the fifth terminal device cannot work together, a sixth interface is displayed, which is used to indicate that the fourth terminal device and the fifth terminal device have failed to work together.

27. A method for networking multiple devices, characterized in that, Applied to the first terminal device, including: The first interface is displayed, which includes multiple terminal device identifiers, including the identifier of a second terminal device and the identifier of a third terminal device; wherein the second terminal device and the third terminal device are connected. A first operation is detected on the first interface, the first operation being used to instruct the second terminal device and the third terminal device to cooperate. When it is determined that the second terminal device and the third terminal device cannot work together, a seventh interface is displayed, which is used to indicate that the second terminal device and the third terminal device have failed to work together.

28. The method according to claim 27, characterized in that, When it is determined that the second terminal device and the third terminal device cannot cooperate, the following steps are included: Based on one or more of the following information: the device type of the second terminal device, the device status of the second terminal device, the device type of the third terminal device, or the device status of the third terminal device, it is determined that the second terminal device and the third terminal device cannot work together.

29. A first terminal device, characterized in that, include: One or more processors; one or more memories; The one or more memories are used to store one or more computer programs and data information; wherein the one or more computer programs include instructions; When the instruction is executed by the one or more processors, it causes the first terminal device to perform the method performed by the first terminal device as claimed in any one of claims 23 to 28.

30. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 23 to 28.

Citation Information

Patent Citations

  • Display method and terminal device

    CN110688179A