KR20220052654A - High availability distribution intelligence system using message transmission bus and intelligence cluster system - Google Patents

Abstract

The present invention provides an intelligent system for high-availability distribution which can support various forms of instruments or terminals. According to the present invention, the intelligent system for high-availability distribution comprises: an end processor performing communication with intelligent terminal devices installed at a plurality of points in a distribution system to receive measurement values at corresponding points and transfer a power flow control instruction; a message transmission device performing a message bus role of relaying data and service requests/responses in a loosely-coupled manner; a main device performing validity inspection of control requests and measurement values acquired by the end processor, performing shared information management for each site and storage management of measurement values/control histories, and making up a plurality of distributed server systems; a real-time operating information DB storing data for storage management of measurement values/control histories and management in a synchronized shared memory space of the distributed server systems; and an HMI providing a user interface for operating the distribution system.

Description

HIGH AVAILABILITY DISTRIBUTION INTELLIGENCE SYSTEM USING MESSAGE TRANSMISSION BUS AND INTELLIGENCE CLUSTER SYSTEM

The present invention relates to a next-generation high-availability intelligent distribution system, and more particularly, to an intelligent distribution system using a message transmission bus and having an intelligent cluster system.

Global interest in the environment is increasing the rate of distributed power generation using new and renewable energy, and the distributed power generation with irregular power generation characteristics is expanded according to the national renewable power diffusion policy (e.g., Renewable 3020 Implementation Plan). Due to the increased complexity of the distribution system, the difficulty in operating the power system is increasing.

On the other hand, the development of communication technologies such as LTE and 5G is applying various types of wireless communication network technology and intelligent technology to the purpose in terms of speed and distance in the power management field.

Therefore, in order to stably operate a power distribution system complicated by distributed power, installation of on-site branch management devices such as a large number of IoT sensors and intelligent terminal devices (FRTUs) that can manage irregular voltages, identify fault points, and quickly process fault section separation is expected to increase.

The expansion of distributed power supply and the increase in installation of IoT sensors and intelligent terminal equipment (FRTU) to manage them require new power distribution management system technology due to the large capacity, various types of data acquired for distribution system operation, and real-time data processing requirements. do.

TDAS (Total Distribution Automation System), developed in 2000, is a SCADA-type system that provides only simple functions for monitoring and controlling the distribution system.

In addition, it is difficult to provide functions such as voltage management and fault point isolation so that commanders can efficiently manage the increasingly complex distribution system due to the limited functional expansion of TDAS.

Considering the situation in which the scope of distribution system operation is scheduled to be expanded from the business unit unit to the headquarters (center) unit, the TDAS for current business unit operation handles mass failures for FI (Fault Indicator) events that occur in large numbers due to disasters/disasters. will face limitations in

Therefore, in the present invention, based on the latest ICT convergence technology and flexible connection of various power equipment, the efficiency of the distribution system management system for accommodating a large number of distributed power sources and various IoT sensors and intelligent terminal devices (or of future distribution system operation) efficiency) measures are desired.

Republic of Korea Registration No. 10-2036243

An object of the present invention is to provide a highly available intelligent distribution system using a message transmission bus capable of mutually supporting various types of devices or terminals.

A high-availability intelligent distribution system according to an aspect of the present invention includes: a front-end processor that communicates with intelligent terminal devices installed at a plurality of points in a distribution system to receive measurement values and transmit power flow control instructions at the corresponding points; a message transmission device serving as a message bus relaying data and service request/response in a loosely-coupled manner; a main device configured to perform validation of measurement values and control requests acquired by the front-end processor, manage shared information for each site and store and manage measurement values/control history, and configure a plurality of distributed server systems; a real-time operation information DB for storing management and measurement values/control history in a synchronized shared memory space of the distributed server system and storing data for management; And it may include an HMI that provides a user interface for the operation of the distribution system.

Here, it may further include a storage device for classifying and storing the acquired measurement value, control history and system information based on business offices, distribution lines, and facilities.

Here, the main device may form a main device clustering system with other main devices - a function of mutual monitoring and recovery between the main devices and a role of an integrated server.

Here, the shear processor is communicatively connected with intelligent terminal devices to collect power data for each major point in real time, and the intelligent terminal device disposed at each point provides information on voltage or power management of the installation point in real time. can be acquired and transmitted to the shear processor periodically or eventively.

Here, the front-end processor transmits the routing keyword to the message transmission device in order to transmit the measurement value obtained from the intelligent terminal device and the unit function module that wants to receive the measurement value, and the message transmission device corresponds to the routing keyword You can search for a message channel and deliver the measurement value to the message queues constituting the channel.

Here, the message transmission apparatus includes: a message queue block having message queues communicatively connected to a corresponding unit function module in a Subscribe/Publish method; a node connection management module for managing communication linkage between the unit function modules on a network; a transport channel management module for managing creation/deletion of a logical transport channel for message transmission and a connection setting between the channel and the message queue; a transport rule management module that connects a message to a corresponding message queue according to the message transport rule; a message queue management module for creating and deleting the message queue and managing messages in the message queue; a message transmission module for inputting and outputting messages to and from the storage according to the request of the client; and a message duplication module for duplicating and managing messages in the storage.

Here, the main unit, the main unit cluster for performing load balancing processing and data loss/non-interruptible failover for system data processing load distribution; a system information manager that performs system acquisition data processing functions such as real-time data management, measurement/event management, alarm management, and history management; and a primary device manager that performs start/stop control and monitoring of other primary devices constituting the primary device cluster.

Here, the real-time operation information DB is distributed and managed on a plurality of servers, and supports high-speed data synchronization when changing/adding real-time system operation information, and may provide an accessible SQL-like API.

Here, the real-time operation information DB includes: a distributed data synchronization unit for performing data synchronization; Distributed data mutual management unit for real-time data management of system operation; and a distributed data processing unit that performs distributed processing of real-time data.

Here, the HMI includes at least one of the result of determination of failure at a specific point calculated by the main device and the status data for a specific point acquired from the real-time operation information DB - voltage, load amount, load pattern, generation amount and electricity quality - can be printed.

Here, the HMI may include a display module as a visual interface for a user; HMI main module that performs data processing for user provision; and an interface between modules for performing a data exchange operation through communication linkage with the real-time operation information DB and the message transmission device.

An intelligent cluster system according to another aspect of the present invention includes: a main device cluster that performs load balancing processing and data loss/non-interruptible failover for systematic data processing load distribution; a system information manager that performs system acquisition data processing functions such as real-time data management, measurement/event management, alarm management, and history management; and a plurality of main devices including a main device manager that monitors and controls the state of the main device process being operated.

