Equipment sharing method and system, equipment and computer readable storage medium

Abstract

The embodiment of the invention discloses a device sharing method and system, a device and a computer readable storage medium, the system comprises a first device, a cloud server, a second device and a third device, the first device and the second device log in a first account, and the third device logs in a second account; the target message is sent to the cloud server, so that the cloud server transmits first credible authorization information to the second device and transmits second credible authorization information to the third device, the first credible authorization information comprises a device security credential of the third device, and the second credible authorization information comprises a device security credential of the second device; and the second equipment and the third equipment perform equipment credible authentication according to the equipment security credential of the opposite-end equipment. In this way, the second device and the third device can carry out credible authentication on the different account number devices according to the device security credentials, authentication can be carried out without inputting pin codes or scanning codes, operation is easy and convenient, and user experience is better.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a device sharing method, system, device and computer-readable storage medium. Background Art

[0002] With the continuous development of terminal technology and the increasing popularity of terminal devices, the types of terminal devices owned by users are becoming more and more diverse, and the number of terminal devices owned is also increasing.

[0003] Currently, when a user shares or shares a terminal device he owns with other users (i.e., device sharing), since the accounts logged in to the terminal devices of different users are different, the terminal devices of other users need to complete trusted authentication through authentication methods such as scanning a code or entering a pin code before they can establish a connection with the terminal device shared by the user, thereby allowing other users to use the terminal device shared by the user.

[0004] However, in the device sharing scenario, when establishing a connection between other users' terminal devices (i.e., devices with different accounts) and the terminal devices shared by the user (i.e., shared devices), the user is required to manually scan the QR code or manually enter the PIN code for device trusted authentication. The operation process is complicated and the user experience is poor. Summary of the invention

[0005] The embodiments of the present application provide a device sharing method, system, device and computer-readable storage medium, which can solve the problem that in the process of establishing a connection between a device with a different account and a shared device, the user needs to manually scan a QR code or manually enter a PIN code for device trusted authentication, which results in a complicated operation process and a poor user experience.

[0006] In a first aspect, an embodiment of the present application provides a device sharing system, including a first device, a cloud server, a second device, and a third device, wherein the first device and the second device log in to a first account, and the third device logs in to the second account, and the first account is different from the second account;

[0007] The first device is used to: in response to one or more operations, send a target message to the cloud server, where the target message includes first information indicating the first account and second information indicating the second account, and the first operation is used to share the second device with the second account;

[0008] The cloud server is used to: transmit first trusted authorization information to the second device and transmit second trusted authorization information to the third device based on the first information and the second information; the first trusted authorization information includes the association information between the device identification of the third device and the security credentials of the first device; the second trusted authorization information includes the association information between the device identification of the second device and the security credentials of the second device; the first device security credentials are the device security credentials of the third device, and the second device security credentials are the device security credentials of the second device.

[0009] The second device is used to: receive first trusted authorization information from the cloud server and store the first trusted authorization information, where the first trusted authorization information is authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device;

[0010] The third device is used to: receive the second trusted authorization information from the cloud server and store the second trusted authorization information; the second trusted authorization information is the authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device.

[0011] As can be seen from the above, after the user inputs one or more operations to the first device to authorize the second device and the second account to have a trusted relationship, the first device responds to the one or more operations and sends a target message to the cloud server; the cloud server can learn from the target message that the device of the first account and the device of the second account have a trusted authorization relationship, and based on the trusted authorization relationship, generate the association information of the device identification of the second device and the security credentials of the second device, as well as the association information between the device identification of the third device and the security credentials of the first device, and transmit the second device and the third device accordingly to reflect the trusted authorization relationship on the cloud side through the device security credentials on the end side. In this way, the second device (i.e., the shared device) and the third device (i.e., the device with a different account) can authenticate whether the opposite device is trustworthy based on the device security credentials of the opposite device, and users of the devices with different accounts do not need to perform device trusted authentication by entering a pin code or scanning a QR code, etc., which makes the operation simpler and provides a better user experience.

[0012] In some possible implementations of the first aspect, the first device is specifically used to: display a group member adding interface in response to a first operation, the first operation being an operation on a group member invitation control; receive a second operation acting on the group member adding interface, the second operation being used to determine a user invited to join the group; send a target message to a cloud server in response to a third operation; the first information includes an identifier of the group owner or information of a first account, the second information includes a member identifier of the invited user in the group or information of a second account, the group owner is the first account, the account of the user invited to join the group is the second account, and the second device is a device in the group.

[0013] In this way, the group owner can share the devices in the group with other users (i.e., the second account) by inviting other users (i.e., the second account) to join the group, thereby supporting the sharing of devices in the group with devices with different accounts in the group scenario, and enabling devices with different accounts to use the devices in the group (i.e., shared devices) as seamlessly and conveniently as devices with the same account, providing a better user experience.

[0014] In some possible implementations of the first aspect, the first device is specifically used to: determine the second device from multiple devices logged into the first account in response to the fourth operation, the fourth operation is used to determine the shared device; in response to the fifth operation, send a target message to the cloud server, the fifth operation is an operation for the member sharing option or at least one user information displayed on the shared member selection interface, the fifth operation is used to determine the user who shares the second device, the account of the user who shares the second device is the second account; the first information includes the information of the second device or the information of the first account, and the second information includes the information of the second account. In this way, the user can specify to share a certain device with other users (i.e., the second account), and enable devices with different accounts to use the shared device seamlessly and conveniently like devices with the same account, and the user experience is better.

[0015] In some possible implementations of the first aspect, the cloud server is specifically used to: obtain device information of the second device based on the first information, and generate association information between a device identifier of the second device and the security credentials of the second device based on the device information of the second device; obtain device information of the third device based on the second information, and generate association information between the device identifier of the third device and the security credentials of the first device based on the device information of the three devices.

[0016] In some possible implementations of the first aspect, the cloud server is also used to: obtain device information of the first device based on the first information, and generate association information between the device identification of the first device and the third device security credential based on the device information of the second device; the third device security credential is the device security credential of the first device.

[0017] The cloud server is specifically used to: generate second trusted authorization information based on the association information between the device identification of the second device and the security credentials of the second device and the association information between the device identification of the first device and the security credentials of the third device; transmit the second trusted authorization information to the third device; at this time, the second trusted authorization information is the authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device, and can also be the authentication information used to authenticate the first device during the process of establishing a connection between the first device and the third device.

[0018] The cloud server is further used to: transmit first trusted authorization information to the first device;

[0019] The first device is also used to: receive first trusted authorization information from the cloud server and store the first trusted authorization information. At this time, the first trusted authorization information is authentication information used to authenticate the third device during the process of establishing a connection between the first device and the third device.

[0020] In this implementation, after the device sharing operation, not only the device security credentials of the second device and the third device are generated, but also the third device security credentials of the first device are generated, and the third device security credentials of the first device are transmitted to the third device, and the first device security credentials of the third device are transmitted to the first device, so that the first device and the third device (i.e., devices with different accounts) can also perform device trusted authentication based on the device security credentials of the opposite device, and establish a trusted connection with the devices with different accounts quickly and conveniently, providing a better user experience.

[0021] In some possible implementations of the first aspect, the device information of the first device, the second device, and the third device may include a device identifier and at least one of the following: device security level information, device model, device version information, and device inherent attribute information. Among them, at least one of the device security level information, device model, device version information, and device inherent attribute information is used to generate a device security credential. In this implementation, the device security credential is generated based on inherent information that remains unchanged for a long time, such as the device security level information, device model, device version information, and device inherent attribute information, so that the generated device security credential can be valid for a long time.

[0022] In some possible implementations of the first aspect, the cloud server is specifically used to: obtain the association information between the device identification of the second device and the second device security credential based on the first information; generate the second trusted authorization information based on the association information between the device identification of the second device and the second device security credential; obtain the association information between the device identification of the third device and the first device security credential based on the second information; generate the first trusted authorization information based on the association information between the device identification of the third device and the first device security credential; transmit the second trusted authorization information to the third device, and transmit the first trusted authorization information to the second device. In this implementation, the cloud server can store the pre-generated device security credentials of each device, and based on the information of the first account and the information of the second account, the device security credentials and device identification of each device can be queried, and the association relationship between the device identification and the device security credential is generated based on this.

[0023] In some possible implementations of the first aspect, the cloud server is further used to: obtain, according to the first information, association information between a device identification of the first device and a security credential of the third device; transmit the first trusted authorization information to the first device;

[0024] The cloud server is specifically used to generate second trusted authorization information according to association information between the device identification of the second device and the second device security credential and association information between the device identification of the first device and the third device security credential.

[0025] In some possible implementations of the first aspect, the second trusted authorization information further includes association information between a device identification of the first device and a security credential of the third device;

[0026] The first device is also used to: obtain wireless broadcast information of the third device, the wireless broadcast message of the third device includes the device identification of the third device; if the first device security credential corresponding to the device identification of the third device is queried from the first trusted authorization information, the third device is determined to be a trusted device.

[0027] After the third device determines that the first device is trustworthy based on the second trusted authorization information, that is, after authenticating that the devices at both ends are trustworthy, the first device and the third device establish a trusted communication connection. At this time, the second trusted authorization information is not only the authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device, but also the authentication information used to authenticate the first device during the process of establishing a connection between the first device and the third device. Of course, in other embodiments, a third trusted authorization information can also be generated separately, and the third trusted authorization information can be sent to the third device. The third trusted authorization information is the authentication information used to authenticate the first device during the process of establishing a connection between the first device and the third device. In this way, the first device and the third device (i.e., different account devices) can also perform device trusted authentication based on the device security credentials, quickly and easily establish a trusted connection, and provide a better user experience.

[0028] In some possible implementations of the first aspect, the second device is also used to: obtain wireless broadcast information of the third device, the wireless broadcast message of the third device includes the device identification of the third device; if the first device security credentials corresponding to the device identification of the third device are queried from the first trusted authorization information, the third device is determined to be a trusted device; at this time, the second device can initiate a connection to the third device, and the third device receives the connection request from the second device. After the third device determines that the second device is trustworthy based on the second trusted authorization information, that is, after authenticating that the devices at both ends are trustworthy, the second device and the third device establish a trusted communication connection. In this way, the second device (i.e., a shared device) and the third device (i.e., a different account device) can authenticate whether the peer device is trustworthy based on the device security credentials of the peer device, and quickly and easily establish a trusted connection, providing a better user experience.

[0029] Or, the third device is also used to: obtain the wireless broadcast information of the second device, the wireless broadcast information of the second device includes the device identification of the second device; if the second device security credentials corresponding to the device identification of the second device are queried from the second trusted authorization information, the second device is determined to be a trusted device. At this time, the third device can initiate a connection to the second device, and the second device receives the connection request from the third device.

[0030] In some possible implementations of the first aspect, the second device is further configured to: automatically send a connection request to a trusted third device; or, if there are at least two trusted third devices, display the at least two trusted third devices in a list of connectable devices, and in response to a user's selection operation on the list of connectable devices, send a connection request to the trusted third device specified by the selection operation. In this way, the second device (i.e., the shared device) can actively initiate a connection to a device with a different account based on the association information between the device credentials and the device identifier of the third device.

[0031] In some possible implementations of the first aspect, when the second device displays the list of connectable devices, the user information and device information of the user to which the connectable device belongs are displayed. For example, in a family group device sharing scenario, when the large-screen device displays the list of connectable devices, it displays Xiao Ming's Mate 30. The large-screen device locally stores the association relationship between the user information and the device information.

[0032] In some possible implementations of the first aspect, the first device is further used to: in response to a sixth operation, send a cancel sharing instruction to the cloud server, where the sixth operation is used to cancel sharing of the second device with the second account;

[0033] The cloud server is further configured to: receive a cancel sharing instruction from the first device, delete the authorization relationship between the second account and the second device in response to the cancel sharing instruction, and send a first delete instruction to the second device and a second delete instruction to the third device;

[0034] The second device is used to: receive a first deletion instruction from the cloud server, and delete the first trusted authorization information stored locally in response to the first deletion instruction;

[0035] The third device is used to: receive a second deletion instruction from the cloud server, and delete the second trusted authorization information stored locally in response to the second deletion instruction.

[0036] In this implementation, when the user of the first device cancels device sharing, the trusted authorization information of the cloud server and the device security credentials stored on the terminal side can be deleted in a timely manner.

[0037] In some possible implementations of the first aspect, the first device and the second device are the same device. In this case, the first device uses itself as a shared device and shares it with the second account for use.

[0038] In some possible implementations of the first aspect, if the first device, the second device, or the third device is powered on again after being powered off, the first device, the second device, or the third device is further used to: after sending a query instruction to the cloud server, receive response information returned by the cloud server to the query instruction, where the query instruction is used to query whether the device sharing relationship is updated. In this way, it can be avoided that the device sharing relationship cannot be updated in time after a change (for example, cancellation of sharing) occurs during the device power-off period.

[0039] In a second aspect, an embodiment of the present application provides a device sharing method, which is applied to a first device, and the method includes:

[0040] In response to a first operation, displaying a group member adding interface, the first operation being an operation on a group member invitation control;

[0041] In response to the second operation, a target message is sent to the cloud server, the target message is used to trigger the cloud server to transmit the first trusted authorization information to the second device, and to transmit the second trusted authorization information to the third device; the second operation is an operation on the member invitation option or at least one user information displayed on the group member adding interface, and the second operation is used to determine the user invited to join the group;

[0042] The target message includes first information for indicating a first account and second information for indicating a second account, the group owner is the first account, the user invited to join the group is the second account; the second device is a device in the group;

[0043] The first device and the second device log in to the first account, and the third device logs in to the second account, and the first account and the second account are different;

[0044] The first trusted authorization information includes association information between a device identification of the third device and security credentials of the first device;

[0045] The second trusted authorization information includes association information between the device identification of the second device and the security credentials of the second device;

[0046] The first trusted authorization information is authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device, and the second trusted authorization information is authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device.

[0047] In some possible implementations of the second aspect, the first information includes an identifier of a group owner or information of a first account, and the second information includes a member identifier of the invited user in the group or information of a second account.

[0048] In a third aspect, an embodiment of the present application provides a device sharing method, which is applied to a first device, and the method includes:

[0049] In response to a first operation, determining a second device from a plurality of devices logged into the first account, the first operation being used to determine a shared device;

