JP6465745B2 - Configuration method, server, and terminal - Google Patents

Description

  The present invention relates to a configuration method, a server, and a terminal.

  Currently, GOOSE (Generic Object Oriented System Event) and MMS (Manufacturing Message Specification) based on IEC 61850 are spreading as communication protocols of control systems installed in substations and the like.

  IEC61850 uses an XML-based meta language called SCL to describe the communication environment and the logical configuration of IEDs (Intelligent Electronic Devices) connected by communication, and integrates the SCL files of each IED And configure the system.

  Currently, such a control system is statically constructed offline. Specifically, a developer applies a generated SCL (Substation Configuration Language) file to the server and each IED, and further starts the control system. Accordingly, the server and the IED and the plurality of IEDs in the control system can communicate with each other.

  A network installed in a substation or the like does not necessarily use DHCP because it is necessary to statically describe IP connection parameters in SCL. In many cases, such a network is pre-assigned with a fixed IP designed on a desk.

  The SCL 500 used to construct a substation system is a language based on XML. The existing system construction tool generates the SCD file 312 based on a design created in advance with respect to a network, an LN (Logical Node), a service, and the like. When the substation system is started up, the generated SCD file 312 is parsed into the IED 41 and the substation server 11 and analyzed, and then the service is executed based on the analyzed content and the IEC 61850 standard. .

  That is, the system construction model of the IEC 61850 standard so far does not assume that a device such as an IED is added to the network and the service is started without stopping the substation system.

  For this reason, it was necessary to design each time the configuration of the substation system was changed. In addition, this design is complicated and a design error is likely to occur, so that there is a problem that human cost increases.

  A conventional technique for solving such a problem has been proposed (see, for example, Patent Document 1). In Patent Literature 1, when the IED 41 is connected to the substation network, the substation server 11 automatically acquires the SCL 500 from the IED 41 connected to the network, and the screen display symbols and character strings extracted from the SCL 500 It is possible to realize plug and play that can automatically recognize IED in a substation system by automatically creating an SCD file that describes the entire system by collating with predefined single-line diagram information Have been described.

Japanese Patent Application No. 2013-164731

  Patent Document 1 only proposes an automatic reconstruction method for SCL files that are metadata, and does not construct network connection information including a new IED. For this reason, in Patent Document 1, plug-and-play IEDs are limited to IEDs in which servers installed in substations already hold information.

  On the other hand, there is a Universal Plug and Play standard (hereinafter referred to as UPnP) as a technology for automatically reconfiguring devices connected to a network without stopping the system.

  In this standard, each device is connected by an IP network in which a DHCP (Dynamic Host Configuration Protocol) server exists, and the connected device is automatically assigned an IP address or the like by the DHCP protocol from the DHCP server. It is assumed that they are connected.

  However, in a substation network based on the IEC 61850 standard, it is assumed that network information such as the IP address of each IED is statically allocated and described in advance in the SCL file at the time of system configuration, and the DHCP protocol is used. Since this is not assumed, plug-and-play operations based on the UPnP standard cannot be realized in the substation system.

  The present invention can reconfigure a substation system without stopping the substation system when an IED or other device is connected to the network in a substation system on which static IP address assignment is a prerequisite, and the IED can be used. A substation system configuration method that realizes a plug-and-play operation is realized.

  In order to solve the above problems, the present invention is a network system configuration method, wherein the network system includes a terminal that performs at least one of monitoring and control of a power transmission network, a server connected to the terminal, A network to which a server is connected, and the method starts transmission of identification information for identifying the terminal to the network according to a first communication method when the terminal is connected to the network. And when the server acquires the identification information according to the first communication method via the network, the communication information stores the acquired identification information in a setting storage unit and includes an address assigned to the terminal. In accordance with the first communication method, and the server monitors the power transmission network to the terminal. Requesting terminal information necessary for instructing at least one process of control to a terminal to which the address is assigned according to a second communication method different from the first communication method, And a procedure for acquiring the terminal information from the terminal according to the second communication method, and a procedure for the server to store the acquired terminal information in the setting storage unit.

  According to the present invention, the system can be reconfigured without stopping the substation system, and the IED can be used.

  Problems, configurations, and effects other than those described above will be clarified by the following description of embodiments.

