Dynamic configurable third-party equipment access method

Abstract

The invention relates to a dynamic configurable third-party equipment access method, which comprises the following steps of: defining an equipment model, and defining a read-write attribute data point name aiming at a communication protocol provided by third-party equipment; a service configuration protocol service is applied, and a third-party equipment model object is created; data point access: the control system accesses a data point of the third-party equipment, so that data can be obtained through protocol service; mapping relation configuration: configuring a mapping relation between the equipment model data points and the key data points of the control system; configuring a mapping relation between the equipment model and the control method of the control system; data and control are implemented, data are transmitted through a message bus, and the data comprise equipment types, equipment names, attribute names, attribute values and types thereof; and calling and writing a specified data point or executing a specific command word through an HTTP (Hyper Text Transport Protocol) interface.

Description

Technical Field

[0001] The present application relates to the field of voice control in coal mines, and more specifically, to a dynamically configurable third-party device access method. Background Art

[0002] Voice centralized control system for underground coal mines. This system is a key part of underground coal mine operations. It integrates voice broadcasting functions and control of important mechanical equipment (such as scrapers, transfer machines, crushers) and emulsion systems. When new equipment needs to be integrated into this system, since different equipment suppliers may have different communication protocols and technical standards, the existing control system needs to be customized to adapt to the data interaction and control requirements of the new equipment. This customization process increases the complexity and maintenance cost of the system, because the internal logic of the control system needs to be adjusted every time a new device is added. To solve this problem, a dynamically configurable third-party device access method is proposed, which aims to simplify the integration process of new equipment through standardized and dynamic configuration and reduce the impact on the existing system logic. Summary of the invention

[0003] The purpose of this application is to provide a dynamically configurable third-party device access method to solve the problems in the prior art.

[0004] A dynamically configurable third-party device access method, comprising the following steps: S1 defines the device model, which includes a label domain and a value domain; S2 protocol service configuration, for the communication protocol provided by third-party devices, defines the names of read and write attribute data points; The S3 application service configures the protocol service and creates a third-party device model object; S4 data point access, the control system accesses the data points of third-party devices, making the data available through protocol services; S5 mapping relationship configuration, configure the mapping relationship between the equipment model data points and the key data points of the control system; Configure the mapping relationship between the device model and the control method of the control system; Data mapping must ensure that data types are consistent, otherwise the update will fail and an error message will be recorded; The control mapping must ensure that the number of parameters is consistent, otherwise the control fails and an error message is recorded; S6 data and control implementation, data is transmitted through the message bus, and the data includes device type, device name, attribute name, attribute value and its type; S7 control is called through the HTTP interface to write specified data points or execute specific command words; Security is ensured, the framework middleware runs locally, the equipment service deployment and configuration are maintained by dedicated personnel, and the model data and control interfaces released to the outside are subject to request authentication.

[0005] Furthermore, in the S1-defined device model, the tag domain stores the inherent attributes of the device, and the attributes are set to read-only to ensure that the device identity information cannot be changed; the value domain contains the engineering value read-only attribute data value, including the controllable point data value, and supports the dynamic addition of new attribute points to meet the needs of device expansion.

[0006] Furthermore, the S2 protocol service configuration is specific: Determine the name of the device's read and write attribute data point based on the communication protocol provided by the third-party device; The data point name includes a device-specific identifier. The protocol service is configured using the application service, and the configuration content includes the defined read and write attribute data point name; the application service creates a corresponding third-party device model object and associates it with the protocol service.

[0007] Further, the S3 application service configures the protocol service and creates a third-party device model object specifically: The application service configures the protocol service through a configuration file or interface tool to specify the read and write attribute data points of the third-party device; Configuration information includes data point name, data type, and necessary information for read and write permissions; Create a third-party device model object in the application service, which implements the model interface class interface; The tag field of the model object stores the inherent properties of the device and is set to read-only; The value domain of the model object stores dynamic attribute data and supports dynamic addition of attribute points; Associate the created third-party device model object with the protocol service to ensure that the protocol service can access and update the value domain data of the model object.

[0008] Further, S4 data point access specific: Define the name of the device's read and write attribute data points according to the communication protocol provided by the third-party device; Create corresponding third-party device model objects through application service configuration protocol services; The protocol service parses the received data points and stores them in the corresponding third-party device model; The control system obtains data points of third-party devices through protocol services to achieve access to data points.