[0050] In response to the second operation, a target message is sent to the cloud server, the target message is used to trigger the cloud server to transmit the first trusted authorization information to the second device, and to transmit the second trusted authorization information to the third device; the target message includes first information for indicating the first account and second information for indicating the second account; the second operation is an operation on the member sharing option or at least one user information displayed on the sharing member selection interface, and the second operation is used to determine the user who shares the second device, and the user who shares the second device is the second account;

[0051] The first device and the second device log in to the first account, and the third device logs in to the second account, and the first account and the second account are different;

[0052] The first trusted authorization information includes association information between a device identification of the third device and security credentials of the first device;

[0053] The second trusted authorization information includes association information between the device identification of the second device and the security credentials of the second device;

[0054] The first trusted authorization information is authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device, and the second trusted authorization information is authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device.

[0055] In some possible implementations of the third aspect, the first information includes information of the second device or information of the first account, and the second information includes information of the second account.

[0056] In some possible implementations of the second aspect or the third aspect, the group is a family group.

[0057] In some possible implementations of the second or third aspect, after sending the target message to the cloud server, the method also includes: in response to a third operation, sending a cancel sharing instruction to the cloud server, the third operation being used to cancel sharing of the second device with the second account, the cancel sharing instruction being used to trigger the cloud server to delete the authorization relationship between the second account and the second device, and sending a first deletion instruction to the second device and a second deletion instruction to the third device, the first deletion instruction being used to instruct the second device to delete the stored first trusted authorization information, and the second deletion instruction being used to instruct the third device to delete the stored second trusted authorization information.

[0058] In some possible implementations of the second aspect or the third aspect, the second trusted authorization information further includes association information between a device identifier of the first device and a security credential of the third device; and the method further includes:

[0059] Receive first trusted authorization information from a cloud server; obtain wireless broadcast information of a third device, the wireless broadcast message of the third device including a device identifier of the third device; if the first device security credential corresponding to the device identifier of the third device is queried from the first trusted authorization information, determine that the third device is a trusted device; after the third device determines that the first device is a trusted device based on the second trusted authorization information, establish a communication connection with the third device.

[0060] In a fourth aspect, an embodiment of the present application provides a device sharing method, which is applied to a cloud server, and the method includes:

[0061] receiving a target message from a first device, the target message including first information indicating a first account and second information indicating a second account, the first account and the second account being different, the target message being information sent by the first device in response to an operation of sharing the second device with the second account, the first device and the second device logging in to the first account;

[0062] According to the target message, the first trusted authorization information is transmitted to the second device, and the second trusted authorization information is transmitted to the third device, and the third device logs in to the second account;

[0063] The first trusted authorization information includes the association information between the device identification of the third device and the security credentials of the first device; the second trusted authorization information includes the association information between the device identification of the second device and the security credentials of the second device; the first trusted authorization information is the authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device, and the second trusted authorization information is the authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device.

[0064] In some possible implementations of the fourth aspect, transmitting the first trusted authorization information to the second device and transmitting the second trusted authorization information to the third device according to the target message include:

[0065] Acquire device information of the second device according to the first information, and generate association information between a device identifier of the second device and a security credential of the second device according to the device information of the second device;

[0066] Acquire device information of a third device according to the second information, and generate association information between a device identifier of the third device and the security credential of the first device according to the device information of the three devices;

[0067] Transmitting second trusted authorization information to a third device based on association information between a device identification of the second device and a security credential of the second device;

[0068] Based on the association information between the device identification of the third device and the security credential of the first device, the first trusted authorization information is transmitted to the second device.

[0069] In some possible implementations of the fourth aspect, the method further includes:

[0070] Acquire device information of the first device according to the first information, and generate association information between a device identifier of the first device and a security credential of the third device according to the device information of the second device;

[0071] Transmitting second trusted authorization information to a third device based on association information between a device identification and a device security credential of the second device includes:

[0072] generating second trusted authorization information according to association information between the device identification of the second device and the second device security credential and association information between the device identification of the first device and the third device security credential;

[0073] The second trusted authorization information is transmitted to the third device.

[0074] In some possible implementations of the fourth aspect, transmitting the first trusted authorization information to the second device and transmitting the second trusted authorization information to the third device according to the target message include:

[0075] Acquire association information between a device identifier of the second device and a security credential of the second device according to the first information;

[0076] Generate second trusted authorization information according to association information between a device identification of the second device and a security credential of the second device;

[0077] Acquire association information between a device identifier of a third device and a security credential of the first device according to the second information;

[0078] Generate first trusted authorization information according to association information between a device identification of the third device and the security credential of the first device;

[0079] The second trusted authorization information is transmitted to the third device, and the first trusted authorization information is transmitted to the second device.

[0080] In some possible implementations of the fourth aspect, the method further includes:

[0081] Acquire, according to the first information, association information between a device identification of the first device and a security credential of the third device;

[0082] Transmitting first trusted authorization information to the first device;

[0083] Generating second trusted authorization information according to the association information between the device identification of the second device and the security credential of the second device includes:

[0084] Second trusted authorization information is generated according to association information between the device identification of the second device and the second device security credential and association information between the device identification of the first device and the third device security credential.

[0085] In some possible implementations of the fourth aspect, the device information includes a device identification and at least one of the following: device security level information, device model, device version information, and device inherent attribute information.

[0086] In some possible implementations of the fourth aspect, the method further includes:

[0087] receiving a cancel sharing instruction from the first device, where the cancel sharing instruction is an instruction sent by the first device in response to canceling an operation of sharing the second device with the second account;

[0088] In response to the cancel sharing instruction, the authorization relationship between the second account and the second device is deleted, and a first deletion instruction is sent to the second device and a second deletion instruction is sent to the third device. The first deletion instruction is used to instruct the second device to delete the stored first trusted authorization information, and the second deletion instruction is used to instruct the third device to delete the stored second trusted authorization information.

[0089] In a fifth aspect, an embodiment of the present application provides a device sharing method, which is applied to a second device, and the method includes:

[0090] Receiving first trusted authorization information from the cloud server, the first trusted authorization information including association information between a device identifier of the third device and a security credential of the first device, the second device logging in to the first account, the third device logging in to the second account, the first account and the second account being different;

[0091] The first trusted authorization information is information sent by the cloud server according to the first information from the first device, the target message includes first information for indicating the first account and second information for indicating the second account, the target message is information sent by the first device in response to the first operation, and the first operation is used to share the second device with the second account; the first device logs in to the first account;

[0092] The first trusted authorization information is stored, where the first trusted authorization information is authentication information used to authenticate the third device during a process of establishing a connection between the second device and the third device.

[0093] In some possible implementations of the fifth aspect, the method further includes:

[0094] Acquire wireless broadcast information of a third device, where the wireless broadcast message of the third device includes a device identifier of the third device;

[0095] If the first device security credential corresponding to the device identification of the third device is queried from the first trusted authorization information, the third device is determined to be a trusted device;

[0096] Automatically send a connection request to a trusted third device; or, if there are at least two trusted third devices, display the at least two trusted third devices in a list of connectable devices, and in response to a user's selection operation on the list of connectable devices, send a connection request to the trusted third device specified in the selection operation.

[0097] In some possible implementations of the fifth aspect, the method also includes: receiving a first deletion instruction from a cloud server, and deleting the first trusted authorization information stored locally in response to the first deletion instruction; wherein the first deletion instruction is an instruction sent by the cloud server based on a cancel sharing instruction from the first device, and the cancel sharing instruction is an instruction sent by the first device in response to a sixth operation, and the sixth operation is used to cancel sharing of the second device with the second account.

[0098] In a sixth aspect, an embodiment of the present application provides a device sharing system, including a first device, a second device, and a third device, wherein the first device and the second device log in to a first account, and the third device logs in to the second account, and the first account is different from the second account;

[0099] The first device is used to: in response to a first operation, send a target message to a cloud server, the target message including first information indicating the first account and second information indicating the second account, the first operation is used to share the second device with the second account; the target message is used to trigger the cloud server to transmit the first trusted authorization information to the second device, and transmit the second trusted authorization information to the third device;

[0100] The second device is used to: receive first trusted authorization information from the cloud server and store the first trusted authorization information, where the first trusted authorization information is authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device;

[0101] The third device is used to: receive second trusted authorization information from the cloud server and store the second trusted authorization information, where the second trusted authorization information is authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device;

[0102] The first trusted authorization information includes association information between the device identification of the third device and the security credentials of the first device; the second trusted authorization information includes association information between the device identification of the second device and the security credentials of the second device.

[0103] In some possible implementations of the sixth aspect, the first device is specifically configured to:

[0104] In response to the second operation, a group member adding interface is displayed, and the second operation is an operation on the group member invitation control; in response to the third operation, a target message is sent to the cloud server, and the third operation is an operation on the member invitation option or at least one user information displayed on the group member adding interface, and the third operation is used to determine the users invited to join the group; the first information includes the identification of the group owner or the information of the first account, and the second information includes the member identification of the invited user in the group or the information of the second account, the group owner is the first account, the account of the user invited to join the group is the second account, and the second device is a device in the group, and the first operation includes the second operation and the third operation.

[0105] In some possible implementations of the sixth aspect, the first device is specifically configured to:

[0106] In response to the fourth operation, a second device is determined from multiple devices logged in to the first account, and the fourth operation is used to determine the shared device; in response to the fifth operation, a target message is sent to the cloud server, and the fifth operation is an operation on the member sharing option or at least one user information displayed on the shared member selection interface, and the fifth operation is used to determine the user sharing the second device, and the user sharing the second device is the second account; the first information includes information of the second device or information of the first account, and the second information includes information of the second account, and the first operation includes the fourth operation and the fifth operation.

[0107] In some possible implementations of the sixth aspect, the first device is further used to: in response to a sixth operation, send a cancel sharing instruction to the cloud server, where the sixth operation is used to cancel sharing of the second device with the second account, and the cancel sharing instruction is used to trigger the cloud server to delete the authorization relationship between the second account and the second device, and send a first deletion instruction to the second device and send a second deletion instruction to the third device;

[0108] The second device is used to: receive a first deletion instruction from the cloud server, and delete the first trusted authorization information stored locally in response to the first deletion instruction;

[0109] The third device is used to: receive a second deletion instruction from the cloud server, and delete the second trusted authorization information stored locally in response to the second deletion instruction.

[0110] In some possible implementations of the sixth aspect, the second device is further used to: obtain wireless broadcast information of the third device, the wireless broadcast message of the third device includes a device identification of the third device; if the first device security credential corresponding to the device identification of the third device is queried from the first trusted authorization information, the third device is determined to be a trusted device. After the third device determines that the second device is trusted according to the second trusted authorization information, the second device and the third device establish a trusted communication connection.

[0111] In some possible implementations of the sixth aspect, the second device is further used to: automatically send a connection request to a trusted third device; or, if there are at least two trusted third devices, display the at least two trusted third devices in a list of connectable devices, and in response to a user's selection operation on the list of connectable devices, send a connection request to the trusted third device specified in the selection operation.

[0112] In some possible implementations of the sixth aspect, when displaying the list of connectable devices, the second device displays user information and device information of users to which the connectable devices belong.

[0113] In some possible implementations of the sixth aspect, the second trusted authorization information further includes association information between a device identification of the first device and a security credential of the third device;

[0114] The first device is also used to: obtain wireless broadcast information of the third device, the wireless broadcast message of the third device includes the device identification of the third device; if the first device security credential corresponding to the device identification of the third device is queried from the first trusted authorization information, the third device is determined to be a trusted device.

[0115] After the third device determines that the first device is credible based on the second credible authorization information, that is, after authenticating that the devices at both ends are credible, the first device and the third device establish a credible communication connection.

[0116] In some possible implementations of the sixth aspect, the first device and the second device are the same device. In this case, the first device uses itself as a shared device and shares it with the second account for use.

[0117] In some possible implementations of the sixth aspect, if the first device, the second device, or the third device is powered on again after being powered off, the first device, the second device, or the third device is further used to: after sending a query instruction to the cloud server, receive response information returned by the cloud server to the query instruction, and the query instruction is used to query whether the device sharing relationship is updated. In this way, it can be avoided that the device sharing relationship cannot be updated in time after a change (such as cancellation of sharing) occurs during power-off.

[0118] In a seventh aspect, an embodiment of the present application provides a device sharing method, which is applied to a device sharing system, wherein the device sharing system includes a first device, a second device, and a third device, wherein the first device and the second device log in to a first account, and the third device logs in to the second account, and the first account is different from the second account; the method includes:

[0119] The first device sends a target message to the cloud server in response to one or more operations, the target message including first information indicating the first account and second information indicating the second account, the first operation being used to share the second device with the second account; the target message is used to trigger the cloud server to transmit the first trusted authorization information to the second device, and to transmit the second trusted authorization information to the third device;

[0120] The second device receives the first trusted authorization information from the cloud server and stores the first trusted authorization information, where the first trusted authorization information is authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device;

[0121] The third device receives the second trusted authorization information from the cloud server and stores the second trusted authorization information, where the second trusted authorization information is authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device;

[0122] The first trusted authorization information includes association information between the device identification of the third device and the security credentials of the first device; the second trusted authorization information includes association information between the device identification of the second device and the security credentials of the second device.

[0123] In some possible implementations of the seventh aspect, the first device sends a target message to the cloud server in response to one or more operations, including:

[0124] In response to a first operation, a group member adding interface is displayed, and the first operation is an operation on a group member invitation control; in response to a second operation, a target message is sent to a cloud server, and the second operation is an operation on a member invitation option or at least one user information displayed on the group member adding interface, and the second operation is used to determine the user invited to join the group; the first information includes the identification of the group owner or the information of the first account, and the second information includes the member identification of the invited user in the group or the information of the second account, the group owner is the first account, the user invited to join the group is the second account, and the second device is a device in the group.

[0125] In some possible implementations of the sixth aspect, in some possible implementations of the sixth aspect, the first device sends a target message to the cloud server in response to one or more operations, including:

[0126] In response to the third operation, a second device is determined from multiple devices logged in to the first account, and the third operation is used to determine the shared device; in response to the fourth operation, a target message is sent to the cloud server, and the fourth operation is an operation on the member sharing option or at least one user information displayed on the shared member selection interface, and the fourth operation is used to determine the user who shares the second device, and the account of the user who shares the second device is the second account; the first information includes information of the second device or information of the first account, and the second information includes information of the second account.

