KR102087670B1 - Method for providing end-to-end path on mixed networks comprising circuit and packet networks, and unified software defined network controller - Google Patents

Abstract

Disclosed is a method for providing an end-to-end (E2E) path for a composite network in which a circuit network and a packet network are mixed, and an integrated software-defined network controller for the same. The method of providing the end-to-end path using SDN technology in a composite network includes generating a path on a circuit network constituting the end-to-end path, generating a path on a packet network constituting the end-to-end path, and the shape of the circuit network and the packet network ( It may include the step of connecting the path on the circuit network and the path on the packet network using the topology) information. Therefore, by using the route providing method and the integrated SDN controller according to the present invention, it is possible to integrally provide end-to-end routes for heterogeneous networks in which a circuit network and a packet network are mixed.

Description

A method for providing end-to-end path on mixed networks comprising circuit and packet networks, and unified software defined network controller}

The present invention relates to a network technology, and more specifically, a circuit network (circuit network) and a packet network (packet network) on a composite network mixed with a method for providing an end-to-end (end-to-end) path to the user, and this It is for an integrated SDN controller (unified Software Defined Network controller).

The network maintained by the service provider to provide the IP-based communication service is largely composed of two different networks. The first is a packet network that is used to transmit data in the form of datagrams, and is built on the basis of IP-based routers. The second is a circuit network that establishes a circuit first and transfers data on it, which is constructed based on transmission devices.

Gradually, although the network is mainly implemented in a packet network, it is expected that a complex network in which the above-mentioned two networks coexist will be used for a considerable period of time. In this case, when the circuit network and the packet network coexist, the end-to-end path is created and maintained between the user, the user, and the server in the cloud data center (CDC). However, there is a problem in that a path must be created across two networks composed of different characteristics and different devices. In particular, there is a need for integrated control of heterogeneous networks in that the user requirements for the end-to-end paths to be generated must be met by using two networks having different characteristics together.

As a method, there may be a method of implementing network equipment in which packet technology and circuit technology are included in one device, and integrating the circuit network and the packet network using these network devices. However, in the case of this method, there is a problem that a large number of existing network equipments must be replaced, and the entire existing network configuration needs to be changed.

The object of the present invention for solving the above problems is, in a complex network environment in which a circuit network and a packet network are mixed, a central controller using SDN technology integrates and operates the entire packet network and the circuit network, thereby forming a packet network and a circuit network. It is to provide a suitable end-to-end path to users on a mixed heterogeneous network and to provide a management method.

Another object of the present invention for solving the above problems is, in a complex network environment in which a circuit network and a packet network are mixed, the entire packet network and the circuit network are integrated and operated to provide and manage an appropriate end-to-end path to the user. In providing an SDN controller.

The present invention for achieving the above object, as a method of operating an integrated software-defined network controller that provides an end-to-end path by managing the circuit network and the packet network collectively. , Generating a path on the circuit network constituting the end-to-end path, generating a path on the packet network constituting the end-to-end path, and using topology information of the circuit network and the packet network It provides a method of operating an integrated software-defined network controller, comprising the step of connecting the path on the circuit network and the path on the packet network.

From here. The shape information may include link state information between nodes defined in the circuit network and the packet network.

Here, the method may further include receiving a request to generate the end-to-end path. In this case, the request for generating the end-to-end path may be received from a user through a service controller that mediates the provision of application services.

Here, the method may further include connecting the end-to-end path with a path to a virtual machine in a cloud data center. In this case, the method may further include providing information regarding a characteristic of the virtual machine and a characteristic of a path to a virtual machine in the cloud data center to a cloud controller managing the cloud data center.

Here, the method further includes the step of transmitting, by the integrated software-defined network controller, information on a path on the generated circuit network to a circuit network network equipment using a predefined application programming interface (API). You can.

Here, the method may further include the step of transmitting, by the integrated software-defined network controller, information on a route on the generated packet network to packet network network equipment using a predefined application programming interface (API). have.

In this case, the predefined application programming interface (API) may be based on the OpenFlow or IETF I2RS (Interface to Routing System) protocol.

