Unified equipment system adaptive to access of three-party equipment and access method and system

Abstract

The invention provides a unified equipment system adaptive to access of three-party equipment and an access method and system. The access method comprises the following steps: establishing an equipment model conforming to the capability of three-party equipment, and mounting function points of the three-party equipment to the equipment model; when the three-party equipment accesses the equipment management system, the equipment management system manages and controls the three-party equipment; when the equipment management system queries the three-party equipment in a cross-application mode, an equipment service interface is called, and the three-party equipment is queried according to the difference query condition. The system comprises modules corresponding to the steps of the method.

Description

Technical Field

[0001] This invention proposes a unified device system and access method and system adapted to the access of third-party devices, belonging to the field of device system access technology. Background Technology

[0002] When interfacing with third-party devices, due to the different device models from different manufacturers, after the devices are connected to the system, devices from different manufacturers of the same product category, different product categories from the same manufacturer, and different manufacturers of different product categories each have their own set of device models. These models have different description dimensions and functionalities, making unified management and application difficult. Based on the interfacing agreement documents provided by the third-party device manufacturers, relevant functions are developed according to the models and capabilities of the third-party devices, and applications are developed. Each type of device is connected and managed independently, and cross-application device queries call the application interface connected to the device to query relevant device information. The above-mentioned existing technology still has the following technical problems: 1. Each device has a different model, and each application system is connected and maintained separately, which is time-consuming and labor-intensive; 2. The description dimensions and functional points of each device are different. When developing using the device functions, the coupling with the device is relatively strong, and it is difficult to replace the same type of product. 3. When querying devices across applications, there are many calls to application interfaces, and the models are not consistent. Summary of the Invention

[0003] This invention provides a unified device system and access method and system adapted to third-party device access, in order to solve the above-mentioned technical problems existing in the prior art. The technical solution adopted is as follows: A method for accessing a unified device system that adapts to third-party device access, the method comprising: Establish a device model that meets the capabilities of third-party devices, and attach the functional points of third-party devices to the device model; When the third-party device is connected to the device management system, the device management system manages and controls the third-party device. When the device management system queries the third-party device across applications, it calls the device service interface and queries the third-party device according to the different query conditions.

[0004] Furthermore, a device model that conforms to the capabilities of the third-party devices is established, and the functional points of the third-party devices are attached to the device model, including: Establish a device model that conforms to the capabilities of the aforementioned third-party devices; The functional points corresponding to the third-party devices are broken down into data points; The data points are attached to the items corresponding to the attributes, actions, and events of the device model. At the same time, the device model records and displays the operating status and overview of the third-party devices.

[0005] Furthermore, the states, overviews, attributes, actions, and events are described as follows: Status refers to the operating status of the third-party devices, such as online / offline status, enabled status, etc. The overview refers to the static description of the third-party device, such as device ID, manufacturer, third-party device ID, IP address, port, transmission method, transmission protocol, etc. Attributes refer to the data points reported by the third-party devices during runtime, such as temperature values, on / off status, and facial images; data points are defined from nine dimensions: ID, code, name, data type, transmission direction, minimum value, maximum value, step size, and multiple. An action refers to an instruction sent to the aforementioned third-party devices, such as temperature setting or switch control. An event refers to a notification reported by the third-party device when it reaches a threshold, such as an alarm, a fault, or a notification.

[0006] Furthermore, when the third-party device is connected to the device management system, the device management system manages and controls the third-party device, including: After the third-party device is connected to the device management system, the device management system obtains the third-party device and its corresponding device information and device model by matching the third-party device ID and manufacturer, or by matching the device model ID. When the third-party device reports its functional points to the device management system, the device management system checks the reported content based on the data points defined in the device model. When the device management system parses the data points of the third-party devices, it queries the information corresponding to the data points based on the query data corresponding to the predefined data points.

[0007] Furthermore, the access method also includes: Real-time monitoring of the status changes of third-party devices; When the state of the third-party device changes, the changed state is taken as the target state, and the first change moment of the target state is recorded. Record the moment when the target state corresponding to the third-party device in the device model changes, and use this as the second change moment; Record the moment when the target status of the third-party equipment obtained from the equipment management system changes, and use this moment as the third change moment; The first time interval is obtained using the first and second change moments; The second time interval is obtained by using the second and third change moments; The third time interval is obtained by using the first and third change moments; The timeliness parameters for state change management are obtained using the first time interval, the second time interval, and the third time interval. The timeliness parameter for state change management is obtained through the following formula: ; in, S Indicates the timeliness parameters for status change management; T 01 , T 02 and T 03 These represent the first time interval, the second time interval, and the third time interval, respectively. k Let represent the adjustment coefficient, and the adjustment coefficient is obtained by the following formula: ; in, k Indicates the adjustment coefficient; T 01 , T 02 and T 03 These represent the first time interval, the second time interval, and the third time interval, respectively. The timeliness parameters for managing state changes are compared with preset timeliness parameter thresholds; When the timeliness parameter for managing status changes is lower than the preset timeliness parameter threshold, the device management system is deemed to have poor timeliness in managing the status changes of third-party devices, and an alarm for abnormal timeliness is triggered.

[0008] An access system for a unified device system adapted to third-party device access, the access system comprising: The model building module is used to build a device model that conforms to the capabilities of third-party devices and to attach the functional points of third-party devices to the device model. The management and control module is used to manage and control the third-party devices when they are connected to the device management system. The query module is used by the device management system to call the device service interface and query the third-party devices according to different query conditions when querying the third-party devices across applications.

[0009] Furthermore, the model building module includes: The equipment model building module is used to build equipment models that conform to the capabilities of the third-party equipment. The data point splitting module is used to split the function points corresponding to the third-party devices into data points; The recording and display module is used to attach the data points to the items corresponding to the attributes, actions, and events of the device model. At the same time, the device model records and displays the operating status and overview of the third-party devices.

