Permission sharing method and electronic equipment

Abstract

The invention provides a permission sharing method and electronic equipment, and relates to the technical field of terminals. Through the simple approaching or touch operation, the first electronic equipment can share the control authority of the intelligent equipment to the second electronic equipment, so that the authority sharing step is simplified, and the use difficulty of a user is reduced. The method comprises the steps that first electronic equipment displays a first sharing interface; and detecting an operation of a user on a first interface element in the first sharing interface, responding to approaching or collision with the second electronic equipment, and sharing the control authority of the first target intelligent equipment corresponding to the first interface element to the second electronic equipment by the first electronic equipment.

Description

Technical Field

[0001] This application relates to the technical field of terminals, and in particular, to a method for sharing permissions and an electronic device. Background Art

[0002] With the rapid development of the Internet of Things (IoT) technology, various IoT devices have emerged widely. For example, smart wearable devices, smart refrigerators, smart curtains, smart door locks, and smart air purifiers. After an electronic device (such as a mobile phone, a tablet, etc.) logs in to the account of a first application (such as a smart life application), and in response to a user operation, it binds to the IoT device and obtains the control permission of the IoT device. Subsequently, the user can control the IoT device bound to the first application account by logging in to the first application account, which brings great convenience to the user.

[0003] In some scenarios, through permission sharing, other first application accounts can also obtain the control permission of the IoT device, enabling other users to control the IoT device by logging in to other first application accounts. However, during the permission sharing process, users usually need to open the device QR code, record the first application account, and rely on other application programs to establish the sharing relationship between other first application accounts and the IoT device. The operation process is cumbersome and the user experience is poor. Summary of the Invention

[0004] To solve the above technical problems, this application provides a method for sharing permissions and an electronic device. The technical solution provided by this application enables a first electronic device to share the control permission of a smart device with a second electronic device through a simple operation of approaching or touching, thereby simplifying the permission sharing steps and reducing the user's difficulty of use.

[0005] To achieve the above technical objectives, this application provides the following technical solutions:

[0006] In a first aspect, a method for sharing permissions is provided, which is applied to a first electronic device. The method includes: displaying a first sharing interface. Detecting an operation of a user 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.

[0007] In this way, the first electronic device and the second electronic device complete the sharing of the control permission of the device based on near-field communication, improving the real-time performance and interactivity of permission sharing, and thus enhancing the user experience.

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

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

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

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

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

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

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

[0015] According to the first aspect, or any implementation manner of the above first aspect, 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: 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, sending the second account logged in by the first electronic device 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 to the second electronic device.

[0016] In some examples, if 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 devices in the home currently managed by the first electronic device. Optionally, the second account is a first application account or a device-level account.

[0017] In some examples, during the process that the second electronic device requests permission sharing from the server based on the second account of the first electronic device, the server can also request authorization from the permission management device corresponding to the second account to ensure the security of permission sharing.

[0018] According to the first aspect, or any implementation manner of the above first aspect, 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.

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

[0020] In this way, the second electronic device can not only obtain the permission of the smart device shared by the first electronic device, but also directly obtain the interface element shared by the first electronic device for controlling the smart device, so as to facilitate the user to determine the entry for controlling the smart device and simplify the user's operation.

[0021] According to the first aspect, or any implementation manner of the above first aspect, the first interface element includes a display element associated with adding a 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: displaying a second interface element, and the second interface element includes a display element associated with the user of the second electronic device.

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

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

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

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

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

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

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

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

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

[0031] According to the first aspect, or any implementation manner of the above first aspect, the control permission specifies the permission range for the user of the first electronic device.

[0032] In this way, the user can set the shareable permissions of the first target smart device according to requirements.

[0033] In some examples, the first electronic device sharing permissions with the second electronic device further includes sharing permissions for a scenario or space. In some examples, the user can also set the permission to allow editing of the scenario.

[0034] According to the first aspect, or any implementation manner of the above first aspect, 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.

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

[0036] In a second aspect, a permission sharing method is provided, which is applied to the second electronic device. The method includes: in response to approaching or touching the first electronic device, receiving the control permission of the first target smart device shared by the first electronic device, where the first target smart device corresponds to a dynamic effect of a first interface element displayed on the first sharing interface of the first electronic device, and the dynamic effect is used to prompt the user that the second electronic device obtains the control permission of the first target smart device.

[0037] According to the second aspect, the dynamic effect includes a dynamic effect of the first interface element associated with the first target smart device moving in, and the first interface element moves out on the first sharing interface. Or, a dynamic effect of a display element associated with the user of the first electronic device moving in.

[0038] According to the second aspect, or any implementation manner of the above second aspect, the method further includes: adding the first interface element in the device management interface. Or, switching the displayed first space management interface to a second space management interface, where 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.

[0039] In some examples, when the user performs home sharing, it is necessary to operate the devices in the home. Therefore, after the second electronic device obtains the control permission of the home shared by the first electronic device, it can switch to display the device management interface of the home, thereby facilitating the user to operate the devices.

[0040] According to the second aspect, or any implementation manner of the above second aspect, the first interface element is a card.

[0041] According to a second aspect, or any implementation of the above second aspect, in response to approaching or touching the first electronic device, receiving the control authority of the first target intelligent 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 to the second electronic device to the first electronic device, where the first account is used to share the control authority of the first target intelligent device to the second electronic device.

[0042] According to a second aspect, or any implementation of the above second aspect, in response to approaching or touching the first electronic device, receiving the control authority of the first target intelligent 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, obtaining the second account logged in to the first electronic device. According to the second account, obtaining the control authority of the first target intelligent device.

[0043] 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, and the computer program code includes computer instructions. When the processor reads the computer instructions from the memory, the first electronic device is caused to perform: displaying a first sharing interface. Detecting an operation by a user on a first interface element in the first sharing interface, and in response to approaching or touching the second electronic device, sharing the control authority of the first target intelligent device corresponding to the first interface element to the second electronic device.

[0044] According to the third aspect, when the processor reads the computer instructions from the memory, the first electronic device is further caused to perform: presenting an animation effect on the first sharing interface, where the animation effect is used to prompt the user to share the first target intelligent device corresponding to the first interface element to the second electronic device.

[0045] According to the third aspect, or any implementation of the above third aspect, in response to approaching or touching the second electronic device, sharing the control authority of the first target intelligent device corresponding to the first interface element to the second electronic device includes: 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, obtaining the first account logged in to the second electronic device. According to the first account, sharing the control authority of the first target intelligent device corresponding to the first interface element in the first sharing interface to the second electronic device.

[0046] According to a third aspect, or any implementation of the above third aspect, in response to the proximity or touch of 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: during the display of the first sharing interface, in response to the proximity or touch of the second electronic device, establishing a communication connection with the second electronic device. Through the communication connection, sending the second account logged in on the first electronic device 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 to the second electronic device.

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

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

[0049] According to a third aspect, or any implementation of the above third aspect, the first interface element includes a display element associated with adding a user, and the added user is used to control the first target smart device; in response to the proximity or touch of the second electronic device, when the processor reads computer instructions from the memory, it also causes the first electronic device to execute: displaying a second interface element, and the second interface element includes a display element associated with the user of the second electronic device.

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

[0051] According to a third aspect, or any implementation of the above third aspect, in response to the proximity or touch of 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 further includes: in response to the proximity or touch of the second electronic device, sharing the control authority of the second target smart device corresponding to the first interface element to the second electronic device, and the first target smart device and the second target smart device belong to the same space or the same scenario.

[0052] According to a third aspect, or any implementation of the above third aspect, the proximity or touch is based on one or more of near field communication (NFC) technology, low power Bluetooth (BLE) technology, and near area network (NAN) communication technology.

[0053] According to a third aspect, or any implementation manner of the above third aspect, the control permission is the permission range specified for the user of the first electronic device.

[0054] According to a third aspect, or any implementation manner of the above third aspect, 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.

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

[0056] 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, and the computer program code includes computer instructions. When the processor reads the computer instructions from the memory, the second electronic device is caused to perform: in response to approaching or touching the first electronic device, receiving the control permission of the first target smart device shared by the first electronic device, where the first target smart device corresponds to a dynamic effect displayed by a first interface element on the first sharing interface of the first electronic device, and the dynamic effect is used to prompt the user that the second electronic device obtains the control permission of the first target smart device.

[0057] According to the fourth aspect, the dynamic effect includes a dynamic effect of the first interface element associated with the first target smart device moving in, and the first interface element moves out on the first sharing interface. Or, a dynamic effect of a display element associated with the user of the first electronic device moving in.

[0058] According to the fourth aspect, or any implementation manner of the above fourth aspect, when the processor reads the computer instructions from the memory, the second electronic device is further caused to perform: adding the first interface element in the device management interface. Or, switching the displayed first space management interface to a second space management interface, where 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.

