TWI392317B - Multi-protocol network registration and address resolution - Google Patents

Description

Network registration and address resolution of multiple protocols

The present invention relates to utility networks, and more particularly to a system and method for operating a utility network management system for network infrastructure registration of devices associated with merchandise delivery provided by utilities. And address resolution for such a device.

Cross-references to related applications

This application is a continuation-in-part of U.S. Patent Application Serial No. 12/127,601, filed on March 27, 2008, the disclosure of which is incorporated herein in Combined reference.

The American National Standards Institute (ANSI) has developed a range of standards and associated communication protocols to enable electronic communication of data generated by utility meters such as power meters. Similarly, communication protocols have been developed for communication with distribution automation (DA) devices for utility service delivery. The invention disclosed herein addresses addressing, address resolution, and the infrastructure needed to provide a wide range of network services supported by these standards.

For example, ANSI C12.19 defines the format of meter data and the table structure that contains such data. Earlier versions of the ANSI metering protocol provided media related mechanisms to interface with meters conforming to the ANSI C12.19 standard. Two of these earlier versions are closely related to the context of the present invention: ANSI C12.18 (or PSEM) is designed to interface a meter to a serial transmission port. It takes into account the original protocol operator (or "operation") group to allow program programming queries (ie, "read") and program planning (ie, "write") of the meter. This interface was originally designed for hand-held devices, but is used by non-standardized groups of network-connected meter communication modules.

ANSI C12.18, extended by ANSI C12.21, provides a meter interface through a data machine that communicates over the telephone system.

The newer standard C12.22 was developed in the form of a utility metering industry to ignore the complexity of several different network connection technologies. For example, many GPRS and CDMA1XRTT cellular technologies have been widely used, as are some limited-scale fixed-line connection technologies. The C12.22 communication protocol developed well before sharing the large-scale fixed-line concept for residential metering.

Regardless of any ignorance or support on the physical layer (L1) in the OSI network model, the C12.22 standard must maintain the agnostic nature of the data link (L2) and network (L3) layers. To this end, C12.22 will provide one of the options for addressing, address resolution, maintenance state, fragment/reassembly, and application layer path selection on the application layer (L7), among other features. For these useful services and applications, one of them must resolve the lower-level network connection address to use a device that conforms to C12.22 to C12.19 to deliver the frame. In a monotonous "peer-to-peer" cellular network (for example, GPRS or CDMA1XRTT), this may be a simple process: in one registration, connect an IP address to a C12.22 application layer address (ie, a C12.22 apTitle). And in smaller networks with built-in classes (or constraints), this processing is straightforward.

However, C12.22 is not designed for metrology scheduling of large-scale networked products (for example, AMR/AMI and building internal networks); it is not highly dynamic for the basic network infrastructure. The environment is designed.

In the field of distribution automation, communication has been developed in utility service delivery and utilizing communication with distribution automation (DA) devices.

For example, regardless of where the communications network, MODBUS ^® protocol to define a controller recognized and the use of message structure. MODBUS describes the processing used by one of the controllers, such as the Monitoring and Data Capture (SCADA) system, to request access by another device, such as a DA device. Furthermore, MODBUS shows how the SCADA system will respond to requests from DA devices and how to detect errors.

The MODBUS protocol is used to establish master-slave communication between the SCADA system and the DA device. MODBUS has two types of serial transmission modes, ASCII and RTU. In the ASCII serial transmission mode, a byte of every 8-bit in a message is transmitted as two ASCII parameters, and in the RTU serial transmission mode, a byte of every 8-bit in a message is transmitted as a bit. Two 4-bit hexadecimal characters.

In another example, DNP 3.0 is a communication protocol used by a SCADA system to pass data and control commands to a DA device. DNP 3.0 and MODBUS communication protocols generally operate on serial lines, but they have recently been modified to operate on TCP/IP as well. Communication protocol in DNP 3.0 In the definition, each device has an address of two bits. In the MODBUS protocol, each device has a single bit address. When using TCP/IP, both addresses can be associated with an IP address. Typically, a SCADA system communicates with a small group of such devices. The SCADA system decides that a command will be transmitted to one of the DNP 3.0 or MODBUS addresses, and then the IP address in a static table is looked up. However, in a large-scale network architecture where all nodes are in communication with a common back office host, the address of one or two bytes may not be sufficient to distinguish all devices in the utility range. Furthermore, when joining different IP networks, the DA communication node attached to the DA device may change its IP address.

