Dynamic Configuration Method and System for Multi-Item Electricity Meter Data Items

By introducing a common data item table and mapping relationship into the AMI master station system, the problem of differentiated configuration of meter data items was solved, and unified storage and differentiated display of meter data were realized, reducing system maintenance costs and response time.

CN123075299APending Publication Date: 2026-11-10SHENZHEN INHEMETER +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611190439.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-06
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

The existing AMI master station system suffers from significant differences in the OBIS code collection indicators reported by smart meters from different regions and batches. This leads to fragmentation of the system across multiple versions, difficulties in code maintenance, high operation and maintenance costs, and a lengthy response chain for business requirements, making it impossible to achieve unified storage and differentiated display of meter data items.

Method used

A dynamic configuration method for multi-item meter data items is adopted. By pre-storing a general data item table and mapping relationship, the unique identifier of the meter device, the reading instruction set and data item identifier are mapped to the reserved fields. This dynamically adapts to the differences in meter data items and supports configuration without modifying the database structure or program code.

Benefits of technology

It enables unified storage and differentiated display of multi-item electricity meter data items, reduces the maintenance costs of database and program code, improves response speed and operation and maintenance efficiency, and supports business configuration adjustments for non-technical personnel.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123075299A_ABST
    Figure CN123075299A_ABST
Patent Text Reader

Abstract

This invention provides a method and system for dynamically configuring multi-item electricity meter data items. The system includes a general data item table pre-configured with a common identifier field group and a reserved data field group; a first mapping relationship pre-configured between device model identifiers and meter reading instruction sets; a second mapping relationship pre-configured between data item identifiers and reserved data fields; retrieving the meter reading instruction set and issuing it to the target electricity meter based on the first mapping relationship; parsing the returned data messages and extracting each data item identifier and its value; matching and determining the reserved data field corresponding to each data item identifier based on the second mapping relationship; and writing the value corresponding to each data item identifier into the reserved data field corresponding to each data item identifier in the general data item table, which is associated with the unique identifier of the target electricity meter device and has been matched and determined. The entire data acquisition, storage, and front-end display chain is configurable, flexibly adapting to the differentiated needs of multi-item electricity meter data items, and achieving unified storage and differentiated display of multi-item data items.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of power automation information acquisition technology, and in particular to a method and system for dynamically configuring data items of multiple electricity meters. Background Technology

[0002] In the existing AMI (Advanced Metering Infrastructure) master station system, due to the inconsistent business management standards of power companies in different regions, there are significant differences in the metering data items (collected indicators such as total positive active power, rate power, maximum demand, three-phase voltage, and loop current) corresponding to the OBIS codes reported by the electricity meters.

[0003] The AMI master station needs to be compatible with various smart meters from multiple regions and different manufacturing batches; furthermore, as a third-party service provider, it also needs to isolate business data and handle differentiated business processes for different electricity customers. Currently, the industry mainstream, to adapt to the needs of multiple projects serving concurrently, generally adopts the following two solutions, which have obvious shortcomings: 1. Customize database table structures for each project; Based on the unique collection parameters of each project, a separate frozen data storage table structure (containing specific data item fields) is designed. This approach leads to system fragmentation across multiple versions, resulting in numerous differentiated code branches. These branches are difficult to maintain and have high operational costs, making it impossible to rely on a standardized system to support the parallel operation of multiple projects.

[0004] 2. General wide table + hard-coded parsing processing; The database uses wide tables with numerous reserved fields for unified storage. However, the entire logic of OBIS data parsing, data entry verification, and front-end data rendering and display is embedded in the program code and requires hard coding. If customer requirements change, such as adding new data collection metrics or adjusting existing data item configurations, developers must modify the underlying code and package and deploy the new version, resulting in a lengthy business requirement response chain. Configuration adjustments rely on professional technical personnel, making it impossible for business operations staff to configure them independently, leading to extremely poor usability.

[0005] In summary, the industry urgently needs a solution that can dynamically adapt to the differentiated configurations of meter data items in different projects without modifying the database table structure or underlying program code, while taking into account both unified storage and differentiated display of metering data. Summary of the Invention

[0006] The technical problem to be solved by the present invention is to provide a method and system for dynamic configuration of multi-item electricity meter data items, so as to achieve dynamic adaptation to the differences of multi-item electricity meter data items without modifying the database structure or program code.

