KR101894660B1 - Controller in software defined networking environment and operating method thereof - Google Patents

Abstract

The present invention relates to a controller in a software defined networking environment and an operating method thereof which can block a data loss in an event by compensating an event processing mechanism used for communication between components in a software defined networking environment, can reduce function dependency between the components, and can provide a rapid reaction due to rapid network traffic. To this end, the controller comprises an event processing module, an event broker module, and a control module.

Description

CONTROLLER IN SOFTWARE DEFINED NETWORKING ENVIRONMENT AND OPERATING METHOD THEREOF FIELD OF THE INVENTION [0001]

The present invention relates to a controller and an operation method thereof, and more particularly, to a controller in a software defined networking environment and a method of operating the same.

Software Defined Networking (hereinafter referred to as SDN) refers to a technology in which an intelligent central management system manages all the network equipment in a network. In the SDN technology, it is possible to develop and assign various functions rather than the existing network structure by processing the control operation related to the packet processing performed by the existing hardware type network device in place of the controller provided in the form of software.

The SDN system generally comprises a controller for controlling the entire network, a plurality of open flow switches controlled by the controller server and processing packets, and a host corresponding to a lower layer of the open flow switch. In this case, the open flow switch is only responsible for packet transmission and reception, and routing, management, and control of the packet are all performed in the controller. In other words, it is the basic structure of the SDN system to separate the data planes and the control planes constituting the network equipment.

In the SDN environment, the controller controls and manages the network environment and is provided as an open source controller such as ONOS, POX, and OpenDayLight. However, commercial controllers have a limitation in the problem of the inter-component communication method, the problem of the component chaining method, and the lack of efficient use of the event-based mechanism.

Specifically, existing commercial controllers use an event-based mechanism for inter-component communication. The component registers a callback function in the event handler, and the event handler calls the component's callback function when a specific event occurs. However, in an event-based mechanism, if a caller terminates a process after delivering an event, there is a risk that data will be lost without the receiver handling the data for that event.

In addition, existing commercial controllers use the Open Service Gateway Initiative (OSGi) to provide dynamic, modular component design. In addition, the communication between components uses an application programming interface (API) as well as the event-based mechanism described above. This causes a dependency problem that requires the component to call another component to perform the next operation and receive the operation result of the component.

The controller does not determine the events that originate from the data plane by itself, but rather by the application that sends the event to the control plane and requests a specific event. Therefore, existing commercial controllers have limitations in that they can not cope with high-speed incoming events or unexpected saturation.

In addition, existing commercial controllers do not provide services for defining the chaining method between components, and even if provided, they are directly defined in the code or use the component priority by the manager (or user). However, security-related components such as checking the integrity of an event have a limitation because they require a higher level of control when determining the event processing order.

In addition, existing network operating systems are used to add more functions to an event-based mechanism rather than to an efficient one. This method is not easy to expand, and there is a limitation that the event processing service of the controller can not provide safety.

Korean Registered Patent No. 101491698 (registered on Feb. 20, 2013), "Control device in software defined network and its operation method" Korean Patent Publication No. 1020160012660 (published on Mar. 23, 2013), "Apparatus and method for controlling a network in an SDN environment"

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems and it is an object of the present invention to supplement an event processing mechanism used for communication between components in a software defined networking environment to prevent data loss in an event, And a method of operating the same.

It is another object of the present invention to provide a controller and an operation method thereof that can effectively determine a processing order and a method between a plurality of components that process the same event by applying dynamic component event chaining.

It is another object of the present invention to provide a controller and an operation method thereof that can effectively use an event processing mechanism by applying an event distribution method based on an administrator policy.

In a software defined network environment according to an embodiment of the present invention, a controller including a plurality of components stores data included in notification events generated from network equipment in a shared storage, and stores the notification event and the stored data An event broker module for transmitting the stored data to the component based on the notification event, and a control module for controlling traffic information, event statistics, and an event processing mechanism according to the function of each component .

