KR102062636B1 - Apparatus for managing energy metering data, Method thereof, and Storage medium having the same - Google Patents

Abstract

An apparatus and method for managing energy meter data is provided. The energy metering data management device may include: a determination module for determining whether data acquired from an electronic meter is first resource data, and as a result of the determination, a matching module for matching the first resource data with LWM2M based second resource data, and the And a generation module for registering the second resource data as URI information.

Description

Apparatus for managing energy metering data, Method approximately, and Storage medium having the same}

The present invention relates to an energy metering data processing technology, and more particularly, to an energy metering data management apparatus that applies Internet of Things (IoT) and Low Power Wide Area (LPWA) technologies, which are the technical trends of the Internet of Things, to an energy remote meter reading system, and It's about how.

In particular, the present invention relates to an energy metering data management apparatus and method for modeling and managing energy metering data based on LWM2M (Light Weight Machine to Machine).

Most electricity meters adopt the DLMS (Device Language Message Specification) protocol, which is an international standard of the International Electronic Committee (IEC) 62056 series standard, and classifies and manages power data hierarchically through an object identification system (OBIS). Designed.

Since DLMS protocol does not consider poor communication network, it is pointed out that the protocol itself is heavy and there is a lot of transaction.

In addition, the DLMS protocol does not have a big problem when used in the electricity meter or the existing meter reading system, but when linked with an external system, there is no definition of a model and a structure for transferring and / or linking the weighing data. Therefore, in order to access data having an OBIS structure using an external system, a conversion server or middleware capable of interpreting the DLMS protocol is additionally required.

In particular, the low power wide area (LPWA) and the Internet of Things (IoT) communication methods, which are the major technologies in the energy remote meter reading system, are ultimately used, and the Internet of Things (IoT terminals, modems, etc.) is rapidly growing. In order to effectively manage a large number of terminals, LWM2M (Light Weight Machine to Machine) protocol, which is a lightweight resource management standard, is used. Thus, there is a need to model and manage effective energy metering data while using this protocol.

1. Korean Patent Publication No. 10-2016-0038121 2. Korean Patent Publication No. 10-2004-0009560 3. Korean Patent No. 10-0808445 (2008.02.22)

The present invention is to solve the problems according to the above background, LWM2M (Light Weight Machine to Machine) based energy metering data reflecting resource management characteristics based on OBIS (Object Identification System) defined in the Device Language Message Specification (DLMS) Its purpose is to provide a management apparatus and method.

In addition, the present invention improves the compatibility with the upper IoT (Internet of Things) platform and energy metering data maximizing the remote metering function and the meter's remote setting function through the lightweight resource management provided by the Light Weight Machine to Machine (LWM2M) Another object is to provide a management apparatus and method.

The present invention provides an energy metering data management device based on LWM2M (Light Weight Machine to Machine) reflecting resource management characteristics based on OBIS (Object Identification System) defined in the Device Language Message Specification (DLMS). to provide.

The energy metering data management device,

A determination module for determining whether data acquired from at least two electronic meters is first resource data;

A matching module for matching the first resource data with LWM2M-based second resource data as a result of the determination; And

And a generation module for generating the second resource data as URI information.

In this case, the first resource data includes at least two or more combinations of a class ID, an object identification system (OBIS) code, and a division number for distinguishing the two or more electronic meters.
The data of the electronic meter is characterized in that the device language message specification (DLMS) information.

In addition, the OBIS code is characterized in that expressed in decimal or hexadecimal.

delete

The matching may include a class ID indicating a large classification of data resources of the electronic meter, an OBIS code indicating a metering value and various setting values of the data resource, and an attribute indicating an actual value of the data resource, and the resource data of the LWM2M. It is characterized by matching to an instance to classify, a resource representing a meaning of resource data, and a resource instance representing a division of resource data.

In addition, the URI information is characterized in that the object, an instance, a resource, and a resource instance representing the major classification of data resources.

