Permission management method and electronic device

By setting the target range and determining the authorization scope of electronic devices, the privacy leakage problem caused by the information exposure of IoT devices is solved, the security management of electronic devices is achieved, and the risk of privacy leakage is reduced.

WO2024244477A1PCT designated stage expired Publication Date: 2024-12-05HUAWEI TECH CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/071347
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-29
Filing Date
2024-01-09
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

With the development of IoT devices, after users’ electronic devices are connected to the IoT system, the device information is easily exposed, which increases the risk of privacy leakage, and it is difficult for existing technologies to effectively reduce this risk.

Method used

Provides a permission management method, by setting the target scope, determining the authorization scope of electronic devices, allowing only designated user accounts or devices to access and interact, and reducing unauthorized information acquisition and interaction.

Benefits of technology

It effectively reduces the risk of privacy leakage of electronic device owners, reduces the received undesired interactive messages, and protects user privacy.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024071347_05122024_PF_FP_ABST
    Figure CN2024071347_05122024_PF_FP_ABST
Patent Text Reader

Abstract

A permission management method and an electronic device, which are applied to the field of terminals. In the method, when at least one first target device bound to a first device is determined, the authorization range of the first target device may be set as a target range, wherein the target range represents that an electronic device, to which a first user account logs in, has an access permission to the first target device, and the first user account is a user account that logs in to the first device. Then, setting information may be sent to a server, so as to instruct the server to manage, on the basis of the target range, the access permission of an electronic device that requests the access to the first target device, thereby reducing the risk of privacy leakage of an owner of the first device.
Need to check novelty before this filing date? Find Prior Art

Description

Rights management method and electronic device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on May 29, 2023, with application number 202310618949.7 and application name “Authority Management Method and Electronic Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminal technology, and in particular to a rights management method and electronic device. Background Art

[0003] With the development of Internet of Things (IoT) technology and electronic devices, more and more IoT devices are being used by users. Users can bind IoT devices to one or more electronic devices, allowing them to control the bound IoT devices through the electronic devices. For example, a user can control IoT device A, which is bound to electronic device A, through electronic device A.

[0004] Currently, once electronic device A is connected to the IoT system, the device information of IoT device A bound to electronic device A will also be exposed in the IoT system, increasing the risk of privacy leakage of the owner of the electronic device.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a rights management method and an electronic device, which can reduce the risk of privacy leakage of the owner of the electronic device.

[0007] To achieve the above objectives, the present invention adopts the following technical solutions:

[0008] In a first aspect, an embodiment of the present application provides a permission management method, in which at least one first target device can be determined, and the first target device is bound to the first device. The authorization scope of the first target device is set to the target range. The target range represents that the electronic device logged in with the first user account has access rights to the first target device, and the first user account is the user account logged in by the first device. Setting information is sent to the server, and the setting information includes the target range, and the setting information is used to instruct the server to manage the access rights of the electronic device requesting access to the first target device based on the target range.

[0009] In the method of the present application, a user can have multiple electronic devices, and each electronic device can be bound to multiple IoT devices. Multiple electronic devices can log in to the same user account on the server in the IoT system. If any electronic device at the control end such as a mobile phone or tablet is referred to as the first device. IoT devices such as speakers, smart screens, smart speakers, and learning smart screens that are bound to the first device are referred to as second devices. The present application can open the device information of the second device bound to the first device only to designated electronic devices and / or one or more electronic devices logged in by a designated user account for viewing. For example, the device information of the second device bound to the first device can be opened to electronic devices logged in with the first user account for viewing, which can reduce the risk of privacy leakage of the owner of the electronic device.

[0010] In conjunction with the first aspect, in one possible design, in response to an input permission setting instruction, a first device list is displayed. The first device list includes the device identifier of at least one second device bound to the first device. A selection operation of at least one device identifier in the first device list is detected, and at least one first target device is determined. The first target device includes the second device corresponding to the selected device identifier in the first device list.

[0011] In this solution, at least one first target device can be determined based on the first device list, and then the visibility range of the at least one first target device can be set, thereby reducing the risk of privacy leakage of the owner of the first target device.

[0012] In combination with the first aspect, in a possible design, the target range further represents that the electronic device logged in with the second user account has access rights to the first target device.

[0013] In this solution, because the target range also indicates that electronic devices logged into the second user account have access rights to the first target device, electronic devices not logged into the second user account cannot obtain device information of the first target device or interact with the first target device. This can reduce the number of unwanted interaction messages received by the first target device, thereby reducing the risk of privacy leakage for the owner of the first target device.

[0014] In conjunction with the first aspect, in one possible design, after determining at least one first target device, a first interface may be displayed, the first interface being used to set a target range. A first instruction input based on the first interface is received, and in response to the first instruction, an account list is displayed, the account list including an account identifier of at least one user account associated with the first user account. A selection operation of at least one account identifier in the account list is detected, and at least one second user account is determined, the second user account being the user account corresponding to the selected account identifier in the account list. A target range is determined based on the second user account.

[0015] The second user account includes one or more user accounts associated with the first user account. For example, the second user account is in the first user account's contact list. This means that the first user account has previously interacted with the second user account. Another example is that the second user account and the first user account have a friend relationship.

[0016] In this solution, the visible range of the first target device can be set in the account dimension, and electronic devices that are not logged in to the second user account can be restricted from obtaining the device information of the first target device and interacting with the first target device. This can reduce the number of unexpected interaction messages received by the first target device, thereby reducing the risk of privacy leakage of the owner of the first target device.

[0017] In conjunction with the first aspect, in one possible design, after determining at least one first target device, a first interface may be displayed, the first interface being used to set a target range. A fifth instruction input based on the first interface is received. In response to the fifth instruction, an input control is displayed. Based on the content input in the input control, at least one second user account represented by the content is determined. Based on the second user account, a target range is determined.

[0018] In this solution, the user can customize a second user account. A target range can then be determined based on the second user account. Because the determined target range indicates that electronic devices logged into the second user account have access rights to the first target device, regardless of whether the second user account is associated with the first user account, electronic devices logged into the second user account can obtain device information about the first target device and interact with it.

[0019] In combination with the first aspect, in one possible design, a first request is sent to a server, the first request including a second user account, the first request being used to request a second device list, the second device list including device identifiers of electronic devices logged in with the second user account. The second device list sent by the server is displayed. A selection operation on at least one device identifier in the second device list is detected, and a second target device is determined, the second target device including the electronic device corresponding to the device identifier selected in the second device list. Based on the second user account and the second target device, a target range is determined, the target range indicating that the second target device logged in with the second user account has access rights to the first target device.

[0020] In this solution, the visible range of the first target device can be set in the device dimension, and the second target device that is not logged in to the second user account can be restricted from obtaining the device information of the first target device and interacting with the first target device. This can reduce the number of unexpected interaction messages received by the first target device, thereby reducing the risk of privacy leakage of the owner of the first target device.

[0021] In combination with the first aspect, in a possible design, the target range further represents that an electronic device logged in with a third user account does not have access permission to the first target device.

[0022] In this solution, because the target range also indicates that electronic devices logged into the third user account do not have access rights to the first target device, electronic devices logged into the third user account cannot obtain device information of the first target device or interact with the first target device. This can reduce the number of unwanted interaction messages received by the first target device, thereby reducing the risk of privacy leakage for the owner of the first target device.

[0023] In conjunction with the first aspect, in one possible design, after determining at least one first target device, a first interface may be displayed, the first interface being used to set a target range. A second instruction input based on the first interface is received. In response to the second instruction, an account list is displayed, the account list including an account identifier of at least one user account associated with the first user account. A selection operation of at least one account identifier in the account list is detected, and at least one third user account is determined. The third user account is the user account corresponding to the selected account identifier in the account list. A target range is determined based on the third user account.

[0024] The third user account includes one or more user accounts associated with the first user account. For example, the third user account is in the first user account's contact list. This means that the first user account has previously interacted with the third user account. Another example is that the third user account and the first user account have a friend relationship.

[0025] In this solution, the visibility range of the first target device can be set based on the account dimension, and electronic devices logged in with a third user account can be restricted from obtaining the device information of the first target device and interacting with the first target device. In other words, all electronic devices logged in with the third user account cannot obtain the device information of the first target device or interact with the first target device. This can reduce the number of unwanted interaction messages received by the first target device, thereby reducing the risk of privacy leakage for the owner of the first target device.

[0026] In conjunction with the first aspect, in one possible design, after determining at least one first target device, a first interface may be displayed, the first interface being used to set a target range. A fourth instruction input based on the first interface is received. In response to the fourth instruction, an input control is displayed. Based on content input in the input control, at least one third user account represented by the content is determined. The target range is determined based on the third user account.

[0027] In this solution, the user can customize a third user account. A target range can then be determined based on the third user account. Because the determined target range indicates that electronic devices logged into the third user account do not have access to the first target device, regardless of whether the third user account is associated with the first user account, electronic devices logged into the third user account cannot obtain device information of the first target device or interact with it. This reduces the number of unwanted interaction messages received by the first target device, thereby reducing the risk of privacy leakage for the owner of the first target device.

[0028] In combination with the first aspect, in one possible design, a second request is sent to the server, the second request including a third user account, the second request being used to request a third device list, the third device list including device identifiers of electronic devices logged in with the third user account. The third device list sent by the server is received and displayed. A selection operation on at least one device identifier in the third device list is detected, and a third target device is determined, the third target device including the electronic device corresponding to the device identifier selected in the third device list. Based on the third user account and the third target device, a target range is determined, the target range indicating that the third target device logged in with the third user account does not have access rights to the first target device.

[0029] In this solution, the visibility range of the first target device can be set in the device dimension, and a third target device logged in with a third user account can be restricted from accessing the device information of the first target device and interacting with the first target device. This can reduce the number of unwanted interaction messages received by the first target device, thereby reducing the risk of privacy leakage for the owner of the first target device.

