JP5039674B2 - Network system and QoS guarantee method - Google Patents

Description

  The present invention relates to a network system in a packet switched network, and more particularly to a QoS guarantee technique.

  In the prior art, the QoS (Quality of Service) of an IP (Internet Protocol) network has been compensated mainly based on a prior prediction of traffic. In a large-scale IP network, it is difficult to guarantee QoS for each type of flow as has been done in ATM (Asynchronous Transfer Mode), that is, for each type of traffic from a specific start point to a specific end point. Differentiated services (DiffServes) for each class, which summarizes flows, have been performed based on the Internet Engineering Task Force (IETF) standard. In the DiffServ framework, a condition to be guaranteed is usually given as a policy to a QoS policy server (also called a band width broker), and the QoS policy server manages the given policy.

  However, at present, a telephone service is provided using an IP network, and a moving image streaming service and a video conference service are becoming widespread. The service described above requires real-time characteristics. Therefore, in the next generation network (NGN), in order to guarantee the above-described service, it is necessary to guarantee the delay and the jitter as well as the bandwidth between the end points, that is, between the terminals.

  In order to cope with such a situation, a QoS guarantee technique based on traffic measurement has been developed. Specifically, there are the following.

  RMON (Remote network MONITORING MIB) is an MIB (Management Information Base) that holds traffic measurement results, and its version 2 is standardized (see, for example, Non-Patent Document 1). The contents of the RMON must be pulled (polled) by the transport control server (or agent) using SNMP (Simple Network Management Protocol). In the method described above, it is difficult to reflect information from all packets in the measurement result.

  NetFlow is a protocol developed by Cisco (see Non-Patent Document 2, for example). When NetFlow is used, information of all packets can be acquired for each micro flow or macro flow, and information of packets sampled at a constant interval can be acquired by UDP.

  If the NetFlow protocol is used, the acquired information can be pushed (reported) to the QoS control server as it is, but the collected information can also be pushed according to a predetermined method. Two versions of NetFlow, Version 5 and Version 9, are often used by router vendors other than Cisco. The specification of data used in NetFlow is described in Non-Patent Document 2, but this is not an IETF standard but an information providing RFC.

  IPFIX (IP Flow Information Export) has been standardized as a successor protocol to NetFlow, but the content of measurement / report is basically the same as NetFlow (for example, see Non-Patent Document 3).

  sFlow is a protocol developed by InMon, and can acquire information on all packets or sampled packets by UDP as in NetFlow (see, for example, Non-Patent Document 4 and Non-Patent Document 5).

  However, unlike NetFlow, there is no information acquisition and aggregation function in units of macro flows (limited to units of micro flows). By selecting an appropriate one of these traffic measurement techniques and using the selected one, it is possible to verify whether or not the designated QoS policy is satisfied.

As another QoS guarantee technology, there is a traffic measurement technology for optimizing the sampling rate when traffic measurement is performed for each network device and identifying abnormal traffic (for example, see Patent Document 1). Further, there is a method in which traffic measurement is performed on a link basis, a flow rate for each user is calculated with reference to packet header information, and a quality degradation degree is obtained based on the flow rate (for example, see Patent Document 2).
Waldbusser, S., "RemoteNetworkMonitoringManagementInformationBase", RFC2819, IETF, May2000. Claise, B., Ed., "CiscoSystemsNetFlowServicesExportVersion9", RFC3954, IETF, October2004. Claise, B. Ed., "SpecificationoftheIPFlowInformationExport (IPFIX) ProtocolfortheExchangeofIPTrafficFlowInformation", RFC5101, IETF, January2008. Phaal, P., Panchen, S., andMcKee, N., "InMonCorporation'ssFlow: AMethodforMonitoringTrafficinSwitchedandRoutedNetworks", RFC3176, IETF, September2001. Phaal, P. and Lavine, M., "sFlowVersion5", sFlow.org, July 2004. JP 2005-286684 A Japanese Patent Laying-Open No. 2005-072907

  The purpose of the present invention is to provide per-class of traffic from network entry to exit or from one endpoint or network area to another endpoint or network area for QoS assurance and other traffic condition understanding and control. It is to grasp traffic (hereinafter referred to as macro flow) and control traffic for each grasped macro flow.

  For example, in the management of the core network, it is necessary to determine and control the traffic amount of a path from a specific ingress edge router to a specific egress edge router in order to guarantee QoS. Alternatively, it is necessary to determine and control the amount of traffic from the first network to the second network of a specific user directly or indirectly connected to the core network.

  In order to perform the above-described control flexibly, it is necessary to obtain the traffic amount by measuring traffic.

  However, in order to perform traffic measurement and measurement result processing as described above, there are the following two problems.

  The first problem is to identify an edge node or endpoint or network area based on the traffic measurement result of a specific ingress edge node and egress edge node, and identify the identified edge node or identified end point or identification Based on the determined network area, the result of traffic measurement is aggregated for each macro flow.

  In traffic measurement, since measurement is not performed in units of sections necessary for QoS guarantee and other traffic condition grasping and control, it is necessary to aggregate measurement results for each macro flow. However, in IPFIX or NetFlow, the results measured for each part of the interval unit necessary for grasping and controlling QoS and other traffic conditions are transmitted. Even if they are added, the traffic volume for each macro flow cannot be obtained.

  The second problem is to reduce the overhead of traffic measurement and transmission / reception of measurement results as described above. Traffic measurement and transmission of measurement results imposes a load on the edge node. The reception of the measurement result places a load on the resource management server. In particular, when the number of flows to be measured becomes enormous, the storage amount of the edge node increases for information aggregation, and the communication amount from the edge node to the resource management server increases. Therefore, it is necessary to reduce the load as described above in order to ensure performance and scalability.

  The present invention solves the above-mentioned two problems and provides a method for controlling traffic for each traffic class from the entrance to the exit of a network or from one end point or network area to another end point or network area.