[0127] In some possible implementations of the seventh aspect, the method further includes:

[0128] In response to the fifth operation, the first device sends a cancel sharing instruction to the cloud server, where the fifth operation is used to cancel sharing of the second device with the second account, and the cancel sharing instruction is used to trigger the cloud server to delete the authorization relationship between the second account and the second device, and send a first deletion instruction to the second device and a second deletion instruction to the third device;

[0129] The second device receives the first deletion instruction from the cloud server, and deletes the first trusted authorization information stored locally in response to the first deletion instruction;

[0130] The third device receives the second deletion instruction from the cloud server, and deletes the second trusted authorization information stored locally in response to the second deletion instruction.

[0131] In some possible implementations of the seventh aspect, the method further includes:

[0132] The second device obtains wireless broadcast information of the third device, where the wireless broadcast message of the third device includes a device identification of the third device; if the first device security credential corresponding to the device identification of the third device is queried from the first trusted authorization information, the third device is determined to be a trusted device;

[0133] After the third device determines that the second device is trustworthy according to the second trusted authorization information, the second device and the third device establish a trusted communication connection.

[0134] In some possible implementations of the seventh aspect, after the third device determines that the second device is trustworthy according to the second trusted authorization information, the second device and the third device establish a trusted communication connection, including:

[0135] The second device automatically sends a connection request to a trusted third device; or, if there are at least two trusted third devices, the at least two trusted third devices are displayed in a list of connectable devices, and in response to a user's selection operation on the list of connectable devices, a connection request is sent to the trusted third device specified by the selection operation.

[0136] The third device queries the second device security credentials corresponding to the device identification of the second device from the second trusted authorization information according to the device identification of the second device in the connection request, determines that the second device is trustworthy, and establishes a connection with the second device.

[0137] In some possible implementations of the seventh aspect, when displaying the list of connectable devices, the second device displays user information and device information of users to which the connectable devices belong.

[0138] In some possible implementations of the seventh aspect, the second trusted authorization information further includes association information between a device identifier of the first device and a security credential of the third device; and the method further includes:

[0139] The first device obtains wireless broadcast information of the third device, and the wireless broadcast message of the third device includes the device identification of the third device; if the first device security credential corresponding to the device identification of the third device is queried from the first trusted authorization information, the third device is determined to be a trusted device.

[0140] After the third device determines that the first device is credible according to the second credible authorization information, that is, after authenticating that the devices at both ends are credible, the first device and the third device establish a credible communication connection.

[0141] In some possible implementations of the seventh aspect, the first device and the second device are the same device. In this case, the first device uses itself as a shared device and shares it with the second account.

[0142] In some possible implementations of the seventh aspect, if the first device, the second device, or the third device is powered on again after being powered off, the method further includes: after the first device, the second device, or the third device sends a query instruction to the cloud server, receiving response information returned by the cloud server to the query instruction, wherein the query instruction is used to query whether the device sharing relationship is updated. In this way, it can be avoided that the device sharing relationship cannot be updated in time after a change (for example, cancellation of sharing) occurs during power-off.

[0143] In an eighth aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method of any one of the second aspect, the third aspect, or the fourth aspect described above is implemented. The electronic device may be a first device, a second device, a third device, or a cloud server.

[0144] In a ninth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method of any one of the second aspect, the third aspect or the fourth aspect is implemented.

[0145] In a tenth aspect, an embodiment of the present application provides a chip system, the chip system includes a processor, the processor is coupled to a memory, and the processor executes a computer program stored in the memory to implement any method of the second aspect, the third aspect, or the fourth aspect. The chip system can be a single chip, or a chip module composed of multiple chips.

[0146] In the eleventh aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on an electronic device, the electronic device executes the method of the second aspect, the third aspect or the fourth aspect mentioned above.

[0147] It can be understood that the beneficial effects of the second to eleventh aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0148] Figure 1A A schematic diagram of a multi-terminal device scenario provided in an embodiment of the present application;

[0149] Figure 1B A schematic diagram of a mobile phone login account provided in an embodiment of the present application;

[0150] Figure 1C A schematic diagram of a super desktop scene provided in an embodiment of the present application;

[0151] Figure 1D A schematic diagram of code scanning authentication provided in an embodiment of the present application;

[0152] Figure 1E A schematic diagram of inputting a PIN code for authentication provided in an embodiment of the present application;

[0153] Figure 2 A schematic block diagram of a device sharing system provided in an embodiment of the present application;

[0154] Figure 3 A schematic flow chart of a device sharing method provided in an embodiment of the present application;

[0155] Figure 4A A schematic diagram of a device sharing process provided in an embodiment of the present application;

[0156] Figure 4B A schematic diagram of the process of inviting family group members provided in an embodiment of the present application;

[0157] Figure 5 A schematic diagram of a super desktop scene provided in an embodiment of the present application;

[0158] Figure 6 A schematic flow chart of a device sharing method provided in an embodiment of the present application;

[0159] Fig. 7A Schematic diagram of device sharing scenario provided for the embodiment of the present application

[0160] Figure 7B A schematic diagram of the process of device sharing within a family group provided in an embodiment of the present application;

[0161] Figure 8 A schematic diagram of a scenario for canceling device sharing provided in an embodiment of the present application;

[0162] Fig. 9 A schematic diagram of a framework of a device sharing system provided in an embodiment of the present application;

[0163] Fig.10 A schematic diagram of a super desktop implementation process in a home group device sharing scenario provided by an embodiment of the present application;

[0164] Fig.11 A schematic diagram of a super desktop service provided in an embodiment of the present application;

[0165] Fig.12 A schematic diagram of the structure of an electronic device 1200 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0166] In the following description, for the purpose of explanation rather than limitation, specific details such as specific system structures and technologies are provided to facilitate a thorough understanding of the embodiments of the present application.

[0167] Multiple terminal devices of the same user usually log in to the same account, and the accounts logged in to terminal devices of different users are usually different.

[0168] For example, see Figure 1A The schematic diagram of a multi-terminal device scenario provided by an embodiment of the present application is shown, and the multi-device scenario exemplarily includes a cloud server 11, a first user 12, and a second user 13. The first user 12 includes a mobile phone 121, a tablet 122, a computer 123, a smart speaker 124, a large screen device 125, and a smart cockpit 126; the second user 13 includes a mobile phone 131, a smart watch 132, and a Bluetooth headset 133.

[0169] Each terminal device of the first user 12 logs into the same account, and each terminal device of the second user 13 also logs into the same account. However, the account logged into by the terminal device of the first user 12 is different from the account logged into by the second user 13.

[0170] For example, see Figure 1B A schematic diagram of mobile phone account login provided in an embodiment of the present application is shown, in which the mobile phone 121 of the first user 12 logs in to account 127, and other terminal devices of the first user 12, namely the tablet 122, computer 123, smart speaker 124, large screen device 125, and smart cockpit 126 are all logged in to account 127.

[0171] The mobile phone 131 of the second user 13 is logged into the account 134 , and other terminal devices of the second user 13 , namely the smart watch 132 and the Bluetooth headset 133 , are also logged into the account 134 .

[0172] Account 127 is 188******27, and account 134 is 158******66. The two accounts are different.

[0173] Understandably, Figure 1B The example of using a mobile phone number as an account to log in to a terminal device is given, but in actual applications, you can also use email addresses to log in to the terminal device, not limited to mobile phone numbers. In addition, Figure 1B The example shows that both mobile phones are logged in to Huawei accounts. However, in actual applications, the accounts logged in to the two mobile phones may not be from the same manufacturer.

[0174] Multiple terminal devices of the first user 12 can all be connected to the cloud server 11 for communication, and multiple terminal devices of the second user 13 can also be connected to the cloud server 11 for communication. Usually, the cloud server 11 stores relevant information of the terminal devices of each user, for example, the cloud server 11 stores the account information of the first user 12, and the information of each terminal device associated with the account of the first user 12, and the information of the terminal device can include, for example, the device identity (Identity document, ID), the device model, the device usage data (such as user behavior data) and the application data, etc.

[0175] In a distributed scenario, based on account management capabilities and distributed technologies (such as distributed databases), various terminal devices under the same account can safely and conveniently establish a trusted communication connection, and synchronize data through the trusted communication connection to realize cross-device services.

[0176] For example, see Figure 1C In the schematic diagram of the super desktop scenario provided by the embodiment of the present application, the mobile phone 121 and the large screen device 125 are both terminal devices of the first user 12, and the same account is logged in. The mobile phone 121 and the large screen device 125 first establish a trusted communication connection, and then synchronize data through the trusted communication connection to implement the "super desktop" service.

[0177] Specifically, the mobile phone 121 and the large-screen device 125 are on the same WLAN, and the Bluetooth of the mobile phone 121 and the large-screen device 125 are both turned on; the user turns on the "Super Desktop" switch on the mobile phone 121, and enters the "Super Desktop" on the large-screen device 125; the user gradually moves the mobile phone 121 closer to the large-screen device 125, and the large-screen device 125 will automatically discover the mobile phone 121 and display the mobile phone 121 on the list of connectable devices; the user clicks on the mobile phone 121 on the list of connectable devices of the large-screen device 125, and the large-screen device 125 can establish a communication connection with the mobile phone 121.

[0178] After the large screen device 125 and the mobile phone 121 establish a communication connection, the large screen device 125 obtains the application data and user data of the mobile phone 121, and displays the application icons installed on the mobile phone 121 on the "super desktop", for example Figure 1C The medium and large-screen device 125 displays icons of applications such as smart life, settings, recorder, app store, gallery, and video installed on the mobile phone 121; when the user clicks on the application icon on the "super desktop" of the large-screen device 125, the mobile phone 121 can synchronize the application data to the large-screen device 125 through a communication connection, and the large-screen device 125 displays according to the data synchronized by the mobile phone 121, so that the user can use the applications installed by the mobile phone 121 on the large-screen device 125.

[0179] However, in a distributed device sharing scenario, when a user wants to share a terminal device he owns with other users, the user needs to log in to different accounts on the shared terminal device and the terminal devices of other users. At this time, when establishing a trusted communication connection between terminal devices logged in to different accounts, the user is required to perform device trusted authentication by scanning a QR code or entering a pin code to ensure that the devices are mutually trustworthy.

[0180] For example, in Figure 1C In the "super desktop" scenario shown, the first user 12 can use the application installed on the mobile phone 121 directly on the large-screen device 125. If the first user wants to share the large-screen device 125 with the second user 13, the large-screen device 125 will be used as a shared device, and the terminal devices of the second user 13 are all different-account devices of the shared device. That is, the first user 12 shares or shares the large-screen device 125 with the second user 13, and the large-screen device 125 is the device that the first user 12 wants to share. For the shared device (i.e., the large-screen device 125), the second user 13's mobile phone 131, smart watch 132, and Bluetooth headset 133 are all different-account devices, that is, terminal devices logged in to different accounts.

[0181] If the second user 13 needs to use the large-screen device 125, it is necessary to access the large-screen device 125 through the terminal device of the second user 13. Assume that the second user 13 wants to use the mobile phone 131 to access the large-screen device 125 so as to use the application installed on the mobile phone 131 on the large-screen device 125. At this time, since the large-screen device 125 is logged in with the account of the first user 12, and the mobile phone 131 is logged in with the account of the second user 13, the accounts logged in by the two devices are different, and the second user 13 cannot directly control the large-screen device 125 to access the applications and data on the mobile phone 131. The second user 13 needs to use the mobile phone 131 to scan the QR code displayed on the large-screen device 125, or enter the pin code displayed on the large-screen device 125, and complete the device trusted authentication between the mobile phone 131 and the large-screen device 125 before a trusted communication connection can be established between the mobile phone 131 and the large-screen device 125.

[0182] For example, see Figure 1D The schematic diagram of code scanning authentication provided by the embodiment of the present application is shown, the mobile phone 131 and the large-screen device 125 turn on Bluetooth and are connected to the same WLAN; the user turns on the "super desktop" switch on the mobile phone 131, enters the "super desktop" on the large-screen device 125, and clicks the "connect other devices" option displayed on the "super desktop". The large-screen device 125 displays the following on the screen: Figure 1D After the user scans the QR code on the screen of the large-screen device 125 using the mobile phone 131, the mobile phone 131 pops up the following Figure 1DThe prompt information shown is used to prompt the user whether to allow connection to the super desktop of the large-screen device; if the user clicks the "Yes" option, the mobile phone 131 performs device authentication based on the device information of the large-screen device 125 carried in the QR code, and after the authentication is successful, the mobile phone 131 actively connects to the large-screen device 125 based on the device information of the large-screen device 125.

[0183] For example, see Figure 1E The schematic diagram of inputting a pin code for authentication provided in the embodiment of the present application is shown, and Figure 1D Type, after the user clicks the "Connect other devices" option displayed on the "super desktop" of the large-screen device 125, the large-screen device 125 displays the following on the screen: Figure 1E The pin code shown; the user enters the pin code in the mobile phone 131 so that the mobile phone 131 and the large-screen device 125 perform device authentication and after the authentication is successful, a communication connection is established.

[0184] After the mobile phone 131 and the large-screen device 125 establish a communication connection, the second user 13 can use the application installed on the mobile phone 131 on the large-screen device 125 to implement the "super desktop" service.

[0185] As can be seen from the above, when a user shares or shares one or more terminal devices owned by him with other users, other users need to scan the code or enter the pin code through their terminal devices to perform device trust authentication, so that the different account devices and the shared devices can establish a trusted communication connection, and then allow other users to use the shared terminal devices. The user operation process is complicated and the user experience is poor.

[0186] In other words, in the device sharing scenario, users of devices with different accounts need to perform operations such as scanning codes or entering PIN codes to complete device trusted authentication between devices with different accounts and shared devices. The operation is complicated and the user experience is poor.

[0187] In response to the problem mentioned above that in the process of establishing a connection between devices with different accounts and shared devices, users are required to perform device trusted authentication by scanning a code or entering a PIN code, which results in complicated operation and poor user experience. The embodiment of the present application provides a technical solution based on a device sharing system, so that after the user performs a device sharing operation on the terminal side, the cloud server records the device sharing information corresponding to the device sharing operation, and the device sharing information is used to characterize the trusted authorization relationship between the shared device and the different account; after the cloud server generates device security credentials based on the trusted authorization relationship, the device security credentials are sent to the terminal side to reflect the trusted authorization relationship on the cloud side through the device security credentials on the terminal side, so that the different account devices and the shared devices can perform trusted authentication through the device security credentials of the opposite device. In the process of establishing a connection between devices with different accounts and shared devices, users of the different account devices are not required to perform device trusted authentication by entering a PIN code or scanning a QR code, which makes the operation simpler and provides a better user experience.