[0010] Furthermore, the states, overviews, attributes, actions, and events are as follows: Status refers to the operating status of the third-party devices, such as online / offline status, enabled status, etc. The overview refers to the static description of the third-party device, such as device ID, manufacturer, third-party device ID, IP address, port, transmission method, transmission protocol, etc. Attributes refer to the data points reported by the third-party devices during runtime, such as temperature values, on / off status, and facial images; data points are defined from nine dimensions: ID, code, name, data type, transmission direction, minimum value, maximum value, step size, and multiple. An action refers to an instruction sent to the aforementioned third-party devices, such as temperature setting or switch control. An event refers to a notification reported by the third-party device when it reaches a threshold, such as an alarm, a fault, or a notification.

[0011] Furthermore, the management control module includes: The device information acquisition module is used to obtain the third-party device and its corresponding device information and device model after the third-party device is connected to the device management system. The device management system obtains the third-party device and its corresponding device information and device model based on the third-party device ID and manufacturer, or based on the device model ID. The content inspection and reporting module is used to inspect the reported content based on the data points defined in the device model when the third-party device reports its functional points to the device management system. The query control module is used by the device management system to query the information corresponding to the data points based on the predefined query data corresponding to the data points when parsing the data points of the third-party devices.

[0012] Furthermore, the access system also includes: The real-time monitoring module is used to monitor the status changes of third-party devices in real time. The first change moment acquisition module is used to take the changed state as the target state when the state of the third-party device changes, and to determine the first change moment when the target state changes. The second change moment acquisition module is used to record the change moment when the target state corresponding to the third-party device in the device model changes, and use it as the second change moment. The third change moment acquisition module is used to record the change moment when the target status corresponding to the third-party equipment obtained in the equipment management system changes, and use it as the third change moment. The first time interval acquisition module is used to acquire the first time interval using the first change moment and the second change moment; The second time interval acquisition module is used to acquire the second time interval using the second change time and the third change time. The third time interval acquisition module is used to acquire the third time interval using the first change moment and the third change moment; The status change management timeliness parameter acquisition module is used to acquire status change management timeliness parameters using the first time interval, the second time interval, and the third time interval. The timeliness parameter for state change management is obtained through the following formula: ; in, S Indicates the timeliness parameters for status change management; T 01 , T 02 and T 03 These represent the first time interval, the second time interval, and the third time interval, respectively. k Let represent the adjustment coefficient, and the adjustment coefficient is obtained by the following formula: ; in, k Indicates the adjustment coefficient; T 01 , T 02 and T 03 These represent the first time interval, the second time interval, and the third time interval, respectively. The parameter comparison module is used to compare the status change management timeliness parameters with preset timeliness parameter thresholds; The abnormal alarm module is used to determine that the timeliness of the device management system for managing the status changes of third-party devices is poor when the timeliness parameter of the status change management is lower than the preset timeliness parameter threshold, and to issue an abnormal timeliness alarm.

[0013] Beneficial effects of this invention: This invention proposes a unified device system and access method adapted to third-party device access. The system describes devices from five dimensions: state, overview, attributes, actions, and events, using a unified device model. It establishes a unified device model for all devices accessing the system, solving the problem of inconsistent third-party device access system models by unifying device access, management, and querying through this model. This addresses the differences caused by varying functionalities when the same product category accesses the system, resolves the confusion in device queries caused by different systems accessing their own devices, and overcomes the fragmented subsequent functional development and inability to utilize unified logic caused by the lack of a unified device model within the system. Furthermore, by establishing a device model that conforms to the capabilities of third-party devices and attaching functionalities to the model, this technical solution achieves flexible device management. When adding new devices or functions, only corresponding extensions to the model are needed. This flexibility allows the device management system to easily adapt to constantly changing market demands and device updates. This technical solution simplifies the access process for third-party devices, enabling devices to be connected to the device management system and put into use more quickly. This reduces access costs and time costs, and improves overall efficiency. This technical solution enables fast and accurate cross-application queries for third-party devices through device service interfaces and differential query conditions. This improves query efficiency, allowing other applications to obtain the required device information more quickly. The device management system provides comprehensive management and control over third-party devices, including device authentication, registration, and status monitoring. This ensures the normal operation and security of the devices, preventing unauthorized access and operation. Furthermore, this technical solution provides a timely troubleshooting and handling mechanism for device faults, further enhancing the reliability of device management. Attached Figure Description

[0014] Figure 1 This is a flowchart of the method described in this invention; Figure 2 This is a system block diagram of the system described in this invention; Figure 3 To provide a detailed illustration of the overview in the unified equipment model; Figure 4 This provides a detailed illustration of data points in a unified equipment model. Detailed Implementation

[0015] The preferred embodiments of the present invention will be described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit the present invention.

[0016] This invention proposes an access method for a unified device system that adapts to the access of third-party devices, such as... Figure 1 As shown, the access method includes: S1. Establish a device model that meets the capabilities of the third-party devices, and attach the functional points of the third-party devices to the device model. S2. When the third-party device is connected to the device management system, the device management system manages and controls the third-party device. S3. When the device management system queries the third-party device across applications, it calls the device service interface and queries the third-party device according to the different query conditions.

[0017] The working principle of the above technical solution is as follows: First, a device model is established based on the actual capabilities and functional requirements of the third-party devices. This model forms the basis for interaction between the third-party devices and the device management system. Next, each functional point of the third-party device is attached to this device model. This gives each functional point a clear location and identifier, facilitating subsequent management and querying. When a third-party device needs to connect to the device management system, it establishes a connection with the system and accepts its management and control. This process includes device authentication, registration, and status monitoring. The device management system performs comprehensive management of the connected third-party devices, including device configuration, upgrades, and troubleshooting. This ensures the normal operation and security of the devices. When the device management system needs to query third-party devices across applications, it calls the device service interface. This interface serves as a bridge for interaction between the device management system and other applications. Based on the query criteria, the device management system filters and queries the third-party devices. The query results are returned to the application that initiated the query for further processing or display.

