A multi-protocol parsing and edge data quality processing communication management module system for integrated energy equipment

Abstract

This invention relates to the field of integrated energy equipment access and edge data processing technology, and discloses a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment. The communication management module system is located between the field equipment network and the cloud-based operation and maintenance system, and includes a multi-protocol interface unit, a protocol adapter unit, a protocol parsing and scheduling unit, a point template library unit, an object relationship mapping unit, an edge data quality unit, a standard event encapsulation unit, a local caching and replay unit, and a security authentication and encryption unit. This invention can improve the semantic uniformity of data and diagnostic availability after multi-protocol equipment access, and reduce the possibility of false real-time alarms triggered by retransmission events.

Description

Technical Field

[0001] This invention relates to the field of integrated energy equipment access and edge data processing technology, and in particular to a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment. Background Technology

[0002] Integrated energy equipment is typically distributed in energy stations, building automation systems, power distribution systems, air conditioning terminal systems, metering systems, and industrial IoT systems. Different manufacturers and different types of field equipment often use different communication protocols. Existing systems generally achieve field equipment access through protocol gateways, industrial data acquisition devices, IoT platform device access SDKs, or EMS / BAS system internal drivers.

[0003] The above solutions typically focus on protocol conversion and data acquisition, emphasizing the reading of field equipment data and its conversion into a unified communication format. However, in integrated energy operation and maintenance scenarios, acquiring raw data points does not equate to obtaining data that can be used for diagnosis, alarms, work order association, or evidence tracing. The same measurement point on different devices may have issues such as different protocol addresses, register definitions, multipliers, units, sampling periods, timestamp formats, and inconsistent quality fields. Furthermore, the subsequent diagnostic system needs to determine which project, site, system, equipment, component, loop, or spatial object the point belongs to, whether the point is necessary for diagnosis, whether the data at the point has reached a diagnostically readable state, and whether the network outage retransmission event should be used as the basis for triggering a real-time alarm.

[0004] Existing protocol gateways can typically only perform format conversion, lacking point template processing, object relationship mapping, and diagnostic availability quality evaluation for integrated energy equipment object models. The data uploaded by existing collectors are mostly loosely packed raw points, requiring cloud-based operation and maintenance systems to perform unit conversion, field cleaning, object binding, quality judgment, and alarm deduplication again. Existing network outage retransmission mechanisms can also easily mistake retransmission events for real-time events, thus affecting the accuracy of real-time alarms and work order triggering.

[0005] Therefore, there is an urgent need for a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment. Summary of the Invention

[0006] The purpose of this invention is to overcome one or more of the above-mentioned existing technical problems and provide a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment.

[0007] To achieve the above objectives, the present invention provides a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment, comprising: The communication management module system is located between the field equipment network and the cloud operation and maintenance system. It includes a multi-protocol interface unit, a protocol adapter unit, a protocol parsing and scheduling unit, a point template library unit, an object relationship mapping unit, an edge data quality unit, a standard event encapsulation unit, a local caching and replay unit, and a security authentication and encryption unit. The multi-protocol interface unit is used to connect integrated energy equipment that uses different communication protocols; The protocol adapter unit reads the original frames or original messages of the field devices in response to the scheduling instructions of the protocol parsing and scheduling unit; The point template library unit is divided into a protocol layer template area, a physical quantity template area, and an operation and maintenance semantic template area, so that the original point will enter the object relationship mapping unit after passing through protocol layer field parsing, physical quantity field conversion, and operation and maintenance semantic field verification in sequence. The object-relational mapping unit binds points to project, site, system, device, component, loop, or space objects; The edge data quality unit writes a diagnostic availability quality vector and quality tag before standard events are generated; The standard event encapsulation unit encapsulates the collected data, object relationships, and diagnostic availability quality vectors into standard events; the local caching and replay unit is used to cache standard events when they are unreachable in the cloud and retransmit them in order after the network is restored.

[0008] According to one aspect of the present invention, the multi-protocol interface unit is provided with at least one hardware interface selected from RS485 interface, RS232 interface, Ethernet interface, 4G / 5G communication interface, CAN interface, digital input / output interface, and analog input / output interface, or is provided with a software driver interface corresponding to the hardware interface. The multi-protocol interface unit is connected to the protocol adapter unit via an isolation circuit to form an isolated connection between the field-side communication line and the protocol adaptation processing line; The protocol adapter unit includes at least two of the following: Modbus adapter, BACnet adapter, OPCUA adapter, MQTT adapter, HTTP adapter, DL / T adapter, and proprietary protocol adapter.

[0009] According to one aspect of the present invention, the protocol layer template area is used to store at least one protocol layer field selected from device type, protocol address, register, data type, byte order, and vendor identifier; The physical quantity template area is used to store at least one of the following physical quantity layer fields: unit, scale factor, offset, physical range, standard unit, and calibration status; The operation and maintenance semantic template area is used to store at least one of the operation and maintenance semantic layer fields, including device object, measurement point purpose, required point marker, diagnostic event family marker, and point grouping marker. The point template library unit performs template processing on the original points in the order of protocol layer template area, physical quantity template area and operation and maintenance semantic template area. When the template verification of any layer fails, a corresponding quality mark is generated and the quality mark is passed to the edge data quality unit and standard event encapsulation unit.

[0010] According to one aspect of the present invention, the protocol parsing and scheduling unit is used to generate a collection scheduling sequence based on the device template, sampling period, scheduling priority, network status and protocol adapter status; When multiple protocol channels exist for the same device, or when there are primary and backup sources at the same location, the protocol parsing and scheduling unit determines the primary source based on template version priority, sampling freshness, diagnostic availability quality vector, and communication success rate. Point data obtained from the primary source enters the point template library unit for template parsing, while point data obtained from non-primary sources is used as the verification source and written into the diagnostic availability quality vector or quality marker. When the communication success rate of the primary source is lower than a preset threshold or the sampling freshness is lower than a preset threshold, the protocol parsing and scheduling unit recalculates the source order and records the source switching information.

[0011] According to one aspect of the present invention, the object relationship mapping unit is used to receive point data processed by the point template library unit, and generate an object path according to at least one of the following fields: tenant identifier, project identifier, site identifier, system identifier, subsystem identifier, equipment identifier, component identifier, loop identifier, space identifier, and point identifier; When the object relationship mapping unit detects missing device objects, inconsistent component relationships, missing spatial bindings, incorrect point grouping, or mismatched diagnostic event families, it writes the topology integrity field into the diagnostic availability quality vector and outputs an object relationship anomaly flag to the standard event encapsulation unit, so that the standard event carries the quality status corresponding to the object path.