[0009] Furthermore, the S5 mapping relationship configuration is specific: Configure the mapping relationship between the equipment model data points and the key data points of the control system. The front bearing temperature attribute data source of the motor model is the engineering value attribute of the front bearing temperature sensor model. When the engineering value attribute data point of the current bearing temperature sensor model is updated, this data value is synchronously updated to the front bearing temperature attribute of the motor model according to the pre-configured mapping relationship; If the data types do not match, the update fails and an error message is logged; Configure the mapping relationship between the device model and the control method of the control system. When the high-speed value of the motor is set, the control system calls and executes the motor speed regulation. The speed control of the source model MotorTransloader is mapped to the target model third_001, and third_001 executes the control in sequence according to the configuration; The speed value $0 in the variable parameter is the basic data type, and the control mapping needs to ensure that the number of parameters on both sides is consistent; Data conversion and parameter verification are performed before control. If they do not match, control fails and error information is recorded.

[0010] Furthermore, S7 security guarantees specifically include: The framework middleware is deployed on the local server. The middleware is responsible for data forwarding and control instruction execution, and the network port is not open to the outside world. The deployment and configuration of device services are the responsibility of trained professionals to ensure correct configuration and the application of the principle of least privilege. Configuration changes are recorded completely to facilitate auditing and backtracking. Model data and control interfaces released to the outside are subject to authentication requests. Model data and control interfaces released by the control system must undergo identity authentication and authorization checks. Authentication mechanisms include API keys, OAuth2.0, and JWT to ensure that only legitimate users can access resources. All access requests are logged.

[0011] The beneficial effects of the present application are as follows: The present application provides a dynamically configurable method to access third-party devices, thereby reducing the impact on the existing control system logic. Specifically, this method realizes flexible connection between the control system and third-party devices through device modeling, protocol service deployment, device data point and control point configuration, and mapping relationship configuration from device model data points to key data points of the control system.

[0012] The core is: Equipment modeling: allows dynamic addition of value range attribute points, so that the system can quickly adapt to different types of new equipment; Data and control mapping: ensures the consistency of data types and the correctness of control parameters, avoiding errors caused by mismatches; Dynamic configuration: enables the control system to dynamically adjust its processing logic according to different third-party devices without making a lot of customized modifications to the system itself, thereby reducing maintenance costs and potential risks.

[0013] These technologies work together to enable the control system to operate more stably and efficiently, maintaining good performance and low maintenance even when new equipment is constantly introduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solution of the embodiment of the present application, the following is a brief introduction to the drawings required for use in the embodiment: Figure 1 This is a property structure diagram of the model in device modeling.

[0015] Figure 2 This is a working framework diagram of the control system involved in this application. DETAILED DESCRIPTION

[0016] In order to make the technical purpose, technical solution and beneficial effects of the present application clearer, the technical solution of the present application is further described below in conjunction with the drawings and specific embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application, that is, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application described and shown in the drawings are usually arranged and designed in various different configurations.

[0017] The present application discloses a dynamically configurable third-party device access method, the specific steps of which include: S1 defines the device model, which includes a label domain and a value domain; S1 defines the device model, which includes a label domain and a value domain; Label field: Intrinsic properties of storage devices, such as manufacturer, model, and serial number; The property is set to read-only to ensure that the device identity information cannot be changed.

[0018] range: Contains engineering value read-only attribute data values ​​(such as temperature, pressure); Contains controllable point data values ​​(such as the color and flashing frequency of the alarm light); Supports dynamic addition of new attribute points to meet device expansion needs.

[0019] Through the above definition, the device model can accurately reflect the basic information and real-time status of the device, and has the flexibility to cope with future functional expansion of the device.

[0020] S2 protocol service configuration, for the communication protocol provided by third-party devices, defines the names of read and write attribute data points; S2 protocol service configuration: Determine the read and write attribute data point names of the device based on the communication protocol (such as ModBus) provided by the third-party device.

[0021] The data point name should include a device-specific identifier to facilitate subsequent data mapping and control mapping.

[0022] The protocol service is configured using the application service, including the defined read and write attribute data point names. The application service creates the corresponding third-party device model object and associates it with the protocol service.

[0023] The S3 application service configures the protocol service and creates a third-party device model object.

