Multi-device coordination method and related apparatus

Abstract

Disclosed in the present application are a multi-device coordination method and a related apparatus. The method comprises: a first terminal detecting a first operation, wherein the first operation is used for sharing a first electronic device with a second account; in response to the first operation, the first terminal sending device sharing information to a server, wherein the device sharing information comprises information of the second account and information of the first electronic device; the server sending the information of the second account to the first electronic device; the server sending the information of the first electronic device to a second terminal; on the basis of the information of the second account and the information of the first electronic device, the second terminal establishing a near-field communication connection with the first electronic device; the second terminal detecting a second operation, wherein the second operation is used for triggering a first distributed service of the second terminal; and in response to the second operation, the second terminal displaying icons of one or more trusted devices, wherein the one or more trusted devices comprise the first electronic device. In this way, devices with different accounts can be coordinated to realize a distributed service.

Description

Multi-device collaboration method and related device

[0001] This application claims priority to the Chinese patent application with application number 202310979898.0 filed with the State Intellectual Property Office of China on August 3, 2023, and priority to the Chinese patent application with invention name “Multi-device collaboration method and related apparatus”. This application claims priority to the Chinese patent application with application number 202310990844.4 filed with the State Intellectual Property Office of China on August 4, 2023, and priority to the Chinese patent application with invention name “Multi-device collaboration method and related apparatus”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of electronic technology, and in particular to a multi-device collaboration method and related apparatus. Background Art

[0003] With the continuous development of terminal technology, users have more and more types of electronic devices with more functions. Due to the limitations of their own hardware structure and system performance, different types of devices usually have different capabilities and advantages. The user's multiple devices, combined with the performance advantages of each device, conduct collaborative control of device interconnection and distributed services, bringing a better user experience to users. For example, mobile terminals such as mobile phones can migrate multimedia content (such as pictures, audio and video, etc.) to smart screens for continued playback; mobile phones can project the mobile phone desktop to the car device, and users can control the phone through the car display; mobile phones can control smart home devices (such as lights, cameras, air conditioners, smart screens), etc.

[0004] Devices with the same account typically have a trust relationship, enabling the coordinated operation of distributed services. However, devices with different accounts typically require users to manually connect and authenticate (for example, by entering a PIN code) to establish a communication connection and enable device collaboration for distributed services, which is cumbersome.

[0005] At present, how to quickly implement distributed services between devices with different accounts still needs further research.

[0006] Summary of the Invention

[0007] The embodiment of the present application provides a multi-device collaboration method, which can quickly implement distributed services between devices for devices with different accounts.

[0008] In the first aspect, the present application discloses a multi-device collaboration method and related apparatus, which are applied to a multi-device collaboration system, characterized in that the above-mentioned system includes a first terminal, a second terminal and a server, the first terminal logs in to a first account, the second terminal logs in to a second account, the first account and the second account are different accounts, and the above-mentioned system also includes at least one electronic device bound to the first account, and the above-mentioned at least one electronic device includes a first electronic device; the method includes: the first terminal detects a first operation, and the first operation is used to share the first electronic device with the second account; in response to the first operation, the first terminal sends device sharing information to the server, and the device sharing information includes information of the second account and information of the first electronic device; the server sends information of the second account to the first electronic device; the server sends information of the first electronic device to the second terminal; based on the information of the second account and the information of the first electronic device, the second terminal and the first electronic device establish a short-range communication connection; the second terminal detects a second operation, and the second operation is used to trigger the first distributed service of the second terminal; in response to the second operation, the second terminal displays icons of the one or more trusted devices; the one or more trusted devices include the first electronic device.

[0009] By implementing the embodiment of the present application, the first electronic device bound to the first account is shared with the second account, and the first electronic device and the second terminal are instructed to obtain each other's information, so that the first electronic device and the second terminal have a trust relationship. That is, when the two devices are close to each other, they can automatically establish a close connection and authentication, completing automatic networking; thereby, the first electronic device and the second terminal, which are not the same account, can also quickly and collaboratively implement distributed services. In this way, a single sharing operation can achieve a long-term and efficient distributed service experience between devices with different accounts, effectively improving the user experience.

[0010] In one implementation, the method further includes: displaying a first identifier along with the icon of the first electronic device, the first identifier being used to indicate that the first electronic device is a device shared by another account with the second account. In implementing this embodiment of the application, the first identifier indicates which devices are shared, allowing the user to have an intuitive understanding of the shared devices.

[0011] In one implementation, the method further includes: the first terminal detects a second operation, and the second operation is used to trigger the first distributed service; in response to the second operation, the first terminal displays icons of one or more trusted devices; the one or more trusted devices include a second electronic device; and the second electronic device is a device shared by other accounts to the first account. When implementing the embodiment of the present application, when executing a distributed service, icons of shared devices of different accounts can be displayed, so that shared devices of different accounts can also collaborate to implement the distributed service. In addition, the first account can share the first electronic device with the second account, and the second account can also share the second electronic device with the first account.

[0012] In one implementation, the method further includes: the second terminal setting a second filter based on the information of the first electronic device, the second filter being used to filter messages from the first electronic device; and the second terminal establishing a short-range communication connection with the first electronic device, including: the second terminal establishing a short-range communication connection with the first electronic device based on the filtered messages of the first electronic device. In implementing this embodiment of the present application, setting the second filter based on the information of the first electronic device can filter out messages from the first electronic device, facilitating the establishment of a short-range communication connection with the first electronic device.

[0013] In one implementation, the method further includes: binding the second account to at least one electronic device, the at least one electronic device including a second electronic device, and the method further includes: in response to the first operation, after the second terminal receives the information of the first electronic device, the second terminal sends device sharing information to the server, and the device sharing information is used to establish a short-range communication connection between the first terminal and the second electronic device.

[0014] In one implementation, a second identifier is displayed alongside the icon of the first electronic device, and the second identifier is used to indicate the first account that shares the first electronic device. In this embodiment of the present application, the user name of the account to which the shared device belongs can be displayed on or around the icon of the shared device, allowing the user to intuitively understand which user is sharing the device with them.

[0015] In one implementation, the method further includes: the second terminal detecting a third operation on the icon of the first electronic device, and in response to the third operation, the second terminal cooperating with the first electronic device to execute the first distributed service. In implementing this embodiment of the present application, a device with a different account can be selected to execute the distributed service.

[0016] In one implementation, a first account creates a first group, family members of the first group include a second account, and a first operation is used to add a first electronic device as an electronic device of the first group. By implementing this embodiment of the present application, devices in the group can be shared with a user by inviting the user to join the group.

[0017] In one implementation, a first account creates a first group, the electronic devices in the first group include the first electronic device, and a first operation is used to add a second account as a family member of the first group. By implementing this embodiment of the present application, the newly added device can be shared with the user by adding the device to the group.

[0018] In one implementation, the first operation is further used to add the device bound to the second account as a family member of the first group.

[0019] In one implementation, the second terminal cooperates with the first electronic device to perform the first distributed service, including: the second terminal and the first electronic device transmit the service data of the first distributed service via a short-range communication connection. In one implementation, the second terminal cooperates with the first electronic device to perform the first distributed service, including: the second terminal sends projection data to the first electronic device via a short-range communication connection; the first electronic device displays the projection screen based on the projection data; or, the second terminal sends application data to the first electronic device via a short-range communication connection; the first electronic device displays the desktop application of the second terminal based on the application data. Alternatively, the second terminal sends audio data to the first electronic device via a short-range communication connection; the first electronic device plays audio based on the audio data. By implementing the embodiments of the present application, devices with different accounts will be able to quickly implement distributed services, such as super terminals, super desktops, screen projection, audio projection and other distributed services.

[0020] In one implementation, the second terminal collaborates with the first electronic device to perform a first distributed service, including: the first electronic device displays a first input box; the first electronic device sends a first request to the second terminal via a near-field communication connection; the first request is used to request the second terminal to assist in inputting information; the second terminal displays a second input box; the second terminal obtains the first information entered by the user in the second input box; the second terminal sends the first information to the first electronic device via a near-field communication connection; the first electronic device displays the first information in the first input box. By implementing this embodiment of the present application, devices with different accounts can quickly implement distributed services, such as assisting in information input.

[0021] In the second aspect, an embodiment of the present application provides a multi-device collaboration method, characterized in that the first terminal logs in to the first account, and the second terminal logs in to the second account, the first account and the second account are different accounts, and the first account is bound to at least one electronic device, and the at least one electronic device includes a first electronic device; the method includes: the first terminal device detects a first operation, and the first operation is used to share the first electronic device with the second account; in response to the first operation, the first terminal device sends device sharing information to the server, and the device sharing information includes information of the second account and information of the first electronic device; the first terminal sends information of the second account to the first electronic device through the server; the first terminal sends information of the first electronic device to the second terminal through the server; the information of the second account and the information of the first electronic device are used to establish a short-range communication connection between the second terminal and the first electronic device.

[0022] By implementing the embodiment of the present application, the first electronic device bound to the first account is shared with the second account, and the first electronic device and the second terminal are instructed to obtain each other's information, so that the first electronic device and the second terminal have a trust relationship. That is, when the two devices are close to each other, they can automatically establish a close connection and authentication, completing automatic networking; thereby, the first electronic device and the second terminal, which are not the same account, can also quickly and collaboratively implement distributed services. In this way, a single sharing operation can achieve a long-term and efficient distributed service experience between devices with different accounts, effectively improving the user experience.

[0023] In one implementation, the method further includes: the first terminal detecting a second operation, where the second operation is used to trigger the first distributed service;

[0024] In response to the second operation, the first terminal displays icons of one or more trusted devices; the one or more trusted devices include a second electronic device; the second electronic device is a device shared by other accounts with the first account.

[0025] In one implementation, the method further includes: displaying a first identifier along with the icon of the second electronic device, where the first identifier is used to indicate that the second electronic device is a device shared with the first account by another account.

[0026] In one implementation, a second identifier is displayed along with the icon of the second electronic device, and the second identifier is used to indicate an account number for sharing the second electronic device.

[0027] In one implementation, the method further includes: the first terminal detecting a fourth operation acting on an icon of the second electronic device, and in response to the fourth operation, the first terminal cooperating with the second electronic device to execute the first distributed service.

[0028] In one implementation, a first group is created with a first account, family members of the first group include a second account, and a first operation is used to add the first electronic device as an electronic device of the first group.

[0029] In one implementation, a first group is created with the first account, the electronic devices of the first group include the first electronic device, and the first operation is used to add the second account as a family member of the first group.

[0030] In one implementation, the first terminal cooperates with the second electronic device to execute the first distributed service, including: the first terminal and the first electronic device transmit service data of the first distributed service through a short-range communication connection.

[0031] In one implementation, a first terminal collaborates with a second electronic device to execute a first distributed service, including: the first terminal sends screen projection data to the second electronic device via a near-field communication connection; the screen projection data is used by the second electronic device to display the projection screen; or the first terminal sends application data to the second electronic device via a near-field communication connection; the application data is used by the second electronic device to display a desktop application of the first terminal. Alternatively, the first terminal sends audio data to the second electronic device via a near-field communication connection; the audio data is used by the second electronic device to play audio.

[0032] In a third aspect, an embodiment of the present application provides a multi-device collaboration method, characterized in that a first terminal logs in to a first account, and a second terminal logs in to a second account, the first account and the second account are different accounts, and the system also includes at least one electronic device bound to the first account, and the at least one electronic device includes a first electronic device; the method includes: the second terminal receives information sent by the server to the first electronic device; based on the information of the first electronic device, the second terminal and the first electronic device establish a short-range communication connection; the second terminal detects a second operation, and the second operation is used to trigger the first distributed service of the second terminal; in response to the second operation, the second terminal displays icons of one or more trusted devices; the one or more trusted devices include the first electronic device.

[0033] By implementing the embodiment of the present application, the first electronic device bound to the first account is shared with the second account, and the first electronic device and the second terminal are instructed to obtain each other's information, so that the first electronic device and the second terminal have a trust relationship. That is, when the two devices are close to each other, they can automatically establish a close connection and authentication, completing automatic networking; thereby, the first electronic device and the second terminal, which are not the same account, can also quickly and collaboratively implement distributed services. In this way, a single sharing operation can achieve a long-term and efficient distributed service experience between devices with different accounts, effectively improving the user experience.

[0034] In one implementation, the method further includes: displaying a first identifier along with the icon of the first electronic device, where the first identifier is used to indicate that the first electronic device is a device shared by another account to the second account.

[0035] In one implementation, a second identifier is displayed along with the icon of the first electronic device, and the second identifier is used to indicate the first account that shares the first electronic device.

[0036] In one implementation, the method also includes: the second terminal sets a second filter based on information of the first electronic device, and the second filter is used to filter messages from the first electronic device; the second terminal and the first electronic device establish a short-range communication connection, including: the second terminal establishes a short-range communication connection with the first electronic device according to the filtered message of the first electronic device.

[0037] In one implementation, the method further includes: the second terminal detecting a third operation acting on the icon of the first electronic device, and in response to the third operation, the second terminal cooperating with the first electronic device to execute the first distributed service.

[0038] In one implementation, a first group is created with a first account, family members of the first group include a second account, and a first operation is used to add the first electronic device as an electronic device of the first group.

[0039] In one implementation, a first group is created with the first account, the electronic devices of the first group include the first electronic device, and the first operation is used to add the second account as a family member of the first group.

[0040] In one implementation, the second terminal cooperates with the first electronic device to execute the first distributed service, including: the second terminal and the first electronic device transmit service data of the first distributed service through a short-range communication connection.