In a software defined network environment according to an embodiment of the present invention, a controller including a plurality of components generates the notification event including a message received from the network device, and transmits the generated notification event to the event processing module And an information collecting module for collecting the traffic information from each of a plurality of nodes connected to the network equipment.

Wherein the control module is configured to dynamically activate or deactivate a component based on the event statistics in the event processing module, or to filter specific events to be transmitted to a specific component, the event processing mechanism of the meta events .

The event statistics may include event volume, component level statistics on event consumption and production, and event type distribution statistics.

The control module may control the event processing mechanism of event chaining of sequential delivery or parallel delivery of the stored data to be performed based on the traffic information.

The event chaining may determine a processing order and a method among the plurality of components for processing an event.

In addition, a controller including a plurality of components in a software defined network environment according to an exemplary embodiment of the present invention includes an input module for receiving requirements for network management from a user, and an input module for analyzing the requirements, resource usage, And a policy table including optimized module combination information according to the optimized module combination information.

The control module may control the event processing mechanism of the event distribution method to be performed based on the policy table.

The control module may determine whether the generated notification event is consistent based on the policy table, and may control delivery of data included in the notification event based on the determination result.

The control module may update the policy table based on a user definition of operatordefined policies (ODPs) received by the input module.

A method of operating a controller including a plurality of components in a software defined network environment according to an exemplary embodiment of the present invention includes storing data included in notification events generated from network equipment in a shared storage, Transmitting the stored data to the component through an event broker module, and receiving the data to which the event processing mechanism based on the traffic information, the event statistics, and the function of each component is applied.

Wherein the step of storing the data in the shared storage comprises generating the notification event including a message received from the network equipment, receiving the generated notification event and transmitting the received notification event to the event processing module, And storing the data included in the notification event in the shared storage.

The event processing mechanism may include meta events for dynamically activating or deactivating a component based on the event statistics in the event processing module, or configuring the specific event to be filtered to a specific component.

In addition, the method of operating a controller including a plurality of components in a software defined network environment according to an embodiment of the present invention may further include collecting the traffic information from each of a plurality of nodes connected to the network equipment.

The event handling mechanism may include event chaining of sequential delivery or parallel delivery of the stored data based on the traffic information.

In addition, in a software defined network environment according to an embodiment of the present invention, a method of operating a controller including a plurality of components includes receiving a requirement for network management from a user, And storing and maintaining optimized module combination information according to the analysis.

The event handling mechanism may include an event distribution method according to the module combination information.

According to an embodiment of the present invention, an event processing mechanism used for inter-component communication in a software-defined networking environment is supplemented to prevent data loss in an event, reduce functional dependency between components, It is possible to provide a solution.

Also, according to the embodiment of the present invention, it is possible to effectively determine a processing order and a method between a plurality of components that process the same event by applying dynamic component event chaining.

Also, according to the embodiment of the present invention, an event processing mechanism can be effectively used by applying an event distribution method based on administrator policy.

FIG. 1 is a diagram for explaining a configuration of a general software definition network.
2 is a block diagram of a controller according to an embodiment of the present invention.
FIG. 3 illustrates an event processing mechanism according to an embodiment of the present invention.
FIG. 4 is a view for explaining an event processing mechanism according to another embodiment of the present invention.
FIG. 5 is a view for explaining an event processing mechanism according to another embodiment of the present invention.
6 is a flowchart of an operation method of a controller according to an embodiment of the present invention.
7 is a flowchart illustrating a method of operating a controller according to another embodiment of the present invention.

Hereinafter, embodiments according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to or limited by the embodiments. In addition, the same reference numerals shown in the drawings denote the same members.

Also, terminologies used herein are terms used to properly represent preferred embodiments of the present invention, which may vary depending on the viewer, the intention of the operator, or the custom in the field to which the present invention belongs. Therefore, the definitions of these terms should be based on the contents throughout this specification.

