WO2025112740A1 - Permission sharing method and electronic device - Google Patents

Abstract

The present application relates to the technical field of terminals. Provided are a permission sharing method and an electronic device. In the present application, a first electronic device can share a control permission of a smart device with a second electronic device by means of a simple bring-close or tapping operation, thereby simplifying a permission sharing step, and reducing the usage difficulty of a user. The method comprises: a first electronic device displaying a first sharing interface; and detecting an operation of a user on a first interface element in the first sharing interface, and in response to being brought close to or tapped against a second electronic device, the first electronic device sharing with the second electronic device a control permission of a first target smart device corresponding to the first interface element.

Description

Authority sharing method and electronic device

This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office on November 27, 2023, with application number 202311604660.6 and application name “Authority Sharing Method and Electronic Device”, all contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of terminal technology, and in particular to a permission sharing method and electronic device.

Background Art

With the rapid development of the Internet of Things (IoT) technology, various IoT devices have emerged widely, such as smart wearable devices, smart refrigerators, smart curtains, smart door locks, and smart air purifiers. After logging into the first application account (such as smart life application), the electronic device (such as a mobile phone, tablet, etc.) obtains the control authority of the IoT device in response to the user's operation and binds to the IoT device. In this way, the user can control the IoT device bound to the first application account by logging into the first application account, which brings great convenience to the user.

In some scenarios, through permission sharing, other first application accounts can also obtain control permissions for the IoT device, allowing other users to control the IoT device by logging into other first application accounts. However, in the permission sharing process, users usually need to open the device QR code, record the first application account, and use other applications to establish a sharing relationship between other first application accounts and the IoT device. The operation process is cumbersome and difficult for users to use.

Summary of the invention

In order to solve the above technical problems, the present application provides a permission sharing method and electronic device. The technical solution provided by the present application allows a first electronic device to share the control permission of a smart device with a second electronic device through a simple approach or touch operation, thereby simplifying the permission sharing steps and reducing the difficulty of user use.

In order to achieve the above technical objectives, this application provides the following technical solutions:

In a first aspect, a permission sharing method is provided, which is applied to a first electronic device. The method includes: displaying a first sharing interface. Detecting a user's operation on a first interface element in the first sharing interface, and in response to approaching or touching a second electronic device, sharing the control permission of a first target smart device corresponding to the first interface element to the second electronic device.

In this way, the first electronic device and the second electronic device complete the sharing of device control authority based on near field communication, thereby improving the real-time and interactivity of authority sharing, thereby enhancing the user experience.

Furthermore, during the device sharing process, the user only needs to approach or touch the first electronic device to trigger the second electronic device to automatically complete the permission sharing, which is simple for the user to operate and effectively reduces the difficulty of user operation.

According to the first aspect, the method further includes: presenting an animation on the first sharing interface, the animation being used to prompt the user to share the first target smart device corresponding to the first interface element to the second electronic device.

In this way, by displaying dynamic effects, users can quickly confirm the permission sharing status, achieve precise control of shared devices, and effectively improve the user experience.

According to the first aspect, or any implementation of the first aspect above, in response to approaching or touching the second electronic device, the control authority of the first target smart device corresponding to the first interface element is shared with the second electronic device, including: in the process of displaying the first sharing interface, in response to approaching or touching the second electronic device, a communication connection is established with the second electronic device. Through the communication connection, a first account logged in by the second electronic device is obtained. According to the first account, the control authority of the first target smart device corresponding to the first interface element in the first sharing interface is shared with the second electronic device.

In some examples, the second electronic device is pre-set with an identification code, or the second electronic device generates the identification code in response to approaching or touching the first electronic device. Subsequently, the first electronic device and the second electronic device establish a communication connection based on the identification code. This improves the security of the established communication connection and ensures the security of subsequent communications.

In some examples, the first account logged into the second electronic device is, for example, an account of a first application (such as a smart life application) used to manage smart devices by the second electronic device, or the first account is a device-level account, such as a Huawei account.

In this way, the first electronic device and the second electronic device establish a more stable communication connection based on the short-range communication connection to complete the sharing of the control authority of the smart device.

According to the first aspect, or any implementation of the first aspect above, in response to approaching or touching the second electronic device, sharing the control authority of the first target smart device corresponding to the first interface element to the second electronic device includes: in the process of displaying the first sharing interface, in response to approaching or touching the second electronic device, establishing a communication connection with the second electronic device. Through the communication connection, sending the second account logged in by the first electronic device to the second electronic device, the second account is used to share the control authority of the first target smart device corresponding to the first interface element in the first sharing interface to the second electronic device.

In some examples, the first electronic device is a central control device, then in response to approaching or touching, the second electronic device can obtain the second account of the first electronic device, so that the second electronic device can obtain the control authority of the smart device in the home currently managed by the first electronic device. Optionally, the second account is the first application account or a device-level account.

In some examples, when the second electronic device requests permission sharing from the server based on the second account of the first electronic device, the server may also request authorization from the permission management device corresponding to the second account to ensure the security of permission sharing.

According to the first aspect, or any implementation of the first aspect above, the first interface element includes a display element associated with the first target smart device, and the method further includes: sharing the first interface element to the second electronic device.

According to the first aspect, or any implementation of the first aspect above, the first interface element is a card.

In this way, the second electronic device can not only obtain the authority of the smart device shared by the first electronic device, but also directly obtain the interface elements shared by the first electronic device for controlling the smart device, thereby facilitating the user to determine the entry to control the smart device and simplifying the user's operation.

According to the first aspect, or any implementation of the first aspect above, the first interface element includes a display element associated with an added user, and the added user is used to control the first target smart device; in response to approaching or touching the second electronic device, the method also includes: displaying a second interface element, and the second interface element includes a display element associated with a user of the second electronic device.

In some examples, the first sharing interface includes a space management interface associated with the space where the first target smart device is located. Then, after the first electronic device determines that the control authority of the first target smart device has been shared with the second electronic device, the second interface element can be displayed on the first sharing interface to prompt the user that the second electronic device currently obtains the control authority of the smart device in the space where the first target smart device is located.

In some examples, the display element associated with the user of the second electronic device is, for example, an avatar of the first application logged into the second electronic device, a home icon, etc.

According to the first aspect, or any implementation of the first aspect above, the animation includes an animation of a first interface element associated with the first target smart device moving out, or an animation of a display element associated with a user of the second electronic device moving in.

In this way, by displaying the movement of elements in or out, users can have a vivid understanding of the permission sharing situation.

According to the first aspect, or any implementation method of the first aspect above, in response to approaching or touching the second electronic device, the control authority of the first target smart device corresponding to the first interface element is shared with the second electronic device, and also includes: in response to approaching or touching the second electronic device, the control authority of the second target smart device corresponding to the first interface element is shared with the second electronic device, and the first target smart device and the second target smart device belong to the same space or the same scene.

In this way, during the home sharing process, the user only needs to perform a simple touch operation to trigger the first electronic device and the second electronic device to automatically complete the sharing of the home group. The user operation is simple and the difficulty of user operation is effectively reduced.

Furthermore, the first electronic device and the second electronic device complete home sharing based on near field communication, thereby improving the real-time and interactivity of home sharing, thereby enhancing the user experience.

According to the first aspect, or any implementation of the first aspect above, approaching or touching is based on one or more of the following communication technologies: NFC (near field communication) technology, BLE (low power consumption) Bluetooth technology, and NAN (near field local area network) communication technology.

In this way, users can share the control rights of the smart device managed by the first electronic device with the second electronic device through short-distance communication methods such as approaching or touching. Compared with other device sharing methods, users no longer need to enter Huawei accounts or open other applications through the first electronic device, which effectively simplifies user operations.

According to the first aspect, or any implementation of the first aspect above, the control authority is an authority range specified by a user of the first electronic device.

In this way, the user can set the sharing permissions of the first target smart device according to needs.

In some examples, the first electronic device may share permissions with the second electronic device including permissions to share scenes or spaces. In some examples, the user may also set permissions to allow editing of scenes.

According to the first aspect, or any one of the implementations of the first aspect above, the first sharing interface includes a user interface for managing at least one The device management interface of a smart device or the space management interface associated with the space where the first target smart device is located.

According to the first aspect, or any implementation of the first aspect above, the first electronic device is a user terminal or a central control device in a space.

In a second aspect, a permission sharing method is provided, which is applied to a second electronic device. The method includes: in response to approaching or touching a first electronic device, receiving the control permission of a first target smart device shared by the first electronic device, wherein the first target smart device displays an animation corresponding to a first interface element displayed by the first electronic device on a first sharing interface, and the animation is used to prompt a user that the second electronic device obtains the control permission of the first target smart device.

According to a second aspect, the animation includes an animation of a first interface element associated with the first target smart device moving in, and the first interface element moving out on the first sharing interface. Or, an animation of a display element associated with a user of the first electronic device moving in.

According to the second aspect, or any implementation of the second aspect above, the method further includes: adding a first interface element in the device management interface. Alternatively, switching the displayed first space management interface to a second space management interface, the first space management interface corresponds to a user of the second electronic device, and the second space management interface corresponds to a user of the first electronic device.

In some examples, when a user performs family sharing, he needs to operate the devices in the family. Therefore, after obtaining the control authority of the family shared by the first electronic device, the second electronic device can switch to display the device management interface of the family, so as to facilitate the user to operate the device.

According to the second aspect, or any implementation of the second aspect, the first interface element is a card.

According to the second aspect, or any implementation of the second aspect above, in response to approaching or touching the first electronic device, receiving the control authority of the first target smart device shared by the first electronic device includes: in response to approaching or touching the first electronic device, establishing a communication connection with the first electronic device. Through the communication connection, sending the first account logged in by the second electronic device to the first electronic device, the first account is used to share the control authority of the first target smart device with the second electronic device.

According to the second aspect, or any implementation of the second aspect above, in response to approaching or touching the first electronic device, receiving the control authority of the first target smart device shared by the first electronic device includes: in response to approaching or touching the first electronic device, establishing a communication connection with the first electronic device. Obtaining a second account logged in by the first electronic device through the communication connection. Obtaining the control authority of the first target smart device based on the second account.

In a third aspect, a first electronic device is provided. The first electronic device includes: a processor, a memory and a display screen, the memory and the display screen are coupled to the processor, the memory is used to store computer program code, the computer program code includes computer instructions, and when the processor reads the computer instructions from the memory, the first electronic device executes: displaying a first sharing interface. Upon detecting a user's operation on a first interface element in the first sharing interface, in response to approaching or touching a second electronic device, the control authority of the first target smart device corresponding to the first interface element is shared with the second electronic device.

According to the third aspect, when the processor reads computer instructions from the memory, it also enables the first electronic device to execute: presenting an animation on the first sharing interface, the animation is used to prompt the user to share the first target smart device corresponding to the first interface element to the second electronic device.

