KR20120133623A - Method for meter registration - Google Patents

Abstract

PURPOSE: A meter registration method is provided to shorten the time required for registering a newly connected meter as only an unregistered meter responds to a registration request according to a register flag by defining the register flag. CONSTITUTION: A data concentration device transmits discovery request packets to a first meter, a second meter, a third meter, and a fourth meter by broadcasting the discovery request packets(S100). The first meter transmits a discovery response packet including a serial number and a meter address of the first meter to the data concentration device through a first time slot(S110). The fourth meter transmits a discovery response packet including a serial number and a meter address of the fourth meter to the data concentration device through a second time slot(S120). The data concentration device stores serial numbers and meter addresses of the first meter and the fourth meter included in the discovery response packets received from the first and the fourth response packets in order to register an unregistered meter(S130). [Reference numerals] (AA) Data concentration device; (BB) First meter(unregistered); (CC) Second meter(registered); (DD) Third meter(registered); (EE) Fourth meter(unregistered); (S100) Broadcasting a discovery request packet; (S110) Discovery response packet(a first time slot); (S120) Discovery response packet(a second time slot); (S130) Registering an unregistered meter

Description

How to register a meter {METHOD FOR METER REGISTRATION}

The present invention relates to a meter registration method. More particularly, the present invention relates to a meter registration method for registering an unregistered meter among meters connected to a data intensive device.

RS-485 network, which is a collective connection method, is connected to a single communication line such as a bus or daisy chain. In order to detect a collision or a network in communication, the corresponding function must be granted in a protocol higher than the data link layer.

Electronic meter for remote metering uses DLMS / COSEM (Device Language Message Specification / Companion Specification for Energy Metering).

In this case, when the meters are connected to the RS-485 network, the connected device that connects the meter, such as a data concentrator (DCU) and a modem, can access the meter only if it has the address of the connected meter according to the DLMS / COSEM method in advance. have.

Conventionally, a modem selects the addresses of responding meters by calling all possible addresses of meters connected to the RS-485 network, and then registers the newly connected meters.

However, according to the related art, each time a user registers a newly connected meter, the address of all the registered meters must be called and a response is waited. Therefore, a long time is required to register a newly connected meter.

In addition, since a modem, a processor, a memory, driving software, and the like must be provided to implement the conventional method in the modem, there is a problem in that the cost of the modem increases.

SUMMARY OF THE INVENTION An object of the present invention is to provide a meter registration method capable of responding to a registration request only in a newly connected meter except for already registered meters when registering an address of a newly connected meter in a data intensive device.

According to an aspect of the present invention, there is provided a method of registering a meter according to a HDLC protocol, by broadcasting a first discovery request packet for searching for a meter not registered in a data intensive device among a plurality of meters conforming to a DLMS protocol. Receiving a plurality of discovery response packets through different time slots from some of the unregistered meters, and registering some unregistered meters by storing a meter address and a meter serial number included in each of the plurality of discovery response packets And sending a set request to some unregistered meters to update a register flag of each of the some unregistered meters.

Meter registration method according to another aspect of the present invention is to check the register flag stored in advance according to the discovery request packet received from the data intensive device to determine whether to register with the data intensive device, if the result of the registration is unregistered one Using the above random number, transmitting a discovery response packet including a meter address and a meter serial number previously stored in any one of a plurality of preset time slots to a data concentrator according to the HDLC protocol, and then data concentration Updating the register flag in accordance with a setup request received from the device.

According to a feature of the present invention, by defining a register flag indicating whether or not to register with the meter, so that only the unregistered meter responds to the registration request according to the register flag, it is possible to shorten the time required to register the newly connected meter. There is.

In addition, by having the unregistered meters transmit the meter information through different time slots, there is an effect that can avoid packet collision between the meters.