Here, the system information manager, a real-time data management unit for managing the real-time data shared by the unit function module; a measurement/event management unit that acquires measurement/event data from a cooperative system, updates real-time data values, and updates quality values; an alarm management unit that receives measurement/event data from the linked system, generates and transmits alarms and events; an editing management unit for updating and disseminating facility information according to system editing; a control management unit receiving a control command from the HMI and performing control processing; and a history management unit that stores the history in a database in real time and periodically.

Here, the primary device cluster may include: a failure monitoring/action unit for monitoring failures occurring in the primary devices and correcting the detected failures; and a master management unit for selecting and changing a primary device performing a master role among the primary devices.

Here, the primary device manager may include: a primary device process status monitoring unit configured to monitor the primary device process and display an execution history and an alarm/event history of the primary device process; and a main device process start control unit that performs On/Off control for the main device process.

Here, it may further include a real-time operation information DB for operating real-time data for system operation.

Here, the main device configures a data model of distribution operation facilities to initialize the real-time data configuration and value, and when a data value is acquired through measurement/event reception of a field terminal device, updates the real-time data value, and edits the system When a configuration change occurs according to the , the configuration of real-time data may be updated in real time by receiving a corresponding message.

Here, the main device constructs a data model that can share real-time status information of facilities in the distribution system, creates it in the real-time operation information DB, and transmits data acquired from a shear processor in charge of communication with an intelligent terminal device in the field. It can be managed in the real-time operation information DB.

Here, the real-time operation information DB includes: a distributed data synchronization unit for performing data synchronization; Distributed data mutual management unit for real-time data management of system operation; and a distributed data processing unit that performs distributed processing of real-time data.

Here, the distributed data mutual management unit includes: a Data Export module capable of storing real-time data stored on a table as a file; a data import module for loading data stored as a file into the table; Data Replication module that can restore data using Redo Log to cope with failure; and a Data Dump module capable of storing instance data of the real-time operation information DB.

Here, the distributed data processing unit includes: a transaction processing module for processing transaction data generated for real-time data processing; a data dictionary module for managing the operation management and data generation information of the real-time operation information DB; a table processing module for managing tables for real-time data storage; And it may include a shared memory management module for managing the read/write and storage area of real-time data in the shared memory.

Here, the distributed data processing unit includes: a Redo Log module for real-time data recovery; and an index management module for performing index management based on the B-Tree algorithm for quick access to real-time system operation information.

Here, the distributed data synchronization unit includes: a data synchronization module for synchronizing corresponding data stored in storages of a plurality of distributed servers; and a remote process module supporting a remote operation means for the storages of the plurality of distributed servers.

When the intelligent system for high availability distribution using the message transmission bus according to the spirit of the present invention having the above configuration is implemented, there is an advantage in that various types of instruments or terminals can be mutually supported.

The high availability intelligent distribution system using the message transmission bus of the present invention has the advantage that it can be utilized in fields such as SCADA systems and smart cities for the purpose of facility monitoring/control.

The high availability intelligent distribution system using the message transmission bus of the present invention has the advantage that it can be utilized as an integrated operation technology for power facilities based on the communication linkage of various intelligent devices and technologies such as a large amount of data collection/storage/analysis.

1 is a block diagram of a next-generation high-availability distribution intelligent system according to an embodiment of a technology realizing the spirit of the present invention.
FIG. 2 is a detailed block diagram illustrating an embodiment of the message transmitting apparatus of FIG. 1;
3 is a conceptual diagram illustrating the role of a main device for real-time data processing.
Fig. 4 is a detailed block diagram showing an embodiment of the main device of Fig. 1;
Fig. 5 is a block diagram showing an embodiment of a main unit (intelligent) cluster system in which the main unit of Fig. 1 is implemented in a clustering operation processing method.
6 is a block diagram illustrating the concept of a real-time operation information sharing DB according to the spirit of the present invention.
7 is a block diagram showing a detailed configuration of the real-time operation information DB of FIG.
8 is a conceptual structural diagram illustrating a key/value management method in real-time operation information sharing.
9 is a structural diagram illustrating a B-Tree Index structure applicable to a real-time operation information DB.
10 is a conceptual diagram illustrating a real-time data synchronization process;
Fig. 11 is a block diagram showing a detailed configuration of the HMI of Fig. 1;
12A-12D show various HMI user-provided screens.
13 is a flowchart showing a procedure for receiving system measurement values up to the HMI.
Fig. 14 is a flowchart showing a control procedure from the HMI to the intelligent terminal device;
Fig. 15 is a block diagram showing the configuration of a main clustering server;
Fig. 16 is a block diagram showing the configuration of program modules as a main device system module;
Fig. 17 is a block diagram showing the main device load balancing - message distribution process.
Fig. 18 is a block diagram illustrating the main device load balancing - periodic distribution allocation process.
Fig. 19 is a block diagram showing a primary device failover - a primary device cluster failover process.
Fig. 20 is a block diagram showing a primary device failover - a primary device Service failover process.
21 is a block diagram showing the main device expansion - the main device cluster expansion process.
22 is a block diagram showing the process of main device extension - main device service extension.
23 is a block diagram showing a process of installing a main device - a main device cluster.
Fig. 24 is a block diagram showing a process of installing a main device - a main device service removing process;
Fig. 25 is a block diagram showing a control command data processing flow;
Fig. 26 is a control result data processing flow chart - a block diagram showing a control result receiving process;
27 is a control result data processing flow chart - a block diagram illustrating an event reception process according to control.
28 is a block diagram illustrating a measurement/event data processing process.

In describing the present invention, terms such as first, second, etc. may be used to describe various components, but the components may not be limited by the terms. The terms are only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component.

When a component is referred to as being connected or connected to another component, it may be directly connected or connected to the other component, but it can be understood that other components may exist in between. .

The terminology used herein is used only to describe specific embodiments, and is not intended to limit the present invention. The singular expression may include the plural expression unless the context clearly dictates otherwise.

In this specification, the terms include or include are intended to designate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, and includes one or more other features or numbers, It may be understood that the existence or addition of steps, operations, components, parts, or combinations thereof is not precluded in advance.

In addition, shapes and sizes of elements in the drawings may be exaggerated for clearer description.

Currently, the stable operation of the distribution system is made by the personal capabilities of the commanders who use the TDAS system. However, in the future, we are faced with a situation in which it is necessary to accept unlimited distributed power sources of individual operators, accommodate various intelligent terminal devices, process frequent events and measurement data of the distribution system, and perform wide-area operation of the distribution system at the headquarters (center) unit.