The present invention disclosed herein addresses the aforementioned specific application layer standards by providing a readily implementable system utilizing known IP infrastructure application communication protocols such as a Domain Name Server (DNS) or directory server technology such as LDAP. Limitation of the agreement. The present invention specifies a DNS base registration support and an address resolution service for a device that communicates at the application layer.

In order to assist in understanding the concepts embodied in the present invention, exemplary embodiments will be described first with reference to their implementations and in conjunction with devices that support the C12.22 standard, and other implementations will be described hereinafter.

Subsequent definitions of architectural concepts and artifacts related to addressing and address resolution appropriate to the C12.22 standard are defined:

̇C12.22 device: A module that hosts a C12.22 application and provides at least one interface for the C12.22 communication module.

̇C12.22 communication module: Provides a network interface for two-way communication between the C12.22 device and the central utility server.

̇C12.22 apTitle: An application layer address based on the ASN.1 number. Each C12.22 communication module (or node) has a C12.22 address. This address can be absolute or relative.

̇C12.22 Relay: An application layer that resolves the network layer (not L2 is L3) address across a directly connected medium (eg, Ethernet LAN; RF subnet) The building of the site. The relay also implements both registration and resolution services.

̇C12.22 Master Relay: A way to resolve the network layer (not L2 is L3) address across all deployed media (for example, all subnets; such as cellular and fixed RF wireless) Network; etc.) The component of the application layer address. The C12.22 master relay is capable of resolving network addresses that cannot be resolved by C12.22 relays. The C12.22 master relay implements both registration and resolution servos. All C12.22 nodes require registration and address resolution support.

In large-scale (eg, residential) scheduling using advanced metering infrastructure for IP infrastructure networks, especially where IP addresses of endpoints such as meters are changed (eg, a device combines and separates the majority) The network of gateways, as required by a registration function, enables a back office application, such as a utility company's central location, to consult endpoints. In an IP infrastructure network, one device that implements such functionality is to utilize Domain Name Service (DNS). In an implementation of the invention, the network in the utility wireless network The routing interface to the majority of the gateways can be multi-homed and can have a majority of IP addresses by definition. In such an embodiment, a dynamic DNS update (also known as DDNS) is used to satisfy this functionality.

Referring to Figure 1, an example of a conventional IP infrastructure utility network is illustrated. For a brief understanding of the principles that form the basis of the present invention, only a single endpoint device is illustrated and discussed in the following examples. It will be appreciated, however, that in practical embodiments of the disclosed aspects, many such devices (such as having thousands or tens of thousands per access point) may appear in any given network.

The endpoint device 110 of the network can incorporate a utility meter M1. Alternatively, endpoint device 110 can incorporate a DA device. The network endpoint communicates with the host device 120, such as a back office server at the utility company, by constructing the subnet's regional network 130 and wide area network 140. For example, the local area network can be a wireless network or a power line carrier (PLC) network. A wide area network can be a proprietary network or a shared network, such as the Internet.

The interface between the regional network 130 and the wide area network 140 is provided by one or more access points 150, 151, 152, such as gateways. Within the local area network, endpoint 110 communicates with one or more access points via communication node 160. The communication node includes an RF transceiver for transmitting and receiving wireless signals transmitted through the area network, and having an address associated with the network layer (L2 or L3) specified by the OSI reference module, such as an IP. Address. In the illustrated example, the communication node is capable of multiple functions, i.e., can communicate with the host 120 via three different access points 150, 151, and 152. To support this capability, the communication node 160 has the indicated Three different IP addresses are defined, and these addresses are associated with three access points, respectively. In other words, whenever a communication node registers with an access point, it assigns a new IP address to it. Each of the assigned IP addresses corresponds to a logical subnet associated with the corresponding access point.

Depending on the distance between the communication node 160 and an access point, and other factors that affect the signal path and strength, the node may be able to communicate directly with the access point. In the illustrated example, node 160 communicates indirectly with each of access points 150, 151, and 152 by relay 170. These relays may be dedicated devices that are only used to deliver data packets from one node to another, or they may be other communication nodes associated with respective endpoint devices.