[0018] Specifically, the unified device model describes devices from five dimensions: status, overview, attributes, actions, and events. All devices connected to the system are uniformly modeled, allowing for unified access, management, and querying of devices. Among these: Status: The status of the device, such as online / offline status, enabled status, etc.; Overview: Static description of the device, such as device ID, manufacturer, third-party device ID, IP address, port, transmission method, transmission protocol, etc.; Detailed explanation of the overview is as follows: Figure 3 As shown, Attributes: Data points reported by the device during operation, such as temperature value, on / off status, and face image; these data points are defined from nine dimensions: ID, code, name, data type, transmission direction, minimum value, maximum value, step size, and multiple; detailed explanations of these data points are as follows... Figure 4 As shown, Action: Instructions sent to the equipment, such as temperature setting, on / off control, etc.; Events: Notifications reported by devices when they reach a threshold, such as alarms, faults, and notifications; Meanwhile, the access method is as follows: 1. Establish a device model that conforms to the capabilities of third-party devices, and decompose the functional points of third-party devices into data points and attach them to the device model attributes, actions, and events.

[0019] 2. When a third-party device is connected, enter the third-party device ID, manufacturer, IP address, etc. into the system, or write the device model ID, server IP address, and port number into the device.

[0020] 3. After the device is connected to the system, the device and device model are matched based on the third-party device ID and manufacturer, or based on the device model ID.

[0021] 4. When device function points are reported, the reported content is checked based on the data points defined in the device model. At the same time, when parsing data points, the defined data points can also be queried.

[0022] 5. When querying devices across applications, you only need to call the device service interface and query the device according to the conditions, and the device model is consistent.

[0023] The above technical solution achieves the following effects: By establishing a device model that conforms to the capabilities of third-party devices and attaching functional points to the model, this solution enables flexible device management. When new devices or functions need to be added, only corresponding extensions need to be made to the model. This flexibility allows the device management system to easily adapt to constantly changing market demands and device updates. This solution simplifies the onboarding process for third-party devices, enabling them to be connected to the device management system and put into use more quickly. This reduces onboarding and time costs and improves overall efficiency. Through device service interfaces and differential query conditions, this solution enables fast and accurate cross-application queries for third-party devices. This improves query efficiency, allowing other applications to obtain the required device information more quickly. The device management system provides comprehensive management and control of third-party devices, including device authentication, registration, and status monitoring. This ensures the normal operation and security of the devices and prevents unauthorized access and operation. Simultaneously, this solution also provides a timely troubleshooting and handling mechanism for device faults, further enhancing the reliability of device management.

[0024] In summary, the above technical solution improves the flexibility and scalability of device management, optimizes the device access process, enhances cross-application query efficiency, and strengthens the security and reliability of device management by establishing a device model that conforms to the capabilities of third-party devices, enabling device access and management, and facilitating cross-application device queries. These technical effects make this solution a promising and valuable solution for the field of device management.

[0025] One embodiment of the present invention involves establishing a device model that conforms to the capabilities of third-party devices, and attaching the functional points of the third-party devices to the device model, including: S101. Establish a device model that conforms to the capabilities of the three-party devices; S102. Decompose the function points corresponding to the third-party devices into data points; S103. The data points are attached to the items corresponding to the attributes, actions, and events of the device model. At the same time, the device model records and displays the operating status and overview of the third-party devices.

[0026] The states, overviews, attributes, actions, and events are described below: Status refers to the operating status of the third-party devices, such as online / offline status, enabled status, etc. The overview refers to the static description of the third-party device, such as device ID, manufacturer, third-party device ID, IP address, port, transmission method, transmission protocol, etc. Attributes refer to the data points reported by the third-party devices during runtime, such as temperature values, on / off status, and facial images; data points are defined from nine dimensions: ID, code, name, data type, transmission direction, minimum value, maximum value, step size, and multiple. An action refers to an instruction sent to the aforementioned third-party devices, such as temperature setting or switch control. An event refers to a notification reported by the third-party device when it reaches a threshold, such as an alarm, a fault, or a notification.

[0027] The working principle of the above technical solution is as follows: Based on the actual capabilities and functional requirements of the third-party equipment, a device model that conforms to these characteristics is constructed. This model serves as the foundation for subsequent function point attachment, equipment management, and querying. The various functional points of the third-party equipment are broken down into specific data points. These data points comprehensively reflect the equipment's operating status and attribute values. The decomposed data points are then attached to the corresponding items of the equipment model's attributes, actions, and events. In this way, each data point has a clear location and identifier, facilitating subsequent management and querying.

[0028] At the same time, the device model will also record and display the operating status (such as online / offline status, enabled status, etc.) and overview (such as static descriptions of device ID, manufacturer, IP, port, etc.) of the third-party devices.

[0029] Once the equipment model is built, the equipment management system can interact with and manage it in the following ways: Status monitoring: Real-time acquisition of the operating status of third-party devices, such as online / offline status and activation status, to ensure the normal operation of the devices.

[0030] Overview query: Query the static description information of third-party devices, such as device ID, manufacturer, etc., to facilitate device management and maintenance.

[0031] Attribute reporting: Receives data points reported by third-party devices during runtime, such as temperature values ​​and switch status, and processes and displays them.

[0032] Action issuance: Sending commands to third-party devices, such as temperature settings and switch controls, to achieve remote control of the devices.

[0033] Event notification: When a third-party device reaches a threshold, receive notifications reported by it, such as alarms or faults, and handle them promptly.

[0034] The above technical solution achieves the following effects: By breaking down the functional points of third-party devices into data points and attaching them to the device model, refined management of the devices is realized. This helps to more accurately understand the operating status and attribute values ​​of the devices, improving the level of intelligence in device management. The established device model conforms to the actual capabilities and functional requirements of the third-party devices, exhibiting strong versatility. Furthermore, the data point attachment method ensures good scalability when adding new devices or functions in the future. This technical solution simplifies the access process for third-party devices, enabling them to be connected to the device management system and put into use more quickly. Simultaneously, by recording and displaying the device's operating status and overview through the device model, the device management process is optimized, improving management efficiency. The device management system comprehensively manages and controls third-party devices through the device model, including data collection, storage, processing, and analysis. This ensures the security and reliability of device data, preventing data loss and tampering. Because the device model records information such as the transmission methods and protocols of the third-party devices, the device management system can support cross-platform and multi-protocol device access. This facilitates interoperability between devices of different brands and models, improving the flexibility and convenience of device management.

