A method, medium and terminal for identifying upgrade package of intelligent metering equipment

Abstract

The present invention is applicable to the field of smart grid technology, and relates to a method, medium and terminal for identifying an upgrade package of a smart metering device, including: rapid identification of upgrade files by upper computer software: definition by hardware phenotype, software version or parameter list name in the image header; rapid identification of upgrade files by smart metering devices: image identification 4 bytes, identification according to BIT bits; digital signature based on elliptic curve ECDSA is used in the image header; parameter upgrade file: the image header is followed by the identification and value of each parameter, and for devices that meet the IEC62056 protocol specification, the characteristics of each parameter are added after the image header; for devices that meet the ANSI protocol specification, the image header is followed by some characteristics of the parameters replaced by the data TAB identification specified in the ANSI standard. The present invention has a simple process and convenient operation, expands the scope of application of the method, and reduces the cost of identifying upgrade packages of smart metering devices.

Description

Technical Field

[0001] The present invention belongs to the technical field of smart grids, and in particular relates to a method, medium and terminal for identifying an upgrade package of a smart metering device. Background Art

[0002] The biggest feature of all smart devices is that they can be upgraded regularly or irregularly, which can not only fix software bugs and reduce losses, but also continuously add or expand new functions to the devices as technology develops, thereby greatly extending the effective life of the device and greatly reducing the cost of purchasing equipment for users. Therefore, they are very popular among users.

[0003] Due to the imbalance of technological development, the current technology has some shortcomings: with the development of smart grids, the international demand for overall AMI system solutions is also increasing, and there are more and more related smart metering devices. There are various upgrade package files, and the existing technology lacks unified planning and identification of upgrade package files; there are differences between upgrade package files, and in order to cope with the upgrade of different equipment, a series of software must be developed to support it, resulting in high subsequent maintenance costs; in actual applications, in the same AMI system, there are products from different manufacturers, as well as different models and types of products from the same manufacturer. Because there is no universal specification for the format of the upgrade file, public utilities (power companies, water companies, gas companies, heating departments) are unable to classify and trace these upgrade files, and customers find it difficult to effectively manage numerous upgrade files. The patent application with publication number CN115658112A provides a method for improving the efficiency of electric energy meter firmware upgrade, including: S10, firmware information header definition; S20, upgrade package production; S30, upgrade package transmission; S40, upgrade package decompression and recovery; S50, upgrade package legality check; S60, firmware activation; S70, firmware abnormal recovery. This patent application mainly optimizes the design and improves the efficiency of the meter firmware upgrade package, which cannot meet the effective operation of the entire AMI system, has low applicability, and still cannot overcome the drawbacks of the prior art.

[0004] Therefore, how to provide an efficient, convenient and low-cost method for identifying upgrade packages of smart metering equipment is an urgent problem to be solved by personnel in this technical field. Summary of the invention

[0005] In view of the shortcomings of the prior art, the purpose of the present invention is to provide a method for identifying an upgrade package of a smart metering device, so as to solve the problems of inconvenient and high cost of the identification process of the upgrade package of the smart metering device in the prior art; in addition, the present invention also provides an identification medium and terminal for the upgrade package of a smart metering device.

[0006] Compared with the prior art, the present invention has at least the following beneficial effects:

[0007] In a first aspect, the present invention provides a method for identifying an upgrade package of a smart metering device, comprising the following steps:

[0008] S10. Rapid identification of upgrade files by host computer software: defined by hardware type, software version or parameter list name in the image header; S20. Rapid identification of upgrade files by smart metering equipment: image identification is 4 bytes and is identified according to BIT bits; S30. ECDSA-based digital signature based on elliptic curve is used in the image header; S40. Parameter upgrade file: the image header is followed by the identification and value of each parameter. For devices that meet the IEC62056 protocol specification, the characteristics of each parameter are added after the image header; for devices that meet the ANSI protocol specification, some characteristics of the parameters following the image header are replaced with the data TAB identification specified in the ANSI standard.