The present invention proposes a distribution system operating system that provides various data analysis processing, system non-stop operation, dynamic function expansion, large-capacity data processing and real-time data sharing functions as a new technology for responding to changes in the distribution system.

1 is a block diagram of a next-generation high-availability distribution intelligent system according to an embodiment of a technology realizing the idea of the present invention.

The high availability intelligent distribution system using the real-time message transmission bus shown communicates with intelligent terminal devices installed at multiple points in the distribution system to receive (current/voltage) measurement values and transmit power flow control instructions at the points. shearing processor 110 to perform; a message transmission device 200 serving as a message bus relaying data and service request/response in a loosely-coupled manner; Validation of the measurement value and control request acquired by the shear processor is performed, shared information management for each site (eg, business office and/or distribution line) and storage management of measurement values/control history are performed, and a plurality of distributed a main unit 300 constituting a server system; a real-time operation information DB 500 for storing management and measurement values/control histories in a synchronized shared memory space of the distributed server system and storing data for management; And it may include an HMI 600 that provides a user interface for operation of the distribution system.

According to implementation, the storage device 400 for storing the acquired measurement values, control history, and system information separately based on business offices, distribution lines, and facilities may be further included.

The illustrated shear processor 110 may perform communication with intelligent terminal devices installed at a plurality of points in the distribution system to receive current/voltage measurement values and control power flow at the corresponding points. The current/voltage measurement value acquired by the front-end processor 110 may be transmitted to the main device 300 through the message transmission device 200 .

The acquired measurement value may be separated by the main unit 300 on the basis of the business office and the distribution line, and may be stored in the storage device 400 and the real-time operation information DB 500 . The storage device 400 manages the history of all data generated in the system, and the real-time operation information DB 500 may serve to provide status data of the current system.

The illustrated front-end processor 110, as a main function, is responsible for communication connection with intelligent terminal devices that monitor/control power flow at multiple points in the distribution system. Here, the distribution system refers to a flow of transmitting power produced through a power consumer consuming power supplied from a power producer or a renewable energy power generation facility to the power producer.

For example, it refers to a power flow that supplies electricity to a general household that consumes electricity supplied from a power producer such as KEPCO or electricity produced by using a facility such as a solar power generator provided in the home.

The disclosed technology is for monitoring the bidirectional power flow rather than simply monitoring the power flow provided from the power producer, which is to monitor and control the quality of power transmitted and received between the power producer and the power provider.

On the other hand, a plurality of main points are designated to monitor/control the power flow of the distribution system, and intelligent terminal devices (11, 12 ~ 1n, 1m) for monitoring/controlling the power flow for each point are installed in the field. . In order to stably supply power to power consumers, the power flow in the distribution system is complicated because power input and cut-off are frequently performed remotely using intelligent terminal devices (11, 12 ~ 1n, 1m) at a plurality of major points. has a form

Here, the shear processor 110 communicates with the intelligent terminal devices 11, 12 to 1n, and 1m in order to collect power data for each major point in real time. The intelligent terminal devices 11, 12 to 1n, 1m disposed at each point acquire information about voltage or power management of the installation point in real time and transmit it to the shear processor 110 periodically or eventively.

Meanwhile, different types of intelligent terminal devices may be disposed at each point. If the same type of intelligent terminal device is deployed from the stage of realizing the first distribution system and power data of the same type or standard is collected based on this, the integrated power data is transmitted without going through new development such as separate new data modeling and communication protocol support. Although it is possible to use it, more management points may be added to the actual distribution system depending on the situation, and the roles of these points may be different, so the types or models of intelligent terminal devices that manage this point may also be different.

FIG. 2 is a detailed block diagram illustrating an embodiment of the message transmission apparatus of FIG. 1 .

The illustrated message transmission device 200 is a main function, and as a function module responsible for real-time data transmission between the front end processor 110, the main unit 300, and the HMI 600, which are unit function modules constituting the next-generation distribution system operating system. It plays a role for processing a large amount of small data transmission and expanding the nonstop function. In the description of the present invention, the unit function module includes even the intelligent terminal devices 11, 12 to 1n, 1m of FIG. It is a concept that includes each block as well.

The message transmission device 200 serves as a message bus supporting data transmission and service request/response to support mutual linkage of unit function modules performing a specific function in a loosely-coupled form.

For example, a routing keyword is transmitted to the message transmission device 200 in order to transmit the measurement value acquired from the intelligent terminal device and the measurement value to the unit function module that wants to receive the measurement value from the shear processor 110, which is a kind of unit function module. In this case, the transport rule management module 250 of the message transmission device 200 may search for a message channel corresponding to the routing keyword and transmit the measurement value to the message queues 280 constituting the channel. In addition, since all unit function modules are communicatively connected to the related message queue 280 in the Subscribe/Publish method, the value transmitted to the corresponding message queue 280 is automatically transferred to the corresponding unit function module and processed. At this time, when a value is transmitted from a specific message queue 280, the corresponding message queue 280 is deleted immediately to prevent duplicate data from being present in the power control system.

For example, the illustrated message transmission device 200 includes a node connection management module 220 that manages communication linkage between unit function modules on a network, creation/deletion of a logical transmission channel for message transmission, and management of connection settings between channels and message queues. The transport channel management module 230, the transport rule management module 250 that connects the message to the corresponding message queue 280 according to the message transport rule, creates/deletes the message queue, and manages the messages in the message queue 280 It may be composed of a message queue management module 240 , a message transmission module 210 for inputting and outputting messages to and from the storage according to a client's request, and a message replication module 260 for copying and managing messages in a distributed storage.

Compared with the existing technology, the existing TDAS has a one-way data delivery system that transmits real-time data acquired from the system through Agworks middleware, while the TDAS database (DB) stores the data of the previous situation after the action was completed.

On the other hand, the intelligent distribution system according to the spirit of the present invention is provided with a message transmission device capable of two-way data transfer instead of the existing agworks middleware that performs one-way data transfer. All functional modules of the distribution system operating system have individual communication channels, and real-time data can be transmitted to the communication channel of the corresponding functional module by the message routing module.

Basically, the message transmission device 200 supports the message format in order to support data exchange between unit function modules configured in the headquarters. Data messages such as measurement/event messages, control/measurement command messages, and alarm/event messages sent and received between each unit function module are configured in the Json [JavaScript Object Notation] format and are messages that can express various data, not fixed messages. you can change it.

For example, when a control/measurement command as shown in Table 1 below is transmitted from the HMI 600 as a control/measurement command message, the main device 300 performs validation of the control command and then transmits the command to the shear processor 110 . can