According to the third aspect, or any implementation of the third aspect, in response to approaching or touching the second electronic device, the control authority of the first target smart device corresponding to the first interface element is shared with the second electronic device, including: in the process of displaying the first sharing interface, in response to approaching or touching the second electronic device, a communication connection is established with the second electronic device. Through the communication connection, a first account logged in by the second electronic device is obtained. According to the first account, the control authority of the first target smart device corresponding to the first interface element in the first sharing interface is shared with the second electronic device.

According to the third aspect, or any implementation of the third aspect above, in response to approaching or touching the second electronic device, sharing the control authority of the first target smart device corresponding to the first interface element to the second electronic device includes: in the process of displaying the first sharing interface, in response to approaching or touching the second electronic device, establishing a communication connection with the second electronic device. Through the communication connection, sending the second account logged in by the first electronic device to the second electronic device, the second account is used to share the control authority of the first target smart device corresponding to the first interface element in the first sharing interface to the second electronic device.

According to the third aspect, or any implementation of the third aspect above, the first interface element includes a display element associated with the first target smart device, and when the processor reads the computer instructions from the memory, it also enables the first electronic device to execute: sharing the first interface element to the second electronic device.

According to the third aspect, or any implementation of the third aspect, the first interface element is a card.

According to the third aspect, or any implementation of the third aspect above, the first interface element includes an element associated with adding a user. display element, adding a user for controlling the first target smart device; in response to approaching or touching the second electronic device, when the processor reads computer instructions from the memory, the first electronic device also executes: displaying a second interface element, the second interface element including a display element associated with the user of the second electronic device.

According to the third aspect, or any implementation of the third aspect above, the animation includes an animation of a first interface element associated with the first target smart device moving out, or an animation of a display element associated with a user of the second electronic device moving in.

According to the third aspect, or any implementation method of the third aspect above, in response to approaching or touching the second electronic device, the control authority of the first target smart device corresponding to the first interface element is shared with the second electronic device, and also includes: in response to approaching or touching the second electronic device, the control authority of the second target smart device corresponding to the first interface element is shared with the second electronic device, and the first target smart device and the second target smart device belong to the same space or the same scene.

According to the third aspect, or any implementation method of the third aspect above, approaching or touching is based on one or more of the following communication technologies: NFC, low-power BLE, and NAN.

According to the third aspect, or any implementation of the third aspect, the control authority is an authority range specified by a user of the first electronic device.

According to the third aspect, or any implementation of the third aspect above, the first sharing interface includes a device management interface for managing at least one smart device, or a space management interface associated with the space where the first target smart device is located.

According to the third aspect, or any implementation of the third aspect above, the first electronic device is a user terminal or a central control device in a space.

In a fourth aspect, a second electronic device is provided. The second electronic device includes: a processor, a memory, and a display screen, the memory and the display screen are coupled to the processor, the memory is used to store computer program code, the computer program code includes computer instructions, when the processor reads the computer instructions from the memory, the second electronic device executes: in response to approaching or touching the first electronic device, receiving the control authority of the first target smart device shared by the first electronic device, wherein the first target smart device displays an animation corresponding to the first interface element displayed by the first electronic device on the first sharing interface, and the animation is used to prompt the user that the second electronic device obtains the control authority of the first target smart device.

According to a fourth aspect, the animation includes an animation of a first interface element associated with the first target smart device moving in, and the first interface element moving out on the first sharing interface. Or, an animation of a display element associated with a user of the first electronic device moving in.

According to the fourth aspect, or any implementation of the fourth aspect above, when the processor reads the computer instruction from the memory, the second electronic device is also caused to execute: adding the first interface element in the device management interface. Or, the displayed first space management interface is switched to the second space management interface, the first space management interface corresponds to the user of the second electronic device, and the second space management interface corresponds to the user of the first electronic device.

According to the fourth aspect, or any implementation of the fourth aspect, the first interface element is a card.

According to the fourth aspect, or any implementation of the fourth aspect above, in response to approaching or touching the first electronic device, receiving the control authority of the first target smart device shared by the first electronic device includes: in response to approaching or touching the first electronic device, establishing a communication connection with the first electronic device. Through the communication connection, sending the first account logged in by the second electronic device to the first electronic device, the first account is used to share the control authority of the first target smart device with the second electronic device.

According to the fourth aspect, or any implementation of the fourth aspect, in response to approaching or touching the first electronic device, receiving the control authority of the first target smart device shared by the first electronic device includes: in response to approaching or touching the first electronic device, establishing a communication connection with the first electronic device. Obtaining a second account logged in by the first electronic device through the communication connection. Obtaining the control authority of the first target smart device based on the second account.

In a fifth aspect, an electronic device is provided, which has the function of implementing the permission sharing method as described in the first aspect and any possible implementation thereof; or, the electronic device has the function of implementing the permission sharing method as described in the second aspect and any possible implementation thereof. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

In a sixth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program (also referred to as an instruction or code), and when the computer program is executed by an electronic device, the electronic device executes the method of the first aspect or any one of the implementations of the first aspect; or the electronic device executes the method of the second aspect or any one of the implementations of the second aspect.

In a seventh aspect, a computer program product is provided, which, when executed on an electronic device, causes the electronic device to The electronic device is equipped to execute the method of the first aspect or any one of the implementation modes of the first aspect; or, the electronic device is enabled to execute the method of the second aspect or any one of the implementation modes of the second aspect.

In an eighth aspect, a circuit system is provided, the circuit system comprising a processing circuit, the processing circuit being configured to execute the method of the first aspect or any one of the embodiments of the first aspect; or, the processing circuit being configured to execute the method of the second aspect or any one of the embodiments of the second aspect.

In the ninth aspect, a chip system is provided, comprising at least one processor and at least one interface circuit, wherein the at least one interface circuit is used to perform transceiver functions and send instructions to the at least one processor, and when the at least one processor executes the instructions, the at least one processor executes the method of the first aspect or any one of the embodiments of the first aspect; or, the at least one processor executes the method of the second aspect or any one of the embodiments of the second aspect.

The technical effects of the aforementioned aspects can be referenced to each other and will not be elaborated here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a device permission sharing interface provided in an embodiment of the present application;

FIG. 2 is a second schematic diagram of a device permission sharing interface provided in an embodiment of the present application;

FIG3 is a schematic diagram of a communication system for applying the authority sharing method provided in an embodiment of the present application;

FIG4 is a schematic diagram of the hardware structure of a first electronic device provided in an embodiment of the present application;

FIG5 is a schematic diagram of the hardware structure of a server provided in an embodiment of the present application;

FIG6 is a third schematic diagram of a device permission sharing interface provided in an embodiment of the present application;

FIG. 7 is a fourth schematic diagram of a device permission sharing interface provided in an embodiment of the present application;

FIG8 is a fifth schematic diagram of a device permission sharing interface provided in an embodiment of the present application;

FIG9 is a sixth schematic diagram of a device authority sharing interface provided in an embodiment of the present application;

FIG10 is a flowchart of a method for sharing permissions provided in an embodiment of the present application;

FIG11 is a seventh schematic diagram of a device authority sharing interface provided in an embodiment of the present application;

FIG12 is a schematic diagram of an eighth device authority sharing interface provided in an embodiment of the present application;

FIG13 is a second flowchart of the permission sharing method provided in an embodiment of the present application;

FIG14 is a ninth diagram of a device authority sharing interface provided in an embodiment of the present application;

FIG15 is a schematic diagram of a device permission sharing interface provided in an embodiment of the present application;

FIG16 is a schematic diagram 11 of a device authority sharing interface provided in an embodiment of the present application;

FIG17 is a third flowchart of the permission sharing method provided in an embodiment of the present application;

FIG18 is a fourth flowchart of a method for sharing permissions provided in an embodiment of the present application;

FIG19 is a flowchart of a method for sharing permissions according to an embodiment of the present application;

FIG20 is a schematic diagram of the structure of a first electronic device provided in an embodiment of the present application;

FIG. 21 is a schematic diagram of the structure of a second electronic device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present application are described below in conjunction with the accompanying drawings in the embodiments of the present application. Wherein, in the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and the appended claims of the present application, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to include expressions such as "one or more", unless there is a clear indication to the contrary in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one or more (including two).

References to "one embodiment" or "some embodiments" etc. described in this specification mean that one or more embodiments of the present application include a particular feature, structure or characteristic described in conjunction with the embodiment. Thus, the phrases "in one embodiment", "in some other embodiments", "in other embodiments", etc. appearing in different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in another way. The term "connected" includes direct and indirect connections, unless otherwise specified. "First" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implying Indicate the number of technical features indicated.

In the embodiments of the present application, the words "exemplarily" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a specific way.

In some embodiments, the smart home system uses the residence as a platform and utilizes technologies such as the Internet of Things and automatic control to organically combine various electronic devices and application subsystems related to home life. Among them, users can manage devices in the smart home system by logging into a smart life application account, such as smart wearable devices, smart refrigerators, smart curtains, smart door locks, and smart air purifiers.

In some examples, after an electronic device (such as a mobile phone, tablet, etc.) logs in to a smart life application account, it binds to an IoT device in response to a user operation and obtains control authority over the IoT device. In some examples, after an IoT device is bound to a smart life application account for the first time, the smart life application account is the primary account for managing the IoT device. After the electronic device logs in to the primary account, the authority to control the IoT device can be shared with other electronic devices, and the smart life application account logged in by other electronic devices is a slave account. That is, the slave account can obtain authority to control some or all IoT devices under the primary account, and the control authority obtained by the slave account may be less than or equal to the control authority of the primary account over the IoT device. Generally, for IoT devices, the electronic device logged in to the primary account is the primary device, and the electronic device logged in to the slave account is the slave device.

Exemplarily, as shown in FIG. 1 (a), the mobile phone displays a smart life application interface 101, which is used to display cards of multiple IoT devices managed under the current smart life application account. The mobile phone detects the user's operation of clicking the ceiling light card 11, and can display a menu bar window 12 including the operation content that can be performed on the ceiling light card 11. The mobile phone detects the user's operation on the shared device control 13 displayed in the menu bar window 12, and determines that the user instructs to share the permission to control the ceiling light corresponding to the ceiling light card 11 with other electronic devices. Then, the mobile phone can display an interface 102 as shown in FIG. 1 (b), and display the sharing method of sharing permissions on the interface, such as scanning a code to share, sharing through a Huawei account, and sharing to friends in the address book.

For example, the mobile phone detects the user's operation on the scan code sharing control 14, and determines that the user instructs to share the authority to control the ceiling light with the peer device by scanning the QR code of the peer device. Then, as shown in Figure 2, the mobile phone (i.e., device 1) displays the code scanning interface. In addition, the user also needs to open the QR code display interface of the peer device (i.e., device 2). After that, the user can use device 1 to scan the QR code displayed by device 2, so that device 1 shares the authority to control the ceiling light with device 2.

