Multi-device cooperation method and related device

Abstract

The invention discloses a multi-device cooperation method and a related device, and the method comprises the steps: a first terminal detects a first operation, and the first operation is used for sharing a first electronic device with a second account; in response to the first operation, the first terminal sends device sharing information to the server, and the device sharing information comprises 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 equipment; the server sends the information of the first electronic equipment to the second terminal; based on the information of the second account number and the information of the first electronic equipment, the second terminal and the first electronic equipment establish near field communication connection; the second terminal detects a second operation, wherein the second operation is used for triggering the first distributed service of the second terminal; in response to a second operation, the second terminal displays the icons of the one or more trusted devices; the one or more trusted devices include a first electronic device. Therefore, the distributed service can be realized in cooperation with the different account number equipment.

Description

Technical Field

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

[0002] With the continuous development of terminal technology, users have more and more types and functions of electronic devices. Limited by their own hardware structure and system performance, different types of devices usually have different capabilities and advantages. Multiple devices of users, combined with the performance advantages of each device, conduct collaborative control of device interconnection and distributed services, bringing users a better user experience. 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-mounted 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.

[0003] Devices with the same account can usually have a trust relationship and can perform coordinated operations on distributed services. However, for devices with different accounts, users are usually required to manually connect and authenticate (for example, enter a PIN code) to establish a communication connection and perform device coordination on distributed services, which is cumbersome for users to operate.

[0004] At present, how to quickly implement distributed services between devices with different accounts still needs further research. Summary of the invention

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

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

[0007] 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 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 first electronic device and the second terminal that are not in 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.

[0008] In one implementation, the method further includes: displaying a first identifier 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. In the implementation of the present application, the first identifier is used to indicate which devices are shared, so that the user has an intuitive understanding of the shared devices.

[0009] 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; 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 distributed services. 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.

[0010] In one implementation, the method further includes: the second terminal sets a second filter based on the information of the first electronic device, 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. In implementing the embodiment of the present application, the second filter is set through the information of the first electronic device, so that the message of the first electronic device can be filtered out, which facilitates the establishment of a short-range communication connection with the first electronic device.

[0011] In one implementation, the method also includes: the second account is bound to at least one electronic device, and the at least one electronic device includes a second electronic device. The method also 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 for the first terminal and the second electronic device to establish a short-range communication connection.

[0012] 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. When implementing the embodiment of the present application, the user name of the account to which the shared device belongs can be displayed on / around the icon of the shared device, so that the user can intuitively understand which user shared the device with him.

[0013] In one implementation, the method further includes: the second terminal detects a third operation on the icon of the first electronic device, and in response to the third operation, the second terminal cooperates with the first electronic device to execute the first distributed service. In the implementation of the present application, a device with a different account number can be selected to execute the distributed service.

[0014] 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 the embodiment of the present application, a user can be invited to join a group to share devices in the group with the user.

[0015] In one implementation, a first account creates a first group, 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. By implementing the embodiment of the present application, the newly added device can be shared with the user by adding the device to the group.

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

[0017] In one implementation, the second terminal cooperates with the first electronic device to perform 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. In one implementation, the second terminal cooperates with the first electronic device to perform a first distributed service, including: the second terminal sends screen 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.

[0018] In one implementation, the second terminal cooperates with the first electronic device to perform the first distributed service, including: the first electronic device displays the first input box; the first electronic device sends a first request to the second terminal via a short-distance communication connection; the first request is used to request the second terminal to assist in inputting information; the second terminal displays the 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 via a short-distance communication connection; the first electronic device displays the first information in the first input box. By implementing the embodiments of the present application, devices with different accounts can quickly implement distributed services, such as assisting in information input.

[0019] In the second 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 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 a 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.

[0020] 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 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 first electronic device and the second terminal that are not in 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.

[0021] 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;

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

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

[0024] 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 for sharing the second electronic device.

[0025] 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 executing the first distributed service in collaboration with the second electronic device.

[0026] 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 a first electronic device as an electronic device of the first group.

[0027] In one implementation, a first group is created with a first account, electronic devices of 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.

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

[0029] In one implementation, the first terminal cooperates with the second electronic device to perform the first distributed service, including: the first terminal sends screen projection data to the second electronic device through a short-range communication connection; the screen projection data is used for the second electronic device to display the projection screen; or the first terminal sends application data to the second electronic device through a short-range communication connection; the application data is used for 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 a short-range communication connection; the audio data is used for the second electronic device to play audio.

[0030] 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 a 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 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.

[0031] 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 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 first electronic device and the second terminal that are not in 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.

[0032] 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 to the second account.

[0033] 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 a first account that shares the first electronic device.

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

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

[0036] 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 a first electronic device as an electronic device of the first group.

[0037] In one implementation, a first group is created with a first account, electronic devices of 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.

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

[0039] In one implementation, 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 via 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 via 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 via a short-range communication connection; the audio data is used by the first electronic device to play audio.

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

[0041] 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, the computer program code comprises computer instructions, and when the processor reads the computer instructions from the memory, the electronic device executes the multi-device collaboration method described in the second aspect.

[0042] 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, and when the processor reads the computer instructions from the memory, the electronic device executes the multi-device collaboration method described in the third aspect.

[0043] In a sixth aspect, an embodiment of the present application provides a computer storage medium, including computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes a multi-device collaboration method in any possible implementation of any of the above aspects.

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

[0045] Figure 1 and Figure 2 A schematic diagram of the system architecture of a communication system provided in an embodiment of the present application;

[0046] FIG. 3A to FIG. 3L A schematic diagram of a user interface of a shared device provided in an embodiment of the present application;

[0047] FIG. 4A to FIG. 4G A schematic diagram of a user interface of a shared device provided in an embodiment of the present application;

[0048] FIG. 5A to FIG. 5H A schematic diagram of a user interface of a shared device provided in an embodiment of the present application;

[0049] FIG. 6A to FIG. 6G A schematic diagram of a user interface of a shared device provided in an embodiment of the present application;

[0050] 7A to 7C A schematic diagram of a user interface of a shared device provided in an embodiment of the present application;

[0051] FIG. 8A to FIG. 8D A schematic diagram of a user interface of a shared device provided in an embodiment of the present application;

[0052] 9A to 9C A schematic diagram of a user interface of a shared device provided in an embodiment of the present application;

