Equipment sharing method and device, storage medium and electronic device

Abstract

The invention discloses an equipment sharing method and device, a storage medium and an electronic device, and relates to the technical field of smart home, and the method comprises the steps: determining the equipment type of target equipment according to a management mode corresponding to the target equipment and the safety level of the target equipment, according to the equipment type of the target equipment, whether the target equipment is allowed to be shared to a target object is determined, and the permission ranges, allowed to be shared, of equipment of different equipment types are different; when it is determined that the target device is allowed to be shared to the target object, determining a target permission range of the target device to be shared to the target object; and sharing the use permission of the target device in the target permission range to the target object. According to the method, the problem that the operation process of the technical scheme of realizing device sharing between users by depending on a new family group mode in the related technology is tedious can be solved.

Description

Technical Field

[0001] The present application relates to the field of smart home technology, and more specifically, to a device sharing method and apparatus, a storage medium, and an electronic device. Background Art

[0002] In a smart home scenario, users usually have multiple smart devices (for example, home appliances, cameras, etc.). When a device needs to be shared with other users but they do not want them to access other devices, the currently commonly used method is to create a new home group, invite shared users to join, and transfer the target device to the home group. This method is not only cumbersome to operate, but also causes users to frequently switch between different home groups, seriously affecting the convenience of use. In addition, users have different permission requirements for different types of devices, and these requirements will be dynamically adjusted as business functions change. Therefore, the relevant technology lacks a device sharing method that can simplify the sharing process and support dynamic adjustment of permissions.

[0003] There is no effective solution to the problem that the technical solution in the related art, which relies on creating a new home group to achieve device sharing between users, has a cumbersome operating process. Summary of the Invention

[0004] The embodiments of the present application provide a device sharing method and apparatus, a storage medium, and an electronic device, so as to at least solve the problem of cumbersome operation procedures of the technical solution in the related art that relies on creating a new home group to realize device sharing between users.

[0005] According to one embodiment of the embodiments of the present application, a device sharing method is provided, including: determining the device type of the target device according to 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 with a target object according to the device type of the target device, wherein the permission scopes allowed for devices of different device types to be shared are different; when it is determined that the target device is allowed to be shared with the target object, determining the target permission scope of the target device to be shared with the target object; and sharing the usage permissions of the target device within the target permission scope with the target object.

[0006] In an exemplary embodiment, determining whether the target device is allowed to be shared with the target object is determined based on the device type of the target device, including: when it is determined that the device type of the target device is a device of the first security level, or a device of the second security level, or a group device, determining that the target device is allowed to be shared with the target object; when it is determined that the device type of the target device is a device of the third security level, determining that the target device is not allowed to be shared with the target object, wherein the device types include: devices of the first security level, devices of the second security level, devices of the third security level, and the group device.

[0007] In an exemplary embodiment, determining the target permission range of the target device to be shared with the target object includes: when it is determined that the device type of the target device is a device of the first security level, determining all permission ranges corresponding to the target device, and determining the target permission range within the all permission ranges; when it is determined that the device type of the target device is a device of the 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 partial permission range of all permission ranges corresponding to the target device; when it is determined that the device type of the target device is 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, the target permission range is determined according to whether the target device is an associated group device, including: when it is determined that the target device is an associated group device, determining a first main device and one or more first sub-devices in the target device; determining a second permission range that the first main device is allowed to be shared to the target object, and determining the target permission range corresponding to the first main device and the one or more first sub-devices within the second permission range; when it is determined that the target device is a non-associated group device, determining a second main device and one or more second sub-devices in the target device; respectively determining a third permission range that the second main 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 respectively determining a fifth permission range corresponding to the second main 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 authority scope with the target object, the method also includes: determining 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; determining whether the target object is the same object as the first object that has management authority over the target device; if it is determined that the target object and the first object are the same object, prohibiting the sharing of the usage rights of the target device within the target authority scope with the target object; if it is determined that 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 family group; if it is determined that the target object and the first object are in the same family group, prohibiting the sharing of the usage rights of the target device within the target authority scope with the target object; if it is determined that the target object and the first object are not in the same family group, allowing the sharing of the usage rights of the target device within the target authority scope with the target object.

[0010] In an exemplary embodiment, after sharing the usage rights of the target device within the target authority scope with the target object, the method further includes: stopping sharing the usage rights of the target device within the target authority scope with the target object under at least one of the following conditions: stopping sharing the usage rights of the target device within the target authority scope with the target object when the first object and / or the target object actively ends sharing the target device, wherein the first object is an object that has management authority over the target device; stopping sharing the usage rights of the target device within the target authority scope with 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 exits the target family group.