[0188] See also Figure 2 A schematic block diagram of a device sharing system provided by an embodiment of the present application is shown. The device connection system may include a first device 21, a cloud server 22, at least one second device 23 and at least one third device 24. The first device 21 and at least one second device 23 log in to a first account, and at least one third device 24 logs in to a second account. The first account is different from the second account.

[0189] The first device 21, the second device 23 or the third device 24 can be, but is not limited to: a mobile phone, a smart wearable device (for example, smart glasses, a smart bracelet, etc.), a vehicle-mounted device, an augmented reality (AR), a virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA) and other electronic devices.

[0190] For example, Figure 1A In the scenario shown, the first device 21 and at least one second device 23 are both terminal devices of the first user 12, and both of them log in to the first account. At this time, the first device 21 is a mobile phone 121, and the at least one second device 23 includes a tablet 122, a computer 123, a smart speaker 124, a large screen device 125, and a smart cockpit 126. At least one third device 24 is a device of the second user 13, which may include a mobile phone 131, a smart watch 132, and a Bluetooth headset 133.

[0191] The cloud server 22 may be a single cloud server or a cluster composed of multiple single cloud servers. A single cloud server may be a software module that provides cloud services or a physical device that provides cloud services. In some embodiments, the cloud server 22 may include a home cloud, a device cloud, and a trust ring cloud. The home cloud may provide smart home cloud services, such as managing various smart home devices; the device cloud may provide device management cloud services. Usually, the device cloud stores the association between accounts and devices, as well as device information of each device; the trust ring cloud may provide cloud services such as device security credential generation, storage, and encryption.

[0192] See also Figure 3 The device sharing method provided in the embodiment of the present application is shown in a schematic flow chart, and the method can be applied to Figure 2 The device sharing system shown, the method may include the following steps:

[0193] Step S301, the first device 21 sends a target message to the cloud server 22 in response to one or more operations, the target message including first information indicating the first account and second information indicating the second account, and the one or more operations are used to share the second device 23 with the second account.

[0194] The first operation is usually a device sharing operation input by a user of the first device 21, which is used to indicate sharing at least one second device with the second account. The first operation may consist of multiple operations such as clicking, long pressing, and selecting to achieve the purpose of sharing at least one second device with the second account.

[0195] In some embodiments, one or more operations may be used to determine a second device from multiple devices logged into the first account to determine a shared device, and to determine a user sharing the second device. For example, one or more operations may include an operation for determining a second device from multiple devices logged into the first account to determine a shared device. In this case, the shared device may be a second device 23, that is, one or more second devices 23 are selected from multiple devices logged into the first account to share the one or more second devices as shared devices with other users; it may also include an operation for determining the user sharing the second device. For example, the operation is an operation for the member sharing option or at least one user information displayed on the shared member selection interface. Through this operation, the information of the second account can be obtained to determine that one or more second devices 23 are shared with the second account. In this way, the user can specify to share one or more devices with other users (i.e., the second account), and enable devices with different accounts to use the shared device seamlessly and conveniently like devices with the same account, providing a better user experience.

[0196] For example, based on Figure 1AIn the scenario shown, the first user 12 shares the large screen device 125 with the second user 13 via the mobile phone 121. Figure 4A A schematic diagram of the device sharing process provided by the embodiment of the present application is shown. The main interface of the mobile phone 121 displays icons of various applications, including but not limited to Smart Life 41, Settings, Recorder, App Store, Video, and Gallery. After the user clicks the icon of Smart Life 41, the mobile phone 121 responds to the click operation and displays the "My Home" interface 42. The "My Home" interface 42 displays cards of various devices associated with the account of the first user 12. Figure 4A The card 43 of the large-screen device 125 and the card of the Huawei router are given as examples, and a control 44 is also displayed.

[0197] In one implementation, the user can share the device through the card 43 of the large-screen device 125. Specifically, after the user long presses the card 43 of the large-screen device 125, the mobile phone 121 responds to the long press operation and displays a window 46, in which two options of sharing the device and deleting the device are displayed. The user clicks the shared device option in the window 46 to designate the large-screen device 125 as a shared device. In response to the shared device option in the window 46, the mobile phone 121 displays a shared member selection interface 47. The shared member selection interface 47 displays multiple member sharing options such as the scan sharing option, the sharing option through the Huawei account, and the sharing option to WeChat friends. It also displays multiple user accounts (such as the accounts of Xiao Zhang, Xiao Wang, and Xiao Li). The user can select member sharing options and shared members as needed.

[0198] The scanning sharing option refers to sharing by scanning the other party's "Smart Life" QR code. When the user clicks the scanning sharing option, the mobile phone 121 automatically calls the camera in response to the click operation and displays a QR code scanning interface to scan the QR code presented by the other party.

[0199] The option of sharing through Huawei account means sharing by entering a Huawei account or adding an account from contacts. When the user clicks on the option of sharing through Huawei account, the mobile phone 121 displays an account input interface in response to the click operation, and the user enters the account to be shared in the account input interface to share the large-screen device 125 with the second account.

[0200] In addition to sharing the device through the scan sharing option, the Huawei account sharing option, and the share to WeChat friends option, the user can share the large-screen device 125 with one or more selected user accounts by selecting multiple user accounts displayed in the sharing member selection interface 47.

[0201] In this scenario, one or more operations may include a long press operation on the card 43 of the large-screen device 125 and an operation of clicking the shared device option in the window 46 to select the large-screen device 125 as a shared device, and may also include related operations on the shared member selection interface 47, for example, an operation of selecting multiple user accounts, or an operation of clicking the sharing option through a Huawei account and an operation of entering a Huawei account, etc. The fifth operation is used to determine the information of the second account. After determining the shared device and the second account, the mobile phone 121 sends a target message to the cloud server 22. At this time, the first information used to indicate the first account may include the information of the second device (such as the device identification of the large-screen device 125, etc.) or the information of the first account, and the second information may include the information of the second account. If the first information includes the information of the second device, the cloud server 22 can obtain the information of the first account based on the information of the second device according to the association between the device and the account (or user).

[0202] In another implementation, the user can also implement device sharing through the control 44. Specifically, the user clicks the control 44, and the mobile phone 121 displays a window 45 in response to the click operation on the control 44, and the window 45 includes multiple options such as sharing devices, deleting devices, and adding devices. The user clicks the shared device option displayed in the window 45, and the mobile phone 121 displays a shared member selection interface 47 in response to the click operation on the shared device option in the window 45. The user can select the account to be shared based on the shared member selection interface 47 to share the large-screen device 125 with the second account.

[0203] exist Figure 4A In the scenario shown, the second device 23 shared with the second account is a large screen device 125, and the first operation may include long pressing a card or clicking a control, as well as account selection or input operations. It is understandable that the first operation may instruct the first account to share one or more second devices with the second account, for example, Figure 1A In the scenario, the first user 12 can input a first operation to the mobile phone 121 to instruct to share the large-screen device 125 and the smart cockpit 126 with the second user 13 (ie, the second account).

[0204] In other embodiments, the first device 21 displays a group member adding interface in response to an operation on a group member invitation control; in response to an operation on a member invitation option or at least one user information displayed on the group member adding interface, the operation is used to determine the user invited to join the group. After determining the user invited to join the group, a confirmation operation can also be input to trigger the first device 21 to send a target message to the cloud server 22 (i.e., in response to the user operation, send the target message to the cloud server). At this time, the first information may include the identifier of the group owner or the information of the first account, and the second information may include the member identifier of the invited user in the group or the information of the second account, and the group owner is the first account. The cloud server can obtain the information of the first account based on the identifier of the group owner, and obtain the information of the second account based on the member identifier. The account of the user invited to join the group is the second account, and the second device is a device in the group.

[0205] For example, the group is a family group. In this case, the user can create a family group and invite other users to join the family group to share the device with other users. In this case, the operation of inviting other users to join the family group can be regarded as a device sharing operation.

[0206] See also Figure 4B The schematic diagram of the process of inviting family group members provided by the embodiment of the present application is shown, based on Figure 4A In the scenario, after the mobile phone 121 displays the "My Home" interface 42, the user clicks on the control 48 displayed on the interface, and the mobile phone 121 displays a window 49 in response to the click operation on the control 48. The window 49 displays multiple options such as My Home, Family Management, and Create a New Family. After the user clicks on the Family Management option in the window 49, the mobile phone 121 displays a Family Management interface 410 in response to the click operation.

[0207] The family management interface 410 displays a control 411. After the user clicks on the control 411, the mobile phone 121 responds to the click operation and displays an interface 412. The interface 412 displays a family member adding control 413. After the user clicks on the family member adding control 413, the mobile phone 121 responds to the click operation and displays a member adding interface 414. The member adding interface 414 displays a variety of options for adding members, such as scanning to add members, adding members through a Huawei account, and adding members through WeChat. It also displays the account information of multiple users. Based on the member adding interface 414, the user can send an invitation to other users to join the family in order to invite other users to join the family group. Figure 4B In FIG. 4 , the owner of the family group is account 188******27. At this time, the second operation may include, for example, a click operation on the control 413, and the third operation may include, for example, a related operation on the member adding interface 414 to determine the second account.

[0208] If the invited user agrees to the invitation, the invited user can become a member of the family group, and the members of the family group can use all or some of the devices in the family group. In this way, the owner of the family group can share all or some of the devices in the family group with other users by inviting other users to join the family group. For example, Figure 1A In the scenario shown, the first user 12 (i.e., the first account) invites the second user 13 (i.e., the second account) to join the family group through the smart life on the mobile phone 121. At this time, one or more operations may include related operations for initiating an invitation to the second account (for example, clicking on the family management option and clicking on the family member adding control 413). The first operation is used to instruct the first account to share one or more third terminal devices with the second account. At this time, the shared multiple third terminal devices may include a tablet 122, a computer 123, a smart speaker 124, a large-screen device 125, and a smart cockpit 126.

[0209] It should be noted that by creating a group, the owner of the group invites other users to join the group to share all or part of the group's devices with other users. The group is not limited to Figure 4B For example, the first user 12 and the second user 13 are friends, and the first user 12 temporarily forms a friend group and invites the second user 13 to join the group.

[0210] It can be seen that the group owner can share the devices in the group with other users (i.e., the second account) by inviting other users (i.e., the second account) to join the group, thereby supporting the sharing of devices in the group with devices with different accounts in the group scenario, and enabling devices with different accounts to use the devices in the group (i.e., shared devices) as seamlessly and conveniently as devices with the same account, providing a better user experience.

[0211] It should be noted that the user creates a family group and determines the devices associated with the family group, and then determines the devices that need to be shared; the group owner requires other users to join the family group, and then determines the second account. In addition, after creating a family group and determining the devices associated with the family group, the user can also add or delete the devices associated with the family group, and then manage the devices shared with other users.

[0212] It should be noted that the above exemplifies the smart life application as the entrance to device sharing, but the entrance to device sharing is not limited to the one mentioned above and is not limited to this.

[0213] After the user inputs one or more operations to the first device 21 to instruct the first account to share at least one second device with the second account, the first device 21 sends a target message to the cloud server 22 in response to the one or more operations. The target message includes first information for indicating the first account and second information for indicating the second account, thereby indicating that the first account shares at least one second device with the second account. That is, the cloud server 22 can learn the second device shared by the first account with the second account based on the target message. For example, Figure 4A In the device sharing scenario shown in the figure, the target message sent by the mobile phone 121 to the cloud server may include the information of the second account (e.g., account number, account name, etc.) and the information of the large-screen device 125 (e.g., the ID or identification of the large-screen device, etc.). In this way, the cloud server can learn from the target message that the first account shares the large-screen device 125 with the second account, that is, learn the trusted authorization relationship between the large-screen device 125 and the second account; for another example, in Figure 4B In the family group device sharing scenario shown, the target message may include information about the second account (such as the member ID of the second account in the family group) and information about the first account (such as the group owner ID of the family group, etc.). In this way, the cloud server can obtain the trusted authorization relationship between the device in the family group and the second account based on the target message.

[0214] In some embodiments, the first information may include information of the target second device, and the second information may include information of the second account.

[0215] Exemplarily, the information of the second account is the user identifier of the second account, the account information of the second account (such as the account number, etc.), or the member ID of the second account in the family group. In the family group scenario, after the invited user agrees to join the family group, a member ID within the group will be assigned to the newly joined family member to identify the family member. The information of the target second device may include the device identifier or device name of the target second device. The target second device is one of multiple second devices, and the device is specified by the user to be shared with other users. For example, in Figure 4A In the device sharing scenario, when the user shares the large-screen device 125 with the second account, the mobile phone 121 uploads the device identifier or device name of the large-screen device 125 to the cloud server. At this time, the target second device is the large-screen device 125.

[0216] In other embodiments, the first information may include information of the first account, and the second information may include information of the second account. The information of the first account may include the user identification of the first account, the account information of the first account (such as the account number of the first account, etc.), or the unique ID of the first account in the family group, and the information of the second account may include the user identification of the second account, the account information of the second account (such as the account number), or the member ID of the second account in the family group. For example, in a family group scenario, the first account is the Owner of the family group, the first account has its Owner ID in the family group, and the second account is a member of the family group. After the user of the second account agrees to join the family group, the first device 21 uploads the Owner ID and the member ID to the cloud server 22.

[0217] In some other embodiments, the first information may include information of the first account and information of the target second device, and the second information may include information of the second account. The target second device is one or more devices specified by the user.

[0218] Step S302: The cloud server 22 transmits the first trusted authorization information to the second device 23 and transmits the second trusted authorization information to the third device 24 according to the first information and the second information.

[0219] The first trusted authorization information includes the association information between the device identification of the third device 24 and the first device security credential; the second trusted authorization information includes the association information between the device identification of the second device 23 and the second device security credential. The first device security credential is the device security credential of the third device, and the second device security credential is the device security credential of the second device.

