JP4864775B2 - Network jurisdiction system - Google Patents

Description

  The present invention has jurisdiction over a system for managing traffic of packets transferred in a network, for example, traffic of a VPN (Virtual Private Network) packet transferred in an MPLS (Multi-Protocol Label Switching) network. The present invention relates to a suitable network jurisdiction system.

  The present invention also relates to a network management device and a traffic measurement device that constitute the network management system, and a traffic management device for linking these devices. Furthermore, the present invention relates to a method for operating the network jurisdiction system.

  In the conventional network jurisdiction system, a distribution normality confirmation function for confirming whether or not a packet normally flows on the network, and for quickly eliminating this when congestion occurs on the network The distribution normality maintenance function and the like were the main functions.

  However, in recent network jurisdiction systems that administer IP (Internet Protocol) networks, not only the normality confirmation and maintenance functions described above but also more advanced jurisdiction functions have been required. For example, there is a service management function that investigates and analyzes a service trend of user traffic for each user and provides a new service for each user based on the analysis result. Furthermore, a network resource management function that examines and analyzes the traffic volume of packets transferred in the network for each node (router or switch) and reconstructs efficient resources in the network based on the analysis results. There is.

  Under such circumstances, even in the traffic management of VPN packets on the MPLS network, the point-to-multi-point traffic management in the conventional general VPN space is not sufficient. It is required to perform detailed traffic management in a point-to-point format and implement highly accurate traffic measurement.

  In addition, as a well-known technique relevant to this invention, the following [patent document 1] is mentioned. In this [Patent Document 1], “MPLS statistical method capable of statistically combining the traffic amount for each user in the MPLS-VPN packet transfer network and for which area the user is using traffic” is described. (Apparatus) "is disclosed.

  However, in this [Patent Document 1], as in the present invention to be described later, “when there is a temporary (or permanent) route change in the VPN packet setting route, the fact of the route change and the fact There is no suggestion of an MPLS statistical method (apparatus) that can take into account even the time of occurrence.

JP 2003-110602 A

  The conventional traffic measurement device reads and collects the traffic amount of the VPN packet from the node based on the route information of a series of VPN packets sent from the user to be measured at the node to be measured. In addition, the total is done. Here, in principle, if the source node and the final destination node are determined, the route information is not changed thereafter. Therefore, the traffic measurement device only needs to aggregate the traffic amount of VPN packets passing through the node by paying attention only to the determined route information (for example, intra-network transfer label) in the node.

  However, in reality, the determined route information may be changed thereafter. For example, there is a case where a node failure or a path failure has occurred on the transfer route of the VPN packet. Or it is a case where there is a reconfiguration of resources in the network.

  In such a case, the intra-network transfer label determined first, for example L1, is changed to another label L2 in order to bypass the failure. Therefore, even if the traffic measuring device keeps paying attention to the label L1 and totals the traffic amount, the result is totally meaningless, and the above-described highly accurate traffic measurement becomes impossible.

  In order to solve such a problem, the traffic measurement device must collect route information for all nodes at a constant cycle. This is because the change of the route information autonomously executed by the node due to the failure is detected in the shortest time and reflected at the next aggregation.

  However, such a method has a disadvantage that firstly, a large amount of monitoring data is leaked onto the network, and the control traffic for that purpose puts pressure on the original data traffic. Second, in the server constituting the traffic measurement device, the route information DB (database) must be constantly refreshed based on the route information collected from each node at the above-mentioned fixed period. There is a disadvantage that the load is significantly increased and the original measurement process is hindered.

  Therefore, in the present invention, when the above-mentioned route change (change of intra-network transfer label) occurs during the transfer of the VPN packet without causing the above disadvantages, the route change is accurately reflected to provide highly accurate traffic. The purpose is to provide a network jurisdiction system capable of measurement.

  It is another object of the present invention to provide a network management device, a traffic measurement device, a traffic management device, and an operation method of the system that constitute the system.

  FIG. 1 is a basic configuration diagram of a network management system according to the present invention. In the figure, reference numeral 1 represents the entire network management system.

  The basic components of the conventional system 1 are a route information change detection unit 2 and a traffic measurement unit 6. Conventionally, these means 2 and 6 have not been linked at all in terms of traffic measurement. However, in the present invention, in order to achieve the above object, the two means 2 and 6 are linked through the new means 3, 4 and 5. The new means are a route information change notification means 3, a route history holding means 4, and a totaling adjustment means 5, as shown in the figure. More specifically, it is as follows.

  The network management system 1 according to the present invention has at least (i) conventional traffic measurement means 6 that collects the traffic amount of VPN packets at a predetermined location in the network 7 and totals the traffic amount within a unit time. (Ii) It is preferable to have the conventional route information change detecting means 2 for detecting the change of the route information when the route information indicating the transfer route of the VPN packet in the network 7 is changed. The system 1 of the present invention is characterized by the following means.

