CN101753366A - Method, equipment and system for realizing stream statistics of virtual private network - Google Patents

Abstract

The embodiment of the present invention relates to the communication field, and provides a method for realizing VPN traffic statistics of a virtual private network, including: receiving a statistical message from an operator P device, and the statistical message includes statistics of Multi-Protocol Label Switching MPLS messages Data and the destination operator PE identification of the MPLS message; receiving label information from the destination PE; performing VPN traffic statistics according to the statistical message and the label information. In the solution provided by the embodiment of the present invention, deploying NetStream on the P device can save user costs compared to deploying NetStream on many PEs connected to the VPN in the prior art. The transmission path in the network can support network planning. The invention also relates to a device and a system for realizing virtual private network traffic statistics.

Description

A method, device and system for realizing virtual private network traffic statistics

technical field

The invention relates to the communication field, in particular to a method, device and system for realizing traffic statistics of a virtual private network.

Background technique

VPN (Virtual Private Network, Virtual Private Network) is a private private network built using a public network. Through VPN, enterprises can connect their remote offices, traveling staff and business partners at a significantly lower cost. At present, VPNs are widely used. Both enterprises and operators have the need to understand the traffic distribution and business models of VPNs.

NetStream (traffic statistics engineering) technology is a statistics and release technology based on network flow information. Using NetStream technology, it can classify and count the traffic and resource usage in the network, manage and bill based on various services and different QoS (Quality of Service, service quality), and provide data support for network planning .

Figure 1 is a simplified schematic diagram of a VPN network. As shown in FIG. 1 , a first CE (Customer Edge, customer edge device) 122 and a second CE 124 are located in the first VPN 120, and a third CE 142 and a fourth CE 144 are located in the second VPN 140. The CEs in the first VPN 120 communicate through the carrier network 110 . The CEs in the second VPN 140 also communicate through the carrier network 110 . The operator network 110 includes a P device (Provider, operator) 114, a first PE (Provider Edge, operator edge equipment) 112, a second PE 116, and a third PE 118. In the network shown in FIG. 1 , if the traffic statistics of the first VPN 120 are to be collected, NetStream needs to be deployed on both the first PE 112 and the third PE 118 . Similarly, if the traffic statistics of the second VPN 140 are performed, NetStream needs to be deployed on both the first PE 112 and the second PE 116 . It can be seen that to collect statistics on the traffic of a VPN, NetStream needs to be deployed on all PEs connected to the VPN.

For VPN, IP (Internet Protocol, Internet Protocol) packets are forwarded from CE to PE; MPLS (Multi-Protocol Label Switching, multi-protocol label switching) is forwarded from PE to P, and then to another PE. Exchange) messages. Therefore, when NetStream is deployed on PEs, there are two aspects. One is to collect statistics on VPN IP packets on the user side of the PE, that is, the side close to the CE; the other is to collect statistics on the network side of the PE. , that is, the side close to the P device collects statistics on MPLS packets. No matter which kind of statistics is used, the statistical data must be sent from the PE to the NSC (NetStream Collector, stream collector). The NSC is responsible for collecting and storing the statistical information and is one of the network management devices. Finally, the network management device analyzes the data collected by the NSC to complete the statistics of VPN traffic.

In the process of realizing the present invention, the inventors of the present invention found that in the above-mentioned prior art, deploying NetStream on multiple PEs is not only costly but also data scattered. In addition, when the number of VPN users increases or decreases, or the address is migrated (that is, the interface through which the PE accesses the VPN changes). NetStream may need to be redeployed and configured. In addition, because the statistics are performed on the PE, only the traffic data flowing in and out of the operator's network through the VPN can be simply analyzed, and it is impossible to analyze the traffic trajectory in the operator's network and each device in the operator's network from the perspective of the entire network. The business model carried by the VPN cannot provide sufficient supporting data for VPN planning.

Contents of the invention

Based on the above analysis, in order to solve the problems in the prior art that NetStream needs to be deployed on multiple PEs, the cost is high, and the data is scattered, the embodiment of the present invention provides a method for realizing virtual private network VPN traffic statistics, including:

Receive a statistical message from the operator P device, the statistical message includes the statistical data of the multi-protocol label switching MPLS message and the PE identifier of the destination operator edge device of the MPLS message;

receiving label information from the target PE;

Perform VPN traffic statistics according to the statistical packets and the label information.

On the other hand, an embodiment of the present invention provides a network management device, including:

The first receiving unit is configured to receive a statistical message from an operator P device, wherein the statistical message includes statistical data of a multi-protocol label switching MPLS message and a destination operator PE identifier of the MPLS message;

a second receiving unit, configured to receive label information from the target PE;

A traffic statistics unit, configured to implement virtual private network VPN traffic statistics according to the statistical message and the label information.

In yet another aspect, an embodiment of the present invention provides an operator device, including:

Multi-protocol label switching MPLS message statistics unit, used to deploy the traffic statistics project NetStream, to obtain the statistical data of MPLS messages;

A destination operator's edge device PE identifier acquisition unit, configured to acquire the destination PE identifier of the MPLS message;

A statistical message sending unit, configured to send a statistical message to a network management device, where the statistical message includes statistical data of the MPLS message and the target PE identifier.

In a fourth aspect, an embodiment of the present invention provides a system for realizing VPN traffic statistics, including a network management device, a carrier P device, a first carrier edge device PE, and a virtual private network VPN traffic from a second carrier edge device PE, passing through the P device to reach the first PE;

The P device is used to deploy the traffic statistics project NetStream, perform multi-protocol label switching MPLS packet statistics, and send statistical packets to the network management device, and the statistical packets include statistical data and the destination PE of the MPLS packets logo;

The first PE is used to deploy the label publishing function of NetStream, and publish label information to the network management device;

The network management device is configured to perform VPN traffic statistics according to the statistical packets and the label information.

In the solution provided by the embodiments of the present invention described above, deploying NetStream on the P device can save user costs compared to deploying NetStream on many PEs connected to the VPN in the prior art. In addition, by performing MPLS on the P device Packet statistics can also grasp the transmission path of VPN traffic in the operator's network, which can support network planning.

Description of drawings

Fig. 1 is a simplified schematic diagram of a VPN network;

Fig. 2 is a simplified schematic diagram of performing VPN traffic statistics in one embodiment of the present invention;

FIG. 3 is a schematic diagram of a network management device performing VPN traffic statistics in an embodiment of the present invention;

Fig. 4 is a simplified schematic diagram of VPN traffic statistics in yet another embodiment of the present invention;

FIG. 5 is a schematic diagram of a network management device performing VPN traffic statistics in an embodiment of the present invention;

FIG. 6 is a flowchart of a method for performing VPN traffic statistics in an embodiment of the present invention;

FIG. 7 is a simplified schematic diagram of a network management device implementing VPN traffic statistics in an embodiment of the present invention;

Fig. 8 is a simplified schematic diagram of P equipment in one embodiment of the present invention;

Fig. 9 is a simplified schematic diagram of P equipment in another embodiment of the present invention;

FIG. 10 is a simplified schematic diagram of a VPN traffic statistics system in an embodiment of the present invention.

Detailed ways

The detailed description will be described below in conjunction with the accompanying drawings and specific embodiments. However, it should be noted that the following embodiments are only examples for helping to understand the technical solutions, and are not intended to limit the present invention.

Fig. 2 is a simplified schematic diagram of performing VPN traffic statistics in an embodiment of the present invention. As shown in Figure 2, VPN traffic statistics include:

202. Deploy NetStream on the P device, perform MPLS packet statistics, and send the statistical packet to the network management device, the statistical packet includes the statistical data of the MPLS packet and the destination PE identifier of the MPLS packet, for example, The statistical data of the MPLS message and the destination PE identifier of the MPLS message are encapsulated into the above statistical message.

For example, you can deploy NetStream on key P devices through which VPN traffic passes, or deploy NetStream on multiple P devices through which VPN traffic passes. Operators can deploy according to their own needs and/strategies.

