An electric energy meter remote monitoring method, system, computer device and medium

Abstract

The present application relates to a kind of electric energy meter remote monitoring method, system, computer equipment and medium, comprising the following steps, receiving each electric energy meter communication message, clear text operation data are obtained by protocol unpacking and cipher decryption;It is time-sequenced alignment and numerical filtering to it, and time-sequenced electrical parameter is obtained;It is compared with operation reference value and detects mutation, and identifies electrical deviation characteristic value;The characteristic value is matched with fault characteristic library, and device alarm information is generated;Accordingly determine control strategy, encapsulate and issue control message, obtain electric energy meter action receipt;According to action receipt, update scattered electric energy meter state record, generate electric energy meter control record, solve how to improve the technical problem of consistency between the remote monitoring result of scattered electric energy meter and actual operation state of meter end.

Description

Technical Field

[0001] This invention relates to the field of remote monitoring technology, and in particular to a method, system, computer equipment, and medium for remote monitoring of electricity meters. Background Technology

[0002] With the application of electricity information collection systems in residential communities, industrial and commercial users, and distribution substations, electricity meters are typically connected to a main station management platform to provide managers with functions such as metering data query, equipment ledger management, operational status display, and anomaly alerts. Maintenance personnel can use the information displayed on the platform to conduct metering verification, troubleshooting, and remote maintenance, thereby reducing the frequency of on-site inspections.

[0003] However, in application scenarios with a large number of electricity meters distributed over a wide area, factors such as load switching, short-term electrical disturbances, terminal measurement fluctuations, and changes in communication link status can cause inconsistencies between the device status displayed on the platform and the actual on-site status of the electricity meters. This makes it difficult for maintenance personnel to accurately confirm whether abnormal states persist or whether the meter status has actually changed after handling, thus preventing the device status records from reflecting the true operating status of the electricity meters in a timely and reliable manner. Therefore, improving the consistency between the remote monitoring results of distributed electricity meters and the actual operating status of the meters has become a technical problem that needs to be solved. Summary of the Invention

[0004] The main objective of this invention is to provide a remote monitoring method for electricity meters, which solves the technical problem of how to improve the consistency between the remote monitoring results of distributed electricity meters and the actual operating status of the meters.

[0005] To achieve the above objectives, the present invention provides a method for remote monitoring of electricity meters, comprising the following steps:

[0006] Receive communication messages from each distributed energy meter, perform protocol unpacking and ciphertext decryption on the communication messages to obtain plaintext operation data;

[0007] The plaintext running data is time-aligned and numerically filtered to obtain the timing electrical parameters;

[0008] The timing electrical parameters are compared with the pre-stored operating reference values ​​to detect deviations and sudden changes, in order to determine whether there are electrical deviation characteristic values.

[0009] If it exists, feature matching is performed based on the electrical deviation feature value and the pre-stored fault feature library to obtain equipment alarm information;

[0010] Based on the device alarm information, a control strategy is determined, and based on the control strategy, control messages are encapsulated and sent to the distributed energy meters to obtain energy meter action receipts.

[0011] The status records of the distributed energy meters are updated based on the energy meter action receipts to obtain the energy meter control records.

[0012] Furthermore, the communication messages are unpacked and decrypted to obtain plaintext execution data, including:

[0013] The communication message is scanned by bytes to obtain the frame header identifier and link check code. Based on the frame header identifier and link check code, the communication message is format checked and the packet header is stripped to obtain the message payload data.

[0014] Based on a preset protocol dictionary, the identifier field of the message payload data is parsed to obtain the service ciphertext segment;

[0015] The message payload data is sliced ​​in the address field to obtain the meter address code. Based on the meter address code, a matching search is performed in the pre-stored key library to obtain the node decryption key.

[0016] Based on the node decryption key, the ciphertext segment of the service is decrypted and shifted to obtain a plaintext data stream.

[0017] The plaintext data stream is byte-ordered and converted to a base to obtain a decimal value. Based on a preset dimensional coefficient, the decimal value is shifted by the decimal point and the units are concatenated to obtain plaintext running data.

[0018] Furthermore, the step of performing time-series alignment and numerical filtering on the plaintext runtime data to obtain timing electrical parameters includes:

[0019] The plaintext operation data is parsed to obtain the reporting timestamp and electrical measurement value. The reporting timestamp is then mapped onto a time axis based on a preset reference clock cycle to obtain the time offset.

[0020] Based on the time offset, the electrical measurement values ​​are interpolated and resampled to obtain a synchronous electrical sequence;

[0021] The synchronous electrical sequence is divided into local data segments by sliding window, and the boundary extrema are removed from the local data segments to obtain extrema-free segments.

[0022] The extremum removal segment is smoothed using a neighborhood weighted average rule to obtain the timing electrical parameters.

[0023] Furthermore, the step of determining a control strategy based on the device alarm information, encapsulating and sending control messages to the distributed energy meters based on the control strategy, and obtaining energy meter action feedback includes:

[0024] The device alarm information is parsed and classified by field to obtain alarm attribute tags. Based on the alarm attribute tags, address matching is performed in a preset strategy matrix to obtain basic control instructions. The execution timing of the basic control instructions is arranged to obtain a control strategy.

[0025] The control strategy is translated into instruction set based on a preset protocol mapping table to obtain operation bytecode; the distributed energy meters are addressed by network node to obtain the target communication address;

[0026] Based on the target communication address, the operation bytecode is frame-formatted and securely signed to obtain an encapsulated control message;

[0027] The encapsulated control message is subjected to channel modulation and time slot allocation to obtain the physical transmission signal;

[0028] The distributed energy meters are driven by the physical layer through the physical transmission signal to obtain a response data frame. The response data frame is then demodulated, decoded, and the status bit is extracted to obtain an energy meter action receipt.

[0029] Furthermore, the step of performing frame format concatenation and security signing on the operation bytecode based on the target communication address to obtain the encapsulated control message includes:

[0030] The operation bytecode is padded with boundary markers and its length is calculated to obtain a delimited data segment. The delimited data segment is then concatenated with data fields based on the target communication address to obtain a verification source sequence.

[0031] A secure authentication signature is obtained by extracting a digest and calculating a signature from the verification source sequence using a pre-set signature private key.

[0032] The secure authentication signature is used to append to the delimited data segment to obtain an encapsulated control message.

[0033] Furthermore, the step of updating the status record of the distributed energy meters based on the energy meter action receipt to obtain the energy meter control record includes:

