CN104620546B - Information processor, collocation method, communication system and program - Google Patents

Abstract

The easy setting (easy configurability) of centralized Control type network can be improved without controlling it flexibility to produce infringement.A kind of information processor configured to control network-based control device, including：Display unit, the display unit is shown with storing for controlling the first corresponding icon of the database of the network-based control information and multiple second icons over the display, each in the plurality of second icon corresponds to one of multiple modules, and each in the plurality of module operates the control information based on pre-defined algorithm；And administrative unit, the administrative unit configure the control device, the control device has following functions：According to the connection of any one in first icon and second icon, the module corresponding with second icon is connected to the database, and the control information is operated in response to the database manipulation order issued by the module.

Description

Information processing device, configuration method, communication system, and program

(Cross-reference to related application)

This application is based on and claims the benefit of priority from Japanese Patent Application No. 2012-202112 filed on September 13, 2012, the entire disclosure of which is incorporated herein by reference.

technical field

The present invention relates to an information processing device, a configuration method, a communication system and a program. Specifically, the present invention relates to an information processing device for configuring a control device that controls a switch group to thereby centrally manage the switch group; a configuration method; a communication system; and a program.

Background technique

In recent years, a technique called OpenFlow (OpenFlow) has been proposed (see Non-Patent Literature (NPL) 1 and 2). OpenFlow treats communication as an end-to-end flow and performs path control, failure recovery, load balancing, and optimization on a per-flow basis. An OpenFlow switch according to NPL 2 has a secure channel for communicating with an OpenFlow controller, and operates according to a flow table appropriately added or rewritten by the OpenFlow controller. In the flow table, a set of the following three items is defined for each flow: the matching condition (matching field) that matches the header of the packet; the flow statistics (counter); and the instruction that defines the processing content (see NPL 2, Section 4.1 "Flow surface").

For example, when receiving a packet, the OpenFlow switch searches the flow table for an entry with a matching condition (see "4.3 Matching Field" in NPL 2) that matches the header information of the incoming packet. If, as a result of the search, the OpenFlow switch finds an entry matching the incoming packet, the OpenFlow switch updates the flow statistics (counters) and based on the processing content written in the command field of the entry (packet transmission from the specified port , flooding, dropping, etc.) to process incoming packets. If the OpenFlow switch does not find an entry matching the incoming packet as a result of the search, the OpenFlow switch transmits an entry setting request (packet entry message) to the OpenFlow controller via a secure channel. That is, the OpenFlow switch requests the OpenFlow controller to send control information for processing incoming packets. The OpenFlow switch receives flow entries defining processing content and updates the flow table. In this way, the OpenFlow switch performs packet forwarding by using the entries stored in the flow table as control information.

[NPL 1]

Nick McKeown and seven other authors, "OpenFlow: Enabling Innovation in CampusNetworks", [online], [searched 13 July 2012], Internet <URL: http://www.openflow.org/documents/openflow-wp -latest.pdf>

[NPL 2]

"OpenFlow Switch Specification" version 1.1.0 implementation (wire protocol 0x01), [online], [retrieved 13 Jul 2012], Internet <URL: http://www.openflow.org/documents/openflow-spec- v1.0.0.pdf>

Contents of the invention

The present invention has given the following analysis. In the centralized control type network represented by OpenFlow in NPL 1 and 2 above, detailed control can be performed. However, in order for the control means corresponding to the OpenFlow controller in the above NPL 1 and 2 to perform desired operations, the operator needs to program the control operations of the controllers. In addition to the basic specification of NPL 2, programming of controllers requires advanced knowledge and techniques such as for managing network configuration, configuration of programming and testing environments.

For example, in NPL 2, in order to configure the OpenFlow controller, various items need to be set up and programmed, including association between each switch and control channel, topology search by LLDP (Link Layer Discovery Protocol), path Computed, setup of flow entries in multiple switches along the path and management of input/output packets per switch. For example, in order to perform programming, a lot of knowledge and skills are required, such as about API (Application Programming Interface) related to topology management and route calculation, many functions related to the API and parameters that need to be given to these functions.

Therefore, even if the equipment of the centralized control type network is installed, the user may not be able to fully utilize the control flexibility.

An object of the present invention is to provide: an information processing device capable of improving the ease of setting (easy configuration) of a centralized control type network without impairing its control flexibility; a configuration method; a communication system; and a program.

According to a first aspect, there is provided an information processing device that configures a control device that controls a network. The information processing apparatus includes: a display unit that displays on the display a first icon corresponding to a database storing control information for controlling the network and a plurality of second icons, the plurality of second icons each of the icons corresponds to one of a plurality of modules each of which operates the control information based on a predetermined algorithm; and a management unit configuring the control device, the control device It has the following functions: according to the connection between the first icon and any one of the second icons, connect the module corresponding to the second icon to the database, and respond to the database issued by the module operation commands to manipulate the control information.

According to a second aspect, a method of configuring a control device of a control network is provided. The configuration method includes: displaying on a display a first icon corresponding to a database storing control information for controlling the network and a plurality of second icons, each of the plurality of second icons corresponding to a plurality of one of the modules, each of the plurality of modules operates the control information based on a predetermined algorithm; and configures the control device, the control device has the following functions: according to the first icon and the second icon connection of any one of the icons, connects the module corresponding to the second icon to the database, and operates the control information in response to a database operation command issued by the module. This method is associated with a specific machine, ie with said control means controlling said network by using said database and modules.

According to a third aspect, there is provided a communication system including an information processing device configuring a control device for controlling a network. The information processing apparatus includes: a display unit that displays on the display a first icon corresponding to a database storing control information for controlling the network and a plurality of second icons, the plurality of second icons each of the icons corresponds to one of a plurality of modules each of which operates the control information based on a predetermined algorithm; and a management unit configuring the control device, the control device It has the following functions: according to the connection between the first icon and any one of the second icons, connect the module corresponding to the second icon to the database, and respond to the database issued by the module operation commands to manipulate the control information.

According to a fourth aspect, there is provided a program that causes an information processing device that configures a control device that controls a network to perform a process of displaying on a display a program corresponding to a database storing control information for controlling the network. a first icon and a plurality of second icons, each of the plurality of second icons corresponds to one of a plurality of modules, each of the plurality of modules operates the control information based on a predetermined algorithm; and Configuring the control device, the control device has the following functions: according to the connection between the first icon and any one of the second icons, connect the module corresponding to the second icon to the database, and manipulating the control information in response to a database manipulation command issued by the module. This program can be recorded in a computer readable (non-transitory) storage medium. That is, the present invention can also be realized as a computer program product.

Valuable effects of the present invention are summarized as follows.

According to the present invention, the ease of setup (ease of configuration) of a centralized control type network can be improved without impairing its control flexibility.

Description of drawings

FIG. 1 shows the configuration of a system according to a first exemplary embodiment of the present disclosure.

FIG. 2 shows the configuration of a control device according to the first exemplary embodiment of the present disclosure.

FIG. 3 shows the configuration of a network DB according to the first exemplary embodiment of the present disclosure.

FIG. 4 is a sequence diagram showing operations according to the first exemplary embodiment of the present disclosure.

FIG. 5 is a sequence diagram showing operations according to the first exemplary embodiment of the present disclosure.

FIG. 6 is a sequence diagram showing operations according to the first exemplary embodiment of the present disclosure.

FIG. 7 shows the configuration of a network DB according to the second exemplary embodiment of the present disclosure.

FIG. 8 shows the configuration of a network DB according to the second exemplary embodiment of the present disclosure.

FIG. 9 shows the configuration of a network DB according to the second exemplary embodiment of the present disclosure.

FIG. 10 shows database operation commands (DB operation commands) used in the second exemplary embodiment of the present disclosure.

FIG. 11 shows database operation commands (DB operation commands) used in the second exemplary embodiment of the present disclosure.

FIG. 12 shows the configuration of a system according to a third exemplary embodiment of the present disclosure.

FIG. 13 shows the configuration of an OpenFlow control unit according to a third exemplary embodiment of the present disclosure.

FIG. 14 shows the operation flow of the network DB by the topology processing unit according to the third exemplary embodiment of the present disclosure.

FIG. 15 shows the operation flow of the network DB by the stream processing unit according to the third exemplary embodiment of the present disclosure.

FIG. 16 shows the operation flow of the network DB by the packet processing unit according to the third exemplary embodiment of the present disclosure.

FIG. 17 is a sequence diagram showing operations according to the third exemplary embodiment of the present disclosure.

FIG. 18 is a sequence diagram showing operations according to the third exemplary embodiment of the present disclosure.

FIG. 19 is a sequence diagram showing operations according to the third exemplary embodiment of the present disclosure.

FIG. 20 is a sequence diagram showing operations according to the third exemplary embodiment of the present disclosure.

FIG. 21 shows the configuration of a system according to a fourth exemplary embodiment of the present disclosure.

FIG. 22 shows a graphical display of a network topology according to a fourth exemplary embodiment of the present disclosure.

FIG. 23 shows a graphic display of packet processing information according to the fourth exemplary embodiment of the present disclosure.

FIG. 24 shows a graphic display of packet input and output information according to the fourth exemplary embodiment of the present disclosure.