1 is a diagram showing the configuration of a meter registration system according to an embodiment of the present invention.
2 is a diagram illustrating a meter registration method according to an embodiment of the present invention.
3 is a diagram illustrating a meter registration method performed by a data intensive device according to an embodiment of the present invention.
4 is a diagram illustrating a meter registration method performed by a meter according to an embodiment of the present invention.
5 is a diagram illustrating a structure of an HDLC packet corresponding to an HDLC protocol according to an embodiment of the present invention.
6 is a diagram illustrating an instruction list of a control field according to an embodiment of the present invention.
7 is a diagram illustrating a structure of a discovery request packet according to an embodiment of the present invention.
8 is a diagram illustrating a structure of a discovery response packet according to an embodiment of the present invention.
9 is a diagram illustrating a data table of a meter according to an embodiment of the present invention.
10 is a diagram illustrating a data format table of a register flag according to an embodiment of the present invention.
11 is a diagram illustrating a data format table of random numbers according to a first embodiment of the present invention.
12 is a diagram illustrating a data format table of random numbers according to a second embodiment of the present invention.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. Here, the repeated description, the notification function that may unnecessarily obscure the gist of the present invention, and the detailed description of the configuration will be omitted. Embodiments of the present invention are provided to more completely explain the present invention to those skilled in the art. Accordingly, the shape and size of elements in the drawings may be exaggerated for clarity.

Hereinafter, a meter registration method according to an embodiment of the present invention will be described with reference to the drawings.

First, a meter registration system according to an embodiment of the present invention will be described with reference to FIG. 1.

1 is a diagram showing the configuration of a meter registration system according to an embodiment of the present invention.

As shown in FIG. 1, the meter registration system 100 includes a data concentration unit (hereinafter referred to as a “DCU”) 110 and a plurality of meters 130, and a plurality of meters. It is a system for registering the meter not registered in the data intensive device 110 among the data intensive device 110. In this case, 32 meters may be connected to one data concentrator 110, and the plurality of meters 130 may include a first meter 131, a second meter 132, a third meter 133, and a fourth meter. Meter 134 may be included.

Here, the data intensive device 110 and the plurality of meters 130 are connected in a multipoint through an RS-485 (hereinafter referred to as RS-485) network, and the data intensive device 110 The protocol between the plurality of meters 130 may follow a Device Language Message Specification (hereinafter, referred to as DLMS) protocol corresponding to a communication protocol for remote meter reading.

In addition, the data intensive device 110 and the plurality of meters 130 transmit packets according to a high-level data link control (hereinafter referred to as HDLC) protocol, which is a sub-protocol of the DLMS protocol. Can be.

The data concentrator 110 broadcasts a discovery request packet for searching for an unregistered meter among the plurality of meters 110 according to a preset protocol command and transmits the discovery request packet to the plurality of meters. Transmit to 110. Here, the data intensive device 110 may generate a discovery request packet according to a discovery request message corresponding to a preset protocol command.

In addition, the data intensive device 110 registers the unregistered meter by using a discovery response packet received from the unregistered meter. Here, the data intensive device 110 may complete registration for an unregistered meter by storing a meter address and a meter serial number included in the discovery response packet.

In addition, the data intensive device 110 transmits a request for setting a register flag to a meter that is registered by the discovery response packet. Here, the data intensive device 110 may access a registered meter and update a register flag indicating whether the corresponding meter is registered.

Each of the plurality of meters 130 checks a register flag of the corresponding meter according to the discovery request packet received from the data intensive device 110 to determine whether the corresponding meter is registered or unregistered with respect to the data intensive device 110.

In addition, each of the plurality of meters 130 unicast the discovery response packet for requesting registration with respect to the meter according to a preset protocol command, if the meter is determined to be unregistered, the data intensive device Transmit to 110. Here, each of the plurality of meters 130 may generate a discovery response packet using a meter address and a meter serial number of the corresponding meter according to a discovery response message corresponding to a preset protocol command.

In addition, each of the plurality of meters 130 updates the register flag of the corresponding meter according to a setting request received from the data intensive device 110. Here, the register flag may indicate registration or non-registration of the corresponding meter, the register flag of the registered meter may have a value of "1", and the register flag of the unregistered meter may have a value of "0".

Next, a method of registering a non-registered meter by a meter registration system according to an embodiment of the present invention will be described with reference to FIG. 2.

2 is a diagram illustrating a meter registration method according to an embodiment of the present invention.