The present invention for achieving the other object is an integrated software-defined network controller that provides an end-to-end path by integrally managing a circuit network and a packet network. A packet topology management unit that maintains and manages connection configuration information of devices, a circuit topology management unit that maintains and manages connection configuration information of circuit network network devices, an adapter unit that performs command delivery to lower devices, and The packet topology management unit and the circuit topology management unit connection shape information is used to generate the end-to-end path that connects the circuit network and the packet network, and provides the end-to-end path to the circuit network and packet network network devices through the adapter unit. Integrated software-defined network control, including a control unit to set To provide dollars.

Here, the controller may further include a packet link discovery unit that collects information on links in the packet network section and provides it to the packet topology management unit.

Here, the controller may further include a circuit link discovery unit that collects information on links in the circuit network section and provides it to the circuit topology management unit.

Here, the control unit may receive a request for generating the end-to-end path from a user through a service controller that mediates the provision of an application service.

At this time, the controller may provide information on the generated end-to-end path to at least some of the nodes constituting the end-to-end path.

Here, the control unit may connect the end-to-end path with a path to a virtual machine in a cloud data center. At this time, the control unit may provide the end-to-end path information to the cloud controller managing the cloud data center, the characteristics of the virtual machine and the path characteristics of the virtual machine in the cloud data center.

Here, the controller may further include a packet network application programming interface (API) unit for communicating with packet network network devices, and the adapter unit may be configured to communicate with the packet network network devices through the packet network API unit.

Here, the controller further includes a circuit network application programming interface (API) unit for communicating with circuit network network devices, and the adapter unit can be configured to communicate with the circuit network network devices through the circuit network API unit. have.

In this case, the application programming interface (API) of the packet network application programming interface (API) may be based on the OpenFlow or IETF I2RS protocol.

Through the present invention, it is possible to provide an integrated end-to-end (E2E) path for heterogeneous networks in which a circuit network and a packet network are mixed using SDN technology.

In particular, when the present invention is followed, it becomes possible to control flows formed on end-to-end paths provided through heterogeneous networks, thereby providing an advantage of expanding the coverage of SDN and increasing flexibility.

1 is a conceptual diagram illustrating an environment in which SDN is applied and used in a carrier-class network.
2 is a conceptual diagram showing the basic structure of SDN.
3 is a conceptual diagram for explaining the concept of the integrated SDN controller according to the present invention to control a composite network environment in which a packet network and a circuit network are mixed.
4 is a block diagram illustrating a configuration example of an integrated SDN controller according to the present invention.
5 is a flowchart illustrating a method for an integrated SDN controller according to the present invention to provide an end-to-end path through integrated management of a packet network and a circuit network.
6 is a conceptual diagram illustrating a specific example of end-to-end path setting performed by the integrated SDN controller according to the present invention.

The present invention can be applied to various changes and may have various embodiments, and specific embodiments will be illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the present invention to specific embodiments, and should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention. In describing each drawing, similar reference numerals are used for similar components.

Terms such as first, second, A, and B can be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from other components. For example, the first component may be referred to as a second component without departing from the scope of the present invention, and similarly, the second component may be referred to as a first component. The term and / or includes a combination of a plurality of related described items or any one of a plurality of related described items.

When an element is said to be "connected" or "connected" to another component, it is understood that other components may be directly connected to or connected to the other component, but may exist in the middle. It should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that no other component exists in the middle.

The terms used in this application are only used to describe specific embodiments, and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "include" or "have" are intended to indicate the presence of features, numbers, steps, actions, components, parts or combinations thereof described herein, one or more other features. It should be understood that the existence or addition possibilities of fields or numbers, steps, operations, components, parts or combinations thereof are not excluded in advance.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person skilled in the art to which the present invention pertains. Terms such as those defined in a commonly used dictionary should be interpreted as having meanings consistent with meanings in the context of related technologies, and should not be interpreted as ideal or excessively formal meanings unless explicitly defined in the present application. Does not.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Hereinafter, the unified SDN controller referred to in the present invention means a functional element that controls related components (eg, switches, routers, etc.) to control the flow of traffic. It is not limited to the form of implementation or the location of the implementation. For example, the integrated SDN controller is a controller functional element defined by ONF (OpenFlow), Internet Engineering Task Force (IETF), European Telecommunication Standards Institute (ETSI), and / or International Telecommunication Union Telecommunication (ITU-T) ( entity). In addition, 'switch (switch)' or 'router (router)' referred to in the present invention means a functional element for substantially forwarding, switching, or routing traffic (or packets), ONF, IETF, ETSI, and / or Alternatively, it may mean a switch, a router, a switching element, a routing element, a forwarding element, etc. defined in ITU-T.