FIG. 25 shows the configuration of a system according to a fifth exemplary embodiment of the present disclosure.

FIG. 26 shows the configuration of a system according to a sixth exemplary embodiment of the present disclosure.

FIG. 27 shows the configuration of a system according to a seventh exemplary embodiment of the present disclosure.

FIG. 28 shows the operation of the network DB by the aggregation logic unit according to the seventh exemplary embodiment of the present disclosure.

FIG. 29 shows operations of a network DB by an aggregation logic unit according to a seventh exemplary embodiment of the present disclosure.

FIG. 30 shows the operation of the network DB by the aggregation logic unit according to the seventh exemplary embodiment of the present disclosure.

FIG. 31 shows the configuration of a system according to an eighth exemplary embodiment of the present disclosure.

FIG. 32 shows operations of a network DB by an integrated logic unit according to an eighth exemplary embodiment of the present disclosure.

FIG. 33 shows operations of a network DB by an integrated logic unit according to an eighth exemplary embodiment of the present disclosure.

FIG. 34 shows the configuration of a system according to a ninth exemplary embodiment of the present disclosure.

FIG. 35 shows a configuration of a component manager of a control device according to a ninth exemplary embodiment of the present disclosure.

FIG. 36 shows the configuration of a system according to a tenth exemplary embodiment of the present disclosure.

FIG. 37 illustrates a screen displayed on a display unit according to a tenth exemplary embodiment of the present disclosure.

FIG. 38 shows the correspondence between user operation contents and control device configurations according to the tenth exemplary embodiment of the present disclosure.

FIG. 39 shows the correspondence between user operation contents and control device configurations according to the tenth exemplary embodiment of the present disclosure.

FIG. 40 shows the correspondence between user operation contents and control device configurations according to the tenth exemplary embodiment of the present disclosure.

FIG. 41 shows the correspondence between user operation contents and control device configurations according to the tenth exemplary embodiment of the present disclosure.

FIG. 42 shows the correspondence between user operation contents and control device configurations according to the tenth exemplary embodiment of the present disclosure.

detailed description

<First Exemplary Embodiment>

According to the first exemplary embodiment of the present disclosure, the control device can control the network in a centralized manner by operating a DB (database) that stores control information related to the configuration of the network and the method of processing packets in the network . For example, DB is configured through key-value storage and operated through predetermined DB operation commands. The DB can be operated by simple operation commands such as commands for inputting information to and outputting information from the DB and commands for deleting information in the DB. In the first exemplary embodiment, the control device can be configured by combining modules that operate the DB by operation commands. Therefore, the control device according to the first exemplary embodiment can be programmed by a simple DB operation command without using API or many functions related thereto.

Next, a first exemplary embodiment will be described in detail with reference to the drawings. FIG. 1 shows the configuration of a communication system according to a first exemplary embodiment of the present disclosure. In FIG. 1, the communication system is configured by a control device 1, a network DB 2, and a network 4 including a plurality of nodes.

The control device 1 controls the network 4 in a centralized manner by operating the network DB 2 .

Each node 3 in the network 4 processes packets according to the control means 1 .

For example, Web DB 2 is a database configured by key-value storage. For example, the web DB2 stores identification information (key) and data (value) in pairs. In the network DB 2, identification information (key) is set for each data (value).

FIG. 2 shows the configuration of the control device 1 . In FIG. 2 , the control device 1 includes a DB operation logic unit 11 , a network control unit 12 and a DB interface unit 10 connected to the network DB 2 .

The DB interface unit 10 has a function of operating the network DB 2 by using predetermined DB operation commands issued by the DB operation logic unit 11 . Alternatively, the control device 1 may be configured by combining a plurality of DB operation logic units 11 . Therefore, the DB interface unit 10 can be connected to a plurality of DB operation logic units 11 (parts indicated by dotted lines in FIG. 2 ). The DB interface unit 10 can operate the network DB 2 by using commands issued from a plurality of DB operation logic units 11 . The DB interface unit 10 can configure information based on a combination of a plurality of DB operation logic units 11 in the network DB 2 . That is, the operator can easily change the configuration of the network DB 2 by changing the combination of a plurality of DB operation logic units 11 connected to the DB interface unit 10 . Thus, the operator can easily configure the control device 1 to be suitable for the type of network 4 or for the communication protocol used in the network 4 .

Examples of commands for operating the network DB 2 will be listed below. However, since the following commands are examples, the DB operation commands according to the present disclosure are not limited to the following examples.

Information input/output commands

message deletion command

Notification subscription command

The information input/output command is used to input information to the network DB 2 . Also, information input/output commands are used to acquire information from the network DB 2 . For example, the DB interface unit 10 acquires data (value) corresponding to the identification information (key) from the network DB 2 using the command "get (key)". Furthermore, the DB interface unit 10 uses the command "put (set) (key, value)" to input data (value) corresponding to the identification information (key) to the network DB 2 . If the data (value) is listed, the DB interface unit 10 can use the command "push (push) (key, value)" or the command "pop (pop) (key, value)" to perform the input of the data (value) or output. That is, data can be used as a queue or as a stack.

The message delete command is used to delete messages from the network DB2. For example, the DB interface unit 10 uses the command "delete (key)" to delete the data (value) corresponding to the identification information (key) from the network DB 2 .

For example, the notification subscribe command is used to subscribe. With this command, if an operation corresponding to the specified identification information (key) is performed on the network DB 2, the network DB 2 notifies the DB interface unit 10 of data (value) corresponding to the identification information (key). For example, the DB interface unit 10 sends a command "subscribe (subscribe) (key)" to the network DB 2, and if an operation corresponding to the identification information (key) is performed, the DB interface unit 10 receives from the network DB 2 the same as the identification information ( key) corresponding data (value). Key patterns, such as wildcards or regular expressions, can be used to identify information. For example, the network DB 2 can use the command "publish (key, value, op)" to notify the DB interface unit 10 of data (value) corresponding to the identification information. Operations (including put/get/delete) corresponding to keys may be included in "op". After the notification, the DB operation logic unit 11 may recognize the addition, acquisition, or deletion of the key corresponding to the identification information.

Multiple DB operation logic units 11 can share a common DB operation command. The network operator can easily expand the DB operation logic unit 11 by allowing a plurality of DB operation logic units 11 to operate the network DB 2 with a common command. That is to say, when the DB operation logic unit 11 having new functions is added to the control device 1 , the operator does not need to newly design the interface between the DB operation logic unit 11 and the network DB 2 .

The DB operation logic unit 11 has a function of operating information stored in the network DB 2 based on a predetermined algorithm defined according to the type of the DB operation logic unit 11 . For example, the DB operation logic unit 11 has a function of inputting information acquired from the network 4 to the network DB 2 via the DB interface unit 10 .

The network control unit 12 has a function of controlling the network 4 based on the network DB 2 configured by the operation of the DB operation logic unit 11 . For example, the network control unit 12 can change the method of controlling the network 4 according to the communication protocol used in the network 4 .

FIG. 3 shows the configuration of the network DB 2 . This configuration of FIG. 3 is an example, so the configuration of the network DB 2 is not limited to that in FIG. 3 .

For example, the network DB 2 includes information on the topology of the network 4 (topology information; first information), information on a packet processing method (packet processing information; second information), and information on packets (packet information; third, second information). 4 information).

For example, the topology information includes information on each node 3 existing in the network 4 (node information) and information on links between each node pair (link information). For example, the node information includes information on the identifier and communication port of the node 3 . For example, the link information includes: an identifier of the link, an identifier of the node 3 connected to the link, and an identifier of a communication port of the node 3 connected to the link.

Packet processing information includes flow information. The flow information is information on the flow to which the packet belongs. A flow represents a group of communication packets having predetermined attributes (attributes that can be identified based on communication destinations, sources, etc.). For example, flow information includes matching conditions, path information, and processing information. For example, the matching condition indicates a condition for identifying a packet corresponding to flow information. For example, the path information indicates a path through which a packet belonging to a flow matching a matching condition passes. For example, the processing information indicates processing to be performed on a packet passing through a path corresponding to the path information (for example, rewriting header information).

The grouping information includes input grouping information and output grouping information. The input packet information is a packet that does not match the matching condition in any flow information among the packets received from the network 4 . The output packet information is a packet to be output from the network 4 .

For example, topology information, packet processing information, and input packet information stored in the network DB 2 may be standardized in a predetermined format. By standardizing the information stored in the network DB 2, the network DB 2 can have compatibility with networks conforming to various protocols.

4 to 6 illustrate operations according to the first exemplary embodiment. Since the operations of FIGS. 4 to 6 are examples, the operations according to the present disclosure are not limited to the operations shown in these drawings.

4 to 6 show examples in which the network DB 2 is operated by a plurality of DB operation logic units 11 ("DB operation logic units 11-1 and 11-2"). The DB operation logic unit 11-1 has a function of operating the network DB 2 and inputting/outputting information on the topology. The DB operation logic unit 11-2 has a function of generating packet processing information based on information stored in the network DB 2.

FIG. 4 shows the operation of the DB operation logic unit 11 - 1 to manage the topology of the network 4 by operating the network DB 2 .