[0007] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows: Methods for dynamically configuring data items in multi-item electricity meters include: A pre-stored general data item table is configured with a public identifier field group and a reserved data field group. The public identifier field group includes a unique identifier for the electricity meter device. A first mapping relationship between pre-configured device model identifiers and copying instruction sets, wherein the copying instruction sets include identifiers of each specified data item and their corresponding copying instructions; A second mapping relationship between pre-configured data item identifiers and reserved data fields; When performing the meter reading task, the reading instruction set corresponding to the target meter is retrieved according to the first mapping relationship and sent to the target meter; Receive and parse the data messages returned by the target meter, and extract the identifiers of each data item and their corresponding values ​​for this meter reading; Based on the second mapping relationship, the reserved data fields corresponding to the identifiers of each data item to be copied are matched and determined; The values ​​corresponding to the identifiers of each data item read in this reading are written into the reserved data fields corresponding to the unique identifiers of the target meter in the general data item table that are associated with and matched with the unique identifier of the meter device.

[0008] Optionally, it also includes: A third mapping relationship between pre-configured items and header configuration information, wherein the header configuration information includes a list of data item identifiers and the attributes corresponding to each data item identifier, and the attributes include display name and data type; In response to a query request initiated by the front end for a specified item, a data set associated with the unique identifier of the meter device belonging to the specified item is loaded from the general data item table; Based on the second mapping relationship, the names of the reserved data fields in the loaded data set are replaced with the corresponding data item identifiers; Based on the third mapping relationship, the identifiers of the data items in the loaded data set are replaced with the corresponding display names; Return the replaced data set to the front end; The front end renders and displays the replaced data set based on the third mapping relationship.

[0009] Optionally, the attributes also include column width and visibility status.

[0010] Optionally, the public identifier field group also includes a freeze time; the reserved data field group consists of several numeric reserved fields and several character reserved fields.

[0011] Optionally, it also includes: Configure the version numbers of the first mapping relationship and the second mapping relationship respectively; Write the values ​​corresponding to the identifiers of each data item being copied into the general data item table. Then, record the version numbers of the first mapping relationship and the second mapping relationship on which they are based.

[0012] Optionally, the data item identifier includes identifiers corresponding to at least two of the following data items: total forward active power, total reverse active power, rate power, maximum demand, three-phase voltage, and loop current.

[0013] Another technical solution provided by this invention is: A dynamic configuration system for multiple meter data items, including: A general data item storage module is used to pre-store a general data item table. The general data item table is configured with a public identifier field group and a reserved data field group. The public identifier field group includes a unique identifier for the electricity meter device. The copying instruction configuration module is used to pre-configure the first mapping relationship between the device model identifier and the copying instruction set, wherein the copying instruction set includes each specified data item identifier and its corresponding copying instruction; The column mapping configuration module is used to pre-configure a second mapping relationship between data item identifiers and reserved data fields; The meter reading task execution module is used to retrieve the meter reading instruction set corresponding to the target meter according to the first mapping relationship and send it to the target meter when executing the meter reading task. In addition, a data parsing and database entry module is used to receive and parse the data messages returned by the target meter, extract the identifiers of each data item read in this reading and their corresponding values; according to the second mapping relationship, match and determine the reserved data fields corresponding to the identifiers of each data item read in this reading; and write the values ​​corresponding to the identifiers of each data item read in this reading into the reserved data fields corresponding to the identifiers of each data item in the general data item table that are associated with the unique identifier of the meter device of the target meter and have been matched and determined.

[0014] Optionally, it also includes: The dynamic header configuration module is used to pre-configure a third mapping relationship between items and header configuration information. The header configuration information includes a list of data item identifiers and the attributes corresponding to each data item identifier. The attributes include display name and data type. In addition, a query rendering module is used to respond to a query request initiated by the front end for a specified item, load a data set associated with the unique identifier of the meter device belonging to the specified item from the general data item table; replace the reserved data field name in the loaded data set with the corresponding data item identifier according to the second mapping relationship; replace the data item identifier in the loaded data set with the corresponding display name according to the third mapping relationship; return the replaced data set to the front end; and render and display the replaced data set according to the third mapping relationship.

[0015] Optionally, the common identifier field group of the general data item table pre-stored in the general data item storage module also includes a freeze time, and the reserved data field group consists of several numeric reserved fields and several character reserved fields.