[0041] In one implementation, the second terminal cooperates with the first electronic device to execute the first distributed service, including: the second terminal sends screen projection data to the first electronic device through a short-range communication connection, and the screen projection data is used by the first electronic device to display the projection screen; or, the second terminal sends application data to the first electronic device through a short-range communication connection; the application data is used by the first electronic device to display the desktop application of the second terminal; or, the second terminal sends audio data to the first electronic device through a short-range communication connection; the audio data is used by the first electronic device to play audio.

[0042] In one implementation, the second terminal cooperates with the first electronic device to execute the first distributed service, including: the second terminal receives a first request sent by the first electronic device through a short-range communication connection; the first request is used to request the second terminal to assist in inputting information; the second terminal displays a second input box; the second terminal obtains the first information input by the user in the second input box; the second terminal sends the first information to the first electronic device through a short-range communication connection; the first information is used by the first electronic device to display in the first input box.

[0043] In a fourth aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory, wherein the memory is coupled to the processor, the memory is used to store computer program code, and the computer program code includes computer instructions. When the processor reads the computer instructions from the memory, the electronic device executes the multi-device collaboration method described in the second aspect.

[0044] In the fifth aspect, an embodiment of the present application provides an electronic device, wherein a server includes: a processor and a memory, wherein the memory is coupled to the processor, and the memory is used to store computer program code, wherein the computer program code includes computer instructions. When the processor reads the computer instructions from the memory, the electronic device executes the multi-device collaboration method described in the third aspect.

[0045] In a sixth aspect, an embodiment of the present application provides a computer storage medium comprising computer instructions, which, when executed on an electronic device, enables the electronic device to execute a multi-device collaboration method in any possible implementation of any of the above aspects.

[0046] In a seventh aspect, an embodiment of the present application provides a computer program product, which, when running on a computer, enables the computer to execute the multi-device collaboration method in any possible implementation of any of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figures 1 and 2 are schematic diagrams of the system architecture of a communication system provided in an embodiment of the present application;

[0048] 3A to 3L are schematic diagrams of user interfaces of a shared device provided in an embodiment of the present application;

[0049] 4A to 4G are schematic diagrams of user interfaces of a shared device provided in an embodiment of the present application;

[0050] 5A to 5H are schematic diagrams of user interfaces of a shared device provided in an embodiment of the present application;

[0051] 6A to 6G are schematic diagrams of user interfaces of a shared device provided in an embodiment of the present application;

[0052] 7A to 7C are schematic diagrams of user interfaces of a shared device provided in an embodiment of the present application;

[0053] 8A to 8D are schematic diagrams of user interfaces of a shared device provided in an embodiment of the present application;

[0054] 9A to 9C are schematic diagrams of user interfaces of a shared device provided in an embodiment of the present application;

[0055] 10A to 10F are schematic diagrams of user interfaces of a shared device provided in an embodiment of the present application;

[0056] FIG11 is a schematic diagram of the system architecture of the software system provided in an embodiment of the present application;

[0057] FIG12 is a schematic diagram of the system architecture of a multi-device collaborative system provided in an embodiment of the present application;

[0058] FIG13 is a schematic diagram of a method flow chart provided in an embodiment of the present application;

[0059] 14A to 14F are schematic diagrams of user interfaces of a hyperterminal provided in an embodiment of the present application;

[0060] 15A to 15C are schematic diagrams of a user interface of a super desktop provided in an embodiment of the present application;

[0061] FIG16 is a schematic diagram of a user interface for audio projection provided in an embodiment of the present application;

[0062] 17A to 17C are schematic diagrams of user interfaces for screen projection provided in an embodiment of the present application;

[0063] 18A and 18B are schematic diagrams of a user interface for a move provided in an embodiment of the present application;

[0064] 19A to 19C are schematic diagrams of user interfaces for auxiliary input provided in an embodiment of the present application;

[0065] FIG20 is a schematic diagram of the device structure of a terminal device provided in an embodiment of the present application;

[0066] Figure 21 is a schematic diagram of the device structure of the server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0067] The following is a clear and detailed description of the technical solutions in the embodiments of the present application in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in the text is only a description of the association relationship between related objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0068] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to imply or suggest relative importance or implicitly indicate the number of the technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of this application, unless otherwise specified, "plurality" means two or more.

[0069] The term "user interface (UI)" in the following embodiments of this application refers to a medium interface for interaction and information exchange between an application or operating system and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. The user interface is a source code written in a specific computer language such as Java and extensible markup language (XML). The interface source code is parsed and rendered on an electronic device and finally presented as content that the user can recognize. The commonly used form of user interface is graphical user interface (GUI), which refers to a user interface related to computer operations that is displayed in a graphical manner. It can be a visual interface element such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. displayed on the display screen of an electronic device.

[0070] The following introduces the communication system 10 involved in the multi-device collaboration method provided in an embodiment of the present application.

[0071] Figures 1 and 2 exemplarily illustrate the system architecture of a communication system 10 provided in an embodiment of the present application. As shown in Figures 1 and 2 , the communication system 10 includes a terminal device 100 for logging into account 1, a terminal device 200 for logging into account 2, a device bound to account 1, and a server 400 for application 1.

[0072] Terminal devices 100 and 200 can communicate with server 400 via a communication network to register and log in to an account for application 1. Users can view, manage, and control devices bound to account 1 through application 1 on terminal device 100, and users can view, manage, and control devices bound to account 2 through application 1 on terminal device 200.

[0073] In some embodiments, the devices bound to account 1 may include network-connected devices bound to account 1. Network-connected devices can be connected to the Internet and have social network attributes. Such devices can be understood as Internet of Things (IoT) devices. The terminal device 100 can control the network-connected IoT devices through the server 400. The terminal device 100 can control the IoT devices bound to account 1 of application 1 through the server 400. For example, the above-mentioned IoT devices include smart screens, car-mounted devices, routers, air conditioners, televisions, projectors, smart speakers, smart door locks, smart lights, smart windows, smart curtains, smart body fat scales, treadmills, smart rice cookers, smart electric kettles, etc.

[0074] In some embodiments, the device bound to account 1 includes the terminal device used to log in to account 1, such as a mobile phone, tablet, smart screen, etc. The terminal device 100 can obtain other terminal devices that log in to the same account through the server 400.

[0075] In some embodiments, the device bound to account 1 includes a wireless device that can be directly connected to the terminal device 100 through short-range communication technology, such as a Bluetooth headset, a wearable device, etc., and the wireless device cannot connect to the Internet.

[0076] In the communication system shown in FIG1 , the terminal device 100 has a trust relationship with the terminal device logged in with the same account. When they are close to each other, they can establish a connection and complete authentication to complete the self-organizing network, thereby collaboratively realizing close-range distributed services (for example, super terminal, super desktop, screen projection, etc.), and transmitting service data through the above-mentioned close-range communication connection. The close-range communication technology involved in this application can be wireless fidelity (WiFi), ultra wide band (UWB), Bluetooth, near field communication (NFC), ZigBee and other close-range communication technologies. The embodiments of this application do not specifically limit the close-range communication technology 1.

[0077] In this embodiment of the present application, devices bound to account 1 (e.g., shared device 1) can be shared with account 2 via terminal device 100. In one implementation, after terminal device 100 adds account 2 to a family group created by account 1, the devices bound to account 1 added to the family group are automatically shared with terminal device 200. Sharing is not limited to family groups; terminal device 100 can also share designated devices bound to account 1 with account 2 in a point-to-point manner.

[0078] In some embodiments, after the terminal device 100 shares the shared device 1 (e.g., an IoT device) bound to account 1 with account 2, the terminal device 200 logged into account 2 can control the shared device 1 through the server 400. However, even if the shared device 1 is shared with the terminal device 200, since the terminal device 200 and the shared device 1 bound to account 1 do not have a trust relationship, the shared device 1 and the terminal device 200 cannot automatically perform distributed services in close proximity.

[0079] The communication system shown in Figure 2 also includes a server 300. In some embodiments, when a device bound to account 1 (e.g., shared device 1) is shared with account 2 through terminal device 100, terminal device 100 can trigger shared device 1 and terminal device 200 logged in to account 2 to perform related operations of credit authorization through server 300, so that credit is authorized between shared device 1 and terminal device 200, that is, a trust relationship exists; after credit authorization, shared device 1 and terminal device 200 can form a self-organizing network when they are close to each other, so that they can collaboratively realize distributed services in close proximity. In some embodiments, server 300 and server 400 are the same server, that is, the application server of application 1. In some embodiments, server 300 and server 400 are not the same server, and are not the application server of application 1.

[0080] In the embodiment of the present application, the above-mentioned application 1 can be a third-party application (such as a smart life application) or a system application (such as a system setting). This application does not specifically limit application 1. The account of application 1 can be an account of an account system unique to application 1 (such as a Huawei account), a mobile phone number (such as a mobile phone number), an email account, an account of a social application, or an account of other specified applications. In some embodiments, the account of application 1 can be bound to accounts of other account systems. For example, if the account of application 1 is a Huawei account, it can also be bound to accounts such as a mobile phone number, an email account, and a social application account. In some embodiments, sharing a device bound to account 1 (such as a shared device 1) with a bound account of account 2 (such as a mobile phone number) is equivalent to sharing a device bound to account 1 with account 2.

[0081] The communication network may include local area networks (LANs) and / or wide area networks (WANs). The communication network may be implemented using any known network communication protocol, which may be various wired or wireless communication protocols, such as Ethernet, universal serial bus (USB), FireWire, global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), Bluetooth, wireless fidelity (Wi-Fi), NFC, voice over Internet protocol (VoIP), a communication protocol supporting a network slicing architecture, or any other suitable communication protocol.

[0082] The terminal devices 100 and 200 may be mobile phones, tablet computers, desktop computers, laptop computers, handheld computers, notebook computers, ultra-mobile personal computers (UMPCs), netbooks, and may also be cellular phones, personal digital assistants (PDAs), augmented reality (AR) devices, virtual reality (VR) devices, artificial intelligence (AI) devices, wearable devices (such as smart bracelets), in-vehicle devices, smart home devices (such as smart TVs, smart screens, large-screen devices, etc.), and / or smart city devices. The embodiments of the present application do not impose any special restrictions on the specific types of the above-mentioned terminal devices.

[0083] The server 300 and the server 400 may be a single server, a server cluster consisting of multiple servers, or a cloud computing center. The server 300 involved in the embodiment of the present application may also be referred to as a cloud server, a cloud, or a cloud side.

[0084] It should be understood that Figures 1 and 2 are merely schematic diagrams of the system structure of the communication system provided in the embodiment of the present application, and do not constitute a specific limitation on the communication system 10. The communication system 10 may include more or fewer devices than shown in the figure. For example, it may also include wireless relay equipment and wireless backhaul equipment (not shown in Figure 1), which are not limited here.

[0085] The following uses Application 1 as an example of a smart life application to illustrate the interface implementation of Account 1 sharing home devices with Account 2.

[0086] In some embodiments, after user 1 (for example, Mrak) registers and logs in to account 1 of the smart life application through the terminal device 100, the smart life application generates a family group 1 (for example, "Mrak's Home"). Then, user 1 can add home devices and family members to family group 1 through the terminal device 100. Account 1 is the creator of family group 1 and the owner of home devices in family group 1. The family creator can manage the home devices added to the family group (for example, delete, classify, control, etc.), and can also manage the family members added to the family group (for example, delete, set permissions, etc.). In the embodiments of the present application, the smart life application may also be referred to as other names, such as smart home application, smart home application, which is not specifically limited here.

[0087] For example, FIG3A and FIG3B show a user interface related to starting a smart life application.

[0088] 3A shows a main interface 11 on a terminal device 100 for displaying applications installed on the terminal device 100. The main interface 11 may include: a status bar, a calendar indicator, a weather indicator, a tray with common application icons, and other application icons, such as application icons 101 for smart life applications.

[0089] As shown in Figures 3A and 3B , in response to a user clicking on application icon 101, terminal device 100 launches the smart life application and displays the smart life application homepage 12. As shown in Figure 3A , homepage 12 includes a page navigation bar 102, a home group option 103, a display navigation bar 104, a device display area 105, and an add control 106.

[0090] The page navigation bar 102 includes the following page options: Home 102A, Mall, Smart, and My 102B. The terminal device 100 currently displays the home page indicated by Home 102A. By clicking other page options in the page navigation bar 102 (such as My 102B), the home page can be switched to the page indicated by the other page option, for example, the user center interface of the smart life application indicated by My 102B.

[0091] The home group option 103 displays the name of the home group, for example, the name of the home group 1 is "Mark's Home".

[0092] Display navigation bar 104 includes the following display options: Devices 104A, Spaces 104B, and My Home 104C. The currently selected display option in display navigation bar 104 (e.g., Devices 104A) indicates how home devices are displayed in device display area 105. Devices 104A indicates the display of home devices in the home group indicated by Home Group option 103; Spaces 104B indicates the display of home devices in the home group indicated by Home Group option 103, categorizing them by the space to which they belong; and My Home 104C indicates all home devices added by the currently logged-in account 1.

[0093] As shown in Figure 3B, the device information of the home device displayed in the device display area 105 may include the device icon, device name, network connection status (such as "online", "offline", etc.), classification information of the space / room to which it belongs (such as "living room", "master bedroom") and connection method (such as Bluetooth).

[0094] A family group can be understood as a virtual device space. Users can add home devices bound to account 1 to the device space, and can also add family members who share these home devices. Family members are accounts in the same account system. This application does not specifically limit the device types of home devices. Family groups, home devices, and family members are only exemplary conceptual names and may also be called other names, which should not constitute a limitation on this application; for example, family groups, home devices, and family members may also be called shared groups, shared devices, and shared members, respectively. Home devices can be devices in various application places such as residences, offices, and schools. The embodiments of this application do not specifically limit the application scenarios of home devices.

[0095] The following interface examples 1 to 5 provide several interface examples for device sharing in smart life applications.