[0059] According to the fourth aspect, or any implementation manner of the above fourth aspect, the first interface element is a card.

[0060] According to the fourth aspect, or any implementation manner of the above fourth aspect, in response to approaching or touching the first electronic device, receiving the control permission 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 a first account logged in by the second electronic device to the first electronic device, and the first account is used to share the control permission of the first target smart device to the second electronic device.

[0061] According to a fourth aspect, or any implementation manner of the above fourth aspect, in response to approaching or touching the first electronic device, receiving the control authority of the first target intelligent device shared by the first electronic device, including: in response to approaching or touching the first electronic device, establishing a communication connection with the first electronic device. Through the communication connection, obtaining the second account logged in by the first electronic device. According to the second account, obtaining the control authority of the first target intelligent device.

[0062] A fifth aspect provides an electronic device, which has the function of implementing the permission sharing method described in the first aspect and any possible implementation manner thereof above; or, the electronic device has the function of implementing the permission sharing method described in the second aspect and any possible implementation manner thereof above. This 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.

[0063] A sixth aspect provides a computer-readable storage medium. The computer-readable storage medium stores a computer program (which can also be referred to as an instruction or code). When the computer program is executed by an electronic device, the electronic device is caused to execute the method of the first aspect or any implementation manner of the first aspect; or, the electronic device is caused to execute the method of the second aspect or any implementation manner of the second aspect.

[0064] A seventh aspect provides a computer program product. When the computer program product runs on an electronic device, the electronic device is caused to execute the method of the first aspect or any implementation manner of the first aspect; or, the electronic device is caused to execute the method of the second aspect or any implementation manner of the second aspect.

[0065] An eighth aspect provides a circuit system. The circuit system includes a processing circuit, and the processing circuit is configured to execute the method of the first aspect or any implementation manner of the first aspect; or, the processing circuit is configured to execute the method of the second aspect or any implementation manner of the second aspect.

[0066] A ninth aspect provides a chip system, including at least one processor and at least one interface circuit. The at least one interface circuit is used to perform transceiver functions and send instructions to the at least one processor. When the at least one processor executes the instructions, the at least one processor executes the method of the first aspect or any implementation manner of the first aspect; or, the at least one processor executes the method of the second aspect or any implementation manner of the second aspect.

[0067] The technical effects of the foregoing aspects can be referred to each other, and will not be elaborated here. Description of the Drawings

[0068] Figure 1 Schematic diagram of the device permission sharing interface provided by the embodiment of the present application Figure 1 ;

[0069] Figure 2 Schematic diagram of the device permission sharing interface provided by the embodiment of the present application Figure 2 ;

[0070] Figure 3 Schematic diagram of the communication system to which the permission sharing method provided by the embodiment of the present application is applied;

[0071] Figure 4 Schematic diagram of the hardware structure of the first electronic device provided by the embodiment of the present application;

[0072] Figure 5 Schematic diagram of the hardware structure of the server provided by the embodiment of the present application;

[0073] Figure 6 Schematic diagram of the device permission sharing interface provided by the embodiment of the present application Figure 3 ;

[0074] Figure 7 Schematic diagram of the device permission sharing interface provided by the embodiment of the present application Figure 4 ;

[0075] Figure 8 Schematic diagram of the device permission sharing interface provided by the embodiment of the present application Figure 5 ;

[0076] Figure 9 Schematic diagram of the device permission sharing interface provided by the embodiment of the present application Figure 6 ;

[0077] Figure 10 Schematic diagram of the permission sharing method flow provided by the embodiment of the present application Figure 1 ;

[0078] Figure 11 Schematic diagram of the device permission sharing interface provided by the embodiment of the present application Figure 7 ;

[0079] Figure 12 Schematic diagram of the device permission sharing interface provided by the embodiment of the present application Figure 8 ;

[0080] Figure 13 Schematic diagram of the permission sharing method flow provided by the embodiment of the present application Figure 2 ;

[0081] Figure 14 Schematic diagram of the device permission sharing interface provided by the embodiment of the present application Figure 9 ;

[0082] Figure 15 Schematic diagram of the device permission sharing interface provided by the embodiment of the present application Figure 10 ;

[0083] Figure 16 Schematic diagram of the device permission sharing interface provided by the embodiment of the present application Figure 10 One;

[0084] Figure 17 Schematic diagram of the process of the permission sharing method provided by the embodiment of the present application Figure 3 ;

[0085] Figure 18 Schematic diagram of the process of the permission sharing method provided by the embodiment of the present application Figure 4 ;

[0086] Figure 19 Schematic diagram of the process of the permission sharing method provided by the embodiment of the present application Figure 5 ;

[0087] Figure 20 Schematic diagram of the structure of the first electronic device provided by the embodiment of the present application;

[0088] Figure 21 Schematic diagram of the structure of the second electronic device provided by the embodiment of the present application. Detailed implementation manners

[0089] Next, in combination with the accompanying drawings in the embodiments of the present application, the technical solutions in the embodiments of the present application will be described. Among them, 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 limit the present application. As used in the specification and appended claims of the present application, the singular forms "a", "an", "the", "above", "said", "this" are intended to include, for example, the expression "one or more", unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" means one or more than two (including two).

[0090] References to "one embodiment" or "some embodiments" etc. described in this specification mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, statements such as "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments" etc. that appear in different places in this specification do not necessarily all refer to the same embodiment, but rather mean "one or more but not all embodiments", unless otherwise specifically emphasized. The terms "comprise", "include", "have" and their variants all mean "including but not limited to", unless otherwise specifically emphasized. The term "connect" includes direct connection and indirect connection, unless otherwise stated. "First", "second" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features.

[0091] In the embodiments of the present application, words such as "exemplarily" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplarily" or "for example" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0092] In some embodiments, the smart home system uses a residence as a platform and utilizes technologies such as the Internet of Things and automatic control to achieve the organic combination of various electronic devices and application subsystems related to home life. Among them, the user can manage the devices in the smart home system by logging in to the smart life application account. For example, smart wearable devices, smart refrigerators, smart curtains, smart door locks, and smart air purifiers, etc.

[0093] In some examples, after an electronic device (such as a mobile phone, a tablet, etc.) logs in to the smart life application account and is bound to an IoT device in response to a user operation, it obtains the control authority of the IoT device. In some examples, after the IoT device is first bound to the smart life application account, the smart life application account is the main account for managing the IoT device. After the electronic device logs in to the main account, it can share the authority to control the IoT device with other electronic devices, and the smart life application accounts logged in by other electronic devices are sub-accounts. That is, the sub-account can obtain the authority to control some or all of the IoT devices under the main account, and the control authority obtained by the sub-account can be less than or equal to the control authority of the main account over the IoT device. Generally, for an IoT device, the electronic device logging in to the main account is the main device, and the electronic device logging in to the sub-account is the sub-device.

[0094] Exemplarily, such as Figure 1As shown in (a), the mobile phone displays the smart life application interface 101, which is used to display the cards of multiple IoT devices managed under the current smart life application account. When the mobile phone detects that the user clicks on the ceiling light card 11, it can display a menu bar window 12 including the operation content that can be performed on the ceiling light card 11. When the mobile phone detects the operation of the user on the shared device control 13 displayed in the menu bar window 12, it is determined 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 the interface 102 as shown in Figure 1 Figure (b), and display the sharing methods of the sharing permission on the interface, such as sharing by scanning the code, sharing through the Huawei account, and sharing with contacts in the address book.

[0095] For example, when the mobile phone detects the operation of the user on the scan code sharing control 14, it is determined that the user instructs to share the permission to control the ceiling light to the peer device by scanning the QR code of the peer device. Then, as shown in Figure 2 Figure, the mobile phone (i.e., device 1) displays the scan code interface. And the user also needs to open the QR code display interface of the peer device (i.e., device 2). After that, the user can scan the QR code displayed by device 2 through device 1 to realize that device 1 shares the permission to control the ceiling light to device 2.

[0096] It can be seen that in the above permission sharing process, the user needs to perform corresponding operations on both ends of the device, the sharing path is relatively long, the operation is cumbersome, and it affects the user experience.

[0097] Another example is that in the process of sharing device permissions through the Huawei account sharing method, the user needs to enter the Huawei account of the peer device (such as the same as the smart life account of the peer device), and then the electronic device can share the control permission of the device selected by the user to the device logged in to this Huawei account. It can be seen that in this process, it increases the difficulty for the user to remember the Huawei account.

[0098] For another example, in the process of sharing device permissions through the contacts in the address book method, the electronic device needs to respond to the user's operation, launch other applications, and display the contacts in the address book information for the user to select. The user needs to browse and select the friend account to be shared. Then, the electronic device shares the control permission 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 launched, and the user operation is cumbersome.

