Electric energy meter detection data whole-process tracking method based on state word identification

Abstract

The application relates to the technical field of electric energy meter production and detection, and provides an electric energy meter detection data whole-process tracking method based on state word identification, which comprises the following steps: setting a unique identity for an electric energy meter, and setting an encryptable and editable state data block in the electric energy meter; entering the unique identity of the electric energy meter into an internet platform; when the state of the electric energy meter is written, synchronously uploading the state of the current link to the internet platform for backup; entering market order parameters into the internet platform; when the electric energy meter is delivered, matching the market order parameters with the unique identity of the electric energy meter and the state data block of the electric energy meter through the internet platform; when the electric energy meter enters a detection link, the detection equipment automatically reads the asset number of the electric energy meter, generates a corresponding state word according to the current link and sends the state word to the detection equipment, and after the detection equipment completes detection, the detection data and the state word are packaged and uploaded to a database, so that real-time binding of the detection data and the state word is realized.

Description

Technical Field

[0001] This application relates to the field of electricity meter production and testing technology, and in particular to a method for tracking the entire process of electricity meter testing data based on status word identifiers. Background Technology

[0002] Traditional data tracking methods have the following technical shortcomings in the production and testing of electricity meters:

[0003] 1. Fragmented status management: In existing technologies, the status information of semi-finished and finished energy meters (such as appearance inspection results, metering parameter writing status, etc.) is usually stored in separate systems or paper records in different stages, lacking a unified digital carrier, which makes it difficult to trace status information and easily leads to data inconsistency problems.

[0004] 2. Disconnect between test data and process: The test data generated by the testing equipment (such as key point voltage, total power consumption, etc.) is not effectively linked with the real-time status of the electricity meter, making it impossible to achieve closed-loop management of "test data - status change - process flow" and making it difficult to accurately locate quality problems in the production process.

[0005] 3. Lack of anomaly handling mechanism: When a test fails, the traditional method only records the reason for the failure manually, without establishing a standardized anomaly status identification and process backtracking mechanism, which leads to chaotic connection of the retesting process after repair and low production efficiency.

[0006] 4. Low level of automation in order matching: When the goods are shipped out, the system relies on manual verification of order parameters and electricity meter status, which can easily lead to problems such as mismatch of specifications and models and omission of parameters. There is a lack of automated matching and verification methods based on data blocks.

[0007] Therefore, a method is urgently needed to solve at least one of the above problems. Summary of the Invention

[0008] This application provides a method for tracking the entire process of electricity meter testing data based on status word identifiers. It aims to solve the problem that although there are solutions for product identification using barcodes or RFID in the existing technology, there is no technical solution that divides the electricity meter status into multi-field data blocks for encrypted management and achieves real-time binding of testing data throughout the entire process through status word identifiers.

[0009] Firstly, this application provides a method for tracking the entire process of electricity meter detection data based on status word identifiers, including:

[0010] A unique identifier is set for each electricity meter. The identifier includes product code, year, month, date and sequence number information. An encrypted and editable status data block is set in the electricity meter. The status data block is divided into a first field, a second field and a third field. The first field is used to mark the status of the semi-finished electricity meter, the second field is used to mark the meter information, and the third field is used to mark the status of the finished electricity meter.

[0011] The unique identifier of the electricity meter is entered into the internet platform. When writing the status of the electricity meter, the status of the current stage is synchronously uploaded to the internet platform for backup. Market order parameters are entered into the internet platform. When the electricity meter is issued, the market order parameters are matched with the unique identifier of the electricity meter and the status data block of the electricity meter through the internet platform. If the match is successful, the electricity meter is allowed to be issued. According to the prescribed protocol, the detection status of each stage is written into the status data block of the electricity meter for storage.

[0012] The testing equipment connects to the tracking system via an IoT interface. When the electricity meter enters the testing phase, the testing equipment automatically reads the electricity meter's asset number, generates the corresponding status word based on the current phase, and sends it to the testing equipment. After the testing equipment completes the testing, it packages the testing data and status word and uploads them to the database, realizing real-time binding between the testing data and status word.

[0013] Set status word change rules: if the current stage of the test data collection is completed and the verification is passed, the status word is updated to the corresponding status of the next stage; if the test fails, the status word is temporarily changed to an exception code and associated with the reason for the failure, and the normal test process is resumed after maintenance.

[0014] In some embodiments, setting an encryptable editable status data block in the energy meter includes: dividing an independent data area in the energy meter's storage module as a status data block; the status data block is access-controlled through an encryption algorithm, allowing only authorized write-status host computers to edit it; the first field specifically marks the appearance status, metering function status, communication function status, key point voltage values, peripheral connection status, and overall power consumption data of the semi-finished energy meter; the second field specifically marks the energy meter's specifications, wiring type, power supply method, software version number, and hardware version number; the third field specifically marks the finished energy meter's metering parameter writing completion status, metering parameter verification pass status, outbound parameter writing completion status, and outbound parameter verification pass status.

[0015] In some embodiments, the step of recording the unique identifier of the electricity meter into the Internet platform and synchronously uploading the status of the current stage to the Internet platform for backup when writing the status of the electricity meter includes: in the semi-finished product ID recording stage corresponding to the unique identifier, the unique identifier of the electricity meter and the initial status data block are synchronously recorded into the database of the Internet platform through the status writing host computer; before each stage writes the status of the electricity meter, the status writing host computer first sends a status query request to the Internet platform to obtain the current status of the electricity meter stored in the platform, and compares it field by field with the status data block read in real time inside the electricity meter; if the comparison result is consistent, the status writing operation of the current stage is executed, and after the writing is completed, the updated status data block is uploaded to the Internet platform in real time for backup storage.

[0016] In some embodiments, the matching of market order parameters with the unique identifier of the electricity meter and the status data block of the electricity meter through the Internet platform includes: in the order information entry stage, entering the order parameters required by the customer into the Internet platform; the order parameters include meter specifications and model, metering parameter requirements, and wiring type; when the electricity meter is issued, the Internet platform automatically retrieves the status data block corresponding to the unique identifier of the electricity meter, extracts the meter specifications and model, wiring status from the second field, and the metering parameter verification status and the issuance parameter writing status from the third field; the extracted parameters are compared with the order parameters item by item, and if the meter specifications and model match, the metering parameter verification status is passed, and the issuance parameter writing status is completed, then the matching is deemed successful.

[0017] In some embodiments, the step of writing the detection status of each stage into the status data block of the energy meter for storage according to a prescribed protocol includes: the write status host computer pre-configuring a prescribed protocol for communication with the energy meter, the protocol including data format, verification rules, and write permission verification mechanism; in the production parameter testing, recalibration parameter testing, and outgoing parameter testing stages, the write status host computer generates status information for corresponding fields based on the test results; and through wired or wireless communication, the generated status information is encoded according to the prescribed protocol and written into the corresponding field of the energy meter status data block, and the storage verification mechanism of the energy meter is triggered to ensure the integrity of the written data.

[0018] In some embodiments, the testing device interfaces with the tracking system via an IoT interface. When the electricity meter enters the testing phase, the testing device automatically reads the asset number of the electricity meter, including: the testing device integrates an RFID reading module or a barcode scanning module, and the asset number is attached to the surface of the electricity meter in the form of an RFID tag or barcode; when the electricity meter enters the identification range of the testing device, the testing device sends a reading command to the tracking system via the IoT interface, automatically captures and parses the asset number information; the tracking system associates the unique identifier and historical status data of the electricity meter with the asset number, and generates a testing task work order for the current phase.

