Device sharing method and apparatus, storage medium, and electronic device

Abstract

The application discloses a device sharing method and device, a storage medium and an electronic device, and relates to the technical field of smart home. The method comprises the following steps: determining the device type of a target device according to the management mode corresponding to the target device and the security level of the target device, and determining whether the target device is allowed to be shared to a target object according to the device type of the target device, wherein the permission range of devices of different device types allowed to be shared is different; in the case that it is determined that the target device is allowed to be shared to the target object, determining the target permission range of the target device to be shared to the target object; and sharing the use permission of the target device within the target permission range to the target object. According to the above method, the problem that the operation process of the technical scheme for realizing device sharing between users by relying on the mode of newly establishing a family group in the prior art is complicated can be solved.

Description

Technical Field

[0001] This application relates to the field of smart home technology, and more specifically, to a method and apparatus for sharing devices, a storage medium, and an electronic device. Background Technology

[0002] In smart home scenarios, users typically own multiple smart devices (e.g., appliances, cameras, etc.). When it's necessary to share a device with other users but not to allow them access to other devices, the common approach is to create a new home group, invite the sharing user to join, and then transfer the target device to that home group. This method is not only cumbersome but also forces users to frequently switch between different home groups, severely impacting usability. Furthermore, users have different permission requirements for different types of devices, and these requirements dynamically adjust as business functions change. Therefore, current technologies lack a device sharing method that simplifies the sharing process and supports dynamic permission adjustments.

[0003] There is no effective solution yet to address the cumbersome operational process of technical solutions that rely on creating new homegroups to achieve device sharing among users. Summary of the Invention

[0004] This application provides a method and apparatus for sharing devices, a storage medium, and an electronic device, to at least solve the problem of cumbersome operation procedures in related technologies that rely on creating new homegroups to achieve device sharing among users.

[0005] According to one embodiment of this application, a device sharing method is provided, comprising: determining the device type of the target device based on the management method corresponding to the target device and the security level of the target device, and determining whether the target device is allowed to be shared to a target object based on the device type of the target device, wherein different device types have different permission ranges for sharing; if it is determined that the target device is allowed to be shared to the target object, determining the target permission range to which the target device is to be shared to the target object; and sharing the usage permissions of the target device within the target permission range to the target object.

[0006] In one exemplary embodiment, determining whether a target device is allowed to be shared to a target object based on its device type includes: if the target device is determined to be a device of a first security level, a device of a second security level, or a group device, determining that the target device is allowed to be shared to the target object; if the target device is determined to be a device of a third security level, determining that the target device is not allowed to be shared to the target object, wherein the device type includes: a device of the first security level, a device of the second security level, a device of the third security level, and a group device.

[0007] In one exemplary embodiment, determining the target permission range to be shared by the target device to the target object includes: if the device type of the target device is determined to be a device of a first security level, determining all permission ranges corresponding to the target device, and determining the target permission range within the all permission ranges; if the device type of the target device is determined to be a device of a second security level, determining a first permission range corresponding to the target device, and determining the target permission range within the first permission range, wherein the first permission range is a portion of the permission ranges corresponding to the target device; if the device type of the target device is determined to be a group device, determining whether the target device is an associated group device, and determining the target permission range based on whether the target device is an associated group device.

[0008] In an exemplary embodiment, determining the target permission range based on whether the target device is an associated group device includes: if the target device is determined to be an associated group device, determining a first master device and one or more first sub-devices in the target device; determining a second permission range in which the first master device is allowed to be shared to the target object, and determining the target permission range corresponding to the first master device and the one or more first sub-devices within the second permission range; if the target device is determined to be a non-associated group device, determining a second master device and one or more second sub-devices in the target device; determining a third permission range in which the second master device is allowed to be shared to the target object and a fourth permission range in which the one or more second sub-devices are allowed to be shared to the target object, and determining a fifth permission range corresponding to the second master device within the third permission range and a sixth permission range corresponding to the one or more second sub-devices within the fourth permission range, wherein the target permission range includes the fifth permission range and the sixth permission range.

[0009] In an exemplary embodiment, before sharing the usage rights of the target device within the target permission scope to the target object, the method further includes: determining the target object through a target pathway, wherein the target pathway includes at least one of the following: the contact information of the target object, the account of the target object in the target program, and the identification information corresponding to the target object; determining whether the target object and a first object having management rights over the target device are the same object; if the target object and the first object are determined to be the same object, prohibiting the sharing of the usage rights of the target device within the target permission scope to the target object; if the target object and the first object are not the same object, determining whether the target object and the first object are in the same home group; if the target object and the first object are determined to be in the same home group, prohibiting the sharing of the usage rights of the target device within the target permission scope to the target object; if the target object and the first object are not in the same home group, allowing the sharing of the usage rights of the target device within the target permission scope to the target object.

[0010] In an exemplary embodiment, after sharing the usage rights of the target device within the target permission scope to the target object, the method further includes: stopping the sharing of the usage rights of the target device within the target permission scope to the target object under at least one of the following conditions: stopping the sharing of the usage rights of the target device within the target permission scope to the target object when a first object and / or the target object actively terminates the sharing of the target device, wherein the first object is an object with management rights over the target device; stopping the sharing of the usage rights of the target device within the target permission scope to the target object when the target device is removed from the device group managed by the target family group corresponding to the first object, and / or the first object leaves the target family group.