[0011] In an exemplary embodiment, after determining the target permission range of the target device to be shared to the target object, the method further includes: when a first object sends a sharing link to the target object, determining whether the sharing link is invalid in one of the following ways, wherein the sharing link is used to indicate the target object's sharing of the target device, and the first object is an object with management authority over the target device: 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 is changed from allowed to be shared to not allowed to be shared, determining that the sharing link is invalid; when the target object refuses to accept the sharing link, determining that the sharing link is invalid.

[0012] According to another embodiment of the embodiments of the present application, a device sharing device is also provided, including: a first determination module, used to determine the device type of the target device according to the management method corresponding to the target device and the 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, wherein the permission scope allowed for devices of different device types to be shared is different; a second determination module, used to determine the target permission scope 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; a sharing module, used to share the usage permission of the target device within the target permission scope to the target object.

[0013] According to another aspect of the embodiments of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the above-mentioned device sharing method when running.

[0014] According to another aspect of an embodiment of the present application, an electronic device is 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 the present application, a computer program product is provided, including a computer program, wherein the computer program is executed by a processor to implement the device sharing method.

[0016] In an embodiment of the present application, the device type of the target device is determined according to the management method and security level corresponding to the target device, and the device type of the target device determines whether the target device is allowed to be shared with the target object, and the scope of permissions allowed to be shared for devices of different device types is different; in the case of determining that the target device is allowed to be shared with the target object, the target permission scope of the target device to be shared with the target object is determined, and the usage permission of the target device within the target permission scope is shared with the target object. That is to say, in an embodiment of the present application, the device is classified into device types with different scopes of permissions allowed to be shared according to the management method and security level corresponding to the target device, and whether the target device is allowed to be shared with the target object is determined according to the different device types; in the case of determining that the target device is allowed to be shared with the target object, the target permission scope of the target device to be shared with the target object is determined, and then the usage permission of the target device within the target permission scope can be shared with the target object. Through the embodiment of the present application, the problem of cumbersome operation procedures of the technical solution in the related art that relies on the method of creating a new home group to realize device sharing between users is solved. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

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

[0020] Figure 2 is a flow chart of a device sharing method according to an embodiment of the present application;

[0021] Figure 3 is a flow chart of a device sharing method according to an optional embodiment of the present application;

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

[0023] Figure 5 This is a structural block diagram of a sharing device of a device according to an embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0026] According to one aspect of the embodiment of the present application, a device sharing method is provided. The device sharing method is widely used in smart home (Smart Home), smart home, smart home device ecology, smart residential (Intelligence House) ecology and other whole-house intelligent digital control application scenarios. Optionally, Figure 1 This is a hardware environment diagram of a device sharing method according to an embodiment of the present application. In this embodiment, the device sharing method can be applied to a module in a home appliance. The module can be applied to, for example, Figure 1 In the hardware environment shown in FIG. 1 , a home appliance 102 and a server 104 are formed. Figure 1 As shown, the server 104 is connected to the home appliance 102 via a network, and can be used to provide services (such as application services, etc.) for the node or the client installed on the node. A database can be set up on the server or independently of the server to provide data storage services for the server 104. Cloud computing and / or edge computing services can be configured on the server or independently of the server to provide data computing services for the server 104.

[0027] The aforementioned network may include, but is not limited to, at least one of the following: a wired network and a wireless network. The aforementioned wired network may include, but is not limited to, at least one of the following: a wide area network, a metropolitan area network, and a local area network. The aforementioned wireless network may include, but is not limited to, at least one of the following: Wi-Fi (Wireless Fidelity) and Bluetooth. The home appliance 102 may include, but is not limited to, a smart air conditioner, a smart range hood, a smart refrigerator, a smart oven, a smart stove, a smart washing machine, a smart water heater, a smart washing machine, a smart dishwasher, a smart projector, a smart TV, a smart clothes drying rack, smart curtains, smart audio and video, a smart socket, a smart speaker, a smart fresh air device, smart kitchen and bathroom equipment, smart bathroom equipment, a smart sweeping robot, a smart window cleaning robot, a smart mopping robot, a smart air purifier, a smart steamer, a smart microwave oven, a smart kitchen treasure, a smart purifier, a smart water dispenser, a smart door lock, and the like.

[0028] In this embodiment, a device sharing method is provided, which is applied to the above module. Figure 2 : is a flow chart of a device sharing method according to an embodiment of the present application, the process comprising the following steps:

[0029] Step S202: determining the device type of the target device based on 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 with the target object based on the device type of the target device, wherein the scope of permission allowed for sharing varies for devices of different device types;