[0019] In some embodiments, the step of generating a corresponding status word based on the current stage and sending it to the detection device, and then having the detection device package the detection data and status word and upload it to the database after completing the detection, thereby achieving real-time binding between the detection data and the status word, includes: the tracking system generating a unique status word prefix based on the current detection stage, wherein the status word includes a stage identifier, a timestamp, and a checksum; sending the status word to the detection device, which automatically collects the detection data after completing the detection; and packaging the detection data and status word according to a preset data structure and uploading it to the tracking system's database through an IoT interface to form a detection record with a status identifier.

[0020] In some embodiments, the step of updating the status word to the status corresponding to the next stage if the current stage's detection data acquisition is completed and verification is passed includes: the tracking system verifies the detection data uploaded by the detection device; if the verification is passed, the system generates the target status of the next stage according to the preset stage flow rules; the target status is specifically manifested as a change in the status bit of the corresponding field in the status data block, for example, after the error detection is qualified, the metering parameter verification status in the third field is updated; the target status is written to the status data block of the energy meter through the status writing host computer, and the records in the Internet platform are updated synchronously.

[0021] In some embodiments, the step of temporarily changing the status word to an exception code if the detection fails includes: when the detection data verification fails, the tracking system generates an exception code corresponding to the failure step; the exception code is written into the corresponding field of the electricity meter status data block, and the current status of the electricity meter is marked as abnormal in the Internet platform, and the time point of the failure is recorded.

[0022] In some embodiments, associating the cause of non-compliance and re-entering the normal testing process after repair includes: when uploading the test data in a package, binding the cause of non-compliance as additional information with the exception code and storing it in the database; repairing the electricity meter according to the cause of non-compliance recorded in the database, and clearing the exception code by writing the status to the host computer after the repair is completed; after clearing the exception code, the electricity meter re-enters the testing process from the previous stage of the abnormal stage, or directly enters the original abnormal stage for re-inspection, until the status word continues to flow after the test is qualified.

[0023] This application provides a method for tracking the entire process of electricity meter testing data based on status word identifiers. It aims to achieve unified storage and real-time synchronization of electricity meter status information throughout its entire lifecycle, from semi-finished to finished product, by combining unique identifiers with status data blocks. This solves the problem of fragmented status information in traditional methods and improves data traceability efficiency. The testing equipment automatically reads the asset number and generates a status word, then packages and uploads the testing data and status word in real time, ensuring a one-to-one correspondence between the testing results at each stage and the electricity meter status, avoiding data confusion or loss, and improving the accuracy of quality problem location. Through a preset mechanism linking abnormal codes with non-conformance reasons, the meter can automatically re-enter the corresponding testing stage after repair, reducing process chaos caused by manual intervention and shortening the processing cycle for non-conforming products. The internet platform automatically matches status data block fields with order parameters, eliminating manual verification errors and ensuring that the parameters of the outgoing electricity meters are completely consistent with customer requirements, reducing order delivery error rates. The status data blocks employ encrypted editing permission control, allowing only authorized devices to write to them, preventing unauthorized tampering and ensuring the integrity and security of production data.

[0024] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

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

[0026] Figure 1 This is a schematic flowchart illustrating the steps of a method for tracking the entire process of electricity meter detection data based on status word identifiers, provided in an embodiment of this application.

[0027] Figure 2 This is an overall working block diagram corresponding to a method for tracking the entire process of electricity meter detection data based on status word identifiers provided in an embodiment of this application;

[0028] Figure 3This is a flowchart of writing the status data block of an energy meter according to an embodiment of this application;

[0029] Figure 4 This is a schematic diagram of the structure of a full-process tracking device for electricity meter detection data based on status word identifiers provided in an embodiment of this application;

[0030] Figure 5 This is a schematic block diagram of the structure of a computer device provided in an embodiment of this application.

[0031] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Detailed Implementation

[0032] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0033] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the order described. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0034] It should be understood that, in order to clearly describe the technical solutions of the embodiments of the present invention, the terms "first" and "second" are used in the embodiments of the present invention to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0035] It should be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0036] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0037] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0038] Traditional data tracking methods have the following technical shortcomings in the production and testing of electricity meters:

[0039] 1. Fragmented status management: In existing technologies, the status information of semi-finished and finished energy meters (such as appearance inspection results, metering parameter writing status, etc.) is usually stored in separate systems or paper records in different stages, lacking a unified digital carrier, which makes it difficult to trace status information and easily leads to data inconsistency problems.

[0040] 2. Disconnect between test data and process: The test data generated by the testing equipment (such as key point voltage, total power consumption, etc.) is not effectively linked with the real-time status of the electricity meter, making it impossible to achieve closed-loop management of "test data - status change - process flow" and making it difficult to accurately locate quality problems in the production process.

[0041] 3. Lack of anomaly handling mechanism: When a test fails, the traditional method only records the reason for the failure manually, without establishing a standardized anomaly status identification and process backtracking mechanism, which leads to chaotic connection of the retesting process after repair and low production efficiency.

[0042] 4. Low level of automation in order matching: When the goods are shipped out, the system relies on manual verification of order parameters and electricity meter status, which can easily lead to problems such as mismatch of specifications and models and omission of parameters. There is a lack of automated matching and verification methods based on data blocks.

[0043] While existing technologies include product identification via barcodes or RFID, there is a lack of solutions that encrypt and manage the electricity meter status into multi-field data blocks, and achieve real-time binding of test data throughout the entire process using status word identifiers. In particular, there is a lack of systematic design for "automatically updating the status word to the next stage after test data collection and verification" and "associating abnormal codes with reasons for non-compliance and driving the re-inspection process after maintenance." This invention effectively solves the technical problems of fragmented data management and inefficient process integration in traditional methods by constructing a status data block structure, status word change rules, and a test data binding mechanism.

[0044] Please see Figure 1 , Figure 1 This is a schematic flowchart illustrating a method for tracking the entire process of electricity meter detection data based on status word identifiers, according to an embodiment of this application. This method can be implemented using computer equipment, which can be deployed on a single server or a server cluster. It can also be deployed on handheld terminals, laptops, wearable devices, or robots, etc.

[0045] It should be noted that the acquisition of any information mentioned in the provided methods is in compliance with relevant regulations and is carried out with the user's consent, and will not infringe on the user's privacy or violate relevant laws and regulations.

[0046] like Figure 1 As shown, the provided method for tracking the entire process of electricity meter detection data based on status word identifiers includes steps S101 to S104. Details are as follows:

[0047] Step S101. Set a unique identifier for the electricity meter. The identifier includes product code, year, month, date and sequence number information. Set an encrypted and editable status data block in the electricity meter. The status data block is divided into a first field, a second field and a third field. The first field is used to mark the status of the semi-finished electricity meter, the second field is used to mark the meter information, and the third field is used to mark the status of the finished electricity meter.

[0048] Specifically, a unique identifier is constructed: each electricity meter is assigned a globally unique identifier, which includes the product code, production year, month, date and serial number, to ensure traceability throughout its entire life cycle.

[0049] Status data block design: Create an encrypted and editable status data block in the built-in storage module (such as EEPROM or security chip) of the energy meter, which is divided into three fields to manage the status and basic information of different stages.

[0050] The identification coding rules include: Product code: using a company-defined prefix (e.g., "DLT-") + category code (e.g., "01" for "electricity meter"), a fixed 8-digit format. Time information: year (4 digits, e.g., "2025"), month (2 digits, padded with zeros), day (2 digits, padded with zeros), a total of 8 digits. Serial number: a daily serial number, using 6 digits (e.g., "000001"), ensuring uniqueness for each day. Final identification example: DLT-01-20250912-000001.