[0053] FIG. 10A to FIG. 10F A schematic diagram of a user interface of a shared device provided in an embodiment of the present application;

[0054] Fig.11 A schematic diagram of the system architecture of the software system provided in the embodiment of the present application;

[0055] Fig.12 A schematic diagram of the system architecture of a multi-device collaborative system provided in an embodiment of the present application;

[0056] Fig.13 A schematic diagram of a method flow chart provided in an embodiment of the present application;

[0057] FIG. 14A to FIG. 14F A schematic diagram of a user interface of a hyperterminal provided in an embodiment of the present application;

[0058] FIG. 15A to FIG. 15C A schematic diagram of a user interface of a super desktop provided in an embodiment of the present application;

[0059] Fig.16 A schematic diagram of a user interface for audio projection provided in an embodiment of the present application;

[0060] FIG. 17A to FIG. 17C A schematic diagram of a user interface for screen projection provided in an embodiment of the present application;

[0061] FIG. 18A to FIG. 18B A schematic diagram of a user interface for the move provided in an embodiment of the present application;

[0062] FIG. 19A to FIG. 19C A schematic diagram of a user interface for auxiliary input provided in an embodiment of the present application;

[0063] Fig. 20 A schematic diagram of the device structure of a terminal device provided in an embodiment of the present application;

[0064] Fig.21 A schematic diagram of the device structure of a server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0065] The technical solutions in the embodiments of the present application will be described clearly and in detail below 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 of the associated 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.

[0066] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more.

[0067] The term "user interface (UI)" in the following embodiments of the present 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 can be recognized by the user. The commonly used form of user interface is a graphical user interface (GUI), which refers to a user interface related to computer operation 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.

[0068] The following is an introduction to the communication system 10 involved in the multi-device collaboration method provided in an embodiment of the present application.

[0069] Figure 1 and Figure 2 The system architecture of the communication system 10 provided in the embodiment of the present application is exemplarily shown. Figure 1 and Figure 2 As shown, 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.

[0070] The terminal device 100 and the terminal device 200 can communicate with the server 400 through the communication network to register and log in to the account of application 1. The user can view, manage, and control the devices bound to account 1 through application 1 of the terminal device 100, and the user can view, manage, and control the devices bound to account 2 through application 1 of the terminal device 200.

[0071] In some embodiments, the device bound to account 1 may include a network-equipped device bound to account 1, which can be connected to the Internet and has the attributes of a social network. Such devices can be understood as Internet of Things (IOT) devices; the terminal device 100 can control the network-equipped 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, vehicle-mounted devices, routers, air conditioners, televisions, projection equipment, smart speakers, smart door locks, smart lights, smart windows, smart curtains, smart body fat scales, treadmills, smart rice cookers, smart electric kettles, etc.

[0072] In some embodiments, the device bound to account 1 includes a terminal device for logging into account 1, such as a mobile phone, a tablet, a smart screen, etc. The terminal device 100 can obtain other terminal devices for logging into the same account through the server 400.

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

[0074] Figure 1 In the communication system shown, the terminal device 100 has a trust relationship with the terminal device logged in to the same account. When they are close, they can establish a connection and complete authentication to complete the self-organizing network, so that they can collaboratively realize close-range distributed services (for example, super terminal, super desktop, screen projection and other services), and transmit 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 wideband (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.

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

[0076] In some embodiments, after the terminal device 100 shares the shared device 1 (e.g., IOT device) bound to the account 1 with the account 2, the terminal device 200 logged into the 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 the 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.

[0077] Figure 2The communication system shown 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 through server 300, so that shared device 1 and terminal device 200 are credited, that is, they have a trust relationship; after credit, 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.

[0078] In the embodiments 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). The present 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.

[0079] The communication network may include local area networks (LAN) and / or wide area networks (WAN). 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), communication protocols supporting network slicing architecture, or any other suitable communication protocols.

[0080] 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), vehicle-mounted 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.

[0081] The server 300 and the server 400 may be a single server, or 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.

[0082] It should be understood that Figure 1 and Figure 2 The system structure diagram of the communication system provided in the embodiment of the present application is only a schematic diagram, and does not constitute a specific limitation on the communication system 10. The communication system 10 may include more or less devices than shown in the figure, for example, it may also include a wireless relay device and a wireless backhaul device ( Figure 1 ), which is not shown in the figure and is not limited here.

[0083] The following takes application 1 as an example of a smart life application to illustrate the interface implementation of account 1 sharing home devices with account 2.

[0084] In some embodiments, after user 1 (e.g., Mrak) registers and logs in to account 1 of the smart life application through terminal device 100, the smart life application generates a family group 1 (e.g., "Mrak's Home"). Then, user 1 can add home devices and family members to family group 1 through 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 (e.g., delete, classify, control, etc.), and can also manage the family members added to the family group (e.g., 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.

[0085] For example, Figure 3A and Figure 3B A related user interface for starting a smart life application is shown.

[0086] Figure 3A The main interface 11 for displaying applications installed on the terminal device 100 is shown. 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 of smart life applications.

[0087] like Figure 3A and Figure 3B As shown, in response to the user clicking the application icon 101, the terminal device 100 starts the smart life application and displays the home page 12 of the smart life application. Figure 3AAs shown, the home page 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 .

[0088] 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 (such as My 102B) in the page navigation bar 102, the home page can be switched to the page indicated by other page options, for example, the user center interface of the smart life application indicated by My 102B.

[0089] 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".

[0090] The display navigation bar 104 includes the following display options: device 104A, space 104B, and my home 104C. The currently selected display option in the display navigation bar 104 (e.g., device 104A) is used to indicate the display mode of the home devices in the device display area 105. Among them, device 104A is used to indicate the display of the home devices in the home group indicated by the home group option 103; space 104B is used to indicate the classification and display of the home devices in the home group indicated by the home group option 103 according to the space to which the device belongs; "my home 104C" is used to indicate all home devices added by the currently logged in account 1.

[0091] like Figure 3B As shown, the device information of the home devices 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).

[0092] A family group can be understood as a virtual device space. Users can add family devices bound to account 1 to the device space, and can also add family members who share these family devices. Family members are accounts in the same account system. This application does not specifically limit the device types of family devices. Family groups, family devices, and family members are merely exemplary conceptual names and may also be referred to as other names, which should not constitute limitations on this application; for example, family groups, family devices, and family members may also be referred to as shared groups, shared devices, and shared members, respectively. Family 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 family devices.

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