[0099] In addition, after the device permission sharing is completed in various ways as described above, it is difficult for the user to find the device with the shared control permission under the smart life application account that has obtained the control device permission. Then, the user may think that the control permission sharing fails, which affects the user experience. For example, if there are already many IoT devices under the smart life application account that has obtained the control device permission, it is difficult for the user to find the required IoT device among the display information of multiple IoT devices.

[0100] In response to this, the embodiment of the present application provides a permission sharing method. Through a simple operation of approaching or touching, the first electronic device can share the control permission of the smart device with the second electronic device, thereby simplifying the permission sharing steps and reducing the user's usage difficulty.

[0101] Figure 3 FIG. is a schematic diagram of a communication system to which the permission sharing method provided by the embodiment of the present application is applied. As Figure 2 shown, the communication system includes a first electronic device 100, a second electronic device 200, a third electronic device 300, and a server 400.

[0102] 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 the 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 special restrictions on the specific form of the first electronic device 100.

[0103] Optionally, as Figure 3 shown, the first electronic device 100 can be connected to one or more third electronic devices 300 for managing and controlling the third electronic devices 300.

[0104] Optionally, the third electronic device 300 may be, for example, a terminal device such as a speaker, a smart screen, a table lamp, an electric lamp, 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 (AI) terminal, etc. The present application does not impose special restrictions on the specific form of the third electronic device 300. The operating system installed on the third electronic device 300 includes but is not limited to Or other operating systems. The third electronic device 300 may also 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 it has an operating system installed, or the operating system installed when it has an operating system installed.

[0105] In some embodiments, the third electronic device 300 is an IoT device. A first application is installed in the first electronic device 100. Among them, the first application is capable of connecting to the IoT device, editing and controlling the IoT device. As Figure 3 shown, the first electronic device 100 connects to one or more third electronic devices 300 through the first application. Optionally, the first application is a smart life application.

[0106] In some examples, after the first electronic device 100 logs in to the first account of the first application, the registration of the third electronic device 300 is completed. 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 in units of home. 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.

[0107] Optionally, the server 400 may be a cloud server or a network server and other computing devices or network devices with computing functions. The server 400 may be a single server, or a server cluster composed of multiple servers, or a cloud computing service center. The server 400 may also be described as a smart home cloud platform for managing smart home devices, corresponding scenarios of smart home devices, etc. included in the smart home system.

[0108] In some embodiments, a wireless communication connection is established between the first electronic device 100 and the second electronic device 200. Among them, the wireless communication technologies for establishing the wireless communication connection include, but are not limited to, at least one of the following: Bluetooth (BT) (for example, traditional Bluetooth or Bluetooth Low Energy (BLE)), Wireless Local Area Networks (WLAN) (such as Wireless Fidelity (Wi-Fi) network), Near Field Communication (NFC), Zigbee, Frequency Modulation (FM), Infrared (IR), etc.

[0109] Optionally, the first electronic device 100 and the second electronic device 200 can also establish a communication connection through a third-party device in the local area network. The third-party device is, for example, a router, a gateway, a smart device controller, a server, etc.

[0110] In some embodiments, a first application is installed in the second electronic device and a second account of the first application is logged in. In some examples, when the second electronic device needs to obtain the permission to control the third electronic device 300, the user can operate the first electronic device 100 that has the permission to control the third electronic device 300 to share the permission to control the third electronic device 300 with the second electronic device 200.

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

[0112] In some embodiments, the above-mentioned operating system is, for example, a smart home system, and the third electronic device 300 is a smart home device. Alternatively, the above-mentioned operating system is a smart office system, and the third electronic device 300 is a smart office device. Alternatively, the above-mentioned communication system can also be other communication systems such as a smart campus communication system, and the embodiments of the present application do not limit this. In the following, taking the above-mentioned communication system as a smart home system and the third electronic device 300 as a smart home device as an example, the permission sharing method provided by the embodiments of the present application will be introduced in detail.

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

[0114] For example, taking the first electronic device 100 having the hardware structure as Figure 4 shown as an example, the hardware structure as Figure 4 shown will be described.

[0115] Exemplarily, Figure 4 shows a schematic structural diagram of the first electronic device 100.

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

[0117] It can be understood that the structure schematically shown in the embodiments 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, or combine certain components, or split certain components, or have different component arrangements. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

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

[0119] The controller may generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.

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

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

[0122] The I2C interface is a two-way 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 can be respectively coupled to a touch sensor, a charger, a flash, a camera 193, etc. through different I2C bus interfaces. For example, the processor 110 can be coupled to the touch sensor through the I2C interface, enabling the processor 110 and the touch sensor to communicate through the I2C bus interface to implement the touch function of the first electronic device 100.

[0123] The MIPI interface can be used to connect the processor 110 to 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 through the CSI interface to implement the shooting function of the first electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the first electronic device 100.

[0124] The USB interface 130 is an interface that conforms to the USB standard specification, and can specifically 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 transfer data between the first electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as AR devices, etc.

[0125] It can be understood that the interface connection relationships between the modules illustrated in the embodiments of the present application are only illustrative and do not constitute a structural limitation on the first electronic device 100. In other embodiments of the present application, the first electronic device 100 can also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0126] The charging management module 140 is used to receive a charging input from a charger. Among them, the charger can be a wireless charger or a wired charger. In some embodiments of wired charging, the charging management module 140 can receive the charging input from the wired charger through the USB interface 130. In some embodiments of wireless charging, the charging management module 140 can receive the wireless charging input through the wireless charging coil of the first electronic device 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device through the power management module 141.

[0127] 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 inputs 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, the wireless communication module 160, etc. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be disposed in the processor 110. In some other embodiments, the power management module 141 and the charging management module 140 can also be disposed in the same device.

[0128] The wireless communication function of the first electronic device 100 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, and the baseband processor, etc.

[0129] The antenna 1 and the 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 multiplexed to improve the utilization rate of the antennas. For example, the antenna 1 can be multiplexed as the diversity antenna of the wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0130] The mobile communication module 150 can provide solutions for wireless communications such as 2G / 3G / 4G / 5G applied to the first electronic device 100. The mobile communication module 150 can include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves by the antenna 1, filter, amplify, etc. 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 through the antenna 1 and radiate it out. In some embodiments, at least some functional modules of the mobile communication module 150 can be disposed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 can be disposed in the same device.

[0131] The modulation and demodulation processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. Subsequently, the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs a sound signal through the audio device, or displays an image or video through the display screen 194. In some embodiments, the modulation and demodulation processor may be an independent device. In other embodiments, the modulation and demodulation processor may be independent of the processor 110 and be disposed in the same device as the mobile communication module 150 or other functional modules.

[0132] The wireless communication module 160 may provide solutions for wireless communications applied to the first electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite systems (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive the signal to be transmitted from the processor 110, perform frequency modulation on it, amplify it, and convert it into electromagnetic waves through the antenna 2 and radiate it out.

[0133] In some embodiments, antenna 1 of the first electronic device 100 is coupled to the mobile communication module 150, and antenna 2 is coupled to the wireless communication module 160, enabling the first electronic device 100 to communicate with the network and other devices through wireless communication technologies. The wireless communication technologies may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), Beidou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

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

[0135] The first electronic device 100 implements the display function through the GPU, the display screen 194, and the application processor, etc. The GPU is a microprocessor for image processing, connected to 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, which execute program instructions to generate or change the display information.

[0136] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), for example, an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Mini-led, a Micro-led, a Micro-oled, a quantum dot light-emitting diode (QLED), etc. are used for production and manufacturing. 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.

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

[0138] The camera 193 is used to capture static images or videos. An object generates an optical image through a lens and projects it onto a 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 transmits 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 format such as RGB, YUV, etc. In some embodiments, the first electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

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

[0140] The internal memory 121 can be used to store computer-executable program codes, and the executable program codes include instructions. The internal memory 121 can include a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function (such as a sound playback function, an image playback function, etc.). The data storage area can store data created during the use of the first electronic device 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 can include a high-speed random access memory, and can 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 the instructions stored in the internal memory 121, and / or the instructions stored in the memory provided in the processor.

[0141] The audio module 170 is used to convert digital audio information into an analog audio signal for output, and is also used to convert an analog audio input into a 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 disposed in the processor 110, or some functional modules of the audio module 170 can be disposed in the processor 110. The first electronic device 100 can perform functions such as music playback and recording through the audio module 170. The audio module 170 can include a speaker, a receiver, a microphone, a headphone jack, and an application processor, etc. to implement audio functions.

[0142] The sensor module 180 can include a pressure sensor, a gyroscope sensor, a barometric 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, etc.