The DB operation logic unit 11-1 of the control device 1 collects information on the topology from the network 4 via the network control unit 12 (S10). Information about the topology is collected by using eg LLDP (Link Layer Discovery Protocol). LLDP is by which devices on a network exchange information with neighboring devices and collect information about neighboring devices connected to a communication port of the device. For example, the network control unit 12 collects from each node 3 information that has been collected by each node 3 in the network 4 through LLDP.

For example, the DB operation logic unit 11-1 generates topology information in a predetermined format corresponding to the network DB 2 based on information collected via the network control unit 12 (S11).

By using a DB operation command (information input/output command), the DB operation logic unit 11-1 stores the generated topology information into the network DB 2 via the DB interface unit 10 (S12).

FIG. 5 shows that the DB operation logic unit 11 - 2 generates information related to a method of processing packets flowing in the network 4 by operating the network DB 2 .

By using a DB operation command (information input/output command), the DB operation logic unit 11-2 of the control device 1 acquires topology information from the network DB 2 via the DB interface unit 10 (S13).

The DB operation logic unit 11-2 can preset the network DB2 by using the notification subscription command so that when the topology information changes, the network DB 2 notifies the DB operation logic unit 11-2 of the change of the topology information. When the topology information is changed, the network DB 2 notifies the DB operation logic unit 11 - 2 of the change of the topology information via the DB interface unit 10 .

Based on the topology information acquired from the network DB 2, the DB operation logic unit 11-2 generates packet processing information in a predetermined format corresponding to the network DB 2 (S14). For example, the DB operation logic unit 11-2 calculates a packet forwarding path ("path information" in FIG. 3) and stores the calculated forwarding path into the packet processing information. For example, the DB operation logic unit 11-2 calculates the forwarding path by using predetermined calculation logic. For example, the DB operation logic unit 11-2 sets the shortest path from the source to the destination as the packet forwarding path.

Furthermore, the DB operation logic unit 11-2 stores packet matching conditions and processing information (such as rewriting headers) into the packet processing information.

By using a DB operation command (information input/output command), the DB operation logic unit 11-2 stores the generated packet processing information into the network DB 2 via the DB interface unit 10 (S15).

FIG. 6 shows that the control device 1 controls the operation of the node 3 in the network 4 by operating the network DB 2 .

By using a DB operation command (information input/output command), the DB operation logic unit 11 - 1 of the control device 1 acquires packet processing information from the network DB 2 via the DB interface unit 10 ( S16 ).

The DB operation logic unit 11-1 can preset the network DB2 by using the notification subscription command so that when the packet processing information changes, the network DB 2 notifies the DB operation logic unit 11-1 of the change of the packet processing information. For example, the DB operation logic unit 11-1 uses a notification subscription command to set a notification condition for notifying an update of the network DB 2 into the network DB 2 . When an update matching this preset notification condition is performed, the network DB 2 notifies the DB operation logic unit 11-2 of the update content of the network DB 2. For example, if the packet processing information is changed, the network DB 2 notifies the DB operation logic unit 11 - 1 of the change of the packet processing information via the DB interface unit 10 .

Based on the packet processing information, the DB operation logic unit 11-1 generates a processing instruction (information defining a packet processing method executed by the node 3) to be set in the node 3 of the network 4 and sets the processing instruction in the node 3 via the network control unit 12. Node 3.

For example, the DB operation logic unit 11-1 refers to path information in the packet processing information, and sets a processing instruction to each node 3 on the forwarding path corresponding to the path (Path) information. For example, the DB operation logic unit 11-1 sets, into each node 3, a processing instruction defining forwarding of a packet from a communication port corresponding to the forwarding path so that the packet is forwarded along the forwarding path corresponding to the path information.

As in the operations shown in FIGS. 4 to 6 above, by operating the network DB 2, the control device 1 can control packet processing in the network 4 in a centralized manner.

As described above, the control device 1 can control the network 4 by operating the network DB 2 with the DB operation command. Thus, the operator of the network 4 can program the control device 1 by incorporating the operating commands of the network DB 2 . The number of DB operation commands is much smaller than the number of commands required by the API or functions related thereto. Therefore, the operator of the network 4 can easily program the control device 1 without having to learn advanced knowledge and techniques.

<Second Exemplary Embodiment>

Next, a second exemplary embodiment of the present disclosure will be described. In the second exemplary embodiment, a configuration example of the network DB 2 and an example of a DB operation command will be described in detail.

7 to 9 show the configuration of the network DB 2 . The configuration of FIGS. 7 to 9 is an example, so the configuration of the network DB 2 is not limited to the configuration in FIGS. 7 to 9 .

Furthermore, in the second exemplary embodiment, the network DB2 is configured by key-value storage. However, the network DB 2 can be configured in a different manner from the key-value store.

FIG. 7 shows topology information stored in the network DB 2 . Topology information is configured by identification information (keys) related to nodes 3 in the network 4 and identification information (keys) related to links between nodes 3 . Each identification information (key) is associated with data (value).

For example, the data (value) corresponding to the identification information “/nodes” indicates the identifier (node ID) of the node 3 existing in the network 4 . "{1, 2, 3, 4, . . . }" in FIG. 7 indicates a node identifier list.

“[node_id]” of the identification information “/nodes/[node_id]” indicates an identifier of one of the nodes 3 existing in the network 4 . For example, the data (value) corresponding to the identification information "/nodes/[node_id]" represents information related to the identifier used when the control device 1 controls the node 3 in the network 4 or related to the manufacturer of the node 3 Information. The identifier used when the control device 1 controls the nodes 3 in the network 4 is different from the identifier associated with the above identification information "/nodes". In the OpenFlow protocol, an identifier used when the control device 1 controls the node 3 in the network 4 is called, for example, DPID (Data Path ID).

For example, data (value) corresponding to the identification information "/nodes/[node_id]/ports" indicates a list of identifiers of communication ports of the nodes 3 corresponding to "[node_id]". "{1, 2, 3, 4, . . . }" in FIG. 7 represents a list of identifiers of communication ports.

"[port_id]" of the identification information "/nodes/[node_id]/ports/[port_id]" indicates an identifier indicating one of the communication ports of the node 3 corresponding to "[node_id]". For example, the data (value) of the identification information "/nodes/[node_id]/ports/[port_id]" includes port status (such as link up status or link down status), communication bandwidth of the port, and the like.

For example, data (values) corresponding to the identification information “/links” represent identifiers of links between nodes 3 existing in the network 4 . "{1, 2, 3, 4, . . . }" in FIG. 7 indicates a list of link identifiers.

“[link_id]” of the identification information “/links/[link_id]” indicates an identifier of one of links between nodes existing in the network 4 . For example, data (values) corresponding to the identification information "/links/[link_id]" includes information on nodes at both ends of the link and information on communication ports of these nodes. For example, in FIG. 7, the data (value) includes an identifier of a packet source node in a link ("src_node_id") and an identifier of a packet destination node in a link ("dst_node_id"). In FIG. 7, "src_port_id" represents an identifier of a port corresponding to a link among the communication ports of the node corresponding to "src_node_id". In FIG. 7, "dst_port_id" represents an identifier of a port corresponding to a link among the communication ports of the node corresponding to "dst_node_id".

The network DB 2 manages the topology of the network 4 by using these database entries shown in FIG. 7 . By using DB operation commands and manipulating the entries shown in FIG. 7 , the DB operation logic unit 11 can manage and operate the topology of the network 4 .

FIG. 8 shows packet processing information stored in the network DB 2 . For example, the packet processing information includes: a matching condition (Filter filter), the matching condition is used to identify the packet corresponding to the packet processing information; a forwarding path (Path path), the forwarding path is for the packet matching the matching condition; and Predetermined processing (Action action), the predetermined processing will be applied to the packet matching the matching condition.

Data (value) corresponding to the identification information ("/flows") indicates an identifier of packet processing information. "{1, 2, 3, 4, . . . }" in FIG. 8 represents a list of identifiers of packet processing information.

"[flow_id]" of the identification information ("/flows/[flow_id]") indicates an identifier of one of packet processing information. For example, data (value) of the identification information "/flows/[flow_id]" includes a matching condition for identifying a packet corresponding to packet processing information corresponding to "[flow_id]". For example, when receiving a packet whose processing method is unknown, the DB operation logic unit 11 of the control device 1 uses a DB operation command to search the network DB 2 for packet processing information having a matching condition corresponding to the packet. The network DB 2 refers to information related to the packet (such as header information), and notifies the DB operation logic unit 11 of packet processing information having a matching condition corresponding to the packet. Based on the packet processing information provided, the DB operation logic unit 11 instructs the nodes 3 in the network 4 to process the packets.

There are cases where the network DB 2 does not have a DB operation command for referring to packet-related information (such as header information) and searching for packet processing information having a matching condition corresponding to the packet. In these cases, the DB operation logic unit 11 of the control device 1 can use a DB operation command to read necessary packet processing information from the network DB 2 and store the information in advance. In this way, the DB operation logic unit 11 can determine the corresponding packet processing information by simply referring to the information on the packet. Based on the determined packet processing information, the DB operation logic unit 11 gives instructions related to packet processing to the nodes 3 in the network 4 .