[0009] Furthermore, in step S10 and step S20, the software versions include IEC62056, ANSI, and STS, and the parameters include the firmware or parameters of the own product and the firmware or parameters of a third party.

[0010] Furthermore, in the step S20, the upgrade files are distinguished by image_identifier in method 1 of category 18 in DLMS / COSEM.

[0011] Furthermore, the upgrade objects identified include statutory firmware, non-statutory firmware and parameters of the electric meter, communication module, user display and gateway.

[0012] Furthermore, in step S40, the parameter features added by the device that meets the IEC62056 protocol specification include the parameter class number, OBIS name, attribute number, data type, and parameter value; the replaced partial features are the parameter class number, OBIS name, and attribute number.

[0013] In a second aspect, the present invention further provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program implements the above method when executed by a processor.

[0014] In a third aspect, the present invention further provides an electronic terminal, comprising: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the terminal executes the method as described above.

[0015] Compared with the prior art, the identification method, medium and terminal of the smart metering device upgrade package provided by the present invention have at least the following beneficial effects:

[0016] The prior art lacks unified planning and identification of upgrade package files, and the maintenance cost is high, making it difficult for customers to effectively manage numerous upgrade files. The present invention, within the framework of existing metrology-related standards (ANSI, IEC62056, DLT698 / 645, etc.), fully combines the upgrade process required by the specification formulation and requirements, and designs a file header for various types of upgrade files such as meter firmware, meter parameters, communication module firmware, communication module parameters, third-party device firmware, third-party device parameters, etc. As a unified file identification method, when the device is OTA upgraded or locally upgraded, the legitimacy, file type, applicable scenario, file version, etc. of the upgrade file can be quickly identified, and the same set of upper computer upgrade software can be used to complete the upgrade operation of the device, reducing the development of software types and quantities, reducing costs, and not changing the workflow of the upgrade operation specified in DLMS / COSEM. The whole process is efficient and convenient, and the definition method of the firmware information header is further improved, which is not only compatible with previous design definitions, but also greatly expands the scope of application of the method. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the scheme of the present invention, a brief introduction is given below to the figures required for use in the description of the embodiments. Obviously, the figures described below are some embodiments of the present invention. For ordinary technicians in this field, other figures can be obtained based on these figures without paying any creative work.

[0018] Figure 1 The present invention provides a flowchart of a method for identifying an upgrade package of a smart metering device. DETAILED DESCRIPTION

[0019] In order to facilitate the understanding of the present invention, the present invention will be described more fully below with reference to the relevant drawings. The preferred embodiments of the present invention are given in the drawings. However, the present invention can be implemented in many different forms and is not limited to the embodiments described herein. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present invention more thorough and comprehensive.