[0016] Optionally, the data parsing and storage module is also used to record the version number of the first mapping relationship and the second mapping relationship on which it is based.

[0017] The beneficial effects of this invention are as follows: The dynamic configuration method and system for multi-project meter data items provided by this invention, by configuring a common identifier field group and a reserved data field group in the general data item table, achieves unified storage of meter data items for different projects, adapting to various project needs without adjusting the database table structure. Simultaneously, a first mapping relationship between the device model identifier and the meter reading instruction set, independent of the business code, and a second mapping relationship between the data item identifier and the reserved data field are pre-configured. When the data items to be read for a project change, only the corresponding mapping configuration needs to be updated, without modifying, compiling, or releasing a new version of the application. Furthermore, a third mapping relationship between projects and meter header configuration information, independent of the front-end display logic, is pre-configured, supporting customized front-end display rules for each project without modifying the front-end page code. This invention achieves end-to-end configuration from meter data collection and storage to front-end display, flexibly adapting to the differentiated needs of multi-project meter data items, achieving unified storage and differentiated business display of multi-project meter data items. Attached Figure Description

[0018] Figure 1 A flowchart illustrating a method for dynamically configuring multi-item electricity meter data items according to an embodiment of the present invention; Figure 2 This is an example of the display effect of the T1-T8 total active power data items of the target electricity meter device collected by Project A in another embodiment of the present invention on the front end; Figure 3 A schematic diagram illustrating the interaction of various modules in a dynamic configuration system for multi-item electricity meter data items, provided as another embodiment of the present invention; Figure 4This is an example of how the forward and reverse total active power data of the target meter device collected in Project B, a specific application scenario of this invention, is displayed on the front end. Detailed Implementation

[0019] To explain in detail the technical principles, specific implementable solutions, possible application scenarios, and achievable objectives and effects of the present invention, exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. It is understood that the embodiments described herein and the embodiments shown in the accompanying drawings are only used to more clearly illustrate the technical solutions of the present invention, and are therefore only examples intended to explain the present invention, and should not be construed as limiting the present invention. It should be understood that the present invention can be implemented in various forms and should not be limited to the embodiments set forth herein.

[0020] Please see Figure 1 This invention provides a dynamic configuration method for multi-item electricity meter data items. It specifically addresses the technical problems of existing AMI master station systems, such as the inability to adapt to differences in meter data items across different projects without adjusting the database structure; the need to modify, compile, and release the application when the data items to be read for a project change, resulting in high maintenance costs and slow response times; and the inability of non-technical personnel to automatically adjust the data collection scope and display method.

[0021] like Figure 1 As shown in the figure, an embodiment of the present invention provides a method for dynamically configuring multi-item electricity meter data items, including the following steps: S1: Pre-store a general data item table, which is configured with a public identifier field group and a reserved data field group. The public identifier field group includes a unique identifier for the electricity meter device.

[0022] The general data item table is a storage table designed for daily and monthly settlements and other types of frozen data, used to uniformly store all types of data reported by electricity meter equipment.

[0023] The general data item table is configured with a public identifier field group and a reserved data field group.

[0024] The public identifier field group includes the unique identifier of the electricity meter device, the freeze time, etc. Optionally, the unique identifier of the electricity meter device can be the device model identifier (also known as the nameplate barcode), the factory serial number (such as SN / meter number), the DLMS logical device name, or the electricity meter resource number (asset number).

[0025] The reserved data field group includes several numeric reserved fields (such as FIELD_DIGIT_1 to FIELD_DIGIT_N) and several character reserved fields (such as FIELD_STRING_1 to FIELD_STRING_M).

[0026] The general data item table design in this embodiment enables the storage structure to be decoupled from the actual data items, and a single table can accommodate any type and number of data items.

[0027] S2: A first mapping relationship between the pre-configured device model identifier and the copying instruction set, wherein the copying instruction set includes the identifier of each specified data item and its corresponding copying instruction.

[0028] The device model identifier refers to the standardized code composed of letters and numbers printed on the nameplate of the electricity meter. It uniquely identifies the phase, principle, function, and product series of the electricity meter and is a core field for identifying electricity meters in record keeping, centralized meter reading systems, and asset management. For example, the device model identifiers are DDZY188-Z, DTSD341, and DDS862.