[0034] The message payload of the energy meter action receipt is decomposed and cyclic redundancy check is performed to obtain the receipt timestamp and physical execution status.

[0035] Based on the receipt timestamp and the pre-stored transaction queue, a time sequence matching is performed to obtain the suspended transaction identifier. Based on the suspended transaction identifier, the physical execution state and the preset expectation matrix are XORed to obtain the state offset vector.

[0036] Based on the state offset vector, the key-value pointers of the pre-stored twin dictionary are overwritten to obtain a physically aligned snapshot;

[0037] Based on the physical alignment snapshot, the mutex lock of the suspended transaction identifier is released to obtain the transaction closed loop imprint.

[0038] Based on the transaction closed-loop imprint, the physical alignment snapshot is spliced ​​into a byte stream and hash digest is calculated to obtain the electricity meter control record.

[0039] Furthermore, the step of releasing the mutex lock on the suspended transaction identifier based on the physical alignment snapshot to obtain the transaction closure imprint includes:

[0040] The bit field mask of the suspended transaction identifier is extracted to obtain the latch node address, and the current state pointer is obtained by address traversal in the preset concurrency control tree based on the latch node address.

[0041] The physical alignment snapshot is parsed to obtain the snapshot storage base address, and the current state pointer is subtracted from the snapshot storage base address by the address span to obtain the pointer offset scalar;

[0042] Based on the pointer offset scalar, the occupancy flag bit corresponding to the latch node address is cleared bit by bit to obtain the lock release status word;

[0043] The lock release status word and the physical alignment snapshot are concatenated into a byte stream and a hash digest is calculated to obtain the transaction closed-loop imprint.

[0044] The present invention also provides a remote monitoring system for electricity meters, comprising:

[0045] The receiving module is used to receive communication messages sent by each distributed energy meter, and to decrypt the communication messages to obtain plaintext operation data.

[0046] The filtering module is used to perform timing alignment and numerical filtering on the plaintext running data to obtain timing electrical parameters;

[0047] The detection module is used to compare the timing electrical parameters with the pre-stored operating reference values ​​and detect deviations and sudden changes to determine whether there are electrical deviation characteristic values.

[0048] The matching module is used to perform feature matching based on the electrical deviation feature value and the pre-stored fault feature library if the fault exists, so as to obtain the equipment alarm information.

[0049] The distribution module is used to determine the control strategy based on the device alarm information, encapsulate and distribute control messages to the distributed energy meters based on the control strategy, and obtain the energy meter action receipt.

[0050] The update module is used to update the status record of the distributed energy meters based on the energy meter action receipt, so as to obtain the energy meter control record.

[0051] The present invention also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of any of the methods described above.

[0052] The present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of any of the methods described above.

[0053] This invention provides a remote monitoring method for electricity meters, comprising the following steps: receiving communication messages sent by various distributed electricity meters; performing protocol unpacking and ciphertext decryption on the communication messages to obtain plaintext operating data; performing time-series alignment and numerical filtering on the plaintext operating data to obtain time-series electrical parameters; comparing the time-series electrical parameters with pre-stored operating reference values ​​for deviation and abrupt change detection to determine whether electrical deviation feature values ​​exist; if so, performing feature matching based on the electrical deviation feature values ​​and a pre-stored fault feature database to obtain equipment alarm information; determining a control strategy based on the equipment alarm information; and based on the control strategy... The control message of the distributed energy meter is encapsulated and sent to obtain the energy meter action receipt. Based on the energy meter action receipt, the status record of the distributed energy meter is updated to obtain the energy meter control record. This solves the technical problem of how to improve the consistency between the remote monitoring results of the distributed energy meter and the actual operating status of the meter. It realizes a closed loop of reliable perception, anomaly identification, directional control and receipt verification of the operating status of the distributed energy meter, so that the status record of the master station can be dynamically aligned with the actual execution status of the meter, and improves the monitoring accuracy, control reliability and status traceability of the remote operation and maintenance process. Attached Figure Description

[0054] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0055] Figure 1 This is a schematic diagram of the steps of a remote monitoring method for electricity meters in one embodiment of the present invention;

[0056] Figure 2 This is a structural block diagram of a remote monitoring system for electricity meters according to one embodiment of the present invention;

[0057] Figure 3 This is a schematic block diagram of the structure of a computer device according to an embodiment of the present invention;

[0058] The objectives, features, and advantages of this invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0059] The embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention. The step numbers in the following embodiments are set only for ease of explanation, and there is no limitation on the order between the steps. The execution order of each step in the embodiments can be adaptively adjusted according to the understanding of those skilled in the art.

[0060] The following describes in detail, with reference to the accompanying drawings, a method for remote monitoring of an electricity meter according to an embodiment of the present invention. First, the method for remote monitoring of an electricity meter according to an embodiment of the present invention will be described with reference to the accompanying drawings.

[0061] like Figure 1 As shown, Figure 1 This invention provides a method for remote monitoring of an electricity meter, comprising the following steps:

[0062] S1 receives communication messages from each distributed energy meter, performs protocol unpacking and ciphertext decryption on the communication messages, and obtains plaintext operation data.

[0063] S11, perform byte-bit scanning on the communication message to obtain the frame header identifier and link check code, and perform format verification and packet header stripping on the communication message based on the frame header identifier and link check code to obtain the message payload data;

[0064] S12, based on the preset protocol dictionary, the identifier field of the message payload data is parsed to obtain the service ciphertext segment;

[0065] S13, Slice the address field of the message payload data to obtain the meter address code, and perform matching and retrieval in the pre-stored key library based on the meter address code to obtain the node decryption key;

[0066] S14, based on the node decryption key, perform cryptographic block decryption and shift restoration on the ciphertext segment of the service to obtain a plaintext data stream;

[0067] S15, the plaintext data stream is byte-order reversed and number system converted to obtain a decimal value, and the decimal value is shifted and units are concatenated based on a preset dimensional coefficient to obtain plaintext running data.

[0068] Specifically, after receiving communication messages from various distributed energy meters or data acquisition terminals, the main station access service first writes the communication messages into the receive buffer and scans the frame start flag as specified in the protocol according to byte order to locate the frame header identifier. Based on the frame format corresponding to the frame header identifier, it reads the length information and the trailing link checksum, performs integrity verification according to the same checksum coverage, and checks whether the frame length, control field, and end flag conform to the protocol definition. Only when all verifications pass is the frame header, length field, control field, and link checksum stripped to form the message payload data. For half-frames, spliced ​​frames, or messages with inconsistent checksums appearing in the buffer, the original receive record is retained and subsequent parsing is stopped to prevent invalid bytes from entering the running data processing stage.