[0096] Interface Example 1: After adding user 2 (ie account 2) to family group 1, the devices of family group 1 are automatically shared with user 2.

[0097] For example, FIG3B to FIG3I show the relevant user interfaces of the terminal device 100 for adding user 2 to the family group 1. FIG3B is a block diagram of FIG3I .

[0098] Exemplarily, as shown in FIG3B and FIG3C , in response to the user clicking on the family group option 103, the terminal device 100 displays a menu box 111. The menu box 111 displays options of family groups joined by account 1, including family group 1 created by account 1, such as option 112 of "Mark's Home" and option 113 of "Office", and may also include family groups created by other accounts joined by account 1, such as option 114 of "Laboratory". Option 114 may also be displayed with a sharing mark 115 to indicate that the family group is a family group created by other accounts, and this device can share the family devices in the family group. Option 112 of "Mark's Home" is currently selected, and options of other family groups are currently unselected. By clicking on options of other family groups, the selected family group can be switched; the aforementioned family group option 103 is the currently selected family group.

[0099] The menu box 111 further displays a family management control 116 and a create new family control 117. The family management control 116 is used to manage the currently selected family group; the create new family control 117 is used to trigger the creation of a new family group.

[0100] As shown in Figures 3C and 3D , in response to the user clicking on the home management control 116, the terminal device 100 displays the home management interface 13. This interface 13 includes entries for the home groups to which account 1 has joined, displaying the number of home devices in the home group and the data of the family members; for example, entries 121 for "Mark's Home," 122 for "Office," and 123 for "Laboratory," as well as a create new home control 124 and a home auto-switching switch 125.

[0101] Create a new home 124 is used to trigger the creation of a new home group. The switch control 125 for automatic home switching includes an on state (ON) and an off state (OFF); each home group can be set to a geographic location. When the switch control 125 includes the on state, the terminal device 100 can switch the home group displayed on the homepage (i.e., the home group indicated by the home group option 103) according to the current geographic location, for example, switching to the home group closest to the current geographic location.

[0102] As shown in Figures 3D and 3E, taking the entry 121 of "Mark's Home" as an example, in response to the user clicking on the entry 121, the terminal device 100 displays the family details interface 14 of "Mark's Home". The family details interface 14 includes a family name 131, a family address 132, room and device management 133, and a family member box 134. Through the family details interface 14, you can edit the name and address of the family group, and the rooms to which each device in the family group belongs. The family member box 134 may include identification information of each family member (such as an avatar and user name, which will be explained later using the avatar as an example), including the avatar of the creator of the family group, that is, the avatar 135 of account 1, and the avatars of other accounts invited to join the family group, such as luna's account avatar.

[0103] As shown in Figures 3E and 3F, the family member box 134 also includes an add member control 137. In response to the user clicking the add member control 137, the terminal device 100 may display a shared member selection interface 15. This selection interface 15 provides various selection options, such as an option 141 for scanning a QR code to share, an option 142 for selecting family members using a Huawei account, an option 143 for selecting family members using social app 1, and an account list 144.

[0104] As shown in Figures 3F and 3G, in response to the user clicking option 142, the terminal device 100 can display the user interface 17 for adding a Huawei account, and the user interface 17 includes a search box 161 and a confirmation control 162; as shown in Figures 3H and 3I, after the user enters the Huawei account of the target user (for example, Emma) in the search box 161, in response to the user clicking the confirmation control 162, the terminal device 100 displays the selection control 146 for Emma's Huawei account in the home management interface 13.

[0105] Option 141 for scanning to share triggers the terminal device 100 to display a code scanning interface. After scanning the QR code of another account (e.g., Account 2) in a smart life app through the code scanning interface, the terminal device 100 will display that account as a selectable family member on selection interface 15. Option 143 triggers the terminal device 100 to display a contact selection interface for social application 1, where contacts in social application 1 are bound to accounts in smart life apps. This interface allows one or more contacts in social application 1 to be selected and displayed in selection interface 15. The Huawei accounts bound to smart life apps for these contacts are selected as selectable accounts.

[0106] Device list 144 may include one or more selectable account selection controls, such as Henry's account selection control 146. When a user clicks a selection control (e.g., selection control 145 and selection control 146), the selection control may be switched from an unselected state to a selected state, i.e., the account corresponding to the selection control may be selected.

[0107] As shown in FIG3F , the family member selection interface 15 further includes a select all control 147 and a share control 148. The select all control 147 is used to select all selectable accounts in the selection interface 15. The user can select one or more accounts in the selection interface 15 to invite them to join the family group 1 (e.g., “Mark’s Home”). As shown in FIG3I and FIG3J , after the user selects Emma’s account and Henry’s account, in response to the user clicking the share control 148, the terminal device 100 sends an invitation request to Emma’s device and Henry’s device to invite them to join “Mark’s Home”, and displays Emma’s avatar 138 and Henry’s avatar in the family member box 134 of the selection interface 14, and displays prompt information around the avatar (e.g., prompt information 139 around the avatar 138) to indicate that the user is waiting for the invitation to be accepted.

[0108] 3K , after Emma accepts the invitation, the terminal device 100 determines that Emma's account has been added as a family member of "Mark's Home" and stops displaying the above prompt message 149. After Henyr rejects the invitation, the terminal device 100 stops displaying Henry's avatar in the family member box 134.

[0109] The terminal device 100 can delete family members added to "Mark's Home." For example, as shown in Figures 3K and 3L , in response to a user clicking Emma's profile picture 138, the terminal device 100 displays Emma's member details interface 16, which includes Emma's user name 152 and Huawei ID 151, as well as a remove member control 153. In response to the user clicking remove member control 153, the terminal device 100 removes Emma's account from "Mark's Home."

[0110] In some embodiments, when adding user 2 to family group 1 (for example, adding Emma to "MarK's Home"), the permissions of user 2 can also be set, such as setting that user 2 can share some or all home devices in family group 1, and setting the operations that user 2 can perform on the sharable home devices in family group 1. For example, user permissions are divided into multiple levels, and the higher the permission level, the more operations that can be performed. Exemplarily, level 1 user permissions may include adding / deleting family members, adding / deleting home devices, setting permissions for family members, editing basic information of the family group (such as name, location, room classification of each device), controlling the use of home devices, etc.; level 2 user permissions include some operations in level 1 user permissions, for example, level 2 user permissions can only control the use of home devices; level 3 user permissions include the ability to control the use of home devices only when family members are close to the location of the family group.

[0111] In an embodiment of the present application, when user 1 (i.e., account 1) invites user 2 (i.e., account 2) to join family group 1, the home device 1 in family group 1 is shared with user 2, that is, the terminal device 100 grants credit to the terminal device 200 and home device 1 of account 2; after the credit is granted, when the terminal device 200 is close to the home device 1, the terminal device 200 and the home device 1 can establish a short-range communication connection and automatically form a network, so that the two devices can collaborate to realize close-range distributed services 1 (such as super terminals, screen projection, etc.). Home device 1 can be referred to as a shared device shared by account 1 to account 2. Optionally, home device 1 is any device in family group 1. Optionally, home device 1 is a home device in family group 1 that supports close-range distributed services 1.

[0112] In some embodiments of the present application, when account 1 invites account 2 to join family group 1 created by account 1, the family devices in family group 1 are shared with account 1; at the same time, as account 2 joins family group 1, the devices bound to account 2 (for example, the devices in family group 2 created by account 2) are also automatically added to family group 1, that is, shared with account 1 or all family members in family group 1.

[0113] For example, FIG. 4A to FIG. 4F show relevant user interfaces of the terminal device 200 accepting an invitation.

[0114] As shown in FIG4A , the smart life application of terminal device 200 logs in to the account of user 1 (e.g., Emma). After receiving the invitation request sent by terminal device 100, the smart life application of terminal device 200 displays a prompt box 201 on home page 21. Prompt box 201 includes prompt information 202, a rejection control 203, and an accept and view control 204. Prompt information 202 is used to prompt Mark to invite him to join "Mark's Home", and the rejection control 203 is used to reject the invitation request. As shown in FIG4A and FIG4B , in response to the user clicking the accept and view control 204, terminal device 200 sends a confirmation message to the smart life application of terminal device 100 to indicate acceptance of the invitation request, obtains the home devices of "Mark's Home" from cloud-side server 400, displays the home group name of "Mark's Home" in the home group option 205 on home page 21, and displays the home devices of "Mark's Home" in the device display area 206.

[0115] In some embodiments, after Emma confirms joining "Mark's Home," the terminal device 200 also displays a prompt on the homepage 21, prompting the user that the terminal device 200 can collaborate with the home devices in "Mark's Home" to perform distributed services, such as HyperTerminal, HyperDesktop, screen projection, audio projection, and auxiliary input. For example, taking the HyperTerminal service as an example, as shown in FIG4C , the terminal device 200 displays a prompt 207 , which indicates that the terminal device can use the devices in "Mark's Home" in the HyperTerminal service. As shown in FIG4C and FIG4D , in response to the user clicking on the prompt 207 , the terminal device 200 may display a HyperTerminal interface 22 . The terminal device 200 may detect nearby home devices in "Mark's Home," such as a car device, and display an icon 211 of the car device, the user name 212 of the account 1 to which it belongs, and a sharing indicator 213 on the HyperTerminal interface 22 . The user name 212 indicates the user name of the account to which the car device belongs, and the sharing indicator 213 indicates that the car device is a shared device shared by other users. Specifically, the distributed services of the hyperterminal will be described in more detail in subsequent embodiments and will not be described in detail here.

[0116] As shown in Figures 4B and 4D, in response to the user clicking on the family group option 205, the terminal device 100 may display a menu box 208. The menu box 208 displays options for family groups joined by the account 2 logged in by the terminal device 200, including options for family groups created by the account 2, such as "Emma's Home." It may also include an option 209 for family groups created by other accounts joined by the account 1, such as "Mark's Home." The sharing mark 210 displayed on this option indicates that "Mark's Home" is a family group created and shared by other accounts.

[0117] Menu box 208 also displays a home management control 211. As shown in Figures 4D and 4E , in response to a user clicking on home management control 211, terminal device 200 displays a home management interface 23 for "Mark's Home." For details about home management interface 23, refer to the description of home management interface 13 on terminal device 100 . As shown in Figures 4E and 4F , home management interface 23 includes an entry 221 for "Mark's Home." In response to a user clicking on entry 221, terminal device 200 displays a home details interface 24 for "Mark's Home." For details about home details interface 24, refer to the description of home details interface 14 on terminal device 100 .

[0118] After Account 2 joins "Mark's Home," it can also choose to exit "Mark's Home." As shown in Figures 4F and 4G, Home Details Interface 24 includes an Exit Home control 231. In response to the user clicking Exit Home control 231, Terminal Device 100 removes Account 2 from "Mark's Home" and returns to Home Management Interface 23, which stops displaying "Mark's Home" entry 221.

[0119] As can be seen from Figures 4A to 4F, after account 2 joins "Mark's Home" created by account 1, user 2 (i.e., account 2) can also view the home devices in "Mark's Home" on the home page of the smart life application through terminal device 200, as well as view the home details interface of "Mark's Home".

[0120] In some embodiments, the user can use the terminal device 200 to add the device bound to account 2 to the family group 1 (for example, "Mark's Home") created by account 1, that is, share the device bound to account 2 with family members in family group 1.

[0121] Interface Example 2: After adding a device to Family Group 1, the device is automatically shared with family members in Family Group 1, such as User 2.

[0122] For example, FIG5A to FIG5F show the relevant user interfaces of the terminal device for adding a device to the home group 1. FIG5A is a block diagram of FIG5F showing the ...

[0123] As shown in FIG5A and FIG5B , in response to the user clicking the add control 106 , the terminal device 100 displays a menu box 301 , which includes functional controls such as adding a device 302 , sharing a device, creating a scene, and connecting to a third-party platform.

[0124] As shown in Figures 5B and 5C , in response to the user clicking "Add Device" 302, the terminal device 100 scans for nearby devices and displays a user interface 31. User interface 31 includes a prompt 303, a manual add control 304, and a scan add control 305. Prompt 303 indicates that the device is being scanned for nearby devices; manual add control 304 triggers adding the device through manual input; and scan add control 305 triggers adding the device by scanning its QR code.

[0125] As shown in FIG5D , after a device (e.g., an in-vehicle device) is scanned, an icon 308 of the in-vehicle device and an add control 306 are displayed. As shown in FIG5D and FIG5E , in response to the user clicking the add control 306, the terminal device 100 adds the in-vehicle device to the home group displayed on the home page 12, i.e., “Mark’s Home,” and switches the text “Add” displayed in the add control 306 to “Added.”

[0126] As shown in Figures 5E and 5F , in response to a user clicking on the in-vehicle device icon 308, the terminal device 100 displays a device settings interface 33. The device settings interface 33 is used to set the name of the added device, the room it belongs to, and other information. As shown in Figures 5F and 5G , the device settings interface 33 also includes a next control 307. In response to the user clicking on the next control 307, the terminal device 100 displays a sharing settings interface 34. The sharing settings interface 34 includes a family member box 311, a separate sharing control 313, and a guest mode 314. The family member box 311 can refer to the relevant description of the family member box 134 described above; the family member box 311 includes an add control 312; as shown in Figures 5G and 5H , in response to the user clicking on the add control 312, the terminal device 100 can display a family member selection interface 15. In this way, when adding a device to family group 1, family members can also be added. The separate sharing control 313 is used to trigger the sharing of the device with a specified user.

[0127] Interface Example 3: The application homepage displays a notification message to recommend user 2 (account 2), and selects family group 1 to add user 2.