For example, as a command result message, when the result of the control/measurement command as shown in Table 2 below transmitted from the HMI 600 is transmitted from the shear processor 110, the main device 300 performs the control result validation check and then the HMI ( 600) can be transmitted. In addition, when processing for the Tag and Limit setting commands is completed, the control result may be transmitted to the HMI 600 . In this case, the control history may be stored in the storage device 400 .

For example, when tag and limit settings are transmitted from the HMI 600, the main device 300 performs the tag and limit settings of the corresponding terminal device according to the standards of Tables 3 and 4 below, and updates the real-time data of the corresponding point. can In case of tag setting, an alarm/event can be generated accordingly. In this case, the setting history may be stored in the storage device 400 .

For example, as a system editing function according to the standard of Table 5 below, the primary device 300 may acquire edit contents from the system/real-time storage device 400 and update the real-time data configuration. When the update is finished, the application of system editing is transmitted to each unit function module, so that it is updated with the latest system information.

For example, as measurement/event processing according to the standards of Table 6 below, when measurement/event is transmitted from the shear processor 110, the main device 300 updates real-time data, generates an alarm/event, and delivers it to each unit function module. can

For example, as alarm/event processing according to the standards of Table 7 below, measurement/event transmitted from the shear processor 110, tag setting, system change notification, etc. may be generated and delivered to each unit function module by generating an alarm/event. In this case, the generated alarm/event history may be stored in the storage device 400 .

Compared with the existing technology, the existing TDAS can process only the data map defined based on the DNP index point of the intelligent terminal device. TDAS redevelopment is necessary to support

The message transmission device 200 according to the spirit of the present invention supports the user-defined message format of the Json type as described above to process new data such as new types of intelligent terminal devices and systematic analysis of Study Mode without redevelopment. there is.

3 is a conceptual diagram illustrating the role of a main device for real-time data processing.

The illustrated main device 300 is a main function, which constructs a data model that can share real-time status information of facilities in the distribution system, creates it in the real-time operation information DB 500, and is responsible for communication with the intelligent terminal device in the field. The data acquired from the shear processor 110 is managed in the real-time operation information DB 500, and alarms and events generated through comparative analysis can be delivered to all required unit function modules. In addition, data acquired for history management and calculated data such as communication success rate and time series may be stored in the storage device 400 in real time or periodically.

4 is a detailed block diagram illustrating an embodiment of the primary device of FIG. 1 .

5 is a block diagram illustrating an embodiment of a primary device (intelligent) cluster system in which the primary device of FIG. 1 is implemented in a clustering task processing method.

Table 8 below defines the roles of the internal functional modules of the main device.

The main device of a more advanced implementation may be the intelligent (main) cluster system of FIG. 5 with a clustering management function. In this case, the main unit 300 operates multiple servers as Multi-Active and uses a clustering method that operates as a single system, increases the speed of processing large amounts of data through load balancing of data processing, and recovers without data loss and non-stop failure can support

In addition, by periodically monitoring the load of the node servers constituting the main unit 300 cluster system, data processing load balancing is performed, and the state of the main unit 300 process is monitored to perform data loss and non-stop failover in case of failure. can do.

A specific example of the configuration and failover of the clustering server operating like the above-described one system will be described later.

The illustrated intelligent (main unit) cluster system includes: a main unit cluster 320 that performs load balancing processing and data loss/non-interruptible failover for systematic data processing load distribution; a system information manager 340 that performs system acquisition data processing functions such as real-time data management, measurement/event management, alarm management, and history management; and a primary device manager 360 that performs start/stop control and monitoring of other primary devices constituting the primary device cluster.

The system information manager 340 of the illustrated main device 300 includes a real-time data management unit 341 for managing real-time data shared by unit function modules; a measurement/event management unit 342 that acquires measurement/event data from the cooperative system, updates real-time data values, and updates quality values; an alarm management unit 348 that receives measurement/event data from a linked system, generates and transmits alarms and events; an editing management unit 345 that updates and propagates facility information according to system editing; a control management unit 344 receiving a control command from the HMI and performing control processing; and a history management unit 346 that stores the history in a database in real time and periodically.

The real-time data management unit 341 manages real-time data shared by all unit function modules. The real-time data is operated through the real-time operation information DB 500 , and the main unit 300 may initialize the real-time data configuration and values by configuring the data model of the distribution operation facilities. The initialization method may be configured by acquiring all terminal device information from the system/real-time storage device 400 and modeling real-time data as Key/Value.

In order to maintain the latest real-time data, the real-time data value may be updated when the data value is obtained through the measurement/event reception of the field terminal device from the shear processor 110 . Also, real-time data values according to TLQ (Tag, Limit, Quality) settings are updated. When a configuration change occurs due to system editing, a corresponding message may be received and the configuration of real-time data may be updated in real time.

The measurement/event management unit 342 receives measurement/event data from the front end processor 110 and the associated system to process and manage it. Acquired data can update real-time data values, generate alarms and events according to the set TLQ (Tag, Limit, Quality), or update quality values such as exceeding the upper limit, communication failure, and non-response of the terminal device. The calculation formula set by can be performed.

The alarm management unit 348 may receive measurement/event data from the front end processor 110 and the linked system, generate an alarm and an event, and deliver it to all necessary unit function modules and the linked system. The occurrence of alarms and events can be processed by first comparing values with existing data, and generating appropriate alarms and events according to the set TLQ. In addition, alarm and event occurrence history may be stored in a database.

The control manager 344 may receive a control command from the HMI 600 and perform control processing. The control command is transmitted to the front end processor 110 through validation, receives the result of the control command execution by the front end processor 110, updates the value, and transmits the control result to the HMI 600 through the control result validation check can The control history may be stored in a database.

The history management unit 346 stores the history in a database in real time and periodically so that it can be utilized. It is possible to store real-time data history by receiving measurement/event data from the front end processor 110 and the linked system, and store analog data, communication success rate, user-set time series data, etc. according to a set period.

Compared to the existing technology, the existing TDAS operates two systems in an Active-Standby mode to cope with system failures. Therefore, there is a void in the operation of the distribution system during active-standby conversion.

On the other hand, in the main device 300 according to the spirit of the present invention, in order to prevent a situation in which the distribution system operation function modules are stopped due to the occurrence of a self-failure of the message transmission device, several data processors are bundled in a cluster form to cope with the failure without interruption. provide technology.

In addition, this clustering technology can cope with a situation of insufficient processing capacity by introducing a new data processor in a non-stop state when the processing capacity for processing the failure signals (FI) coming up in large quantities from the distribution system is insufficient in the event of a natural disaster such as a typhoon.

Therefore, since the performance of the data processors can be utilized to the fullest, wide-area operation in the headquarters (center) unit is possible even with a small number of data processors, resulting in low cost construction and reduced maintenance.