1 is a conceptual diagram illustrating an environment in which SDN is applied and used in a carrier network.

Referring to FIG. 1, a wireless network such as 3G / LTE 101, WiFi 101, and the like, back-bone network 103, router 104, edge access network 105 , All the carrier network equipment covering the data center 106 is connected to the SDN controller 120 through an open interface (110), and its settings and functions are controlled by the SDN controller 120. On the SDN controller, various applications 141, 142, 143, ... are operated through an open software development kit (SDK) 130.

The open nature of the SDN can open a closed carrier network to third parties to facilitate the provision of innovative new services, and can result in reductions in Capital Expenditures (CAPEX) and Operating Expenditure (OPEX). However, the research and development of SDN's carrier-class network application is still at a very basic stage, and in particular, it is necessary to specify the connection method of various heterogeneous networks.

The present invention proposes a method of providing an end-to-end path (E2E path) based on SDN technology from the perspective of a heterogeneous network (or a complex network) in which a circuit network and a packet network are interlocked among various heterogeneous networks.

In the present invention, the central control device uses the SDN technology without modifying the existing network configuration to build and operate the entire packet network and circuit network in an integrated form, thereby forming a network in which the packet network and the circuit network are mixed. Defines techniques to provide and manage appropriate end-to-end paths for users.

First, the characteristics of the circuit network and the packet network constituting the complex network which is the object of the present invention will be briefly described.

The purpose of the circuit network is to provide a communication path with guaranteed bandwidth between two geographically separated points. Circuit equipments representing transport networks have traditionally developed their own control and management technologies for each manufacturer, so it is difficult to interoperate with each other. Therefore, when establishing a communication network, the equipment domains for each manufacturer are constructed and the interworking and operation between them is It is common to do it in a central operational support system. Therefore, the transmission network composed mainly of circuit networks takes the form of centralized control.

On the other hand, the service network built on the transport network is built on the basis of packet technology, and the linkage between equipment manufacturers is unified through continuous standardization. For example, the IP-based connection link connecting two routers is physically connected at the lower layer of the transport layer on the network protocol, and logical connection is achieved by allocation of slots by time division or wavelength division techniques. Each device is operated with its own control, but the operation mechanism is elaborately implemented so that normal operation of the entire network can be achieved. Therefore, the service network composed mainly of packet networks takes the form of distributed control.

Meanwhile, Software Defined Network (SDN) is a next-generation networking technology that can conveniently handle network routing and control and complex operation management through software programming. To this end, SDN separates the data plane and control plane of the network and provides a standardized interface therebetween. Therefore, the network operator can control the communication function performed in the data plane in various ways by programming the control plane according to various situations.

SDN is based on the separation of the control plane and the transmission plane. The standardized interface between the two planes is the OpenFlow standardized by ONF or the Interface to Routing System (I2RS) standardized by IETF. However, SDN does not limit OpenFlow or I2RS to its underlying technology. In other words, SDN is a much larger concept, a network structure or a new paradigm, and OpenFlow and I2RS are one of the interface technologies for SDN.

Currently, ONF, which is promoting SDN standardization, views the SDN based on two basic principles.

First, SDN needs to do software defined forwarding. This means that the data forwarding function handled by the hardware at the switch / router must be controlled through an open interface and software.

Second, SDN aims at Global Management Abstraction. SDN should enable more advanced network management tools to be developed through abstraction. For example, these abstraction tools may include the ability to control network elements and react to events (such as topology changes or new flow inputs) while viewing the state of the entire network.

2 is a conceptual diagram showing the basic structure of SDN.