FIG. 1 is a diagram for explaining a configuration of a general software definition network.

Referring to FIG. 1, a software defined network in the present invention may include an SDN controller 100, a network device 200, and a host 300. The network device 200 and the host 300 may be referred to as a node, and a link may denote a connection between two nodes. The controller 100 manages the network equipment 200 and centrally manages and controls the plurality of network equipment 200.

Specifically, the SDN controller 100 according to the present invention includes software that performs functions such as topology management, path management related to packet processing, link discovery, and flow management. And can be implemented in a modularly mounted form.

The network equipment 200 functions to process packets under the control of the SDN controller 100. Examples of the network equipment 200 include a mobile communication base station, a base station controller, a gateway equipment, a wired network switch, and a router.

The most common network equipment 200 used in a software defined network is the open flow switch 200. The open flow switch 200 can be understood as a concept including a switch supporting only an open flow protocol, a virtual switch supporting an open flow protocol, and a general L2 switch supporting an open flow protocol, ) Can be controlled by a switch that supports the Netconf protocol as well as a switch that supports the open flow protocol. Thus, the present invention is not limited by the type of protocol used for exchanging information between the controller 100 and the switch 200 in a software defined networking environment. However, the most widely used protocol for this is the OpenFlow protocol, so the case where the network device 200 is the open flow switch 200 will be mainly described.

More specifically, the open flow switch 200 exchanges information with the controller 100 through a secure channel. The secure channel is a communication channel between the switch 200 and the controller 100 located at a remote location, and information exchanged between the controller 100 and the switch 200 can be encrypted.

The open flow switch 200 has one or more flow tables for defining and processing packets and including statistical information related to the packets. The flow table is composed of a flow rule that defines packet processing. The flow rule is added by a flow mode message (FlowMod Message) generated by the controller 100 and transmitted to the open flow switch 200, Modified or deleted.

The open flow switch 200 processes the packet with reference to the flow table. The flow table may include a match field for a packet defining a flow, operation information for defining processing of the packet, and statistical information for each flow (Stats). Each row constituting the flow table is called a flow entry, and a priority can be assigned to each flow entry. The switch can process the packet according to the operation information of the flow entry having the highest priority among the flow entries having match information matching the information of the packet.

The host 300 means a terminal or the like corresponding to a lower layer of the switch 200, and may be used to mean a client and a server. The host 300 may generate a packet for transmission to another host via a software defined network, and may transmit the packet to the switch 200 through a port of the network interface.

For example, when the first host 300a wants to send a packet to the second host 300b, the first host 300a generates a packet to be sent and transmits the packet to the first host 300a via an open flow switch (200a). When there is a flow entry matched with the packet in the open flow switch 200a receiving the packet, the packet is processed as specified in the flow entry. However, when there is no flow entry matched with the packet in the open flow switch 200a, the open flow switch 200a transmits a packet (Packetin Message), which is a packet informing the controller 100 of the packet flow. The controller 100 generates a flow rule change specifying the processing of the packet and transmits it to the open flow switch 200a, and the open flow switch 200a changes the state and processes the packet based thereon.

In order for the controller 100 to receive a message that is a packet and to generate a flow rule change specifying the processing of the packet, the software installed in the control 100 is used to perform functions such as topology management and path management related to packet processing To create a flow rule change. The controller 100 of the present invention modularizes each function performed in the controller 100 to change a flow rule and blocks loss of data included in an event generated from the network equipment 200, Each function to be performed is modularized to reduce the dependency between the components and to provide quick response according to the sudden network traffic so that the network can be effectively managed according to various network environments.

2 is a block diagram of a controller according to an embodiment of the present invention.

2, the controller 100 includes an event processing module 110, an event broker module 120, and a control module 130. The controller 100 includes an input / output module 140, (150), an input module (160), and a resource monitoring module (170).