[0094] Interface implementation 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.

[0095] For example, FIG. 3B to FIG. 3I The relevant user interface of the terminal device 100 for adding user 2 to the family group 1 is shown.

[0096] For example, Figure 3B and Figure 3C As shown, 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 display 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.

[0097] The menu box 111 also 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.

[0098] like Figure 3C and Figure 3D As shown, in response to the user clicking the home management control 116, the terminal device 100 displays the home management interface 13. The home management interface 13 includes: an entry of the home group to which the account 1 joins, on which the number of home devices in the home group and the data of the family members are displayed; for example, an entry 121 of "Mark's home", an entry 122 of "office", and an entry 123 of "laboratory", as well as a switch control 124 for creating a new home and a switch control 125 for automatically switching the home.

[0099] Create a new home 124 is used to trigger the creation of a new home group. The switch control 125 for the home automatic switch includes an on state (ON) and an off state (OFF); each home group can be set with a geographic location. When the switch control 125 includes an on state, the terminal device 100 can switch the home group displayed on the home page (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.

[0100] like Figure 3D and Figure 3E As shown, 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, the name and address of the family group, and the rooms to which each device in the family group belongs can be edited. 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 avatars of other accounts invited to join the family group, such as luna's account avatar.

[0101] like Figure 3E and Figure 3F As shown, 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 can display a shared member selection interface 15. The selection interface 15 provides multiple selection options, such as an option 141 for scanning a code to share, an option 142 for selecting family members through a Huawei account, an option 143 for selecting family members through a social application 1, and an account list 144.

[0102] like Figure 3F and Figure 3G As shown, in response to the user clicking on option 142, the terminal device 100 may display a user interface 17 for adding a Huawei account, the user interface 17 including a search box 161 and a confirmation control 162; Figure 3H and Fig. 3I As shown, 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 of Emma's Huawei account in the home management interface 13.

[0103] Option 141 of scanning code to share can trigger the terminal device 100 to display the code scanning interface. After scanning the QR code of other accounts (such as account 2) of smart life applications through the code scanning interface, the terminal device 100 can display the account as an optional family member in the selection interface 15. Option 143 can trigger the terminal device 100 to display the contact selection interface of social application 1. The contacts in social application 1 are bound to the accounts of smart life applications. Through this interface, one or more contacts of social application 1 can be selected and displayed in the selection interface 15. The Huawei accounts of smart life applications bound to the above contacts are optional accounts.

[0104] The 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 (such as 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 is selected.

[0105] like Figure 3F As shown, the family member selection interface 15 also 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 and invite them to join the family group 1 (for example, "Mark's home"). Fig. 3I and Figure 3J As shown, after the user selects Emma's account and Henry's account, in response to the user clicking the sharing 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 (for example, prompt information 139 around the avatar 138) to indicate that it is waiting for the user to accept the invitation.

[0106] like Figure 3K As shown, 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 information 149. After Henyr rejects the invitation, the terminal device 100 stops displaying Henry's avatar in the family member box 134.

[0107] The terminal device 100 can delete the family members added in "Mark's home". Figure 3K and Figure 3L As shown, in response to the user clicking on Emma's avatar 138, the terminal device 100 displays Emma's member details interface 16, which includes Emma's user name 152 and Huawei account 151, and also includes a remove member control 153. In response to the user clicking on the remove member control 153, the terminal device 100 removes Emma's account from "MarK's Home".

[0108] 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 of the 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 that family members can only control the use of home devices when they are close to the location of the family group.

[0109] 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, family device 1 in family group 1 is shared with user 2, that is, terminal device 100 authorizes terminal device 200 and family device 1 logged in to account 2; after authorization, when terminal device 200 is close to family device 1, terminal device 200 and family device 1 can establish a short-range communication connection and automatically form a network, so that the two devices can collaborate to realize short-range distributed services 1 (such as super terminals, screen projection, etc.). Family device 1 can be referred to as a shared device shared by account 1 to account 2. Optionally, family device 1 is any device in family group 1. Optionally, family device 1 is a family device in family group 1 that supports short-range distributed services 1.

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

[0111] For example, 4A to 4F The relevant user interface of the terminal device 200 accepting the invitation is shown.

[0112] like Figure 4AAs shown, the smart life application of the terminal device 200 logs in to the account of user 1 (for example, Emma). After the smart life application of the terminal device 200 receives the invitation request sent by the terminal device 100, a prompt box 201 is displayed on the home page 21. The prompt box 201 includes a prompt message 202, a rejection control 203, and an accept and view control 204. The prompt message 202 is used to prompt Mark to invite him to join "Mark's home", and the rejection control 203 is used to reject the above invitation request; Figure 4A and Figure 4B As shown, in response to the user clicking to accept and view the control 204, the terminal device 200 feeds back confirmation information to the smart life application of the terminal device 100 to indicate acceptance of the above invitation request, and obtains the home devices of "Mark's Home" from the cloud server 400, displays the home group name of "Mark's Home" in the home group option 205 of the home page 21, and displays the home devices in "Mark's Home" in the device display area 206.

[0113] In some embodiments, after Emma confirms to join "Mark's Home", the terminal device 200 also displays a prompt message on the home page 21 to prompt the user that the terminal device 200 can cooperate with the home devices in "Mark's Home" to perform distributed services, such as super terminal, super desktop, screen projection, audio projection, auxiliary input and other distributed services. For example, taking the super terminal service as an example, Figure 4C As shown, the terminal device 200 displays a prompt message 207, which is used to prompt that the terminal device can use the devices in "Mark's home" in the hyperterminal service. Figure 4C and Figure 4D As shown, in response to the user clicking the prompt information 207, the terminal device 200 can display the hyperterminal interface 22; the terminal device 200 can detect the home devices of "Mark's home" nearby, such as car-mounted devices, and display the icon 211 of the car-mounted device, the user name 212 of the account 1 to which it belongs, and the sharing mark 213 on the hyperterminal interface 22. The user name 212 is used to indicate the user name of the account to which the car-mounted device belongs, and the sharing mark 213 is used to indicate that the above-mentioned car-mounted device is a shared device shared by other users. Specifically, the distributed services of the hyperterminal are described in more detail in the subsequent embodiments, which will not be repeated here.

[0114] like Figure 4B and Figure 4DAs shown, 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 of family groups joined by the account 2 logged in by the terminal device 200, including options of family groups created by the account 2, such as "Emma's Home", and may also include options 209 of family groups created by other accounts joined by the account 1, such as "Mark's Home", and the sharing mark 210 displayed on the option is used to indicate that "Mark's Home" is a family group created and shared by other accounts.

[0115] The menu box 208 also displays a home management control 211; Figure 4D and Figure 4E As shown, in response to the user clicking the home management control 211, the terminal device 200 displays the home management interface 23 of "Mark's home". The home management interface 23 can refer to the relevant description of the home management interface 13 on the terminal device 100. Figure 4E and Figure 4F As shown, the home management interface 23 includes an entry 221 of "Mark's home". In response to the user clicking on the entry 221, the terminal device 200 displays the home details interface 24 of "Mark's home". The home details interface 24 can refer to the relevant description of the home details interface 14 on the terminal device 100.

[0116] After Account 2 joins "Mark's Home", it can also choose to exit "Mark's Home". Figure 4F and Figure 4G As shown, the home details interface 24 includes an exit home control 231. In response to the user clicking the exit home control 231, the terminal device 100 moves the account 2 out of "Mark's home" and returns to the home management interface 23, and the home management interface 23 stops displaying the entry 221 of "Mark's home".

[0117] Depend on 4A to 4F It can be seen that after account 2 joins "Mark's Home" created by account 1, user 2 (ie 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, and view the home details interface of "Mark's Home".

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

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

[0120] For example, FIG. 5A to FIG. 5F It shows the relevant user interface of the terminal device adding a device in the family group 1.

[0121] like Figure 5A and Figure 5B As shown, 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.

[0122] like Figure 5B and Figure 5C As shown, in response to the user clicking the operation of adding a device 302, the terminal device 100 scans nearby devices and displays a user interface 31. The user interface 31 includes a prompt message 303, a manual add control 304, and a scan add control 305. The prompt message 303 is used to prompt that nearby devices are being scanned; the manual add control 304 is used to trigger adding the device by manual input; and the scan add control 305 is used to trigger adding the device by scanning the device QR code.

[0123] like Figure 5D As shown, after scanning a device (such as a vehicle-mounted device), an icon 308 of the vehicle-mounted device and an add control 306 are displayed. Figure 5D and Figure 5E As shown, in response to the user clicking the add control 306, the terminal device 100 adds the vehicle-mounted device to the family group displayed on the home page 12, namely "Mark's Home", and switches the text "Add" presented by the add control 306 to "Added".

[0124] like Figure 5E and Fig. 5F As shown, in response to the user clicking the icon 308 of the vehicle-mounted device, the terminal device 100 displays the device setting interface 33. The device setting interface 33 is used to set the name of the added device, the room to which it belongs, and other information. Fig. 5F and Figure 5G As shown, the device setting interface 33 also includes a next control 307. In response to the user clicking the next control 307, the terminal device 100 displays a sharing setting interface 34. The sharing setting 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 related description of the family member box 134 described above; the family member box 311 includes an add control 312; as shown in FIG. Figure 5G and Figure 5HIn response to the user clicking the add control 312, the terminal device 100 may display the family member selection interface 15. In this way, when adding a device to the family group 1, family members may also be added. The separate share control 313 is used to trigger sharing of the device to a specified user.

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

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

[0127] In some embodiments, Figure 6C As shown, when the smart life application detects that a family member in the family sharing group has not joined the family group 1 of the smart life application, a message box 321 may be displayed on the home page 12. The message box 321 is used to recommend family members in the family sharing group to the user, prompting the user to add the family members in the family sharing group to "Mark's home" to share the home devices in "Mark's home". Figure 6C and Fig.6D As shown, the message box 321 includes a rejection control 322 and an invitation control 323. The rejection control 322 is used to reject the invitation; Figure 6C and Fig.6D As shown, in response to the user clicking the invitation control 323, the terminal device 100 may display Figure 6B The selection box 324 shown in the figure includes the accounts in the family sharing group that are not added to "family group 1" and their corresponding selection controls, a rejection control 325 and an invitation control 326. The rejection control 325 is used to reject the selection of family members from the selection box 324. Fig.6D and Fig. 6E As shown, 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.

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

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

[0130] In some embodiments, Fig. 7A As shown, when the smart life application detects that the family members in the family sharing group have not joined the family group of the smart life application, a message 331 can be pushed to the notification center 37 of the terminal device 100. The message 331 is used to recommend the family members in the family sharing group to the user, prompting the user to add the family members in the family sharing group to the family group of the smart life application to share the home devices in the family group. Fig. 7A and Figure 7B As shown, in response to the user clicking on the message 331, the terminal device 100 may display a family management interface 38, which includes options for each family group that the account 1 joins and a confirmation control 332. Figure 7B and Figure 7C As shown, after the user selects "Mark's Home", in response to the user clicking the confirmation control 332, the terminal device 100 can display a selection box 333, which is used to display accounts from the home sharing group recommended by the smart life application, from which the user 1 selects an account to join "Mark's Home". The selection box 333 can refer to the relevant description of the aforementioned selection box 324, which will not be repeated here.

[0131] In some embodiments, in the aforementioned interface embodiment 3 and interface embodiment 4, after the switch of family member recommendation is turned on, the smart life application will push a message on the home page 12 or notification center 37 to recommend family members from the family sharing group. Fig. 8A and Figure 8B As shown, in response to the user clicking 102B, the terminal device 100 displays the user center interface 41 of the smart life application. Figure 8B and Figure 8CAs shown, in response to the user clicking on the setting item 341 in the user center interface 41, the terminal device 100 displays the setting interface 42. The setting interface 42 includes a switch 342 for family member recommendation, and the switch 342 has two states: on and off. Figure 8C and Fig.8D As shown, in response to the user clicking the switch 342, the terminal device 100 switches the switch 342 from the closed state to the open state.

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

[0133] For example, Fig.9A and Fig. 9B As shown, the home page 12 displays a control card 401 of the "Smart Screen" of "Mark's Home"; in response to the user's long pressing of the card 401, the terminal device 100 displays a menu box 402, which includes a shared device control 403. Fig. 9B and Fig. 9C As shown, in response to the user clicking the shared device control 403, the terminal device 100 displays the shared member selection interface 15. 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.

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

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

[0136] For example, Fig. 10A and Fig. 10B As shown, in response to the user sliding up the family sharing interface 36 of the family sharing group of the Huawei account, 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. Fig. 10B and Fig. 10C As shown, in response to the user clicking the view control 501, the terminal device 100 displays the 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, shared devices that account 1 receives from other users, and sharable devices bound to account 1.

[0137] For example, Fig. 10CAs shown, the shared device interface 51 includes a navigation bar 502 and a device display area 503. The navigation bar 502 includes shared devices 504, accepted 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 accepted 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. Fig. 10C and Fig. 10D As shown, when the shared device 504 is selected, the device display area 503 displays a card 507 of the vehicle-mounted device; in response to the user clicking the card 507, the terminal device 100 displays the sharing details interface 52 of the vehicle-mounted device.

[0138] like Fig. 10D As shown, 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 that your vehicle-mounted device is shared with your family members, so that your family members can use distributed services (such as super desktop, super terminal) to link 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 receives the shared vehicle-mounted device; the add member control 508 is used to add users who share the vehicle-mounted device.

[0139] like Fig.10E and Fig.10F As shown, when the shared device 505 is selected, the device display area 503 displays a smart screen card 508; in response to the user clicking the card 508, the terminal device 100 displays the sharing details interface 53 of the smart screen. The sharing details interface 53 includes prompt information 509 and prompt information 510. The prompt information 509 is used to indicate the sharer of the smart screen, that is, Emma; the 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, super terminal) to link with the smart screen.

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

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

[0142] In the embodiment of the present application, exemplary embodiments of the terminal device 100 include but are not limited to An electronic device running Harmony OS or other operating systems. The following description will be made by taking the operating system of the terminal device 100 as Harmony OS as an example. Fig.11 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 be referred to Fig.11 The relevant description will not be repeated here.

[0143] In some embodiments, the Hongmeng 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.

[0144] like Fig.11 As shown, the kernel layer 240 is a layer between hardware and software. The kernel layer includes a kernel abstract layer (KAL) and a driver subsystem. KAL includes multiple kernels, such as the Linux kernel of the Linux system, LiteOS, a lightweight IoT system kernel, etc. The driver subsystem may include a hardware driver framework (HDF). The hardware driver framework can provide unified peripheral access capabilities and a driver development and management framework. The kernel layer of multiple kernels can select the corresponding kernel for processing according to the needs of the system.

[0145] 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:

[0146] System basic capability subsystem set: provides basic capabilities for the operation, scheduling, migration and other operations of distributed applications on multiple devices of Hongmeng system. It may include distributed soft bus, distributed data management, distributed task scheduling, Ark multi-language runtime, public basic library, multi-mode input, graphics, security, artificial intelligence (AI), user program framework and other subsystems.

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

[0148] Enhanced software service subsystem set: Provides differentiated capability-enhanced software services for different devices for the Hongmeng system. It may include smart screen proprietary business, wearable proprietary business, and Internet of Things (IOT) proprietary business subsystems.

[0149] Hardware service subsystem set: Provides hardware services for Hongmeng system. It may include location services, biometric recognition, wearable proprietary hardware services, IOT proprietary hardware services and other subsystems.

[0150] The framework layer provides multi-language user program frameworks and capability frameworks in Java, C, C++, JS, and other languages ​​for Hongmeng system application development, two user interface (UI) frameworks (including the JavaUI framework for Java language and the JS UI framework for JS language), and multi-language framework application programming interfaces (APIs) open to various software and hardware services. Depending on the degree of componentization of the system, the APIs supported by Hongmeng system devices will also vary.

[0151] 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 desktops, control bars, 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 applications in the Hongmeng system. For the specific implementation of the smart home app, please refer to the relevant description of the aforementioned APP1.

[0152] 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, 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.

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

[0154] It is understandable that the above Fig.11The system architecture shown does not constitute a limitation of the system architecture of HarmonyOS. In other embodiments, HarmonyOS 200 may have more features than those described above. Fig.11 The structure shown may be more or less system architecture structures, or other forms of system architecture, which is not limited here.

[0155] In combination with the above embodiments, Fig.12 The system architecture of a multi-device collaborative system provided by an embodiment of the present application is shown.

[0156] like Fig.12 As shown, the above-mentioned 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.

[0157] Server 300 includes a device cloud and a family service. The device cloud is used to manage the device list bound to each account, and to send the authorization information of the receiving device to the shared device during the credit authorization phase (for example, the user identification (UID) of the account 2 of the receiving device), and to send the authorization information of the shared device to the receiving device (for example, the unique device identifier (UDID) of the shared device, the UID of the account 1 to which the shared device belongs (i.e., the account of the person who shares the shared device)).

[0158] The end-side equipment includes cloud service end-side supporting facilities, distributed services, distributed collaborative architecture, free interconnection module, protocol stack and short-range communication module. The end-side supporting facilities include SNS kit and authorization information management module. SNS kit can provide friends and group services based on Huawei account. After one installation, it has all the basic capabilities of Huawei mobile services, including friend messages, system notification numbers and family sharing services. The authorization information management module is used to manage the received authorization information.

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

[0160] The distributed collaborative architecture includes distributed controls, distributed scene optimization API, service discovery and filtering, distributed business management, collaborative configuration center, and cross-device collaborative services. The distributed collaborative architecture provides support for the realization of distributed business.

[0161] The free interconnection module includes DM, soft bus and Hichain. The distributed soft bus is the communication base of distributed devices, providing a unified distributed communication capability for the interconnection between devices. Based on the distributed soft bus, other devices around can be automatically discovered and connected to form a network, that is, automatic networking. Hichain is a protocol mechanism to achieve device interconnection security. It can authenticate two devices based on the authorization information of the two devices at both ends to achieve end-to-end data encryption.

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

[0163] 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. The input operation 1 is used to view the device display interface of the account 1. The device display interface is used to display the device list of the shareable devices of the account 1.

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

[0165] 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 a device list of sharable devices displayed in the device display interface.

[0166] In some embodiments, the device display interface is used to display the devices in the family group 1 created by the account 1. FIG. 3A to FIG. 3D , the family group 1 is "Mark's home" in the smart life application, the device display interface is the home page 12 of the smart life application, and the home page 12 displays the home devices of "Mark's home", and the home devices of "Mark's home" can be shared with family members who join "Mark's home". For example, refer to FIG. 10B to FIG. 10C , account 1 is a Huawei account, family group 1 is the family sharing group of the Huawei account in "System Settings", and the device display interface is the family sharing interface 36 or the shared device interface 51 in "System Settings". The family sharing interface 36 and the shared device interface 51 display the shareable family devices bound to account 1.

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

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

[0169] S12. The home service request of server 300 sends request 1 to the device cloud of server 300 to request to query the device list 1 of account 1.

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

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

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

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

[0174] In some embodiments, the SNS Kit of the 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 the terminal device 200. In some embodiments, the terminal device 100 only shares some devices bound to account 1 as sharable devices with other accounts, and the SNS Kit of the terminal device 100 filters out the above sharable devices from the device list 1 according to preset rules.

[0175] 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. The user 1 can view the devices through the device display interface.

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

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

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

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

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

[0181] In the 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 shared 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.

[0182] 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).

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

[0184] In some embodiments, account 1 shares multiple shared devices (e.g., shared device 1) with account 2, and 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, the 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.

[0185] 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., the account 1 logged in by the terminal device 200), and the UID of the recipient of the shared device 1 (i.e., the account 2 logged in by the terminal device 200).

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

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

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

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

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