In addition, the matching matches the class ID, OBIS code, and attributes of the electronic meter to instances, resources, and queries of LWM2M, respectively. It is characterized in that a plurality to accommodate a plurality of attributes.

In addition, the URI information is characterized in that the object, the instance, resources, and in the order of the query.

The matching may be performed by matching a class ID, an OBIS code, and an attribute of the electronic meter with a resource, a resource instance, and a query of LWM2M, respectively. The query is also characterized by multiple numbers to accommodate multiple attributes.

The URI information may include an object, a resource, a resource instance, and a query.

In addition, the matching matches an OBIS code and an attribute of the electronic meter with a resource and a query of the LWM2M, respectively, and if the attribute is plural, the query is plural to accommodate a plurality of attributes. It is characterized by that.

The URI information may include an object, a resource, and a query in this order.

On the other hand, another embodiment of the present invention, the determination module, the determination step of determining whether the data obtained from the two or more electronic meters is the first resource data; A matching step of matching, by the matching module, the first resource data with LWM2M-based second resource data; And generating, by the generation module, the second resource data as URI information.

On the other hand, another embodiment of the present invention provides a computer readable storage medium storing program code for executing the energy metering data management method described above.

According to the present invention, LWM2M (Light Weight Machine to Machine) based energy metering data modeling and / or by applying the Internet of Thing (IoT) and Low Power Wide Area (LPWA) technologies, which are the technical trends of the Internet of Things, to the energy remote meter reading system Management is possible.

In addition, another effect of the present invention is to maximize the remote metering function and the meter setting remote control function by using the LWM2M technology, which is a lightweight resource management method, using a DLMS (Device Language Message Specification) method with a large overhead. have.

In addition, another effect of the present invention is that it is possible to link with various IoT servers without additional conversion software, it is possible to reduce the interworking establishment costs and program development costs with other systems.

In addition, another effect of the present invention is the advantage that can be easily extended to the various applications of the use of power data that was limited in the existing remote meter reading system.

1 is an object identification system (OBIS) code structure generally used in a Device Language Message Specification (DLMS) protocol.
FIG. 2 is an example illustrating the meaning of each layer of a general Light Weight Machine to Machine (LWM2M) Uniform Resource Identifier (URI).
3 is another example illustrating the meaning of each layer of a general Light Weight Machine to Machine (LWM2M) Uniform Resource Identifier (URI).
4 is an example resource model of a temperature sensor in the LWM2M (Light Weight Machine to Machine) shown in FIG.
5 is a Light Weight Machine to Machine (LWM2M) URI structure of the first management model according to an embodiment of the present invention.
6 is a flowchart illustrating a process of executing a first management model according to an embodiment of the present invention.
7 is a Light Weight Machine to Machine (LWM2M) URI structure of the second management model according to another embodiment of the present invention.
8 is a flowchart illustrating a process of executing a second management model according to another embodiment of the present invention.
9 is a conceptual diagram of an energy metering data management device according to another embodiment of the present invention.
FIG. 10 is a detailed configuration diagram of the communication terminal shown in FIG. 9.
11 is a Light Weight Machine to Machine (LWM2M) URI structure of a third management model according to another embodiment of the present invention.
12 is a flowchart illustrating a process of executing a third management model according to another embodiment of the present invention.
13 is a LWM 2M (Light Weight Machine to Machine) URI structure of a fourth management model according to another embodiment of the present invention.
14 is a flowchart illustrating a process of executing a fourth management model according to another embodiment of the present invention.
15 is a conceptual diagram illustrating an extension example with another system according to another embodiment of the present invention.

As the present invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

In describing each drawing, like reference numerals are used for like elements. Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.

For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term “and / or” includes any combination of a plurality of related items or any of a plurality of related items.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art.

Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Should not.

Hereinafter, an energy metering data management apparatus and method according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

1 is an object identification system (OBIS) code structure generally used in a Device Language Message Specification (DLMS) protocol. In general, the Light Weight Machine to Machine (LWM2M) is a lightweight IoT communication management model established by the Open Mobile Alliance (OMA), an international standardization organization for IoT device management, and is a CoAP (Constrained Application Protocol) in Representational State Transfer (REST) format. It works based on the protocol.