[0011] In an exemplary embodiment, after determining the target permission range to which the target device is to be shared with the target object, the method further includes: if a first object sends a sharing link to the target object, determining whether the sharing link is invalid by one of the following methods, wherein the sharing link is used to instruct the target object to share the target device, and the first object is an object with management permissions for the target device: if the target object does not accept the sharing link within a target time period, determining that the sharing link is invalid; if the target object has accepted the sharing link, and any usage permission of the target device within the target permission range is changed from allowed to not allowed to be shared, determining that the sharing link is invalid; if the target object refuses to accept the sharing link, determining that the sharing link is invalid.

[0012] According to another embodiment of the present application, a device sharing apparatus is also provided, comprising: a first determining module, configured to determine the device type of the target device based on the management method corresponding to the target device and the security level of the target device, and to determine whether the target device is allowed to be shared to a target object based on the device type of the target device, wherein different device types have different allowed sharing permission ranges; a second determining module, configured to determine the target permission range to be shared to the target object when it is determined that the target device is allowed to be shared to the target object; and a sharing module, configured to share the usage permissions of the target device within the target permission range to the target object.

[0013] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer program, and the computer program is configured to execute the sharing method of the above-described device when it is run.

[0014] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the device sharing method through the computer program.

[0015] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program, wherein the computer program is executed by a processor using the device sharing method described above.

[0016] In this embodiment, the device type of the target device is determined based on its management method and security level. The device type then determines whether the target device is allowed to be shared with the target object, as different device types have different allowed sharing permissions. If the target device is determined to be allowed to be shared with the target object, the target permission range to be shared with the target object is determined, and the usage permissions of the target device within the target permission range are shared with the target object. In other words, this embodiment categorizes devices into different allowed sharing permission ranges based on their management method and security level, and determines whether the target device is allowed to be shared with the target object based on the different device types. If the target device is determined to be allowed to be shared with the target object, the target permission range to be shared with the target object is determined, and thus the usage permissions of the target device within the target permission range are shared with the target object. This embodiment solves the problem of cumbersome operation processes in related technologies that rely on creating new homegroups to achieve device sharing between users. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a schematic diagram of the hardware environment for a device sharing method according to an embodiment of this application;

[0020] Figure 2 This is a flowchart of a device sharing method according to an embodiment of this application;

[0021] Figure 3 This is a flowchart of a device sharing method according to an optional embodiment of this application;

[0022] Figure 4 This is a schematic diagram of a device type according to an optional embodiment of this application;

[0023] Figure 5 This is a structural block diagram of a device sharing apparatus according to an embodiment of this application. Detailed Implementation

[0024] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0025] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0026] According to one aspect of the embodiments of this application, a method for sharing devices is provided. This device sharing method is widely applicable to whole-house intelligent digital control application scenarios such as smart homes, smart home ecosystems, and smart house ecosystems. Optionally, Figure 1 This is a schematic diagram of the hardware environment for a device sharing method according to an embodiment of this application. In this embodiment, the device sharing method can be applied to modules in home appliances, and the modules can be applied to, for example... Figure 1 The hardware environment shown consists of home appliance 102 and server 104. Figure 1 As shown, server 104 is connected to home appliance 102 via a network and can be used to provide services (such as application services) to nodes or clients installed on nodes. A database can be set up on the server or independently to provide data storage services for server 104. Cloud computing and / or edge computing services can be configured on the server or independently to provide data processing services for server 104.

[0027] The aforementioned networks may include, but are not limited to, at least one of the following: wired network, wireless network. The aforementioned wired network may include, but is not limited to, at least one of the following: wide area network (WAN), metropolitan area network (MAN), local area network (LAN). The aforementioned wireless network may include, but is not limited to, at least one of the following: Wi-Fi (Wireless Fidelity), Bluetooth. Home appliances 102 may not be limited to smart air conditioners, smart range hoods, smart refrigerators, smart ovens, smart stoves, smart washing machines, smart water heaters, smart washing equipment, smart dishwashers, smart projectors, smart TVs, smart clothes racks, smart curtains, smart audio-visual equipment, smart sockets, smart speakers, smart speakers, smart fresh air systems, smart kitchen and bathroom equipment, smart bathroom equipment, smart robot vacuum cleaners, smart window cleaning robots, smart mopping robots, smart air purifiers, smart steam ovens, smart microwave ovens, smart water heaters, smart air purifiers, smart water dispensers, smart door locks, etc.

[0028] This embodiment provides a device sharing method, applied to the above-mentioned module. Figure 2 This is a flowchart of a device sharing method according to an embodiment of this application, the process including the following steps:

[0029] Step S202: Determine the device type of the target device according to the management method and security level of the target device, and determine whether the target device is allowed to be shared with the target object according to the device type of the target device. The scope of permissions allowed to be shared varies for different device types.

[0030] Where the target device is determined to be a device that can be managed independently, the target device is defined as an exclusive device.

[0031] If it is determined that the management method corresponding to the target device is to require unified management, the target device is identified as a group device. In this case, it means that the target device is a group of devices, not a single device.

[0032] If the target device is determined to be the exclusive device, the security level of the target device is determined, and the device type of the target device is determined according to the security level. The device type of the target device determined according to the security level includes: a device of the first security level, a device of the second security level, and a device of the third security level.

[0033] If the target device is determined to be a group device, the group device is determined to be the device type of the target device.

[0034] The device types in this application embodiment may include: devices of the first security level, devices of the second security level, devices of the third security level, and groups of devices.