[0191] In some embodiments, the user confirmation information includes a UDID list 2 of shared devices (e.g., shared device 1) accepted by the user and a UID of the sharer of the shared device (i.e., account 1 logged in by 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.

[0192] In some embodiments, the SNS kit of the terminal device 200 displays a device sharing authorization box for each shared device indicated by the above UDID list; user 2 (i.e., account 2) confirms whether to accept sharing for each shared device sharing authorization box. For each shared device (e.g., shared device 1) that is confirmed to be accepted, 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 to accept 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).

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

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

[0195] S26. The home service of server 300 transmits authorization information 1 to the device cloud of server 300. 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).

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

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

[0198] 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) that receive the sharing device 1.

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

[0200] 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-distance communication module 1 according to the authorization information of the newly added account 2, and the filter 1 is used to filter out the messages from the account 2 sent through the short-distance communication module 1.

[0201] 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).

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

[0203] 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 accepts the shared device, so as to be used for the subsequent self-organizing network between the terminal device 200 and the shared device 1.

[0204] S31. The authorization information management of the terminal device 200 sends a notification message to the soft bus to notify the shared device of the change in the authorization information sending, including the addition of the authorization information of the shared device 1.

[0205] 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 the messages sent to the shared device 1 through the short-range communication module 1.

[0206] 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 a self-organizing network. Specifically, it can include steps S41 to S48.

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

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