It can be seen that in the above permission sharing process, users need to perform corresponding operations on both devices. The sharing path is relatively long and the operation is cumbersome, which affects user usage.

For another example, when sharing device permissions through Huawei account sharing, the user needs to enter the Huawei account of the other device (such as the same as the smart life account of the other device), and then the electronic device can share the control permissions of the device selected by the user with the device logged in with the Huawei account. It can be seen that in this process, it is more difficult for users to remember Huawei accounts.

For another example, when sharing device permissions through address book friends, the electronic device needs to respond to user operations, pull up other applications, and display address book friend information for the user to select. The user needs to browse and select the friend account to be shared. After that, the electronic device shares the control permissions of the device selected by the user to the device corresponding to the friend account selected by the user. It can be seen that in this process, the sharing path is relatively long, and other applications need to be pulled up, which makes the user operation cumbersome.

In addition, after completing the sharing of device permissions through various methods mentioned above, it is difficult for users to find devices that have shared control permissions under the smart life application account that has obtained the control device permission. Then, users may think that the control permission sharing has failed, affecting the user experience. For example, there are already many IoT devices under the smart life application account that has obtained the control device permission. Users need to find the required IoT device in the display information of multiple IoT devices, which is difficult.

In this regard, an embodiment of the present application provides a permission sharing method, through a simple approach or touch operation, a first electronic device can share the control authority of a smart device with a second electronic device, thereby simplifying the permission sharing steps and reducing the difficulty of user use.

Fig. 3 is a schematic diagram of a communication system to which the authority sharing method provided in an embodiment of the present application is applied. As shown in Fig. 2, the communication system includes a first electronic device 100, a second electronic device 200, a third electronic device 300 and a server 400.

Optionally, the first electronic device 100 may be a dedicated device for controlling smart home devices, or a device including the function of controlling smart home devices. For example, the first electronic device 100 may be a smart home device control panel, or a terminal device such as a mobile phone, a tablet, a smart speaker, a smart watch, etc. Among them, the smart home device control panel is a dedicated device for controlling smart home devices in a smart home system. In some embodiments, the first electronic device 100 may be a fixed device or a portable device. The present application does not impose any special restrictions on the specific form of the first electronic device 100.

Optionally, as shown in FIG. 3 , the first electronic device 100 may be connected to one or more third electronic devices 300 for managing and controlling the third electronic devices 300 .

Optionally, the third electronic device 300 may be, for example, a speaker, a smart screen, a desk lamp, a light, a camera, an air purifier, a mobile phone, a tablet computer, a personal computer (PC), a personal digital assistant (PDA), a netbook, a wearable electronic device, an artificial intelligence terminal, or other terminal devices. The present application does not impose any special restrictions on the specific form of the third electronic device 300. The operating system installed in the third electronic device 300 includes but is not limited to Or other operating systems. The third electronic device 300 may not be installed with an operating system. In some embodiments, the third electronic device 300 may be a fixed device or a portable device. This application does not limit the specific type of the third electronic device 300, whether an operating system is installed, and the operating system installed when an operating system is installed.

In some embodiments, the third electronic device 300 is an IoT device. The first electronic device 100 is installed with a first application. The first application is capable of connecting to the IoT device, editing and controlling the IoT device. As shown in FIG. 3 , the first electronic device 100 is connected to one or more third electronic devices 300 through the first application. Optionally, the first application is a smart life application.

In some examples, the first electronic device 100 completes the registration of the third electronic device 300 after logging into the first account of the first application. The first electronic device 100 sends the registration information of the third electronic device, such as device information, to the server 400. In some examples, the server 400 manages one or more third electronic devices 300 included in one or more homes on a home basis. During the registration process of the third electronic device 300, the server 400 adds the third electronic device 300 to the corresponding home. In some examples, one or more homes are managed under the first account of the first application logged in by the first electronic device 100. The server 400 can obtain the first account, one or more homes, and device information under different homes, and manage them.

Optionally, the server 400 may be a device or network device with computing functions such as a cloud server or a network server. The server 400 may be a single server, or a server cluster consisting of multiple servers, or a cloud computing service center. The server 400 may also be described as a smart home cloud platform, which is used to manage smart home devices included in the smart home system, scenes corresponding to the smart home devices, etc.

In some embodiments, a wireless communication connection is established between the first electronic device 100 and the second electronic device 200. The wireless communication technology for establishing the wireless communication connection includes but is not limited to at least one of the following: Bluetooth (BT) (e.g., traditional Bluetooth or Bluetooth low energy (BLE)), wireless local area networks (WLAN) (e.g., wireless fidelity (Wi-Fi) networks), near field communication (NFC), Zigbee, frequency modulation (FM), infrared (IR), etc.

Optionally, the first electronic device 100 and the second electronic device 200 may also establish a communication connection through a third-party device in the local area network, such as a router, a gateway, a smart device controller, a server, etc.

In some embodiments, the second electronic device has the first application installed and the second account of the first application logged in. In some examples, the second electronic device needs to obtain the permission to control the third electronic device 300, and the user can share the permission to control the third electronic device 300 with the second electronic device 200 by operating the first electronic device 100 that has the ability to control the third electronic device 300.

In some examples, the second electronic device 200 is a device including a function of controlling smart home devices, and the device type of the second electronic device 200 is the same as or different from the device type of the first electronic device 100. The second electronic device 200 can be connected to one or more third electronic devices 300, and the one or more connected third electronic devices 300 can be controlled by the first application. It should be understood that the third electronic device 300 connected to the first electronic device 100 is the same as, or different from, or partially the same as the third electronic device 300 connected to the second electronic device 200. The third electronic device 300 that the first electronic device 100 shares control authority with the second electronic device 200 is a device that has not established a connection with the second electronic device 200.

In some embodiments, the operating system is, for example, a smart home system, and the third electronic device 300 is a smart home device. Alternatively, the operating system is a smart office system, and the third electronic device 300 is a smart office device. Alternatively, the communication system may also be other communication systems such as a smart campus communication system, which is not limited in the present embodiment of the application. The following takes the case where the communication system is, for example, a smart home system and the third electronic device 300 is a smart home device as an example to describe in detail the permission sharing method provided in the present embodiment of the application.

Optionally, the first electronic device 100, the second electronic device 100, the third electronic device 300, and the server 400 in the embodiment of the present application may be implemented by different devices, and the different devices may have the same, similar, or somewhat different hardware structures. Structure, such as the hardware structure shown in Figure 4 or Figure 5.

For example, taking the first electronic device 100 having the hardware structure shown in FIG. 4 as an example, the hardware structure shown in FIG. 4 is described.

Exemplarily, FIG4 shows a schematic structural diagram of the first electronic device 100 .

The first electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the first electronic device 100. In other embodiments of the present application, the first electronic device 100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

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

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

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

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

The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple groups of I2C buses. The processor 110 may be coupled to the touch sensor, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor through the I2C interface, so that the processor 110 communicates with the touch sensor through the I2C bus interface to realize the touch function of the first electronic device 100.

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

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

It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the first electronic device 100. In other embodiments of the present application, the first electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

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

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

The wireless communication function of the first electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

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

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

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

The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the first electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of the signal, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

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

In some embodiments, the first electronic device 100 communicates with the server 400 and the second electronic device 200 via the mobile communication module 150 or the wireless communication module 160 to achieve sharing of control authority of the third electronic device 300, etc.

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

The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be manufactured using a liquid crystal display (LCD), such as an organic light-emitting diode (OLED), an active matrix organic light-emitting diode or an active matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Mini-LED, Micro-LED, Micro-oled, quantum dot light-emitting diodes (QLED), etc. In some embodiments, the first electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

In some embodiments, the first electronic device 100, in response to a user operation, determines that the user indicates to share the third electronic device 300 during the process of displaying the first application through the display screen 194. Afterwards, in response to the user's touch operation, the identification code of the second electronic device 200 is obtained, and based on the identification code, the first electronic device 100 and the second electronic device 200 establish a secure communication connection. Afterwards, based on the interaction of the secure communication connection, the first electronic device 100 can obtain the account logged in by the second electronic device, and thus request the server 400 to obtain a sharing code for sharing the control authority of the third electronic device 300 with the second electronic device 200 through the wireless communication module 160. In this way, the second electronic device 200 can subsequently obtain the authority to control the third electronic device 300 based on the sharing code.

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

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the first electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and videos are stored in the external memory card.

The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 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 first electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 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 110 executes various functional applications and data processing of the first electronic device 100 by running instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110. The first electronic device 100 can use the audio module 170, such as music playing, recording, etc. The audio module 170 can include a speaker, a receiver, a microphone, a headphone interface, and an application processor to implement audio functions.

The sensor module 180 may include a pressure sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

A touch sensor is also called a "touch control device". The touch sensor can be arranged on the display screen 194, and the touch sensor and the display screen 194 form a touch screen, also called a "touch control screen". The touch sensor is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor can also be arranged on the surface of the first electronic device 100, which is different from the position of the display screen 194.

The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The first electronic device 100 may receive key input and generate key signal input related to user settings and function control of the first electronic device 100.

Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

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

The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or disconnected from the first electronic device 100 by inserting or removing the SIM card interface 195. The first electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1.

For example, taking the server 400 having the hardware structure shown in FIG. 5 as an example, the hardware structure shown in FIG. 5 is described.

5 is a schematic diagram of the hardware structure of a server 400 provided in an embodiment of the present application. The server 400 includes at least one processor 401, a communication line 402, a memory 403 and at least one communication interface 404. The memory 403 may also be included in the processor 401.

It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the server 400. In other embodiments of the present application, the server 400 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

Processor 401 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

The communication link 402 may include a pathway to transmit information between the above-mentioned components.

Communication interface 404, used to communicate with other devices. In the embodiment of the present application, the communication interface can be a module, a circuit, a bus, an interface, a transceiver or other device capable of implementing a communication function, used to communicate with other devices. Optionally, when the communication interface is a transceiver, the transceiver can be an independently arranged transmitter, which can be used to send information to other devices, and the transceiver can also be an independently arranged receiver, which is used to receive information from other devices. The transceiver can also be a component that integrates the functions of sending and receiving information, and the embodiment of the present application does not limit the specific implementation of the transceiver.

The memory 403 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may be independent and connected to the processor via the communication line 402. The memory may also be integrated with the processor.

The memory 403 is used to store computer-executable instructions for implementing the solution of the present application, and the execution is controlled by the processor 401. The processor 401 is used to execute the computer-executable instructions stored in the memory 403, thereby implementing the authority sharing method provided in the following embodiments of the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, instructions, computer program or other names, which are not specifically limited in the embodiments of the present application.