[0030] Wherein, when it is determined that the management mode corresponding to the target device is capable of being managed separately, the target device is determined as an exclusive device;

[0031] When it is determined that the management mode corresponding to the target device requires unified management, the target device is determined to be a group device. In this case, it indicates that the target device is a group of devices rather than a single device.

[0032] In the case where it is determined that the target device is the exclusive device, determining a security level of the target device, and determining a device type of the target device according to the security level, wherein the device type of the target device determined according to the security level includes: a device of a first security level, a device of a second security level, and a device of a third security level;

[0033] In the case that the target device is determined to be a group device, the group device is determined as the device type of the target device.

[0034] That is, the device types in the embodiment of the present application may include: devices of the first security level, devices of the second security level, devices of the third security level, and group devices.

[0035] The above-mentioned first security level equipment may be equipment with lower risks;

[0036] The second security level device may be a high-security device with a certain degree of sensitivity, for example, a device that may contain personal privacy data;

[0037] The device at the third security level may 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 with the target object, determine a target permission range of the target device to be shared with the target object;

[0039] Step S206: Share the usage authority of the target device within the target authority range with the target object.

[0040] Through the above steps, the device type of the target device is determined according to the management method and security level corresponding to the target device, and the device type of the target device determines whether the target device is allowed to be shared with the target object. The scope of permissions allowed to be shared for devices of different device types is different; when it is determined that the target device is allowed to be shared with the target object, the target permission scope of the target device to be shared with the target object is determined, and the usage permission of the target device within the target permission scope is shared with the target object. That is to say, the embodiment of the present application classifies the devices into device types with different scopes of permissions allowed to be shared according to the management method and security level corresponding to the target device, and determines whether the target device is allowed to be shared with the target object according to different device types; when it is determined that the target device is allowed to be shared with the target object, the target permission scope of the target device to be shared with the target object is determined, and then the usage permission of the target device within the target permission scope can be shared with the target object. Through the embodiment of the present application, the problem of cumbersome operation procedures of the technical solution in the related art that relies on the method of creating a new home group to realize device sharing between users is solved.

[0041] Optionally, the above-mentioned step S202 determines whether the target device is allowed to be shared with the target object based on the device type of the target device, including: when it is determined that the device type of the target device is a device of the first security level, or a device of the second security level, or a group device, determining that the target device is allowed to be shared with the target object; when it is determined that the device type of the target device is a device of the third security level, determining that the target device is not allowed to be shared with the target object, wherein the device types include: devices of the first security level, devices of the second security level, devices of the third security level and the group device.

[0042] It is understood that devices at the first security level may be low-risk devices that do not involve sensitive information. These devices are allowed to be shared with the target because they pose relatively low security risks and will not pose a significant privacy or security threat to the initiating user.

[0043] Second-level security devices may contain sensitive information or have high functional safety requirements. Despite the risks, these devices are still allowed to be shared. When sharing, the receiving user's access rights are restricted based on the device's characteristics and the initiator's settings to protect the device's sensitive information.

[0044] Group devices: 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 groups or non-associated groups.

[0045] Devices at the third security level are considered to have the highest security level and may be involved in highly sensitive or critical operations. Sharing these devices with the intended recipient is prohibited to maximize device security and data privacy. If sharing is necessary, additional security measures, such as secondary confirmation, advanced encryption, or real-name authentication, may be required to ensure safe and controllable sharing.

[0046] Optionally, the above-mentioned step S204 of determining the target permission range of the target device to be shared with the target object includes: when it is determined that the device type of the target device is a device of the first security level, determining all permission ranges corresponding to the target device, and determining the target permission range within the all permission ranges; when it is determined that the device type of the target device is a device of the 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 partial permission range of all permission ranges corresponding to the target device; when it is determined that the device type of the target device is 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] It is understood that, if it is determined that the device is of the first security level, all permission ranges of the target device can be listed to form a list of all permission ranges. Subsequently, the initiating user selects the permissions he wants to share with the target object based on the list of all permission ranges, thereby determining the target permission range.

[0048] When it is determined that the device is of the second security level, the permissions suitable for sharing will be determined from all permission scopes to generate a first permission scope list, where the first permission scope may include, for example: access rights to non-sensitive data in the target device and usage rights to basic functions of the target device, etc. Then, the initiating user can select usage rights in the target permission scope in the first permission scope list for sharing, ensuring that sensitive information or functions are not inadvertently leaked.

[0049] When it is determined that the target device is a group device, it is determined whether the group device is an associated group device or a non-associated group device, and the target permission range is determined according to whether the target device is an associated group device or a non-associated group device.