[0012] According to one aspect of the present invention, the edge data quality unit is located between the object relation mapping unit and the standard event encapsulation unit, and is used to perform at least one of the following processing on the point data that has completed object relation mapping: timestamp delay detection, missing value detection, outlier detection, unit error detection, horizontal line detection, jump detection, duplicate data detection and communication interruption detection, and form a diagnostic availability quality vector. The diagnostic availability quality vector includes fields for freshness, continuity, physical range, unit confidence, calibration status, topology integrity, and diagnostic requirement point coverage. The edge data quality unit generates four levels of status based on the diagnostic availability quality vector: archived only, displayable, diagnostic, or triggerable work orders. When at least one field in the diagnostic availability quality vector is below the corresponding threshold, the edge data quality unit retains the upload status of the corresponding point data and writes a low-quality flag, an undiagnostic status field, or an untriggerable status field into the event to be encapsulated.

[0013] According to one aspect of the present invention, a standard event encapsulation unit is used to encapsulate acquired data, object path, point identifier, numerical value, unit, diagnostic availability quality vector, quality marker, set of diagnostic necessary points, set of missing necessary points, diagnostic availability status, original acquisition time, idempotent key and real-time marker into a standard event; The standard event type is set as telemetry event, alarm event, defective bit event, communication anomaly event, or data quality event; When the coverage of diagnostic essential points is lower than a preset threshold, the standard event encapsulation unit generates a defect bit event, a data quality event, or a template revision item.

[0014] According to one aspect of the present invention, the local caching and replay unit is provided with a local caching medium and a replay queue, wherein the local caching medium is at least one of an SQLite database, a file queue, an embedded time-series library, or a message queue; When the cloud-based operation and maintenance system is unreachable, message signing fails, the timestamp window does not meet the upload conditions, or the encrypted channel is unavailable, the local cache and replay unit writes the standard events to be uploaded into the replay queue and records the sequence number, original collection time, replay batch number, replay reason, and real-time mark for the standard events to be uploaded. After the network is restored, the local cache and replay unit retransmits the cached events in the order of the original acquisition time and sequence number, sets the real-time flag of the retransmitted events to a non-real-time state, and sets the real-time alarm trigger field of the retransmitted events to an untriggerable state.

[0015] According to one aspect of the present invention, a template version management unit is further provided, which is connected to the point template library unit, the protocol parsing and scheduling unit and the standard event encapsulation unit, and is provided with a current template area, a candidate template area and a rollback template area; When the cloud-based operation and maintenance system issues candidate site templates, the template version management unit performs signature verification, version verification, applicable device verification, and rollback packet verification on the candidate site templates, and enables the candidate site templates and the current site templates to parse the same original frame or original message in parallel during the shadow parsing cycle. If the parsing success rate, unit confidence and object relationship matching rate of the candidate point template all reach the corresponding threshold, and the decrease in diagnostic usability quality vector does not exceed the threshold, then the candidate point template will be switched to the current point template in the next sampling period. If the candidate point template signature verification fails, the applicable equipment does not match, the acquisition failure rate exceeds the threshold, or the diagnostic availability quality vector decreases beyond the threshold, the template will be rolled back and a template failure event will be generated.

[0016] According to one aspect of the present invention, a configuration and diagnostic interface unit and a status indication and maintenance unit are also provided. The configuration and diagnostic interface unit is connected to a protocol adapter unit, a protocol parsing and scheduling unit, a point template library unit, a local cache and replay unit and a template version management unit, and is used to perform local configuration, remote configuration, template download, driver status reading, acquisition status reading and debug log output. The status indication and maintenance unit is equipped with an operation indicator, a communication indicator, a fault indicator, a maintenance button or a maintenance port, used to display data acquisition failure, cache backlog, cloud connection status, template switching status and security authentication status; The security authentication and encryption unit manages access credentials and message signing keys using at least one of the following methods: APIKey, digital certificate, TLS channel, national cryptographic algorithm, or secure storage area; The standard event encapsulation unit sends standard events to the cloud operation and maintenance system through at least one of the following methods: MQTT topic, Webhook interface, HTTP interface, or cloud message queue.

[0017] Based on this, the beneficial effects of the present invention are as follows: the communication management module system processes the protocol layer fields, physical quantity fields and operation and maintenance semantic fields in layers on the field side, so that the original points form point data with unified field meanings and object relationships before uploading, reducing the secondary cleaning of the original points by the cloud operation and maintenance system. Before standard events are generated, edge data quality units write diagnostic availability quality vectors, enabling cloud-based operations and maintenance systems to determine the usage status of standard events based on freshness, continuity, physical range, unit reliability, calibration status, topology integrity, and coverage of necessary diagnostic points. Standard events carry object paths, idempotent keys, original acquisition times, and real-time flags, providing a unified field basis for event deduplication, object association, historical tracing, and real-time alarm triggering. The local caching and replay unit caches standard events in sequence when the network is disconnected or the cloud is unreachable, and writes the replay batch number, replay reason and non-real-time status when retransmitting, reducing the possibility of retransmitted events being misjudged as real-time alarms. The template version management unit enables field equipment template updates to be switched only after the conditions of parsing success rate, unit reliability, object relationship matching rate, and diagnostic availability quality vector are met through shadow parsing and rollback processing of candidate point templates. Attached Figure Description

[0018] Figure 1This is a schematic diagram of the system architecture of a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment, according to an exemplary embodiment. Figure 2 This is a flowchart illustrating a multi-protocol parsing and edge data quality processing communication management module system for integrated energy equipment, according to an exemplary embodiment. Figure 3 This is a point object relationship mapping diagram of a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment, according to an exemplary embodiment. Figure 4 This is a flowchart illustrating the quality vector and event encapsulation of a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment, according to an exemplary embodiment. Figure 5 This is a timing diagram illustrating the network outage buffering and retransmission of a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment, according to an exemplary embodiment. Detailed Implementation

[0019] The invention will now be discussed with reference to exemplary embodiments. It should be understood that the described embodiments are merely intended to enable those skilled in the art to better understand and thus implement the invention, and are not intended to imply any limitation on the scope of the invention.

[0020] As used herein, the term “comprising” and its variations are to be interpreted as open-ended terms meaning “including but not limited to”. The term “based on” is to be interpreted as “at least partially based on”, and the terms “one embodiment” and “an embodiment” are to be interpreted as “at least one embodiment”.

[0021] According to one embodiment of the present invention, Figure 1 This is a schematic diagram of the system architecture of a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment, according to an exemplary embodiment. Figure 1 As shown, to achieve the above objectives, the present invention provides a multi-protocol parsing and edge data quality processing communication management module system for integrated energy equipment, comprising: The communication management module system is located between the field equipment network and the cloud operation and maintenance system. It includes a multi-protocol interface unit, a protocol adapter unit, a protocol parsing and scheduling unit, a point template library unit, an object relationship mapping unit, an edge data quality unit, a standard event encapsulation unit, a local caching and replay unit, and a security authentication and encryption unit. The multi-protocol interface unit is used to connect integrated energy equipment that uses different communication protocols; The protocol adapter unit reads the original frames or original messages of the field devices in response to the scheduling instructions of the protocol parsing and scheduling unit; The point template library unit is divided into a protocol layer template area, a physical quantity template area, and an operation and maintenance semantic template area, so that the original point will enter the object relationship mapping unit after passing through protocol layer field parsing, physical quantity field conversion, and operation and maintenance semantic field verification in sequence. The object-relational mapping unit binds points to project, site, system, device, component, loop, or space objects; The edge data quality unit writes a diagnostic availability quality vector and quality tag before standard events are generated; The standard event encapsulation unit encapsulates the collected data, object relationships, and diagnostic availability quality vectors into standard events; the local caching and replay unit is used to cache standard events when they are unreachable in the cloud and retransmit them in order after the network is restored.