As shown in FIG. 2, first, the data concentrator 110 broadcasts a discovery request packet and transmits the discovery request packet to the first meter 131, the second meter 132, the third meter 133, and the first meter. 4 is transmitted to the meter 134 (S100).

Next, the first meter 131 transmits a discovery response packet including a meter address and a meter serial number of the first meter 131 to the data concentrator 110 through the first time slot (S110).

Thereafter, the fourth meter 134 transmits the discovery response packet including the meter address and the meter serial number of the fourth meter 134 to the data concentrator 110 through the second time slot (S120).

Next, the data concentrator 110 may include a meter address of each of the first meter 131 and the fourth meter 134 included in discovery response packets received from the first meter 131 and the fourth meter 134. Register the unregistered meter by storing the meter serial number (S130).

Here, the first meter 131 and the fourth meter 134 are meters that are not registered in the data concentrator 110, and the second meter 132 and the third meter 133 are registered in the data concentrator 110. Since the first meter 131 and the fourth meter 134 only transmit the discovery response packet to the data concentrator 110 in response to the discovery request packet.

As such, by allowing only the unregistered meter to respond, the time required for registration can be shortened as compared with the conventional method of registering a non-registered meter by receiving a response from all meters connected to the data intensive device 110 regardless of whether or not it is registered. It works.

In addition, since the first meter 131 and the fourth meter 134 transmit the discovery response packet through different time slots, packet collision between the first meter 131 and the fourth meter 134 may be avoided. It has an effect.

Next, a meter registration method performed by the data intensive device of the meter registration system according to an embodiment of the present invention will be described with reference to FIG. 3.

3 is a diagram illustrating a meter registration method performed by a data intensive device according to an embodiment of the present invention.

As shown in FIG. 3, first, the data concentrator 110 may also refer to an order indicating number (OIN) hereinafter according to a discovery request message to search for an unregistered meter among all meters connected on a network. In operation S200, a discovery request packet including an order indication number OIN is generated. Here, the data intensive device 110 may determine the number of order indications OIN according to the maximum number of connections of the meter connected to the data intensive device 110, and the number of order indications OIN may be determined by an unregistered meter. Can be used as a threshold when determining.

For example, when the maximum number of connections is 32, the data intensive device 110 may determine the order indication number OIN as "16" corresponding to half of the maximum number of connections.

Next, the data intensive device 110 transmits the discovery request packet to the plurality of meters 130 (S210).

Thereafter, the data intensive device 110 receives discovery response packets from unregistered meters for a predetermined time (S220). Here, the data intensive device 110 may receive discovery response packets for a time up to 1000 milliseconds after transmitting the search request packet. In this case, each discovery response packet may include a meter address and a meter serial number.

For example, the data concentrator 110 receives the first discovery response packet including the meter address and the meter serial number of the first meter 131 from the first meter 131, and then the fourth meter 134. From the fourth discovery response packet including the meter address of the fourth meter 134 and the meter serial number.

Next, the data intensive device 110 registers unregistered meters by storing a meter address and a meter serial number of each of the unregistered meters included in the discovery response packets (S230).

For example, the data concentrator 110 stores a meter address and a meter serial number of the first meter 131 included in the first discovery response packet to register the meter with respect to the first meter 131. Meter registration of the fourth meter 134 may be performed by storing the meter address and the meter serial number of the fourth meter 134 included in the 4 search response packet.

Thereafter, the data intensive device 110 transmits a setting request for updating a register flag of each registered meters to the registered meters (S240).

Here, the data intensive device 110 may repeat the procedure according to the meter registration method illustrated in FIG. 3 a plurality of times so that all unregistered meters included in the plurality of meters 130 may be registered.

In addition, the data intensive device 110 repeats the procedure according to the meter registration method illustrated in FIG. 3 a plurality of times, and then includes a plurality of discovery request packets including an order indication number OIN having a value greater than the maximum number of connections. By sending to the meters 130, all unregistered meters can be registered.

Next, a meter registration method performed by a meter in a meter registration system according to an embodiment of the present invention will be described with reference to FIG. 4.