A typical example of the present invention is as follows. That is, a network system comprising a plurality of networks, a plurality of network devices connected to the network, and a management server that controls traffic flowing through a network path composed of the networks and the network devices, management server, determines a connection storing unit that manages information about the connection between the plurality of networks and the plurality of network devices, said network device as a starting point the traffic is measured, and said network device comprising an end point The determined storage unit and the connection storage unit, and the determined one of the plurality of traffics flowing through the network path connecting the determined network device serving as the start point and the determined network device serving as the end point. The starting network Extraction that extracts characteristics of traffic flowing between a first network device connected to the network via a device and a second network device connected to the network via the determined network device An instruction unit that transmits request information including a measurement condition for measuring the traffic based on the extracted traffic characteristics, and the determined starting point based on the extracted traffic characteristics An aggregation unit that summarizes the measurement results of the plurality of traffic flowing through the network path that connects the network device to be determined and the network device that is the determined end point for each traffic including common information; and based on the traffic measurement result, to control the traffic control Comprising a part, wherein the extraction unit refers to the connection memory unit, based on the information about the connection between the determined start point and becomes a network device and the first network device, which is the determined Information on connection between the network device serving as the determined end point and the second network device is determined by determining entrance feature information that is a feature of the traffic in the network device serving as the start point and referring to the connection storage unit And determining the egress feature information that is the feature of the traffic in the network device that is the determined end point, and the instruction unit becomes the determined start point based on the determined ingress feature information A first measurement condition of the traffic to be measured by the network device is determined, and the request information including the first measurement condition is A second measurement condition of the traffic information to be transmitted to the network device serving as the determined start point and to be measured by the network device serving as the determined end point based on the extracted exit feature information; The request information including the second measurement condition is transmitted to the network device serving as the determined end point .

  According to the present invention, traffic measurement results can be aggregated for each macro flow, and traffic measurement results of a specific traffic class passing through a specific ingress edge node and a specific egress edge router can be obtained. Moreover, the overhead which generate | occur | produces by traffic measurement and transmission / reception of a measurement result can be reduced.

  First, the outline | summary of the 1st Embodiment of this invention is demonstrated.

  The present invention collects and manages routing information indicating which resource management server 131 (see FIG. 1) is directly or indirectly connected from which edge router (see FIG. 1) to which address range or AS (Autonomous System) network. However, it holds data related to the measurement object including the macro flow identification information.

  The resource management server 131 (see FIG. 1) determines the traffic characteristics that can be detected from the packet that traffic between a specific ingress edge router and egress edge router has based on the routing information, and determines the determined traffic characteristics. Direct traffic measurement and measurement information reporting based on it.

  The ingress edge router and egress edge router aggregate the packet information based on the instructed characteristics, and transmit the result to the resource management server 131.

  Specifically, the resource management server 131 refers to the routing information, and from the connection information between the core network and the external network, for each traffic class, characteristic information that characterizes the traffic class with a small number of characteristics. Based on the determined feature information, an aggregation method of measurement results having a high degree of aggregation is obtained, and an entry edge router and an exit edge router are instructed.

  The ingress edge router and egress edge router perform traffic measurement according to the instructed aggregation method and report the measurement result. The resource management server 131 obtains the traffic amount averaged in the time direction and interpolated / extrapolated for each reported measurement result, and obtains the target traffic amount by adding the traffic amount for each traffic class.

  As a result, the traffic amount for each specific ingress edge router and specific egress edge router can be obtained. In addition, since the traffic class is characterized by a small number of features, the flow aggregation unit can be increased, and the load on the edge router can be reduced.

  Further, an amount that can be added is obtained from the measurement result, and the traffic amount for each traffic class can be obtained by adding the obtained amounts.

  A first embodiment of the present invention will be described.

  FIG. 1 is a block diagram showing a network configuration and a system configuration in the first embodiment of the present invention.

  Edge routers 111, 112, and 113 are connected to the core network 125. Each edge router may be a switch.

  When the edge routers 111, 112, and 113 are not particularly distinguished, they are described as edge routers 111, 112, and 113.

  When the core network 125 includes one or a plurality of core nodes, the edge routers 111, 112, and 113 are connected to the core nodes or are connected by edge routers.

  Further, the core network 125 does not include a core node, and the edge routers 111, 112, and 113 can be connected to each other.

  In FIG. 1, the IP address of the edge router 111 is 10.10.11.1, and a network 121 with an AS number of 11 is passed through a link connected to the network interface 114 with an interface number of 1. It is connected to the. The network 121 may be a single access network, or may be connected to the access network via a backbone and a core network of a carrier different from the core network 125. The network 121 is assigned a subnet address with an address of 10.10.0.21.0 / 24, that is, an address range of 10.10.21.1 to 10.10.12.255.

  The edge router 111 is connected to the network 124 having the AS number 11 via a link connected to the network interface 115 having the interface number 2. The network 124 may be a single access network, or may be connected to the access network via a backbone and a core network of a carrier different from the core network 125. The network 124 is assigned a subnet address with an address of 10.10.20.4.0 / 24, that is, an address range of 10.10.0.24.1 to 10.10.24.255.

  The IP address of the edge router 112 is 10.10.10.1 and is connected to a network 122 having an AS number of 12 via a link connected to the network interface 116 having an interface number of 1. The network 122 may be a single access network, or may be connected to the access network via a backbone or a core network of a carrier different from the core network 125. The network 122 is assigned a subnet address with an address of 10.10.22.0/24, that is, an address range of 10.10.22.1 to 10.10.22.255.

  The IP address of the edge router 113 is 10.10.10.1 and is connected to the network 123 whose AS number is 13 via a link connected to the network interface 117 having the interface number 1. The network 123 may be a single access network, or may be connected to the access network via a backbone and a core network of a carrier different from the core network 125. The network 123 is assigned a subnet address with an address of 10.10.223.0/24, that is, an address range of 10.10.23.1 to 10.10.23.255.

  A resource management server 131 is connected to the edge router 111. A management terminal 132 is connected to the resource management server 131.

  The resource management server 131 includes a measurement target management unit 133, a network connection DB 135, a traffic feature extraction unit 136, a collection information instruction unit 137, a traffic information analysis unit 138, and a router setting unit 139 as programs, and the measurement target DB 134 as data. A network connection DB 135 is provided. The configuration described above will be described later. The resource management server 131 may be directly connected to the edge router 111 or may be indirectly connected.

  FIG. 2 is a diagram illustrating an example of the measurement target DB 134 according to the first embodiment of this invention.

  The measurement target DB 134 manages policies and measurement results for each macro flow input from the management terminal 132 or input by another method. Here, the policy describes a traffic condition to be satisfied by the macro flow. In FIG. 2, the traffic condition is that the bandwidth does not exceed a specific value.

  Specifically, the measurement management target DB 134 manages the ID 201, the input edge router 202, the start point 203, the egress edge router 204, the end point 205, the class 206, the reserved bandwidth 206, the ingress real bandwidth 207, and the egress real bandwidth 208. .

  The ID 201 stores an identifier for specifying data managed by the measurement management target DB 134. The input edge router 202 stores an IP address for specifying an edge router to which a flow is input. The start point 203 stores an AS number or a subnet address for specifying a network to which a flow is input. The egress edge router 204 stores an IP address for specifying the edge router to which the flow is output. The end point 205 stores an AS number or a subnet address for specifying a network to which a flow is output. Class 206 stores the DiffServ class of the flow. The reserved bandwidth 206 stores a bandwidth set by the management terminal 132. The actual entrance bandwidth 207 stores the actual entrance bandwidth of the target flow calculated based on the traffic measurement result transmitted from the entrance edge router. The egress real bandwidth 208 stores the egress real bandwidth of the target flow calculated based on the traffic measurement result transmitted from the egress edge router. Traffic measurement and transmission / reception of measurement results will be described later with reference to FIGS. 6A, 6B, 7, 8, and 9. FIG.

  In the measurement target data 211, the ID 201 is P00011, and the IP1 address 0.10.11.1, that is, the edge router 111 is designated as the ingress edge router 202. “% 1” indicates that the interface number of the connected network interface is 1, that is, the interface 114. The starting point 203 is not specified. As the egress edge router 204, the IP address 10.10.12.1, that is, the edge router 112 is designated. The network interface of the egress edge router 204 is not specified, but only one interface is connected to the outside. The end point 205 is not specified. EF (Expanded Forwarding) is specified as class 206 (PHB, Per-Hop Behavior). This indicates that this macro flow is traffic to be prioritized such as voice traffic. Also, 1.0 Gbps is designated as the reserved bandwidth 207.

  In the measurement target data 212, the ID 201 is P00012, and the IP address 10.10.11.1, that is, the edge router 111 is designated as the ingress edge router 202. The start point 203 is designated with an AS number of 11. As the egress edge router 204, the IP address 10.10.10.1, that is, the edge router 112 is designated. The network interface of the egress edge router 204 is not specified. The end point 205 of the macro flow is not specified. AF2 (Assured Forwarding 1) is designated as the class 206. Further, 3.0 Gbps is designated as the reserved bandwidth 207.

  In the measurement target data 213, the ID 201 is P00021, and the IP address 10.10.11.1, that is, the edge router 111 is designated as the ingress edge router 202. “% 2” indicates that the interface number of the connected network interface is 2, that is, the interface 115. The starting point 203 is not specified. As the egress edge router 204, the IP address 10.10.10.1, that is, the edge router 112 is designated. The end point 205 is designated with an AS number of 13. AF1 (Assured Forwarding 1) is designated as the class 206. In addition, 2.0 Gbps is designated as the reserved bandwidth 207.

  In the measurement target data 214, the ID 201 is P00022, and the IP address 10.10.11.1, that is, the edge router 111 is designated as the ingress edge router 202. The start point 203 is designated with an AS number of 12. As the egress edge router 204, the IP address 10.10.3.1, that is, the edge router 113 is designated. The end point 205 is designated with an AS number of 13. AF1 (Assured Forwarding 1) is designated as the class 206. Also, 1.0 Gbps is designated as the reserved bandwidth 207.

  In the measurement target data 215, the ID 201 is P00031, and the entrance edge router 202 is not specified. The starting point 203 is designated as 10.124.0 / 24 as a subnet address. The egress edge router 204 is not designated. The end point 204 is designated as 10.11.23.0/24 as a subnet address. EF (Expected Forwarding) is specified as the class 206. Also, 1.0 Gbps is designated as the reserved bandwidth 207.

  In addition, when not distinguishing each measurement object data, it describes as measurement object data 211, 212, 213, 214, 215.

  FIG. 3 is an explanatory diagram illustrating the flow of the measurement target data 211, 212, 213, 214, and 215 in FIG.

  The measurement target data 211 is applied to a flow from the network 121 to the network 122 via the core network 125 as in the flow 311.

  The measurement target data 212 is applied to a flow from the network 121 to the network 122 via the core network 125 as in the flow 312.

  The measurement target data 213 is applied to a flow from the network 124 to the network 122 via the core network 125 as in the flow 313.

  The measurement target data 214 is applied to a flow from the network 124 to the network 123 via the core network 125 as in a flow 314.

  The measurement target data 215 is applied to a flow from the network 124 to the network 123 via the core network 125 as in a flow 315.

  FIG. 4 is a diagram illustrating an example of the network connection DB 135 according to the first embodiment of this invention.

  The network connection DB 135 manages an end point address 401, an end point AS 402, a gateway 403, and an interface 404.

  The end point address 401 stores an address for specifying the subnet address on the end point side of the flow. The end point AS 402 stores an AS number for specifying the network on the end point side of the flow. The gateway 403 stores an IP address for specifying the edge router on the end point side of the flow. The interface 404 stores an interface number for specifying the interface of the edge router on the end point side of the flow.

  The record 411 has an end address (subnet address) of 10.10.21.0/24 from the core network 125 and an IP address of 10.10. 11 shows that the gateway of 11.1, that is, the interface of interface number 1 of the edge router 111 is routed.

  The record 412 has an end point address (subnet address) of 10.10.4.0/24 from the core network 125, and an IP address of 10.10. It shows that the gateway of 11.1 is passed, that is, the interface of interface number 2 of the edge router 111 is passed.

  The record 413 has an IP address of 10.10.10 in order to reach the network whose end address (subnet address) is 10.10.2.02.0 / 24 from the core network 125 and whose end AS number is 12. It shows that the gateway of 12.1 is passed through the interface of interface number 1 of the edge router 112.

  The record 414 has an IP address of 10.10.13 in order to reach the network having the end point address (subnet address) of 10.10.23.0.24 and the end point AS number of 13 from the core network 125. .1 gateway, that is, the interface of interface number 1 of the edge router 113.

  Although the contents stored in the network connection DB 135 can be input by a network administrator or the like, it is desirable to automatically store the information collected by the network management system by a program in order to make a mistake.

  FIG. 5 shows an instruction of measurement from the resource management server 131 to each edge router and reporting of the measurement result in the first embodiment of the present invention, and correspondingly, periodically from each edge router to the resource management server 131. It is a figure which shows the sequence of the measurement result transmitted to.

  When the resource management server 131 transmits the collection information instruction 501 to the edge router 111, a response 502 is transmitted from the edge router 111. When the resource management server 131 transmits the collection information instruction 503 to the edge router 112, a response 504 is transmitted from the edge router 112. When the resource management server 131 transmits the collection information instruction 505 to the edge router 113, a response 506 is transmitted from the edge router 112.

  Thereafter, the edge router 111 periodically transmits the measurement result 511 and the measurement result 521 to the resource management server 131, and the edge router 112 periodically transmits the measurement result 512 and the measurement result 522 to the resource management server 131. 113 periodically transmits the measurement result 513 and the measurement result 523 to the resource management server 131.

  Hereinafter, specific processing of the first exemplary embodiment of the present invention will be described. Specific processing includes processing when a policy is received from the management terminal 132 and processing when a measurement result is received from each edge router.

  FIG. 6A is a flowchart showing a process 601 of the resource management server 131 when a policy is received from the management terminal 132 according to the first embodiment of this invention.

  In step 602, the resource management server 131 that has received the policy from the management terminal 132 activates the measurement target management unit 133, and the measurement target management unit 133 stores the measurement target data for each macro flow in the measurement target data DB 139.

  In step 603, the resource management server 131 activates the router setting unit 139, and the router setting unit 139 sets measurement target data in each edge router. The measurement target data to be set can be set for policing (band limitation) for the ingress interface for each macro flow, and for queuing and scheduling for each queue at the egress interface. Note that only one of the settings described above can be set, or both can be set.

  For example, regarding the measurement target data 211, when the total amount of traffic having DSCP corresponding to the EF class at the entrance interface 1 of the entrance edge router exceeds 1.0 Gbps, the entrance edge router discards the excess packets. That is, it is set to perform policing.

  When the resource management server 131 knows the traffic volume for each session (micro flow) by SIP signaling at the start of the session, the individual traffic volume is set for each session so that the total traffic volume is 1.0 Gbps or less. It is also possible to specify. When set as described above, if the total amount of traffic exceeds 1.0 Gbps, session start is rejected when the next session is started. That is, admission control can be performed.

  In the measurement target data 211, since an EF class that is a traffic class to be preferentially controlled in the exit interface is specified in the class 206, a priority control type queue is assigned to the exit interface.

  Further, the measurement target data 213 and the measurement target data 214 indicate that the traffic having the DSCP corresponding to the AF1 class is transmitted to the scheduler of the egress interface (interface connected to the core network) of the ingress edge router. (For example, a queue scheduled by CBWFQ (Class-Based Weighted Fair Queueing) scheduling) is assigned, and the total bandwidth reserved in at least the measurement target data 213 and the measurement target data 214 is 5.0 Gbps or more for the queue. Set to pass traffic. For example, in the router GR4000 of Hitachi, it is possible to set at least what percentage of the interface output band to be assigned to a specific class by the QoS-queue-list command in the CLI, so the output band (link capacity) If it is 10 Gbps, it may be set to allocate 50%.

  In step 604, the traffic feature extraction unit 136 extracts traffic features for all macro flows. Details of this step will be described later with reference to FIG.

  In step 605, the collection information instruction unit 137 instructs each edge router to measure and report the measurement result based on the extracted traffic characteristics. Details of this step will be described later with reference to FIG.

  By step 605, overhead due to traffic measurement and transmission / reception of measurement results is reduced, and Problem 2 can be solved. Note that the problem 1 can be solved by omitting the step 605 and instructing each edge router in advance to perform fixed measurement and report of the measurement result.

  Next, processing when a measured traffic measurement result is received from each edge router will be described.

  FIG. 6B is a flowchart illustrating a process 611 when a traffic measurement measurement result is received from each edge router in the first embodiment of this invention.

  In step 612, the resource management server 131 that has received the traffic measurement result from each edge router activates the traffic information analysis unit 138, and the traffic information analysis unit 138 measures traffic based on the traffic characteristics extracted in step 604. The results are aggregated for each target flow. Furthermore, the traffic information analysis unit 138 transmits the actual bandwidth values at the ingress edge router and the egress edge router to the measurement target management unit 133 regarding the traffic measurement results aggregated for each target flow. Details of this step will be described later with reference to FIG.

  In step 613, the measurement target management unit 133 stores the received actual bandwidth values at the ingress edge router and the egress edge router in the actual entrance bandwidth 207 and the actual exit bandwidth 208 of the measurement target DB 134 for each macro flow. The stored actual entrance band 207 and actual exit band 208 are compared with the reserved band 208. As a result of the comparison, either the entrance real band 207 or the exit real band 208 is a value that exceeds the reserved band 208 or approaches the value of the reserved band 208 (for example, reaches 80% of the reserved band). ), A warning message is output to the management terminal 132 to prompt the operator to change the setting. The operator is a person who operates the management terminal 132.

  Based on the above-described message, the operator may change the traffic path by changing the policy or changing the setting of MPLS (Multi-Protocol Label Switching) or the like, so that the bandwidth can be increased. The processing when the traffic measurement result measured from each edge router is received is completed.

  FIG. 7 is a flow chart showing processing for extracting traffic features in step 604 according to the first embodiment of this invention. The following processing is repeatedly executed for each target macro flow.

  In step 701, if there is an undetermined entry edge router through which the target macro flow passes and its interface, the undetermined one is obtained by referring to the network connection DB 135. That is, the network connection DB 135 is searched using the information on the start point of the target macro flow as a search key, the gateway and the interface are obtained, and the obtained gateway and interface are stored in the entry edge 202 of the target macro flow.

  For example, in the measurement target data 211, since both the IP address and interface of the ingress edge router 202 are designated, the above-described processing is not necessary.

  In the measurement target data 212, since the IP address of the ingress edge router is designated as 10.10.11.1, it can be seen that it is the edge router 111, but the interface is not designated. However, since the start point 203 has an AS number of 11, when the resource management server 131 searches the network connection DB 135, it matches the end point AS 402 of the record 411, and thus it can be seen that the interface is 1.

  In the measurement target data 215, since the subnet address of the start point 203 is designated as 10.124.0 / 24, when the resource management server 131 searches the network connection DB 135 using this as a search key, the end point of the record 412 It can be seen that the addresses 401 match, so the ingress edge router 202 is the edge router 111 and the interface is 2. It can also be seen that the AS number is 11.

  In step 702, if there is an undetermined egress edge router and its interface through which the target macro flow passes, the network connection DB 135 is referred to determine the undetermined one. That is, the network connection DB 135 is searched using the information on the end point of the target macro flow as a search key, the gateway and the interface are obtained, and the obtained gateway and interface are stored in the exit edge 203 of the target macro flow.

  In the measurement target data 211, since the egress edge router is designated as 10.10.12.11, it can be seen that it is the edge router 112, but the interface is not designated. However, since the edge router 112 has only one interface connected to the outside, it can be seen that the interface is 1. The same applies to the measurement target data 212.

  With respect to the measurement target data 215, since the end point subnet address is designated as 10.11.23.0/24, when the resource management server 131 searches the network connection DB 135 using this as a search key, the end point address of the record 414 401 matches, so it can be seen that the ingress edge router is 10.10.3.1, or edge router 111 and the interface is 1. It can also be seen that the AS number is 13.

  In step 703, the traffic feature extraction unit 136 determines entrance feature information using the ingress edge router and interface information obtained in step 701.

  Specifically, first, all traffic passing through the ingress edge router satisfies the conditions of the start point AS number and the start point IP address / subnet address specified in the target macro flow, and the other traffic If the above condition is not satisfied, the traffic feature extraction unit 136 determines the entrance feature information as “entrance edge router identifier”.

  The measurement target data 211, 212, 213, 214, and 215 do not satisfy this condition because the ingress edge router 202 is all the edge router 111 and is not characterized even if only the ingress edge router 202 is specified.

  Second, all traffic passing through a specific interface (i) of the ingress edge router satisfies the conditions of the start point AS number and start point IP address / subnet address specified in the target macro flow, and other traffic When the above-described conditions are not satisfied, the traffic feature extraction unit 136 determines the entrance feature information as [entrance edge router identifier% i].

  All the entrance feature information of each measurement target data 211, 212, 213, 214, 215 is determined by the entrance feature information described above. Specifically, [10.10.11.1% 1] is determined for the measurement target data 211 and 212, and the measurement target data 213, 214, and 215 is [10.10.11.1% 2]. Is determined.

  Third, traffic having one designated start AS number a passing through the ingress edge router satisfies the condition of the start IP address / subnet address in the target macro flow, and the other traffic does not satisfy the condition In this case, the traffic feature extraction unit 136 determines the entrance feature information as [ingress edge router identifier, a].

  Fourth, traffic having a designated one source IP address / subnet address p passing through the ingress edge router satisfies the condition of the source AS number in the target macro flow, and other traffic satisfies the condition. If there is not, the traffic feature extraction unit 136 determines the entrance feature information as [entrance edge router identifier, p].

  Fifth, in cases other than those described above (the interface, the origin AS number and the origin IP address / subnet address set are (i1, a1, p1), (i2, a2, p2),...), The traffic feature extraction unit 136 determines the ingress feature information as [ingress edge router identifier, ((% i, i2, a2, p2),...]].

  In step 704, the traffic feature extraction unit 136 determines egress feature information using the egress edge router and interface information obtained in step 702.

  Specifically, first, all traffic passing through the egress edge router satisfies the conditions of the destination AS number and the destination IP address / subnet address specified in the target macro flow, and the other traffic satisfies the conditions. If not, the traffic feature extraction unit 136 determines the exit feature information to be [egress edge router identifier].

  All the exit characteristic information of each measurement target data 211, 212, 213, 214, 215 is determined. Specifically, the measurement target data 211, 212, and 213 are determined as [10.10.12.1], and the measurement target data 214 and 215 are determined as [10.10.13.1].

  Second, all the traffic passing through the specific interface (i) of the egress edge router satisfies the conditions of the destination AS number and the destination IP address / subnet address specified in the target macro flow, and other traffic When the condition is not satisfied, the traffic feature extraction unit 136 determines the exit feature information as [egress edge router identifier% i].

  Third, traffic having a designated start AS number a passing through the egress edge router satisfies the condition of the destination IP address / subnet address in the target macro flow, and the other traffic does not satisfy the condition In this case, the traffic feature extraction unit 136 determines the exit feature information as [egress edge router identifier, a].

  Fourth, traffic having one designated start point IP address / subnet address p passing through the egress edge router satisfies the condition of the destination AS number in the target macro flow, and other traffic does not satisfy the condition In this case, the traffic feature extraction unit 136 determines the exit feature information as [egress edge router identifier, p].

  Fifth, in the cases other than the above (assuming that the set of interface, destination AS number and destination IP address / subnet address is (i1, a1, p1), (i2, a2, p2),...), The traffic feature extracting unit 136 Let egress feature information be [egress edge router identifier% 1, ((i1, a1, p1), (i2, a2p, 2), ...)].

  FIG. 8 is a flowchart illustrating processing in which the collection information instruction unit 137 according to the first embodiment of this invention instructs each edge router to perform traffic measurement and report of measurement results based on the extracted traffic characteristics. The following processing is repeatedly executed for each target macro flow.

  In step 801, the collected information instruction unit 137 instructs each ingress edge router to measure traffic and report the measurement result.

  Specifically, when the ingress feature information determined in step 703 is [ingress edge router identifier], the collection information instruction unit 137 instructs each ingress edge router to acquire the end point-ToS aggregation record. Here, the end point-ToS aggregation record is traffic information including [total number of bytes, end point subnet address, end point AS number, measurement time] regarding each aggregated flow.

  The total number of bytes is the sum of all the number of bytes of packets belonging to the flow. The end point subnet address is specified by the end point address prefix and the number of bits of the end point address prefix. The end point AS number is an AS number of an end point or end point side neighboring BGP (Boeder Gateway Protocol) peer. The measurement time is the time when the traffic measurement related to the aggregated record is started or the time when the packet arrives first.

  When using the NetFlow protocol version 5 implemented in many existing routers for traffic measurement, the collection information instruction unit 137 reports the Destination-Prefix-ToSAggregation records by CLI (command line interface). You just have to tell the ingress edge router.

  When the IPFIX protocol, which is an IETF standard, is used for traffic measurement, the collection information instruction unit 137 designates a template including each of the above-described contents and performs traffic measurement and measurement result report for each entrance edge. Just tell the router.

  In addition, for the reporting interval, for example, the collection information instruction unit 137 instructs each ingress edge router to specify the value of the maximum communication time (time-active) so that it is executed every one minute. The value of the maximum communication time can also be indicated by CLI or the like.

  If the ingress feature information determined in step 703 is other than [ingress edge router identifier], the collection information instruction unit 137 instructs each ingress edge router to acquire the start point end point-ingress interface-ToS aggregation record. Since each of the measurement target data 211, 212, 213, 214, 215 has the determined entrance feature information [10.10.11.1% 1] or [10.10.11.1% 2], each edge router Is instructed to acquire the start point / end point / entrance interface / ToS aggregation record. Here, the start point end point-ingress interface-ToS aggregation record includes [total number of bytes, start point subnet address, start point AS number, ingress interface, end point subnet address, end point AS number, measurement time] for each aggregated flow. Traffic information.

  Here, the total number of bytes, the end point subnet address, the end point AS number, and the measurement time are the same as those of the end point-ToS aggregation record described above. The start point subnet address is specified by the start point address prefix and the number of bits of the start point address prefix. The start point AS number is the AS number of the start point or the start point side adjacent BGP peer. The ingress interface is an interface through which the flow is input to an edge router that performs traffic measurement.

  When using the NetFlow protocol Version 5 for traffic measurement, the collection information instruction unit 137 may instruct each ingress edge router to report the Prefix-ToSA aggregation record by CLI.

  When using the IPFIX protocol for traffic measurement, the collection information instruction unit 137 specifies a template including each of the above contents and instructs each ingress edge router to report the traffic measurement and the measurement result. Good.

  The setting of the report interval is the same as that in the case of the end point-ToS aggregate record.

  In step 802, the collection information instruction unit 137 transmits an instruction to the egress edge router.

  When the egress feature information determined in step 704 is [egress edge router identifier], the collection information instruction unit 137 instructs each egress edge router to acquire the start point-ToS aggregation record. Since each of the measurement target data 211, 212, 213, 214, 215 has the determined exit feature information [10.10.12.1] or [10.10.13.1], each edge router has a start point-ToS. Acquisition of aggregated record is instructed. Here, the start point-ToS aggregation record is traffic information including [total number of bytes, start point subnet address, start point AS number, measurement time] for each aggregated flow.

  The meaning of the value included in the start point-ToS aggregation record is the same as that of the above-described start point-ToS aggregation record.

  When the NetFlow protocol version 5 is used for traffic measurement, the collection information instruction unit 137 may instruct each egress edge router to report the Source-Prefix-ToSA aggregation record by CLI.

  When the IPFIX protocol, which is an IETF standard, is used for traffic measurement, the collection information instruction unit 137 designates a template including each of the above-described contents and performs traffic measurement and measurement result report for each entrance edge. Just tell the router. The setting of the report interval is the same as in the case of the end point-ToS aggregate record.

  If the exit feature information determined in step 704 is other than [exit edge router identifier], the collection information instruction unit 137 instructs each exit edge router to acquire the start point / end point-ToS aggregation record. Here, the start point / end point-exit interface-ToS aggregation record includes traffic including [total number of bytes, start point subnet address, start point AS number, exit interface, end point subnet address, end point AS number, measurement time] for each aggregated flow. Information.

  The egress interface is an interface through which the flow is output from an egress edge router that performs traffic measurement.

  When using the NetFlow protocol version 5 for traffic measurement, the collection information instruction unit 137 may instruct each egress edge router to report the Prefix-ToSA aggregation record by CLI.

  When the IPFIX protocol is used for traffic measurement, the collection information instruction unit 137 instructs each ingress edge router to specify traffic measurement and report the measurement result by designating the template including the above-described contents. That's fine. The setting of the report interval is the same as in the case of the end point-ToS aggregate record.

  The collected information instruction unit 137 completes the process of instructing each edge router to measure traffic and report the measurement result based on the extracted traffic characteristics.

  FIG. 9 is an explanatory diagram illustrating details of a process in which the traffic information analysis unit 138 according to the first embodiment of this invention aggregates the results measured based on the extracted traffic characteristics for each target flow. . The following processing is repeatedly executed for each target macro flow.

  In step 901, the traffic information analysis unit 138 aggregates the measurement results of the target macro flow in each ingress edge router and calculates the actual bandwidth.

  Specifically, when the ingress feature information is [ingress edge router identifier], the traffic information analysis unit 138 determines the attributes of the target macro flow (the end point AS number, the end point IP address) from the acquired end point-ToS aggregation record. / The subnet address, ToS) is added to the total number of bytes of the flow to calculate the actual entrance bandwidth.

  When the entrance feature information is other than [entrance edge router identifier], the traffic information analysis unit 138 includes the attributes (start point / end point AS number, start point / end point IP) of the target macro flow in the acquired start point / end point-ToS aggregation record. The total number of bytes of the flow that matches the address / subnet address, ToS) is added to calculate the actual entrance bandwidth.

  In step 902, the traffic information analysis unit 138 aggregates the measurement results of the target macro flow in each egress edge router and calculates the actual bandwidth.

  Specifically, when the exit characteristic information is [exit edge router identifier], the traffic information analysis unit 138 includes the attributes (start AS number, start IP address) of the target macro flow in the acquired start-ToS aggregation record. / The subnet address, ToS) is added to the total number of bytes of the flow to calculate the exit actual bandwidth.

  When the exit characteristic information is other than [exit edge router identifier], the traffic information analysis unit 138 includes the attributes (start point / end point AS number, start point / end point IP) of the target macro flow in the acquired start point / end point-ToS aggregation record. The total number of bytes of the flow that matches the address / subnet address, ToS) is added to calculate the actual exit bandwidth.

  In the above-described processing, only the value of the actual entrance band or the actual exit band is calculated, but other statistical values such as a band deviation, a maximum band value, or a minimum band value can also be calculated. .

  According to the first embodiment of the present invention, since the edge node, the end point, or the network area is specified based on the measurement result of the edge router, the position of the measurement target of the macro flow to be measured can be specified.

  Also, the feature information of the macro flow passing through the specified edge node, the specified end point or the specified network area is extracted, and the edge router performs traffic measurement based on the extracted feature information. Since the measurement result is transmitted to the resource management server 131, the overhead due to traffic measurement and transmission / reception of the measurement result can be reduced.

  Further, since the measurement results are aggregated for each macro flow, the traffic amount for each macro flow can be obtained.

  Hereinafter, a second embodiment of the present invention will be described.

  Since the network configuration and system configuration of the second embodiment of the present invention are the same as those of the first embodiment of the present invention, description thereof will be omitted.

  In the second embodiment of the present invention, the traffic measurement is not set for the ingress edge router and the egress edge router, and each ingress edge router and each egress edge router have the macro flow to be measured designated by the operator. The resource management server 132 totals the measurement results and displays the totals.

  Specifically, the management terminal 132 designates a measurement target instead of inputting a policy. Data related to the designated measurement target is stored in the measurement target DB 134. Information on the reserved bandwidth 207 is not stored in the measurement target DB 134. The router setting unit 139 is not used in the second embodiment of the present invention.

  Further, as described above, since the reserved bandwidth 207 is not stored in the measurement target DB 134, the resource management server 131 does not perform the process of step 613, but instead displays the measurement result on the management terminal 132.

  In the first embodiment, the actual bandwidth is calculated based on the measurement result, the calculated actual bandwidth is compared with the reserved bandwidth, and the traffic in the core network 125 is controlled based on the compared result. It was. However, the control content is not notified to the computers 101, 102, 103, 104. Therefore, any of the computers 101, 102, 103, and 104 may send excessive traffic and the QoS condition may not be satisfied.

  In order to solve this problem, the operator may determine the control content based on the actual bandwidth displayed on the management terminal 132, and transmit the determined control content to the computers 101, 102, 103, and 104. There are the following methods for transmission.

  When the computers 101, 102, 103, and 104 communicate with each other such as voice or video, a protocol for session control is usually used. Examples of the above-described protocol include SIP (Session Initiation Protocol) standardized by IETF or RTSP (Real-Time Streaming Protocol).

  When the resource management server 131 communicates using the protocol described above, the resource management server 131 communicates using the protocol described above at the start and end of the session. When using SIP, an INVITE request is normally transmitted from the computer requesting communication to the other party at the start of the session, and communication is started by changing an OK response to the INVITE request received by the other party.

  In the INVITE request and the OK response, the type and resource amount of communication media such as voice / video used for communication are described by SDP (Session Description Protocol) which is an IETF standard protocol. Normally, the contents of the SPD are described by a communicating computer on the transmitting side or receiving side, and the described contents are transmitted to the communication partner, but the SIP proxy (not shown) attached to the resource management server 131 may rewrite the contents. Is possible.

  In the NGN (Next Generation Network) standard of 3GPP and European Telecommunications Standards Institute (ETSI), a resource control method including rewriting as described above is standardized. By using the mechanism as described above, the control content can be transmitted to the computers 101, 102, 103, and 104. The computers 101, 102, 103, and 104 adjust communication media and the like according to the received control content. , Communication can be performed to ensure QoS.

  According to the second embodiment of the present invention, it is possible to transmit the control content to the computers 101, 102, 103, 104 and control the traffic, so there is no need to set the control content in each edge router, The load on the edge router can be reduced.

  Hereinafter, a third embodiment of the present invention will be described.

  Since the network configuration and system configuration of the third embodiment of the present invention are the same as those of the first embodiment of the present invention, description thereof will be omitted.

  The third embodiment of the present invention is different from the first embodiment of the present invention in the following points. In the first embodiment of the present invention, the information of the acquired start point-ToS aggregation record, end point-ToS aggregation record, or start point / end point-ToS aggregation record is further aggregated in step 901 and step 902.

  However, when a plurality of aggregate records are received asynchronously and the range of time to be aggregated is different for each aggregate record, the received aggregate records cannot be simply added. Therefore, a time average is taken for each aggregated record, and the obtained average values are added.

  FIG. 10 is an explanatory diagram illustrating a process of collecting measurement results transmitted asynchronously in the third embodiment of the present invention.

  In the third embodiment of the present invention, the measurement result 511 is divided into a measurement result 1011 and a measurement result 1014, and the measurement result 1011 and the measurement result 1014 are transmitted from each edge router to the resource management server 131 in this order.

  The measurement result 1011 includes a measurement result 1012 related to the flow f1 and a measurement result 1013 related to the flow f2, and the measurement result 1014 includes a measurement result 1015 related to the flow f3.

  The measurement result 512 is divided into a measurement result 1021 and a measurement result 1024, and is transmitted from each edge router to the resource management server 131 in the order of the measurement result 1021 and the measurement result 1024. The measurement result 1021 includes a measurement result 1022 related to the flow f1 and a measurement result 1023 related to the flow f2, and the measurement result 1024 includes a measurement result 1025 related to the flow f3.

  Hereinafter, processing of the traffic information analysis unit 138 according to the third embodiment of the present invention will be described.

  FIG. 11 is a flowchart illustrating processing of the traffic information analysis unit 138 according to the third embodiment of this invention.

  The processing described below is executed by a task (thread) different from the processing described with reference to FIG. 9, but each time a measurement result transmitted from each edge router to the resource management server 131 is waited for and received (step 1101). Repeatedly.

  In step 1102, when the received measurement result includes the measurement result of the new flow, the traffic information analysis unit 138 generates average bandwidth information initialized for each new flow. Since there is a plurality of average bandwidth information, it is identified by the flow identification information. The flow identification information is information including a start point subnet address, a start point AS number, an end point subnet address, an end point AS number, a ToS value, an ingress interface, an egress interface, and the like included in the measurement result of the flow. However, in the extracted traffic characteristics, since the flow measurement result does not include any of the above-described information, the flow identification information does not include the information.

  In Step 1103, when the measurement result of the received flow includes the existing flow measurement result, that is, the average bandwidth information having the same identification information as the identification information of the existing flow information exists in the measurement result of the received flow. The average bandwidth information is updated for each existing flow.

