Equipment cooperation method based on label sharing

Through the device collaboration method based on tag sharing, the complex problem of device management permission control is solved, the flexible classification and sharing of devices is realized, management and collaboration efficiency is improved, and security and compliance are ensured.

CN119094584APending Publication Date: 2024-12-06XIAMEN MILESIGHT IOT CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411177928.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-26
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Existing equipment management technologies cannot accurately control equipment management permissions, resulting in complex equipment identification, difficult classification, misclassification, and incomplete management, affecting business processes and collaboration efficiency.

Method used

Using a device collaboration method based on tag sharing, users assign tags to devices and upload them to cloud services. Cloud services build tag device mapping tables, and use device sharing and permission control based on tags to realize the functions, location or department classification and grouping of devices.

Benefits of technology

It realizes flexible classification and sharing of equipment, automated permission control, improves management efficiency and collaboration efficiency, and reduces user operation burden and error rate.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094584A_ABST
    Figure CN119094584A_ABST
Patent Text Reader

Abstract

The invention relates to an equipment cooperation method based on label sharing. The method comprises the following steps: a user uploads an equipment label to a cloud service; the cloud service constructs a label equipment mapping table based on the received equipment labels corresponding to the equipment; when the user needs to share, the sharing information is uploaded to the cloud service; the cloud service searches for all devices corresponding to the device label needing to be shared from a label device mapping table based on the sharing information, and shares the found devices to the user account to be shared; when the cloud service receives a device access request sent by a user, whether the user is a binding user of a device corresponding to the device access request is firstly judged, if not, whether the device exists under an account of the user is judged, and if yes, the permission of the user for accessing the sharing device is limited based on the access permission in the sharing information corresponding to the device. And ending equipment sharing of the to-be-shared user based on the expiration time. According to the invention, the equipment can be better managed in a centralized manner.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of device management, and in particular to a device collaboration method based on tag sharing. Background Art

[0002] Currently, the management of device collaboration is limited and the management rights of devices cannot be accurately controlled. Specifically, there are the following shortcomings:

[0003] (1) Users need to rely on specific device names or features to identify and find devices, which becomes complicated in large-scale device management, especially when the number of devices is large or they have similar features.

[0004] (2) It is difficult to effectively classify and group equipment according to function, location or other attributes, which affects management efficiency and workflow.

[0005] (3) Equipment is easily misclassified or missed, resulting in incomplete or inaccurate management, which in turn affects the correctness of business processes and decisions.

[0006] (4) Users need to spend a lot of time and energy to find, identify and manage devices, which may reduce user experience and increase workload and error rate.

[0007] (5) It is difficult for team members to accurately find the equipment they need to share or collaborate on, which reduces the team's collaboration efficiency and flexibility. Summary of the invention

[0008] In order to solve the above problems, the present invention proposes a device collaboration method based on tag sharing.

[0009] The specific plan is as follows:

[0010] A device collaboration method based on tag sharing includes the following steps:

[0011] The user assigns a device tag to each device bound to it, and uploads the device tag corresponding to each device to the cloud service;

[0012] The cloud service constructs a tag device mapping table based on the device tags corresponding to the received devices;

[0013] When a user needs to share a bound device, the user uploads the sharing information to the cloud service; the sharing information includes the device tag to be shared, the user to be shared, the access permission and the expiration time;

[0014] Based on the reported sharing information, the cloud service searches for all devices corresponding to the device tags to be shared from the tag device mapping table, and shares the found devices to the user account to be shared;

[0015] When the cloud service receives a device access request from a user, it first determines whether the user is a bound user of the device corresponding to the device access request. If not, it determines whether the device exists under the user's account. If so, it limits the user's access to the shared device based on the access permissions in the corresponding sharing information of the device, and terminates the device sharing of the sharing user based on the expiration time.

[0016] Furthermore, the shared information includes multiple device tags, and each device tag has its corresponding access rights and expiration time.

[0017] Furthermore, the equipment tag is set according to the function, location or department of the equipment.

[0018] Furthermore, the label device mapping table records the correspondence between the unique code of the device and the device label.

[0019] Furthermore, when the cloud service receives a device access request sent by a user, before determining whether the user is a bound user of the device corresponding to the device access request, it also includes determining whether the device exists based on the device unique code in the device access request; if it exists, continue with subsequent operations; if it does not exist, return a corresponding error identifier.

[0020] Furthermore, the mode of ending the device sharing of the user to be shared based on the expiration time is performed by creating a scheduled task, and the scheduled time in the scheduled task is the expiration time.

