JP2018093245A - Network system, controller, control method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a network system which can avoid a collision of traffic processing rules between virtual networks in advance.SOLUTION: A network system comprises: physical nodes; a first controller; and second controllers. The physical nodes process, based on a processing rule to handle communication traffics, a communication traffic identified by an identification condition included in the processing rule. The first controller uses the physical nodes to construct a plurality of virtual networks. The second controllers are assigned to the plurality of virtual networks. The first controller assigns, based on a predetermined condition, the plurality of virtual networks sets of identifiers which can be used as an identification condition, respectively, and notifies the second controllers of the sets of identifiers assigned thereto.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a network system, a control device, a control method, and a program, and more particularly, to a network system, a control device, a control method, and a program in a network configured by devices that transfer packets according to instructions from the control device.

  As shown in Non-Patent Documents 1 and 2, in recent years, a technique called OpenFlow has been proposed. OpenFlow captures communication as an end-to-end flow and performs path control, failure recovery, load balancing, and optimization on a per-flow basis. The OpenFlow switch that functions as a forwarding node includes a secure channel for communication with the OpenFlow controller, and operates according to a flow table that is appropriately added or rewritten from the OpenFlow controller. In the flow table, for each flow, a set of a rule (FlowKey; matching key) that matches a packet header, an action (Action) that defines the processing content, and flow statistical information (Stats) is defined.

  For example, when the OpenFlow switch receives the first packet (first packet), the OpenFlow switch searches the flow table for an entry having a rule (FlowKey) that matches the header information of the received packet. When an entry that matches the received packet is found as a result of the search, the OpenFlow switch performs the processing content described in the action field of the entry on the received packet. On the other hand, if no entry matching the received packet is found as a result of the search, the OpenFlow switch forwards the received packet to the OpenFlow controller via the secure channel, and the source / destination of the received packet. To request the determination of the route of the packet based on the above, receive the flow entry that realizes this, and update the flow table.

  As described above, the OpenFlow switch determines a packet processing method according to the flow entry setting from the OpenFlow controller. In particular, OUTPUT that outputs a packet to a specified interface is frequently used as a processing method, but the port specified at this time is not limited to a physical interface.

  As described above, OpenFlow is realized by defining traffic control as a set of processing rules defined by the match condition by controlling the OpenFlow switch by the OpenFlow controller.

  In addition, a technique for virtualizing a network configured using OpenFlow and responding to various needs has been proposed.

  Non-Patent Document 3 discloses a slicing technique for performing traffic control by a plurality of open flow controllers, and enables a plurality of operators to independently operate a common open flow network. In Non-Patent Document 3, a special OpenFlow controller called FlowVisor makes it possible to control one OpenFlow switch by multiple policies by mediating between one OpenFlow switch and multiple OpenFlow controllers. ing. In FlowVisor, identification information of traffic to be accommodated by each OpenFlow controller is registered, and processing rule requests from the OpenFlow switch are distributed according to the information, and exclusive control of processing rules instructed by the OpenFlow controller is performed. This avoids conflicts between policies. This technology makes it possible to virtually cut out a plurality of networks from a common OpenFlow network and provide them to the user.

  Patent Document 1 discloses a technique for reducing the control load of an OpenFlow controller, and describes a technique for hierarchizing an OpenFlow network. In Patent Document 1, when one or more OpenFlow networks exist, upper OpenFlow controllers (hereinafter referred to as upper controllers) that further control each OpenFlow controller (hereinafter referred to as “lower controller”) that controls the physical OpenFlow network. Is described). Each subordinate controller notifies the host controller of the network it controls as a single virtual switch, and realizes layering of the network by receiving flow control from the host controller. As shown in FIG.

  Non-Patent Document 4 discloses an architecture applied to an OpenFlow network by combining a plurality of virtualization technologies including slicing and hierarchization described in Non-Patent Document 3 and Patent Document 1. Non-Patent Document 4 defines Aggregator (contraction function), Slicer (cutout function), and Fedatorator (combining function) as components that perform network virtualization, and these are applied to the network recursively. We propose an architecture that converts and controls a network composed of typical OpenFlow switches into various configurations.

  Non-Patent Document 5 discloses a technique for realizing the architecture described in Non-Patent Document 4 on other network control technologies such as VXLAN (Virtual eXtensible Local Area Network) as well as an open flow network. Yes.

  Further, a traffic processing rule verifying means that becomes a problem when the above-described virtualization technology is applied to a network has been proposed.

  Non-Patent Document 6 discloses a technique for verifying that target traffic is transferred as specified by a traffic processing rule set in an OpenFlow network. In Non-Patent Document 6, a set of packet headers corresponding to a traffic identification condition in a traffic processing rule is geometrically expressed as an identifier space. Then, it is verified whether the traffic control as expected can be realized by checking whether the identifier space of the traffic processing rule set in the OpenFlow switch on the transfer path matches or has a common partial space. In addition, it is verified that traffic control intended for the entire network is performed by simultaneously checking whether or not the identifier space conflicts with another traffic processing rule that has already been set.

  Non-Patent Document 7 describes a technique for verifying whether a traffic processing rule set in a virtual network is set as intended or whether a collision with a traffic processing rule in another virtual network occurs. The effectiveness of the traffic processing rule is expressed by expressing the traffic identification conditions that can be used in the traffic processing rule as a binary decision tree, and checking whether the traffic identification conditions in the configured traffic processing rule deviate from the usable range. Verification is in progress.

Special table 2013-522934 gazette