The data (values) corresponding to the identification information "/flows/[flow_id]" include: a forwarding path ("Path") for a packet matching the matching condition and a process to be performed on the packet matching the matching condition ("Action action"). The DB operation logic unit 11 notifies the node 3 in the network 4 of an instruction for forwarding the packet so that the packet is forwarded along the forwarding path defined in the packet processing information. Furthermore, if a process to be performed on the packet ("Action") exists, the DB operation logic unit 11 instructs the node 3 in the network 4 to perform the process.

FIG. 9 shows database entries related to packets forwarded to the control device 1 (packets whose processing method is undetermined). The network DB 2 can manage information on packets whose processing methods are not determined as database entries.

The data (value) corresponding to the identification information "/packets/in" indicates a list of identifiers of packets forwarded to the control device 1 (packets whose processing method is undetermined). For example, by using the DB operation command "push_tail" for adding values to the end of the list and the DB operation command "pop_head" for extracting values from the top of the list, the identifier list is used as a FIFO (first in first out) queue.

For example, the data (value) of the identification information "/packets/in/[packet_id]" includes: the identifier of the packet, the reception time of the packet, the identifier of the node 3 that has received the packet, and the communication port of the packet receiving node 3. identifier.

For example, if a packet is forwarded to the control device 1 , the DB operation logic unit 11 uses a DB operation command to store information related to the packet into the network DB 2 .

The data (value) corresponding to the identification information "/packets/out" indicates a list of identifiers of packets whose processing method has been determined and which need to be returned from the control device 1 to the network 4 . For example, among the packets stored in the queue corresponding to "/packets/in", the packet whose processing method has been determined is stored in the queue corresponding to "/packets/out". For example, data (value) corresponding to "/packets/out" is a list and used as a FIFO type queue.

For example, the data (value) corresponding to the identification information "/packets/out/[packet_id]" includes: an identifier of a node to which a packet is returned from the control device 1, an ID of a port to which a packet is returned among the communication ports of the node, The identifier and the data stored in the packet (ie the packet itself).

For example, the DB operation logic unit 11 operates the network DB 2 using a notification subscription command so that if a packet is stored in a queue corresponding to "/packets/out" and if the key "/packets/out" is operated, the DB operation logic is notified Unit 11. If the packet is stored in the queue (that is, if the entries corresponding to "/packets/out" and "/packets/out/[packet_id]" are updated), the network DB 2 notifies the DB operation logic unit 11 of the pair and "/ packets/out/[packet_id]" corresponding data update.

The packets stored in the identification information "/packets/out/" and the identification information "/packets/out/[packet_id]" may not correspond to the packets stored in the queue corresponding to "/packets/in". In this way, the control device 1 can efficiently output packets.

10 and 11 show DB operation commands used when the DB operation logic unit 11 operates the network DB 2 . As shown in FIGS. 10 and 11, by using a push command and a pop command, operations such as inserting data into and acquiring data from an arbitrary position of the list can be performed. Also, for example, the control device 1 uses a subscribe command to be notified of a change in an entry with a specific key in the database. Also, for example, use commands such as get (get), put (set), and delete (delete), etc. to get, set, and delete details about nodes, links, flows, and packets or nodes, links, flows, and The grouped value.

By using the DB operation commands shown in FIGS. 10 and 11 and operating the network DB 2 configured as shown in FIGS. 7 to 9, the DB operation logic unit 11 can control the network 4 in a centralized manner. Therefore, the operator can program the control device 1 by using the DB operation command and incorporating the operation command of the network DB 2 . The number of DB operation commands is much smaller than the number of commands required by the API used in ordinary programming or functions related thereto. Therefore, the operator can easily program the control device 1 compared to ordinary programming.

<Third Exemplary Embodiment>

Next, a third exemplary embodiment of the present disclosure will be described. The DB operation logic unit 11 can be realized by modules having various functions. In the third exemplary embodiment, an OpenFlow control unit 11A is arranged as the DB operation logic unit 11 .

Fig. 12 shows the configuration of a system according to a third exemplary embodiment. The OpenFlow control unit 11A has a function of controlling the network 4 based on the OpenFlow protocol. The third exemplary embodiment will be described assuming that the network 4 is configured by the nodes 3 compatible with the OpenFlow protocol. In the third exemplary embodiment, the network 4 will be called an OpenFlow network, if necessary.

FIG. 13 shows the configuration of the OpenFlow control unit 11A. The OpenFlow control unit 11A includes: a topology processing unit 110 , a flow processing unit 111 and a packet processing unit 112 .

The topology processing unit 110 uses DB operation commands to operate the network DB2 via the DB interface unit 10 . For example, the topology processing unit 110 operates on the network DB 2 to set topology information into the network DB 2 . Also, for example, the topology processing unit 110 operates on the network DB 2 to acquire topology information from the network DB 2 .

FIG. 14 shows an operation example in which the topology processing unit 110 operates on the network DB 2 . The topology processing unit 110 uses the command "push_tail(/nodes)" to add identifiers of nodes added to the OpenFlow network to the end of the entry list "/nodes". Furthermore, the topology processing unit 110 uses the command "put(/nodes/[node_id], <node_info>)" to add information corresponding to "<node_info>" (as a variable of the command) to the entry "/nodes/[node_id ]" ([node_id] is the identifier of the node added to the entry "/nodes"). For example, the topology processing unit 110 adds the information described in the first exemplary embodiment to the entry "/nodes/[node_id]".

The above series of operations can be collectively performed by using the command "push_tail(/nodes, <node_info>)" instead of the above command "push_tail(/nodes)". In this case, the execution of the command "put(/nodes/[node_id], <node_info>)" can be omitted.

The topology processing unit 110 uses the command "push_tail(/links)" to add identifiers of inter-node links added to the OpenFlow network to the end of the entry list "/links". Furthermore, the topology processing unit 110 uses the command "put(/links/[link_id], <link_info>)" to add information corresponding to "<link_info>" (as a variable of the command) to the entry "/links/[link_id ]" ([link_id] is the identifier of the link added to the entry "/links"). For example, the topology processing unit 110 adds the information described in the first exemplary embodiment to the entry "/links/[link_id]".

The above series of operations can be collectively performed by using the command "push_tail(/links, <link_info>)" instead of the above command "push_tail(/links)". In this case, the execution of the command "put(/links/[link_id], <link_info>)" can be omitted.

If a certain node or link is deleted from the OpenFlow network, the topology processing unit 110 uses the command "pop_at" to delete the identifier of the deleted node or link from the node or link list. If a certain node or link is deleted from the OpenFlow network, the topology processing unit 110 uses the command "delete" to delete the entry corresponding to the deleted node or link from the network DB 2 .

By using the command "pop_at", the above series of operations can be collectively performed. Therefore, the execution of the command "delete" can be omitted.

By using the command "get", the topology processing unit 110 acquires data (value) corresponding to the designated identification information (key).

The stream processing unit 111 operates the network DB 2 via the DB interface unit 10 using a DB operation command. For example, the stream processing unit 111 operates on the network DB 2 to set packet processing information into the network DB 2 . Also, for example, the stream processing unit 111 operates the network DB 2 to search the network DB 2 for packet processing information corresponding to a packet whose processing method is unknown.

FIG. 15 shows an operation example in which the stream processing unit 111 operates on the network DB 2 . If the control device 1 receives a packet whose processing method is unknown from the OpenFlow network, the stream processing unit 111 receives a request to search for a processing method for the packet from the packet processing unit 112 . For example, the packet processing unit 112 uses the command "get_matching_flow(<packet_info>)" to request the flow processing unit 111 to search for a processing method for the packet. "<packet_info>" which is an argument of the command is information on a packet whose processing method is unknown (for example, header information or the packet itself).

Based on the request from the packet processing unit 112, the flow processing unit 111 searches the network DB 2 for packet processing information having a matching condition corresponding to "<packet_info>". The flow processing unit 111 receives the identifier ("flow_id") of the acquired packet processing information from the network DB 2 . For example, based on the received identifier and by using the command "get(/flows/[flow_id])", the flow processing unit 111 acquires packet processing information. The stream processing unit 111 supplies the packet processing information to the packet processing unit 112 . If there is no such packet processing information matching the search condition, the stream processing unit 111 notifies the packet processing unit 112 of this effect.

If the network DB 2 does not have a command for searching packet processing information having a matching condition corresponding to "<packet_info>", the stream processing unit 111 can use a DB operation command to read necessary packet processing information from the network DB 2 and store that information in advance. In this way, the stream processing unit 11 can determine corresponding packet processing information by referring to information on packets.

If there is no corresponding packet processing information, the packet processing unit 112 adds the received packet to the network DB 2 using the command "push_tail(/packets/in, <packet_info>)".

If there is corresponding packet processing information, the packet processing unit 112 requests the stream processing unit 111 to process the packet.

Based on the acquired packet processing information, the stream processing unit 111 sets a packet processing operation (i.e., a packet processing rule) into the nodes 3 of the OpenFlow network, and at the same time causes the node 3 to communicate from an appropriate node of the node 3 based on the packet processing information The port outputs received packets.