[0035] The aforementioned equipment at the first safety level can be equipment with lower risk;

[0036] The devices mentioned above in the second security level can be high-security devices with certain sensitivity, such as devices that may contain personal privacy data;

[0037] The device in the third security level mentioned above can be other devices, that is, devices that cannot be shared.

[0038] Step S204: If it is determined that the target device is allowed to be shared to the target object, determine the target permission range to which the target device is to be shared to the target object;

[0039] Step S206: Share the usage rights of the target device within the target permission scope to the target object.

[0040] Through the above steps, the device type of the target device is determined based on its management method and security level. The device type then determines whether the target device is allowed to be shared with the target object, as different device types have different permitted sharing permissions. If the target device is determined to be allowed to be shared with the target object, the target permission range to be shared with the target object is determined, and the usage permissions of the target device within the target permission range are shared with the target object. In other words, this application embodiment categorizes devices into different permitted sharing permission ranges based on their management method and security level, and determines whether the target device is allowed to be shared with the target object based on the different device types. If the target device is determined to be allowed to be shared with the target object, the target permission range to be shared with the target object is determined, and thus the usage permissions of the target device within the target permission range can be shared with the target object. This application embodiment solves the problem of cumbersome operation processes in related technologies that rely on creating new homegroups to achieve device sharing between users.

[0041] Optionally, step S202 above, which determines whether the target device is allowed to be shared to the target object based on the device type of the target device, includes: if the device type of the target device is determined to be a device of a first security level, a device of a second security level, or a group device, then determining that the target device is allowed to be shared to the target object; if the device type of the target device is determined to be a device of a third security level, then determining that the target device is not allowed to be shared to the target object, wherein the device type includes: a device of the first security level, a device of the second security level, a device of the third security level, and a group device.

[0042] Understandably, devices at the first security level are those with low risk and that do not involve sensitive information. These devices are permitted to be shared with the target audience because their security risk is relatively low, and sharing will not pose a significant privacy or security threat to the initiating user.

[0043] Second-level security devices: These can be high-security devices that may contain sensitive information or have high functional safety requirements. Despite the risks, sharing of such devices is still permitted. When sharing, access permissions for the receiving user will be restricted based on the device's characteristics and the initiating user's settings to protect the device's sensitive information.

[0044] Group devices: These include associated group devices and non-associated group devices. Group devices can be shared with target objects, but the specific permission scope will be treated differently depending on whether they are associated or non-associated groups.

[0045] Devices at the third security level: These can be devices with the highest security level, potentially involved in highly sensitive or critical operations. These devices are not permitted to be shared with the intended recipients to maximize device security and data privacy. If sharing is absolutely necessary, additional security measures may be required, such as two-factor authentication, advanced encryption, or real-name authentication, to ensure the sharing process is secure and controllable.

[0046] Optionally, step S204 above, determining the target permission range to be shared by the target device to the target object, includes: if the target device is determined to be a device of a first security level, determining all permission ranges corresponding to the target device, and determining the target permission range within all permission ranges; if the target device is determined to be a device of a second security level, determining the first permission range corresponding to the target device, and determining the target permission range within the first permission range, wherein the first permission range is a portion of all permission ranges corresponding to the target device; if the target device is determined to be a group device, determining whether the target device is an associated group device, and determining the target permission range based on whether the target device is an associated group device.

[0047] Understandably, if the device is identified as belonging to the highest security level, all permission scopes of the target device can be listed, creating a complete permission scope list. Subsequently, the initiating user, based on this list, selects the permissions they wish to share with the target, thus determining the target permission scope.

[0048] If the device is determined to be at the second security level, appropriate permissions for sharing will be determined from all permission scopes to generate a first permission scope list. The first permission scope may include, for example, access permissions to non-sensitive data on the target device and access permissions to use the basic functions of the target device. The initiating user can then select the access permissions from the first permission scope list to share, ensuring that sensitive information or functions are not unintentionally leaked.

[0049] If it is determined that the device is a group device, it is necessary to determine whether the group device is an associated group device or a non-associated group device, and determine the target permission scope based on whether the target device is an associated group device or a non-associated group device.

[0050] Specifically, determining the target permission range based on whether the target device is an associated group device includes: if the target device is determined to be an associated group device, identifying a first master device and one or more first sub-devices within the target device; determining a second permission range within which the first master device is allowed to be shared to the target object, and determining the target permission range corresponding to the first master device and the one or more first sub-devices within the second permission range; if the target device is determined to be a non-associated group device, identifying a second master device and one or more second sub-devices within the target device; determining a third permission range within which the second master device is allowed to be shared to the target object and a fourth permission range within which the one or more second sub-devices are allowed to be shared to the target object, and determining a fifth permission range corresponding to the second master device within the third permission range and a sixth permission range corresponding to the one or more second sub-devices within the fourth permission range, wherein the target permission range includes the fifth permission range and the sixth permission range.

[0051] Understandably, when the target device is identified as a device in an associated group, the process begins by identifying the primary device and the primary child device. Next, the sharing permissions of the primary device are determined: based on the type and security level of the primary device, a second set of permissions is defined that allows the primary device to be shared with the target object. This second set of permissions is selected from all permissions of the primary device and applies to sharing. Finally, the permissions are extended to the primary child devices: within the second set of permissions, these permissions are applied to all primary child devices within the associated group. In other words, once the target object obtains usage permissions for the primary device, it will automatically gain the same usage permissions for all primary child devices associated with the primary device, without requiring a separate sharing process.

