Electric energy meter frozen data storage and reading method and electric energy meter

Abstract

The present disclosure relates to a power meter frozen data storage method, a reading method and a power meter. The storage method comprises, in response to a freezing instruction, generating an entry identified by a freezing time, the entry recording a freezing type and freezing data at the freezing time, the freezing instruction containing freezing tasks of multiple freezing types; the freezing data storing frozen sub-data of one or more associated object attributes; the frozen sub-data storing a data validity judgment symbol and an associated object attribute data corresponding to the data validity judgment symbol; and the data validity judgment symbol containing one or more freezing type state words. The embodiment of the present disclosure stores the freezing data of different freezing types occurring at the same time once, without repeatedly storing the same data, greatly reducing the storage space occupation, and also ensuring the consistency of the data storage time of different freezing types.

Description

Technical Field

[0001] This disclosure relates to the field of electricity meter technology, and more specifically, to an electricity meter frozen data storage and reading method and an electricity meter. Background Technology

[0002] Freezing is an important data recording function of electricity meters. When a freeze occurs during operation, the electricity meter records the frozen data. The specific data to be recorded depends on the associated object attributes (e.g., voltage, current, active power, reactive power, etc.) and freeze type (e.g., daily freeze, hourly freeze, minute freeze, monthly freeze, quarterly freeze, time zone table freeze, day / time period table switching freeze, tiered freeze, etc.) configured by the user for the freeze. The meter also stores the specific values ​​of these associated object attributes at the time of the freeze.

[0003] Frozen data at the same time are usually highly correlated, so they are typically stored together and then retrieved in a unified manner. This increases data utilization but reduces storage space and shortens data processing time. Summary of the Invention

[0004] The embodiments of this disclosure provide a method for storing and reading frozen data in an electricity meter, as well as an electricity meter itself.

[0005] In a first aspect of this disclosure, a method for freezing data storage in an electricity meter is provided. The method includes generating an entry identified by a freeze time in response to a freeze command. The entry records the freeze type and frozen data at that freeze time. The freeze command includes freeze tasks for multiple freeze types. The frozen data storage includes frozen sub-data of one or more associated object attributes. The frozen sub-data storage includes a data validity check and associated object attribute data corresponding to the data validity check. The data validity check includes one or more freeze type status words.

[0006] In some embodiments, the process of freezing data records in an entry includes: obtaining a total associated object attribute table; and freezing sub-data in the entry according to all associated object attribute records in the total associated object attribute table, wherein associated object attribute data that has not been frozen is null and the corresponding data validity check is set to zero.

[0007] In some embodiments, the freeze type includes at least minute freeze, hour freeze, and day freeze.

[0008] In some embodiments, the process of generating a freeze type includes: generating a freeze type based on the configuration parameters of the freeze task, wherein the configuration parameters are used to indicate that the relevant positions in the fields of the freeze type are 0 or 1.

[0009] In some embodiments, the process of generating the data validity qualifier includes: forming a data validity qualifier containing the freeze type status word based on the freeze type status word of the freeze task.

[0010] In a second aspect of this disclosure, a method for reading frozen data from an electricity meter is provided. The method includes, in response to a frozen data read instruction, retrieving an entry at the frozen time, using the read frozen time as an index. Each entry records the frozen type and frozen data at that frozen time. The frozen data read instruction includes the read frozen time and a frozen type status word. Furthermore, the method also includes, in response to the presence of multiple frozen types for an entry, sequentially traversing frozen sub-data corresponding to different associated object attributes in the frozen data. Each frozen sub-data store contains a data validity check and associated object attribute data corresponding to the data validity check. The data validity check contains one or more frozen type status words.

[0011] The process of traversing each frozen sub-data includes: responding to the data validity check in the frozen sub-data containing the read frozen type status word, and reading the frozen sub-data corresponding to the data validity check.

[0012] In some embodiments, the process of traversing each frozen sub-data further includes: traversing the next frozen sub-data in response to the data validity check in the frozen sub-data not containing the read frozen type status word.

[0013] In some embodiments, in response to an entry having multiple freeze types, sequentially traversing the frozen sub-data corresponding to different associated object attributes in the frozen data includes: in response to an entry having multiple BIT positions for the freeze type, sequentially traversing the frozen sub-data corresponding to different associated object attributes in the frozen data according to the order of all associated object attributes in the total associated object attribute table.

[0014] In some embodiments, the method further includes reading frozen data under an entry in response to the entry's freeze type having one bit.