[0143] A touch sensor, also known as a "touch control device". The touch sensor can be disposed on the display screen 194. The touch sensor and the display screen 194 form a touch screen, also known as a "touch control screen". The touch sensor is used to detect touch operations acting thereon or in its vicinity. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual outputs related to the touch operations can be provided through the display screen 194. In some other embodiments, the touch sensor can also be disposed on the surface of the first electronic device 100, at a different position from where the display screen 194 is located.

[0144] The button 190 includes a power-on button, volume buttons, etc. The button 190 can be a mechanical button or a touch button. The first electronic device 100 can receive button inputs and generate key signal inputs related to the user settings and function controls of the first electronic device 100.

[0145] The motor 191 can generate vibration prompts. The motor 191 can be used for incoming call vibration prompts and also for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playing, etc.) can correspond to different vibration feedback effects. For touch operations acting on different regions of the display screen 194, the motor 191 can also correspond to different vibration feedback effects. Different application scenarios (such as time reminders, receiving messages, alarms, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effects can also support customization.

[0146] The indicator 192 can be an indicator light and can be used to indicate the charging state, power change, and can also be used to indicate messages, missed calls, notifications, etc.

[0147] The SIM card interface 195 is used to connect to the SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation with the first electronic device 100. The first electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1.

[0148] For example, taking the server 400 having the Figure 5 hardware structure shown as an example, the Figure 5 hardware structure shown will be described.

[0149] Figure 5 The following is a schematic diagram of the hardware structure of the server 400 provided by 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. Among them, the memory 403 can also be included in the processor 401.

[0150] It can be understood that the structure illustrated in the embodiments 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 those illustrated, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0151] The processor 401 may 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 solution of the present application.

[0152] The communication line 402 may include a path for transmitting information between the above components.

[0153] The communication interface 404 is used for communicating with other devices. In the embodiments of the present application, the communication interface may be a module, a circuit, a bus, an interface, a transceiver, or other devices capable of implementing communication functions, for communicating with other devices. Optionally, when the communication interface is a transceiver, the transceiver may be an independently provided transmitter, which can be used to send information to other devices, or the transceiver may be an independently provided receiver, for receiving information from other devices. The transceiver may also be a component integrating the functions of sending and receiving information. The specific implementation of the transceiver in the embodiments of the present application is not limited.

[0154] 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 may also be 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 compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory may exist independently and be connected to the processor through the communication line 402. The memory may also be integrated with the processor.

[0155] Among them, the memory 403 is used to store computer-executable instructions for implementing the solution of this application, and is controlled and executed by the processor 401. The processor 401 is used to execute the computer-executable instructions stored in the memory 403, so as to implement the permission sharing method provided in the following embodiments of this application.

[0156] Optionally, the computer-executable instructions in the embodiments of this application may also be referred to as application code, instructions, computer programs, or other names, and the embodiments of this application do not make specific limitations thereto.

[0157] In a specific implementation, as an embodiment, the processor 401 may include one or more CPUs, such as Figure 5 CPU0 and CPU1 in

[0158] In a specific implementation, as an embodiment, the server 400 may include multiple processors, such as Figure 5 processor 401 and processor 405 in

[0159] The above Figure 4 and Figure 5 described device structures are also applicable to devices such as the second electronic device or other two-party devices for permission sharing.

[0160] In the following, taking the first electronic device 100 as the device with the control permission of the third electronic device 300, the second electronic device 200 as the device that needs to obtain the control permission of the third electronic device 300, the third electronic device 300 as an IoT device (such as a smart home device and other smart devices), and the server 400 as a smart home cloud server as an example, the permission sharing method provided in the embodiments of this application will be introduced in detail.

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

[0162] In some examples, during the process of the first electronic device running the first application, the first electronic device responds to a user operation and can share the control permission of at least one smart device in the home with the second electronic device. Optionally, the control permission is the permission range specified by the user of the first electronic device. For example, the first electronic device responds to a user's setting operation and determines that the shared control permission includes the permission to control the start or stop of the smart device, but does not include the permission to adjust parameters, etc.

[0163] In some examples, during the process of the first electronic device displaying the first sharing interface, if an operation on the first interface element in the first sharing interface is detected, it can be determined that the user instructs to share the control permission 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 permission of the first target smart device corresponding to the first interface element to the second electronic device.

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

[0165] Optionally, approaching or touching is based on one or more of NFC technology, BLE Bluetooth technology, and neighbor awareness networking (NAN) communication technology. Optionally, the communication technology based on NAN is, for example, Wi-Fi aware communication technology. Optionally, in some sharing scenarios supported by possible short-range communication technologies, there may be no need for a clear approaching or touching action 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 performed between them.