6 is a block diagram illustrating the concept of a real-time operation information sharing DB 500 according to the spirit of the present invention.

7 is a block diagram illustrating a detailed configuration of the real-time operation information DB 500 of FIG. 1 .

A general TDAS system provides historical data consisting of measured measurement data, switch status, and FI events as a database (DB) for data analysis for distribution system operation. This causes a problem in that as the capacity of the data managed in the database increases, the data provision speed decreases.

In the present invention, in order to solve this problem, the distribution system operation is a real-time data sharing space that provides the recently measured data, switch state values, and FI event values in the distribution system for data analysis by configuring it with the center of the business office DL. A real-time operation information sharing DB 500 is proposed.

The illustrated real-time operation information DB 500 implements the main functions, and in order to operate the distribution system, the next-generation distribution operating system is a unit function module, such as the main unit 300, the HMI 600, and the shear processor 110. It has function modules. These unit function modules are operated in a distributed computing method so that various unit functions can be further extended. These unit function modules may request real-time system operation information such as voltage/current measurement values of a specific time period, switch status, and system topology acquired from the distribution system in common. Accordingly, the next-generation power distribution operating system may provide a real-time operation information DB 500 function to share real-time system operation information between unit function modules.

The real-time operation information DB 500 is a distributed memory DB that is distributed and managed on a plurality of servers (which may also be a server performing the role of the main device 300), and high-speed data synchronization when changing/adding real-time system operation information support, and can provide a SQL-like API that unit function modules can access this operation information.

The real-time operation information DB 500 stores and manages real-time system operation information in a key/value method in a memory, and may also support index technology for quick access to data.

As shown, the real-time operation information DB 500 includes a distributed data synchronization unit 550 for performing data synchronization with respect to the real-time operation information DB 500; Distributed data mutual (move) management unit (read/load/copy/restore) 520 for real-time data management of system operation; and a distributed data processing unit (with index/shared memory/table) 560 that performs distributed processing of real-time data.

As shown, the distributed data movement (mutual) management unit 520 includes a Data Export module 522 that can store real-time data stored on a table as a file; Data Import module 524 for loading data stored as a file into a table; Data Replication module 526 capable of restoring data using a redo log to cope with failure; and a Data Dump module 528 capable of storing instance data of the real-time operation information DB.

As shown, the distributed data synchronization unit 550 includes a data synchronization module 552 for synchronizing corresponding data (eg, mirroring data or copy data) stored in the storages of a plurality of distributed servers; and a remote process module 554 that supports remote operation means for the repositories of the plurality of distributed servers.

8 is a conceptual structural diagram illustrating a key/value management method in real-time operation information sharing.

To support the development of new unit function modules using the real-time operation information DB 500, APIs are provided to perform real-time data creation/deletion/update/inquiry tasks. The API may provide a key/value method data processing function of the NoSql method suitable as shown in FIG. 8 in order to operate the large-capacity real-time data of the real-time operation information DB 500 . The real-time operation information DB 500 may support three types of Key/Value structures as shown.

As shown, the distributed data processing unit 560 includes a transaction processing module 561 for processing transaction data generated for real-time data processing; a data dictionary module 562 for managing the operation management and data generation information of the real-time operation information DB; a table processing module 565 for managing tables for real-time data storage; It may include a shared memory management module 568 that reads/writes real-time data to the shared memory and manages the storage area.

Additionally, the distributed data processing unit 560 includes a Redo Log module 566 for real-time data recovery; and an index management module 566 for performing index management based on the B-Tree algorithm for quick access to real-time system operation information.

The real-time operation information DB 500 locks the real-time data in the preempted transaction when the same real-time data is simultaneously changed for sequential processing when a transaction occurs in order to maintain data integrity, and releases the lock when transaction processing is completed. Data integrity can be maintained by making it available to other transactions. In addition, for automatic lock release, the lock transaction process detects an abnormal state, and when an abnormal state occurs, all corresponding changes are canceled to prevent data errors from occurring.

9 is a structural diagram illustrating a B-Tree Index structure applicable to a real-time operation information DB.

An index management module 564 is provided for fast processing of real-time data. The real-time operation information DB 500 has a characteristic that, once formed, key value changes (Insert/Update/Delete) of real-time data do not occur frequently, and real-time data inquiry occurs frequently. Accordingly, the index uses the B-Tree algorithm to improve data inquiry speed, and the index structure may have, for example, the B-Tree structure of FIG. 6 .

The real-time operation information DB 500 is provided with a redo log module 566 that records the application log of transaction changes for recovery when an error occurs in real-time data, and uses the stored redo log to provide a real-time operation information DB 500 can be restored

10 is a conceptual diagram illustrating a real-time data synchronization process.

The real-time operation information DB 500 may have an operating environment configured in a distributed server manner, and this configuration is advantageous from various viewpoints. Real-time data synchronization is supported for the integrity of operational information on distributed servers, so that data changes occurring in the real-time operational information DB 500 operated by each server can be synchronized with the real-time operational information DB 500 operated in other servers. . Even if a failure occurs in one real-time operation information DB 500 operating on the distributed server, it can be supported so that the entire system can be operated without interruption. Depending on the implementation, the server constituting the main device 300 provided for each site (business office) may also constitute the distributed server.

11 is a block diagram illustrating a detailed configuration of the HMI 600 of FIG. 1 .

12A-12D show various HMI user-provided screens.

The illustrated HMI 600 is a main function, and a user may provide a user interface function for operation of the distribution system.

The HMI 600 may output a result of determining whether a specific point is faulty calculated by the main device 300 and status data for a specific point acquired from the real-time operation information DB 500 . Here, the status data may include at least one of a voltage for a specific point, a load amount, a load pattern, a power generation amount, and an electricity quality.

The HMI 600 may be viewed as a kind of system for the purpose of providing an intuitive screen that can grasp the status of facilities at a glance through various visualization techniques and topology service provision based on topography. For example, by acquiring real-time data and system information from the real-time operation information DB 500, the message transmission device 200, and the storage device 400, TLQ (Tag, Limit, Quality) setting, control validation and voltage/current trend and Facility information can be provided.

The structure of the HMI 600 is, as shown in FIG. 11, a display module 620 as a visual interface for the user, and an HMI Main Module 640 that performs data processing for the user. , an interface 680 between modules, and each detailed configuration is as follows.

The display module 620 may provide a system diagram, Dashboard, system status and facility information screen for the purpose of serving as a user interface for the user to monitor the distribution system status and control facilities through a monitor. For example, after loading the facility information and the schematic diagram stored in the storage device 400 when the HMI 600 is started, a real-time value is received from the real-time operation information DB 500 and the message transmission device 200 to provide a large amount of facility object information. Display can be processed quickly without delay.