[0015] In a third aspect of this disclosure, an electricity meter is provided, the electricity meter including a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program, when executed by the processor, implementing the electricity meter frozen data storage method as described in the first aspect, or implementing the electricity meter frozen data reading method as described in the second aspect.

[0016] It should be understood that the description in the Summary of the Invention section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0017] The above and other objects, features, and advantages of embodiments of the present disclosure will become readily apparent from the following detailed description taken in conjunction with the accompanying drawings. Several embodiments of the present disclosure are illustrated in the drawings by way of example and not limitation.

[0018] Figure 1 A schematic diagram of an example environment in which some embodiments of this disclosure may be implemented is shown;

[0019] Figure 2 A flowchart illustrating a method for freezing data storage in an electricity meter according to some embodiments of this disclosure is shown;

[0020] Figure 3a An example diagram of a frozen data storage structure for an energy meter according to some embodiments of the present disclosure is shown;

[0021] Figure 3b An example diagram is shown of a data storage structure for multiple associated object attributes in frozen data of an electricity meter according to some embodiments of the present disclosure;

[0022] Figure 4 An example diagram is shown illustrating the process of freezing data storage in an electricity meter according to some embodiments of the present disclosure;

[0023] Figure 5 A flowchart of a method for reading frozen data from an energy meter according to some embodiments of the present disclosure is shown;

[0024] Figure 6 An example diagram is shown illustrating the process of freezing data reading from an electricity meter according to some embodiments of this disclosure.

[0025] In the various figures, the same or corresponding reference numerals indicate the same or corresponding parts. Detailed Implementation

[0026] Preferred embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art.

[0027] The term “comprising” and its variations as used herein signify open inclusion, i.e., “including but not limited to”. Unless otherwise stated, the term “or” means “and / or”. The term “based on” means “at least partially based on”. The terms “one example embodiment” and “one embodiment” mean “at least one example embodiment”. The term “another embodiment” means “at least one additional embodiment”. Other explicit and implicit definitions may also be included below.

[0028] As mentioned earlier, when a freeze occurs during operation, the electricity meter needs to record the freeze data. Freeze data from the same time period is usually highly correlated, so it is generally stored simultaneously and then retrieved uniformly. This increases data utilization but reduces storage space usage and shortens data processing time.

[0029] In some related technologies, a set of mask numbers is generated based on the associated object attributes configured for the frozen records of an energy meter, and these mask numbers are stored in correspondence with the associated object attributes. A mask is then generated based on the mask numbers, and this mask is stored in correspondence with the associated object data. This method eliminates the need to store the corresponding associated object descriptor (generally more than 4 bytes) for each frozen record; instead, the mask number and mask are used to correspond to the associated object attributes and their data, reducing the space occupied by storing the associated object descriptor for each frozen record. However, this technology requires a new encoding method, and it needs to be designed based on the associated object attributes configured within the energy meter. Since the associated object attributes configured for different models of energy meters are not entirely the same, re-encoding is required. Furthermore, during freezing, multiple freezing types may be executed simultaneously, and each type of freezing task typically allocates independent memory space to store its data. Because the same associated object attribute has the same frozen data in different freezing types at the same time, the same data will be repeatedly stored in different memory spaces, still consuming a significant amount of memory.

[0030] To address this, according to embodiments of this disclosure, a method for storing frozen data of an electricity meter is provided. This method stores frozen data of multiple freezing types in entries identified by freezing time. The frozen data includes frozen sub-data of one or more associated object attributes, each frozen sub-data consisting of a data validity check and associated object attribute data. When a certain associated object attribute data is frozen under multiple freezing types, multiple freezing type status words are concatenated to form a data validity check. The associated object attribute data is stored corresponding to the data validity check, enabling the same associated object attribute data under different freezing types at the same freezing time to be stored only once.

[0031] This approach utilizes a single data validity check token formed from freeze type status words across multiple freeze types, and stores one associated object attribute data for each token. This significantly reduces the storage space required for multiple identical associated object attribute data under different freeze types. Furthermore, storing the same associated object attribute data across different freeze types that freeze simultaneously ensures consistency in data storage for associated object attributes across different freeze types at the same freeze time, resolving the issue of inconsistent instantaneous values ​​of the same associated object attribute data under different freeze types due to differences in sampling time during freeze tasks. Moreover, subsequent data collection from the electricity meter only requires a single scan to obtain associated object attribute data for multiple freeze types, resulting in high data processing efficiency.