[0128] In some embodiments, the user center of the Huawei account is also provided with a family sharing group, to which one or more family members can be added. Users in a family sharing group are usually close, and information, payments, photos, contacts, and other content can be synchronized and shared among family members. An entrance to the user center of the Huawei account is provided in the "System Settings" of the terminal device 100, through which you can enter the user center interface 35 of the Huawei account shown in Figure 6A. The user center interface 35 includes an entry 321 for family sharing; as shown in Figures 6A and 6B, in response to the user clicking on the entry 321, the terminal device 100 can display the family sharing interface 36. The family sharing interface 36 displays the members of the family sharing group.

[0129] In some embodiments, as shown in FIG6C , when the smart life application detects that a family member in the family sharing group has not joined Family Group 1 in the smart life application, a message box 321 may be displayed on homepage 12 . Message box 321 recommends family members in the family sharing group to the user, prompting the user to add the family member in the family sharing group to "Mark's Home" to share the home devices in "Mark's Home." As shown in FIG6C and FIG6D , message box 321 includes a reject control 322 and an invite control 323 . The reject control 322 is used to reject the invitation. As shown in FIG6C and FIG6D , in response to the user clicking the invite control 323 , the terminal device 100 may display a selection box 324 as shown in FIG6B . The selection box 324 includes accounts in the family sharing group that have not joined "Family Group 1" and their corresponding selection controls, a reject control 325 , and an invite control 326 . The reject control 325 is used to refuse to select a family member from the selection box 324 . As shown in FIG6D and FIG6E, after the user selects Anna and Henry through the selection control, in response to the user clicking the invitation control 326, the terminal device 100 displays the family details interface 14, and displays the avatars of Anna and Henry who are to accept the invitation in the family member box.

[0130] In one implementation, if the user clicks the reject control 322 or the invite control 323 on the homepage 12 and then returns to the homepage, the terminal device 100 stops displaying the message box 321. As shown in Figures 6F and 6G, if the user switches the homepage displayed to another family group, such as "Office," the terminal device 100 may display a message box 327 for "Office" to recommend family members in the home sharing group for "Office." It will be appreciated that stopping the display of the message box 321 for "Mark's Home" does not affect the display of the message box 327 for "Office."

[0131] Interface Example 4: The notification center of the terminal device 100 displays a notification message to recommend user 2, and selects family group 1 to add user 2.

[0132] In some embodiments, as shown in FIG7A , when the smart life application detects that a family member in a home sharing group has not joined the smart life application's home group, it may push a message 331 to the notification center 37 of the terminal device 100. Message 331 recommends family members in the home sharing group to the user, prompting the user to add the family members in the home sharing group to the smart life application's home group to share the home devices in the home group. As shown in FIG7A and FIG7B , in response to the user clicking on message 331, the terminal device 100 may display a home management interface 38 , which includes options for each home group that account 1 has joined and a confirmation control 332 . As shown in FIG7B and FIG7C , after the user selects "Mark's Home," in response to the user clicking on the confirmation control 332 , the terminal device 100 may display a selection box 333 , which displays accounts from the home sharing group recommended by the smart life application, from which user 1 can select an account to join "Mark's Home." The description of selection box 333 is similar to the description of selection box 324 above and is not repeated here.

[0133] In some embodiments, in the aforementioned interface embodiments 3 and 4, only after the switch for recommending family members is turned on will the smart life application push a message on the homepage 12 or notification center 37 to recommend family members from the family sharing group. For example, as shown in Figures 8A and 8B, in response to a user clicking 102B, the terminal device 100 displays the user center interface 41 of the smart life application. As shown in Figures 8B and 8C, in response to a user clicking a settings item 341 in the user center interface 41, the terminal device 100 displays a settings interface 42. The settings interface 42 includes a switch 342 for recommending family members, which has two states: on and off. As shown in Figures 8C and 8D, in response to a user clicking switch 342, the terminal device 100 switches switch 342 from the off state to the on state.

[0134] Interface Example 5: Select a specific device that has been added to share with one or more designated users outside the family group.

[0135] For example, as shown in Figures 9A and 9B, the home page 12 displays a control card 401 for the "Smart Screen" of "Mark's Home"; in response to the user long pressing the card 401, the terminal device 100 displays a menu box 402, which includes a shared device control 403. As shown in Figures 9B and 9C, in response to the user clicking the shared device control 403, the terminal device 100 displays a selection interface 15 for shared members. After selecting one or more accounts through the selection interface 15, the above-mentioned "Smart Screen" is shared with the above-mentioned one or more accounts. The account selected here does not need to join the family group.

[0136] Taking application 1 as "system settings" as an example, the following interface embodiment 6 provides another interface embodiment for device sharing in "system settings".

[0137] Interface Example 6: Add home device 1 to the home details interface of the home sharing group of account 1 and share it with account 2.

[0138] For example, as shown in Figures 10A and 10B , in response to a user swiping up on the Family Sharing interface 36 of the Huawei account's Family Sharing group, the terminal device 100 displays more content of the Family Sharing interface 36, including some shared devices and a viewing control 501 for more shared devices. As shown in Figures 10B and 10C , in response to a user clicking on the viewing control 501, the terminal device 100 displays a shared device interface 51. The shared device interface 51 is used to display one or more of the following: shared devices that account 1 has shared with other users, devices that account 1 has received from other users, and sharable devices bound to account 1.

[0139] Exemplarily, as shown in FIG10C , the shared device interface 51 includes a navigation bar 502 and a device display area 503. The navigation bar 502 includes shared devices 504, shared devices 505, and sharable devices 506. When the shared device 504 is selected, the device display area 503 is used to display the shared devices that account 1 has shared with other users; when the shared device 505 is selected, the device display area 503 is used to display the shared devices shared by other users accepted by account 1; when the sharable device 506 is selected, the device display area 503 is used to display the sharable devices bound to account 1. As shown in FIG10C and FIG10D , when the shared device 504 is selected, the device display area 503 displays a card 507 for the vehicle-mounted device; in response to the user clicking on the card 507, the terminal device 100 displays the sharing details interface 52 for the vehicle-mounted device.

[0140] As shown in FIG10D , the sharing setting interface 52 includes a prompt message 504, a switch control 505 for sharing with all family members, a switch control 506 for sharing with specified family members, a delete control 507 for the shared receiving device, and an add member control 508. The prompt message 504 is used to prompt you to share your vehicle-mounted device with your family members, so that your family members can use distributed services (such as super desktop, super terminal) to interact with your vehicle-mounted device. Only one of the switch control 505 and the switch control 506 is in the on state, and the user can switch the switch control on and off; the delete control 507 is used to delete the added family member (i.e., Emma) who has received the shared vehicle-mounted device; the add member control 508 is used to add users who share the vehicle-mounted device.

[0141] As shown in Figures 10E and 10F, when the shared device 505 is selected, the device display area 503 displays a smart screen card 508; in response to the user clicking on the card 508, the terminal device 100 displays the smart screen sharing details interface 53. The sharing details interface 53 includes prompt information 509 and prompt information 510. Prompt information 509 is used to indicate the sharer of the smart screen, that is, Emma; prompt information 510 is used to prompt your family members to share the smart screen with you, and you can also use distributed services (such as super desktop and super terminal) to interact with the smart screen.

[0142] In some embodiments, application 1 is provided with a chat interface for a group (such as the aforementioned family group 1 / family sharing group), and each family member in the group can send the device bound to the family member through the chat interface to share the device with other family members in the group.

[0143] Not limited to the above-mentioned interface embodiments 1 to 6, the terminal device 100 can also share the device (such as shared device 1) bound to user 1 (ie account 1) to user 2 (ie account 1) through other interfaces, which is not specifically limited here.

[0144] In the embodiment of the present application, exemplary embodiments of the terminal device 100 include but are not limited to Hongmeng system (Harmony OS) or other operating systems of electronic devices. The following is an example of the operating system of the terminal device 100 being Hongmeng system. For example, Figure 11 is a schematic diagram of the software structure of the terminal device 100 of the embodiment of the present application. The software structure of other terminal devices involved in the embodiment of the present application can refer to the relevant description of Figure 11, which will not be repeated here.

[0145] In some embodiments, the HarmonyOS system can be divided into four layers, including the kernel layer, the system service layer, the framework layer, and the application layer, and the layers communicate with each other through software interfaces.

[0146] As shown in Figure 11, the kernel layer 240 is the layer between hardware and software. The kernel layer includes the kernel abstraction layer (KAL) and the driver subsystem. The KAL includes multiple kernels, such as the Linux kernel and LiteOS, a lightweight IoT kernel. The driver subsystem can include the Hardware Driver Foundation (HDF). The HDF provides unified peripheral access capabilities and a driver development and management framework. The multi-kernel kernel layer can select the appropriate kernel for processing based on system requirements.

[0147] The system service layer is the core capability set of the Hongmeng system. The system service layer provides services to applications through the framework layer. This layer may include:

[0148] System Basic Capability Subsystem Set: This provides the fundamental capabilities for running, scheduling, and migrating distributed applications across multiple devices within the Hongmeng OS. This includes subsystems such as a distributed soft bus, distributed data management, distributed task scheduling, the Ark multi-language runtime, public base libraries, multi-mode input, graphics, security, artificial intelligence (AI), and a user program framework.

[0149] Basic software service subsystem set: Provides public and general software services for the Hongmeng system. This includes event notification, phone, multimedia, Design For X (DFX), MSDP & DV, and other subsystems.

[0150] Enhanced software service subsystems: These provide HarmonyOS with differentiated, device-specific, and enhanced software services. These services may include specialized smart screen services, wearable technology services, and IoT (Internet of Things) services.

[0151] Hardware service subsystem set: Provides hardware services for the Hongmeng system. This may include location services, biometric recognition, wearable proprietary hardware services, IoT proprietary hardware services, and other subsystems.

[0152] The framework layer provides user program frameworks and capability frameworks in multiple languages, including Java, C, C++, and JS, for Hongmeng OS application development. It also provides two user interface (UI) frameworks (a Java UI framework for Java and a JS UI framework for JS), as well as a multi-language framework for application programming interfaces (APIs) for various software and hardware services. The APIs supported by Hongmeng OS devices will vary depending on the system's componentization.

[0153] The application layer includes system applications, extended applications, and third-party non-system applications. System applications may include applications installed by default on electronic devices, such as the desktop, control bar, and settings. Extended applications can be non-essential applications developed and designed by the manufacturer of the electronic device, such as smart home apps. Third-party non-system applications can be developed by other manufacturers but can run in the Hongmeng system. The specific implementation of the smart home app can refer to the relevant description of APP1 above.

[0154] The applications of the Hongmeng system are composed of one or more meta-programs (Feature Ability, FA) or meta-services (Particle Ability, PA). Among them, FA has a UI interface and provides the ability to interact with users. PA has no UI interface and provides the ability to run tasks in the background and a unified data access abstraction. PA mainly provides support for FA, such as providing computing power as a background service, or providing data access capabilities as a data warehouse. Applications developed based on FA or PA can implement specific business functions, support cross-device scheduling and distribution, and provide users with a consistent and efficient application experience.

[0155] Multiple electronic devices running the Harmony system can achieve hardware mutual assistance and resource sharing through distributed soft bus, distributed device virtualization, distributed data management and distributed task scheduling.

[0156] It can be understood that the system architecture shown in Figure 11 above does not constitute a limitation of the system architecture of HarmonyOS. In other embodiments, HarmonyOS200 may have more or fewer system architecture structures than the structure shown in Figure 11 above, or it may be other forms of system architecture, which is not limited here.

[0157] In combination with the foregoing embodiments, FIG12 shows a system architecture of a multi-device collaborative system provided in an embodiment of the present application.

[0158] As shown in FIG12 , the multi-device collaborative system includes a cloud-side server 300 and a terminal-side device, namely, a terminal device 100 , a terminal device 200 or a shared device 1 .

[0159] Server 300 includes a device cloud and a family service. The device cloud manages the list of devices bound to each account, and during the authorization phase, sends authorization information for the receiving device (e.g., the user identification (UID) of Account 2 of the receiving device) to the sharing device, and sends authorization information for the sharing device (e.g., the unique device identifier (UDID) of the sharing device and the UID of Account 1 (i.e., the account of the person sharing the device)) to the receiving device.

[0160] The device-side equipment includes cloud service support, distributed services, a distributed collaborative architecture, a free interconnection module, a protocol stack, and a short-range communication module. The device-side support includes an SNS kit and an authorization information management module. The SNS kit provides friend and group services based on a Huawei account. A single installation provides all the basic capabilities of Huawei Mobile Services, including friend messaging, system notification numbers, and family sharing services. The authorization information management module manages received authorization information.

[0161] Distributed services include super terminal, super desktop, screen projection, audio projection, auxiliary input, and gesture services. The embodiment of the present application can also provide more short-range distributed services, which are not specifically limited here.

[0162] The distributed collaborative architecture includes distributed controls, distributed scenario optimization APIs, service discovery and filtering, distributed business management, a collaborative configuration center, and cross-device collaborative services. The distributed collaborative architecture provides support for the implementation of distributed businesses.

[0163] The free interconnection module includes DM, Softbus, and Hichain. The distributed softbus is the communication foundation for distributed devices, providing unified distributed communication capabilities for interoperability. Based on the distributed softbus, it can automatically discover other devices in the surrounding area and connect them to form a network, which is called automatic networking. Hichain is a protocol mechanism for ensuring device interconnection security. It can authenticate two devices based on their authorization information, achieving end-to-end data encryption.

[0164] In combination with the above embodiments, the present application provides a multi-device collaboration method. For example, as shown in FIG13 , the method flow of the method may include part or all of steps S10 to S48 .

[0165] S10. The SNS Kit of the terminal device 100 detects the user's input operation 1; the terminal device 100 logs in to the account 1, and the input operation 1 is used to view the device display interface of the account 1, which is used to display the device list of the shareable devices of the account 1.