In operation of such an IP infrastructure network, the host 120 will query the communication node 160 by its IP address (and the endpoint device 110 to which the communication node is connected by the proxy host). The host may receive a command to poll the meter M1 associated with the correspondent node 160. In response to receiving this command, the host transmits a lookup request containing the desired device name to the name/address resolution server 180. In one embodiment, server 180 can be a domain name server (DNS) server. In another embodiment, server 180 can provide a directory service, such as LDAP. In the following discussion, an embodiment using a DNS server will be referred to. It will be appreciated, however, that the directory server can be used in the illustrated embodiment as a name/address resolution server.

The DNS server contains a record 182 identifying the IP address assigned to the named device. In the illustrated example, node 160 has the specified The three IP addresses, IPv61, IPv62, and IPv63, are intimately associated with three access points 150, 151, and 152, respectively. Although these addresses represent the IPv6 version of the address, it will be appreciated that other versions of the Internet Protocol can be used, depending on the structure of the network. When a majority of the addresses are assigned to a device, the preference metric can be utilized to assist in the selection of the particular address to be returned in response to the request. For example, each address can have an associated weighted value W1, W2 or W3. When registered at an access point, the node can be used to specify the weighted value, based on any of a variety of criteria to indicate the quality of the communication link between the node and the individual access point. Other factors that can be used for the priority measure can be the priority of the path selection, the subnet configuration, and/or the service group. Based on the value of the measure, the address can be stored as a sequential list.

Corresponding to the DNS lookup request, the DNS server retrieves the record 182 for the node identified in the request and sends one of the IP addresses back to the host 120. Typically, the DNS server will return the IP address with the highest weighted value, such as the first address in the list. However, for load balancing purposes, if an access point associated with its address is processing a large amount of network traffic, the DNS server may choose to associate with another access point that has more capability to handle traffic. IP address.

Upon receiving the IP address from the DNS server 180, the host 120 generates a data packet containing a polling command addressed to the correspondent node 160 and through a special access point associated with the IP address provided by the DNS server 180. To select the path to the node. Upon receiving this packet, node 160 retrieves the data contained therein (in this case, a polling command) and transfers it Submit to the associated meter. On the return, the meter provides the data (eg, current meter readings) requested by the polling command, which is sent to the host in a response packet through the same access point.

Figure 2 illustrates a conventional C12.22 network. When the C12.22 device 111, such as a meter, is activated on the network, it is registered with the C12.22 primary relay 181 through its associated communication node 161. This registration can be made directly or through an intermediate C12.22 relay 153. Unlike the IP network described above, the C12.22 device has traditionally not been able to perform multiplex functions, so it registers itself only with one relay or directly with the main relay. The C12.22 device registers its application layer address (called ApTitle) with the relay or master relay. If the relay acts as a proxy for the C12.22 device, the ApTitle of the C12.22 device is registered with the primary relay.

The host 121 in the C12.22 network may be a notification and verification host that naturally passes through the C12.22 standard interrogation device. When the host needs to consult a meter, it sends a resolution service request to the primary relay 181, which retrieves the appropriate record 183 and sends back the ApTitle associated with the specified meter. The host then consults the meter through the relay registered by the device or directly through the main relay.

In an IP-based network, communication between the host and the meter or its communication nodes occurs at the network layer (L3). In contrast, in the case of 12.22 networks, communication between the host and the C12.22 device occurs at the application layer (L7) of the network. Unlike the network layer address provided by the DNS server, the address of the application layer does not indicate how to connect to the device. It only provides the network name of the device. The operation of the C12.22 network is based on the presence of an application layer address to a pair of network layer addresses. A hypothesis of mapping.

In accordance with the present invention, a registered host of both IP and C12.22 base communications is utilized by utilizing an IP DNS server. The function of the C12.22 application layer is laid on the infrastructure of the IP foundation. Communication can occur at the IP layer or at the C12.22 application layer. At the IP layer, the host application can query the network node (and use the proxy host to query one of the meters connected to the network node). In order to extend this service to C12.22 communication, the C12.22 registration and resolution service is implemented on the DNS server. Similar to the way IP-based Servo uses a unique IP-based DNS resolution request, the C12.22 host can use a C12.22 resolution request against the C12.22-enabled DNS server to consider the endpoint (for example, C12 compliant) .22 standard meter or indoor equipment for C12.22 application layer consultation.