[0032] Figure 1 A schematic diagram of an example environment 100 in which some embodiments of this disclosure may be implemented is shown. For example... Figure 1 As shown, environment 100 includes an electricity meter master station 102, which is typically the core system in a power system used for centralized management and control of electricity meter data. It generally runs on a server or computer cluster, requiring powerful computing and storage capabilities to handle large amounts of data and concurrent tasks. Environment 100 also includes a concentrator 104, which communicates upstream with the electricity meter master station 102, typically via 2G / 3G / 4G / 5G. Environment 100 also includes multiple electricity meters 106-1, 106-2, ..., 106-n. These meters are often located at user terminals, and downstream communication occurs between the concentrator 104 and the meters, typically via G3-PLC (third-generation power line communication) or BPLC (Broadband Power Line Communication). The electricity meter master station 102 can collect data (including real-time data, historical data, frozen data, etc.) from the electricity meter and concentrator 104 through the communication network. It can also process and analyze the collected data and store the processed data in the database for subsequent query and analysis.

[0033] like Figure 1 As shown, the electricity meter master station 102 configures a meter list on the system side according to user needs. This meter list includes electricity meter information (such as meter number, model, communication address, etc.) and the meter tasks corresponding to the electricity meter information. Meter tasks include task numbers and the corresponding data acquisition tasks. Data acquisition tasks are configured according to user acquisition requirements and may include tasks for acquiring instantaneous data (such as configuring acquisition time, acquisition object, etc.), freeze tasks (such as configuring freeze type, freeze object, etc.), and tasks for acquiring historical data. Figure 1As shown, the electricity meter master station 102 sends the metering task to the concentrator 104. After receiving the metering task, the concentrator 104 returns the setting result. If the task is sent to the concentrator 104 and stored, it returns success; otherwise, it returns failure. The electricity meter master station 102 needs to send the task to the concentrator 104 again until success. Afterward, the concentrator 104 sends the relevant metering task to the corresponding electricity meter based on the electricity meter information in the metering task. For example, metering task 1 belonging to electricity meter 1 is sent by the concentrator 104 to electricity meter 1, ..., metering task n belonging to electricity meter n is sent by the concentrator 104 to electricity meter n. After electricity meters 106-1, 106-2, ..., 106-n successfully configure their respective metering tasks, they periodically respond to each task instruction and execute the relevant task operations. Each electricity meter sends the collected, frozen, and stored data 1, ..., n after task execution to the electricity meter master station 102 via the concentrator 104.

[0034] The storage of frozen data in this embodiment is performed on each terminal energy meter. Taking energy meter 1 as an example, there are three freezing tasks in energy meter 1, corresponding to three freezing types (daily freeze, hourly freeze, and minute freeze). The freezing tasks are configured when the following calculation task 1 is sent to the meter. The RTC timer interrupt in the energy meter triggers the freezing tasks at a certain point. For example, at time T1, freezing tasks 1, 2, and 3 are triggered simultaneously. At time T2, only freezing task 1 is triggered. At time Ti, freezing tasks 1, 2, and 3 are triggered simultaneously. During freezing, in response to the freeze command, an entry is generated with the freeze time as the record identifier. This entry records the freeze type and frozen data under that freeze time. For example, time T1 in the table is used as the record identifier for the first entry, and this entry stores the freeze type and frozen data under the freeze time T1. The freeze command includes freezing tasks of multiple freeze types, and the freezing tasks need to freeze m frozen objects (i.e., the associated object attribute data referred to in the figure and this document). Accordingly, the freeze type field under this entry (e.g., "Type 1" in the diagram) is formed based on the configuration parameters of the freeze task. These configuration parameters indicate whether the relevant bits in the freeze type field are set to "0" or "1". The freeze type corresponding to each bit is pre-configured by the system. For example, the initial field of the freeze type is "0000". When the configuration parameters of the freeze task indicate that "Daily Freeze", "Hourly Freeze", and "Minute Freeze" are enabled, the field of "Type 1" is set to "0111"; when the configuration parameters of the freeze task indicate that "Daily Freeze" is enabled and "Hourly Freeze" and "Minute Freeze" are disabled, the field of "Type" is set to "0001". The frozen data under this entry includes multiple frozen sub-data. Each frozen sub-data store contains associated object attribute data and a data validity check. Based on the freeze type status word of the freeze task, a data validity check containing the freeze type status word is formed. In some implementations, if an associated object's attribute data involves multiple freeze types, there are multiple freeze type status words, which are concatenated to form a data validity check. If an associated object's attribute data involves one freeze type, the freeze type status word of that freeze type constitutes the data validity check. In this way, multiple entries from time T1 to Ti can be recorded. When reading a frozen record, the freeze time can be used as an index to perform a search to retrieve the entry at the desired freeze time.