[0166] Exemplarily, as Figure 6 shown in (a) below, the first electronic device displays the first sharing interface 601. This sharing interface 601 is a device management interface, including cards corresponding to multiple smart devices included in the home (such as A's home). The cards display some information and control buttons of the smart device. The user can select the device to be shared according to their own needs. For example, the first electronic device detects the user's operation on the card 61 (i.e., the first interface element) and displays the menu bar window 62. Then, 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 lamp in the living room corresponding to the 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. Then, as Figure 6 shown in the interface 602 in (b) below, the first electronic device can display the window 64. In the window 64, a card 65 corresponding to the first target smart device selected by the user for sharing is displayed. It should be understood that the number of devices selected by the user for sharing is one or more. And in the window 64, the way of device sharing is also displayed. As shown by the reference numeral 66, the first electronic device can display a prompt message to prompt the user that the device can be shared by touching.

[0167] In this way, through short-range communication methods such as getting close to or touching, the user can share the control authority of the intelligent device managed by the first electronic device with the second electronic device. Compared with other device sharing methods, the user no longer needs to input the Huawei account through the first electronic device, launch other applications, etc., effectively simplifying the user operation.

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

[0169] 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 intelligent device through the card.

[0170] Exemplarily, as Figure 7 shown in (a) of, the device management interface 701, as shown by the reference numeral 71, the home managed by the second electronic device (such as B's home) includes 11 intelligent devices, and the device management interface 701 displays the cards corresponding to these 11 intelligent devices respectively. Subsequently, the second electronic device obtains the control authority of the first target intelligent device (such as the living room light) in response to getting close to or touching the first electronic device, and obtains the first interface element (such as the card corresponding to the living room light) corresponding to the first target intelligent device. Then, as Figure 7 shown in the interface 702 in (b) of, as shown by the reference numeral 72, the number of intelligent 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).

[0171] In this way, the second electronic device can not only obtain the authority of the intelligent device shared by the first electronic device, but also directly obtain the interface element shared by the first electronic device for controlling the intelligent device, so as to facilitate the user to determine the entry for controlling the intelligent device and simplify the user operation.

[0172] In some embodiments, the user can select one or more intelligent 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 according to the user operation. 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 authority of multiple intelligent devices in the scene or space selected by the user with the second electronic device according to the user operation. That is, the first sharing interface includes a device management interface for managing at least one intelligent device, or a space management interface associated with the space where the first target intelligent device is located.

[0173] Optionally, the above-mentioned space is, for example, the entire home, or a room in the home, or an office, a meeting room, etc. in an office scenario.

[0174] Optionally, the sharing of the control authority of the intelligent devices in the scenario not only includes the control authority of the intelligent devices in the scenario shared with the second electronic device, but may also include the editing authority of the scenario. Optionally, the user can select the scope of the control authority to be shared.

[0175] Exemplarily, as Figure 8 shown, the first interface elements displayed by the first electronic device on the intelligent life application interface 801 not only include the cards 81 corresponding to the intelligent devices, but also include the cards 82 corresponding to the scenarios and the cards 83 corresponding to the spaces. Then, in response to the user's operation on the card 82 (or card 83), the first electronic device can determine that the user instructs to share the control authority of multiple intelligent devices in the scenario (or space) corresponding to the card 82 (or card 83) to the second electronic device. For example, the multiple intelligent devices include a first target intelligent device and a second target intelligent device. The first target intelligent device and the second target intelligent device belong to the same space or the same scenario. In response to approaching or touching the second electronic device, the first electronic device shares the control authority of the first target intelligent device and the second target intelligent device corresponding to the first interface element to the second electronic device.

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

[0177] In this way, in a more abundant intelligent device management scenario, the user can, through simple operations, share the control authority of multiple intelligent devices in the scenario or space to the second electronic device, improving the user experience.

[0178] In some scenarios, the first electronic device, in response to approaching or touching the second electronic device, establishes a short-range communication connection, and thus, based on this short-range communication connection, realizes sharing the control authority of the first target intelligent device to the second electronic device. The following introduces in detail the method for establishing this short-range communication connection and sharing the control authority based on this short-range communication connection through the Figure 10 shown method.

[0179] Figure 10 is a schematic flowchart of a permission sharing method provided by an embodiment of the present application. It should be noted that this method is not based on Figure 10And limited by the specific order described below, it should be understood that in other embodiments, the order of some steps of the method can be mutually exchanged according to actual needs, or some of the steps can also be omitted or deleted. The method includes the following steps:

[0180] S1001. The first electronic device detects that the user indicates an operation of sharing a device in the first application.

[0181] Among them, the first application is, for example, a smart life application for managing and controlling a third electronic device. The operation of indicating sharing a device is, for example, an operation in which the user selects a third electronic device to be shared.

[0182] Exemplarily, as shown in (a) of Figure 6 During the process that 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. Then, the first electronic device detects the operation that the user clicks the shared device control 63 displayed in the menu bar window 62, and determines that it detects the operation that the user indicates sharing a device.

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

[0184] In some examples, the preset operation is, for example, an operation such as a tap to pull up a near-field communication connection (such as an NFC connection). It should be understood that the preset operation can also be other operations convenient for the user to implement, such as a shake operation.

[0185] In some embodiments, after the second electronic device responds to the user operation and starts the first application, it generates an identification code and writes the identification code into the NFC tag. Optionally, after the second electronic device writes the identification code into the NFC tag, it can mark the NFC mode as the tag mode. Subsequently, after the first electronic device and the second electronic device detect the user's tap 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 the reader mode.

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

[0187] In some examples, the second electronic device may not pre-set an identification code, but instead generate an identification code in accordance with a preset period in response to the touch-and-touch operation of the first electronic device. 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 the touch-and-touch operation of the first electronic device. Optionally, the second electronic device generates an identification code in response to the touch-and-touch operation and starts the first application.

[0188] For example, the first electronic device determines the second electronic device located nearby by means such as Bluetooth ranging. And, a vibration sensor is pre-set in the second electronic device. In response to a preset operation of the user, after the second electronic device detects the touch-and-touch operation through the vibration sensor, it generates an identification code.

[0189] 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 the tag mode. Subsequently, if the second electronic device detects an operation indicating sharing the device in the first application, it can mark the NFC mode as the reader mode again. Optionally, when the NFC mode of the second electronic device is the reader mode, it can delete the identification code in the NFC tag. Subsequently, after the second electronic device exits the device sharing interface, it can trigger the generation of an identification code again. Or, the second electronic device does not delete the identification code in the NFC tag.

[0190] In this way, compared with other sharing methods, the user does not have to input the Huawei account through the first electronic device, pull up other applications, etc., effectively simplifying the user operation.

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

[0192] In some embodiments, after the first electronic device obtains the identification code of the second electronic device, it can send a Bluetooth connection request to the second electronic device. Optionally, the first electronic device sends a Bluetooth connection request to the second electronic device by means of Bluetooth broadcasting. Correspondingly, after the touch-and-touch operation, the second electronic device can turn on Bluetooth broadcasting to receive the Bluetooth connection request broadcast by the first electronic device.

[0193] In some embodiments, in response to the Bluetooth connection request, the first electronic device and the second electronic device can establish a Bluetooth connection. In some examples, to ensure the security of Bluetooth communication, the first electronic device and the second electronic device can perform key negotiation 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 with this communication key, thereby ensuring the security of the communication data transmission, that is, realizing the establishment of a secure communication connection.

[0194] 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. After that, the first electronic device and the second electronic device can 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 pre-set in the first electronic device, or a sin code generated by the first electronic device through a preset algorithm. Sin2 is, for example, a sin code pre-set in the second electronic device, or a sin code generated by the second electronic device through a preset algorithm.

[0195] In other examples, the first electronic device and the second electronic device pre-store the same number (such as 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 this number and the identification code of the second electronic device.

[0196] It should be understood that in addition to the two communication key negotiation methods in the above examples, the first electronic device and the second electronic device can also negotiate communication keys through other methods, and the embodiments of the present application will not list them one by one.

[0197] S1004. The first electronic device obtains the account logged in by the second electronic device through a secure communication connection.

[0198] In some examples, the account logged in by the second electronic device is, for example, a smart life application account that currently manages the first target intelligent device. Or, this account can also be a device-level account, such as a Huawei account.

[0199] 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 the ownerId. The second electronic device is described as the member device, and the account logged in by the second electronic device is the UserId.

[0200] In some embodiments, after the second electronic device establishes a secure communication connection with the first electronic device, it can send the UserId encrypted with the communication key to the first electronic device. In some examples, the second electronic device can also respond to the account acquisition request sent by the first electronic device and send the UserId to the first electronic device.

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

[0202] S1005. The first electronic device sends the device identifier of the device to be shared and the account logged in by the second electronic device to the server.

[0203] In some embodiments, in response to a user's operation indicating sharing of a device, the first electronic device can determine the device to be shared and the device identifier of the device to be shared. 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 obtaining a sharing code for sharing the device corresponding to the device identifier with the account.

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

[0205] S1006. The server generates a sharing code based on the device identifier and the account logged in by the second electronic device.

[0206] In some embodiments, after receiving the deviceId and memberUserId sent by the first electronic device, the server determines that the third electronic device corresponding to the deviceId is a device controlled under the account logged in by the first electronic device. Then, the server can generate a corresponding sharing code (shareCode).

[0207] In some examples, the sharing code generated by the server is configured with expiration conditions, and the expiration conditions include, for example, usage times requirements, usage time requirements, etc. For example, to ensure the security of device permission sharing, the usage times of the sharing code are at most once. Optionally, the server can also set an effective usage period for the sharing code, such as being valid within 5 minutes, etc.

[0208] S1007. The server sends the sharing code to the first electronic device.

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

[0210] S1008. The first electronic device sends the sharing code to the second electronic device.

[0211] In some embodiments, after receiving the sharing code, the first electronic device encrypts the sharing code using a 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.

[0212] S1009. The second electronic device sends a device sharing request to the server, and the sharing code is carried in the device sharing request.

[0213] In some embodiments, after obtaining the sharing code, the second electronic device may send a device sharing request to the server to request the control permission 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.

[0214] In some examples, when the first application on the second electronic device is logged in to its own first application account, the second electronic device sends a device sharing request to the server so that its first application account can obtain the control permission of the device to be shared.

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

[0216] 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 to determine whether the sharing code is correct. If the sharing code is correct, the server further parses and authenticates the sharing code. If the sharing code is incorrect, the server sends a device sharing failure response to the second electronic device.

[0217] After that, when the sharing code is correct, the server obtains the device identifier and the first application account indicated by the sharing code. Then, 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 condition and can share the device to be shared corresponding to the device identifier to the second electronic device. If not, the server can determine that the second electronic device does not meet the sharing condition and can send a device sharing failure response to the second electronic device.

[0218] In some embodiments, the server manages one or more third electronic devices under the account through 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 identifier of the device to be shared to the account logged in by the second electronic device.

[0219] In some embodiments, after the server establishes a sharing relationship between the second electronic device and the device to be shared, it can 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.

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

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

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

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

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

[0225] For example, Figure 6 In the interface 602 shown in (b), in response to the user's tap operation, the first electronic device determines that the ceiling light of the living room corresponding to the card 65 has been successfully shared with the second electronic device. Figure 11In the shown interface 101, the first electronic device can display a sharing animation in which the card 65 moves out of the window 64, thus vividly informing the user that the control authority of the current living room light has been shared with other devices.

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

[0227] Exemplarily, as Figure 12 shown in (a) below, 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 Figure 12 shown in the interface 1202 in (b) below, the second electronic device can display the card 121 corresponding to the ceiling light in the living room (i.e., the first interface element). 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 the second electronic device automatically generates it according to the device information.

[0228] In some examples, on the smart life application interface, the second electronic device displays multiple cards corresponding to multiple devices in sequence according to certain rules. For example, the display positions of the cards corresponding to the devices are 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 in (c) below. That is, through the moving-in animation effect, it vividly informs the user 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, facilitating the user to operate the card 121 corresponding to the living room light. Figure 12 In some embodiments, for the method shown above

[0229] shown, the first electronic device realizes the sharing of the control authority of the first target intelligent device through the interaction with the second electronic device and the server. Then, after the permission sharing is successful, the first electronic device and the second electronic device can also obtain the message of the successful sharing through the interaction, so as to display the sharing animation. Figure 10

[0230] Figure 13 Figure 13 is a schematic flowchart of another permission sharing method provided by the embodiments of the present application. It should be noted that this method does not Figure 13And subject to the specific order described below, it should be understood that in other embodiments, the order of some steps of the method can be interchanged according to actual needs, or some of the steps can also be omitted or deleted. The method includes the following steps:

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

[0232] S1302. The server sends a sharing success response to the first electronic device.

[0233] In some embodiments, after the server determines to establish a sharing relationship between the second electronic device and the device to be shared, it can send a sharing success response to the first electronic device and the second electronic device respectively, so as to inform the first electronic device and the second electronic device that the server has shared the permissions of the device to be shared to the second electronic device.

[0234] 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 the server determines to establish a sharing relationship, it can send a sharing success response to the first electronic device, and carry the device identifier 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 the first electronic device receives the sharing success response, it can determine which intelligent devices have been shared with which control device.

[0235] In some examples, the sharing success response sent by the server to the second electronic device carries the device information of the intelligent device that has been shared successfully. Alternatively, the sharing success response sent by the server to the second electronic device does not carry the device information of the intelligent device that has been shared successfully, and after the first electronic device receives the sharing success response, it sends the device information of the intelligent device that has been shared successfully to the second electronic device through a secure communication connection with the second electronic device.

[0236] In some examples, the server can 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 can 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 embodiments of the present application do not limit the execution order of step S1301 or step S1302.

[0237] In other examples, the server can send a sharing success response to the first electronic device or the second electronic device alone.

[0238] 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 as indicated by the sharing success response. After that, the second electronic device sends a device sharing success indication to the first electronic device through the secure communication connection with the first electronic device, and the device sharing success indication carries the device identifier of the smart device that has been successfully shared. In this way, after receiving the device sharing success indication, the first electronic device can also determine that the device corresponding to the device identifier has been shared with the second electronic device. That is, step S1302 is an optional step.

[0239] 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 as indicated by the sharing success response and the corresponding second electronic device. After that, the first electronic device sends a device sharing success indication to the second electronic device through the secure communication connection with the second electronic device, and the device sharing success indication carries the device information of the smart device that has been successfully shared. In this way, after receiving the device sharing success indication, the second electronic device can also determine that it has obtained the control authority of the device corresponding to the device information. That is, step S1301 is an optional step.

[0240] S1303. The first electronic device displays a sharing animation.

[0241] In some embodiments, after the first electronic device determines the device that has been successfully shared, it can display a sharing animation to prompt the user that the device has been shared with other devices.

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

[0243] S1304. The second electronic device displays a sharing animation.

[0244] In some embodiments, after the second electronic device determines the device that has been successfully shared, it can display a sharing animation to prompt the user that it has obtained the control authority of the device.

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

[0246] In this way, by displaying the sharing animation, it helps the user quickly confirm the device sharing situation, realize precise control of the shared device, and effectively improve the user experience.

[0247] In some scenarios, the user operating the second electronic device may need to control all the third electronic devices in a certain home controlled by the first electronic device, through the aboveFigure 10 The method shown can achieve the sharing of the control permissions of all third electronic devices. However, the process of selecting the third electronic device may be relatively complex, and the data transmission volume is relatively large.

[0248] 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 the proximity or tap of the second electronic device, the first electronic device can share the control permissions of the smart devices managed in this space management interface to the second electronic device.

[0249] Exemplarily, as Figure 14 shown in (a) below, 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 to the smart life application. As shown by the reference numeral 141, the currently displayed home is the home of A. In response to the operation of the user on the control indicated by the reference numeral 141, the first electronic device displays a menu bar window 142. After that, in response to the operation of the user on the home management control 143 in the menu bar window 142, the first electronic device can display a home management interface 1402 as shown in Figure 14 shown in (b) below. In response to the operation of the user on the control 144 on the home management interface 1402, the first electronic device can display a home details page 1403 (i.e., the first sharing interface) as shown in Figure 14 shown in (c) below. The details information of the home of A, such as the home name, home location, family members, etc., is displayed on the home details page 1403. After that, the first electronic device detects the operation of the user on the add member control 145 (i.e., the first interface element), and determines that the user instructs to add a family member to the home of A. After that, after the first electronic device responds to the tap operation of the user, it determines to share the currently displayed home of A to the second electronic device.

[0250] In some examples, the first interface element includes a display element associated with adding a user, such as the add member control 145. Among them, the added user is used to control the first target smart device. Then, after the sharing of the smart devices in the home is successful, the first electronic device can display a second interface element, and the second interface element includes a display element associated with the user of the second electronic device. Optionally, the first electronic device can also display an animation effect, and the animation effect includes the animation effect of the display element associated with the user of the second electronic device moving in.

[0251] Exemplarily, as Figure 14 shown in the interface 1404 in (d) below, the first electronic device displays a sharing animation. As shown by the reference numeral 146, the first electronic device displays an animation of the avatar (or home icon) of the smart life application logged in by the second electronic device moving into the currently displayed home details page. After that, as Figure 15As shown in the interface 1501, on the family details page of A's home on the first electronic device, the avatar 151 (i.e., the second interface element) is displayed in the family member section. If the avatar 151 is the avatar of the smart life application account logged in on the second electronic device, the user can confirm that the current family has been successfully shared with the second electronic device.

[0252] In some examples, after the permission sharing of the smart device is successful, the second electronic device can also display an animation effect.

[0253] Exemplarily, as Figure 16 shown in the interface 1601 in (a), the second electronic device displays the smart life application. As shown by the reference numeral 161, the family managed under the account logged in to the current smart life application is B's home, and the number of devices in the home is 11. After that, in response to the user's touch operation, the second electronic device determines that the family sharing is successful. Then, as Figure 16 shown in the interface 1602 in (b), the second electronic device displays an animation in which the avatar (or family icon) 162 of the smart life application logged in on the first electronic device flies into the currently displayed smart life interface, so as to help the user confirm that the family sharing has been completed.

[0254] In some examples, when the user performs family sharing, it is necessary to operate the devices in the family. Therefore, after the second electronic device obtains the control permission of the family shared by the first electronic device, it can switch to display the device management interface of the family, so as to facilitate the user to operate the devices.

[0255] Exemplarily, as Figure 16 shown in the interface 1603 in (c), after the second electronic device displays the family sharing animation, as shown by the reference numeral 163, it can directly switch to display the device management interface corresponding to A's home where the sharing is successful. In this way, the operation of the user to switch families is simplified, and the user experience is improved.

[0256] Optionally, for other contents to implement the sharing animation display on the first electronic device and the second electronic device, reference can be made to the relevant contents of step S1301-step S1304 shown above. This application embodiment will not elaborate on this. Figure 13

[0257] In this way, during the home sharing process, the user only needs 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 user operation difficulty is effectively reduced.

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

[0259] ​In some scenarios, the first electronic device responds to the proximity or touch of the second electronic device to establish a short - range communication connection, and based on this short - range communication connection, realizes sharing the control authority of the first target intelligent device in the home to the second electronic device. The following is a detailed introduction to the method of sharing the control authority of the home group through Figure 17 the method shown below.

[0260] In some examples, the server can share the permissions of all third - electronic devices in the home by adding the first application account of the second electronic device as a family member of a certain home in the first application account of the first electronic device, enriching the device permission sharing scenario and enhancing the user experience.

[0261] Figure 17 FIG. is a schematic flowchart of another permission sharing method provided by the embodiments of the present application. It should be noted that this method is not limited by Figure 17 the specific order described below. It should be understood that in other embodiments, the order of some steps of this method can be interchanged according to actual needs, or some of the steps can also be omitted or deleted. The method includes the following steps:

[0262] S1701. The first electronic device detects that the user indicates an operation of adding a family member in the first application.

[0263] In some embodiments, an entry for adding a family member is provided in the first application of the first electronic device. For example, the user can add a family member by entering a Huawei account. It can be seen that since the user needs to remember the Huawei account, the difficulty is relatively high. Therefore, based on the permission sharing method such as the above Figure 10 example, the first electronic device and the second electronic device can also complete the addition of family members based on the near - field communication method.

[0264] Exemplarily, as shown in the family details page 1403 in (c) of Figure 14 , the first electronic device detects the operation of the user on the add - member control 145 and determines that the user indicates adding a family member in the home of A.

[0265] S1702. In response to a preset operation, the first electronic device obtains the identification code generated by the second electronic device.

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

[0267] S1704. The first electronic device obtains the account logged in by the second electronic device through the secure communication connection.

[0268] In some embodiments, during the process of the first electronic device displaying the home details page (such as the home details page 1403), when a preset operation (such as a tap-and-touch operation) is detected, it can be determined that an operation indicating the addition of a family member by the user is detected. That is, during the process of the first electronic device displaying the home details page, the user can directly trigger the first electronic device to add a family member through the tap-and-touch operation, without having to operate on the add member control anymore, thus simplifying the user operation.

[0269] Optionally, for the other content of steps S1702 - S1704, reference can be made to the relevant content of steps S1002 - S1004 above, which will not be elaborated here.

[0270] S1705. The first electronic device sends the home identifier of the home that the first application is currently displaying home and the account logged in by the second electronic device to the server.

[0271] In some embodiments, during the process of the first electronic device running the first application, an operation indicating the addition of a family member by the user is detected. Therefore, the first electronic device can determine which home under the first application account the first application is currently displaying, and then can obtain the home identifier of this home. Then, after the first electronic device obtains the account logged in by the second electronic device, it can send this home identifier and this account to the server to request to obtain a sharing code for adding this account to the home corresponding to this home identifier.

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

[0273] In some examples, only one home is managed under the account logged in by the first electronic device. Then, after the first electronic device obtains the account logged in by the second electronic device, it can directly send this account to the server to obtain the sharing code. That is, the first electronic device does not need to send this home identifier to the server anymore, and the server can also determine the unique home based on the account logged in by the first electronic device later and generate the corresponding sharing code.

[0274] S1706. The server generates a sharing code according to the home identifier and the account logged in by the second electronic device.

[0275] In some embodiments, after the server receives the homeId and member UserId sent by the first electronic device, it determines that the home corresponding to the homeId is the home managed under the account logged in by the first electronic device. Then, the server can generate a corresponding sharing code (shareCode).

[0276] In some examples, the sharing code generated by the server is configured with expiration conditions, such as usage times requirements, usage time requirements, 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 an effective usage period for the sharing code, such as being valid within 5 minutes, etc.

[0277] S1707. The server sends the sharing code to the first electronic device.

[0278] S1708. The first electronic device sends the sharing code to the second electronic device.

[0279] S1709. The second electronic device sends a home sharing request to the server, and the home sharing request carries the sharing code.

[0280] In some embodiments, the home sharing request sent by the second electronic device to the server carries the sharing code, and the sharing code is used to share the control permission of the third electronic device in the home corresponding to the homeId, so as to join the home corresponding to the homeId, thereby realizing the sharing of the home of the first electronic device.

[0281] Optionally, for other contents of steps S1707 - S1709, reference can be made to the relevant contents of steps S1007 - S1009 above, which will not be elaborated here.

[0282] S1710. The server establishes a sharing relationship between the second electronic device and the home indicated by the sharing code according to the account logged in by the second electronic device and the sharing code.

[0283] In some embodiments, after receiving the home 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 to determine whether the sharing code is correct. If the sharing code is correct, the server further parses and authenticates the sharing code. If the sharing code is incorrect, the server sends a home sharing failure response to the second electronic device.

[0284] After that, when the sharing code is correct, the server obtains the home identifier and the first application account indicated by the sharing code. Then, the server determines whether the account logged in by the second electronic device that sends the home 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 home corresponding to the home identifier 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 home sharing failure response to the second electronic device.

[0285] In some embodiments, the server manages one or more families under the account through the first application. Then, after the server determines to share the family of the first electronic device with the second electronic device, it can obtain the information of the family managed under the account logged in by the first electronic device, such as including the family identifier, the device information of at least one third electronic device recorded under the family, etc. After that, the server creates a new family under the first application account logged in by the second electronic device, and sets the information of the newly created family to the information of the family of the first electronic device for which the sharing is successful, so as to establish the sharing relationship of the home corresponding to the second electronic device and the family identifier.

[0286] In some embodiments, after the server establishes the sharing relationship of the home corresponding to the second electronic device and the family identifier, it can send a home sharing success response to the second electronic device. Optionally, the sharing success response carries the information of the home, such as including the family identifier, the device information of at least one third electronic device recorded under the home, etc. In this way, after receiving the home sharing success response, the second electronic device can obtain the permission to manage the home, such as establishing a communication connection with the devices in the home according to the device information carried in the home sharing success response.

[0287] In some examples, the control permission of the second electronic device for the shared home is less than or equal to the control permission of the first electronic device for the shared home.

[0288] In this way, during the home sharing process, the user only needs a simple tap 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, effectively reducing the user operation difficulty.

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

[0290] The above takes the first electronic device actively performing a tap operation with the second electronic device to initiate the permission sharing process as an example to introduce the permission sharing process. In some examples, the second electronic device can also actively initiate the permission sharing process. The following details the process of the second electronic device actively initiating the permission sharing.

[0291] In some examples, the first electronic device is a user terminal or a central control device in the space. In some scenarios, when the first electronic device is a central control device, the second electronic device can obtain the control permission of the smart devices in the home managed by the central control device in response to approaching or tapping the first electronic device.

[0292] Figure 18The flowchart of another permission sharing method provided by the embodiments of this application. It should be noted that this method is not limited by Figure 18 the specific order described below. It should be understood that in other embodiments, the order of some steps of this method can be interchanged according to actual needs, or some of the steps can also be omitted or deleted. The method includes the following steps:

[0293] S1801. During the process of the second electronic device displaying the first application, in response to a preset operation, obtain the identification code preset in the first electronic device.

[0294] In some embodiments, an identification code is preset in the first electronic device, written into the NFC tag, and the NFC mode is marked as the tag mode.

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

[0296] 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, fixedly set at a certain position in the home. In this way, after other users bring the second electronic device into the home, they can request to join the group (home) managed by the first electronic device through operations such as a tap.

[0297] 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. However, after the first electronic device (such as a smart home device control panel) logs in to the first application account, it will display the home interface matching the current location according to the positioning, so as to manage the third electronic devices in the home where it is currently located. Or, during the process of the first electronic device logging in to the first application account, the server determines the home where the first electronic device is located, so that after the first electronic device logs in to the first application account, it can only display the device management interface of this home and manage the devices in this home.

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

[0299] S1803. The second electronic device obtains the account and home identifier logged in by the first electronic device through the secure communication connection.

[0300] In some examples, when the number of homes under the account logged in on 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 the unique home according to the account logged in on the first electronic device.

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

[0302] Optionally, for other content of steps S1802 - S1803, reference may be made to the relevant content of steps S1003 - S1004 above, which will not be elaborated here.

[0303] S1804. The second electronic device sends a group join request to the server, and the group join request carries the account logged in on the first electronic device and the home identifier.

[0304] In some embodiments, after obtaining the account logged in on the first electronic device and the home identifier, the second electronic device may send a group join request to the server to request to join the home corresponding to the home identifier under the account of the first application. Correspondingly, the server receives the group join request sent by the second electronic device.

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

[0306] S1806. The permission management device sends a permission acquisition response to the server.

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

[0308] Optionally, the permission management device is, for example, at least one device that has logged in to the account and the account is currently in a logged-in state. For example, the user has logged in to 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 may determine the mobile phone as the permission management device. Or, the account is logged in on both the mobile phone and the tablet, then the server may determine both the mobile phone and the tablet as the permission management devices.

[0309] Optionally, the permission management device is, for example, the device that registered the account of the first application.

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

[0311] Optionally, the permission acquisition request carries a home identifier and the account logged in to 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 home identifier and the account of the first application, so as to prompt the user to confirm whether to allow the account of the first application to join the home corresponding to the home identifier. After that, the permission management device generates a permission acquisition response according to the user operation.

[0312] In some embodiments, during the authorization process, the permission management device can also determine the scope of permissions indicated by the user for authorization according to the user operation. For example, allowing the second electronic device to obtain the control permissions of all devices in the home, or allowing the second electronic device to obtain the control permissions of some devices in the home, or not allowing the second electronic device to obtain the control permissions of the devices in the home, etc.

[0313] S1808. The server adds the account logged in to the second electronic device to the group corresponding to the home identifier according to the account logged in to the second electronic device.

[0314] In some embodiments, the server determines whether the second electronic device is authorized according to the received permission acquisition response. For example, if the permission acquisition response indicates that the second electronic device is not authorized, the server can send a group join failure response to the second electronic device. Another example is that if the permission acquisition response indicates that the second electronic device is authorized, the server can add the account logged in to 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).

[0315] 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 home group managed by the first electronic device. The user operation is simple, effectively reducing the user operation difficulty.

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

[0317] In some embodiments, after the group sharing is completed, the first electronic device and the second electronic device can also display corresponding sharing animations. Among them, the display process and display effect of the sharing animation can refer to the display process and display effect of the sharing animation during the home sharing process between the first electronic device and the second electronic device, which will not be elaborated in this embodiment of the present application.

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

[0319] Optionally, Figure 19 is a schematic flowchart of another permission sharing method provided by the embodiments of this application. As Figure 19 shown, the method includes the following steps.

[0320] S1901. The first electronic device displays a first sharing interface.

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

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

[0323] S1902. An operation on a first interface element in the first sharing interface is detected.

[0324] 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 to the second electronic device. For example, the first interface element is a card.

[0325] S1903. In response to approaching or a tap - to - connect with the second electronic device, the first electronic device shares the control permission of the first target smart device corresponding to the first interface element to the second electronic device.

[0326] S1904. The second electronic device displays an animation effect.

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

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

[0329] Moreover, during the device sharing process, the user only needs to perform a simple tap - to - connect operation to trigger the first electronic device and the second electronic device to automatically complete the permission sharing. The user operation is simple, effectively reducing the user operation difficulty.

[0330] Optionally, for other content of steps S1901 - S1904, reference may be made to the relevant content executed by the above-mentioned first electronic device or second electronic device, which will not be elaborated here.

[0331] The above has been combined with Figure 6 - Figure 19 and has elaborated in detail the permission sharing method provided by the embodiments of the present application. The following will be combined with Figure 20 and will elaborate in detail the first electronic device provided by the embodiments of the present application, and will be combined with Figure 21 and will elaborate in detail the second electronic device provided by the embodiments of the present application.

[0332] In a possible design, Figure 20 is a schematic structural diagram of the first electronic device provided by the embodiments of the present application. As Figure 20 shown, 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 can be used to implement the functions of the first electronic device involved in the above method embodiments.

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

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

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

[0336] Among them, the transceiver unit may include a receiving unit and a transmitting unit, and can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or a transceiver module. The operations and / or functions of each unit in the first electronic device 2000 respectively implement the corresponding processes of the permission sharing method described in the above method embodiments. All relevant contents of each step involved in the above method embodiments can be cited in the function descriptions of the corresponding functional units. For the sake of brevity, they will not be repeated here.

[0337] Optionally, Figure 20 the first electronic device 2000 shown may further include a storage unit ( Figure 20 not shown in the figure), and a program or instruction is stored in the storage unit. When the transceiver unit 2001, the processing unit 2002, and the display unit 2003 execute the program or instruction, Figure 20 the first electronic device 2000 shown can execute the permission sharing method described in the above method embodiments.

[0338] Figure 20 The technical effects of the first electronic device 2000 shown can refer to the technical effects of the permission sharing method described in the above method embodiments, and will not be repeated here.

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

[0340] In a possible design, Figure 21 is a schematic structural diagram of a second electronic device provided in an embodiment of this application. As Figure 21 shown, 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 can be used to implement the functions of the second electronic device involved in the above method embodiments.

[0341] Optionally, the transceiver unit 2101 is used to support the second electronic device 2100 to execute Figure 10 S1002, S1003, S1004, S1008, and S1009 in Figure 13 ; and / or, used to support the second electronic device 2100 to execute Figure 17 S1301 in Figure 18 ; and / or, used to support the second electronic device 2100 to execute Figure 19S1903 in it.

[0342] Optionally, a processing unit 2102, configured to support the second electronic device 2100 to execute Figure 19 S1902 in it.

[0343] Optionally, a display unit 2103, configured to support the second electronic device 2100 to execute Figure 13 S1302 in it; and / or, configured to support the second electronic device 2100 to execute Figure 19 S1904 in it.

[0344] Wherein, the transceiver unit may include a receiving unit and a transmitting unit, and may be implemented by a transceiver or transceiver-related circuit components, 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 for implementing the corresponding processes of the permission sharing method described in the above method embodiments. All relevant contents of each step involved in the above method embodiments can be cited in the function descriptions of the corresponding functional units. For the sake of brevity, they will not be elaborated here.

[0345] Optionally, Figure 21 the second electronic device 2100 shown may further include a storage unit ( Figure 21 not shown in the figure), and a program or instruction is stored in the storage unit. When the transceiver unit 2101, the processing unit 2102, and the display unit 2103 execute the program or instruction, Figure 21 the second electronic device 2100 shown can execute the permission sharing method described in the above method embodiments.

[0346] Figure 21 The technical effects of the second electronic device 2100 shown can refer to the technical effects of the permission sharing method described in the above method embodiments, and will not be elaborated here.

[0347] In addition to the form of the second electronic device 2100, the technical solution provided in this application can also be a functional unit or chip in the second electronic device, or a device used in conjunction with the second electronic device.

[0348] This application embodiment also provides a chip system, including: a processor, the processor is coupled to a memory, and the memory is used to store a program or instruction. When the program or instruction is executed by the processor, the chip system implements the method in any of the above method embodiments.

[0349] Optionally, there may be one or more processors in the chip system. 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 that implements functions by reading software code stored in a memory.

[0350] Optionally, there may also be one or more memories in the chip system. The memory may be integrated with the processor or may be separately provided from the processor, which is not limited in the embodiments of the present application. Exemplarily, the memory may be a non-transitory processor, such as a read-only memory (ROM). It may be integrated with the processor on the same chip or may be separately provided on different chips. The embodiments of the present application do not specifically limit the type of the memory and the setting manner of the memory and the processor.

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

[0352] It should be understood that the steps in the above method embodiments may be completed by the integrated logic circuit in the hardware of the processor or by instructions in the form of software. The method steps disclosed in combination with the embodiments of the present application may be directly embodied as being executed and completed by the hardware processor, or may be executed and completed by a combination of the hardware and software modules in the processor.

[0353] The embodiments of the present application further provide a computer-readable storage medium, in which a computer program is stored. When the computer program runs on a computer, the computer is enabled to execute the above related steps to implement the permission sharing method in the above embodiments.

[0354] An embodiment of the present application also provides a computer program product. When the computer program product runs on a computer, it causes the computer to execute the above-related steps to implement the permission sharing method in the above embodiment.

[0355] In addition, an embodiment of the present application also provides a device. The device may specifically be a component or a module, and the device may include one or more processors and a memory connected thereto. Among them, the memory is used to store a computer program. When the computer program is executed by one or more processors, it causes the device to execute the permission sharing method in each of the above method embodiments.

[0356] Among them, the device, computer-readable storage medium, computer program product or chip provided by the embodiments of the present application are all 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 elaborated here.

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

[0358] Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the above division of each functional module is used as an example. In actual applications, the above functions can be allocated 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 processes of the above-described system, device, and unit can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated here.

[0359] In several embodiments provided by the present application, it should be understood that the disclosed method can be implemented in other ways. The device embodiments described above are merely illustrative. 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 displayed or discussed coupling or direct coupling or communication connection to each other can be through some interfaces, and the indirect coupling or communication connection of the modules or units can be in electrical, mechanical or other forms.

[0360] In addition, each functional unit in various embodiments of the present application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0361] The computer-readable storage medium includes but is not limited to any of the following: USB flash drive, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disc, etc., which can store program codes.

[0362] As described above, it is only the specific implementation manner 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 covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A permission sharing method, It is characterized in that Applied to a first electronic device, 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.

2. The method according to claim 1, It is 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.

3. The method according to claim 1 or 2, It is characterized in that The step of sharing the control authority of the first target smart device corresponding to the first interface element to the second electronic device in response to approaching or touching the second electronic device includes: 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.

4. The method according to claim 1 or 2, It is characterized in that The step of sharing the control authority of the first target smart device corresponding to the first interface element to the second electronic device in response to approaching or touching the second electronic device includes: 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.

5. The method according to any one of claims 1 to 4, It is characterized in that The first interface element includes a display element associated with the first target smart device, and the method further includes: The first interface element is shared to the second electronic device.

6. The method according to claim 5, It is characterized in that The first interface element is a card.

7. The method according to any one of claims 1 to 6, It is 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.

8. The method according to claim 2, It 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.

9. The method according to any one of claims 1 to 8, It is characterized in that The step of sharing the control authority of the first target smart device corresponding to the first interface element to the second electronic device in response to approaching or touching the second electronic device 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.

10. The method according to any one of claims 1 to 9, It is characterized in that The approach or touch is based on one or more of the short-range wireless communication NFC technology, the low-power BLE Bluetooth technology, and the short-range local area network NAN communication technology.

11. The method according to any one of claims 1 to 10, It is characterized in that The control authority is an authority range specified by a user of the first electronic device.

12. The method according to any one of claims 1 to 11, It 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.

13. The method according to any one of claims 1 to 12, It is characterized in that The first electronic device is a user terminal or a central control device in a space.

14. A permission sharing method, It is characterized in that Applied to a second electronic device, the method includes: 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.

15. The method according to claim 14, It is 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.

16. The method according to claim 14 or 15, It is 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.

17. The method according to claim 16, It is characterized in that The first interface element is a card.

18. The method according to any one of claims 14 to 17, It is characterized in that 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; 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.

19. The method according to any one of claims 14 to 17, It is characterized in that 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.

20. An electronic device, It is characterized in that include: 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 codes, and the computer program codes include 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.

21. A computer-readable storage medium, It is characterized in that The computer-readable storage medium includes a computer program, which, when executed on an electronic device, enables the electronic device to execute the method as claimed in any one of claims 1 to 13; or enables the electronic device to execute the method as claimed in any one of claims 14 to 19.

22. A computer program product, It is characterized in that When the computer program product is executed on a computer, the computer is enabled to execute the method according to any one of claims 1 to 13; or the computer is enabled to execute the method according to any one of claims 14 to 19.

Images