a) route information change notification means 3 for notifying that the route information has changed;
b) On the traffic measurement means 6 side, based on the change notification from the route information change notification means 3, a route history holding means 4 for holding a history relating to the route change of the VPN packet;
c) In cooperation with the traffic measuring means 6, the route history holding means 4 is referred to when the traffic amount is aggregated, and when the route is changed at a certain time, the aggregation at that time is adjusted to the aggregate corresponding to the changed route. This is a total adjustment means 5.

  Even if the above-described route change (for example, change from the intra-network transfer label L1 to L2) occurs in the network 7 by the total adjustment unit 5, the traffic totalization for the label L1 performed before the route change is generated. After the occurrence, the traffic is switched to the traffic aggregation for the label L2. That is, unlike the conventional case, traffic is not continuously counted with the original label L1 regardless of whether or not a route change has occurred.

  It is possible to accurately measure the traffic amount of the VPN packet by accurately reflecting the route change that occurs on the MPLS network. Therefore, it becomes possible for the network administrator to detect a problem case in the network monitoring work at an early stage, and it becomes possible to make an efficient resource deployment plan in the planning work of the network administrator.

  First, a specific configuration example of a device group that constructs the network management system 1 to which the present invention is applied will be described.

FIG. 2A is a diagram showing a specific overall configuration of the conventional system 1.
FIG. 2B is a diagram showing a specific overall configuration of the system 1 of the present invention.

3, 4, and 5 are enlarged views of the network management device 100, the traffic management device 200, and the traffic measurement device 300 in FIG.
6, 7, and 9 are enlarged views of the network management device 100, the traffic management device 200, and the traffic measurement device 300 in FIG. 2B, respectively.

  3, 4, and 5 are mostly the same as the configurations of FIGS. 6, 7, and 8, and will be described with reference to FIGS. 6, 7, and 8.

The relationship between these configurations of FIGS. 6 to 8 and the configuration of FIG. 1 is as follows. That is,
The network management system 1 includes at least a network management device 100 (FIG. 6) and a traffic measurement device 300 (FIG. 8) cooperating with the network management device 100. The traffic measurement device 300 includes traffic measurement. Means 6, route history holding means 4, and total adjustment means 5 are included. Further, the network management apparatus 100 includes a route information change detection unit 2 and a route information change notification unit 3.

  The network jurisdiction system 1 further includes a traffic management device 200 (FIG. 7) for exchanging predetermined information with the network management device 100 on one side and for exchanging predetermined information with the traffic measurement device 300 on the other side. The traffic management device 200 includes a route information change relay unit 8 (also shown in FIG. 1) that relays route change information from the route information change notification unit 3 to the route history holding unit 4. 300 includes route information change accepting means 9 (FIG. 8) for accepting route change information from the route information change relay means 8.

  Referring to FIG. 6, the path information change detection device 104 (= means 2) collects failure information from the network 7, failure recovery information, routing table change information in the node (router), syslog, and the like. This is a conventional operation. Of these pieces of aggregated information, in particular, the information regarding the change of the route information is not owned only by the network administrator, and a route to be sent to the traffic measuring device 300 is created according to the present invention. Means 3 for this purpose is realized as the route information change notification device 103.

  Means for transmitting the change notification to the traffic measuring device 300 is necessary. For this purpose, attention is paid to the existing traffic management device 200, and the means 8 for transferring the change notification therein (FIG. 1, FIG. 1). 7) is introduced. In FIG. 7, the means 8 is realized as a route information change relay device 203.

  The change notification relayed by the relay device 203 is first received by the means 9 of FIG. The means 9 is realized as a route information change accepting device 302.

  The route change information received by the receiving device 302 is taken into the means 4. In FIG. 8, the means 4 is realized by a route history information writing device 303 and a route history information DB (database) 310 that holds a route history.

  On the other hand, the traffic measuring means 6 in FIG. 8 is mainly composed of the traffic counting device 308 and is configured to cooperate with the traffic measuring device 306, the traffic DB 311, and the traffic data reading device 309. Unlike the corresponding 306 ', 311', and 309 'shown in FIG. 5, these 306, 311 and 309 constitute the total adjustment means 5 in consideration of information from the route history information reading device 304. The function of the means 5 and the function of the means 4 will be described in detail later with specific examples.

  The functional parts particularly related to the present invention have been described with reference to FIGS. 6 to 8. The other functional parts in the figure are briefly described as follows.