[0166] In an embodiment of the present application, a user logs in to account 1 through terminal device 100. User 1 performs input operation 1 to view the device display interface of account 1 on terminal device 100. The device display interface is used to display devices of account 1 that can be shared with other users.

[0167] In some embodiments, the detection module of the terminal device 100 detects the user's input operation 1, which is used to view the device display interface of account 1; the detection module sends an instruction to the SNS Kit, instructing the SNS Kit to obtain the device list of shareable devices displayed in the device display interface.

[0168] In some embodiments, the device display interface is used to display devices in Family Group 1 created by Account 1. For example, referring to the descriptions of Figures 3A to 3D , Family Group 1 is "Mark's Home" in the Smart Life app, and the device display interface is Home Page 12 of the Smart Life app. Home Page 12 displays the devices in "Mark's Home," which can be shared with family members added to "Mark's Home." For example, referring to the descriptions of Figures 10B to 10C , Account 1 is a Huawei account, Family Group 1 is a Family Sharing group for Huawei accounts in "System Settings," and the device display interface is Family Sharing interface 36 or Shared Devices interface 51 in "System Settings." Family Sharing interface 36 and Shared Devices interface 51 display the shareable family devices bound to Account 1.

[0169] In some embodiments, in response to the user's input operation 1, the SNS Kit of the terminal device 100 obtains a device list displayed on the device display interface. Specifically, steps S11 to S15 may be included.

[0170] S11 . The SNS Kit of the terminal device 100 sends a request 1 to the home service of the server 300 to request to query the device list 1 of the account 1 .

[0171] S12 , the home service request of the server 300 sends a request 1 to the device cloud of the server 300 to request to query the device list 1 of the account 1 .

[0172] In the embodiment of the present application, the device cloud of the server 300 is used to store and manage the devices bound to each account.

[0173] S13. The device cloud of the server 300 returns the device list 1 to the home service of the server 300.

[0174] S14 . The home service of the server 300 returns the device list 1 to the SNS Kit of the terminal device 100 .

[0175] S15 . The SNS Kit of the terminal device 100 filters the sharable devices in the device list 1 and generates a device list 2 .

[0176] In some embodiments, the SNS Kit of terminal device 100 filters out devices that support distributed service 1 (e.g., hyperterminal) from the device list as shared devices that can be shared with terminal device 200. In some embodiments, terminal device 100 only shares some of the devices bound to account 1 as shareable devices with other accounts. The SNS Kit of terminal device 100 filters out these shareable devices from device list 1 according to preset rules.

[0177] S16. The SNS Kit of the terminal device 100 triggers the terminal device 100 to display a device display interface. The device display interface displays the devices in the device list 2. User 1 can view the devices through the device display interface.

[0178] Step S15 is optional. The SNS Kit of the terminal device 100 does not need to filter the device list 1. The device display interface directly displays all devices in the device list 1.

[0179] In some embodiments, after viewing the aforementioned device display interface, the user selects some or all devices (e.g., shared device 1) from device list 2 displayed on the device display interface to share with account 2. Terminal device 100, through server 300, instructs shared device 1 and terminal device 200 to complete the credit authorization process. After the credit authorization process is complete, shared device 1 stores the authorization information for terminal device 200, and terminal device 200 stores the authorization information for shared device 1. Specifically, account 1 shares shared device 1 with account 2, and the credit authorization process is completed between shared device 1 and terminal device 200 logged in to account 2, which may include steps S20 to S29.

[0180] S20 . The SNS Kit of the terminal device 100 detects the user's input operation 2 , where the input operation 2 is used to select a shared device (eg, shared device 1 ) from the devices displayed on the device display interface for sharing.

[0181] In some embodiments, the detection module of the terminal device 100 detects the user's input operation 2, which is used to select a sharing device and a receiving device for sharing; the detection module sends an instruction to the SNS Kit, instructing the SNS Kit to determine the sharing device and the receiving device for sharing.

[0182] In some embodiments, after input operation 2 selects the sharing device and the receiving device for sharing, in response to input operation 2, the terminal device 100 instructs the sharing device 1 and the terminal device 200 to complete the credit authorization through the server 300. Specifically, steps S21 to S29 may be included.

[0183] In an embodiment of the present application, the terminal device 100 logged into account 1 shares the shared device 1 with the terminal device 200 logged into account 2. Account 1 is the owner and sharer of the shared device 1, and the terminal device 100 is the sharing device of the shared device 1; account 2 is the recipient of the shared device 1, and the terminal device 200 is the receiving device of the shared device 1.

[0184] S21. The SNS Kit of the terminal device 100 uploads the device sharing information 1 to the home service of the server 300. The device sharing information 1 includes the device identifier (UDID) of the shared device 1, the UID of the sharer of the shared device 1 (i.e., the account 1 of the terminal device 100), and the UID of the recipient of the shared device 1 (e.g., the account 2 logged in by the terminal device 200).

[0185] In some embodiments, account 1 shares shared device 1 with multiple accounts, and the recipients of shared device 1 include the aforementioned multiple accounts (e.g., account 2). The aforementioned device sharing information 1 includes a UID list of recipients, and the UID list includes the UIDs corresponding to the aforementioned multiple accounts. In one implementation, family group 1 created by account 1 of terminal device 100 includes multiple family members. When shared device 1 is added to family group 1, account 1 shares shared device 1 with some or all of the aforementioned multiple family members.

[0186] In some embodiments, account 1 shares multiple shared devices (e.g., shared device 1) with account 2. The device sharing information 1 includes a UDID list of the multiple shared devices, and the UDID list includes the UDIDs corresponding to the multiple shared devices. In one implementation, a family group 1 created by account 1 of the terminal device 100 includes multiple shareable family devices. When user 1 adds account 2 to family group 1, account 1 shares the multiple family devices with account 2.

[0187] S22. The home service of the server 300 sends device sharing information 2 for account 2 to the SNS kit of the terminal device 200. The device sharing information 2 includes the device identifier (UDID) of the shared device 1, the UID of the sharer of the shared device 1 (i.e., account 1 logged in by the terminal device 200), and the UID of the recipient of the shared device 1 (i.e., account 2 logged in by the terminal device 200).

[0188] The home service of server 300 obtains device sharing information 2 for account 2 based on device sharing information 1. Device sharing information 2 includes a list of UDIDs of one or more shared devices selected by the user, the UID of the sharer of shared device 1 (i.e., account 1 logged in by terminal device 200), and the UID of the recipient of shared device 1 (i.e., account 2).

[0189] S23. Based on the above device sharing information 2, the SNS kit of the terminal device 200 triggers the terminal device 200 to display a device sharing authorization box, where the device sharing authorization box is used to indicate whether to accept the shared device shared by the account 1.

[0190] S24 . After the user confirms to accept the shared device shared by account 1 , the SNS kit of the terminal device 200 detects the user's confirmation operation.

[0191] In response to the user's confirmation operation, the SNS kit of the terminal device 200 determines to complete the authorization with the sharing device 1 through the server 300. Specifically, the process may include steps S25 to S29.

[0192] S25 . The SNS kit of the terminal device 200 uploads user confirmation information to the home service of the server 300 . The user confirmation information is used to indicate that the account 2 confirms to accept the sharing of the account 1 .

[0193] In some embodiments, the user confirmation information includes a UDID list 2 of the shared devices (e.g., shared device 1) accepted by the user and the UID of the sharer of the shared device (i.e., account 1 logged in by the terminal device 200). The user confirmation information is used to indicate that user 2 confirms acceptance of the shared device indicated by the above UDID list 2 shared by account 1.

[0194] In some embodiments, the SNS kit of the terminal device 200 displays a device sharing authorization box for each shared device indicated by the UDID list; user 2 (i.e., account 2) confirms whether to accept sharing in the sharing authorization box for each shared device. For each shared device confirmed to be accepted (e.g., shared device 1), the SNS kit of the terminal device 200 uploads user confirmation information to the home service of the server 300. The user confirmation information is used to indicate that account 2 confirms acceptance of shared device 1 shared by account 1. The user confirmation information includes the UDID of shared device 1 and the UID of the sharer of shared device 1 (i.e., account 1).

[0195] In some embodiments, the home service of server 300 generates shared task 1 based on device sharing information 2. When the home service of server 300 transmits device sharing information 2 to the SNS kit of terminal device 200, it also transmits the task identifier of shared task 1. In step S25, user confirmation information includes the task identifier of shared task 1 and the UDID of shared device 1. The user confirmation information is used to indicate that user 2 confirms acceptance of shared device 1 in the shared task indicated by the task identifier.

[0196] In one implementation, for each recipient who accepts sharing in the recipient's UID list, the home service of the server 300 obtains the user confirmation information uploaded by the recipient.

[0197] S26. The home service of server 300 transmits authorization information 1 to the device cloud of server 300. The authorization information 1 includes, for each recipient who accepts sharing, a list of UDIDs of the accepted shared devices (e.g., shared device 1), the UID of the sharer of the shared device (i.e., account 1), and the UID of the recipient (i.e., account 2).

[0198] After the device cloud of server 300 obtains authorization information 1, it instructs shared device 1 to perform credit-related operations through steps S27 to S29, and instructs terminal device 200 to perform credit-related operations through steps S30 to S32. The embodiment of the present application does not specifically limit the execution order of steps S27 and S29.

[0199] S27. The device cloud of the server 300 transmits the recipient's authorization information 2 to the authorization information management module of the shared device 1. The recipient's authorization information 2 includes the UID of the account 2. The authorization information 2 indicates that the account 2 has accepted the shared device 1 shared by the account 1.

[0200] It can be understood that the sharing device 1 stores the authorization information 2 of all recipients (such as the account 2 of the terminal device 200 ) who receive the sharing device 1 .

[0201] S28. The authorization information management module of the shared device 1 sends a notification message to the soft bus to inform the recipient that the authorization information is changed, that is, the authorization information of the account 2 is newly added.

[0202] S29. The soft bus of the shared device 1 updates the ad hoc network filter based on the changed authorization information of the receiving device, including setting the filter 1 of the short-range communication module 1 according to the authorization information of the newly added account 2. The filter 1 is used to filter out messages from account 2 sent through the short-range communication module 1.

[0203] S30. The device cloud of the server 300 transmits the authorization information 3 of the shared device 1 to the authorization information management module of the terminal device 200. The authorization information 3 of the shared device 1 includes: the UDID of the shared device 1, and the UID of the account to which the shared device 1 belongs (ie, account 1).

[0204] In some embodiments, the authorization information 3 includes a list of UDIDs of multiple shared devices accepted by the account 2 , the multiple shared devices 1 mentioned above.

[0205] It can be understood that the terminal device 200 logged into account 2 stores the authorization information 2 of each shared device accepted by account 2, and the shared device 1 stores the authorization information 3 of the recipient who accepted the shared device, for subsequent self-organizing networking between the terminal device 200 and the shared device 1.

[0206] S31. The authorization information management of the terminal device 200 sends a notification message to the soft bus to notify the shared devices of changes in the authorization information transmission, including the addition of the authorization information of the shared device 1.

[0207] S32. The soft bus of the terminal device 200 updates the ad hoc network filter based on the changed authorization information of the shared device 1, including setting the filter 2 of the short-range communication module 1 according to the newly added authorization information of the shared device 1, and the filter 2 is used to filter out messages sent to the shared device 1 through the short-range communication module 1.

[0208] In the embodiment of the present application, after step S32, the shared device 1 and the terminal device 200 have completed the authorization; when the terminal device 200 is close to the shared device 1, the two devices can automatically connect and authenticate to form an ad hoc network. Specifically, steps S41 to S48 may be included.

[0209] S41 , when the terminal device 200 is close to the shared device 1 , the soft bus of the terminal device 200 initiates a self-organizing network based on the filter 2 .

[0210] S42 : Based on filter 1 and filter 2 , the soft bus of the terminal device 200 establishes a short-range communication connection with the soft bus of the shared device 1 .

[0211] In some embodiments, when the terminal device 200 starts the distributed service 1, the short-range communication module 1 is turned on to scan nearby devices; when the filter 2 of the short-range communication module 1 detects a message from the shared device 1, a short-range communication connection can be established with the shared device 1, and authentication can be completed based on the authorization information of both parties. In one implementation, when the terminal device 200 starts the distributed service 1, the short-range communication module 1 broadcasts a discovery signal (e.g., a beacon frame), and the discovery signal carries the UID of account 2; after the short-range communication module 1 of the shared device 1 scans the above-mentioned discovery signal, it determines that the discovery signal matches the filter 1, that is, the UID of account 2 set by the filter 1 is the same as the UID carried by the discovery signal, then it determines that the terminal device 200 is a trusted device, and sends a connection request to the terminal device 200, and the connection request includes the UDID of the shared device 1 and the UID of the sharer (i.e., account 1); after the short-range communication module 1 of the terminal device 200 receives the above-mentioned connection request, if it determines that the above-mentioned connection request signal matches the filter 2, that is, the UDID of the shared device 1 set by the filter 2 is the same as the UDID carried in the connection request, and the UID of the sharer's account set is the same as the UID carried in the connection request, then it determines that the shared device 1 is a trusted device, and sends a connection response to the terminal device 200; based on the above-mentioned connection response, the terminal device 200 and the short-range communication module 1 of the shared device 1 establish a connection.