[0069] After obtaining the message payload data, the identifier field is read according to the pre-maintained protocol dictionary. The protocol dictionary stores the identifier code, field position, field length, service category, and data segment boundary, thereby confirming the service to which the message belongs and extracting the service ciphertext segment. For identifier codes that are not present in the dictionary, have incorrect field lengths, or whose field arrangement does not meet the protocol requirements, the message is marked as not recognized by the protocol and will not proceed to the subsequent decryption process, thus avoiding the misinterpretation of control information, address information, or non-service data as operational data to be restored.

[0070] Subsequently, according to the address field start position and occupied length defined in the protocol, the message payload data is sliced ​​into address fields to obtain meter address codes. These meter address codes are then used as key indexes to retrieve node decryption keys from a pre-stored key repository. The key repository associates and stores meter address codes with node decryption keys, key versions, and validity status. When a key rotation record exists for the same meter address code, the valid node decryption key is selected based on the version information in the identifier field. If a valid key cannot be found, only the reason for decryption failure is recorded; other meter keys are not used as substitutes to avoid incorrect data recovery due to key mismatch.

[0071] After obtaining the node decryption key, the encrypted data segment is decrypted block by block according to the predefined cryptographic block boundaries and processing order. Then, the data is restored in reverse order according to the shift direction and shift bits specified in the protocol, returning the encoded data bytes to their original arrangement to obtain the plaintext data stream. After decryption, the data length, field types, and built-in consistency information of the plaintext data stream are verified. If the verification result does not meet the protocol requirements, no running parameters are generated, and the original message and the reason for the anomaly are retained to avoid distorted data caused by key version mismatch, corrupted transmitted content, or message tampering.

[0072] Finally, for multi-byte numerical fields in the plaintext data stream, the byte order is reversed according to the protocol, and the binary, hexadecimal, or compressed decimal encoding is converted into decimal values. Then, the corresponding dimensional coefficients are called according to the parameter identifier to complete the decimal point shift and physical unit concatenation. For example, when the original voltage value is 2305 and each counting unit corresponds to 0.1 volts, the conversion result is 230.5 volts. The system stores the restored parameter name, decimal value, physical unit, meter address code, and message reception time together to form plaintext operational data. In this embodiment, the above scheme can complete integrity verification, targeted decryption, and normalized value restoration before the message enters subsequent monitoring and processing, improving the reliability of the operational data source.

[0073] S2, perform timing alignment and numerical filtering on the plaintext running data to obtain timing electrical parameters.

[0074] S21, perform field parsing on the plaintext operation data to obtain the reporting timestamp and electrical measurement value, and perform time axis mapping on the reporting timestamp based on a preset reference clock cycle to obtain the time offset;

[0075] S22, interpolate and resample the electrical measurement values ​​based on the time offset to obtain a synchronous electrical sequence;

[0076] S23, the synchronous electrical sequence is divided into sliding window blocks to obtain local data segments, and the boundary extrema are removed from the local data segments to obtain extrema-free segments;

[0077] S24, the extremum removal segment is smoothed based on the neighborhood weighted average rule to obtain the timing electrical parameters.

[0078] Specifically, the plaintext operational data is parsed according to preset field definitions, extracting the reporting timestamp and corresponding electrical measurement values. These electrical measurement values ​​can include numerical values ​​with clearly defined parameter identifiers, such as voltage, current, power, and electrical energy. The system maps the reporting timestamp to a unified time axis formed by a preset reference clock cycle and determines the nearest reference time corresponding to that timestamp, using the time difference between the two as the time offset. A timestamp earlier than the corresponding reference time is recorded as an early offset, and a timestamp later than the corresponding reference time is recorded as a delayed offset. For data with missing timestamps, exceeding the allowable time synchronization range, or conflicting with the time sequence of adjacent data from the same meter, the original record is retained and marked as having abnormal time quality, and it is not included in this round of synchronization processing.

[0079] After obtaining the time offset, for electrical measurement values ​​of the same meter and the same parameter identifier, interpolation resampling is performed according to each reference time on a unified time axis. Specifically, for each reference time to be supplemented, adjacent electrical measurement values ​​with valid times are found on both sides, and the resampling result is determined based on the time proximity of the measurements on both sides to the reference time. When the original reported timestamp falls exactly on the reference time, its corresponding electrical measurement value is directly retained. If the time interval between adjacent valid measurement values ​​exceeds the preset allowable interval, or if any of the measurement values ​​has a time quality abnormality mark, interpolation is not performed, but the missing mark is retained at the corresponding reference time to avoid constructing a distorted operating state using historical data with excessively large intervals. After this processing, a synchronous electrical sequence with a unified time coordinate for each parameter is obtained.

[0080] Subsequently, the synchronous electrical sequence is continuously divided into blocks according to a preset window length and sliding step size, so that each local data segment contains the same type of electrical parameters within adjacent reference times. For each local data segment, extreme points near the upper and lower boundaries of the values ​​are identified, and the extreme points are continuously compared with the effective measured values ​​of their adjacent reference times. When an extreme point appears only at a single reference time and the change in the value with its neighboring measured value exceeds a preset single-point disturbance threshold, it is discarded as a boundary extreme. If the change in electrical parameters persists across multiple adjacent reference times, the trend of change is retained, and the parameter is not deleted simply because its value is high or low. This avoids misinterpreting real load switching or electrical anomalies as transient noise, resulting in a segment without extreme values.

[0081] For each valid measurement value in the extremum removal segment, valid measurements within its temporal neighborhood are selected for smoothing calculations. Neighborhood weights are determined based on temporal distance and data quality, with measurements closer in time and lacking quality anomaly markers receiving higher weights. Measurements at the beginning and end of the segment use only existing neighborhood data, and their weights are normalized. After neighborhood-weighted averaging, isolated fluctuations are smoothed out, while parameter changes reflected by multiple consecutive reference times maintain their direction of change, ultimately forming time-series electrical parameters with unified time coordinates and data quality markers. In this embodiment, the above scheme reduces the impact of communication time differences and single-point disturbances on the continuity of electrical parameters, providing a time-consistent and numerically stable data foundation for subsequent operational status analysis.