[0029] Optionally, the data item identifier can be a DL / T645 Data Identifier (DI). For example, 00 01 00 00 represents the current total positive active energy. Alternatively, it can be a DL / T698.45 OAD object attribute descriptor. For example, 01 1000 represents the positive active energy value.

[0030] Preferably, the data item is identified by an OBIS code, which is compatible with all smart meters both domestically and internationally. For example, an OBIS code of 1-0: 1.8.0.255 represents total positive active energy.

[0031] In some specific implementations, the device model identifiers in the first mapping relationship can be arranged according to the "project" dimension, or the association between projects and device model identifiers can be established simultaneously in the first mapping relationship. Thus, the first mapping relationship is essentially an association of "project - device model identifier - meter reading instruction set". When executing a meter reading task for a certain project, the target project can be located first based on the first mapping relationship, then the corresponding target device model identifier can be further retrieved, and finally the meter reading instruction set required for collecting the corresponding electricity meter data items from the target meter device under the target project can be retrieved.

[0032] S3: The second mapping relationship between pre-configured data item identifiers and reserved data fields.

[0033] The second mapping relationship is the same as the first mapping relationship, and both are maintained using configuration.

[0034] The second mapping relationship defines the correspondence between specific data item identifiers and the location of target storage fields within the general data item table. Assuming OBIS encoding is used as the data item identifier, the second mapping relationship is used to determine the specific field location in the general data item table where the collected corresponding OBIS encoded data should be stored. It can be understood that the second mapping relationship actually represents the correspondence between variable fields in the general data item table and the actual stored data items.

[0035] In some specific implementations, the data item identifiers include, but are not limited to, identifiers corresponding to data items such as: total forward active power, total reverse active power, rate power, maximum demand, three-phase voltage, and loop current.

[0036] In some specific implementations, based on the OBIS codes (i.e., data item identifiers) corresponding to all the data items that need to be copied in the project, the target storage field in the general data item table that corresponds one-to-one with them is configured in the second mapping relationship.

[0037] For example, the OBIS code representing "total positive active power" can be mapped to the position of the numeric reserved field "FIELD_DIGIT_1 field" in the general data item table.

[0038] For example, the mapping between the data item identifier configured in the second mapping relationship and the reserved data field is shown in the following example: { "01239302": "FIELD_DIGIT_1", "03030002": "FIELD_DIGIT_2", "03031002": "FIELD_DIGIT_3", "04030006": "FIELD_STRING_1", "04031002": "FIELD_STRING_2", "04032002": "FIELD_STRING_3" }

[0039] S4: When performing the meter reading task, retrieve the reading instruction set corresponding to the target meter according to the first mapping relationship and send it to the target meter.

[0040] In some specific implementations, when performing a data reading task for a certain project, the target device model identifier corresponding to the target project is first located based on the first mapping relationship, and then the data reading instruction set required for the target meter device under the target project to collect the corresponding electricity meter data item is retrieved and sent to the target meter device.

[0041] S5: Receive and parse the data messages returned by the target meter, and extract the identifiers of each data item and their corresponding values ​​for this meter reading.

[0042] S6: Based on the second mapping relationship, match and determine the reserved data field corresponding to each data item identifier of this copying.

[0043] S7: Write the values ​​corresponding to the identifiers of each data item read this time into the reserved data fields corresponding to the unique identifiers of the target meter in the general data item table that are associated with and matched with the unique identifier of the meter device of the target meter.

[0044] Here, since different projects may contain the same data item identifier, a unique identifier for the meter device is introduced in the general data item table to distinguish them, so as to ensure the accuracy of the stored data of various data items under different projects and to prevent them from being confused.

[0045] In some specific implementations, when performing step S2, the version number of the current first mapping relationship is configured simultaneously; similarly, when performing step S3, the version number of the current second mapping relationship is configured simultaneously. Subsequently, step S7 is performed, where the values ​​corresponding to the identifiers of each data item read in this transaction are written into the general data item table. Afterwards, the version numbers of the first and second mapping relationships upon which this data processing is based are synchronously recorded to support historical data tracing and backtracking.

[0046] Please see Figure 1 and Figure 2 Another embodiment of the present invention further extends the above embodiments by improving the front-end rendering and display processing.

