Patent Grant
9794124
The present invention is based upon and claims the benefit of the priority of Japanese patent application No. 2009-233895 filed on Oct. 7, 2009, the disclosure of which is incorporated herein in its entirety by reference thereto.
The present invention relates to an information system, control server, virtual network management method, and program, and particularly to an information system, control server, virtual network management method, and program providing a virtual network.
Patent Document I discloses a virtual network constructing device that realizes end-to-end security for each service, security between services at a client, and scalability for a large-scale system. According to this document, when a client selects an available service in launcher software transmitted from a path control server after the client's authentication request has been accepted, a corresponding path constructing request is transmitted to the path control server. The path control server issues the client an instruction for connecting to a base router, and also issues the base router an instruction for connecting to the client. The document recites that an in-base VLAN can be dynamically constructed between the client and the base router as a result.
Patent Document 2 discloses a system for managing customers in a hierarchical manner. Further, Patent Document 3 discloses a peer-to-peer network capable of providing a new network topology.
Non-Patent Document 1 proposes a technology called OpenFlow. OpenFlow treats communication as an end-to-end flow, and performs path control, failure recovery, load balancing, and optimization for each flow. An OpenFlow switch that functions as a forwarding node operates according to a flow table appended or updated by an OpenFlow controller according to OpenFlow protocol. In the flow table, pairs of a packet matching rule that specify a packet and an action such as outputting the packet to a specific port, discarding it, or rewriting a header are registered as flow entries. When there is a corresponding entry, the OpenFlow switch processes a received packet according to an action written in the entry, and notifies the OpenFlow protocol of the reception of the packet when there is no corresponding entry.
The entire disclosures of Patent Documents 1 to 3 and Non-Patent Document 1 are incorporated herein in their entirety by reference thereto.
The following analysis is given by the present invention.
The technologies of Patent Documents 1 to 3 logically divide a network, however, they do not perform detailed path control by determining a policy for each flow. Further, a method such as source routing can be used to perform path control, but the net data amount a packet can contain gets reduced in this case.
Regarding this point, Non-Patent Document 1 proposes a configuration in which path control is performed by the OpenFlow switch operating based on the flow table that defines an action for each flow, but the document only discusses network management, access control, and construction of a virtual network by virtualizing the OpenFlow switch as concrete examples of applications of this configuration.
The present invention has been made in considering the above circumstances, and it is an object thereof to provide a configuration capable of configuring a virtual network by virtualizing a physical network and achieving finely tuned path control in the virtual network.
According to a first aspect of the present invention, there is provided an information system, comprising: a plurality of physical nodes that hold control information defining an operation corresponding to the characteristics of an input/output packet(s) and that perform processing on an input/out-put packet(s) according to the control information; a first storage unit that stores configuration information of a virtual network including a virtual node configured using at least one of the physical nodes; a second storage unit that stores virtual network identifying information identifying the virtual network from characteristics of an input packet; and a control server that identifies a physical node configuring a virtual network that handles a packet having a characteristic in common with a packet received by the physical node based on a request from the physical node and that updates control information for each of the physical nodes.
According to a second aspect of the present invention, there is provided a control server, connected to a plurality of physical nodes that hold control information defining an operation corresponding to characteristics of an input/output packet(s) and that perform processing on an input/output packet(s) according to the control information, comprising: a first storage unit that stores configuration information of a virtual network including a virtual node configured using at least one of the physical nodes; a second storage unit that stores virtual network identifying information identifying the virtual network from characteristics of an input packet; and a control unit that identifies a physical node(s) configuring a virtual network that handles a packet having a characteristic in common with a packet received by the physical node based on a request from the physical node and that updates control information for each of the physical nodes.
According to a third aspect of the present invention, there is provided a virtual network management method executed by a control server connected to a plurality of physical nodes that hold control information defining an operation corresponding to characteristics of an input/output packet(s) and that perform processing on an input/output packet(s) according to the control information. The virtual network management method comprises a step of having the control server identify a physical node(s) configuring a virtual network that handles a packet having a characteristic in common with a packet received by the physical node(s) based on a request from the physical node(s) by referring to a first storage unit that stores configuration information of a virtual network including a virtual node configured using at least one of the physical nodes and to a second storage unit that stores virtual network identifying information identifying the virtual network from the characteristics of an input packet; and a step of updating control information for each of the identified physical nodes. This method is tied to the control server, a specific machine connected to the physical nodes and updating the control information thereof.
According to a fourth aspect of the present invention, there is provided a program, executed by a computer configuring a control server connected to a plurality of physical nodes that hold control information defining an operation corresponding to characteristics of an input/output packet(s) and that perform processing on an input/output packet(s) according to the control information, having the computer execute a process of having the control server identify a physical node(s) configuring a virtual network that handles a packet having a characteristic in common with a packet received by the physical node(s) based on a request from the physical node(s) by referring to a first storage unit that stores configuration information of a virtual network including a virtual node(s) configured using at least one of the physical nodes and to a second storage unit that stores virtual network identifying information identifying the virtual network from the characteristics of an input packet; and a process of updating control information for each of the identified physical nodes. Note that this program may be stored in a storage medium readable by a computer. In other words, the present invention can be embodied as a computer program product.
According to the present invention, it becomes possible to perform path control according to the characteristics of a packet on a configured virtual network. Further, high-speed processing can be achieved since no inquiry to the control server is necessary after the control information has been updated and each physical node does not have to refer to a routing table.
First, an outline of the present invention will be given with reference to the drawings. As shown in
The control sever 20 comprises a first storage unit (virtual network configuration information storage unit) 202 that stores configuration information of a virtual network comprised of virtual nodes which are virtualized versions of the physical nodes 10; a second storage unit (virtual network identifying information storage unit) 203 that stores virtual network identifying information that identifies the virtual network from the characteristics of the input packet(s); and a control unit 210 that identifies a physical node(s) configuring a virtual network that handles a packet(s) having a characteristic in common with the packet(s) received by the physical node(s) and that updates control information for each of physical nodes 10 based on a request from the physical node 10 concerned.
The physical node 10 can be realized by a switch equivalent to the OpenFlow switch of Non-Patent Document 1 that operates according to the flow table or a router, and notifies the control server 20 that a packet not in the flow table is received upon reception of the packet (request for creating a flow entry; an arrow from the physical node 10 to the control unit 210 in
Upon receiving the request for creating a flow entry, the control server 20 refers to the second storage unit 203 and identifies a virtual network to which the packet concerned should belong from the characteristics (port number, physical node ID, and header information) of the input packet. Next, the control server 20 refers to the first storage unit 202, suitably performs forwarding processing on the received packet within the virtual network, identifies a physical node or nodes corresponding to the identified virtual network, and updates the control information of the identified physical node or nodes (arrows from the control unit 210 to the physical nodes 10 in
Further, the control server 20 can be realized by adding the functions relating to the virtual network described above to the OpenFlow controller of Non-Patent Document 1 as a base. Or it is also possible to realize the control server 20 by having another server that provides the functions relating to the virtual network described above work together with the OpenFlow controller of Non-Patent Document 1.
Next, a first exemplary embodiment of the present invention will be described in detail with reference to the drawings.
The physical nodes 10 are connected each other and it is configured by a switch or router that forwards a packet(s) sent/received to/from the external network 30. In the present exemplary embodiment, the physical node 10 is assumed to be an OpenFlow switch.
The control server 20 is connected to the physical nodes 10 via secure channels and instructs the physical nodes 10 to update the control information. In the present exemplary embodiment, the control server 20 is assumed to be a server that comprises a function as the OpenFlow controller communicating with the physical nodes 10 using the OpenFlow protocol.
The external node(s) 30 is configured by a server(s) that provides various services to a user terminal accessing from the external network. In the present exemplary embodiment, the external node 30 is assumed to be an Http (Hyper-Text Transfer Protocol) server.
In the example in
In the explanation below, it is assumed that the control server 20 constructs a virtual network configured by a layer 3 switch (L3SW), a firewall (FW), a load balancer (LB), and a layer 2 switch (L2SW) shown in
The virtual node emulation unit 211 performs processing as a virtual node using virtual objects having a class corresponding to the aforementioned L3SW, FW, LB, and L2SW stored in the virtual node object storage unit 201. For instance, each virtual object is identified by a virtual node table shown in
The setting of the virtual node shown in
The virtual network control unit 212 performs input/output of packet information from/to the virtual node emulation unit 211 according to an association between the configuration information of the virtual network stored in the virtual network configuration information storage unit 202 and the virtual network identifying information storage unit 203 and the real network thereof. Further, the virtual network control unit 212 temporarily stores the received packet in a packet cache 215 and creates conversion contents of a packet header to be instructed to a physical node to which the packet is ultimately outputted.
By providing as many the tables shown in
The virtual network control unit 212 supplies an input packet(s) to the virtual node emulation unit 211, obtains the processing result thereof, and then supplies a physical node that has received this packet and the port number thereof, and a physical node after physical-virtual conversion performed on the packet on which network processing has been performed by the virtual node emulation unit 211, and the output port number thereof, to the path control unit 213.
The path control unit 213 calculates a forwarding path for outputting the packet supplied to the physical node based on physical network topology information stored in the physical topology information storage unit 204 from the physical node after the physical-virtual conversion. For this path calculation, for instance, Dijkstra's shortest path algorithm can be used.
Further, the path control unit 213 stores the result of the path calculation in the shortest path information storage unit 205 as a cache for a predetermined period of time. When performing subsequent path calculations, the path control unit 213 refers to the shortest path stored in the shortest path information storage unit 205 and is able to omit the path calculation processing if the cache remains.
Further, the path control unit 213 stores a pair of the flow and the shortest path information in the set flow forwarding path information storage unit 206 as well. When performing subsequent path calculations, the path control unit 213 is able to use the path information stored in the set flow forwarding path information storage unit 206.
The shortest path information storage unit 205 and the set flow forwarding path information storage unit 206 can be omitted. Further, how much is stored in each path information can be suitably changed according to the purpose and the hardware specifications of this system.
The OpenFlow protocol processing unit 214 instructs each physical node 10 to update the flow table 12 according to the path information calculated by the path control unit 213 as described.
As described, network processing equivalent to the virtual network in the upper part of
Next, with reference to
As shown in
Here, it is assumed that this packet is the first packet and no entry corresponding to the received packet is registered in the flow table of the physical node #1. Therefore, the physical node #1 issues an inquiry with the port number (input port number) that received the packet and the packet to the control server 20, and requests the control server to generate and transmit a flow entry (step S002; packet receipt notification (Packet-In)).
Upon receiving the packet receipt notification (Packet-In), the OpenFlow protocol processing unit 214 of the control server 20 adds the source physical node ID (input physical node) of the packet receipt notification (Packet-In) and forwards the packet to the virtual network control unit 212 (step S003). Note that the physical node ID can be derived from the management switch table shown in
The virtual network control unit 212 stores the received packet in the packet cache 215 and performs virtual-physical conversion on the packet by referring to the virtual network identifying information illustrated in
Next, as shown in
The virtual network control unit 212 resolves the physical node ID that outputs the packet and the physical port ID thereof by performing a reverse lookup on the virtual network identifying information illustrated in
Next, the virtual network control unit 212 requests setting of a flow entry that includes the input physical node, the input port number, the header information, the resolved physical node ID and the physical port ID outputting the packet, and the header conversion contents.
Next, as shown in
The physical node #2 outputs a received packet from the designated port according to the instruction from the path control unit 213 (step S008). Further, at this time, the OpenFlow protocol processing unit 214 may have the physical node #2 execute an action of obtaining an IP DA (Internet Protocol Destination Address) from the header of the received packet, transmitting an ARP request to ports other than the port, that received the received packet, and obtaining a corresponding MAC DA.
Further, the OpenFlow protocol processing unit 214 creates a flow entry to each physical node corresponding to the specified shortest path and transmits the flow entries to the physical nodes #1 and #2 (flow entry adding request; FlowMod (Add)). At this time, the OpenFlow protocol processing unit 214 sends a flow entry defining an action of converting the header to the physical node #2 as well.
The physical nodes #1 and #2 add the flow entries to the flow tables 12 according to the instruction from the OpenFlow protocol processing unit 214 (step S009).
Then, as shown in
Similarly, since the set flow entry is detected in a search in the flow table 12 (step S103), the physical node #2 successively outputs the packets received from the physical node #1 from the designated port (step S104).
Although this is omitted in
In the exemplary embodiment described above, the explanation was given using an example in which a virtual router is provided as a virtual node, however, the firewall (FW) and the load balancer (LB) on the virtual network shown in
For instance, when the virtual node emulation unit 211 is operated as a firewall according to a firewall policy of performing filtering operation by referring to the header information of a particular layer, a function equivalent to the firewall on the virtual network can be realized by setting an action of having the physical node receive the packet outputted from the virtual router and drop a corresponding packet based on the result thereof.
Similarly, for instance, a function equivalent to the load balancer on the virtual network can be realized by setting an action of supplying an output from the firewall to the virtual node emulation unit 211 that operates according to a predetermined load balance policy and switching the destination of the packet based on the result thereof.
The exemplary embodiment of the present invention has been described above, however, the present invention is not limited to the above exemplary embodiment and further modifications, replacements, and adjustments can be added within the scope of the basic technological concept of the present invention. For instance, the OpenFlow switch is used as the physical node and the OpenFlow protocol is used in the communication between the physical node and the control server in the exemplary embodiment described above, however, the present invention is not limited to the example above and any switch or protocol having the same functions can be used. For instance, the physical node can be realized by a router on an IP network or an MPLS switch on an MPLS (Multi-Protocol Label Switching) network, in addition to the OpenFlow switch.
It should be noted that within the entire disclosure (including the claims) and based on the fundamental technical concept, modifications and/or adjustment of the disclosed exemplary embodiments or examples may be done. Also various combination and selection of the various disclosed elements may be done within the scope of the claims of the present invention. That is, variations or modifications that may be done by the person of ordinary skill in the art based on the entire disclosure and technical concept including the claims may be included.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2009-233895 | Oct 2009 | JP | national |
The Present application is a Continuation application of U.S. patent application Ser. No. 13/500,564, filed on Apr. 5, 2012.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7133407 | Jinzaki et al. | Nov 2006 | B2 |
| 7286535 | Ishikawa et al. | Oct 2007 | B2 |
| 7339929 | Zelig et al. | Mar 2008 | B2 |
| 7545829 | Shimazaki et al. | Jun 2009 | B2 |
| 7684382 | Ishii et al. | Mar 2010 | B2 |
| 7773600 | Ishikawa et al. | Aug 2010 | B2 |
| 20010016914 | Tabata | Aug 2001 | A1 |
| 20030037165 | Shinomiya | Feb 2003 | A1 |
| 20030162499 | Jonsson | Aug 2003 | A1 |
| 20030169747 | Wang | Sep 2003 | A1 |
| 20030189932 | Ishikawa et al. | Oct 2003 | A1 |
| 20040059831 | Chu | Mar 2004 | A1 |
| 20040210623 | Hydrie et al. | Oct 2004 | A1 |
| 20040215630 | Parekh et al. | Oct 2004 | A1 |
| 20060029087 | Ooi | Feb 2006 | A1 |
| 20060041580 | Ozdemir et al. | Feb 2006 | A1 |
| 20060056384 | Ishii et al. | Mar 2006 | A1 |
| 20070153700 | Spalink et al. | Jul 2007 | A1 |
| 20080037546 | Ishikawa et al. | Feb 2008 | A1 |
| 20080307519 | Curcio et al. | Dec 2008 | A1 |
| 20090138577 | Casado et al. | May 2009 | A1 |
| 20100107162 | Edwards | Apr 2010 | A1 |
| 20100169880 | Haviv et al. | Jul 2010 | A1 |
| 20100257263 | Casado | Oct 2010 | A1 |
| 20100293544 | Wilson et al. | Nov 2010 | A1 |
| 20110176549 | Wu et al. | Jul 2011 | A1 |
| 20120257496 | Lattmann et al. | Oct 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 1 164 754 | Dec 2001 | EP |
| 2002-077266 | Mar 2002 | JP |
| 2002-252631 | Sep 2002 | JP |
| 2002-325090 | Nov 2002 | JP |
| 2003-023444 | Jan 2003 | JP |
| 2003-304278 | Oct 2003 | JP |
| 2003-318949 | Nov 2003 | JP |
| 2004-272905 | Sep 2004 | JP |
| 2005-051648 | Feb 2005 | JP |
| 2006-086889 | Mar 2006 | JP |
| 2007-525728 | Sep 2007 | JP |
| 2008-306725 | Dec 2008 | JP |
| 2009-135805 | Jun 2009 | JP |
| Entry |
|---|
| Japanese Office Action dated May 8, 2015 with a partial English translation. |
| Kazuto ASO, “A Virtual Router that Changes IP Services, a Configuration of user Environment for each user, which is Implemented in Various Product by Various Vender”, Nikkei Communication, Nikkei BP, Apr. 15, 2002, No. 364, p. 78-80. |
| Japanese Office Action dated Dec. 2, 2014 with a partial English translation. |
| International Search Report in PCT/JP2010/067640 dated Jan. 18, 2011(English Translation Thereof). |
| McKeown, Nick et al., “OpenFlow: Enabling Innovation in Campus Networks,” [online], searched on Jul. 17, 2009, Internet < URL : http://www.openflowswitch.org//documents/openflow-wplatest.pdf>. |
| European Search Report dated Mar. 6, 2013. |
| Peter Sjodin, et al., “Network Visualization Based on Flows”, Jun. 9, 2009 (Jun. 9, 2009), pp. 1-17, XP055053941, Terena Networking Conference 2009 Retrieved from the Internet: URL:http://www.fp7-federica.eu/documents/FEDERICA Sjodin pre mala ga—062009. pdf [retrieved on 2013-02-191]. |
| Farrel Old Dog Consulting J-P Vasseur Cisco Systems A et al., “A Path Computation Element (PCE)-Based Architecture; rfc4655.txt”, Aug. 1, 2006, Aug. 1, 2006 (Aug. 1, 2006), XP015047407, ISSN: 0000-0003. |
| Mehrdad Dianati et al., “Enabling Tussle-Agile Inter-networking Architectures by Underlay Virtualisation”, Sep. 1, 2009 (Sep. 1, 2009), Future Internet—FIS 2009, Springer Berlin Heidelberg, Berlin, Heidelberg, pp. 81-95, XP019148359, ISBN: 978-3-642-14955-9. |
| Japanese Office Action dated Sep. 29, 2015, with an English translation. |
| Saurav Das, et al., “Simple Unified Control for Packet and Circuit Networks”, IEEE/LEOS Summer Tropical Meeting, 2009 (LEOSST'09), pp. 147-148, Jul. 2009, IEEE, URL:http://ieeexplore.ieee.org/xpls/abs—all.jsp?arnumber=5226211. |
| Nick Mckeown, “Software-defined Networking”, Apr. 2009, URL://www.cs.rutgers.edu/˜badri/552dir/papers/intro/nick09.pdf. |
| Decision on Appeal, Trial Case No. Fufuku-2015-4314, Appeal Against an Examiner's Decision of Rejection to Application No. 2014-043134), dated May 9, 2017, pp. 1-25. |
| OpenFlow Switch Specification Version 0.9.0 (Wire Protocol 0×98), Jul. 20, 2009, pp. 1-36. |
| OpenFlow Switch Specification Obtained http://www.openflowswitch.org (last accessed on Jun. 26, 2017). |
| Number | Date | Country | |
|---|---|---|---|
| 20150350026 A1 | Dec 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13500564 | US | |
| Child | 14825406 | US |