[0082] S3, compare the timing electrical parameters with the pre-stored operating reference values ​​for deviation and abrupt change detection to determine whether there are electrical deviation characteristic values.

[0083] Specifically, based on the meter address, parameter identifier, and reference time period, the reference item corresponding to the time-series electrical parameter is retrieved from the pre-stored operating reference values. Then, under the same units, the deviation direction and magnitude of the current value relative to the reference item are determined moment by moment. Simultaneously, parameter changes at adjacent reference times are read to identify sudden changes occurring continuously within a short period. When a reference item is missing, the current data is marked as pending verification without deviation judgment. When the deviation magnitude exceeds the allowable deviation range of the parameter, or the sudden change magnitude exceeds a preset sudden change threshold and is confirmed at continuous sampling nodes, the parameter identifier, occurrence time, deviation direction, and deviation magnitude are recorded to form an electrical deviation characteristic value; the remaining data is retained as a normal operation record. In this embodiment, the above scheme can reliably distinguish between persistent anomalies and occasional fluctuations, improving the accuracy of electrical operation deviation identification.

[0084] S4. If it exists, then feature matching is performed based on the electrical deviation feature value and the pre-stored fault feature library to obtain equipment alarm information.

[0085] Specifically, the meter address, parameter identifier, occurrence time, deviation direction, and deviation amplitude are read from the electrical deviation characteristic value. Using the parameter identifier as a filtering condition, corresponding candidate fault entries are retrieved from a pre-stored fault characteristic database. Each fault entry is associated with and stored as a fault category, characteristic direction, amplitude range, time characteristic, and alarm level. The current electrical deviation characteristic value is compared item by item with the candidate fault entries. If the direction matches, the deviation amplitude falls within the corresponding range, and the time characteristic meets the requirements, a match is confirmed. If multiple entries match simultaneously, the entry with the most matching conditions is selected first. Subsequently, the meter address, fault category, alarm level, occurrence time, and deviation criteria are encapsulated into equipment alarm information; features that do not meet the matching conditions are only stored in a pending review record. In this embodiment, the above scheme can improve the correspondence between alarm information and actual anomaly types.

[0086] S5. Based on the device alarm information, determine the control strategy, encapsulate and send control messages to the distributed energy meters based on the control strategy, and obtain the energy meter action receipt.

[0087] S51, perform field parsing and attribute classification on the device alarm information to obtain alarm attribute tags, and perform address matching in a preset strategy matrix based on the alarm attribute tags to obtain basic control instructions, and arrange the execution timing of the basic control instructions to obtain a control strategy.

[0088] S52, based on the preset protocol mapping table, the control strategy is translated into instruction set to obtain operation bytecode; network node addressing is performed on the distributed energy meters to obtain the target communication address.

[0089] Specifically, in this embodiment, the meter address, fault type, alarm level, occurrence time, and deviation basis from the device alarm information are read, and attribute classification is performed according to fault type, alarm level, and affected objects to generate alarm attribute tags. The rows of the preset strategy matrix correspond to fault types, the columns correspond to alarm levels and affected objects, and the cross-units are associated with basic control instructions. These basic control instructions include operation type, applicable objects, execution priority, and preconditions. The system uses alarm attribute tags as an index to complete address matching; if no valid unit is matched, only a status pending manual review is generated, and no control instructions are output.

[0090] After obtaining basic control commands, for multiple basic control commands of the same meter, the execution priority and preconditions should be arranged in sequence, with status verification commands arranged first, followed by disposal commands. Disposal commands with dependencies are executed only after the preconditions for verification are met, and commands with mutual exclusion should not be issued concurrently. For operations involving changes in power supply status, authorization confirmation and current status consistency verification should also be retained. The sequence number, triggering condition, and waiting requirements of each command are associated and output to form a control strategy.

[0091] Subsequently, based on the correspondence between meter protocol version, operation type, and field code in the preset protocol mapping table, the control strategy is translated line by line, converting abstract operation names, parameter values, and execution identifiers into operation bytecode, while preserving the original command order. Then, the concentrator identifier, network node identifier, and routing information in the device file are queried using the meter address to obtain the target communication address. Before sending the command, the meter address associated with the target communication address is checked to ensure consistency with the device alarm information. If the address is missing, offline, or inconsistent, the generation of the corresponding downlink task is stopped and the anomaly is recorded. In this embodiment, the above scheme enables accurate correspondence between alarm handling and the target meter and its communication protocol, improving the orderliness and reliability of remote control.

[0092] S53, based on the target communication address, the operation bytecode is spliced ​​in frame format and securely signed to obtain an encapsulated control message.

[0093] S531, perform boundary marker padding and length calculation on the operation bytecode to obtain a delimited data segment, and concatenate the data fields of the delimited data segment based on the target communication address to obtain a verification source sequence;

[0094] S532, the digest of the verification source sequence is extracted and the signature is calculated using a preset signature private key to obtain a secure authentication signature;

[0095] S533, the secure authentication signature is used to append to the end of the delimited data segment to obtain an encapsulated control message.

[0096] Specifically, the operation bytecode is encapsulated line by line according to the preset specifications. First, the header and footer of the operation bytecode are filled with data segment boundary markers as specified in the specification, and the number of valid operation bytes between the boundary markers is counted. The count is written into the corresponding length field to obtain the delimited data segment. The length field only reflects the actual number of valid operation bytes and does not count boundary markers repeatedly. When the counted length is inconsistent with the field length allowed by the specification, or when there are missing operation bytecodes, the encapsulation of the current instruction is stopped. Subsequently, the target communication address is written into the address field according to the byte order specified in the specification, and concatenated with the delimited data segment in the predetermined field order. This ensures that the target communication address, length field, operation bytecode, and boundary markers together constitute the verification source sequence, guaranteeing that the subsequent authentication content corresponds to the actual object to be sent.

[0097] After obtaining the verification source sequence, the secure signature interface corresponding to the preset signature private key is called to extract the digest of each byte in the verification source sequence according to its concatenation order. Then, a signature calculation is performed based on the digest result to obtain the secure authentication signature. The preset signature private key is stored in a controlled key storage area and is only allowed to be called by the signature interface. It is not written into control messages or output to the communication link in plaintext form. Since the target communication address and delimited data segment are both included in the verification source sequence, any change in any address field, length field, or operation byte will cause the secure authentication signature to no longer correspond to the original verification source sequence. When the signature interface call fails, the digest extraction is incomplete, or the secure authentication signature length does not meet the specification requirements, message generation is terminated and an encapsulation error is recorded.