[0220] The cloud server 22 can provide account management capabilities and device management capabilities. It can store the correspondence between each account and device. Through the correspondence between the account and the device, all devices associated with the account can be queried based on the account; in addition, the device information of each device is also stored. The device information may include but is not limited to: device model, device ID, device name, device security level information, device version information and device inherent attribute information, etc.

[0221] In some embodiments, the first information includes information of the first account, and the second information includes information of the second account. Based on the information of the first account, the cloud server 22 can query each second device associated with the first account and obtain the device information of each second device; for each second device, based on the device information of the second device, generate the second device security credential of the second device, and associate the second device security credential of the second device with the device identification of the second device to establish an association relationship between the second device security credential and the device identification of the second device, and finally obtain the second trusted authorization information based on the association relationship between the second device security credential and the device identification of each second device. That is, the second trusted authorization information can include the association information between the second device security credential and the device identification of at least one second device.

[0222] After the cloud server 22 generates the second trusted authorization information, it can obtain the relevant information (such as communication address, etc.) of each third device associated with the second account according to the information of the second account, and then send the second trusted authorization information to one or more third devices according to the relevant information of the third device. It is understandable that the cloud server 22 can send the second trusted authorization information to all third devices, to some third devices, or even to some specific third devices.

[0223] Similarly, the cloud server 22 can obtain each third device associated with the second account and the device information of each third device based on the information of the second account; for each third device, based on the device information of the third device, generate the first device security credential of the third device, and associate the first device security credential with the device identification of the third device to establish an association relationship between the first device security credential and the device identification of the third device, and finally obtain the first trusted authorization information based on the association relationship of each third device. That is, the first trusted authorization information can include the association information between the first device security credential and the device identification of at least one third device.

[0224] After the cloud server 22 generates the first trusted authorization information, it can obtain the relevant information (such as communication address, etc.) of each second device associated with the first account based on the information of the first account, and then send the first trusted authorization information to one or more second devices based on the relevant information of the second device.

[0225] It should be noted that the device security level information, device model, device version information and device inherent attribute information of the second device and the first device are generally fixed and will not change in a long period of time. Based on these fixed information that does not change in a long period of time, the generated device security credentials can remain unchanged for a long time, and there is no need to frequently perform the device security credential generation operation and other processes. If the device security credentials are generated based on non-fixed information that changes in a short period of time, whenever the device information changes, the cloud server 22 needs to regenerate the device security credentials based on the changed device information, and it may be necessary to frequently perform the device security credential generation process.

[0226] In other embodiments, the first information may include information of the target second device, or include information of the first account and information of the target second device; the second information may include information of the second account. At this time, the cloud server 22 may obtain information of the first account based on the correspondence between the account and the device and the information of the target second device. The second trusted authorization information is generated based on the information of the first account, and the first trusted authorization information is generated based on the information of the second account. The specific process can be found above and will not be repeated here.

[0227] In a specific application, when the cloud server 22 generates device security credentials based on device information, it can use public key infrastructure (PKI) technology to sign the device information, thereby ensuring the security of device security credential transmission to the greatest extent.

[0228] It is worth pointing out that the cloud server 22 can generate the device security credentials of each device in advance, and after obtaining the target message, it can query the second device security credentials of the second device and the first device security credentials of the third device based on the first information and the second information, and establish the association relationship between the device security credentials and the device identification of each device. Alternatively, the cloud server 22 can generate the association relationship between the device security credentials and the device identification of each device in advance, and after obtaining the target message, it can query the association information between the second device security credentials and the device identification of the second device, and the association information between the device identification of the third device and the first device security credentials based on the first information and the second information.

[0229] Step S303: The second device 23 receives the first trusted authorization information from the cloud server 22 and stores the first trusted authorization information. The first trusted authorization information is authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device.

[0230] Step S304, the third device 24 receives the second trusted authorization information from the cloud server 22, and stores the second trusted authorization information; the second trusted authorization information is the authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device.

[0231] The second device 23 and the third device 24 can authenticate whether the opposite device is credible according to the device security credentials of the opposite device stored locally. If both devices are authenticated as credible, the two devices can establish a credible communication connection.

[0232] Exemplarily, after scanning the wireless broadcast information sent by the surrounding devices, the second device 23 reads each first trusted authorization information locally; for each wireless broadcast information, based on the first trusted authorization information, it is determined whether the device security credentials corresponding to the device identifier carried by the wireless broadcast information are queried. Specifically, for each wireless broadcast information, the device identifier carried by the wireless broadcast information is compared with the device identifier of the first trusted authorization information to determine whether the two are consistent. If the device identifier carried by the wireless broadcast information is consistent with a device identifier in the first trusted authorization information, the device security credentials corresponding to the device identifier are used as the device security credentials corresponding to the device identifier of the wireless broadcast information, that is, it is determined that the device security credentials corresponding to the device identifier carried by the wireless broadcast information are queried; if each device identifier in the first trusted authorization information is inconsistent with the device identifier carried by the wireless broadcast information, it is determined that the device security credentials corresponding to the device identifier carried by the wireless broadcast information are not queried. Among them, the wireless broadcast information can be, for example, Bluetooth broadcast information or Wi-Fi broadcast information.

[0233] For each wireless broadcast information, if the second device finds the device security credentials corresponding to the device identifier of the wireless broadcast information, it determines that the device corresponding to the device identifier of the wireless broadcast information is a trusted device and adds it to the trusted device list; conversely, if the device security credentials corresponding to the device identifier of the wireless broadcast information cannot be found, it determines that the device corresponding to the device identifier of the wireless broadcast information is an untrusted device. In this way, in the process of establishing a connection between different account devices and shared devices, the third terminal device (i.e., shared device) can perform trusted authentication on each second terminal device (i.e., different account device) based on the first corresponding relationship.

[0234] In some embodiments, if the second device initiates a connection request to the third device, the second device obtains the wireless broadcast information of the third device, and the wireless broadcast message of the third device includes the device identification of the third device; if the first device security credential corresponding to the device identification of the third device is queried from the first trusted authorization information, the third device is determined to be a trusted device, that is, the second device authenticates the third device as a trusted device through the first trusted authorization information. After the second device determines that the third device is a trusted device, it can send a connection request to the third device, and the connection request includes information such as the device identification of the second device. The third device can query the device security credential corresponding to the device identification carried in the connection request from the second trusted authorization information. If the corresponding device security credential is queried, it is determined that the second device is a trusted device, and a trusted communication connection is established with the second device.

[0235] Similarly, if the third device initiates a connection request to the second device, the third device obtains the wireless broadcast information of the second device, and the wireless broadcast information of the second device includes the device identification of the second device; if the second device security credentials corresponding to the device identification of the second device are queried from the second trusted authorization information, the second device is confirmed to be a trusted device. That is, the third device 24 authenticates the second device as a trusted device through the second trusted authorization information. The second device determines whether the device security credentials of the third device are stored locally based on the first trusted authorization information, so as to authenticate the third device as trusted.

[0236] It can be understood that the first trusted authorization information includes the relationship between the device identification of the third device and the security credentials of the first device. When the device identification of the target wireless broadcast information (i.e., one of the multiple wireless broadcast information scanned) is the same as the device identification in the first trusted authorization information, it is considered that the device that sends the target wireless broadcast information is one of the at least one third device. The second device can identify the third device among the surrounding devices based on the corresponding relationship between the device security credentials and the device identification, and because the device security credentials of the third device are stored locally, it further confirms that the authentication of the third device has passed, identifies the third device as a trusted device, and initiates a connection to the trusted third device to establish a communication connection with the trusted third device. Among them, the connection request sent by the second device to the third device carries the device information of the second device (such as the device identification). After receiving the connection request, the third device determines whether the device security credentials of the second device can be queried from the second trusted authorization information. If the device security credentials of the second device can be queried, it is determined that the second device is trusted, and a trusted communication connection is established with the second device.

[0237] It is understandable that there may be one or more third devices in the surrounding environment of the second device, so the second device can identify one or more trusted third devices. When a trusted third device is identified, the second device can actively send a connection request to the trusted third device to establish a communication connection with the trusted third device. Of course, the second device can also send a connection request to the trusted third device after receiving a trigger instruction from the user.

[0238] When multiple trusted third devices are identified, the second device can send a connection request to the trusted third device specified by the user under user operation to establish a connection with the specified trusted third device. Of course, the second device can also actively send a connection request to all trusted third devices.

[0239] For example, see Figure 5 The schematic diagram of the super desktop scenario provided by the embodiment of the present application is shown. In the device sharing scenario of the family group, the owner of the family group wants to share the large-screen device 51 owned by him with other members of the family group. The large-screen device 51 is logged in to the owner's account. The owner can Figure 4B In the process shown, two users, Xiao Ming and Jack@mail.com, are invited to join the family group. For each of the two users, the cloud server 22 generates the first trusted authorization information of the user account and sends it to the large-screen device 51. The cloud server 22 also generates the second trusted authorization information of the large-screen device and sends it to each device under the two user names, Xiao Ming and Jack@mail.com. In this way, the large-screen device 51 stores the device security credentials of each device of the two users, Xiao Ming and Jack@mail.com, and each device of the two users, Xiao Ming and Jack@mail.com, stores the device security credentials of the large-screen device 51. The large-screen device 51, Xiao Ming and Jack@mail.com's mobile phones all turn on the Bluetooth function. The large-screen device 51, Xiao Ming and Jack@mail.com's mobile phones send out wireless broadcast information. The large-screen device 51 scans and obtains the wireless broadcast information in the surrounding environment, and based on the first trusted authorization information stored locally, authenticates that Xiao Ming's Mate 30Pro and P50, and Jack@mail.com's Mate40 Pro are trustworthy, and displays multiple mobile phones in the connectable device connection 53 of the super desktop 52. Similarly, Xiao Ming's Mate30Pro and P50, and Jack@mail.com's Mate40 Pro will also perform device trustworthiness authentication on the large-screen device 51 based on the second trusted authorization information.

[0240] The user can click on a device in the connectable device list 53 as needed to specify the terminal device to send the connection request, and the large-screen device 51 responds to the click operation and sends a request to the connectable device clicked by the user. For example, the user clicks on the option of Xiao Ming's Mate 30Pro in the connectable device list 53, and the large-screen device 51 sends a connection request to Xiao Ming's Mate 30Pro to establish a communication connection with the device.

[0241] It should be noted that in Figure 5 In the illustrated scenario, when the large-screen device 51 is shared with only one user, that is, the Owner only shares the large-screen device 51 with Xiao Ming and only invites Xiao Ming to join the family group, the large-screen device 51 identifies Xiao Ming's two trusted devices and displays them on the connectable device list 53 for the user to select. In addition, when the large-screen device 51 is shared with at least two users, that is, the Owner shares the large-screen device 51 with Xiao Ming and Jack@mail.com and invites Xiao Ming and Jack@mail.com to join the family group, at this time, the large-screen device 51 can identify the trusted devices of each user and display them on the connectable device list 53 for the user to select.

[0242] It is worth pointing out that in Figure 5 In the scenario, when the large-screen device 51 displays the list of connectable devices, it not only displays device information (such as device name), but also displays user information of each device (such as Xiao Ming), that is, displays the user to whom each device belongs. At this time, the large-screen device 51 locally stores the correspondence between user information (such as user ID) and device information. According to the correspondence, the user and user information to which each device belongs can be queried, and the display information including the device information and user information is obtained by splicing the device information and user information, and displayed on the list of connectable devices, which provides a better user experience.

[0243] It is understandable that in a distributed scenario, in order to ensure the connection security between multiple devices and realize the safe flow of user data and application data between various devices, it is usually necessary to ensure that the devices are correctly trusted, that is, a trust relationship has been established between devices, and after verifying the trust relationship, a secure connection channel can be built to realize the safe transmission of user data and application data. For devices logged in to different accounts, if a trusted connection is established after trusted authentication by scanning a code or entering a pin code, the user experience is poor.

[0244] In the embodiment of the present application, when the user inputs the first operation for indicating sharing the second device with the second account to the first device 21, it can be considered that the authorization of the second device and the second account is credible. After the first terminal device responds to the first operation and sends the target message to the cloud server, the cloud server obtains the trusted authorization relationship between the second device and the second account according to the target message, and generates the association information between the device identification of the second device and the security credentials of the second device based on the trusted authorization relationship, as well as the association information between the device identification of the third device and the first device security credentials and the device identification, and transmits the second device and the third device accordingly, so as to reflect the trusted authorization relationship on the cloud side through the device security credentials on the end side. In this way, the second device (i.e., the shared device) and the third device (i.e., the different account device) can authenticate whether the opposite device is credible based on the device security credentials of the opposite device, and the user of the different account device does not need to perform device trusted authentication by entering a pin code or scanning a QR code, etc., which makes the operation easier and provides a better user experience. For example, in a group device sharing scenario, through the device sharing solution of the embodiment of the present application, after the second account confirms to join the group, the user of the second account can log in to the device of the second account and use the device logged in to the first account in the group, so that the user of the second account can obtain the same experience or a similar experience as the user of the same account (i.e., the first account), thereby improving the user experience of the second account.

[0245] It should also be pointed out that during the process of users of devices with different accounts performing trusted authentication by entering a PIN code or scanning a QR code, and establishing a connection between the devices with different accounts and the shared devices, the shared devices cannot autonomously discover the devices with different accounts and require users to add them manually. Moreover, each time a shared device establishes a connection with a device with different accounts, the user is required to repeatedly enter a PIN code or scan a QR code, which means that from a user's perspective, repeated authentication is required for each use.

[0246] In the embodiment of the present application, the shared device (i.e., the second device) can proactively discover the user to whom the device with a different account belongs, based on the correspondence between the device identifier and the device security credentials, by comparing whether the device identifier carried by the wireless broadcast information and the device identifier in the information authorization information are the same; in addition, the shared device and the device with a different account can persistently store the trusted authorization information, so each time a connection is established, the device can be authenticated based on the stored trusted authorization information. From the user's perspective, there is no need to repeat the authentication each time.

[0247] As described above, the cloud server 22 may generate first trusted authorization information and second trusted authorization information based on the first information and the second information, and transmit the first trusted authorization information to the second device and the second trusted authorization information to the third device.