[0212] In some embodiments, the shared device 1 can also actively start the distributed service 1; when the shared device 1 starts the distributed service 1, the short-range communication module 1 will be turned on to scan nearby devices; when the filter 1 of the short-range communication module 1 detects a message from account 2, a short-range communication connection can be established with the terminal device 200 logged in to account 2. In one implementation, when the shared device 1 starts the distributed service 1, the short-range communication module 1 broadcasts a discovery signal (such as a beacon frame), and the discovery signal carries the UDID of the shared device 1 and the UID of the sharer (i.e., account 1); if the short-range communication module 1 of the terminal device 200 scans the above discovery signal, it determines that the discovery signal matches the filter 2, that is, the UDID of the shared device 1 set by the filter 2 is the same as the UDID carried by the discovery signal, the UID of the sharer's account set is the same as the UID carried by the connection request, and the UID of the sharer's account set is the same as the UID carried by the connection request. If the UID carried by the detection signal is the same, the shared device 1 is determined to be a trusted device, and a connection request is sent to the shared device 1, and the connection request includes the UID of the account 2 of the terminal device 200; after the short-range communication module 1 of the shared device 1 receives the above connection request, if it is determined that the above connection request signal matches the filter 1, that is, the UID of the account 2 set by the filter 1 is the same as the UID carried by the connection request, the terminal device 200 is determined to be a trusted device, and a connection response is sent to the terminal device 200; based on the above connection response, the terminal device 200 and the short-range communication module 1 of the shared device 1 establish a connection.

[0213] S43 . The soft bus of the terminal device 200 sends an authentication notification 1 to the Hichain of the terminal device 200 to instruct initiation of device authentication with the shared device 1 .

[0214] S44 . The Hichain of the terminal device 200 obtains the authorization information of the shared device 1 from the authorization information management module of the terminal device 200 based on the authentication notification 1 .

[0215] S45 . The Hichain of the terminal device 200 sends an authentication notification 2 to the Hichain of the shared device 1 to instruct the initiation of device authentication with the terminal device 200 .

[0216] S46 . The Hichain of the shared device 1 obtains the authorization information of the account 1 from the authorization information management module of the shared device 1 based on the authentication notification 2 .

[0217] S47 . Based on the authorization information of the shared device 1 and the authorization information of the account 1 , the Hichain of the shared device 1 and the Hichain of the terminal device 200 are authenticated.

[0218] In some embodiments, the Hichain of the sharing device 1 and the Hichain of the terminal device 200 are authenticated to obtain a key pair, which is used to derive the encryption key for subsequent communication between the two devices, thereby achieving secure communication.

[0219] S48. After the authentication is completed, the Hichain of the terminal device 200 sends an authentication success message to the soft bus to indicate that the shared device 1 and the terminal device 200 have completed the authentication.

[0220] It should be noted that when multiple devices with the same account are close to each other, they will automatically connect and authenticate, that is, self-organizing networking; after success, devices with the same account can collaborate to realize distributed services. Two devices that are not with the same account cannot self-organize, and thus cannot collaborate to realize distributed services. In the embodiment of the present application, the terminal device 100 shares the shared device 1 bound to account 1 with account 2, instructs the shared device 1 and the terminal device 200 logged in to account 2 to obtain each other's authorization information and update the filter according to the other party's authorization information, so that the shared device 1 and the terminal device 200 have a credit relationship, that is, when the two devices are close, they can automatically establish a close connection and authentication, and complete automatic networking; thereby, the shared device 1 and the terminal device 200 that are not with the same account can also collaborate to realize distributed services.

[0221] In combination with the foregoing embodiments, the distributed services applied in the embodiments of the present application are exemplarily described below by taking the short-range communication technology 1 being Bluetooth as an example.

[0222] Distributed services: HyperTerminal

[0223] In some embodiments, a master device (e.g., terminal device 100) and devices bound to it (e.g., smart screens, in-vehicle devices, speakers, etc.) form a collection of electronic devices that can be considered a distributed, collaborative virtual hyperterminal. The master device can schedule other devices in the hyperterminal to collaborate on tasks, transfer tasks, and continue tasks.

[0224] Exemplarily, taking the shared device 1 as a vehicle-mounted device as an example, FIG. 14A to FIG. 14C show relevant user interfaces of the hyper terminal.

[0225] Referring to steps S41 to S48, after the terminal device 100 shares the vehicle-mounted device bound to account 1 with account 2, when the terminal device 200 logged in to account 2 is close to the above-mentioned vehicle-mounted device, it can establish a short-range communication connection with the vehicle-mounted device to complete the ad hoc network.

[0226] As shown in Figure 14A, when the terminal device 200 displays the main interface 62, it receives a swipe down operation performed by the user on the status bar; in response to the above swipe down operation, the terminal device 200 displays the control center interface 62 shown in Figure 14B. The control center interface 62 includes shortcut icons for multiple commonly used functions (such as WLAN icons, Bluetooth icons, NFC icons, etc.).

[0227] As shown in FIG14B , the control center interface 52 may also include a hyperterminal card, in which a control 606 is displayed. In some embodiments, as shown in FIG14B and FIG14C , in response to clicking the control 606, the terminal device 200 displays a hyperterminal interface 63. The hyperterminal interface 63 includes an icon 601 of the terminal device 200 and icons of detected trusted devices, such as a laptop icon 603 and an in-vehicle device icon 602. The embodiments of the present application do not specifically limit the method for opening the hyperterminal interface 63. The opening method shown in FIG14A to FIG14C is only an example.

[0228] In some embodiments, the trusted device is a device currently in a network with the terminal device 200, i.e., a device that has established a short-range communication connection and completed authentication with the terminal device 200. The trusted device can be a device with the same account as the terminal device 200 (e.g., the laptop), or a shared device that has established a trust relationship with the terminal device 200 (e.g., the in-vehicle device).

[0229] In an embodiment of the present application, after the terminal device 200 detects a trusted device, it queries the authorization information management module, which stores the device identifiers (e.g., UDIDs) of shared devices shared by other accounts. As shown in FIG14C , if the device identifiers of the shared devices stored in the authorization information management module include the device identifier of the vehicle-mounted device, the terminal device 200 determines that the vehicle-mounted device is a shared device and displays a sharing identifier 605 on or around the vehicle-mounted device icon 602 to indicate that the vehicle-mounted device is a shared device shared by other users. The authorization information management module also stores the account information (e.g., user name, avatar, account number, and family group to which the shared device belongs) of the account (i.e., account 1) to which the shared device (e.g., the vehicle-mounted device) belongs. Based on the account information of account 1 to which the vehicle-mounted device belongs, the account information of account 1 can be displayed on or around the vehicle-mounted device icon 603. For example, as shown in FIG14C , the user name 604 of account 1, i.e., "Mark," is displayed around the vehicle-mounted device icon 603 to indicate that the vehicle-mounted device is a device shared by user "Mark."

[0230] For example, as shown in Figures 14C and 14D, it is detected that the icon 602 of the vehicle-mounted device is dragged to the area where the icon 601 of the terminal device 200 is located. In one implementation, in response to the above-mentioned drag operation, the terminal device 200 sends the projection data (such as the display screen of the terminal device 200) to the vehicle-mounted device through the short-range communication connection; as shown in Figure 14E, the vehicle-mounted device displays the display screen of the terminal device 200 in the projection window based on the above-mentioned projection data. In one implementation, in response to the above-mentioned drag operation, the terminal device 200 sends the application data of the super desktop to the vehicle-mounted device through the above-mentioned short-range communication connection; as shown in Figure 14F, the vehicle-mounted device displays the application icons installed by the terminal device 200 in the display area 613 of the user interface 71 based on the above-mentioned application data. In this way, the vehicle-mounted device and the terminal device 200 that are not on the same account can also collaborate to implement distributed services based on proximity, and a single sharing operation can achieve a long-term and efficient experience of the super terminal between devices with different accounts.

[0231] It is understood that according to existing technology, account 1 is bound to the vehicle-mounted device, while terminal device 200 used to log in to account 2 is not bound to the vehicle-mounted device. Therefore, the vehicle-mounted device and terminal device 200 are not devices with the same account. When terminal device 200 is close to the vehicle-mounted device, the two devices cannot automatically establish a connection, and thus cannot collaborate to implement distributed services of the hyperterminal.

[0232] Distributed Services: Super Desktop

[0233] In some embodiments, the super desktop can be understood as: desktop applications of other devices (such as shared device 1) can be viewed and used on one device (such as terminal device 200), and the function of the super desktop is implemented on the device.

[0234] For example, as shown in Figures 14D and 14F, when the terminal device 200 is close to the vehicle-mounted device, the application of the terminal device 200 can be migrated to the vehicle-mounted device through the super terminal on the terminal device 200 to run, and the desktop application of the terminal device 200 can be viewed and used on the vehicle-mounted device.

[0235] Exemplarily, taking the shared device 1 as a vehicle-mounted device as an example, FIG. 15A to FIG. 15C show related user interfaces of another super desktop.

[0236] 15A , the user interface 71 of the vehicle-mounted device includes a navigation bar 611, and the navigation bar 611 includes a super desktop option 612. When the super desktop option 612 is selected, the display area 613 of the user interface 71 is used to display the super desktop.

[0237] In some embodiments, when the in-vehicle device detects an input operation that triggers a super desktop, it displays the user interface 71 shown in FIG15A , detects nearby trusted devices, and displays a device option 614 indicating that one or more trusted devices, such as the terminal device 200, has been detected in the display area 613 of the user interface 71. The user can select a device from the one or more trusted devices and view the super desktop of the device on the in-vehicle device.

[0238] As shown in Figures 15A and 15B, the vehicle-mounted device detects a user operation (e.g., a click) on the device option 614 of the terminal device 200. The vehicle-mounted device obtains the application data transmitted by the terminal device 200 via a short-range communication connection and displays the desktop application of the terminal device 200, i.e., the super desktop, in the display area 613 based on the application data. In this way, the vehicle-mounted device and the terminal device 200, which are not on the same account, can also achieve collaborative proximity-based distributed services. A single shared operation can achieve a long-term and efficient experience of the super desktop between devices with different accounts.

[0239] In some embodiments, when a user operation (e.g., a click) on the device option 614 of the terminal device 200 is detected, the vehicle-mounted device sends a request message to the terminal device 200; based on the request message, the terminal device 200 displays a confirmation box 621. The confirmation box 621 includes a prompt message 622, a cancel control 623, and an allow control 624. The prompt message 622 is used to prompt the user whether to allow the vehicle-mounted device to use the super desktop, the cancel control 623 is used to refuse the vehicle-mounted device from using the super desktop; the allow control 624 is used to allow the vehicle-mounted device to use the super desktop. In response to the user clicking the allow control 624, the terminal device 200 sends a confirmation message to the vehicle-mounted device; based on the confirmation message, the vehicle-mounted device displays the super desktop of the terminal device 200 in the display area 613.

[0240] Distributed business: audio projection

[0241] For example, taking the shared device 1 as a "speaker" as an example, FIG16 shows a user interface related to sound projection.

[0242] Referring to steps S41 to S48, after the terminal device 100 shares the speaker bound to account 1 with account 2, when the terminal device 200 logged in to account 2 is close to the above-mentioned speaker, it can establish a short-range communication connection with the speaker to complete the self-organizing network.

[0243] In some embodiments, the "System Settings" of the terminal device 200 is provided with a projection control entrance, through which the terminal device 200 detects nearby trusted devices and displays the projection control interface 81 shown in Figure 16. The projection control interface 81 includes a broadcast control center component 631, as well as icons and selection controls for detecting one or more trusted devices, such as an icon 632 and a selection control 633 for a "speaker". The broadcast control center component 631 is used to control the audio being played. The user can select a device from the one or more trusted devices mentioned above and project the audio played by the broadcast control center component 631 to the device for playback.

[0244] Similar to the relevant description of the aforementioned super terminal, after the terminal device 200 detects a trusted device, it queries the authorization information management module whether the device is a shared device; the query shows that the "speaker" is a shared device shared by other users, and the terminal device 200 displays a sharing logo 634 on / around the "speaker" icon 632 to indicate that the "speaker" is a shared device shared by other users; it can also display the account information of the account to which the "speaker" belongs, such as the user name 635, to indicate that the user sharing the "speaker" is Mark.

[0245] As shown in Figure 16, the terminal device 200 detects the user's operation (e.g., click) on the selection control 633 of the "speaker", and the terminal device 200 sends the audio data played by the broadcast control center component 631 to the "speaker" through a short-range communication connection; the speaker plays the audio based on the received audio data. In this way, speakers and terminal devices 200 that are not on the same account can also collaborate to implement distributed services based on proximity. A single shared operation can achieve a long-term and efficient audio experience between devices with different accounts, effectively improving the user experience.

[0246] Distributed services: screen projection

[0247] For example, taking the shared device 1 as a "smart screen" as an example, Figures 17A to 17C show the relevant user interfaces of screen projection.

[0248] As shown in Figures 17A and 17B, the control center interface 62 includes a screen projection control 641. In response to the user clicking 641, the terminal device 200 scans for nearby devices using near-field communication technology and displays icons of one or more scanned devices that support screen projection, such as the "Smart Screen" icon 643, in the screen projection selection box 642. The user can select a device from the one or more devices to project the display of the terminal device 200 to the device for display.

[0249] Similar to the relevant description of the aforementioned super terminal, after the terminal device 200 detects a trusted device, it queries the authorization information management module whether the device is a shared device; the query shows that the "smart screen" is a shared device shared by other users, and the terminal device 200 displays a sharing logo 645 on / around the "smart screen" icon 643 to indicate that the "smart screen" is a shared device shared by other users; it can also display the account information of the account to which the "smart screen" belongs, such as the user name 644, to indicate that the user sharing the "smart screen" is Mark.

[0250] As shown in Figures 17A and 17B, the terminal device 200 detects the user's operation on the icon 643 of the "Smart Screen" (such as clicking). After establishing a short-range communication connection with the "Smart Screen", the terminal device 200 sends the projection data to the "Smart Screen" through the short-range communication connection; as shown in Figure 17C, the "Smart Screen" displays the display screen of the terminal device 200 based on the received projection data. The embodiment of the present application does not specifically limit the method of triggering screen projection, and Figures 17A to 17C are only an example. In this way, smart screens and terminal devices 200 that are not on the same account can also collaborate to implement distributed services based on proximity, and a shared operation can be used between devices with different accounts to achieve a long-term and efficient experience of screen projection. In the existing solution, screen projection between devices with different accounts requires manual verification by the user, such as entering a projection PIN code.