[0024] The S3 application service configures the protocol service and creates a third-party device model object: The application service configures the protocol service through a configuration file or an interface tool to specify the read and write attribute data points of the third-party device.

[0025] Configuration information should include data point name, data type, and necessary information on read and write permissions.

[0026] Create a third-party device model object in the application service. The object needs to implement the model interface class interface.

[0027] The tag field of the model object stores the inherent properties of the device (such as manufacturer and model) and is set to read-only.

[0028] The value domain of the model object stores dynamic attribute data (such as engineering values ​​and controllable point data) and supports dynamic addition of attribute points.

[0029] Associate the created third-party device model object with the protocol service to ensure that the protocol service can access and update the value domain data of the model object.

[0030] S4 data point access, the control system accesses the data points of third-party devices, making the data available through protocol services.

[0031] S4 data point access specific: Define the read and write attribute data point names of the device according to the communication protocol (such as ModBus) provided by the third-party device.

[0032] Create corresponding third-party device model objects by applying service configuration protocol services.

[0033] The protocol service parses the received data points and stores them in the corresponding third-party device model.

[0034] The control system obtains data points of third-party devices through protocol services to achieve access to data points.

[0035] S5 mapping relationship configuration, configure the mapping relationship between the equipment model data points and the key data points of the control system; Configure the mapping relationship between the device model and the control method of the control system; Data mapping must ensure that data types are consistent, otherwise the update will fail and an error message will be recorded; The control mapping must ensure that the number of parameters is consistent, otherwise the control fails and an error message is recorded.

[0036] S5 mapping relationship configuration details: Configure the mapping relationship between the equipment model data points and the key data points of the control system. Taking the motor as an example, the front bearing temperature attribute data source of the motor model can be the engineering value attribute of the front bearing temperature sensor model.

[0037] When the engineering value attribute data point of the current bearing temperature sensor model is updated, this data value is synchronously updated to the front bearing temperature attribute of the motor model according to the pre-configured mapping relationship.

[0038] If the data types do not match, the update fails and an error message is logged.

[0039] Configure the mapping relationship between the device model and the control method of the control system. Taking the motor as an example, when the high-speed speed value of the motor is set, the control system calls to execute the motor speed regulation.

[0040] The speed control of the source model MotorTransloader is mapped to the target model third_001, and third_001 executes the control in sequence according to the configuration (writes the data values ​​of the corresponding data points).

[0041] The speed value $0 in the variable parameter is the basic data type, and the control mapping needs to ensure that the number of parameters on both sides is consistent.

[0042] Data conversion and parameter verification are performed before control. If they do not match, control fails and error information is recorded.

[0043] Through the above specific mapping configuration steps, the consistency of data types and the correctness of control parameters are ensured, thereby achieving flexible connection between the control system and third-party devices and reducing the impact on the existing control system logic; S6 data and control implementation, data is transmitted through the message bus, including device type, device name, attribute name, attribute value and its type; S7 control is called through the HTTP interface to write specified data points or execute specific command words; Security is guaranteed, the framework middleware runs locally, and the equipment service deployment and configuration are maintained by dedicated personnel; Request authentication for model data and control interfaces released to the outside world; S7 security guarantees include: The framework middleware is deployed on the local server to ensure the real-time and security of data processing and service response.

[0044] The middleware is responsible for data forwarding and control instruction execution. It does not open network ports to the outside world, reducing the external attack surface.

[0045] The deployment and configuration of device services is the responsibility of trained professionals, ensuring correct configuration and application of the principle of least privilege.

[0046] Configuration changes are fully recorded to facilitate auditing and backtracking.

[0047] The model data and control interface released to the outside must be authenticated. The model data and control interface released by the control system must undergo identity authentication and authorization checks.

[0048] Authentication mechanisms include but are not limited to API keys, OAuth2.0, and JWT to ensure that only legitimate users can access resources.

[0049] Record logs of all access requests to monitor for unusual activity and subsequent audits.

[0050] Through the above measures, it is ensured that when third-party devices are connected to the control system, flexible dynamic configuration can be achieved while ensuring the security of the system.

[0051] The present application is described in detail below with reference to the accompanying drawings: Disadvantages of the existing technology: Currently, most equipment access uses customized processes to adjust the logic in the control system to complete the data and control support of third-party equipment. In the long run, there are too many customized logics in the control system, and the system maintenance cost gradually increases. The purpose of the present invention is to reduce the impact of third-party equipment access on the control system processing logic through dynamic configuration content with a unified format.