[0050] Specifically, the target permission range is determined according to whether the target device is an associated group device, including: when it is determined that the target device is an associated group device, determining a first main device and one or more first sub-devices in the target device; determining a second permission range that the first main device is allowed to be shared to the target object, and determining the target permission range corresponding to the first main device and the one or more first sub-devices within the second permission range; when it is determined that the target device is a non-associated group device, determining a second main device and one or more second sub-devices in the target device; respectively determining a third permission range that the second main 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 respectively determining a fifth permission range corresponding to the second main 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] It is understood that when the target device is determined to be an associated group device, the first main device and the first sub-device are first identified. Secondly, the sharing permissions of the first main device are determined: based on the type and security level of the first main device, the second permission range allowed for the first main device to be shared with the target object is determined. The second permission range is to filter out the set of permissions applicable to sharing from all permissions of the first main device. Finally, the permissions are extended to the first sub-devices: within the second permission range, these permissions are applied to all first sub-devices in the associated group device. In other words, once the target object obtains the use permissions of the first main device, it will automatically obtain the same use permissions for all first sub-devices following the first main device, without the need for a separate sharing process.

[0052] In the case of determining that the target device is a non-associated group device, first, it is necessary to identify the second main device and the second sub-device; secondly, the permissions of the second main device and the second sub-device are determined: the third permission range that the second main device is allowed to be shared with the target object, and the fourth permission range that one or more second sub-devices are allowed to be shared with the target object are determined respectively. The determination of the third permission range and the fourth permission range is also based on the respective device types and security levels, as well as the designation of the first object (i.e., the initiator user); finally, independent permission allocation: when determining the permissions of non-associated group devices, the permissions of the second main device will not be automatically extended to the second sub-device. In other words, the target object's permission to use the second main device and the permission to use the second sub-device need to be obtained through a separate sharing process. The fifth permission range corresponding to the second main device is determined within the third permission range, and the sixth permission range corresponding to the second sub-device is determined within the fourth permission range. The final target permission range consists of the fifth permission range and the sixth permission range.

[0053] Optionally, before sharing the usage rights of the target device within the target authority scope with the target object in the above-mentioned step S206, the method also includes: determining 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; determining whether the target object is the same object as the first object that has management authority over the target device; if it is determined that the target object and the first object are the same object, prohibiting the sharing of the usage rights of the target device within the target authority scope with the target object; if it is determined that 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 family group; if it is determined that the target object and the first object are in the same family group, prohibiting the sharing of the usage rights of the target device within the target authority scope with the target object; if it is determined that the target object and the first object are not in the same family group, allowing the sharing of the usage rights of the target device within the target authority scope with the target object.

[0054] It is understandable that before sharing the target permission range with the target object, it is necessary to determine the target object and whether the sharing conditions are met. Specifically:

[0055] Determine the target object: The target object may be determined based on, but not limited to, the target object's contact information, an account number in a specific application (target application), or identification information of the target object.

[0056] Determine the relationship between the target object and the first object: Determine whether the first object and the target object are the same object: Check whether the target object is the same object as the first object that has management permissions on the target device. If so, the sharing operation will be prohibited because the target object already has management permissions and no further sharing is required.

[0057] Determine whether the target object and the first object are in the same home group: If the target object and the first object are not the same object, further check whether they are in the same home group. Users in the same home group typically already have permission to use shared devices. Therefore, if the target object and the first object are in the same home group, it indicates that the target object already has management permissions for the target device and does not need to share. Therefore, sharing will be prohibited to avoid duplicate permissions and conflicts.

[0058] Confirmation of sharing conditions: Conditions for allowing sharing: Sharing the target device's usage permissions within the target's permission range to the target object will be allowed only after it is confirmed that the target object and the first object are neither the same person nor in the same family group.

[0059] In summary, the user database can be used to compare the information of the first and target parties, including but not limited to mobile phone numbers, account information, and family group identifiers, to verify their identities and relationship. Based on the verified user relationship, a logical judgment is performed to determine whether sharing is allowed. If the target party is the same person or in the same family group, the sharing process is blocked; otherwise, the sharing operation is allowed to proceed.

[0060] Once the sharing conditions are met, a sharing invitation can be sent to the target object through the target channel (such as SMS, in-app notification or email, etc.), 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 authority scope with the target object in the above-mentioned step S206, the method further includes: stopping sharing the usage rights of the target device within the target authority scope with the target object under at least one of the following conditions: stopping sharing the usage rights of the target device within the target authority scope with the target object when the first object and / or the target object actively ends sharing the target device, wherein the first object is an object that has management authority over the target device; stopping sharing the usage rights of the target device within the target authority scope with 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 exits the target family group.