[0051] The status data block structure includes: First field (Semi-finished product status): 16 bits, using a bitmask to mark the process status (e.g., bit 1 indicates "Appearance inspection completed", bit 2 indicates "Metering chip initialization"), supporting dynamic expansion. Second field (Meter information): 64 bits, storing fixed attributes (e.g., rated voltage, current specifications, communication protocol type) and variable parameters (e.g., initial metering baseline), stored encrypted in JSON format (encryption algorithm such as AES-128). Third field (Finished product status): 16 bits, marking the finished product inspection status (e.g., "0x01" indicates "Withstand voltage test passed", "0x02" indicates "Parameter writing completed"), supporting exception codes (e.g., "0xFF" indicates inspection failed).

[0052] The encryption mechanism includes: when writing state data blocks, a session key is generated through the device's security chip to encrypt the field data and prevent unauthorized tampering; when reading, the digital signature (such as the SHA-256 hash value) needs to be verified.

[0053] Step S102. Enter the unique identifier of the electricity meter into the Internet platform. When writing the status of the electricity meter, the status of the current stage is synchronously uploaded to the Internet platform for backup. Enter the market order parameters into the Internet platform. When the electricity meter is issued, the market order parameters are matched with the unique identifier of the electricity meter and the status data block of the electricity meter through the Internet platform. If the match is qualified, the electricity meter is allowed to be issued. According to the prescribed protocol, the detection status of each stage is written into the status data block of the electricity meter for storage.

[0054] Specifically, data synchronization and backup involves synchronizing the electricity meter's identification and status data to the cloud platform in real time, creating a complete digital archive. Automated order matching verifies the consistency between order parameters and electricity meter status before shipment, avoiding human error. The status writing protocol defines a standard protocol for writing status data to the status data block at each stage (such as appearance inspection and functional testing).

[0055] The internet platform architecture adopts a microservice architecture and is deployed in a private or hybrid cloud, including an "identity registration module," a "status monitoring module," and an "order matching engine." The electricity meter connects to the platform via a wired (RJ45) or wireless (4G / NB-IoT) interface. Each time the status changes (e.g., upon completion of a detection), an HTTP POST request is triggered to upload the hash value and timestamp of the current status data block.

[0056] The order matching process includes: when entering market orders, key parameters (such as rated current "10(60)A" and communication method "RS485+LoRa") are entered simultaneously. Before the goods are shipped out, the system automatically retrieves the second field (meter information) of the electricity meter and compares it with the order parameters. The verification items include: specifications, communication protocol, and metering parameter range (such as voltage "220V±10%").

[0057] The matching rules use regular expressions or structured queries (such as SQL). If all required fields are consistent and the status of the third field is "finished product qualified (0x0F)", a green outbound label is generated; otherwise, a red warning is marked.

[0058] The detection status writing protocol includes: defining a unified data format (such as JSON) containing fields: {device number, stage name, status value, timestamp, operator ID}. Equipment at each stage (such as appearance inspection station, withstand voltage tester) connects via OPC UA or MQTT protocol, and writes the detection results to the corresponding positions of the first / third fields of the status data block according to the protocol.

[0059] Step S103. The detection equipment connects to the tracking system through the Internet of Things interface. When the electricity meter enters the detection stage, the detection equipment automatically reads the asset number of the electricity meter, generates the corresponding status word according to the current stage, and sends it to the detection equipment. After the detection equipment completes the detection, it packages the detection data and status word and uploads them to the database to realize the real-time binding of detection data and status word.

[0060] Specifically, the testing equipment automatically identifies the electricity meter through a standardized interface and generates a unique status word for each process. The testing results (such as voltage values ​​and power consumption data) are packaged and stored with the status word to achieve a "data-status-process" association.

[0061] Equipment docking and identification include: the testing equipment is equipped with an RFID reader or QR code scanning module, and the unique identification identifier (such as through EPC code or QR code) is automatically read when the energy meter enters the workstation. The tracking system generates the current status word (format: 4-digit process code + 8-digit timestamp + 2-digit check digit, such as "0320250912AB") based on the current workstation type (such as "metering accuracy testing" corresponding to the process code "03").

[0062] Data binding and uploading include: after the detection equipment completes data acquisition (such as the measured voltage value of key points "225V", power consumption "0.5W"), the data is encapsulated into a data packet containing a status word.