For example, packet processing operations take information based on the format defined by the OpenFlow protocol and are used to cause the node 3 to process packets. The packet processing operations include identification conditions for identifying packets received by the node 3 and methods for processing packets matching the identification conditions. The stream processing unit 111 sets the packet processing operation into the node 3, and the node 3 stores the set packet processing operation in the memory. Node 3 searches the memory for a packet processing operation with an identification condition matching the received packet. If node 3 finds, based on the retrieved packet processing operations, a packet processing operation having an identification condition matching the received packet, node 3 processes the received packet (e.g., through the communication port specified by the packet processing operation forward packets).

For example, the stream processing unit 111 sets the identification condition into the packet processing operation based on the matching condition included in the packet processing information.

Based on the path information (Path path) included in the packet processing information, the stream processing unit 111 identifies a packet forwarding path in the OpenFlow network. The flow processing unit 111 notifies the node 3 on the packet forwarding path of the packet processing operation. Based on the packet processing operation, the flow processing unit 111 may instruct each node 3 on the forwarding path to forward the packet along the forwarding path corresponding to the packet processing information. That is, when the stream processing unit 111 instructs the node 3 to forward the packet, the packet processing operations set in each node 3 include a method for forwarding the packet through the communication port corresponding to the forwarding path.

If the packet processing information includes, for example, predetermined processing (Action) that needs to be performed on the packet, the stream processing unit 111 determines the node 3 that needs to perform the predetermined processing (Action). The stream processing unit 111 sets a packet processing operation in the determined node 3 in which processing determined as predetermined processing (for example, header rewriting or encapsulation/decapsulation) is defined.

For example, the stream processing unit 111 uses the command "subscribe to subscribe" so that when a predetermined update (update of packet processing information or link information) is performed in the network DB 2, the network DB 2 notifies the stream processing unit 111 of information related to the update . If the information specified by the command "subscribe" is updated, the network DB 2 notifies the stream processing unit 111 of the information using the command "publish". For example, based on information provided by using the command "publish", the stream processing unit 111 determines whether to change the packet processing operation already set in the node 3 in the OpenFlow network. If a change in the packet processing operation is necessary, the stream processing unit 111 generates a new packet processing operation and sets the new packet processing operation into the node 3 .

If, for example, a link or node in the OpenFlow network is deleted, the stream processing unit 111 deletes packet processing information corresponding to the deleted link or node from the network DB 2 . For example, the flow processing unit 111 deletes packet processing information including the deleted link or forwarding path on which the node is arranged from the network DB 2 .

The stream processing unit 111 uses the command "pop_at" to delete the identifier corresponding to the packet processing information that needs to be deleted from the list of packet processing information. The flow processing unit 111 deletes the entry ("/flows/[flow_id]") corresponding to the packet processing information using the command "delete". For example, the stream processing unit 111 generates new packet processing information replacing the deleted packet processing information, uses the command "push_at", and stores the generated packet processing information into the network DB 2 .

By using the command "pop_at", the above series of operations can be collectively performed. Therefore, the execution of the command "delete" can be omitted.

The packet processing unit 112 uses a DB operation command to operate the network DB2 via the DB interface unit 10 . For example, the packet processing unit 112 operates on the network DB 2 to set packet-related information into the network DB 2 .

FIG. 16 shows an operation example in which the packet processing unit 112 operates on the network DB 2 . For example, when receiving a packet whose processing method is unknown from the OpenFlow network, the packet processing unit 112 requests the flow processing unit 111 for a processing method corresponding to the packet. As described above, for example, the packet processing unit 112 uses the command "get_matching_flow(<packet_info>)" to request the flow processing unit 111 to search for a packet processing method.

If the stream processing unit 111 notifies the packet processing unit 112 that packet processing information corresponding to the packet does not exist, the packet processing unit 112 registers the information on the packet into the network DB 2 . For example, the packet processing unit 112 uses the command "push_tail(/packets/in)" to register the identifier of the packet to the end of the entry list "/packets/in". Furthermore, the packet processing unit 112 uses the command "put(/packets/in/[packet_id], <packet_info>)" to add information corresponding to "<packet_info>" which is a variable of the command to the entry "/packets/in /[packet_id]" ([packet_id] is the identifier of the packet added to the entry /packets/in).

The above series of operations can be collectively performed by using the command "push_tail(/packets/in, <node_info>)" instead of the above command "push_tail(/packets/in)". In this case, execution of the command "put(/packets/in/[node_id], <packet_info>)" can be omitted.

If the packet processing information corresponding to the packet added to the entry "/packets/in" is generated, the packet is added to the entry "/packets/out". For example, the packet processing unit 112 sets the network DB 2 in advance so that if the command "subscribe" is used and if the packet is added to the entry "/packets/out", the network DB 2 notifies the packet processing unit 112 of the entry "/packets/out". out''s updates. For example, the packet processing unit 112 uses the command "publish" so that if the entry "/packets/out" is updated, the packet processing unit 112 receives the changed key from the network DB 2 . In this way, the packet processing unit 112 can recognize the identifier of the packet that has been registered in the entry "/packets/out". For example, if the stream processing unit 111 sets a packet processing operation into a node in the OpenFlow network, the packet processing unit 112 transmits a packet corresponding to the received identifier to the OpenFlow network. Furthermore, the packet processing unit 112 deletes the received identifier from the entry "/packets/out" using the command "pop_at(/packets/out, <packet_id>)", and deletes the entry "/packets/out/ [packet_id]".

If the command "pop_head(/packets/out)" is used instead of the above command "pop_at", packet information can be received from the top of "/packets_out", and the entry "/packets/out/[packet_id]" can be deleted. Therefore, execution of the above command "delete" can be omitted.

17 to 20 are timing charts showing operations according to the third exemplary embodiment.

FIG. 17 shows the operations performed when a node is added to the network 4 . The topology processing unit 110 deletes addition of nodes to the OpenFlow network, and collects information on the added nodes.

For example, the topology processing unit 110 uses the command "push_tail(/nodes)" to add a node to the entry list "/nodes" in the network DB 2 . After adding the node to the list, the topology processing unit 110 receives “node_id” which is the identifier of the node in the network DB 2 from the network DB 2 .

For example, the topology processing unit 110 uses the command "put" to add information on nodes to entries in the network DB 2 . For example, the information on the added node is the information on the node and the information on the communication port of the node.

FIG. 18 shows the operations performed when a node is deleted from the network 4 . The topology processing unit 110 detects deletion of a node from the OpenFlow network, and collects information on the deleted node.

For example, the topology processing unit 110 uses the command "pop_at" to delete the identifier corresponding to the deleted node from the entry list "/nodes". Furthermore, the topology processing unit 110 uses the command "pop_at" to delete the identifier of the link related to the deleted node from the entry list "/links".

For example, the topology processing unit 110 uses the command "delete" to delete information on a node deleted from the OpenFlow network and information on a link related to the deleted node.

FIG. 19 shows operations performed when a link is added to the network 4 and operations performed when a link is deleted from the network 4 . The topology processing unit 110 deletes adding links to the OpenFlow network, and collects information on the added links.

For example, the topology processing unit 110 uses the command "push_tail" to add a link to the entry "/links". After adding the link to the entry list "/links", the topology processing unit 110 receives the identifier of the link added to the list from the network DB 2 . Based on the received identifier, the topology processing unit 110 uses the command "put" to register information on the link added to the OpenFlow network to the entry "/links/[link_id]".

The topology processing unit 110 detects deletion of a link from the OpenFlow network, and collects information on the deleted link.

For example, the topology processing unit 110 uses the command "delete" to delete the entry "/links/[link_id]" of the deleted link from the network DB 2 . Also, for example, the topology processing unit 110 uses the command "pop_at" to delete the identifier of the deleted link from the entry list "/links".

FIG. 20 is a diagram showing the operation of the OpenFlow control unit 11A controlling the OpenFlow network based on the packet processing information included in the network DB 2 . The packet processing unit 112 receives a packet ("packet_in" in FIG. 20 ) whose packet processing method is unknown from the OpenFlow network. For example, the packet processing unit 112 uses the command "get_matching_flow(<packet_info>)" to inquire of the flow processing unit 111 about packet processing information corresponding to the received packet.

For example, the flow processing unit 111 searches the network DB 2 for an entry ("/flows/[flow_id]") having a matching condition matching the packet information ("packet_info") included in "get_matching_flow (<packet_info>)".

For example, if the stream processing unit 111 finds packet processing information that matches the packet received by the packet processing unit 112, the stream processing unit 111 generates a packet processing operation (processing rule) to be set in the node 3 in the network 4, and transmits the packet via The packet processing unit 112 notifies the node 3 of the packet processing operation. In addition to notifying the node 3 of the packet processing operation, the packet processing unit 112 returns the packet received from the network 4 to the network 4 ("packet_out" in FIG. 20).

If the flow processing unit 111 does not find packet processing information matching the packet received by the packet processing unit 112, the flow processing unit 111 uses the command "push_tail" to add the packet received by the packet processing unit 112 to the entry "/packets/in" . After adding the packet to the entry "/packets/in", the stream processing unit 111 receives the identifier of the packet added to the entry ("packet_id" in FIG. 20 ) from the network DB 2 . Based on the received identifier, the stream processing unit 111 uses the command "put" to add information on the packet received by the packet processing unit 112 to the entry "/packets/in/[packet_id]".

<Fourth Exemplary Embodiment>