In the updating method, when the traffic information analysis unit 138 receives flow measurement results at regular intervals, the updated average bandwidth information B (i) is expressed by the following equation.
(Formula) B (i) = (1-α) B (i−1) + αb (i)
Here, B (i-1) is the average bandwidth information before the update, and b (i) is a value (bps) obtained by dividing the total number of bytes by the measurement time (communication time in seconds) of the flow measurement result. . Α is a constant that satisfies 0 <α <1 and is determined in advance. The average band information B (i) represents a moving average of the flow band value b.

  When the traffic information analysis unit 138 receives the measurement result 1011 of FIG. 10, in step 1102, average bandwidth information related to the flow f1 is generated from the measurement result 1012 related to the flow f1, and from the measurement result 1013 related to the flow f2 to the flow f2. Average bandwidth information is generated.

  When the traffic information analysis unit 138 receives the measurement result 1014 of FIG. 10, in step 1102, average bandwidth information related to the flow f3 is generated from the measurement result 1025 related to the flow f3.

  When the traffic information analysis unit 138 receives the measurement result 1021 of FIG. 10, the average bandwidth information related to the flow f1 is updated by the measurement result 1022 related to the flow f1 in step 1103, and the average related to the flow f2 is updated based on the measurement result 1023 related to the flow f2. Band information is updated.

  When the traffic information analysis unit 138 receives the measurement result 1024 in FIG. 10, the average bandwidth information related to the flow f3 is updated with the measurement result 1025 related to the flow f3 in Step 1103.

  In steps 901 and 902 of FIG. 9, the traffic information analysis unit 138 calculates the entrance real bandwidth and the exit real bandwidth using the average bandwidth information generated in steps 1102 and 1103 or the updated average bandwidth information. . That is, the average bandwidth information for each flow included in the measurement result is added for each macro flow, and these actual bandwidths are obtained.

  According to the third embodiment of the present invention, measurement results can be aggregated even when a plurality of aggregate records are received asynchronously.

  Hereinafter, a fourth embodiment of the present invention will be described.

  Since the network configuration and system configuration of the fourth embodiment of the present invention are the same as those of the first embodiment of the present invention, description thereof will be omitted.

  The fourth embodiment differs from the first embodiment in the following points. In the first embodiment, in Step 613, when the actual entrance band 208 or the actual exit band 209 exceeds or approaches the reserved bandwidth 207, the resource management server 131 warns the operator, and based on the alert, the operator There was a need to manually change the settings of each edge router. However, quality degradation can be avoided if the resource management server 131 automatically changes the settings of each edge router.

  In the fourth embodiment of the present invention, instead of step 613, the setting of each edge router is automatically changed by performing the steps described below.

  Specifically, the actual bandwidth values at the ingress edge router and egress edge router received by the measurement target data management unit 133 are stored in the measurement target data DB 134 for each macro flow, and the actual entrance bandwidth 208 and the actual exit bandwidth 209 The reserved bandwidth 207 is compared. If any of them exceeds the reserved bandwidth 207 or approaches the reserved bandwidth 207 (for example, reaches 80% of the reserved bandwidth), the measurement target management unit 133 has the same entrance as the macro flow. A macro flow having a sufficient bandwidth is searched from other macro flows passing through the edge router and the egress edge router. If a macro flow having a sufficient bandwidth is found, the reserved bandwidth of the macro flow having a sufficient bandwidth is reduced, and the reduced amount is added to the macro flow. Then, the setting of the edge router 111 is changed through the router setting unit 139. In addition, the resource management server 131 outputs a message to the management terminal 132 to notify the operator that the reserved bandwidth 207 has been changed.

  Or, when the total bandwidth between the ingress edge router and egress edge router through which the macro flow passes can be increased by automatically changing the setting such as MPLS, The reserved bandwidth of the macro flow is added as much as the bandwidth that could be increased without changing the setting. Thereafter, the router setting unit 139 changes the setting of the edge router 111. In addition, the resource management server 131 outputs a message to the management terminal 132 to notify the operator that the reserved bandwidth has been changed.

  According to the fourth embodiment of the present invention, the resource management server 131 compares the entrance real bandwidth 208 and the exit real bandwidth 209 with the reserved bandwidth 207, and any of them exceeds the reserved bandwidth 207. If the resource management server 131 automatically changes the setting of the edge router to control the traffic when the reserved bandwidth 207 is approached, the operation of the operator is facilitated.

  The fifth embodiment of the present invention will be described below.

  Since the network configuration and system configuration of the fifth embodiment of the present invention are the same as those of the first embodiment of the present invention, description thereof will be omitted.

  The fifth embodiment of the present invention differs from the first embodiment of the present invention in the following points. In the first embodiment of the present invention, in the collection information instruction processing 605 (see FIG. 8), the collection information instruction unit 137 selects one of two types of instructions, and selects each entry edge router or each exit. I was instructing the edge router. However, the above-described method does not effectively use the five types of classification extracted in step 703 and step 704.

  In the fifth embodiment of the present invention, in step 801, the collection information instruction unit 137 classifies the following five types of instructions and instructs the ingress edge router.

  First, when the ingress feature information is [ingress edge router identifier], the collection information instruction unit 137 instructs the ingress edge router to acquire the end point-ToS aggregation record.

  Second, when the ingress feature information is [ingress edge router identifier% i], the collection information instruction unit 137 instructs the ingress edge router to acquire the ingress interface-end point-ToS aggregate record. The ingress interface-end point-ToS aggregation record is traffic information including [total number of bytes, ingress interface, destination subnet address, destination AS number, measurement time].

  A report format including the above-described contents is not defined in the NetFlow protocol version 5. Therefore, in the NetFlow protocol Version 9 or IPFIX, a template including the above-described content is defined, and the collection information instruction unit 137 needs to instruct the edge router to report traffic information including the above-described content.

  Third, when the entry feature information is [entrance edge router identifier, a] (a is an AS number), the collection information instruction unit 137 instructs the entry edge router to acquire the start point AS-end point-ToS aggregation record. The start point AS-end point-ToS aggregation record is traffic information including [total number of bytes, start point AS number, end point subnet address, end point AS number, measurement time].

  A report format including the above-described contents is not defined in the NetFlow protocol version 5. Therefore, in the NetFlow protocol Version 9 or IPFIX, a template including the above-described content is defined, and the collection information instruction unit 137 needs to instruct the edge router to report traffic information including the above-described content.

  Fourth, when the ingress feature information is [ingress edge router identifier, p] (p is a subnet address), the collection information instruction unit 137 instructs the ingress edge router to acquire the start point subnet address-end point-ToS aggregation record. . The start point start point subnet address-end point-ToS aggregation record is traffic information including [total number of bytes, start point subnet address, end point subnet address, end point AS number, measurement time].

  A report format including the above-described contents is not defined in the NetFlow protocol version 5. Therefore, in the NetFlow protocol Version 9 or IPFIX, a template including the above-described content is defined, and the collection information instruction unit 137 needs to instruct the edge router to report traffic information including the above-described content.

  Fifth, if the entry feature information does not correspond to any of the above, the collection information instruction unit 137 instructs the entry edge router to acquire the start point / end point-ToS aggregation record.

  In step 802, the instructions are classified into five types as in step 801, and are instructed to the ingress edge router.

  Specifically, first, when the egress feature information is [egress edge router identifier], the collection information instruction unit 137 instructs the egress edge router to acquire the start point-ToS aggregation record.

  Second, when the exit feature information is [exit edge router identifier% 1], the collection information instruction unit 137 instructs the exit edge router to acquire the exit interface-start point-ToS aggregation record.

  Third, when the exit feature information is [exit edge router identifier, a], the collection information instruction unit 137 instructs the exit edge router to acquire the end point AS-start point-ToS aggregate record.

  Fourth, when the exit characteristic information is [exit edge router identifier, p], the collection information instruction unit 137 instructs the exit edge router to acquire the end point subnet address-start point-ToS aggregation record.

  Fifth, if the exit feature information does not correspond to any of the above, the collection information instruction unit 137 instructs the entrance edge router to acquire the start point / end point-ToS aggregate record.

  According to the fifth embodiment of the present invention, the degree of information aggregation in the edge router can be increased and the processing overhead can be reduced.