[0063] {;

[0064] "Equipment Number":"DLT-01-20250912-000001",;

[0065] "Status word":"0320250912AB",;

[0066] "Detection data":{;

[0067] Voltage: 225.0;

[0068] Power consumption: 0.5;

[0069] "Qualified": true;

[0070] },;

[0071] "Collection Time": "2025-09-12T06:15:30Z";

[0072] Data packets are uploaded to a time-series database (such as InfluxDB) via HTTP / 2 or Kafka message queues to create a three-dimensional index of "status word - detection data - time" to support subsequent full-process traceability.

[0073] Step S104. Set the status word change rules. If the current stage's detection data collection is completed and the verification is passed, the status word is updated to the corresponding status of the next stage. If the detection fails, the status word is temporarily changed to an exception code and associated with the reason for the failure. After repair, the normal detection process will be restarted.

[0074] Specifically, after a test passes, the status word is automatically updated to the next stage according to preset rules, driving the process flow. When a test fails, an exception code is marked and associated with the cause, triggering a closed-loop process of repair and re-inspection.

[0075] The rules for changing the status include: defining a finite state machine (FSM) for status word changes, such as: Semi-finished product stage: "Appearance inspection passed (0x01)" → "Metering chip writing (0x02)" → "Functional test (0x04)" (status is accumulated through bitwise OR operations). Finished product stage: "Withstand voltage test passed (0x01)" → "Parameter verification (0x02)" → "Finished product passed (0x03)" (using numerical increment rules). After the testing equipment uploads the qualified data, the system automatically calls the status change interface to update the current status word to the target value of the next stage (e.g., from "0320250912AB" to "0420250912CD").

[0076] The abnormal status handling mechanism includes: Abnormal code definition: using the format of "process code + error type" (such as "03-E01" indicating "error out of range" in the metrology and testing process), and associated with the preset non-compliance cause library (storing processing suggestions, such as "recalibrate the metrology chip").

[0077] Process-driven: When a test fails, the system automatically: ① marks the third field status as an exception code (e.g., "0xFF") and records the error occurrence in the first field; ② generates a repair work order, pushes it to the MES system, and includes the reason for the failure and historical test data; ③ after repair, clears the exception code using a dedicated reset device, resets the status word to the initial value of that stage, and re-enters the testing process. The verification mechanism includes: before each status change, verifying the integrity of the test data (e.g., whether it contains required fields, whether the values ​​are within a reasonable range); if verification fails, the change is blocked and an alarm is triggered.

[0078] In some embodiments, setting an encryptable editable status data block in the energy meter includes: dividing an independent data area in the energy meter's storage module as a status data block; the status data block is access-controlled through an encryption algorithm, allowing only authorized write-status host computers to edit it; the first field specifically marks the appearance status, metering function status, communication function status, key point voltage values, peripheral connection status, and overall power consumption data of the semi-finished energy meter; the second field specifically marks the energy meter's specifications, wiring type, power supply method, software version number, and hardware version number; the third field specifically marks the finished energy meter's metering parameter writing completion status, metering parameter verification pass status, outbound parameter writing completion status, and outbound parameter verification pass status.

[0079] By dividing the energy meter storage module into independent areas as status data blocks and implementing access control through encryption algorithms, it is ensured that only authorized devices can edit the data; the specific status marker content of the three fields is clearly defined, covering the key statuses of the semi-finished product, basic meter information, and finished product stages.

[0080] The storage module is partitioned and encrypted by dividing a fixed address space (such as 0x1000-0x1FFF) in the built-in Flash or external EEPROM of the energy meter MCU as a status data block area. The area is written protected by the AES-256 encryption algorithm. The host computer needs to pass security authentication (such as digital certificate verification) to obtain write permission to write the status.

[0081] The authorization verification process involves the host computer sending a write request → the electricity meter verifying the MAC address whitelist → verifying the session key (generated via HMAC-SHA256) → allowing the write operation.

[0082] The detailed field content includes: First field (semi-finished product status, 128 bits): Appearance status (8 bits): Each bit corresponds to a different appearance inspection item (e.g., the first bit "1" indicates that the shell has no scratches, the second bit "1" indicates that the display screen has no defects); Metering function status (32 bits): Stores key point voltage values ​​(e.g., rated voltage 220V±10%), and total power consumption data (unit mW, retaining 1 decimal place); Communication function status (16 bits): Marks the initialization status of communication modules such as RS485 and LoRa (e.g., "0x03" indicates that dual communication ports are activated); Peripheral connection status (16 bits): Indicates the installation compliance of peripherals such as wiring terminals and current transformers (marked by bitmask).

[0083] The second field (meter information, 256 bits): Specifications and Model (64 bits): such as "DTZY123-Z", which includes information such as the type of electricity meter (single-phase / three-phase) and communication method; Wiring type (8 bits): "01" indicates single-phase two-wire, "02" indicates three-phase four-wire, etc.; Software / Hardware Version Number (32 bits each): such as "V1.2.3" "HW-2025A", which supports version upgrade traceability.

[0084] The third field (finished product status, 128 bits): Metering parameter writing completion status (32 bits): marks whether parameters such as electricity meter constant and rate period have been successfully written (e.g., "0x01" indicates completion); Outbound parameter verification status (32 bits): contains the final verification result (Boolean value) of parameters such as wiring system and communication protocol required by the order.

[0085] In some embodiments, the step of recording the unique identifier of the electricity meter into the Internet platform and synchronously uploading the status of the current stage to the Internet platform for backup when writing the status of the electricity meter includes: in the semi-finished product ID recording stage corresponding to the unique identifier, the unique identifier of the electricity meter and the initial status data block are synchronously recorded into the database of the Internet platform through the status writing host computer; before each stage writes the status of the electricity meter, the status writing host computer first sends a status query request to the Internet platform to obtain the current status of the electricity meter stored in the platform, and compares it field by field with the status data block read in real time inside the electricity meter; if the comparison result is consistent, the status writing operation of the current stage is executed, and after the writing is completed, the updated status data block is uploaded to the Internet platform in real time for backup storage.

[0086] The two-way status verification mechanism ensures data consistency by comparing the status with the local status of the electricity meter through the Internet platform before the status is written, thus avoiding status conflicts caused by network latency or equipment failure.

[0087] Initial entry and synchronization include: When entering the semi-finished product ID, the write status host computer connects to the energy meter via USB or Bluetooth interface, reads the unique identifier (such as barcode parsing value) and the initial status data block (default all 0 or preset initial value), and uploads it to the platform database via HTTPS protocol to establish the "identity identifier - initial status" mapping relationship.

[0088] Status comparison and writing include: Before writing the status at each stage, the host computer first sends a GET request (carrying an identity identifier) ​​to the platform to obtain the latest status data block (including timestamp) stored on the platform.

[0089] Simultaneously, the local status data block of the electricity meter is read in real time, and the CRC check code (generated by MD5 hash) and timestamp of the two are compared. If they match, writing is allowed; otherwise, an error message is triggered (such as "status inconsistent, writing is prohibited"). After writing is completed, the host computer uploads the updated status block and its SHA-256 hash value to the platform, overwriting the original record, to ensure that the platform and the device status are synchronized in real time.

[0090] In some embodiments, the matching of market order parameters with the unique identifier of the electricity meter and the status data block of the electricity meter through the Internet platform includes: in the order information entry stage, entering the order parameters required by the customer into the Internet platform; the order parameters include meter specifications and model, metering parameter requirements, and wiring type; when the electricity meter is issued, the Internet platform automatically retrieves the status data block corresponding to the unique identifier of the electricity meter, extracts the meter specifications and model, wiring status from the second field, and the metering parameter verification status and the issuance parameter writing status from the third field; the extracted parameters are compared with the order parameters item by item, and if the meter specifications and model match, the metering parameter verification status is passed, and the issuance parameter writing status is completed, then the matching is deemed successful.

[0091] Parameterized order verification defines the mapping relationship between key order parameters and status data block fields, and achieves automated matching through structured comparison rules, avoiding errors from manual verification.

[0092] Order parameters are entered through the order entry interface on the platform. Required fields include: meter specifications and model (e.g., "three-phase four-wire prepaid smart meter"), metering parameter requirements (e.g., "rated current 10(60)A"), and wire type (e.g., "three-phase three-wire"). The system automatically converts these into structured data (e.g., JSON format) for storage.

[0093] The automated matching process includes: When the electricity meter is dispatched, the platform queries the status data block based on the meter's unique identifier and extracts: the second field: specification model (e.g., "DTZY123-Z"), wire type (field value "02" corresponds to three-phase four-wire); the third field: metering parameter verification status (e.g., "0x01" indicates pass), and dispatching parameter writing status (e.g., "0x02" indicates completion).

[0094] The comparison rules include: complete matching of specifications and models (exact string comparison); the wire type code is consistent with the order requirements; the measurement parameter verification status is "passed" and the outbound parameter writing status is "completed"; matching results: if all conditions are met, an outbound permission is generated; otherwise, outbound is rejected and a mismatch item is marked (such as "specification and model do not match").

[0095] In some embodiments, the step of writing the detection status of each stage into the status data block of the energy meter for storage according to a prescribed protocol includes: the write status host computer pre-configuring a prescribed protocol for communication with the energy meter, the protocol including data format, verification rules, and write permission verification mechanism; in the production parameter testing, recalibration parameter testing, and outgoing parameter testing stages, the write status host computer generates status information for corresponding fields based on the test results; and through wired or wireless communication, the generated status information is encoded according to the prescribed protocol and written into the corresponding field of the energy meter status data block, and the storage verification mechanism of the energy meter is triggered to ensure the integrity of the written data.

[0096] Standardized communication protocols ensure that the detection status at each stage is reliably written to the status data block, thus preventing data corruption, by defining a write protocol that includes data format, verification rules, and permission verification.

[0097] The protocol architecture design includes: Data format: TLV (type-length-value) format, for example: [type=0x01 (appearance inspection status)][length=4 bytes][value=0x000001 (qualified)] Verification rules: CRC32 check value is calculated before writing, and the energy meter automatically verifies after writing. If the verification fails, it will roll back and record the error log; Authorization verification: Only authorized host computers in write status (MAC address pre-entered whitelist) can initiate write requests. Each request is accompanied by a timestamp and digital signature (generated by RSA algorithm).

[0098] The process status writing includes: Production parameter testing stage: generating appearance status, power consumption data, etc., and writing to the corresponding bit of the first field; Outbound parameter detection stage: verifying whether the order parameters have been written, generating the outbound parameter writing status, and writing to the third field; Communication methods supported: RS-485 (wired) or BLE (wireless), default baud rate 9600, 8 data bits, 1 stop bit, even parity.

[0099] In some embodiments, the testing device interfaces with the tracking system via an IoT interface. When the electricity meter enters the testing phase, the testing device automatically reads the asset number of the electricity meter, including: the testing device integrates an RFID reading module or a barcode scanning module, and the asset number is attached to the surface of the electricity meter in the form of an RFID tag or barcode; when the electricity meter enters the identification range of the testing device, the testing device sends a reading command to the tracking system via the IoT interface, automatically captures and parses the asset number information; the tracking system associates the unique identifier and historical status data of the electricity meter with the asset number, and generates a testing task work order for the current phase.

[0100] IoT Interface and Automatic Identification: Non-contact reading of electricity meter identification is achieved through RFID or barcode technology, historical data is linked and inspection work orders are generated, thereby improving process automation.

[0101] Testing equipment (such as a withstand voltage test bench) integrates a UHF RFID reader (supporting ISO 18000-6C protocol) or an industrial-grade barcode scanner (supporting high-speed QR code reading). An RFID tag (128-bit EPC code) or a QR code (containing an identification string) with a unique identifier is affixed to the surface of the electricity meter. When the electricity meter enters the equipment's identification range (RFID effective distance 1-3 meters, barcode scanning distance 0.5-1 meter), the equipment sends a read command to the tracking system via the MQTT protocol. The system parses the asset number, queries the database to obtain the electricity meter's unique identifier, current status data block, and historical testing records (such as the last testing stage and pass / fail status). Based on the current stage type (such as "metering error detection") and historical status, a testing work order (including testing items, standard values, and allowable error range) is generated and pushed to the equipment's operation interface.

[0102] In some embodiments, the step of generating a corresponding status word based on the current stage and sending it to the detection device, and then having the detection device package the detection data and status word and upload it to the database after completing the detection, thereby achieving real-time binding between the detection data and the status word, includes: the tracking system generating a unique status word prefix based on the current detection stage, wherein the status word includes a stage identifier, a timestamp, and a checksum; sending the status word to the detection device, which automatically collects the detection data after completing the detection; and packaging the detection data and status word according to a preset data structure and uploading it to the tracking system's database through an IoT interface to form a detection record with a status identifier.

[0103] The status word structured design achieves a unique binding between detection data and process steps by including a status word containing a step identifier, timestamp, and check bit, supporting full-process traceability.

[0104] The status word generation rules include: Format: Stage identifier (2 bits, such as "01" for appearance inspection) + timestamp (14 bits, YYYYMMDDHHMMSS) + check bit (2 bits, XOR check), such as "03202509120830AB"; The tracking system generates the status word based on the current inspection stage number (obtained from the MES system) and the real-time time, and sends it to the inspection device through the API interface.

[0105] After data acquisition is completed through the testing equipment (e.g., voltage 223V, error +1.5%), the data is packaged according to the following structure:

[0106] {;

[0107] Device ID: "DLT-01-20250912-000001", ;

[0108] "Status word":"03202509120830AB",;

[0109] "Testing Items":["Voltage Test","Error Verification"],;

[0110] "Test Results":{"Voltage":223.0, "Error":1.5, "Pass":false},;

[0111] "Timestamp":"2025-09-12T08:30:15Z";

[0112] };

[0113] Uploaded to the MySQL database of the tracking system via HTTP POST request, an index of "status word - detection result" is created, supporting quick query of corresponding detection data by status word.

[0114] In some embodiments, the step of updating the status word to the status corresponding to the next stage if the current stage's detection data acquisition is completed and verification is passed includes: the tracking system verifies the detection data uploaded by the detection device; if the verification is passed, the system generates the target status of the next stage according to the preset stage flow rules; the target status is specifically manifested as a change in the status bit of the corresponding field in the status data block, for example, after the error detection is qualified, the metering parameter verification status in the third field is updated; the target status is written to the status data block of the energy meter through the status writing host computer, and the records in the Internet platform are updated synchronously.

[0115] The automated process automatically updates the status data block fields based on preset rules after a qualified inspection, driving the production process to the next stage and avoiding delays caused by manual intervention.

[0116] Verification and rule matching include: after receiving the detection data, the tracking system verifies it according to the standard value (e.g., voltage allowable range 220V±15%, error ≤±1.0%). If all indicators are qualified, a status update is triggered.

[0117] The process flow rules are shown in the table below:

[0118]

[0119] The status update operation includes: the system generates the target status (such as setting the "metering parameter verification status" of the third field from 0x00 to 0x01), and sends a write command to the energy meter through the write status host computer; after the host computer completes the write, it synchronously calls the platform API to update the Internet platform record, with the operation time and operator ID (obtained from the login token).

[0120] In some embodiments, the step of temporarily changing the status word to an exception code if the detection fails includes: when the detection data verification fails, the tracking system generates an exception code corresponding to the failure step; the exception code is written into the corresponding field of the electricity meter status data block, and the current status of the electricity meter is marked as abnormal in the Internet platform, and the time point of the failure is recorded.

[0121] Standardized abnormal status identification generates a unique abnormal code when a test fails, marks the status data block, and synchronizes it to the platform, providing clear guidance for subsequent maintenance.

[0122] The exception code generation includes: Format: process code (2 digits) + error type (2 digits), such as "03E0" indicating "error out of range" in the metrology and testing process, corresponding to the error type code table (pre-existing in the tracking system); Generation logic: Match the error type according to the non-conforming item (such as error = 1.6% > 1.0%), and combine the process code to generate the exception code.

[0123] Status updates are synchronized with the platform by writing an exception code (overwriting the original status value) to the third field of the energy meter status data block, and simultaneously marking the "abnormal status" in the energy meter file on the platform, recording the time of failure (accurate to the second) and the exception code;

[0124] The early warning mechanism is triggered by sending emails / SMS notifications to quality management personnel, which include abnormal codes, non-conforming steps, and links to historical test data.

[0125] In some embodiments, associating the cause of non-compliance and re-entering the normal testing process after repair includes: when uploading the test data in a package, binding the cause of non-compliance as additional information with the exception code and storing it in the database; repairing the electricity meter according to the cause of non-compliance recorded in the database, and clearing the exception code by writing the status to the host computer after the repair is completed; after clearing the exception code, the electricity meter re-enters the testing process from the previous stage of the abnormal stage, or directly enters the original abnormal stage for re-inspection, until the status word continues to flow after the test is qualified.

[0126] By binding the reasons for non-compliance with exception codes, the abnormal status can be cleared after repair, and re-inspection from specified stages can be supported, ensuring closed-loop management of quality issues.

[0127] The non-compliance reason binding includes: when uploading test data, adding a "non-compliance reason" field (such as "calibration parameter error of metering chip") to the database record, establishing a foreign key association with the exception code, and supporting subsequent statistical analysis (such as generating quality reports by reason).

[0128] The maintenance and re-inspection process includes: maintenance personnel read the abnormal codes and causes through the maintenance terminal, and troubleshoot the fault by referring to historical test data (such as recalibrating the metering chip); after maintenance is completed, a dedicated reset device (write status host computer) is used to clear the abnormal codes in the status data block and write the "maintenance completed" mark (such as setting the third field to "0xFE"); re-inspection strategy: the system automatically determines the re-inspection starting point according to the type of abnormal link. For example, if the appearance inspection fails, the re-inspection starts from the "appearance inspection" link after maintenance; if the metrological test fails, the re-inspection starts from the link before "metrological function test" until the test is qualified and the status word continues to flow.

[0129] In some embodiments, the data redundancy problem of traditional fixed-field storage is solved by using an autoencoder to compress and store state data blocks and by reconstructing error detection data anomalies, while realizing real-time health monitoring of state data.

[0130] Model building and training include: Data preprocessing: collecting historical state data blocks (including normal / abnormal state samples), normalizing them, and using them as the training set; Network structure: designing a three-layer autoencoder (384-dimensional input layer → 64-dimensional hidden layer → 384-dimensional output layer), with the hidden layer being the compressed state feature vector; Training objective: minimizing the reconstruction error (MSE) so that the model learns the latent feature distribution of normal state data.

[0131] The real-time application process includes: Data compression: The host computer writes the original state data (384 bits) into the trained encoder, generates a 64-dimensional feature vector, and stores it in the energy meter storage module, compressing the storage space; Anomaly detection: When reading the state data, the original data is reconstructed through the decoder, and the reconstruction error is calculated (if the error is greater than the threshold of 0.15, it is judged as an anomaly); Anomaly marking: If an anomaly is detected, the anomaly code (anomaly type classification based on K-means clustering) is automatically written into the reserved field of the state data block (such as the last 8 bits of the first field), triggering a quality warning.

[0132] In some embodiments, by constructing a knowledge graph of electricity meter parameters and combining it with a graph neural network (GNN) to achieve semantic-level matching between order parameters and status data blocks, the problem of insufficient flexibility in traditional rule matching is solved, and fuzzy matching and implicit relationship mining are supported.

[0133] The knowledge graph construction includes: entity definition: including "order parameters" (specifications, wire type, measurement parameters), "status fields" (second field, third field), and "matching rules" (compatibility relationship, derived relationship); relationship modeling: such as "specifications → includes → wire type" and "measurement parameter requirements → associated → measurement parameter verification status", with relationship weights trained using historical order data; the graph is stored using the Neo4j graph database, and node attributes include text descriptions and vector representations (generated using the TransE algorithm).

[0134] The intelligent matching process includes: Order parsing: using NLP technology to convert customer order text (such as "high voltage three-phase multi-function energy meter") into graph node query statements; Graph neural network inference: inputting the vector representation of the state data block, calculating the semantic similarity between the order node and the state node through GNN (a threshold ≥ 0.8 is used to determine a match); Flexible matching: supporting parameter-derived matching (such as order requirements "RS485 communication", state data "dual-mode communication (RS485+LoRa)" is used to determine compatibility through relational inference), and outputting the matching confidence score for manual review.

[0135] In some embodiments, by combining YOLO object detection with reinforcement learning (DQN), intelligent scheduling and task allocation of detection equipment can be achieved, solving the efficiency bottleneck of traditional fixed processes and dynamically optimizing the detection path.

[0136] The visual recognition module includes: Asset number recognition: An industrial camera is installed at the entrance of the inspection equipment to identify the barcode / RFID tag on the surface of the electricity meter in real time using the YOLOv8 model (recognition accuracy ≥99.5%), and output a unique identification mark; State feature extraction: The appearance status of the electricity meter is identified simultaneously (such as the installation angle of the wiring terminals), and a pre-trained ResNet model is used to determine whether it meets the pre-inspection preparation status.

[0137] The reinforcement learning scheduling system includes: a state space defining state parameters such as the load of the testing equipment (idle / busy), the priority of electricity meter testing (based on order delivery date), and historical testing time; an action space defining actions such as selecting testing equipment allocation and adjusting the order of testing items; a reward function training the DQN model through experience replay with the goal of maximizing testing throughput and minimizing equipment idle time; and real-time scheduling querying historical testing data based on electricity meter identification, automatically allocating the optimal testing equipment (e.g., prioritizing equipment with a current load of <50% and proficient in testing that model) and generating dynamic testing work orders.

[0138] In some embodiments, a detection status prediction model is constructed using a Long Short-Term Memory (LSTM) network to predict potential anomalies in the current process based on historical detection data, thereby achieving preventative quality control.

[0139] Time series data modeling includes: Input features: extracting historical detection data of the same type of electricity meter (such as power consumption data, voltage fluctuation value, communication response time and other time series features of the first 5 stages); Label definition: detection result of the current stage (qualified / abnormal), and the abnormal type is used as a multi-class label; Model structure: two LSTM layers (128 neurons each) + fully connected layer, using Adam optimizer, and the loss function is cross-entropy.

[0140] The pre-diagnosis application process includes: Real-time prediction: When the energy meter enters the detection stage, the model predicts the detection result of the current stage based on the status data of the completed stages (such as the voltage value sequence of key points in the first 3 stages); Anomaly pre-triggering: If the predicted anomaly probability is >70%, the pre-detection mechanism is automatically triggered (such as increasing the detection sample size and adjusting the detection accuracy), and the "pre-diagnosis anomaly" status is marked in the status data block (a special flag is reserved); Model update: After each detection is completed, the latest data is added to the training set, and the prediction accuracy is continuously optimized through online learning.

[0141] In some embodiments, by constructing a digital twin model of electricity meter production and testing, and combining discrete event simulation (DES) with Bayesian networks, virtual simulation and risk prediction of state data blocks can be achieved.

[0142] The construction of digital twins includes: physical entity mapping: creating a virtual twin for each electricity meter and synchronizing its status data blocks, detection history, hardware parameters and other information; simulation model: building a detection process simulation environment based on AnyLogic and defining parameters such as time consumption probability and equipment failure rate for each stage; Bayesian network: modeling the dependencies between stages (such as the probability of an anomaly in the "metering parameter writing" stage affecting the "outbound parameter verification" stage).

[0143] State simulation and optimization include: virtual flow simulation based on the current state data block to simulate and predict the possible states of subsequent stages (e.g., predicting the probability of "measuring parameters passing verification" to be 85%); risk warning: if the simulation finds that the abnormal probability of a certain stage is greater than the threshold (e.g., 60%), the detection strategy is automatically adjusted (e.g., pre-allocating high-precision detection equipment); and the optimal detection path suggestion is generated and written into the "optimization strategy field" of the state data block (e.g., dynamically inserting parallel detection stages when the predicted "communication function detection" takes a long time).

[0144] In some embodiments, associating the cause of non-compliance and re-entering the normal testing process after repair includes: when uploading the test data in a package, binding the cause of non-compliance as additional information with the exception code and storing it in the database; repairing the electricity meter according to the cause of non-compliance recorded in the database, and clearing the exception code by writing the status to the host computer after the repair is completed; after clearing the exception code, the electricity meter re-enters the testing process from the previous stage of the abnormal stage, or directly enters the original abnormal stage for re-inspection, until the status word continues to flow after the test is qualified.

[0145] In some embodiments, the main objective of this patent is to provide a method for tracking the entire process of electricity meter detection data based on status word identifiers. To achieve the above objective, the technical solution of this patent comprises three parts: an electricity meter, an internet platform, and a status writing host computer.

[0146] (1) Electricity Meter: The electricity meter has a unique ID. The ID contains the following information: product code, year, month, date, and sequence number. The electricity meter has a status data block that can be encrypted and edited to detect the status. The status data block is divided into N fields; Field 1 marks the status of the semi-finished electricity meter: appearance status, metering function, communication function, key point voltage, peripheral status, power consumption, etc. Field 2 marks the meter information: meter specifications and model, wiring status, power supply method, software version, hardware version, etc. Field 3 marks the status of the finished electricity meter: metering parameter writing status, metering parameter verification status, outbound parameter writing status, outbound parameter verification status.

[0147] (2) Internet Platform: The unique identification ID of the electricity meter is entered into the Internet platform. At the same time as each stage records the meter status, this status is uploaded to the Internet platform for backup. Before each stage records the meter status, it first compares the status on the Internet platform with the status stored internally in the meter. Only if the comparison matches can the status of that stage be written. Simultaneously, market order parameters are entered into the Internet platform. When the electricity meter is issued, the Internet platform matches the market order parameters with the unique identification ID of the electricity meter and the electricity meter status data block, and issues qualified electricity meters to the warehouse.

[0148] (3) Write status to host computer: Write the detection status of each link into the meter storage according to the specified protocol.

[0149] like Figure 2As shown, in the semi-finished product ID entry stage, the unique ID of the electricity meter is entered into the system; in the various levels of test data entry stage, the status word is uploaded to the server via the network according to the test results; in the order information entry stage, customer requirement parameters are entered into the system; in the outbound parameter issuance stage, on the one hand, the customer's required parameters are compared with the read meter parameters to verify whether the meter type and parameters meet the customer's requirements; on the other hand, the status data block of the ID in the platform is compared with the meter data block, and the outbound process can only be completed if the information is consistent. Figure 3 As shown, the "data acquisition + status writing" process enables real-time binding of data and status words at each stage, avoiding data gaps. Specifically, this includes:

[0150] 1. Data Acquisition (Core Testing Step): Testing equipment (such as error calibrators and withstand voltage testers) connects to the tracking system via an IoT interface. When the electricity meter enters a certain stage: the equipment automatically reads the electricity meter asset number (via RFID or barcode scanning); the system generates a status word based on the current stage and sends it to the testing equipment; after the equipment completes the testing, it automatically packages the testing data (such as error value and equipment number) and the status word and uploads them to the database.

[0151] 2. Status word change rules: The status word can only be updated to the next stage after the data acquisition of the current stage is completed and the verification is passed (e.g., after the "error detection" data is qualified, a certain bit of the status word changes from "00" to "01"); if the detection of a certain stage fails (e.g., the withstand voltage test fails), the status word will temporarily change to "abnormal code" (e.g., "99") and the reason for failure will be associated. After maintenance, the normal process will be resumed.

[0152] The DC meter's detection status data block is shown in the table below:

[0153]

[0154] The status word is defined as follows: Bytes 1-2: Semi-finished product detection status; Byte 3: Meter information; Byte 4: Finished product detection status. The specific bit information is shown in the table below:

[0155]

[0156] The DC meter identification ID is shown in the table below:

[0157]

[0158] The DC meter identification ID is defined as follows: 1~6 digits: product code; 7~8 digits: year; 9~10 digits: month; 11~12 digits: date; 13~16 digits: serial number. Example: 00DZ102506090001: 4P first generation DC power supply three-wire system.

[0159] Please see Figure 4 As shown, Figure 4 This is a schematic diagram of the structure of a power meter detection data end-to-end tracking device 200 based on status word identifiers provided in this application embodiment. This power meter detection data end-to-end tracking device 200 based on status word identifiers is used to execute the steps of the power meter detection data end-to-end tracking method based on status word identifiers shown in the above embodiments. The power meter detection data end-to-end tracking device 200 based on status word identifiers can be a single server or a server cluster, or it can be a terminal, such as a handheld terminal, a laptop computer, a wearable device, or a robot.

[0160] like Figure 4 As shown, the energy meter detection data full-process tracking device 200 based on status word identifiers includes:

[0161] The identification setting unit 201 is used to set a unique identification for the electricity meter. The identification includes product code, year, month, date and sequence number information. It also sets an encrypted and editable status data block in the electricity meter. The status data block is divided into a first field, a second field and a third field. The first field is used to mark the status of the semi-finished electricity meter, the second field is used to mark the meter information, and the third field is used to mark the status of the finished electricity meter.

[0162] The identification input unit 202 is used to input the unique identification of the electricity meter into the Internet platform. When writing the status of the electricity meter, the status of the current stage is synchronously uploaded to the Internet platform for backup. Market order parameters are input into the Internet platform. When the electricity meter is issued, the market order parameters are matched with the unique identification of the electricity meter and the status data block of the electricity meter through the Internet platform. If the match is qualified, the electricity meter is allowed to be issued. According to the prescribed protocol, the detection status of each stage is written into the status data block of the electricity meter for storage.

[0163] The real-time binding unit 203 is used for the detection equipment to connect with the tracking system through the Internet of Things interface. When the electricity meter enters the detection stage, the detection equipment automatically reads the asset number of the electricity meter, generates the corresponding status word according to the current stage and sends it to the detection equipment. After the detection equipment completes the detection, it packages the detection data and status word and uploads them to the database to realize the real-time binding of detection data and status word.

[0164] The status verification unit 204 is used to set the status word change rules. If the current stage of detection data collection is completed and the verification is passed, the status word is updated to the corresponding status of the next stage. If the detection fails, the status word is temporarily changed to an exception code and associated with the reason for failure. After maintenance, the normal detection process will be restarted.

[0165] It should be noted that those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described full-process tracking device for electricity meter detection data based on status word identifiers and each module can be referred to the corresponding process in the embodiments of the full-process tracking method for electricity meter detection data based on status word identifiers described above, and will not be repeated here.

[0166] The aforementioned method for tracking the entire process of electricity meter detection data based on status word identifiers can be implemented as a computer program, which can be used in various ways, such as... Figure 4 It runs on the device shown.

[0167] Please see Figure 5 , Figure 5 This is a schematic block diagram of the structure of a computer device provided in an embodiment of this application. The computer device includes a processor, a memory, and a network interface connected via a device bus, wherein the memory may include a storage medium and internal memory.

[0168] The storage medium can store operating devices and computer programs. The computer program includes program instructions that, when executed, cause the processor to perform any method for tracking the entire process of energy meter detection data based on status word identifiers.

[0169] The processor provides computing and control capabilities, supporting the operation of the entire computer device.

[0170] The internal memory provides an environment for the execution of computer programs in non-volatile storage media. When the computer program is executed by the processor, it enables the processor to execute any method for tracking the entire process of electricity meter detection data based on status word identifiers.

[0171] This network interface is used for network communication, such as sending assigned tasks. Those skilled in the art will understand that... Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the terminal to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0172] It should be understood that the processor can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among these, a general-purpose processor can be a microprocessor or any conventional processor.