Its main functions provide registration, management, reporting, security, etc. of IoT (Internet of Things) terminals, and a URI (Uniform Resource Identifier) that represents the path of device resources. Naming rules.

Every URI of an LWM2M device (not shown) is composed of a combination of an object, an instance, a resource, and a resource instance. LWM2M can use basic REST commands such as GET, PUT, POST, and DELETE provided by CoAP, and ObAP function of CoAP for periodic reporting.

Recently, as the demand for interoperability and / or compatibility between objects increases domestically and internationally, end terminals of most IoT systems are using the LWM2M protocol, which is a REST-based lightweight resource management standard considering limited hardware resource conditions.

Resource (data) management of electronic meters (not shown), which adopts and uses DLMS around the world, uses OBIS code system. An electronic meter refers to a general device capable of measuring energy, and more specifically, may be expressed as an electricity meter, a gas meter, or a water meter.

Referring to FIG. 1, the OBIS code is composed of six digits (A, B, C, D, E, F). Each six digit has a hierarchical structure concept and each digit has a specific meaning. A is the field, B is the type, C and D are the subtypes, E is the time zone (tariff) or harmonics, and F is the time value.

 For example, OBIS code 0.0.1.0.0.FF is used for time information of KEPCO's electronic electricity meter (or electronic meter), and 1.1.1.8.0.FF is used for effective power amount. As such, the various information (metering values) and resources (various set values) required for the electronic meter are all defined and managed by the OBIS code of the DLMS. Prior to defining OBIS, DLMS has an interface class ID.

In DLMS, dozens of interface classes are defined and used to secure interoperability of data modeling. Interface classes are composed of attributes and methods. The first attribute of the Interface Class is always used as the OBIS code.

In detail, the OBIS code is defined based on a rule as shown in FIG. 1. After the second attribute, you can specify the actual measurement and measurement values, parameter setting values, and units if necessary. In conclusion, the DLMS data model can be characterized by the combination of Class ID + OBIS + Attribute. Examples of OBIS codes used in electronic meters are shown in the following table.

Item Class ID Hexadecimal number (OBIS) Attribute count Clock 8 0.0.1.0.0.FF 1-9 Active energy 3 1.1.1.8.0.FF 1 to 3 End of billing period 22 0.0.F.0.0.FF 1 ~ 4 Sum Time integral 4 1.1.1.8.0.1 1-5

On the other hand, the resource management method used by the LWM2M device uses a Uniform Resource Identifier (URI) structure. 2 and 3 showing this. That is, FIG. 2 is an example illustrating the meaning of each layer of a general Light Weight Machine to Machine (LWM2M) Uniform Resource Identifier (URI), and FIG. 3 is a view of each of a typical Light Weight Machine to Machine (LWM2M) Uniform Resource Identifier (URI) Another example of hierarchical meaning. 2 and 3, all URIs are a combination of Object (210) + Instance (220) + Resource (230) or Object (210) + Instance (220) + Resource (230) + Resource Instance (340). It is composed.

In order to facilitate understanding of the above-described structure will be described with reference to FIG.

4 is an example resource model of a temperature sensor in the LWM2M (Light Weight Machine to Machine) shown in FIG. Referring to FIG. 4, the object 210 refers to a large classification of resources such as temperature and humidity, and the instance 220 may indicate that there are a plurality of temperature sensors, that is, temperature sensor 1, temperature sensor 2, and temperature sensor 3. Means burn, etc.

Resource 230 refers to actual data such as actual temperature value, unit (° C. or F), maximum / minimum value of temperature, and Resource Instance (340 of FIG. 3) indicates when the corresponding temperature sensor provides multiple temperature data. It performs the division role of. As shown in FIG. 4, an object of a temperature sensor in LWM2M is defined as 3303, a resource of an actual measurement value is defined as 5700, and a resource of a unit of measurement is defined as 5701.