[0047] like Figure 1 As shown, the dynamic configuration method for multi-item electricity meter data items provided in this embodiment further includes: S8: A third mapping relationship between pre-configured items and header configuration information. The header configuration information includes a list of data item identifiers and the attributes corresponding to each data item identifier. The attributes include, but are not limited to: display name (supporting multilingual keys), data type, column width, and display / hidden status.

[0048] The third mapping relationship is also maintained in a configuration format and is used to store the configuration information of the front-end presentation layer; the third mapping relationship specifically defines the correspondence between each item and the list of data items to be displayed and their attributes.

[0049] For example, the specific configuration of the third mapping relationship is as follows: [{ "title / / Display Name": "import_active_energy / / Total positive active energy" ", "label": "import_active_energy / / total positive active energy" ", "dataIndex / / Data item identifier": "03030002", "key": "03030002", "width / / column width": 208, "align / / alignment": "", "isShow / / show / hide / display status": true, "type" / / data type: "customize" / / custom }, ... ] S9: In response to a query request from the front end for a specified item, first load the data set associated with the unique identifier of the meter device belonging to the specified item from the general data item table; then, according to the second mapping relationship, replace the reserved data field name in the loaded data set with the corresponding data item identifier; simultaneously, according to the third mapping relationship, replace the data item identifier in the loaded data set with the corresponding display name; after that, return the replaced data set to the front end. S10: The front end renders and displays the replaced data set according to the third mapping relationship (show / hide control).

[0050] like Figure 2 The image shown is an example of how the total active power data items T1-T8 of the target electricity meter device collected by Project A are displayed on the front end.

[0051] Please see Figure 3 Another embodiment of the present invention provides a dynamic configuration system for multiple meter data items based on the above embodiments.

[0052] This embodiment provides a dynamic configuration system for multi-item electricity meter data items, combined with Figure 3 The understanding includes at least a general data item storage module, a copying instruction configuration module, a column mapping configuration module, a copying task execution module, and a data parsing and database entry module.

[0053] The general data item storage module is used to pre-store a general data item table. The general data item table is configured with a public identifier field group and a reserved data field group. The public identifier field group includes a unique identifier for the electricity meter device.

[0054] In some specific embodiments, the common identifier field group of the general data item table pre-stored in the general data item storage module also includes a freeze time, and the reserved data field group consists of several numeric reserved fields and several character reserved fields.

[0055] The copying instruction configuration module is used to pre-configure a first mapping relationship between the device model identifier and the copying instruction set, wherein the copying instruction set includes the identifier of each specified data item and its corresponding copying instruction.

[0056] The column mapping configuration module is used to pre-configure a second mapping relationship between data item identifiers and reserved data fields.

[0057] The meter reading task execution module is used to retrieve the meter reading instruction set corresponding to the target meter according to the first mapping relationship and send it to the target meter when performing the meter reading task.

[0058] The data parsing and database module is used to receive and parse the data messages returned by the target meter, extract the identifiers of each data item read this time and their corresponding values; according to the second mapping relationship, match and determine the reserved data fields corresponding to the identifiers of each data item read this time; and write the values ​​corresponding to the identifiers of each data item read this time into the reserved data fields corresponding to the identifiers of each data item in the general data item table that are associated with the unique identifier of the meter device of the target meter and have been matched and determined.

[0059] In some specific implementations, the data parsing and storage module is also used to record the version number of the first mapping relationship and the second mapping relationship on which it is based.

[0060] In some other specific embodiments, the dynamic configuration system further includes a dynamic header configuration module and a query rendering module.

[0061] The dynamic header configuration module is used to pre-configure a third mapping relationship between items and header configuration information. The header configuration information includes a list of data item identifiers and the attributes corresponding to each data item identifier. The attributes include display name, data type, column width, and display / hidden status.

[0062] The query rendering module is used to respond to a query request initiated by the front end for a specified item, load a data set associated with the unique identifier of the meter device belonging to the specified item from the general data item table; replace the reserved data field name in the loaded data set with the corresponding data item identifier according to the second mapping relationship; replace the data item identifier in the loaded data set with the corresponding display name according to the third mapping relationship; return the replaced data set to the front end; and render and display the replaced data set according to the third mapping relationship.

[0063] This embodiment provides a dynamic configuration system for multiple electricity meter data items. Through the collaborative work of the above modules, it realizes full-link configuration from electricity meter data collection and storage to front-end display. It can flexibly adapt to the differentiated needs of multiple electricity meter data items, and achieve unified storage and differentiated display of multiple electricity meter data items.