Referring to FIG. 2, the intelligence of the network is centralized in the SDN controller 231 to manage the entire network, and the network is regarded as one logical switch. A manager (or a network management system (NMS)) can control all network devices 211, 212, 213, ... through a standardized interface 220 without vendor dependency, and design and operate the network. Can be simplified.

In addition, SDN can also simplify network devices. That is, when designing a device, it is not necessary to consider processing hundreds to thousands of protocols (RFC; Request for Comments), and simply need to receive a command from an SDN controller to process data.

The network administrator does not need to manually manage configuration information of tens of thousands of lines distributed over thousands of devices, for example, and can control the network simply by constructing an abstracted network with a program.

In addition to the network abstraction, SDN provides a series of application programming interfaces (APIs) 240 between the SDN control layer 230 and the application layer 250. A common network service can be implemented by using the API, and all types of policy management such as routing, access control, traffic engineering, QoS management, and power control suitable for business goals are possible.

However, although there are many discussions on the benefits and functions that can be obtained through the introduction of SDN technology, specific cases are rare about the connection schemes of various heterogeneous networks constituting the infrastructure layer 210.

In particular, for wired and wireless communication providers, offloading of mobile data, smart content delivery that comprehensively considers the resources and traffic conditions of the entire infrastructure, and virtualization control and real-time management of long-distance delivery networks, including metro Ethernet and optical transmission networks, are organically managed by software. It is expected to develop SDN with the concept of integrated control. Therefore, rather than replacing the existing network at once through the SDN network, it is essential to introduce a concept of SDN into the existing heterogeneous mixed network and gradually apply it.

3 is a conceptual diagram for explaining the concept of the integrated SDN controller according to the present invention to control a composite network environment in which a packet network and a circuit network are mixed.

The service controller 310 is a functional entity that serves as a broker for providing application services, and serves as an end-point to the user. For example, the service controller makes it possible to search for the type of service provided to the user, and serves to receive a request for a desired service from the user. Meanwhile, the service controller 310 is an external component interworking with the integrated SDN controller 320 to be described later according to the present invention, and its detailed implementation and operation method are not described in the present invention.

Next, the cloud controller (cloud controller) 330 utilizes the resources in the cloud data center (Cloud Data Center; CDC; 331; or, Data Center) to use the virtual machine (Virtual Machine) required to provide application services It creates and provides a path that connects to the created virtual machine to the outside and provides it. Meanwhile, the cloud controller 330 is an external component interworking with the integrated SDN controller 320 according to the present invention, and its detailed implementation and operation method are not described in the present invention. In this specification, the term 'cloud controller' refers to a cloud data center or any functioning entity that governs data centers, and should not be limited by the term 'cloud'.

Finally, the integrated SDN controller 320 according to the present invention generates the path of the packet section 321 and the circuit section 322 based on the user's request received through the service controller 310. And connecting to form an end-to-end path.

In many cases, since the other end of the end-to-end path becomes a virtual machine in the cloud data center 331, the integrated SDN controller 320 generates the end-to-end path for the virtual machine provided by the cloud controller 330 described above. The application service can be delivered to the user by connecting to the path.

Referring to FIG. 3, the service controller 310 is requested to set an end-to-end path from a user who becomes one end of the end-to-end path (S301). At this time, instead of the user becoming one end of the end-to-end path, the other end of the end-to-end path (the other user or the virtual machine in the CDC) or a third party may be requested to set the end-to-end path. In addition, one end of the end to end path may be a virtual machine or a server in a data center as well as a user.

At this time, the user can perform a route setting request for the corresponding service by searching for the type of service provided through the service controller and revealing the intention to use the specific service. Next, the service controller 310 requests generation of the end-to-end path to the integrated SDN controller 320 based on the location and path characteristics of the end (user) that requested the path setup (S302).

Next, the integrated SDN controller 320 generates a path 321 on the packet network constituting the end-to-end path in response to the service controller 310 request for generating the end-to-end path (S305), and configures the end-to-end path. After generating the path 322 on the circuit network (S306), the generated paths are connected to generate mapping information of the end-to-end path to configure the end-to-end path, and the generated end-to-end path is again service controller 310. Notify (S307).