[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present invention. The terms used in the specification of the present invention herein are only for the purpose of describing specific embodiments and are not intended to limit the present invention.

[0021] The present invention provides a method for identifying an upgrade package of a smart metering device, which is applied in a process of upgrading software of a smart metering device. The method for identifying an upgrade package of a smart metering device comprises the following steps:

[0022] S10. Rapid identification of upgrade files by host computer software: defined by hardware type, software version or parameter list name in the image header;

[0023] S20, rapid identification of upgrade files by smart metering equipment: image mark 4 bytes, marked according to BIT bits;

[0024] S30, the image header uses an ECDSA digital signature based on elliptic curve;

[0025] S40, parameter upgrade file: After the image header are the identifiers and values ​​of each parameter. For devices that meet the IEC62056 protocol specification, the characteristics of each parameter are added after the image header; for devices that meet the ANSI protocol specification, some characteristics of the parameters after the image header are replaced with the data TAB identifier specified in the ANSI standard.

[0026] The invention has a simple process and is easy to operate, expands the scope of application of the method, and reduces the cost of identifying upgrade packages for smart metering equipment.

[0027] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings.

[0028] The present invention provides a method for identifying an upgrade package of a smart metering device, which is applied in the process of upgrading the software of the smart metering device. Figure 1 As shown, in this embodiment, the method for identifying the smart metering device upgrade package includes the following steps:

[0029] S10. The host computer software quickly identifies the upgrade file (IEC62056, ANSI, STS and other future types of files; firmware or parameters of the product supplier's own products, or third-party firmware or parameters): define it based on the hardware type, software version or parameter list name in the image header to achieve uniqueness and intuitiveness; for parameter upgrades, the image type and version in the image header are similar to parameter_list_name of attribute 2 of class 65 of IEC62056.

[0030] S20. Rapid identification of upgrade files for smart metering devices (IEC62056, ANSI, STS and other future types of files; firmware or parameters of the product supplier's own products, or third-party firmware or parameters): Refer to the image_identifier in method 1 of the 18 categories specified in the DLMS / COSEM blue book to distinguish, and the image identifier 4 bytes are identified according to the BIT bit, which comprehensively covers the statutory firmware, non-statutory firmware, parameters and other upgrade objects of devices such as electricity meters, communication modules, user displays, gateways, etc., thereby supporting the simultaneous transmission of multiple images and then simultaneous updates.

[0031] S30. The image header uses an ECDSA digital signature based on an elliptic curve. Currently, the mainstream international standards in various fields have put forward requirements for the security of remote firmware upgrades, explicitly requiring secure upgrades and requiring the use of an ECDSA digital signature based on an elliptic curve for firmware or parameters. The digital signature has an OBIS signature specified in the standard, and various international certification agencies also use this as a marked software identification signature in their certification reports.

[0032] S40, parameter upgrade file: the image header is followed by the identifier and value of each parameter, referring to the definition of 65 types of parameter identifiers in DLMS / COSEM. For devices that meet the IEC62056 protocol specification, the image header is followed by the class number, OBIS name, attribute number, data type (see the provisions of the blue book), and parameter value of each parameter; for devices that meet the ANSI protocol specification, only the class number, OBIS name, and attribute number of the parameter that follows the image header need to be replaced with the data TAB identifier specified in the ANSI standard; for product types that meet other protocol specifications, the definition is similar.

[0033] Furthermore, in this embodiment, the image file itself should be able to reflect the necessary information for traceability and facilitate rapid identification of the host computer system and the electric meter. This information includes: digital signature value, address, length, manufacturer, meter type, software version, other relevant information, etc. This part of information is at the front of the image file. The image header is 256 bytes. The front bytes are defined as shown in Table 1 below, and the following bytes are reserved for the future:

[0034] Table 1

[0035]

[0036] Furthermore, in this embodiment, the definition of image type and version is:

[0037] The image type and version consists of six parts: base product model, product subclass configuration number X1, file classification number X2, module submodel (X3), version number X4X5, totaling 16 octets (2+1+2+2+2+2+1+1+1+2).

[0038] Furthermore, in this embodiment, the basic product model of different types of products is two uppercase English characters, and the definition is shown in Table 2:

[0039] Table 2

[0040]

[0041] Furthermore, in this embodiment, the product subclass configuration number X1 is two uppercase English characters, corresponding to the subclass of the base product. Among them, the corresponding base product is an electric energy meter, which starts with the letter M; the corresponding base product is a communication module, which starts with the letter C; the corresponding base product is a gateway, which starts with the letter G; the corresponding base product is a concentrator, which starts with the letter T; the corresponding base product is an indoor display unit, which starts with the letter I, and the definition is shown in Table 3:

[0042] Table 3

[0043]

[0044] Furthermore, in this embodiment, the sub-model number X2 of the model is optional, as shown in Table 4, and is two characters, which are any combination of numbers and uppercase letters:

[0045] Table 4

[0046]

[0047] Furthermore, in this embodiment, the file classification code X3 is two digits used to distinguish the classification management of firmware, parameter files, etc., and is defined as shown in Table 5:

[0048] Table 5

[0049]

[0050] Furthermore, in this embodiment, the file classification number X4 is two digits, which are used to distinguish the sub-class management of the Boot area, legal measurement related, and non-legal measurement related, and the definition is shown in Table 6:

[0051] Table 6

[0052]

[0053] Furthermore, in this embodiment, the format of the file version number is VX5.X6, a total of 5 characters, where "V" and "." are fixed format characters, X5 is 1 digit, indicating a major version, and X6 is 2 digits, indicating a minor version. Major versions usually introduce larger functional changes and improvements, including new functions, user interface improvements, and performance optimization, etc., while minor versions mainly focus on the optimization of existing functions and bug fixes, and do not involve major functional changes.

[0054] An embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, any one of the methods in the present embodiment is implemented.

[0055] An embodiment of the present invention further provides an electronic terminal, comprising: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the terminal executes any one of the methods in this embodiment.

[0056] The computer-readable storage medium in this embodiment can be understood by ordinary technicians in this field: all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to the computer program. The aforementioned computer program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

[0057] The electronic terminal provided in this embodiment includes a processor, a memory, a transceiver and a communication interface. The memory and the communication interface are connected to the processor and the transceiver and complete communication with each other. The memory is used to store computer programs, the communication interface is used to communicate, and the processor and the transceiver are used to run computer programs so that the electronic terminal executes each step of the above method.

[0058] Compared with the prior art, the identification method of the upgrade package of the smart metering device described in the above embodiment lacks unified planning and identification of the upgrade package files in the prior art, and the maintenance cost is high, and it is difficult for customers to effectively manage many upgrade files. The present invention is within the framework of the existing measurement-related standards (ANSI, IEC62056, DLT698 / 645, etc.), fully combines the upgrade process required by the specification formulation, and designs a file header for various types of upgrade files such as meter firmware, meter parameters, communication module firmware, communication module parameters, third-party device firmware, and third-party device parameters. As a unified file identification method, when the device is OTA upgraded or locally upgraded, the legitimacy, file type, applicable scenario, file version, etc. of the upgrade file can be quickly identified, and the same set of upper computer upgrade software can be used to complete the upgrade operation of the device, which reduces the development of software types and quantities, reduces costs, does not change the workflow of the upgrade operation specified in DLMS / COSEM, and the whole process is efficient and convenient. The definition method of the firmware information header is further improved, which is not only compatible with the previous design definition, but also greatly expands the scope of application of the method.

[0059] Obviously, the embodiments described above are only preferred embodiments of the present invention, rather than all embodiments. The preferred embodiments of the present invention are shown in the accompanying drawings, but they do not limit the patent scope of the present invention. The present invention can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present invention more thorough and comprehensive. Although the present invention has been described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific embodiments, or to perform equivalent replacements for some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of the present invention, directly or indirectly used in other related technical fields, is also within the scope of patent protection of the present invention.

Claims

1. A method for identifying an upgrade package of a smart metering device, characterized in that: The following steps are involved: S10. Rapid identification of upgrade files by host computer software: defined by hardware type, software version or parameter list name in the image header. Software versions include IEC62056, ANSI, STS. Parameters include firmware or parameters of own products and third-party firmware or parameters. S20, fast identification of upgrade files by smart metering equipment: the image identifier is 4 bytes, and is identified according to the BIT bit. In step S20, the upgrade files are distinguished by the image_identifier in the 18-category method 1 in DLMS / COSEM. The upgrade objects identified include the legal firmware, illegal firmware and parameters of the meter, communication module, user display and gateway; S30, the image header uses an ECDSA digital signature based on elliptic curve; S40, parameter upgrade file: after the image header are the identifiers and values ​​of each parameter. For devices that meet the IEC62056 protocol specification, the characteristics of each parameter are added after the image header, and the parameter characteristics include the class number, OBIS name, attribute number, data type, and parameter value of the parameter; for devices that meet the ANSI protocol specification, the image header is followed by part of the characteristics of the parameter replaced with the data TAB identifier specified in the ANSI standard, and the replaced part of the characteristics are the class number, OBIS name, and attribute number of the parameter; The image header is 256 bytes; the image type and version include the base product model, product subclass configuration number X1, module submodel X2, file classification number X3, version number X4 and version number X5, a total of 16 octets.

2. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to claim 1 is implemented.

3. An electronic terminal, characterized in that: include: Processor and memory; The memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the terminal executes the method as claimed in claim 1.

Images