[0030] In conjunction with the first aspect, in one possible design, after determining at least one first target device, a first interface may be displayed, the first interface being used to set a target range. A third instruction input based on the first interface is received. In response to the third instruction, the target range is determined.

[0031] In this solution, the third instruction is used to instruct that the device information of the first target device be visible only to electronic devices logged into the first user account. The visibility range of the first target device can be set based on the account, restricting electronic devices not logged into the first user account from accessing the device information of the first target device and interacting with it. This can reduce the number of unwanted interaction messages received by the first target device, thereby reducing the risk of privacy leakage for the owner of the first target device.

[0032] In a second aspect, an embodiment of the present application provides a permission management method, in which setting information sent by a first device is received. The setting information includes a target range, and the setting information is used to indicate that access rights of electronic devices requesting access to the first target device are managed based on the target range, and the first target device is bound to the first device. The target range indicates that electronic devices logged in with a first user account have access rights to the first target device, and the first user account is the user account logged in by the first device. In response to the setting information, access rights of electronic devices requesting access to the first target device are managed based on the target range.

[0033] In the method of the present application, after receiving the setting information sent by the first device, the setting information can be stored in the storage space corresponding to the first user account, so that the device information of the second device bound to the first device is only available to the designated electronic device and / or one or more electronic devices logged in by the designated user account for viewing based on the setting information. For example, the device information of the second device bound to the first device can be made available to the electronic device logged in by the first user account for viewing, which can reduce the risk of privacy leakage of the electronic device owner.

[0034] In conjunction with the second aspect, in one possible design, after receiving the setting information sent by the first device, when a third device is detected, the authorization range of the first target device bound to the third device is updated to the target range based on the setting information. The third device includes an electronic device logged in with the first user account, and the third device is different from the first device.

[0035] In this solution, after receiving the setting information sent by the first device, the third device can send an update instruction to the third device if it detects the third device. The update instruction is used to instruct the third device to update the visible range of the first target device bound to the third device to the target range. After receiving the update instruction, the third device can update the visible range of the first target device bound to the third device to the target range.

[0036] In combination with the second aspect, in a possible design, the target range further represents that the electronic device logged in with the second user account has access rights to the first target device.

[0037] In this solution, since the target scope also indicates that electronic devices logged into the second user account have access rights to the first target device, electronic devices requesting device information of the first target device can be managed. Electronic devices not logged into the second user account can be restricted from obtaining device information of the first target device and interacting with the first target device. This can reduce the number of unwanted interaction messages received by the first target device, thereby reducing the risk of privacy leakage for the owner of the first target device.

[0038] In combination with the second aspect, in a possible design, before receiving the setting information sent by the first device, a first request sent by the first device can also be received. The first request includes a second user account, and the second user account includes one or more user accounts associated with the first user account. In response to the first request, a second device list is sent to the first device, and the second device list includes the device identifiers of electronic devices logged in with the second user account. In the case of receiving the setting information sent by the first device based on the second device list, the target range included in the setting information also represents that the second target device logged in with the second user account has access rights to the first target device. The second target device includes the electronic device corresponding to the device identifier selected in the second device list detected by the first device.

[0039] In this solution, based on the target range, the second target device that is not logged in with the second user account can be restricted from obtaining the device information of the first target device and interacting with the first target device, which can reduce the number of unexpected interaction messages received by the first target device, thereby reducing the risk of privacy leakage of the owner of the first target device.

[0040] In conjunction with the second aspect, in one possible design, the second user account is determined based on content input into an input control on the first device. The input control includes a control displayed by the first device in response to a fifth instruction input into the displayed first interface. The fifth instruction is used to instruct the first device to grant access rights to the first target device to the electronic device logged in with the second user account.

[0041] In this solution, the user can customize the second user account. Since the target scope also indicates that electronic devices logged into the second user account have access rights to the first target device, electronic devices requesting device information of the first target device can be managed. Electronic devices not logged into the second user account can be restricted from obtaining device information of the first target device and interacting with the first target device, which can reduce the number of unwanted interaction messages received by the first target device, thereby reducing the risk of privacy leakage for the owner of the first target device.

[0042] In combination with the second aspect, in a possible design, the target range further represents that an electronic device logged in with a third user account does not have access permission to the first target device.

[0043] In this solution, since the target scope also indicates that electronic devices logged into the third user account do not have access rights to the first target device, electronic devices requesting device information of the first target device can be managed. Electronic devices logged into the third user account can be restricted from obtaining device information of the first target device and interacting with the first target device, thereby reducing the number of unwanted interaction messages received by the first target device and thereby reducing the risk of privacy leakage for the owner of the first target device.

[0044] In conjunction with the second aspect, in one possible design, before receiving the setup information sent by the first device, a second request sent by the first device may also be received. The second request includes a third user account, and the third user account includes one or more user accounts associated with the first user account. In response to the second request, a third device list is sent to the first device, where the third device list includes device identifiers of electronic devices logged in with the third user account.

[0045] When the first device receives setting information sent based on the third device list, the target range included in the setting information further indicates that a third target device logged in with a third user account does not have access rights to the first target device. The third target device includes an electronic device corresponding to a device identifier selected from the third device list detected by the first device.

[0046] In this solution, based on the target range, the third target device logged in with a third user account can be restricted from obtaining the device information of the first target device and interacting with the first target device, which can reduce the number of unexpected interaction messages received by the first target device, thereby reducing the risk of privacy leakage of the owner of the first target device.

[0047] In conjunction with the second aspect, in one possible design, the third user account is determined based on content input into an input control on the first device. The input control includes a control displayed by the first device in response to a fourth instruction input into the displayed first interface. The fourth instruction is used to instruct the first device to deny access permissions to the first target device to the electronic device logged in with the third user account.

[0048] In this solution, users can customize a third user account. Because the target scope also indicates that electronic devices logged into the third user account do not have access to the first target device, electronic devices requesting device information of the first target device can be managed. Electronic devices logged into the third user account can be restricted from obtaining device information of the first target device and interacting with the first target device, which can reduce the number of unwanted interaction messages received by the first target device, thereby reducing the risk of privacy leakage for the owner of the first target device.

[0049] In a third aspect, embodiments of the present application provide an electronic device. The electronic device includes a memory and one or more processors, the memory and the processors being coupled; the memory is configured to store computer program code, the computer program code including computer instructions, and when the processor executes the computer instructions, the electronic device executes the method described in the first aspect and any possible design thereof, or the electronic device executes the method described in the second aspect and any possible design thereof.

[0050] In a fourth aspect, an embodiment of the present application provides a chip system. The chip system includes one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected via a line. The interface circuit is used to receive signals from the memory of the electronic device and send signals to the processor. The signals include computer instructions stored in the memory. When the processor executes the computer instructions, the electronic device executes the method described in the first aspect and any possible design thereof, or causes the electronic device to execute the method described in the second aspect and any possible design thereof.

[0051] In a fifth aspect, embodiments of the present application provide a computer storage medium comprising computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the method described in the first aspect and any possible design thereof, or the electronic device executes the method described in the second aspect and any possible design thereof.

[0052] In a sixth aspect, embodiments of the present application provide a computer program product. When the computer program product is executed on a computer, the computer is caused to execute the method described in the first aspect and any possible design thereof, or the electronic device is caused to execute the method described in the second aspect and any possible design thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] FIG1 is a schematic structural diagram of an Internet of Things system provided by the prior art;

[0054] FIG2 is a schematic diagram of an interface for setting a do not disturb mode provided by the prior art;

[0055] FIG3 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application;

[0056] FIG4A is a schematic diagram of an interface of an application program for setting an authorization scope of a second device provided in an embodiment of the present application;

[0057] FIG4B is a schematic diagram of an interface including a first device list provided in an embodiment of the present application;

[0058] FIG5 is a schematic diagram of a first interface provided in an embodiment of the present application;

[0059] FIG6 is a schematic diagram of a first interface including a second device list provided in an embodiment of the present application;

[0060] FIG7 is a schematic diagram of a first interface including an account list provided in an embodiment of the present application;

[0061] FIG8 is a schematic diagram of a second interface including an account list provided in an embodiment of the present application;

[0062] FIG9 is a schematic diagram of a second interface including a second device list provided in an embodiment of the present application;

[0063] FIG10 is a schematic diagram of a third interface including an account list provided in an embodiment of the present application;

[0064] FIG11 is a schematic diagram of a first interface including input controls provided in an embodiment of the present application;

[0065] FIG12 is a schematic diagram of an interface including a third device list provided in an embodiment of the present application;

[0066] FIG13 is a schematic diagram of a second interface including input controls provided in an embodiment of the present application;

[0067] FIG14 is a schematic diagram of an interactive interface provided in an embodiment of the present application;

[0068] FIG15 is a schematic diagram of an Internet of Things system provided by an embodiment of the present application;

[0069] FIG16 is a flowchart of a rights management method provided in an embodiment of the present application;

[0070] FIG17 is a schematic diagram of interaction between a user and an Internet of Things system according to an embodiment of the present application;

[0071] FIG18 is a structural diagram of another electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0072] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships can exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

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

[0074] Figure 1 shows a schematic diagram of an IoT system. The IoT system includes device 101, device 102, and server 103. Devices 101 and 102 are both connected to server 103. Device 101 is bound to IoT device 104, which has interactive features such as audio calls, video calls, and messaging.

[0075] Because IoT device 104 is bound to device 101, device 101 can obtain device information about IoT device 104. Furthermore, because device 101 is connected to server 103, server 103 can obtain device information about IoT device 104 from device 101. Furthermore, device 102, which is connected to server 103, can also obtain device information about IoT device 104 from the server. Furthermore, device 102 can request interaction with IoT device 104 based on the obtained device information. For example, device 102 can initiate audio calls, video calls, and messaging chats with IoT device 104.