[0173] In one embodiment, the processor is configured to run a computer program stored in memory to perform the following steps:

[0174] A unique identifier is set for each electricity meter. The identifier includes product code, year, month, date and sequence number information. An encrypted and editable status data block is set in the electricity meter. The status data block is divided into a first field, a second field and a third field. The first field is used to mark the status of the semi-finished electricity meter, the second field is used to mark the meter information, and the third field is used to mark the status of the finished electricity meter.

[0175] The unique identifier of the electricity meter is entered into the internet platform. When writing the status of the electricity meter, the status of the current stage is synchronously uploaded to the internet platform for backup. Market order parameters are entered into the internet platform. When the electricity meter is issued, the market order parameters are matched with the unique identifier of the electricity meter and the status data block of the electricity meter through the internet platform. If the match is successful, the electricity meter is allowed to be issued. According to the prescribed protocol, the detection status of each stage is written into the status data block of the electricity meter for storage.

[0176] The testing equipment connects to the tracking system via an IoT interface. When the electricity meter enters the testing phase, the testing equipment automatically reads the electricity meter's asset number, generates the corresponding status word based on the current phase, and sends it to the testing equipment. After the testing equipment completes the testing, it packages the testing data and status word and uploads them to the database, realizing real-time binding between the testing data and status word.