[0022] According to one embodiment of the present invention, the multi-protocol interface unit is provided with at least one hardware interface selected from RS485 interface, RS232 interface, Ethernet interface, 4G / 5G communication interface, CAN interface, digital input / output interface, and analog input / output interface, or is provided with a software driver interface corresponding to the hardware interface. The multi-protocol interface unit is connected to the protocol adapter unit via an isolation circuit to form an isolated connection between the field-side communication line and the protocol adaptation processing line; The protocol adapter unit includes at least two of the following: Modbus adapter, BACnet adapter, OPCUA adapter, MQTT adapter, HTTP adapter, DL / T adapter, and proprietary protocol adapter.

[0023] According to one embodiment of the present invention, the protocol layer template area is used to store at least one protocol layer field selected from device type, protocol address, register, data type, byte order, and vendor identifier; The physical quantity template area is used to store at least one of the following physical quantity layer fields: unit, scale factor, offset, physical range, standard unit, and calibration status; The operation and maintenance semantic template area is used to store at least one of the operation and maintenance semantic layer fields, including device object, measurement point purpose, required point marker, diagnostic event family marker, and point grouping marker. The point template library unit performs template processing on the original points in the order of protocol layer template area, physical quantity template area and operation and maintenance semantic template area. When the template verification of any layer fails, a corresponding quality mark is generated and the quality mark is passed to the edge data quality unit and standard event encapsulation unit.

[0024] According to one embodiment of the present invention, the protocol parsing and scheduling unit is used to generate a collection scheduling sequence based on the device template, sampling period, scheduling priority, network status and protocol adapter status; When multiple protocol channels exist for the same device, or when there are primary and backup sources at the same location, the protocol parsing and scheduling unit determines the primary source based on template version priority, sampling freshness, diagnostic availability quality vector, and communication success rate. Point data obtained from the primary source enters the point template library unit for template parsing, while point data obtained from non-primary sources is used as the verification source and written into the diagnostic availability quality vector or quality marker. When the communication success rate of the primary source is lower than a preset threshold or the sampling freshness is lower than a preset threshold, the protocol parsing and scheduling unit recalculates the source order and records the source switching information.

[0025] According to one embodiment of the present invention, the object relationship mapping unit is used to receive the point data processed by the point template library unit, and generate an object path according to at least one of the following fields: tenant identifier, project identifier, site identifier, system identifier, subsystem identifier, equipment identifier, component identifier, loop identifier, space identifier and point identifier; When the object relationship mapping unit detects missing device objects, inconsistent component relationships, missing spatial bindings, incorrect point grouping, or mismatched diagnostic event families, it writes the topology integrity field into the diagnostic availability quality vector and outputs an object relationship anomaly flag to the standard event encapsulation unit, so that the standard event carries the quality status corresponding to the object path.

[0026] According to one embodiment of the present invention, the edge data quality unit is located between the object relation mapping unit and the standard event encapsulation unit, and is used to perform at least one of the following processing on the point data that has completed object relation mapping: timestamp delay detection, missing value detection, outlier detection, unit error detection, horizontal line detection, jump detection, duplicate data detection and communication interruption detection, and form a diagnostic availability quality vector. The diagnostic availability quality vector includes fields for freshness, continuity, physical range, unit confidence, calibration status, topology integrity, and diagnostic requirement point coverage. The edge data quality unit generates four levels of status based on the diagnostic availability quality vector: archived only, displayable, diagnostic, or triggerable work orders. When at least one field in the diagnostic availability quality vector is below the corresponding threshold, the edge data quality unit retains the upload status of the corresponding point data and writes a low-quality flag, an undiagnostic status field, or an untriggerable status field into the event to be encapsulated.

[0027] According to one embodiment of the present invention, the standard event encapsulation unit is used to encapsulate the collected data, object path, point identifier, numerical value, unit, diagnostic availability quality vector, quality marker, set of necessary diagnostic points, set of missing necessary points, diagnostic availability status, original acquisition time, idempotent key and real-time marker into a standard event; The standard event type is set as telemetry event, alarm event, defective bit event, communication anomaly event, or data quality event; When the coverage of diagnostic essential points is lower than a preset threshold, the standard event encapsulation unit generates a defect bit event, a data quality event, or a template revision item.

[0028] According to one embodiment of the present invention, the local caching and replay unit is provided with a local caching medium and a replay queue, wherein the local caching medium is at least one of an SQLite database, a file queue, an embedded time-series library, or a message queue; When the cloud-based operation and maintenance system is unreachable, message signing fails, the timestamp window does not meet the upload conditions, or the encrypted channel is unavailable, the local cache and replay unit writes the standard events to be uploaded into the replay queue and records the sequence number, original collection time, replay batch number, replay reason, and real-time mark for the standard events to be uploaded. After the network is restored, the local cache and replay unit retransmits the cached events in the order of the original acquisition time and sequence number, sets the real-time flag of the retransmitted events to a non-real-time state, and sets the real-time alarm trigger field of the retransmitted events to an untriggerable state.

[0029] According to one embodiment of the present invention, a template version management unit is further provided. The template version management unit is connected to the point template library unit, the protocol parsing and scheduling unit and the standard event encapsulation unit, and is provided with a current template area, a candidate template area and a rollback template area. When the cloud-based operation and maintenance system issues candidate site templates, the template version management unit performs signature verification, version verification, applicable device verification, and rollback packet verification on the candidate site templates, and enables the candidate site templates and the current site templates to parse the same original frame or original message in parallel during the shadow parsing cycle. If the parsing success rate, unit confidence and object relationship matching rate of the candidate point template all reach the corresponding threshold, and the decrease in diagnostic usability quality vector does not exceed the threshold, then the candidate point template will be switched to the current point template in the next sampling period. If the candidate point template signature verification fails, the applicable equipment does not match, the acquisition failure rate exceeds the threshold, or the diagnostic availability quality vector decreases beyond the threshold, the template will be rolled back and a template failure event will be generated.