[0076] However, because device 102 can freely access the device information of IoT device 104 through server 103 and interact with it, IoT device 104 may receive a large number of unexpected interaction messages. For example, IoT device 104 may receive a large number of advertising messages sent by device 102, increasing the risk of privacy leakage for the owner of IoT device 104.

[0077] In a related technology, an electronic device can control a bound IoT device to enter Do Not Disturb mode. Referring to Figure 2 , device 200 is bound to a speaker. The settings interface 201 displayed by device 200 includes a control 202 for controlling whether the speaker is in Do Not Disturb mode.

[0078] When the speaker is not in Do Not Disturb mode, the user can click or select control 202. In response to the user clicking or selecting control 202, device 200 controls the speaker to activate Do Not Disturb mode. When speaker 210 is in Do Not Disturb mode, only electronic devices logged in by associated accounts that have a friend relationship with the user account logged in on device 200 can obtain the speaker's device information and initiate interactions with the speaker. Electronic devices logged in by unassociated accounts that do not have a friend relationship with the user account logged in on device 200 will not be able to obtain the speaker's device information or initiate interactions with the speaker.

[0079] However, device 200 can only restrict electronic devices logged in by non-associated accounts from obtaining device information of the speaker and initiating interactions with the speaker through the above method, while electronic devices logged in by associated accounts can still obtain device information of the speaker and initiate interactions with the speaker, increasing the risk of privacy leakage of the speaker owner.

[0080] Based on the above problems, an embodiment of the present application provides a permission management method, which can open the device information of the IoT device bound to the electronic device only to designated electronic devices and / or one or more electronic devices logged in by a designated user account for viewing, thereby reducing the risk of privacy leakage of the electronic device owner.

[0081] The electronic device in the embodiments of the present application can be a portable computer (such as a mobile phone, a foldable screen mobile phone), a tablet computer, a laptop computer, a personal computer (PC), a wearable electronic device (such as a smart watch), an augmented reality (AR) / virtual reality (VR) device, an in-vehicle computer, etc. The following embodiments do not impose any special restrictions on the specific form of the electronic device.

[0082] The operating system installed in the electronic device provided in the embodiment of the present application includes but is not limited to Or other operating systems. Of course, the electronic device provided in the embodiments of the present application may not be installed with an operating system. This application does not limit the specific type of electronic device, whether an operating system is installed, or the type of operating system if an operating system is installed.

[0083] FIG3 shows a schematic structural diagram of the electronic device 100 .

[0084] The 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 speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

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

[0086] 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 memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0087] The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

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

[0089] In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit

[0090] (inter-integrated circuit, I2C) interface, integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, pulse code modulation (pulse code modulation, PCM) interface, universal asynchronous receiver / transmitter (universal asynchronous receiver / transmitter, UART) interface, mobile industry processor interface (mobile industry processor interface, MIPI), general-purpose input / output (general-purpose input / output, GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface, and / or universal serial bus (universal serial bus, USB) interface, etc.

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

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

[0093] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 100. The mobile communication module 150 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc.

[0094] The mobile communication module 150 can receive electromagnetic waves via antenna 1, filter, amplify, and perform other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be provided in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be provided in the same device as at least some of the modules of the processor 110.

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

[0096] The wireless communication module 160 can provide wireless communication solutions for application on the electronic device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication technology (NFC), infrared technology (IR), etc.

[0097] Wireless communication module 160 can be one or more devices that integrate at least one communication processing module. Wireless communication module 160 receives electromagnetic waves via antenna 2, frequency-modulates and filters the electromagnetic wave signals, and transmits the processed signals to processor 110. Wireless communication module 160 can also receive signals to be transmitted from processor 110, frequency-modulate and amplify them, and then convert them into electromagnetic waves for radiation via antenna 2.

[0098] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150 , and antenna 2 is coupled to wireless communication module 160 , so that electronic device 100 can communicate with the network and other devices through wireless communication technology.

[0099] The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS) and / or satellite based augmentation system (SBAS).

[0100] Exemplarily, the electronic device can access the Internet of Things through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, and interact with other electronic devices connected to the same Internet of Things.

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

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

[0103] Exemplarily, the display screen 194 may display an interface for setting the authorization range of the IoT device bound to the electronic device (also referred to as a first interface in the embodiment of the present application). The user can input an instruction for setting the authorization range of the IoT device bound to the electronic device to the electronic device based on the first interface. After detecting the instruction input by the user for setting the authorization range of the IoT device bound to the electronic device, the processor 110 may set the authorization range of the IoT device bound to the electronic device to the target range in response to the instruction.

[0104] The electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

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

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

[0107] For example, the electronic device can display the screen of a video call with other electronic devices connected to the same Internet of Things through the GPU, the display screen 194, and the application processor.

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

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

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

[0111] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function.

[0112] For example, music, video, and other files can be stored on an external storage card. Another example is storing the account information of a user account logged into an electronic device on an external storage card. Another example is storing the account information of accounts associated with the user account logged into the electronic device on an external storage card. Another example is maintaining the authorization scope of an IoT device bound to the electronic device on an external storage card.

[0113] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 can include a program storage area and a data storage area.

[0114] Among them, the program storage area can store the operating system, at least one application required for a function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. The data storage area can also store the account information of the user account logged in to the electronic device. The data storage area can also store the account information of the account associated with the user account logged in to the electronic device. The data storage area can also store the authorization scope of the IoT device bound to the electronic device, etc.

[0115] In addition, the internal memory 121 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0116] The electronic device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor, such as music playback, recording, and voice calls with other electronic devices connected to the same Internet of Things.

[0117] For example, the technical solutions involved in the following embodiments can all be implemented in electronic devices having the above hardware architecture. The following describes in detail the rights management method provided by the embodiments of the present application in conjunction with the accompanying drawings and application scenarios.

[0118] The rights management method provided in the embodiment of the present application can be applied to an Internet of Things system, which includes a server for data storage and management. An electronic device can join the Internet of Things system by connecting to the server.

[0119] In some embodiments, after an electronic device is connected to a server, a user account corresponding to the user's identity information can be logged into the server. A user account is an identifier used to represent the user's identity information. For example, the user account can be a user's mobile phone number, an email address, or a user-defined string, etc., although this embodiment of the present application is not limiting.

[0120] Each user account corresponds to a portion of storage space on the server. After an electronic device logs in to the user account corresponding to the user's identity information on the server, it can send relevant information about the electronic device to the server. Based on the user account logged in by the electronic device, the server can store the relevant information about the electronic device in the storage space corresponding to the user account.

[0121] The relevant information of the electronic device may include device information of the electronic device, device information of the IoT device bound to the electronic device, account information of the user account logged into the electronic device, recent contact information of the user account logged into the electronic device, etc. The device information of the IoT device bound to the electronic device may include the device identifier of the IoT device bound to the electronic device, the interaction capability of the IoT device bound to the electronic device (for example, whether voice calls can be made), etc., which is not limited in the embodiments of the present application.

[0122] In some embodiments, a user may have multiple electronic devices, and each electronic device may be bound to multiple IoT devices. Multiple electronic devices may log in to the same user account on the server in the IoT system. For example, user A has both a mobile phone and a tablet. Both the mobile phone and the tablet can be bound to user A's speakers, smart screens, smart speakers, and learning smart screens and other IoT devices. Both user A's mobile phone and tablet can log in to the user account that represents user A's identity on the server in the IoT system. User A can control user A's speakers, smart screens, smart speakers, and learning smart screens and other IoT devices through the mobile phone. User A can also control user A's speakers, smart screens, smart speakers, and learning smart screens and other IoT devices through the tablet.

[0123] In the embodiment of the present application, any electronic device at a control end, such as a mobile phone or a tablet computer, can be referred to as a first device. An IoT device such as a speaker, a smart screen, an intelligent speaker, and a learning smart screen that is bound to the first device is referred to as a second device. A wired communication connection can be used between the first device and the second device, or a wireless communication connection (for example, a Bluetooth connection, a local area network connection, etc.) can be used between the first device and the second device, which is not limited in the embodiment of the present application.

[0124] In some embodiments, since each second device is bound to the first device, the first device can obtain the device information of each second device, and each second device can also obtain the device information of other second devices from the first device. Furthermore, each second device can interact with one or more second devices corresponding to the device information obtained from the first device based on the device information obtained from the first device. For example, second device 1, second device 2, and second device 3 are all bound to the first device. Second device 1 can access and interact with second device 2, and second device 2 can also access and interact with second device 3, and so on.

[0125] In some embodiments, referring to FIG4A , an application 400 for setting an authorization scope for a second device is installed on a first device. The authorization scope for the second device refers to the scope of electronic devices that have permission to access the second device (in this embodiment of the application, it may also be referred to as the scope of electronic devices that have permission to obtain device information of the second device).

[0126] For example, if only device A has permission to obtain the device information of a second device, the second device's authorization scope is device A. If device A and the first device are connected to the same IoT system, device A can obtain the device information of the second device bound to the first device and interact with the second device. For another example, if both device A and device B have permission to obtain the device information of the second device, the second device's authorization scope is device A and device B. If device A, device B, and the first device are connected to the same IoT system, both device A and device B can obtain the device information of the second device bound to the first device and interact with the second device.

[0127] In some embodiments, the first device may log in to a user account corresponding to the user's identity information on the server based on a request from the application 400. After successful login, the first device and the second device may interact with any electronic device in the IoT system.

[0128] For example, referring to FIG4A , after the first device detects that the user has clicked or selected application 400, it may display a login interface. The user may enter a user account (e.g., a first user account) or the first user account and the password corresponding to the first user account on the login interface to input a login instruction to the first device requesting login to the first user account on the server. After the first device detects the login instruction input by the user, it requests login to the first user account on the server based on the content input by the user on the login interface.