[0062] It is understandable that after the usage rights within the target permission range are shared with the target object, sharing with the target device needs to be stopped if at least one of the following conditions is met:

[0063] (1) Actively end sharing:

[0064] 1) Active Termination by the First Party: Assume that the first party, who has administrative rights to the target device, decides to terminate sharing of the target device. This intention may stem from the fact that the device is no longer needed, the shared party has behaved inappropriately, or other personal reasons. In this case, the target party will immediately cease sharing the target device's usage rights within the target's scope of rights, and all relevant permissions will be revoked to protect the security of the device and data.

[0065] 2) Target User Active Termination: If the target user no longer needs to use the target device or wishes to terminate sharing for their own safety, they can initiate a request to terminate sharing. Upon receiving such a request, the target device's usage permissions will be terminated immediately, ensuring that user permissions remain consistent with their needs.

[0066] (2) Automatically terminate sharing:

[0067] 1) The target device is removed from the management of the target home group: If the target device is removed from the device group managed by the home group corresponding to the first object, the usage rights of the target device within the target permission scope will be automatically stopped from being shared with the target object.

[0068] 2) The first subject exits the home group: If the first subject decides to exit the target home group, this will also trigger the automatic cessation of sharing the target device usage rights to all target subjects currently sharing the target device.

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

[0070] In addition, the situation of family members of the target family group where the first object exists is monitored, and when it is determined that the first object has exited the target family group, the sharing termination process is triggered.

[0071] Permission revocation and notification operations can be performed. When sharing is terminated, the target object's permission record will be cleared from the database, ensuring 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, informing them that sharing has been terminated and the possible reason for the termination, to enhance user transparency and trust in system operations. The database is used to store permission records.

[0072] Optionally, after determining the target permission range of the target device to be shared to the target object in the above step S204, the method further includes: when a first object sends a sharing link to the target object, determining whether the sharing link is invalid in one of the following ways, wherein the sharing link is used to indicate the target object's sharing of the target device, and the first object is an object with management authority over the target device: 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 is changed from allowed to be shared to not allowed to be shared, determining that the sharing link is invalid; when the target object refuses to accept the sharing link, determining that the sharing link is invalid.

[0073] The conditions for the shared connection to fail may include:

[0074] Failure to accept the sharing link within the target time period: If the target object does not respond to accept the device's sharing permissions within the preset target time period after the first object sends the sharing link to the target object, the sharing link will be deemed invalid. The above technical solution can prevent sharing invitations from being pending for a long time. At the same time, it also takes into account that the target object may fail to accept the sharing within the specified time due to various reasons (such as not checking the message in time, decision-making hesitation, etc.), thereby automatically terminating the validity of the sharing link, freeing up system resources and reducing potential confusion in permission management.

[0075] Sharing is not allowed due to changes in device permissions: Even if the target object has accepted the use permission of the target device through the sharing link, if the state of any use permission of the target device within the target permission range changes from allowing sharing to not allowing sharing, the original sharing link will be deemed invalid. This may be because the device owner (ie the first object) has adjusted the permission settings or the system policy has been updated, resulting in the original sharing permission no longer being applicable. At this point, the target object will lose control or use permission of the device, and the original sharing link will become invalid to prevent unauthorized access or data leakage.

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

[0077] In order to better understand the process of the sharing method of the above-mentioned device, the implementation method flow of the sharing of the above-mentioned device is described below in combination with an optional embodiment, but it is not used to limit the technical solution of the embodiment of this application.

[0078] Figure 3 is a flow chart of a device sharing method according to an optional embodiment of the present application, such as Figure 3 As shown:

[0079] The device sharing method of an optional embodiment of the present application involves a server (may involve one or more), an initiator user terminal (i.e., a first object) and a recipient user terminal (i.e., a target object);

[0080] The initiator user terminal is a user who has management authority over the target device and shares the target device with others; the receiver user terminal is a user who accepts the target device and has the right to use the target device after accepting the sharing.

[0081] Step S301, the server configures the device type;

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

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

[0084] (2) High-security devices can be shared with other users by one or more users with administrative privileges, but the recipient user is limited in the scope of their use of the high-security device's functions;

[0085] (3) Group device: A group device includes one or more types of associated group devices and non-associated group devices, specifically:

[0086] 1) Associated group devices: 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 recipient users. When a recipient user obtains permission to use the master device in the associated group, it will also obtain permission to use one or more sub-devices that follow the master device in the associated group. When a recipient user loses permission to use the master device in the associated group, it will also lose permission to use one or more sub-devices that follow the master device in the associated group.