[0098] Finally, the target communication address field is retained at the beginning of the message, and the security authentication signature is appended to the end of the delimited data segment, forming an encapsulated control message containing the target communication address, delimited data segment, and security authentication signature. After encapsulation, the target communication address, operation bytecode, and execution object and execution order in the control policy are checked again to ensure consistency. Only after successful verification is the message entered into the distribution queue. If address mismatch, bytecode modification, or signature loss is found, the corresponding pending task is deleted and an exception record is retained. In this embodiment, the above scheme can ensure consistency between control content, target node, and authentication signature, improving the integrity and reliability of remote control messages.

[0099] S54, perform channel modulation and time slot allocation on the encapsulated control message to obtain the physical transmission signal;

[0100] S55, the distributed energy meter is driven by the physical layer through the physical transmission signal to obtain a response data frame, and the response data frame is demodulated, decoded and status bit extracted to obtain the energy meter action receipt.

[0101] Specifically, based on the communication profile corresponding to the target communication address, the available channels and their physical layer parameters are determined, including the communication medium type, modulation scheme, channel coding scheme, and time slot resource status. For encapsulated control messages, bit stream conversion is first performed according to the coding rules of the selected channel, then the encoded bit stream is mapped to the corresponding modulation symbols, and synchronization identification information is added to the beginning of the message to form a physical transmission signal that can be recognized by the target energy meter. During time slot allocation, the control terminal searches for available transmission time slots and reserved response time slots corresponding to the target communication address within the current communication cycle, avoiding time slots already occupied by other network nodes; only when both the transmission and response time slots meet the allocation conditions is the physical transmission signal written to the corresponding time slot, preventing signal collisions caused by multiple distributed energy meters simultaneously occupying the same channel.

[0102] After entering the allocated transmission time slot, the communication interface loads the physical transmission signal onto the corresponding communication medium, driving the distributed energy meters corresponding to the target communication address to receive the control content. Simultaneously, the control end listens for response data frames in the reserved response time slot, demodulates them using modulation parameters matching the transmission signal, recovers the response bit stream, and then decodes it according to the corresponding channel coding rules. The recovered response data frames must be checked sequentially against the target communication address, command identifier, and message integrity to confirm that they were indeed returned by the energy meter corresponding to this control task; response data frames with inconsistent addresses, inconsistent command identifiers, or failed integrity checks are not used as the result of this control.

[0103] For verified response data frames, the status bits are extracted according to the protocol definition, and combined with the command reception status, execution status, or rejection status represented by the status bits, a power meter action receipt is generated. If no valid response data frame is received within the reserved response time slot, or demodulation and decoding fail, the corresponding control task is marked as unconfirmed, and is not considered successfully executed. In this embodiment, the above scheme can complete the orderly transmission of control messages and confirmation of execution status in a shared communication channel, improving the verifiability of remote control results for distributed power meters.

[0104] S6, based on the energy meter action receipt, update the status record of the distributed energy meter to obtain the energy meter control record.

[0105] S61, perform message payload decomposition and cyclic redundancy check on the energy meter action receipt to obtain the receipt timestamp and physical execution status;

[0106] S62, perform time-series matching between the receipt timestamp and the pre-stored transaction queue to obtain the suspended transaction identifier, and perform an XOR logical operation between the physical execution state and the preset expectation matrix based on the suspended transaction identifier to obtain the state offset vector.

[0107] S63, based on the state offset vector, the key-value pointer of the pre-stored twin dictionary is overwritten to obtain a physical alignment snapshot.

[0108] Specifically, upon receiving an action receipt from the electricity meter, the message payload is disassembled according to the receipt protocol, separating the message header, service payload, and cyclic redundancy check (CRC) field. The CRC result is then recalculated within the protection field range specified in the protocol. Service payload parsing continues only if the recalculated result matches the CRC field carried in the receipt; receipts that fail the check only record a communication anomaly and do not participate in status updates. For service payloads that pass the check, the receipt timestamp and status bits reflecting the actual meter execution result are extracted, and the payload is restored to its physical execution state according to the status bit definition.

[0109] Subsequently, based on the receipt timestamp, control transactions in a suspended state with a time range matching the receipt are retrieved from the pre-stored transaction queue to obtain the suspended transaction identifier. The transaction queue stores the transaction identifier, target communication address, instruction identifier, issuance time, effective waiting interval, and preset expectation matrix index. When multiple candidate transactions with overlapping time ranges exist, they are further distinguished by combining the target communication address and instruction identifier; if a unique match cannot be found, the state is not overwritten. After determining the suspended transaction identifier, its corresponding preset expectation matrix is ​​retrieved, and the physical execution state is XORed bit-by-bit with the state bits in the preset expectation matrix according to the same field order. When the state bits match, the corresponding position is recorded as no offset; when the state bits do not match, the corresponding position is recorded as having an offset, and the judgment results of each position constitute a state offset vector.

[0110] Finally, based on the offset positions in the state offset vector, the key-value pointers corresponding to the meter address and state fields in the pre-stored twin dictionary are located, and the corresponding key-value pointers are overwritten with the verified physical execution state from the receipt; state fields without offsets retain their original values. During the overwriting process, a new state version is generated and associated with and saved the suspended transaction identifier, receipt timestamp, and data quality flag; the original historical snapshot is not directly deleted. If the key-value pointer does not exist or the state field cannot be matched, the snapshot submission is terminated and a dictionary anomaly is recorded. In this embodiment, the above scheme can correct the virtual state based on the verified action receipt, improving the consistency between the energy meter state record and the actual execution state.

[0111] S64, based on the physical alignment snapshot, release the mutex lock on the suspended transaction identifier to obtain the transaction closed loop imprint.

[0112] S641, the bit field mask of the suspended transaction identifier is extracted to obtain the latch node address, and the addressing traversal is performed in the preset concurrency control tree based on the latch node address to obtain the current status pointer;

[0113] S642, perform memory segment parsing on the physical alignment snapshot to obtain the snapshot storage base address, and subtract the address span from the current state pointer and the snapshot storage base address to obtain the pointer offset scalar;

[0114] S643, based on the pointer offset scalar, the occupancy flag bit corresponding to the latch node address is cleared bit by bit to obtain the lock release status word.