Meanwhile, the integrated SDN controller 320 may request the cloud controller 330 to determine and provide the data center where the service to be provided is located and the characteristics of the required virtual machine and the path characteristics from the virtual machine to the external contact point of the data center ( S303). In response to this, the cloud controller 330 may generate a virtual machine to mount the service and a path from the corresponding virtual machine to an external contact point upon request, and provide it to the integrated SDN controller (S304).

Meanwhile, the above-described interworking procedures (S303, S304) between the integrated SDN controller and the cloud controller may be performed prior to the circuit network and packet network path generation procedures (S305, S306) for constructing the aforementioned end-to-end path. , Circuit network, packet network path generation procedure, or may be performed after the circuit network, packet network path creation procedure.

4 is a block diagram illustrating a configuration example of an integrated SDN controller according to the present invention.

4, the integrated SDN controller 320 according to the present invention includes a packet network application programming interface (API) unit 321, a circuit network application programming interface (API) unit 324, and a packet topology management unit 322. ), Circuit topology management unit 235; Adapter section 328; And it may be configured to include a control unit 327.

First, the packet network application programming interface 321 is a communication interface for transmitting commands of route setting and route management to packet equipments 351, 352, 353, ..., and collecting information.

Next, the circuit network application programming interface 324 is a communication interface for issuing commands for route setting and route management for circuit devices 361, 362, 363, ..., and collecting information.

Next, the packet topology management unit 322 maintains and manages connection shapes of devices in a packet network section in real time. In addition, the circuit topology management unit 325 serves to maintain and manage the connection shape of equipment in the circuit network section in real time.

On the other hand, the integrated SDN controller 320 according to the present invention collects information on links in the packet network section so that the packet topology management unit 322 can maintain and manage the packet network section in real time in the form of connection of the devices in the packet network section. The packet link discovery unit 323 provided to the packet topology management unit may be further included. That is, the packet link discovery unit may serve to automatically update topology information by automatically discovering new links in a packet network section, links in a failed state, or links recovered from a failure.

In addition, the integrated SDN controller according to the present invention collects information on links in the circuit network section, so that the circuit topology management section maintains and manages in real time in the form of connection of equipment in the circuit network section, the circuit topology (topology) ) The circuit link discovery unit 326 provided to the management unit may be further included. That is, the circuit link discovery unit serves to automatically update topology information by automatically discovering new links in the circuit network section, links in a failed state, or links recovered from a failure.

Accordingly, when the above-described packet topology management unit 322 and the circuit topology management unit 325 are interlocked, integrated network topology information of the composite network can be obtained, and the packet and circuit link discovery units 323 and 236 When interlocking, information of a new link, a link in a failure state, or a link recovered from a failure may be updated in real time.

Next, the adapter unit 328 is a component that performs command transmission to lower devices. That is, the adapter unit 328 receives a command to be transmitted to the lower devices 351, 352, 353, 361, 362, and 363 from the control unit 327 to be described later, and packets APIs corresponding to the command. The lower devices are directly managed by calling through the API unit 321 or the circuit API unit 324.

Finally, the control unit 327 forms the end-to-end path connecting the circuit network and the packet network using the connection shape information of the packet topology management unit and the circuit topology management unit, and the circuit network and the packet network through the adapter unit. It serves to set the end-to-end path to network devices.

In addition, the control unit 327 serves to receive a request for generating the end-to-end path from a user through a service controller that mediates the provision of application services. In addition, the control unit 427 connects the end-to-end path with a path to a virtual machine in a cloud data center, and the end-to-end path is communicated to a cloud controller managing the cloud data center. It serves to provide information about the characteristics of the virtual machine and the path of the virtual machine in the cloud data center. In order for the control unit 327 to communicate with a service controller or a cloud data center, the integrated SDN controller 320 may include additional components (not shown) for communication.

As an additional component, the integrated SDN controller may include a database management unit (not shown) that performs a function of storing and managing information generated or maintained by the above-described components including packet and circuit topology management units in a database format. You can.

5 is a flowchart illustrating a method for an integrated SDN controller according to the present invention to provide an end-to-end path through integrated management of a packet network and a circuit network. Meanwhile, FIG. 6 is a conceptual diagram illustrating a specific example of end-to-end path setting performed by the integrated SDN controller according to the present invention.