Nick McKeown and 7 others, “OpenFlow: Enabling Innovation in Campus Networks”, [online], [searched September 17, 2014], Internet <URL: http://archive.openflow.org/documents/openflow-wp -latest.pdf> "OpenFlow Switch Specification" Version 1.0.0. (Wire Protocol 0x01) ", [online], [searched September 17, 2014], Internet <URL: https://www.opennetworking.org/images/stories/ downloads / sdn-resources / onf-specifications / openflow / openflow-spec-v1.0.0.pdf> Sherwood, Rob, et al. "Carving research slices out of your production networks with OpenFlow." ACM SIGCOMM Computer Communication Review 40.1 (2010): 129-130. Toshio Koide, Yuta Hamada, and Hideyuki Shimonishi. "A network abstraction model that simplifies the creation of SDN controllers (Special Features on SDN to Advance ICT Systems)-(Latest Technology Supporting NEC SDN Solutions)." NEC Technical Report 66.2 (2014): 32-35. Yohei Iizawa, Shoji Morimoto, and Hideyuki Shimonishi. "Multi-layer abstraction technology to realize heterogeneous network integrated control platform (Special feature on SDN to advance ICT system)-(Latest technology supporting NEC SDN Solutions)." NEC Technical Review 66.2 (2014): 44-47. Kazemian, Peyman, George Varghese, and Nick McKeown. "Header Space Analysis: Static Checking for Networks." NSDI. 2012. Al-Shaer, Ehab, and Saeed Al-Haj. "FlowChecker: Configuration analysis and verification of federated OpenFlow infrastructures." Proceedings of the 3rd ACM workshop on Assurable and usable security configuration. ACM, 2010.

  Each disclosure of the above prior art document is incorporated herein by reference. The following analysis was made by the present inventors.

  As described above, by using a network control technique such as OpenFlow and virtualizing the network, it is possible to set a traffic processing rule according to requests from a plurality of users. However, these traffic processing rules will eventually be set to a common physical network, but if the processing rules of each virtual network are inconsistent, traffic may be subject to unintended control. Conceivable. When the network is virtualized in a complex manner as in Non-Patent Document 4, since the traffic processing rules that are set are diversified, the probability of inconsistencies between the processing rules increases.

  By using the technique described in Non-Patent Document 3, it is possible to restrict the control to control only the traffic type permitted for each user. When setting of a traffic processing rule that deviates from the permitted range is instructed, exclusive control of the traffic processing rule is realized by correcting or rejecting it before setting the physical network. However, the technique described in Non-Patent Document 3 does not have a means for verifying the traffic type information itself, and if the available traffic type settings for each user collide, the intended control cannot be executed. Further, since exclusive control of traffic processing rules is performed in response to transmission of setting instructions from the OpenFlow controller, it is not possible to calculate processing rules that do not collide with other rules in advance.

  By using the techniques described in Non-Patent Documents 6 and 7, it is possible to verify whether the set traffic processing rule does not cause a contradiction between virtual networks or whether the intended control can be realized. However, similarly to Non-Patent Document 3, this technology cannot perform verification of registration information and pre-calculation of processing rules for avoiding a collision.

  In view of the above, an object of the present invention is to provide usable traffic identification condition calculation and information disclosure means necessary for avoiding collision of traffic processing rules between virtual networks in advance.

  According to a first aspect of the present invention, based on a processing rule for processing communication traffic, a physical node that processes communication traffic identified by an identification condition included in the processing rule, and the physical node are used. A first control device that constructs a plurality of virtual networks and a second control device that is assigned to each of the plurality of virtual networks, the first control device based on a predetermined condition, A network system is provided in which a set of identifiers that can be used as the identification condition is assigned to each of the plurality of virtual networks, and the assigned set of identifiers is notified to the second control device.

  According to a second aspect of the present invention, there is provided a control device that controls a physical node that processes communication traffic identified by an identification condition included in the processing rule based on a processing rule for processing communication traffic. Constructing a plurality of virtual networks using the physical nodes, assigning a set of identifiers usable as the identification condition to each of the plurality of virtual networks based on a predetermined condition, and assigning the assigned identifier set Is provided to a second control device assigned to each of the plurality of virtual networks.

  According to a third aspect of the present invention, there is provided a physical node control method for processing communication traffic identified by an identification condition included in a processing rule based on a processing rule for processing communication traffic, Constructing a plurality of virtual networks using the physical node, assigning a set of identifiers usable as the identification conditions to each of the plurality of virtual networks based on a predetermined condition, and the assigned identifiers A second control device assigned to each of the plurality of virtual networks is provided.

According to the fourth aspect of the present invention, it is mounted on a control device that controls a physical node that processes communication traffic identified by an identification condition included in the processing rule, based on a processing rule for processing communication traffic. A program to be executed by a computer, wherein a plurality of virtual networks is processed based on a process for constructing a plurality of virtual networks using the physical nodes and based on a predetermined condition There is provided a program that executes a process of assigning each of the identifiers and a process of notifying a set of the assigned identifiers to a second control device assigned to each of the plurality of virtual networks.
This program can be recorded on a computer-readable storage medium. The storage medium may be non-transient such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, or the like. The present invention can also be embodied as a computer program product.

  According to each aspect of the present invention, a network system, a control device, a control method, and a program that contribute to avoiding collision of traffic processing rules between virtual networks in advance are provided.

It is a figure for demonstrating the outline | summary of one Embodiment. 1 shows an example of a system configuration in a first embodiment. The structural example of the control apparatus 10 in 1st embodiment is shown. The structural example of the control apparatus 20 in 1st embodiment is shown. The structural example of the control apparatus 30 in 1st embodiment is shown. The structural example of the control apparatus 40 in 1st embodiment is shown. The identifier space calculated by the control apparatus 10-1 in 1st embodiment is illustrated. The accommodation traffic conditions in 1st embodiment are illustrated. The duplication of the accommodation traffic conditions in the first embodiment is illustrated. The identifier space calculated by the control apparatus 20 in 1st embodiment is illustrated. In the first embodiment, two network identifier spaces disclosed in the control device 30 are illustrated. In the first embodiment, an identifier space calculated by the control device 30 is illustrated. In the second embodiment, an identifier space calculated by the control device 20 is illustrated. In the second embodiment, an identifier space modified by the control device 20 is illustrated. In the second embodiment, an identifier space modified by the control device 30 is illustrated. The structure of the control apparatus 10 in 3rd embodiment is illustrated. The structure of the control apparatus 20 in 3rd embodiment is illustrated. The structure of the control apparatus 30 in 3rd embodiment is illustrated. In 3rd Embodiment, the identifier space disclosed by the control apparatus 40-2 is illustrated. In 3rd Embodiment, the traffic identification conditions contained in the traffic processing rule set by the control apparatus 40-2 are illustrated. In the third embodiment, the traffic identification condition corrected by the control device 30 is illustrated. In the fourth embodiment, an identifier space disclosed in the control device 30 is illustrated. In 4th Embodiment, the identifier space calculated by the control apparatus 30 is illustrated.

  First, an outline of one embodiment will be described. Note that the reference numerals of the drawings attached to the outline are attached to the respective elements for convenience as an example for facilitating understanding, and the description of the outline is not intended to be any limitation.

  Referring to FIG. 1, the network system according to an embodiment includes a physical node 100, a first control device 101, and a second control device 102. Based on a processing rule for processing communication traffic, the physical node 100 processes communication traffic identified by the identification condition included in the processing rule. The first control apparatus 101 constructs a plurality of virtual networks using the physical node 100. The second control device 102 is assigned to each of the plurality of virtual networks. The first control device 101 assigns a set of identifiers that can be used as identification conditions to each of the plurality of virtual networks based on a predetermined condition, and notifies the second control device 102 of the set of assigned identifiers.

  In the network system of FIG. 1, the first control apparatus 101 constructs a plurality of virtual networks and assigns a set of identifiers (identifier space described later) that can be used in each virtual network. The set of assigned identifiers is provided to the second control apparatus 102 that controls each virtual network. The second control apparatus 102 is instructed by a traffic control instruction (flow setting instruction) so as to conform to the provided set of identifiers or from an upper apparatus of the second control apparatus 102 that does not conform to the set of identifiers. Rejecting the traffic control instruction can avoid collision of identification conditions.

  The network system according to an embodiment calculates a traffic processing rule by calculating a traffic identification condition allowed in each virtual network to prevent collision with other virtual networks when the network is virtualized in various ways. Can be provided.

  Hereinafter, specific embodiments will be described in more detail with reference to the drawings. In addition, in each embodiment, the same code | symbol is attached | subjected to the same component and the description is abbreviate | omitted.