[0052] When the target device is determined to be a non-associated group device, firstly, the second primary device and the second secondary device need to be identified; secondly, the permissions of the second primary device and the second secondary device need to be determined: a third permission scope that the second primary device is allowed to share with the target object, and a fourth permission scope that one or more second secondary devices are allowed to share with the target object are determined. The determination of the third and fourth permission scopes is also based on their respective device types and security levels, as well as the designation of the first object (i.e., the initiating user); finally, independent permission allocation: when determining the permissions of non-associated group devices, the permissions of the second primary device are not automatically extended to the second secondary devices. That is, the target object's usage permissions for the second primary device and its usage permissions for the second secondary devices need to be obtained through separate sharing processes. A fifth permission scope corresponding to the second primary device is determined within the third permission scope, and a sixth permission scope corresponding to the second secondary device is determined within the fourth permission scope. The final target permission scope consists of the fifth and sixth permission scopes.

[0053] Optionally, before sharing the usage rights of the target device within the target permission scope to the target object in step S206 above, the method further includes: determining the target object through a target pathway, wherein the target pathway includes at least one of the following: the contact information of the target object, the account of the target object in the target program, and the identification information corresponding to the target object; determining whether the target object and a first object with management rights over the target device are the same object; if the target object and the first object are determined to be the same object, prohibiting the sharing of the usage rights of the target device within the target permission scope to the target object; if the target object and the first object are not the same object, determining whether the target object and the first object are in the same home group; if the target object and the first object are determined to be in the same home group, prohibiting the sharing of the usage rights of the target device within the target permission scope to the target object; if the target object and the first object are not in the same home group, allowing the sharing of the usage rights of the target device within the target permission scope to the target object.

[0054] Understandably, before sharing the target permission scope to the target object, it is necessary to identify the target object and determine whether the sharing conditions are met. Specifically:

[0055] Identifying target objects: Target objects can be identified based on, but are not limited to, the target object's contact information, account in a specific application (target program), or the target object's identification information.

[0056] Determine the relationship between the target object and the first object: Determine if the first object and the target object are the same object: Check if the target object is the same object as the first object that has management permissions for the target device. If so, the sharing operation will be prohibited because the target object already has management permissions and there is no need to share it.

[0057] Determine if the target object and the first object are in the same homegroup: If the target object and the first object are not the same object, further check if they are in the same homegroup. Users in the same homegroup usually already have access to the shared device. Therefore, if the target object and the first object are in the same homegroup, it means that the target object already has management rights to the target device and no sharing operation is needed. Therefore, the sharing operation will also be prohibited to avoid duplicate permission granting and conflict.

[0058] Confirmation of sharing conditions: Sharing is allowed only when it is confirmed that the target object and the first object are neither the same person nor in the same household group, the usage rights of the target device within the target's permission scope will be shared with the target object.

[0059] In summary, the user database can be used to compare the information of the primary and target users, including but not limited to phone numbers, account information, and family group identifiers, to verify their identities and relationships. Based on the verified user relationship, logical judgments are executed to determine whether sharing is allowed. If the target users are the same person or in the same family group, the sharing process will be blocked; otherwise, the sharing operation will be allowed to continue.

[0060] Once the sharing conditions are met, a sharing invitation can be sent to the target user through the target channel (such as SMS, in-app notification, or email), informing them of the specific information and permission scope of the shared device.

[0061] Optionally, after sharing the usage rights of the target device within the target permission scope to the target object in step S206 above, the method further includes: stopping the sharing of the usage rights of the target device within the target permission scope to the target object under at least one of the following conditions: stopping the sharing of the usage rights of the target device within the target permission scope to the target object when a first object and / or the target object actively terminates the sharing of the target device, wherein the first object is an object with management rights over the target device; stopping the sharing of the usage rights of the target device within the target permission scope to the target object when the target device is removed from the device group managed by the target family group corresponding to the first object, and / or the first object leaves the target family group.

[0062] It is understandable that after sharing usage permissions within the target scope to the target object, sharing to the target device needs to be stopped if at least one of the following conditions is met:

[0063] (1) Actively terminate sharing:

[0064] 1) Active Termination by the First Object: Suppose that the first object with administrative privileges over the target device decides to terminate the sharing of the target device. This intention may stem from the device no longer needing to be shared, misconduct by the sharing object, or other personal reasons. In this case, the sharing of usage rights for the target device within the target's authorized scope will be immediately stopped to the target object, and all related permissions of the target object will be revoked to protect the security of the device and data.

[0065] 2) Active Termination by the Target Object: If the target object no longer needs to use the target device, or wants to terminate the sharing for its own security reasons, the target object can also actively initiate a sharing termination request. Upon receiving such a request, the sharing of the target device's usage rights to the target object will be stopped immediately, ensuring that user permissions are consistent with needs.

[0066] (2) Automatically terminate sharing:

[0067] 1) Target device removed from target home group management: If the target device is removed from the device group managed by the home group corresponding to the first object, the sharing of the target device's usage permissions within the target permission scope to the target object will be automatically stopped.

[0068] 2) First object leaves homegroup: If the first object decides to leave the target homegroup, this will also trigger the automatic cessation of sharing access to the target device with all target objects currently sharing the target device.

[0069] An event monitoring mechanism can be implemented to monitor key events such as changes in the status of the target device, user operations, and changes in family group members: monitor the status changes of the target device, and trigger the sharing termination process when it is determined that the target device changes from being present in the device group to not being present in the device group, and / or the target device changes from being powered on to being powered off.