Hereinafter, FIGS. 5 and 6 are referred to in parallel to describe embodiments of the present invention.

First, referring to FIG. 5, the integrated SDN controller generates an end-to-end path in response to a request for generating an end-to-end path of the service controller. Generating step (S510), generating a path on the packet network constituting the end-to-end path (S520) and connecting the path on the circuit network and the path on the packet network by using the circuit network and the topology information of the packet network. It may be configured to include a step (S530).

At this time, the execution order of steps S510 and S520 is not limited. That is, step S520 may be executed before step S510, and steps S510 and S520 may be performed in parallel.

Hereinafter, specific examples of the above-described step (S510) of constructing a path on the circuit network, step (S520) of constructing a path on the packet network, and step (S530) of connecting a path on the circuit network and a path on the packet network are described. The specific execution method of the above-described steps (S510, S520, S530) is not necessarily limited to the method described below.

First, the step of generating a path on the circuit network (S510) is specifically through the circuit topology management unit 325, the control unit 327, the adapter unit 328, and the circuit API unit 324 described through FIG. Can be performed.

That is, when the control unit 327 receives an end-to-end path setting request 610 from an external (for example, a service controller), the control unit based on the current circuit network connection configuration information maintained by the circuit topology management unit 325. As a circuit path setup (Circuit Path Setup; 620) illustrated in Figure 6 to define the connection configuration for the two nodes (621, 622) to be connected.

Next, the control unit 327 refers to the current circuit network configuration information maintained by the circuit topology management unit 325 and real-time link information collected by the circuit link discovery unit, between two nodes defined in the circuit path setting. Existing links are sequentially described to complete the circuit path on the circuit network section. At this time, a unique circuit path name may be assigned to the path on the generated circuit network section.

In addition, the control unit 327 is in accordance with the API protocol of the circuit network equipment in order to secure the completed path through the adapter unit 328 and the circuit API unit 324, the actual circuit equipment (361, 362, 363, ... ) To send the commands to set the path.

Next, the step of creating a route on the packet network (S520) is specifically through the packet topology management unit 322, the control unit 327, the adapter unit 328, and the packet API unit 321 described through FIG. Can be performed.

That is, when the controller 327 receives the end-to-end path setting request 610 from an external (eg, service controller), the control unit 327 is based on the current packet network connection configuration information maintained by the packet topology management unit 322. As shown in the packet path setup (Packet Path Setup; 630) illustrated in FIG. 6, a connection configuration for two nodes 622 and 623 to be connected is defined.

Next, the control unit 327 refers to the current packet network configuration information maintained by the packet topology management unit 322 and the real-time link information collected by the packet link discovery unit, to connect the two nodes defined in the packet path setting. Specifies that the virtual network name (VLAN-ID in the example of FIG. 6) is recognized for network nodes on the path. To this end, the packet topology management unit 322 searches for current connection configuration information to check available paths.

In order to allow the nodes on the identified path to set the identified path, it goes through the adapter unit 328 and the packet API unit 321 in accordance with the API protocol of the packet network equipments to actual packet equipments 351, 352, 353, ... Sends commands to set the determined route.

Finally, in step S530 of connecting the path on the circuit network and the path on the packet network, between the circuit path on the circuit network and the packet path on the packet network generated in steps S510 and S520, respectively. Mapping information 640 defining a connection relationship is generated to complete generation of a path in a final end-to-end section, and mapping information is managed in a table form.

At this time, the generated end-to-end path is assigned a unique identifier and can be managed in the form of a table, and information on the generated end-to-end path can be provided to at least some of the nodes constituting the end-to-end path. have. For example, the information about the generated end-to-end path is in the form of mapping information illustrated through FIG. 6, one end of the end-to-end (eg, a user) and / or the other end (eg, a virtual machine in a cloud data center) ).

Although described above with reference to preferred embodiments of the present invention, those skilled in the art variously modify and change the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. You can understand that you can.