[0248] Of course, in addition to transmitting the first trusted authorization information to the second device, the first trusted authorization information can also be transmitted to the first device, or transmitted to all devices associated with the first account, and all devices associated with the first account include the first device and each second device. In this way, not only can the second device perform device trusted authentication on the third device based on the first trusted authorization information, but the first device can also perform device trusted authentication on the third device based on the first trusted authorization information to achieve cross-device services with each third device 24 (such as super desktop, distributed photo album, super terminal, etc.). At this time, the second trusted authorization information also includes the association between the device identification of the first device and the security credentials of the third device.

[0249] For example, when the first information includes information of the second device or the target second device, and the second information includes information of the second account, the cloud server 22 searches for information of the first account based on the association relationship between the account and the device, according to the information of the target second device or the second device, and obtains the device information of the first device and the device information of each second device based on the information of the first account, generates association information between the device identification of the first device and the third device security credential based on the device information of the first device; generates association information between the device identification of the second device and the second device security credential based on the device information of each second device, and generates second trusted authorization information based on the association information between the device identification of the second device and the second device security credential, and the association information between the device identification of the first device and the third device security credential. The second trusted authorization information is transmitted to the third device, and the third device can automatically discover and authenticate the first device based on the association information between the device identification of the first device and the third device security credential in the second trusted authorization information, and automatically discover and authenticate the second device based on the association information between the device identification of the second device and the second device security credential in the second trusted authorization information.

[0250] Similarly, the cloud server 22 generates first trusted authorization information based on the information of the second account, and transmits the first trusted authorization information to the first device and the second device.

[0251] In this way, the first device and the third device can establish a trusted communication connection based on the device security credentials after authenticating that the other device is trustworthy, thereby realizing cross-device services between the first device and the third device; the second device and the third device can also establish a trusted communication connection based on the device security credentials after authenticating that the other device is trustworthy, thereby realizing cross-device services between the second device and the third device.

[0252] In order to better introduce the device sharing process, the following Figure 6 A schematic flow chart of a device sharing method provided in an embodiment of the present application is shown for description. Figure 6 As shown, the method may include the following steps:

[0253] Step S601: The first device 21 sends a target message to the cloud server 22 in response to a first operation. The target message includes first information indicating a first account and second information indicating a second account. The first operation is used to share the second device 23 with at least one second account.

[0254] It should be noted that the user can share the device with a single user or multiple users. For example, in a family group device sharing scenario, the owner can ask multiple users to join the family group in order to share the devices in the family group with multiple users. When sharing a device with at least one second account, steps S602 to S607 are executed for each second account. In this way, the second device (i.e., the shared device) stores the correspondence between the device security credentials and the device identification of each second account. Based on the correspondence between the device security credentials and the device identification of each second account, the terminal device associated with each second account is autonomously discovered and trusted authentication is performed. For example, see Figure 5 In the scenario shown, Xiao Ming and Jack@mail.com are both second accounts, and the large-screen device 51 can identify Xiao Ming and Jack@mail.com as trusted devices.

[0255] Step S602: The cloud server 22 obtains first trusted authorization information and second trusted authorization information according to the first information and the second information.

[0256] The second trusted authorization information includes the association information between the device identification of the first device and the security credentials of the third device, and the association information between the device identification of the second device and the security credentials of the second device. The first trusted authorization information includes the association information between the device identification of the third device and the security credentials of the first device.

[0257] It should be noted that the first trusted authorization information and the second trusted authorization information may be generated in advance or in real time. The specific generation process may refer to the above-mentioned related content and will not be described in detail here.

[0258] The first trusted authorization information is the authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device. The second trusted authorization information is the authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device. The second trusted authorization information is also the authentication information used to authenticate the first device during the process of establishing a connection between the first device and the third device.

[0259] Step S603: The cloud server 22 sends first trusted authorization information to the first device 21.

[0260] Step S604: The cloud server 22 sends first trusted authorization information to the second device 23.

[0261] Step S605 : The cloud server 22 sends second trusted authorization information to the third device 24 .

[0262] Step S606: The first device 21 performs device trustworthiness authentication on the third device 24 according to the first trusted authorization information.

[0263] Step S607: The second device 23 performs device trust authentication on the third device 24 according to the first trusted authorization information.

[0264] Step S608: The third device 24 performs device trust authentication on the first device 21 and the second device 23 according to the second trusted authorization information.

[0265] Step S609: The trusted authentication between the first device 21 and the third device 24 is passed, and a trusted communication connection is established.

[0266] Exemplarily, if the first device 21 initiates a connection request to the third device 24, the first device 21 obtains the wireless broadcast information of the third device 24, and the wireless broadcast message of the third device includes the device identification of the third device; if the first device security credentials corresponding to the device identification of the third device 24 are queried from the first trusted authorization information, the third device 24 is determined to be a trusted device. After the first device 21 determines that the third device 24 is trustworthy, it can send a connection request to the third device 24, and the connection request carries the device information of the first device 21 (such as the device identification). After receiving the connection request, the third device determines whether the device security credentials of the first device can be queried from the second trusted authorization information. If the device security credentials of the first device can be queried, it is determined that the first device is trustworthy, and a trusted communication connection is established with the first device.

[0267] For example, in a hyperterminal service scenario, the first device 21 needs to obtain relevant information of each third device, and can perform automatic discovery, trusted authentication, and automatic connection initiation based on the first trusted authorization information to establish a trusted communication connection with the third device.

[0268] Step S610: The trusted authentication at both ends of the second device 23 and the third device 24 is passed, and a trusted communication connection is established.

[0269] As can be seen from the above, not only the association information between the device identification of the second device and the security credentials of the second device is generated, but also the association information between the device identification of the first device and the security credentials of the third device is generated, and the second trusted authorization information including the two association information is transmitted to the third device, and the first trusted authorization information is transmitted to the first device and the second device, so that the devices associated with the first account all store the device security credentials of the devices associated with the second account, and the devices associated with the second account also store the device security credentials of the devices associated with the first account. The devices between the two accounts can automatically discover and trustworthy authenticate devices with different accounts based on local device security credentials, and establish a trusted communication connection to realize cross-device services between devices with different accounts. The operation is simple, so that users can get the usage experience of devices with the same account, and the user experience is better.

[0270] For example, see Fig. 7A In the schematic diagram of the device sharing scenario shown, the first device and the second device log in to the first account, and the third device logs in to the second account. In response to the first operation, the first device sends a target message to the cloud server; the cloud server sends the first trusted authorization information to the second device and sends the second trusted authorization information to the third device according to the target message; the second device performs trusted authentication on the third device according to the first trusted authorization information, and the third device performs trusted authentication on the second device according to the second trusted authorization information. After the trusted authentication on both ends is passed, the second device and the third device establish a trusted communication connection to conduct cross-device services.

[0271] Furthermore, the cloud server may also transmit the first trusted authorization information to the first device. At this time, the second trusted authorization information also includes the association information between the device identification of the first device and the security credentials of the third device. The first device performs trusted authentication on the third device based on the first trusted authorization information, and the third device performs trusted authentication on the first device based on the second trusted authorization information. After the trusted authentication on both ends is passed, the first device and the third device establish a trusted communication connection to conduct cross-device services.

[0272] It is worth noting that the first device can also share itself as a shared device with other users. In this case, the second device and the first device mentioned above can be the same device. The first device responds to the first operation to share the first device with the second account and sends a target message to the cloud server. According to the target message, the cloud server transmits the first trusted authorization information to the first device and the second trusted authorization information to the third device. The first device and the third device perform trusted authentication of the two devices according to the first trusted authorization information and the second trusted authorization information, and then establish a trusted communication connection.

[0273] It should also be noted that after the cloud server 22 sends the trusted authorization information to the terminal device, the terminal device can perform device trusted authentication on the device with the different account according to the trusted authorization information. For example, the first target device receives the trusted authorization information from the cloud server, and the trusted authorization information includes the association information between the device identification and the device security credentials of the second target device. The first target device logs in to the first account, and the second target device logs in to the second account, and the first account and the second account are different.

[0274] The first target device obtains at least one wireless broadcast information scanned; if the device security credentials corresponding to the device identifier in the target wireless broadcast information are queried based on the trusted authorization information, then it is determined that the device corresponding to the target wireless broadcast information is a trusted second target device, and the target wireless broadcast information is one of the broadcast information in the at least one wireless broadcast information; and a communication connection is established with the trusted second target device. That is, the trusted authorization relationship on the cloud side is reflected through the device security credentials on the end side, so that two devices with different accounts can perform device trusted authentication based on the device security credentials of the other end. Furthermore, the trusted authorization information may not be generated based on the device sharing operation, that is, the embodiment of the present application may not apply the device sharing scenario, but may perform device trusted authentication on the other end device based on the locally stored device security credentials of the other end for any two devices with different accounts.

[0275] In order to better introduce the device sharing process, the following will combine Figure 7B The process diagram of device sharing within a home group provided in an embodiment of the present application is illustrated.

[0276] In the family group device sharing scenario, the family group is created by the Owner user. After the user creates the family group, the terminal device generates a group ID and sends it to the home cloud. For example, referring to the scenario diagram shown in 4B, the user can create a new family group by clicking the Create a New Family option in window 49 or clicking the Create a New Family option in the family management interface 410. The mobile phone 121 responds to the user's family group creation operation and sends relevant information to the home cloud. The home cloud assigns a group ID to the family group and records the association between the group ID and the user account or user ID.

[0277] Each time a user is added to a family group, a member ID is assigned to the new member. There are multiple terminal devices in the family group, and each device in the family group has a device ID.

[0278] like Figure 7BAs shown, in this scenario, the system architecture may include account family, home cloud, device cloud, signal ring cloud, device 1, device 2, and device 3. Device 1 and device 3 log in to account A, and device 2 logs in to account B, and account A is different from account B. Device 1 and device 3 are devices of the Owner user, and device 2 is a device of a family group member.

[0279] Device 1 and device 2 both include Smart Life App, HiLink service, soft bus and trusted authorization relationship data. Device 3 includes HiLink service or credential authorization service and trusted authorization relationship data. Device 1 and device 2 can be, for example, mobile phones, and device 3 can be, for example, a large-screen device.

[0280] Among them, Account Family, Home Cloud, Device Cloud, and Signal Ring Cloud are all on the cloud side. Trust Ring Cloud can provide the ability to generate device security credentials and an interface for querying device credentials. It stores various device security credentials and encrypted device security credentials. That is, Trust Ring Cloud can generate device security credentials based on the device information provided by the Device Cloud, and establish a correspondence between the device security credentials and the device identification. After the device security credentials are generated, the device security credentials are persistently stored and a query interface is provided to the outside. The Device Cloud can query the device security credentials corresponding to the device identification (such as the device ID) based on the device identification.

[0281] The device cloud can provide the ability to maintain the relationship between devices and users and the interface for notifying authorization relationships. The device cloud stores the devices associated with each account and the device information of each device. The device cloud usually stores the relationship between the device ID and the user ID or user account (i.e., the DeviceId-Uid relationship).

[0282] The home cloud (or smart home cloud) can provide interfaces for Push, MQTT, message center notification, obtaining account family members, adding family members, requesting authorization relationships, and notifying device cloud authorization relationships. That is, the home cloud can associate each user's account, manage family groups, receive information from each terminal device, send notifications or information to each terminal device, etc. The account family can be regarded as a specific data structure stored on the home cloud, which is an abstract concept. The home cloud can synchronize the family group information of the user account, that is, the home cloud synchronizes members from the account family, and notifies the home cloud when there are new members in the account family. The Smart Life App obtains the new members of the account family from the home cloud.

[0283] like Figure 7B As shown, the process of sharing devices within a family group may include:

[0284] 1. Add family members. The Owner user invites account B to join the family group on the Smart Life App of device 1. The process of inviting users to join the family group can be found in Figure 4B , which will not be described here. Device 1 responds to the Owner user's operation of adding family members and sends relevant information to the home cloud, which may include the family group ID and the member's user ID (UID). In this scenario, the operation of adding family members input by the Owner user on device 1 can be regarded as an operation of sharing the device with account B, and the group ID and member's user ID sent by device 1 to the home cloud can be regarded as the target message.

[0285] 2. Home Cloud pushes or feeds members to confirm authorization. That is, Home Cloud sends an invitation notification message to the smart life app of device 2 through push or feed based on the user ID of the member uploaded by device 1, so that the user of device B can confirm whether to join the family group.

[0286] 3. Member authorization confirmation. After member B confirms to join the family group on the smart life app of device 2, device 2 returns a response message to the home cloud to confirm joining the group, informing the home cloud to confirm joining the family group. After receiving the confirmation message from device 2, the home cloud assigns a member ID to account B and records a sharing relationship (or authorization relationship) to record the trusted authorization relationship between account B and each device under account A.

[0287] 4. After the home cloud responds to the confirmation message returned by device 2, it transmits OwnerId, member ID and DevIds to the device cloud. OwnerId can find the device associated with the Owner user according to the group ID. DevIds can be the device IDs of all devices associated with account A, or a device ID under account A, which is the device ID of device 3 in this example. In other words, the home cloud synchronizes the relationship between Owner, Member and authorized device DevIds to the device cloud;

[0288] 5. The device cloud obtains the device information of device 1, device 2, and device 3 based on OwnerId, member ID, and DevIds, and sends the device information of device 1, device 2, and device 3 to the trust ring cloud. The trust ring cloud generates the DevId credentials of device 1, device 2, and device 3 (i.e., the correspondence between the device security credentials and the device identification) based on the device information, and provides a query interface for the device cloud to query. The device cloud can query the DevId credentials of device 1, device 2, and device 3 from the trust ring cloud based on the device ID.

[0289] The device cloud obtains the DevId credentials of device 1, device 2, and device 3, and pushes a notification to the home cloud. The notification may include DevId and push notification, or Uid and push notification, to inform the home cloud which device to send the trusted authorization relationship to or notify the device to query the trusted authorization relationship.

[0290] 6. Home Cloud sends authorization relationship data to Device 2 and Device 3 according to the push notification of Device Cloud, or notifies Device 2 and Device 3 to actively query authorization relationship data. Of course, Home Cloud can also send authorization relationship data to Device 1, or Device 1 can obtain authorization relationship data from Device 3 through distributed data synchronization technology.