4 is a diagram illustrating a meter registration method performed by a meter according to an embodiment of the present invention.

As shown in FIG. 4, first, each of the plurality of meters 130 receives a discovery request packet including an order indication number OIN from the data intensive device 110 (S300). Here, since the plurality of meters 130 perform the meter registration method according to the same procedure, only the first meter 131 will be described below, but the plurality of meters 130 also perform the same procedure. In addition, a case in which the maximum number of connections of the meter that can be connected to the data intensive device 110 is 32 will be described.

Next, the first meter 131 checks the value of the register flag of the first meter 131 according to the discovery request packet to determine whether the first meter 131 is registered in the data concentrator 110 (S305). . Here, the first meter 131 may determine the first meter 131 as an unregistered meter if the register flag has a value of "0", and the first meter 131 if the register flag has a value of "1". Can be determined as a registered meter.

As a result of determining whether the first meter 131 is registered, when the first meter 131 is an unregistered meter that is not registered, the first meter 131 is also called a first random number (Random Number 1, hereinafter referred to as 'RN1'). ) Is generated (S310). Here, the first meter 131 may determine the first random number RN1 from 1 to 32 integers according to the maximum number of connections of the meter connected to the data concentrator 110.

Thereafter, the first meter 131 compares the first random number RN1 with the order indication number OIN to determine whether the first random number RN1 is smaller than the order indication number OIN (S315). Here, the order indication number OIN may correspond to “16” corresponding to half of the maximum connection number of the meter connected to the data concentrator 110.

As a result of determining whether the first random number RN1 is smaller than the order indication number OIN, when the first random number RN1 is smaller than the order indication number OIN, the first meter 131 determines the second random number 2 (Random Number 2). , Hereinafter also referred to as 'RN2' (S320). Here, the first meter 131 may determine the second random number RN2 among integers of 1 or more and 32 or less.

Next, the first meter 131 compares the second random number RN2 with the order indication number OIN, and determines whether the second random number RN2 is smaller than the order indication number OIN (S325).

As a result of determining whether the second random number RN2 is smaller than the order indication number OIN, when the second random number RN2 is smaller than the order indication number OIN, the first meter 131 determines the third random number 3. , Also referred to as 'RN3' below (S330). Here, the first meter 131 may determine the third random number RN3 among integers of 1 or more and 32 or less.

Thereafter, the first meter 131 compares the third random number RN3 with the order indication number OIN to determine whether the third random number RN3 is smaller than the order indication number OIN (S335).

As a result of determining whether the third random number RN3 is smaller than the order indication number OIN, when the third random number RN3 is smaller than the order indication number OIN, the first meter 131 determines the fourth random number 4. , Hereinafter also referred to as 'RN4' (S340). Here, the first meter 131 may determine the fourth random number RN4 among integers of 1 or more and 5 or less according to the preset number of time slots.

Next, the first meter 131 determines the response delay time using the fourth random number to respond to the data intensive device 110 through any one of a plurality of preset time slots (S345). Here, the first meter 131 may respond through a specific time slot in response to the response delay time, thereby avoiding a packet collision between the first meter 131 and another metering period.

Subsequently, the first meter 131 concentrates the discovery response packet including the meter address and the meter serial number of the first meter 131 through one of the time slots according to the determined response delay time. Transmitting to the device 110 (S350).

Next, the first meter 131 receives a setting request for updating the register flag of the first meter 131 from the data concentrator 110 (S355). Here, when the registration for the first meter 131 is completed, the data intensive device 110 may transmit a setting request for requesting to update a register flag of the first meter 131.

Thereafter, the first meter 131 updates the register flag according to the received setting request (S360). Here, the first meter 131 may update the value of the register flag from "0" to "1", and may not respond to the discovery request packet received from the data intensive device 110.

Meanwhile, as a result of determining whether the first meter 131 is registered, when the first meter 131 is a registered registered meter, the first meter 131 ends the procedure according to the meter registration method.

On the other hand, as a result of determining whether the first random number RN1 is smaller than the order indication number OIN, when the first random number RN1 is not smaller than the order indication number OIN, the first meter 131 determines whether the first random number RN1 is smaller than the order indication number OIN. Terminate the procedure accordingly.