[0035] In summary, the above technical solution achieves refined and intelligent management of equipment, as well as cross-platform and multi-protocol device access, by establishing a device model that conforms to the capabilities of third-party devices and splitting functional points into data points and attaching them to the device model. These technical effects make this solution have broad application prospects and value in the field of equipment management.

[0036] In one embodiment of the present invention, when the third-party device is connected to the device management system, the device management system manages and controls the third-party device, including: S201. After the third-party device is connected to the device management system, the device management system obtains the third-party device and its corresponding device information and device model based on the third-party device ID and manufacturer, or based on the device model ID. S202. When the third-party device reports its functional points to the device management system, the device management system checks the reported content based on the data points defined in the device model. S203. When the device management system parses the data points of the third-party device, it queries the information corresponding to the data points according to the query data corresponding to the predefined data points.

[0037] The working principle of the above technical solution is as follows: When a third-party device connects to the device management system, the system first identifies the device's ID and manufacturer, or matches it based on the device model ID. Through matching, the system can obtain the corresponding device information and device model of the third-party device. This information forms the basis for subsequent device management and control.

[0038] The third-party devices report their functionalities to the equipment management system, including various device statuses and parameters. The equipment management system then checks the reported information against the data points defined in the equipment model. This is primarily to ensure that the reported data matches the data points defined in the equipment model, thereby ensuring data accuracy and reliability.

[0039] The equipment management system parses the data points of the three-party devices, including extracting data point values, status, and other information. Based on the predefined query data corresponding to each data point, the system queries the information associated with that data point. This is primarily to obtain more detailed and comprehensive equipment information for subsequent equipment management and control.

[0040] The above technical solution offers the following benefits: Unified management of third-party equipment through the equipment management system enables real-time monitoring, maintenance, and fault early warning, significantly improving equipment management efficiency. The system can automatically generate maintenance plans and fault reports, reducing manual intervention and lowering management costs. Defining data points through equipment models and checking reported content ensures data accuracy and completeness, helping to avoid equipment management problems caused by data errors or omissions. The equipment management system supports the access of various types of third-party equipment and manages them uniformly based on equipment models. This allows the system to adapt to different equipment management needs in various scenarios, enhancing the flexibility of equipment management. Through data analysis and data mining techniques, the equipment management system can predict and optimize equipment operating status. This helps to identify potential problems early, preventing production stoppages or losses due to equipment failures.

[0041] In summary, this technical solution achieves improved equipment management efficiency, ensured data accuracy and integrity, enhanced equipment management flexibility, and promoted intelligent equipment management through unified management and control of the three parties' equipment via an equipment management system.

[0042] In one embodiment of the present invention, the access method further includes: Step 1: Monitor the status changes of the three-party devices in real time; Step 2: When the state of the third-party device changes, the changed state is taken as the target state, and the first change moment of the target state is recorded. Step 3: Record the moment when the target state corresponding to the three-party devices in the device model changes, and use this as the second moment of change; Step 4: Record the moment when the target status of the third-party equipment obtained from the equipment management system changes, and use this as the third change moment; Step 5: Obtain the first time interval using the first and second change moments; Step 6: Obtain the second time interval using the second and third change moments; Step 7: Use the first and third change moments to obtain the third time interval; Step 8: Obtain the status change management timeliness parameters using the first time interval, the second time interval, and the third time interval; The timeliness parameter for state change management is obtained through the following formula: ; in, S Indicates the timeliness parameters for status change management; T 01 , T 02 and T 03 These represent the first time interval, the second time interval, and the third time interval, respectively. k Let represent the adjustment coefficient, and the adjustment coefficient is obtained by the following formula: ; in, k Indicates the adjustment coefficient; T 01 , T 02 and T 03 These represent the first time interval, the second time interval, and the third time interval, respectively. Step 9: Compare the status change management timeliness parameters with the preset timeliness parameter thresholds; Step 10: When the timeliness parameter of the status change management is lower than the preset timeliness parameter threshold, it is determined that the timeliness of the equipment management system for the status change management of the third-party equipment is poor, and an alarm for abnormal timeliness is triggered.

[0043] The working principle of the above technical solution is as follows: Real-time monitoring of the status changes of third-party devices is achieved through sensor technology and the Internet of Things (IoT). These status changes may include anomalies in key parameters such as temperature, pressure, vibration, and humidity. When the status of the third-party devices changes, the system can identify this change and record the first moment of the status change. Simultaneously, the device model and the device management system will also record the second and third moments of the corresponding target status change. Using these three moments of change, three time intervals can be calculated: the first time interval (the difference between the first and second moments of change), the second time interval (the difference between the second and third moments of change), and the third time interval (the difference between the first and third moments of change). These three time intervals, along with an adjustment coefficient k, are combined using a specific formula to calculate the status change management timeliness parameter S. This parameter reflects the timeliness of the device management system's management of the status changes of the third-party devices. The calculated status change management timeliness parameter S is compared with a preset timeliness parameter threshold. If S is lower than the threshold, the device management system is deemed to have poor timeliness in managing the status changes of the third-party devices, and a timeliness anomaly alarm is triggered.

[0044] The effects of the above technical solution are as follows: By monitoring the status changes of the three-party equipment in real time and responding quickly to these changes, the equipment management system can manage equipment status more promptly, thereby improving the timeliness of equipment management. By calculating time intervals and status change management timeliness parameters, the system can more accurately evaluate the effectiveness of equipment management, thus helping managers make more informed decisions. Through timely monitoring and management of equipment status changes, the system can promptly detect and resolve potential equipment failures, thereby improving the stability of equipment operation. By providing early warnings and timely handling of equipment status changes, the system can reduce downtime and maintenance costs caused by equipment failures. The identification and alarm mechanisms in the equipment anomaly handling process can promptly detect equipment anomalies and notify relevant personnel for handling, thereby avoiding potential production accidents and data loss, and enhancing equipment safety.