[0177] Set status word change rules: if the current stage of the test data collection is completed and the verification is passed, the status word is updated to the corresponding status of the next stage; if the test fails, the status word is temporarily changed to an exception code and associated with the reason for the failure, and the normal test process is resumed after maintenance.

[0178] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to implement the steps of the method for tracking the entire process of electricity meter detection data based on status word identifiers as described in the first aspect above.

[0179] The computer-readable storage medium may be an internal storage unit of the computer device described in the foregoing embodiments, such as the hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, SmartMedia Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the computer device.

[0180] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for tracking the entire process of electricity meter detection data based on status word identifiers, characterized in that, include: A unique identifier is assigned to each electricity meter, including product code, year, month, date, and sequence number. An encrypted and editable status data block is also set within the electricity meter. This status data block is divided into a first field, a second field, and a third field. The first field marks the status of the semi-finished electricity meter, the second field marks meter information, and the third field marks the status of the finished electricity meter. Setting the encrypted and editable status data block involves: dividing the electricity meter's storage module into an independent data area as the status data block; the status data block uses an encryption algorithm for access control, allowing only authorized status-writing host computers to edit it. The first field specifically marks the semi-finished electricity meter's appearance status, metering function status, communication function status, key point voltage values, peripheral connection status, and overall power consumption data. The second field specifically marks the electricity meter's specifications, wiring type, power supply method, software version number, and hardware version number. The third field specifically marks the finished electricity meter's metering parameter writing completion status, metering parameter verification pass status, outbound parameter writing completion status, and outbound parameter verification pass status. The unique identifier of the electricity meter is entered into the internet platform. When writing the status of the electricity meter, the status of the current stage is synchronously uploaded to the internet platform for backup. Market order parameters are entered into the internet platform. When the electricity meter is issued, the market order parameters are matched with the unique identifier of the electricity meter and the status data block of the electricity meter through the internet platform. If the match is successful, the electricity meter is allowed to be issued. According to the prescribed protocol, the detection status of each stage is written into the status data block of the electricity meter for storage. The testing equipment connects to the tracking system via an IoT interface. When the electricity meter enters the testing phase, the testing equipment automatically reads the electricity meter's asset number, generates the corresponding status word based on the current phase, and sends it to the testing equipment. After the testing equipment completes the testing, it packages the testing data and status word and uploads them to the database, realizing real-time binding between the testing data and status word. Set status word change rules: if the current stage of the test data collection is completed and the verification is passed, the status word is updated to the corresponding status of the next stage; if the test fails, the status word is temporarily changed to an exception code and associated with the reason for the failure, and the normal test process is resumed after maintenance.