In FIG. 6, a network configuration information management apparatus 101 is a means for managing router setting information (line type, bandwidth, etc.) and inter-router link information (topology, etc.) on the network 7.
The service information management apparatus 102 is means for managing VPN service registration information in the MPLS network.

The route information change notification device 103 described above is means for notifying the traffic measurement server (300) of the route information change detected by the device 104, and
The route information change detection device 104 is a means for detecting a failure or congestion state of a router on the network 7 and detecting a route information change.

The network configuration information DB 110 is a means for storing information of the device 101,
The service information DB 111 is means for storing information on the device 102.

Referring to FIG. 7, the network configuration information cooperation device 201 is a means for extracting necessary information such as address information and line type information from the information of the device 110,
The service information cooperation apparatus 202 is a means for extracting necessary information such as a VPN number from the information of the apparatus 111,
The route information change relay device 203 described above is means for relaying a change notification from the device 103, and
The traffic collection / setting / cancellation accepting device 204 is a means for accepting the setting of a traffic measurement location (predetermined node).

The traffic processing device 205 is a means for processing traffic information in an easy-to-view manner for the client.
The traffic transmission requesting device 206 is a means for obtaining the traffic total requested by the client from the traffic measurement server (300).
The traffic display device 207 is a means for visually displaying the requested traffic aggregation.

The network configuration information DB excerpt 210 is means for extracting and storing necessary information from the device 110,
The service information DB excerpt 211 is means for extracting and storing necessary information from the device 111.

In FIG. 8, a route information collection device 301 is a means for reading out the contents of a VPN routing table or a normal routing table from each router on the network 7 and generating route information.
The route information change accepting device 302 described above is means for accepting the route information change notification from the network management server (200).

The route history information writing device 303 is means for writing the changed route information on the time axis,
The route history information reading device 304 described above is means for reading label information from the route history information DB 310. The network 7 is an MPLS network, and the above-described path information is label information including an intra-network transfer label.

The traffic collection / setting / cancellation device 305 is a means for setting or canceling the traffic measurement location,
The traffic measurement device 306 is means for collecting traffic at the set traffic measurement points.

The traffic transmission accepting device 307 is a means for accepting traffic calculation for traffic display.
The traffic counting device 308 described above is means for calculating traffic for traffic display,
The traffic data reading device 309 is means for reading out the corresponding traffic from the traffic DB 311.