Using this, the measured value URI of the first temperature sensor is represented by / 3303/0/5700, and the measured value URI of the second temperature sensor is represented by / 3303/1/5700. The actual first temperature reading, 37.5 degrees, is stored in the "/ 3303/0/5700 URL path". The user can obtain 3UR, a value of / 3303/0/5700, by using a GET command of a Representational State Transfer (REST) structure. In addition, the unit can be identified through the value of / 3303/0/5701.

Since LWM2M (Light Weight Machine to Machine) operates based on CoAP (Constrained Application Protocol), a REST structure, it can also use the query function of URI provided by REST. This function can be used to set the operation condition or variable of URI by using '?' And '&' delimiter at the end of URI.

For example, if you want to get the data value of the first temperature sensor to the second decimal point, you can express “/ 3303/0/5700? Point = 2”. Where point is a predefined value. If you want to use more than one query, you can expand them with '&' delimiter like “/ 3303/0/5700? Point = 2 & minus = 1 & plus = 8”.

As described above, the resource management of the meter using the DLMS is composed of Class ID + OBIS + Attribute, and the OBIS code is represented by 6 digits. In addition, the resource management of the LWM2M can be characterized by a combination of Object + Instance + Resource + Resource Instance.

Reflecting such resource management characteristics, an embodiment of the present invention proposes a new energy metering data modeling and / or management concept based on LWM2M by reflecting the characteristics of the DLMS management system. In order to define a new data resource management model based on LWM2M, it is necessary to define a new object ID with the concept of the top-level classification.

In an embodiment of the present invention, as an embodiment, a value of 40000 will be used as an object number, and the number is described to help understanding of an embodiment of the present invention, and the present invention is limited to the term. It is not clear. Assume that 40000 is not a predefined Object number.

One embodiment of the present invention proposes a method of displaying 6 OBIS codes as one string or string of numbers. OBIS 6 digits can be arranged in two digits Hex (hexadecimal) in one string. For example, 0.0.1.0.0.FF (0x00, 0x00, 0x01, 0x00, 0x00, 0xFF), which is the time information OBIS code of the electricity meter, can be expressed as a single string that is 0000010000FF. In the form, when 0.0.1.0.0.FF (000, 000, 001, 000, 000, 255) codes are arranged in a line, it can be expressed as 000000001000000255.

5 is a Light Weight Machine to Machine (LWM2M) URI structure of the first management model according to an embodiment of the present invention. Referring to FIG. 5, the first management model includes intuitive modeling and resource management in which the class ID, OBIS, and attributes of the electricity meter are matched to the instance 520, resource 530, and resource instance 540 of the LWM2M, respectively. Way.

For example, the structure (Class ID: 8, OBIS: 0.0.1.0.0.FF, Attribute: 2) used when reading time information of the electricity meter is "/ 40000/8 / 0000010000FF" when the first management model is used. It can be expressed as a LWM2M URI of the form "2/2". Here, "4000" corresponds to the object 510.

6 is a flowchart illustrating a process of executing a first management model according to an embodiment of the present invention. Through the first management model, all resources of the existing meter can be converted to the LWM2M standard management model. Referring to FIG. 6, it is determined whether the acquired data is resource data of the electricity meter (step S610).

As a result of the determination, if the resource data, the Class ID is checked and it is matched with an instance (step S620). In addition, the OBIS code is checked and matched with a Resource (step S630). In addition, the attribute is checked and matched with a resource instance (step S640). Finally, the generated Uniform Resource Identifier (URI) information is registered in the LWM2M (step S650).

The first management model provides the advantage that an intuitive conversion of the DLMS information of the electronic meter into the LWM2M standard management model is possible. However, in the resource information of the electronic meter, a plurality of attributes may exist in one OBIS code. Therefore, when using the first management model, as many URI paths as the number of attributes must be generated. That is, since the first management model scheme requires a lot of memory, a second management model may be proposed to overcome this problem.