In a specific implementation, as an embodiment, the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 5 .

In a specific implementation, as an embodiment, the server 400 may include multiple processors, such as the processor 401 and the processor 405 in FIG5 . Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

The device structures described in FIG. 4 and FIG. 5 may also be applicable to a second electronic device or other two-party devices for authority sharing.

In the following, the permission sharing method provided in the embodiment of the present application is described in detail by taking the first electronic device 100 as a device having control authority over the third electronic device 300, the second electronic device 200 as a device that needs to obtain control authority over the third electronic device 300, the third electronic device 300 as an IoT device (such as smart devices such as smart home devices), and the server 400 as a smart home cloud server as an example.

In some embodiments, the first electronic device starts a first application (such as a smart life application) in response to a user operation. Optionally, the smart life application is used to manage at least one smart device included in the home.

In some examples, when the first electronic device is running the first application, the first electronic device can share the control authority of at least one smart device in the home with the second electronic device in response to the user operation. Optionally, the control authority is the authority range specified by the user of the first electronic device. For example, the first electronic device determines that the shared control authority includes the authority to control the startup or shutdown of the smart device in response to the user's setting operation, but does not include the authority to adjust parameters, etc.

In some examples, when the first electronic device displays the first sharing interface, it detects the user's operation on the first interface element in the first sharing interface, and it can be determined that the user instructs to share the control authority of the first target smart device corresponding to the first interface element with the second electronic device. Then, in response to approaching or touching the second electronic device, the first electronic device can share the control authority of the first target smart device corresponding to the first interface element with the second electronic device.

Optionally, the first sharing interface is a device management interface, which is used to display a card corresponding to at least one smart device in the home, through which the corresponding smart device can be controlled, so that the user can manage at least one smart device through the device management interface. The first interface element is, for example, a card displayed on the first sharing interface.

Optionally, the approach or touch is based on one or more of NFC technology, BLE Bluetooth technology, and near-field local area network (neighbor awareness networking, NAN) communication technology. Optionally, the communication technology based on NAN is, for example, wireless fidelity surrounding awareness Wi-Fi aware communication technology. Optionally, in some possible sharing scenarios supported by short-distance communication technology, there is no need for clear approach or touch actions between devices. Instead, when the distance between devices is within a certain range, a connection can be directly established through the corresponding communication technology and sharing can be carried out between each other.