It is a block diagram which shows the substation system of Example 1. It is explanatory drawing which shows the abstracted substation model of Example 1. FIG. FIG. 3 is an explanatory diagram illustrating a protocol stack of a service according to the first embodiment. 4 is an explanatory diagram illustrating communication based on GOOSE in Embodiment 1. FIG. FIG. 6 is an explanatory diagram illustrating a GOOSE message according to the first embodiment. It is explanatory drawing which shows the value stored in GOOSE PDU of Example 1. FIG. FIG. 3 is an explanatory diagram showing an MMS of Example 1. It is explanatory drawing which shows the file described by SCL of Example 1. FIG. FIG. 6 is an explanatory diagram illustrating processing for setting an IED according to the first embodiment. It is explanatory drawing which shows the SCD file by SCL of Example 1. FIG. It is explanatory drawing which shows the information described in SCL of Example 1. FIG. It is explanatory drawing which shows the content of DataSet of the embedding request message which IED of Example 1 sends out. It is explanatory drawing which shows the content of DataSet of the communication setting request message which the substation server of Example 1 sends out. It is explanatory drawing which shows the content of DataSet of the IP connection completion notification message which IED of Example 1 sends out. It is a sequence diagram which shows the process at the time of connecting new IED of Example 1 to a substation network. It is a sequence diagram which shows the process at the time of connecting IED of Example 2 to a substation network.

  Hereinafter, embodiments will be described with reference to the drawings.

  FIG. 1 is a block diagram illustrating a substation system 10 according to the first embodiment.

  The substation system 10 is a system that is mounted in correspondence to a power transmission network (including power transformers: switches, switches, transmission lines, etc.) installed in the substation, and a system that controls power fluctuations in the substation. It is. However, the facility where the substation system 10 of the present embodiment is installed is not limited to a substation, but may be any facility as long as it includes a plurality of devices that control electric power.

  For example, the substation system 10 of the present embodiment may be installed in a power system facility including a power plant and a power storage facility. Moreover, the installation in which the substation system 10 is installed may be constructed by a plurality of vendors.

  The substation system 10 includes devices such as a substation server 11, a time server 12, a control device 13, a protection relay 14, a layer 2 switch (L2SW) 16, and a Merging Unit (MU) 17.

  Devices included in the substation system 10 are connected to each other via a process bus (station bus) 15. The process bus 15 relays communication according to a protocol defined by the IEC 61850 standard. The L2SW 16 connects the process bus 15 and the device.

  The process bus 15 and the L2SW 16 are networks that connect devices included in the substation system 10. The process bus 15 and the L2SW 16 are hereinafter referred to as a substation network.

  The substation server 11 is a computer including a processor, a memory, an auxiliary storage device, and a network interface. The substation server 11 may include an output device such as a display or a printer, and an input device such as a keyboard or a mouse. The substation server 11 executes processing using a communication protocol when the processor executes a program.

  The substation server 11 outputs an instruction to shut off the power transmission network at the substation when a failure occurs. In addition, the substation server 11 communicates with the control device 13, the protection relay 14, and the MU 17 and instructs processing.

  The substation server 11 is connected to the control station server 19. The control station server 19 monitors and controls the substation system 10 via the substation server 11.

  The control station server 19 is a computer including a processor, a memory, an auxiliary storage device, and a network interface. The control station server 19 may include an output device such as a display or a printer and an input device such as a keyboard or a mouse. The substation server 11 implements functions by the processor executing a program.

  The time server 12 is a device that provides time information for synchronizing the time in the substation network. The time server 12 is a computer including a processor, a memory, an auxiliary storage device, and a network interface.

  The control device 13 is installed at a plurality of measurement points provided in the power transmission network of the substation, and monitors states such as voltage and phase. Then, the control device 13 sends the monitoring result to the substation network.

  The MU 17 collects monitoring results from the plurality of control devices 13 and sends the collected monitoring results to the substation network. When a failure occurs, the protection relay 14 controls the power transmission network by cutting off the power transmission network at the failure location.

  The substation server 11 acquires information 20 sent from the MU 17 and the control device 13. Furthermore, the substation server 11 acquires wide area state information in the entire substation system 10 from the control station server 19. Then, the substation server 11 identifies a fault location based on the acquired information, and transmits a power transmission network cutoff instruction 21 to the protection relay 14 corresponding to the fault location.

  When the protection relay 14 receives the cutoff instruction, the protection relay 14 executes control (interlock 22) to directly send the cutoff instruction to the other protection relay 14 that is likely to be affected by the failure without passing through the substation server 11. May be.

  Such a control device 13 and the protection relay 14 have a communication function based on the IEC 61850 standard, and are generally called intelligent electronic devices (hereinafter referred to as IED).

  Hereinafter, the control device 13 and the protection relay 14 are collectively referred to as IED41. Further, the substation server 11 and the time server 12 of the substation system 10 are collectively referred to as a server 42.

  FIG. 2 is an explanatory diagram illustrating an abstracted substation model 40 according to the first embodiment.

  In the IEC 61850 standard, as shown in FIG. 2, the IEC 61850-6 standard defines a substation model 40 that abstracts the server 42, the IED 41, and the like. Then, the service 70 executed based on the substation model 40 is defined by the IEC 61850-7 and IEC 61850-8 standards.

  The substation model 40 standardizes and defines a Logical Node (LN) 50 and a Data Object (DO) 60. The LN 50 is a functional model of the IED 41 and the server 42 shown in FIG. The DO 60 is a data object used for processing performed by the LN 50.

  The substation model 40 defines a standardized service 70 based on a communication protocol such as MMS and GOOSE between the modeled IED 41 and the server 42. By these regulations, the substation system 10 in which a plurality of vendors can be mixed can be configured.

  FIG. 3 is an explanatory diagram illustrating a protocol stack of the service 70 according to the first embodiment.

  FIG. 3 shows a communication protocol stack of the service 70, which is defined by IEC 61850-7, IEC 61850-8, and the like.

  The abstract communication service interface (ACSI) 80 is an abstracted interface defined by IEC61850. The ACSI 80 is realized by using an existing communication protocol using a specific communication service mapping (hereinafter referred to as SCSM) 85.

  The ACSI 80 defines protocols such as a data processing method 81, time synchronization 82, GOOSE protocol 83, and Sampled Values 84. The data processing method 81 defines a method for performing data reference, reporting and logging, control, and settling (characteristic adjustment). The time synchronization 82 defines a method for performing time synchronization.

  The communication protocols used in the IEC 61850 standard are mainly GOOSE protocol 83, MMS protocol 86, and Sampled Values 84.

  The GOOSE protocol 83 is a communication protocol for sending information of a transmission source device to another device. The MMS protocol 86 is a communication protocol for a transmission source device to instruct other devices to perform processing and cause other devices to execute processing.

  Sampled Values 84 is a communication protocol used to periodically transmit voltage, current, phase information and the like at measurement points set in the substation network.

  Hereinafter, a program for implementing the GOOSE protocol 83 is referred to as a GOOSE program, and a program for implementing the MMS protocol 86 is referred to as an MMS program. The IED 41 and the substation server 11 have a communication device having the same functions as the GOOSE program and the MMS program, or the GOOSE program and the MMS program, and execute the GOOSE protocol and the MMS protocol by these programs or communication devices.

  FIG. 4A is an explanatory diagram illustrating communication based on the GOOSE protocol 83 according to the first embodiment.

  The GOOSE protocol 83 is a communication protocol that is implemented on the layer 2 and realizes highly real-time communication based on the Publisher / Subscriber model. When the GOOSE protocol 83 is used, a device having a communication function communicates as a Publisher 120 or a Subscriber 110.

  In the present embodiment, GOOSE is a communication protocol on L2 based on the Publisher / Subscriber model. In non-IP communication, a destination can be specified based on a MAC address, and multicast communication (or broadcast communication) in the GOOSE protocol can be specified.

  Communication in the Publisher / Subscriber model will be described. The Publisher 120 executes a multicast communication request to the transmission buffer 123 for the GOOSE message 100 to be transmitted to the network to which the Publisher 120 is connected (122). The Publisher 120 executes multicast communication by using a multicast MAC address as a destination.

  The Subscriber 110 designates an acquisition condition for the GOOSE message 100 flowing on the substation network (111), and requests the reception buffer 112 to acquire the GOOSE message 100 (112).

  When the received GOOSE message 100 is specified by the acquisition condition specified by the Subscriber 110, the reception buffer 112 returns the received GOOSE message 100 as a response to the Subscriber 110 (113).

  FIG. 4B is an explanatory diagram illustrating the GOOSE message 100 according to the first embodiment.

  The GOOSE message 100 includes an Ethernet header (Ethernet is a registered trademark, the same applies hereinafter) 101, a VLAN header 102, a GOOSE header 103, and a GOOSE PDU 104.

  The Ethernet header 101 includes information indicating a destination (for example, a multicast MAC address), a MAC address indicating a transmission source, and the like. The VLAN header 102 stores information on a VLAN identifier and a VLAN priority, and a value is set by a transmission source.

  The GOOSE header 103 stores APPID. The APPID is an identifier set by a developer or an operator (hereinafter referred to as a developer or the like) according to the purpose of use of the GOOSE message 100.

  The GOOSE PDU 104 includes a plurality of DataSets 105. The DataSet 105 includes the content of the message to be transmitted to the Subscriber 110.

  FIG. 5 is an explanatory diagram illustrating values stored in the GOOSE PDU 104 according to the first embodiment.

  The GOOSE PDU 104 includes the information shown in FIG. 5 defined in IEC 61850-7-2. A parameter name 1041 shown in FIG. 5 indicates the name of information included in the GOOSE PDU 104. A value stored in the parameter name 1041 may be used as an identifier in the GOOSE PDU 104.

  The parameter type 1042 indicates the type of parameter indicated by the parameter name 1041. The description 1043 is a description of the parameter indicated by the parameter name 1041, and may indicate a range that the parameter value can take.

  The entries 1044, 1045, 1046, and 1047 shown in FIG. 5 indicate GoCBRef, GoID, DatSet, and GOOSEDdata as parameters. GoCBRef indicates the reference name of the modeled IED 41 and LN 50.

  The GoID is an identifier of the GOOSE message 100. DataSet is a reference name of DataSet105.

  GOOSEDdata corresponds to DataSet 105 shown in FIGS. 4A and 4B.

  FIG. 6 is an explanatory diagram illustrating the MMS protocol 86 according to the first embodiment.

  The MMS protocol 86 is a communication protocol based on the Client / Server model that operates on TCP / IP, performs processing in response to a request from the Client 130, and responds to the Client 130.

  When the client 130 executes the communication service 135 defined by IEC 61850-7, the client 130 transmits the MMS Request 131 to the server 140 via the transmission buffer 132.

  The server 140 receives the MMS request 131 via the reception buffer 141. Thereafter, the MMS Server 143 of the Server 140 performs processing for the request, and returns an MMS Response 134 to the Client 130 via the transmission buffer 145.

  The client 130 receives the MMS response 134 via the reception buffer 133, and a series of MMS communication is completed.

  The communication service 135 defined by IEC61850-7 acquires the configuration information of the LN 50 and the service 70, references and updates of each data value of the DO 60, references and updates of each value of the DataSet 105 transmitted by the service 70, and Define various service contents, such as referencing and updating files containing configuration information. The server 140 implements a function corresponding to the communication service 135 as necessary.

  For the definition and configuration in the substation system 10 of the present embodiment, a plurality of types of XML-based SCLs 500 defined by the IEC 61850-6 standard are used. By using the SCL 500, contents such as the LN 50, the DO 60, and the service 70 can be acquired between the modeled devices.

  FIG. 7 is an explanatory diagram illustrating files described by the SCL 500 according to the first embodiment.

  The file shown in FIG. 7 is described by the SCL 500. File types described by the SCL 500 include an ICD file 311, an IID file 315, a CID file 313, an SCD file 312, an SED file 316, and an SSD file 314.

  An ICD (IED Capability Description) file 311 includes a template corresponding to the IED 41. Here, the template corresponding to the IED 41 is a template according to the function corresponding to the type of the IED 41 and the type of the LN 50 corresponding to the IED 41.

  An IID (Instantated IED Description) file 315 includes information set in advance with respect to the IED 41, and more specifically includes a definition of the DO 60.

  A CID (Configured IED Description) file 313 includes a part of information included in an SCD file 312 described later, and includes only information regarding a specific IED 41.

  The SCD (Substation Configuration Description) file 312 includes information regarding the entire configuration included in the substation system 10. Specifically, the SCD file 312 includes data flow and DO 60 definition, information indicating the structure of the substation system 10, and information necessary for communication.

  The SED (System Exchange Description) file 316 includes information related to an interface for exchanging information between the plurality of substation systems 10.

  An SSD (System Specification Description) file 314 includes information indicating the structure of the substation system 10 and the type of the LN 50.

  FIG. 8 is an explanatory diagram illustrating files and processes used for setting setting information in the IED 41 according to the first embodiment.

  The IEDConfigurator 300 and the SystemConfigurator 301 are functions for setting the IED 41, and may be implemented in the device of the IED 41 and the device of the server 42, or may be implemented in a computer outside the substation system 10.

  The IEDConfigurator 300 and the SystemConfigurator 301 shown in FIG. 8 generate a file for setting setting information in the IED 41 using the SCL 500, and set the IED 41 by transmitting and receiving the generated file.

  The IEDConfigurator 300 is connected to at least one IED 41 and communicates with the IED 41. The System Configurator 301 is connected to at least one IED Configurator 300.

  The IEDConfigurator 300 sets a setting value related to the IEC 61850 standard in the IED 41. First, the IEDConfigurator 300 outputs an ICD file 311 according to a model type corresponding to the IED 41 or the like.

  Here, the IEDConfigurator 300 may transmit the IID file 315 to the SystemConfigurator 301.

  Then, the System Configurator 301 acquires the output ICD file 311 and generates an SCD file 312 using the setting values related to the entire substation system 10 and the ICD file 311.

  Here, the System Configurator 301 may acquire the SED file 316 or the SSD file 314 from the System Configurator 301 of another substation system 10. Then, the SystemConfigurator 301 may generate the SCD file 312 based on the ICD file 311 and the acquired SED file 316 and SSD file 314.

  The IEDConfigurator 300 acquires the SCD file 312 generated by the SystemConfigurator 301, extracts setting contents related to the IED 41 connected thereto from the SCD file 312, and generates a CID (Configured IED Description) file including the extracted contents. The IEDConfigurator 300 transfers the generated CID file 313 to the IED 41 and sets it.

  FIG. 9 is an explanatory diagram illustrating the SCD file 312 by the SCL 500 according to the first embodiment.

  The substation server 11 of the present embodiment has the SCD file 312 in its own memory or auxiliary storage device. The substation server 11 may have a setting storage unit that holds the SCD file 312. The SCD file 312 included in the substation server 11 includes information regarding the IED 41 included in the substation system 10.

  The substation server 11 can establish communication with the IED 41 using the MCD protocol 86 shown in FIG. 6 by using the SCD file 312 held by the substation server 11.

  SCL 500 shown in FIG. 9 includes regions 501 to 507. Areas 501 to 501 shown in FIG. 9 are information related to the IED 41 newly connected to the substation network, and are information added by processing to be described later.

  FIG. 10 is an explanatory diagram illustrating information described in the SCL 500 according to the first embodiment.

  The SCL 500 includes the elements shown in FIG. 10 in a metadata format. The SCL 500 includes, for example, a Header element 401, a Substation element 402, a Communication element 403, an IED element 404, and a DataTypeTemplates element 405.

  The Header element 401 indicates information such as the version of the SCL 500 file.

  The Substation element 402 indicates information on devices such as the IED 41 connected to the substation system 10 and configuration information in the substation system 10.

  A Communication element 403 indicates communication parameters (IP address, subnet mask, gateway address, multicast MAC address, VLAN ID, VLAN priority, APPID, etc.) of the communication interface according to the MMS protocol 86 and the GOOSE protocol 83.

  An area 501 shown in FIG. 9 is an area for declaring the storage position of the Communication element 403, and an area 502 is an area for storing the contents of the Communication element 403. An area 503 declares a location for storing GOOSE communication parameters, and an area 504 stores GOOSE communication parameters.

  The IED element 404 indicates the logical device of the IED 41, the LN 50, the DO 60, a data set of available services, and data transmission contents.

  An area 505 shown in FIG. 9 is an area for declaring the storage position of the IED element 404, and an area 506 is an area for storing the contents of the IED element 404.

  A DataTypeTemplates element 405 indicates the definition of the type of description included in the IED element 404. An area 507 illustrated in FIG. 9 is an area for declaring the storage position of the DataTypeTemplates element 405.

  The developer uses a tool for system configuration using the SCL 500 as described above. This tool is provided by several vendors. Therefore, the developer can configure the substation system 10 including multi-vendor equipment.

  11 to 13 below show the contents of the DataSet 105 of the GOOSE message 100 for system configuration exchanged between the substation server 11 and the IED 41 when a new IED 41 is connected to the substation system 10.

  FIG. 11 is an explanatory diagram illustrating the contents of the DataSet 105 of the incorporation request message transmitted by the IED 41 according to the first embodiment.

  When a new IED 41 is connected to the substation network, the newly connected IED 41 first functions as the Publisher 120 in the GOOSE protocol 83. Then, the new IED 41 transmits, as the Publisher 120, an embedded request message including the contents of the DataSet 105 shown in FIG.

  The built-in request message is a GOOSE message 100 and includes identification information for the substation server 11 to identify the newly connected IED 41.

  The embedded request message includes MessageType 511, ConfigurationType 512, MACAddress 513, VLANPriority 514, VLANID 515, IEDName 516, and AuthenticationData 517 as parameters.

  MessageType 511 indicates an index of information included in the incorporation request message. ConfigurationType 512 indicates the purpose of connection of IED 41, such as whether IED 41 is newly added to the substation network (new addition) or is replaced with old IED 41 (addition by replacement).

  Note that the incorporation request message does not include the configuration type 512 or the configuration type 512 indicates only a new addition, so that the integration request message of the first embodiment only indicates that the IED 41 is newly added.

  MACAddress 513 indicates the sender of the embedded request message, and indicates the MAC address of the IED 41 newly connected to the substation network in this embodiment.

  VLAN Priority 514 indicates the priority of the VLAN. The VLAN ID 515 indicates a VLAN identifier. The IEDName 516 indicates identification information such as the name of the sender of the incorporation request message (that is, the newly connected IED 41). AuthenticationData 517 indicates identification information for authentication of the transmission source device.

  FIG. 12 is an explanatory diagram illustrating the contents of the DataSet 105 of the communication setting request message transmitted by the substation server 11 according to the first embodiment.

  The substation server 11 functions as the Publisher 120 when receiving a built-in request message including the contents shown in FIG. 11 from the IED 41. Then, the substation server 11 sends a communication setting request message including the contents shown in FIG. 12 to the IED 41 as a publisher 120 to the substation network.

  The communication setting request message is a GOOSE message 100 for notifying the newly connected IED 41 of communication parameters necessary for IP communication such as an IP address assigned to the newly connected IED 41.

  The communication setting request message includes Type 521, Error Code 522, DHCPPEnable 523, GoCBRef 524, IPAddress 525, Subnet 526, and Gateway Address 527 as parameters.

  Type 521 indicates an index of information included in the communication setting request message. Error Code 522 indicates whether or not processing such as IP address assignment has been completed normally. DHCPnable 523 indicates whether DHCP is valid.

  GoCBRef 524 indicates the reference name of the LN 50 corresponding to the IED 41. IPAddress 525 indicates the IP address assigned to the destination of the communication setting request message. Here, the transmission destination of the communication setting request message is the IED 41 newly connected to the substation network.

  Subnet 526 indicates the subnet mask of the transmission source of the communication setting request message (that is, substation server 11). Gateway Address 527 indicates the address of the gateway used for communication.

  FIG. 13 is an explanatory diagram illustrating the contents of the DataSet 105 of the IP connection completion notification message transmitted by the IED 41 according to the first embodiment.

  After the IED 41 has set the communication parameters included in the communication setting request message to itself, the IED 41 sends an IP connection completion notification message to the substation server 11. The IP connection completion notification message is a GOOSE message 100 including Type 531, Error Code 532, GoCBRef 533 and ARName 534.

  Type 531 indicates an index of information included in the IP connection request message. The ErrorCode 532 indicates whether or not the communication parameter setting notified from the substation server 11 has been normally completed. GoCBRef 533 indicates the reference name of the LN 50 corresponding to the IED 41. ARName 534 indicates the AR name of the source of the IP connection completion notification message (that is, the newly connected IED 41).

  The Publisher 120 is an identifier standardized by, for example, a standard in order to identify the GOOSE message 100 for configuring the substation system 10 and the GOOSE message 100 for other uses as shown in FIGS. 11 to 13. Furthermore, identifiers other than those used for general purposes are stored in the GOOSE header 103 as APPID.

  In addition, the Publisher 120 may store an identifier standardized in the standard as a GoID (corresponding to the entry 1045) in the GOOSE PDU 104 in order to identify the GOOSE message 100 for configuring the substation system 10.

  In addition, the Publisher 120 according to the present embodiment sends the GOOSE message 100 shown in FIGS. 11 to 13 as a destination that is not used for general purposes, for example, a multicast MAC address. The Publisher 120 of this embodiment may designate any MAC address other than the multicast MAC address as long as it is a MAC address that designates a plurality of devices including the substation server 11 as destinations.

  FIG. 14 is a sequence diagram illustrating processing when the new IED 41 according to the first embodiment is connected to the substation network.

  FIG. 14 shows the processing of the substation server 11 and the processing of the IED 41 when the IED 41 is newly connected to the substation network. In the following, the processing in the IED 41 and the substation server 11 is executed by the GOOSE program and the MMS program that each has. However, a physical device having the same functions as the GOOSE program and the MMS program may execute processing, and other programs other than the GOOSE program using the GOOSE protocol 83 and the MMS program using the MMS protocol 86 may be used. A part of the processing described below may be executed.

  Before the IED 41 connects to the substation network, the IEDConfigurator 300 sets the CID file 313 to the IED 41 using the method shown in FIG. 8 (410). The CID file 313 set here includes information stored in the incorporation request message.

  After setting by the IEDConfigurator 300, the IED 41 restarts and reflects the setting contents of the CID file 313. The IED 41 then connects to the substation network (420).

  After connecting to the substation network, the GOOSE program of the IED 41 starts sending the embedded request message including the contents shown in FIG. 11 to the substation network by multicast according to the GOOSE protocol 83 as the Publisher 120 (430).

  However, the incorporation request message in the first embodiment indicates that the IED 41 is newly added by not including the Configuration Type 512 or by indicating only the new addition of the Configuration Type 512. Further, the GOOSE program of the IED 41 stores the APPID indicating the incorporation request message in the GOOSE header 103 of the incorporation request message, and transmits the incorporation request message.

  After the sequence 430, the GOED program of the IED 41 receives the communication setting request message shown in FIG. 12, and further continues to transmit the embedded request message until the communication parameters for IP communication are set. This is because, in sequence 430, the IED 41 is not assigned an IP address and cannot perform IP communication with the substation server 11.

  The GOOSE program of the substation server 11 acquires the embedded request message, which is the GOOSE message 100, from the substation network by filtering and constantly monitoring the APPID included in the GOOSE header 103 as the Subscriber 110 (210). When the GOOSE program of the substation server 11 acquires the built-in request message, the GOOSE program may authenticate the device included in the IED 41 using the AuthenticationData 517 of the received built-in request message (220).

  When the substation network is a completely closed network and all the devices included in the newly connected IED 41 are safe, the GOOSE program of the substation server 11 authenticates the devices included in the IED 41 in sequence 220. It does not have to be.

  When authenticating the device of the IED 41, the GOOSE program of the IED 41 first stores the character string data encrypted with the common key in the Authentication Data 147 shown in FIG. Then, the GOOSE program of the substation server 11 decrypts the value of the AuthenticationData 147 with the same common key as the common key used by the GOOSE program of the IED 41 in the sequence 220, and collates that the original character strings match, thereby checking the IED 41. Authenticate the device provided by.

  After the sequence 220, the GOOSE program of the substation server 11 extracts an unused IP address from the list of IP addresses held in the memory or the auxiliary storage device of the substation server 11, and uses the extracted IP address as a communication parameter. (240). Here, the GOOSE program of the substation server 11 assigns other communication parameters (subnet mask of Subnet 526 and gateway address of Gateway Address 527) necessary for IP communication to IED 41 to IED 41.

  After the sequence 240, the GOOSE program of the substation server 11 stores information indicating the newly connected IED 41 in the SCD file 312 held in advance (250). Here, the information indicating the newly connected IED 41 is an access point attribute value and identification information included in the incorporation request message.

  The SCD file 312 held in advance by the substation server 11 stores information indicating the overall configuration of the substation system 10 managed by the substation server 11. The SCD file 312 is stored in a setting storage unit such as a memory of the substation server 11 or an auxiliary storage device.

  In the sequence 250, specifically, the GOOSE program of the substation server 11 generates and adds the description of the area 501 of the SCD file 312 shown in FIG. 9 using the IEDName 516 included in the received built-in request message. . Also, the GOOSE program of the substation server 11 sets the assigned IP address, subnet mask, and gateway address as access point attribute values in the area 502 (corresponding to the contents of the Communication element 403) of the SCD file 312. .

  The access point used here corresponds to the newly connected IED 41 and is identified by the IEDName 516 included in the received incorporation request message. An area 501 indicates that the communication element 403 of the IED 41 is stored in the area 502.

  After the sequence 250, the GOOSE program of the substation server 11 stores the multicast MAC address, the VLAN priority, and the communication parameters for GOOSE communication in the area 504 of the SCD file 312 as the communication parameters for GOOSE communication. , VLAN identifier is set. An area 503 indicates that an area 504 stores communication parameters for GOOSE communication.

  By the sequences 250 and 260, the GOOSE program of the substation server 11 can add the parameters of the substation network after newly connecting the IED 41 to the SCD file 312.

  After the sequences 250 and 260, the GOOSE program of the substation server 11 sends the communication setting request message shown in FIG. 12 to the substation network as the Publisher 120 (270). Here, the GOOSE program of the substation server 11 sends a communication setting request message by multicast communication according to the GOOSE protocol 83. The GOOSE program of the substation server 11 stores the APPID indicating the communication setting request message in the GOOSE header 103 of the communication setting request message, and sends out the communication setting request message.

  Further, the GOOSE program of the substation server 11 is necessary for the IP communication in the sequence 270, and stores the communication parameters assigned in the sequence 240 (the parameters of the IPAddress 525, the Subnet 526, and the Gateway Address 527) in the transmitted communication setting request message.

  Note that the GOOSE program of the substation server 11 may continue sending the communication setting request message until the IP connection completion notification message is received.

  The GOOSE program of the IED 41 acquires the communication setting request message from the substation network by filtering and constantly monitoring the APPID included in the GOOSE header 103 as a subscriber 110 (440).

  After the sequence 440, the GOED program of the IED 41 sets the communication parameters (IPAddress 525, Subnet 526, and Gateway Address 527) necessary for the IP communication included in the acquired communication setting request message as the communication parameters of the IED 41. Then, the MMS program of the IED 41 starts IP communication with the substation server 11 by restarting the IP protocol stack (450). Here, the MMS program of the IED 41 may establish a connection by IP communication with the substation server 11.

  After the IP communication is started by the sequence 450, the GOOSE program of the IED 41 stops sending the built-in request message that has been sent from the sequence 430 (455). As a result, the IED 41 allows the substation server 11 to reliably acquire the incorporation request message by multicast communication, and can stop useless multicast communication after setting the IP communication parameters.

  After the sequence 455, the GOED program of the IED 41 sends the IP connection completion notification message shown in FIG. 13 as the Publisher 120 according to the GOOSE 83 protocol (460). The GOED program of the IED 41 stores the APPID indicating the IP connection completion notification message in the GOOSE header 103 of the IP connection completion notification message, and transmits the IP connection completion notification message.

  The substation server 11 receives the IP connection completion notification message (280). Thereby, the setting of IP communication in the IED 41 is completed.

  The IED 41 that has become capable of IP communication does not need to publish an embedded request message while holding communication parameters for IP communication.

  If the IEDName 516 included in the received installation request message has already been stored in the SCD file 312 (for example, the area 501), the GOOSE program of the substation server 11 regards it as a reconnection of the existing IED 41 and newly receives it. The embedded request message may be ignored.

  After the sequence 280, the MMS program of the substation server 11 uses the ARName 534 included in the received IP connection completion notification message, and the IED 41 connected to the service of the MMS protocol 86 operating on TCP / IP according to the MMS protocol 86. Request sequentially. Here, the MMS program of the substation server 11 requests a service as the Client 130 from the IED 41 which is the Server 140.

  Specifically, the MMS program of the substation server 11 uses ARName and uses the MMS protocol 86 to obtain a service directory acquisition request, an LN list acquisition request, an object list acquisition request, a data list acquisition request, and the like. Services are sequentially provided to the IED 41.

  Then, as a response to the service, the IED 41 transmits the logical configuration information of the IED 41 (configuration information such as LN50, DO60, service 70, and DataSet 105 used by the service 70) to the substation server 11 (470). As a result, the MMS program of the substation server 11 acquires the logical configuration information of the IED 41 from the IED 41 (290).

  The logical configuration information is configuration information necessary for the MMS program of the substation server 11 to instruct the IED 41 to perform processing such as control and monitoring of the power transmission network using the MMS protocol 86. The IED 41 changes the monitoring method and the control method for the power transmission network in which the IED 41 is installed according to the method instructed by the MMS protocol 86 from the substation server 11.

  The MMS program of the substation server 11 adds the area 505 to the SCD file 312 for the connected IED 41 using the IEDName 516 included in the received incorporation request message. Then, the MMS program of the substation server 11 generates an IED element 404 including logical configuration information such as the LN 50, the DO 60, the service 70, and the DataSet 105. The generated IED element 404 is stored in the area 506 of the SCD file 312.

  After the sequence 290, the MMS program of the substation server 11 uses the file read service of the MMS protocol 86, and acquires the CID file 313 previously set in the IED 41 (300). Further, the MMS program of the IED 41 transmits the CID file 313 to the substation server 11 according to the MMS protocol 86 as a response to the file read service (480).

  Here, the MMS program of the substation server 11 requests the file read service as the Client 130 from the IED 41 that is the Server 140.

  Then, the MMS program of the substation server 11 uses the acquired CID file 313 to check the consistency of the IED element 404 generated in the sequence 290 (305).

  When matching is achieved and the generated IED element 404 is consistent, the MMS program of the substation server 11 officially registers the generated IED element 404 in the area 506 of the SCD file 312. When the newly added DataTypeTemplates attribute is stored in the acquired CID file 313, the MMS program of the substation server 11 stores the added DataTypeTemplates attribute and the generated IED element 404 in the area 506 of the SCD file 312. Add (310).

  Note that when the CID file 313 set in advance in the IED 41 is complete, the sequences 290 and 305 are unnecessary. The MMS program of the substation server 11 may add the logical configuration information indicated by the CID file 313 to the SCD file 312 as a new IED element 404 as it is.

  However, the MMS program of the substation server 11 combines the logical configuration information indicated by the CID file 313 and the logical configuration information such as LN50 and DO60 acquired by the sequence 290 by using the steps of sequences 290, 300, and 305 together. You may check for inconsistencies.

  If there is a contradiction, the MMS program of the substation server 11 may present an error message or error log to the user via the output device or the control station server 19 to which the substation server 11 is connected. Accordingly, the substation server 11 can debug the system configuration and avoid setting the SCD file 312 unlike the actual configuration.

  Examples of errors and warnings indicating that a contradiction has been detected include the following. That is, when the logical configuration information indicated by the CID file 313 does not include a part or all of the logical configuration information acquired by the sequence 290, the MMS program of the substation server 11 includes the LN 50 and the DO 60 that actually exist. It is determined that the generated IED element 404 is not defined, and it is determined that the generated IED element 404 includes a contradiction, and an error is output.

  Further, when some or all of the logical configuration information indicated by the CID file 313 is not included in the logical configuration information acquired by the service of the MMS protocol 86, the MMS program of the substation server 11 is defined in the SCL 500. It is determined that the LN 50 or the DO 60 is not operating on the hardware, and it is determined that the generated IED element 404 includes a contradiction, and an error is output.

  If the attribute and data type of the DO 60 indicated by the CID file 313 and the attribute and data type of the DO 60 acquired by the service of the MMS protocol 86 do not match, the MMS program of the substation server 11 executes the SCL 500 and the actual hardware. Therefore, it is determined that the attribute and data type of the DO 60 do not match, and it is determined that the generated IED element 404 includes a contradiction, and an error is output.

  After the SCD file 312 is generated by the sequence 310, the MMS program of the substation server 11 reparses the SCD file 312 including the information on the new IED 41, and recognizes information on the added IED 41 (320). As a result, the MMS program of the substation server 11 can instruct monitoring and control processing by the IED 41 based on the SCD file 312 including the information related to the newly connected IED 41 and the MMS protocol 86, and can control the processing of the IED 41. .

  Through the above processing, even in a substation network that does not use DHCP, the substation server 11 and the IED 41 use the GOOSE protocol 83 that allows communication even if an IP address is not assigned. Information necessary for IP communication can be exchanged from a situation in which it is not assigned. For this reason, after connecting the IED 41 to the substation network, the IED 41 can automatically establish IP communication in the substation network.

  This also allows the substation server 11 to access the IED 41 immediately after the connection of the IED 41 to the substation network. In addition, it is not necessary for a developer or the like to design in advance on a desk for IP communication in a substation network.

  Further, after starting the IP communication, the substation server 11 acquires the logical configuration information in the IED 41 from the IED 41 using the MMS protocol 86. Accordingly, the substation server 11 can instruct power control and monitoring processing by the IED 41 using the MMS protocol 86, and can realize the function of the IED 41 based on the IEC 61850 in the substation system 10.

  Then, by establishing the IP communication and acquiring the information of the IED 41 by the MMS protocol 86, a new IED 41 is added to the substation system 10 by plug and play without stopping the substation system 10. System 10 can be reconfigured.

  In the first embodiment, the IED 41 connected to the substation system 10 is a newly added IED 41. However, when the IED 41 is actually added, the existing IED 41 has the same function as the existing IED 41 because of a failure, near-life, or the like, other than when the IED 41 is newly added. It may be exchanged for IED41.

  The substation system 10 according to the second embodiment provides a method of changing the procedure for reconfiguring the substation system 10 according to the purpose of introduction, such as new addition or addition by replacement, when a new IED 41 is connected. To do.

  The substation system 10 of Example 2 is the same as the substation system 10 of Example 1 shown in FIG. The configurations shown in FIGS. 2 to 10, 12, and 13 are all the same in the first embodiment and the second embodiment.

  Hereinafter, the difference in processing from FIG. 14 will be mainly described with reference to FIG.

  The embedded request message of the second embodiment is different from the first embodiment and the second embodiment in that two types of information added by new addition and replacement are stored in the Configuration Type 512.

  FIG. 15 is a sequence diagram illustrating processing when the IED 41 according to the second embodiment is connected to the substation network.

  When connecting a new IED 41 to the substation network, a developer or the like who connects the IED 41 to the substation network stores a value indicating new addition as a connection purpose in the Configuration Type 512 in the sequence 410. 313 is set.

  In the sequence 430, the GOED program of the IED 41 starts to send an embedded request message storing a value indicating new addition to the configuration type 512 to the substation network.

  When the existing IED 41 is replaced with a new IED 41, the developer or the like sets the CID file 313 to store a value indicating addition by replacement as a connection purpose in the configuration type 512 in the sequence 410. As the IEDName (corresponding to IEDName 516), the same name as the existing IED 41 before the exchange is set in the CID file 313.

  Accordingly, in sequence 430, the GOED program of the IED 41 starts to send an embedded request message in which a value indicating addition by replacement is stored in the Configuration Type 512 to the substation network.

  The sequences 420 and 210 in the second embodiment are the same as those in the first embodiment.

  After the sequence 210, the substation server 11 determines whether the configuration type 512 of the received built-in request message indicates new addition or addition by exchange (230).

  When the Configuration Type 512 indicates a new addition, the substation server 11 executes the processes after the sequences 240 and 250 as in the first embodiment, and the IED 41 executes the processes after the sequence 440 as in the first embodiment. As a result, the substation server 11 can newly assign an IP address or the like to the IED 41 and control the new IED 41 by the MMS protocol 86, as in the first embodiment.

  On the other hand, when it is determined in sequence 230 that the Configuration Type 512 indicates addition by replacement, the substation server 11 performs the following processing for replacement.

  Specifically, when it is determined that the Configuration Type 512 indicates addition by replacement, the GOOSE program of the substation server 11 executes the sequence 240 shown in FIG. 14 and assigns an IP address to the newly connected IED 41.

  Then, the GOOSE program of the substation server 11 extracts the IEDName 516 included in the received incorporation request message. Then, the GOOSE program of the substation server 11 specifies the IED element 404 (area 506) and the communication element 403 (area 502) including the same name as the extracted IEDName 516 in the existing SCD file 312 (330).

  After the sequence 330, the GOOSE program of the substation server 11 rewrites the area 502 of the identified Communication element 403 with the newly assigned IP address and the information included in the embedded request message. Thereby, the GOOSE program of the substation server 11 changes the communication destination on the SCD file 312 to the newly connected IED 41 (340).

  After the sequence 340, the substation server 11 executes the sequences 270 and 280. Further, the IED 41 executes the sequences 440, 450, 455, and 460 in accordance with the communication setting request message in the sequence 270.

  When the IED 41 is replaced, the substation server 11 does not need to update the information (specifically, the IED element 404, etc.) of the SCD file 312 related to the configuration and service of the IED 41 because the IED 41 having the same functional configuration is switched. . For this reason, the MMS program of the substation server 11 executes the sequence 320 after the sequence 280 without executing the sequence 290 or the like. The substation server 11 reparses the updated SCD file 312 and ends the exchange of the IED 41.

  Thereby, the MMS program of the substation server 11 can instruct monitoring and control processing of the IED 41 according to the MMS protocol 86 using the information of the SCD file 312 related to the configuration and service of the IED 41 before replacement.

  Note that the above-described ConfigurationType 512 has two types of addition by new addition and replacement, but other values may be included. For example, when updating the function of the IED 41, the Configuration Type 512 may include a value indicating update, and when the IED 41 is explicitly deleted from the substation system 10, the Configuration Type 512 may include a value indicating deletion.

  When ConfigurationType 512 indicates an update, the GOOSE program of the substation server 11 does not update the communication parameters because the connection between the IED 41 and the substation network itself continues the conventional setting, and according to the function updated in the IED 41. The logical configuration information may be updated in the SCD file 312.

  In addition, such a system that automatically performs configuration may be reconnected after temporarily disconnecting the IED 41. For this reason, when the connection between the IED 41 and the substation network is disconnected, it is not desirable to immediately determine that the IED 41 has been deleted and delete the information of the IED 41 from the SCD file 312.

  Therefore, in order to explicitly delete the IED 41, the developer or the like may set the CID file 313 to store a value indicating deletion in the Configuration Type 512.

  When the Configuration Type 512 indicates deletion, the substation server 11 deletes the logical configuration information and communication parameter information of the IED 41 indicated by the IED Name 516 included in the received incorporation request message from the SCD file 312. Thereby, the substation server 11 can delete the IED 41 from the substation system 10 explicitly.

  As described above, when the IED 41 is connected by including information indicating the purpose of the connection in the built-in request message, the substation server 11 determines whether the connection is newly added or exchanged. The processing can be switched according to the purpose. And the method of comprising the substation system 10 which can be used not only at the time of the change of the structure of the substation system 10 but system operation, such as at the time of a failure and a periodical replacement | exchange, is realizable.

  In the present embodiment, GOOSE protocol 83 and MSS 86 are used as communication protocols. However, it is a communication protocol that communicates using different address designation methods, such as GOOSE protocol 83 and MMS protocol 86, and a message can be sent to a destination without designating a specific address as in GOOSE protocol 83. As long as the communication protocol can be used, any name protocol may be used.

  The present invention is not limited to the above-described embodiments, and includes various modifications. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. In addition, it is possible to add, delete, or replace another configuration for a part of the configuration of each embodiment.

  Each of the above-described configurations, functions, processing units, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as a program, a table, or a file that realizes each function can be placed in a recording device such as a memory, a hard disk, or an SSD (Solid State Drive), or a recording medium such as an IC card or an SD card.

  Further, the control lines and information lines indicate what is considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