For example, the target PE identifier may be the IP address of the target PE. For example, the P device performs a local query according to the outer label of the MPLS packet, and obtains the IP address of the destination PE. As shown in Figure 2, in the statistical packets sent by the P device, the Out-label (outer label) is 400, the In-label (inner label) is 1024, and the PE-Address (the IP address of the destination PE) is 10.1 .1.1.

204. Deploy the label information publishing function of NetStream on the target PE, and the target PE sends the label information of the target PE to the network management device, and the label information includes TAL (Time Application Label, time application label) information. For example, the TAL information may include the mapping relationship between the IP address of the target PE and the Router-id of the target PE, and the mapping relationship between the Router-id of the target PE and the label value of the target PE. For another example, the TAL information may include the mapping relationship among the local IP address, Router-id and label value. As shown in Figure 2, in the TAL information sent by PE1 to the network management device, the Router-id (routing device identifier) is 1.1.1.1, the PE-Address (the IP address of the destination PE) is 10.1.1.1; the Router-id is 1.1.1.1, Label (label) is 1024, Type (type) is vpls (Virtual Private LAN Service, virtual private LAN service), Index (VPN index) is 100.

There is no sequence restriction between the above 204 and 202 . It is also possible to execute 204 first, and then execute 202, or execute at the same time.

206. The network management device performs VPN traffic statistics according to the above statistical packets and label information.

For example, the process of VPN traffic statistics includes: the network management device extracts the IP address of the destination PE from the statistical packets sent by the P device, obtains the Router-id corresponding to the IP address, and then adds the The carried inner label and the queried Router-id are used as the Key (key) value, and the label information from the destination PE is queried to obtain the corresponding VPN type and VPN index, and realize the corresponding combination of statistical data and TAL information. As shown in the example in Figure 3, the IP address of the destination PE (that is, 10.1.1.1) is extracted from the statistical message sent by the P device; the IP address of the destination PE (that is, 10.1. 1.1) The corresponding Router-id is 1.1.1.1; then, use the inner label (1024) carried in the statistical message sent by the P device and the queried Router-id (1.1.1.1) as the Key value, and query the label information to obtain Corresponding VPN type and VPN index. As another example in Figure 3, the destination PE address (namely 30.3.3.3) is extracted from the statistical message sent by the P device; The Router-id is 1.1.1.1; then, use the inner label (2000) carried in the statistical packet sent by the P device and the queried Router-id (1.1.1.1) as the Key value to query the label information to obtain the corresponding VPN type and VPN index.

If it is necessary to further analyze the data and present the data to the user in a friendly manner, the above VPN traffic statistics process may also include:

208. After the network management device implements the corresponding combination of statistical data and TAL information, that is, after identifying VPN traffic data, it can query the destination PE for auxiliary information as needed. For example, the auxiliary information includes the VPN name, and for example, auxiliary information Including VPN name, MAC (Medium Access Control, media access control) or VRF (Virtual Routing and Forwarding, virtual routing and forwarding) routing, etc. When the network management device performs auxiliary information query, it can use SNMP (Simple Network Management Protocol, Simple Network Management Protocol), and use the VPN type and VPN index as the Key value to realize the query. For example, query the MAC of L2VPN (Layer 2 virtual private network, Layer 2 virtual private network), or query the VRF route of L3VPN (Layer 3virtual private network, Layer 3 virtual private network).

Of course, auxiliary information, such as VPN name, MAC or VRF route, etc. may also be carried in the label information sent by the destination PE to the network management device.

In another embodiment of the present invention, the above-mentioned step 202 can be implemented in another way, and the target PE identifier can be a Router-id (routing device identifier), that is, the P device obtains the Router-id, and the Router-id together with the statistical data, They are also sent to the network management device. Correspondingly, in the above step 204, the label information issued by the destination PE to the network management device includes TAL information, and the TAL information includes a mapping relationship between Router-id and label value; in step 206, the step of querying the Router-id according to the IP address of the destination PE can be omitted. In this embodiment, the Router-id is only an example, and other identifiers that can uniquely identify the destination PE, such as character strings, special symbols, and specific numbers, may also be used.

Fig. 4 is a simplified schematic diagram of VPN traffic statistics in still another embodiment of the present invention. As shown in Figure 4, VPN traffic statistics include:

402. Deploy NetStream on the P device, and perform policy configuration, and configure the IP address of the PE accessing the VPN to the P device. For another example, the IP address of the PE accessing the VPN and the mapping relationship between the IP address and the corresponding Router-id can be configured on the P device. The P device selectively collects statistics on MPLS packets according to the configured policy, and sends a statistics packet to the network management device. The statistics packet includes the statistical data of the MPLS packets and the ID of the destination PE. For example, the statistical data of the MPLS message and the destination PE identifier of the MPLS message are encapsulated into the above statistical message.

For example, according to the configured policy, the P device collects statistics on the MPLS packets when the IP address of the destination PE belongs to the configured IP address range.

For policy configuration, the IP address of the PE connected to the VPN and the mapping relationship between the IP address and Router-id are configured on the P device, the destination PE identifier included in the statistical message can be Router-id, and the Router-id -id corresponds to the destination IP address of the MPLS packet. As shown in Figure 4, in the statistical packets sent by the P device, the Out-label is 400, the In-label is 1024, and the Router-id is 1.1.1.1. Of course, the destination PE identifier is not limited to the Router-id, and may also be other identifiers that can uniquely identify the destination PE, such as character strings, special symbols, and specific numbers.

For the case of configuring the IP address of the PE that accesses the VPN to the P device during policy configuration, the destination PE identifier included in the statistical message may be the destination IP address of the MPLS message.

404. Deploy the label information publishing function of NetStream on the target PE, and the target PE sends label information to the network management device, and the label information includes TAL (Time Application Label, time application label) information.

For example, when configuring the policy, the IP address of the PE connected to the VPN and the mapping relationship between the IP address and the Router-id are configured on the P device, and the TAL information released by the destination PE can include Router-id to label value mapping. As shown in Figure 4, in the label information sent by PE1 to the network management device, Router-id is 1.1.1.1, Label is 1024, Type (type) is vpls, and Index (VPN index) is 100.

For another example, for the case where the IP address of the PE connected to the VPN is configured to the P device during policy configuration, the TAL information released by the destination PE may include the mapping relationship between the local IP address and Router-id, the Router-id The mapping relationship with tag values. In another implementation manner, the TAL information may include the mapping relationship among the local IP address, the Router-id, and the label value.

406. The network management device performs VPN traffic statistics according to the above statistical packets and label information.

For example, for the case where the destination PE identifier is Router-id in the statistics packet sent by the P device, the process of VPN traffic statistics includes: the network management device extracts the inner label and Router-id, as the Key value, queries the label information from the PE, obtains the corresponding VPN type and VPN index, and realizes the corresponding combination of statistical data and TAL information. As shown in Figure 5, extract the Router-id (i.e. 1.1.1.1) and inner label (i.e. 1024) from the statistical message sent by the P device; use the above-mentioned Router-id and inner label as the Key value to query the label Information, get the corresponding VPN type is vpls, and VPN index, etc. As another example in Figure 5, extract the Router-id (ie 2.2.2.2) and inner label (ie 1024) from the statistical message sent by the P device; use the above-mentioned Router-id and inner label as the Key value Query label information, get the corresponding VPN type is 13vpn, and VPN index, etc. As another example in Figure 5, the Router-id (i.e. 1.1.1.1) and the inner label (i.e. 2000) are extracted from the statistical message sent by the P device; the above-mentioned Router-id and inner label are used as the Key value Query the label information, get the corresponding VPN type is vpws (virtual private wire service, virtual private network service), and VPN index, etc.

If it is necessary to further analyze the data and present the data to the user in a friendly manner, the above VPN traffic statistics process may also include:

408. After the network management device implements corresponding merging of statistical data and TAL information, that is, after identifying VPN traffic data, it can query the destination PE for auxiliary information, such as VPN name, MAC or VRF route, etc. as required. When the network management device performs auxiliary information query, it can use SNMP (Simple Network Management Protocol, Simple Network Management Protocol).

Of course, auxiliary information, such as VPN name, VRF route, etc., may also be carried in the label information sent by the destination PE to the network management device.