[0087] 2) Non-associated group devices: These include a primary device (i.e., a second primary device) and one or more secondary devices (i.e., secondary secondary devices) that follow the primary device. The primary device in a non-associated group can be shared with a recipient user by one or more initiating users. However, when a recipient user obtains access to the primary device in an associated group, they will not simultaneously obtain access to the one or more secondary devices that follow the primary device in the non-associated group. When a recipient 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 range of invalid devices allows the system to adjust dynamically.

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

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

[0091] Step S304, the server verifies the device type;

[0092] If the device type is determined to be other devices (i.e., abnormal situation), step S305 is executed;

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

[0094] Step S305, prompting abnormal situation;

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

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

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

[0098] If the user identification is determined to be abnormal, step S308 is executed;

[0099] If the user identification is determined to be normal, step S309 is executed;

[0100] Step S308: The initiating user terminal prompts an abnormality;

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

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

[0103] Step S311: The server updates the process status to: pending acceptance;

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

[0105] Step S313: The receiving user terminal selects whether to accept the sharing;

[0106] If the receiving user selects other (for example, the receiving user chooses not to accept), step S314 is executed;

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

[0108] Step S314: The server updates the process status to: expired;

[0109] Step S315: The server updates the process status to: Accepted;

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

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

[0112] The initiating user terminal may also execute step S318, device authority change / cancel sharing and other operations. If it is determined that the receiving user terminal executes step S318, step S314 is executed.

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

[0114] The initiator user can share the device for which he has management permissions with the recipient user:

[0115] 1) If the initiator and recipient are in the same family group, the recipient already has device usage permissions and higher permissions, so there is no need to grant the recipient permissions 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 designated target user is the same as the initiator user, there is no need to grant the user permission again because the initiator user already has device management permissions;

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

[0119] Shared Acceptable Use Rules:

[0120] 1) After the recipient user accepts the device usage permission of the target device, the target device is added to the recipient user's home group as an independent group;

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

[0122] 3) If the initiator user's management rights to the target device change, the recipient user's rights to the device remain unchanged;

[0123] 4) If the relationship between the target device and the home group co-existing with the initiating user changes, the receiving user's permission to use 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 recipient user has accepted the target device's usage rights, and the target device's usage rights have not been automatically revoked due to any changes;

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

[0128] 1) The recipient user accepts the target device's usage rights, but the target device's usage rights are automatically revoked due to a change;

[0129] 2) The recipient user does not accept the target device's usage permission, but the target device's usage permission invitation becomes invalid due to a change;

[0130] (3) Pending Acceptance: The target device usage permission invitation (i.e., shared link) is effective, but the recipient user has not yet accepted the target device usage permission invitation.

[0131] The optional embodiment of the present application is an apparatus and method for realizing device sharing based on the user dimension, including initiating sharing, accepting sharing, using shared devices, and the logic of changing the state of the sharing relationship throughout the entire process. At the same time, the sharing function realized by configuring the device type through the system can take into account flexibility, stability, and security. That is, the optional embodiment of the present application establishes a device sharing model based on the user dimension, which is compatible with the existing family group sharing model; and formulates detailed and reasonable sharing rules, imposes sharing restrictions and refines rules for different device types, ensuring the security, stability, and convenience of the sharing and use process; at the same time, it supports multiple ways of initiating and accepting sharing, expands channels, and is compatible with diverse social and usage habits.

[0132] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it 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 the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.

[0133] Figure 5 is a structural block diagram of a sharing device of a device according to an embodiment of the present application; Figure 5 As shown, including:

[0134] A first determining module 52 is configured to determine a device type of the target device based on a management mode corresponding to the target device and a security level of the target device, and determine whether the target device is allowed to be shared with a target object based on the device type of the target device, wherein different device types have different permission ranges for being shared;

[0135] A second determining module 54 is configured to determine a 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 configured to share the usage permission of the target device within the target permission range with the target object.

[0137] Through the above-mentioned device, the device type of the target device is determined according to the management method and security level corresponding to the target device, and the device type of the target device determines whether the target device is allowed to be shared with the target object. The scope of permissions allowed to be shared for devices of different device types is different; when it is determined that the target device is allowed to be shared with the target object, the target permission scope of the target device to be shared with the target object is determined, and the usage permission of the target device within the target permission scope is shared with the target object. That is to say, the embodiment of the present application classifies the devices into device types with different scopes of permissions allowed to be shared according to the management method and security level corresponding to the target device, and determines whether the target device is allowed to be shared with the target object according to different device types; when it is determined that the target device is allowed to be shared with the target object, the target permission scope of the target device to be shared with the target object is determined, and then the usage permission of the target device within the target permission scope can be shared with the target object. Through the embodiment of the present application, the problem of cumbersome operation procedures of the technical solution of relying on the method of creating a new home group to realize device sharing between users in the related art is solved.