2. The method according to claim 1, characterized in that, The process of recording the unique identifier of the electricity meter into the internet platform, and simultaneously uploading the current status to the internet platform for backup when writing the status of the electricity meter, includes: In the semi-finished product ID entry stage corresponding to the unique identifier, the unique identifier of the energy meter and the initial status data block are synchronously entered into the database of the Internet platform through the write status host computer. Before each stage writes the status of the electricity meter, the status writing host computer first sends a status query request to the Internet platform to obtain the current status of the electricity meter stored in the platform, and compares it field by field with the status data block read in real time inside the electricity meter. If the comparison results match, the current state write operation is executed, and the updated state data block is uploaded to the Internet platform for backup storage in real time after the write is completed.

3. The method according to claim 1, characterized in that, The process of matching market order parameters with the unique identifier of the electricity meter and the status data block of the electricity meter through an internet platform includes: During the order information entry process, the customer's required order parameters are entered into the internet platform; the order parameters include meter specifications and model, metering parameter requirements, and wiring type. When an electricity meter is issued from the warehouse, the Internet platform automatically retrieves the status data block corresponding to the unique identifier of the electricity meter, extracts the meter specifications and model, wiring status from the second field, and the metering parameter verification status and outbound parameter writing status from the third field. The extracted parameters are compared with the order parameters one by one. If the meter specifications and models match, the metering parameter verification status is passed, and the outbound parameter writing status is completed, then the matching is deemed qualified.