[0052] This application first needs to implement device modeling. The device model is defined according to the type. The attribute structure of the model is as follows Figure 1 , divided into tag domain and value domain according to whether it is mutable or immutable: the tag domain is the inherent attribute of the device, such as manufacturer, model, etc., and the attribute is read-only; the value domain contains read-only attribute data values ​​such as engineering values ​​and controllable point data values ​​(such as the color and flashing frequency attributes of the alarm light device model), and also supports dynamic addition of value domain attribute points.

[0053] As shown in the table below: The entire system manages each model through the model interface class. There is no direct association between the models. The device model needs to implement the interface of the model interface class. Among them, EventExec is a unified model event processing interface with variable parameters, which is used to control the execution model.

[0054] Device models of uncertain types are uniformly connected to third-party device models within the system. This model value domain has no fixed data points, and any attribute data reported by the protocol service will be retained.

[0055] The detailed steps are: 1. Protocol service deployment and equipment data point and control point configuration; 2. Taking ModBus as an example, according to the docking point table provided by the third-party manufacturer, define the relevant read and write attribute data point names, configure the protocol service through the application service, and create the corresponding third-party device model object in the application service during configuration; 3. After step 2, the control system has access to the data points of the third-party device; 4. Configure the mapping relationship between the device model data points and the key data points of the control system, and configure the mapping relationship between the device model and the control methods related to the control system. Data mapping: Taking the motor as an example, the data source of the front bearing temperature attribute of the motor model can be the engineering value attribute of the front bearing temperature sensor model (or a data point of a third-party manufacturer's device collected through the protocol). When the engineering value attribute data point of the current bearing temperature sensor model is updated, according to the data mapping configuration, this data value will be synchronously updated to the front bearing temperature attribute of the motor model. Data mapping only supports the mapping of basic data types, and the data types need to be similar. When updating the target data point according to the source data, if the data type does not match, the update fails and the corresponding error message is recorded. The configuration format is as follows: Control mapping: Taking the motor as an example, the high-speed speed value of the motor is set, and the control system is called to execute the motor speed regulation. The speed regulation control of the source model MotorTransloader is mapped to the target model third_001. Third_001 executes the control in sequence according to the configuration (writes the corresponding data point data value), where $0 is the speed value in the variable parameter. The variable parameters are all basic data types, and the control mapping requires the number of parameters on both sides to be consistent. Data conversion and parameter verification will be performed before control. If they do not match, control is not allowed and the corresponding error message is recorded.

[0056] as follows: 5. After step 4, the control system realizes complete third-party device access, and the data warning, business control and other processes in the control system form a complete logic. Any third-party device access has basically no impact on the control system. The system working framework is as follows: Figure 2 ; Data: Using the message bus, the data reporting TOPIC contains information such as device type and device name, and the data body contains information such as attribute name, attribute value, attribute value type, etc. The data value is updated to the corresponding attribute point of the response model in the control system through relevant information.

[0057] Control: Call through HTTP interface, write the data points specified by the device or define specific command words and multiple data points (such as the alarm light flashing command, write the two attributes of color and frequency at the same time) to perform corresponding control.

[0058] Security: Equipment access security: The framework middleware works locally, and the equipment service deployment and configuration are maintained by dedicated maintenance tools and personnel; Equipment external: The control system publishes model data to the outside, provides model data query, business function control interface, and authenticates the corresponding request. The data source model and control execution target model of the control system of this application can be adjusted dynamically to reduce the impact of third-party equipment access on the overall logic of the control system. The internal processing flow of the control system is basically fixed, reducing the risk of control system logic adjustments caused by potential third-party equipment access.

[0059] In an optional implementation, the model implementation is removed, and the control system is directly connected to the control bus and the data bus through the control configuration and the data configuration to realize device control and device data access.

[0060] The alternative solution is suitable for application services that only implement control-related functions without other complex business functions. In this case, it is necessary to specify the device service to which the target control point belongs in the configuration; the device service is not reflected in the current solution mapping configuration. When the data point of the device service is configured through the control system, the control system creates a model to automatically make corresponding associations.

Claims

1. A dynamically configurable third-party device access method, characterized in that: The following steps are involved: S1 defines the device model, which includes a label domain and a value domain; S2 protocol service configuration, for the communication protocol provided by third-party devices, defines the names of read and write attribute data points; The S3 application service configures the protocol service and creates a third-party device model object; S4 data point access, the control system accesses the data points of third-party devices, making the data available through protocol services; S5 mapping relationship configuration, configure the mapping relationship between the equipment model data points and the key data points of the control system; Configure the mapping relationship between the device model and the control method of the control system; Data mapping must ensure that data types are consistent, otherwise the update will fail and an error message will be recorded; The control mapping must ensure that the number of parameters is consistent, otherwise the control fails and an error message is recorded; S6 data and control implementation, data is transmitted through the message bus, and the data includes device type, device name, attribute name, attribute value and its type; S7 control is called through the HTTP interface to write specified data points or execute specific command words; Security is ensured, the framework middleware runs locally, the equipment service deployment and configuration are maintained by dedicated personnel, and the model data and control interfaces released to the outside are subject to request authentication.

2. A dynamically configurable third-party device access method according to claim 1, characterized in that: In the S1 defined device model, the tag domain stores the inherent attributes of the device, and the attributes are set to read-only to ensure that the device identity information cannot be changed; the value domain contains the engineering value read-only attribute data value, including the controllable point data value, and supports dynamic addition of new attribute points to meet the needs of device expansion.

3. A dynamically configurable third-party device access method according to claim 1, characterized in that: S2 protocol service configuration specific: Determine the name of the device's read and write attribute data point based on the communication protocol provided by the third-party device; The data point name includes a device-specific identifier, and the protocol service is configured using the application service. The configuration content includes the defined read and write attribute data point name; The application service creates the corresponding third-party device model object and associates it with the protocol service.

4. A dynamically configurable third-party device access method according to claim 1, characterized in that: The S3 application service configures the protocol service and creates a third-party device model object: The application service configures the protocol service through a configuration file or interface tool to specify the read and write attribute data points of the third-party device; Configuration information includes data point name, data type, and necessary information for read and write permissions; Create a third-party device model object in the application service, which implements the model interface class interface; The tag field of the model object stores the inherent properties of the device and is set to read-only; The value domain of the model object stores dynamic attribute data and supports dynamic addition of attribute points; Associate the created third-party device model object with the protocol service to ensure that the protocol service can access and update the value domain data of the model object.

5. A dynamically configurable third-party device access method according to claim 1, characterized in that: S4 data point access specific: Define the name of the device's read and write attribute data points according to the communication protocol provided by the third-party device; Create corresponding third-party device model objects through application service configuration protocol services; The protocol service parses the received data points and stores them in the corresponding third-party device model; The control system obtains data points of third-party devices through protocol services to achieve access to data points.

6. A dynamically configurable third-party device access method according to claim 1, characterized in that: S5 mapping relationship configuration details: Configure the mapping relationship between the equipment model data points and the key data points of the control system. The front bearing temperature attribute data source of the motor model is the engineering value attribute of the front bearing temperature sensor model. When the engineering value attribute data point of the current bearing temperature sensor model is updated, this data value is synchronously updated to the front bearing temperature attribute of the motor model according to the pre-configured mapping relationship; If the data types do not match, the update fails and an error message is logged; Configure the mapping relationship between the device model and the control method of the control system. When the high-speed value of the motor is set, the control system calls and executes the motor speed regulation. The speed control of the source model MotorTransloader is mapped to the target model third_001, and third_001 executes the control in sequence according to the configuration; The speed value $0 in the variable parameter is the basic data type, and the control mapping needs to ensure that the number of parameters on both sides is consistent; Data conversion and parameter verification are performed before control. If they do not match, control fails and error information is recorded.

7. A dynamically configurable third-party device access method according to claim 1, characterized in that: S7 security guarantees include: The framework middleware is deployed on the local server. The middleware is responsible for data forwarding and control instruction execution, and the network port is not open to the outside world. The deployment and configuration of device services are the responsibility of trained professionals to ensure correct configuration and the application of the principle of least privilege. Configuration changes are recorded completely to facilitate auditing and backtracking. Model data and control interfaces released to the outside are subject to authentication requests. Model data and control interfaces released by the control system must undergo identity authentication and authorization checks. Authentication mechanisms include API keys, OAuth2.0, and JWT to ensure that only legitimate users can access resources. All access requests are logged.

Images