[0030] According to one embodiment of the present invention, a configuration and diagnostic interface unit and a status indication and maintenance unit are further provided. The configuration and diagnostic interface unit is connected to a protocol adapter unit, a protocol parsing and scheduling unit, a point template library unit, a local cache and replay unit and a template version management unit, and is used to perform local configuration, remote configuration, template download, driver status reading, acquisition status reading and debugging log output. The status indication and maintenance unit is equipped with an operation indicator, a communication indicator, a fault indicator, a maintenance button or a maintenance port, used to display data acquisition failure, cache backlog, cloud connection status, template switching status and security authentication status; The security authentication and encryption unit manages access credentials and message signing keys using at least one of the following methods: APIKey, digital certificate, TLS channel, national cryptographic algorithm, or secure storage area; The standard event encapsulation unit sends standard events to the cloud operation and maintenance system through at least one of the following methods: MQTT topic, Webhook interface, HTTP interface, or cloud message queue.

[0031] According to one embodiment of the present invention, the communication management module system is set between the field device network and the cloud operation and maintenance system. The field device network may include chillers, cooling towers, water pumps, valves, electricity meters, water meters, gas meters, heat meters, temperature and humidity sensors, air conditioning units, VAV terminals, FCU terminals, power distribution equipment and other integrated energy equipment. The cloud operation and maintenance system may include integrated energy management system, building automation system, energy station operation and maintenance system, chiller plant PHM system, building operation and maintenance system or industrial Internet of Things platform.

[0032] The multi-protocol interface unit connects to the field device network. The protocol adapter unit connects to the multi-protocol interface unit. The protocol parsing and scheduling unit connects to the protocol adapter unit. The point template library unit connects to the protocol parsing and scheduling unit and the object relationship mapping unit respectively. The object relationship mapping unit connects to the edge data quality unit. The edge data quality unit connects to the standard event encapsulation unit. The standard event encapsulation unit communicates with the cloud operation and maintenance system through the security authentication and encryption unit. The local caching and replay unit connects to the standard event encapsulation unit and the security authentication and encryption unit, and is used to cache the standard events to be uploaded when the upload conditions are not met.

[0033] The communication management module system can be installed inside an industrial enclosure. The multi-protocol interface unit includes multi-protocol interface terminals located on the side or terminal block area of ​​the industrial enclosure. The protocol adapter unit includes a protocol adapter processor or pluggable communication board connected to the multi-protocol interface terminals. The point template library unit includes a point template storage area. The object relationship mapping unit includes an object relationship mapping table. The edge data quality unit includes a quality assessment processing unit. The local cache and replay unit includes a local cache medium and a replay queue. The security authentication and encryption unit includes a security authentication chip or a security storage area. The configuration and diagnostic interface unit includes a configuration and maintenance interface. The status indication and maintenance unit includes an operation indicator, a communication indicator, and a fault indicator.

[0034] Protocol adapters can be installed in an industrial chassis as pluggable communication boards, or as a combination of protocol adapter processors and interface drivers. Pluggable communication boards are added, removed, or replaced according to the protocol types of equipment in the project site. Protocol adapter processors are used to perform protocol identification, raw frame reading, message parsing, and adapter status feedback. Point template storage, object relationship mapping tables, local buffer media, and replay queues can be located in the same non-volatile memory or in separate storage areas. Security authentication chips or secure storage areas are used to store access credentials, digital certificates, message signing keys, or encryption parameters.

[0035] The multi-protocol interface unit can be implemented using a combination of hardware interfaces and software driver interfaces. The hardware interfaces include at least one of the following: RS485 interface, RS232 interface, Ethernet interface, 4G / 5G communication interface, CAN interface, digital input / output interface, and analog input / output interface. The software driver interface corresponds to the aforementioned hardware interfaces and is used to carry protocol drivers, serial port parameters, network connection parameters, drive status, and sampling parameters. The multi-protocol interface unit is connected to the protocol adapter unit via an isolation circuit, establishing electrical or logical isolation between the field-side communication lines and the protocol adaptation processing lines to adapt to the wiring environments of different field devices.

[0036] The protocol adapter unit includes at least two of the following: Modbus adapter, BACnet adapter, OPCUA adapter, MQTT adapter, HTTP adapter, DL / T adapter, and proprietary protocol adapter. Each protocol adapter is used to read the raw frames or raw messages of the corresponding protocol. Responding to the scheduling instructions of the protocol parsing and scheduling unit, the protocol adapter unit reads field device data according to the device address, protocol address, register, topic, interface address, or proprietary protocol parameters. For protocol adapters with configurable start / stop states, the protocol parsing and scheduling unit can select to enable or disable the corresponding protocol adapter based on the driver status, network status, or device template.

[0037] The protocol parsing and scheduling unit reads the device template, sampling period, scheduling priority, network status, and protocol adapter status, and forms a data acquisition and scheduling sequence. This sequence may include device identifier, protocol type, sampling period, sampling order, number of retries, timeout time, and adapter identifier. When multiple protocol channels exist for the same device (e.g., the same meter accesses via Modbus and HTTP simultaneously), the protocol parsing and scheduling unit determines the primary source based on template version priority, sampling freshness, diagnostic availability quality vector, and communication success rate. When primary and backup sources exist for the same location, the location data obtained from the primary source enters the location template library unit for template parsing. Location data from non-primary sources is used as a verification source and written into the diagnostic availability quality vector or quality flag, without directly overwriting the primary source data. When the communication success rate or sampling freshness of the primary source falls below a preset threshold, the protocol parsing and scheduling unit recalculates the source order and writes the source switching information to the scheduling log or pending encapsulation event.

[0038] According to one embodiment of the present invention, Figure 2 This is a flowchart illustrating a multi-protocol parsing and edge data quality processing communication management module system for integrated energy equipment, according to an exemplary embodiment. Figure 2 As shown, the multi-protocol parsing process includes reading raw frames or raw messages, protocol layer parsing, physical quantity conversion, operation and maintenance semantic verification, object relationship mapping, diagnostic availability quality vector generation, and standard event encapsulation. Specifically, the protocol adapter unit first selects an adapter based on the device protocol, device vendor, and point template version, and then reads the raw data corresponding to the device address or point register. For register-type protocols, protocol layer parsing may include register address parsing, data type parsing, byte order parsing, and vendor identifier parsing. For message-type protocols, protocol layer parsing may include topic parsing, field path parsing, message body parsing, and timestamp parsing.

[0039] The point template library unit includes a protocol layer template area, a physical quantity template area, and an operation and maintenance semantic template area. The protocol layer template area stores at least one protocol layer field, including device type, protocol address, register, data type, byte order, and vendor identifier. The physical quantity template area stores at least one physical quantity layer field, including unit, scale factor, offset, physical range, standard unit, and calibration status. The operation and maintenance semantic template area stores at least one operation and maintenance semantic layer field, including device object, measurement point purpose, required point marker, diagnostic event family marker, and point grouping marker.