Next, a fourth exemplary embodiment of the present disclosure will be described. In the fourth exemplary embodiment, an example will be described in which the control device 1 operates the network DB 2 by using the visualization DB operation logic unit 11B.

In order to support the operator to manage the network 4 using the control device 1, the visualization DB operation logic unit 11B has the function of displaying at least a part of the information stored in the network DB 2 through an image so that the information can be grasped visually.

Fig. 21 shows a configuration according to a fourth exemplary embodiment. The visualization DB operation logic unit 11B in FIG. 21 acquires topology information from the network DB 2, and displays the connection relationship between nodes and links on the display device. For example, as shown in FIG. 22 , the visualization DB operation logic unit 11B displays the network topology by an image. The number assigned to each node represents the identifier of the node. In addition, the number assigned to each link represents the identifier of the link. When the network DB 2 notifies the visualization DB operation logic unit 11B of the change of topology information based on the notification, the visualization DB operation logic unit 11B acquires the node and link information from the network DB 2, and changes the connection relationship of the displayed nodes and links .

In this way, by connecting the visualization DB operation logic unit 11B in FIG. 21 to the network DB 2, the operator can acquire the configuration of the management target network as visualization information. Furthermore, the visualization DB operation logic unit 11B can display the packet processing information in the network DB 2 by an image. For example, the visualization DB operation logic unit 11B attaches path information (path) included in the entry "/flows/[flow_id]" to the topology displayed by the image. Fig. 23 shows packet processing information displayed by images. In FIG. 23, an entry "/flows/10" having an identifier "10" is displayed by an image. Information about the nodes and links through which the packet passes and information about the direction in which the packet is forwarded are displayed graphically.

As shown in FIG. 24, the visualization DB operation logic unit 11B displays the entries "/packets/in/[packet_id]" and "/packets/out/[packet_id]" by images.

<Fifth Exemplary Embodiment>

Next, a fifth exemplary embodiment of the present disclosure will be described. In the fifth exemplary embodiment, the control device 1 operates an instance of the network DB 2 by using the slice logic unit 11C.

Fig. 25 shows a configuration according to a fifth exemplary embodiment. The slicing logic unit 11C of FIG. 25 has a function of duplicating the network DB 2 to perform network slicing (virtual division). The slice logic unit 11C extends the state or change of a single network DB 2 to a plurality of network DBs 2A and 2B, and feeds back the state or change of the plurality of network DBs 2A and 2B to the original network DB2. In FIG. 25, the control device 1 includes two network DB interface units 10-1 and 10-2. However, a network DB interface unit may be arranged for each network DB. Alternatively, a single network DB interface unit may be connected to a plurality of network DBs 2 .

As described above, by connecting the slice logic unit 11C to an arbitrary network DB 2, each of a plurality of network operators (network users) can manage a slice network as a dedicated network. For example, an upper-level network operator can manage network DB 2, and a lower-level network operator licensed by the upper-level network operator can manage network DBs 2A and 2B.

<Sixth Exemplary Embodiment>

Next, a sixth exemplary embodiment of the present disclosure will be described. In the sixth exemplary embodiment, an example will be described in which the control device 1 operates the network DB 2 by using the shortest path logic unit 11D. The shortest path logic unit 11D has a function of calculating the shortest path among paths from a packet forwarding source to a destination in the network 4 .

Fig. 26 shows a configuration according to a sixth exemplary embodiment. Based on the topology information obtained from the network DB 2 and the host information read from the host information storage unit 21, the shortest path logic unit 11D in FIG. 26 calculates the shortest forwarding path between arbitrary hosts, and stores the shortest forwarding path to the shortest path storage unit 20.

When the network DB 2 notifies the shortest path logic unit 11D of an update of the topology-related entry based on the updated content, the shortest path logic unit 11D recalculates the shortest path and updates the shortest path storage unit 20 . For example, the shortest path logic unit 11D uses the command "subscribe" so that if the entry "/nodes" or "/links" is updated, the network DB 2 notifies the shortest path logic unit 11D of the updated information.

If the entry specified by the command "subscribe" is updated, the network DB 2 uses the command "publish" to notify the shortest path logic unit 11D of information on the entry. When receiving a notification from the network DB 2 about an update of the topology information, the shortest path logic unit 11D recalculates the shortest path corresponding to the new topology information, and stores the shortest path in the shortest path storage unit 20 . When recalculating the shortest path, the shortest path logic unit 11D may update the packet processing information. For example, path information ("path information") included in the packet processing information may be updated when the shortest path is recalculated. For example, the shortest path logic unit 11D uses the command "put" to store the updated packet processing information in the entry "/flows/[flow_id]" of the network DB 2 .

As described above, by connecting the control device 1 having the shortest path logic unit 11D in FIG. 26 to the network DB2, a function of calculating the shortest path and a function of updating packet processing information corresponding to the shortest path are added to the control device 1 middle.

<Seventh Exemplary Embodiment>

Next, a seventh exemplary embodiment of the present disclosure will be described. In the seventh exemplary embodiment, an example will be described in which the control apparatus 1 operates the network DB 2 by using the aggregation logic unit 11E. The aggregation logic unit 11E has the function of: aggregating multiple nodes and multiple links to abstract the network topology.

Fig. 27 shows a configuration according to a seventh exemplary embodiment. For example, the aggregation logic unit 11E in FIG. 27 abstracts the topology information stored in the network DB 2, and stores the abstracted topology information in the network DB 2C.

For example, the aggregation logic unit 11E operates on the networks DB2 and 2C via the DB interface units 10-3 and 10-4, respectively.

For example, FIG. 28 outlines an operation in which the aggregation logic unit 11E abstracts topology information in the network DB 2 and stores the abstracted topology information in the network DB 2C. For example, the aggregation logic unit 11E abstracts topology information according to operators' operations. In FIG. 28 , in the topology information stored in the network DB 2 , the aggregation logic unit 11E aggregates and abstracts nodes 1 and 2 , and aggregates and abstracts nodes 3 and 4 . A new node generated by aggregating nodes 1 and 2 corresponds to node 1 stored in the network DB 2C. A new node generated by aggregating nodes 3 and 4 corresponds to node 2 stored in the network DB 2C.

29 and 30 show entries in the network DBs 2 and 2C, respectively. The aggregation logic unit 11E aggregates the entries "/nodes/1" and "/nodes/2" in FIG. 29 . Furthermore, the aggregation logic unit 11E aggregates the entries "/nodes/3" and "/nodes/4" in FIG. 29 . Through these aggregation operations, the number of nodes to be stored in the network DB 2 is abstracted as "3".

For example, the aggregation logic unit 11E uses the command "push" to add three abstract nodes to the entry list "/nodes" in the network DB 2C. As shown in FIG. 30, the data (value) of the entry "/nodes" in the network DB 2C is updated to "{1, 2, 3}" by the aggregation operation. For example, the aggregation logic unit 11E uses the command "put" to add information on each abstract node to the entry "/nodes/[node_id]" in the network DB 2C. For example, the aggregation logic unit 11E registers the ID ("node ID" in FIGS. 29 and 30) used when the control device 1 controls the node into the entry "/nodes/[node_id]". Also, if the node registered in the entry "/nodes/[node_id]" is an abstract node, the aggregation logic unit 11E registers the ID ("original" in FIG. 30 ) before the node is abstracted in the entry "/nodes/[node_id]" nodes/[node_id]".

In FIG. 30, "node ID (a)" and "node ID (b)" are assigned as IDs of two nodes generated by abstraction. Also, a node corresponding to the entry "/nodes/5" in the network DB 2 is registered in the entry "/nodes/3" in the network DB 2C. Assign "node ID (c)" as the node ID associated with the entry "/nodes/3" in the network DB 2C.

For example, when a node is aggregated, the aggregation logic unit 11E also aggregates the corresponding link. For example, in FIGS. 29 and 30 , the aggregation logic unit 11E aggregates the links corresponding to "/links/2" and "/links/4" in FIG. 29 into "/links/1" in FIG. 30 . For example, the aggregation logic unit 11E uses the command "put" to store data (values) corresponding to "/links/2" and "/links/4" in FIG. 29 to the entry "/links/1" in the network DB 2C. "middle. In addition, the aggregation logic unit 11E does not register the link ("/links/1" in FIG. 29) (the aggregation of "/nodes/1" and "/nodes/2" in FIG. 29 is no longer necessary) to the network DB2C. For example, in FIG. 29, "{src_node: A, dst_node: B}" indicates a link for forwarding a packet from a node with node ID (A) to a node with node ID (B).

As mentioned above, the aggregation logic unit 11E can abstract the topology. That is, the operator can control and manage the target network based on the abstracted topology, and can easily manage the network.

<Eighth Exemplary Embodiment>

Next, an eighth exemplary embodiment of the present disclosure will be described. In the eighth exemplary embodiment, an example will be described in which the control device 1 operates the network DB 2 by using the integrated logic unit 11F. The integration logic unit 11F has a function of integrating topology information included in a plurality of network DBs.

Fig. 31 shows a configuration according to the eighth exemplary embodiment. For example, the integration logic unit 11F in FIG. 31 integrates topology information included in the network DBs 2D and 2E, and stores the integrated topology information into the network DB 2F.