On the other hand, as a result of determining whether the second random number RN2 is smaller than the order indication number OIN, and when the second random number RN2 is not smaller than the order indication number OIN, the first meter 131 enters the meter registration method. Terminate the procedure accordingly.

On the other hand, as a result of determining whether the third random number RN3 is smaller than the order indication number OIN, and when the third random number RN3 is not smaller than the order indication number OIN, the first meter 131 enters the meter registration method. Terminate the procedure accordingly.

As described above, when the meter 131 compares the random numbers generated a plurality of times with the order indication number OIN corresponding to the threshold, the meter registration system 100 sets the number of meters in response to the discovery request packet in a preset time. The number of slots may not be exceeded.

That is, when the maximum number of connections of the meters connected to the data concentrator 110 is 32, according to the first comparison procedure for the random number and the order indication number generated in the meter, only 16 meters are probabilistic in the next comparison procedure. In accordance with the second comparison procedure for random numbers and sequence marks generated by the meter, only up to eight meters are passed on to the next comparison procedure, and the third for random numbers and sequence marks generated by the meter. According to the comparison procedure, only up to four meters remain.

Accordingly, by comparing the random numbers generated multiple times with the order indication number (OIN), it is possible to prevent the meters responding to the data intensive device 110 from overlapping one time slot to avoid packet collisions between the meters. It can be effective.

Next, a packet structure corresponding to the HDLC protocol according to an embodiment of the present invention will be described with reference to FIG. 5.

5 is a diagram illustrating a structure of an HDLC packet corresponding to an HDLC protocol according to an embodiment of the present invention.

As shown in FIG. 5, the HDLC packet 200 includes a start flag field (Flag ₁ ) 210, a frame format field (Frame Format) 220, a destination address field (hereinafter referred to as 'Dest. Address'). 230), source address field (hereinafter referred to as 'Src. Address') 240, control field (250), header check sequence field (hereinafter referred to as 'HCS') 260, information field (Information) 270, frame check sequence field (hereinafter referred to as 'FCS') 280, and end flag field (Flag ₂ ) 290 Include.

The start flag field Flag ₁ 210 is a field indicating the start of the HDLC packet 200.

The frame format field 220 includes information about the frame format of the HDLC packet 200.

The destination address field (Dest. Address) 230 includes the address of the receiving device of the HDLC packet 200.

The source address field (Src. Address) 240 includes the address of the transmitting device of the HDLC packet 200.

The control field 250 includes a protocol command reserved in advance. Herein, the control field 250 may include a discovery request message or a discovery response message.

The header check sequence field (HCS) 260 is a field inserted for cyclic redundancy checking (hereinafter also referred to as 'CRC').

The information field 270 is a field into which information or data to be transmitted to the receiving device of the HDLC packet 200 is inserted.

The frame check sequence field (FCS) 280 is a field inserted for error detection and correction at the receiving device of the HDLC packet 200.

The end flag field (Flag ₂ ) 290 is a field indicating the end of the HDLC packet 200.

Next, a method of designating a protocol command for registering a meter according to an embodiment of the present invention will be described with reference to FIG. 6.

6 is a diagram illustrating an instruction list of a control field according to an embodiment of the present invention.

As shown in FIG. 6, the command list 300 is a list of commands not reserved in the control field of the DLMS protocol.

Herein, the command corresponding to the discovery request message may be designated in the command list 300 and the command corresponding to the discovery response message may be specified so that the discovery request message and the discovery response message do not overlap.