[0045] By monitoring the status changes of three-party equipment in real time and immediately recording the relevant timestamps when status changes occur, the system can respond quickly to changes in equipment status. This helps reduce delays in equipment fault detection and handling, improving the timeliness of equipment management. By calculating the status change management timeliness parameter S and comparing it with a preset timeliness parameter threshold, the system can quantitatively evaluate the timeliness of equipment management. This allows managers to intuitively understand the efficiency of equipment management and take corresponding measures for improvement. The system can accurately record the first, second, and third status changes of the three-party equipment, providing an accurate data basis for calculating the time interval. By calculating the time interval and the status change management timeliness parameter S using the above formula, the system can accurately reflect the effectiveness of equipment management. This helps managers to more accurately understand changes in equipment status and make more informed decisions.

[0046] When the timeliness parameter S for status change management falls below a preset threshold, the system triggers a timeliness anomaly alarm. This helps to promptly identify potential equipment failures and take corresponding preventative measures to avoid escalation. By providing early warnings and timely handling of equipment status changes, the system can reduce downtime caused by equipment failures. This helps improve equipment utilization and production efficiency. By monitoring equipment status in real time and conducting timeliness assessments, the system can predict potential equipment failure points and perform preventative maintenance. This helps reduce maintenance costs caused by equipment failures. The system can quantitatively assess the timeliness of equipment management, thereby helping managers optimize resource allocation. By promptly identifying and handling equipment status changes, the system can prevent potential production accidents. This helps protect the lives of employees and the safety of company property. The system can monitor equipment status in real time and promptly alarm when equipment anomalies occur. This helps prevent data loss or corruption caused by equipment failures, protecting the company's data security.

[0047] In summary, the technical benefits of the above-mentioned solutions in terms of performance indicators are mainly reflected in improved timeliness, enhanced accuracy, increased stability, reduced maintenance costs, and enhanced security. These effects work together in the equipment management system to improve the overall efficiency and security of equipment management.

[0048] This invention proposes an access system for a unified device system that adapts to the access of third-party devices, such as... Figure 2 As shown, the access system includes: The model building module is used to build a device model that conforms to the capabilities of third-party devices and to attach the functional points of third-party devices to the device model. The management and control module is used to manage and control the third-party devices when they are connected to the device management system. The query module is used by the device management system to call the device service interface and query the third-party devices according to different query conditions when querying the third-party devices across applications.

[0049] The working principle of the above technical solution is as follows: First, a device model is established based on the actual capabilities and functional requirements of the third-party devices. This model forms the basis for interaction between the third-party devices and the device management system. Next, each functional point of the third-party device is attached to this device model. This gives each functional point a clear location and identifier, facilitating subsequent management and querying. When a third-party device needs to connect to the device management system, it establishes a connection with the system and accepts its management and control. This process includes device authentication, registration, and status monitoring. The device management system performs comprehensive management of the connected third-party devices, including device configuration, upgrades, and troubleshooting. This ensures the normal operation and security of the devices. When the device management system needs to query third-party devices across applications, it calls the device service interface. This interface serves as a bridge for interaction between the device management system and other applications. Based on the query criteria, the device management system filters and queries the third-party devices. The query results are returned to the application that initiated the query for further processing or display.

[0050] Specifically, the unified device model describes devices from five dimensions: status, overview, attributes, actions, and events. All devices connected to the system are uniformly modeled, allowing for unified access, management, and querying of devices. Among these: Status: The status of the device, such as online / offline status, enabled status, etc.; Overview: Static description of the device, such as device ID, manufacturer, third-party device ID, IP address, port, transmission method, transmission protocol, etc.; Detailed explanation of the overview is as follows: Figure 3 As shown, Attributes: Data points reported by the device during operation, such as temperature value, on / off status, and face image; these data points are defined from nine dimensions: ID, code, name, data type, transmission direction, minimum value, maximum value, step size, and multiple; detailed explanations of these data points are as follows... Figure 4 As shown, Action: Instructions sent to the equipment, such as temperature setting, on / off control, etc.; Events: Notifications reported by devices when they reach a threshold, such as alarms, faults, and notifications; Meanwhile, the access method is as follows: 1. Establish a device model that conforms to the capabilities of third-party devices, and decompose the functional points of third-party devices into data points and attach them to the device model attributes, actions, and events.

[0051] 2. When a third-party device is connected, enter the third-party device ID, manufacturer, IP address, etc. into the system, or write the device model ID, server IP address, and port number into the device.

[0052] 3. After the device is connected to the system, the device and device model are matched based on the third-party device ID and manufacturer, or based on the device model ID.

[0053] 4. When device function points are reported, the reported content is checked based on the data points defined in the device model. At the same time, when parsing data points, the defined data points can also be queried.

[0054] 5. When querying devices across applications, you only need to call the device service interface and query the device according to the conditions, and the device model is consistent.

[0055] The above technical solution achieves the following effects: By establishing a device model that conforms to the capabilities of third-party devices and attaching functional points to the model, this solution enables flexible device management. When new devices or functions need to be added, only corresponding extensions need to be made to the model. This flexibility allows the device management system to easily adapt to constantly changing market demands and device updates. This solution simplifies the onboarding process for third-party devices, enabling them to be connected to the device management system and put into use more quickly. This reduces onboarding and time costs and improves overall efficiency. Through device service interfaces and differential query conditions, this solution enables fast and accurate cross-application queries for third-party devices. This improves query efficiency, allowing other applications to obtain the required device information more quickly. The device management system provides comprehensive management and control of third-party devices, including device authentication, registration, and status monitoring. This ensures the normal operation and security of the devices and prevents unauthorized access and operation. Simultaneously, this solution also provides a timely troubleshooting and handling mechanism for device faults, further enhancing the reliability of device management.

[0056] In summary, the above technical solution improves the flexibility and scalability of device management, optimizes the device access process, enhances cross-application query efficiency, and strengthens the security and reliability of device management by establishing a device model that conforms to the capabilities of third-party devices, enabling device access and management, and facilitating cross-application device queries. These technical effects make this solution a promising and valuable solution for the field of device management.