[First form]

  FIG. 2 is a diagram illustrating a configuration example of the entire system according to the first embodiment. Referring to FIG. 2, a network 3-1 composed of nodes 1-1 to 1-3 and a network 3-2 composed of nodes 1-4 to 1-6 are connected to each other. Further, the terminal 2 is connected to each of the nodes 1-1, 1-2, 1-5, and 1-6. The network 3-1 is directly managed by the control device 10-1, and the network 3-2 is directly managed by the control device 10-2.

  The control devices 10-1 and 10-2 provide information on the network managed by the control devices 10-1 and 10-2 to other control devices, and enter control. The control device 20 constructs two virtual networks from the information of the control device 10-1 and provides virtual network information to the control device 40-1 and the control device 30.

  The control device 20 transfers the control instruction from the control device 40-1 and the control instruction from the control device 30 to the control device 10-1, and also controls the information from the control device 10-1 to the control device 40-1, It has a function of distributing to the control device 30.

  The control device 30 combines the network information from the control device 10-2 and the control device 20, and provides a single network information to the control device 40-2. The control device 30 has a function of dividing a control instruction from the control device 40-2 and distributing it to the control device 10-2 and the control device 20.

  The control device 40 calculates a flow to be set for the corresponding network from the received network information, and transmits the calculated flow to the lower control device.

  Next, configuration examples of the control devices 10, 20, 30, and 40 will be described with reference to FIGS.

  Referring to FIG. 3, the control device 10 includes a node communication unit 11, a node control message processing unit 12, a processing rule calculation unit 13, a network information management unit 14, an identifier space calculation unit 15, and an inter-control device message. The processing unit 16 and the control device communication unit 17 are configured.

  The node communication unit 11 connects to the node 1 and performs communication.

  The node control message processing unit 12 analyzes the information received from the node 1, converts the function distributed to other functional units, and the information from the other functional units into a control message for the node 1, and sends it to the node communication unit 11. Send.

  The processing rule calculation unit 13 calculates a processing rule for instructing setting to the node 1 based on information from the network information management unit 14 and transmits the processing rule to the node control message processing unit 12.

  The network information management unit 14 manages network information managed by the control device 10, updates information based on information from the node 1 and information from the control device 20 or 30, and updates information to the control devices 20 and 30. And notify node 1.

  The identifier space calculation unit 15 calculates and holds an identifier space that can be used as a traffic identification condition of a flow in the network managed by the control device 10 based on the network information held by the network information management unit 14. Notify the network information management unit 14.

  The inter-control device message processing unit 16 analyzes a function for creating a message for transmitting information to the control devices 20 and 30 and information received from the control devices 20 and 30 based on a request from another functional unit. It has a function to distribute to the functional part.

  The control device communication unit 17 manages communication with the control devices 20 and 30.

  In addition, the processing rule calculation unit 13 includes a flow database (flow DB; Data Base) 131 that stores the processing rule that has been calculated by itself and the flow information that is the basis of the calculation. The network information management unit 14 includes a network database (network DB) 141 that stores network information managed by the control device 10, that is, network topology, node 1 information, flow information to be set in the network, and the like. The identifier space calculation unit 15 includes an identifier space database (identifier space DB) 151 that stores the identifier space calculated by itself.

  Referring to FIG. 4, the control device 20 includes a network slice unit 21, an identifier space calculation unit 22, a network information management unit 23, an inter-control device message processing unit 24, and a control device communication unit 25. ing.

  The network slice unit 21 stores a plurality of pieces of virtual network information based on the network information received from the control device 10 (that is, the lower level network information that is the basis of virtualization) and the identification conditions of the traffic to be accommodated in the virtual network. calculate. Further, the network slice unit 21 transmits information from the lower network to the network information management unit 23 that manages the corresponding virtual network information, or transmits information from the control device 30 or 40 to the inter-control device message processing unit 24. It has a function to do.

  The identifier space calculation unit 22 calculates an identifier space that can be used as a flow traffic identification condition in each virtual network based on the lower network information and the identifier space included therein, stores the identifier space as an identifier space of the virtual network, and stores the corresponding virtual space. The network information management unit 23 that manages network information is notified.

  The network information management unit 23 manages lower network information and network information corresponding to the virtual network.

  The inter-control device message processing unit 24 creates a message for transmitting information to the control devices 10, 30, and 40 based on a request from another functional unit, and information received from the control devices 10, 30, and 40. It has a function to analyze and distribute to other functional parts.

  The control device communication unit 25 manages communication with the control devices 10, 30, and 40.

  The network slice unit 21 includes an information distribution unit 211 and an accommodation traffic condition database (accommodation traffic condition DB) 212. The information distribution unit 211 has a function of distributing information from the control devices 10, 30, and 40 to the network information management unit 23 that manages the corresponding network information based on the information in the accommodated traffic condition database 212. The accommodation traffic condition database 212 stores (stores) identification conditions of traffic to be accommodated in the virtual network.

  Further, the identifier space calculation unit 22 includes an identifier space database 221 that stores the identifier space calculated by itself, and the network information management unit 23 includes a network database 231 that stores lower-level network information and virtual network information.

  The network information management unit 23 may exist independently for each lower network and virtual network. The network information management unit 23 is single, but the network database 231 exists independently for each network. Also good. Alternatively, a single network database 231 may be used, and network information may be managed in an independent area inside the network database 231. Further, the network information management unit 23 may adopt a method that does not have lower network information and that is acquired from a lower network control device as needed, or that uses information notified from the lower network control device. .

  The information stored in the accommodated traffic condition database 212 may be registered from the outside by an operator or a user, or any information registration means such as setting at startup can be used. That is, the control device 20 holds in advance identification conditions (accommodated traffic identification conditions) for identifying communication traffic to be accommodated in the virtual network, and a set of identifiers usable in the virtual network based on the identification conditions held in advance. Can be managed.

  Referring to FIG. 5, the control device 30 includes a network coupling unit 31, an identifier space calculation unit 32, a network information management unit 33, an inter-control device message processing unit 34, and a control device communication unit 35. ing.

  The network coupling unit 31 is based on the network information received from the control devices 10 and 20 (that is, the lower network information that is the basis for virtualization) and the boundary information between the lower networks stored in the network boundary database 312. A plurality of lower network information is combined to calculate a single virtual network information. Further, the network combining unit 31 transmits information from the lower network to the network information management unit 33 that manages the corresponding virtual network information, or transmits information from the control device 40 to the inter-control device message processing unit 34. have.

  The identifier space calculation unit 32 calculates an identifier space that can be used as a flow traffic identification condition in the virtual network based on the lower-layer network information and the identifier space included therein, stores the identifier space as the identifier space of the virtual network, and stores the corresponding virtual space. The network information management unit 33 that manages network information is notified.

  The network information management unit 33 manages lower network information and network information corresponding to the virtual network.

  The inter-control device message processing unit 34 creates a message for transmitting information to the control devices 10, 20, and 40 based on a request from another function unit, and information received from the control devices 10, 20, and 40. It has a function to analyze and distribute to other functional parts.

  The control device communication unit 35 manages communication with the control devices 10, 20, and 40.

  The network coupling unit 31 includes a control instruction decomposing unit 311 and a network boundary database (network boundary DB) 312. The control instruction decomposing unit 311 has a function of decomposing information from the control device 40 based on information in the network boundary database 312 and distributing the information to the network information managing unit 33 that manages the corresponding network information. The network boundary database 312 stores (stores) information about boundaries connecting lower networks, that is, information such as links between networks.

  The identifier space calculation unit 32 stores an identifier space database (identifier space DB) 321 that stores its calculated identifier space, and the network information management unit 33 stores a network database (network DB) that stores lower-level network information and virtual network information. ) 331, respectively.

  The network information management unit 33 may employ a method that does not have lower network information and that is acquired from a lower network control device as needed, or a method that uses information notified from the lower network control device. Alternatively, the information stored in the network boundary database 312 may be registered from the outside by an operator or a user, or any information registration means such as setting at startup can be used.

  Referring to FIG. 6, the control device 40 includes a flow calculation unit 41, a network information management unit 42, an inter-control device message processing unit 43, and a control device communication unit 44.

  The flow calculation unit 41 acquires the network information received from the control devices 20 and 30 (that is, the lower network information to be flow controlled) from the network information management unit 42, and calculates the flow to be set in the lower network.

  The network information management unit 42 manages the lower network information.

  The inter-control device message processing unit 43 analyzes a function for creating a message for transmitting information to the control devices 20 and 30 and information received from the control devices 20 and 30 based on a request from another function unit. It has a function to distribute to the functional part.

  The control device communication unit 44 manages communication with the control devices 20 and 30.

  The flow calculation unit 41 includes a flow database (flow DB) 411 that stores a flow calculated by itself. The network information management unit 42 includes a network database (network DB) 421 that stores lower-level network information and virtual network information.

  The network information management unit 42 may adopt a method that does not have lower network information and that is acquired from a lower network control device as needed, or a method that uses information notified from the lower network control device.

  Note that the network databases 141, 231, 331, and 421 included in the control devices 10, 20, 30, and 40 may hold information related to the terminal 2 as well as the network information. Further, the network information management units 14, 23, 33, and 42 may exist separately as external devices connected by arbitrary information communication means instead of inside the control devices 10, 20, 30, and 40.

  The control devices to which the control devices 10, 20, 30, 40 described in FIGS. 3 to 6 are connected are in accordance with the system configuration of FIG. Connection destination.

  When the communication system shown in FIG. 2 is configured by the control apparatus having the configuration shown in FIGS. 3 to 6, the apparatus that calculates the flow as the traffic processing method is the control apparatus 40 connected at the highest level. Therefore, the flow calculated by the control device 40 and instructed to set is inspected in each control device that mediates control whether the traffic identification condition included in the flow is acceptable.

  The control devices 10, 20, and 30 hold a set of traffic identification conditions (hereinafter referred to as identifier space) that can be instructed by the control devices 20, 30, and 40 connected to the host device. It is disclosed (provided) to the control devices 20, 30, and 40. The control devices 10, 20, and 30 are not permissible flow setting instructions when a traffic control instruction that does not correspond to the identifier space (hereinafter referred to as a flow setting instruction) is transmitted from the control devices 20, 30, and 40. By returning an error notification including this, it is ensured that the flow settings from each control device do not collide.

  Alternatively, the control device 40 obtains in advance an identifier space defined by the control devices 20 and 30 which are the control devices directly below, calculates a flow setting instruction suitable for the space, and transmits the flow setting instruction to the control devices 20 and 30. By doing so, avoidance of flow setting collision may be guaranteed. Since the identifier space disclosed by the control devices 20 and 30 reflects the identifier space in the lower control device, it can be guaranteed that the control device 20 is allowed to reach the lowest control device 10.

  Hereinafter, a method of calculating the identifier space in the control devices 10, 20, and 30 will be described.

  In the first embodiment, the identifier space is calculated based on a traffic identification condition that can be used by the physical device corresponding to the node. Taking OpenFlow (Spec 1.0) as an example, source MAC (Media Access Control) address, destination MAC address, VLAN ID, VLAN priority, L2 frame type, IP ToS (Internet Protocol Type of Service), IP protocol number The source IP address, destination IP address, source L4 port number, destination L4 port number 11 types of packet header information, and packet input port 12 types of fields are the basis. When a plurality of models are mixed, an identifier space is calculated from identification conditions that can be supported by each model. Hereinafter, an example limited to the source MAC address, the destination MAC address, the source IP address, and the destination IP address will be described.

  In the control device 10, a set of identification conditions that can be used as a traffic processing rule by a device corresponding to a node is an identifier space. In the present embodiment, a method of sharing one identifier space in the entire network without including information on input ports and input nodes in the identifier space regardless of the location is shown. Therefore, the identifier space calculation in the control device 10 becomes an identifier space including all values from the minimum value to the maximum value allowed in each field.

  FIG. 7 shows an example of identifier space expression calculated by the control device 10. In FIG. 7, all values that can be used in the specification are expressed as “any”. When different types of devices are mixed, a product set of identification conditions that can be used by each device is calculated and used as an identifier space. If a node that can identify a source MAC address, a destination MAC address, a source IP address, and a destination IP address and a node that can identify a source MAC address and a destination MAC address are mixed, both An arbitrary set of values of the source MAC address and destination MAC address fields, which is the product of

  Next, an identifier space calculation method in the control device 20 will be described.

  In the control device 20, in order to cut out the network into a plurality of virtual networks, traffic control collision avoidance is guaranteed by calculating the identifier space to be independent between the virtual networks.

  For example, in the configuration of FIG. 2, the network 3-1 is virtualized to an equivalent network by the control device 10-1, and network information is stored in the network database 141 in the control device 10-1. The control device 20 generates two virtual networks based on this network information and provides them to the control device 40-1 and the control device 30. At that time, the control device 20 calculates the identifier space based on the identification condition of the traffic to be accommodated in the network provided to the control device 40-1 and the control device 30.

  For example, the traffic identification condition is set by an operator or a user at the time of system configuration and is stored in the accommodated traffic condition database 212 in the control device 20.

  FIG. 8 shows an example of traffic accommodation conditions. In FIG. 8, the traffic with the destination MAC address from 00: 00: 00: 00: 00 to 00: 00: 00: 00: 00f is accommodated in the virtual network 1 provided to the control device 40-1. Is set to Further, it is set so that traffic having a destination IP address of 192.168.0.1 to 192.168.0.9 is accommodated in the virtual network 2 provided to the control device 30. In addition, distribution to the virtual network 1 has a high priority (1), and distribution to the virtual network 2 has a low priority (2).

  The control device 20 calculates the identifier space based on this accommodated traffic condition. For example, when this accommodated traffic condition is used as the identifier space of the virtual networks 1 and 2 as it is, the destination MAC address is 00: 00: 00: 00: 00 to 00: 00: 00: 00: 00, and Traffic identification conditions where the destination IP address is in the range of 192.168.0.1 to 192.168.0.9 will collide.

  FIG. 9 shows the duplication of the identifier space that causes the above collision. In FIG. 9, the horizontal axis represents the destination IP address value, the vertical axis represents the destination MAC address value, and the source IP address and source MAC address are omitted. The area filled in black indicates the identifier space of the virtual network 1, the white area indicates the identifier space of the virtual network 2, and the overlapping area is the overlap of the identifier space. In order to avoid such duplication, the control device 20 reduces the identifier space of the virtual network 2 having a low priority and expresses it as a prohibited area in the identifier space of the virtual network 2.

  An identifier space calculated by the control device 20 is shown in FIG. Note that φ indicates an empty set. The identifier space of the virtual network 1 has the same permitted area as the accommodated traffic condition of FIG. 8, and all the prohibited areas are empty sets. The identifier space of the virtual network 2 has the same range as the accommodated traffic condition as the permitted space, but the destination MAC address that is a common (overlapping) portion with the virtual network 1 as the prohibited region is 00: 00: 00: 00: 00 : 01 to 00: 00: 00: 00: 00: 0f. By this calculation, identifier spaces independent from each other are disclosed to the control devices 40-1 and 30.

  Finally, identifier space calculation in the control device 30 will be described.

  In the control device 30, a plurality of networks can be integrated and controlled by combining the lower network corresponding to the control device 20 and the control device 10-2 to form one upper network. Therefore, the control device 30 integrates the identifier spaces of the two lower networks to form the identifier space of the upper network.

  FIG. 11 shows identifier spaces disclosed by the control devices 20 and 10-2, respectively. In FIG. 11, the identifier space of the virtual network 2 has a destination IP address of 192.168.0.1 to 192.168.0.9 as a permitted area and a destination MAC address of 00:00:00 as a prohibited area. : 00: 00 to 00: 00: 00: 00: 0f. The identifier space of the virtual network 3 (network provided to the control device 10-2) has a destination MAC address of 00: 00: 00: 00: 11 to 00: 00: 00: 00: 00: 1f as a permitted area. And an empty set as a prohibited area.

  In order to combine these identifier spaces, the control device 30 calculates the product in the permitted area and the sum in the prohibited area in the two spaces, and calculates the sum of the virtual network 4 provided to the control device 40-2. The identifier space.

  FIG. 12 shows the identifier space of the virtual network 4. As shown in FIG. 12, the destination IP address is a product of the permitted area of the virtual network 2 and the permitted area of the virtual network 3 as the permitted area, and the range is 192.168.0.1 to 192.168.0.9, and The range of the destination MAC address from 00: 00: 00: 00: 11 to 00: 00: 00: 00: 00: 1f is calculated. Further, the destination MAC address that is the sum of the prohibited area of the virtual network 2 and the prohibited area (empty set) of the virtual network 3 is set as the prohibited area from 00: 00: 00: 00: 00 to 00:00:00: A range of 00: 0f is calculated.

  As described above, in the first embodiment, in the above identifier space calculation, the sum of the product of the permitted area and the prohibited area is calculated, so that it is end-to-end in a combined network that is a separate network at the lower level. By calculating and disclosing the identifier space that can be used in common, an area of traffic identification conditions in which the flow is valid even across the network is shown. Further, each control device calculates an identifier space, so that an identifier space that can be used in each virtual network without colliding with other networks is defined and provided to each control device.

  Further, the control device that has received the traffic identification condition collates using this identifier space, and if it is not acceptable, notifies the fact as an error (sends a rejection notice), so that the collision of the traffic identification condition is not caused. Finally avoided. More specifically, when the inter-control device message processing unit included in each control device receives a processing rule setting request from a higher-level control device, the identifier used for the processing rule requested to be set is In response to being not included in the set of identifiers that can be used as the processing rule identification condition, a rejection notification indicating that the processing rule cannot be set is transmitted. Alternatively, the collision of the traffic identification conditions may be finally avoided by obtaining the identifier space in advance and calculating the traffic identification conditions corresponding thereto.