The HMI main module 640 may acquire data from other unit function modules and then perform data processing according to the purpose. By combining the processed data with UI elements so that the user can easily grasp it, the simple data obtained from the field can be converted into a meaningful information form required for the user to operate the distribution system.

The common UI 641 provided in the HMI main module 640 configures the graphic engine module so that there is no screen break or delay display when a large amount of raster and vector graphic elements are displayed on the monitor screen, and between multiple screens or between multiple screens or graphics The UI component data mapping module can be used to perform data interworking between objects. In addition, it is possible to minimize the redundancy of development products by configuring the printing and capture functions for screen output, such as toolbars, tab views, and menus, which are commonly used on multiple screens, into modules.

The UI setting module 644 provided in the HMI main module 640 can freely arrange and arrange the layout of the HMI screen used by the user. The screen layout for each user is stored in the storage device 400, and when the HMI 600 is restarted or the screen layout saved by the user's request is loaded, the user screen is configured. In addition, the user can quickly execute commands by registering the frequently used execution menu in the toolbar menu.

In the information processing/output module 646 provided in the HMI main module 640, the data stored in the storage device 400 is searched for and displayed on the screen by searching for a specific line (D/L) in the system diagram, or D /L can automatically generate single-line diagrams.

For example, real-time values and historical values for points of equipment designated by the user are inquired from the storage device 400 and the real-time operation information DB 500 and displayed on the trend change screen. In addition, it automatically saves the system diagram screen in case of a failure in the distribution line, and provides a function so that the user can search the storage list and reproduce the system status in the case of a failure on the screen.

The account/system management module 648 provided in the HMI main module 640 registers and manages user accounts of the HMI 600 and grants data access rights such as facility control, system editing, and setting work to each user. there is. For example, AOR (Area of Responsibility) is implemented as a function of setting data access rights for each facility by business office and line (D/L).

The operation setting module 643 provided in the HMI main module 640 prevents erroneous operation due to erroneous information obtained from field equipment or more by setting tags or memos for the information acquired in the field through the terminal device in advance. In case of need, it is possible to arbitrarily set the equipment status value with the manual override function. In addition, by allowing the user to directly set temporary elements such as jumpers and cuts used during field work in the system, the condition of the site can be reflected in the distribution diagram.

In the alarm/event processing module 649 provided in the HMI main module 640, alarms can be registered for important matters (value change) among real-time measured values and event values acquired in the field, and alarm text for each facility and point You can set the color, background color, alarm sound, and alarm sound duration. The user can recognize the generated alarm by operating the mouse/keyboard, and upon recognizing the alarm, the alarm sound and screen display (blinking, highlight, etc.) can be canceled.

The control processing module 647 provided in the HMI main module 640 provides a function for the user to remotely control the field facility, and a control validation and control interlock function for determining whether a user control command can be executed. can accommodate Control validity verification prevents duplicate control of one facility from being executed by multiple HMIs 600, and gives control priority to the user who first executed the facility control command among users who have been granted control authority.

The module-to-module interface 680 may perform a data exchange operation through communication linkage with the storage device 400 connected to the HMI 600 , the real-time operation information DB 500 , and the message transmission device 200 . The facility attribute information and system drawings stored in the storage device 400 are acquired through the RDB linkage function, and the real-time operation information DB 500 and the linkage work are performed to display the real-time acquisition values of the facilities collected in the field on the screen. can In order to receive a message generated by the main device 300 or the like or to transmit a message generated by the HMI 600 to another unit function module, a linkage operation with the message transmission device 200 may be performed.

13 is a flowchart illustrating a system measurement value reception procedure up to the HMI.

In the flowchart shown, the status data of a specific point received through the front-end processor 110 are transmitted to the main device 300 through the message transmission device 200, and the main device 300 checks the validity of the received status data. It is stored in the storage device 400 and the real-time operation information DB (500). The HMI 600 acquires the latest measured values by accessing the real-time operation information DB 500 if necessary. In the case of an alarm/event, since it has the purpose of conveying an emergency situation of the distribution system, it may be transmitted to the HMI 600 in real time through the message transmission device 200 .

14 is a flowchart illustrating a control procedure from the HMI to the intelligent terminal device.

In the illustrated flowchart, the HMI 600 provides a function of transmitting a control command request for a specific point input by the user to the main device 300 through the message transmission device 200 . The main unit 300 checks the execution authority of the received control command request and transmits it to the front end processor 110 through the message transmission device 120 to control a specific point.

Next, a clustering server configuration and failover that operates as a single system for a plurality of distributed main devices will be described by way of example.

According to the spirit of the present invention, the main device can be operated in a clustering method that operates as if one system by operating multiple servers in Multi-Active mode. In this case, load balancing may be performed for load balancing, and data loss and non-disruptive failover may be performed for high availability (HA). Servers operated in multiple units require a centrally managed distributed coordinator for status monitoring and shared data processing. The role of this distributed coordinator is suggested to be performed through ZooKeeper.

15 is a block diagram showing the configuration of a main clustering server.

The clustering server shown performs a clustering method that operates as a single system by operating multiple main server servers in Multi-Active mode. installed and ready to operate.

Here, as load balancing for system load balancing, the main cluster cluster distributes and allocates messages to each main server service to perform distributed parallel processing.

Here, for zero data loss and non-disruptive failover, the ZooKeeper Client in each primary process can communicate with the ZooKeeper Server to maintain a session. When a session is stopped, ZooKeeper Server sends a session termination notification to other ZooKeeper Clients. Through this, the failure of the stopped process is detected, and the process is transferred to another active program as soon as a failure occurs due to multi-active operation, and data loss and non-interruptible failover are performed.

Here, the distributed coordinator processing that monitors the status of each server and manages shared data is Zookeeper, which provides data storage (persistent/temporary/sequence data) for data sharing and data change notification (Watch) through cluster membership management. can be done using

16 is a block diagram illustrating the configuration of program modules as a main device system module.

The main device program in the illustrated case is composed of four processes. The main unit cluster, main unit service, and main unit launcher are configured on the main server server, and the main unit manager is configured on the HMI. The main cluster cluster uses Zookeeper Server, a distributed coordinator, to perform load balancing for system load balancing, data loss, and non-stop failover. The main unit service performs main unit functions such as real-time data management, measurement/event management, and alarm management. The main unit launcher performs On/Off control and monitoring of the main unit process. The main device Manager monitors the main device process operated on the main device server, and shows the execution history and alarm/event history of each main device process in real time, and performs On/Off control of the main device process through the main device launcher.