7 is a Light Weight Machine to Machine (LWM2M) URI structure of the second management model according to another embodiment of the present invention. Referring to FIG. 7, the second management model is a model in which attribute information is transmitted using a query form to solve a problem in which multiple attributes exist in one OBIS code.

For example, the structure used to read the electricity meter's time information (Attribute 2) and time-zone (Attribute 3) [(Class ID: 8, OBIS: 0.0.1.0.0.FF, Attribute: 2) ) And (Class ID: 8, OBIS: 0.0.1.0.0.FF, Attribute: 3)] are represented by LWM2M URI of the form “/ 40000/8 / 0000010000FF? Attribute = 2 & attribute = 3” through the second administrative model. Can be. That is, two separate URIs are not required, but one URI can accommodate as many attributes as desired.

Therefore, it is possible to provide an advantage of having one converted LWM2M URI path number regardless of the number of attributes. In other words, in the case of the first management model, the number of LWM2M URI paths is required as many as the number of attributes to be read. That is, minimizing the number of URIs consumes more hardware resources such as memory.

8 is a flowchart illustrating a process of executing a second management model according to another embodiment of the present invention. Referring to FIG. 8, it is determined whether the acquired data is resource data of the electricity meter (step S810).

As a result of the determination, if the resource data, the Class ID is checked and it is matched with an instance (step S820). In addition, the OBIS code is checked and matched with a Resource (step S830). In addition, the attribute is checked and specified as a query (step S840). Finally, the generated Uniform Resource Identifier (URI) information is registered in the LWM2M (step S850).

9 is a conceptual diagram of an energy metering data management apparatus 900 according to another embodiment of the present invention. Referring to FIG. 9, the energy meter data management apparatus 900 may include a modem 920 for acquiring electronic meter data (that is, meter data) transmitted by the first to n th meter meters 930-1 to 930-n. It may be configured to include a communication terminal 910 for determining whether the electronic meter data obtained by being connected to the modem 920 is resource data, matching the resource data with LWM2M based resource data, and registering the resource data as URI information. Can be.

The communication terminal 910 is a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a server computer And so on.

The modem 920 performs communication using wireless communication or wired communication. In the case of wired communication, it may be RS485, RS232, Ethernet communication, and the wireless communication may include rDA (Infrared Data) communication, local area network (LAN), Bluetooth, LG Fidelity (LFith), WiFi (Wireless Fidelity), and NFC. (Near Field Control) and the like. In FIG. 9, the plurality of power meters 930-1 to 930-n are connected to one modem 920, but the plurality of modems 920 and the power meters 930-1 to 930-n are connected to one. A one-to-one correspondence is also possible. As the first to n th wattmeters 930-1 to 930-n, an electronic wattmeter may be used.

10 is a detailed configuration diagram of the communication terminal 910 shown in FIG. 9. Referring to FIG. 10, the communication terminal 910 determines whether the data acquired from the first to nth electricity meters 930-1 to 930-n is resource data, and when the determination result is resource data. And a matching module 1030 for matching the resource data with LWM2M based resource data, a generation module 1040 for generating LWM2M based resource data as URI information, and the like.

9 to 10 separately illustrate the communication terminal 910 and the modem 920, the communication terminal and the modem may be integrated into one device.

The “… module” described in FIG. 10 may be implemented in hardware, software, or a combination thereof. In hardware implementation, an application specific integrated circuit (ASIC), a digital signal processing (DSP), a programmable logic device (PLD), a field programmable gate array (FPGA), a processor, a controller, and a microprocessor are designed to perform the above functions. , Other electronic units, or a combination thereof. In the software implementation, the module may be implemented as a module that performs the above-described function. The software may be stored in a memory unit and executed by a processor. The memory unit or the processor may employ various means well known to those skilled in the art.