Exemplarily, as shown in FIG. 6 (a), the first electronic device displays a first sharing interface 601, which is a device management interface, including cards corresponding to multiple smart devices included in home (such as A's home), and the cards display some information, control buttons, etc. of the smart device. The user can select the device to be shared according to his own needs. For example, the first electronic device detects the user's operation on card 61 (i.e., the first interface element) and displays a menu bar window 62. Afterwards, the first electronic device detects the user's operation of clicking the shared device control 63 displayed in the menu bar window 62, and determines that the user instructs to share the ceiling light in the living room corresponding to card 61 (i.e., the first target smart device). That is, the first electronic device detects the user's operation of instructing to share the device. Afterwards, as shown in the interface 602 in FIG. 6 (b), the first electronic device can display a window 64, and display a card 65 corresponding to the first target smart device selected by the user for sharing in the window 64. It should be understood that the number of devices selected by the user to share is one or more. In addition, the window 64 also displays the device sharing method, as shown by reference numeral 66, and the first electronic device can display a prompt message to prompt the user to share the device by touching it.

In this way, users can share the control rights of the smart device managed by the first electronic device with the second electronic device through short-distance communication methods such as approaching or touching. Compared with other device sharing methods, users no longer need to enter Huawei accounts or open other applications through the first electronic device, which effectively simplifies user operations.

In some embodiments, the first interface element includes a display element associated with the first target smart device, and the first electronic device can also share the first interface element with the second electronic device.

For example, if the first interface element is a card, then in the above example scenario, the first electronic device can also share the card with the second electronic device. Then, after the second electronic device displays the card, the user can control the first target smart device through the card.

Exemplarily, as shown in the device management interface 701 in (a) of FIG. 7 , as shown in the figure mark 71, the home managed by the second electronic device (such as B's home) includes 11 smart devices, and the device management interface 701 displays the cards corresponding to the 11 smart devices. Subsequently, the second electronic device obtains the control authority of the first target smart device (such as the light in the living room) in response to approaching or touching the first electronic device, and obtains the first interface element corresponding to the first target smart device (such as the card corresponding to the light in the living room). Then, as shown in the interface 702 in (b) of FIG. 7 , as shown in the figure mark 72, the number of smart devices in B's home managed by the second electronic device becomes 12, and the second electronic device can display the first interface element (such as card 73).

In this way, the second electronic device can not only obtain the permissions of the smart device shared by the first electronic device, but also directly obtain The interface elements shared by the first electronic device for controlling the smart device make it easier for the user to determine the entry point for controlling the smart device, thereby simplifying the user's operation.

In some embodiments, the user can select one or more smart devices to be shared in the device management interface through the above method. In some examples, the first electronic device can create a scene or space based on user operations. Then, the user can also directly select the scene or space to be shared, so that the first electronic device can directly share the control rights of multiple smart devices in the scene or space selected by the user to the second electronic device based on the user's operation. That is, the first sharing interface includes a device management interface for managing at least one smart device, or a space management interface associated with the space where the first target smart device is located.

Optionally, the above space is, for example, an entire home, or a room in a home, or an office or conference room in an office scenario.

Optionally, the sharing of the control authority of the smart device in the scene includes not only the control authority of the smart device in the scene shared with the second electronic device, but also the editing authority of the scene. Optionally, the user can select the scope of the control authority to be shared.

Exemplarily, as shown in FIG8 , the first interface element displayed by the first electronic device on the smart life application interface 801 includes not only a card 81 corresponding to a smart device, but also a card 82 corresponding to a scene and a card 83 corresponding to a space. Then, in response to the user's operation on card 82 (or card 83), the first electronic device can determine that the user instructs to share the control rights of multiple smart devices in the scene (or space) corresponding to card 82 (or card 83) with the second electronic device. For example, the multiple smart devices include a first target smart device and a second target smart device, and the first target smart device and the second target smart device belong to the same space or the same scene. In response to approaching or touching the second electronic device, the first electronic device shares the control rights of the first target smart device and the second target smart device corresponding to the first interface element with the second electronic device.

Correspondingly, as shown in Figure 9, the second electronic device can also obtain the first interface element shared by the first electronic device. As shown in interface 901, the second electronic device can display a scene card 91, a space card 92, and a device card 93 shared by the first electronic device.

In this way, in a richer smart device management scenario, the user can share the control rights of multiple smart devices in a scene or space to a second electronic device through simple operations, thereby improving the user experience.

In some scenarios, the first electronic device establishes a short-distance communication connection in response to approaching or touching the second electronic device, thereby sharing the control authority of the first target smart device to the second electronic device based on the short-distance communication connection. The method shown in Figure 10 is used as follows to introduce in detail the method of establishing the short-distance communication connection and sharing the control authority based on the short-distance communication connection.

FIG10 is a flowchart of a permission sharing method provided in an embodiment of the present application. It should be noted that the method is not limited to FIG10 and the specific sequence described below. It should be understood that in other embodiments, the order of some steps in the method can be interchanged according to actual needs, or some steps can be omitted or deleted. The method includes the following steps:

S1001: A first electronic device detects that a user instructs a device sharing operation in a first application.

The first application is, for example, a smart life application for managing and controlling the third electronic device. The operation of indicating the sharing device is, for example, an operation of the user selecting the third electronic device to be shared.

For example, as shown in FIG6(a), when the first electronic device displays the smart life application interface 601, it detects the user's operation on the card 61 and displays the menu bar window 62. Afterwards, the first electronic device detects the user's operation of clicking the shared device control 63 displayed in the menu bar window 62, and determines that the user's operation of indicating the sharing device is detected.

S1002: In response to a preset operation, the first electronic device obtains an identification code generated by the second electronic device.

In some examples, the preset operation is, for example, an operation of tapping to initiate a near field communication connection (such as an NFC connection, etc.). It should be understood that the preset operation may also be other operations that are convenient for the user to implement, such as a shake operation, etc.

In some embodiments, the second electronic device generates an identification code after launching the first application in response to a user operation, and writes the identification code into the NFC tag. Optionally, after writing the identification code into the NFC tag, the second electronic device can mark the NFC mode as a tag mode. In this way, after the first electronic device and the second electronic device detect the user's bump operation, the first electronic device can read the preset identification code in the NFC tag of the second electronic device. Optionally, the NFC mode of the first electronic device is a card reader mode.

Optionally, the identification code generated by the second electronic device is, for example, a personal identification number (PIN) code.

In some examples, the second electronic device may not preset the identification code, but respond to the touch operation of the first electronic device, press Generate an identification code according to a preset period. In this way, the first electronic device can also obtain the identification code generated by the second electronic device. Optionally, the second electronic device is in any display interface, and generates an identification code in response to a touch operation of the first electronic device. Optionally, the second electronic device generates an identification code in response to the touch operation and starts the first application.

For example, the first electronic device determines the second electronic device located nearby by Bluetooth distance measurement or the like. In addition, the second electronic device is pre-installed with a vibration sensor, and in response to a preset operation of the user, the second electronic device can detect the touch operation through the vibration sensor and generate an identification code.

In some embodiments, after the second electronic device starts the first application and writes the generated identification code into the NFC tag, it marks its own NFC mode as tag mode. Later, if the second electronic device detects the user's instruction to share the device in the first application, it can modify the NFC mode mark to reader mode. Optionally, when the NFC mode of the second electronic device is reader mode, the identification code in the NFC tag can be deleted. Later, after the second electronic device exits the device sharing interface, it can trigger the generation of the identification code again. Alternatively, the second electronic device does not delete the identification code in the NFC tag.

In this way, compared with other sharing methods, users no longer need to enter their Huawei account or open other applications through the first electronic device, which effectively simplifies user operations.

S1003: The first electronic device and the second electronic device negotiate a communication key based on the identification code and establish a secure communication connection.

In some embodiments, after acquiring the identification code of the second electronic device, the first electronic device may send a Bluetooth connection request to the second electronic device. Optionally, the first electronic device sends the Bluetooth connection request to the second electronic device by Bluetooth broadcasting. Correspondingly, after the bump operation, the second electronic device may turn on Bluetooth broadcasting to receive the Bluetooth connection request broadcasted by the first electronic device.

In some embodiments, in response to the Bluetooth connection request, the first electronic device and the second electronic device may establish a Bluetooth connection. In some examples, to ensure the security of Bluetooth communication, the first electronic device and the second electronic device may negotiate a key based on the identification code of the second electronic device to generate a communication key. Subsequently, the first electronic device and the second electronic device encrypt the communication data using the communication key, thereby ensuring the security of the communication data transmission, that is, establishing a secure communication connection.

In some examples, during the communication key negotiation process, the first electronic device sends sin1 to the second electronic device, and the second electronic device sends sin2 to the second electronic device. Afterwards, the first electronic device and the second electronic device may generate the same communication key based on sin1, sin2 and the identification code of the second electronic device. Optionally, sin1 is, for example, a sin code preset in the first electronic device, or a sin code generated by the first electronic device using a preset algorithm. Sin2 is, for example, a sin code preset in the second electronic device, or a sin code generated by the second electronic device using a preset algorithm.

In other examples, the first electronic device and the second electronic device are pre-set with an identical number (eg, a large number greater than a preset threshold), and the first electronic device and the second electronic device can generate the same communication key based on the number and the identification code of the second electronic device.

It should be understood that in addition to the two communication key negotiation methods exemplified above, the first electronic device and the second electronic device may also perform communication key negotiation through other methods, which will not be exemplified one by one in the embodiments of the present application.

S1004: The first electronic device obtains the account number used to log in to the second electronic device through a secure communication connection.

In some examples, the account logged into the second electronic device is, for example, the smart life application account currently managing the first target smart device. Alternatively, the account may also be a device-level account, such as a Huawei account.

In some embodiments, during the device sharing process, the first electronic device shares device permissions with the second electronic device. Based on this, the first electronic device is described as the owner device, and the account logged in by the first electronic device is ownerId. The second electronic device is described as a member device, and the account logged in by the second electronic device is UserId.

In some embodiments, after establishing a secure communication connection with the first electronic device, the second electronic device may send the UserId encrypted by the communication key to the first electronic device. In some examples, the second electronic device may also send the UserId to the first electronic device in response to an account acquisition request sent by the first electronic device.

Optionally, the above steps S1002 and S1003 are optional steps. In response to a preset operation, the first electronic device can also directly obtain the first account (such as a smart life account or a Huawei account) logged in by the second electronic device.

S1005: The first electronic device sends the device identification of the device to be shared and the account number for logging in to the second electronic device to the server.

In some embodiments, the first electronic device can determine the device to be shared and the device identifier of the device to be shared in response to the user's instruction to share the device. Then, after obtaining the account logged in by the second electronic device, the first electronic device can send the device identifier and the account to the server to request to obtain a sharing code for sharing the device corresponding to the device identifier with the account.

For example, the first electronic device sends the device identifier (deviceId) of the device to be shared and the member UserId of the second electronic device to the server.

S1006: The server generates a sharing code according to the device identification and the account used to log in to the second electronic device.

In some embodiments, after receiving the deviceId and member UserId sent by the first electronic device, the server determines that the third electronic device corresponding to the deviceId is a device controlled by the account logged in by the first electronic device. Afterwards, the server may generate a corresponding sharing code (shareCode).

In some examples, the sharing code generated by the server is configured with an expiration condition, which includes, for example, a usage count requirement, a usage time requirement, etc. For example, to ensure the security of device permission sharing, the sharing code can be used at most once. Optionally, the server can also set a valid usage period for the sharing code, such as valid for 5 minutes.

S1007: The server sends a sharing code to the first electronic device.

In some embodiments, after generating the sharing code, the server feeds back the sharing code to the first electronic device. Correspondingly, the first electronic device receives the sharing code fed back by the server.

S1008: The first electronic device sends a sharing code to the second electronic device.

In some embodiments, after receiving the sharing code, the first electronic device encrypts the sharing code using the communication key. Then, the first electronic device sends the encrypted sharing code to the second electronic device. Correspondingly, the second electronic device receives the encrypted sharing code sent by the first electronic device. Then, the second electronic device can decrypt the encrypted sharing code to obtain the sharing code.

S1009: The second electronic device sends a device sharing request to the server, where the device sharing request carries a sharing code.

In some embodiments, after obtaining the sharing code, the second electronic device may send a device sharing request to the server to request control authority of the device corresponding to the sharing code carried in the device sharing request. Correspondingly, the server receives the device sharing request sent by the second electronic device.

In some examples, when the first application is logged in to its own first application account, the second electronic device sends a device sharing request to the server so that its own first application account can obtain control authority over the device to be shared.

S1010: The server establishes a sharing relationship between the second electronic device and the device to be shared according to the account number and sharing code logged in by the second electronic device.

In some embodiments, after receiving the device sharing request, the server parses and authenticates the sharing code. For example, the server determines whether the sharing code is correct, such as by determining whether the sharing code is generated by the server and meets the expiration condition requirements. If the sharing code is correct, the server further parses and authenticates the sharing code. If the sharing code is wrong, the server sends a device sharing failure response to the second electronic device.

Afterwards, if the sharing code is correct, the server obtains the device identification and the first application account indicated by the sharing code. Afterwards, the server determines whether the account logged in by the second electronic device that sent the device sharing request is the same as the first application account indicated by the sharing code. If so, the server can determine that the second electronic device meets the sharing conditions, and can share the device to be shared corresponding to the device identification with the second electronic device. If not, the server can determine that the second electronic device does not meet the sharing conditions, and can send a device sharing failure response to the second electronic device.

In some embodiments, the server manages one or more third electronic devices under the account of the first application through the account of the first application. Then, the server can establish a sharing relationship between the second electronic device and the device to be shared by adding the device identification of the device to be shared to the account logged in by the second electronic device.

In some embodiments, after the server establishes a sharing relationship between the second electronic device and the device to be shared, it may send a sharing success response to the second electronic device. Optionally, the sharing success response carries device information of the device to be shared, such as a device identifier, a device media access control (MAC) address, etc. In this way, after receiving the sharing success response, the second electronic device can obtain the authority to control the device to be shared, such as establishing a communication connection with the device to be shared based on the device information carried in the sharing success response. Optionally, the authority to control the device to be shared includes, for example, the authority to use the device to be shared, the authority to share the device to be shared again, the authority to cancel the sharing relationship with the device to be shared, etc.

In some examples, the second electronic device's control authority over the device to be shared is less than or equal to the first electronic device's control authority over the device to be shared. In some examples, the first electronic device can determine the scope of authority to share with the second electronic device to control the device to be shared based on user operations.

In this way, the first electronic device and the second electronic device share the control authority of the device based on the near field communication, thereby improving the authority sharing. The real-time and interactivity of sharing can enhance the user experience.

Furthermore, during the device sharing process, the user only needs to perform a simple touch operation to trigger the first electronic device and the second electronic device to automatically complete the permission sharing, which is simple for the user to operate and effectively reduces the difficulty of user operation.

In some scenarios, since the second electronic device may control other devices, after the device sharing is completed, the user may not know that the device has been shared successfully, or cannot find the control entrance of the shared device, which affects the user's experience. Based on this, the permission sharing method provided in the embodiment of the present application can display a sharing animation after the device permissions are shared to help the user confirm the permission sharing status of the device.

In some examples, the first electronic device presents an animation on the first sharing interface, which is used to prompt the user to share the first target smart device corresponding to the first interface element to the second electronic device. For example, the animation includes an animation of the first interface element associated with the first target smart device moving out.

For example, as shown in interface 602 in (b) of FIG6 , in response to the user's tap operation, the first electronic device determines that the ceiling light of the living room corresponding to card 65 has been successfully shared with the second electronic device. Then, as shown in interface 101 of FIG11 , the first electronic device can display a sharing animation of card 65 moving outside window 64, thereby vividly informing the user that the control authority of the current living room light has been shared with other devices.

In some other examples, the second electronic device displays an animation, which is used to prompt the second electronic device to obtain the control authority of the first target smart device. For example, the animation includes an animation of a first interface element associated with the first target smart device moving in.

For example, as shown in (a) of FIG12, during the process of the second electronic device displaying the smart life application interface 1201, in response to the user's touch operation, it is determined that the control authority of the ceiling light in the living room controlled by the first electronic device has been successfully obtained. Then, as shown in the interface 1202 in (b) of FIG12, the second electronic device can display the card 121 (i.e., the first interface element) corresponding to the ceiling light in the living room. Optionally, the display content of the card 121 corresponding to the ceiling light in the living room can be notified by the first electronic device or the server, or automatically generated by the second electronic device according to the device information.

In some examples, on the smart life application interface, the second electronic device displays multiple cards corresponding to multiple devices in order according to certain rules. For example, the display position of the cards corresponding to the devices is arranged according to the device location, device usage frequency, device type, etc. Therefore, after the second electronic device obtains the control authority of the ceiling light in the living room and displays the corresponding card 121, it can display an animation until the card 121 moves to the appropriate display position shown in the interface 1203 shown in (c) of Figure 12. That is, through the moving-in animation, the user is vividly informed that the current second electronic device has obtained the control authority of the living room light, and helps the user quickly determine the display position of the card 121 corresponding to the living room light, so that the user can operate the card 121 corresponding to the living room light.

In some embodiments, as shown in the method of FIG10 above, the first electronic device shares the control authority of the first target smart device through interaction with the second electronic device and the server. Then, after the authority sharing is successful, the first electronic device and the second electronic device can also obtain the message of the successful sharing through interaction, thereby displaying the sharing animation.

FIG13 is a flowchart of another permission sharing method provided in an embodiment of the present application. It should be noted that the method is not limited to FIG13 and the specific sequence described below. It should be understood that in other embodiments, the order of some steps in the method can be interchanged according to actual needs, or some steps can be omitted or deleted. The method includes the following steps:

S1301. The server sends a sharing success response to the second electronic device.

S1302: The server sends a sharing success response to the first electronic device.

In some embodiments, after determining that a sharing relationship is established between the second electronic device and the device to be shared, the server may send a sharing success response to the first electronic device and the second electronic device respectively to inform the first electronic device and the second electronic device that the current server has shared the permissions of the device to be shared with the second electronic device.

In some examples, the server can determine the first electronic device corresponding to the sharing code according to the sharing code carried in the device sharing request sent by the second electronic device. Then, after determining that the sharing relationship is established, the server can send a sharing success response to the first electronic device, and carry the device identification of the device to be shared and the first application account of the second electronic device in the sharing success response. In this way, after receiving the sharing success response, the first electronic device can determine which smart devices are shared with which control device.

In some examples, the sharing success response sent by the server to the second electronic device carries the device information of the successfully shared smart device. Alternatively, the sharing success response sent by the server to the second electronic device does not carry the device information of the successfully shared smart device, and after receiving the sharing success response, the first electronic device sends the device information of the successfully shared smart device to the second electronic device through the secure communication connection between the first electronic device and the second electronic device.

In some examples, the server may first send a sharing success response to the first electronic device, and then send a sharing success response to the second electronic device. Alternatively, the server may first send a sharing success response to the second electronic device, and then send a sharing success response to the first electronic device. That is, the embodiment of the present application does not limit the execution order of step S1301 or step S1302.

In other examples, the server may send a sharing success response to the first electronic device or the second electronic device separately.

For example, after the server sends a sharing success response to the second electronic device, the second electronic device determines the first electronic device corresponding to the device that has been successfully shared indicated by the sharing success response. Afterwards, the second electronic device sends a device sharing success indication to the first electronic device through a secure communication connection with the first electronic device, and the device sharing success indication carries the device identification of the successfully shared smart device. In this way, after receiving the device sharing success indication, the first electronic device can also determine that the device corresponding to the device identification has been shared with the second electronic device. That is, step S1302 is an optional step.

For another example, after the server sends a sharing success response to the first electronic device, the first electronic device determines the device that has been successfully shared indicated by the sharing success response and the corresponding second electronic device. Afterwards, the first electronic device sends a device sharing success indication to the second electronic device through a secure communication connection with the second electronic device, and the device sharing success indication carries the device information of the successfully shared smart device. In this way, after receiving the device sharing success indication, the second electronic device can also determine the control authority of the device corresponding to the device information. That is, step S1301 is an optional step.

S1303: The first electronic device displays a sharing animation.

In some embodiments, after determining that a device has been shared successfully, the first electronic device may display a sharing animation to prompt the user that the device has been shared with other devices.

It should be understood that after the first electronic device shares the authority to control a certain smart device with other devices, the first electronic device still has the authority to control the smart device.

S1304: The second electronic device displays a sharing animation.

In some embodiments, after determining that a device has been shared successfully, the second electronic device may display a sharing animation to prompt the user that the user has currently obtained permission to control the device.

It should be understood that the embodiments of the present application do not limit the execution order of step S1303 and step S1304, and whether to execute step S1303 or step S1304.

In this way, by displaying the sharing animation, users can quickly confirm the device sharing status, accurately control the shared devices, and effectively improve the user experience.

In some scenarios, a user operating a second electronic device may need to control all third electronic devices in a home controlled by a first electronic device. Through the method shown in FIG. 10 above, control authority over all third electronic devices can be shared, but the process of selecting a third electronic device may be more complicated and involve a large amount of data transmission.

In some embodiments, the first sharing interface displayed by the first electronic device may also be a space management interface associated with the space where the first target smart device is located. In this way, in response to approaching or touching the second electronic device, the first electronic device may share the control authority of the smart device managed in the space management interface with the second electronic device.

Exemplarily, as shown in (a) of FIG. 14 , the first electronic device displays a smart life application interface 1401. Among them, one or more homes are managed under the account currently logged in by the smart life application, as shown in reference numeral 141, and the home currently displayed is A's home. In response to the user's operation on the control indicated by reference numeral 141, the first electronic device displays a menu bar window 142. Thereafter, in response to the user's operation on the home management control 143 in the menu bar window 142, the first electronic device may display a home management interface 1402 as shown in (b) of FIG. 14 . In response to the user's operation on the control 144 on the home management interface 1402, the first electronic device may display a home details page 1403 (i.e., a first sharing interface) as shown in (c) of FIG. The home details page 1403 displays detailed information of A's home, such as home name, home location, family members, etc. Thereafter, the first electronic device detects the user's operation on the add member control 145 (i.e., the first interface element), and determines that the user instructs to add family members to A's home. Afterwards, the first electronic device determines to share the currently displayed A's home with the second electronic device in response to the user's tap operation.

In some examples, the first interface element includes a display element associated with adding a user, such as the add member control 145. The added user is used to control the first target smart device. Then, after the smart device in the home is successfully shared, the first electronic device may display a second interface element, which includes a display element associated with the user of the second electronic device. Optionally, the first electronic device may also display an animation, which includes an animation of a display element associated with the user of the second electronic device moving in.

For example, as shown in interface 1404 in (d) of FIG. 14 , the first electronic device displays a sharing animation, as shown in reference numeral 146 , and the first electronic device displays the avatar (or home icon) of the smart life application logged in by the second electronic device moving into the currently displayed Afterwards, as shown in interface 1501 of FIG. 15 , the first electronic device displays avatars 151 (i.e., second interface elements) in the family details page of A's home. If the avatar 151 is the avatar of the smart life application account logged in by the second electronic device, the user can confirm that the current home has been successfully shared with the second electronic device.

In some examples, after the permissions of the smart device are shared successfully, the second electronic device may also display an animation.

For example, as shown in interface 1601 in (a) of FIG16 , the second electronic device displays a smart life application, as shown in reference numeral 161, the family managed under the account currently logged into the smart life application is B's family, and the number of devices included in the family is 11. Afterwards, in response to the user's touch operation, the second electronic device determines that the family sharing is successful. Then, as shown in interface 1602 in (b) of FIG16 , the second electronic device displays an animation of the avatar (or family icon) 162 of the smart life application logged into the first electronic device flying into the currently displayed smart life interface, thereby helping the user confirm that the family sharing has been completed.

In some examples, when a user performs family sharing, he needs to operate the devices in the family. Therefore, after obtaining the control authority of the family shared by the first electronic device, the second electronic device can switch to display the device management interface of the family, so as to facilitate the user to operate the device.

For example, as shown in interface 1603 in (c) of FIG16 , after displaying the home sharing animation, the second electronic device can directly switch to display the device management interface corresponding to A's home that has been successfully shared, as shown by reference numeral 163. In this way, the user's home switching operation is simplified and the user's experience is improved.

Optionally, to enable the first electronic device and the second electronic device to display other contents of the shared animation, reference may be made to the relevant contents of steps S1301 to S1304 shown in FIG. 13 above, which will not be described in detail in this embodiment of the present application.

In this way, during the home sharing process, the user only needs to perform a simple touch operation to trigger the first electronic device and the second electronic device to automatically complete the sharing of the home group. The user operation is simple and the difficulty of user operation is effectively reduced.

Furthermore, the first electronic device and the second electronic device complete home sharing based on near field communication, thereby improving the real-time and interactivity of home sharing, thereby enhancing the user experience.

In some scenarios, the first electronic device establishes a short-range communication connection in response to approaching or touching the second electronic device, thereby sharing the control authority of the first target smart device in the home to the second electronic device based on the short-range communication connection. The method of sharing the control authority of the home group is described in detail below through the method shown in Figure 17.

In some examples, the server can achieve permission sharing of all third electronic devices in a home by adding the first application account of the second electronic device as a family member of a home in the first application account of the first electronic device, enriching the device permission sharing scenarios and improving the user experience.

FIG17 is a flowchart of another permission sharing method provided in an embodiment of the present application. It should be noted that the method is not limited to FIG17 and the specific sequence described below. It should be understood that in other embodiments, the order of some steps in the method can be interchanged according to actual needs, or some steps can be omitted or deleted. The method includes the following steps:

S1701: The first electronic device detects that a user instructs in a first application to add a family member.

In some embodiments, the first application of the first electronic device provides an entry for adding family members. For example, the user can add family members by entering a Huawei account. It can be seen that it is difficult for the user to remember the Huawei account. Therefore, based on the permission sharing method as shown in the example of FIG. 10 above, the first electronic device and the second electronic device can also complete the addition of family members based on near field communication.

Exemplarily, as shown in the family details page 1403 in (c) of FIG. 14 , the first electronic device detects the user's operation on the add member control 145 and determines that the user instructs to add a family member to A's home.

S1702: In response to a preset operation, the first electronic device obtains an identification code generated by the second electronic device.

S1703: The first electronic device and the second electronic device negotiate a communication key based on the identification code and establish a secure communication connection.

S1704: The first electronic device obtains the account number used to log in to the second electronic device through a secure communication connection.

In some embodiments, when the first electronic device is displaying a family details page (such as family details page 1403), a preset operation (such as a tap operation) is detected, and it can be determined that an operation of the user indicating to add a family member is detected. That is, when the first electronic device is displaying the family details page, the user can directly trigger the first electronic device to add a family member through a tap operation without having to operate the add member control, thereby simplifying the user operation.

Optionally, for other contents of step S1702 to step S1704, reference may be made to the relevant contents of the above-mentioned step S1002 to step S1004, which will not be repeated here.

S1705: The first electronic device sends a home identifier and a second electronic device that the first application currently displays home to the server. The account you are logged in with.

In some embodiments, the first electronic device detects a user's instruction to add a family member during the process of running the first application. Therefore, the first electronic device can determine which home managed by the first application account is currently displayed by the first application, and then obtain the family identification of the home. Then, after obtaining the account logged in by the second electronic device, the first electronic device can send the family identification and the account to the server to request a sharing code for adding the account to the home corresponding to the family identification.

For example, the first electronic device sends to the server the home identifier (homeId) of the first application currently displaying home and the member UserId of the second electronic device.

In some examples, only one home is managed under the account logged in by the first electronic device. Then, after obtaining the account logged in by the second electronic device, the first electronic device can directly send the account to the server to obtain the sharing code. That is, the first electronic device does not need to send the home identifier to the server again. The server can also determine the unique home based on the account logged in by the first electronic device and generate the corresponding sharing code.

S1706. The server generates a sharing code according to the family identification and the account used to log in to the second electronic device.

In some embodiments, after receiving the homeId and member UserId sent by the first electronic device, the server determines that the home corresponding to the homeId is the home managed under the account logged in by the first electronic device. Afterwards, the server may generate a corresponding sharing code (shareCode).

In some examples, the sharing code generated by the server is configured with an expiration condition, which includes, for example, a usage count requirement, a usage time requirement, etc. For example, to ensure the security of device permission sharing, the sharing code can be used at most once. Optionally, the server can also set a valid usage period for the sharing code, such as valid for 5 minutes.

S1707: The server sends a sharing code to the first electronic device.

S1708: The first electronic device sends a sharing code to the second electronic device.

S1709: The second electronic device sends a family sharing request to the server, where the family sharing request carries a sharing code.

In some embodiments, the home sharing request sent by the second electronic device to the server carries a sharing code, which is used to share the control authority of the third electronic device in the home corresponding to the homeId, thereby joining the home corresponding to the homeId and sharing the home of the first electronic device.

Optionally, for other contents of step S1707 to step S1709, reference may be made to the relevant contents of the above-mentioned step S1007 to step S1009, which will not be repeated here.

S1710. The server establishes a sharing relationship between the second electronic device and the home indicated by the sharing code according to the account number and the sharing code used to log in to the second electronic device.

In some embodiments, after receiving the family sharing request, the server parses and authenticates the sharing code. For example, the server determines whether the sharing code is correct, such as by determining whether the sharing code is generated by the server and meets the expiration condition requirements. If the sharing code is correct, the server further parses and authenticates the sharing code. If the sharing code is wrong, the server sends a family sharing failure response to the second electronic device.

Afterwards, if the sharing code is correct, the server obtains the family identification and the first application account indicated by the sharing code. Afterwards, the server determines whether the account logged in by the second electronic device that sends the family sharing request is the same as the first application account indicated by the sharing code. If so, the server can determine that the second electronic device meets the sharing conditions and can share the family corresponding to the family identification with the second electronic device. If not, the server can determine that the second electronic device does not meet the sharing conditions and can send a family sharing failure response to the second electronic device.

In some embodiments, the server manages one or more households under the account of the first application through the account of the first application. Then, after determining to share the household of the first electronic device with the second electronic device, the server can obtain the information of the household managed under the account logged in by the first electronic device, such as the household identification, the device information of at least one third electronic device recorded under the household, etc. Afterwards, the server creates a new household under the first application account logged in by the second electronic device, and sets the information of the newly created household to the information of the household of the first electronic device that has been successfully shared, thereby establishing a sharing relationship between the second electronic device and the home corresponding to the household identification.

In some embodiments, after the server establishes a sharing relationship between the second electronic device and the home corresponding to the home identifier, it may send a home sharing success response to the second electronic device. Optionally, the sharing success response carries information about the home, such as the home identifier, device information of at least one third electronic device recorded under the home, etc. After a successful response to home sharing, you can obtain the authority to manage the home, such as establishing a communication connection with the devices in the home based on the device information carried in the successful response to home sharing.

In some examples, the control authority of the second electronic device over the shared home is less than or equal to the control authority of the first electronic device over the shared home.

In this way, during the home sharing process, the user only needs to perform a simple touch operation to trigger the first electronic device and the second electronic device to automatically complete the sharing of the home group. The user operation is simple and the difficulty of user operation is effectively reduced.

Furthermore, the first electronic device and the second electronic device complete home sharing based on near field communication, thereby improving the real-time and interactivity of home sharing, thereby enhancing the user experience.

The above article introduces the permission sharing process by taking the example of the first electronic device actively performing a touch operation with the second electronic device to initiate the permission sharing process. In some examples, the second electronic device may also actively initiate the permission sharing process, and the following article introduces the process of the second electronic device actively initiating permission sharing in detail.

In some examples, the first electronic device is a user terminal or a central control device in a space. In some scenarios, when the first electronic device is a central control device, the second electronic device can obtain control rights for smart devices in the home managed by the central control device in response to approaching or touching the first electronic device.

FIG18 is a flowchart of another permission sharing method provided in an embodiment of the present application. It should be noted that the method is not limited to FIG18 and the specific sequence described below. It should be understood that in other embodiments, the order of some steps in the method can be interchanged according to actual needs, or some steps can be omitted or deleted. The method includes the following steps:

S1801. The second electronic device obtains an identification code preset by the first electronic device in response to a preset operation while displaying the first application.

In some embodiments, an identification code is pre-installed in the first electronic device, the identification code is written into the NFC tag, and the NFC mode is marked as a tag mode.

In some examples, after the first electronic device is started, it starts running the smart life application to trigger the NFC mode to be marked as tag mode.

In some examples, the first electronic device is a dedicated device for managing at least one third electronic device. For example, the first electronic device is a smart home device control panel, a smart home device central control screen, etc. The first electronic device is a fixed device, which is fixedly set at a certain location in the home, so that other users can bring the second electronic device into the home and request to join the group (home) managed by the first electronic device by touching it.

In some examples, the first electronic device is used to manage at least one third electronic device in the home where it is currently located. For example, there are multiple homes under the first application account logged in by the first electronic device, but after logging in to the first application account, the first electronic device (such as a smart home device control panel) will display a home interface that matches the current location based on the positioning, thereby managing the third electronic device in the home where it is currently located. Alternatively, when the first electronic device is logging in to the first application account, the server determines the home where the first electronic device is located, so that after logging in to the first application account, the first electronic device can only display the device management interface of the home and manage the devices in the home.

S1802: The first electronic device and the second electronic device negotiate a communication key based on the identification code and establish a secure communication connection.

S1803. The second electronic device obtains the account number and family identification of the first electronic device through a secure communication connection.

In some examples, when the number of homes under the account logged in by the first electronic device is one, the first electronic device may not need to feedback the home identifier to the second electronic device. Subsequently, the server may determine a unique home based on the account logged in by the first electronic device.

In some examples, the second account of the first electronic device acquired by the second electronic device may be a smart life application account, or may be a device-level account logged in by the first electronic device, such as a Huawei account.

Optionally, for other contents of step S1802 to step S1803, reference may be made to the relevant contents of the above-mentioned step S1003 to step S1004, which will not be repeated here.

S1804: The second electronic device sends a group joining request to the server, where the group joining request carries the account number and family identification used to log in to the first electronic device.

In some embodiments, after obtaining the account and home ID of the first electronic device, the second electronic device can send a group joining request to the server to request to join the home corresponding to the home ID under the account of the first application. Correspondingly, the server receives the group joining request sent by the second electronic device.

S1805. The server sends a permission acquisition request to the permission management device.

S1806. The rights management device sends a rights acquisition response to the server.

In some embodiments, the server obtains the account of the first application carried in the group joining request, and determines the permission management device corresponding to the account.

Optionally, the rights management device is, for example, at least one device that has logged into the account and is currently logged in. For example, if the user has logged into the account on multiple devices such as a mobile phone and a tablet, and the account is currently logged in on the mobile phone, the server can determine that the mobile phone is a rights management device. Alternatively, if the account is logged in on both the mobile phone and the tablet, the server can determine that both the mobile phone and the tablet are rights management devices.

Optionally, the permission management device is, for example, a device for registering an account of the first application.

In some embodiments, after determining the authority management device, the server may send a permission acquisition request to the authority management device to determine whether the user using the authority management device authorizes the second electronic device to join the group.

Optionally, the permission acquisition request carries the family identifier and the account number logged in by the second electronic device. In this way, after receiving the permission acquisition request, the permission management device can display corresponding prompt information according to the family identifier and the account number of the first application to prompt the user to confirm whether to allow the account number of the first application to be added to the home corresponding to the family identifier. Afterwards, the permission management device generates a permission acquisition response according to the user operation.

In some embodiments, during the authorization process, the rights management device may also determine the scope of the rights authorized by the user according to the user's operation, such as allowing the second electronic device to obtain the control rights of all devices in the home, or allowing the second electronic device to obtain the control rights of some devices in the home, or not allowing the second electronic device to obtain the control rights of the devices in the home.

S1808. The server adds the account logged in by the second electronic device to the group corresponding to the family identification according to the account logged in by the second electronic device.

In some embodiments, the server determines whether the second electronic device is authorized based on the received permission acquisition response. For example, if the permission acquisition response indicates that the second electronic device is not authorized, the server may send a group joining failure response to the second electronic device. For another example, if the permission acquisition response indicates that the second electronic device is authorized, the server may add the account logged in by the second electronic device to the group corresponding to the home identifier, thereby establishing a sharing relationship between the second electronic device and the group corresponding to the home identifier, and completing the sharing of the group (home).

In this way, during the group sharing process, the user only needs to perform a simple touch operation to trigger the second electronic device to automatically join the family group managed by the first electronic device. The user operation is simple and the difficulty of user operation is effectively reduced.

Furthermore, the first electronic device and the second electronic device complete group sharing based on near field communication, thereby improving the real-time and interactivity of group sharing, thereby enhancing the user experience.

In some embodiments, after the group sharing is completed, the first electronic device and the second electronic device may also display corresponding sharing animations. The sharing animation display process and display effect can refer to the sharing animation display process and display effect of the first electronic device and the second electronic device in the process of home sharing, and the present application embodiment will not repeat them.

In some embodiments, the first electronic device may also be pre-set with permissions to allow home sharing, so that the server does not need to apply for authorization from the permission management device. In this way, the interaction process is further simplified and the efficiency of device permission sharing is improved.

Optionally, Figure 19 is a flow chart of another permission sharing method provided in an embodiment of the present application. As shown in Figure 19, the method includes the following steps.

S1901: The first electronic device displays a first sharing interface.

Optionally, the first electronic device is a user terminal or a central control device in a space.

Optionally, the first sharing interface includes a device management interface for managing at least one smart device, or a space management interface associated with the space where the first target smart device is located.

S1902: Detecting a user's operation on a first interface element in a first sharing interface.

Optionally, the first interface element includes a display element associated with the first target smart device. The first electronic device can share the first interface element with the second electronic device. For example, the first interface element is a card.

S1903: In response to approaching or touching the second electronic device, the first electronic device shares the control authority of the first target smart device corresponding to the first interface element with the second electronic device.

S1904. The second electronic device displays an animation effect.

Optionally, the first electronic device presents an animation on the first sharing interface, where the animation is used to prompt the user to Optionally, the motion effect includes a first interface element associated with the first target smart device moving out, or a display element associated with the user of the second electronic device moving in.

In this way, the first electronic device and the second electronic device complete the sharing of device control authority based on near field communication, thereby improving the real-time and interactivity of authority sharing, thereby enhancing the user experience.

Furthermore, during the device sharing process, the user only needs to perform a simple touch operation to trigger the first electronic device and the second electronic device to automatically complete the permission sharing, which is simple for the user to operate and effectively reduces the difficulty of user operation.

Optionally, other contents of step S1901 to step S1904 may refer to the relevant contents executed by the first electronic device or the second electronic device mentioned above, which will not be repeated here.

The above is a detailed description of the permission sharing method provided in the embodiment of the present application in combination with Figures 6 to 19. The following is a detailed description of the first electronic device provided in the embodiment of the present application in combination with Figure 20, and a detailed description of the second electronic device provided in the embodiment of the present application in combination with Figure 21.

In a possible design, FIG20 is a schematic diagram of the structure of the first electronic device provided in an embodiment of the present application. As shown in FIG20, the first electronic device 2000 may include: a transceiver unit 2001, a processing unit 2002, and a display unit 2003. The first electronic device 2000 may be used to implement the functions of the first electronic device involved in the above method embodiment.

Optionally, the transceiver unit 2001 is used to support the first electronic device 2000 to execute S1002, S1003, S1004, S1005, S1007 and S1008 in Figure 10; and/or, to support the first electronic device 2000 to execute S1302 in Figure 13; and/or, to support the first electronic device 2000 to execute S1702, S1703, S1704, S1705, S1707 and S1708 in Figure 17; and/or, to support the first electronic device 2000 to execute S1801, S1802 and S1803 in Figure 18; and/or, to support the first electronic device 2000 to execute S1903 in Figure 19.

Optionally, the processing unit 2002 is used to support the first electronic device 2000 to execute S1001 in Figure 10; and/or, to support the first electronic device 2000 to execute S1701 in Figure 17; and/or, to support the first electronic device 2000 to execute S1902 in Figure 19.

Optionally, the display unit 2003 is used to support the first electronic device 2000 to execute S1304 in Figure 13; and/or is used to support the first electronic device 2000 to execute S1901 in Figure 19.

Among them, the transceiver unit may include a receiving unit and a sending unit, and may be implemented by a transceiver or a transceiver-related circuit component, and may be a transceiver or a transceiver module. The operations and/or functions of each unit in the first electronic device 2000 are respectively to implement the corresponding processes of the authority sharing method described in the above method embodiment. All relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional unit, and for the sake of brevity, they will not be repeated here.

Optionally, the first electronic device 2000 shown in FIG20 may further include a storage unit (not shown in FIG20 ), in which a program or instruction is stored. When the transceiver unit 2001, the processing unit 2002, and the display unit 2003 execute the program or instruction, the first electronic device 2000 shown in FIG20 may execute the authority sharing method described in the above method embodiment.

The technical effects of the first electronic device 2000 shown in FIG. 20 may refer to the technical effects of the authority sharing method described in the above method embodiment, and will not be repeated here.

In addition to being in the form of the first electronic device 2000, the technical solution provided in the present application may also be a functional unit or chip in the first electronic device, or a device used in conjunction with the first electronic device.

In one possible design, FIG21 is a schematic diagram of the structure of a second electronic device provided in an embodiment of the present application. As shown in FIG21, the second electronic device 2100 may include: a transceiver unit 2101, a processing unit 2102, and a display unit 2103. The second electronic device 2100 may be used to implement the functions of the second electronic device involved in the above method embodiment.

Optionally, the transceiver unit 2101 is used to support the second electronic device 2100 to execute S1002, S1003, S1004, S1008 and S1009 in Figure 10; and/or, to support the second electronic device 2100 to execute S1301 in Figure 13; and/or, to support the second electronic device 2100 to execute S1702, S1703, S1704, S1708 and S1709 in Figure 17; and/or, to support the second electronic device 2100 to execute S1801, S1802, S1803 and S1804 in Figure 18; and/or, to support the second electronic device 2100 to execute S1903 in Figure 19.

Optionally, the processing unit 2102 is used to support the second electronic device 2100 to execute S1902 in Figure 19.

Optionally, the display unit 2103 is used to support the second electronic device 2100 to execute S1302 in Figure 13; and/or is used to support the second electronic device 2100 to execute S1904 in Figure 19.

The transceiver unit may include a receiving unit and a sending unit, and may be implemented by a transceiver or a transceiver-related circuit component, and may be a transceiver or a transceiver module. The operations and/or functions of each unit in the second electronic device 2100 are respectively to implement the above The corresponding process of the authority sharing method described in the method embodiment, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional unit, and will not be repeated here for the sake of brevity.

Optionally, the second electronic device 2100 shown in FIG21 may further include a storage unit (not shown in FIG21 ), in which a program or instruction is stored. When the transceiver unit 2101, the processing unit 2102, and the display unit 2103 execute the program or instruction, the second electronic device 2100 shown in FIG21 may execute the authority sharing method described in the above method embodiment.

The technical effects of the second electronic device 2100 shown in FIG. 21 may refer to the technical effects of the authority sharing method described in the above method embodiment, and will not be repeated here.

In addition to being in the form of the second electronic device 2100, the technical solution provided in the present application may also be a functional unit or chip in the second electronic device, or a device used in conjunction with the second electronic device.

An embodiment of the present application also provides a chip system, including: a processor, the processor is coupled to a memory, the memory is used to store programs or instructions, when the program or instructions are executed by the processor, the chip system implements the method in any of the above method embodiments.

Optionally, the processor in the chip system may be one or more. The processor may be implemented by hardware or by software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc. When implemented by software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.

Optionally, the memory in the chip system may also be one or more. The memory may be integrated with the processor or may be separately arranged with the processor, which is not limited in the embodiments of the present application. Exemplarily, the memory may be a non-transient processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip or may be arranged on different chips respectively. The embodiments of the present application do not specifically limit the type of memory and the arrangement of the memory and the processor.

Exemplarily, the chip system can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.

It should be understood that each step in the above method embodiment can be completed by an integrated logic circuit of hardware in a processor or by instructions in the form of software. The method steps disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware processor, or by a combination of hardware and software modules in a processor.

An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on a computer, the computer executes the above-mentioned related steps to implement the permission sharing method in the above-mentioned embodiment.

The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer is caused to execute the above-mentioned related steps to implement the permission sharing method in the above-mentioned embodiment.

In addition, an embodiment of the present application further provides a device. The device may be a component or a module, and the device may include one or more processors and a memory connected to each other. The memory is used to store a computer program. When the computer program is executed by one or more processors, the device executes the permission sharing method in the above-mentioned method embodiments.

Among them, the device, computer-readable storage medium, computer program product or chip provided in the embodiments of the present application are used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

The steps of the method or algorithm described in conjunction with the disclosed content of the embodiments of the present application can be implemented in hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory (RAM), flash memory, read only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, mobile hard disks, read-only compact disks (CD-ROMs) or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC) middle.

Through the description of the above implementation methods, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed; that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

In the several embodiments provided in the present application, it should be understood that the disclosed method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of modules or units, which can be electrical, mechanical or other forms.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

Computer-readable storage media include, but are not limited to, any of the following: USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks or optical disks, and other media that can store program codes.

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 (22)

A permission sharing method, characterized in that it is applied to a first electronic device, and the method includes: Display the first sharing interface; A user operation on a first interface element in the first sharing interface is detected, and in response to approaching or touching a second electronic device, the control authority of a first target smart device corresponding to the first interface element is shared with the second electronic device. The method according to claim 1, characterized in that the method further comprises: An animation is presented on the first sharing interface, where the animation is used to prompt the user to share the first target smart device corresponding to the first interface element to the second electronic device. The method according to claim 1 or 2, characterized in that, in response to approaching or touching the second electronic device, sharing the control authority of the first target smart device corresponding to the first interface element to the second electronic device comprises: During the process of displaying the first sharing interface, in response to approaching or touching the second electronic device, establishing a communication connection with the second electronic device; Obtaining, through the communication connection, a first account for logging into the second electronic device; According to the first account, the control authority of the first target smart device corresponding to the first interface element in the first sharing interface is shared to the second electronic device. The method according to claim 1 or 2, characterized in that, in response to approaching or touching the second electronic device, sharing the control authority of the first target smart device corresponding to the first interface element to the second electronic device comprises: During the process of displaying the first sharing interface, in response to approaching or touching the second electronic device, establishing a communication connection with the second electronic device; Through the communication connection, a second account logged in by the first electronic device is sent to the second electronic device, and the second account is used to share the control authority of the first target smart device corresponding to the first interface element in the first sharing interface with the second electronic device. The method according to any one of claims 1 to 4, wherein the first interface element comprises a display element associated with the first target smart device, and the method further comprises: The first interface element is shared to the second electronic device. The method according to claim 5 is characterized in that the first interface element is a card. The method according to any one of claims 1 to 6, characterized in that the first interface element includes a display element associated with an added user, and the added user is used to control the first target smart device; in response to approaching or touching the second electronic device, the method further includes: A second interface element is displayed, the second interface element comprising a display element associated with a user of the second electronic device. The method according to claim 2 is characterized in that the animation includes an animation of the first interface element associated with the first target smart device moving out, or an animation of the display element associated with the user of the second electronic device moving in. The method according to any one of claims 1 to 8, wherein in response to approaching or touching a second electronic device, sharing the control authority of a first target smart device corresponding to the first interface element with the second electronic device, further comprises: In response to approaching or touching the second electronic device, the control authority of the second target smart device corresponding to the first interface element is shared with the second electronic device, and the first target smart device and the second target smart device belong to the same space or the same scene. The method according to any one of claims 1 to 9 is characterized in that the approach or touch is based on one or more of the following technologies: NFC technology, BLE technology, and NAN technology. The method according to any one of claims 1-10 is characterized in that the control authority is a permission range specified by a user of the first electronic device. The method according to any one of claims 1-11 is characterized in that the first sharing interface includes a device management interface for managing at least one smart device, or a space management interface associated with the space where the first target smart device is located. The method according to any one of claims 1-12 is characterized in that the first electronic device is a user terminal or a central control device in a space. A permission sharing method, characterized in that it is applied to a second electronic device, and the method comprises: In response to approaching or touching a first electronic device, receiving control authority of a first target smart device shared by the first electronic device, wherein the first target smart device corresponds to a first interface element displayed by the first electronic device on a first sharing interface; Display an animation, where the animation is used to prompt the user that the second electronic device obtains control authority over the first target smart device. The method according to claim 14, characterized in that the animation includes an animation of the first interface element associated with the first target smart device moving in, and the first interface element moving out on the first sharing interface; Alternatively, a display element associated with the user of the first electronic device moves in. The method according to claim 14 or 15, characterized in that the method further comprises: Add the first interface element in the device management interface; or, The displayed first space management interface is switched to a second space management interface, the first space management interface corresponds to a user of the second electronic device, and the second space management interface corresponds to the user of the first electronic device. The method according to claim 16 is characterized in that the first interface element is a card. The method according to any one of claims 14 to 17, wherein the receiving, in response to approaching or touching the first electronic device, the control authority of the first target smart device shared by the first electronic device comprises: In response to approaching or bumping with a first electronic device, establishing a communication connection with the first electronic device; Through the communication connection, a first account logged in by the second electronic device is sent to the first electronic device, and the first account is used to share the control authority of the first target smart device with the second electronic device. The method according to any one of claims 14 to 17, wherein the step of receiving the control authority of the first target smart device shared by the first electronic device in response to approaching or touching the first electronic device comprises: In response to approaching or bumping with a first electronic device, establishing a communication connection with the first electronic device; Obtaining, through the communication connection, a second account for logging into the first electronic device; According to the second account, the control authority of the first target smart device is obtained. An electronic device, characterized in that it includes: a processor, a memory and a display screen, wherein the memory and the display screen are coupled to the processor, the memory is used to store computer program code, and the computer program code includes computer instructions. When the processor reads the computer instructions from the memory, the electronic device executes the method as described in any one of claims 1 to 13; or, the electronic device executes the method as described in any one of claims 14 to 19. A computer-readable storage medium, characterized in that the computer-readable storage medium includes a computer program, and when the computer program is run on an electronic device, the electronic device executes the method as described in any one of claims 1 to 13; or, the electronic device executes the method as described in any one of claims 14 to 19. A computer program product, characterized in that when the computer program product is run on a computer, the computer is caused to execute the method as described in any one of claims 1 to 13; or, the computer is caused to execute the method as described in any one of claims 14 to 19.