4. The method according to claim 1, characterized in that, The process of writing the detection status of each stage into the status data block of the electricity meter for storage, according to the prescribed protocol, includes: The host computer in write mode is pre-configured with a specified protocol for communication with the electricity meter, which includes data format, verification rules and write permission verification mechanism; In the production parameter testing, recalibration parameter testing, and outbound parameter detection stages, the status writing host computer generates status information for the corresponding fields based on the detection results. The generated status information is encoded according to the prescribed protocol and written into the corresponding field of the status data block of the electricity meter through wired or wireless communication, and the storage verification mechanism of the electricity meter is triggered to ensure the integrity of the written data.

5. The method according to claim 1, characterized in that, The detection equipment connects to the tracking system via an IoT interface. When the electricity meter enters the detection phase, the detection equipment automatically reads the electricity meter's asset number, including: The testing equipment integrates an RFID reading module or a barcode scanning module, and the asset number is attached to the surface of the electricity meter in the form of an RFID tag or barcode; When the electricity meter enters the identification range of the detection equipment, the detection equipment sends a reading command to the tracking system through the Internet of Things interface, automatically capturing and parsing the asset number information. The tracking system generates a work order for the current stage of the inspection task by associating the unique identifier of the electricity meter with its asset number and historical status data.

6. The method according to claim 1, characterized in that, The process involves generating a corresponding status word based on the current stage and sending it to the detection device. After the detection device completes the detection, it packages the detection data and the status word and uploads them to the database, achieving real-time binding between the detection data and the status word. This includes: The tracking system generates a unique status word prefix based on the current detection stage. The status word includes a stage identifier, a timestamp, and a check bit. The status word is sent to the testing equipment, which then automatically collects the testing data after completing the test. The detection data and status words are packaged according to a preset data structure and uploaded to the tracking system's database through an IoT interface to form a detection record with a status identifier.

7. The method according to claim 1, characterized in that, If the current stage's detection data collection is completed and verification passes, the status word is updated to the status corresponding to the next stage, including: The tracking system verifies the detection data uploaded by the detection equipment. If the verification passes, it generates the target status of the next stage according to the preset stage flow rules. The target state is specifically manifested as a change in the state bit of the corresponding field in the state data block. After the error detection is qualified, the measurement parameter in the third field is checked and the state is updated. The target state is written to the status data block of the electricity meter by writing to the status host computer, and the record in the Internet platform is updated synchronously.

8. The method according to claim 1, characterized in that, If the detection fails, the status word will be temporarily changed to an error code, including: When the test data fails to be verified, the tracking system generates an exception code corresponding to the non-conforming step. Write the exception code into the corresponding field of the electricity meter status data block, mark the current status of the electricity meter as abnormal in the Internet platform, and record the time point when the test failed.

9. The method according to claim 1, characterized in that, The reasons for the aforementioned non-compliance, after repair and re-entry into the normal testing process, include: When uploading the test data in a package, the reasons for non-compliance are bound to the exception code as additional information and stored in the database; The electricity meter is inspected and repaired according to the reasons for non-compliance recorded in the database. After the inspection and repair are completed, the abnormal code is cleared by writing the status to the host computer. After the abnormal code is cleared, the electricity meter re-enters the testing process from the previous stage of the abnormal process, or directly enters the original abnormal stage for re-inspection, until the test is passed and the status word continues to flow.

Images