[0070] In addition, the system monitors the family members of the target family group in which the first object exists, and triggers a sharing termination process if it is determined that the first object has left the target family group.

[0071] It can perform permission revoke and notification operations. When sharing is terminated, the permission records of the target object will be cleared from the database to ensure that it can no longer access or control the target device. At the same time, a notification message can be sent to the target object to inform it that the sharing has been terminated and the possible reason for the termination, so as to enhance the user's transparency and trust in the system operation. The database is used to store permission records.

[0072] Optionally, after determining the target permission range to which the target device is to be shared with the target object in step S204 above, the method further includes: if the first object sends a sharing link to the target object, determining whether the sharing link is invalid by one of the following methods, wherein the sharing link is used to instruct the target object to share the target device, and the first object is an object with management permissions for the target device: if the target object does not accept the sharing link within a target time period, determining that the sharing link is invalid; if the target object has accepted the sharing link, and any usage permission of the target device within the target permission range is changed from allowed to not allowed to be shared, determining that the sharing link is invalid; if the target object refuses to accept the sharing link, determining that the sharing link is invalid.

[0073] The conditions under which a shared connection fails may include:

[0074] If a shared link is not accepted within the target time period: If the target object does not respond to accept the device's sharing permission within the preset target time period after the first object sends a shared link to it, the shared link will be considered invalid. This technical solution avoids prolonged pending sharing invitations and also considers that the target object may fail to accept the sharing within the limited time due to various reasons (such as not checking messages in time, hesitation in decision-making, etc.), thus automatically terminating the validity of the shared link, freeing up system resources, and reducing potential permission management chaos.

[0075] Device permission changes disallow sharing: Even if the target object has accepted access to the target device via a shared link, if the target device's access permission status changes from allowed to disallowed, the original shared link will be deemed invalid. This may be due to the device owner (i.e., the first object) adjusting permission settings or system policy updates, rendering the original shared permissions inapplicable. In this case, the target object will lose control or access to the device, and the original shared link will become invalid to prevent unauthorized access or data leakage.

[0076] If the target user refuses to accept the link: The validity of a shared link also depends on the target user's willingness to accept it. If the target user explicitly refuses to accept the shared link, the link will be immediately deemed invalid, and the subsequent sharing process will be stopped. This respects the target user's decision and avoids unnecessary push notifications and permission allocations, protecting the user's privacy and device security.

[0077] To better understand the process of the above-mentioned device sharing method, the implementation flow of the above-mentioned device sharing method will be described below in conjunction with optional embodiments, but it is not intended to limit the technical solution of the embodiments of this application.

[0078] Figure 3 This is a flowchart of a device sharing method according to an optional embodiment of this application, such as... Figure 3 As shown:

[0079] The device sharing method in the optional embodiments of this application involves a server (which may involve one or more), an initiating user terminal (i.e., a first object), and a receiving user terminal (i.e., a target object);

[0080] The initiating user is a user who has management rights over the target device and shares it with others; the receiving user is a user who accepts the sharing of the target device and has usage rights over it after accepting the sharing.

[0081] Step S301: Configure the device type on the server side;

[0082] in, Figure 4 This is a schematic diagram of a device type according to an optional embodiment of this application, such as... Figure 4 As shown, the equipment types include: ordinary equipment (i.e., equipment of the first security level), high-security equipment (i.e., equipment of the second security level), group equipment, and other equipment (i.e., equipment of the third security level), wherein:

[0083] (1) Ordinary devices can be shared by one or more users with administrative privileges with other users;

[0084] (2) High-security devices can be shared by one or more users with management privileges with other users, but the scope of use of the high-security device by the receiving user is limited;

[0085] (3) Group devices: Group devices encompass one or more of associated group devices and unassociated group devices, specifically:

[0086] 1) Associated Group Devices: This group includes a master device (i.e., the first master device) and one or more sub-devices (i.e., the first sub-devices) that follow the master device. The master device in the associated group can be shared by one or more initiating users with the receiving users. When a receiving user gains access to the master device in the associated group, they will simultaneously gain access to one or more sub-devices that follow the master device in the associated group. When a receiving user loses access to the master device in the associated group, they will also simultaneously lose access to one or more sub-devices that follow the master device in the associated group.

[0087] 2) Non-Associated Group Devices: This group includes a primary device (i.e., the second primary device) and one or more secondary devices (i.e., the second secondary devices) that follow the primary device. The primary device in a non-associated group can be shared by one or more initiating users with the receiving user. However, when a receiving user gains access to the primary device in an associated group, they will not simultaneously gain access to the one or more secondary devices that follow the primary device in the non-associated group; similarly, when a receiving user loses access to the primary device in an associated group, they will not simultaneously lose access to the one or more secondary devices that follow the primary device.

[0088] (4) Other devices: Devices that cannot be shared with other users. The scope of invalid devices can be dynamically adjusted by the system.

[0089] Step S302: The initiating user terminal has device management permissions;

[0090] Step S303: The initiating user selects the target device;

[0091] Step S304: The server verifies the device type;

[0092] If the device type is determined to be another device (i.e., an abnormal situation), proceed to step S305;

[0093] If the device type is determined to be ordinary device, high-security device, or main device (i.e., normal situation), execute device S306;

[0094] Step S305 indicates an abnormal situation;

[0095] Step S306: The initiating user selects the target user (i.e., the target object) / sharing method;