[0209] 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 the account 2; after the short-range communication module 1 of the shared device 1 scans the above discovery signal, it is determined that the discovery 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 discovery signal, then the terminal device 200 is determined to be a trusted device, and a connection request is sent 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 connection request, if it is determined that the above 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 by the connection request, and the UID of the sharer's account set is the same as the UID carried by the connection request, then the shared device 1 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.

[0210] 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 the account 2, a short-range communication connection can be established with the terminal device 200 logged in to the 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-mentioned 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 is the same as the UID carried by the connection request, and the UID of the sharer's account 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, then 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.

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

[0212] S44. 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.

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

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

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

[0216] 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 a subsequent communication encryption key between the two devices, thereby achieving secure communication.

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

[0218] It should be noted that when multiple devices of the same account are close to each other, they will automatically connect and authenticate, that is, self-organizing network; after success, the devices of the same account can collaborate to realize distributed services. Two devices that are not of the same account cannot self-organize network, 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 the authorization information of the other party and update the filter according to the authorization information of the other party, so that the shared device 1 and the terminal device 200 have a credit relationship, that is, when the two devices are close to each other, they can automatically establish a close connection and authentication to complete automatic networking; thus, the shared device 1 and the terminal device 200 that are not of the same account can also collaborate to realize distributed services.

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