[0115] Specifically, in this embodiment, the latch node code is extracted from the suspended transaction identifier according to the preset bit field start position and bit field length, and non-latched information is removed based on the bit field mask to obtain the latch node address. A preset concurrency control tree uses the latch node address as the node index, and each node is associated with and stores the occupancy status, transaction ownership information, and current status pointer. Starting from the root node of the concurrency control tree, the system traverses the corresponding branches level by level according to the latch node address until the target latch node is located, and reads the current status pointer currently stored in that node. If the latch node address does not exist, the node has been re-occupied by other incomplete transactions, or the current status pointer is null, subsequent release processing is stopped to avoid erroneous operations on other nodes in the concurrency control tree.

[0116] Subsequently, the storage structure of the physically aligned snapshot is parsed using memory segments. The snapshot storage base address recorded in the snapshot header is read, and it is confirmed that the current state pointer and the snapshot storage base address are located in the same controlled memory region. Using the snapshot storage base address as a reference, the address span of the current state pointer is subtracted to obtain a pointer offset scalar. This pointer offset scalar represents the storage distance of the current latch node state record relative to the starting position of this physically aligned snapshot. Only when the pointer offset scalar is within the allocated memory segment of the snapshot and meets the address alignment requirements of the state record is it used as the basis for lock release verification. If the pointer is outside the snapshot storage range, the address span is abnormal, or the snapshot version is inconsistent with the pending transaction identifier, the occupancy flag is not cleared.

[0117] After completing the state association verification using the pointer offset scalar, the occupancy flag corresponding to the latch node address is located, and the transaction ownership information recorded in this flag is checked to see if it is still consistent with the pending transaction identifier. If they are consistent, only the occupancy flag is atomically cleared bit by bit, while other state bits in the same state word remain unchanged, resulting in the lock release state word. If they are inconsistent, the original occupancy state is maintained and a release conflict record is written. After the lock release state word is generated, the corresponding pending transaction is updated to the completed state, enabling subsequent control tasks to re-request the latch node. In this embodiment, the above scheme can accurately release the corresponding concurrent lock after the state snapshot is aligned, reducing the risk of transaction mismatch and duplicate occupancy.

[0118] S644, the lock release status word and the physical alignment snapshot are concatenated into a byte stream and a hash digest is calculated to obtain the transaction closed loop imprint.

[0119] S6441, the lock release status word is byte-order normalized and length marker is appended to obtain a standard status sequence.

[0120] Specifically, the valid bytes representing the lock occupancy status, release result, and transaction association status in the lock release status word are read, and their canonical byte order is determined according to a preset specification. For multi-byte status fields, when the current stored byte order is inconsistent with the canonical byte order, the byte arrangement is flipped according to the field boundaries; single-byte status fields retain their original order, resulting in a normalized status byte stream. The number of valid bytes in the normalized status byte stream is then counted, and a length marker representing this number is appended to the beginning of the status byte stream to form a standard status sequence. The length marker only covers the normalized status bytes and does not include the length marker itself; when the actual number of bytes is inconsistent with the status field definition, the generation of the standard status sequence is stopped and an exception is recorded. In this embodiment, the above scheme can eliminate byte order differences between different nodes, ensuring that the lock release status can be consistently parsed.

[0121] S6442, the standard state sequence and the physical alignment snapshot are continuously arranged and merged with the byte stream to obtain a mixed state data block.

[0122] S64421, The standard state sequence and the physical alignment snapshot are summed by byte length to obtain a merge length value. Based on the merge length value, a continuous storage interval is divided in physical memory to obtain a merged memory block.

[0123] S64422, extract the first address of the standard state sequence to obtain the state base address pointer, and extract the first address of the physical alignment snapshot to obtain the snapshot base address pointer;

[0124] S64423, Based on the state base address pointer and the snapshot base address pointer, the standard state sequence and the physical aligned snapshot are written sequentially into the merged memory block in front-to-back order to obtain a sequentially concatenated byte stream;

[0125] S64424, perform integrity verification and end null byte padding on the sequentially concatenated byte stream to obtain a mixed state data block.

[0126] Specifically, the effective byte length of the standard state sequence and the effective byte length of the physically aligned snapshot are read first. The effective byte length of the standard state sequence includes its length marker and the normalized lock release status word, while the effective byte length of the physically aligned snapshot is based on the snapshot's own effective data boundary. The two are then summed to obtain the merged length value, which is then checked for non-zeroness, maximum length, and overflow. If the checks pass, a contiguous storage region with a capacity not less than the merged length value is allocated in physical memory. When the underlying storage management uses a fixed alignment granularity, the actual allocated region capacity can be greater than the merged length value; any excess capacity is reserved for subsequent empty byte padding, resulting in a merged memory block. If any input sequence length is invalid, or a contiguous storage region cannot be obtained, the current merge process is stopped, and no subsequent data blocks are generated.

[0127] Subsequently, the starting addresses of the standard state sequence and the physical alignment snapshot are extracted to obtain the state base address pointer and the snapshot base address pointer, respectively. The state base address pointer points to the physical memory location where the first valid byte of the standard state sequence is located, and the snapshot base address pointer points to the physical memory location where the first valid byte of the physical alignment snapshot is located. After extraction, the two source memory regions are verified to be completely present within the allocated range based on the corresponding valid byte lengths, and the source sequence is set to an unmodifiable read state during this copying period. If either base address pointer is null, the pointed-to region length is insufficient, or the source data version changes, the allocated merged memory block is revoked and the address resolution error is recorded to prevent reading invalid memory or mixing in data of different versions.

[0128] After the source address verification is successful, the starting address of the merged memory block is set as the write start point. All valid bytes of the standard state sequence are read according to the state base address pointer and continuously written to the beginning of the merged memory block. After the standard state sequence is written, the write position is extended to its end. Then, all valid bytes of the physically aligned snapshot are read according to the snapshot base address pointer and continuously written to the standard state sequence. No other business fields are inserted between the two, resulting in a sequentially concatenated byte stream. During the copying process, the read and write boundaries are limited according to the length of their respective valid bytes. The write stops when the merge length value is reached. If the actual number of bytes written is inconsistent with the merge length value, or if the target interval abnormally overlaps with any source interval, the write result is canceled.