Fig. 32 shows topology information stored in the network DB 2D and information stored in the network DB 2E. The network DB 2D includes topology information configured by three nodes (nodes 1-3) and three links (links 1-3). The network DB 2E includes topology information configured by three nodes (nodes 1-3) and three links (links 1-3).

FIG. 33 shows new topology information generated by integrating topology information in network DBs 2D and 2E.

As shown in FIGS. 32 and 33, by integrating two topologies, six nodes are stored in the network DB 2F. For example, the integrated logic unit 11F uses the command "push" to store the node list into the entry "/nodes". By causing the integration logic unit 11F to operate the network DB2F with the command "push", the list of integration nodes ("{1, 2, 3, 4, 5, 6}") is stored in the entry "/nodes". Also, for example, the integrated logic unit 11F uses the command "put" to store information on the node into the entry "/nodes/[node_id]".

As shown in FIGS. 32 and 33, by integrating the two topologies, seven links are stored in the network DB 2F. For example, the integrated logic unit 11F uses the command "push" to store the link list into the entry "/links". By causing the integrated logic unit 11F to operate the network DB2F with the command "push", a list of integrated nodes ("{1, 2, 3, 4, 5, 6, 7}") is stored in the entry "/links". Also, for example, the integrated logic unit 11F uses the command "put" to store link-related information into the entry "/links/[link_id]".

<Ninth Exemplary Embodiment>

Next, a ninth exemplary embodiment of the present disclosure will be described. The operator can manage the network DB 2 or the DB operation logic unit 11 (or the components 11A- 11F described in the third to eighth exemplary embodiments) by using the function of the component manager 30 . The component manager 30 will be described in the ninth exemplary embodiment.

Fig. 34 shows the configuration of a system according to a ninth exemplary embodiment. The operator manages the network DB 2 and the DB operation logic unit 11 by using the function of the component manager 30 . Furthermore, as shown in FIG. 34, even when the network DB 2 and the DB operation logic unit 11 are arranged in a plurality of servers (servers 200 to 400), the component manager 30 can integrally manage the network DB 2 and the DB operation logic Unit 11. In FIG. 34, the control apparatus 1 is configured by a network DB 2 and a DB operation logic unit 11 arranged in a plurality of servers.

FIG. 35 shows the configuration of the component manager 30 . In FIG. 35 , the component manager 30 includes: a component information storage unit 31 , a component management unit 32 , an external control interface unit 33 and a component control interface unit 34 .

The component information storage unit 31 stores the configuration and connection of the network DB described in the above exemplary embodiments and the DB operation logic unit 11 (such as the components 11A-11F described in the third exemplary embodiment to the eighth exemplary embodiment) relation.

The component control interface unit 34 has a function as an interface for connecting to the network DB 2, the DB operation logic unit 11, and the like. The component manager 30 accesses the network DB 2 and the DB operation logic unit 11 via the component control interface unit 34 .

The component management unit 32 has an activation and termination function 320 for creating and deleting the network DB 2 and starting and terminating the DB operation logic unit 11 in response to operations from the operator. The component management unit 32 has a connection function 321 for connecting components via the component control interface unit 34 in response to an operation from an operator. The component management unit 32 includes: an activity monitoring function 322 for monitoring whether the DB operation logic unit 11 is running properly. Furthermore, the component management unit 32 updates the content of the component information storage unit 31 based on an operation from the operator.

The processing management unit 9 in FIG. 34 is connected to the component control interface unit 34 . For example, if the DB operation logic unit 11 is configured on a plurality of servers (as shown in FIG. 34 ), the processing management unit 9 performs management operations (including starting, terminating, and monitoring on these servers based on instructions from the component management unit 32). The DB operation logic unit 11) operated on. Furthermore, as shown in FIG. 34, a plurality of DB operation logic units 11 may be connected to different networks such as an OpenFlow network and an MPLS (Multiprotocol Label Switching) network.

<Tenth Exemplary Embodiment>

Next, a tenth exemplary embodiment of the present disclosure will be described. FIG. 36 shows the configuration of a system according to a tenth exemplary embodiment of the present disclosure. Hereinafter, the user interface 40 in FIG. 36 is described with reference to the accompanying drawings.

The server 400 shown in FIG. 36 has a function of configuring the control device 1 based on the user interface 40 used by the operator.

The server (information processing apparatus) 400 includes: a display unit 401 and a management unit 402 . The display unit 401 has a function of displaying icons corresponding to the network DB 2 and the DB operation logic unit 11 (the icons are classified into a first icon corresponding to the network DB 2 and a second icon corresponding to the DB operation logic unit 11) on Functions on the user interface 40, such as on a screen displayed on a display. The management unit 402 has a function of configuring the control device 1 based on the connection relationship of the icons operated by the operator.

FIG. 37 shows a screen displayed by the display unit 401 . The screen of FIG. 37 has a layout including a template display area and a work area, the template display area displays the above network DB 2 and the DB operation logic unit 11 (such as the components 11A described in the third exemplary embodiment to the eighth exemplary embodiment) -11F) corresponds to the template icon.

For example, if the operator drags and drops a template corresponding to the necessary network DB2, DB operation logic unit 11, and shortest path logic unit 11D from the template display area in FIG. 37, the corresponding icon is displayed in the work area. If the operator connects the icons displayed in the work area, a connection line is displayed between the icons in the work area. For example, when the display unit 401 receives a display request from the operator, it displays information related to the network DB 2 or the DB operation logic unit 11 or the network topology generated by the visualization DB operation logic unit 11B in the object display area using a pop-up window or the like. details. For example, when the display unit 401 detects a click or the like (display request) on an icon in the work area, it is displayed in the object display area using a pop-up window or the like with the network DB 2 or the DB operation logic unit 11 or by the visualization DB operation logic unit 11B generates detailed information about the network topology.

FIG. 38 is a diagram showing that the operations performed via the user interface 40 and the configuration of the control device 1 configured by the management unit 402 are related to each other. The management unit 402 may be configured by the component manager 30 .

For example, the display unit 401 can display the operation result of the network DB 2 by the DB operation logic unit 11 . For example, if the icon corresponding to the DB operation logic unit 11 and the icon corresponding to the network DB 2 are connected to each other, the display unit 401 displays the operation result of the network DB 2 through the DB operation logic unit 11 .

38 shows that the icon TP1 (NW-DB; corresponding to the network DB 2), the icon TP2 (OF-NW; corresponding to the OpenFlow control unit 11A), and the icon TP3 (the shortest path; corresponding to the OpenFlow control unit 11A) have been selected from the template display area. corresponding to the shortest path logic unit 11D). These icons are arranged in the working area and connected to each other. In this way, the network DB 2 , the OpenFlow control unit 11A, and the shortest path logic unit 11D are added and connected to the control device 1 . A network 4 corresponding to the network DB 2 is controlled by the OpenFlow protocol, and shortest path control is performed on the network 4 .

FIG. 39 is a diagram showing that the icon TP4 (visualization; corresponding to the visualization DB operation logic unit 11B) in FIG. 38 is connected to the icon TP1 (NW-DB; corresponding to the network DB 2 ). In this way, a network topology display function using images or the like is added to this control device 1 .

FIG. 40 is a schematic diagram of the icon TP5 (aggregation; aggregation logic unit 11E) additionally connected to the icon TP1 (NW-DB), where the icon TP2 (OF-NW) is connected to the icon TP1 (NW-DB). The aggregation logic unit 11E corresponding to the icon TP5 (aggregation) aggregates and abstracts the topology information in the network DB, and stores the information in another network DB 2 . Icon TP5 (visualization) is connected to another network DB2. As shown in Figure 40, both complex network topologies and abstract network topologies can be displayed as images.

FIG. 41 is a schematic diagram of the icon TP6 (slice; corresponding to the slice logic unit 11C) additionally connected to the icon TP1 (NW-DB) and generating a logically divided network DB, wherein the icon TP2 (OF-NW) is connected to the icon TP1 (NW-DB). In this way, a single network can be sliced into multiple virtual networks. Furthermore, by connecting various icons in the template display area to icons representing these slice network DBs (NW-DB; Network DB), slice networks can be individually controlled and used.

Fig. 42 is a schematic diagram of icon TP7 (integrated; corresponding to integrated logic unit 11F) connected to a plurality of icons TP1 (NW-DB) and generating a network DB integrating these networks, wherein icon TP2 (OF-NW) is connected to icon TP1 (NW-DB). In this way, multiple networks can be controlled and used as a single network.

As described above, by using the user interface according to the present exemplary embodiment, the operator can customize the initial settings or functions of the network control device without advanced knowledge and technology. Furthermore, it is possible to allow the operator to set each network, refer to the entries of the network DB, and operate the entries via this user interface 40 . For example, it is preferable to allow the operator to modify setting values or add, change or delete items related to control (flow) operations by moving the cursor to fields in the object display area in FIG. 37 .

Although the exemplary embodiments of the present disclosure have been described, the present invention is not limited thereto. Various changes, substitutions or adjustments can be made without departing from the basic technical concept of the present invention. For example, the network configuration or component configuration in each drawing is only for facilitating understanding of the present invention. That is, the present invention is not limited to these configurations in the drawings.