[0220] Distributed services: HyperTerminal

[0221] In some embodiments, the master device (e.g., terminal device 100) and the electronic device set formed by the devices bound to the master device (e.g., smart screen, vehicle-mounted device, speaker, etc.) can be regarded as a distributed collaborative virtual super terminal. The master device can schedule other devices in the super terminal to perform task collaboration, task transfer, and task continuation.

[0222] For example, taking the shared device 1 as a vehicle-mounted device, FIG. 14A to FIG. 14C The relevant user interface of the hyperterminal is shown.

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

[0224] like Fig.14A As shown, when the terminal device 200 displays the main interface 62, it receives a sliding operation performed by the user on the status bar; in response to the sliding operation, the terminal device 200 displays Fig. 14BThe control center interface 62 shown includes shortcut icons of multiple commonly used functions (eg, a WLAN icon, a Bluetooth icon, an NFC icon, etc.).

[0225] like Fig. 14B As shown, the control center interface 52 may also include a card of a hyperterminal, in which a control 606 is displayed. Fig. 14B and Fig. 14C As shown, in response to the operation of clicking the control 606, the terminal device 200 displays the hyperterminal interface 63, which includes an icon 601 of the terminal device 200 and icons of detected trusted devices, such as an icon 603 of a laptop and an icon 602 of a vehicle-mounted device. The embodiment of the present application does not specifically limit the method of opening the hyperterminal interface 63. FIG. 14A to FIG. 14C The opening method shown is only an example.

[0226] In some embodiments, the above-mentioned trusted device is a device currently networking with the terminal device 200, that is, a device that establishes a short-range communication connection and completes authentication with the terminal device 200. The above-mentioned trusted device can be a device with the same account as the terminal device 200 (such as the above-mentioned notebook), or a shared device that establishes a trust relationship with the terminal device 200 (such as the above-mentioned vehicle-mounted device).