[0138] In an exemplary embodiment, the first determination module 52 is further used to determine that the target device is allowed to be shared with the target object when it is determined that the device type of the target device is a device of the first security level, or a device of the second security level, or a group device; and to determine that the target device is not allowed to be shared with the target object when it is determined that the device type of the target device is a device of the third security level, wherein the device types include: devices of the first security level, devices of the second security level, devices of the third security level, and the group device.

[0139] In an exemplary embodiment, the second determination module 54 is further used to determine all permission ranges corresponding to the target device when it is determined that the device type of the target device is a device of the first security level, and determine the target permission range within all permission ranges; when it is determined that the device type of the target device is a device of the second security level, determine the first permission range corresponding to the target device, and determine the target permission range within the first permission range, wherein the first permission range is a partial permission range of all permission ranges corresponding to the target device; when it is determined 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 range based on whether the target device is an associated group device.

[0140] In an exemplary embodiment, the second determination module 54 is further used to, when it is determined that the target device is an associated group device, determine a first main device and one or more first sub-devices in the target device; determine a second permission range that the first main device is allowed to be shared to the target object, and determine the target permission range corresponding to the first main device and the one or more first sub-devices within the second permission range; when it is determined that the target device is a non-associated group device, determine a second main device and one or more second sub-devices in the target device; respectively determine a third permission range that the second main 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 respectively determine a fifth permission range corresponding to the second main 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 also used 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; determining whether the target object is the same object as the first object that has management authority over the target device; if it is determined that the target object and the first object are the same object, prohibiting the sharing of the usage authority of the target device within the target authority scope to the target object; if it is determined that 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 family group; if it is determined that the target object and the first object are in the same family group, prohibiting the sharing of the usage authority of the target device within the target authority scope to the target object; if it is determined that the target object and the first object are not in the same family group, allowing the sharing of the usage authority of the target device within the target authority scope to the target object.

[0142] In an exemplary embodiment, the sharing module 56 is also used for the sharing module 56 to stop sharing the usage rights of the target device within the target authority scope to the target object when at least one of the following conditions is met: when the first object and / or the target object actively ends sharing the target device, stop sharing the usage rights of the target device within the target authority scope to the target object, wherein the first object is an object that has management authority over the target device; 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 exits the target family group, stop sharing the usage rights of the target device within the target authority scope to the target object.

[0143] In an exemplary embodiment, the sharing module 56 is also used 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 indicate the target object's sharing of the target device, and the first object is an object with management authority over the target device: when the target object does not accept the sharing link within the target time period, the sharing link is determined to be invalid; when the target object has accepted the sharing link and any usage permission of the target device within the target permission scope is changed from allowing sharing to not allowing sharing, the sharing link is determined to be invalid; when the target object refuses to accept the sharing link, the sharing link is determined to be invalid.

[0144] An embodiment of the present application further provides a storage medium, which includes a stored program, wherein the program executes any of the above methods when it is run.

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

[0146] S1, determining the device type of the 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 with the target object according to the device type of the target device, wherein the scope of permission allowed for sharing of devices of different device types is different;

[0147] S2, when it is determined that the target device is allowed to be shared with the target object, determining a target permission range of the target device to be shared with the target object;

[0148] S3: Share the usage permission of the target device within the target permission range with the target object.

[0149] An embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one 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 may be configured to execute the following steps through a computer program:

[0152] S1, determining the device type of the 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 with the target object according to the device type of the target device, wherein the scope of permission allowed for sharing of devices of different device types is different;

[0153] S2, when it is determined that the target device is allowed to be shared with the target object, determining a target permission range of the target device to be shared with the target object;

[0154] S3: Share the usage permission of the target device within the target permission range with the target object.

[0155] An embodiment of the present application further provides a computer program product, including a computer program, which is used by a processor to execute the steps in any of the above method embodiments.

[0156] Optionally, in this embodiment, the computer program product may be processed by a processor to execute the following steps:

[0157] S1, determining the device type of the 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 with the target object according to the device type of the target device, wherein the scope of permission allowed for sharing of devices of different device types is different;

[0158] S2, when it is determined that the target device is allowed to be shared with the target object, determining a target permission range of the target device to be shared with the target object;