[0040] In a specific processing step, the protocol layer template area first parses the original point value based on the protocol address, register, data type, and byte order. The physical quantity template area then performs field conversion on the original point value based on the scaling factor, offset, source unit, standard unit, and physical range. The operation and maintenance semantic template area then performs semantic verification based on the device object, measurement point purpose, necessary point marker, diagnostic event family marker, and point grouping marker. The processing logic can be represented as follows: adapter=select_adapter(device.protocol,device.vendor,device.template_version) raw_payload=adapter.read(device.address,point.registers) value=parse(raw_payload,point.data_type,point.byte_order) value=value×point.scale+point.offset value=convert_unit(value,point.source_unit,point.standard_unit) In this context, adapter represents the protocol adapter, raw_payload represents the raw frame or raw message, point.data_type represents the point data type, point.byte_order represents the byte order, point.scale represents the scaling factor, point.offset represents the offset, point.source_unit represents the source unit, and point.standard_unit represents the standard unit.

[0041] When any template in the protocol layer template area, physical quantity template area, or operation and maintenance semantic template area fails verification, the point template library unit generates a corresponding quality tag. For example, if the protocol layer field verification fails, a protocol field anomaly tag can be generated; if the physical quantity field verification fails, a unit anomaly, multiplier anomaly, offset anomaly, or physical range anomaly tag can be generated; if the operation and maintenance semantic field verification fails, a device object missing, measurement point purpose anomaly, required point tag missing, point grouping error, or diagnostic event family mismatch tag can be generated. These quality tags are passed to the edge data quality unit and the standard event encapsulation unit, enabling the standard events to carry the abnormal states during the template processing.

[0042] According to one embodiment of the present invention, Figure 3This is a point object relationship mapping diagram illustrating a multi-protocol parsing and edge data quality processing communication management module system for integrated energy equipment, as shown in an exemplary embodiment. Figure 3 As shown, the object relationship mapping unit binds the point data processed by the point template library unit to project, site, system, equipment, component, loop, or space objects. The object relationship mapping unit can generate object paths according to at least one of the following fields: tenant identifier, project identifier, site identifier, system identifier, subsystem identifier, equipment identifier, component identifier, loop identifier, space identifier, and point identifier. The object path can be represented as "project / site / system / equipment / component / point", or it can be extended to "tenant / project / site / system / subsystem / equipment / loop / space / point" depending on the application scenario.

[0043] In the energy station scenario, the object path can be "a project / cooling station / cooling tower / fan / current". In the BAS scenario, the object path can be "a project / building automation system / air conditioning unit / supply air temperature". In the meter acquisition scenario, the object path can be "a project / power distribution system / meter / active energy". When the object relationship mapping unit detects missing equipment objects, inconsistent component relationships, missing spatial bindings, incorrect point grouping, or mismatched diagnostic event families, it writes the topology integrity field into the diagnostic availability quality vector and outputs an object relationship anomaly flag to the standard event encapsulation unit. The object relationship anomaly flag is used to make the standard event carry the quality status corresponding to the object path.

[0044] The edge data quality unit performs at least one of the following processing steps on the point data for which object relation mapping has been completed: timestamp delay detection, missing value detection, outlier detection, unit error detection, horizontal line detection, jump detection, duplicate data detection, and communication interruption detection. The edge data quality unit forms a diagnostic usability quality vector, which includes at least the fields of freshness, continuity, physical extent, unit reliability, calibration status, topology integrity, and diagnostically necessary point coverage.

[0045] Freshness indicates the degree of matching between the acquisition time and the current processing time of the data at the location; continuity indicates the degree of continuity of the data at the location within the sampling period; physical range indicates whether the value at the location is within the allowable range of the corresponding physical quantity; unit reliability indicates the reliability of the source unit, standard unit, and unit conversion relationship; calibration status indicates whether the calibration information of the corresponding device or location meets the template requirements; topology completeness indicates whether the relationships between objects, devices, components, spaces, and location groupings are complete; and diagnostic necessary point coverage indicates the proportion of valid data obtained in the set of locations required for a certain diagnostic event family.

[0046] According to one embodiment of the present invention, Figure 4 This is a flowchart illustrating the quality vector and event encapsulation process of a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment, according to an exemplary embodiment. Figure 4 As shown, the diagnostic availability quality vector is input into the quality vector unit from fields such as freshness, continuity, physical range, unit confidence, calibration status, topology integrity, and diagnostic necessity point coverage. The quality vector unit outputs four levels of status based on the threshold values ​​of each field: archive only, displayable, diagnosable, or triggerable work order. When freshness is insufficient but the data value is still within the physical range, a displayable status can be generated. When continuity or diagnostic necessity point coverage is insufficient, an undiagnosable status can be generated. When unit confidence is insufficient, calibration status is abnormal, or topology integrity is insufficient, a low-quality flag, data quality event, or defect bit event can be generated. When each quality field reaches its corresponding threshold and meets the requirements of the diagnostic event family, a diagnosable status or triggerable work order status can be generated. The diagnostic availability quality vector can be represented as: quality_vector={ freshness_score continuity_score, physical_range_score, unit_trust_score, calibration_score, topology_integrity_score, required_point_coverage } Among them, freshness_score represents freshness, continuity_score represents continuity, physical_range_score represents physical range, unit_trust_score represents unit trust, calibration_score represents calibration status, topology_integrity_score represents topology integrity, and required_point_coverage represents coverage of diagnostically required points.

[0047] The diagnostic availability status can be determined according to the following conditions: diagnosis_ready= freshness score ≥ F and continuity_score≥C and physical_range_score≥R andrequired_point_coverage≥P Wherein, F represents the freshness threshold, C represents the continuity threshold, R represents the physical range threshold, and P represents the diagnostic necessary point coverage threshold. The above thresholds can be determined by the configuration issued by the point template, device template, diagnostic event family, or cloud operation and maintenance system.

[0048] The edge data quality unit generates four levels of status based on the diagnostic availability quality vector: archived only, displayable, diagnosable, or triggerable. When the diagnostic availability quality vector is below the corresponding threshold, the communication management module system can still retain the upload status of the corresponding data point, but write a low-quality flag, an undiagnosable status field, or an untriggerable status field into the event to be encapsulated. For example, when the meter multiplier is suspected to be abnormal, the corresponding data can be marked as displayable, but an energy consumption abnormality work order cannot be triggered; when the chilled water supply and return water temperatures lack the necessary diagnostic points, a defective bit event or a data quality event can be generated, but the relevant events of that chiller station are not marked as diagnosable.

[0049] The standard event encapsulation unit encapsulates the collected data, object path, point identifier, numerical value, unit, diagnostic availability quality vector, quality marker, set of necessary diagnostic points, set of missing necessary points, diagnostic availability status, original acquisition time, idempotent key, and real-time marker into a standard event. A standard event can be represented as: event={ event_type, tenant_id, project_id, object_path, point_id, value, unit quality_vector, quality_flags, required_points, missing_required_points, diagnosis_ready, timestamp, idempotency_key, realtime } Among them, event_type represents the event type, tenant_id represents the tenant identifier, project_id represents the project identifier, object_path represents the object path, point_id represents the point identifier, value represents the numerical value, unit represents the unit, quality_vector represents the diagnostic availability quality vector, quality_flags represents the quality flags, required_points represents the set of diagnostic required points, missing_requiredpoints represents the set of missing required points, diagnosis_ready represents the diagnostic availability status, timestamp represents the original acquisition time, idempotency_key represents the idempotency key, and realtime represents the real-time flag.