1 is a block diagram showing a network configuration and a system configuration in a first embodiment of the present invention. It is a figure which shows an example of measurement object DB of the 1st Embodiment of this invention. FIG. 3 is an explanatory diagram illustrating a flow of measurement target data in FIG. 2. It is a figure which shows an example of network connection DB of the 1st Embodiment of this invention. Indication of measurement and report of measurement results from the resource management server to each edge router in the first embodiment of the present invention, and corresponding measurement results periodically transmitted from each edge router to the resource management server It is a figure which shows the sequence of. It is a flowchart which shows the process of the resource management server at the time of receiving the policy from the management terminal in the 1st Embodiment of this invention. It is a flowchart which shows the process at the time of receiving the measurement result of traffic measurement from each edge router in the 1st Embodiment of this invention. It is a flowchart which shows the process which extracts the traffic characteristic in step 604 of the 1st Embodiment of this invention. The processing described below is repeatedly executed for each target macro flow. It is a flowchart which shows the process which the collection information instruction | indication part of the 1st Embodiment of this invention instruct | indicates measurement to each edge router based on the extracted traffic characteristic, and the report of the measured result. It is explanatory drawing explaining the detail of the process which the traffic information analysis part of the 1st Embodiment of this invention aggregates the result measured based on the extracted traffic characteristic for every object flow. It is explanatory drawing explaining the process which collects the measurement result transmitted asynchronously in the 3rd Embodiment of this invention. It is a flowchart explaining the process of the traffic information analysis part of the 3rd Embodiment of this invention.