[0096] Among them, the initiating user can specify the target user through various means (i.e., target means), including but not limited to: mobile phone number, application account, etc.

[0097] Step S307: The server queries the user identifier (i.e., identifier information);

[0098] If the user identifier is determined to be abnormal, proceed to step S308;

[0099] If the user identifier is determined to be normal, proceed to step S309;

[0100] Step S308: The initiating user terminal displays an error message;

[0101] Step S309: The initiating user confirms the user information;

[0102] Step S310: The initiating user initiates the sharing process;

[0103] In step S311, the server updates the process status to: pending acceptance;

[0104] Step S312: The receiving user terminal views the shared information;

[0105] Step S313: The receiving user selects whether to receive the sharing.

[0106] If the recipient user selects another option (e.g., the recipient user chooses not to accept), proceed to step S314.

[0107] If the receiving user chooses to receive, proceed to step S315;

[0108] In step S314, the server updates the process status to: expired;

[0109] In step S315, the server updates the process status to: Accepted;

[0110] Step S316: The receiving user terminal uses the functions within the scope of permissions (i.e., the target scope of permissions);

[0111] In addition, the receiving user can perform operations such as canceling sharing (i.e. Figure 3 If step S317 is executed on the receiving user terminal, then step S314 is executed.

[0112] Furthermore, the initiating user terminal can also perform step S318, such as changing device permissions / canceling sharing. If it is determined that the receiving user terminal has performed step S318, then step S314 is executed.

[0113] In summary, the sharing initiation rules in the optional embodiments of this application are as follows:

[0114] The initiating user can share devices with which they have administrative privileges with the receiving user:

[0115] 1) If the initiating user and the receiving user are in the same family group, the receiving user already has device usage rights and higher permissions, so there is no need to grant the receiving user usage rights again.

[0116] 2) The initiating user can specify the target user through various means, including but not limited to: mobile phone number, application account, etc.;

[0117] 3) When the specified target user and the initiating user are the same user, since the initiating user already has device management permissions, there is no need to grant the user usage permissions again.

[0118] 4) The initiating user can cancel or withdraw the sharing action before the receiving user accepts the device usage permission.

[0119] Shared usage rules:

[0120] 1) After the receiving user accepts the device usage rights of the target device, the target device is added to all the receiving user's home groups as a separate group;

[0121] 2) After the receiving user accepts the device usage permission, both the initiating user and the receiving user can end the device sharing;

[0122] 3) If the initiating user's management permissions for the target device change, the receiving user's usage permissions for the device remain unchanged;

[0123] 4) If the relationship between the target device and the initiating user's shared family group changes, the receiving user's access to the target device will automatically end.

[0124] Shared state definition:

[0125] Each device sharing process can include multiple of the following states:

[0126] (1) Accepted: The receiving user has accepted the right to use the target device, and the right to use the target device has not been automatically cancelled due to any changes;

[0127] (2) Invalid: Any of the following situations may exist:

[0128] 1) The receiving user accepted the access to the target device, but the access to the target device was automatically revoked due to a certain change;

[0129] 2) The receiving user did not accept the access permission for the target device, but the access permission invitation for the target device became invalid due to some change;

[0130] (3) Pending Acceptance: The invitation to use the target device (i.e., the shared link) has been activated, but the receiving user has not yet accepted the invitation to use the target device.

[0131] This application's optional embodiments provide a device and method for device sharing based on a user dimension, including initiating sharing, accepting sharing, using shared devices, and the logic for changes in the sharing relationship state throughout the entire process. Furthermore, the sharing function implemented through system configuration of device types ensures flexibility, stability, and security. In other words, this application's optional embodiments establish a user-dimensional device sharing model that is compatible with existing homegroup sharing models; and formulate detailed and reasonable sharing rules, with sharing restrictions and rule refinements for different device types to ensure the security, stability, and convenience of the sharing and usage process; simultaneously, it supports multiple sharing initiation and acceptance methods, expanding channels and accommodating diverse social and usage habits.

[0132] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of this application.

[0133] Figure 5 This is a structural block diagram of a device sharing apparatus according to an embodiment of this application; as shown below. Figure 5 As shown, it includes:

[0134] The first determining module 52 is used to determine the device type of the target device according to the management method and security level of the target device, and to determine whether the target device is allowed to be shared to the target object according to the device type of the target device, wherein the scope of permissions allowed to be shared is different for different device types;

[0135] The second determining module 54 is used to determine the target permission range of the target device to be shared with the target object when it is determined that the target device is allowed to be shared with the target object;

[0136] The sharing module 56 is used to share the usage rights of the target device within the target permission scope to the target object.

[0137] The aforementioned device determines the device type of the target device based on its management method and security level, and then determines whether the target device is allowed to be shared with the target object based on its device type. Different device types have different permitted sharing permissions. If the target device is determined to be allowed to be shared with the target object, the target permission range to be shared with the target object is determined, and the usage permissions of the target device within the target permission range are shared with the target object. In other words, this embodiment classifies devices into different permitted sharing permission ranges based on their management method and security level, and determines whether the target device is allowed to be shared with the target object based on the different device types. If the target device is determined to be allowed to be shared with the target object, the target permission range to be shared with the target object is determined, and thus the usage permissions of the target device within the target permission range are shared with the target object. This embodiment solves the problem of cumbersome operation procedures in related technologies that rely on creating new homegroups to achieve device sharing between users.