[0064] Please see Figure 4 Based on any of the above embodiments, the present invention also provides a specific application scenario. In this specific application scenario, the technical solution of the present invention will be described in detail with reference to a specific project example.

[0065] 1. Configuration Phase: Suppose that Project B needs to read the total positive active energy (corresponding to OBIS code FIELD_ID:03030002) and the total negative active energy (corresponding to OBIS code FIELD_ID:03040002) of the electricity meter.

[0066] First, in the first mapping relationship of the meter reading instruction configuration module, configure the mapping relationship between the two OBIS codes and their corresponding meter reading instruction sets to complete the configuration of the meter reading instructions.

[0067] Subsequently, in the second mapping relationship in the column mapping configuration module, the mapping relationships are established as follows: 03030002 → FIELD_DIGIT_1 and 03040002 → FIELD_DIGIT_2, so as to map OBIS code 03030002 to the FIELD_DIGIT_1 field in the general data item storage module and map OBIS code 03040002 to the FIELD_DIGIT_2 field in the general data item storage module, thus clarifying the exclusive storage field locations for these two types of data items.

[0068] Meanwhile, in the third mapping relationship in the dynamic header configuration module, the header configuration information of project B defines the header display as "Total Forward Active Energy" corresponding to OBIS code 03030002 and "Total Reverse Active Energy" corresponding to OBIS code 03040002, thus completing the configuration definition of the data item display rules.

[0069] 2. Operational Phase: After the system initiates the meter reading task for Project B, it sends a set of meter reading instructions carrying the aforementioned OBIS codes to the target meter device.

[0070] The target meter device responds to the reading command and sends back the corresponding collected data. The data parsing and database module parses out the value corresponding to OBIS code 03030002 as 100.5 and the value corresponding to OBIS code 03040002 as 220.1.

[0071] Based on the second mapping relationship in the column mapping configuration module, the system matches the reserved data fields in the general data item table of the general data item storage module corresponding to the two OBIS codes mentioned above.

[0072] Write the values ​​corresponding to the two OBIS codes above into the FIELD_DIGIT_1 and FIELD_DIGIT_2 fields of the general data item table respectively to complete the data standardization and storage.

[0073] 3. Front-end query and display stage: When the front end initiates a data query request, the system first loads the FIELD_DIGIT_1 and FIELD_DIGIT_2 fields and their data, which are the unique identifiers of all meters belonging to this item, from the general data item table.

[0074] Then, the rendering module first queries the column mapping configuration module. Based on the second mapping relationship in the column mapping configuration module, the FIELD_DIGIT_1 field in the loaded data is restored to 03030002, and FIELD_DIGIT_2 is restored to 03040002.

[0075] Then, by querying the dynamic header configuration module, based on the third mapping relationship in the dynamic header configuration module, 03030002 in the loaded data is rendered as "total positive active power" and 03040002 is rendered as "total negative active power", thus completing the personalized front-end display of different project data items without modifying the front-end page code.

[0076] For example, the front-end display effect of the forward and reverse total active power data items of the target meter device collected by Project B is shown in the following figure.

[0077] 4. Adjustment Phase: When the business requirements of Project B change, necessitating the addition of a "current" data item for data reading, the configuration process described above only needs to be repeated. This involves adding the OBIS code, reading instruction set, reserved data fields, and header configuration information for the corresponding current data item. The entire adjustment process requires no system service shutdowns, no modification to the database table structure, and no alteration to the front-end or back-end business code. The configuration takes effect immediately upon completion, allowing for rapid adaptation to the project's differentiated and dynamic data item reading and display needs.

[0078] In summary, the dynamic configuration method and system for multi-item electricity meter data items provided by this invention, through its end-to-end configurable architecture design, possesses multiple technical advantages compared to traditional customized development solutions, as detailed below: (1) Enable database structure reuse and adapt to rapid access of multiple projects.

[0079] By employing a standardized design with reserved numeric and character fields in the general data item table, differentiated meter data items from different projects are uniformly stored in the same data table structure. In scenarios involving new project integration or iterating on existing project data items, no database table structure modification operations (such as ALTER TABLE) are required, ensuring the stability of the database's physical structure throughout the process, significantly reducing database transformation costs and operational risks.