[0035] In this way, data for the same associated object attributes frozen under different freeze types at the same freeze time is stored only once, and it is stored one-to-one with the data validity criterion composed of multiple freeze type keywords. This not only reduces the amount of data stored, but also ensures the numerical consistency of associated object attribute data under different freeze types at the same freeze time. Furthermore, this method is simple and adaptable to various types of electricity meters.

[0036] Figure 2A flowchart of a method 200 for freezing data storage in an electricity meter, according to some embodiments of this disclosure, is shown. For example... Figure 2 As shown in block 202, method 200 can generate entries with freeze time as record identifiers in response to a freeze command. Each entry records the freeze type and frozen data at that freeze time. The freeze command includes freeze tasks for multiple freeze types. The frozen data stores frozen sub-data of one or more associated object attributes; each frozen sub-data store includes a data validity check and associated object attribute data corresponding to the data validity check; the data validity check includes one or more freeze type status words. In some implementations, in response to a freeze task containing multiple freeze types in the freeze command, a total associated object attribute table is obtained. The total associated object attribute table stores all associated object attributes configured during the electricity meter's factory initialization and the data offset positions of each associated object attribute. Frozen sub-data is recorded in each entry based on all associated object attributes in the total associated object attribute table. That is, when there are 10 associated object attributes in the total associated object attribute table, and 6 associated object attributes are frozen, then 10 associated object attributes need to be stored and recorded. Unfrozen associated object attribute data is recorded as null values, and frozen associated object attribute data is stored as actual frozen data.

[0037] In some implementations, the entry also stores the number of frozen entries, which can record the number of entries under various freezing types, as well as the number of entries under all freezing types. Figure 3a An example diagram of a frozen data storage structure for an electricity meter according to some embodiments of the present disclosure is shown. Figure 3a The entries are stored sequentially according to freeze time, freeze type, number of frozen entries, and the first to mth items. Each data item corresponds to an associated object attribute, which can be current, voltage, power, etc. Each data item contains a data validity checker and its corresponding frozen sub-data.

[0038] Figure 3b An example diagram is shown of a data storage structure for multiple associated object attributes in electricity meter frozen data according to some embodiments of this disclosure. For example, the total associated object attribute table has 10 associated object attributes. A freeze at the current time (minute, hour, and day) involves 6 associated object attributes, specifically minute freeze (related to associated object attributes 1, 2, and 3), hour freeze (related to associated object attributes 4 and 5), and day freeze (related to associated object attributes 1, 2, 4, and 6). Therefore, associated object attributes 7, 8, 9, and 10 have not been frozen. Figure 3b In the context of related object attributes 7, 8, 9, and 10, the data validity check operator for the seventh, eighth, ninth, and tenth items is set to zero, and the corresponding related object attribute data is null. Furthermore, it is known that related object attributes 1 and 2 both involve minute-based and day-based freezes. Figure 3bIn the associated object attributes 1 and 2, the data validity check operators for the first and second data items are both based on the freeze type keywords for minute-based freezes and day-based freezes. Therefore, the data validity check operators for the first and second data items are the same. For example, if the freeze type keyword for minute-based freezes is BIT1 and the freeze type keyword for day-based freezes is BIT3, the data validity check operator is BIT1BIT3. In this method, one instance of each freeze type is stored in both the first and second data items. Similarly, associated object attribute 4 involves hourly and daily freezes. Figure 3b The data validity check for the fourth item corresponding to attribute 4 of the associated object is formed based on the freeze type keywords for hourly and daily freezes. For example, if the freeze type keyword for hourly freezes is BIT2, the data validity check is BIT2BIT3. The fourth item also stores one frozen data item corresponding to this data validity check. As for attributes 3, 5, and 6 of the associated object, each is frozen according to a different freeze type, and their data validity check is the freeze type keyword for that type. In this way, one entry can save three duplicate data storage locations. As time progresses, multiple entries under different freeze times will be recorded, freeing up storage space for a large amount of duplicate data across tens of thousands of entries, significantly reducing storage space usage.