It connects to the MMDB where real-time data is operated and performs data processing through the MMDB processing library built into the main device program. The connection between the main device and each component is performed through the data distribution middleware rather than a direct connection, and message delivery is performed through functions such as Publish and Get provided by the data distribution middleware. Data messages such as measurement/event messages, control/measurement command messages, and alarm/event messages transmitted and received between each component are configured in Json format to enable scalable message processing as dynamic messages rather than fixed messages.

Next, processing processes according to each case are specifically exemplified using the above-described primary device clustering structure.

Fig. 17 is a block diagram showing the main device load balancing - message distribution process.

As shown in the figure, for load balancing, the main device program performs data connection with each component through data distribution middleware, so a method of performing load balancing by distributing and delivering the amount of messages to be processed to each server is used. For the sequential processing of messages generated in the terminal device, messages from the same terminal device are performed in the same server. The main device cluster performing load balancing distributes the total amount of terminal device IDs, pre-allocates them to each main device service performing the main device function, and delivers a message to the corresponding main device service when it is received. Also, the main device service processes the message received by itself.

Fig. 18 is a block diagram illustrating the main device load balancing - periodic distribution allocation process.

As shown, each primary device service periodically acquires its own server load and registers it with Zookeeper, and the primary device cluster acquires the load of each server through Zookeeper and allocates it in advance through distribution operation. The distribution operation is performed by redistributing the assigned terminal device ID of the server that exceeds the load reference value (default: 80%) to the server below the reference value (if the load is 90%, 10% of the terminal device ID is redistributed) Assignment). Distribution allocation information is registered with ZooKeeper server for high availability. In order to prevent message processing by the same terminal device in two or more servers, the terminal device ID for which message processing has not been completed is not included in the distribution assignment.

19 is a block diagram illustrating a primary device failover - a primary device cluster failover process.

Failover is required to ensure high availability of the primary device. Failures of the primary system program can be divided into the primary system cluster performing load balancing and the failure of the primary system service performing the primary system function. It receives a session termination notification through the ZooKeeper server, detects a failure, and performs a failover accordingly.

As shown, the other main cluster (Slave), which has been notified when the main cluster (Master) fails, confirms the previously elected Master candidates and confirms the new Master, acquires the distribution and allocation information of the existing Master from Zookeeper, It takes over message distribution and performs data loss and non-disruptive failover.

Fig. 20 is a block diagram illustrating a process of failover of a primary device - a failover of a primary device service.

As shown, the main device cluster (Master), which has been notified when the main device service fails, reassigns the assigned terminal device ID of the stopped main device service to another main device service, and acquires all messages from the message queue of the stopped main device service. , it distributes and delivers to other main device services to perform data loss and non-interruptible failover.

Next, the Dimensioning rule for increasing/decreasing the main device is exemplified.

21 is a block diagram showing the main device expansion - the main device cluster expansion process.

22 is a block diagram illustrating the process of main device extension - main device service extension.

23 is a block diagram illustrating a process of installing a primary device - installing a cluster of a primary device.

24 is a block diagram illustrating the process of installing a main device - a main device service.

When the main server server capacity is exceeded, it is possible to increase the data throughput by adding a H/W node equipped with the same main system program and MMDB. The main program is automatically operated by detecting the new main program according to the additional session registration of the ZooKeeper server, so there is no need to configure the existing program and restart it. In addition, since the closing is also detected as the end of the session and automatically operated, there is no need to set the config of the existing program and restart it.

On the other hand, since the ZooKeeper server performs the functions of sharing data between the main server servers and monitoring and notifying the main device process session, there is no need to add an additional server. If it is expanded, it is necessary to register a new Zookeeper server IP in the existing Zookeeper server config and restart it. In the case of the reduction of ZooKeeper servers, it is necessary to maintain the operation of more than half, which is the constraint of ZooKeeper server operation. ZooKeeper server stops the service if the number of running servers does not become a majority for integrity processing of data inconsistencies. At least 3 units are required to operate, and when 3 units are operated, 1 unit is stopped, when 4 units are operating, 1 unit is stopped, when 5 units are operated, 2 units are stopped, and when 6 units are operated, only 2 units are allowed.

25 is a block diagram illustrating a control command data processing flow.

After receiving the control command from the HMI, the main cluster cluster verifies the terminal device ID, checks the pre-assigned main device service number, and delivers a message to the corresponding main device service. The received main device service transmits the control command to the FEP after validating the control command and generating information.

26 is a control result data processing flow chart - a block diagram illustrating a control result receiving process.

27 is a control result data processing flow chart - a block diagram illustrating an event reception process according to control.

The front end processor (FEP) transmits the control result to the main device program after executing the control command. In the case of BO control, the control result and event data according to the control are transmitted. The main unit cluster receives the control result and event data from the front end processor (FEP), checks the terminal device ID, checks the pre-assigned main unit service number, and delivers a message to the main unit service. The received main device service performs control result validation, generates an alarm for event data, and delivers the control result to the HMI.

28 is a block diagram illustrating a measurement/event data processing process.

The front end processor (FEP) transmits the measurement/event data to the main device program. The main device cluster receives the measurement/event data from the front end processor (FEP), checks the terminal device ID, checks the pre-assigned main device service number, and delivers a message to the corresponding main device service. When data change is confirmed through comparison operation, the received main device service generates an alarm and delivers it to HMI and all programs that require an alarm.

Those skilled in the art to which the present invention pertains should understand that the present invention may be embodied in other specific forms without changing the technical spirit or essential characteristics thereof, so the embodiments described above are illustrative in all respects and not restrictive. only do The scope of the present invention is indicated by the following claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be construed as being included in the scope of the present invention. .

10, 11, 12 ~ 1n, 1m: intelligent terminal device
110: shear processor 200: message transmission device
220: node connection management module 230: transmission channel management module
280: message queue 240: message queue management module
250: transmission message transmission module 260: message replication module
300, 301, 302 ~ 30n: main value
320: device cluster 340: system information manager
360: main device manager 400: storage device
500: Real-time operation information DB 550: Distributed data synchronization unit
520: distributed data mutual management unit 560: distributed data processing unit
600: HMI 620: display module
640: HMI main module 680: Interface between modules

Claims (23)