[0021] The present invention adopts the above technical solution and has the following beneficial effects:

[0022] (1) Allows devices to be classified and organized according to different attributes, such as function, location, department, etc. This flexibility allows devices to be grouped and shared as needed, helping to better organize and manage device resources.

[0023] (2) Users or administrators do not need to manually configure permissions. The cloud service automatically controls device access rights based on preset rules to ensure security and compliance.

[0024] (3) Centrally manage devices under one or more tags for unified control and monitoring. Users can manage device access rights and configurations through management tags, thereby achieving centralized management of devices.

[0025] (4) Team members can share devices under specific tags as needed, thereby promoting collaboration and resource sharing within the team. Multi-tag sharing ensures that team members can access the devices they need, enhancing collaboration efficiency and work fluency.

[0026] (5) In a complex working environment, devices may have different functions, uses, and limitations. This embodiment can help users and administrators better understand and manage these complexities and perform device classification and control in a targeted manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 Shown is an overall flow chart of an embodiment of the present invention.

[0028] Figure 2 Shown is a flow chart of the sharing process in this embodiment. DETAILED DESCRIPTION

[0029] To further illustrate various embodiments, the present invention provides drawings. These drawings are part of the disclosure of the present invention, which are mainly used to illustrate the embodiments and can be used in conjunction with the relevant descriptions in the specification to explain the operating principles of the embodiments. With reference to these contents, ordinary technicians in this field should be able to understand other possible implementations and advantages of the present invention.

[0030] The present invention will now be further described with reference to the accompanying drawings and specific implementation methods.

[0031] The embodiment of the present invention provides a device collaboration method based on tag sharing, such as Figure 1 and Figure 2 As shown, the method comprises the following steps:

[0032] S1: The user assigns a device tag to each device bound to the user, and uploads the device tag corresponding to each device to the cloud service.

[0033] Devices are devices that can be remotely operated, such as sensors and switches. The permissions corresponding to the devices include read permissions and write permissions.

[0034] Before uploading device tags, you need to add the device to the cloud service and store the binding relationship between the user and the device.

[0035] Device tags can be set based on the device's function, location, department, and other characteristics. When assigning device tags to newly bound devices, the device tags used can be the original tags or newly added tags. Each device can have one or more device tags, and there is no limit here. Users can add, reduce, or change device tags for devices as needed.

[0036] S2: The cloud service constructs a tag device mapping table based on the device tags corresponding to the received devices.

[0037] In this embodiment, after the cloud service receives the device tag corresponding to the device, it matches the unique code of the device with the device tag to form a tag device mapping table. Since a device can have multiple tags, the unique code of a device in the tag device mapping table may correspond to multiple device tags.

[0038] S3: When a user needs to share the bound device, the user uploads the sharing information to the cloud service. The sharing information includes the device label to be shared, the user to be shared, the access permission and the expiration time.

[0039] Users can log in to the cloud service to configure and upload shared information.

[0040] The device tags that need to be shared can include one or more. The users to be shared can be one or more users or user groups. The access rights and expiration time are set according to the device tag, that is, all shared devices belonging to the same device tag have the same access rights and expiration time. The access rights and expiration time of the corresponding shared device are set for each device tag that needs to be shared. The expiration time is used to limit the end time of sharing. When the time reaches the expiration time, the sharing information expires, and the corresponding user to be shared has no permission to access the corresponding shared device. By setting different access rights for devices under different device tags, the security of the device and the confidentiality of data are guaranteed.

[0041] S4: The cloud service searches for all devices corresponding to the device tags to be shared from the tag device mapping table based on the reported sharing information, and shares the found devices to the user account to be shared.

[0042] When the found device is shared to the user account to be shared, not only the correspondence between the user to be shared and the device is recorded, but also a sharing message notification can be sent to the shared user so that the shared user can know and use it in time.

[0043] S5: When the cloud service receives a device access request from a user, it first determines whether the user is a bound user of the device corresponding to the device access request. If not, it determines whether the device exists under the user's account. If so, it limits the user's access to the shared device based on the access permissions in the corresponding sharing information of the device, and terminates the device sharing of the sharing user based on the expiration time.

[0044] When it is determined that the user is a bound user of the device corresponding to the device access request, the user is granted full authority to access the corresponding device.

[0045] When determining whether the device exists under the user's account, the result of sharing the found device to the user account to be shared in step S4 can be used to determine whether a device exists under the user's account based on the recorded correspondence between the user to be shared and the device to be shared.