[Second form]
Next, a second embodiment will be described.

  First, the operation of the control device 20 in this embodiment will be described. In the present embodiment, the control device 20 holds the accommodation traffic conditions as shown in FIG. 8 as in the first embodiment. Based on this condition, the control device 20 calculates the identifier space for the virtual network 1 provided to the control device 40-1 and the virtual network 2 provided to the control device 30 as shown in FIG.

  Referring to FIG. 13, in the second embodiment, the control device 20 does not calculate the prohibited area, and the destination MAC address that is the overlapping area of the accommodated traffic conditions is from 00: 00: 00: 00: 00 to 00: The range of 0: 00: 00: 00: 0f and the destination IP address from 192.168.0.1 to 192.168.0.9 is treated as a permitted area for both virtual networks 1 and 2, and the control device 40 -1,30.

  However, in this state, a flow collision may occur between the virtual networks 1 and 2. Therefore, the control device 20 performs collision avoidance based on the order of use by setting the previously used traffic identification condition as a prohibited area in another virtual network.

  For example, the control device 40-1 determines that the source MAC address = 00: 00: 00: 00: 21, the destination MAC address = 00: 00: 00: 00: 01, and the source IP address = 192.168. Suppose that the control device 20 is instructed to set a flow having a traffic identification condition of 10.1 and destination IP address = 192.168.0.1. In this case, the control device 20 checks whether or not the flow corresponds to the overlap area, and if so, the field constituting the overlap area, that is, the value of the destination MAC address and the destination IP address, is a virtual network that is another virtual network. 2 is added to the prohibited area. As a result of the addition to the prohibited area, the identifier space as shown in FIG. 14 is rewritten.

  Further, the control device 30 updates the identifier space calculated by itself and disclosed to the control device 40-2 based on the identifier space rewritten by the control device 20, as shown in FIG.

  As described above, in the second mode, a prohibited area is required while avoiding a collision of traffic identification conditions in the entire system by propagating an overlapping identifier space as a prohibited area according to the usage situation. This is prevented from increasing.