[0129] Finally, an integrity check is performed on the sequentially concatenated byte stream. This checks if the length marker in the standard state sequence matches the actual written length, and compares the valid byte content of the standard state sequence and the physical alignment snapshot before and after copying. If the integrity check passes, the remaining capacity after the end of the sequentially concatenated byte stream in the merged memory block is filled with empty bytes, ensuring the entire merged memory block has a defined tail. No additional padding is performed when the merged memory block capacity is exactly equal to the merge length. After confirming again that there is no residual data in the tail-filled area, a mixed-state data block is obtained. In this embodiment, the above scheme can merge the lock release state and the physical alignment snapshot into a complete, well-defined, continuous data block in a fixed order, providing reliable input for transaction closed-loop imprint calculation.

[0130] S6443, the mixed state data block is divided into segments with a fixed step size and padded with the last bit to obtain a sequential plaintext slice. Based on a preset initial constant, the sequential plaintext slice is subjected to progressive nonlinear bit operations and state compression to obtain the final hash vector.

[0131] S6444, perform hexadecimal encoding on the final-level hash vector to obtain the transaction closed-loop imprint.

[0132] Specifically, the mixed-state data block is processed using pre-configured SHA-256 hashing rules. First, the mixed-state data block is treated as an input byte stream arranged in a predetermined order, and its actual bit length before hash padding is recorded. The null bytes at the end formed in the preceding order are valid content of the mixed-state data block and do not replace the end-bit padding in this step. Then, a padding bit with a value of one is appended to the end of the input byte stream, followed by consecutive zero padding bits. A fixed-length field for writing the original bit length is retained at the end, ensuring that the total length of the padded data is divisible by the fixed processing step size of SHA-256. The padded data is sequentially segmented according to the consecutive bit segments corresponding to each processing step size to obtain sequential plaintext slices. If the original length field cannot be written or the padded length does not meet the fixed processing step size requirement, the hash calculation is terminated.

[0133] For each sequential plaintext slice, eight preset SHA-256 initial constants are read as the first-level state, and each slice is expanded into an initial message word according to a predetermined byte order. Based on the initial message word, the message words required for subsequent rounds are generated through circular right shift, XOR, and word expansion. Then, the current state, round constants, and message words are sequentially processed through conditional selection, majority decision, circular right shift, XOR, and fixed-length addition, causing each state component to undergo non-linear updates in each round. After processing a sequential plaintext slice, its update result is compressed and merged with the state before entering that slice, serving as the input state for the next sequential plaintext slice, until all sequential plaintext slices are processed, resulting in a final-level hash vector composed of eight fixed-length state components. Any change in the input byte, byte order, or padding content will cause a corresponding change in the final-level hash vector.

[0134] Finally, following the SHA-256 standard byte order, each state component in the final-level hash vector is read sequentially. Each byte is converted into two hexadecimal characters and concatenated continuously in a uniform uppercase encoding order. Leading zeros are retained for smaller bytes to avoid ambiguity caused by different character lengths. After transcoding, a fixed-length transaction loop imprint is obtained and associated with the corresponding suspended transaction identifier and physically aligned snapshot version. If the final-level hash vector length is abnormal or the transcoding result length does not conform to the preset format, the transaction loop imprint is not written. In this embodiment, the above scheme can convert the final state of the control transaction into a unique and verifiable loop imprint, improving the integrity of state traceability.

[0135] S65, based on the transaction closed-loop imprint, perform byte stream splicing and hash digest calculation on the physical alignment snapshot to obtain the electricity meter control record.

[0136] Specifically, the fixed encoding length of the transaction loop imprint and the physical alignment snapshot version are first verified. The transaction loop imprint is converted into an imprint byte stream according to a preset character encoding, and the physical alignment snapshot is serialized according to the predetermined field order of meter address, physical execution status, status version, and data quality marker. Subsequently, the imprint byte stream is concatenated in a fixed order, with the snapshot byte stream preceding it, and a digest is calculated using preset hash rules. The transaction loop imprint, snapshot version, and digest result are associated and written into the energy meter control record; no record is written if any field is missing, the version is inconsistent, or the digest is abnormal. In this embodiment, the above scheme can form a verifiable closed-loop record between the control result and the actual status snapshot.

[0137] The above describes the remote monitoring method for electricity meters in the embodiments of the present invention. The following describes the remote monitoring device for electricity meters in the embodiments of the present invention. Please refer to [link / reference]. Figure 2 One embodiment of the remote monitoring device for electricity meters in this invention includes:

[0138] The receiving module 21 is used to receive communication messages sent by each distributed energy meter, and to perform protocol unpacking and ciphertext decryption on the communication messages to obtain plaintext operation data.

[0139] Filtering module 22 is used to perform timing alignment and numerical filtering on the plaintext running data to obtain timing electrical parameters;

[0140] The detection module 23 is used to compare the timing electrical parameters with the pre-stored operating reference values ​​and detect abrupt changes to determine whether there are electrical deviation characteristic values.

[0141] The matching module 24 is used to perform feature matching based on the electrical deviation feature value and the pre-stored fault feature library if the fault exists, so as to obtain the equipment alarm information.

[0142] The sending module 25 is used to determine the control strategy based on the device alarm information, encapsulate and send control messages to the distributed energy meters based on the control strategy, and obtain the energy meter action receipt.

[0143] The update module 26 is used to update the status record of the distributed energy meters based on the energy meter action receipt to obtain the energy meter control record.

[0144] In this embodiment, the specific implementation of each unit in the above system embodiment is described in the above method embodiment, and will not be repeated here.

[0145] like Figure 3 As shown in the diagram, this embodiment of the invention provides a structural schematic block diagram of a computer device, including:

[0146] At least one processor;

[0147] At least one memory for storing at least one program;

[0148] When the at least one program is executed by the at least one processor, the at least one processor implements the above-described method for predicting dynamic changes in the ecological environment.

[0149] It is evident that the content of the above method embodiments is applicable to this device embodiment. The specific functions implemented in this device embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0150] Furthermore, this application also discloses a computer program product or computer program stored in a computer-readable storage medium. A processor of a computer device can read the computer program from the computer-readable storage medium and execute the computer program, causing the computer device to perform the aforementioned method for predicting dynamic changes in the ecological environment. Similarly, the content of the above method embodiments is applicable to this storage medium embodiment. The specific functions implemented in this storage medium embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0151] The above is a detailed description of the preferred embodiments of the present invention. However, the present invention is not limited to the embodiments described. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A method for remote monitoring of an electricity meter, characterized in that, Includes the following steps: Receive communication messages from each distributed energy meter, perform protocol unpacking and ciphertext decryption on the communication messages to obtain plaintext operation data; The plaintext running data is time-aligned and numerically filtered to obtain the timing electrical parameters; The timing electrical parameters are compared with the pre-stored operating reference values ​​to detect deviations and sudden changes, in order to determine whether there are electrical deviation characteristic values. If it exists, feature matching is performed based on the electrical deviation feature value and the pre-stored fault feature library to obtain equipment alarm information; Based on the device alarm information, a control strategy is determined, and based on the control strategy, control messages are encapsulated and sent to the distributed energy meters to obtain energy meter action receipts. The status records of the distributed energy meters are updated based on the energy meter action receipts to obtain the energy meter control records.