[0050] The standard event type can be set to telemetry event, alarm event, defect bit event, communication anomaly event, or data quality event. Telemetry events are used to represent regular point data that has completed template processing and object relationship mapping; alarm events are used to represent data that meets alarm conditions and reaches the corresponding quality status; defect bit events are used to represent insufficient coverage of diagnostic necessary points or missing necessary points; communication anomaly events are used to represent protocol channel anomalies, adapter anomalies, or communication interruptions; data quality events are used to represent unit anomalies, multiplier anomalies, physical range anomalies, flat lines, jumps, duplicate data, or other quality anomalies. When the coverage of diagnostic necessary points is lower than a preset threshold, the standard event encapsulation unit generates a defect bit event, a data quality event, or a template revision item.

[0051] When a standard event reaches the triggerable work order state, the standard event encapsulation unit writes the triggerable work order status field into the standard event; when a standard event does not reach the triggerable work order state, the standard event encapsulation unit writes the non-triggerable status field into the standard event. Thus, when a standard event is uploaded, it simultaneously carries the data value, object relationship, and quality status, allowing the system to subsequently distinguish between displayable data, diagnostic data, and triggerable work order data.

[0052] According to one embodiment of the present invention, Figure 5 This is a timing diagram illustrating the network outage buffering and retransmission of a communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment, according to an exemplary embodiment. Figure 5As shown, the local caching and replay unit caches standard events when the cloud-based operations and maintenance system is unavailable, and retransmits them in order after the network is restored. The local caching and replay unit has a local cache medium and a replay queue. The local cache medium can be an SQLite database, a file queue, an embedded time-series library, or a message queue. When the cloud-based operations and maintenance system is unavailable, message signing fails, the timestamp window does not meet the upload conditions, or the encrypted channel is unavailable, the local caching and replay unit writes the standard events to be uploaded into the replay queue and records the sequence number, original acquisition time, replay batch number, replay reason, and real-time marker.

[0053] When a standard event to be uploaded is written to the local cache queue, the local cache and replay unit records the sequence_no, original_timestamp, replay_batch_id, replay_reason, and realtime fields of that standard event to be uploaded. Here, sequence_no represents the sequence number, original_timestamp represents the original acquisition time, replay_batch_id represents the replay batch number, replay_reason represents the replay reason, and realtime represents the real-time marker.

[0054] After network recovery, the local cache and replay unit retransmits cached events in the order of the combination of `original_timestamp` and `sequence_no`, sets the `realtime` field of the retransmitted event to `false`, and sets the real-time alarm trigger field to an untriggerable state. Retransmitted events are only used for historical data completion, trend recovery, and evidence tracing, and are not used to trigger subsequent work orders as newly occurring real-time alarm events. For standard events entering the local cache queue due to network anomalies, message signature failures, timestamp windows not meeting upload conditions, or unavailable encrypted channels, the local cache and replay units record the corresponding replay reasons to facilitate classification and processing of retransmitted events by the cloud-based operations and maintenance system.

[0055] The security authentication and encryption unit manages access credentials, message signatures, timestamp windows, TLS channels, or equivalent encryption methods. It can manage access credentials and message signing keys using at least one of the following methods: APIKey, digital certificate, TLS channel, national cryptographic algorithms, or secure storage. The standard event encapsulation unit can send standard events to the cloud-based operations and maintenance system via at least one of the following methods: MQTT topic, Webhook interface, HTTP interface, or cloud message queue. When message signing fails, the timestamp window does not meet the upload conditions, or the encryption channel is unavailable, the standard event enters the local cache and replay unit to await subsequent retransmission.

[0056] The communication management module system may also include a template version management unit. This unit is connected to the site template library unit, protocol parsing and scheduling unit, and standard event encapsulation unit, and includes a current template area, a candidate template area, and a rollback template area. The current template area stores currently active site templates, the candidate template area stores candidate site templates issued by the cloud-based operations and maintenance system but not yet active, and the rollback template area stores rollback templates that can be used for anomaly recovery.

[0057] When the cloud-based operations and maintenance system distributes candidate site templates, the template version management unit first performs signature verification, version verification, applicable device verification, and rollback package verification on the candidate site templates. After the verification passes, the template version management unit enables the candidate site template and the current site template to parse the same original frame or original message in parallel during the shadow parsing cycle, and compares the parsing success rate, unit reliability, object relationship matching rate, and diagnostic availability quality vector degradation rate of the candidate site template and the current site template.

[0058] During the shadow parsing process of candidate point templates, the template version management unit does not immediately replace the current point template with the candidate point template. Instead, it parses the same original frame or original message in parallel with the current point template within the shadow parsing cycle. The parsing result of the current point template continues to serve as the data source for standard event encapsulation, while the parsing result of the candidate point template is used to calculate the parsing success rate, unit confidence, object relationship matching rate, and the rate of decline in the diagnostic availability quality vector.

[0059] If the success rate of parsing, unit reliability, and object relationship matching rate of the candidate point template all reach the corresponding thresholds, and the decline in the diagnostic availability quality vector does not exceed the threshold, then the candidate point template will be switched to the current point template in the next sampling period. If the candidate point template fails signature verification, version verification, applicable device mismatch, or rollback package verification, the template version management unit will refuse to enable the candidate point template and generate a template failure event. If the candidate point template's corresponding collection failure rate exceeds the threshold, object relationship matching rate falls below the threshold, unit reliability falls below the threshold, or the decline in the diagnostic availability quality vector exceeds the threshold within the shadow parsing period, the template version management unit will restore the rollback template and write the failure reason into the template failure event. The template failure event can be uploaded to the cloud operation and maintenance system as a standard data quality event.

[0060] The configuration and diagnostic interface unit is used to perform local configuration, remote configuration, template download, driver status reading, acquisition status reading, and debug log output. This unit can connect to the protocol adapter unit, protocol parsing and scheduling unit, point template library unit, local caching and replay unit, and template version management unit. Field personnel or remote maintenance personnel can use the configuration and diagnostic interface unit to read adapter status, acquisition status, template version, cache backlog status, replay queue status, and debug logs.

[0061] The configuration and diagnostic interface unit is also used to read the protocol adapter status, acquisition scheduling status, point template version, candidate template status, rollback template status, replay queue backlog, cache usage, cloud connection status, security authentication status, and debugging logs. The configuration and diagnostic interface unit can receive local configuration commands or remote configuration commands to update device templates, point templates, sampling period, scheduling priority, protocol adapter start / stop status, security authentication parameters, and replay strategies.