[0057] In one embodiment of the present invention, the model building module includes: The equipment model building module is used to build equipment models that conform to the capabilities of the third-party equipment. The data point splitting module is used to split the function points corresponding to the third-party devices into data points; The recording and display module is used to attach the data points to the items corresponding to the attributes, actions, and events of the device model. At the same time, the device model records and displays the operating status and overview of the third-party devices.

[0058] The states, overviews, attributes, actions, and events are as follows: Status refers to the operating status of the third-party devices, such as online / offline status, enabled status, etc. The overview refers to the static description of the third-party device, such as device ID, manufacturer, third-party device ID, IP address, port, transmission method, transmission protocol, etc. Attributes refer to the data points reported by the third-party devices during runtime, such as temperature values, on / off status, and facial images; data points are defined from nine dimensions: ID, code, name, data type, transmission direction, minimum value, maximum value, step size, and multiple. An action refers to an instruction sent to the aforementioned third-party devices, such as temperature setting or switch control. An event refers to a notification reported by the third-party device when it reaches a threshold, such as an alarm, a fault, or a notification.

[0059] The working principle of the above technical solution is as follows: Based on the actual capabilities and functional requirements of the third-party equipment, a device model that conforms to these characteristics is constructed. This model serves as the foundation for subsequent function point attachment, equipment management, and querying. The various functional points of the third-party equipment are broken down into specific data points. These data points comprehensively reflect the equipment's operating status and attribute values. The decomposed data points are then attached to the corresponding items of the equipment model's attributes, actions, and events. In this way, each data point has a clear location and identifier, facilitating subsequent management and querying.

[0060] At the same time, the device model will also record and display the operating status (such as online / offline status, enabled status, etc.) and overview (such as static descriptions of device ID, manufacturer, IP, port, etc.) of the third-party devices.

[0061] Once the equipment model is built, the equipment management system can interact with and manage it in the following ways: Status monitoring: Real-time acquisition of the operating status of third-party devices, such as online / offline status and activation status, to ensure the normal operation of the devices.

[0062] Overview query: Query the static description information of third-party devices, such as device ID, manufacturer, etc., to facilitate device management and maintenance.

[0063] Attribute reporting: Receives data points reported by third-party devices during runtime, such as temperature values ​​and switch status, and processes and displays them.

[0064] Action issuance: Sending commands to third-party devices, such as temperature settings and switch controls, to achieve remote control of the devices.

[0065] Event notification: When a third-party device reaches a threshold, receive notifications reported by it, such as alarms or faults, and handle them promptly.

[0066] The above technical solution achieves the following effects: By breaking down the functional points of third-party devices into data points and attaching them to the device model, refined management of the devices is realized. This helps to more accurately understand the operating status and attribute values ​​of the devices, improving the level of intelligence in device management. The established device model conforms to the actual capabilities and functional requirements of the third-party devices, exhibiting strong versatility. Furthermore, the data point attachment method ensures good scalability when adding new devices or functions in the future. This technical solution simplifies the access process for third-party devices, enabling them to be connected to the device management system and put into use more quickly. Simultaneously, by recording and displaying the device's operating status and overview through the device model, the device management process is optimized, improving management efficiency. The device management system comprehensively manages and controls third-party devices through the device model, including data collection, storage, processing, and analysis. This ensures the security and reliability of device data, preventing data loss and tampering. Because the device model records information such as the transmission methods and protocols of the third-party devices, the device management system can support cross-platform and multi-protocol device access. This facilitates interoperability between devices of different brands and models, improving the flexibility and convenience of device management.

[0067] In summary, the above technical solution achieves refined and intelligent management of equipment, as well as cross-platform and multi-protocol device access, by establishing a device model that conforms to the capabilities of third-party devices and splitting functional points into data points and attaching them to the device model. These technical effects make this solution have broad application prospects and value in the field of equipment management.

[0068] In one embodiment of the present invention, the management control module includes: The device information acquisition module is used to obtain the third-party device and its corresponding device information and device model after the third-party device is connected to the device management system. The device management system obtains the third-party device and its corresponding device information and device model based on the third-party device ID and manufacturer, or based on the device model ID. The content inspection and reporting module is used to inspect the reported content based on the data points defined in the device model when the third-party device reports its functional points to the device management system. The query control module is used by the device management system to query the information corresponding to the data points based on the predefined query data corresponding to the data points when parsing the data points of the third-party devices.

[0069] The working principle of the above technical solution is as follows: When a third-party device connects to the device management system, the system first identifies the device's ID and manufacturer, or matches it based on the device model ID. Through matching, the system can obtain the corresponding device information and device model of the third-party device. This information forms the basis for subsequent device management and control.

[0070] The third-party devices report their functionalities to the equipment management system, including various device statuses and parameters. The equipment management system then checks the reported information against the data points defined in the equipment model. This is primarily to ensure that the reported data matches the data points defined in the equipment model, thereby ensuring data accuracy and reliability.

[0071] The equipment management system parses the data points of the three-party devices, including extracting data point values, status, and other information. Based on the predefined query data corresponding to each data point, the system queries the information associated with that data point. This is primarily to obtain more detailed and comprehensive equipment information for subsequent equipment management and control.

[0072] The above technical solution offers the following benefits: Unified management of third-party equipment through the equipment management system enables real-time monitoring, maintenance, and fault early warning, significantly improving equipment management efficiency. The system can automatically generate maintenance plans and fault reports, reducing manual intervention and lowering management costs. Defining data points through equipment models and checking reported content ensures data accuracy and completeness, helping to avoid equipment management problems caused by data errors or omissions. The equipment management system supports the access of various types of third-party equipment and manages them uniformly based on equipment models. This allows the system to adapt to different equipment management needs in various scenarios, enhancing the flexibility of equipment management. Through data analysis and data mining techniques, the equipment management system can predict and optimize equipment operating status. This helps to identify potential problems early, preventing production stoppages or losses due to equipment failures.