The route history information DB 310 described above is means for storing the changed route information collected by the device 301.
The traffic DB 311 described above is means for storing information collected by the device 306.

  The operation in the network management system 1 configured as described above with reference to FIGS. 6 to 8 is as follows.

  The network administrator registers the setting information of the router on the MPLS network using the network configuration information management apparatus 101 and stores it in the network configuration information DB 110. The service manager registers the VPN service information using the service information management apparatus 102 and stores it in the service information DB 111. The monitoring and operation department of the service manager registers the traffic measurement location in the traffic measurement device 306 using the traffic collection / setting / release receiving device 204 and the traffic collection / setting / release device 305. For example, the VPN routing table and the routing table are read from each router on the network 7 by using the route information collecting device 301 and the route history information writing device 303 in the once / daily periodic process, and stored in the route history information DB 310. Store. Based on the traffic measurement setting period, the traffic measurement device 306 starts traffic collection and writes the traffic data collected in the traffic DB 311.

  When the network management device detects a router failure or congestion, the route information change detection device 104 uses the route information change notification device 103, the route information change relay device 203, and the route information change notification reception device 302, Informs the route information collection device 301 that the route has been changed. The route information changing device 301 reads the contents of the VPN routing table and the normal routing table from each router on the network and reflects them in the route history information DB 310.

  Here, when there is a traffic display request from the traffic display client 401 (FIG. 6), the traffic display device 207 informs the traffic processing device 205 that there has been a traffic display request. The traffic processing device 205 sends the request to the traffic counting device 308 via the traffic transmission requesting device 206 and the traffic transmission accepting device 307. The traffic counting device 308 reads label information based on the traffic collection time from the route history information DB 310, reads traffic that matches the label information from the traffic DB 311 via the traffic data reading device 309, and calculates a traffic value. Then, the calculated traffic value is returned as a response result to the traffic display device 207 via the traffic transmission accepting device 307 → the traffic transmission requesting device 206 → the traffic processing device 205.

  The problem to be solved by the present invention and the solution thereof will become more apparent from the following specific examples.

  FIG. 9 is a diagram showing the relationship between the system 1 of the present invention and the network 7 with a specific example. In the figure, the configuration of FIGS. 6 to 8 is positioned in the upper part of the figure, and the network 7 exists under the structure. The device 100 collects, for example, failure occurrence information from the network 7, and the device 300 reads out route information (label) from each router in the network, collects traffic by the own device 306, and obtains the resulting traffic data. obtain. An enlarged view of the network 7 side in this figure is as follows.

  FIG. 10 is an enlarged view of the network 7 of FIG. In this figure, the VPN for Company A and the VPN for Company B are accommodated under the edge routers ER-1 to ER-4. These edge routers ER-1 to ER-4 can perform data transfer via the core routers CR-1 to CR-3.

  This data transfer is routed according to a Label Forwarding Table (LFT) held for each router (ER, CR). These LFTs are further enlarged and shown in FIGS.

  For example, referring to FIG. 11, the LFT of the edge router ER-1 includes “destination address”, “VPN identification label”, “exit ER address”, and “out-network transfer label” (outbound transfer label). Each information is set. In the LFT of the core router CR-1, each information of “In network transfer label” (ingress transfer label), “Exit I / F” (exit interface) and “Out network transfer label” is set. Has been. In the example of this figure, the outgoing transfer label of the edge router ER-1 is “24”. The core router CR-2 receiving this “24” as the incoming transfer label replaces it with the outgoing transfer label “12” and sends it to the destination. These labels are the above-described path information and are written in the VPN packet.

  FIG. 13 is a diagram showing a frame 10 of the VPN packet transferred on the line.

  In the MPLS network, the IP header (IP address) C is not used, but is transferred while looking at the intra-network transfer label E of the shim header B. The intra-network transfer label E is replaced with another label every time it passes through the relay router (ER, CR). On the other hand, the VPN identification label F never changes. Here, the logic for measuring the traffic of the VPN packet transferred from the Tokyo head office of the company A to the Osaka branch office and a specific example of the above-described problem will be described with reference to FIGS.

  The VPN identification label of company A is 200 (FIG. 11), and when a VPN packet is transmitted from the Tokyo head office (source) of company A, the edge router ER-1 that has received the packet transmits the VPN packet to the VPN packet. , 24 (VPN identification label F is fixed at 200) is assigned as an intra-network transfer label E in the shim header B, and transmitted to the core router CR-2.

  Upon receiving this, the CR-2 receives the VPN packet of the intra-network transfer label 24, replaces it with the intra-network transfer label 12, and transmits it to the CR-1. When CR-1 receives the VPN packet of the intra-network transfer label 12, it replaces the label with 28 and transmits it to CR-3.

  Upon receiving the VPN packet of the intra-network transfer label 28, CR-3 replaces the label with 33 and transmits it to ER-3. When the ER-3 receives the VPN packet having the intra-network transfer label 33 and the VPN identification label 200, the ER-3 removes the shim header B in the packet and sends the VPN packet to the interface of the exit 0 (FIG. 12) of the ER-3. Send.

  In this way, VPN packets are transferred from the Tokyo head office of company A to the Osaka branch of company A, which is the transmission source. At this time, the intra-network transfer label E replaced at each router is defined according to the destination by the MPLS LDP protocol. For example, the intra-network transfer label E is replaced from 24 to 12 in CR-2, and this label 12 means that it is for ER-3.

  Thus, when measuring the traffic value of VPN packets transferred from the Tokyo headquarters of Company A to the Osaka branch, the intra-network transfer label E of all routers is decoded, and the packet size is added in units of labels according to the traffic collection location. It will be good if you do. In the example of FIGS. 10 to 12, since traffic values are collected at the exit 0 of CR-2 (routed toward CR-1), the traffic from the Tokyo head office of Company A to the Osaka branch office is identified by VPN. What is necessary is just to count the packet size of the VPN packet in which the label F is 200 and the intra-network transfer label E is 12.

  Looking at the problems described above, for example, if a line failure occurs between CR-2 and CR-1, the MPLS LDP described above is used to relieve the VPN packet that flows between them. The protocol changes the route so that the VPN packet does not relay the CR-1. That is, the label information is changed.

  In such a case, the conventional traffic counting device 308 ′ (FIG. 5) continues to count the intra-network transfer labels 12 as they are before the route change. However, since this label 12 already means another traffic (for example, from the Tokyo branch of company A to the Kobe branch), an erroneous calculation of the traffic value occurs. This is the problem described above.

  In FIG. 14, (A) shows a route change history, and (B) shows a traffic count reflecting the history. This figure (A) shows the information managed by path | route history information DB310 (= means 4) by this invention of FIG. In this example, label E, which was 12 until time 9/5, indicates that the route has been changed to label E = 10 due to, for example, the occurrence of a line failure at time 9/6. Further, it indicates that the line failure has been recovered at time 9/7 and the label E has returned to 12.