[0062] The status indication and maintenance unit is equipped with an operation indicator, communication indicator, fault indicator, maintenance button, or maintenance port to display data acquisition failure, cache backlog, cloud connection status, template switching status, and security authentication status. The status indication and maintenance unit can connect to the protocol parsing and scheduling unit, local caching and replay unit, template version management unit, and security authentication and encryption unit to allow field personnel to determine the current operating status of the communication management module system. The operation indicator displays the module's operating status; the communication indicator displays the communication status of field devices or the cloud connection status; the fault indicator displays data acquisition failure, cache backlog, template switching failure, message signature failure, or security authentication anomaly; the maintenance button or maintenance port is used to enter local maintenance mode, read logs, or trigger configuration checks.

[0063] According to one embodiment of the present invention, the protocol adapter unit can be extended according to the protocol type of the field device; the point template library unit can be distributed by the cloud-based operation and maintenance system or imported through local configuration; the security authentication and encryption unit can adopt APIKey, digital certificate, TLS channel, national cryptographic algorithm, or customer-specified security method; the local caching medium can adopt SQLite database, file queue, embedded time series library, or message queue; the communication management module system can be set up independently as a field communication management device or as a communication board in the field edge control unit. When the communication management module system is used as a communication board in the field edge control unit, its output content is still standard events, point data, diagnostic availability quality vector, and replay status, and it does not directly generate policy slot control output.

[0064] The communication management module system outputs standard events, location data, diagnostic availability quality vectors, quality markers, object paths, idempotent keys, raw acquisition time, real-time markers, and replay status. The communication management module system does not directly generate work order actions, control strategies, or strategy slot control outputs, nor does it directly execute safety interlocks or manual bypass control. For standard events that reach the triggerable work order state, the communication management module system only writes the triggerable work order status field into the standard event; for standard events that do not reach the triggerable work order state, the communication management module system writes the non-triggerable status field. Subsequent work order generation, control strategy generation, strategy slots, safety interlocks, and manual bypass are handled separately by the cloud-based operation and maintenance system or the field edge control unit based on the standard events.

[0065] According to one embodiment of the present invention, the communication management module system connects to the chiller, cooling tower, water pump, valve, electricity meter, and temperature and humidity sensor within the energy station. The chiller uses the Modbus protocol, the cooling tower controller uses the BACnet protocol, and some energy consumption meters use the OPCUA or DL / T protocol. The multi-protocol interface unit connects to the above-mentioned devices through an RS485 interface, an Ethernet interface, and corresponding software driver interfaces. The protocol adapter unit enables the Modbus adapter, BACnet adapter, and OPCUA adapter respectively.

[0066] The protocol parsing and scheduling unit generates a data acquisition and scheduling sequence based on the equipment template, sampling period, and scheduling priority. The point template library unit sequentially performs protocol layer field parsing, physical quantity field conversion, and maintenance semantic field verification for chilled water supply and return temperatures, cooling water supply and return temperatures, chiller load, pump frequency, valve opening, and meter readings. The object-relationship mapping unit binds the above points to corresponding projects, sites, chiller plants, equipment, components, and point objects. The edge data quality unit calculates the diagnostic availability quality vector. When a chiller plant's diagnostic event family lacks necessary points such as chilled water return temperature or flow rate, the standard event encapsulation unit generates a defect bit event or data quality event, without marking the chiller plant event as diagnostically available.

[0067] According to one embodiment of the present invention, the communication management module system reads data on the air conditioning unit, VAV, FCU, space temperature, CO2 concentration, and valve position from the BAS system. The multi-protocol interface unit connects to the BAS system via an Ethernet interface, and the protocol adapter unit reads the raw messages using a BACnet adapter or an HTTP adapter. The point template library unit performs template processing on the space temperature, CO2 concentration, valve opening, supply air temperature, and fan status. The operation and maintenance semantic template area associates the above points with space comfort, terminal equipment, or BAS communication-related diagnostic event families.

[0068] The object-relationship mapping unit generates object paths based on projects, buildings, floors, spaces, devices, and locations. The edge data quality unit detects timestamp delays, flat lines, jumps, and communication interruptions, and generates a diagnostic availability quality vector. The standard event encapsulation unit generates telemetry events, data quality events, or communication anomaly events based on the diagnostic availability quality vector, and sends the standard events to the cloud-based operations and maintenance system, enabling the cloud-based operations and maintenance system to identify end-point comfort anomalies and service chain issues based on the standard events.

[0069] According to one embodiment of the present invention, after a batch of meters are replaced on-site, the cloud-based operation and maintenance system sends candidate point templates to the communication management module system. The template version management unit writes the candidate point templates into the candidate template area and performs signature verification, version verification, applicable device verification, and rollback packet verification on the candidate point templates. After the verification is passed, the template version management unit enables the candidate point templates and the current point templates to parse the same batch of original frames or original messages in parallel during the shadow parsing cycle.

[0070] During the shadow parsing cycle, the protocol parsing scheduling unit still uses the parsing results corresponding to the current point template as the primary source data. The parsing results of the candidate point templates are used to calculate the parsing success rate, unit confidence, object relationship matching rate, and the decline in the diagnostic availability quality vector. If the parsing success rate, unit confidence, and object relationship matching rate of the candidate point template all reach the corresponding thresholds, and the decline in the diagnostic availability quality vector does not exceed the threshold, the template version management unit will switch the candidate point template to the current point template in the next sampling cycle. If the collection failure rate exceeds the threshold or the decline in the diagnostic availability quality vector exceeds the threshold, the template version management unit will restore the rollback template and generate a template failure event.

[0071] It should be understood that the sequence number of each step in the invention and embodiments of the present invention does not absolutely imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

Claims

1. A communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment, characterized in that, include: The communication management module system is located between the field equipment network and the cloud operation and maintenance system. It includes a multi-protocol interface unit, a protocol adapter unit, a protocol parsing and scheduling unit, a point template library unit, an object relationship mapping unit, an edge data quality unit, a standard event encapsulation unit, a local caching and replay unit, and a security authentication and encryption unit. The multi-protocol interface unit is used to connect integrated energy equipment that uses different communication protocols; The protocol adapter unit reads the original frames or original messages of the field devices in response to the scheduling instructions of the protocol parsing and scheduling unit; The point template library unit is divided into a protocol layer template area, a physical quantity template area, and an operation and maintenance semantic template area, so that the original point will enter the object relationship mapping unit after passing through protocol layer field parsing, physical quantity field conversion, and operation and maintenance semantic field verification in sequence. The object-relational mapping unit binds points to project, site, system, device, component, loop, or space objects; The edge data quality unit writes a diagnostic availability quality vector and quality tag before standard events are generated; The standard event encapsulation unit encapsulates collected data, object relationships, and diagnostic availability quality vectors into standard events; The local caching and replay unit is used to cache standard events when they are unreachable in the cloud and retransmit them in order after the network is restored.