Fig. 6 is a flow chart of a method for performing VPN traffic statistics in one embodiment of the present invention. As shown in Fig. 6, the method for performing VPN traffic statistics includes:

602. Receive a statistical message from the P device, where the statistical message includes statistical data of the MPLS message and a destination PE identifier of the MPLS message. For example, the destination PE identifier may be the IP address of the destination PE, or Router-id, or other identifiers that can uniquely identify the destination PE, such as character strings, special symbols, and specific numbers.

604. Receive label information from the destination PE, where the label information includes TAL information. For example, the TAL information may include the mapping relationship between the local IP address and the Router-id, and the mapping relationship between the Router-id and the label value. The TAL information can also only include the mapping relationship between Router-id and label value

606. Perform VPN traffic statistics according to the above statistical packets and label information.

For example, extract the IP address of the destination PE from the above statistical message, query the Router-id corresponding to the IP address, and then use the inner label carried in the statistical message and the queried Router-id as the Key value , query the label information, obtain the corresponding VPN type and VPN index, and realize the corresponding combination of statistical data and TAL information.

For another example, extract the inner label and Router-id from the statistical message sent by the P device, use it as the Key value, query the label information, obtain the corresponding VPN type and VPN index, and realize the correspondence between statistical data and TAL information merge.

The method for packet statistics in the foregoing embodiments may also include:

608. After the network management device implements corresponding merging of statistical data and TAL information, that is, after identifying VPN traffic data, it can query the destination PE for auxiliary information, for example, VPN name, MAC or VRF route, etc., as required. When the network management device performs auxiliary information query, it can use SNMP (Simple Network Management Protocol, Simple Network Management Protocol), and use the VPN type and VPN index as the Key value to realize the query. In this way, the data can be further analyzed and presented to the user in a friendly manner.

Fig. 7 is a simplified schematic diagram of a network management device implementing VPN traffic statistics in an embodiment of the present invention. As shown in Figure 7, the network management devices that implement VPN traffic statistics include:

The first receiving unit 702 is configured to receive a statistical message from the P device, where the statistical message includes statistical data of the MPLS message and a destination PE identifier of the MPLS message. For example, the destination PE identifier may be the IP address of the destination PE, the Router-id of the destination PE, or other identifiers that can uniquely identify the destination PE, such as character strings, special symbols, and specific numbers.

The second receiving unit 704 is configured to receive label information from the target PE, where the label information includes TAL information. For example, the TAL information may include a mapping relationship between an IP address and a Router-id, and a mapping relationship between a Router-id and a label value. The TAL information can also only include the mapping relationship between Router-id and label value

The traffic statistics unit 706 is configured to perform VPN traffic statistics according to the above statistical packets and label information.

The auxiliary information query unit 708 is configured to query the destination PE for auxiliary information, for example, VPN name, MAC or VRF route and so on. In this way, the data can be further analyzed and presented to the user in a friendly manner.

The first receiving unit 702 and the second receiving unit 704 in the above embodiments may also be integrated into one receiving unit. In another embodiment of the present invention, the network management device may not include the auxiliary information query unit 708 . For example, auxiliary information, such as VPN name, MAC or VRF route, etc. may also be carried in the label information sent by the destination PE to the network management device.

Fig. 8 is a simplified schematic diagram of P equipment in an embodiment of the present invention. As shown in Fig. 8, P equipment includes:

The MPLS packet statistics unit 802 is used to deploy NetStream to obtain statistical data of MPLS packets;

The destination PE identifier acquiring unit 804 is configured to acquire the destination PE identifier of the MPLS message through the outer label of the MPLS message. For example, the destination PE identifier may be the IP address of the destination PE, or Router-id, or other identifiers that can uniquely identify the destination PE, such as character strings, special symbols, and specific numbers.

A statistical message sending unit 806, configured to send a statistical message to the network management device, where the statistical message includes statistical data of the MPLS message and a destination PE identifier.

Fig. 9 is a simplified schematic diagram of P equipment in another embodiment of the present invention. As shown in Fig. 9, P equipment includes:

The policy configuration unit 902 is used for policy configuration, and configures the IP address of the VPN access PE to the local. Another implementation is to configure the IP address of the VPN access PE and the mapping relationship between the IP address and Router-id to local;

The MPLS packet statistics unit 904 is used to deploy NetStream to perform statistics on MPLS packets conforming to the configured policy to obtain statistical data; for example, according to the configured policy, the P device, when the IP address of the destination PE belongs to the configured IP address range , collect statistics on the MPLS packets.

The destination PE identifier acquiring unit 906 is configured to acquire the destination PE identifier of the MPLS packet. For example, the destination PE identifier may be an IP address, or Router-id, or other identifiers that can uniquely identify the destination PE, such as character strings, special symbols, and specific numbers. For another example, the destination PE identifier can be obtained from the outer label of the MPLS message; it can also be obtained through a configured policy, for example, the Router-id corresponding to the destination IP address of the MPLS message is obtained according to the configured policy.

A statistical message sending unit 908, configured to send a statistical message to the network management device, where the statistical message includes statistical data of the MPLS message and a destination PE identifier.

Fig. 10 is a simplified schematic diagram of a VPN traffic statistics system in an embodiment of the present invention. As shown in FIG. 10 , the VPN traffic statistics system includes a network management device 1002 , a P device 1006 and a first PE 1008 ; the VPN traffic flows from the second PE 1004 , passes through the P device 1006 , and reaches the destination PE, that is, the first PE 1008 .

The above-mentioned P equipment is used to deploy NetStream, perform MPLS message statistics, and send a statistical message to the network management device 1002, and the statistical message includes the statistical data of the MPLS message and the destination PE identification of the MPLS message;

For example, the destination PE identifier may be the IP address of the destination PE, Router-id, or other identifiers that can uniquely identify the destination PE, such as character strings, special symbols, and specific numbers.

The above-mentioned first PE 1008 is used to deploy the NetStream label information publishing function, and publish the label information to the network management device 1002 .

The label information issued by the PE includes TAL information. For example, the TAL information may include the mapping relationship between the local IP address and the Router-id, and the mapping relationship between the Router-id and the label value. The TAL information released by the PE may also only include the mapping relationship between Router-id and label value.

The aforementioned network management device 1002 is configured to perform VPN traffic statistics according to the aforementioned statistical packets and label information.

For example, the network management device extracts the IP address of the destination PE from the statistics packet sent by the P device, queries the Router-id corresponding to the IP address of the destination PE, and then compares the inner label and The queried Router-id is used as the Key value to query the label information to obtain the corresponding VPN type and VPN index, and realize the corresponding merger of statistical data and TAL.

In another embodiment of the present invention, the above-mentioned first PE1008 can also be used to respond to the auxiliary information query request of the network management device 1002, and send auxiliary information to the network management device 1002, for example, it can be VPN name, MAC or VRF routing etc.

The embodiment of the present invention also provides a kind of PE, including:

The label information publishing unit is configured to deploy the label information publishing function of the NetStream, and send the label information to the network management device. For example, the label information includes TAL information.

In another embodiment of the present invention, PE may also include:

The query request response unit is configured to respond to the auxiliary information query request of the network management device 1002, and send auxiliary information to the network management device, for example, VPN name, MAC or VRF route, etc.

Part of the steps in the embodiments of the present invention can be realized by software, and the corresponding software program can be stored in a readable storage medium, such as an optical disk or a hard disk.

In the solution provided by the embodiment of the present invention, deploying NetStream on the P device can save user costs compared with deploying NetStream on many PEs connected to the VPN in the prior art. In addition, by performing MPLS reporting on the P device It can also grasp the transmission path of VPN traffic in the operator's network and support network planning. In some embodiments of the present invention, the data sent by the PE to the network management device is a Key value instead of all VPN data, which can effectively save network bandwidth. If necessary, the network management device can query the destination PE for more detailed data according to these Key values. In some embodiments of the present invention, by configuring the policy on the P device, the P device can selectively collect statistics on MPLS packets, which can not only effectively save the resources of the P device, but also reduce the burden of data reception and processing by the network management device. Data pressure.