[0129] After successful login, the first device can send relevant information of the first device to the server. After the server receives the relevant information of the first device, it can store the relevant information of the first device in the storage space corresponding to the first user account. Any electronic device in the Internet of Things system can obtain relevant information of the first device from the storage space corresponding to the first user account on the server, thereby initiating interaction with the second device bound to the first device based on the relevant information of the first device. Among them, the relevant information of the first device can be found in the description of the aforementioned embodiment, which will not be repeated here.

[0130] In some embodiments, since each second device is bound to the first device and the first device is logged in with the first user account, other electronic devices logged in with the first user account (which may also be referred to as third devices in the embodiments of the present application, and the third device is different from the first device) can also access the second device bound to the first device through the server and interact with it. For example, the second device 1 and the second device 2 are both bound to the first device. The first device and the third device are both logged in with the first user account in the server, so the third device can access the second device 1 or the second device 2 through the server and interact with it.

[0131] In some embodiments, after the first device logs in to the first user account, a first device list may be displayed. The first device list includes the device identifiers of the second devices bound to the first device. For example, referring to FIG4B , the first device list 410 displayed by the first device includes the device identifier 411 of the speaker, the device identifier 412 of the smart screen, the device identifier 413 of the smart speaker, and the device identifier 414 of the learning smart screen.

[0132] In some embodiments, the user can set an authorization scope for at least one second device based on the first device list.

[0133] For example, referring to Figure 4B , the user can click or select the identifier 411 corresponding to the speaker. In response to the user clicking or selecting the identifier 411 corresponding to the speaker, the first device may display an interface for setting the authorization scope of the speaker. For another example, the user can click or select the identifier 411 corresponding to the speaker and the identifier 412 corresponding to the smart screen. In response to the user clicking or selecting the identifier 411 corresponding to the speaker and the identifier 412 corresponding to the smart screen, the first device may display an interface for setting the authorization scope of the speaker and the smart screen.

[0134] In the embodiment of the present application, the second device for which the user sets the authorization scope through the first device can also be referred to as the first target device, and the first target device is bound to the first device. The following description of the permission management method provided in the embodiment of the present application continues by taking the case where the first device detects a user clicking or selecting an identifier corresponding to the first target device and displays an interface for setting the authorization scope for the first target device (also referred to as the first interface in the embodiment of the present application) as an example.

[0135] In some embodiments, a user may input a first instruction in a first interface displayed by a first device. The first instruction is used to instruct the first device to set the device information of the first target device to be visible to electronic devices logged in with some user accounts. In response to the first instruction input by the user, the first device may obtain and display an account list. The account list includes at least one user account that is associated with the first user account. For example, the user account is in the contact list of the first user account. That is, the first user account has interacted with the user account. For another example, there is a friend relationship between the user account and the first user account, etc., which is not limited in the embodiments of the present application.

[0136] The first device may request the server to obtain the account list. The first device may also directly call the historically stored account list, which is not limited in the embodiment of the present application.

[0137] In some embodiments, after the first device displays an account list in response to a first instruction input by a user, the user can click or select at least one account identifier in the account list to select a second user account, the second user account corresponding to the account identifier selected by the user. In response to the user clicking or selecting the account identifier of the second user account, the first device can set the device information of the first target device to be visible to electronic devices logged in with the second user account.

[0138] That is to say, the first device can set the authorization scope of the first target device in the account dimension, and can limit electronic devices that are not logged in to the second user account from obtaining the device information of the first target device and interacting with the first target device, which can reduce the number of unexpected interaction messages received by the first device and greatly protect the user's privacy.

[0139] For example, after determining the first target device, the first device may display a first interface 500 as shown in FIG5 . The first interface includes a control 501 for setting the device information of the first target device to be visible to certain user accounts. The user may input a first instruction to the first device by clicking control 501. In response to the first instruction input by the user, the first device may display an account list 510.

[0140] Account list 510 includes multiple account identifiers of user accounts associated with the first user account (e.g., account identifier 511 corresponding to account 1, account identifier 512 corresponding to account 2, account identifier 513 corresponding to account 3, etc.). The user can click or select account identifiers 511 and 512 to select account 1 and account 2 as the second user account. After the first device detects the user's click or selection of account identifiers 511 and 512, it can set the device information of the first target device to be visible to electronic devices logged in to account 1 or account 2.

[0141] In some embodiments, after a first device sets the device information of a first target device to be visible to an electronic device logged in with a second user account, it may generate first information. The first information indicates that the device information of the first target device is visible to the electronic device logged in with the second user account. The first device may send the first information to a server. After receiving the first information, the server may manage the electronic devices in the IoT system based on the first information.

[0142] For example, when the server receives the first information, if an electronic device logged in with a second user account requests the server to obtain the device information of the first target device, the server can determine based on the first information that the electronic device logged in with the second user account is within the authorized range of the first target device. Therefore, the server can allow the electronic device logged in with the second user account to obtain the device information of the first target device.

[0143] For another example, when the server receives the first information, if an electronic device that is not logged into the second user account requests the server to obtain the device information of the first target device, the server can determine based on the first information that the electronic device that is not logged into the second user account is outside the authorized range of the first target device. Therefore, the server can prohibit the electronic device that is not logged into the second user account from obtaining the device information of the first target device.

[0144] In some embodiments, after the first device displays the account list in response to the first instruction input by the user, the user can click or select at least one account identifier in the account list to select a second user account, wherein the second user account corresponds to the account identifier selected by the user.

[0145] In response to a user clicking or selecting the account identifier of a second user account, the first device may request from the server the device identifiers of electronic devices logged into the second user account. After the server sends the device identifiers of the electronic devices logged into the second user account to the first device, the first device may display a second device list in response to receiving the device identifiers of the electronic devices sent by the server. The second device list includes the device identifiers of the electronic devices logged into the second user account.

[0146] The user can click or select at least one device identifier in the second device list. The electronic device corresponding to the device identifier selected by the user in the second device list can also be referred to as a second target device. After the first device detects the user's click or selection of the device identifier of the second target device, the device information of the first target device can be set to be visible to the second target device logged in with the second user account.

[0147] That is to say, the first device can set the authorization scope of the first target device in the device dimension, and can limit the second target device that has not logged in to the second user account to obtain the device information of the first target device and interact with the first target device, which can reduce the number of unexpected interaction messages received by the first device and greatly protect the user's privacy.

[0148] For example, referring to Figure 5 , after the first device detects that the user has clicked or selected account identifier 511 corresponding to Account 1 and account identifier 512 corresponding to Account 2, it may request the server to obtain the device identifiers of the electronic devices logged in to Account 1 and Account 2. In response to receiving the device identifiers sent by the server, the first device may display a second device list 600 as shown in Figure 6 .

[0149] The second device list 600 may include a device identifier 601 corresponding to device A logged in with account 1, a device identifier 602 corresponding to device B, and a device identifier 603 corresponding to device C, as well as a device identifier 604 corresponding to device D logged in with account 2, a device identifier 605 corresponding to device E, and so on. The user can click or select device identifiers 601 and 604. After the first device detects the user's click or selection of device identifiers 601 and 604, it may set the device information of the first target device to be visible to device A logged in with account 1 and device D logged in with account 2.

[0150] In some embodiments, after a first device sets the device information of a first target device to be visible to a second target device logged in with a second user account, it may generate second information. The second information indicates that the device information of the first target device is visible to the second target device logged in with the second user account. The first device may send the second information to a server. After receiving the second information, the server may manage various electronic devices in the IoT system based on the second information.

[0151] For example, when the server receives the second information, if a second target device logged in with a second user account requests the server to obtain the device information of the first target device, the server can determine based on the second information that the second target device logged in with the second user account is within the authorized range of the first target device. Therefore, the server can allow the second target device logged in with the second user account to obtain the device information of the first target device.

[0152] For another example, when the server receives the second information, if a second target device that is not logged into the second user account requests the server to obtain the device information of the first target device, the server can determine based on the second information that the second target device that is not logged into the second user account is outside the authorization range of the first target device. Therefore, the server can prohibit the second target device that is not logged into the second user account from obtaining the device information of the first target device.

[0153] Optionally, referring to Figure 7, in response to the first instruction input by the user, the first device displays an account list that also includes a control 701 for setting the device information of the first target device to be visible to all electronic devices logged in to the second user account, and a control 702 for setting the device information of the first target device to be visible to some electronic devices logged in to the second user account.

[0154] If the first device detects a user clicking or selecting control 701, it can set the device information of the first target device to be visible to the electronic device logged in with the second user account, as described in the previous embodiment. If the first device detects a user clicking or selecting control 702, it can display the second device list 600 shown in Figure 6 above. The user can click or select the second target device in the second device list 600 to set the device information of the first target device to be visible to the second target device logged in with the second user account.

[0155] In some embodiments, a user may enter a second instruction in a first interface displayed on a first device. The second instruction is used to instruct the first device to disable the device information of the first target device from being visible to electronic devices logged into certain user accounts. In response to the second instruction entered by the user, the first device may obtain and display an account list. The account list includes at least one user account associated with the first user account. The description of the user accounts associated with the first user account can be found in the aforementioned embodiments and is not further elaborated here.

[0156] In some embodiments, after the first device displays the account list in response to the second instruction input by the user, the user can click or select at least one account identifier in the account list to select a third user account, where the third user account corresponds to the account identifier selected by the user. In response to the user clicking or selecting the account identifier of the third user account, the first device can set the device information of the first target device to be invisible to the electronic device logged in with the third user account.

[0157] In other words, the first device can set the authorization scope of the first target device based on the account dimension, and can restrict electronic devices logged in with the third user account from obtaining the device information of the first target device and interacting with the first target device. That is, all electronic devices logged in with the third user account cannot obtain the device information of the first target device or interact with the first target device. This can reduce the number of unwanted interaction messages received by the first device and greatly protect the user's privacy.

[0158] For example, after the first device determines the first target device, it may display a first interface 500 as shown in FIG5 . The first interface includes a control 502 for setting the device information of the first target device to be invisible to electronic devices logged in with some user accounts. The user may input a second instruction to the first device by clicking control 502. In response to the second instruction input by the user, the first device may display an account list 800 as shown in FIG8 .