[0227] In the 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 identifier (eg, UDID) of the shared device shared by other accounts; Fig. 14C As shown, if the device identification of the shared device stored in the authorization information management module includes the device identification of the above-mentioned vehicle-mounted device, the terminal device 200 determines that the above-mentioned vehicle-mounted device is a shared device, and displays a sharing identification 605 on / around the icon 602 of the vehicle-mounted device 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 (such as 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 (such as the above-mentioned 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 / around the icon 603 of the vehicle-mounted device. Exemplarily, as Fig. 14C As shown, the user name 604 of account 1, namely “Mark”, is displayed around the in-vehicle device icon 603 to indicate that the in-vehicle device is a device shared by the user “Mark”.

[0228] For example, Fig. 14C and Fig.14DAs shown, when 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 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 a short-range communication connection; Fig.14E As shown, the vehicle-mounted device displays the display screen of the terminal device 200 in the projection window based on the projection data. In one implementation, in response to the drag operation, the terminal device 200 sends the application data of the super desktop to the vehicle-mounted device through the short-range communication connection; Fig.14F As shown, the vehicle-mounted device displays the application icons installed by the terminal device 200 based on the above application data in the display area 613 of the user interface 71. In this way, the vehicle-mounted device and the terminal device 200 that are not in the same account can also cooperate to realize the distributed service based on the close distance, and a single sharing operation can realize the long-term and efficient experience of the super terminal between devices with different accounts.

[0229] It can be understood that according to the prior art, account 1 is bound to the above-mentioned vehicle-mounted device, and the terminal device 200 logged in to account 2 is not bound to the above-mentioned vehicle-mounted device, and the above-mentioned vehicle-mounted device and the terminal device 200 are not the same account devices. When the terminal device 200 is close to the vehicle-mounted device, the two devices cannot automatically establish a connection, and thus cannot collaborate to realize the distributed services of the super terminal.

[0230] Distributed Services: Super Desktop

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

[0232] For example, taking the shared device 1 as a vehicle-mounted device, FIG. 15A to FIG. 15C The relevant user interface of the hyperterminal is shown.

[0233] For example, Fig.14D and Fig.14F As shown, 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 for operation through the hyperterminal on the terminal device 200, and the desktop application of the terminal device 200 can be viewed and used on the vehicle-mounted device.

[0234] For example, Fig.15A As shown, 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.

[0235] In some embodiments, when the vehicle-mounted device detects an input operation that triggers the super desktop, the vehicle-mounted device displays Fig.15A The user interface 71 shown detects nearby trusted devices, and displays one or more trusted devices detected, such as device options 614 of the terminal device 200 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 vehicle-mounted device.

[0236] like Fig.15A and Fig. 15B As shown, the vehicle-mounted device detects the user's operation (e.g., click operation) on the device option 614 of the terminal device 200, and the vehicle-mounted device obtains the application data transmitted by the terminal device 200 through the 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 that are not in the same account can also realize the coordinated distributed service based on short distance, and a shared operation can realize the long-term and efficient experience of the super desktop between devices with different accounts.

[0237] In some embodiments, when a user operation (e.g., 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; the terminal device 200 displays a confirmation box 621 based on the request message. 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.

[0238] Distributed services: audio projection

[0239] For example, taking the shared device 1 as a "speaker", Fig.16 The relevant user interface of audio projection is shown.

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

[0241] In some embodiments, the "system settings" of the terminal device 200 is provided with a projection control portal, through which the terminal device 200 detects nearby trusted devices and displays Fig.16The audio projection control interface 81 shown. The audio projection control interface 81 includes a broadcast control center component 631, and icons and selection controls for detecting one or more trusted devices, such as an icon 632 of a "speaker" and a selection control 633. 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.

[0242] 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; the account information of the account to which the "speaker" belongs, such as the user name 635, can also be displayed to indicate that the user sharing the "speaker" is Mark.

[0243] like Fig.16 As shown, the terminal device 200 detects the user's operation (such as clicking) 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 in the same account can also collaborate to implement distributed services based on short distances. A single shared operation can achieve long-term and efficient audio projection experience between devices with different accounts, effectively improving the user experience.

[0244] Distributed services: screen projection

[0245] For example, taking the shared device 1 as a "smart screen", FIG. 17A to FIG. 17C The relevant user interface of screen projection is shown.

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

[0247] 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; the account information of the account to which the "smart screen" belongs, such as the user name 644, can also be displayed to indicate that the user sharing the "smart screen" is Mark.

[0248] like Fig.17A and Fig. 17B As shown, the terminal device 200 detects the user's operation (such as clicking) on ​​the icon 643 of the "smart screen", and 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; Fig. 17C As shown, 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 the projection. FIG. 17A to FIG. 17C This is just an example. In this way, the smart screen and terminal device 200 that are not in the same account can also collaborate to realize distributed services based on close proximity. A single sharing operation can achieve long-term and efficient screen projection experience between devices with different accounts. In the existing solution, screen projection between devices with different accounts requires manual verification by the user, such as entering a screen projection PIN code.

[0249] Distributed business: a trick

[0250] For example, taking the shared device 1 as a "smart screen", Fig.18A and Fig.18B The relevant user interface of "Move One Move" is shown.

[0251] In some embodiments, Fig.18A As shown, the user holds the terminal device 200 and performs the preset gesture of the "Move" function. After the terminal device 200 detects the preset gesture, it determines the device (such as a smart screen) pointed by the preset gesture, 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; Fig.18B As shown, a service card for the current application, such as service card 651, is displayed based on the above application data to control the current application of the smart screen.

[0252] In this way, the smart screen and the terminal device 200 that are not in the same account can also collaborate to realize the distributed service based on close distance, that is, one move. In addition, when the existing "one move" function is shared with family members, there is usually a limit on the length of credit, while in the solution provided in the embodiment of the present application, the smart screen and the terminal device 200 have a credit relationship and there is no limit on the length of credit.

[0253] Distributed business: auxiliary input

[0254] For example, taking the shared device 1 as a "smart screen", FIG. 19A to FIG. 19C The relevant user interface of auxiliary input is shown.

[0255] For example, FIG. 19A to FIG. 19C A user interface related to auxiliary input is shown. Fig.19A As shown, when the smart screen detects that the user wants to input information, for example, when an operation is detected 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. Fig.19B As shown, the terminal device 200 displays the push information 701. Fig.19B and Fig.19C As shown, in response to the user clicking on the push information 701, the terminal device 200 can display the keyboard 702 and the information input box 703, and the information input box 702 includes the information input field 704, the cancel control 705 and the 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 field 704; in response to the user clicking on 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 on the confirmation control 706, the terminal device 200 sends the information in the information input field 703 to the "smart screen" through the short-range communication connection.

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

[0257] In combination with the aforementioned 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 a first electronic device; the method includes steps S101 to S107.

[0258] In the 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.

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

[0260] In some embodiments, 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. For example, refer to the above-mentioned interface embodiment 1.

[0261] In some embodiments, the first account creates a first group, 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.

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

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

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

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

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

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

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

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

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

[0271] In some embodiments, the method further includes: the first terminal detects a second operation, 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; the second electronic device is a device shared by other accounts to the first account. In the embodiment of the present application, the second terminal can also share the device bound to account 2 with account 1.

[0272] In some embodiments, the method further includes: the second terminal sets a second filter based on the information of the first electronic device, 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. In the embodiment of the present application, the second filter can be the aforementioned filter 2.

[0273] In some embodiments, 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. Optionally, the second identifier may be a user name corresponding to the first account.

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

[0275] Exemplary, reference FIG. 14A to FIG. 14F , the icon of the first electronic device may be the icon 602 of the vehicle-mounted device. Fig.16 , the icon of the first electronic device may be a speaker icon 632, and the third operation may include an operation on a selection control 633 corresponding to the icon 632. Fig.15A , the icon of the first electronic device may be the icon 614 of the terminal device 200. Fig. 17B According to the relevant description, the icon of the first electronic device can be the icon 643 of the smart screen.

[0276] 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 screen projection data to the first electronic device through a short-range communication connection; the first electronic device displays the projection screen based on the screen 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.

[0277] In some embodiments, the second terminal cooperates with the first electronic device to perform the first distributed service, including: the first electronic device displays the first input box; the first electronic device sends a first request to the second terminal through a short-distance communication connection; the first request is used to request the second terminal to assist in inputting information; the second terminal displays the 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-distance communication connection; the first electronic device displays the first information in the first input box. For example, refer to FIG. 19A to FIG. 19C Description of auxiliary information input.

[0278] The following introduces the structure of a terminal device 100 provided in an embodiment of the present application. Fig. 20 A schematic structural diagram of the terminal device 100 is shown.

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

[0280] It is to 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 in the figure, or combine some components, or split some 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.

[0281] 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 processor (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), etc. Different processing units may be independent devices or integrated into one or more processors.

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

[0283] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0284] In some embodiments, the processor 110 may include one or more interfaces. The interface 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, etc.

[0285] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple groups of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through the I2C interface, so that the processor 110 communicates with the touch sensor 180K through the I2C bus interface, thereby realizing the touch function of the terminal device 200.

[0286] 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 achieve communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 via the I2S interface to achieve the function of answering a call through a Bluetooth headset.

[0287] 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 to realize the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0288] The UART interface is a universal serial data bus for asynchronous communication. The 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 generally 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 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

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

[0290] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the 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.

[0291] The USB interface 130 is an interface that complies with the USB standard specification, and specifically can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the terminal device 200, and can also be used to transmit data between the terminal device 200 and peripheral devices. It can also be used to connect headphones to play audio through the headphones. The interface can also be used to connect other electronic devices, such as AR devices, etc.

[0292] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present invention is only a schematic 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 different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

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

[0294] 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 supplies power to the processor 110, the internal memory 121, the display screen 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 number, battery health status (leakage, impedance), etc. 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.

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

[0296] 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 the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

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

[0298] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent 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 the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a 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.

[0299] 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 integrating 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, modulate the frequency, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0300] 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).

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