11 Substation server 41 IED
50 LN (Logical Node)
60 DO (Data Object)
70 Service 83 GOOSE
86 MMS
312 SCD file 500 SCL file

Claims (11)

A network system configuration method comprising:
The network system includes a terminal that performs at least one of monitoring and control of a power transmission network, a server connected to the terminal, and a network connected to the server,
The method
A procedure for starting transmission of identification information for identifying the terminal to the network according to a first communication method when the terminal is connected to the network;
When the server acquires the identification information according to the first communication method via the network, the acquired identification information is stored in a setting storage unit, and communication information including an address assigned to the terminal is obtained. Transmitting to the network according to the first communication method;
The server allocates terminal information necessary for instructing the terminal to perform at least one process of monitoring and controlling the power transmission network according to a second communication method different from the first communication method. Requesting the requested terminal,
The server acquires the terminal information from the terminal according to the second communication method;
The server, see contains and a procedure for storing the acquired terminal information in the setting storage unit,
The procedure for starting the transmission of the identification information to the network includes information indicating exchange when the terminal is connected to the network by exchanging with another terminal connected to the network and the other terminal. Including the step of starting transmission of the identification information by including in the identification information information for identifying
In the method, when the acquired identification information includes information indicating the exchange, the server provides terminal information necessary for instructing the other terminal to perform at least one process of monitoring and controlling the power transmission network. configuring the setting specified from the storage unit, characterized by a free Mukoto steps that tell at least one process monitoring and control of the power grid to the terminal using the specific terminal information.   A network system configuration method comprising:
  The network system includes a terminal that performs at least one of monitoring and control of a power transmission network, a server connected to the terminal, and a network connected to the server,
  The method
  A procedure for starting transmission of identification information for identifying the terminal to the network according to a first communication method when the terminal is connected to the network;
  When the server acquires the identification information according to the first communication method via the network, the acquired identification information is stored in a setting storage unit, and communication information including an address assigned to the terminal is obtained. Transmitting to the network according to the first communication method;
  The server allocates terminal information necessary for instructing the terminal to perform at least one process of monitoring and controlling the power transmission network according to a second communication method different from the first communication method. Requesting the requested terminal,
  The server acquires the terminal information from the terminal according to the second communication method;
  The server stores the acquired terminal information in the setting storage unit,
  The terminal holds setting information preset in the terminal,
  The method
  A procedure in which the terminal generates the identification information based on the setting information;
  After the server acquires the terminal information from the terminal, according to the second communication method, causing the terminal to execute transmission of the setting information to the server;
  The server includes a procedure for outputting information indicating a warning when the acquired terminal information and the transmitted setting information contradict each other.   A network system configuration method comprising:
  The network system includes a terminal that performs at least one of monitoring and control of a power transmission network, a server connected to the terminal, and a network connected to the server,
  The method
  A procedure for starting transmission of identification information for identifying the terminal to the network according to a first communication method when the terminal is connected to the network;
  When the server acquires the identification information according to the first communication method via the network, the acquired identification information is stored in a setting storage unit, and communication information including an address assigned to the terminal is obtained. Transmitting to the network according to the first communication method;
  The server allocates terminal information necessary for instructing the terminal to perform at least one process of monitoring and controlling the power transmission network according to a second communication method different from the first communication method. Requesting the requested terminal,
  The server acquires the terminal information from the terminal according to the second communication method;
  The server stores the acquired terminal information in the setting storage unit,
  The first communication method is GOOSE (Generic Object Oriented System Event) protocol,
  The second communication method is an MMS (Manufacturing Message Specification) protocol,
  In the procedure for starting transmission of the identification information to the network, the terminal starts transmission of the identification information to the network by multicasting the identification information according to the GOOSE protocol. .   The configuration method according to claim 1, 2, or 3,
  A configuration method comprising: a step of stopping transmission of the identification information to the network when the terminal acquires the communication information via the network.   A server connected to the network,
  When a terminal that performs at least one of monitoring and control of a power transmission network is connected to the network, identification information for identifying the terminal is acquired from the terminal via the network according to a first communication method,
  Storing the acquired identification information in a setting storage unit;
  Transmitting communication information including an address assigned to the terminal to the network according to the first communication method;
  Requesting terminal information necessary for instructing the terminal about a power monitoring method or a control method according to a second communication method different from the first communication method, to the terminal to which the address is assigned,
  Obtaining the terminal information from the terminal according to the second communication method;
  The acquired terminal information is stored in the setting storage unit,
  The identification information includes information indicating an exchange and information for identifying the other terminal when the terminal is connected to the network by being exchanged with another terminal connected to the network;
  The server
  When the acquired identification information includes information indicating the exchange, the terminal information necessary for instructing the other terminal to perform at least one process of monitoring and control of the power transmission network is specified from the setting storage unit,
  A server that instructs at least one process of monitoring and control of the power transmission network to the terminal using the specified terminal information.   A server connected to the network,
  When a terminal that performs at least one of monitoring and control of a power transmission network is connected to the network, identification information for identifying the terminal is acquired from the terminal via the network according to a first communication method,
  Storing the acquired identification information in a setting storage unit;
  Transmitting communication information including an address assigned to the terminal to the network according to the first communication method;
  Requesting terminal information necessary for instructing the terminal about a power monitoring method or a control method according to a second communication method different from the first communication method, to the terminal to which the address is assigned,
  Obtaining the terminal information from the terminal according to the second communication method;
  The acquired terminal information is stored in the setting storage unit,
  The identification information is generated based on setting information preset in the terminal,
  The server
  After obtaining the terminal information from the terminal, according to the second communication method, causing the terminal to execute transmission of the setting information to the server,
  A server that outputs information indicating a warning when the acquired terminal information and the transmitted setting information contradict each other.   A server connected to the network,
  When a terminal that performs at least one of monitoring and control of a power transmission network is connected to the network, identification information for identifying the terminal is acquired from the terminal via the network according to a first communication method,
  Storing the acquired identification information in a setting storage unit;
  Transmitting communication information including an address assigned to the terminal to the network according to the first communication method;
  Requesting terminal information necessary for instructing the terminal about a power monitoring method or a control method according to a second communication method different from the first communication method, to the terminal to which the address is assigned,
  Obtaining the terminal information from the terminal according to the second communication method;
  The acquired terminal information is stored in the setting storage unit,
  The first communication method is GOOSE (Generic Object Oriented System Event) protocol,
  The server according to claim 2, wherein the second communication method is an MMS (Manufacturing Message Specification) protocol.   A terminal that performs at least one of monitoring and control of a power grid,
  When connected to the network to which the server is connected, according to the first communication method, start transmitting identification information for identifying the terminal to the network,
  From the server that acquired the identification information, communication information including an address assigned to the terminal is acquired according to the first communication method via the network,
  Terminal information necessary for instructing at least one of a power monitoring method and a control method by the terminal from the server is transmitted to the server according to a second communication method different from the first communication method. ,
  When connected to the network by being exchanged with another terminal connected to the network, the identification information includes information indicating exchange and information for identifying the other terminal in the identification information. Starting to transmit to the network.   A terminal that performs at least one of monitoring and control of a power grid,
  When connected to the network to which the server is connected, according to the first communication method, start transmitting identification information for identifying the terminal to the network,
  From the server that acquired the identification information, communication information including an address assigned to the terminal is acquired according to the first communication method via the network,
  Terminal information necessary for instructing at least one of a power monitoring method and a control method by the terminal from the server is transmitted to the server according to a second communication method different from the first communication method. ,
  Pre-set setting information is retained,
  Generating the identification information based on the setting information;
  A terminal that transmits the setting information to the terminal according to the second communication method according to an instruction from the server.   A terminal that performs at least one of monitoring and control of a power grid,
  When connected to the network to which the server is connected, according to the first communication method, start transmitting identification information for identifying the terminal to the network,
  From the server that acquired the identification information, communication information including an address assigned to the terminal is acquired according to the first communication method via the network,
  Terminal information necessary for instructing at least one of a power monitoring method and a control method by the terminal from the server is transmitted to the server according to a second communication method different from the first communication method. ,
  The first communication method is GOOSE (Generic Object Oriented System Event) protocol,
  The second communication method is an MMS (Manufacturing Message Specification) protocol,
  The terminal starts transmission of the identification information to the network by multicasting the identification information according to the GOOSE protocol. The terminal according to claim 8, 9 or 10 ,
When the communication information is acquired through the network, the terminal stops transmitting the identification information to the network.

Images