Also, for example, network extraction logic is applicable in addition to the variation of the DB operation logic unit 11 described in the above exemplary embodiment. With this logic, by partially extracting the topology of a single network DB and extending the extracted topology to another network DB, the flow of the network DB can be extended to the flow of the original network DB. By connecting the two network DBs in this way, a function of partially controlling the network is added to the network control device. For example, another network operator may be allowed to operate only a part of the network, or the routing algorithm may only be changed for that part.

Furthermore, although the above exemplary embodiments have been described assuming control of a real network, a network control unit linked with a network emulator such as NS3 (Network Emulator Version 3) may be arranged. In this way, the network control device can control not only the real physical network, but also the network on the emulator. Thus, the network operator can test the operation or performance of the thus created network control device on an emulator before applying the control device to a real physical network.

Finally, preferred modes of the present invention will be outlined.

<first mode>

(See the information processing device in the first aspect above)

<second mode>

In the information processing apparatus in the first mode, the display unit displays control information stored in the database in response to a request on the first icon for displaying a state of the database.

<third mode>

In the information processing apparatus in the first mode or the second mode, according to connection of any one of the first icon and the second icon, the display unit displays The database operation command issued by the module corresponding to the icon is the result obtained by operating the control information.

<Fourth mode>

In the information processing apparatus in any one of the first mode to the third mode, according to the connection of the first icon and the second icon corresponding to a module performing display of the status of the network, the The display unit displays the status of the network.

<Fifth mode>

In the information processing apparatus of any one of the first mode to the fourth mode, the operation on the control information is performed in response to a common database operation command used by the plurality of modules.

<sixth mode>

In the information processing apparatus in any one of the first to fifth modes, the database includes first information on the topology of the network, and a method of processing packets in the network related secondary information.

<Seventh mode>

In the information processing device in any one of the first to sixth modes, the database includes third information for managing packets received by the control device from the network, and for managing The fourth information of the packet sent by the control device to the network.

<eighth mode>

In the information processing apparatus in any one of the first mode to the seventh mode, the second icon corresponds to a module executing at least one selected from the group consisting of: a communication terminal Path calculation, network topology management, network topology aggregation, network segmentation and network integration.

<Ninth mode>

(See the configuration method in the second aspect above)

<tenth mode>

In said compounding method in a ninth mode, control information stored in said database is displayed on said display in response to a request on said first icon for displaying a status of said database.

<Eleventh mode>

In the configuration method in the ninth mode or the tenth mode, according to the connection of any one of the first icon and the second icon, displaying on the display by responding to the connection with the second icon The database operation command issued by the module corresponding to the icon is the result obtained by operating the control information.

<Twelfth mode>

In the configuration method in any one of the ninth mode to the eleventh mode, according to the first icon and the second icon corresponding to a module performing display of the status of the network connection, the status of the network is displayed on the display.

<Thirteenth mode>

In the configuration method in any one of the ninth mode to the twelfth mode, an operation on the control information is performed in response to a common database operation command used by the plurality of modules.

<Fourteenth mode>

In the configuration method described in any one of the ninth mode to the thirteenth mode, the database includes first information related to the topology of the network, and a method of processing packets in the network related secondary information.

<fifteenth mode>

In the configuration method described in any one of the ninth mode to the fourteenth mode, the database includes third information for managing packets received by the control device from the network, and for managing The fourth information of the packet sent by the control device to the network.

<Sixteenth mode>

In the configuration method described in any one of the ninth mode to the fifteenth mode, the second icon corresponds to a module that executes at least one item selected from the group consisting of: a communication terminal Path calculation, network topology management, network topology aggregation, network segmentation and network integration.

<Seventeenth mode>

(see communication system in third aspect above)

<Eighteenth mode>

(See procedures in Section 4 above)

The entire disclosure of the above NPL is incorporated herein by reference. Modifications and adjustments of the exemplary embodiments and examples are possible within the scope of the entire disclosure of the present invention (including claims) and based on the basic technical concept of the present invention. Various combinations and selections of various disclosed elements (including elements in each of the claims, exemplary embodiments, examples, drawings, etc.) are possible within the scope of the claims of the present invention. That is, the present invention naturally includes various variations and modifications made by those skilled in the art based on the entire disclosure including claims and technical concepts. Numerical ranges are disclosed in this specification. However, even if the specification does not specifically disclose any numerical values or subranges included in the ranges, such numerical values and ranges should be deemed to have been expressly disclosed.

[List of Reference Signs]

1 control unit

2. 2A to 2F network database (network DB)

3 nodes

4 network

4A Management Network

9 Processing snap-ins

10. 10-1 to 10-6 DB interface unit

11, 11-1, 11-2 DB operation logic unit

12 Network Control Unit

11A OpenFlow Control Unit

11B visual DB operation logic unit

11C slice logic unit

11D shortest path logical unit

11E aggregate logic unit

11F integrated logic unit

20 shortest path storage units

21 host information storage unit

30 Component Manager (Configuration Snap-in)

31 Component information storage unit

32 Component Snap-ins

33 External Control Interface Unit

34 component control interface unit

40 user interface

100, 200, 300, 400 servers

110 topology processing unit

111 stream processing unit

112 packet processing unit

320 Start and stop functions

321 connection function

322 Activity monitoring function

401 display unit

402 snap-in

TP1 to TP6 icons

Claims (17)

1. An information processing device, the information processing device configures a control device for controlling the network, and the information processing device includes: a display unit that displays on a display a first icon corresponding to a database storing control information for controlling the network and a plurality of second icons, each of the plurality of second icons corresponding to one of a plurality of modules, each of the plurality of modules operates on the control information based on a predetermined algorithm; and a management unit, the management unit configures the control device, and the control device has the following function: according to the connection between the first icon and any one of the second icons, the A module is connected to the database, and operates the control information in response to a database operation command issued by the module, wherein the control means controls nodes included in the network based on the rewritten control information. 2. The information processing device according to claim 1, Wherein, according to the request for displaying the state of the database on the first icon, the display unit displays the control information stored in the database. 3. The information processing device according to claim 1 or 2, Wherein, according to the connection of any one of the first icon and the second icon, the display unit displays that the control is operated by responding to a database operation command issued by the module corresponding to the second icon. information obtained as a result. 4. The information processing device according to claim 1 or 2, Wherein, the display unit displays the status of the network according to the connection of the first icon and the second icon corresponding to the module performing the display of the status of the network. 5. The information processing device according to claim 1 or 2, Wherein, the operation on the control information is performed in response to a common database operation command used by the plurality of modules. 6. The information processing device according to claim 1 or 2, Wherein said database comprises first information related to the topology of said network, and second information related to a method of processing packets in said network. 7. The information processing device according to claim 1 or 2, Wherein, the database includes third information for managing packets received by the control device from the network, and fourth information for managing packets sent by the control device to the network. 8. The information processing device according to claim 1 or 2, Wherein, the second icon corresponds to a module that executes at least one item selected from the group consisting of: path calculation between communication terminals, management of network topology, aggregation of network topology, segmentation of network, and network topology integration. 9. A method for configuring a control device controlling a network, the configuration method comprising: displaying on the display a first icon corresponding to a database storing control information for controlling the network and a plurality of second icons, each of the plurality of second icons corresponding to one of the plurality of modules, so each of the plurality of modules operates on the control information based on a predetermined algorithm; and Configuring the control device, the control device has the following functions: according to the connection between the first icon and any one of the second icons, connect the module corresponding to the second icon to the database, and operating the control information in response to a database operation command issued by the module, wherein the control means controls nodes included in the network based on the rewritten control information. 10. The configuration method according to claim 9, comprising: Control information stored in the database is displayed on the display in response to a request to display the status of the database on the first icon. 11. The configuration method according to claim 9 or 10, comprising: According to the connection of any one of the first icon and the second icon, the control information is displayed on the display to operate the control by responding to a database operation command issued by a module corresponding to the second icon The result obtained. 12. The configuration method according to claim 9 or 10, comprising: The status of the network is displayed on the display according to the connection of the first icon and the second icon corresponding to a module performing display of the status of the network. 13. The configuration method according to claim 9 or 10, comprising: An operation on the control information is performed in response to a common database operation command used by the plurality of modules. 14. A configuration method according to claim 9 or 10, wherein the database comprises first information relating to the topology of the network and second information relating to the method of handling packets in the network. 15. The configuration method according to claim 9 or 10, wherein the database includes third information for managing packets received by the control device from the network, and for managing the packets received by the control device from the network. The fourth information of the packet sent by the network. 16. The configuration method according to claim 9 or 10, wherein the second icon corresponds to a module executing at least one selected from the group consisting of: path calculation between communication terminals, network Topology management, network topology aggregation, network segmentation and network integration. 17. A communication system comprising an information processing device configured to configure a control device for controlling a network, the information processing device comprising: a display unit that displays on a display a first icon corresponding to a database storing control information for controlling the network and a plurality of second icons, each of the plurality of second icons corresponding to one of a plurality of modules, each of the plurality of modules operates on the control information based on a predetermined algorithm; and a management unit, the management unit configures the control device, and the control device has the following function: according to the connection between the first icon and any one of the second icons, the A module is connected to the database and operates the control information in response to a database operation command issued by the module, wherein the control means controls nodes included in the network based on the rewritten control information.