On the other hand, referring to FIG. 14B, the devices 308, 309, 306, and 311 in FIG. 8 collect traffic and obtain data as shown in this figure. Here, if there is no DB 310, device 304, etc. in FIG. 8 (conventional), the device 308 has a traffic volume of label E = 12 from the Tokyo head office of company A to the Osaka branch office from time 9/5 to 9/7. As shown in FIG. 2B, 1200 (◯) +1000 (×) +1100 (◯) = 3300
Will be counted.

However, actually, referring to the history of FIG. 9A, the label E of the VPN packet temporarily changes from E = 12 to E = 10 at time 9/6. In the traffic aggregation of FIG. (B), it is necessary to aggregate E = 10 (に つ い て) at time 9/6. Therefore, the total aggregate traffic volume is
1200 (◯) +1200 (◎) +1100 (◯) = 3500
It becomes. Note that the packet with label E = 12 at that time is different from the traffic of interest.

  As understood from the above example (FIG. 14), by further considering the route history, it is possible to realize traffic measurement with higher accuracy than in the past.

  Although the above description has been made for the entire network management system, the network management device (100) alone and the traffic measurement device (300) alone are characteristic.

First, looking at the former, when there is a change in the route information indicating the transfer route in the network 7 of the VPN packet, it has at least route information change notification means 3 for notifying that the route information has changed. Furthermore, the network management device is characterized by the fact that it is included in the traffic measurement device 300 having the traffic measurement means 6 that collects the traffic amount of VPN packets at predetermined locations in the network 7 and totals the traffic amount within a unit time. In the network management apparatus, the route information change notifying unit 3 notifies the route history holding unit 4 that aggregates the traffic amount in cooperation with the traffic measuring unit that the route information has been changed. is there.

On the other hand, looking at the latter, the traffic measuring means 6 for collecting the traffic amount of the VPN packet at a predetermined location in the network 7 and totaling the traffic amount within a unit time, and the transfer route of the VPN packet in the network 7 are shown. When there is a change in the route information, the route history holding unit 4 that holds the history regarding the route change of the VPN packet, and the route history holding unit 4 are referred to when the traffic amount is totaled in cooperation with the traffic measurement unit. A traffic measuring device characterized in that it has at least a tally adjusting means 5 for adjusting the tally at the time when the route is changed to a tally adapted to the changed route, and also a VPN packet network 7 When there is a change in the route information indicating the transfer route within 7, the route information change notification The route history holding means 4 receives the route change information notified from the means, and is a traffic measuring device.

  Furthermore, the present invention is also characterized as a method for operating the network jurisdiction system. When it is detected that there is a change in the route information, the first step of notifying the route change information to the outside, and the route change information include When notified, the second step of creating and maintaining a history regarding the route change of the VPN packet, and referring to the above history when counting the traffic volume, if there is a route change at a certain time And a third step of adjusting the total to a total corresponding to the change path.

  The embodiment of the present invention described in detail above is as follows.