[0159] Among them, account list 800 includes multiple account identifiers of user accounts associated with the first user account (for example, account identifier 801 corresponding to account 10, account identifier 802 corresponding to account 20, account identifier 803 corresponding to account 30, etc.). The user can click or select account identifier 801 and account identifier 802 to select account 10 and account 20 as the third user account. After the first device detects the user's click or selection operation on account identifier 801 and account identifier 802, it can set the device information of the first target device to be invisible to the electronic device logged in with account 10 or account 20.

[0160] In some embodiments, after the first device sets the device information of the first target device to be invisible to electronic devices logged in with a third user account, it may generate third information. The third information is used to indicate that the device information of the first target device is invisible to electronic devices logged in with the third user account. The first device may send the third information to a server. After receiving the third information, the server may manage the electronic devices in the IoT system based on the third information.

[0161] For example, if the server receives the third information and an electronic device logged in with a third user account requests the server to obtain the device information of the first target device, the server can determine based on the first information that the electronic device logged in with the third user account is outside the authorized range of the first target device. Therefore, the server can prohibit the electronic device logged in with the third user account from obtaining the device information of the first target device.

[0162] For another example, when the server receives the third information, if an electronic device that is not logged into the third user account requests the server to obtain the device information of the first target device, the server can determine based on the third information that the electronic device that is not logged into the third user account is within the authorized range of the first target device. Therefore, the server can allow the electronic device that is not logged into the third user account to obtain the device information of the first target device.

[0163] In some embodiments, after the first device displays the account list in response to the second instruction input by the user, the user can click or select at least one account identifier in the account list to select the third user account.

[0164] The third user account corresponds to the account identifier selected by the user. In response to the user clicking or selecting the account identifier of the third user account, the first device may request from the server the identifier of the electronic device logged in to the third user account. After the server sends the device identifier of the electronic device logged in to the third user account to the first device, the first device may display a third device list in response to receiving the device identifier of the electronic device sent by the server. The third device list includes the device identifiers of the electronic devices logged in to the third user account.

[0165] The user can click or select at least one device identifier in the third device list. The electronic device corresponding to the device identifier selected by the user in the third device list can also be referred to as a third target device. After the first device detects the user's click or selection of the device identifier of the third target device, the device information of the first target device can be set to be invisible to the third target device logged in with the third user account.

[0166] In other words, the first device can set the authorization scope of the first target device at the device level, restricting third target devices logged in with third user accounts from accessing the device information of the first target device and interacting with the first target device. This can reduce the number of unwanted interaction messages received by the first device, greatly protecting the user's privacy.

[0167] For example, referring to Figure 8 , after the first device detects that the user has clicked or selected account identifier 801 corresponding to account 10 and account identifier 802 corresponding to account 20, it can request the server to obtain the device identifiers of the electronic devices logged in to account 10 and account 20. In response to receiving the device identifiers sent by the server, the first device can display a third device list 900 as shown in Figure 9 .

[0168] The third device list 900 may include device identifiers 901 corresponding to device G logged in with account 10, device identifiers 902 corresponding to device H, and device identifiers 903 corresponding to device I, as well as device identifiers 904 corresponding to device J logged in with account 30, and device identifiers 905 corresponding to device K. The user can click or select device identifiers 901 and 905. After the first device detects the user's click or selection of device identifiers 901 and 905, it may set the device information of the first target device to be invisible to device G logged in with account 10 and device K logged in with account 20.

[0169] In some embodiments, after the first device sets the device information of the first target device to be invisible to a third target device logged in with a third user account, it may generate fourth information. The fourth information indicates that the device information of the first target device is invisible to the third target device logged in with the third user account. The first device may send the fourth information to a server. After receiving the fourth information, the server may manage various electronic devices in the IoT system based on the fourth information.

[0170] For example, when the server receives the fourth information, if a third target device logged in with a third user account requests the server to obtain the device information of the first target device, the server can determine based on the fourth information that the third target device logged in with the third user account is outside the authorized range of the first target device. Therefore, the server can prohibit the third target device logged in with the third user account from obtaining the device information of the first target device.

[0171] For another example, when the server receives the fourth information, if a third target device that is not logged into the third user account requests the server to obtain the device information of the first target device, the server can determine based on the fourth information that the third target device that is not logged into the third user account is within the authorization range of the first target device. Therefore, the server can allow the third target device that is not logged into the third user account to obtain the device information of the first target device.

[0172] Optionally, referring to Figure 10, in response to the second instruction input by the user, the first device displays an account list that also includes a control 1001 for setting that the device information of the first target device is invisible to all electronic devices logged in to the third user account, and a control 1002 for setting that the device information of the first target device is invisible to some electronic devices logged in to the third user account.

[0173] If the first device detects a user clicking or selecting control 1001, it can, as described in the previous embodiment, hide the device information of the first target device from all electronic devices logged into the third user account. If the first device detects a user clicking or selecting control 1002, it can display the third device list 900 shown in FIG. 9 . The user can click or select a third target device in the third device list 900 to hide the device information of the first target device from the third target device logged into the third user account.

[0174] In some embodiments, a user may enter a third instruction in the first interface displayed by the first device. The third instruction is used to instruct the first device to set the device information of the first target device to be visible only to electronic devices logged in with the first user account. In response to the third instruction entered by the user, the first device may set the device information of the first target device to be visible only to electronic devices logged in with the first user account. In other words, only electronic devices logged in with the first user account can obtain the device information of the first target device and interact with the first target device.

[0175] In other words, the first device can set the authorization scope of the first target device based on the account dimension, and can restrict electronic devices that are not logged into the first user account from obtaining the device information of the first target device and interacting with the first target device. This can reduce the number of unwanted interaction messages received by the first device and greatly protect the user's privacy.

[0176] For example, after the first device determines the first target device, it may display a first interface 500 as shown in FIG5 . First interface 500 includes a control 503 for setting the device information of the first target device to be visible to electronic devices logged in with the first user account. The user may input a third instruction to the first device by clicking control 503. In response to the third instruction input by the user, the first device may set the device information of the first target device to be visible to electronic devices logged in with the first user account.

[0177] In some embodiments, after the first device sets the device information of the first target device to be visible to electronic devices logged in to the first user account, it may generate fifth information. The fifth information is used to indicate that the device information of the first target device is visible to electronic devices logged in to the first user account. The first device may send the fifth information to a server. After receiving the fifth information, the server may manage various electronic devices in the Internet of Things system based on the fifth information.

[0178] For example, when the server receives the fifth information, if an electronic device logged in with the first user account requests the server to obtain the device information of the first target device, the server can determine based on the fifth information that the electronic device logged in with the first user account is within the authorized range of the first target device. Therefore, the server can allow the electronic device logged in with the first user account to obtain the device information of the first target device.

[0179] For another example, when the server receives the fifth information, if an electronic device that is not logged into the first user account requests the server to obtain the device information of the first target device, the server can determine based on the fifth information that the electronic device that is not logged into the first user account is outside the authorized range of the first target device. Therefore, the server can prohibit the electronic device that is not logged into the first user account from obtaining the device information of the first target device.

[0180] In some embodiments, a user may input a fourth instruction to the first device. The fourth instruction is used to instruct the first device to set the device information of the first target device to be invisible to electronic devices logged in with a third user account. In response to the fourth instruction input by the user, the first device may display an input control. After detecting the content input by the user in the input control, the first device may determine that the content input by the user in the input control is from the third user account and set the device information of the first target device to be invisible to electronic devices logged in with the third user account.

[0181] In other words, the first device can set the authorization scope of the first target device based on the account dimension. Even if the third user account is not a user account associated with the first user account, the first device can restrict electronic devices logged in with the third user account from obtaining the device information of the first target device and interacting with the first target device. In other words, all electronic devices logged in with the third user account cannot obtain the device information of the first target device or interact with the first target device. This can reduce the number of unwanted interaction messages received by the first device and greatly protect the user's privacy.

[0182] Exemplarily, after the first device determines the first target device, it may display a first interface 500 as shown in FIG5 . The first interface 500 includes a control 504 for setting the device information of the first target device to be invisible to electronic devices logged in with a third user account. The user may input a fourth instruction to the first device by clicking the control 504. In response to the fourth instruction input by the user, the first device may display an input control 1101 as shown in FIG11 . After the first device detects the content "xxxx.xx" entered by the user in the input control, it may determine "xxxx.xx" as the third user account and set the device information of the first target device to be invisible to electronic devices logged in with the "xxxx.xx" account.

[0183] In some embodiments, after the first device sets the device information of the first target device to be invisible to electronic devices logged in with a third user account, sixth information may be generated. The sixth information indicates that the device information of the first target device is invisible to electronic devices logged in with the third user account. The first device may send the sixth information to a server. After receiving the sixth information, the server may manage the electronic devices in the IoT system based on the sixth information.

[0184] For example, if the server receives the sixth information and an electronic device logged in with a third user account requests the server to obtain the device information of the first target device, the server can determine based on the sixth information that the electronic device logged in with the third user account is outside the authorized range of the first target device. Therefore, the server can prohibit the electronic device logged in with the third user account from obtaining the device information of the first target device.

[0185] For another example, when the server receives the sixth information, if an electronic device that is not logged into the third user account requests the server to obtain the device information of the first target device, the server can determine based on the sixth information that the electronic device that is not logged into the third user account is within the authorized range of the first target device. Therefore, the server can allow the electronic device that is not logged into the third user account to obtain the device information of the first target device.

[0186] In some embodiments, after the first device detects content input by the user in the input control and determines that the content input by the user in the input control is a third user account, it can also request from the server to obtain the device identification of the electronic device logged in to the third user account. After the server sends the device identification of the electronic device logged in to the third user account to the first device, the first device can display the third device list in response to receiving the device identification of the electronic device sent by the server.