The event processing module 110 stores data included in notification events generated from the network device 200 in the shared storage 111 and delivers notification events and stored data.

The controller 100 according to the embodiment of the present invention may further include an input and output module 140 and an information collection module 150. The input and output module 140 receives a message from the network equipment 200, Module 150 may receive traffic information.

For example, the input / output module 140 may generate a notification event including a message received from the network device 200, and may transmit the generated notification event to the event processing module 110. Here, the message received from the network device 200 may be a control message for routing, managing, and controlling the packet. For example, the message may be a packet in the embodiment described in FIG.

According to an embodiment, the input / output module 140 may generate an event including a message received from the network equipment 200. [ The event may include an event type field including information on a data field including a message and information on a data field, the information being exchanged between the components in the controller 100 operating on an event basis.

As another example, the information collecting module 150 may collect traffic information from each of a plurality of nodes connected to the network equipment 200. [

The event processing module 110 stores the data included in the notification event received through the input / output module 140 in the shared storage 111 and then transmits the data included in the event to each component 10 in the chain .

According to an embodiment, the event processing module 110 may directly transmit event-containing data to the plurality of components 10 and may transmit the event-containing data to the event broker module 120.

The event broker module 120 sends the stored data to the component 10 based on the notification event.

The event broker module 120 receives an event generated by each component 10 in the controller 100 that operates based on an event, and transmits the event to the entire module. Accordingly, the component 10 included in the controller 100 can exchange messages through the event broker module 120 without exchanging messages directly between the components.

For example, the event broker module 120 may serve as a bridge for inter-component communication to minimize the dependency between the plurality of components 10. [ Depending on the embodiment, the event broker module 120 may be responsible for limiting direct communication between components 10 and eliminating implementation dependencies defined for component 10 using a request and response system.

The control module 130 controls traffic information, event statistics, and event handling mechanisms according to the function of each component (or module).

The control module 130 may be configured to dynamically activate or deactivate a component based on event statistics in the event processing module 110 or to filter a specific event to be delivered to a specific component, Can be controlled to be performed.

The event statistics may include event volume, component level statistics on event consumption and production, and event type distribution statistics.

For example, the control module 130 may control to automatically trigger the predetermined handling logic in the event processing module 110 based on the meta-event.

The meta-event allows a user to perform a predetermined function when a specific situation is reached. The meta-event provides the user with the activation of a conditional component in advance. If the event generation pattern does not meet the condition, can do. In addition, the meta-event may be adjusted to filter certain events for a particular component that may cause the event handling module 110 to generate unwanted resources.

The control module 130 may control the sequential delivery of the stored data based on the traffic information or the event handling mechanism of event chaining of the parallel delivery to be performed.

For example, when the event processing module 110 serves a common event as a group of a plurality of components 10, the control module 130 generates an event chaining event (event chaining event) The processing mechanism can be controlled to be performed.

Here, sequential delivery can occur when a component is granted the right to potentially terminate an event chain based on internally defined decisions about an event, such as a filter criteria match. In addition, parallel propagation may be applicable when the response of a component to an event does not affect other components.

The controller 100 according to the embodiment of the present invention may further include an input module 160 and a policy table (not shown).

The input module 160 may receive a request for a network management from a user or input a control device mode. In addition, the input module 160 may receive information on the activation of the component, and may be used to generate a pre-operation environment file of the controller 100.

The policy table may include requirements, resource usage, and optimized module combination information according to functional analysis of each component. In particular, the policy table may include a policy-based event distribution scheme for efficiently using an event-based mechanism, and may be reflected in the component 10 in some embodiments.

For example, for policy-based event distribution, a network operating system administrator (or user) can define administrator policies (administrator-defined policies, ODPs) based on software-defined networking and key fields in the network.

When an administrator defines an administrator policy for a specific component, the policy is immediately reflected in the component's policy table. When a generated event is matched with a policy in the policy table, the event enters the work pool. If the event does not match, the event is not accepted.

For example, the administrator policy may be configured with seven fields including a data path ID, an inport, a protocol, a source / destination IP address, and a port.

Depending on the embodiment, the control module 130 may update the policy table based on the administrator policy received by the input module 160. [ Thereafter, the control module 130 determines whether the notification event is generated based on the policy table through the event processing module 110, and controls the delivery of data included in the notification event based on the determination result.

The control module 130 may be included in the event processing module 110, the event broker module 120 and the plurality of components 10 in the controller 100 according to the embodiment of the present invention.

Referring to FIG. 2, the component 10 can process an event by performing a unique function of the component, and can generate another event according to the processing result. The event processing module 110, the event broker module (120) and the control module (130). Other modules (the first component, the second component, and the Nth component) included in the controller 100 according to the embodiment of the present invention may also include an event processing module 110, an event broker module 120, a control module 130, Output module 140, an information collecting module 150, an input module 160, and a resource monitoring module 170. The input /

The resource monitoring module 170 may monitor the resource usage of each of the plurality of components and may request the control module 130 to control the operation of the corresponding component if the resource usage of any component is higher than a preset reference. The resource monitoring module 170 also corresponds to one of a plurality of components constituting the controller 100, but differs in that the resource monitoring module 170 can perform its own functions in comparison with other components.

FIG. 3 illustrates an event processing mechanism according to an embodiment of the present invention.

More specifically, FIG. 3A shows an example of event processing of an event processing module and intercomponent events through direct interaction in a controller according to an embodiment of the present invention, and FIG. 3B shows an example of event processing (Notification events) processed through an event queue, and FIG. 3C shows an example of meta events transmitted to the basic framework.

Referring to FIG. 3, when a notification event occurs according to a trigger event, the event processing module stores the original data in the event and performs data management on behalf of the triggered component. In addition, data in the event can be delivered to each component in the chain.

In addition, the controller according to an exemplary embodiment of the present invention can substitute functional dependencies between components using an event broker in communication between components generated through exchange of request and response events. For example, the component may trigger only a request event to an event handling module.

The meta-event may cause the base framework to activate or deactivate a component. According to an embodiment, the meta-event may request user intervention if an abnormal event generation pattern occurs.

FIG. 4 is a view for explaining an event processing mechanism according to another embodiment of the present invention.

More specifically, FIG. 4 illustrates an example of delivering an event to a component based on sequential delivery or parallel delivery within a controller according to another embodiment of the present invention.

For example, the controller according to another exemplary embodiment of the present invention may perform the event forwarding of the component based on the role of the component, deliver the event to the component having the higher authority, and then transmit the event in parallel or sequentially Can be evaluated to check context dependency. Accordingly, the controller can process the adjusted event chain by imposing sequencing on the dependent component to perform event processing of the independent component.

Here, sequential delivery can occur when a component is granted the right to potentially terminate an event chain based on internally defined decisions about an event, such as a filter criteria match. In addition, parallel propagation may be applicable when the response of a component to an event does not affect other components.

FIG. 5 is a view for explaining an event processing mechanism according to another embodiment of the present invention.

More specifically, FIG. 5 illustrates an example of distributing an event based on a policy in a controller according to another embodiment of the present invention.

5, when an operator (administrator or user) defines ODPs (operator-defined policies), the controller according to another embodiment of the present invention includes a policy table in a component, Can be updated.

Thereafter, the event processing module judges whether the generated event matches a policy in the policy table, and when the event matches, enters the event into a worker pool. If the event does not match, the event processing module does not accept the event.

Here, the ODPs include data path IDs, inports, ports, protocol (Proto), source / destination IP addresses (Src IP or Dst IP), and ports (Sport or Dport) ≪ / RTI >

6 is a flowchart of an operation method of a controller according to an embodiment of the present invention.

The method shown in FIG. 6 may be performed by a controller including a plurality of components in a software defined network environment according to the embodiment of the present invention shown in FIG.

Referring to FIG. 6, in step 610, data included in a notification event generated from a network device is stored in a shared storage.

For example, in operation 610, a notification event including a message received from a network device is generated (not shown), a generated notification event is received and transmitted to an event processing module (not shown) (Not shown) of storing the data included in the notification event received in the shared storage.

According to an embodiment, the event processing module may directly transmit event-containing data to a plurality of components or may be delivered through an event broker module.

In step 620, the data stored through the event broker module is transmitted to the component based on the notification event.

The event broker module receives an event generated by each component in the controller according to an embodiment of the present invention that operates based on an event, and transmits the event to the entire module. Therefore, the components included in the controller can exchange messages through the event broker module without exchanging messages directly between the components.

In operation 630, data including traffic information, event statistics, and event processing mechanisms according to the functions of the respective components are received.

For example, the component may receive data to which an event handling mechanism based on a notification event is applied.

A method of operating a controller according to an embodiment of the present invention includes collecting traffic information from each of a plurality of nodes connected to a network device (not shown), inputting requirements (not shown) (Not shown) for storing and maintaining optimized module combination information according to the function, resource usage, and functional analysis of each component.

The event processing mechanism may include meta events for dynamically activating or deactivating a component based on event statistics in an event processing module, or configuring a specific event to be transmitted to a specific component to be filtered.

In addition, the event processing mechanism may include sequential delivery of stored data or event chaining of parallel delivery based on traffic information, and may include an event distribution method based on module combination information.

7 is a flowchart illustrating a method of operating a controller according to another embodiment of the present invention.

Referring to FIG. 7, the controller 100 receives a message 710 from the network device 200 and generates an event 720 including a message received from the network device. An event generating step 720 includes generating a data field including a message received from the network equipment, generating an event type field including information on the data field, and generating an event including a data field and an event type field Lt; / RTI >

The input / output module 410 that generated the event transmits the event to the event processing module 110 (730), and the event processing module 110 stores the data in the event in the shared storage (740).

Then, the event processing module 110 transmits the data in the event to the event broker module 120 (750). The event broker module 120 determines 760 the transmission according to the event processing mechanism and delivers 770 the data to the specific component 10.

For example, the event processing module 110 may perform transmission according to an event processing mechanism of a meta event that is configured to dynamically activate or deactivate a component based on event statistics, or to filter specific events to be transmitted to a specific component 10 Can be performed.

In another example, the event processing module 110 may perform transmission according to the event processing mechanism of event chaining of sequential delivery of data or parallel delivery of stored data based on traffic information.

As another example, the event processing module 110 may perform transmission according to the event processing mechanism of the event distribution method based on the policy table.

8 is a flowchart illustrating a method of operating a controller according to another embodiment of the present invention.

Referring to FIG. 8, the operation method of the controller according to another embodiment of the present invention is as follows. The controller receives the requirements for the network management from the user (810), and generates and stores 820 the optimized module combination information according to the requirements, the resource usage, and the function analysis of each component in the policy table. In addition, new information according to the user's input may be updated 830 in the policy table, and one or more components corresponding to the module combination information may be activated 840. In this case, it can only be done by the activated component.

In addition, if the controller receives the controller mode from the user (850), the controller may activate (860) one or more components (or modules) corresponding to the controller mode and the required module.

Depending on the embodiment, the control device modes may include a scalability enhancement mode, a performance enhancement mode, a confidentiality enhancement mode, a data integrity assurance mode, and a usability enhancement mode, Are the same as those of the controller 100, and therefore will not be described.

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. For example, the apparatus and components described in the embodiments may be implemented within a computer system, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA) A programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For ease of understanding, the processing apparatus may be described as being used singly, but those skilled in the art will recognize that the processing apparatus may have a plurality of processing elements and / As shown in FIG. For example, the processing unit may comprise a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

The software may include a computer program, code, instructions, or a combination of one or more of the foregoing, and may be configured to configure the processing device to operate as desired or to process it collectively or collectively Device can be commanded. The software and / or data may be in the form of any type of machine, component, physical device, virtual equipment, computer storage media, or device , Or may be permanently or temporarily embodied in a transmitted signal wave. The software may be distributed over a networked computer system and stored or executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.

The method according to an embodiment may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions to be recorded on the medium may be those specially designed and configured for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape, optical media such as CDROMs and DVDs, magnetic optical media such as floppy disks, magnetooptical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI > or equivalents, even if it is replaced or replaced.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

100: Controller (SDN controller)
200: Open flow switch, network equipment
300: Host

Claims (18)

A controller comprising a plurality of components in a software defined network environment,
An event processing module for storing data included in a notification event generated from a network device in a shared storage, and for transmitting the notification event and the stored data;
An event broker module that transmits the stored data to the component based on the notification event; And
A control module for controlling to provide traffic information, event statistics, and an event handling mechanism according to the function of each component
/ RTI > The method according to claim 1,
An input / output module for generating the notification event including a message received from the network device and transmitting the generated notification event to the event processing module; And
An information collecting module for collecting the traffic information from each of a plurality of nodes connected to the network equipment;
Lt; / RTI > The method according to claim 1,
The control module
A controller that controls the event processing mechanism of meta events to be performed to dynamically activate or deactivate a component based on the event statistics in the event processing module or to filter specific events transmitted to a specific component, . The method of claim 3,
The event statistics
Event volume, component level statistics on event consumption and production, and event type distribution statistics. The method according to claim 1,
The control module
And controls the event processing mechanism of event chaining of sequential delivery or parallel delivery of the stored data to be performed based on the traffic information. 6. The method of claim 5,
The event chaining
And determines a processing order and a method among the plurality of components that process the event. The method according to claim 1,
An input module for receiving requirements for network management from a user; And
A policy table including the requirements, resource usage, and optimized module combination information according to the function analysis of each component
Lt; / RTI > 8. The method of claim 7,
The control module
And controls the event processing mechanism of the event distribution method to be performed based on the policy table. 8. The method of claim 7,
The control module
Determines whether the generated notification event is matched based on the policy table, and controls delivery of data included in the notification event based on the determination result. 8. The method of claim 7,
The control module
And updates the policy table based on a user definition of operatordefined policies (ODPs) received by the input module. A method of operating a controller including a plurality of components in a software defined network environment,
Storing data included in notification events generated from network equipment in a shared storage;
Transmitting the stored data to the component via an event broker module based on the notification event; And
Receiving the data to which the event processing mechanism based on the traffic information, the event statistics, and the function of each component is applied
Lt; / RTI > 12. The method of claim 11,
The step of storing the data in a shared repository
Generating the notification event including a message received from the network equipment;
Receiving the generated notification event and transmitting the received notification event to the event processing module; And
Storing the data included in the notification event received by the event processing module in the shared storage
Lt; / RTI > 13. The method of claim 12,
The event handling mechanism
Wherein the event processing module includes meta events for dynamically activating or deactivating a component based on the event statistics in the event processing module or filtering a specific event to be transmitted to a specific component. 12. The method of claim 11,
Collecting the traffic information from each of a plurality of nodes connected to the network equipment
≪ / RTI > 15. The method of claim 14,
The event handling mechanism
And event chaining of the sequential delivery or parallel delivery of the stored data based on the traffic information. 12. The method of claim 11,
Receiving a request for a network management from a user; And
Storing and maintaining optimized module combination information according to the requirements, resource usage, and functional analysis of each component
≪ / RTI > 17. The method of claim 16,
The event handling mechanism
And an event distribution method based on the module combination information. 18. A computer program stored in a computer-readable medium for performing the method of any one of claims 11 to 17.

Images