[0138] In an exemplary embodiment, the first determining module 52 is further configured to determine that the target device is allowed to be shared to the target object if the device type of the target device is determined to be a device of a first security level, a device of a second security level, or a group device; and to determine that the target device is not allowed to be shared to the target object if the device type of the target device is determined to be a device of a third security level, wherein the device type includes: a device of the first security level, a device of the second security level, a device of the third security level, and a group device.

[0139] In one exemplary embodiment, the second determining module 54 is further configured to: determine all permission ranges corresponding to the target device when the device type of the target device is determined to be a device of a first security level, and determine the target permission range within the all permission ranges; determine a first permission range corresponding to the target device when the device type of the target device is determined to be a device of a second security level, and determine the target permission range within the first permission range, wherein the first permission range is a portion of the permission ranges corresponding to the target device; and determine whether the target device is an associated group device when the device type of the target device is determined to be a group device, and determine the target permission range based on whether the target device is an associated group device.

[0140] In an exemplary embodiment, the second determining module 54 is further configured to, when determining that the target device is an associated group device, determine a first master device and one or more first sub-devices in the target device; determine a second permission range that the first master device is allowed to be shared to the target object, and determine the target permission range corresponding to the first master device and the one or more first sub-devices within the second permission range; when determining that the target device is a non-associated group device, determine a second master device and one or more second sub-devices in the target device; determine a third permission range that the second master device is allowed to be shared to the target object and a fourth permission range that the one or more second sub-devices are allowed to be shared to the target object, and determine a fifth permission range corresponding to the second master device within the third permission range and a sixth permission range corresponding to the one or more second sub-devices within the fourth permission range, wherein the target permission range includes the fifth permission range and the sixth permission range.

[0141] In an exemplary embodiment, the sharing module 56 is further configured to determine the target object through a target path, wherein the target path includes at least one of the following: the contact information of the target object, the account of the target object in the target program, and the identification information corresponding to the target object; determine whether the target object and a first object with management authority over the target device are the same object; if the target object and the first object are determined to be the same object, prohibit sharing the usage rights of the target device within the target authority scope to the target object; if the target object and the first object are not the same object, determine whether the target object and the first object are in the same home group; if the target object and the first object are determined to be in the same home group, prohibit sharing the usage rights of the target device within the target authority scope to the target object; if the target object and the first object are not in the same home group, allow sharing the usage rights of the target device within the target authority scope to the target object.

[0142] In an exemplary embodiment, the sharing module 56 is further configured to stop sharing the usage rights of the target device within the target permission scope to the target object under at least one of the following conditions: stopping the sharing of the target device's usage rights within the target permission scope to the target object when a first object and / or the target object actively terminates the sharing of the target device, wherein the first object is an object with management rights over the target device; stopping the sharing of the target device's usage rights within the target permission scope to the target object when the target device is removed from the device group managed by the target family group corresponding to the first object, and / or the first object leaves the target family group.

[0143] In an exemplary embodiment, the sharing module 56 is further configured to determine whether the sharing link is invalid in one of the following ways when the first object sends the sharing link to the target object, wherein the sharing link is used to instruct the target object to share the target device, and the first object is an object with management authority over the target device: determining that the sharing link is invalid when the target object does not accept the sharing link within a target time period; determining that the sharing link is invalid when the target object has accepted the sharing link and any usage permission of the target device within the target permission range has changed from allowed to not allowed to be shared; and determining that the sharing link is invalid when the target object refuses to accept the sharing link.

[0144] Embodiments of this application also provide a storage medium including a stored program, wherein the program executes any of the methods described above when it is run.

[0145] Optionally, in this embodiment, the storage medium may be configured to store program code for performing the following steps:

[0146] S1. Determine the device type of the target device based on the management method and security level of the target device, and determine whether the target device is allowed to be shared with the target object based on the device type of the target device. The scope of permissions allowed to be shared varies for different device types.

[0147] S2, if it is determined that the target device is allowed to be shared to the target object, determine the target permission range to be shared by the target device to the target object;

[0148] S3, share the usage rights of the target device within the target permission scope to the target object.

[0149] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0150] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0151] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0152] S1. Determine the device type of the target device based on the management method and security level of the target device, and determine whether the target device is allowed to be shared with the target object based on the device type of the target device. The scope of permissions allowed to be shared varies for different device types.

[0153] S2, if it is determined that the target device is allowed to be shared to the target object, determine the target permission range to be shared by the target device to the target object;

[0154] S3, share the usage rights of the target device within the target permission scope to the target object.

[0155] Embodiments of this application also provide a computer program product, including a computer program that is executed by a processor through the steps of any of the above method embodiments.

[0156] Optionally, in this embodiment, the above-mentioned computer program product can be executed by a processor using the following steps:

[0157] S1. Determine the device type of the target device based on the management method and security level of the target device, and determine whether the target device is allowed to be shared with the target object based on the device type of the target device. The scope of permissions allowed to be shared varies for different device types.

[0158] S2, if it is determined that the target device is allowed to be shared to the target object, determine the target permission range to be shared by the target device to the target object;

[0159] S3, share the usage rights of the target device within the target permission scope to the target object.