[0159] S3: Share the usage permission of the target device within the target permission range with the target object.

[0160] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store program codes.

[0161] Optionally, specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0162] Obviously, those skilled in the art should understand that the modules or steps of the present application described above can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices. Alternatively, they can be implemented using program code executable by the computing device, so that they can be stored in a storage device and executed by the computing device. In some cases, the steps shown or described can be performed in a different order than herein, or they can be made into separate integrated circuit modules, or multiple modules or steps can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0163] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A device sharing method, characterized in that: include: Determining the device type of the 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 with the target object according to the device type of the target device, wherein the scope of permissions allowed to be shared for devices of different device types is different; if it is determined that the target device is allowed to be shared with the target object, determining the target permission scope of the target device to be shared with the target object; The usage permission of the target device within the target permission range is shared with the target object.

2. The device sharing method according to claim 1, characterized in that: Determining whether the target device is allowed to be shared with the target object according to the device type of the target device includes: In a case where it is determined that the device type of the target device is a device of the first security level, a device of the second security level, or a group device, determining that the target device is allowed to be shared with the target object; When it is determined that the device type of the target device is 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 types include: devices of the first security level, devices of the second security level, devices of the third security level and the group device.

3. The device sharing method according to claim 1, characterized in that: Determining a target permission scope of the target device to be shared with the target object includes: In the case where it is determined that the device type of the target device is a device of the first security level, determining all permission ranges corresponding to the target device, and determining the target permission range within all permission ranges; When it is determined that the target device is a device of the 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 partial permission range of all permission ranges corresponding to the target device; In the case that it is determined that the device type of the target device is a group device, it is determined whether the target device is an associated group device, and the target permission range is determined according to whether the target device is an associated group device.

4. The device sharing method according to claim 3, characterized in that: Determining the target permission range according to whether the target device is an associated group device includes: In a case where it is determined that the target device is an associated group device, determining a first main device and one or more first sub-devices in the target device; Determine a second permission range of the first master device that is allowed to be shared with 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; In a case where it is determined that the target device is a non-association group device, determining a second main device and one or more second sub-devices in the target device; Determine respectively the third permission range within which the second main device is allowed to be shared with the target object and the fourth permission range within which the one or more second sub-devices are allowed to be shared with the target object, and determine respectively the fifth permission range corresponding to the second main device within the third permission range and the 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.

5. The device sharing method according to claim 1, characterized in that: Before sharing the usage permission of the target device within the target permission scope with the target object, the method further includes: determining the target object through a target path, wherein the target path includes at least one of the following: contact information of the target object, an account number of the target object in a target program, and identification information corresponding to the target object; determining whether the target object and a first object having 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, prohibiting the use permission of the target device within the target permission scope from being shared with the target object; In a case where it is determined that 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 family group; If it is determined that the target object and the first object are in the same family group, prohibiting the use permission of the target device within the target permission scope from being shared with the target object; In a case where it is determined that the target object and the first object are not in the same family group, the usage permission of the target device within the target permission range is allowed to be shared with the target object.

6. The device sharing method according to claim 1, characterized in that: After sharing the usage permission of the target device within the target permission scope with the target object, the method further includes: stopping sharing the usage permission of the target device within the target permission scope with the target object in at least one of the following situations: When the first object and / or the target object actively ends sharing of the target device, stopping sharing the usage permission of the target device within the target permission scope with the target object, wherein the first object is an object having management permission for the target device; When 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 exits the target home group, stop sharing the usage rights of the target device within the target permission scope with the target object.

7. The device sharing method according to claim 1, characterized in that: After determining a target permission range to be shared from the target device to the target object, the method further includes: When a first object sends a sharing link to the target object, determining whether the sharing link is invalid is performed in one of the following ways, wherein the sharing link is used to indicate sharing of the target device by the target object, and the first object is an object having management authority over the target device: If the target object does not accept the shared link within a target time period, determining that the shared 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 being allowed to be shared to not being shared, determining that the sharing link is invalid; In a case where the target object refuses to accept the sharing link, it is determined that the sharing link is invalid.

8. A device sharing apparatus, characterized in that: include: a first determining module, configured to determine a device type of the target device according to a management mode corresponding to the target device and a security level of the target device, and determine whether the target device is allowed to be shared with a target object according to the device type of the target device, wherein different device types have different permission scopes for being shared; a second determining module, configured to, when it is determined that the target device is allowed to be shared with the target object, determine a target permission range for the target device to be shared with the target object; A sharing module is used to share the usage permission of the target device within the target permission range with the target object.

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

10. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 7 through the computer program.

Images