An example of configuring a network operating in this manner is illustrated in Figure 3. The definition specific C12.22 DNS resource record 182' contains not only the IP address or addresses for the communication node associated with a given meter or other C12.22 device, but also the ApTitle that is assigned to the device. Therefore, when requesting from the DNS server, the server can send back an address binding, which is uniquely related to the type of the request (ie, the DNS request will be sent back to the address in the IP DNS format; The C12.22 parsing request will be sent back to the address in the C12.22 format). When a fully qualified domain name appears, Dynamic DNS provides the IP address currently associated with the named device, ie one of the three IPv6 addresses in the example of Figure 3.

Furthermore, since the resource record contains both an IP address and a C12.22 ApTitle, it can return two types of addresses corresponding to a single request. For example, corresponding to the DNS request, the server 180 can determine the ApTitle of the identified device even if it is not requested, and send it back with the appropriate address.

In this way, the DNS server will perform the role of the C12.22 primary relay to perform registration and deregistration (C12.22 service) on the C12.22 application layer. The device is capable of registering (and deregistering) both on the network and the application layer. Conversely, instead of the network, the application layer can overload the registration service on either layer, thereby eliminating redundant registrations and deregistering packets. For example, after registering its network address, the communication node 160 may intercept the C12.22 registration request from the device 110 and discard it because it is redundant to the previously registered network address.

In its unique mode, the C12.22 device communicates with the host at the application layer (L7) of the network. As with another feature of the present invention, an IP-based communication protocol enables communication with the C12.22 device at the network layer while the device continues to operate in its unique mode. In this aspect of the invention, when the host 120 transmits a C12.22 resolution service request to the DNS server 180, the server does not return the ApTitle of the device indicated in the request. More specifically, since the DNS resource record for the device contains both the IP address of the device and the ApTitle, the IP address can be sent back. Using this IP address, the host can then transfer commands to the communication node 160 associated with the device.

Referring to FIG. 4, the data packet of the IP format transmitted over the network is received by the communication node 160 on the network interface 164. Interface 164 can be a component of a wireless transceiver, for example, in the context of a wireless network. Interface 164 will The received data packet is delivered to a processor 166 that reads the data and reformats its commands in accordance with the C12.22 communication protocol. The C12.22 format command is then forwarded to the intended device by the device interface 168. In the current example, the device interface 168 will support the C12.22 protocol. In response to the command, the communication node receives a response from the device on interface 168 in a manner consistent with the C12.22 standard. The processor 166 reformats the data into an IP packet instead of transmitting the response at the application layer in a conventional manner, and then transmits it over the network via interface 164. Therefore, for C12.22 devices, the operation of the network is transparent. The only communication using the C12.22 communication protocol is between the meter or the C12.22 device and the communication node. All other communications on the network are based on IP protocols.

A particular advantage of this aspect of the invention is that the multiplex capability can be implemented on a C12.22 device. In particular, since the data from the C12.22 device is transmitted over the network using the IP-based communication protocol instead of the C12.22 communication protocol, the features and functions of the IP network can be utilized. Therefore, the communication node 160 can select any of the access points 150, 151, or 152 that are available as a return path back to the host, rather than being limited to a single relay registered by the C12.22 device. Due to the path diversity provided by the multi-path capability, the link to the relay fails and thus will not prevent the data from reaching the host. The opposite is to increase the robustness of the overall C12.22 system.

Other endpoints on the network (not shown) may or may not be C12.22 devices. Therefore, the network can be of the same kind: the whole consists of endpoint devices that conform to C12.22, or can be heterogeneous: with IP base and C12.22 A mix of basic endpoint devices. For example, the endpoint device can be a DA device.

In an alternative embodiment, a utility network management system for network infrastructure registration and address resolution of a DA device can be implemented. As mentioned earlier, the two standard communication protocols developed for DA are DNP 3.0 and MODBUS. Moreover, it will be appreciated by those skilled in the art that the present invention can be applied to other DA communication protocols.

Then define the structural views and components related to the addressing and address resolution of the DA protocol:

̇DA device: Hosting the hacking software and providing at least one serial or Ethernet interface to one of the DA communication nodes, the customer software supporting at least one DA communication protocol such as MODBUS and DNP 3.0.

̇Communication node: A network interface that provides two-way communication between the DA device and the central utility SCADA system.

FIG. 5 illustrates a conventional monitoring and data capture "SCADA" system network for managing DA device 211. Examples of DA devices include a generator, circuit breaker, tap changer, substation automation (SA), feeder automation (FA), load control device (LCD), point of load unit (LPU), smart electronic device ( IED), programmable logic controller (PLC), distributed control system (DCS), and distributed terminal unit (DTU).