[0073] In summary, this technical solution achieves improved equipment management efficiency, ensured data accuracy and integrity, enhanced equipment management flexibility, and promoted intelligent equipment management through unified management and control of the three parties' equipment via an equipment management system.

[0074] In one embodiment of the present invention, the access system further includes: The real-time monitoring module is used to monitor the status changes of third-party devices in real time. The first change moment acquisition module is used to take the changed state as the target state when the state of the third-party device changes, and to determine the first change moment when the target state changes. The second change moment acquisition module is used to record the change moment when the target state corresponding to the third-party device in the device model changes, and use it as the second change moment. The third change moment acquisition module is used to record the change moment when the target status corresponding to the third-party equipment obtained in the equipment management system changes, and use it as the third change moment. The first time interval acquisition module is used to acquire the first time interval using the first change moment and the second change moment; The second time interval acquisition module is used to acquire the second time interval using the second change time and the third change time. The third time interval acquisition module is used to acquire the third time interval using the first change moment and the third change moment; The status change management timeliness parameter acquisition module is used to acquire status change management timeliness parameters using the first time interval, the second time interval, and the third time interval. The timeliness parameter for state change management is obtained through the following formula: ; in, S Indicates the timeliness parameters for status change management; T 01 , T 02 and T 03 These represent the first time interval, the second time interval, and the third time interval, respectively. k Let represent the adjustment coefficient, and the adjustment coefficient is obtained by the following formula: ; in, k Indicates the adjustment coefficient; T 01 , T 02 and T 03 These represent the first time interval, the second time interval, and the third time interval, respectively. The parameter comparison module is used to compare the status change management timeliness parameters with preset timeliness parameter thresholds; The abnormal alarm module is used to determine that the timeliness of the device management system for managing the status changes of third-party devices is poor when the timeliness parameter of the status change management is lower than the preset timeliness parameter threshold, and to issue an abnormal timeliness alarm.

[0075] The working principle of the above technical solution is as follows: Real-time monitoring of the status changes of third-party devices is achieved through sensor technology and the Internet of Things (IoT). These status changes may include anomalies in key parameters such as temperature, pressure, vibration, and humidity. When the status of the third-party devices changes, the system can identify this change and record the first moment of the status change. Simultaneously, the device model and the device management system will also record the second and third moments of the corresponding target status change. Using these three moments of change, three time intervals can be calculated: the first time interval (the difference between the first and second moments of change), the second time interval (the difference between the second and third moments of change), and the third time interval (the difference between the first and third moments of change). These three time intervals, along with an adjustment coefficient k, are combined using a specific formula to calculate the status change management timeliness parameter S. This parameter reflects the timeliness of the device management system's management of the status changes of the third-party devices. The calculated status change management timeliness parameter S is compared with a preset timeliness parameter threshold. If S is lower than the threshold, the device management system is deemed to have poor timeliness in managing the status changes of the third-party devices, and a timeliness anomaly alarm is triggered.

[0076] The effects of the above technical solution are as follows: By monitoring the status changes of the three-party equipment in real time and responding quickly to these changes, the equipment management system can manage equipment status more promptly, thereby improving the timeliness of equipment management. By calculating time intervals and status change management timeliness parameters, the system can more accurately evaluate the effectiveness of equipment management, thus helping managers make more informed decisions. Through timely monitoring and management of equipment status changes, the system can promptly detect and resolve potential equipment failures, thereby improving the stability of equipment operation. By providing early warnings and timely handling of equipment status changes, the system can reduce downtime and maintenance costs caused by equipment failures. The identification and alarm mechanisms in the equipment anomaly handling process can promptly detect equipment anomalies and notify relevant personnel for handling, thereby avoiding potential production accidents and data loss, and enhancing equipment safety.

[0077] By monitoring the status changes of three-party equipment in real time and immediately recording the relevant timestamps when status changes occur, the system can respond quickly to changes in equipment status. This helps reduce delays in equipment fault detection and handling, improving the timeliness of equipment management. By calculating the status change management timeliness parameter S and comparing it with a preset timeliness parameter threshold, the system can quantitatively evaluate the timeliness of equipment management. This allows managers to intuitively understand the efficiency of equipment management and take corresponding measures for improvement. The system can accurately record the first, second, and third status changes of the three-party equipment, providing an accurate data basis for calculating the time interval. By calculating the time interval and the status change management timeliness parameter S using the above formula, the system can accurately reflect the effectiveness of equipment management. This helps managers to more accurately understand changes in equipment status and make more informed decisions.

[0078] When the timeliness parameter S for status change management falls below a preset threshold, the system triggers a timeliness anomaly alarm. This helps to promptly identify potential equipment failures and take corresponding preventative measures to avoid escalation. By providing early warnings and timely handling of equipment status changes, the system can reduce downtime caused by equipment failures. This helps improve equipment utilization and production efficiency. By monitoring equipment status in real time and conducting timeliness assessments, the system can predict potential equipment failure points and perform preventative maintenance. This helps reduce maintenance costs caused by equipment failures. The system can quantitatively assess the timeliness of equipment management, thereby helping managers optimize resource allocation. By promptly identifying and handling equipment status changes, the system can prevent potential production accidents. This helps protect the lives of employees and the safety of company property. The system can monitor equipment status in real time and promptly alarm when equipment anomalies occur. This helps prevent data loss or corruption caused by equipment failures, protecting the company's data security.

[0079] In summary, the technical benefits of the above-mentioned solutions in terms of performance indicators are mainly reflected in improved timeliness, enhanced accuracy, increased stability, reduced maintenance costs, and enhanced security. These effects work together in the equipment management system to improve the overall efficiency and security of equipment management.

[0080] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. An access method of a unified device system adapted for access of a three-party device, characterized by, The access method comprises: establishing a device model conforming to the capability of the three-party device, and mounting the function points of the three-party device under the device model; when the three-party device accesses the device management system, the device management system manages and controls the three-party device; when the device management system cross-application queries the three-party device, a device service interface is called, and the three-party device is queried according to different query conditions.