[0187] The third device list includes device identifiers of electronic devices logged in with a third user account. The user can click or select at least one device identifier in the third device list to select a third target device. The third target device is the electronic device corresponding to the device identifier selected by the user in the third device list. After the first device detects the user clicking or selecting the device identifier of the third target device, the device information of the first target device can be set to be invisible to the third target device logged in with the third user account.

[0188] In other words, the first device can set the authorization scope for the first target device at the device level. Even if the third user account is not associated with the first user account, the first device can restrict the third target device logged in with the third user account from obtaining the device information of the first target device and interacting with the first target device. This can reduce the number of unwanted interaction messages received by the first device, greatly protecting the user's privacy.

[0189] Exemplarily, referring to Figure 11, after the first device detects the content "xxxx.xx" entered by the user in the input control 1101 and determines "xxxx.xx" as the third user account, it can also display the third device list 1201 as shown in Figure 12. The third device list 1201 includes the device identifier 1202 of the device L with the fourth user account logged in and the device identifier 1203 of the device M. The user can click or select the device identifier 1202. After the first device detects the user's click or selection operation on the device identifier 1202, it can set the device L with the account "xxxx.xx" logged in to be invisible to the device information of the first target device. That is, the device L with only the account "xxxx.xx" logged in cannot obtain the device information of the first target device and interact with the first target device.

[0190] In some embodiments, after the first device sets the device information of the first target device to be invisible to a third target device logged in with a third user account, the first device may generate seventh information. The seventh information indicates that the device information of the first target device is invisible to the third target device logged in with the third user account. The first device may send the seventh information to a server. After receiving the seventh information, the server may manage various electronic devices in the IoT system based on the seventh information.

[0191] For example, when the server receives the seventh information, if a third target device logged in with a third user account requests the server to obtain the device information of the first target device, the server can determine based on the seventh information that the third target device logged in with the third user account is outside the authorized range of the first target device. Therefore, the server can prohibit the third target device logged in with the third user account from obtaining the device information of the first target device.

[0192] For another example, when the server receives the seventh information, if a third target device that is not logged into the third user account requests the server to obtain the device information of the first target device, the server can determine based on the seventh information that the third target device that is not logged into the third user account is within the authorization range of the first target device. Therefore, the server can allow the third target device that is not logged into the third user account to obtain the device information of the first target device.

[0193] Optionally, referring to FIG13 , the interface including input controls displayed by the first device further includes a control 1301 for setting the device information of the first target device to be invisible to all electronic devices logged in with the third user account, and a control 1302 for setting the device information of the first target device to be invisible to some electronic devices logged in with the third user account. If the first device detects a user click or selection operation on control 1301, the device information of the first target device may be set to be invisible to all electronic devices logged in with the third user account, as described in the aforementioned embodiment.

[0194] If the first device detects a user click or selection operation on control 1302, it can display the third device list 1201 shown in Figure 12. The user can click or select a third target device in the third device list 1201 to set the third target device logged in with the third user account to not be able to see the device information of the first target device.

[0195] In some embodiments, a user may input a fifth instruction to the first device. The fifth instruction is used to instruct the first device to set the device information of the electronic device logged in with the second user account to be visible to the first target device. In response to the fifth instruction input by the user, the first device may display an input control. After detecting the content input by the user in the input control, the first device may determine the content input by the user in the input control as belonging to the second user account and set the device information of the electronic device logged in with the second user account to be visible to the first target device.

[0196] That is to say, the first device can set the authorization scope of the first target device in the account dimension. Even if the second user account is not a user account associated with the first user account, the first device can allow the electronic device logged in with the second user account to obtain the device information of the first target device and interact with the first target device, that is, all electronic devices logged in with the second user account can obtain the device information of the first target device and interact with the first target device.

[0197] In some embodiments, after the first device sets the device information of the first target device to be visible to the electronic device logged in with the second user account, the first device may generate eighth information. The eighth information indicates that the device information of the first target device is visible to the electronic device logged in with the second user account. The first device may send the eighth information to the server. After receiving the eighth information, the server may manage the electronic devices in the IoT system based on the eighth information.

[0198] For example, when the server receives the eighth information, if an electronic device logged in with the second user account requests the server to obtain the device information of the first target device, the server can determine based on the eighth information that the electronic device logged in with the second user account is within the authorized range of the first target device. Therefore, the server can allow the electronic device logged in with the second user account to obtain the device information of the first target device.

[0199] For another example, when the server receives the eighth information, if an electronic device that is not logged into the second user account requests the server to obtain the device information of the first target device, the server can determine based on the eighth information that the electronic device that is not logged into the second user account is outside the authorized range of the first target device. Therefore, the server can restrict the electronic device that is not logged into the second user account from obtaining the device information of the first target device.

[0200] In some embodiments, after the first device detects content input by the user in the input control and determines the content input by the user in the input control as a second user account, it may also request from the server to obtain the device identification of the electronic device logged in with the second user account. After the server sends the device identification of the electronic device logged in with the second user account to the first device, the first device may display the second device list in response to receiving the device identification of the electronic device sent by the server.

[0201] The second device list includes device identifiers of electronic devices logged in with the second user account. The user can click or select at least one device identifier in the second device list to select a second target device. The second target device is the electronic device corresponding to the device identifier selected by the user in the second device list. After the first device detects the user clicking or selecting the device identifier of the second target device, the second target device logged in with the second user account can be set to be visible to the device information of the first target device.

[0202] That is to say, the first device can set the authorization scope of the first target device in the device dimension. Even if the second user account is not a user account associated with the first user account, the first device can allow the second target device logged in with the second user account to obtain the device information of the first target device and interact with the first target device.

[0203] In some embodiments, after the first device sets the device information of the first target device to be visible to the second target device logged in with the second user account, ninth information may be generated. The ninth information indicates that the device information of the first target device is visible to the second target device logged in with the second user account. The first device may send the ninth information to a server. After receiving the ninth information, the server may manage the electronic devices in the IoT system based on the ninth information.

[0204] For example, when the server receives the ninth information, if a second target device logged in with a second user account requests the server to obtain the device information of the first target device, the server can determine based on the ninth information that the second target device logged in with the second user account is within the authorized range of the first target device. Therefore, the server can allow the second target device logged in with the second user account to obtain the device information of the first target device.

[0205] For another example, when the server receives the ninth information, if a second target device that is not logged into the second user account requests the server to obtain the device information of the first target device, the server can determine based on the ninth information that the second target device that is not logged into the second user account is outside the authorization range of the first target device. Therefore, the server can restrict the second target device that is not logged into the second user account from obtaining the device information of the first target device.

[0206] Optionally, the interface including input controls displayed by the first device further includes a control for setting that all electronic devices logged in to the second user account are visible to the device information of the first target device, and a control for setting that some electronic devices logged in to the second user account are visible to the device information of the first target device. If the first device detects that the user clicks or selects the control for setting that all electronic devices logged in to the second user account are visible to the device information of the first target device, the device can set that all electronic devices logged in to the second user account are visible to the device information of the first target device as described in the aforementioned embodiment.

[0207] If the first device detects that the user has clicked or selected a control for setting the device information of some electronic devices logged in with the second user account to be visible to the first target device, the first device may display the second device list 1 in the above embodiment. The user may click or select the second target device in the second device list to set the device information of the second target device logged in with the second user account to be visible to the first target device.

[0208] In some embodiments, a user may input a sixth instruction to the first device. The sixth instruction instructs the first device to set the device information of the first target device to be visible to all electronic devices. In response to the sixth instruction input by the user, the first device sets the device information of the first target device to be visible to all electronic devices. This means that all electronic devices can obtain the device information of the first target device and interact with the first target device.

[0209] For example, after determining the first target device, the first device may display a first interface 500 as shown in FIG5 . The first interface includes a control 505 for setting the device information of the first target device to be visible to all electronic devices. The user may input a sixth instruction to the first device by clicking control 505. In response to the sixth instruction input by the user, the first device may set the device information of the first target device to be visible to all electronic devices.

[0210] In some embodiments, after the first device sets the device information of the first target device to be visible to all electronic devices, it may generate tenth information. The tenth information is used to indicate that the device information of the first target device is visible to all electronic devices. The first device may send the tenth information to a server. After receiving the tenth information, the server may manage each electronic device in the IoT system based on the tenth information.

[0211] Since the tenth information is used to represent the device information of the first target device and is visible to all electronic devices, when the server receives the tenth information, the server can determine based on the tenth information that any electronic device requesting to obtain the device information of the first target device is within the authorized range of the first target device. Therefore, any electronic device can obtain the device information of the first target device through the server.

[0212] In some embodiments, the first target device can also be bound to a third device. The third device can also be a control-end electronic device such as a mobile phone or tablet. The third device and the first device are logged in with the same user account, namely the first user account, but the third device is different from the first device. For example, the first device can be a mobile phone, the third device can be a tablet, and the second device can be a speaker. The mobile phone and tablet are logged in with the same user account, and both the mobile phone and tablet are bound to the speaker.

[0213] After the first device completes setting the authorization scope for the first target device and sends the setting information representing the authorization scope of the first target device (such as the first to tenth messages in the aforementioned embodiment) to the server, the server can detect whether a third device exists based on the first user account. If the server detects the presence of the third device, it can send an update instruction to the third device to instruct the third device to update the authorization scope of the first target device.

[0214] In some embodiments, after receiving the update instruction sent by the server, the third device may update the authorization scope of the first target device to synchronize the updated authorization scope of the first target device with the first device.

[0215] The following describes in detail the effects of the rights management method provided in the application embodiment in conjunction with specific scenarios.

[0216] The first device is a mobile phone, and the multiple second devices bound to the first device are speakers, smart screens, and learning smart screens.