[0291] After device 1, device 2, and device 3 obtain the authorization relationship data, the authorization relationship can be written to the disk (i.e., stored locally). The authorization relationship data of device 1 and device 3 are the same, which can include Uidlist. Uidlist includes DevIdlist and Udidlist corresponding to Uid. The authorization relationship data of device 2 is DevInfolist (DeviId and Udid). Among them, UID is the user ID, DevId (device ID) is the number in the environment, and the device ID will change when the device is deleted or added. Udid is the unique identifier of the device in the entire network. When the device is deleted or added, Udid will not change. Usually, the device identification includes the device ID and the device's Udid. Figure 7B The DevIdlist in includes device security credentials, which typically include a series of security certificates and the device's security identifier, etc.

[0292] exist Figure 7B In the embodiment, device 2 stores the correspondence between the device identification and the device security credentials of device 1 and device 3, and device 3 stores the correspondence between the device identification and the device security credentials of device 2.

[0293] Device 3 can autonomously discover device 2 based on the trusted authorization relationship data, perform trusted authentication on device 2, and establish a trusted communication connection with device 2. Similarly, device 2 can autonomously discover device 1 and device 3 based on the trusted authorization relationship data, perform trusted authentication on device 1 and device 3, and establish a trusted communication connection with device 1 and device 3.

[0294] exist Figure 7B In the scenario shown, the home group owner can share devices within the group with other group members and support the synchronization of device security credentials.

[0295] In some embodiments, after device sharing, the user can cancel device sharing. At this time, the first device 21 can send a cancel sharing instruction to the cloud server 22 in response to the cancel device sharing operation, the cancel device sharing operation is used to cancel sharing of the second device with the second account, and the cancel sharing instruction is used to instruct to cancel sharing of the second device with the second account.

[0296] For example, see Figure 8 The schematic diagram of the cancellation device sharing scenario provided by the embodiment of the present application is shown, based on Figure 4A In the device sharing scenario shown, a "My" control 415 is displayed on the "My Home" interface 42 of the mobile phone 121. After the user clicks the "My" control 415, the mobile phone 121 responds to the click operation and displays an interface 416, and a sharing management option 417 is displayed on the interface 416. After the user clicks the sharing management option 417, the mobile phone 121 responds to the click operation and displays an interface 418. The interface 418 displays information about the devices currently shared by the account and a remove sharing control 419. After the user selects one or more devices to be unshared, the user clicks the remove sharing control 419 to cancel the sharing of the selected devices. At this time, the sixth operation may include the operation of clicking the remove sharing control 419, or multiple operations such as clicking the sharing management option 417 and clicking the remove sharing control 419.

[0297] After the cloud server 22 receives the cancel sharing instruction from the first device 21, it deletes the authorization relationship between the second account and the second device in response to the cancel sharing instruction, and sends a first deletion instruction to the second device and a second deletion instruction to the third device. The first deletion instruction is used to instruct the second device to delete the stored first trusted authorization information, and the second deletion instruction is used to instruct the third device to delete the stored second trusted authorization information.

[0298] It is understandable that if the cloud server 22 sends the first trusted authorization information to the first device 21 during device sharing, the cloud server 22 may also send a deletion instruction to the first device 21 to allow the first device 21 to delete the first trusted authorization information stored locally.

[0299] In this way, when the user of the first device 21 cancels device sharing, the trusted authorization information of the cloud server and the device security credentials stored in the terminal device can be deleted in a timely manner.

[0300] The user may cancel device sharing when the device is offline, and the cloud server 22 cannot promptly notify the offline terminal device to delete the local device security credentials. At this time, if the first device, the second device, or the third device is powered on again after being powered off, they can send a query instruction to the cloud server and receive the response information returned by the cloud server for the query instruction. The query instruction is used to query whether the device sharing relationship is updated. In this way, it can be avoided that the device sharing relationship is not updated in time after a change (for example, canceling sharing) during power-off. When the response information indicates that the device sharing relationship has changed and the device sharing has been canceled, the terminal device promptly deletes the locally stored trusted authorization information. For example, in Figure 7B In the scenario shown, after device 1, device 2 or device 3 is powered on again, it can send a query instruction to the cloud side, which carries the device ID, so that the cloud side can pull again based on the device ID to obtain information such as device security credentials and device identification.

[0301] As described above, through the device sharing solution provided in the embodiment of the present application, the terminal device can locally store the correspondence between the device security credentials and the device identification, and based on the correspondence between the device security credentials and the device identification, perform autonomous discovery, trusted authentication, and automatic connection initiation for devices with different accounts to realize cross-device services.

[0302] In order to better introduce the technical solution provided by the embodiments of the present application, the following will take the super desktop, a cross-device service, as an example to introduce the process of automatic device discovery, authentication and automatic connection after device sharing, as well as the process of using shared devices.

[0303] See also Fig. 9 A framework schematic diagram of a device sharing system provided by an embodiment of the present application is shown. The device sharing system may include a cloud side and a terminal side. The cloud side may include a home cloud, a device cloud, and a trust ring cloud. For a detailed introduction, please refer to the above and will not be repeated here. The software system architecture of the terminal device on the terminal side may include an application layer, a framework and service layer, a hardware abstraction layer (HAL) layer, and a Linux kernel. The first device 21, the second device 23, and the third device 24 may all include the software system architecture.

[0304] The application layer includes applications such as Smart Life, Shell Application, Device Credential Association Service, and End-Cloud Connection Service. Smart Life can provide device sharing and storage, and manage the devices of the family group. Shell Application is responsible for opening and controlling applications across devices. Desktop Application is responsible for synchronizing and displaying application information across devices. End-Cloud Connection Service is used to implement End-Cloud Communication Service, which is responsible for connecting and communicating between end-side devices and cloud services. Device Credential Management Service is used to provide device security credential management capabilities.

[0305] The framework and service layer includes modules such as collaborative configuration management, distributed hardware virtualization, device management (DM), device authentication, device profile (DP) and soft bus.

[0306] Among them, the collaborative configuration management service provides atomic capabilities for collaborative businesses such as "application migration management", "hardware migration management" and "display adaptation strategy". It can make decisions on collaborative strategies based on configurable collaborative rules, and call on the distributed capabilities of the super terminal to achieve collaboration, as well as adaptation of migration management and display strategies.

[0307] Distributed hardware virtualization is used to support the calling of cross-device hardware capabilities, such as calling hardware capabilities such as camera, audio, and GPS through camera virtualization, audio virtualization, and GPS virtualization.

[0308] Device management is used to support device discovery, device binding, querying the trusted device list, and querying currently trusted devices.

[0309] The device profile is used to store trusted authorization relationship data, that is, the correspondence between the device security credentials and the device identity.

[0310] Device authentication is used to support device authentication services.

[0311] The soft bus is used to provide low-level device discovery, device connection and other connection capabilities.

[0312] based on Fig. 9 The software system architecture of the end-side device is shown. After the device is shared, the shared device can monitor the online and offline events of the device through the soft bus. When the device is trusted, the correspondence between the device security credentials and the device identification stored in the DP can be obtained to identify whether there are trusted devices in the surrounding devices (for example, whether there are trusted devices in the family group). After the device is trusted, the device connection is automatically initiated through the soft bus, and the application data of the device is synchronized.

[0313] For example, see Fig.10 A schematic diagram of the super desktop implementation process in a home group device sharing scenario provided by an embodiment of the present application is shown. The process can be divided into multiple stages, including home device scanning, automatic discovery and connection of home devices, and cross-device exchange of application information and user interfaces. Fig.10 The example given is that the family public device is a cockpit or a large-screen device, and the main control device of the family members is the member's mobile phone.

[0314] It is understandable that in a family group device sharing scenario, a family public device is usually used as a shared device and shared with other users in the family group. Figure 1A , the first user 12 and the second user 13 are in the same family group. The first user 12 is the owner and owns the large-screen device 125 and the smart cockpit 126. The large-screen device 125 and the smart cockpit 126 are public devices in the family. The first user 12 shares these public devices with the second user 13 through the device sharing operation on the mobile phone 121. The second user 13 can use the large-screen device 125 and the smart cockpit 126 through the mobile phone 131. For example, based on the super desktop service, the second user 13 can use the applications installed on the mobile phone 131 on the large-screen device 125 and the smart cockpit 126.

[0315] In the home device scanning phase, the home public device and the member master device first turn on the wireless functions such as Bluetooth and Wi-Fi to trigger the home public device and the member master device to send wireless broadcast information outward and scan the surrounding wireless broadcast information. Fig.10 As shown, the member's main control device is a mobile phone, and the family public device is a cockpit or large-screen device. After the mobile phone and the cockpit or large-screen device turn on the Bluetooth function, the family public device scans the Bluetooth broadcasts of surrounding devices.

[0316] During the automatic discovery and connection stage of home devices, through the device discovery capability provided by the soft bus and device management module, after the Bluetooth of the cockpit or large-screen device discovers the device, the device authentication module can be called to perform trusted authentication of the device. During the device authentication process, the device authentication module can query the device security credentials of the mobile phone in DP. If the device security credentials of the mobile phone are queried, it confirms that the mobile phone is safe and reliable, and actively initiates a connection to the mobile phone. After the cockpit or large-screen device establishes a connection with the mobile phone, DM binds the device information of the mobile phone, notifies the desktop application device to go online, and synchronizes the application data of the mobile phone. DP stores the correspondence between the device identification of the mobile phone and the device security credentials, which can be obtained through the device sharing solution mentioned above.

[0317] During the cross-device application information exchange stage, the desktop applications between the mobile phone and the cockpit or large-screen device perform business interactions so that the cockpit or large-screen device obtains the application data of the mobile phone.

[0318] In the user interface stage, the cockpit or large-screen device displays the icons of the mobile phone's application on the super desktop through the shell application and the desktop application based on the application data of the mobile phone, that is, displays the super desktop icon. For example, see Figure 1C In the scenario shown, icons of applications installed on the mobile phone 121 are displayed on the interface of the large-screen device 125 .

[0319] It should be noted that in a family group device sharing scenario, when a device is shared with multiple family group members, the shared device can store the device security credentials of multiple users' terminal devices locally. Based on the device security credentials of multiple users' terminal devices, the terminal devices of multiple users can be automatically discovered and authenticated. For example, see Figure 5 , Xiao Ming and Jack@mail.com are both family group members, and the large screen device 51 can identify Xiao Ming and Jack@mail.com as trusted devices. In addition, the shared device also stores the corresponding relationship between user information and terminal devices locally, and can then identify the user to whom the terminal device belongs, and display the user information on the list of connectable devices.

[0320] As can be seen from the above, through the device sharing solution provided by the embodiment of the present application, the device security credentials of the device with different account can be stored on the terminal side. Based on the device security credentials, the shared device can automatically discover the devices of the family group members (devices with different accounts), perform trusted authentication on the devices of the family group members, and automatically initiate a connection to the devices of the family group members. The family group members do not need to perform trusted authentication by scanning codes and entering pin codes, and do not need to perform operations such as scanning codes and entering pin codes every time they connect. For example, device A can directly access the application list on device B, and support application filtering and control according to device capabilities.

[0321] After the shared device displays the super desktop, the user can use the applications installed on the device with the different account on the shared device. When the user uses the applications installed on the device with the different account on the shared device, the shared device can adapt according to the screen resolution and the horizontal and vertical screen orientation of the device, and support cross-device hardware migration. For example, the shared device can display according to the screen resolution of the device; for another example, the shared device can use the microphone of the device to record applications, use the speakers of the device to play sounds, use the camera of the device to record videos, use the GPS of the device for positioning, and so on.

[0322] For example, see Fig.11 The schematic diagram of the super desktop service provided by the embodiment of the present application is shown, the shared device is a cockpit or a large screen device, and the different account device is a mobile phone. The cockpit or large screen device synchronizes the application data of the mobile phone and displays the super desktop based on the Launcher application. The super desktop includes icons of various applications installed on the mobile phone. The process may include:

[0323] 1. The user clicks on the application icon on the super desktop of the cockpit or large-screen device. The cockpit or large-screen device responds to the click operation by starting or pulling up the projection shell application, loading the application interface of the mobile phone through the projection shell application, and starting the application through starActivity.

[0324] 2. The collaborative configuration management service of the cockpit or large-screen device notifies the collaborative configuration management service of the mobile phone to start the corresponding application.

[0325] 3. The collaborative configuration management service of the mobile phone calculates the application display strategy (such as horizontal and vertical screen switching and resolution adaptation, etc.), calls; calls virtualized hardware capabilities; calls DDMS to create a virtual display; obtains hardware capabilities and uses hardware capabilities (including virtual audio, virtual camera and fused GPS, etc.); configures camera strategies to use the camera of the cockpit or large-screen device; configures audio diversion strategies to divert the media sound and navigation sound of the mobile phone application to the audio device of the cockpit or large-screen device.

[0326] 4. The collaborative configuration management service of the mobile phone calls the system interface to start the application and displays it on the virtual display.

[0327] 5. The mobile phone starts screen projection, which starts the distributed hardware virtualization service and sends the virtual application interface to the cockpit or large-screen device for display.

[0328] 6. The cockpit or large-screen device receives the projection data stream transmitted by the mobile phone, receives the data stream displayed by the mobile phone application, and sends the projection data stream to the shell application for display.

[0329] As can be seen above, in the family group device sharing scenario, the end-side device implements the application flow function based on the device security credentials, and implements the application adaptation device screen display and supports access to distributed hardware capabilities. For example, device A can open the application of device B, the application interface is adapted to the screen of device A, and the application is supported to use various hardware capabilities of device A.

[0330] That is to say, when the user crosses the application icon of the device on the large-screen side, the large-screen starts the HiWindow application; the collaborative configuration management on the large-screen side notifies the collaborative configuration management on the mobile phone side to start the corresponding application; the collaborative configuration management on the mobile phone side processes the application display strategy (parallel field of view / horizontal screen, etc.), calls the virtualization hardware capabilities, and calls DDMS to create a virtual display; the collaborative configuration management service on the mobile phone side calls the AMS interface to start the application and display it on the virtual display; the mobile phone side starts the screen projection service and prepares to project the virtual display to the large-screen side; the large-screen side receives the projection data and displays it in the HiWindow application.

[0331] Among them, HiWindow application is responsible for displaying applications on the mobile phone side; Launcher is used for super desktop formation notification and UI display; collaborative configuration management is used to manage cross-device application migration and hardware migration strategies; parallel horizon is used to support applications to be opened in parallel horizon mode and support application multi-window display. Distributed hardware platform is used to provide hardware virtualization, cast+ screen projection capabilities, etc. Distributed window management (DWMS) is used to provide application screen projection interface capabilities, window display adaptation logic, and architecture reconstruction.