2. The remote monitoring method for electricity meters according to claim 1, characterized in that, The communication message is depacked and decrypted to obtain the plaintext execution data, including: The communication message is scanned by bytes to obtain the frame header identifier and link check code. Based on the frame header identifier and link check code, the communication message is format checked and the packet header is stripped to obtain the message payload data. Based on a preset protocol dictionary, the identifier field of the message payload data is parsed to obtain the service ciphertext segment; The message payload data is sliced ​​in the address field to obtain the meter address code. Based on the meter address code, a matching search is performed in the pre-stored key library to obtain the node decryption key. Based on the node decryption key, the ciphertext segment of the service is decrypted and shifted to obtain a plaintext data stream. The plaintext data stream is byte-ordered and converted to a base to obtain a decimal value. Based on a preset dimensional coefficient, the decimal value is shifted by the decimal point and the units are concatenated to obtain plaintext running data.

3. The remote monitoring method for electricity meters according to claim 1, characterized in that, The step of performing time-series alignment and numerical filtering on the plaintext running data to obtain time-series electrical parameters includes: The plaintext operation data is parsed to obtain the reporting timestamp and electrical measurement value. The reporting timestamp is then mapped onto a time axis based on a preset reference clock cycle to obtain the time offset. Based on the time offset, the electrical measurement values ​​are interpolated and resampled to obtain a synchronous electrical sequence; The synchronous electrical sequence is divided into local data segments by sliding window, and the boundary extrema are removed from the local data segments to obtain extrema-free segments. The extremum removal segment is smoothed using a neighborhood weighted average rule to obtain the timing electrical parameters.

4. The remote monitoring method for electricity meters according to claim 1, characterized in that, The process of determining a control strategy based on the device alarm information, encapsulating and sending control messages to the distributed energy meters based on the control strategy, and obtaining energy meter action receipts includes: The device alarm information is parsed and classified by field to obtain alarm attribute tags. Based on the alarm attribute tags, address matching is performed in a preset strategy matrix to obtain basic control instructions. The execution timing of the basic control instructions is arranged to obtain a control strategy. The control strategy is translated into instruction set based on a preset protocol mapping table to obtain operation bytecode; the distributed energy meters are addressed by network node to obtain the target communication address; Based on the target communication address, the operation bytecode is frame-formatted and securely signed to obtain an encapsulated control message; The encapsulated control message is subjected to channel modulation and time slot allocation to obtain the physical transmission signal; The distributed energy meters are driven by the physical layer through the physical transmission signal to obtain a response data frame. The response data frame is then demodulated, decoded, and the status bit is extracted to obtain an energy meter action receipt.

5. The remote monitoring method for electricity meters according to claim 4, characterized in that, The step of performing frame format concatenation and security signing on the operation bytecode based on the target communication address to obtain an encapsulated control message includes: The operation bytecode is padded with boundary markers and its length is calculated to obtain a delimited data segment. The delimited data segment is then concatenated with data fields based on the target communication address to obtain a verification source sequence. A secure authentication signature is obtained by extracting a digest and calculating a signature from the verification source sequence using a pre-set signature private key. The secure authentication signature is used to append to the delimited data segment to obtain an encapsulated control message.

6. The remote monitoring method for electricity meters according to claim 1, characterized in that, The process of updating the status record of the distributed energy meters based on the energy meter action feedback to obtain the energy meter control record includes: The message payload of the energy meter action receipt is decomposed and cyclic redundancy check is performed to obtain the receipt timestamp and physical execution status. Based on the receipt timestamp and the pre-stored transaction queue, a time sequence matching is performed to obtain the suspended transaction identifier. Based on the suspended transaction identifier, the physical execution state and the preset expectation matrix are XORed to obtain the state offset vector. Based on the state offset vector, the key-value pointers of the pre-stored twin dictionary are overwritten to obtain a physically aligned snapshot; Based on the physical alignment snapshot, the mutex lock of the suspended transaction identifier is released to obtain the transaction closed loop imprint. Based on the transaction closed-loop imprint, the physical alignment snapshot is spliced ​​into a byte stream and hash digest is calculated to obtain the electricity meter control record.

7. The remote monitoring method for electricity meters according to claim 6, characterized in that, The step of releasing the mutex lock on the suspended transaction identifier based on the physical alignment snapshot to obtain the transaction closure imprint includes: The bit field mask of the suspended transaction identifier is extracted to obtain the latch node address, and the current state pointer is obtained by address traversal in the preset concurrency control tree based on the latch node address. The physical alignment snapshot is parsed to obtain the snapshot storage base address, and the current state pointer is subtracted from the snapshot storage base address by the address span to obtain the pointer offset scalar; Based on the pointer offset scalar, the occupancy flag bit corresponding to the latch node address is cleared bit by bit to obtain the lock release status word; The lock release status word and the physical alignment snapshot are concatenated into a byte stream and a hash digest is calculated to obtain the transaction closed-loop imprint.

8. A remote monitoring system for electricity meters, characterized in that, include: The receiving module is used to receive communication messages sent by each distributed energy meter, and to decrypt the communication messages to obtain plaintext operation data. The filtering module is used to perform timing alignment and numerical filtering on the plaintext running data to obtain timing electrical parameters; The detection module is used to compare the timing electrical parameters with the pre-stored operating reference values ​​and detect deviations and sudden changes to determine whether there are electrical deviation characteristic values. The matching module is used to perform feature matching based on the electrical deviation feature value and the pre-stored fault feature library if the fault exists, so as to obtain the equipment alarm information. The distribution module is used to determine the control strategy based on the device alarm information, encapsulate and distribute control messages to the distributed energy meters based on the control strategy, and obtain the energy meter action receipt. The update module is used to update the status record of the distributed energy meters based on the energy meter action receipt, so as to obtain the energy meter control record.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images