[0302] The display screen 194 is used to display images, videos, etc. The 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), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the terminal device 200 may include 1 or N display screens 194, where N is a positive integer greater than 1.

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

[0304] The ISP is used to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, and the light is transmitted to the camera photosensitive element through the lens. The light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converts it into an image visible to the naked eye. The ISP can also perform algorithm optimization on the noise and brightness of the image. The ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0305] 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 optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted 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.

[0306] The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the terminal device 200 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0307] Video codecs are used to compress or decompress digital videos. The terminal device 200 may support one or more video codecs. Thus, the terminal device 200 may play or record videos in multiple coding formats, such as moving picture experts group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0308] NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of the terminal device 200 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

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

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

[0311] 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 unit potential level; universal flash storage (UFS), embedded multi media card (eMMC), etc. according to the storage specification.

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

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

[0314] 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 through the external memory interface 120 to implement a data storage function. For example, files such as music and videos are stored in the external non-volatile memory.

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

[0316] 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 arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110.

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

[0318] 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 voice can be received by placing the receiver 170B close to the ear.

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

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

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

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

[0323] 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 positioning and navigation.

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

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

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

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

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

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

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

[0331] The touch sensor 180K is also called a "touch control device". The touch sensor 180K can be set on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also called a "touch control screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the terminal device 200, which is different from the position of the display screen 194.

[0332] 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 block of a human vocal part.

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

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

[0335] Indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0336] 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 the SIM card interface 195 or removing the SIM card from the SIM card interface 195 .

[0337] The following introduces the structure of a server 300 provided in an embodiment of the present application. Fig.21 The structure of a server 300 provided in an embodiment of the present application is exemplified.

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

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

[0340] In some embodiments of the present application, the transmitter 1005 and the receiver 1006 can be regarded as a wireless modem. In the server 300, the number of the transmitter 1005 and the receiver 1006 can be one or more. The antenna 1008 can be used to convert the electromagnetic energy in the transmission line into electromagnetic waves in the free space, or convert the electromagnetic waves in the free space into electromagnetic energy in the transmission line. The coupler 1007 is used to divide the mobile communication signal received by the antenna 1008 into multiple paths and distribute them to multiple receivers 1006.

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

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

[0343] The processor 1001 can be used to read and execute computer-readable instructions. Specifically, the processor 1001 can be used to call a program stored in the memory 1002, such as an implementation program of 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.

[0344] It should be noted that Fig.21 The server 300 shown 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.

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

[0346] The various implementation modes of the present application can be combined arbitrarily to achieve different technical effects.

[0347] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part 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, the process or function described in the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can 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. The available medium can 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 disk (SSD)), etc.

[0348] Those skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by computer programs to instruct related hardware, and the programs can be stored in computer-readable storage media. When the programs are executed, they can include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

[0349] In short, the above description is only an embodiment of the technical solution of the present invention, and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present invention shall be included in the protection scope 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 device; and the second electronic device is a device shared by other accounts with the first account.

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