(Appendix 1)
In the network jurisdiction system,
Traffic measuring means for collecting the traffic volume of VPN packets at a predetermined location in the network and totaling the traffic volume within a unit time;
Route information change notifying means for notifying that the route information has changed when the route information indicating the transfer route of the VPN packet in the network is changed;
On the traffic measurement means side, based on the change notification from the route information change notification means, a route history holding means for holding a history relating to the route change of the VPN packet;
In cooperation with the traffic measurement means, the route history holding means is referred to when the traffic amount is aggregated, and when the route is changed at a certain time, the aggregation at the time is adjusted to the aggregation corresponding to the changed route. A network jurisdiction system further comprising: a tally adjustment means.

(Appendix 2)
The network jurisdiction system includes at least a network management device and a traffic measurement device cooperating with the network management device,
The traffic measurement device includes the traffic measurement means, the route history holding means, and the aggregation adjustment means.
The network management system according to appendix 1, wherein the network management device includes the route information change notification means.

(Appendix 3)
The network jurisdiction system is:
On the one hand, it further includes a traffic management device that exchanges predetermined information with the network management device, and on the other hand, exchanges predetermined information with the traffic measurement device,
The traffic management device includes a route information change relay unit that relays route change information from the route information change notification unit to the route history holding unit.
The network jurisdiction system according to appendix 2, wherein the traffic measurement device includes route information change accepting means for accepting the route change information from the route information change relay means.

(Appendix 4)
The network management system according to appendix 1, wherein the network is an MPLS network, and the route information is label information including an intra-network transfer label.

(Appendix 5)
In the network management device,
A network management apparatus comprising at least route information change notification means for notifying that the route information is changed when the route information indicating the transfer route in the network of the VPN packet is changed.

(Appendix 6)
The traffic amount of the VPN packet at a predetermined location in the network is collected, and the traffic amount is within a traffic measurement device having a traffic measurement unit that aggregates the traffic amount within a unit time. 6. The network management device according to appendix 5, wherein the route information holding unit that performs aggregation is notified from the route information change notification unit that the route information has been changed.

(Appendix 7)
In the traffic measurement device,
Traffic measuring means for collecting the traffic amount of VPN packets at a predetermined location in the network and totaling the traffic amount within a unit time;
Route history holding means for holding a history of route change of the VPN packet when there is a change in route information indicating a transfer route in the network of the VPN packet;
In cooperation with the traffic measurement means, the route history holding means is referred to when the traffic amount is aggregated, and when the route is changed at a certain time, the aggregation at the time is adjusted to the aggregation corresponding to the changed route. Total adjustment means to
A traffic measuring device having at least

(Appendix 8)
When the route information indicating the transfer route of the VPN packet in the network is changed, the route history holding unit receives the route change information notified from the route information change notification unit. The traffic measuring device according to appendix 7.

(Appendix 9)
An operation method in a network jurisdiction system having at least traffic measurement means for collecting the traffic volume of VPN packets at a predetermined location in the network and totaling the traffic volume within a unit time,
When detecting that the route information has changed, notifying the route change information;
When the route change information is notified, creating and holding a history about the route change of the VPN packet;
In the aggregation of the traffic volume, referring to the history, and when the route is changed at a certain time, adjusting the aggregation at the time to the aggregation according to the changed route;
A method for operating a network jurisdiction system, comprising:

1 is a basic configuration diagram of a network management system according to the present invention. (A) is a concrete whole structure of the conventional system 1, (B) is a concrete whole block diagram of the system 1 of this invention. It is a figure which expands and shows the network management apparatus 100 in FIG. It is a figure which expands and shows the traffic management apparatus 200 in FIG. 2 (A). It is a figure which expands and shows the traffic measuring device 300 in FIG. 2 (A). It is a figure which expands and shows the network management apparatus 100 in FIG. It is a figure which expands and shows the traffic management apparatus 200 in FIG. 2 (B). It is a figure which expands and shows the traffic measuring device 300 in FIG. 2 (B). It is a figure which shows the relationship between the system 1 of this invention, and the network 7 with a specific example. It is a figure which expands and shows the network 7 of FIG. FIG. 4 is an enlarged view (No. 1) showing an LFT held for each router. It is the figure (the 2) which expands and shows LFT hold | maintained for every router. It is a figure which shows the flame | frame of the VPN packet transferred on a circuit | line. (A) The figure showing the history of a route change, (B) The figure showing the traffic total reflecting the history.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Network jurisdiction system 2 Path | route information change detection means 3 Path | route information change notification means 4 Path | route history holding means 5 Total adjustment means 6 Traffic measurement means 7 Network 8 Path | route information change relay means 9 Path | route information change reception means

Claims (6)

In the network jurisdiction system,
Traffic measuring means for collecting the traffic amount of VPN packets at a predetermined location in the network and totaling the traffic amount within a unit time;
Route information change notifying means for notifying that the route information has changed when the route information indicating the transfer route of the VPN packet in the network is changed;
Route history information writing means for writing the changed route information notified from the route information change notification means on the time axis;
In the traffic measurement unit, a route history holding unit that holds a history of route change on the time axis by the route history information writing unit of the VPN packet;
In cooperation with the traffic measurement means, the route history holding means is referred to when the traffic amount is aggregated, and when the route is changed at a certain time, the aggregation at that time is changed to match the changed route. And tally adjusting means for adjusting the tally of the traffic measuring means by the changed tally,
A network jurisdiction system characterized by comprising: The network jurisdiction system includes at least a network management device and a traffic measurement device cooperating with the network management device,
The traffic measurement device includes the traffic measurement means, the route history holding means, and the aggregation adjustment means.
The network management system according to claim 1, wherein the network management device includes the route information change notification unit. The network jurisdiction system is:
On the one hand, it further includes a traffic management device that exchanges predetermined information with the network management device, and on the other hand, exchanges predetermined information with the traffic measurement device,
The traffic management device includes a route information change relay unit that relays route change information from the route information change notification unit to the route history holding unit.
The network management system according to claim 2, wherein the traffic measurement device includes route information change accepting means for accepting the route change information from the route information change relay means. In the traffic measurement device,
Traffic measuring means for collecting the traffic amount of VPN packets at a predetermined location in the network and totaling the traffic amount within a unit time;
Route information change notifying means for notifying that the route information has changed when the route information indicating the transfer route of the VPN packet in the network is changed;
Route history information writing means for writing the changed route information notified when the route information indicating the transfer route in the network of the VPN packet is changed on the time axis;
In the traffic measurement unit, a route history holding unit that holds a history of route change on the time axis by the route history information writing unit of the VPN packet;
In cooperation with the traffic measurement means, the route history holding means is referred to when the traffic amount is aggregated, and when the route is changed at a certain time, the aggregation at that time is changed to match the changed route. And tally adjusting means for adjusting the tally of the traffic measuring means by the changed tally,
A traffic measuring device having at least When the route information indicating the transfer route of the VPN packet in the network is changed, the route history holding unit receives the route change information notified from the route information change notification unit. The traffic measurement device according to claim 4 . An operation method in a network jurisdiction system having at least traffic measurement means for collecting the traffic volume of VPN packets at a predetermined location in the network and totaling the traffic volume within a unit time,
Collecting the amount of VPN packet traffic at a predetermined location in the network and counting the amount of traffic within a unit time; and
Notifying that there is a change in the route information when there is a change in the route information indicating the transfer route in the network of the VPN packet;
Writing on the time axis the changed route information notified by the notifying step;
Maintaining a history of path changes on the time axis of the VPN packet written by the writing step;
When totaling the traffic volume, the history regarding the route change held in the holding step is referred to, and when the route change occurs at a certain time, the total at that time is adjusted to the changed route. Changing and totaling, and adjusting the total of the traffic measuring means by the changed total;
A method for operating a network jurisdiction system, comprising:

Images