[0332] Fig.12 1 shows a schematic diagram of the structure of an electronic device 1200. The electronic device 1200 may include a processor 1210, a memory 1220 and a communication module 1230. The electronic device 1200 may be a first device, a second device or a third device, and may also be a cloud server.

[0333] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 1200. In other embodiments of the present application, the electronic device 1200 may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware. For example, when the electronic device 1200 is a terminal device, the electronic device 1200 may also include a camera, an audio module, a display screen, a sensor module, and the like.

[0334] The processor 1210 may include one or more processing units, for example, the processor 1210 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. Among them, different processing units may be independent devices or integrated into one or more processors. The controller may generate an operation control signal according to the instruction opcode and the timing signal to complete the control of fetching and executing instructions.

[0335] The communication module 1230 of the electronic device 1200 may be one of a wireless communication module and a mobile communication module.

[0336] The mobile communication module can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 1200. The mobile communication module may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module may receive electromagnetic waves through an antenna, filter, amplify, etc. the received electromagnetic waves, and transmit them to a modulation and demodulation processor for demodulation. The mobile communication module may also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna.

[0337] The wireless communication module 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 electronic device 1200. The wireless communication module can be one or more devices integrating at least one communication processing module. The wireless communication module receives electromagnetic waves via an antenna, modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 1210. The wireless communication module can also receive the signal to be sent from the processor 1210, modulate the frequency, amplify it, and convert it into electromagnetic waves for radiation through the antenna.

[0338] In some embodiments, the antenna of the electronic device 1200 is coupled to the mobile communication module, and the antenna is coupled to the wireless communication module, so that the electronic device 1200 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, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS) and / or satellite based augmentation system (SBAS).

[0339] The memory 1220 may be used to store computer executable program codes, which include instructions. The memory 1220 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 1200 (such as audio data, a phone book, etc.), etc. In addition, the memory 1220 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 1210 executes various functional applications and data processing of the electronic device 1200 by running instructions stored in the memory 1220, and / or instructions stored in a memory provided in the processor.

[0340] For example, when the electronic device 120 is the first device, when the processor 1210 executes the instructions stored in the memory 1220, the relevant process executed by the first terminal device in any of the above-mentioned device sharing processes is implemented, for example, in response to the first operation, a target message is sent to the cloud server.

[0341] For example, when the electronic device 1200 is a second device or a third device, when the processor 1210 executes instructions stored in the memory 1220, the relevant process executed by the second terminal device or the third terminal device in any of the above-mentioned device sharing processes is implemented.

[0342] For example, when the electronic device 1200 is a cloud server, when the processor 1210 executes instructions stored in the memory 1220, it implements the relevant processes executed by the cloud server in any of the above-mentioned device sharing processes, such as generating a correspondence between the device security credentials and the device identification based on the device information, and sending it to the corresponding terminal device.

[0343] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0344] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device capable of carrying the computer program code to an electronic device, a recording medium, a computer memory, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), an electric carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

[0345] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0346] In the embodiments provided in the present application, it should be understood that the disclosed devices, electronic devices and methods can be implemented in other ways. For example, the device / electronic device embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0347] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0348] The electronic device provided in the embodiments of the present application may include a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, a method as described in any one of the above method embodiments is implemented.

[0349] The embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0350] An embodiment of the present application provides a computer program product. When the computer program product runs on an electronic device, the electronic device can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0351] The present application also provides a chip system, which includes a processor coupled to a memory, and the processor executes a computer program stored in the memory to implement the methods described in the above method embodiments. The chip system can be a single chip or a chip module composed of multiple chips.

[0352] In the above-mentioned embodiments, the description of each embodiment has its own emphasis. For the part that is not described or recorded in detail in a certain embodiment, please refer to the relevant description of other embodiments. It should be understood that the size of the sequence number of each step in the above-mentioned embodiment does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. In addition, in the description of the present application specification and the attached claims, the terms "first", "second", "third", etc. are only used to distinguish the description, and cannot be understood as indicating or implying relative importance. The reference "one embodiment" or "some embodiments" described in the present application specification means that one or more embodiments of the present application include specific features, structures or characteristics described in combination with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in the different places in this specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways.

[0353] Finally, it should be noted that the above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A device sharing system, characterized in that: The system comprises a first device, a cloud server, a second device and a third device, wherein the first device and the second device log in to a first account, and the third device logs in to a second account, and the first account is different from the second account; The first device is used to: in response to one or more operations, send a target message to a cloud server, the target message including first information indicating a first account and second information indicating a second account; The cloud server is used to: transmit first trusted authorization information to the second device and transmit second trusted authorization information to a third device according to the first information and the second information; The first trusted authorization information includes association information between the device identification of the third device and the first device security credential; the second trusted authorization information includes association information between the device identification of the second device and the second device security credential; The second device is used to: receive the first trusted authorization information from the cloud server, and store the first trusted authorization information, where the first trusted authorization information is authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device; The third device is used to: receive the second trusted authorization information from the cloud server, and store the second trusted authorization information; The second trusted authorization information is authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device.

2. The system according to claim 1, characterized in that The first device is specifically used for: In response to the first operation, displaying a group member adding interface; receiving a second operation on the group member adding interface, where the second operation is used to determine a user invited to join the group; In response to a third operation, sending the target message to the cloud server; The first information includes the identifier of the group owner or the information of the first account, the second information includes the member identifier of the invited user in the group or the information of the second account, the group owner is the first account, the second device is a device in the group, and the account of the user invited to join the group is the second account.

3. The system according to claim 1, characterized in that The second device is further used to: obtain wireless broadcast information of the third device, the wireless broadcast message of the third device including the device identification of the third device; if the first device security credential corresponding to the device identification of the third device is queried from the first trusted authorization information, the third device is determined to be a trusted device; Alternatively, the third device is also used to: obtain wireless broadcast information of the second device, the wireless broadcast information of the second device including the device identification of the second device; if the second device security credentials corresponding to the device identification of the second device are queried from the second trusted authorization information, it is determined that the second device is a trusted device.

4. The system according to claim 3, characterized in that The second device is also used for: Automatically sending a connection request to the trusted third device; or, if there are at least two trusted third devices, displaying the at least two trusted third devices in a list of connectable devices, and in response to a user's selection operation on the list of connectable devices, sending a connection request to the trusted third device specified by the selection operation.

5. The system according to any one of claims 1 to 4, characterized in that: The first device and the second device are the same device.

6. A device sharing method, characterized in that: Applied to a first device, the method includes: In response to a first operation, displaying a group member adding interface, wherein the first operation is an operation on a group member invitation control; In response to the second operation, a target message is sent to the cloud server, wherein the target message is used to trigger the cloud server to transmit the first trusted authorization information to the second device, and to transmit the second trusted authorization information to the third device; the second operation is an operation on the member invitation option or at least one user information displayed on the group member adding interface, and the second operation is used to determine the user invited to join the group; The target message includes first information for indicating a first account and second information for indicating a second account, the group owner is the first account, the user invited to join the group is the second account; the second device is a device in the group; The first device and the second device log in to the first account, the third device logs in to the second account, and the first account and the second account are different; The first trusted authorization information includes association information between the device identification of the third device and the security credentials of the first device; The second trusted authorization information includes association information between the device identification of the second device and the security credentials of the second device; The first trusted authorization information is authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device, and the second trusted authorization information is authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device.

7. The method according to claim 6, characterized in that The first information includes the identifier of the group owner or the information of the first account, and the second information includes the member identifier of the invited user in the group or the information of the second account.

8. A device sharing method, characterized in that: Applied to a first device, the method includes: In response to a first operation, determining a second device from a plurality of devices logged into the first account, wherein the first operation is used to determine a shared device; In response to the second operation, a target message is sent to the cloud server, the target message is used to trigger the cloud server to transmit the first trusted authorization information to the second device, and to transmit the second trusted authorization information to the third device; the target message includes first information for indicating the first account and second information for indicating the second account; the second operation is an operation on the member sharing option or at least one user information displayed on the sharing member selection interface, the second operation is used to determine the user who shares the second device, and the user who shares the second device is the second account; The first device and the second device log in to the first account, the third device logs in to the second account, and the first account and the second account are different; The first trusted authorization information includes association information between the device identification of the third device and the security credentials of the first device; The second trusted authorization information includes association information between the device identification of the second device and the security credentials of the second device; The first trusted authorization information is authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device, and the second trusted authorization information is authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device.

9. The method according to claim 8, characterized in that The first information includes information of the second device or information of the first account, and the second information includes information of the second account.

10. The method according to claim 6 or 8, characterized in that: After sending the target message to the cloud server, the method further includes: In response to a third operation, a cancel sharing instruction is sent to the cloud server, the third operation is used to cancel sharing of the second device with the second account, the cancel sharing instruction is used to trigger the cloud server to delete the authorization relationship between the second account and the second device, and send a first deletion instruction to the second device and a second deletion instruction to the third device, the first deletion instruction is used to instruct the second device to delete the stored first trusted authorization information, and the second deletion instruction is used to instruct the third device to delete the stored second trusted authorization information.

11. The method according to any one of claims 6 or 8, characterized in that: The second trusted authorization information also includes association information between the device identification of the first device and the security credentials of the third device; the second trusted authorization information is also authentication information used to authenticate the first device during the process of establishing a connection between the first device and the third device; The method further comprises: receiving the first trusted authorization information from the cloud server; Acquire wireless broadcast information of the third device, where the wireless broadcast message of the third device includes a device identifier of the third device; If the first device security credential corresponding to the device identification of the third device is queried from the first trusted authorization information, the third device is determined to be a trusted device; After the third device determines that the first device is a trusted device according to the second trusted authorization information, a communication connection with the third device is established.

12. A device sharing method, characterized in that: Applied to a cloud server, the method comprises: receiving a target message from a first device, the target message including first information indicating a first account and second information indicating a second account, the first account and the second account being different, the target message being information sent by the first device in response to an operation of sharing the second device with the second account, the first device and the second device logging in to the first account; According to the target message, first trusted authorization information is transmitted to the second device, and second trusted authorization information is transmitted to a third device, and the third device logs in to the second account; The first trusted authorization information includes the association information between the device identification of the third device and the security credentials of the first device; the second trusted authorization information includes the association information between the device identification of the second device and the security credentials of the second device; the first trusted authorization information is the authentication information used to authenticate the third device during the process of establishing a connection between the second device and the third device, and the second trusted authorization information is the authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device.

13. The method according to claim 12, characterized in that According to the target message, transmitting the first trusted authorization information to the second device, and transmitting the second trusted authorization information to the third device, comprises: Acquire association information between a device identification of the second device and a security credential of the second device according to the first information; generating the second trusted authorization information according to association information between the device identification of the second device and the security credential of the second device; Acquire association information between the device identification of the third device and the security credential of the first device according to the second information; generating the first trusted authorization information according to association information between the device identification of the third device and the security credential of the first device; The second trusted authorization information is transmitted to the third device, and the first trusted authorization information is transmitted to the second device.

14. The method according to claim 13, characterized in that The method further comprises: Acquire, according to the first information, association information between a device identification of the first device and a security credential of a third device; transmitting the first trusted authorization information to the first device; Generating the second trusted authorization information according to the association information between the device identification of the second device and the security credential of the second device includes: The second trusted authorization information is generated based on the association information between the device identification of the second device and the security credentials of the second device and the association information between the device identification of the first device and the security credentials of the third device. The second trusted authorization information is also the authentication information used to authenticate the first device during the process of establishing a connection between the first device and the third device.

15. The method according to any one of claims 12 to 14, characterized in that The method further comprises: receiving a cancel sharing instruction from the first device, where the cancel sharing instruction is an instruction sent by the first device in response to canceling an operation of sharing the third device with the second account; In response to the cancel sharing instruction, the authorization relationship between the second account and the second device is deleted, and a first deletion instruction is sent to the second device and a second deletion instruction is sent to the third device, the first deletion instruction is used to instruct the second device to delete the stored first trusted authorization information, and the second deletion instruction is used to instruct the third device to delete the stored second trusted authorization information.

16. A device sharing method, characterized in that: Applied to a device sharing system, the device sharing system includes a first device, a second device and a third device, the first device and the second device log in to a first account, the third device logs in to a second account, and the first account is different from the second account; The method comprises: The first device sends a target message to the cloud server in response to one or more operations, the target message including first information indicating a first account and second information indicating a second account, the first operation being used to share the second device with the second account; the target message being used to trigger the cloud server to transmit first trusted authorization information to the second device, and to transmit second trusted authorization information to the third device; The second device receives the first trusted authorization information from the cloud server and stores the first trusted authorization information, where the first trusted authorization information is authentication information used to authenticate the third device during a process of establishing a connection between the second device and the third device; The third device receives the second trusted authorization information from the cloud server and stores the second trusted authorization information, where the second trusted authorization information is authentication information used to authenticate the second device during the process of establishing a connection between the second device and the third device; The first trusted authorization information includes association information between the device identification of the third device and the first device security credential; the second trusted authorization information includes association information between the device identification of the second device and the second device security credential.

17. The method according to claim 16, characterized in that The first device sends a target message to the cloud server in response to one or more operations, including: The first device displays a group member adding interface in response to a first operation, where the first operation is an operation on a group member invitation control; The first device sends the target message to the cloud server in response to a second operation, wherein the second operation is an operation on a member invitation option or at least one user information displayed on the group member adding interface, and the second operation is used to determine a user invited to join the group; The first information includes the identifier of the group owner or the information of the first account, the second information includes the member identifier of the invited user in the group or the information of the second account, the group owner is the first account, the user invited to join the group is the second account, and the second device is a device in the group.

18. The method according to claim 16 or 17, characterized in that The method further comprises: The second device acquires wireless broadcast information of the third device, where the wireless broadcast message of the third device includes a device identifier of the third device; If the second device queries the first device security credential corresponding to the device identification of the third device from the first trusted authorization information, the third device is determined to be a trusted device; After the third device determines that the first device is a trusted device according to the second trusted authorization information, the second device and the third device establish a trusted communication connection.

19. A device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 6 to 11 or 12 to 15 is implemented.

20. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 6 to 11 or 12 to 15 is implemented.

Images