Claims (11)

A network system comprising: a plurality of networks; a plurality of network devices connected to the network; and a management server that controls traffic flowing through a network path composed of the networks and the network devices,
The management server
A connection storage unit that manages information related to connections between the plurality of networks and the plurality of network devices;
Said network device as a starting point the traffic is measured, and a determination unit for determining said network device comprising an end point,
Referring to the connection storage unit, the network serving as the determined starting point among a plurality of traffics flowing through the network path connecting the network device serving as the determined starting point and the network device serving as the determined end point Extraction that extracts characteristics of traffic flowing between a first network device connected to the network via a device and a second network device connected to the network via the determined network device And
An instruction unit that transmits request information including measurement conditions for measuring the traffic based on the extracted traffic characteristics;
Based on the characteristics of the extracted traffic, the measurement results of the plurality of traffic flowing through the network path connecting the network device that is the determined start point and the network device that is the determined end point are used as common information. An aggregator that aggregates traffic including
A control unit that controls the traffic based on the measurement results of the plurality of collected traffic ,
The extraction unit includes:
With reference to the connection storage unit, based on the information on the connection between the determined network device and the first network device, characteristics of the traffic in the determined network device Determine certain entrance feature information,
With reference to the connection storage unit, on the basis of information on the connection between the determined network device serving as the end point and the second network device, characteristics of the traffic in the determined network device serving as the end point Determine some exit feature information,
The instruction unit includes:
Based on the determined entrance characteristic information, a first measurement condition of the traffic to be measured by the network device as the determined start point is determined, and the request information including the first measurement condition is determined. To the network device that is the starting point,
Based on the extracted exit feature information, a second measurement condition of the traffic information to be measured by the network device serving as the determined end point is determined, and the request information including the second measurement condition is determined. A network system for transmitting to a network device serving as an end point . The controller is
Based on the measurement results of the collected traffic, the traffic volume is calculated for each traffic including the common information,
The network system according to claim 1, wherein the traffic is controlled based on a result of the calculation.   The extraction unit includes:
  A case where all traffic passing through the determined network device passes through the specific network path, and all traffic which does not pass through the determined network device does not pass through the specific network path ,
  The network system according to claim 1, wherein identification information of the network device serving as the determined start point is determined as the entrance feature information.   The extraction unit includes:
  All traffic passing through a specific interface of the determined network device as a starting point passes through a specific network path;
  When all traffic that does not pass through the specific interface of the determined network device does not pass through the specific network path,
  2. The network system according to claim 1, wherein a set of identification information of the network device as the determined start point and identification information of the specific interface is determined as the entrance feature information.   The extraction unit includes:
  The network to which the determined network device as the starting point is connected has a specific AS number,
  When all traffic passing through the determined network device as the start point passes through the network device as the determined end point,
  The network system according to claim 1, wherein a set of identification information of the network device that is the determined start point and the specific AS number is determined as the entrance feature information.   The extraction unit includes:
  The network to which the determined network device is connected matches a specific subnet address,
  When all traffic passing through the determined network device as the start point passes through the network device as the determined end point,
  2. The network system according to claim 1, wherein a set of the identification information of the network device serving as the determined start point and the specific subnet address is determined as the entrance feature information.   The extraction unit includes:
  All traffic passing through the network device that is the determined end point passes through the network device that is the determined start point;
  If all traffic that does not pass through the determined network device does not pass through the determined network device,
  The network system according to claim 1, wherein identification information of the network device serving as the determined end point is determined as the exit characteristic information.   The extraction unit includes:
  All traffic passing through the specific interface of the determined network device passes through the determined network device of the starting point;
  If all traffic that does not pass through the specific interface of the determined network device does not pass through the determined network device,
  The network system according to claim 1, wherein a set of identification information of the network device serving as the determined end point and identification information of the specific interface is determined as the exit feature information.   The extraction unit includes:
  A network to which the determined network device as the end point is connected has the specific AS number;
  When all traffic passing through the network device that is the determined start point passes through the network device that is the determined start point,
  The network system according to claim 1, wherein a set of identification information of the network device serving as the determined end point and the specific AS number is determined as the exit feature information.   The extraction unit includes:
  The network to which the determined network device is connected matches the specific subnet address;
  When all traffic passing through the determined network device as the start point passes through the network device as the determined end point,
  The network system according to claim 1, wherein a set of identification information of the network device serving as the determined end point and the specific subnet address is determined as the exit characteristic information.   A QoS guarantee method in a network path composed of a plurality of networks, a plurality of network devices connected to the network, and the networks and the network devices,
  A resource management server connected to at least one of the networks manages information related to connection between the plurality of networks and the plurality of network devices;
  The QoS guarantee method is:
  A first step of determining the network device as a start point of a section in which traffic is measured and the network device as an end point;
  Of a plurality of traffics flowing through the network path connecting the determined network device that is the starting point and the determined network device that is the end point, the network device is connected to the network via the determined network device that is the starting point. A second step of extracting characteristics of traffic flowing between the first network device and the second network device connected to the network via the network device serving as the determined end point;
  A third step of transmitting request information including a measurement condition for measuring the traffic based on the extracted traffic characteristics;
  Based on the characteristics of the extracted traffic, the measurement results of the plurality of traffic flowing through the network path connecting the network device that is the determined start point and the network device that is the determined end point are used as common information. A fourth step that summarizes for each traffic that includes
  And a fifth step of controlling the traffic based on the collected measurement results of the plurality of traffics,
  The second step includes
  With reference to the connection storage unit, based on the information on the connection between the determined network device and the first network device, characteristics of the traffic in the determined network device Determining certain entrance feature information;
  With reference to the connection storage unit, on the basis of information on the connection between the determined network device serving as the end point and the second network device, characteristics of the traffic in the determined network device serving as the end point Determining certain exit feature information,
  The third step includes
  Based on the determined entrance characteristic information, a first measurement condition of the traffic to be measured by the network device as the determined start point is determined, and the request information including the first measurement condition is determined. Transmitting to the starting network device;
  Based on the determined exit characteristic information, a second measurement condition of the traffic to be measured by the network device serving as the determined end point is determined, and the request information including the second measurement condition is determined. A QoS guarantee method comprising: transmitting to a network device as an end point.

Images