[0039] Figure 4 An example diagram is shown of an electricity meter frozen data storage process 400 according to some embodiments of the present disclosure. For example... Figure 4 As shown, process 400 begins after the electricity meter's RTC is triggered. The electricity meter responds to the freeze command and executes the freeze. In box 402, process 400 determines whether there are multiple freeze types in the freeze command. If not, and if there is only one freeze type, then box 404 is executed to freeze the data according to the original frozen associated object attribute table. For example, for monthly freezes, the first month's frozen data stores the first month's freeze time, the "monthly freeze" freeze type, and the frozen data (including one or more associated object attribute data). The second month's freeze time, if only monthly freezes occur, then the second month's frozen data is stored in the same format as the first month's frozen data. If it is determined that there are multiple freeze types in the freeze command, then box 406 is entered to obtain all associated object attributes from the total associated object attribute table. Process 400 can determine in box 408 whether each associated object attribute is the target data for freezing. If not, then according to box 410, the frozen sub-data is stored, the data validity check is set to zero, and the associated object attribute data is set to null (e.g., ...). Figure 3b (The seventh to tenth data items shown). If so, then store the frozen sub-data according to box 412 to form a data validity check character containing a frozen type status word (e.g., Figure 3b The third, fifth, and sixth data items shown), or data valid judges that form multiple frozen status words (e.g. Figure 3b The first, second, and fourth items of data shown are used to record the actual frozen data as associated object attribute data and store them according to the data validity judgment method. Following the above method, multiple frozen sub-data are stored together sequentially to obtain the frozen data responding to the current freeze command, which is stored in box 414. Finally, the frozen data and its related freeze types and number of frozen records are organized according to the freeze time as the record identifier. Figure 3a Store in the format shown.

[0040] Figure 5 A flowchart of a method 500 for reading frozen data from an electricity meter according to some embodiments of the present disclosure is shown. This method 500 is performed by the electricity meter in response to a frozen data reading command sent by the electricity meter master station via a concentrator. Figure 5 As shown in block 502, method 500 can respond to a frozen data read instruction by retrieving an entry under the frozen time as an index. The entry records the frozen type and frozen data under that frozen time. The frozen data read instruction includes the frozen time and frozen type status word. In some implementations, the electricity meter stores frozen data under multiple frozen times. The relevant entry is retrieved based on the frozen time index. In block 504, in response to multiple frozen types in the entry, method 500 sequentially traverses the frozen sub-data corresponding to different associated object attributes in the frozen data. Each frozen sub-data store contains a data validity check and associated object attribute data corresponding to the data validity check. The data validity check contains one or more frozen type status words. The process of traversing each frozen sub-data includes: responding to the data validity check containing the read frozen type status word in the frozen sub-data, reading the frozen sub-data corresponding to the data validity check, and then traversing the next frozen sub-data after reading.

[0041] In some implementations, the process of traversing each frozen sub-data also includes: traversing the next frozen sub-data in response to the data validity check in the frozen sub-data not containing the read frozen type status word.

[0042] In this way, the relevant entries are located using the freeze time. Then, when it is determined that an entry has multiple freeze types, it is necessary to check whether the data validity checker in each frozen sub-data contains the freeze type status word to be read. This allows the required data to be retrieved from each frozen sub-data one by one. Because of the storage method of this frozen data—that is, different freeze types of the same associated object attribute correspond to one associated object attribute data—a single data read can filter the required associated object attribute data from multiple freeze types, eliminating the need to repeatedly read and check each associated object attribute data for different freeze types, greatly improving data reading efficiency.

[0043] Figure 6An example diagram is shown of a data freeze reading process 600 for an electricity meter according to some embodiments of the present disclosure. This process 600 begins execution after the electricity meter responds to a data freeze reading command. Figure 6 As shown, in box 602, process 600 queries the corresponding entry in the frozen record using the read freeze time as an index. Then, it retrieves the freeze type from the entry for judgment. In box 604, if process 600 determines that the freeze type in the entry has multiple bits, it proceeds to box 606 to traverse the frozen sub-data corresponding to different associated object attributes in the frozen data. In one example, the freeze type is "0011," which has two bits (i.e., two positions are "1"), so it is necessary to further determine which frozen sub-data contains the associated object attribute data of the read freeze type. In some implementations, the frozen sub-data corresponding to different associated object attributes is traversed sequentially according to the order of all associated object attributes in the overall associated attribute table. In box 608, during the traversal, it is determined whether the data validity checker contains a frozen type keyword. If it does not contain a frozen keyword and the traversal has not ended as determined by box 612, then return to box 606 to traverse the next frozen sub-data. If it contains a frozen keyword, then box 610 is executed to read the frozen sub-data corresponding to the data validity checker. If the traversal has not ended as determined by box 612, then return to box 606 to traverse the next frozen sub-data. When the traversal ends as determined by box 612, the reading is complete.

[0044] like Figure 6 As shown in box 614, process 600 further determines if the frozen data type in the entry has one bit. If so, it proceeds to box 616 to directly read the frozen data under that entry. In one example, the frozen data type is "0001" with one bit (i.e., one bit is "1"). This entry stores frozen data of one frozen type, which is the target data to be read, so the frozen data in the entry is read directly. Finally, after the target frozen data is read, it is sent to the energy meter master station via the concentrator.

[0045] This disclosure also provides an electricity meter, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the electricity meter frozen data storage method or the electricity meter frozen data reading method of this disclosure.

[0046] While several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented individually or in any suitable sub-combination in multiple implementations.

[0047] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

[0048] The various embodiments of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or technical improvements to the embodiments in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A method for freezing data in an electricity meter, characterized in that, include: In response to a freeze command, an entry is generated with the freeze time as the record identifier. The entry records the freeze type and frozen data under the freeze time. The freeze command contains freeze tasks of multiple freeze types. The frozen data stores one or more frozen sub-data of associated object attributes; the frozen sub-data stores a data validity checker and associated object attribute data corresponding to the data validity checker; the data validity checker contains one or more freeze type status words, and when an associated object attribute data is frozen for multiple freeze types, the multiple freeze type status words are concatenated to form the data validity checker. The process of freezing data records in the aforementioned entries includes: Get the attribute table of all associated objects; and In the entry, freeze sub-data is recorded according to all associated object attribute records in the total associated object attribute table, wherein the associated object attribute data that has not been frozen is null and the corresponding data validity check is set to zero.

2. The method for freezing data storage in an electricity meter according to claim 1, characterized in that, The freeze types include at least minute freeze, hour freeze, and day freeze.

3. The method for freezing data storage in an electricity meter according to claim 1, characterized in that, The process for generating the freeze type includes: Based on the configuration parameters of the freeze task, the freeze type is generated, whereby the configuration parameters are used to indicate whether the relevant positions in the fields of the freeze type are 0 or 1.

4. The method for freezing data storage in an electricity meter according to claim 1, characterized in that, The process of generating the data validity criterion includes: Based on the freeze type status word of the frozen task, a data validity check character containing the freeze type status word is formed.

5. A method for reading frozen data from an electricity meter, characterized in that, The frozen data of the electricity meter is stored according to any one of claims 1 to 4, and the method for reading the frozen data of the electricity meter includes: In response to a frozen data read command, the system retrieves entries for that frozen time, using the read frozen time as an index. Each entry records the frozen type and frozen data for that frozen time. The frozen data read command includes the read frozen time and the frozen type status word. In response to the entry having multiple freeze types, the frozen sub-data corresponding to different associated object attributes in the frozen data is traversed sequentially. Each frozen sub-data stores a data validity checker and associated object attribute data corresponding to the data validity checker. The data validity checker contains one or more freeze type status words. The process of traversing each frozen sub-data includes: in response to the data validity check in the frozen sub-data containing the read frozen type status word, reading the frozen sub-data corresponding to the data validity check.

6. The method for reading frozen data from an electricity meter according to claim 5, characterized in that, The process of traversing each frozen sub-data also includes: In response to the fact that the data validity check in the frozen sub-data does not contain the read frozen type status word, the next frozen sub-data is traversed.

7. The method for reading frozen data from an electricity meter according to claim 5, characterized in that, In response to the freeze type of the entry, there are multiple freeze types. The frozen sub-data corresponding to different associated object attributes in the frozen data are traversed sequentially, including: In response to the entry's freeze type having multiple BIT positions, the frozen sub-data corresponding to different associated object attributes in the frozen data are sequentially traversed according to the order of all associated object attributes in the total associated object attribute table.

8. The method for reading frozen data from an electricity meter according to claim 7, characterized in that, Also includes: In response to the entry having a freeze type with one bit, the frozen data under the entry is read.

9. An electricity meter, characterized in that, The electricity meter includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the electricity meter frozen data storage method as described in any one of claims 1 to 4, or the electricity meter frozen data reading method as described in any one of claims 5 to 8.

Images