[0160] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0161] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0162] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0163] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for sharing a device, characterized in that, include: The device type of the target device is determined based on the management method and security level of the target device, and whether the target device is allowed to be shared with the target object is determined based on the device type of the target device. Different device types have different permissions to be shared. If it is determined that the target device is allowed to be shared with the target object, the target permission range to which the target device is to be shared with the target object is determined; Share the usage rights of the target device within the target permission scope to the target object; Determining the target permission scope to be shared by the target device to the target object includes: If the target device is determined to be a group device, determine whether the target device is an associated group device, and determine the target permission scope based on whether the target device is an associated group device. The determination of the target permission scope based on whether the target device is an associated group device includes: If the target device is determined to be an associated group device, a first master device and one or more first sub-devices are determined in the target device; Determine a second permission range that the first master device is allowed to be shared to the target object, and within the second permission range, determine the target permission range corresponding to the first master device and the one or more first sub-devices; If the target device is determined to be a non-associated group device, a second master device and one or more second sub-devices are identified in the target device; A third permission range that the second master device is allowed to be shared to the target object and a fourth permission range that the one or more second sub-devices are allowed to be shared to the target object are determined respectively. A fifth permission range corresponding to the second master device is determined within the third permission range and a sixth permission range corresponding to the one or more second sub-devices is determined within the fourth permission range. The target permission range includes the fifth permission range and the sixth permission range.

2. The method for sharing equipment according to claim 1, characterized in that, Determining whether the target device is allowed to be shared with the target object based on the target device type includes: If the target device is determined to be a device of the first security level, a device of the second security level, or a group device, then the target device is allowed to be shared with the target object. If the target device is determined to be a device of the third security level, it is determined that the target device is not allowed to be shared with the target object, wherein the device type includes: devices of the first security level, devices of the second security level, devices of the third security level, and the group of devices.

3. The method for sharing equipment according to claim 1, characterized in that, Determining the target permission scope to be shared by the target device to the target object includes: If the target device is determined to be a device of the first security level, then all permission ranges corresponding to the target device are determined, and the target permission range is determined within all permission ranges. If the target device is determined to be a device of the second security level, a first permission range corresponding to the target device is determined, and the target permission range is determined within the first permission range, wherein the first permission range is a partial permission range among all permission ranges corresponding to the target device.

4. The method for sharing equipment according to claim 1, characterized in that, Before sharing the usage rights of the target device within the target permission scope to the target object, the method further includes: The target object is determined by a target approach, wherein the target approach includes at least one of the following: the target object's contact information, the target object's account in the target program, and the target object's corresponding identification information; Determine whether the target object and the first object that has management authority over the target device are the same object; If it is determined that the target object and the first object are the same object, it is prohibited to share the usage rights of the target device within the scope of the target permissions with the target object; If it is determined that the target object and the first object are not the same object, determine whether the target object and the first object are in the same family group; If it is determined that the target object and the first object are in the same home group, the sharing of the target device's usage permissions within the target permission scope to the target object shall be prohibited; If it is determined that the target object and the first object are not in the same home group, the access rights of the target device within the target permission scope are allowed to be shared to the target object.

5. The method for sharing equipment according to claim 1, characterized in that, After sharing the usage rights of the target device within the target permission scope with the target object, the method further includes: The sharing of the target device's usage rights within the target permission scope to the target object shall be stopped if at least one of the following conditions is met: If the first object and / or the target object actively terminates the sharing of the target device, the sharing of the target device's usage rights within the target permission scope to the target object shall be stopped, wherein the first object is an object with management rights over the target device; If the target device is removed from the device group managed by the target home group corresponding to the first object, and / or the first object leaves the target home group, the sharing of the target device's usage rights within the target permission scope to the target object shall be stopped.

6. The method for sharing equipment according to claim 1, characterized in that, After determining the target permission scope to be shared by the target device to the target object, the method further includes: If a first object sends a shared link to the target object, the validity of the shared link is determined by one of the following methods, wherein the shared link is used to instruct the target object to share the target device, and the first object is an object with management authority over the target device: If the target object does not accept the shared link within the target time period, the shared link is determined to be invalid. If the target object has accepted the shared link, and any usage permission of the target device within the target permission scope is changed from allowed to not allowed to be shared, the shared link is determined to be invalid. If the target object refuses to accept the shared link, the shared link is determined to be invalid.

7. A device for sharing equipment, characterized in that, include: The first determining module is used to determine the device type of the target device according to the management method and security level of the target device, and to determine whether the target device is allowed to be shared to the target object according to the device type of the target device, wherein the scope of permissions allowed to be shared is different for different device types; The second determining module is used to determine the target permission range to be shared by the target device to the target object when it is determined that the target device is allowed to be shared to the target object; The sharing module is used to share the usage rights of the target device within the target permission scope to the target object; The second determining module is further configured to, when determining that the device type of the target device is a group device, determine whether the target device is an associated group device, and determine the target permission scope based on whether the target device is an associated group device; The second determining module is further configured to, when determining that the target device is an associated group device, determine a first master device and one or more first sub-devices in the target device; determine a second permission range that the first master device is allowed to be shared to the target object, and determine the target permission range corresponding to the first master device and the one or more first sub-devices within the second permission range; when determining that the target device is a non-associated group device, determine a second master device and one or more second sub-devices in the target device; determine a third permission range that the second master device is allowed to be shared to the target object and a fourth permission range that the one or more second sub-devices are allowed to be shared to the target object, and determine a fifth permission range corresponding to the second master device within the third permission range and a sixth permission range corresponding to the one or more second sub-devices within the fourth permission range, wherein the target permission range includes the fifth permission range and the sixth permission range.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program, when executed, performs the method according to any one of claims 1 to 6.

9. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method described in any one of claims 1 to 6 through the computer program.

Images