2. The communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment as described in claim 1, characterized in that, The multi-protocol interface unit is provided with at least one hardware interface selected from RS485 interface, RS232 interface, Ethernet interface, 4G / 5G communication interface, CAN interface, digital input / output interface, and analog input / output interface, or is provided with a software driver interface corresponding to the hardware interface. The multi-protocol interface unit is connected to the protocol adapter unit via an isolation circuit to form an isolated connection between the field-side communication line and the protocol adaptation processing line; The protocol adapter unit includes at least two of the following: Modbus adapter, BACnet adapter, OPC UA adapter, MQTT adapter, HTTP adapter, DL / T adapter, and proprietary protocol adapter.

3. The communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment as described in claim 1, characterized in that, The protocol layer template area is used to store at least one protocol layer field, including device type, protocol address, register, data type, byte order, and vendor identifier. The physical quantity template area is used to store at least one of the following physical quantity layer fields: unit, scale factor, offset, physical range, standard unit, and calibration status; The operation and maintenance semantic template area is used to store at least one of the operation and maintenance semantic layer fields, including device object, measurement point purpose, required point marker, diagnostic event family marker, and point grouping marker. The point template library unit performs template processing on the original points in the order of protocol layer template area, physical quantity template area and operation and maintenance semantic template area. When the template verification of any layer fails, a corresponding quality mark is generated and the quality mark is passed to the edge data quality unit and standard event encapsulation unit.

4. The communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment as described in claim 1, characterized in that, The protocol parsing and scheduling unit is used to generate a data acquisition scheduling sequence based on the device template, sampling period, scheduling priority, network status, and protocol adapter status. When multiple protocol channels exist for the same device, or when there are primary and backup sources at the same location, the protocol parsing and scheduling unit determines the primary source based on template version priority, sampling freshness, diagnostic availability quality vector, and communication success rate. Point data obtained from the primary source enters the point template library unit for template parsing, while point data obtained from non-primary sources is used as the verification source and written into the diagnostic availability quality vector or quality marker. When the communication success rate of the primary source is lower than a preset threshold or the sampling freshness is lower than a preset threshold, the protocol parsing and scheduling unit recalculates the source order and records the source switching information.

5. The communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment as described in claim 1, characterized in that, The object-relationship mapping unit is used to receive the point data processed by the point template library unit and generate an object path according to at least one of the following fields: tenant identifier, project identifier, site identifier, system identifier, subsystem identifier, equipment identifier, component identifier, loop identifier, space identifier, and point identifier. When the object relationship mapping unit detects missing device objects, inconsistent component relationships, missing spatial bindings, incorrect point grouping, or mismatched diagnostic event families, it writes the topology integrity field into the diagnostic availability quality vector and outputs an object relationship anomaly flag to the standard event encapsulation unit, so that the standard event carries the quality status corresponding to the object path.

6. The communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment as described in claim 1, characterized in that, The edge data quality unit is located between the object relation mapping unit and the standard event encapsulation unit. It is used to perform at least one of the following processing on the point data that has completed object relation mapping: timestamp delay detection, missing value detection, outlier detection, unit error detection, horizontal line detection, jump detection, duplicate data detection, and communication interruption detection, and form a diagnostic availability quality vector. The diagnostic availability quality vector includes fields for freshness, continuity, physical range, unit confidence, calibration status, topology integrity, and diagnostic requirement point coverage. The edge data quality unit generates four levels of status based on the diagnostic availability quality vector: archived only, displayable, diagnostic, or triggerable work orders. When at least one field in the diagnostic availability quality vector is below the corresponding threshold, the edge data quality unit retains the upload status of the corresponding point data and writes a low-quality flag, an undiagnostic status field, or an untriggerable status field into the event to be encapsulated.

7. The communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment as described in claim 1, characterized in that, The standard event encapsulation unit is used to encapsulate the collected data, object path, point identifier, numerical value, unit, diagnostic availability quality vector, quality marker, set of necessary diagnostic points, set of missing necessary points, diagnostic availability status, original acquisition time, idempotent key, and real-time marker into a standard event; The standard event type is set as telemetry event, alarm event, defective bit event, communication anomaly event, or data quality event; When the coverage of diagnostic essential points is lower than a preset threshold, the standard event encapsulation unit generates a defect bit event, a data quality event, or a template revision item.

8. The communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment as described in claim 1, characterized in that, The local caching and replay unit is equipped with a local caching medium and a replay queue. The local caching medium is at least one of an SQLite database, a file queue, an embedded time-series library, or a message queue. When the cloud-based operation and maintenance system is unreachable, message signing fails, the timestamp window does not meet the upload conditions, or the encrypted channel is unavailable, the local cache and replay unit writes the standard events to be uploaded into the replay queue and records the sequence number, original collection time, replay batch number, replay reason, and real-time mark for the standard events to be uploaded. After the network is restored, the local cache and replay unit retransmits the cached events in the order of the original acquisition time and sequence number, sets the real-time flag of the retransmitted events to a non-real-time state, and sets the real-time alarm trigger field of the retransmitted events to an untriggerable state.

9. The communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment as described in claim 1, characterized in that, It also includes a template version management unit, which is connected to the point template library unit, protocol parsing and scheduling unit, and standard event encapsulation unit, and has a current template area, a candidate template area, and a rollback template area; When the cloud-based operation and maintenance system issues candidate site templates, the template version management unit performs signature verification, version verification, applicable device verification, and rollback packet verification on the candidate site templates, and enables the candidate site templates and the current site templates to parse the same original frame or original message in parallel during the shadow parsing cycle. If the parsing success rate, unit confidence and object relationship matching rate of the candidate point template all reach the corresponding threshold, and the decrease in diagnostic usability quality vector does not exceed the threshold, then the candidate point template will be switched to the current point template in the next sampling period. If the candidate point template signature verification fails, the applicable equipment does not match, the acquisition failure rate exceeds the threshold, or the diagnostic availability quality vector decreases beyond the threshold, the template will be rolled back and a template failure event will be generated.

10. The communication management module system for multi-protocol parsing and edge data quality processing of integrated energy equipment as described in claim 1, characterized in that, It also includes a configuration and diagnostic interface unit and a status indication and maintenance unit. The configuration and diagnostic interface unit is connected to the protocol adapter unit, protocol parsing and scheduling unit, point template library unit, local caching and replay unit and template version management unit, and is used to perform local configuration, remote configuration, template download, driver status reading, acquisition status reading and debug log output. The status indication and maintenance unit is equipped with an operation indicator, a communication indicator, a fault indicator, a maintenance button or a maintenance port, used to display data acquisition failure, cache backlog, cloud connection status, template switching status and security authentication status; The security authentication and encryption unit manages access credentials and message signing keys using at least one of the following methods: API Key, digital certificate, TLS channel, national cryptographic algorithm, or secure storage area; The standard event encapsulation unit sends standard events to the cloud operation and maintenance system through at least one of the following methods: MQTT topic, Webhook interface, HTTP interface, or cloud message queue.

Images