When the DA device is booted on the network, it is registered with the SCADA system 281 via the associated DA communication node 261. The DA device has a static address that is hard coded in the device. The DA device registers its application layer address (ie, the static DA device address) in the SCADA system.

In the SCADA system network, communication between the SCADA system and the DA device takes place at the application layer (L7) of the network. Unlike the network layer address, the application layer address does not indicate how to connect to the device. It only provides the network name of the device. The operation of the SCADA system network is based on the assumption that there is an application layer address to one-to-one mapping of network layer addresses.

According to the present invention, the function of the DA application layer is attached to the public infrastructure of the IP infrastructure by using the IP DNS server as the registration host for both the IP and DA communication protocol basic communication, such as the communication network described in FIG. road. Communication can be done at the IP layer or the DA application layer. At the IP layer, the host application can query the network node (and the proxy host to consult the DA device connected to the network node). In order to extend the communication of such services to the DA device, the registration and resolution services of the DA device are implemented on the DNS server. Similar to the way in which the IP infrastructure service uses a unique IP-based DNS resolution request, the SCADA system network can utilize a DA protocol such as MODBUS or DNP 3.0 parsing request against the SCADA-enabled DNS server as the endpoint (eg, DA application layer consultation for DA devices conforming to the DA protocol.

An example of configuring a network to operate in this manner is illustrated in Figure 6. The DNS resource record 282' defining a particular DA device contains not only the IP address or the address of the DA communication node associated with the given DA device, but also the DA device address assigned to the device. Therefore, when requesting the DNS server, the server can send back a specific address link associated with the request type (ie, the DNS request is sent back to the IP DNS format link; the DA protocol resolve request is sent back to MODBUS or DNP) Link in 3.0 format). When When a fully qualified domain name appears, Dynamic DNS provides the IP address currently associated with the named device, such as one of the three IPv6 addresses in the example of Figure 6.

Furthermore, since the resource record contains both the IP address and the DA device address, it can send back two types of addresses in response to a single request. For example, in response to the DNS request, the server 280 can determine the DA device address of the identified device even if no request is made and return it with the appropriate IP address.

In its unique mode, the DA device communicates with the SCADA system network at the application layer (L7) of the network. According to another feature of the invention, communication with the DA device can be implemented at the network layer using an IP-based communication protocol while the device continues to operate in its unique mode. In this aspect of the invention, when the host 220 transmits a resolution service request from a DA device to the DNS server 280, the server does not return the DA device address of the device indicated in the request. More specifically, since the device's DNS resource record contains both the device's IP address and the DA device address, it can send back an IP address. Using this IP address, the host can then transfer a command to the DA communication node 260 associated with the device.

Referring again to FIG. 4, the data packet of the IP format transmitted over the network is received by the communication node 160 on the network interface 164. In the case of a wireless network, for example, interface 164 can be a component of a wireless transceiver. The interface 164 will deliver the received data packet to the processor 166, which will read the data and reformat its command in accordance with the DA device's protocol. Then the device protocol interface 168 will be used to format the DA protocol format. To be forwarded to the intended device, device interface 168 supports one or more DA protocols in this example. On the return, the correspondent node will receive a response from the device compliant with the DA device communication protocol on interface 168. Instead of transmitting this response at the application layer in a conventional manner, processor 166 reformats the data into an IP packet, which is then transmitted over the network through interface 164. Therefore, the operation of the network is transparent to the DA device. The only communication that utilizes the DA device communication protocol is between the DA device and the communication node. All other communications on the network are based on IP protocols.

A particular advantage of this aspect of the invention is that it makes the multiplex function of the DA device feasible. In particular, since the IP-based communication protocol is used instead of the DA device communication protocol to transmit data from the DA device over the network, it is possible to utilize all the features and functions of the IP network. Therefore, the communication node 260 can select any of the available access points 250, 251, or 252 as a path back to the host without being limited to a single path specified by the fixed address associated with the DA device. Due to the diversity of paths provided by the multiplex function, the failure of the link of its fixed address will therefore prevent the data from reaching the host. Therefore, the robustness of the overall SCADA system increases.

For example, in a network having an endpoint device compliant with a DA device, the DA device can communicate with the communication node via serial communication. In such a network, the network node has an IP address that is used by the host to communicate with the DA device having the DA device address. For its part, the host can poll a particular DA device via the correspondent node.

In another example, at least some of the DA devices can be connected via an Ethernet connection. To communicate, and have its own IP address. In this case, the IP address of the DA device is registered with the DNS server 280 along with the IP address of its associated communication node 260. Therefore, the host can poll through the WAN and communicate directly with the IP infrastructure DA endpoint device. In such a case, the communication node 260 will recognize the IP address of the associated DA device and act as a relay for forwarding the packet destined for the IP address.

Large utilities have several independent DNP 3.0 or MODBUS SCADA system networks and may not need to be identified by their communication protocol address to identify the location of the device or which corporate control range it is in. The DNS name stored in the DNS server can have a hierarchical structure. Such an architecture can be based on the hierarchy of the network views to which it is connected, or can be based on the perspective of which utility operator and substation to which the device is connected.

It will be appreciated by those skilled in the art that the present invention can be embodied in other forms without departing from the spirit and essential characteristics. Therefore, the previous description is considered to be illustrative, not limiting. The scope of the invention is indicated by the following claims, and all modifications are intended to be included within the meaning and scope of the equivalents.

110‧‧‧Endpoint device

111‧‧‧C12.22 device

120‧‧‧Host device

121‧‧‧C12.22 host

130‧‧‧Regional Network

140‧‧‧ Wide Area Network

150,151,152‧‧‧ access points

153‧‧‧Intermediate C12.22 relay

160,161‧‧‧Communication node

164‧‧‧Internet interface

166‧‧‧ processor

168‧‧‧ device interface

170‧‧‧ relay

180‧‧‧Name/Address Resolution Server

181‧‧‧C12.22 main relay

182,183‧‧ records

210,211‧‧‧DA (Distribution Automation) device

220‧‧‧Host device

230‧‧‧Wireless Local Area Network

231‧‧‧Regional Network

240‧‧‧ Wide Area Network

250,251,252‧‧‧ access points

260,261‧‧‧DA communication node

270‧‧‧ relay

280‧‧‧DNS server

281‧‧‧SCADA (Monitoring and Data Capture) System

282’‧‧‧DNS resource records

The foregoing aspects and numerous attendant advantages of the present invention will be more readily apparent and appreciated by reference <RTIgt; Block diagram Figure 2 is a block diagram of a network operating according to the C12.22 standard; Figure 3 is a block diagram of an IP network including a C12.22 device; Figure 4 is a block diagram of a communication node; Figure 5 is a block diagram operating according to the DA protocol A block diagram of the network; and Figure 6 is a block diagram of an IP network containing a DA device.

210,211‧‧‧DA (Distribution Automation) device

220‧‧‧Host device

230‧‧‧Wireless Local Area Network

240‧‧‧ Wide Area Network

250,251,252‧‧‧ access points

260,261‧‧‧DA communication node

270‧‧‧ relay

280‧‧‧DNS server

281‧‧‧SCADA (Monitoring and Data Capture) System

282’‧‧‧DNS resource records

Claims (57)

A method of providing communication between nodes in a utility network, comprising: receiving a request to provide an application layer address under a domain name service or directory service to a public network that conforms to C12.22 Means; determining, by a plurality of network addresses associated with the devices stored on the service, a network address of the device, the plurality of addresses including an application layer address and at least one network layer address; And returning at least one network layer address associated with the device to respond to the request. The method of claim 1, wherein the network address is determined based on a priority measure of the network address, the priority measure identifying one of a plurality of network addresses for communicating with the device. The method of claim 2, wherein the priority of the network address is based at least in part on one of the following network characteristics: path selection priority, subnet configuration, and service ethnic group. The method of claim 1, wherein the network address and at least one C12.22 ApTitle are included in a single message sent back in response to the request. The method of claim 1, wherein the service is implemented in a DNS server, and wherein the DNS server determines the C12.22 ApTitle associated with the device, and the determined ApTitle and the network layer address are determined. Send it back together. For example, the method of claim 1 of the patent scope, wherein the service is implemented in one In the directory server, and wherein the directory server determines the C12.22 ApTitle associated with its device, and returns the determined ApTitle with the network layer address. The method of claim 1, wherein the network address is an address in an IP format. A method for providing utility network communication between at least two nodes in a utility network, comprising: receiving a resource record request for a specific node in a utility network under a network address resolution service; responding to receiving the resource Recording a request to select a network layer address for a node in the utility network from an ordered list of one or more network layer addresses associated with nodes in the utility network; The node in the utility network determines one or more C12.22 ApTitle; and returns the determined network layer address and the determined one or more C12.22 ApTitles to respond to the request. For example, in the method of claim 8, wherein the sequence table is maintained according to the network trait measurement, the network trait measurement specifically specifies at least one measurable viewpoint in the network to determine the network bit communicating with the node. The preferred order of the addresses. The method of claim 8, wherein the received resource record request includes a request to return a network layer address associated with a node specified in the resource record request. For example, the method of applying for patent scope 10, wherein the resource record please Ask for a request to a DNS server. The method of claim 10, wherein the resource record request is a directory service search. For example, in the method of claim 9, wherein the resource record request is sent back in a DNS response, and the judgment of C12.22 ApTitles is performed even if the request is not specifically sent back to C12.22 ApTitles. The method of claim 9, wherein the resource record request is an LDAP search, and wherein the C12.22 ApTitles judgment is performed even if the LDAP search does not specifically return one or more C12.22 ApTitles. The method of claim 9, wherein the network layer address is an address in an IP format. A method for providing utility network communication between at least two nodes in a utility network, comprising: receiving a resource record request of a specific node in a utility network under a network address resolution service; Metricing, determining a network layer address of the particular node from a plurality of network layer addresses associated with the particular node; determining one or more C12.22 ApTitles for the particular node; and transmitting the determined The network layer address and the judged C12.22 ApTitles are back to the request. For example, the method of claim 16 wherein the network address measurement specifies a node associated with the determined network layer address to communicate. The preferred path. A network name/address resolution server having a resource record stored therein, the resource records respectively having a node on a network and including one or more addresses communicating with each node, wherein At least some of the resource records include one of a node identification, one or more network layer addresses of the identified node, and at least one application layer address of the node; and wherein a request is made to provide a bit The address is given to a specific node, and the server sends back a network layer address or the application layer address according to the request. For example, the server of claim 18, wherein the server implements a domain name service. For example, the server of claim 18, wherein the server implements a directory service. For example, the server of claim 20, wherein the directory service is an LDAP. For example, in the server of claim 18, in response to a request to provide an application layer address, the server will send back a network layer service. A node in a utility network comprising: a first interface communicating with an associated device via a C 12.22 protocol; a second interface through an IP protocol and a network Communicating; and a processor responsive to IP basic data packets through the second interface Receiving, reformatting the data in the packet to comply with a C12.22 protocol, and forwarding the reformatted material through the first interface, and the response is reformatted in the first interface C12.22 The data is received, the data is reformatted into an IP based packet, and the packet is transmitted over the network through the second interface. For example, in the node of claim 23, the second interface wirelessly transmits the packet to the network. A method of providing communication between nodes in a utility network, comprising: receiving a request to provide an application layer of a DA device in a utility network under one of a domain name service or a directory service Addressing, the DA device is configured to communicate according to a communication protocol including at least one of MODBUS and DNP 3.0; determining a network of the DA device from a plurality of network addresses associated with devices stored on the service A path address, the plurality of addresses including an application layer address and at least one network layer address; and returning at least one network layer address associated with the device to respond to the request. The method of claim 25, wherein the network address is determined according to a network address priority measure, wherein the network address priority measure identifies one of a plurality of network addresses used to communicate with the device By. The method of claim 26, wherein the network address prioritization is based at least in part on one of the following network characteristics: path selection priority, subnet configuration, and service group. The method of claim 25, wherein the network address and the at least one DA device address are included in a single message sent back by the request. The method of claim 25, wherein the service is implemented in a DNS server, and wherein the DNS server determines a DA device address associated with the device, and the determined DA device bit The address is sent back with the network layer address. The method of claim 25, wherein the service is implemented in a directory server, and wherein the directory server determines a DA device address associated with the device, and the determined DA device bit The address is sent back with the network layer address. A method for providing utility network communication between at least two nodes in a utility network, comprising: receiving a resource record request of a particular node in a utility network under a network address resolution service; in response to receiving The resource record request selects a network layer address for a node in the utility network from one of a plurality of network layer addresses associated with a node in the utility network Determining one or more DA device addresses for nodes in the utility network to cause the node to communicate according to a communication protocol including at least one of MODBUS and DNP 3.0; and returning the determined network The layer address and the one or more DA device addresses that have been determined to respond to the request. For example, the method of claim 31, according to a network The quality measure maintains the sequence table. The network trait measure specifies at least one measurable point of view in a network to determine a preferred sequence of network addresses for communication with the node. The method of claim 31, wherein the received resource record request includes a request to return a network layer address associated with a node specified in the resource record request. The method of claim 33, wherein the resource record request is included in a request for a DNS server. The method of claim 33, wherein the resource record request is a directory service search. The method of claim 32, wherein the resource record request is sent back in a DNS response, and wherein the determination of the DA device address is performed even if the request is not specifically sent back to the DA device address. The method of claim 32, wherein the resource record request is an LDAP search, and wherein the determination of the DA device address is performed even if the LDAP search does not specifically return one or more DA device addresses. A method for providing utility network communication between at least two nodes in a utility network, comprising: receiving a resource record request of a specific node in a utility network under a network address resolution service; a location metric, determining a network layer address of a particular node from a majority of network layer addresses associated with the particular node; determining one or more DA device addresses for the particular node to The specific node is caused to communicate according to a communication protocol including at least one of MODBUS and DNP 3.0; and the determined network layer address and the determined DA device address are transmitted to respond to the request. The method of claim 38, wherein the network address metric specifies a preferred path for communication with a node associated with the determined network layer address. A node in a utility network comprising: a first interface communicating with an associated device by a DA device address protocol, the DA device address protocol causing the first interface of the node to be based Having a communication protocol including at least one of MODBUS and DNP 3.0; a second interface communicating with a network via an IP protocol; and a processor responsive to the IP basis through the second interface Receiving the data packet, reformatting the data in the packet to comply with a DA device address protocol, and forwarding the reformatted data through the first interface, and responding to the DA device address in the first interface The reformatted data is received, the data is reformatted into an IP based packet, and the packet is transmitted over the network through the second interface. For example, in the node of claim 40, the second interface wirelessly transmits the packet to the network. A method for communicating over a network, comprising: recording and transmitting a record for identifying a distribution automation device ("DA device" Sending a DNS lookup request to a Domain Name Service ("DNS") server, wherein the record contains at least one Internet Protocol ("IP") address and at least one DA protocol address, the DA protocol The address enabling communication according to a communication protocol including at least one of MODBUS and DNP 3.0; receiving at least the IP address from the DNS server; generating a data packet; and transmitting the data packet to the IP address The DA device is connected. The method of claim 42, wherein the record comprises a plurality of IP addresses. The method of claim 43, wherein an IP address is selected from the plurality of IP addresses according to an IP address priority measure, the IP address priority measure identifying a plurality of IP addresses for communication with the DA device One of the IP addresses. The method of claim 44, wherein the IP address prioritization is based at least in part on one of the following network traits: path selection priority, subnet configuration, and service ethnic group. The method of claim 42, wherein the data packet comprises an IP communication protocol command comprising at least one of a request or a command. The method of claim 42, wherein the data packet is transmitted to the DA device associated with the IP address via one of a plurality of communication paths. For example, the method of claim 47, wherein the communication path includes a DA communication node. A method of communicating over a network, comprising: receiving, from a host, a record search request identifying a distribution automation device ("DA device"), wherein the record includes at least one network address and at least one DA communication a protocol address, the DA protocol address enabling communication according to a communication protocol including at least one of MODBUS and DNP 3.0; and returning at least one application layer address and at least one network layer address to the host In response to the lookup request. The method of claim 49, wherein the record comprises a plurality of IP addresses. The method of claim 50, wherein an IP address is selected from the plurality of IP addresses according to an IP address priority measure, and the IP address priority measure identifies a plurality of IP addresses for communication with the DA device. One of the IP addresses. The method of claim 51, wherein the IP address prioritization is based at least in part on one of the following network traits: path selection priority, subnet configuration, and service ethnic group. The method of claim 49, wherein the data packet comprises an IP protocol command including at least one of a request or a command. The method of claim 49, wherein the data packet is transmitted to the DA device associated with the IP address via one of a plurality of communication paths. The method of claim 54, wherein the communication path comprises a DA communication node. A method of communicating over a network, comprising: receiving a data packet associated with a distribution automation device ("DA device"), wherein the data packet includes an Internet Protocol ("IP") command; reformatting The IP command becomes a DA communication protocol including at least one of MODBUS and DNP 3.0; and the DA communication protocol is transmitted to the DA device. The method of claim 56, wherein the data packet comprises an IP communication protocol command comprising at least one of a request or a command.