2. The access method of claim 1, wherein, establishing a device model conforming to the capability of the three-party device, and mounting the function points of the three-party device under the device model, comprising: establishing a device model conforming to the capability of the three-party device; splitting the function points corresponding to the three-party device into data points; mounting the data points under the items corresponding to the attributes, actions and events of the device model, and meanwhile, the device model records and displays the running state and summary of the three-party device.

3. The access method of claim 2, wherein the access method is characterized by, The state, summary, attribute, action and event are as follows: the state refers to the running state of the three-party device; the summary refers to the static description of the three-party device; the attribute refers to the data points reported by the attribute value of the running three-party device; the action refers to the instruction issued to the three-party device; the event refers to the notification reported by the three-party device when reaching a threshold.

4. The access method of claim 1, wherein the access method is characterized by: when the three-party device accesses the device management system, the device management system manages and controls the three-party device, comprising: after the three-party device accesses the device management system, the device management system matches and obtains the three-party device and the device information and device model corresponding to the three-party device according to the three-party device ID and the manufacturer, or according to the device model ID; when the function points of the three-party device report to the device management system, the device management system checks the reported content according to the data points defined by the device model; when the device management system analyzes the data points of the three-party device, the device management system queries the information corresponding to the data points according to the pre-defined query data corresponding to the data points.

5. The access method of claim 1, wherein the access method is characterized by: The access method further comprises: real-time monitoring of the state change of the three-party device; when the state of the three-party device changes, the changed state is taken as a target state, and the first change time when the target state changes; the change time when the target state corresponding to the three-party device in the device model changes is recorded as a second change time; the change time when the target state corresponding to the three-party device obtained in the device management system changes is recorded as a third change time; the first time interval is obtained by using the first change time and the second change time; the second time interval is obtained by using the second change time and the third change time; the third time interval is obtained by using the first change time and the third change time; the state change management time effectiveness parameter is obtained by using the first time interval, the second time interval and the third time interval; the state change management time effectiveness parameter is obtained by using the following formula: ； wherein, S represents a state change management time effectiveness parameter; T 01 , T 02 and T 03 respectively represent a first time interval, a second time interval and a third time interval; k represents an adjustment coefficient, and the adjustment coefficient is obtained by the following formula: ； wherein, k represents a regulation coefficient; T 01 , T 02 and T 03 respectively represent a first time interval, a second time interval and a third time interval; the state change management time effectiveness parameter is compared with a preset time effectiveness parameter threshold; when the state change management time effectiveness parameter is lower than the preset time effectiveness parameter threshold, it is determined that the state change management timeliness of the device management system for the three-party device is poor, and a timeliness abnormality alarm is given.

6. An access system for a unified device system adaptable to third-party device access, characterized in that, The access system comprises: The model establishing module is configured to establish a device model in line with the capability of the third-party device and mount the function points of the third-party device to the device model. The management control module is configured to manage and control the third-party device by the device management system when the third-party device accesses the device management system. The query module is configured to query the third-party device by the device management system across applications, call a device service interface, and query the third-party device according to different query conditions.

7. The access system of claim 6, wherein the access system is adapted to access the unified device system of the third party device. The model establishing module comprises: ​ The device model establishing module is configured to establish a device model in line with the capability of the third-party device. The data point splitting module is configured to split the function points corresponding to the third-party device into data points. The record display module is configured to mount the data points to the items corresponding to the attributes, actions and events of the device model, and record and display the running state and summary of the third-party device by the device model.

8. The access system of claim 7, wherein, The state, summary, attribute, action and event are as follows: The state refers to the running state of the third-party device. The summary refers to the static description of the third-party device. The attribute refers to the data points reported by the attribute value of the third-party device in running. The action refers to the instruction issued to the third-party device. The event refers to the notification reported by the third-party device when reaching a threshold.

9. The access system of claim 6, wherein the access system is adapted to access the unified device system of the third party device. The management control module comprises: ​ The device information acquisition module is configured to acquire the device information and device model of the third-party device by the device management system according to the third-party device ID and manufacturer, or according to the device model ID matching when the third-party device accesses the device management system. The content checking and reporting module is configured to check the reporting content by the device management system according to the data points defined by the device model when the function points of the third-party device report to the device management system. The query control module is configured to query the information corresponding to the data points according to the query data corresponding to the data points when the device management system analyzes the data points of the third-party device.

10. The access system of claim 6, wherein the access system is adapted to access the unified device system of the third party device. The access system further comprises: The real-time monitoring module is configured to monitor the state change of the third-party device in real time. The first change time acquisition module is configured to acquire the state changed as a target state when the state of the third-party device changes, and acquire the first change time when the target state changes. The second change time acquisition module is configured to record the change time when the target state corresponding to the third-party device in the device model changes as a second change time. The third change time acquisition module is configured to record the change time when the target state corresponding to the third-party device acquired in the device management system changes as a third change time. The first time interval acquisition module is configured to acquire a first time interval by using the first change time and the second change time. The second time interval acquisition module is configured to acquire a second time interval by using the second change time and the third change time. The third time interval acquisition module is configured to acquire a third time interval by using the first change time and the third change time. The state change management timeliness parameter acquisition module is configured to acquire a state change management timeliness parameter by using the first time interval, the second time interval, and the third time interval. The state change management timeliness parameter is acquired by using the following formula: ； wherein, S represents a state change management time effectiveness parameter; T 01 , T 02 and T 03 respectively represent a first time interval, a second time interval and a third time interval; k represents an adjustment coefficient, and the adjustment coefficient is obtained by the following formula: ； wherein, k represents a regulation coefficient; T 01 , T 02 and T 03 respectively represent a first time interval, a second time interval and a third time interval; The parameter comparison module is configured to compare the state change management timeliness parameter with a preset timeliness parameter threshold. The abnormality alarm module is configured to determine that the state change management timeliness of the equipment management system for the three-party equipment is poor when the state change management timeliness parameter is lower than the preset timeliness parameter threshold, and perform a timeliness abnormality alarm.

Images