[0217] If user A sets mobile phone A logged in with user account B on the first device to not be able to access the speaker, smart screen, and learning smart screen bound to the first device, user B will not be able to obtain the device information of the speaker, smart screen, and learning smart screen bound to the first device by logging in with mobile phone A with user account B, and will not be able to initiate interaction with the speaker, smart screen, and learning smart screen bound to the first device.

[0218] If user A sets up on the first device that mobile phone A logged in with user account B can access the speaker and smart screen bound to the first device, but cannot access the learning smart screen bound to the first device. Then user B can obtain the device information of the speaker and smart screen bound to the first device by logging in to mobile phone A with user account B, and display interface 1400 as shown in Figure 14. Interface 1400 includes the device information of the speaker and smart screen. In addition, since mobile phone A logged in with user account B does not have the authority to obtain the device information of the learning smart screen bound to the first device, the device information of the learning smart screen bound to the first device will not be displayed in interface 1400.

[0219] User B can input an operation in interface 1400 to instruct mobile phone A logged in with user account B to initiate interaction with the speaker bound to the first device. For example, user B clicks control 1401 in interface 1400 to initiate a voice call with the speaker bound to the first device.

[0220] The present application also provides an IoT system, as shown in FIG15 . The IoT system includes a first device 1501, at least one second device 1502, and a server 1503. The first device 1501 is connected to the server 1503, and each second device 1502 is connected to the first device 1501. Each second device 1502 is an IoT device bound to the first device 1501.

[0221] The first device 1501 is used to control the second device 1502 bound thereto.

[0222] For example, the first device 1501 can set the authorization scope of each second device 1502.

[0223] The server 1503 is used to store and manage relevant information of the first device 1501 .

[0224] For example, the server 1503 may store the authorization scope of the second device 1502 set by the first device 1501 .

[0225] For another example, the server may store device information of the first device 1501 and device information of the second device 1502 .

[0226] For another example, the server may store the binding relationship between the first device 1501 and each second device 1502 .

[0227] For another example, the server 1503 may restrict some electronic devices connected to the Internet of Things system from obtaining the device information of the second device 1502 based on the authorization scope of the second device 1502 .

[0228] In conjunction with Figure 16, the Internet of Things system provided in the embodiment of the present application can execute the following steps S1610-S1640 to implement the permission management method provided in the embodiment of the present application.

[0229] S1610: The first device determines at least one first target device.

[0230] The first target device includes an IoT device bound to the first device, and the first device can control the first target device. For example, the first device can set an authorization scope for the first target device.

[0231] In some embodiments, referring to FIG17 , a user may input a permission setting instruction to a first device. In response to the permission setting instruction, the first device may display a list of first devices. The permission setting instruction is used to instruct the first device to set an authorization scope for at least one second device bound to the first device. The list of first devices includes the device identifier of the at least one second device.

[0232] The first device detects a user's selection operation on at least one device identifier in the first device list and can determine at least one first target device, where the first target device is the electronic device corresponding to the device identifier selected in the first device list.

[0233] S1620: The first device sets the authorization scope of the first target device as the target scope.

[0234] In some embodiments, since the first target device is bound to the first device, if the first device has a first user account logged in to the server, other electronic devices logged in to the first user account (which may also be referred to as a third device in the embodiment of the present application, and the third device is different from the first device) can also access the first target device through the server and interact with it.

[0235] That is, the target range may indicate that electronic devices logged in with a first user account have access rights to the first target device; the first user account is a user account logged in by the first device.

[0236] For example, the first target device 1 is bound to the first device. Both the first device and the third device have a first user account logged into the server, so the third device can access the second device 1 through the server and interact with it.

[0237] In some embodiments, referring again to FIG. 17 , after the first device determines at least one first target device, it may further display a first interface for setting a target range. After receiving a first instruction input by the user based on the first interface, the first device may display an account list. The account list includes one or more account identifiers of user accounts associated with the first user account.

[0238] The first device detects that a user has selected at least one account identifier in the account list, and can determine at least one second user account, wherein the second user account is the user account corresponding to the selected account identifier in the account list.

[0239] In some embodiments, after determining at least one first target device, the first device may further display a first interface for setting a target range. After receiving a fifth instruction input by the user based on the first interface, the first device may display an input control for receiving input of a second user account.

[0240] The fifth instruction is used to instruct the first device to set the electronic device logged in with the second user account to have access rights to the first target device. The user can enter the user account in the input control. After the first device detects the content entered by the user in the input control, it determines the content entered by the user in the input control as the second user account.

[0241] In some embodiments, the first device may determine a target range based on the second user account, where the target range indicates that the first target device is visible to electronic devices logged in with the second user account.

[0242] Optionally, referring to Figure 17, after the first device determines at least one second user account, it can also send a first request to the server. The first request includes the second user account. The first request is used to request to obtain a second device list. The second device list includes the device identifiers of electronic devices logged in with the second user account. After receiving the first request, the server can obtain the second device list and send the second device list to the first device. The first device can receive and display the second device list. Afterwards, the user can select at least one device identifier in the second device list. After the first device detects the user's selection operation on at least one device identifier in the second device list, it can determine the second target device. The second target device is the electronic device corresponding to the device identifier selected in the second device list.

[0243] The first device can determine a target range based on the second user account and the second target device. The target range indicates that the second target device logged in with the second user account has access rights to the first target device.

[0244] In some embodiments, after determining at least one first target device, the first device may further display a first interface for setting a target range. After receiving a second instruction input by the user based on the first interface, the first device may display an account list. The account list includes one or more account identifiers of user accounts associated with the first user account.

[0245] The first device detects that a user has selected at least one account identifier in the account list, and can determine at least one third user account, wherein the third user account is the user account corresponding to the selected account identifier in the account list.

[0246] In some embodiments, after determining at least one first target device, the first device may further display a first interface for setting a target range. After receiving a fourth instruction input by a user based on the first interface, the first device may display an input control for receiving input from a third user account.

[0247] The fourth instruction is used to instruct the first device to deny access rights to the first target device to electronic devices logged in with a third user account. The user may enter a user account in the input control. The first device detects the user input in the input control and identifies the user input in the input control as the third user account.

[0248] In some embodiments, the first device may determine a target range based on the third user account, where the target range indicates that electronic devices logged in with the third user account do not have access rights to the first target device.

[0249] Optionally, after the first device determines at least one third user account, it may also send a second request to the server. The second request includes the third user account. The second request is used to request a third device list. The third device list includes the device identifiers of electronic devices logged in with the third user account. After receiving the second request, the server may send the third device list to the first device. The first device may receive and display the third device list. Afterwards, the user may select at least one device identifier in the third device list. After the first device detects the user's selection operation on at least one device identifier in the third device list, it may determine the third target device. The third target device is the electronic device corresponding to the device identifier selected in the third device list.

[0250] The first device may determine a target range based on the third user account and the third target device, where the target range indicates that the third target device logged in with the third user account does not have access permission to the first target device.

[0251] In some embodiments, after the first device determines at least one first target device, it may further display a first interface, where the first interface is used to set a target range. After the first device receives a third instruction input by the user based on the first interface, it may determine the target range. The third instruction is used to instruct the first device to set a setting so that only electronic devices logged in with the first user account have access rights to the first target device. Accordingly, the target range indicates that only electronic devices logged in with the first user account have access rights to the first target device.

[0252] S1630: The first device sends setting information to the server, where the setting information includes a target range. The setting information is used to instruct the server to manage access rights of electronic devices requesting access to the first target device based on the target range.

[0253] S1640: The server manages the access rights of the electronic device requesting to access the first target device based on the received setting information.

[0254] In some embodiments, continuing to refer to Figure 17, after the server receives the setting information sent by the first device, it can store the setting information in the storage space corresponding to the first user account to manage the access rights of the electronic device requesting access to the first target device based on the setting information.

[0255] In some embodiments, referring again to FIG. 17 , after receiving the setup information sent by the first device, the server may, upon detecting a third device, send an update instruction to the third device. The update instruction is used to instruct the third device to update the authorization scope of the first target device bound to the third device to the target scope. After receiving the update instruction, the third device may update the authorization scope of the first target device bound to the third device to the target scope.

[0256] In some schemes, multiple embodiments of the present application can be combined and the combined scheme can be implemented. Optionally, some operations in the process of each method embodiment are optionally combined, and / or the order of some operations is optionally changed. In addition, the execution order between the steps of each process is only exemplary and does not constitute a limitation on the execution order between the steps. There can also be other execution orders between the steps. It is not intended to indicate that the execution order is the only order in which these operations can be performed. Ordinary technicians in this field will think of many ways to reorder the operations described herein. In addition, it should be noted that the process details involved in a certain embodiment of this article are also applicable to other embodiments in a similar manner, or different embodiments can be used in combination.

[0257] Furthermore, some steps in the method embodiments may be equivalently replaced with other possible steps. Alternatively, some steps in the method embodiments may be optional and may be deleted in certain usage scenarios. Alternatively, other possible steps may be added to the method embodiments.

[0258] Furthermore, the various method embodiments may be implemented separately or in combination.

[0259] It is understandable that in order to implement the above functions, the electronic device includes hardware and / or software modules corresponding to the execution of each function. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of this application.

[0260] This embodiment can divide the electronic device into functional modules based on the above-mentioned method example. For example, each functional module can be divided according to its function, or two or more functions can be integrated into a single processing module. The above-mentioned integrated modules can be implemented in the form of hardware. It should be noted that the module division in this embodiment is illustrative and only represents a logical functional division. In actual implementation, other division methods may be used.

[0261] An embodiment of the present application also provides an electronic device, as shown in FIG18 , which may include one or more processors 1801 , a memory 1802 , and a communication interface 1803 .

[0262] The memory 1802 and the communication interface 1803 are coupled to the processor 1801. For example, the memory 1802, the communication interface 1803 and the processor 1801 may be coupled together via a bus 1804.