[0080] (2) The acquisition logic and data items are completely decoupled, and there is no need to iterate the program version.

[0081] By configuring a first mapping relationship and a second mapping relationship that exist independently of the business code, complete decoupling is achieved between data collection rules, field mapping rules, and project business logic. When data items are added, deleted, or changed in the project, only the corresponding mapping configuration in the backend needs to be updated. There is no need to modify, compile, or release the application. The application files remain unchanged, effectively improving the efficiency of requirement iteration.

[0082] (3) Supports accurate tracing of historical data and avoids the problem of data distortion during configuration iteration.

[0083] During the data parsing and ingestion phase, while data storage is being written, the current mapping version information is simultaneously recorded. Subsequent queries of historical frozen data can accurately match the mapping relationship of the corresponding period based on the version number bound to the data row, thus completing data parsing and restoration. This completely avoids problems such as historical data parsing errors and data inability to be correctly restored due to later configuration rule changes, ensuring the accuracy and traceability of data throughout its entire lifecycle.

[0084] (4) The front-end display and the underlying storage are separated to achieve differentiated code-free adaptation.

[0085] By independently configuring dynamic header information through a third mapping relationship, the front-end display rules are completely decoupled from the underlying data storage structure. For the same meter data item, different front-end display names, display statuses, and arrangement orders can be flexibly configured according to the business needs of different projects, without modifying the front-end page code or updating the front-end static resource files. This enables low-cost personalized display of multiple project data items.

[0086] (5) Optimize the system architecture and improve the ability to support multiple projects concurrently.

[0087] By adopting a unified data storage structure, multiple projects share the same data access interface, completely eliminating the large amount of code branching logic caused by traditional multi-project customization. This effectively simplifies the system architecture, reduces code redundancy, significantly increases the number of projects that a single system instance can support simultaneously, and enhances the system's multi-project concurrency support capabilities and operational stability.

[0088] (6) Lower the threshold for business adjustment operations and simplify existing operation and maintenance processes.

[0089] All data item adjustments and rule adaptations are implemented through visual configuration. When on-site projects encounter requirements such as data item modifications or display rule adjustments, administrators only need to modify the corresponding configuration parameters for quick results. No technical operations such as program development, compilation, and deployment are required. Even non-technical personnel can complete routine maintenance adjustments, significantly reducing the on-site maintenance threshold and labor costs.

[0090] Although preferred embodiments of the invention have been described, those skilled in the art, upon understanding the basic inventive concept, can make other changes and modifications to the embodiments. Therefore, the appended claims are intended to cover the preferred embodiments and all equivalent modifications falling within the scope of protection defined by the claims and their equivalents. Clearly, those skilled in the art can make various alterations and variations to the invention without departing from its spirit and scope. If such modifications and variations fall within the scope of protection defined by the claims and their equivalents, the invention also intends to include them.

[0091] It should be noted that any reference signs placed between parentheses in the claims should not be construed as limiting the claims. The word "comprising" does not exclude the presence of components or steps not listed in the claims. The word "a" or "an" preceding a component does not exclude the presence of a plurality of such components. The invention can be implemented by means of hardware comprising several different components and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by the same item of hardware.

[0092] In this invention, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this invention, "multiple" means two or more, unless otherwise explicitly specified. The term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone.

[0093] In this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0094] In this specification, the use of terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refers to a specific feature, structure, material, or characteristic described in connection with that embodiment or example, which is included in at least one embodiment or example of the present invention. The illustrative expressions of the above terms in this specification should not be construed as necessarily referring to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0095] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent modifications made based on the content of the present invention specification and drawings, or direct or indirect applications in related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for dynamically configuring data items in a multi-item electricity meter, characterized in that, include: A pre-stored general data item table is configured with a public identifier field group and a reserved data field group. The public identifier field group includes a unique identifier for the electricity meter device. A first mapping relationship between pre-configured device model identifiers and copying instruction sets, wherein the copying instruction sets include identifiers of each specified data item and their corresponding copying instructions; A second mapping relationship between pre-configured data item identifiers and reserved data fields; When performing the meter reading task, the reading instruction set corresponding to the target meter is retrieved according to the first mapping relationship and sent to the target meter; Receive and parse the data messages returned by the target meter, and extract the identifiers of each data item and their corresponding values ​​for this meter reading; Based on the second mapping relationship, the reserved data fields corresponding to the identifiers of each data item to be copied are matched and determined; The values ​​corresponding to the identifiers of each data item read in this reading are written into the reserved data fields corresponding to the unique identifiers of the target meter in the general data item table that are associated with and matched with the unique identifier of the meter device.