310: service controller
320: integrated SDN controller
321: packet API unit 322: packet topology management unit
323: packet link discovery unit
324: Circuit API section 325: Circuit topology management section
326: circuit link discovery unit
327: control unit 328: adapter unit
351 ~ 353: Packet network network device
361 ~ 363: Circuit network network device

Claims (19)

A method of operating an integrated software-defined network controller that provides an end-to-end path through integrated management of a circuit network and a packet network,
Generating a path on the circuit network constituting the end-to-end path;
Generating a path on the packet network constituting the end-to-end path; And
And connecting a path on the circuit network and a path on the packet network using topology information of the circuit network and the packet network,
A method of operating an integrated software defined network controller, wherein at least a portion of the end-to-end path consists of a path on the circuit network and at least a portion of a path on the packet network. The method according to claim 1,
The configuration information includes link state information between nodes defined in the circuit network and the packet network, and a method of operating an integrated software-defined network controller. The method according to claim 1,
And receiving a request to create the end-to-end path. The method according to claim 3,
The request for generating the end-to-end path is received from a user through a service controller that mediates the provision of application services, and the method of operating the integrated software-defined network controller. The method according to claim 1,
A method of operating an integrated software-defined network controller, further comprising associating the end-to-end path with a path to a virtual machine in a cloud data center. The method according to claim 5,
And providing information regarding a characteristic of the virtual machine and a characteristic of a path to a virtual machine in the cloud data center to a cloud controller managing the cloud data center. The method according to claim 1,
The integrated software-defined network controller, using the predefined application programming interface (API), further comprising the step of transmitting information about the path on the generated circuit network to the circuit network equipment, integrated software-defined network controller How it works. The method according to claim 1,
The integrated software-defined network controller using a predefined application programming interface (API), further comprising the step of transmitting information about the path on the generated packet network to the packet network network equipment, How it works. The method according to claim 8,
The predefined application programming interface (API) is based on the OpenFlow or IETF I2RS (Interface to Routing System) protocol, the operation method of the integrated software-defined network controller. An integrated software-defined network controller device that provides an end-to-end path through integrated management of circuit networks and packet networks.
A packet topology management unit that maintains and manages connection configuration information of packet network devices;
A circuit topology management unit that maintains and manages connection configuration information of circuit network network devices;
An adapter unit that performs command transmission to lower devices; And
Using the packet topology management unit and the connection topology information of the circuit topology management unit, the end-to-end path connecting the circuit network and the packet network is generated, and the end-to-end path is provided to the circuit network and packet network network devices through the adapter unit. It includes a control unit to set,
An integrated software defined network controller device, wherein at least a portion of the end-to-end path consists of a path on the circuit network and at least a portion of a path on the packet network. The method according to claim 10,
An integrated software-defined network controller device further comprising a packet link discovery unit that collects information about links in the packet network section and provides the packet topology management unit with the information. The method according to claim 10,
An integrated software-defined network controller device further comprising a circuit link discovery unit that collects information on links in the circuit network section and provides the circuit topology to the circuit topology management unit. The method according to claim 10,
The control unit receives a request to generate the end-to-end path through a service controller that mediates the provision of an application service from a user. The method according to claim 13,
The control unit provides information on the generated end-to-end path to at least some of the nodes constituting the end-to-end path, an integrated software-defined network controller device. The method according to claim 10,
The control unit connects the end-to-end path with a path to a virtual machine in a cloud data center, an integrated software-defined network controller device. The method according to claim 15,
The control unit provides the end-to-end path to the cloud controller managing the cloud data center, providing information about the characteristics of the virtual machine and the path characteristics of the virtual machine in the cloud data center. The method according to claim 10,
An integrated software defined network controller device further comprising a packet network application programming interface (API) unit for communicating with packet network network devices, the adapter unit communicating with the packet network network devices via the packet network API unit. The method according to claim 17,
The application programming interface (API) of the packet network application programming interface (API) unit is based on the I2RS protocol of OpenFlow or IETF, an integrated software-defined network controller device. The method according to claim 10,
An integrated software-defined network controller device further comprising a circuit network application programming interface (API) unit for communicating with circuit network network devices, wherein the adapter unit communicates with the circuit network network devices through the circuit network API unit.

Images