[0263] The communication interface 1803 is used to transmit data with other devices. The memory 1802 stores computer program code. The computer program code includes computer instructions. When the computer instructions are executed by the processor 1801, the electronic device executes the rights management method in the embodiment of the present application.

[0264] Among them, the processor 1801 can be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute the various exemplary logic blocks, modules and circuits described in conjunction with the present disclosure. The processor can also be a combination that implements computing functions, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The processor can be used to support the electronic device to execute the method steps provided in the above embodiments. For example, the processor can be used to support the electronic device to execute steps S1610-S1640 in Figure 16.

[0265] Bus 1804 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Bus 1804 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, FIG18 shows only one thick line, but this does not imply that there is only one bus or only one type of bus.

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

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

[0268] Optionally, the memory in the chip system may be one or more. The memory may be integrated with the processor or may be provided separately from the processor, which is not limited in the embodiments of the present application. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or provided on different chips. The embodiments of the present application do not specifically limit the type of memory or the configuration of the memory and the processor.

[0269] 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 processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.

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

[0271] An embodiment of the present application further provides a computer-readable storage medium, in which computer program code is stored. When the processor executes the computer program code, the electronic device executes the relevant method steps in the above method embodiment.

[0272] An embodiment of the present application further provides a computer program product, which, when executed on a computer, enables the computer to execute the relevant method steps in the above method embodiment.

[0273] In addition, embodiments of the present application further provide a device. Specifically, the device may be a component or module, and may include one or more processors and a memory connected to each other. The memory is configured to store a computer program. When the computer program is executed by one or more processors, the device performs the scenario configuration method described in each of the above method embodiments.

[0274] The apparatus, computer-readable storage medium, computer program product, or chip provided in 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 of the corresponding methods provided above, and will not be repeated here.

[0275] The steps of the method or algorithm described in conjunction with the disclosure of the embodiments of the present application can be implemented in hardware or by executing software instructions by a processor. The software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, mobile hard disks, read-only compact discs (CD-ROMs), or any other form of storage medium 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 can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC).

[0276] Through the description of the above embodiments, those skilled in the art will clearly understand that for the sake of convenience and brevity, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed; that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working processes of the above-mentioned systems, devices, and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

Claims

1. A rights management method, characterized in that: The method comprises: Determining at least one first target device, wherein the first target device is bound to the first device; Set the authorization scope of the first target device as the target scope; the target scope indicates that the electronic device logged in with the first user account has access rights to the first target device; the first user account is the user account logged in by the first device; Sending setting information to a server, the setting information including the target range; the setting information is used to instruct the server to manage access rights of an electronic device requesting to access the first target device based on the target range.

2. The method according to claim 1, characterized in that The determining of at least one first target device comprises: In response to the input permission setting instruction, displaying a first device list; the first device list includes the device identification of at least one second device bound to the first device; A selection operation of at least one of the device identifiers in the first device list is detected, and the at least one first target device is determined; the first target device includes a second device corresponding to the device identifier selected in the first device list.

3. The method according to claim 1 or 2, characterized in that: The target range also indicates that an electronic device logged into the second user account has access rights to the first target device.

4. The method according to claim 3, characterized in that The second user account includes one or more user accounts associated with the first user account; after determining at least one first target device, the method further includes: Displaying a first interface; the first interface is used to set the target range; Receiving a first instruction input based on the first interface; In response to the first instruction, displaying an account list, the account list including an account identifier of at least one user account associated with the first user account; Detecting a selection operation of at least one of the account identifiers in the account list, and determining at least one second user account; the second user account is a user account corresponding to the account identifier selected in the account list; The target range is determined based on the second user account.

5. The method according to claim 3, characterized in that: After determining at least one first target device, the method further includes: Displaying a first interface; the first interface is used to set the target range; receiving a fifth instruction input based on the first interface; In response to the fifth instruction, displaying an input control; Based on the content input in the input control, determining at least one second user account represented by the content; Based on the second user account, the target range is determined.

6. The method according to claim 4 or 5, characterized in that: The determining the target range based on the second user account includes: Sending a first request to a server, the first request including the second user account, the first request being used to request obtaining a second device list, the second device list including device identifiers of electronic devices logged in with the second user account; Display the second device list sent by the server; Detecting a selection operation of at least one of the device identifiers in the second device list, determining a second target device; the second target device includes an electronic device corresponding to the device identifier selected in the second device list; The target range is determined based on the second user account and the second target device; the target range indicates that the second target device logged in with the second user account has access rights to the first target device.

7. The method according to claim 1 or 2, characterized in that: The target range also indicates that an electronic device logged in with a third user account does not have access permission to the first target device.

8. The method according to claim 7, characterized in that The third user account includes one or more user accounts associated with the first user account; after determining at least one first target device, the method further includes: Displaying a first interface; the first interface is used to set the target range; receiving a second instruction input based on the first interface; In response to the second instruction, displaying an account list, the account list including an account identifier of at least one user account associated with the first user account; Detecting a selection operation of at least one of the account identifiers in the account list, determining at least one of the third user accounts; the third user account is a user account corresponding to the account identifier selected in the account list; Based on the third user account, the target range is determined.

9. The method according to claim 7, characterized in that: After determining at least one first target device, the method further includes: Displaying a first interface; the first interface is used to set the target range; receiving a fourth instruction input based on the first interface; In response to the fourth instruction, displaying an input control; Based on the content input in the input control, determining at least one third user account represented by the content; Based on the third user account, the target range is determined.

10. The method according to claim 8 or 9, characterized in that: The determining the target range based on the third user account includes: Sending a second request to the server, the second request including the third user account, the second request being used to request obtaining a third device list, the third device list including device identifiers of electronic devices logged in with the third user account; receiving and displaying the third device list sent by the server; Detecting a selection operation of at least one of the device identifiers in the third device list, determining a third target device; the third target device includes an electronic device corresponding to the device identifier selected in the third device list; The target range is determined based on the third user account and the third target device; the target range indicates that the third target device logged in with the third user account does not have access permission to the first target device.

11. The method according to claim 1 or 2, characterized in that: After determining at least one first target device, the method further includes: Displaying a first interface; the first interface is used to set the target range; receiving a third instruction input based on the first interface; In response to the third instruction, the target range is determined.

12. A rights management method, characterized in that: The method comprises: receiving setting information sent by a first device; the setting information includes a target range; the setting information is used to indicate that access rights of an electronic device requesting access to a first target device are managed based on the target range; the first target device is bound to the first device; the target range indicates that an electronic device logged in with a first user account has access rights to the first target device; the first user account is a user account logged in by the first device; In response to the setting information, access rights of electronic devices requesting access to the first target device are managed based on the target range.

13. The method according to claim 12, characterized in that After receiving the setting information sent by the first device, the method further includes: When a third device is detected, the authorization range of the first target device bound to the third device is updated to the target range based on the setting information; the third device includes an electronic device logged in with the first user account; the third device is different from the first device.

14. The method according to claim 12 or 13, characterized in that The target range also indicates that an electronic device logged into the second user account has access rights to the first target device.

15. The method according to claim 14, characterized in that Before receiving the setting information sent by the first device, the method further includes: receiving a first request sent by the first device; the first request includes the second user account; the second user account includes one or more user accounts associated with the first user account; In response to the first request, sending a second device list to the first device, where the second device list includes device identifiers of electronic devices logged in with the second user account; The receiving the setting information sent by the first device includes: receiving the setting information sent by the first device based on the second device list; the target range also indicates that the second target device logged in with the second user account has access rights to the first target device; the second target device includes the first The electronic device corresponding to the device identification selected in the second device list detected by a device.

16. The method according to claim 14, characterized in that The second user account is determined based on the content input in the input control in the first device; the input control includes a control displayed by the first device in response to a fifth instruction input in the displayed first interface; the fifth instruction is used to instruct the first device to set the electronic device logged in with the second user account to have access rights to the first target device.

17. The method according to claim 12 or 13, characterized in that: The target range also indicates that an electronic device logged in with a third user account does not have access permission to the first target device.

18. The method according to claim 17, characterized in that Before receiving the setting information sent by the first device, the method further includes: receiving a second request sent by the first device; the second request includes the third user account, and the third user account includes one or more user accounts associated with the first user account; In response to the second request, sending a third device list to the first device, the third device list including device identifiers of electronic devices logged in with the third user account; The receiving the setting information sent by the first device includes: Receive setting information sent by the first device based on the third device list; the target range also represents that the third target device logged in with the third user account does not have access rights to the first target device; the third target device includes the electronic device corresponding to the device identifier selected in the third device list detected by the first device.

19. The method according to claim 18, characterized in that The third user account is determined based on the content input in the input control in the first device; the input control includes a control displayed by the first device in response to a fourth instruction input in the displayed first interface, and the fourth instruction is used to instruct the first device to set the electronic device logged in with the third user account to have no access rights to the first target device.

20. An electronic device, characterized in that: include: A memory and one or more processors; the memory is coupled to the processor; wherein the memory stores computer program code, the computer program code includes computer instructions, and when the computer instructions are executed by the processor, the electronic device executes the method as described in any one of claims 1-11, or the electronic device executes the method as described in any one of claims 12-19.

21. A computer storage medium comprising computer instructions, characterized in that: When the computer instructions are executed on an electronic device, the electronic device executes the method according to any one of claims 1 to 11, or the electronic device executes the method according to any one of claims 12 to 19.

22. A computer program product, characterized in that When the computer program product is executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 11, or the electronic device is caused to execute the method according to any one of claims 12 to 19.

Citation Information

Patent Citations

  • Method and apparatus of controlling access permission among multi devices, and mobile terminal

    CN106685978A

  • Authorization method of Internet of Things equipment control authority

    CN110677410A

  • Internet of things system based on security orientation and group sharing

    US11310235B1

  • Data Permission Management for Wearable Devices

    US20160034696A1

  • Electronic device for controlling internet of things device and method for controlling internet of things device

    WO2020145599A1