[0251] Distributed business: a trick

[0252] For example, taking the shared device 1 as a "smart screen" as an example, Figures 18A and 18B show the relevant user interfaces of "Move One Move".

[0253] In some embodiments, as shown in FIG18A , the user holds the terminal device 200 and performs a preset gesture of the “Move” function. After the terminal device 200 detects the preset gesture, it determines the device (e.g., a smart screen) to which the preset gesture points, and the terminal device 200 establishes a short-range communication connection with the smart screen. The terminal device 200 obtains the application data of the current application of the smart screen through the short-range communication connection. As shown in FIG18B , a service card for the current application, such as service card 651, is displayed based on the application data to control the current application of the smart screen.

[0254] In this way, the smart screen and terminal device 200, which are not connected to the same account, can also collaborate to implement distributed services based on proximity, i.e., "one move". In addition, when the existing "one move" function is shared with family members, there is usually a credit limit. However, in the solution provided by the embodiment of the present application, the smart screen and terminal device 200 have a credit relationship and there is no credit limit.

[0255] Distributed business: auxiliary input

[0256] For example, taking the shared device 1 as a "smart screen" as an example, Figures 19A to 19C show the relevant user interfaces of auxiliary input.

[0257] For example, Figures 19A to 19C illustrate a user interface related to assisted input. As shown in Figure 19A, when the smart screen detects that the user wants to input information, for example, when it detects an operation acting on the information input box 701, the smart screen can detect a nearby trusted device, such as the terminal device 200, and send a push message to the terminal device 200 to request the terminal device 200 to assist in inputting information. As shown in Figure 19B, the terminal device 200 displays the push message 701. As shown in Figures 19B and 19C, in response to the user clicking on the push message 701, the terminal device 200 can display a keyboard 702 and an information input box 703. The information input box 702 includes an information input field 704, a cancel control 705, and a confirmation control 706. The terminal device 200 can obtain the information generated by the user through the keyboard 702 and display it in the information input bar 704; in response to the user clicking the cancel control 705, the terminal device 100 stops displaying the keyboard 702 and the information input box 703; in response to the user clicking the confirm control 706, the terminal device 200 sends the information in the information input bar 703 to the "smart screen" via a short-range communication connection.

[0258] In this way, the smart screen and terminal device 200 that are not under the same account can also collaborate to realize distributed services based on proximity. A single sharing operation can realize long-term and efficient experience of auxiliary input between devices with different accounts, effectively improving the user experience.

[0259] In combination with the above-mentioned embodiments, the present application discloses a multi-device collaboration method and related apparatus, which are applied to a multi-device collaboration system, characterized in that the above-mentioned system includes a first terminal, a second terminal and a server, the first terminal logs in to a first account, the second terminal logs in to a second account, the first account and the second account are different accounts, the above-mentioned system also includes at least one electronic device bound to the first account, and the above-mentioned at least one electronic device includes the first electronic device; the method includes steps S101 to S107.

[0260] In an embodiment of the present application, the first terminal may be the aforementioned terminal device 100; the second terminal may be the aforementioned terminal device 200; the server may be the aforementioned server 300; the first account may be the aforementioned account 1; the second account may be the aforementioned account 2; the first electronic device may be a device shared by the aforementioned terminal device 100 to the terminal device 200, such as the aforementioned home device 1 or shared device 1.

[0261] S101: A first terminal detects a first operation, where the first operation is used to share a first electronic device with a second account.

[0262] In some embodiments, a first account creates a first group, family members of the first group include a second account, and a first operation is used to add the first electronic device as an electronic device of the first group.

[0263] In some embodiments, a first group is created with the first account, the electronic devices of the first group include the first electronic device, and the first operation is used to add the second account as a family member of the first group.

[0264] In the embodiment of the present application, the first group may be the aforementioned family group 1.

[0265] S102: In response to the first operation, the first terminal sends device sharing information to the server, where the device sharing information includes information of the second account and information of the first electronic device.

[0266] The information of the second account may be the authorization information of the aforementioned second account, and the information of the first electronic device may be the authorization information of the aforementioned first electronic device.

[0267] S103: The server sends the second account information to the first electronic device.

[0268] S104: The server sends the information of the first electronic device to the second terminal.

[0269] S105: Based on the information of the second account and the information of the first electronic device, the second terminal and the first electronic device establish a short-range communication connection.

[0270] S106: The second terminal detects a second operation, where the second operation is used to trigger a first distributed service of the second terminal.

[0271] S107: In response to the second operation, the second terminal displays icons of the one or more trusted devices; the one or more trusted devices include the first electronic device.

[0272] In some embodiments, the method further includes: displaying a first identifier along with the icon of the first electronic device, the first identifier being used to indicate that the first electronic device is a device shared by another account to the second account. The first identifier may be the aforementioned sharing identifier.

[0273] In some embodiments, the method further includes: the first terminal detecting a second operation, the second operation triggering the first distributed service; in response to the second operation, the first terminal displaying icons of one or more trusted devices; the one or more trusted devices including a second electronic device; and the second electronic device being a device shared with the first account by another account. In this embodiment of the present application, the second terminal may also share a device bound to account 2 with account 1.

[0274] In some embodiments, the method further includes: the second terminal setting a second filter based on the information of the first electronic device, the second filter being configured to filter messages from the first electronic device; and the second terminal establishing a short-range communication connection with the first electronic device, including: the second terminal establishing a short-range communication connection with the first electronic device based on the filtered messages from the first electronic device. In this embodiment of the present application, the second filter may be the aforementioned filter 2.

[0275] In some embodiments, a second identifier is displayed along with the icon of the first electronic device, and the second identifier is used to indicate the first account that shares the first electronic device. Optionally, the second identifier can be a user name corresponding to the first account.

[0276] In some embodiments, the method further includes: the second terminal detecting a third operation acting on the icon of the first electronic device, and in response to the third operation, the second terminal cooperating with the first electronic device to execute the first distributed service.

[0277] Exemplarily, with reference to the descriptions in Figures 14A to 14F , the icon of the first electronic device may be an icon 602 of an in-vehicle device. Exemplarily, with reference to the descriptions in Figure 16 , the icon of the first electronic device may be an icon 632 of a speaker, and the third operation may include an operation acting on a selection control 633 corresponding to the icon 632. Exemplarily, with reference to the descriptions in Figure 15A , the icon of the first electronic device may be an icon 614 of the terminal device 200. Exemplarily, with reference to the descriptions in Figure 17B , the icon of the first electronic device may be an icon 643 of a smart screen.

[0278] In some embodiments, the second terminal cooperates with the first electronic device to perform the first distributed service, including: the second terminal and the first electronic device transmit the service data of the first distributed service through a short-range communication connection. In some embodiments, the second terminal cooperates with the first electronic device to perform the first distributed service, including: the second terminal sends projection data to the first electronic device through a short-range communication connection; the first electronic device displays the projection screen based on the projection data; or, the second terminal sends application data to the first electronic device through a short-range communication connection; the first electronic device displays the desktop application of the second terminal based on the application data. Alternatively, the second terminal sends audio data to the first electronic device through a short-range communication connection; the first electronic device plays audio based on the audio data.

[0279] In some embodiments, the second terminal collaborates with the first electronic device to perform a first distributed service, including: the first electronic device displays a first input box; the first electronic device sends a first request to the second terminal via a near-field communication connection; the first request is used to request the second terminal to assist in inputting information; the second terminal displays a second input box; the second terminal obtains the first information entered by the user in the second input box; the second terminal sends the first information to the first electronic device via a near-field communication connection; the first electronic device displays the first information in the first input box. For example, refer to Figures 19A to 19C for the description of assisting information input.

[0280] The following describes the structure of a terminal device 100 provided in an embodiment of the present application. FIG20 shows a schematic diagram of the structure of the terminal device 100.

[0281] The terminal device 200 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0282] It should be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the terminal device 200. In other embodiments of the present application, the terminal device 200 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0283] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0284] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0285] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

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

[0287] The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C bus lines. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, and the like via different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K via the I2C interface, enabling communication between the processor 110 and the touch sensor 180K via the I2C bus interface, thereby implementing the touch function of the terminal device 200.

[0288] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface, enabling the function of answering calls through a Bluetooth headset.

[0289] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0290] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface, enabling the function of playing music through Bluetooth headphones.

[0291] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display 194 and the camera 193. MIPI interfaces include the camera serial interface (CSI) and the display serial interface (DSI). In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to implement the camera function of the terminal device 200. The processor 110 and the display 194 communicate via the DSI interface to implement the display function of the terminal device 200.

[0292] The GPIO interface can be configured via software. The GPIO interface can be configured as either a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to the camera 193, display 194, wireless communication module 160, audio module 170, sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0293] The USB interface 130 is an interface that complies with USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the terminal device 200, or to transfer data between the terminal device 200 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as AR devices.

[0294] It is understood that the interface connection relationship between the modules illustrated in the embodiment of the present invention is merely an illustrative illustration and does not constitute a structural limitation on the terminal device 200. In other embodiments of the present application, the terminal device 200 may also adopt a different interface connection method from the above embodiment, or a combination of multiple interface connection methods.

[0295] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the terminal device 200. While charging the battery 142, the charging management module 140 can also power the electronic device through the power management module 141.

[0296] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0297] The wireless communication function of the terminal device 200 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

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

[0299] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the terminal device 200. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0300] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0301] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the terminal device 200. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, demodulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0302] In some embodiments, the antenna 1 of the terminal device 200 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the terminal device 200 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0303] Terminal device 200 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0304] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-oLed, or a quantum dot light-emitting diode (QLED). In some embodiments, terminal device 200 may include one or N display screens 194, where N is a positive integer greater than one.

[0305] The terminal device 200 can realize the shooting function through the ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0306] The ISP processes data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then passed to the ISP for processing and converted into a visible image. The ISP can also perform algorithmic optimization on image noise and brightness. It can also optimize parameters such as exposure and color temperature of the captured scene. In some embodiments, the ISP can be located within camera 193.

[0307] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the terminal device 200 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0308] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the terminal device 200 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0309] Video codecs are used to compress or decompress digital video. Terminal device 200 may support one or more video codecs. This allows terminal device 200 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0310] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU enables intelligent cognitive applications in the terminal device 200, such as image recognition, face recognition, speech recognition, and text comprehension.

[0311] The internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM).

[0312] Random access memory may include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM, for example, the fifth generation DDR SDRAM is generally referred to as DDR5 SDRAM), etc.; non-volatile memory may include disk storage devices and flash memory.

[0313] Flash memory can be divided into NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. according to the operating principle; single-level cell (SLC), multi-level cell (MLC), triple-level cell (TLC), quad-level cell (QLC), etc. according to the storage cell potential level; universal flash storage (UFS) and embedded multi media card (eMMC) can be divided into UFS and eMMC according to the storage specification.

[0314] The random access memory can be directly read and written by the processor 110, and can be used to store executable programs (such as machine instructions) of the operating system or other running programs, and can also be used to store user and application data.

[0315] The non-volatile memory may also store executable programs and user and application data, etc., and may be loaded into the random access memory in advance for direct reading and writing by the processor 110 .

[0316] The external memory interface 120 can be used to connect to an external non-volatile memory to expand the storage capacity of the terminal device 200. The external non-volatile memory communicates with the processor 110 via the external memory interface 120 to implement data storage. For example, files such as music and videos can be stored in the external non-volatile memory.

[0317] The terminal device 200 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0318] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

[0319] The speaker 170A, also called a "speaker", is used to convert audio electrical signals into sound signals. The terminal device 200 can listen to music or listen to hands-free calls through the speaker 170A.

[0320] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the terminal device 200 receives a call or voice message, the user can hear the voice by placing the receiver 170B close to the ear.

[0321] Microphone 170C, also known as a "microphone" or "speaker," is used to convert sound signals into electrical signals. When making a call or sending a voice message, a user can speak by approaching microphone 170C with their mouth to input the sound signal into microphone 170C.

[0322] The headphone jack 170D is used to connect a wired headphone and can be the USB interface 130 or a 3.5mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0323] The pressure sensor 180A is used to sense the pressure signal and convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be disposed on the display screen 194 .

[0324] The gyro sensor 180B may be used to determine the motion posture of the terminal device 200. In some embodiments, the angular velocity of the terminal device 200 around three axes (ie, x, y, and z axes) may be determined by the gyro sensor 180B.

[0325] The air pressure sensor 180C is used to measure air pressure. In some embodiments, the terminal device 200 calculates the altitude through the air pressure value measured by the air pressure sensor 180C to assist in positioning and navigation.

[0326] The magnetic sensor 180D includes a Hall sensor.

[0327] The acceleration sensor 180E can detect the magnitude of the acceleration of the terminal device 200 in various directions (generally three axes).

[0328] The distance sensor 180F is used to measure distance. The terminal device 200 can measure distance using infrared or laser. In some embodiments, when shooting a scene, the terminal device 200 can use the distance sensor 180F to measure distance to achieve fast focusing.

[0329] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector such as a photodiode.

[0330] The ambient light sensor 180L is used to sense the brightness of the ambient light. The terminal device 200 can adaptively adjust the brightness of the display screen 194 according to the sensed brightness of the ambient light.

[0331] The fingerprint sensor 180H is used to collect fingerprints. The terminal device 200 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0332] The temperature sensor 180J is used to detect temperature. In some embodiments, the terminal device 200 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy.

[0333] The touch sensor 180K is also called a "touch device." The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor 180K is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the terminal device 200, at a location different from that of the display screen 194.