The above is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person familiar with the technology can easily think of changes or replacements within the technical scope disclosed in the present invention. , should be covered within the protection scope of the present invention.

Claims (14)

1. A method for realizing virtual private network VPN traffic statistics, is characterized in that, comprising: Receive a statistical message from the operator P device, the statistical message includes the statistical data of the multi-protocol label switching MPLS message and the PE identifier of the destination operator edge device of the MPLS message; receiving label information from the target PE; Perform VPN traffic statistics according to the statistical packets and the label information. 2. The method according to claim 1, wherein the tag information includes Time Application Label (TAL) information. 3. The method according to claim 2, wherein the target PE identification comprises the Internet Protocol IP address of the target PE; the TAL information comprises the mapping of the IP address of the target PE and the routing device identification of the target PE relationship, the mapping relationship between the routing device identifier of the destination PE and the label value of the destination PE; The performing VPN traffic statistics according to the statistical message and the label information includes: Extracting the IP address of the destination PE, querying the TAL information, and obtaining the routing device identifier corresponding to the IP address of the destination PE; Querying the TAL information according to the routing device identifier and the inner label carried in the statistical message; Obtain the corresponding VPN type and VPN index, and realize the corresponding combination of the statistical data and the TAL information. 4. The method according to claim 2, wherein the target PE identifier includes a routing device identifier of the destination PE; the TAL information includes a mapping relationship between a routing device identifier and a label value; The performing VPN traffic statistics according to the statistical message and the label information includes: Extracting the routing device identifier and the inner label carried in the statistical message; Querying the TAL information according to the routing device identifier and the inner label; Obtain the corresponding VPN type and VPN index, and realize the corresponding combination of the statistical data and the TAL information. 5. The method according to claim 4, wherein the statistical data is obtained by the P device based on a configured policy. 6. The method according to any one of claims 1-4, further comprising: Query the target PE for auxiliary information. 7. A network management device, characterized in that, comprising: The first receiving unit is configured to receive a statistical message from an operator P device, wherein the statistical message includes statistical data of a multi-protocol label switching MPLS message and a destination operator PE identifier of the MPLS message; a second receiving unit, configured to receive label information from the target PE; A traffic statistics unit, configured to implement virtual private network VPN traffic statistics according to the statistical message and the label information. 8. The network management device according to claim 7, further comprising: An auxiliary information query unit, configured to query the target PE for auxiliary information. 9. The network management device according to claim 7 or 8, wherein the statistical data is obtained by the P device based on a configured policy. 10. The network management device according to claim 7 or 8, wherein the first receiving unit and the second receiving unit can be integrated into one receiving unit. 11. An operator's equipment, characterized in that, comprising: Multi-protocol label switching MPLS message statistics unit, used to deploy the traffic statistics project NetStream, to obtain the statistical data of MPLS messages; A destination operator's edge device PE identifier acquisition unit, configured to acquire the destination PE identifier of the MPLS message; A statistical message sending unit, configured to send a statistical message to a network management device, where the statistical message includes statistical data of the MPLS message and the target PE identifier. 12. The operator equipment according to claim 11, wherein the operator equipment further comprises: The policy configuration unit is used for policy configuration, and configures the IP address of the PE accessing the virtual private network VPN to the local; The MPLS packet statistical unit obtaining statistical data of MPLS packets includes: performing statistics on MPLS packets conforming to configuration policies to obtain the statistical data. 13. A system for realizing VPN traffic statistics, characterized in that it includes network management equipment, operator P equipment, first operator edge equipment PE, virtual private network VPN traffic from the second operator edge equipment PE, through the P equipment, reaching the first PE; The P device is used to deploy the traffic statistics project NetStream, perform multi-protocol label switching MPLS packet statistics, and send statistical packets to the network management device, and the statistical packets include statistical data and the destination PE of the MPLS packets logo; The first PE is used to deploy the label publishing function of NetStream, and publish label information to the network management device; The network management device is configured to perform VPN traffic statistics according to the statistical packets and the label information. 14. The system of claim 13, the first PE is further configured to send assistance information to the network management device.

Images