a front end processor that communicates with intelligent terminal devices installed at multiple points in the distribution system to receive measurement values and transmit power flow control instructions at the corresponding points;
a message transmission device serving as a message bus relaying data and service request/response in a loosely-coupled manner;
a main device configured to perform validation of measurement values and control requests acquired by the front-end processor, manage shared information for each site and store and manage measurement values/control history, and configure a plurality of distributed server systems;
a real-time operation information DB for storing management and measurement values/control history in a synchronized shared memory space of the distributed server system and storing data for management; and
HMI providing user interface for operation of distribution system
High-availability distribution intelligent system using a message transfer bus comprising a.
According to claim 1,
A storage device that classifies and stores the acquired measurement values, control history and system information according to business offices, distribution lines, and facilities.
Distribution intelligent system further comprising a.
According to claim 1,
The claim is
An intelligent distribution system that forms a clustering system for other main devices and a clustering system for the main devices - the function of mutual monitoring and recovery between the main devices and the role of the integrated server.
According to claim 1,
The shear processor,
Communication is connected with intelligent terminal devices to collect power data for each major point in real time,
The intelligent terminal device disposed at each point acquires information on voltage or power management of the installation point in real time and transmits it to the shear processor periodically or eventively.
According to claim 1,
Transmitting the routing keyword to the message transmission device in order to transmit the measurement value obtained from the intelligent terminal device in the front-end processor and the corresponding measurement value to the unit function module that wants to receive it,
The message transmission device searches for a message channel corresponding to a routing keyword, and transmits a measurement value to message queues constituting the channel.
According to claim 1,
The message transmission device,
a message queue block having message queues communicatively connected to a corresponding unit function module in a Subscribe/Publish method;
a node connection management module for managing communication linkage between the unit function modules on a network;
a transport channel management module for managing creation/deletion of a logical transport channel for message transmission and a connection setting between the channel and the message queue;
a transport rule management module that connects a message to a corresponding message queue according to the message transport rule;
a message queue management module for creating and deleting the message queue and managing messages in the message queue;
a message transmission module for inputting and outputting messages to and from the storage according to the request of the client; and
A message replication module that replicates and manages messages in the storage.
A distribution intelligent system that includes.
According to claim 1,
The claim is
Main device cluster that performs load balancing processing and data loss/non-disruptive failover for system data processing load balancing;
a system information manager that performs system acquisition data processing functions such as real-time data management, measurement/event management, alarm management, and history management; and
Main device manager that performs start/stop control and monitoring of other primary devices constituting the primary device cluster
A distribution intelligent system comprising a.
According to claim 1,
The real-time operation information DB,
A distribution intelligence system that is distributed and managed across multiple servers, supports high-speed data synchronization when changing/adding real-time system operation information, and provides an accessible SQL-like API.
According to claim 1,
The real-time operation information DB,
Distributed data synchronization unit for performing data synchronization;
Distributed data mutual management unit for real-time data management of system operation; and
Distributed data processing unit that performs distributed processing of real-time data
A distribution intelligent system comprising a.
According to claim 1,
The HMI is
Distribution intelligence that outputs the determination result of failure at a specific point calculated in the main device and status data for a specific point acquired from the real-time operation information DB - including at least one of voltage, load amount, load pattern, generation amount and electricity quality system.
According to claim 1,
The HMI is
a display module as a visual interface for a user;
HMI main module that performs data processing for user provision; and
Inter-module interface for performing data exchange work through communication linkage with the real-time operation information DB and the message transmission device
A distribution intelligent system comprising a.
Main device cluster that performs load balancing processing and data loss/non-disruptive failover for system data processing load balancing;
a system information manager that performs system acquisition data processing functions such as real-time data management, measurement/event management, alarm management, and history management; and
The main unit manager that monitors and controls the operating main unit process
An intelligent cluster system consisting of a plurality of main devices including
13. The method of claim 12,
The system information manager,
a real-time data management unit that manages real-time data shared by unit function modules;
a measurement/event management unit that acquires measurement/event data from a cooperative system, updates real-time data values, and updates quality values;
an alarm management unit that receives measurement/event data from the linked system, generates and transmits alarms and events;
an editing management unit for updating and disseminating facility information according to system editing;
a control management unit receiving a control command from the HMI and performing control processing; and
History management unit that saves the history in real time and periodically in the database
An intelligent cluster system that includes
13. The method of claim 12,
The main device cluster is
a failure monitoring/action unit for monitoring failures occurring in the main devices and correcting the detected failures; and
Master management unit that selects and changes the primary device performing the master role among the primary devices
An intelligent cluster system that includes
13. The method of claim 12,
The main device manager is
a main device process status monitoring unit that monitors the main device process and displays an execution history and an alarm/event history of the main device process; and
Main device process start control unit that performs On/Off control for the main device process
An intelligent cluster system that includes
13. The method of claim 12,
Real-time operation information DB for operating real-time data for system operation
The main cluster system further comprising a.
17. The method of claim 16,
The claim is
Configure the data model of distribution operation facilities to initialize the real-time data configuration and value;
When the data value is acquired through measurement/event reception of the field terminal device, the real-time data value is updated,
When a configuration change occurs due to system editing, the main cluster system receives the corresponding message and updates the configuration of real-time data in real time.
17. The method of claim 16,
The claim is
A data model that can share real-time status information of facilities in the power distribution system is constructed and created in the real-time operation information DB, and data acquired from a shear processor in charge of communication with an intelligent terminal device in the field is stored in the real-time operation information DB Managed primary cluster system.
17. The method of claim 16,
The real-time operation information DB,
Distributed data synchronization unit for performing data synchronization;
Distributed data mutual management unit for real-time data management of system operation; and
Distributed data processing unit that performs distributed processing of real-time data
A distribution intelligent system comprising a.
20. The method of claim 19,
The distributed data mutual management unit,
Data Export module that can save real-time data stored on the table as a file;
a data import module for loading data stored as a file into the table;
Data Replication module that can restore data using Redo Log to cope with failure; and
Data Dump module that can store the instance data of the real-time operation information DB
A distribution intelligent system that includes.
20. The method of claim 19,
The distributed data processing unit,
a transaction processing module for processing transaction data generated for real-time data processing;
a data dictionary module for managing the operation management and data generation information of the real-time operation information DB;
a table processing module for managing tables for real-time data storage; and
A shared memory management module that reads/writes real-time data to shared memory and manages storage area
A distribution intelligent system that includes.
22. The method of claim 21,
The distributed data processing unit,
Redo Log module for real-time data recovery; and
Index management module that performs index management based on B-Tree algorithm for quick access to real-time system operation information
Distribution intelligent system further comprising a.
20. The method of claim 19,
The distributed data synchronization unit,
a data synchronization module for synchronizing data corresponding to each other stored in storages of a plurality of distributed servers; and
A remote process module supporting a remote operation means for the storages of the plurality of distributed servers
A distribution intelligent system that includes.

Images