[0334] The bone conduction sensor 180M can obtain a vibration signal. In some embodiments, the bone conduction sensor 180M can obtain a vibration signal of a vibrating bone mass in a human vocal part.

[0335] The buttons 190 include a power button, a volume button, etc. The buttons 190 can be mechanical buttons or touch buttons.

[0336] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts and can also be used for touch vibration feedback.

[0337] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0338] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or disconnected from the terminal device 200 by inserting or removing the SIM card into or from the SIM card interface 195 .

[0339] The following describes the structure of a server 300 provided in an embodiment of the present application. FIG21 exemplarily shows the structure of a server 300 provided in an embodiment of the present application.

[0340] As shown in Figure 21, the server 300 may include: one or more processors 1001, memory 1002, communication interface 1003, transmitter 1005, receiver 1006, coupler 1007, and antenna 1008. These components may be connected via a bus 1004 or other means, with Figure 21 using a bus connection as an example.

[0341] The communication interface 1003 can be used for the server 300 to communicate with other communication devices, such as the terminal device 100. Specifically, the communication interface 1003 can be a 3G communication interface, a 4G communication interface, a 5G communication interface, or a communication interface of a future new air interface. Not limited to a wireless communication interface, the server 300 can also be configured with a wired communication interface 1003, such as a local access network (LAN) interface. The transmitter 1005 can be used to transmit and process the signal output by the processor 1001. The receiver 1006 can be used to receive and process the mobile communication signal received by the antenna 1008.

[0342] In some embodiments of the present application, transmitter 1005 and receiver 1006 can be considered a wireless modem. In server 300, the number of transmitters 1005 and receivers 1006 can be one or more. Antenna 1008 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or vice versa. Coupler 1007 is used to split the mobile communication signal received by antenna 1008 into multiple paths and distribute them to multiple receivers 1006.

[0343] Memory 1002 is coupled to processor 1001 and is used to store various software programs and / or multiple sets of instructions. Specifically, memory 1002 may include high-speed random access memory and may also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 1002 may store a network communication program that can be used to communicate with one or more additional devices, one or more terminal devices, or one or more network devices.

[0344] In some embodiments of the present application, the memory 1002 may be used to store an implementation program of the application distribution method provided in one or more embodiments of the present application on the server 300. For implementation of the application distribution method provided in one or more embodiments of the present application, please refer to the above embodiments.

[0345] The processor 1001 may be configured to read and execute computer-readable instructions. Specifically, the processor 1001 may be configured to call a program stored in the memory 1002, such as a program for implementing the application distribution method provided in one or more embodiments of the present application on the server 300 side, and execute the instructions contained in the program.

[0346] It should be noted that the server 300 shown in FIG21 is only one implementation of the embodiment of the present application. In actual applications, the server 300 may also include more or fewer components, which is not limited here.

[0347] For more details about the functions and working principles of the server 300, please refer to the relevant content in the above embodiments, which will not be repeated here.

[0348] The various implementation modes of this application can be combined arbitrarily to achieve different technical effects.

[0349] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described herein are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0350] Those skilled in the art will appreciate that all or part of the process steps in the above-described method embodiments can be implemented by a computer program instructing the relevant hardware. The program can be stored in a computer-readable storage medium, and when executed, the program can include the process steps in the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0351] In short, the above description is only an embodiment of the technical solution of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made based on the disclosure of the present invention should be included in the scope of protection of the present invention.

Claims

1. A multi-device collaboration method, applied to a multi-device collaboration system, characterized in that: The system includes a first terminal, a second terminal and a server, the first terminal logs in a first account, the second terminal logs in a second account, the first account and the second account are different accounts, the system also includes at least one electronic device bound to the first account, the at least one electronic device includes the first electronic device; the method includes: The first terminal detects a first operation, where the first operation is used to share the first electronic device with the second account; In response to the first operation, the first terminal sends device sharing information to the server, where the device sharing information includes information of the second account and information of the first electronic device; The server sends the information of the second account to the first electronic device; The server sends the information of the first electronic device to the second terminal; The second terminal establishes a short-range communication connection with the first electronic device based on the information of the second account and the information of the first electronic device; The second terminal detects a second operation, where the second operation is used to trigger a first distributed service of the second terminal; In response to the second operation, the second terminal displays icons of one or more trusted devices; the one or more trusted devices include the first electronic device.

2. The method according to claim 1, characterized in that Also includes: A first identifier is displayed along with the icon of the first electronic device, and the first identifier is used to indicate that the first electronic device is a device shared by other accounts to the second account.

3. The method according to claim 1 or 2, characterized in that: Also includes: The first terminal detects a second operation, where the second operation is used to trigger a first distributed service; In response to the second operation, the first terminal displays icons of one or more trusted devices; the one or more trusted devices include a second electronic device; and the second electronic device is a device shared by other accounts with the first account.

4. The method according to claim 1 or 2, characterized in that: Also includes: The second account is bound to at least one electronic device, the at least one electronic device includes a second electronic device, and the method further includes: In response to the first operation, after the second terminal receives the information of the first electronic device, the second terminal sends device sharing information to the server, where the device sharing information is used to establish a short-range communication connection between the first terminal and the second electronic device.

5. The method according to any one of claims 1 to 4, characterized in that: Also includes: The second terminal sets a second filter based on the information of the first electronic device, where the second filter is used to filter messages from the first electronic device; The second terminal and the first electronic device establish a short-range communication connection, including: The second terminal establishes a short distance communication connection with the first electronic device according to the filtered message of the first electronic device.

6. The method according to any one of claims 1 to 5, characterized in that: A second identifier is also displayed along with the icon of the first electronic device, and the second identifier is used to indicate the first account that shares the first electronic device.

7. The method according to any one of claims 1 to 6, characterized in that: Also includes: The second terminal detects a third operation performed on the icon of the first electronic device, In response to the third operation, the second terminal cooperates with the first electronic device to execute a first distributed service.

8. The method according to any one of claims 1 to 7, characterized in that: The first account creates a first group, family members of the first group include the second account, and the first operation is used to add the first electronic device as an electronic device of the first group.

9. The method according to any one of claims 1 to 7, characterized in that: A first group is created with the first account, the electronic devices of the first group include the first electronic device, and the first operation is used to add the second account as a family member of the first group.

10. The method according to any one of claims 1 to 6, characterized in that: The first operation is also used to add the device bound to the second account as a family member of the first group.

11. The method according to any one of claims 1 to 10, characterized in that: The second terminal cooperates with the first electronic device to execute a first distributed service, including: The second terminal and the first electronic device transmit the service data of the first distributed service via a short-range communication connection.

12. The method according to any one of claims 1 to 10, characterized in that: The second terminal cooperates with the first electronic device to execute a first distributed service, including: The second terminal sends the screen projection data to the first electronic device through the short-range communication connection; The first electronic device displays a projection screen based on the projection screen display; or, The second terminal sends application data to the first electronic device via the short-range communication connection; The first electronic device displays a desktop application of the second terminal based on the application data; or, The second terminal sends audio data to the first electronic device via the short-range communication connection; The first electronic device plays audio based on the audio data.

13. The method according to any one of claims 1 to 10, characterized in that: The second terminal cooperates with the first electronic device to execute a first distributed service, including: The first electronic device displays a first input box; The first electronic device sends a first request to the second terminal through the short-range communication connection; the first request is used to request the second terminal to assist in inputting information; The second terminal displays a second input box; The second terminal obtains first information input by the user in the second input box; The second terminal sends the first information to the first electronic device through the short-range communication connection; The first electronic device displays the first information in the first input box.

14. The method according to any one of claims 1 to 13, characterized in that: The information of the second account includes the user identity UID of the second account; the information of the first electronic device includes the unique identification code UDID of the first electronic device and the UID of the first account that shares the first electronic device.

15. A multi-device collaboration method, characterized in that: A first terminal logs in to a first account, and a second terminal logs in to a second account, the first account and the second account are different accounts, the first account is bound to at least one electronic device, and the at least one electronic device includes a first electronic device; the method includes: The first terminal device detects a first operation, where the first operation is used to share the first electronic device with the second account; In response to the first operation, the first terminal device sends device sharing information to the server, where the device sharing information includes information of the second account and information of the first electronic device; The first terminal sends the information of the second account to the first electronic device through the server; The first terminal sends the information of the first electronic device to the second terminal through the server; The information of the second account and the information of the first electronic device are used for the second terminal to establish a short-range communication connection with the first electronic device.

16. The method according to claim 15, characterized in that Also includes: The first terminal detects a second operation, where the second operation is used to trigger a first distributed service; In response to the second operation, the first terminal displays icons of one or more trusted devices; the one or more trusted devices include a second Electronic equipment; The second electronic device is a device shared with the first account by other accounts.

17. The method according to claim 15 or 16, characterized in that Also includes: The icon of the second electronic device is displayed with a first identifier, and the first identifier is used to indicate that the second electronic device is a device shared with the first account by other accounts.

18. The method according to any one of claims 15 to 17, characterized in that A second identifier is also displayed along with the icon of the second electronic device, and the second identifier is used to indicate an account for sharing the second electronic device.

19. The method according to any one of claims 15 to 18, characterized in that Also includes: The first terminal detects a fourth operation acting on the icon of the second electronic device, In response to the fourth operation, the first terminal cooperates with the second electronic device to execute a first distributed service.

20. The method according to any one of claims 15 to 19, characterized in that The first account creates a first group, family members of the first group include the second account, and the first operation is used to add the first electronic device as an electronic device of the first group.

21. The method according to any one of claims 15 to 19, characterized in that A first group is created with the first account, the electronic devices of the first group include the first electronic device, and the first operation is used to add the second account as a family member of the first group.

22. The method according to any one of claims 15 to 19, characterized in that The first terminal cooperates with the second electronic device to execute a first distributed service, including: The first terminal and the first electronic device transmit the service data of the first distributed service via a short-range communication connection.

23. The method according to any one of claims 15 to 21, characterized in that The first terminal cooperates with the second electronic device to execute a first distributed service, including: The first terminal sends the projection data to the second electronic device through the short-range communication connection; the projection data is used by the second electronic device to display the projection screen; or, The first terminal sends application data to the second electronic device through the short-range communication connection; the application data is used by the second electronic device to display the desktop application of the first terminal; or, The first terminal sends audio data to the second electronic device through the short-range communication connection; the audio data is used by the second electronic device to play audio.

24. A multi-device collaboration method, characterized in that: The first terminal logs in a first account, the second terminal logs in a second account, the first account and the second account are different accounts, the system further includes at least one electronic device bound to the first account, the at least one electronic device includes the first electronic device; the method includes: The second terminal receives the information sent by the server to the first electronic device; The second terminal establishes a short-range communication connection with the first electronic device based on the information of the first electronic device; The second terminal detects a second operation, where the second operation is used to trigger a first distributed service of the second terminal; In response to the second operation, the second terminal displays icons of one or more trusted devices; the one or more trusted devices include the first electronic device.

25. The method according to claim 24, characterized in that Also includes: A first identifier is displayed along with the icon of the first electronic device, and the first identifier is used to indicate that the first electronic device is a device shared by other accounts to the second account.

26. The method according to claim 24 or 25, characterized in that A second identifier is also displayed along with the icon of the first electronic device, and the second identifier is used to indicate the first account that shares the first electronic device.

27. The method according to any one of claims 24 to 26, characterized in that Also includes: The second terminal sets a second filter based on the information of the first electronic device, where the second filter is used to filter messages from the first electronic device; The second terminal and the first electronic device establish a short-range communication connection, including: The second terminal establishes a short distance communication connection with the first electronic device according to the filtered message of the first electronic device.

28. The method according to any one of claims 24 to 27, characterized in that Also includes: The second terminal detects a third operation performed on the icon of the first electronic device, In response to the third operation, the second terminal cooperates with the first electronic device to execute a first distributed service.

29. The method according to any one of claims 24 to 28, characterized in that The first account creates a first group, family members of the first group include the second account, and the first operation is used to add the first electronic device as an electronic device of the first group.

30. The method according to any one of claims 24 to 28, characterized in that A first group is created with the first account, the electronic devices of the first group include the first electronic device, and the first operation is used to add the second account as a family member of the first group.

31. The method according to any one of claims 24 to 30, characterized in that The second terminal cooperates with the first electronic device to execute a first distributed service, including: The second terminal and the first electronic device transmit the service data of the first distributed service via a short-range communication connection.

32. The method according to any one of claims 24 to 30, characterized in that The second terminal cooperates with the first electronic device to execute a first distributed service, including: The second terminal sends screen projection data to the first electronic device through the short-range communication connection, and the screen projection data is used for the first electronic device to display the projection screen; or, The second terminal sends application data to the first electronic device through the short-range communication connection; the application data is used by the first electronic device to display the desktop application of the second terminal; or, The second terminal sends audio data to the first electronic device through the short-range communication connection; the audio data is used by the first electronic device to play audio.

33. The method according to any one of claims 24 to 30, characterized in that The second terminal cooperates with the first electronic device to execute a first distributed service, including: The second terminal receives a first request sent by the first electronic device through the short-range communication connection; the first request is used to request the second terminal to assist in inputting information; The second terminal displays a second input box; The second terminal obtains first information input by the user in the second input box; The second terminal sends the first information to the first electronic device through the short-range communication connection; the first information is used by the first electronic device to display in the first input box.

34. An electronic device, characterized in that: It includes a memory and a processor, the memory and the processor are electrically coupled, the memory is used to store program instructions, and the processor is configured to call all or part of the program instructions stored in the memory so that the electronic device executes the method as described in any one of claims 15-23 or 24-33.

35. A computer storage medium, characterized in that The method comprises computer instructions, which, when executed on an electronic device, cause the electronic device to execute the method as described in any one of claims 15-23 or 24-33.

Images