[0046] When the device does not exist under the user's account, the user is prohibited from accessing the device.

[0047] In this embodiment, when the cloud service receives a device access request sent by a user, before determining whether the user is a bound user of the device corresponding to the device access request, it also includes determining whether the device exists based on the device unique code in the device access request; if so, continue with subsequent operations; if not, return a corresponding error identifier.

[0048] In this embodiment, the device sharing of the user to be shared is terminated based on the expiration time by creating a scheduled task, and the scheduled time in the scheduled task is the expiration time.

[0049] In this embodiment, permission control is implemented using AOP (Aspect-Oriented Programming) aspect annotations. It is necessary to annotate the interface that needs to control permissions, and specify the permission list that can access the interface and the device information that needs to be judged. This is mainly for single device operations or batch device operations to achieve precise control of device permissions.

[0050] Furthermore, when the cloud service receives a newly uploaded device tag, it determines whether the device tag belongs to a device tag that needs to be shared in the existing (i.e., not expired) sharing information. If so, the device corresponding to the newly uploaded device tag is shared to the corresponding user account to be shared. In this way, intelligent and automated sharing logic can be implemented without the need for additional user operations.

[0051] The embodiments of the present invention have the following beneficial effects:

[0052] (1) Allows devices to be classified and organized according to different attributes, such as function, location, department, etc. This flexibility allows devices to be grouped and shared as needed, helping to better organize and manage device resources.

[0053] (2) Users or administrators do not need to manually configure permissions. The cloud service automatically controls device access rights based on preset rules to ensure security and compliance.

[0054] (3) Centrally manage devices under one or more tags for unified control and monitoring. Users can manage device access rights and configurations through management tags, thereby achieving centralized management of devices.

[0055] (4) Team members can share devices under specific tags as needed, thereby promoting collaboration and resource sharing within the team. Multi-tag sharing ensures that team members can access the devices they need, enhancing collaboration efficiency and work fluency.

[0056] (5) In a complex working environment, devices may have different functions, uses, and limitations. This embodiment can help users and administrators better understand and manage these complexities and perform device classification and control in a targeted manner.

[0057] Although the present invention has been specifically shown and described in conjunction with the preferred embodiments, it should be understood by those skilled in the art that various changes may be made to the present invention in form and details without departing from the spirit and scope of the present invention as defined by the appended claims, all of which are within the scope of protection of the present invention.

Claims

1. A device collaboration method based on tag sharing, It is characterized in that The following steps are involved: The user assigns a device tag to each device bound to it, and uploads the device tag corresponding to each device to the cloud service; The cloud service constructs a tag device mapping table based on the device tags corresponding to the received devices; When a user needs to share a bound device, the user uploads the sharing information to the cloud service; the sharing information includes the device tag to be shared, the user to be shared, the access permission and the expiration time; Based on the reported sharing information, the cloud service searches for all devices corresponding to the device tags to be shared from the tag device mapping table, and shares the found devices to the user account to be shared; When the cloud service receives a device access request from a user, it first determines whether the user is a bound user of the device corresponding to the device access request. If not, it determines whether the device exists under the user's account. If so, it limits the user's access to the shared device based on the access permissions in the corresponding sharing information of the device, and terminates the device sharing of the sharing user based on the expiration time.

2. The device collaboration method based on tag sharing according to claim 1, Features: The shared information includes multiple device tags, each of which has its corresponding access rights and expiration time.

3. The device collaboration method based on tag sharing according to claim 1, Features: Equipment labels are set based on the function, location or department of the equipment.

4. The device collaboration method based on tag sharing according to claim 1, Features: The label device mapping table records the correspondence between the unique code of the device and the device label.

5. The device collaboration method based on tag sharing according to claim 1, Features: When the cloud service receives a device access request sent by a user, before determining whether the user is a bound user of the device corresponding to the device access request, it also includes determining whether the device exists based on the device unique code in the device access request; if so, continue with subsequent operations; if not, return a corresponding error identifier.

6. The device collaboration method based on tag sharing according to claim 1, Features: The method of ending the device sharing of the user to be shared based on the expiration time is performed by creating a scheduled task, and the scheduled time in the scheduled task is the expiration time.

7. The device collaboration method based on tag sharing according to claim 1, Features: It also includes, when the cloud service receives a newly uploaded device tag, determining whether the device tag belongs to a device tag that needs to be shared in the existing sharing information. If so, sharing the device corresponding to the newly uploaded device tag to the corresponding user account to be shared.