11 is a Light Weight Machine to Machine (LWM2M) URI structure of a third management model according to another embodiment of the present invention. In particular, when the third management model needs to support a plurality of power meters 930-1 to 930-n in one modem 920, it is a management model that can distinguish each power meter. As shown in FIG. 11, the class ID, OBIS, and attribute of each electricity meter are matched to the Resource 1130, Resource Instance 1140, and Query 1150 of the LWM2M, respectively. Of course, there are other object numbers 1110 and instances 1120.

12 is a flowchart illustrating a process of executing a third management model according to another embodiment of the present invention. Referring to FIG. 12, it is determined whether it is the last power meter (step S1210). If it is determined that the last meter is finished, otherwise, if not the last meter, the meter index (division number) is matched to an instance to distinguish the meter, and the meter resource check is started (step S1220).

Thereafter, if the resource data, the Class ID is checked, and this is matched with a resource (step S1240). In addition, the OBIS code is checked and matched with a resource instance (step S1250). In addition, the attribute is checked and specified as a query (step S1260). Finally, the generated Uniform Resource Identifier (URI) information is registered in the LWM2M (step S1270).

For example, a structure used when reading time information and time_zone of the x-th meter from the first to n-th meter 930-1 to 930-n attached to one modem (920 of FIG. 9) [(Class ID : 8, OBIS: 0.0.1.0.0.FF, Attribute: 2) and (Class ID: 8, OBIS: 0.0.1.0.0.FF, Attribute: 3)] are assigned to the "/ 40000 / x / 8 / 0000010000FF? attribute = 2 & attribute = 3 ”.

That is, the time information of the first power meter 930-1 may be expressed as an LWM2M URI having a form of “/ 40000/1/8 / 0000010000FF? Attribute = 2 & attribute = 3”. This management model allows the division of multiple meters and all resources of each meter to be converted to the LWM2M standard management model.

13 is a Light Weight Machine to Machine (LWM2M) URI structure of a fourth management model according to another embodiment of the present invention. Generally, the resource model of DLMS is hierarchically composed of Class ID, OBIS code, and Attribute, but the most important indicator that represents actual resource is OBIS code.

Referring to FIG. 13, the fourth management model is a model for defining a corresponding OBIS code as a resource and matching the remaining attributes with a query without using a class ID. For example, a structure used to read time information and time_zone of an x-th meter among a plurality of meters 930-1 to 930-n attached to one modem 920 [(ClassID: 8, OBIS: 0.0. 1.0.0.FF, Attribute: 2) and ClassID: 8, OBIS: 0.0.1.0.0.FF, Attribute: 3)] are defined as “/ 40000 / x / 0000010000FF? It may be expressed as an LWM2M URI in the form of attribute = 2 & attribute = 3 ”. For example, time information and time_zone information of the first electronic meter may be represented by an LWM2M URI having a form of “/ 40000/1 / 0000010000FF? Attribute = 2 & attribute = 3”. Through this management model, the classification of multiple meters based on OBIS code and all resources of each meter can be converted to LWM2M standard management model.

14 is a flowchart illustrating a process of executing a fourth management model according to another embodiment of the present invention. Referring to FIG. 14, it is determined whether it is the last power meter (step S1410). If it is determined that the last meter is finished, otherwise, if not the last meter, the power meter index (division number) is matched to an instance to distinguish the meter, and the meter resource check is started (step S1420).

Thereafter, the OBIS code is checked and matched with a resource instance (step S1440). In addition, the attribute is checked and specified as a query (step S1450). Finally, the generated Uniform Resource Identifier (URI) information is registered in the LWM2M (step S1460).

15 is a conceptual diagram illustrating an extension example with another system according to another embodiment of the present invention. Referring to FIG. 15, when the LWM2M-based data management model 1520 using the proposed DLMS-OBIS data structure 1510 is used, it may be linked with various IoT servers 1530 to 1560 without further conversion. For example, various services such as providing power billing information to the government IoT server 1530, providing power consumption form information to the artificial intelligence server 1540, and providing power demand data for each day to the big data server 1550. Development is possible. In addition, it is also possible to provide the power consumption form information to the foreign third-party server 1560. In addition, a modem management program 1570 for managing the modem is configured. Of course, the modem management program 1570 may be installed in the communication terminal.