[Third form]
Subsequently, a third embodiment will be described.

  FIG. 16 illustrates the configuration of the control device 10 according to the third embodiment. In FIG. 16, the configuration of the control device 10 is the same as the first and second embodiments except for a part thereof, and the processing rule calculation unit 13 is different from the first and second embodiments.

  The processing rule calculation unit 13 includes a flow database (flow DB) 131 and an identification condition correction unit 132. The flow database 131 stores the processing rule that has been calculated by itself (the processing rule calculation unit 13) and the flow information that is the basis of the calculation. The identification condition correction unit 132 corrects the traffic identification condition of the flow instructed from the control devices 20 and 30 in accordance with the information in the identifier space database 151 included in the identifier space calculation unit 15.

  FIG. 17 illustrates the configuration of the control device 20 in the third embodiment. In FIG. 17, the configuration of the control device 20 is the same as the first and second embodiments except for a part thereof, and the network slice unit 21 is different from the first and second embodiments.

  The network slice unit 21 includes an information distribution unit 211, an accommodation traffic condition database (accommodation traffic condition DB) 212, and an identification condition correction unit 213. The information distribution unit 211 has a function of distributing information from the control devices 10, 30, and 40 to the network information management unit 23 that manages the corresponding network information based on the information in the accommodated traffic condition database 212. The accommodation traffic condition database 212 stores identification conditions for traffic to be accommodated in the virtual network. The identification condition correction unit 213 corrects the traffic identification condition of the flow instructed from the control devices 30 and 40 in accordance with the information in the identifier space database 221 included in the identifier space calculation unit 22.

  FIG. 18 illustrates the configuration of the control device 30 in the third embodiment. In FIG. 18, the configuration of the control device 30 is the same as the first and second embodiments except for a part thereof, and the network coupling unit 31 is different from the first and second embodiments.

  The network combining unit 31 includes a control instruction decomposing unit 311, a network boundary database (network boundary DB) 312, and an identification condition correcting unit 213. The control instruction decomposing unit 311 has a function of decomposing information from the control device 40 based on information in the network boundary database 312 and distributing the information to the network information managing unit 33 that manages the corresponding network information. The network boundary database 312 stores information related to boundaries connecting lower networks, that is, information such as links between networks. The identification condition correction unit 313 corrects the traffic identification condition of the flow instructed from the control device 40 in accordance with the information in the identifier space database 321 included in the identifier space calculation unit 32.

  In the third mode, the control devices 10, 20, and 30 have the identification condition correction units 132, 213, and 313, so that some of the flows instructed by the higher-level control device do not match the corresponding identifier space. Is modified to match the identifier space. In the adaptation process, only a flow that is specified so as to be able to take an arbitrary value in the field constituting the traffic identification condition and that matches the identifier space by limiting the portion is targeted.

  For example, when the control device 30 presents the identifier space of the virtual network 4 provided to the control device 40-2 as shown in FIG. 19, the flow having the traffic identification condition as shown in FIG. -2 is specified.

  The flow shown in FIG. 20 does not match the identifier space of FIG. 19 in the destination IP address field, and has a value exceeding the area specified by the identifier space. For such a flow, the control device 30 limits the field of the destination IP address according to the identifier space of FIG. With this processing, the flow of FIG. 20 is modified as shown in FIG. By this processing, the lower control devices 20 and 10-2 are instructed to flow suitable for the identifier space.

  21 uses the range expression as the IP address value. However, if the control devices 10, 20, 30, and 40 permit the range expression, the range expression may be used as it is. A range expression flow may be divided into a plurality of flows having a single value. In addition, when the node does not allow the range expression when the flow that is the range expression is received, the control apparatus 10 may divide and set the plurality of flows having one value as described above. . Alternatively, in this case, when the control device 10 once stores the flow in the flow database 131 and receives a processing rule request conforming to this range expression from the node, the control device 10 matches the value of the packet header included in the processing rule request. You may set one by one.

  As described above, in the third embodiment, since the means for correcting the traffic identification condition of the flow is provided, it is possible to perform an operation that can be set as much as possible even for a flow that does not conform to the identifier space.

