WO2016143311A1 - ネットワーク制御装置、ネットワーク制御方法、および、プログラムの記録媒体 - Google Patents
ネットワーク制御装置、ネットワーク制御方法、および、プログラムの記録媒体 Download PDFInfo
- Publication number
- WO2016143311A1 WO2016143311A1 PCT/JP2016/001151 JP2016001151W WO2016143311A1 WO 2016143311 A1 WO2016143311 A1 WO 2016143311A1 JP 2016001151 W JP2016001151 W JP 2016001151W WO 2016143311 A1 WO2016143311 A1 WO 2016143311A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- virtual link
- link
- network
- request
- settable
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 51
- 238000013461 design Methods 0.000 claims abstract description 19
- 230000008569 process Effects 0.000 claims description 21
- 230000008859 change Effects 0.000 claims description 7
- 230000004044 response Effects 0.000 claims description 7
- 238000004364 calculation method Methods 0.000 description 53
- 238000007726 management method Methods 0.000 description 39
- 238000012545 processing Methods 0.000 description 9
- 230000000694 effects Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000008034 disappearance Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000002068 genetic effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/82—Miscellaneous aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
- H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/83—Admission control; Resource allocation based on usage prediction
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
Definitions
- the present invention relates to a network control device, a network control method, and a program, and more particularly, to a control technology and a design technology for a multi-layer network and a multi-domain network.
- the communication carrier network is composed of a plurality of layers (network layers). For example, a network in which a packet layer that can efficiently use network resources by a statistical multiplexing effect and an optical layer that is suitable for long-distance and large-capacity transmission has been constructed.
- packet layer technologies include, for example, MPLS (Multi-Protocol Label Switching) and MPLS-TP (Multi-Protocol Label Switching-Transport Profile).
- MPLS Multi-Protocol Label Switching
- MPLS-TP Multi-Protocol Label Switching-Transport Profile
- the optical layer is generally a circuit-switched network, and OTN (Optical Transport Network) is known as a representative technique.
- the OTN is further divided into TDM (Time Division Division Multiplexing) and WDM (Wavelength Division Division Multiplexing) layers depending on the path switching method. In general, these networks are independently controlled for each layer.
- Patent Document 1 discloses a multi-layer path control technique based on intensive topology design in a packet and WDM two-layer network.
- Patent Document 2 describes a method of abstracting path information that can be set in a lower layer in the form of a node or a link and advertising it using an upper layer routing protocol so that an optimum path can be set. Has been.
- the measurement result of the traffic amount flowing through the upper path (the logical path of the packet network) is acquired in the multilayer network including the packet network and the circuit switching network. Then, the routes of the circuit-switched network and the packet network are calculated, and when congestion occurs due to traffic concentration on some lower links, a route that avoids the lower links is calculated.
- Patent Document 4 describes that the upper layer traffic volume is measured and the lower layer path setting is changed (for example, control of the number of lower layer paths) based on the traffic volume.
- Patent Document 5 describes a technique for establishing a connection between an origin node and a destination node in a short time
- Patent Document 6 discloses a technique for generating a new route for a destination node. Are listed.
- paths and links have a nested configuration. That is, in a lower layer network, a path is set by using lower layer nodes, ports, and links as network resources. In the upper layer network, the path set in the lower layer is treated as a link between nodes, and the node and port information added to it becomes the upper layer network resource. Set.
- the path information that can be set in the lower layer is abstracted in the form of a node or link and advertised by the routing protocol of the higher layer, the optimum path is set even in such a case. It becomes possible to do.
- the advertised lower layer resource information is included, if the upper layer path that satisfies the requirements such as bandwidth and delay cannot be calculated, the path setting fails. become. This is because the path requirement required in the upper layer is not properly transmitted to the lower layer.
- the upper layer can receive supply of desired resources from the lower layer.
- An object of the present invention is to provide a network control device, a network control method, and a program that contribute to the solution of the problem.
- the network control device receives a request for an upper virtual link that can be set to connect between ports of a user connected to an upper layer network, and determines the performance of the settable upper virtual link.
- a request for a lower virtual link that can be set to connect between the upper layer control unit that is obtained and associated and the ports in the upper layer network via the lower layer network; and
- a lower layer control unit that obtains performance and associates and holds the performance.
- the upper layer control unit includes a resource demand prediction unit that predicts a future request for the upper virtual link based on a history of a plurality of settable upper virtual link requests, and a request for the predicted upper virtual link.
- a capacity design unit that calculates resources of the lower layer network necessary for supplying the upper virtual link, and corresponds to the additional resource calculated by the capacity design unit. Requests a lower virtual link to the lower layer control unit, accepts a request for the upper virtual link selected according to the settable upper virtual link and the settable upper link performance, and requests the upper virtual link
- the settable lower virtual link Requesting link it sets the flow corresponding to the settable lower virtual link to the lower layer network.
- the network control device accepts a request for an upper virtual link that can be set for connecting between user ports connected to an upper layer network, and the upper layer that can be set. Determining and associating and holding the performance of the virtual link; accepting a request for a lower virtual link that can be set to connect between ports in the higher layer network via the lower layer network; and Determining and associating and holding a link performance; receiving a request for the settable higher virtual link and a higher virtual link selected according to the settable higher link performance; and the requested higher rank
- the configurable sub-virtual on the path of the flow corresponding to the virtual link A link corresponding to the configurable lower virtual link is set in the lower layer network, and the future upper virtual link is based on a history of requests for the plurality of configurable upper virtual links. Predicting a link request, and calculating the lower layer network resources necessary to supply the upper virtual link in response to the predicted upper virtual link request.
- the program according to the third aspect of the present invention receives a request for an upper virtual link that can be set to connect between user ports connected to an upper layer network, and obtains the performance of the settable upper virtual link.
- the process of associating and holding accepts a request for a lower virtual link that can be set to connect between ports in the upper layer network via the lower layer network, and obtains and associates the performance of the settable lower virtual link.
- the settable lower virtual link A process for setting a flow corresponding to a link in the lower layer network, a process for predicting a request for the upper virtual link in the future based on a history of requests for a plurality of the settable upper virtual links, and the predicted And causing the computer to execute processing for calculating resources of the lower layer network necessary for supplying the upper virtual link in response to a request for the upper virtual link.
- the program can also be provided as a program product recorded in a non-transitory computer-readable storage medium.
- the upper layer can receive supply of desired resources from the lower layer, and appropriately grasp the trend of requests for the resources of the lower layer. It becomes possible.
- FIG. 4 It is a figure which illustrates the data structure of the network database for users after creating the network database information for users shown in FIG. 4 is a flowchart illustrating a flow setting operation by the network control apparatus according to the first embodiment. It is a figure for demonstrating the information which each network database information after the flow setting shown in FIG. 14 hold
- FIG. 1 is a block diagram illustrating the configuration of a network control device 1 according to an embodiment.
- the network control device 1 includes an upper layer control unit 2 and a lower layer control unit 3.
- the upper hierarchy control unit 2 further includes a resource demand prediction unit 208 and a capacity design unit 209. The operation of one embodiment is illustrated in FIG.
- the upper layer control unit 2 accepts a request to connect the ports of the nodes included in the upper layer network (for example, between the ports P802 and P803, between the ports P804 and P805, and between the ports P801 and P806 in FIG. 15).
- the lower layer control unit 3 obtains and associates the link (for example, links L901 to L903 in FIG. 15) connecting the ports via the lower layer network and the performance of the link (for example, link bandwidth, delay, etc.). Hold.
- the upper layer control unit 2 accepts a flow between nodes included in the upper layer network and selected according to the link and the performance. If the link (for example, links L901 and L902 in FIG. 15) is included in the flow path, the upper layer control unit 2 sets the flow corresponding to the link in the lower layer network.
- the resource demand prediction unit 208 predicts such a future request based on a history of a plurality of the requests (that is, a request for connecting ports of nodes included in the upper layer network).
- the capacity design unit 209 calculates the resources of the lower layer network necessary for supplying the link in response to the predicted request.
- the network control device 1 performs the following procedure when controlling a multi-layer network composed of a plurality of layers of networks. That is, the network control device 1 generates a link in the upper layer network based on the topology information of the lower layer network and the request for connecting the ports of the nodes included in the upper layer network presented by the user.
- a request for connecting ports of nodes included in an upper layer network presented by a user is referred to as a “latent link request”, and a link generated based on the latent link request is referred to as a “latent link”.
- the generated links are, for example, links L901 to L903 in FIG.
- the lower layer route (for example, the links L601 and L602 in FIG. 15) corresponding to the potential link. ) To the lower layer network.
- the upper layer can inform the lower layer of the resource (link) requirements desired by itself.
- the upper layer can always be supplied with a desired resource.
- the lower layer can collect resource requirements desired by each individual from a plurality of upper layers, and optimize the resource allocation by performing path design by combining these requirements.
- the lower network side monitors the process of potential link generation / disappearance based on the latent link request given from the upper layer, thereby the behavior of the resource use of the upper layer network. You can know the tendency. Thereby, the resource deployment plan based on the information can be made.
- latent link information that satisfies requirements specified in advance for the upper layer network is provided based on the topology information of the lower layer network.
- the upper layer network calculates a path using the topology obtained by adding the latent link information provided from the lower layer to the topology information of the own layer. As a result, it is possible to efficiently design and set a path in consideration of resource information that can be provided from the lower layer to the upper layer.
- multilayer network control as “multilayer control” and using the term “flow” synonymously with “path”.
- the network control apparatus 10 controls the lower layer network 31 and the upper layer network 32 in accordance with a flow request from the user request unit 20 by the user.
- the network control apparatus 10 includes an NWDB (Network Database) 101 for users, an upper layer NWDB 102, a lower layer NWDB 103, an upper layer control unit 104, a latent link DB 107, and a lower layer control unit 108.
- the network control device 10 includes an upper layer control unit 105 and a lower layer control unit 106.
- the upper layer control unit 105 and the lower layer control unit 106 control the upper layer network 32 and the lower layer network 31 in accordance with respective information changes in the upper layer NWDB 102 and the lower layer NWDB 103.
- a program or a group of programs executed on a computer that plays the role described in the following description may be used.
- a single user will be described, but a plurality of users may exist.
- the NWDB 101 for users is accessed from the user request unit 20 and stores resource information available to the user.
- the upper layer NWDB 102 holds information on the upper layer network 32.
- the lower layer NWDB 103 holds information of the lower layer network 31.
- Each network database holds network information including topology information including nodes, ports, and links and flow (path equivalent) information set therein.
- the lower layer control unit 108 provides information on links (latent links) that the lower layer NW 31 can potentially provide to the upper layer NW 32 to the upper layer control unit 104 via the latent link DB 107. .
- a latent link request and a latent link opening request are received from the upper layer control unit 104 via the latent link DB 107.
- the upper layer control unit 104 obtains potential link information that can be provided to the user from the latent link obtained in the latent link DB 107 and the topology information of the upper layer NW 32 stored in the upper layer NWDB 102. To the user request unit 20. This information is provided via the NWDB 101 for users. Further, the upper layer control unit 104 receives a latent link request and a latent link opening request from the user request unit 20 via the user-oriented NWDB 101.
- the upper layer control unit 104 accesses an external database NWDB 101, upper layer NWDB 102, and latent link DB 107, and acquires or updates information to an external database (DB) access unit 202.
- the upper hierarchy control unit 104 includes a latent link information management unit 203, a layer boundary information management unit 204, a DB information correspondence management unit 205, a path calculation unit 206, a resource demand prediction unit 208, a capacity design unit, 209.
- the latent link information management unit 203 creates and manages latent link information and virtual port information of the NWDB 101 for users.
- the layer boundary information management unit 204 manages the layer boundary with each of the upper layer and the lower layer.
- the DB information correspondence management unit 205 manages the correspondence of information stored in the NWDB 101 for users, the upper layer NWDB 102, and the latent link DB 107.
- the path calculation unit 206 performs path calculation based on the topology information of the network database.
- the resource demand prediction unit 208 monitors and records the latent link request from the upper layer network and the utilization status of the latent link, and predicts the demand of the upper layer using the history information.
- the capacity design unit 209 estimates the amount and arrangement pattern of necessary resources based on the prediction result by the resource demand prediction unit 208.
- the latent link information management unit 203 includes a path calculation scheduler 301, a path calculation request database 302, and a latent link request database 303.
- the path calculation scheduler 301 manages path calculation events.
- the path calculation request database 302 stores information on latent link requests.
- the latent link request database 303 holds a correspondence relationship between a path and a latent link calculated according to the latent link request.
- the lower layer control unit 108 is configured in the same manner as the upper layer control unit 104 shown in FIG. However, there are two databases that the lower layer control unit 108 accesses from the external DB access unit 202: the lower layer NWDB 103 and the latent link DB 107.
- the upper layer control unit 104 is connected to a plurality of latent link DBs 107.
- the latent link DBs 107 may be connected to a plurality of lower layer networks.
- the upper layer control unit 104 and the lower layer control unit 108 realize equivalent functions by executing a program stored in a memory (not shown) of the network control device 10 on a computer such as a CPU (Central Processing Unit). You can also Hereinafter, the operation of the network control apparatus 10 according to the present embodiment will be described with reference to the multilayer network illustrated in FIG.
- the multi-layer network includes a lower layer network 31, an upper layer network 32, and a layer boundary 40.
- the upper layer network 32 includes nodes N11 to N13 and ports P301 to P310.
- the lower layer network 31 includes nodes N21 to N23, ports P401 to P412, and links L601 to L603.
- the layer boundary 40 has boundary connections B501 to B506.
- the boundary connections B501 to B506 are links that connect ports.
- the boundary connection B501 connects the ports P305 and P401.
- the boundary connection B502 connects the ports P306 and P402.
- the boundary connection B503 connects the ports P307 and P403.
- the boundary connection B504 connects the ports P308 and P404.
- the boundary connection B505 connects the ports P309 and P405.
- a boundary connection B506 connects the ports P310 and P406.
- the upper layer control unit 105 and the lower layer control unit 106 of the network control apparatus 10 obtain information on the upper layer network 32 and information on the lower layer network 31 in FIG. 5 from the respective networks. Furthermore, it is assumed that the upper layer control unit 105 and the lower layer control unit 106 have registered information on nodes, ports, and links in the upper layer NWDB 102 and the lower layer NWDB 103, respectively. Further, it is assumed that the information on the layer boundary 40 is recorded in the lower layer control unit 108 in advance. Similarly, the upper layer control unit 104 holds information on the layer boundary between the upper layer NW 32 and the user network.
- the latent link information management unit 203 of the lower layer control unit 108 writes the boundary port information of the upper layer network 32 connected to the lower layer network 31 to the latent link DB 107 through the external DB access unit 202 (FIG. 6). Step S301).
- the information on the boundary port of the upper layer network is obtained from the information held in the layer boundary information management unit 204 of the upper layer control unit 104.
- the latent link information management unit 203 of the upper hierarchy control unit 104 acquires information on the port added to the latent link DB 107 via the external DB access unit 202. This is performed by a callback or message notification from the latent link DB 107 to the external DB access unit 202 or via this.
- the latent link information management unit 203 records the acquired port information in the path calculation request database 302.
- the information of these ports added to the latent link DB 107 may represent a physical port or may be a virtual port abstracted from the physical port.
- a virtual port can be associated with any physical port. Therefore, the connection of the upper layer network 32 to the lower layer network 31 can be expressed by a smaller number of virtual ports than the actual number of physical ports. Below, it demonstrates using a virtual port.
- the latent link information management unit 203 of the upper layer control unit 104 adds a latent link request to the latent link DB 107 via the external DB access unit 202 (step S302).
- a latent link request is associated with two virtual ports and describes the requirements for potential links that can connect both virtual ports. Examples of requirements include bandwidth, delay, reliability, priority, and the like.
- the user also creates the virtual ports necessary to create the latent link request. At this time, the user specifies at least the position of the virtual port, that is, the number of nodes and virtual ports with which the virtual port is associated. The contents of these latent link requests may be specified via an input interface to the layer boundary information management unit 204 of the upper layer control unit 104, which is not shown in FIG.
- the latent link request and latent link information stored in the user-oriented network DB 101 may be acquired, and the request content may be determined based on these.
- the latent link information management unit 203 of the lower layer control unit 108 acquires the latent link request added to the latent link DB 107 via the external DB access unit 202. This is performed by a callback or message notification from the latent link DB 107 to the external DB access unit 202 or via this. Alternatively, it is performed by polling the latent link DB 107 by or via the external DB access unit 202.
- the latent link information management unit 203 of the lower layer control unit 108 records the acquired latent link request in the path calculation request database 302.
- the latent link information management unit 203 of the lower layer control unit 108 checks the connectability of the link connecting the created virtual ports and creates a latent link (step S303).
- the path calculation scheduler 301 generates a path calculation request from the latent link request in the path calculation request database.
- each latent link request recorded in the path calculation request database in the previous step is read as a path request for connecting two virtual ports with specified requirements.
- These path calculation requests include, in addition to the latent link request added in the previous step, path calculation requests for the latent link requests previously stored in the NWDB 101 for users and the path calculation request database 302. It doesn't matter.
- Each path calculation request has information (for example, an identifier of the latent link request) that can uniquely identify the corresponding latent link request.
- the path calculation scheduler 301 determines the time for performing path calculation for these path calculation requests. This time is immediately or after a certain time has elapsed since the present time. When path calculation is performed after a certain amount of time has elapsed from the present time, the elapsed time may be fixedly or dynamically determined based on a program or a set / designated value in advance, and the load status of the network control device 10 It may be determined in consideration of the above. Further, time, time, or information used for deriving these may be given as parameters of the latent link request created in step S302, and determination may be made based on the information.
- the path calculation scheduler 301 passes a path calculation request to the path calculation unit 206 at a predetermined time.
- the path calculation unit 206 performs path calculation on the path calculation request passed from the path calculation scheduler 301.
- the path calculation unit 206 performs path calculation using a constrained shortest path first (CSPF), a heuristic method such as a genetic method, a mathematical programming method, or other path calculation algorithms.
- CSPF constrained shortest path first
- the path calculation unit 206 confirms the possibility of connection of a latent link in the path calculation. In confirming the connection possibility, it is confirmed that the upper layer port corresponding to the virtual port designated as the end point of the latent link is physically connected to the lower layer port. This is confirmed with reference to information recorded in the layer boundary information management unit 204.
- the nodes N11 and N12 in FIG. 5 can be connected.
- the port P305 or P306 of the node N11 is connected to the port P401 or P402 of the node N21 by a boundary connection B501 or B502.
- the node N12 is connected to the node N22 by the boundary connection B503 or B504.
- a latent link can be set between the nodes N11 and N12.
- being physically connected means literally physically connected.
- the upper and lower layer ports are physically connected across one or more switchable devices such as a switch, even if both ports are not short-circuited in the same device, the switching control of the same device If the two ports can be short-circuited, it is determined that connection is possible.
- the path calculation unit 206 passes the path calculation result to the latent link information management unit 203.
- the result of each path calculation has information that can uniquely identify the corresponding path calculation request or the potential link request to which the path calculation request corresponds.
- the latent link information management unit 203 collates the path calculation result received from the path calculation unit 206 with the latent link request in the path calculation request database 302. Also, latent link information corresponding to the latent link request is created, and a combination of the link information and the path calculation result is stored in the latent link request database 303.
- the potential link information is information that uniquely identifies the potential link request, and the link specifications (bandwidth, delay, reliability, etc.) when the virtual ports specified in the potential link request are connected by the same path. Performance such as priority).
- the specification of the path may be used as it is, or the specification of the path is processed (the bandwidth value is made smaller than the path bandwidth, the delay value is made larger than the path delay).
- the obtained value may be used.
- the latent link is stored in the latent link request database 303 together with information indicating that the path does not exist, or Do not store this potential link. This expresses that there is no latent link.
- the path calculation scheduler 301 or the latent link request database 303 notifies the latent link DB 107 of the latent link information via the external DB access unit 202 (step S303). ).
- This notification includes information of the potential link specification and the corresponding potential link request that can be uniquely identified.
- the latent link is recorded in the latent link DB 107 as a link connecting the virtual ports assigned in step S301.
- a latent link is a link that is not actually set, so the latent link information or the latent link DB 107 includes information for determining the difference between the two.
- the lower layer control unit 108 stores information on potential links connectable between upper layer boundary ports in the potential link DB 107.
- virtual ports P801 to P806 corresponding to the physical boundary ports of the nodes N11 to N13 and latent links L901 to L903 indicated by dotted lines are stored in the latent link DB 107.
- FIG. 8 shows a specific data configuration of the latent link DB 107 in the multi-layer network of FIG.
- topology information such as port information 107B and link information 107C is registered in the latent link DB 107.
- “Assigned” in the port information 107B is information indicating whether or not the port is a virtual port. If TRUE, it indicates that the port is not a virtual port but an actual port, and if FALSE, the port is a virtual port. “Established” in the link information 107C is information indicating whether the link is a latent link. If TRUE, the link is a set link in which a flow is actually set in the lower layer network. If FALSE, the link is a latent link. It shows that.
- the delay (Delay) represents a link delay that occurs when a link is created by setting a lower layer flow in the section.
- FIG. 9 and 10 respectively show the upper layer network DB 102 and the lower layer network DB 103 when the latent link DB 107 is created.
- NWDB 102 since there is no flow in the lower layer network, there is no link and only node information 102A and port information 102B are registered. However, depending on the network configuration, a link connecting ports that are not layer boundaries may be registered. In this case, the link including the link is copied to the NWDB for users.
- topology information such as node information 103A, port information 103B, and link information 103C is registered.
- the delay information (Delay) of the link information 103C is a propagation delay based on the physical distance of the link, for example, and is registered by the lower layer control unit 106.
- the flow may be registered depending on the initial state of the network. In this case, a latent link creation operation is performed after creating a set link corresponding to each flow.
- FIG. 11 shows the data structure of the layer boundary 40 held by the layer boundary information management unit 204 of the lower layer control unit 108.
- the node, port, link, and flow information in each network database is not limited to that described above.
- the maximum bandwidth, the remaining bandwidth, and bandwidth information reserved for the flow may be added to each port, or cost information for route calculation may be added as metric information in addition to link delay.
- the network to be controlled is an optical layer network
- available resource information and empty resource information may be added to the port.
- the resource information is the wavelength in the WDM layer, the time slot in the TDM layer, the flow identification information in the header in the layer based on packet switching (the label in the shim header in MPLS, the VID (VLAN Identifier) in VLAN (Virtual Local Area Network)) , OpenFlow supports matching tuple combinations, etc.).
- the user request unit 20 and the upper layer control unit 104 request and provide latent link information that can be provided to the user by the upper layer network 32 through the user network DB 101 by the same processing as in FIG. Perform (FIG. 12).
- the path calculation unit 206 of the upper layer control unit 104 performs path calculation in a combined topology in which the latent link stored in the latent link DB 107 is added as a link to the topology stored in the upper layer network DB 102.
- the route candidates include a first route (total delay 200 msec) via links L901 (delay 100 msec) and L902 (delay 100 msec), and a second route (total delay 300 msec) via link L903 (delay 300 msec).
- a latent link (X) based on the first route (L901-L902) is created.
- the user request unit 20 selects a potential link to be used from the potential links stored in the user network DB 101, and adds a corresponding flow to the user network DB 101. (Step S401).
- the latent link information management unit 203 of the upper layer control unit 104 detects the update of the user network DB 101 by a callback or message notification from the user network DB 101 to the external DB access unit 202 or via this. Alternatively, it is detected by polling the external DB access unit 202 or the user network DB 101 via the external DB access unit 202.
- the upper layer control unit 104 Upon receiving the flow setting request from the user request unit 20, the upper layer control unit 104 starts a flow setting process for setting the latent link X used by the flow. First, it is determined whether or not the latent link corresponding to the designated flow is provided only by the upper layer network 32 (step S402). As an example, the route in the upper layer network corresponding to the latent link X is L901-L902 (Yes in step S402). Therefore, in order to set a flow that passes through each latent link, the flow is registered in the latent link DB 107 (step S403). A flow F701 in the latent link DB 107 is schematically shown in FIG. At this time, the status of the flow information 107D in the latent link DB 107 shown in FIG.
- the lower layer control unit 108 Upon receiving the flow setting request from the upper layer control unit 104, the lower layer control unit 108 starts processing for setting the latent link used by the flow.
- the latent link information management unit 203 of the lower layer control unit 108 sets the latent links L901 and L902 corresponding to the flows F901 and F902 as actual links.
- the lower layer control unit 106 sets the flows F703 and F704 that form both latent links (step S404).
- the lower layer control unit 106 changes the status of the flow F703 in the lower layer NWDB 103 to “set” as illustrated in FIG.
- the lower layer control unit 108 changes the latent link L901 in the latent link DB 107 corresponding to the set flow F703 to “set” (step S405). Specifically, as shown in FIG. 16, the Established (set) of the latent link L901 is changed to “TRUE”. Further, the virtual ports P802 and P803 at the end points of the latent link L901 are also associated with the ports of the higher layer NWDB 102. The end point ports of the flow F703 of the lower layer NWDB 103 are the port P402 of the node N21 and the port P403 of the node N22. Therefore, by referring to the layer boundary information shown in FIG.
- the DB information correspondence management unit 205 of the lower layer control unit 108 associates the virtual port P802 of the latent link DB 107 with the port P306 of the node N11 of the upper layer network DB 102.
- the DB information correspondence management unit 205 further associates the port P307 of the node N12 of the higher layer network DB 102 with the virtual port P803 of the latent link DB 107, and holds these port correspondences.
- the latent link information management unit 203 of the lower layer control unit 108 changes the assigned values of the virtual ports P802 and P803 in the port information 107B of the latent link DB 107 to “TRUE”.
- the upper layer control unit 104 registers the link of the latent link DB 107 changed to the already set in the previous step as a link in the upper layer network DB 102 (step S406). More specifically, a link L001 corresponding to the link L901 of the user-facing NWDB 101 is registered between the ports P306 and P307 of the higher layer NWDB 102 based on the correspondence between the DB information held previously. At this time, other link information such as delay is also copied.
- the DB information correspondence management unit 205 also holds the correspondence relationship between the link L901 of the user-oriented NWDB 101 and the link L001 of the upper layer NWDB 102 as the correspondence between DB information.
- the lower layer control unit 108 recalculates the latent links (Step S407). Specifically, the processing shown in FIG. 6 is performed after excluding the port at the layer boundary used by the link flow setting so far from the nodes of the upper layer network 32.
- the upper layer control unit 104 performs the above steps S403 to S407 for all the latent links through which the flow is first registered in the user NWDB 101 (step S408). As described above, among the two potential links L901 and L902 included in the flow F701, the processing for the potential link L901 is completed, but the other potential link L902 remains (No in step S408). Therefore, the above steps S403 to S407 are executed for the latent link L902.
- Step S410 the flow is actually set in each network device of the upper layer network 32 according to the information of the flow F701 registered by the upper layer control unit 105.
- the upper layer control unit 105 changes the status information of the flow F702 of the upper layer NWDB 102 to “set” as illustrated in FIG.
- the upper layer control unit 104 changes the status of the flow F701 in the user NWDB 101 to “set”, as shown in FIG.
- the user request unit 20 can know the completion of the flow setting by changing the flow information of the NWDB 101 for users.
- the upper layer control unit 104 sets a flow necessary for the lower layer network 31 and the upper layer network 32 as shown in FIG.
- the data structures of the latent link DB 107, the upper layer NWDB 102, and the lower layer NWDB 103 shown in FIG. 15 are illustrated in FIGS. 16, 17, and 18, respectively.
- flow information 107D is added in addition to the topology information (107B, 107C).
- the established information of the link that has been set is “TRUE”, and the assigned information of the port associated with the port of the upper layer network is “TRUE”.
- flow information 103D is added.
- flow path information is held in the form of a list of links through which it passes.
- the information of the node and port at the input side end point of the flow is held in Match.
- the action stores information on nodes and ports at the output end points of the flow.
- Resource demand forecast The resource demand prediction unit 208 of the upper layer control unit 104 monitors information on latent links set as links in the operations from step S402 to S408 in the flowchart of FIG. This can be known about the potential link information of the user NWDB 101 by polling the user NWDB 101 or receiving a change notification from the database.
- the resource demand prediction unit 208 records fluctuations in the number, specifications, distribution, etc. of latent link requests obtained by monitoring, and predicts future demand based on the history. The prediction result is obtained as the number, specifications, and distribution of latent link requests.
- the capacity design unit 209 determines the amount of resources required to supply potential links that can be connected to the potential link requests. And calculate the distribution. This calculation is performed in consideration of a link existing in the upper layer NWDB 102 and resources in use or available from the potential link recorded in the potential link DB 107. When the potential link for the predicted potential link request cannot be provided by only the current resource, the capacity designing unit 209 calculates the amount and arrangement of the additional required resources. Also, a corresponding latent link request is generated based on information on the amount and arrangement of resources that are additionally required, newly registered in the latent link DB 107, and additionally supplied with potential links from lower layers.
- the above resource demand prediction and capacity design can be performed in the same manner in the lower layer control unit 108.
- the lower layer network 31 is a network physically located at the lowest layer, such as a WDM network
- the additional deployment of resources calculated by the capacity design unit 209 involves the addition of physical facilities.
- latent link information including specifications such as performance is stored in the NWDB 101 for users and the latent link DB 107.
- the upper layer will It is possible to design and set a path that meets the flow requirements on the premise of supply.
- On the lower network side it is possible to know the trend of the resource usage behavior of the upper layer network by monitoring the process of generating and disappearing the latent link based on the latent link request given from the upper layer. For this reason, a resource deployment plan based on the information can be made.
- the network control device according to the second embodiment of the present invention has the same configuration as the network control device according to the first embodiment. Regarding the operation, a difference between the present embodiment and the first embodiment will be described.
- the network control apparatus performs the operation shown in FIG. 19 in addition to the operation described in the first embodiment.
- the latent link information management unit 203 of the upper layer control unit 104 periodically updates the latent link request information (step S502).
- the process performed in step S502 is equivalent to the process in step S302 in the first embodiment.
- the latent link information management unit 203 notifies the latent link DB 107 of the latest latent link request information (step S503).
- the process performed in step S503 is equivalent to the process in step S303 in the first embodiment.
- the time interval before and after performing these steps repeatedly is determined by the path calculation scheduler 301. This time may be determined fixedly or dynamically based on a program or a set / designated value in advance, or may be determined in consideration of the load status of the network control device 10. Further, time, time, or information used for deriving these may be assigned as parameters of the latent link request created in step S502, and the determination may be made based on the information.
- the update of the latent link request information by the latent link information management unit 203 of the upper layer control unit 104 may be synchronized with the update of the latent link request information from the user to the NWDB 101 for the user. That is, when the user updates the latent link request information and notifies the user-oriented NWDB 101 in the same manner as in step S502, the upper layer control unit 104 recalculates the latent links in the user-oriented NWDB 101 as in step S503. ,Update. As a result, when the route associated with the latent link in the user-oriented NWDB 101 changes, the upper layer control unit 104 changes the latent link request to the lower layer to secure additional resources or release surplus resources. (Step S502).
- the latent link information recorded in the latent link DB 107 can be continuously updated. Thereby, the effect by 1st Embodiment can be maintained.
- the network control device according to the third embodiment of the present invention has the same configuration as the network control device according to the first and second embodiments. Regarding the operation, a difference between the present embodiment and the first and second embodiments will be described.
- the latent link information management unit 203 detects that a change has occurred in the network state of one of the upper layer network 32 and the lower layer network 31 via the upper layer NWDB 102 or the lower layer NWDB 103 (step S601). This is performed by callback or message notification from the upper layer NWDB 102 or the lower layer NWDB 103 to the external DB access unit 202. Alternatively, it is performed by polling the upper layer NWDB 102 or the lower layer NWDB 103 by the external DB access unit 202.
- the latent link information management unit 203 updates the latent link request information and notifies the latent link DB 107 of the latest latent link request information (step S602).
- the process performed in step S602 is equivalent to the process in step S502 in the second embodiment.
- step S603 the latent link in the latent link DB 107 is updated with the one notified from the latent link information management unit 203 (step S603).
- the process performed in step S603 is equivalent to the process in step S503 in the second embodiment.
- the latent link information recorded in the latent link DB 107 can be immediately updated in response to a change in the state of the upper layer network 32 or the lower layer network 31 due to a reason not depending on the network control device 10. .
- the connection possibility of the latent link currently recorded on latent link DB107 is maintainable. Note that reasons that do not depend on the network control device 10 include failures, control and setting changes from another system, facility construction, and the like.
- the network control device according to the fourth embodiment of the present invention has the same configuration as the network control device according to the first to third embodiments. Regarding the operation, a difference between the present embodiment and the first to third embodiments will be described.
- the user can update the latent link request in the latent link DB 107 at any timing via the user request unit 20.
- the latent link request information in the latent link DB 107 is updated.
- the latent link information management unit 203 detects this update through an operation similar to that in step S302 in the first embodiment, updates the latent link information through an operation similar to that in step S502 in the second embodiment, and transfers the latent link information to the latent link DB 107. Notify the latest potential link information.
- the latent link DB 107 is updated with the latest latent link information notified by the same operation as in step S503 of the second embodiment.
- the user When a user adds a latent link request, the user adds a latent link request to the latent link DB 107 through the user request unit 20 at an arbitrary timing.
- the operation after adding the latent link request is in accordance with the operation of the first embodiment.
- the user When the user deletes the latent link request, the user deletes the latent link request from the latent link DB 107 through the user request unit 20 at an arbitrary timing.
- the operation after deleting the latent link request conforms to the operation after step S602 in the third embodiment.
- the NWDB 101 for users may manage the latent link request in the soft state. That is, the NWDB 101 for users holds a timer for each latent link request, and deletes the latent link information when the predetermined time has elapsed. If there is an update to the same latent link request or the same request from the user before the timer expires, the timer is reset.
- the user can always notify the network control apparatus 10 of the change in the request for the latent link via the latent link DB 107.
- the user can always be supplied with the latent link he / she desires.
- a predetermined field of a PCEP (Path Computation Element communication Protocol) message is used as a message including a latent link request or a message notifying a generated latent link (for example, from a lower layer to an upper layer).
- a predetermined value can be used.
- storage means for holding a policy regarding disclosure of latent links for each upper layer may be provided.
- the input of path calculation and / or the latent link information notified to each higher layer is changed according to the policy.
- flexible control according to the policy can be performed for each of a plurality of upper layers.
- the present invention can be applied to a service in which a carrier quickly provides a virtual network on demand to a user.
- the present invention can be applied to a VPN (Virtual Private Network) service that connects user base networks, a network control portion of a data center and a user base, or a cloud service that connects data centers to each other.
- VPN Virtual Private Network
- the configurable lower virtual link performance includes at least one of bandwidth, delay, reliability, and priority of the configurable lower virtual link.
- the lower layer control unit may configure the configurable lower virtual link and the configurable based on topology information of a layer boundary between the upper layer network and the lower layer network and topology information of the lower layer network. Find the performance of the lower virtual link, The network control device according to appendix 1 or 2.
- the upper layer control unit obtains a path of the flow based on topology information of the upper layer network and the configurable lower virtual link; The network control device according to any one of appendices 1 to 3.
- the lower layer control unit periodically performs an operation of obtaining and maintaining the performance of the settable lower virtual link and the settable lower virtual link in association with each other, The network control device according to any one of appendices 1 to 4.
- the lower layer control unit obtains the performance of the configurable lower virtual link and the configurable lower virtual link and associates and holds the operation to at least one of the upper layer network and the lower layer network When network conditions change, The network control device according to any one of appendices 1 to 5.
- the network control method according to the second aspect is as described above.
- the configurable lower virtual link performance includes at least one of bandwidth, delay, reliability, and priority of the configurable lower virtual link.
- the network control device based on topology information of a layer boundary between the upper layer network and the lower layer network, and topology information of the lower layer network, the configurable lower virtual link and the configurable lower layer Find the performance of the virtual link, The network control method according to appendix 7 or 8.
- [Appendix 10] The network control according to any one of appendices 7 to 9, including a step in which the network control device obtains a route of the flow based on topology information of the upper layer network and the configurable lower virtual link. Method.
- the network control device periodically performs an operation of obtaining and holding the settable lower virtual link and the performance of the settable lower virtual link in association with each other, The network control method according to any one of appendices 7 to 10.
- [Appendix 12] The network control device obtains and associates and holds the performance of the configurable lower virtual link and the configurable lower virtual link in at least one of the upper layer network and the lower layer network. To be performed when the status of The network control method according to any one of appendices 7 to 11.
- the program according to the third aspect is as described above.
- the configurable lower virtual link performance includes at least one of bandwidth, delay, reliability, and priority of the configurable lower virtual link.
- [Appendix 15] Based on the topology information of the layer boundary between the upper layer network and the lower layer network and the topology information of the lower layer network, the performance of the configurable lower virtual link and the configurable lower virtual link is obtained. Causing the computer to execute a process; The program according to appendix 13 or 14.
- [Appendix 16] Causing the computer to execute processing for obtaining a path of the flow based on topology information of the upper layer network and the configurable lower virtual link; The program according to any one of appendices 13 to 15.
- [Appendix 17] Causing the computer to execute processing for periodically performing an operation of obtaining and associating and holding the settable lower virtual link and the performance of the settable lower virtual link.
- [Appendix 18] The state of at least one of the first layer network and the second layer network changes the operation of obtaining and maintaining the performance of the configurable lower virtual link and the configurable lower virtual link. Causing the computer to execute processing to be performed when The program according to any one of appendices 13 to 17.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
本発明の第1実施形態では、2レイヤからなるマルチレイヤネットワークを制御する制御装置の構成および動作について詳細に説明する。
図2において、本実施形態によるネットワーク制御装置10は、ユーザによるユーザ要求部20からのフロー要求に従って、下位レイヤネットワーク31および上位レイヤネットワーク32を制御する。ネットワーク制御装置10は、ユーザ向けNWDB(Network Database:ネットワークデータベース)101、上位レイヤNWDB102、下位レイヤNWDB103、上位階層制御部104、潜在リンクDB107、下位階層制御部108を有する。さらに、ネットワーク制御装置10は、上位レイヤ制御部105および下位レイヤ制御部106を有する。上位レイヤ制御部105および下位レイヤ制御部106は、上位レイヤNWDB102および下位レイヤNWDB103におけるそれぞれの情報変更に従って、上位レイヤネットワーク32および下位レイヤネットワーク31をそれぞれ制御する。なお、ここでユーザの代わりに、以降の説明で記述される役割を果たす、計算機上で実行されるプログラムまたはプログラム群を用いてもよい。また、以降では、単一のユーザを対象に説明するが、ユーザは複数存在しても構わない。
ただし、下位階層制御部108が外部DBアクセス部202からアクセスするデータベースは、下位レイヤNWDB103と潜在リンクDB107の2つである。
一方、下位レイヤネットワーク31は、ノードN21~N23と、ポートP401~P412と、リンクL601~L603とを有する。
以下、ネットワーク制御装置10の潜在リンク作成動作(例えば、潜在リンクDB107内に作成)と、フロー設定動作について、図6~図18を参照しつつ詳細に説明する。
まず、下位階層制御部108の潜在リンク情報管理部203は外部DBアクセス部202を通して潜在リンクDB107へ、下位レイヤネットワーク31と接続されている上位レイヤネットワーク32の境界ポートの情報を書き込む(図6のステップS301)。上位レイヤネットワークの境界ポートの情報は、上位階層制御部104のレイヤ境界情報管理部204で保持されている情報から得られる。上位階層制御部104の潜在リンク情報管理部203は、外部DBアクセス部202を介して、潜在リンクDB107に追加されたポートの情報を取得する。これは潜在リンクDB107から外部DBアクセス部202に対する、または、これを介したコールバックもしくはメッセージ通知によって行われる。あるいは、外部DBアクセス部202またはこれを介した、潜在リンクDB107に対するポーリングによって行われる。潜在リンク情報管理部203は、取得したポートの情報をパス計算要求データベース302に記録する。ここで、潜在リンクDB107に追加される、これらのポートの情報は物理ポートを表現するものでも構わないし、物理ポートを抽象化した仮想ポートでも構わない。仮想ポートは、任意の物理ポートと関連づけることができる。したがって、実際の物理ポート数よりも少ない数の仮想ポートで、上位レイヤネットワーク32の下位レイヤネットワーク31への接続を表現することができる。以下では、仮想ポートを用いて説明する。
パス計算スケジューラ301はパス計算要求データベース内の潜在リンク要求から、パス計算要求を生成する。このとき、先のステップでパス計算要求データベースに記録された潜在リンク要求はそれぞれ、2つの仮想ポートを指定の要件で接続するパスの要求として読み替えられる。これらのパス計算要求には、先のステップで追加された潜在リンク要求の他、それ以前からユーザ向けNWDB101および、パス計算要求データベース302に格納されていた潜在リンク要求に対するパス計算要求が含まれていても構わない。各パス計算要求は、対応する潜在リンク要求を一意に特定可能な情報(例えば、潜在リンク要求の識別子など)を有する。
パス計算部206は、パス計算スケジューラ301から渡されたパス計算要求に対してパス計算を行う。パス計算部206は、下位レイヤネットワーク31のトポロジにおいて、パスの計算をCSPF(Constrained Shortest Path First)、遺伝法などのヒューリスティック法、数理計画法、または、その他のパス計算アルゴリズムを用いて行う。また、パス計算部206は、パス計算の中で、潜在リンクの接続可能性を確認する。接続可能性の確認では、潜在リンクの端点として指定されている仮想ポートに対応する上位レイヤのポートが、下位レイヤのポートと物理的に接続されていることを確認する。これは、レイヤ境界情報管理部204に記録されている情報を参照して確認される。
次に、ユーザ向けNWDB101にフローが追加された場合のネットワーク制御装置10の動作を、図5および図7の構成を例に、図12~図18を参照しつつ説明する。
また、DB情報間対応管理部205は、ユーザ向けNWDB101のリンクL901と上位レイヤNWDB102のリンクL001との対応関係もDB情報間対応として保持する。
上位階層制御部104のリソース需要予測部208は、図14のフローチャートのステップS402からS408までの動作においてリンクとして設定される潜在リンクの情報を監視する。これは、ユーザ向けNWDB101の潜在リンク情報について、ユーザ向けNWDB101をポーリングするか、または、同データベースから変更通知を受けることで知ることができる。
以上述べたように、第1の実施形態によれば、ユーザ向けNWDB101および潜在リンクDB107に、性能等の諸元も含めた潜在リンクの情報を格納する。事前に下位のレイヤに対して要求を通知することにより、まだ下位のレイヤでフローが設定されておらず、上位レイヤにリンクが存在しない状態であっても、上位のレイヤでは、所望のリンクの供給を前提に、フローの要求に合うパスを設計・設定することができる。また、下位のネットワーク側では、上位のレイヤから与えられる潜在リンク要求に基づいた潜在リンクの生成・消滅の過程を監視することにより、上位レイヤネットワークのリソース使用の挙動の傾向を知ることができる。このため、その情報に基づくリソース配備計画を立てることができる。
本発明の第2の実施形態に係るネットワーク制御装置は、第1の実施形態に係るネットワーク制御装置と同様の構成を有する。動作に関して、本実施形態と第1の実施形態との差分を説明する。
第2の実施形態によるネットワーク制御装置は、第1の実施形態で説明した動作の他、図19に示した動作を行う。
本発明の第2実施形態によれば、潜在リンクDB107に記録される潜在リンク情報を更新し続けることができる。これにより、第1の実施形態による効果を持続することができる。
本発明の第3の実施形態に係るネットワーク制御装置は、第1および第2の実施形態に係るネットワーク制御装置と同様の構成を有する。動作に関して、本実施形態と第1および第2の実施形態との差分を説明する。
図20のフローチャートを参照して第3の実施形態の動作を説明する。潜在リンク情報管理部203は上位レイヤNWDB102または下位レイヤNWDB103を介して、上位レイヤネットワーク32および下位レイヤネットワーク31のいずれかのレイヤのネットワークの状態に変化が起きたことを検知する(ステップS601)。
これは、上位レイヤNWDB102または下位レイヤNWDB103から外部DBアクセス部202に対するコールバックまたはメッセージ通知によって行われる。あるいは、外部DBアクセス部202による上位レイヤNWDB102または下位レイヤNWDB103に対するポーリングによって行われる。
本発明の第3実施形態によれば、ネットワーク制御装置10に依らない事由による上位レイヤネットワーク32または下位レイヤネットワーク31の状態変化に応じて、潜在リンクDB107に記録される潜在リンク情報を直ちに更新できる。これにより、潜在リンクDB107に記録されている潜在リンクの接続可能性を維持できる。なお、ネットワーク制御装置10によらない事由には、障害、別系統からの制御や設定変更、設備工事、などがある。
本発明の第4の実施形態に係るネットワーク制御装置は、第1ないし第3の実施形態に係るネットワーク制御装置と同様の構成を有する。動作に関して、本実施形態と第1ないし第3の実施形態との差分を説明する。
本発明の第4の実施形態によると、ユーザはユーザ要求部20を介して任意のタイミングで潜在リンクDB107内の潜在リンク要求を更新できる。これに伴い、潜在リンクDB107内の潜在リンク要求情報が更新される。潜在リンク情報管理部203は本更新を第1の実施形態におけるステップS302と同様の動作によって検知し、第2の実施形態のステップS502と同様の動作によって潜在リンク情報を更新し、潜在リンクDB107へ最新の潜在リンク情報を通知する。潜在リンクDB107は、第2の実施形態のステップS503と同様の動作によって、通知された最新の潜在リンク情報によって更新される。
本発明の第4の実施形態によれば、ユーザは潜在リンクに対する要求の変化をつねに潜在リンクDB107を介してネットワーク制御装置10へ伝えることが可能となる。これにより、ユーザはつねに自身が望む潜在リンクの供給を受けることができる。
上記実施形態において、潜在リンク要求を含むメッセージ、または、生成された潜在リンクを(例えば、下位のレイヤから上位のレイヤへ)通知するメッセージとして、PCEP(Path Computation Element communication Protocol)メッセージの所定のフィールドに所定の値を設定したものを用いることができる。
本発明は、例えばキャリアがユーザに対し、オンデマンドにて迅速に仮想ネットワークを提供するサービスについて、適用することができる。具体的には、ユーザの拠点ネットワーク同士を接続するVPN(Virtual Private Network)サービスや、データセンタとユーザ拠点、または、データセンタ同士を接続するクラウドサービスのネットワーク制御部分などに適用することができる。
[付記1]
上記第1の態様に係るネットワーク制御装置のとおりである。
[付記2]
前記設定可能な下位仮想リンクの性能は、前記設定可能な下位仮想リンクの帯域、遅延、信頼性、および、優先度のうちの少なくともいずれかを含む、
付記1に記載のネットワーク制御装置。
[付記3]
前記下位階層制御部は、前記上位レイヤネットワークと前記下位レイヤネットワークの間のレイヤ境界のトポロジ情報、および、前記下位レイヤネットワークのトポロジ情報に基づいて、前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求める、
付記1または2に記載のネットワーク制御装置。
[付記4]
前記上位階層制御部は、前記上位レイヤネットワークのトポロジ情報、および、前記設定可能な下位仮想リンクに基づいて、前記フローの経路を求める、
付記1ないし3のいずれか一に記載のネットワーク制御装置。
[付記5]
前記下位階層制御部は、前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求めるとともに関連付けて保持する動作を、定期的に行う、
付記1ないし4のいずれか一に記載のネットワーク制御装置。
[付記6]
前記下位階層制御部は、前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求めるともに関連付けて保持する動作を、前記上位レイヤネットワークおよび前記下位レイヤネットワークのうちの少なくともいずれかのネットワークの状態が変化した場合に行う、
付記1ないし5のいずれか一に記載のネットワーク制御装置。
[付記7]
上記第2の態様に係るネットワーク制御方法のとおりである。
[付記8]
前記設定可能な下位仮想リンクの性能は、前記設定可能な下位仮想リンクの帯域、遅延、信頼性、および、優先度のうちの少なくともいずれかを含む、
付記7に記載のネットワーク制御方法。
[付記9]
前記ネットワーク制御装置は、前記上位レイヤネットワークと前記下位レイヤネットワークの間のレイヤ境界のトポロジ情報、および、前記下位レイヤネットワークのトポロジ情報に基づいて、前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求める、
付記7または8に記載のネットワーク制御方法。
[付記10]
前記ネットワーク制御装置が、前記上位レイヤネットワークのトポロジ情報、および、前記設定可能な下位仮想リンクに基づいて、前記フローの経路を求めるステップを含む、 付記7ないし9のいずれか一に記載のネットワーク制御方法。
[付記11]
前記ネットワーク制御装置は、前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求めるとともに関連付けて保持する動作を、定期的に行う、
付記7ないし10のいずれか一に記載のネットワーク制御方法。
[付記12]
前記ネットワーク制御装置は、前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求めるともに関連付けて保持する動作を、前記上位レイヤネットワークおよび前記下位レイヤネットワークのうちの少なくともいずれかのネットワークの状態が変化した場合に行う、
付記7ないし11のいずれか一に記載のネットワーク制御方法。
[付記13]
上記第3の態様に係るプログラムのとおりである。
[付記14]
前記設定可能な下位仮想リンクの性能は、前記設定可能な下位仮想リンクの帯域、遅延、信頼性、および、優先度のうちの少なくともいずれかを含む、
付記13に記載のプログラム。
[付記15]
前記上位レイヤネットワークと前記下位レイヤネットワークの間のレイヤ境界のトポロジ情報、および、前記下位レイヤネットワークのトポロジ情報に基づいて、前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求める処理を、前記コンピュータに実行させる、
付記13または14に記載のプログラム。
[付記16]
前記上位レイヤネットワークのトポロジ情報、および、前記設定可能な下位仮想リンクに基づいて、前記フローの経路を求める処理を、前記コンピュータに実行させる、
付記13ないし15のいずれか一に記載のプログラム。
[付記17]
前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求めるとともに関連付けて保持する動作を、定期的に行う処理を、前記コンピュータに実行させる、
付記13ないし16のいずれか一に記載のプログラム。
[付記18]
前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求めるともに関連付けて保持する動作を、前記第1レイヤネットワークおよび前記第2レイヤネットワークのうちの少なくともいずれかのネットワークの状態が変化した場合に行う処理を、前記コンピュータに実行させる、
付記13ないし17のいずれか一に記載のプログラム。
2 上位階層制御部
3 下位階層制御部
10 ネットワーク制御装置
20 ユーザ要求部
31 下位レイヤネットワーク
32 上位レイヤネットワーク
40 レイヤ境界
101 ユーザ向けネットワークデータベース
101B、102B、103B、107B ポート情報
101C、102C、103C、107C リンク情報
101D、102D、103D、107D フロー情報
102 上位レイヤネットワークデータベース
102A、103A ノード情報
103 下位レイヤネットワークデータベース
104 上位階層制御部
105 上位レイヤ制御部
106 下位レイヤ制御部
107 潜在リンクデータベース
108 下位階層制御部
202 外部データベースアクセス部
203 潜在リンク情報管理部
204 レイヤ境界情報管理部
205 データベース情報間対応管理部
206 パス計算部
208 リソース需要予測部
209 容量設計部
301 パス計算スケジューラ
302 パス計算要求データベース
303 潜在リンク要求データベース
B501~B506 境界コネクション(リンク)
F701 要求されたフロー
F702 上位レイヤフロー
F703、F704 下位レイヤの設定されたフロー
L001、L002 上位レイヤリンク
L601~L603 下位レイヤリンク
L901~L903 潜在リンク
N11~N13、N21~N23 ノード
P301~P310、P401~P412 ポート
P801~P806 仮想ポート
Claims (10)
- 上位レイヤネットワークに接続するユーザのポート間を接続するために設定可能な上位仮想リンクの要求を受け付け、前記設定可能な上位仮想リンクの性能を求めるとともに関連付けて保持する上位階層制御手段と、
下位レイヤネットワークを介して前記上位レイヤネットワーク内のポート間を接続するために設定可能な下位仮想リンクの要求を受け付け、前記設定可能な下位仮想リンクの性能を求めるとともに関連付けて保持する下位階層制御手段と、を備え、
前記上位階層制御手段は、複数の前記設定可能な上位仮想リンクの要求の履歴に基づいて、将来の前記上位仮想リンクの要求を予測するリソース需要予測手段と、
予測した前記上位仮想リンクの要求に対して前記上位仮想リンクを供給するために必要な前記下位レイヤネットワークのリソースを算出する容量設計手段と、をさらに有し、
前記容量設計手段により算出された追加リソースに相当する、前記設定可能な下位仮想リンクを前記下位階層制御手段に要求し、
前記設定可能な上位仮想リンクおよび前記設定可能な上位リンクの性能に応じて選択された上位仮想リンクの要求を受け付け、要求された前記上位仮想リンクに対応するフローの経路に前記設定可能な下位仮想リンクが含まれる場合、前記下位階層制御手段に対して前記設定可能な下位仮想リンクを要求し、前記設定可能な下位仮想リンクに対応するフローを前記下位レイヤネットワークに設定する、
ことを特徴とする、ネットワーク制御装置。 - 前記設定可能な下位仮想リンクの性能は、前記設定可能な下位仮想リンクの帯域、遅延、信頼性、および、優先度のうちの少なくともいずれかを含む、
請求項1に記載のネットワーク制御装置。 - 前記下位階層制御手段は、前記上位レイヤネットワークと前記下位レイヤネットワークの間のレイヤ境界のトポロジ情報、および、前記下位レイヤネットワークのトポロジ情報に基づいて、前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求める、
請求項1または2に記載のネットワーク制御装置。 - 前記上位階層制御手段は、前記上位レイヤネットワークのトポロジ情報、および、前記設定可能な上位仮想リンクに基づいて、前記フローの経路を求める、
請求項1ないし3のいずれか1項に記載のネットワーク制御装置。 - 前記下位階層制御手段は、前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求めるとともに関連付けて保持する動作を、定期的に行う、
請求項1ないし4のいずれか1項に記載のネットワーク制御装置。 - 前記下位階層制御手段は、前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求めるともに関連付けて保持する動作を、前記上位レイヤネットワークおよび前記下位レイヤネットワークのうちの少なくともいずれかのネットワークの状態が変化した場合に行う、
請求項1ないし5のいずれか1項に記載のネットワーク制御装置。 - ネットワーク制御装置が、上位レイヤネットワークに接続するユーザのポート間を接続するために設定可能な上位仮想リンクの要求を受け付け、前記設定可能な上位仮想リンクの性能を求めるとともに関連付けて保持し、
下位レイヤネットワークを介して前記上位レイヤネットワーク内のポート間を接続するために設定可能な下位仮想リンクの要求を受け付け、前記設定可能な下位仮想リンクの性能を求めるとともに関連付けて保持し、
前記設定可能な上位仮想リンクおよび前記設定可能な上位リンクの性能に応じて選択された上位仮想リンクの要求を受け付け、
要求された前記上位仮想リンクに対応するフローの経路に前記設定可能な下位仮想リンクが含まれる場合、前記設定可能な下位仮想リンクに対応するフローを前記下位レイヤネットワークに設定し、
複数の前記設定可能な上位仮想リンクの要求の履歴に基づいて、将来の前記上位仮想リンクの要求を予測し、
予測した前記上位仮想リンクの要求に対して前記上位仮想リンクを供給するために必要な前記下位レイヤネットワークのリソースを算出する、
ことを特徴とする、ネットワーク制御方法。 - 前記設定可能な下位仮想リンクの性能は、前記設定可能な下位仮想リンクの帯域、遅延、信頼性、および、優先度のうちの少なくともいずれかを含む、
請求項7に記載のネットワーク制御方法。 - 前記ネットワーク制御装置は、前記上位レイヤネットワークと前記下位レイヤネットワークの間のレイヤ境界のトポロジ情報、および、前記下位レイヤネットワークのトポロジ情報に基づいて、前記設定可能な下位仮想リンクと前記設定可能な下位仮想リンクの性能を求める、
請求項7または8に記載のネットワーク制御方法。 - 上位レイヤネットワークに接続するユーザのポート間を接続するために設定可能な上位仮想リンクの要求を受け付け、前記設定可能な上位仮想リンクの性能を求めるとともに関連付けて保持する処理と、
下位レイヤネットワークを介して前記上位レイヤネットワーク内のポート間を接続するために設定可能な下位仮想リンクの要求を受け付け、前記設定可能な下位仮想リンクの性能を求めるとともに関連付けて保持する処理と、
前記設定可能な上位仮想リンクおよび前記設定可能な上位仮想リンクの性能に応じて選択された上位仮想リンクの要求を受け付ける処理と、
要求された前記上位仮想リンクに対応するフローの経路に前記設定可能な下位仮想リンクが含まれる場合、前記設定可能な下位仮想リンクに対応するフローを前記下位レイヤネットワークに設定する処理と、
複数の前記設定可能な上位仮想リンクの要求の履歴に基づいて、将来の前記上位仮想リンクの要求を予測する処理と、
予測した前記上位仮想リンクの要求に対して前記上位仮想リンクを供給するために必要な前記下位レイヤネットワークのリソースを算出する処理と、をコンピュータに実行させる、
ことを特徴とするプログラムの記録媒体。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP16761286.0A EP3267635B1 (en) | 2015-03-06 | 2016-03-03 | Network control device, network control method, and recording medium for program |
RU2017135251A RU2683850C1 (ru) | 2015-03-06 | 2016-03-03 | Устройство управления сетью, способ управления сетью и носитель записи для программы |
JP2017504860A JP6699654B2 (ja) | 2015-03-06 | 2016-03-03 | ネットワーク制御装置、ネットワーク制御方法、および、プログラム |
US15/555,615 US10237202B2 (en) | 2015-03-06 | 2016-03-03 | Network control device, network control method, and recording medium for program |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2015-044738 | 2015-03-06 | ||
JP2015044738 | 2015-03-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016143311A1 true WO2016143311A1 (ja) | 2016-09-15 |
Family
ID=56879465
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2016/001151 WO2016143311A1 (ja) | 2015-03-06 | 2016-03-03 | ネットワーク制御装置、ネットワーク制御方法、および、プログラムの記録媒体 |
Country Status (5)
Country | Link |
---|---|
US (1) | US10237202B2 (ja) |
EP (1) | EP3267635B1 (ja) |
JP (1) | JP6699654B2 (ja) |
RU (1) | RU2683850C1 (ja) |
WO (1) | WO2016143311A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019065353A1 (ja) * | 2017-09-28 | 2019-04-04 | 日本電気株式会社 | 制御装置、通信システム、通信方法 |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108984102B (zh) * | 2017-06-02 | 2021-06-22 | 伊姆西Ip控股有限责任公司 | 管理存储系统的方法、系统和计算机程序产品 |
WO2019159234A1 (en) * | 2018-02-13 | 2019-08-22 | Nec Corporation | Information processing apparatuses, method, program and non-transitory computer readable recording medium |
CN110635931B (zh) * | 2018-06-22 | 2021-05-14 | 华为技术有限公司 | 链路组配置方法和装置 |
US11663504B2 (en) * | 2019-11-01 | 2023-05-30 | EMC IP Holding Company LLC | Method and system for predicting resource reallocation in a resource pool |
CN110932968B (zh) * | 2019-11-18 | 2021-05-14 | 华南理工大学 | 一种流量转发方法及装置 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014054691A1 (ja) * | 2012-10-03 | 2014-04-10 | 日本電気株式会社 | 通信システム、制御装置、制御方法及びプログラム |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6400681B1 (en) | 1996-06-20 | 2002-06-04 | Cisco Technology, Inc. | Method and system for minimizing the connection set up time in high speed packet switching networks |
US20020116485A1 (en) * | 2001-02-21 | 2002-08-22 | Equipe Communications Corporation | Out-of-band network management channels |
US7225244B2 (en) * | 2000-05-20 | 2007-05-29 | Ciena Corporation | Common command interface |
US7693976B2 (en) * | 2000-07-11 | 2010-04-06 | Ciena Corporation | Granular management of network resources |
US7263597B2 (en) * | 2001-04-19 | 2007-08-28 | Ciena Corporation | Network device including dedicated resources control plane |
JP3714329B2 (ja) | 2002-01-22 | 2005-11-09 | 日本電信電話株式会社 | 可変容量リンク装置及び可変容量リンク設定方法 |
US7889675B2 (en) | 2003-01-31 | 2011-02-15 | Tellabs Operations, Inc. | Method and system for multi-layer network routing |
JP3895360B2 (ja) | 2003-02-03 | 2007-03-22 | 日本電信電話株式会社 | 光ネットワーク、光エッジルータ及びそのプログラム |
WO2004081730A2 (en) * | 2003-03-07 | 2004-09-23 | Netnostics, Inc. | Network architecture |
GB0407336D0 (en) | 2004-03-31 | 2004-05-05 | British Telecomm | Pathfinding system |
JP4283736B2 (ja) | 2004-06-25 | 2009-06-24 | 日本電信電話株式会社 | トラヒック情報処理方法、トラヒック情報処理プログラム、および、トラヒック情報処理装置 |
US7903557B1 (en) | 2005-09-21 | 2011-03-08 | Qlogic, Corporation | Multipathing using multiple endpoint addresses for load balancing in a network |
JP4621220B2 (ja) | 2007-02-27 | 2011-01-26 | 日本電信電話株式会社 | 仮想トポロジ設計装置および仮想トポロジ設計方法 |
CN101741538B (zh) * | 2008-11-13 | 2013-01-16 | 中兴通讯股份有限公司 | 同步调度方法 |
EP2403290B1 (en) * | 2010-07-02 | 2013-09-11 | Vodafone IP Licensing limited | Radio resource management based on location prediction |
JPWO2015059917A1 (ja) * | 2013-10-21 | 2017-03-09 | 日本電気株式会社 | マルチレイヤネットワーク制御方法および装置 |
-
2016
- 2016-03-03 RU RU2017135251A patent/RU2683850C1/ru active
- 2016-03-03 JP JP2017504860A patent/JP6699654B2/ja active Active
- 2016-03-03 EP EP16761286.0A patent/EP3267635B1/en active Active
- 2016-03-03 WO PCT/JP2016/001151 patent/WO2016143311A1/ja active Application Filing
- 2016-03-03 US US15/555,615 patent/US10237202B2/en active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014054691A1 (ja) * | 2012-10-03 | 2014-04-10 | 日本電気株式会社 | 通信システム、制御装置、制御方法及びプログラム |
Non-Patent Citations (3)
Title |
---|
See also references of EP3267635A4 * |
YOHEI IIZAWA ET AL.: "Dynamic Multi-layer Path Control Using Virtual Links", PROCEEDINGS OF THE 2014 IEICE GENERAL CONFERENCE TSUSHIN 2, 21 March 2014 (2014-03-21), pages 162 * |
YOHEI IIZAWA ET AL.: "ICT System o Kodoka suru SDN Tokushu Heterogeneous-mo Togo Seigyo Kiban o Jitsugen suru Multilayer Chushoka Gijutsu", NEC TECHNICAL JOURNAL, vol. 66, no. 2, 1 February 2014 (2014-02-01), pages 44 - 47 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019065353A1 (ja) * | 2017-09-28 | 2019-04-04 | 日本電気株式会社 | 制御装置、通信システム、通信方法 |
Also Published As
Publication number | Publication date |
---|---|
RU2683850C1 (ru) | 2019-04-02 |
JP6699654B2 (ja) | 2020-05-27 |
EP3267635B1 (en) | 2020-10-21 |
EP3267635A4 (en) | 2018-08-22 |
JPWO2016143311A1 (ja) | 2017-12-14 |
US20180083890A1 (en) | 2018-03-22 |
EP3267635A1 (en) | 2018-01-10 |
US10237202B2 (en) | 2019-03-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6699654B2 (ja) | ネットワーク制御装置、ネットワーク制御方法、および、プログラム | |
CN109039884B (zh) | 网络路径预测和选择的方法、设备和介质 | |
US10374956B1 (en) | Managing a hierarchical network | |
JP6393773B2 (ja) | Ipネットワークにおける部分ソフトウェア定義ネットワークのスイッチ置換 | |
US10511524B2 (en) | Controller communications in access networks | |
Guo et al. | Shared backup network provision for virtual network embedding | |
US9461877B1 (en) | Aggregating network resource allocation information and network resource configuration information | |
JP2005312048A (ja) | ネットワークトラフィックを管理する方法、システム及び論理装置 | |
EP2577919B1 (en) | Reducing network power consumption | |
JP2013191942A (ja) | パス計算方法 | |
JP6733655B2 (ja) | ネットワーク制御装置、ネットワーク制御方法、および、プログラム | |
US20230164071A1 (en) | Multi-tier deterministic networking | |
US11706146B1 (en) | Directing network traffic using local routing decisions with a global overview | |
WO2015059917A1 (ja) | マルチレイヤネットワーク制御方法および装置 | |
US10630563B2 (en) | Application-driven cross-stratum resource monitoring | |
EP3136649A1 (en) | Method and system for providing load information of an optical data transmission system | |
CN112217651B (zh) | 融合网络的路径标签确定方法及装置 | |
EP3284225B1 (en) | A configuration system for configuring the control-plane of a software-defined network | |
JP2002247087A (ja) | Ipネットワーク負荷分散方法、ipネットワーク、ipルーティング装置及びルートサーバ装置 | |
JP6384481B2 (ja) | ネットワーク設計支援装置、ネットワーク設計方法及びプログラム | |
EP2437441B1 (en) | A method for generating a look-up table for retrieving data rates for a data transmission connection | |
JP6269238B2 (ja) | ネットワーク管理方法、ネットワーク管理システム、およびネットワーク管理装置 | |
JP2012156626A (ja) | 管理装置、通信システム、通信方法、および通信プログラム | |
JP2008278007A (ja) | グループパス予約制御方法及び経路予約装置及びシステム及びプログラム | |
JP4280230B2 (ja) | 経路計算指示方法、計算指示プログラム、および、計算指示装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16761286 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2017504860 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15555615 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2016761286 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2017135251 Country of ref document: RU |