2. The dynamic configuration method for multi-item electricity meter data items as described in claim 1, characterized in that, Also includes: A third mapping relationship between pre-configured items and header configuration information, wherein the header configuration information includes a list of data item identifiers and the attributes corresponding to each data item identifier, and the attributes include display name and data type; In response to a query request initiated by the front end for a specified item, a data set associated with the unique identifier of the meter device belonging to the specified item is loaded from the general data item table; Based on the second mapping relationship, the names of the reserved data fields in the loaded data set are replaced with the corresponding data item identifiers; Based on the third mapping relationship, the identifiers of the data items in the loaded data set are replaced with the corresponding display names; Return the replaced data set to the front end; The front end renders and displays the replaced data set based on the third mapping relationship.

3. The dynamic configuration method for multi-item electricity meter data items as described in claim 2, characterized in that, The attributes also include column width and visibility status.

4. The dynamic configuration method for multi-item electricity meter data items as described in claim 1, characterized in that, The public identifier field group also includes the freeze time; the reserved data field group consists of several numeric reserved fields and several character reserved fields.

5. The dynamic configuration method for multi-item electricity meter data items as described in claim 1, characterized in that, Also includes: Configure the version numbers of the first mapping relationship and the second mapping relationship respectively; Write the values ​​corresponding to the identifiers of each data item being copied into the general data item table. Then, record the version numbers of the first mapping relationship and the second mapping relationship on which they are based.

6. The dynamic configuration method for multi-item electricity meter data items as described in claim 1, characterized in that, The data item identifier includes identifiers corresponding to at least two of the following data items: total positive active power, total reverse active power, rate power, maximum demand, three-phase voltage, and loop current.

7. A dynamic configuration system for multiple meter data items, characterized in that, include: A general data item storage module is used to pre-store a general data item table. The general data item table is configured with a public identifier field group and a reserved data field group. The public identifier field group includes a unique identifier for the electricity meter device. The copying instruction configuration module is used to pre-configure the first mapping relationship between the device model identifier and the copying instruction set, wherein the copying instruction set includes each specified data item identifier and its corresponding copying instruction; The column mapping configuration module is used to pre-configure a second mapping relationship between data item identifiers and reserved data fields; The meter reading task execution module is used to retrieve the meter reading instruction set corresponding to the target meter according to the first mapping relationship and send it to the target meter when executing the meter reading task. In addition, a data parsing and database entry module is used to receive and parse the data messages returned by the target meter, extract the identifiers of each data item read in this reading and their corresponding values; according to the second mapping relationship, match and determine the reserved data fields corresponding to the identifiers of each data item read in this reading; and write the values ​​corresponding to the identifiers of each data item read in this reading into the reserved data fields corresponding to the identifiers of each data item in the general data item table that are associated with the unique identifier of the meter device of the target meter and have been matched and determined.

8. The dynamic configuration system for multi-item electricity meter data items as described in claim 7, characterized in that, Also includes: The dynamic header configuration module is used to pre-configure a third mapping relationship between items and header configuration information. The header configuration information includes a list of data item identifiers and the attributes corresponding to each data item identifier. The attributes include display name and data type. In addition, a query rendering module is used to respond to a query request initiated by the front end for a specified item, load a data set associated with the unique identifier of the meter device belonging to the specified item from the general data item table; replace the reserved data field name in the loaded data set with the corresponding data item identifier according to the second mapping relationship; replace the data item identifier in the loaded data set with the corresponding display name according to the third mapping relationship; return the replaced data set to the front end; and render and display the replaced data set according to the third mapping relationship.

9. The dynamic configuration system for multi-item electricity meter data items as described in claim 7, characterized in that, The common identifier field group of the pre-stored general data item table in the general data item storage module also includes the freeze time, and the reserved data field group consists of several numeric reserved fields and several character reserved fields.

10. The dynamic configuration system for multi-item electricity meter data items as described in claim 7, characterized in that, The data parsing and storage module is also used to record the version number of the first mapping relationship and the second mapping relationship on which it is based.