Accordingly, the resource management model of the present invention can extend the utilization of power data limited in the existing power system to various fields.

In addition, the implementation of energy metering data modeling and management according to an embodiment of the present invention is any of the terminals constituting the system, such as an electronic meter, modem, gateway (Gateway), DCU (Data Concentration Unit), AMI (Ambient Intelligence) server It may be made in one or more terminals. However, given the characteristics of the DLMS protocol, which has a high overhead, it may be implemented in an electronic meter that generates DLMS packets or a modem that communicates closest to the electronic meter.

In addition, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in a program instruction form that can be executed by various computer means and recorded in a computer-readable medium. The computer readable medium may include program (instruction) code, data file, data structure, etc. alone or in combination.

The program (instruction) codes recorded on the medium may be those specially designed and constructed for the present invention, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROM, DVD, Blu-ray, etc., and ROM, RAM ( Semiconductor memory devices specifically configured to store and execute program (command) code, such as RAM), flash memory, and the like.

Here, examples of the program (instruction) code include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

900: energy metering data management device
910: communication terminal
920: modem
930-1 to 930-n: first to n th power meters

Claims (17)

A determination module 1020 that determines whether data acquired from at least two electronic meters is first resource data;
A matching module 1030 for matching the first resource data with second resource data based on a light weight machine to machine (LWM2M); And
And a generation module 1040 for generating the second resource data as Uniform Resource Identifier (URI) information.
The first resource data includes at least two or more combinations of a class ID, an object identification system (OBIS) code, and a division number for distinguishing the two or more electronic meters.
The energy meter data management device, characterized in that the data of the electronic meter is Device Language Message Specification (DLMS) information.
delete The method of claim 1,
The OBIS code is an energy metering data management device, characterized in that expressed in decimal or hexadecimal.
delete The method of claim 1,
The matching classifies the resource data of the LWM2M into a class ID indicating a large classification of data resources of the electronic meter, an OBIS code indicating a metering value and various setting values of the data resource, and an attribute indicating an actual value of the data resource. The energy metering data management device, characterized in that each matching to an instance (Resource), a resource (Resource) indicating the meaning of the resource data, and a resource instance (Resource Instance) indicating the division of the resource data.
The method of claim 5, wherein
And the URI information comprises an object, an instance, a resource, and a resource instance in order of a major classification of data resources.
The method of claim 1,
The matching matches a class ID, an OBIS code, and an attribute of the electronic meter with an instance, a resource, and a query of LWM2M, respectively. Energy metering data management device, characterized in that the plurality to accommodate the property of.
The method of claim 7, wherein
And the URI information comprises an object number, an instance, a resource, and a query in order.
The method of claim 1,
The matching matches a class ID, an OBIS code, and an attribute of the electronic meter with a resource, a resource instance, and a query of an LWM2M, respectively. Energy metering data management device, characterized in that a plurality to accommodate a plurality of attributes.
The method of claim 9,
The URI information is an energy metering data management apparatus, characterized in that in the order of the object (Resource), Resource (Resource Instance) and Query (Query).
delete delete A determination step of determining, by the determination module 1020, whether data acquired from two or more electronic meters is first resource data;
A matching step of matching the first resource data with LWM2M-based second resource data by the matching module 1030; And
And generating, by the generation module 1040, the second resource data as URI information, wherein the first resource data includes a class ID, an object identification system (OBIS) code, and a classification for distinguishing the two or more electronic meters. A combination of at least two or more of the numbers,
Energy meter data management method, characterized in that the data of the electronic meter is Device Language Message Specification (DLMS) information.
delete The method of claim 13,
The OBIS code is an energy metering data management method, characterized in that expressed in decimal or hexadecimal.
delete A computer-readable storage medium storing program code for executing the energy metering data management method according to any one of claims 13 and 15.

Images