[Fourth form]
Subsequently, a fourth embodiment will be described.

  The configuration of the control device in the fourth embodiment can be the same as that of the first embodiment or the third embodiment. In the fourth embodiment, a network identifier space is held in association with a port.

  FIG. 22 shows an example of an identifier space disclosed in the control device 30. Note that p1 to p14 described in the input port field match the port ID in the system configuration of FIG.

  In the fourth embodiment, the identifier space calculated by the control device 30 is as shown in FIG. 23, and different identifier spaces are designated depending on the value of the input port. However, the calculation of the identifier space in the control device 20 is the same as in the first embodiment.

  In the fourth mode, whether or not the flow conforms to the identifier space is verified including the input port in the traffic identification condition in the flow. Therefore, for example, a flow that controls traffic that is input from the port p1 and output to the port p14 passes through different identifier spaces along the transfer path. Specifically, in the flow for controlling the transfer in the network 3-1 in the system configuration of FIG. 2 from being input from the port p1 to being output to the port p7, the input port field in FIG. The identification condition is verified according to the permitted area and the prohibited area that are set to ˜p7. On the other hand, the flow for controlling the transfer in the network 3-2 in FIG. 2 is input from the port p8 and output to the port p14, that is, the permission that the input port field in FIG. 23 is the ports p8 to p14. Validated according to zone and forbidden zone. In the fourth embodiment, for the sake of explanation, it is assumed that all port IDs are unique in the entire system, so the input port field is included in the identifier space. However, if the port ID is not unique, the node ID It is also possible to uniquely identify by expressing in combination.

  In the fourth embodiment, since the identifier space can be defined in units of ports, the amount of information for expressing the identifier space increases, but there is room for changing traffic identification conditions in the middle of the transfer path, and the degree of freedom of flow control Will improve.

  The control devices 10, 20, 30, and 40 described in the first to fourth embodiments can also be realized by a computer program that causes a computer installed in each control device to execute the processing of each unit described above.

  The configurations and operations described in the first to fourth embodiments are examples, and are not intended to limit the configurations and operations of the control device and the like.

  For example, the control device 20 manages at least one communication network including the physical node 1 (for example, the network 3-1), and out of the communication interfaces of the physical nodes included in the communication network to be managed (non-managed communication network ( For example, a set of identifiers that can be used in a communication interface (port 7 of the node 1-3) connected to the network 3-2) may be calculated, and the calculated set of identifiers may be managed in association with a predetermined communication interface. . That is, the control devices 20, 30 and the like may calculate only the identifier space that can be used in the edge port, and hold the calculated identifier space in association with the edge port.

  Based on the intersection of identifier sets that can be used in the communication interfaces of the physical nodes included in each of the plurality of communication networks, the control device 20 uses the identifiers that can be used in the virtual network constructed using the physical nodes. A set may be calculated, and the calculated set of identifiers may be managed in association with a plurality of communication networks. That is, the control devices 20, 30 and the like calculate not only the identifier space that can be used in common in all nodes included in the communication network, and store the calculated identifier space in association with the virtual network, but also the communication. You may manage in connection with a network.

  A part or all of the above embodiments can be described as in the following supplementary notes, but is not limited thereto.

[Appendix 1]
Based on a processing rule for processing communication traffic, a physical node that processes communication traffic identified by an identification condition included in the processing rule;
A first control device (for example, the control device 20 in FIG. 2) that constructs a plurality of virtual networks using the physical node;
A second control device (for example, the control devices 40-1 and 30 in FIG. 2) assigned to each of the plurality of virtual networks,
The first control device includes:
Based on a predetermined condition, a set of identifiers that can be used as the identification condition is assigned to each of the plurality of virtual networks,
A network system for notifying the set of assigned identifiers to the second control device.
[Appendix 2]
The first or second control device is:
For each communication interface included in the physical node, calculate the set of identifiers usable in the communication interface,
The network system according to appendix 1, wherein the calculated set of identifiers is managed in association with the communication interface.
[Appendix 3]
The first or second control device is:
Based on the identifier usable in the communication interface of the physical node, a set of the identifier usable in a virtual network constructed using the physical node is calculated,
The network system according to appendix 1 or 2, wherein the set of calculated identifiers is managed in association with the virtual network constructed using the physical node.
[Appendix 4]
The first or second control device is:
The set of identifiers usable in the virtual network constructed using the physical node is calculated based on the union or intersection set of the set of identifiers usable in the communication interface of the physical node. The network system described.
[Appendix 5]
The first or second control device is:
A set of identifiers usable in a predetermined communication interface connected to a second communication network among communication interfaces of physical nodes included in the first communication network corresponding to the virtual network;
The network system according to attachment 2, wherein the calculated set of identifiers is managed in association with the predetermined communication interface.
[Appendix 6]
The first or second control device is:
Based on the union or product set of the set of identifiers usable in a predetermined communication interface of the physical node included in the first communication network, the virtual network constructed using the physical node can be used. The network system according to appendix 5, which calculates a set of identifiers.
[Appendix 7]
The first control device includes:
The identification condition for identifying communication traffic to be accommodated in the virtual network is held in advance,
The network system according to any one of appendices 1 to 6, wherein the set of identifiers usable in the virtual network is managed based on the identification condition held in advance.
[Appendix 8]
The first control device includes:
When the set of identifiers that can be used in each of the plurality of virtual networks overlap with each other, the set of identifiers that are not allowed to be used as the identifier by each of the plurality of virtual networks. The network system according to any one of appendices 1 to 7, set as:
[Appendix 9]
The first control device includes:
When the set of identifiers that can be used in each of the plurality of virtual networks overlap each other, a predetermined identifier included in the overlapping set can be used in a virtual network having a high priority among the plurality of virtual networks. The network system according to any one of appendices 1 to 8, which is set as a unique identifier.
[Appendix 10]
The first control device includes:
When the sets of identifiers that can be used in each of the plurality of virtual networks overlap with each other, a predetermined identifier included in the overlapping set is assigned to the virtual to which the processing rule including the predetermined identifier is first assigned. The network system according to any one of appendices 1 to 9, which is set as an identifier usable in a network.
[Appendix 11]
The first control device includes:
The network system according to appendix 9 or 10, wherein the predetermined identifier is set as an identifier that cannot be used by a virtual network other than the virtual network to which the processing rule including the predetermined identifier is assigned.
[Appendix 12]
The first control device includes:
The network system according to any one of appendices 1 to 11, wherein a set of identifiers usable in each of the plurality of virtual networks is calculated so as to be independent for each of the plurality of virtual networks.
[Appendix 13]
The first or second control device is:
When receiving a request for setting the processing rule, the identifier is included in the set of identifiers that can be used as an identification condition of the processing rule when the identifier included in the processing rule for which setting is requested 13. The network system according to any one of appendices 1 to 12, which transmits a rejection notice indicating that a rule cannot be set.
[Appendix 14]
The first or second control device is:
(1) When a request for setting the processing rule is received, the identifier included in the processing rule requested to be set is changed to an identifier included in a set of identifiers that can be used as an identification condition of the processing rule. The network system as described in any one of thru | or 13.
[Appendix 15]
It is as the control apparatus which concerns on the above-mentioned 2nd viewpoint.
[Appendix 16]
This is the same as the control method according to the third aspect described above.
[Appendix 17]
It is as the program which concerns on the above-mentioned 4th viewpoint.
The forms of Supplementary Notes 15 to 17 can be expanded to the forms of Supplementary Note 2 to Supplementary Note 14 in the same manner as the Supplementary Note 1 form.

  Each disclosure of the cited patent documents and the like cited above is incorporated herein by reference. Within the scope of the entire disclosure (including claims) of the present invention, the embodiments and examples can be changed and adjusted based on the basic technical concept. In addition, various combinations or selections of various disclosed elements (including each element in each claim, each element in each embodiment or example, each element in each drawing, etc.) within the scope of the entire disclosure of the present invention. Is possible. That is, the present invention of course includes various variations and modifications that could be made by those skilled in the art according to the entire disclosure including the claims and the technical idea. In particular, with respect to the numerical ranges described in this document, any numerical value or small range included in the range should be construed as being specifically described even if there is no specific description.

DESCRIPTION OF SYMBOLS 1, 1-1 to 1-6 Node 2 Terminal 3-1, 3-2 Network 10-1, 10-2, 20, 30, 40-1, 40-2 Control apparatus 11 Node communication part 12 Node control message process Unit 13 Processing rule calculation unit 14, 23, 33, 42 Network information management unit 15, 22, 32 Identifier space calculation unit 16, 24, 34, 43 Inter-control device message processing unit 17, 25, 35, 44 Control device communication unit 21 Network slice unit 31 Network coupling unit 41 Flow calculation unit 100 Physical node 101 First control device 102 Second control device 131, 411 Flow database (flow DB)
132, 213, 313 Identification condition correction unit 141, 231, 331, 421 Network database (network DB)
151, 221 and 321 Identifier space database (identifier space DB)
211 Information distribution part 212 accommodation traffic condition database (accommodation traffic condition DB)
311 Control instruction decomposition unit 312 Network boundary database (network boundary DB)

Claims (17)

Based on a processing rule for processing communication traffic, a physical node that processes communication traffic identified by an identification condition included in the processing rule;
A first control device that constructs a plurality of virtual networks using the physical node;
A second control device assigned to each of the plurality of virtual networks,
The first control device includes:
Based on a predetermined condition, a set of identifiers that can be used as the identification condition is assigned to each of the plurality of virtual networks,
A network system for notifying the set of assigned identifiers to the second control device. The first or second control device is:
For each communication interface included in the physical node, calculate the set of identifiers usable in the communication interface,
The network system according to claim 1, wherein the calculated set of identifiers is managed in association with the communication interface. The first or second control device is:
Based on the identifier usable in the communication interface of the physical node, a set of the identifier usable in a virtual network constructed using the physical node is calculated,
The network system according to claim 1 or 2, wherein the calculated set of identifiers is managed in association with the virtual network constructed using the physical node. The first or second control device is:
4. The set of identifiers usable in a virtual network constructed using the physical node is calculated based on a union or intersection set of the set of identifiers usable in the communication interface of the physical node. The network system described in 1. The first or second control device is:
A set of identifiers usable in a predetermined communication interface connected to a second communication network among communication interfaces of physical nodes included in the first communication network corresponding to the virtual network;
The network system according to claim 2, wherein the calculated set of identifiers is managed in association with the predetermined communication interface. The first or second control device is:
Based on the union or product set of the set of identifiers usable in a predetermined communication interface of the physical node included in the first communication network, the virtual network constructed using the physical node can be used. The network system according to claim 5, wherein a set of identifiers is calculated. The first control device includes:
The identification condition for identifying communication traffic to be accommodated in the virtual network is held in advance,
The network system according to any one of claims 1 to 6, wherein a set of identifiers usable in the virtual network is managed based on the identification condition held in advance. The first control device includes:
When the set of identifiers that can be used in each of the plurality of virtual networks overlap with each other, the set of identifiers that are not allowed to be used as the identifier by each of the plurality of virtual networks. The network system according to any one of claims 1 to 7, which is set as: The first control device includes:
When the set of identifiers that can be used in each of the plurality of virtual networks overlap each other, a predetermined identifier included in the overlapping set can be used in a virtual network having a high priority among the plurality of virtual networks. The network system according to any one of claims 1 to 8, wherein the network system is set as a unique identifier. The first control device includes:
When the sets of identifiers that can be used in each of the plurality of virtual networks overlap with each other, a predetermined identifier included in the overlapping set is assigned to the virtual to which the processing rule including the predetermined identifier is first assigned. The network system according to claim 1, wherein the network system is set as an identifier that can be used in a network. The first control device includes:
The network system according to claim 9 or 10, wherein the predetermined identifier is set as an identifier that cannot be used by a virtual network other than the virtual network to which the processing rule including the predetermined identifier is assigned. The first control device includes:
The network system according to any one of claims 1 to 11, wherein a set of identifiers usable in each of the plurality of virtual networks is calculated so as to be independent for each of the plurality of virtual networks. The first or second control device is:
When receiving a request for setting the processing rule, the identifier is included in the set of identifiers that can be used as an identification condition of the processing rule when the identifier included in the processing rule for which setting is requested The network system according to any one of claims 1 to 12, wherein a rejection notification indicating that a rule cannot be set is transmitted. The first or second control device is:
When the request for setting the processing rule is received, the identifier included in the processing rule requested to be set is changed to an identifier included in a set of identifiers that can be used as an identification condition of the processing rule. The network system according to any one of 1 to 13. Based on a processing rule for processing communication traffic, a control device that controls a physical node that processes communication traffic identified by an identification condition included in the processing rule,
Constructing a plurality of virtual networks using the physical nodes;
Based on a predetermined condition, a set of identifiers that can be used as the identification condition is assigned to each of the plurality of virtual networks,
A control device that notifies the second control device assigned to each of the plurality of virtual networks of the assigned set of identifiers. Based on a processing rule for processing communication traffic, a physical node control method for processing communication traffic identified by an identification condition included in the processing rule,
Constructing a plurality of virtual networks using the physical nodes;
Assigning a set of identifiers usable as the identification condition to each of the plurality of virtual networks based on a predetermined condition;
Notifying a set of assigned identifiers to a second control device assigned to each of the plurality of virtual networks;
Control method. Based on a processing rule for processing communication traffic, a program that is executed by a computer mounted on a control device that controls a physical node that processes communication traffic identified by an identification condition included in the processing rule,
A process of constructing a plurality of virtual networks using the physical node;
A process of allocating a set of identifiers usable as the identification condition to each of the plurality of virtual networks based on a predetermined condition;
A process of notifying a set of assigned identifiers to a second control device assigned to each of the plurality of virtual networks;
A program that executes

Images