For example, the first command (0x9F) 310 included in the command list 300 may be designated as a command corresponding to the discovery request message, and the second command (0xAF) included in the command list 300 ( 310 may be designated as a command corresponding to the discovery response message.

Next, a structure of a discovery request packet according to an embodiment of the present invention will be described with reference to FIG. 7.

7 is a diagram illustrating a structure of a discovery request packet according to an embodiment of the present invention.

As shown in FIG. 7, the discovery request packet 400 includes a start flag field (Flag ₁ ) 410, a frame format field (Frame Format) 420, a destination address field (Dest. Address) 430, a source. Address field (Src. Address) 440, control field (Control) 450, header check sequence field (HCS) 460, information field (Information) 470, frame check sequence field (FCS) 480 , And an end flag field (Flag ₂ ) 490.

The start flag field (Flag ₁ ) 410 includes a field value indicating the start of the discovery request packet 400, that is, "0x7E".

The frame format field (Frame Format) 420 includes field values indicating information on the frame format of the discovery request packet 400, that is, "0xA0" and "0x18".

The destination address field (Dest. Address) 430 includes field values indicating the address of the meter receiving the discovery request packet 400, that is, "0xFEFE" and "0xFEFF". Here, the destination address field (Dest. Address) 430 may have a field value corresponding to all meters connected to the data concentrator 110.

The source address field (Src. Address) 440 includes a field value indicating the address of the data concentrator 110 that transmits the discovery request packet 400, that is, a "DCU address."

The control field 450 includes a field value corresponding to the discovery request message, that is, "0x9F".

The header check sequence field (HCS) 460 includes a field value for cyclic redundancy checking (hereinafter also referred to as 'CRC'), that is, a header checksum.

The information field 470 includes an order indicating number determined according to the maximum number of connections of the meter connected to the data intensive device 110. Herein, the information field 470 may have “16” as an order indication number when the maximum number of connections of the meter connected to the data intensive device 110 is 32.

The frame check sequence field (FCS) 480 includes a field value for error detection and correction for the discovery request packet 400, that is, a frame checksum.

The end flag field Flag ₂ 490 includes a field value indicating the end of the discovery request packet 400, that is, "0x7E".

Next, a structure of a discovery response packet according to an embodiment of the present invention will be described with reference to FIG. 8.

8 is a diagram illustrating a structure of a discovery response packet according to an embodiment of the present invention.

As illustrated in FIG. 8, the discovery response packet 500 includes a start flag field (Flag ₁ ) 510, a frame format field (Frame Format) 520, a destination address field (Dest. Address) 530, a source. Address field (Src. Address) 540, control field (Control) 550, header check sequence field (HCS) 560, information field (Information) 570, frame check sequence field (FCS) 580 , And an end flag field (Flag ₂ ) 590.

The start flag field (Flag ₁ ) 510 includes a field value indicating the start of the discovery response packet 500, that is, "0x7E".

The frame format field (Frame Format) 520 includes field values indicating information on the frame format of the discovery response packet 500, that is, "0xA0" and "0x18".

The destination address field (Dest. Address) 530 includes a field value indicating the address of the data concentrator 110 that receives the discovery response packet 500, that is, a "DCU address".

The source address field (Src. Address) 540 includes a field value indicating the address of the meter sending the discovery response packet 500, that is, "Meter address."

The control field 550 includes a field value corresponding to the discovery response message, that is, "0xAF".

The header check sequence field (HCS) 560 includes a field value for cyclic redundancy checking (hereinafter also referred to as 'CRC'), that is, a header checksum.

The information field 570 includes a meter serial number of the corresponding meter.

The frame check sequence field (FCS) 580 includes a field value for error detection and correction for the discovery response packet 500, that is, a frame checksum.

The end flag field (Flag ₂ ) 590 includes a field value indicating the end of the discovery response packet 500, that is, "0x7E".

Next, a data table of a meter according to an embodiment of the present invention will be described with reference to FIGS. 9 to 12.

9 is a diagram illustrating a data table of a meter according to an embodiment of the present invention.

As shown in FIG. 9, each of the plurality of meters 130 stores a data table 600 in which a format, a configuration method, and a usage method of all data that the meter should hold.

The data table 600 includes a data classification 610, an object identification system code (hereinafter referred to as an 'OBIS code') 620 and an interface class according to the COmpanion Specification for Energy Metering (COSEM). (Interface Class) 630.

Here, the OBIS code 620 follows the Object Identification System (hereinafter also referred to as 'OBIS'), and has six digits, namely "A", "B", "C", "D", and "E". And "F". At this time, OBIS gives recognition codes to the operation, control, and setting of the meter as well as all power meter data such as power amount, voltage, current, etc. to acquire the meter value remotely or to manage and control the meter. Corresponds to

In addition, the interface class 630 represents a type of data in which the format, composition, and usage of the data are formalized according to COSEM, and class ID for classifying a class of similar objects. Has

As such, all data in the meter must have an interface class 630 defined for each data category 610 and have an OBIS code 620 so that the data can be accessed from inside or outside the meter. .

For example, if the data classification 610 is a register flag, the OBIS code 620 may be "A", "B", "C", "D", "E" and "F". Is configured to correspond to "0", "96", "96", "1", "14" and "255", respectively, and the interface class 630 has a class id of " 1 ", the version (version) is defined as" 0 "can be defined as" Data ".

In addition, when the data classification 610 is the first random number (Random Number 1), the OBIS code 620 is "A", "B", "C", "D", "E" and "F". Is configured to correspond to "0", "96", "96", "1", "15" and "255", respectively, and the interface class 630 has a class id of " 1 ", the version (version) is defined as" 0 "can be defined as" Data ".

In addition, when the data classification 610 is the second random number, the OBIS code 620 is "A", "B", "C", "D", "E" and "F". Is configured to correspond to "0", "96", "96", "1", "16", and "255", respectively, and the interface class 630 has a class id of " 1 ", the version (version) is defined as" 0 "can be defined as" Data ".

In addition, when the data classification 610 is a third random number, the OBIS code 620 is "A", "B", "C", "D", "E" and "F". Is configured to correspond to "0", "96", "96", "1", "17" and "255", respectively, and the interface class 630 has a class id of " 1 ", the version (version) is defined as" 0 "can be defined as" Data ".

In addition, when the data classification 610 is the fourth random number, the OBIS code 620 is "A", "B", "C", "D", "E" and "F". Is configured to correspond to "0", "96", "96", "1", "18", and "255", respectively, and the interface class 630 has a class id of " 1 ", the version (version) is defined as" 0 "can be defined as" Data ".

10 is a diagram illustrating a data format table of a register flag according to an embodiment of the present invention.

As shown in FIG. 10, the data type table 700 includes an interface class 710 for a register flag, data attributes 720, a data type 730, and a data minimum value. (Min) 740 and data maximum value Max 750.

Here, according to the data type table 700, the register flag may be defined as an interface class 710 as "Data". Here, when the interface class 710 is defined as "Data", the class ID Class_id may be defined as "1", and the version may be defined as "0".

In addition, according to the data type table 700, a data type 730, a data minimum value Min 740, and a data maximum value Max 750 are defined for each data attribute 720. do.

For example, when the data attributes 720 are "logical_name", the data type 730 may be defined as "octet-string". In addition, when the data attributes 720 is "value", the data type 730 is defined as "boolean", and the data minimum value Min 740 indicates that the meter is an unregistered meter. Defined as "0", the data maximum value (Max) 750 may be defined as "1" indicating that the meter is a registered meter.

11 is a diagram illustrating a data format table of random numbers according to a first embodiment of the present invention.

As shown in FIG. 11, the data type table 800 includes an interface class 810 for random numbers, data attributes 820, a data type 830, and a data minimum value ( Min) 840 and data maximum value 850.

Here, according to the data type table 800, the random number may be defined as an interface class 810 as "Data". Here, when the interface class 810 is defined as "Data", the class ID Class_id may be defined as "1", and the version may be defined as "0".

In addition, according to the data type table 800, a data type 830, a data minimum Min, and a data maximum 850 are defined for each data attribute 820. do.

For example, when the data attributes 820 are "logical_name", the data type 830 may be defined as "octet-string". In addition, when the data attributes 820 is "value", the data type 830 is defined as "integer", and the data minimum value Min 840 is defined as "1". The data maximum value 850 may be defined as “32” corresponding to the maximum number of connections of the meter connected to the data intensive device 110.

12 is a diagram illustrating a data format table of random numbers according to a second embodiment of the present invention.

As shown in FIG. 12, the data type table 900 includes an interface class 910 for random numbers, data attributes 920, a data type 930, and a data minimum value ( Min) 940 and data maximum (Max) 950.

Here, according to the data type table 900, the random number may be defined as an interface class 910 as "Data". Here, when the interface class 910 is defined as "Data", the class ID Class_id may be defined as "1", and the version may be defined as "0".

In addition, according to the data type table 900, a data type 930, a data minimum Min, and a data maximum 950 are defined for each data attribute 920. do.

For example, when the data attributes 920 is "logical_name", the data type 930 may be defined as "octet-string". In addition, when the data attributes 920 is "value", the data type 930 is defined as "integer", the data minimum value Min 940 is defined as "1", The data maximum value Max 950 may be defined as “5” corresponding to the number of preset time slots.

As described above, an optimal embodiment has been disclosed in the drawings and specification. Although specific terms have been employed herein, they are used for purposes of illustration only and are not intended to limit the scope of the invention as defined in the claims or the claims. Therefore, those skilled in the art will understand that various modifications and equivalent other embodiments are possible therefrom. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

100: meter registration system
110: data intensive device
130-134: Meter
200: HDLC packet
300: command list
400: discovery request packet
500: discovery response packet
600: data table
700, 800, 900: Data Type Tables

Claims (13)

Broadcasting, according to the HDLC protocol, a first discovery request packet for searching for a meter not registered in the data intensive device among the plurality of meters conforming to the DLMS protocol;
Receiving a plurality of discovery response packets through different time slots from unregistered meters of some of the plurality of meters;
Registering the plurality of unregistered meters by storing a meter address and a meter serial number included in each of the plurality of discovery response packets; And
And sending a request for setting to update a register flag of each of the some unregistered meters to the some unregistered meters. The method according to claim 1,
The register flag is
Meter registration method indicating whether or not to register the data intensive device. The method according to claim 2,
The first discovery request packet is
And a threshold for ensuring that the number of meters responsive to the first discovery request packet does not exceed a number of a plurality of preset time slots. The method according to claim 3,
The threshold is
Meter registration method is determined according to the maximum number of connections of the meter connected to the data intensive device. The method of claim 4,
The threshold is
Meter registration method having a value less than the maximum number of connections. The method of claim 4,
After transmitting the setup request to the plurality of unregistered meters,
Sending a second discovery request packet to the plurality of meters including a threshold having a value greater than the maximum number of connections; And
And registering the remaining unregistered meter by using a discovery response packet received from the remaining unregistered meter except for the some unregistered meter among the plurality of meters. The method according to claim 1,
Connecting to the some unregistered meters via an object recognition system code (OBIS code) and updating a register flag of each of the some unregistered meters. Determining whether to register the data intensive device by checking a register flag stored in advance according to a discovery request packet received from the data intensive device;
If it is determined that the registration is not registered, the discovery response packet including a meter address and a meter serial number previously stored in any one of a plurality of preset time slots using one or more random numbers is detected according to the HDLC protocol. Transmitting to a data intensive device; And
And updating the register flag according to a setting request received from the data intensive device. The method according to claim 8,
The step of transmitting the discovery response packet to the data concentrator
And transmitting the discovery response packet to the data intensive device through a time slot corresponding to the random number among the plurality of time slots. The method according to claim 9,
The step of transmitting the discovery response packet to the data intensive device through the time slot corresponding to the random number is
Determining a response delay time using the random number; And
And transmitting the discovery response packet to the data intensive device after the response delay time has elapsed. The method according to claim 8,
The step of transmitting the discovery response packet to the data concentrator
Determining whether to respond to the discovery request packet by comparing a threshold included in the discovery request packet with a first random number; And
And sending a discovery response packet to the data intensive device through a time slot corresponding to a second random number of the plurality of time slots when responding according to a result of the determination of the response. The method of claim 11,
Determining whether or not the response
And, when responding to the discovery request packet, determine whether the response is determined by comparing the threshold with the first random number to avoid packet collision in the one time slot. The method of claim 12,
The threshold is
Determined according to the maximum number of connections of the meter connected to the data concentrator,
The first random number is
Meter registration method is generated with a value less than the maximum number of connections.

Images