VPN service flow direction monitoring method and system in MPLS network, and related equipment

Abstract

The invention provides a method and a system for monitoring the flow direction of a VPN (Virtual Private Network) service flow in an MPLS (Multi-Protocol Label Switching) network and related equipment, and relates to the technical field of networks. The method comprises the steps that flow direction classification information containing LSP label information and VPN label information is generated for different VPN service flow data in an MPLS network so as to mark all flow directions of the different VPN service flow data, and each flow direction corresponds to a monitoring queue; according to the traffic flow direction classification information of the different VPN service flow data, scheduling the different VPN service flow data to monitoring queues of corresponding traffic flow directions; and carrying out statistics on the VPN service flow data transmitted in each monitoring queue to obtain a VPN service flow direction monitoring result of the MPLS network. According to the invention, accurate monitoring of the data condition of the service flow data in each flow direction can be realized.

Description

Background Art

[0002] As MPLS VPN services develop among global operators, VPN service requirements are becoming increasingly higher, especially for high-end customers, who need to be provided with VPN service information flow analysis services. Currently, the service port traffic size monitoring service provided to VPN users does not meet the end-to-end traffic monitoring needs of customers.

[0003] Currently, the VPN service traffic flow direction monitoring method is Netflow V9 technology, which effectively records and analyzes the one-way data packet flow transmitted between a source address and a destination address through a template-based statistical data output method, and all data packets share the same source port number and destination port number at the transport layer. Netflow V9 collects and analyzes data from preset fields (about 100 fields) in the data packet, which has the problem of large data volume; and it can only monitor based on physical ports or overall traffic, and cannot realize network traffic flow direction monitoring in the business dimension, and the monitoring accuracy is low.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] The present invention provides a method, system and related equipment for monitoring the flow direction of VPN service traffic in an MPLS network, which at least to some extent overcome the technical problems of a VPN service traffic flow direction monitoring solution in an MPLS network having many monitoring fields and low monitoring accuracy.

[0006] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by the practice of the present disclosure.

[0007] According to one aspect of the present disclosure, a method for monitoring VPN service traffic flow direction in an MPLS network is provided, comprising: generating traffic flow direction classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network, wherein the traffic flow direction classification information is used to mark each traffic flow direction of different VPN service flow data, and each traffic flow direction corresponds to a monitoring queue; scheduling different VPN service flow data to the monitoring queue of the corresponding traffic flow direction according to the traffic flow direction classification information of different VPN service flow data; counting the VPN service flow data transmitted in each monitoring queue to obtain a VPN service traffic flow direction monitoring result of the MPLS network; wherein the LSP label information is LSP label information for identifying a label switching path LSP in the MPLS network obtained through a label distribution protocol LDP message; and the VPN label information is VPN service label information for identifying a VPN service instance in the VPN network obtained through a border gateway protocol BGP message.

[0008] In some embodiments, traffic flow classification information including LSP label information and VPN label information is generated for different VPN service flow data in an MPLS network, including: obtaining VPN service flow monitoring configuration information, wherein the VPN service flow monitoring configuration information is used to configure the VPN service information to be monitored and / or the traffic flow information to be monitored; according to the service flow monitoring configuration information, determining the field information of the label exchange path identifier between MPLS network node devices and / or the service label identifier monitoring field in the monitoring field, that is, generating traffic flow classification information including LSP label information and VPN label information.

[0009] In some embodiments, after determining the field information of the label switching path identifier between MPLS network node devices and / or the VPN service label identifier monitoring field in the monitoring field according to the service flow monitoring configuration information, the method further includes: monitoring whether the VPN service flow monitoring configuration information has changed; if the VPN service flow monitoring configuration information has changed, updating the field information of the label switching path identifier between MPLS network node devices and / or the VPN service label identifier monitoring field in the monitoring field according to the changed service flow monitoring configuration information.

[0010] In some embodiments, after determining the field information of the label switching path identifier between network node devices and / or the service label identifier monitoring field in the monitoring field according to the service flow monitoring configuration information, the method further includes: monitoring whether the MPLS network signaling message and / or the VPN service routing signaling message changes; if the MPLS network signaling message and / or the VPN service routing signaling message changes, updating the field information of the path identifier between MPLS network node devices and / or the VPN service identifier monitoring field in the monitoring field according to the changed MPLS network signaling message and / or the VPN service routing signaling message.

[0011] In some embodiments, the VPN service traffic flow direction monitoring result of the MPLS network includes at least one of the following: VPN service traffic flow direction byte count statistics result, VPN service traffic flow direction data packet count statistics result, VPN service traffic flow direction flow velocity statistics result.

[0012] In some embodiments, after counting the VPN service flow data transmitted in each monitoring queue to obtain the VPN service traffic flow direction monitoring results of the MPLS network, the method also includes: obtaining a customized data reporting model, the data reporting model uses on-demand collection and active push to report data; using the data reporting model, encapsulate and report the VPN service traffic flow direction monitoring results of the MPLS network.

[0013] In some embodiments, the VPN service traffic flow monitoring results collected by the MPLS network are encapsulated using the YANG data model; and the encapsulated data is reported based on the Telemetry data reporting mechanism.

[0014] In some embodiments, the VPN service flow data includes at least one of the following: service flow data of a single VPN service in a single traffic flow direction; service flow data of a single VPN service in multiple traffic flows; service flow data of multiple VPN services in multiple traffic flows.

[0015] In some embodiments, before generating traffic flow classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network, the method further includes: if the VPN service flow data is service flow data of a single VPN service instance in a single traffic flow direction, then obtaining the Loopback address and VPN service routing information of a single destination device involved in the VPN service instance in a BGP message through the inbound routing configuration parameters configured for the VPN service instance as the VPN label information in the traffic flow classification information; obtaining the LSP label information of the destination device in an LDP message through the Loopback address of the single destination device involved in the VPN service instance as the LSP label information in the traffic flow classification information; if the VPN service flow data is service flow data of a single VPN service instance in multiple traffic flow directions, then obtaining the multiple destination devices involved in the VPN service instance in a BGP message through the inbound routing configuration parameters configured for the VPN service instance The method comprises the following steps: obtaining the Loopback address and VPN service routing information of the multiple destination devices involved in the VPN service instance in the LDP message as the VPN label information in the traffic flow direction classification information; obtaining the LSP label information of the multiple destination devices involved in the VPN service instance in the LDP message through the Loopback addresses of the multiple destination devices involved in the VPN service instance, as the LSP label information in the traffic flow direction classification information; if the VPN service flow data is the service flow data of multiple VPN service instances in multiple traffic flow directions, obtaining the Loopback address and VPN service routing information of the multiple destination devices involved in each VPN service instance in the BGP message through the inbound routing configuration parameters configured for each VPN service instance, as the VPN label information in the traffic flow direction classification information; obtaining the LSP label information of the multiple destination devices involved in each VPN service instance in the LDP message through the Loopback addresses of the multiple destination devices involved in each VPN service instance, as the LSP label information in the traffic flow direction classification information.

[0016] In some embodiments, before generating traffic flow classification information containing LSP label information and VPN label information for different VPN service flow data in the MPLS network, the method also includes: if the VPN service routing signaling message changes, updating the VPN label information in the traffic flow classification information; if the MPLS network signaling message changes, updating the LSP label information in the traffic flow classification information.

[0017] According to another aspect of the present disclosure, a device for monitoring VPN service traffic flow direction in an MPLS network is also provided, comprising: a VPN service flow data monitoring module, used to generate traffic flow direction classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network, wherein the traffic flow direction classification information is used to mark each traffic flow direction of different VPN service flow data, and each traffic flow direction corresponds to a monitoring queue; a VPN service flow data scheduling module, used to schedule different VPN service flow data to the monitoring queue of the corresponding traffic flow direction according to the traffic flow direction classification information of different VPN service flow data; a VPN service flow data statistics module, used to count the VPN service flow data transmitted in each monitoring queue to obtain the VPN service traffic flow direction monitoring result of the MPLS network; wherein the LSP label information is the LSP label information used to identify the label switching path LSP in the MPLS network obtained through the label distribution protocol LDP message; and the VPN label information is the VPN service label information used to identify the VPN service instance in the VPN network obtained through the border gateway protocol BGP message.

[0018] According to another aspect of the present disclosure, a VPN service traffic flow direction monitoring system in an MPLS network is also provided, comprising: a source router, a destination router and a monitoring controller; wherein the source router is used to generate traffic flow direction classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network after receiving VPN service flow data in the MPLS network, and dispatch different VPN service flow data to monitoring queues of corresponding traffic directions according to the traffic flow direction classification information of different VPN service flow data, wherein the traffic flow direction classification information is used to mark each traffic flow direction of different VPN service flow data, and each traffic flow direction corresponds to a monitoring queue; the monitoring controller is used to count the VPN service flow data transmitted in each monitoring queue to obtain the VPN service traffic flow direction monitoring result of the MPLS network; wherein the LSP label information is the LSP label information used to identify the label switching path LSP in the MPLS network obtained through the label distribution protocol LDP message; and the VPN label information is the VPN service label information used to identify the VPN service instance in the VPN network obtained through the border gateway protocol BGP message.

[0019] In some embodiments, the system also includes: a user-end device, which communicates with the monitoring controller and is used to receive the VPN service traffic flow direction monitoring results of the MPLS network reported by the monitoring controller; wherein the monitoring controller is also used to encapsulate and report the VPN service traffic flow direction monitoring results of the MPLS network using a custom data reporting model.

[0020] According to another aspect of the present disclosure, an electronic device is also provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the above-mentioned methods for monitoring VPN service traffic flow in an MPLS network by executing the executable instructions.

[0021] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method for monitoring the flow direction of VPN service traffic in an MPLS network described in any one of the above is implemented.

[0022] According to another aspect of the present disclosure, a computer program product is provided, including: a computer program or instructions, which, when executed by a processor, implements any one of the above methods for monitoring VPN service traffic flow direction in an MPLS network.

[0023] The method, system and related equipment for monitoring the flow direction of VPN service traffic in an MPLS network provided in the embodiments of the present disclosure generate traffic flow direction classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network to mark the various traffic directions of different VPN service flow data, so that each traffic direction corresponds to a monitoring queue, and then according to the traffic flow direction classification information of different VPN service flow data, the different VPN service flow data are dispatched to the monitoring queue of the corresponding traffic direction, and finally the VPN service flow data transmitted in each monitoring queue are counted to obtain the VPN service traffic direction monitoring result of the MPLS network.

[0024] Through the embodiments of the present disclosure, accurate monitoring of the data status of VPN service flow data in each traffic flow direction in the MPLS network can be achieved.

[0025] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0027] Figure 1 A schematic diagram of a packet header format of a data packet when using Netflow V9 technology to monitor network traffic provided in the related art is shown;

[0028] Figure 2 A flow chart of a method for monitoring VPN service traffic flow direction in an MPLS network according to an embodiment of the present disclosure is shown;

[0029] Figure 3 A flow chart of an optional method for monitoring VPN service traffic flow direction in an MPLS network in an embodiment of the present disclosure is shown;

[0030] Figure 4 A flow chart of adding traffic flow direction classification information to business flow data in an embodiment of the present disclosure is shown;

[0031] Figure 5 A schematic diagram of a traffic flow direction monitoring system for an MPLS Layer 3 VPN service in an embodiment of the present disclosure is shown;

[0032] Figure 6 A flow chart of a method for monitoring traffic flow direction of an MPLS Layer 3 VPN service in an embodiment of the present disclosure is shown;

[0033] Figure 7 A schematic diagram of a process for obtaining traffic flow classification information in an embodiment of the present disclosure is shown;

[0034] Figure 8 A schematic diagram of a process of scheduling different VPN service flow data to corresponding traffic flow direction monitoring queues based on traffic flow direction classification information in an embodiment of the present disclosure is shown;

[0035] Fig. 9 A schematic diagram of a VPN service traffic flow direction monitoring device in an MPLS network according to an embodiment of the present disclosure is shown;

[0036] Fig.10 A schematic diagram of a VPN service traffic flow direction monitoring system in an MPLS network according to an embodiment of the present disclosure is shown;

[0037] Fig.11 A structural block diagram of an electronic device in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0038] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0039] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0040] For ease of understanding, before introducing the embodiments of the present disclosure, several terms involved in the embodiments of the present disclosure are first explained as follows:

[0041] MPLS: Multi-Protocol Label Switching, is a new technology that uses labels to guide data to be transmitted at high speed and efficiently in an open communication network. Multi-protocol means that MPLS not only supports multiple network layer (layer 3) protocols, but is also compatible with multiple data link layer (layer 2) technologies.

[0042] VPN: Virtual Private Network, a private network established on a public network that can provide encrypted communication services. It is widely used in corporate networks. VPN gateways enable remote access by encrypting data packets and converting destination addresses. VPN can be implemented in a variety of ways, including servers, hardware, and software.

[0043] LDP: Label Distribution Protocol, is a key protocol in MPLS networks. In an MPLS network, two label switching routers (LSRs) must agree on the labels used to forward traffic between them or through them.

[0044] VRF: Virtual Routing Forwarding, VPN routing forwarding table, also known as VPN service instance. PE (Provider Edge Router) establishes and maintains a special entity for directly connected sites (Site). Each site has its own VPN service instance on PE. Each VPN service instance contains the routing forwarding table of one or more CE (Customer Edge Router) directly connected to the PE. In order to achieve intercommunication between sites in the same VPN, the VPN service instance also contains the routing information of sites belonging to the same VPN located on other PEs.

[0045] The specific implementation of the embodiment of the present disclosure is described in detail below with reference to the accompanying drawings.

[0046] As introduced in the background technology section of the present disclosure, the current network traffic monitoring method generally adopts NetFlow V9 technology. Figure 1 The following is a diagram showing a packet header format of a data packet when using Netflow V9 technology to monitor network traffic in a related art. Figure 1 As shown, the meaning of each field is described as follows:

[0047] Version Number: The data stream record format version number of the output data packet.

[0048] Count: The total number of template, information, and optional template summary records in the output data packet.

[0049] SysUpTime: The uptime of the device after it is enabled (in milliseconds).

[0050] UNIX Secs: The time (in seconds) it takes for an output packet to be sent from the exporter.

[0051] Sequence Number: This sequence number increases as the number of packets output by the exporter in a certain observation domain accumulates, and can be used by the collector to determine whether there is any output packet loss.

[0052] Source ID: Indicates the observation domain where the exporter is located (represented by a 32-bit value). The collector can distinguish different output flows of the same exporter based on the source IP address and Source ID field of the data packet.

[0053] In actual applications, NetFlow V9 technology has the following shortcomings:

[0054] 1) NetFlow V9 technology cannot monitor the VPN services of specific customers, which limits its application in specific business scenarios.

[0055] 2) When NetFlow V9 technology is used to monitor network traffic, it requires a large number of monitoring fields, a complex mechanism, and high requirements for device performance. In actual operation, in order to reduce the burden on equipment, this technology will use sampling monitoring to monitor network traffic. Although this sampling monitoring method can reflect the status of network traffic to a certain extent, its sampling results are often not accurate enough, especially when the network traffic is large. If a sampling ratio of 1000:1 or 5000:1 is used for monitoring, the accuracy of traffic monitoring will be greatly reduced.

[0056] 3) When NetFlow V9 technology is used to monitor network traffic, it is necessary to regenerate the corresponding NetFlow V9 table entries, which increases the complexity and maintenance cost of existing network monitoring operations.

[0057] Therefore, the current NetFlow V9 technology has problems such as low monitoring accuracy and high operation and maintenance costs when performing network traffic monitoring.

[0058] With the continuous development of MPLS VPN services, the service requirements of VPN services are getting higher and higher, especially for high-end customers, who need to be provided with VPN service traffic flow analysis services. For the traffic flow monitoring of MPLS VPN services, the current traffic flow monitoring method using NetFlow V9 technology can only monitor physical ports or entire machines. There is a large amount of irrelevant data in the collection process, which has extremely high requirements for equipment and systems. The proportional sampling leads to low accuracy and is difficult to apply in operators. In addition, since the traffic flow cannot be monitored for a single VPN service, it cannot meet the user-level traffic flow monitoring and analysis requirements.

[0059] In order to realize accurate monitoring of traffic flow direction in the service dimension, a VPN service traffic flow direction monitoring solution in an MPLS network is provided in the embodiment of the present disclosure, by newly defining traffic flow direction classification information to mark each traffic flow direction of VPN service flow data, so that each traffic flow direction corresponds to a monitoring queue, and then according to the traffic flow direction classification information of different VPN service flow data, different VPN service flow data are dispatched to the monitoring queue of the corresponding traffic flow direction, and finally the VPN service flow data transmitted in each monitoring queue is counted to obtain the VPN service traffic flow direction monitoring result of the MPLS network. Through the embodiment of the present disclosure, accurate monitoring of each traffic flow direction of service flow data can be realized.

[0060] Figure 1 FIG. 2 shows an exemplary application system architecture diagram to which the method in the embodiment of the present disclosure can be applied. Figure 1 As shown, the system architecture may include a terminal device 101 , a network 102 and a server 103 .

[0061] The network 102 is a medium for providing a communication link between the terminal device 101 and the server 103, and can be a wired network or a wireless network.

[0062] Optionally, the wireless network or wired network described above uses standard communication technology and / or protocol. The network is usually the Internet, but it can also be any network, including but not limited to a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a mobile, wired or wireless network, a dedicated network or any combination of a virtual private network). In some embodiments, the data exchanged through the network is represented by technologies and / or formats including Hyper Text Mark-up Language (HTML), Extensible Markup Language (XML), etc. In addition, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), Internet Protocol Security (IPSec) can also be used to encrypt all or some links. In other embodiments, customized and / or dedicated data communication technologies can also be used to replace or supplement the above data communication technologies.

[0063] The terminal device 101 can be various electronic devices, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, smart speakers, smart watches, wearable devices, augmented reality devices, virtual reality devices, etc.

[0064] Optionally, the client of the application installed in different terminal devices 101 is the same, or the client of the same type of application based on different operating systems. Based on the different terminal platforms, the specific form of the client of the application can also be different, for example, the application client can be a mobile client, a PC client, etc.

[0065] The server 103 may be a server that provides various services, such as a background management server that provides support for the device operated by the user using the terminal device 101. The background management server may analyze and process the received request and other data, and feed back the processing results to the terminal device.

[0066] Optionally, the server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as big data and artificial intelligence platforms.

[0067] Those skilled in the art will know that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration, and any number of terminal devices, networks and servers may be provided according to actual needs, and the embodiments of the present disclosure do not limit this.

[0068] Those skilled in the art will know that Figure 1 The number of terminals, networks, and network-side devices in the example is only illustrative, and any number of terminals, networks, and network-side devices may be provided according to actual needs. The embodiments of the present disclosure are not limited to this.

[0069] Under the above system architecture, an embodiment of the present disclosure provides a method for monitoring the flow direction of VPN service traffic in an MPLS network, which can be executed by any electronic device with computing and processing capabilities.

[0070] In some embodiments, the method for monitoring the flow direction of VPN service traffic in an MPLS network provided in the embodiments of the present disclosure can be executed by a terminal device of the above-mentioned system architecture; in other embodiments, the method for monitoring the flow direction of VPN service traffic in an MPLS network provided in the embodiments of the present disclosure can be executed by a server in the above-mentioned system architecture; in other embodiments, the method for monitoring the flow direction of VPN service traffic in an MPLS network provided in the embodiments of the present disclosure can be implemented by the terminal device and server in the above-mentioned system architecture through interaction.

[0071] Figure 2 A flow chart of a method for monitoring VPN service flow direction in an MPLS network according to an embodiment of the present disclosure is shown. Figure 2 As shown, the method for monitoring the flow direction of VPN service traffic in an MPLS network provided in an embodiment of the present disclosure may include the following steps:

[0072] S202, generating traffic flow direction classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network, wherein the traffic flow direction classification information is used to mark each traffic flow direction of different VPN service flow data, and each traffic flow direction corresponds to a monitoring queue.

[0073] It should be noted that the traffic flow direction classification information in the embodiment of the present disclosure is newly defined information that can be used to mark each traffic flow direction of VPN service flow data in the MPLS network. Different service flow data and different traffic flow directions have different corresponding traffic flow direction classification information. The traffic flow direction classification information defined in the embodiment of the present disclosure refers to information that can distinguish different traffic flows of different services. Different traffic flow direction classification information can be defined for different service flow data.

[0074] In some embodiments, when the service flow data to be monitored is MPLS VPN data (VPN service flow data in an MPLS network); the traffic flow classification information defined in the embodiments of the present disclosure is determined by the LSP label information used to identify the LSP in the MPLS network and the VPN service label information used to identify the VPN service instance in the VPN network. In order to meet the diversified monitoring scenarios of service traffic flow, in a specific implementation, the traffic flow classification information can be defined as a combination of LSP label information and VPN label information, wherein the LSP label information represents the LSP label information used to identify the LSP in the MPLS network, and the VPN label information represents the VPN service label information used to identify the VPN service instance in the VPN network.

[0075] S204, scheduling different VPN service flow data to monitoring queues of corresponding traffic directions according to traffic direction classification information of different VPN service flow data.

[0076] In the disclosed embodiments, VPN service flow data may be, but is not limited to, any of the following: ① service flow data of a single VPN service in a single traffic flow direction; ② service flow data of a single VPN service in multiple traffic flows; ③ service flow data of multiple VPN services in multiple traffic flows. In order to meet the diverse service monitoring scenarios, a corresponding monitoring queue may be created for each traffic flow direction of each service, so that different VPN service flow data may be dispatched to the monitoring queue of the corresponding traffic flow direction according to the traffic flow direction classification information of different VPN service flow data.

[0077] S206, counting the VPN service flow data transmitted in each monitoring queue to obtain the VPN service flow direction monitoring result of the MPLS network.

[0078] It should be noted that after scheduling different VPN business flow data to the monitoring queue of the corresponding traffic direction according to the traffic flow classification information of different VPN business flow data, statistics are taken based on the VPN business flow data transmitted in each monitoring queue to obtain the data situation of any service in any traffic flow direction.

[0079] In some embodiments, the VPN service traffic flow direction monitoring results of the MPLS network in the embodiments of the present disclosure include but are not limited to any one or more of the following: service traffic flow direction byte count statistics results, service traffic flow direction packet count statistics results, and service traffic flow direction flow rate statistics results.

[0080] In some embodiments, Figure 3 As shown, after counting the VPN service flow data transmitted in each monitoring queue to obtain the VPN service flow direction monitoring result of the MPLS network, the VPN service flow direction monitoring method in the MPLS network provided in the embodiment of the present disclosure may also include the following steps:

[0081] S208, obtaining a customized data reporting model, the data reporting model adopts on-demand collection and active push to report data;

[0082] S210, using a data reporting model, encapsulates and reports the monitoring result of the flow direction of VPN service traffic in the MPLS network.

[0083] It should be noted that the data reporting model in the embodiment of the present disclosure is a predefined structured data model for collecting and reporting data, and the data to be reported (VPN service traffic flow monitoring results of the MPLS network) can be encapsulated according to the format of the data reporting model.

[0084] In some embodiments, the VPN service traffic flow direction monitoring method in the MPLS network provided in the embodiments of the present disclosure can use the YANG data model to collect and encapsulate the VPN service traffic flow direction monitoring results of the MPLS network; based on the Telemetry data reporting mechanism, the encapsulated data is reported.

[0085] YANG (Yet Another Next Generation) is a data modeling language. As a machine-oriented model interface, it clearly defines the data structure and its constraints, and can describe data more flexibly and completely. Telemetry, also known as Network Telemetry, is a technology for remotely collecting data from physical or virtual devices at high speed. These physical or virtual devices actively report data to the collector periodically in push mode. Compared with the traditional pull mode data reporting method, this technology can provide more real-time and faster data collection functions. Telemetry only needs to configure a subscription once, and the device can continuously report data, reducing the pressure on the device to process query requests.

[0086] In some embodiments, the LSP label information in the traffic flow classification information is obtained through a label distribution protocol LDP message; and the VPN label information in the traffic flow classification information is obtained through a border gateway protocol BGP message.

[0087] In some embodiments, before generating traffic flow classification information containing LSP label information and VPN label information for different VPN service flow data in the MPLS network, the VPN service traffic flow monitoring method in the MPLS network provided in the embodiments of the present disclosure may also include: if the VPN service routing signaling message changes, updating the VPN label information in the traffic flow classification information; if the MPLS network signaling message changes, updating the LSP label information in the traffic flow classification information.

[0088] In some embodiments, Figure 4 As shown, the VPN service flow direction monitoring method in the MPLS network provided in the embodiment of the present disclosure can generate flow direction classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network through the following steps:

[0089] S402, obtaining VPN service flow monitoring configuration information, wherein the service flow monitoring configuration information is used to configure service information to be monitored and / or traffic flow direction information to be monitored;

[0090] S404, according to the VPN service flow monitoring configuration information, determine the field information of the MPLS network node device label switching path identifier and / or service label identifier monitoring field in the monitoring field, and generate LSP label information and VPN label information for traffic flow classification.

[0091] It should be noted that the method for monitoring the flow direction of VPN services in an MPLS network provided in the embodiments of the present disclosure can monitor a single VPN service in a single flow direction (such as any flow direction of a certain service), can monitor a single VPN service in multiple flow directions (such as all flow directions of a certain service), and can monitor multiple VPN services in multiple flow directions (such as all flow directions of all services). In specific implementation, the service information to be monitored or the flow direction information to be monitored can be configured through the service flow monitoring configuration information.

[0092] It should be noted that after configuring the service information to be monitored and / or the traffic flow direction information to be monitored through the service flow monitoring configuration information, a corresponding monitoring queue can be created according to the service and / or traffic flow direction to be monitored. In some embodiments, in order to achieve flexible monitoring of services and / or traffic flows, a corresponding monitoring queue can be created for each traffic flow direction of each service to be monitored.

[0093] In some embodiments, after determining the field information of the label exchange path identifier and / or the service label identifier monitoring field between the MPLS network node devices in the monitoring field according to the VPN service flow monitoring configuration information, generating the LSP label information and the VPN label information for the flow direction classification, such as Figure 4 As shown, the method for monitoring the flow direction of VPN service traffic in an MPLS network provided in the embodiment of the present disclosure may also include the following steps:

[0094] S406, monitoring whether the service flow monitoring configuration information has changed;

[0095] S408, if the service flow monitoring configuration information is changed, then update the field information of the MPLS network node device label switching path identifier and / or service label identifier monitoring field in the monitoring field according to the changed service flow monitoring configuration information.

[0096] It should be noted that changes in the service flow monitoring configuration information may cause changes in the monitoring fields that need to be monitored. Therefore, by monitoring whether the service flow monitoring configuration information has changed, and when the service flow monitoring configuration information has changed, the field information of the label exchange path identifier and / or service label identifier monitoring field between the MPLS network node devices in the monitoring field is automatically updated according to the changed service flow monitoring configuration information, and LSP label information and VPN label information are generated for traffic flow classification. This allows the VPN service traffic flow direction monitoring method in the MPLS network provided in the embodiment of the present disclosure to quickly adapt to different monitoring needs.

[0097] In some embodiments, after determining the field information of the label exchange path identifier and / or the service label identifier monitoring field between the MPLS network node devices in the monitoring field according to the VPN service flow monitoring configuration information, generating the LSP label information and the VPN label information for the flow direction classification, such as Figure 4 As shown, the method for monitoring the flow direction of VPN service traffic in an MPLS network provided in the embodiment of the present disclosure may also include the following steps:

[0098] S412, monitoring whether the MPLS network signaling message and / or the VPN service routing signaling message changes;

[0099] S414, if the MPLS network signaling message and / or VPN service routing signaling message changes, the field information of the label switching path identifier between MPLS network node devices and / or the service label identifier monitoring field in the monitoring field is updated according to the changed MPLS network signaling message and / or VPN service routing signaling message.

[0100] It should be noted that the network signaling message in the embodiment of the present disclosure may be various signaling messages involved in network transmission data, and changes in the network signaling message may cause changes in the field information of the path identifier between network node devices; the service routing signaling message in the embodiment of the present disclosure may be various signaling messages involved in network transmission service data, and changes in the service reason signaling message may cause the field information of the label switching path identifier and / or service label identifier monitoring field between MPLS network node devices in the service monitoring field to generate LSP label information and VPN label information for traffic flow classification changes. Therefore, the embodiment of the present disclosure monitors whether the MPLS network signaling message and / or VPN service routing signaling message changes, and timely updates the field information of the label switching path identifier and / or service label identifier monitoring field between MPLS network node devices in the monitoring field when the MPLS network signaling message and / or VPN service routing signaling message changes, and can timely update the traffic flow classification information added to the VPN service flow data based on the updated monitoring field information, so as to accurately dispatch different VPN service flow data to the monitoring queue of the corresponding traffic flow direction for statistical analysis based on the updated traffic flow classification information.

[0101] In some embodiments, when the service flow data to be monitored is MPLS VPN data, the LSP label information in the traffic flow classification information is obtained through a label distribution protocol LDP message; the VPN label information in the traffic flow classification information is obtained through a border gateway protocol BGP message.

[0102] Specifically, the method for monitoring the flow direction of VPN service traffic in an MPLS network provided in an embodiment of the present disclosure can obtain LSP label information and VPN label information through the following steps:

[0103] 1) If the VPN service flow data is service flow data of a single VPN service instance in a single traffic flow direction, the loopback address of a single destination device involved in the VPN service instance and the VPN service routing information are obtained in the BGP message through the inbound routing configuration parameters configured for the VPN service instance, as the VPN label information in the traffic flow classification information; the LSP label information of the destination device involved in the VPN service instance is obtained in the LDP message through the loopback address of the single destination device involved in the VPN service instance, as the LSP label information in the traffic flow classification information;

[0104] 2) If the VPN service flow data is service flow data of a single VPN service instance in multiple traffic flow directions, the loopback addresses of multiple destination devices involved in the VPN service instance and the VPN service routing information are obtained in the BGP message through the inbound routing configuration parameters configured for the VPN service instance, as the VPN label information in the traffic flow classification information; the LSP label information of the multiple destination devices involved in the VPN service instance is obtained in the LDP message through the loopback addresses of the multiple destination devices involved in the VPN service instance, as the LSP label information in the traffic flow classification information;

[0105] 3) If the VPN service flow data is service flow data of multiple VPN service instances in multiple traffic flow directions, the Loopback addresses of multiple destination devices involved in each VPN service instance and the VPN service routing information are obtained in the BGP message through the inbound routing configuration parameters configured for each VPN service instance, as the VPN label information in the traffic flow classification information; the LSP label information of the multiple destination devices involved in each VPN service instance is obtained in the LDP message through the Loopback addresses of the multiple destination devices involved in each VPN service instance, as the LSP label information in the traffic flow classification information.

[0106] Furthermore, in some embodiments, the method for monitoring VPN service traffic flow direction in an MPLS network provided in the embodiments of the present disclosure may also include the following steps: if the VPN service routing signaling message changes, the VPN label information in the traffic flow classification information is updated; if the MPLS network signaling message changes, the LSP label information in the traffic flow classification information is updated.

[0107] Below, taking the MPLS three-layer VPN service as an example, the VPN service flow direction monitoring method in the MPLS network provided in the embodiment of the present disclosure is described in detail:

[0108] Table 1

[0109]

[0110]

[0111] As shown in Table 1, for MPLS Layer 3 VPN services, the LSP label representing the LSP label information and the VPN label representing the VPN service instance label information can be combined (the combination method is not specifically limited in the embodiment of the present disclosure) as classification information for distinguishing the flow direction of VPN service traffic, and through the mechanism associated with the MPLS networking protocol and the VPN service protocol processing, the field information of the LSP label and the VPN label is obtained to realize L+V-based traffic classification processing, and the classified service flow data is dispatched to the corresponding monitoring queue for counting statistics and / or flow rate calculation; further, by tracking the dynamic changes of service monitoring configuration information, network networking or service signaling messages, a dynamic update processing mechanism of the flow direction mark field is realized, thereby realizing dynamic adaptation of traffic flow statistics, and finally achieving accurate and dynamic monitoring of traffic flow. Furthermore, by defining the data reporting model and field of traffic statistics, based on the Telemetry reporting mechanism, the VPN service flow direction monitoring results of the MPLS network are updated in real time and reported to the NMS (Network Management System) to realize accurate monitoring of the service flow direction.

[0112] Figure 5 A traffic flow monitoring system for an MPLS layer 3 VPN service in an embodiment of the present disclosure is shown. Figure 5 As shown, the Loopback address of source route A is 100.1.1.100, and the Loopback address of destination route B is 100.1.1.200. In the embodiment of the present disclosure, the traffic flow information of the A-R3-R4-B link is monitored as an example for explanation.

[0113] Source route A, as the origin router, can use the "L+V" two-dimensional field as traffic flow classification information to mark the traffic flow direction of the VPN service from the source device to the destination device. The VPN service traffic flow direction monitoring method in the MPLS network provided in the embodiment of the present disclosure can be processed by the source device based on the VPN service instance. Taking source route A as an example, it has the following label combinations to route B, route C and route D.

[0114] In the embodiment of the present disclosure, the LSP label subscript identifies the label information of the source route to the destination route segment; for example, from route A to route B, it is L AB The VPN label subscript identifies the outgoing traffic of the current route, which is identified by the outgoing traffic route and VPN. For example, the outgoing traffic of A can be represented as V Ax ; Among them, x can take any value according to different VPN service instances.

[0115] Figure 6 A method for monitoring the flow direction of MPLS layer 3 VPN services in an embodiment of the present disclosure is shown. Figure 6 As shown, the method for monitoring VPN service flow direction in an MPLS three-layer VPN MPLS network provided in the embodiment of the present disclosure includes the following steps:

[0116] S602, business flow monitoring information configuration (business, traffic flow direction, time).

[0117] S604, acquiring a monitoring field, and generating traffic flow classification information including LSP label information and VPN label information.

[0118] It should be noted that the LSP label information in the traffic flow classification information is MPLS LSP label information, and the VPN label information in the traffic flow classification information is VPN service label information.

[0119] In specific implementation, in different VPN service flow direction monitoring configuration scenarios, the corresponding service traffic flow direction feature field is obtained, and after the network service routing is stable, the traffic flow direction classification information of the VPN service is generated.

[0120] S606, dispatching different VPN service flow data to corresponding monitoring queues according to flow direction classification information of different VPN service flow data, and obtaining VPN service flow direction monitoring results of the MPLS network by statistics.

[0121] In the specific implementation, based on the traffic flow monitoring classification matching, the service traffic flows of different VPNs are scheduled into queues through the queue scheduling mechanism, and the traffic flow service byte count and data packet quantity statistics are implemented; at the same time, based on the settable time interval, the traffic flow velocity statistics are implemented.

[0122] S608, monitor whether the service flow monitoring configuration information / network signaling message (LDP) / service routing signaling message (BGP) has changed.

[0123] If yes, execute S610; if no, return to execute S604.

[0124] It should be noted that when the VPN service traffic flow direction monitoring configuration changes in the VPN MPLS network, the network status causes LDP changes, and the VPN service changes, it is necessary to re-parse and process LDP and VPN service BGP signaling messages to obtain new VPN service traffic flow direction classification information, that is, L+V information.

[0125] S610: Determine whether to report data.

[0126] If yes, execute S612; if no, return to execute S606.

[0127] S612: Encapsulate the reported data using the YANG data model; and report the data based on the Telemetry data reporting mechanism.

[0128] In the specific implementation, flow direction statistics are collected regularly according to the defined YANG data model, and traffic flow direction data is reported to the management and analysis system regularly based on the Telemetry data reporting mechanism to achieve centralized monitoring and analysis of business traffic flow.

[0129] In some embodiments, the method for obtaining the service flow classification information is as follows: Figure 7 As shown in the figure, VPN service monitors traffic flow and is enabled at the service origin node. It is divided into the following configuration modes:

[0130] 1) Mode 1: Specific VPN service specific direction monitoring. In this mode, for a specific VPN service instance, the traffic flow monitoring in a specific direction is enabled. The destination direction device VPN service routing announcement BGP Loopback address needs to be specified. This mode is suitable for monitoring the special direction of key VPN services.

[0131] 2) Mode 2: Specific VPN service monitoring. This mode is targeted at specific VPN service instances and enables VPN service flow monitoring in all directions. It is suitable for enabling monitoring of key VPN services.

[0132] 3) Mode 3: Global VPN service monitoring. In this mode, all VPN service flow monitoring is enabled, that is, flow monitoring is implemented in all directions of all VPN instances on the VPN service router.

[0133] It should be noted that the granularity of Mode 1, Mode 2, and Mode 3 increases from small to large, and the complete set of combinations of the former mode is composed of the latter mode.

[0134] In mode 1, after VPN service flow monitoring is enabled, the BGP loopback address is advertised through the configured VPN service route, and the L label information is obtained in the LDP processing process; at the same time, the source router uses the route parameter import route-target (RT) configured in the VPN service VRF instance to match the VPN service route label information V of the destination loopback address and RT in the BGP processing process;

[0135] In the working condition of mode 2, after VPN service flow monitoring is enabled, the source router obtains the next-hop IP address of the VPN service instance route, i.e. the destination device Loopback address and the VPN service route label information V corresponding to RT, for the configured specific VPN service VRF instance based on the configured routing parameter import route-target (RT) through the BGP processing process result; on this basis, the source router obtains the destination device Loopback addresses involved in the VPN instance and obtains the destination device L label information of the VPN instance based on the LDP processing process;

[0136] In the working condition of mode 3, after VPN service flow monitoring is enabled, the source router obtains the next-hop IP address of each VPN service instance route, that is, the destination device Loopback address and the VPN instance service route label information V corresponding to RT, for all VPN service VRF instances based on the configured routing parameter import route-target (RT) through the BGP processing process result; on this basis, by obtaining the destination device Loopback address of all VPN instances, the L label information is obtained based on the LDP processing process.

[0137] Through the above processing mechanism, the L+V classification mark of the VPN service traffic flow direction can be obtained. In order to implement VPN service monitoring and traffic flow direction monitoring and management, it is necessary to match and record the corresponding configured VPN instance name, configured route-distinguisher (RD) mark information, VPN service source / destination Loopback address information, and associate them with the internal queue number of the device.

[0138] In some embodiments, the process of scheduling different VPN service flow data to corresponding traffic flow monitoring queues based on traffic flow classification information is as follows: Figure 8 As shown in the figure, after obtaining the classification tags L and V for traffic flow direction monitoring, a VPN instance has one L and multiple V values ​​for a single flow direction. The production process of introducing traffic into the queue can be implemented using the following pseudo code:

[0139] if L match J and V match-any(K1,K2,...,Km)

[0140] then forwarding the packet through queue <n>.

[0141] Taking the monitoring of traffic flow of A-R3-R4-B as an example, the VPN from source node A to destination node B <x>The flow direction can be identified by L AB +V XB The two-dimensional field is used to classify the flow direction of VPN service traffic. Each flow direction of the VPN service instance enters the same queue, and traffic statistics are processed in the queue as follows:

[0142] 1) The queue counts the number of forwarded packets. The statistical values ​​include the total number of packets and the number of forwarded bytes, using a 64-bit counter.

[0143] 2) According to a certain time interval, the number of data packets and forwarded bytes in the queue is obtained regularly, and the difference in the time interval range is calculated to obtain the flow rate of the calculated data packets and forwarded bytes / bits. The monitoring action can define the time interval and set the unit in minutes, which can be configured according to operational needs.

[0144] The dynamic processing of traffic flow direction monitoring includes the following two aspects:

[0145] 1) Business flow monitoring configuration change processing process:

[0146] ① New service flow monitoring configuration processing: At this time, there is no VPN service flow monitoring queue in the MPLS network. The L+V label is obtained according to three modes, a matching rule is formed, and the traffic is imported into the queue for quantity statistics;

[0147] ②Business flow monitoring configuration change processing process:

[0148] In the case of a change in the monitoring configuration of mode 1, if the original configuration monitoring direction no longer needs to be monitored, the corresponding L+V matching rule is deleted and the corresponding monitoring queue is released; the corresponding L+V label is obtained for the monitoring configuration of the newly added direction, a matching rule is formed, and traffic is imported into the queue for quantity statistics. When mode 1 is closed, the L+V matching rule under the VPN instance is deleted, and the monitoring and statistics queue is determined.

[0149] When the monitoring configuration of mode 2 changes, if the original configured VPN instance no longer needs to be monitored, all L+V matching rules under the VPN instance are deleted and the corresponding monitoring queue is released. At the same time, the corresponding L+V label is obtained for the newly added VPN instance, a matching rule is formed, and traffic is imported into the queue for quantity statistics.

[0150] In the case where the monitoring configuration of mode 3 is changed, when mode 3 is enabled, if the monitoring configuration of mode 1 and mode 2 exists, these monitoring modes remain unchanged, and the newly added L+V labels for monitoring the flow direction of all other VPN instances are obtained to form matching rules, and the traffic is imported into the queue for quantity statistics; when mode 3 is disabled, if the monitoring configuration of mode 1 and mode 2 exists, the monitoring queue is retained, the monitoring L+V matching rules of other VPN instances are deleted, and the corresponding monitoring queues are released.

[0151] 2) Network and service signaling change processing:

[0152] ① Network signaling changes: Link status changes or changes in various protocol processes during network operation cause IGP routing recalculation, which leads to LDP redistribution of labels in the MPLS network, resulting in changes in the LSP of the MPLS label switching path, that is, the L label of the corresponding target Loopback address changes. Therefore, it is necessary to monitor the advertisement message in the LDP session. When the FEC / LABEL mapping relationship of the destination Loopback address changes, the L label of the flow monitoring mark of the corresponding Loopback needs to be updated again.

[0153] ②Business routing signaling changes, the following two types of changes may occur and are handled separately:

[0154] Category 1: The loopback address corresponding to the update source of the VPN service route BGP announcement changes. At this time, it is necessary to replace the L label of the original monitoring queue with the L label corresponding to the new loopback address, and update the address information of the destination-loopback field in the data reporting model.

[0155] Category 2: Changes in the routing and configuration parameters of the VPN service instance, changes in the device BGP routing process, etc. will cause changes in the VPN instance V label. It is necessary to monitor the update message in the BGP session (usually the session between the service route and the RR), adapt to the signaling changes in real time, and obtain the latest VPN instance V label in the update / withdrawal new information. Based on this, update the V label matching the monitoring queue traffic.

[0156] In the disclosed embodiment, for the bundled monitoring of the Loopback address information of the source route and the destination route, when the LDP in the L label information occurs (label information update) or the V label changes (the RT and RD paths of the VPN in BGP change), a time notification message will be generated, and VA1 will change, assuming it is VA2. The present invention can realize dynamic tracking and real-time adaptation of signaling changes; the purpose of dynamic monitoring of traffic flow can be achieved based on the update, withdrawal, delete, increase and other operations. An example of a configuration model for an accurate monitoring method of the flow direction of MPLS three-layer VPN traffic is as follows:

[0157] The corresponding configuration parameter information is shown in Table 2.

[0158] Table 2

[0159]

[0160]

[0161] For example, for VPN instance vpn1 under the A-R3-R4-B path, the total bytes of traffic flow size of this VPN instance are total-byte, the total number of packets is total-packet, and the traffic rate within a certain time interval is interval-byte-rateBPS (bytes / second) and interval-pkt-rate PPS (packets / second).

[0162] Based on the same inventive concept, the embodiment of the present disclosure also provides a device for monitoring the flow direction of VPN service traffic in an MPLS network, as described in the following embodiment. Since the principle of solving the problem in the device embodiment is similar to that in the above method embodiment, the implementation of the device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0163] Fig. 9 A schematic diagram of a VPN service flow direction monitoring device in an MPLS network according to an embodiment of the present disclosure is shown. Fig. 9 As shown, the device includes: a VPN service flow data monitoring module 901, a VPN service flow data scheduling module 902 and a VPN service flow data statistics module 903.

[0164] Among them, the VPN business flow data monitoring module 901 is used to generate traffic flow direction classification information including LSP label information and VPN label information for different VPN business flow data in the MPLS network, wherein the traffic flow direction classification information is used to mark each traffic flow direction of different VPN business flow data, and each traffic flow direction corresponds to a monitoring queue; the VPN business flow data scheduling module 902 is used to schedule different VPN business flow data to the monitoring queue of the corresponding traffic direction according to the traffic flow direction classification information of different VPN business flow data; the VPN business flow data statistics module 903 is used to count the VPN business flow data transmitted in each monitoring queue to obtain the VPN business traffic flow direction monitoring result of the MPLS network.

[0165] It should be noted that, in the disclosed embodiment, the traffic flow classification information generated for different VPN service flow data in the MPLS network includes: LSP label information and VPN label information, the LSP label information is the LSP label information used to identify the label switching path LSP in the MPLS network, and the VPN label information is the VPN service label information used to identify the VPN service instance in the VPN network. Among them, the LSP label information in the traffic flow classification information is obtained through the label distribution protocol LDP message; the VPN label information in the traffic flow classification information is obtained through the border gateway protocol BGP message.

[0166] In some embodiments, the above-mentioned VPN service flow data may include but is not limited to at least one of the following: service flow data of a single VPN service in a single traffic flow direction; service flow data of a single VPN service in multiple traffic flows; service flow data of multiple VPN services in multiple traffic flows.

[0167] In some embodiments, the VPN service traffic flow direction monitoring results of the above MPLS network may include but are not limited to at least one of the following: service traffic flow direction byte count statistics, service traffic flow direction packet count statistics, and service traffic flow direction flow rate statistics.

[0168] In one embodiment, the VPN service flow direction monitoring device in the MPLS network provided in the embodiment of the present disclosure may also include: a service flow monitoring configuration module 904, which is used to obtain VPN service flow monitoring configuration information, wherein the service flow monitoring configuration information is used to configure the service information to be monitored and / or the traffic flow direction information to be monitored; a monitoring field determination module 905, which is used to determine the field information of the label switching path identifier and / or the service label identifier monitoring field between the MPLS network node devices in the monitoring field according to the VPN service flow monitoring configuration information, and generate LSP label information and VPN label information for traffic flow direction classification. In this embodiment, the above-mentioned VPN service flow data monitoring module 901 is also used to: generate LSP label information and VPN label information for traffic flow direction classification according to the field information of the label switching path identifier and / or the service label identifier monitoring field between the MPLS network node devices in the monitoring field.

[0169] In some embodiments, the VPN service traffic flow direction monitoring device in the MPLS network provided in the embodiments of the present disclosure may also include: a first monitoring field update module 906, which is used to monitor whether the service flow monitoring configuration information has changed; if the service flow monitoring configuration information has changed, then according to the changed service flow monitoring configuration information, the field information of the label exchange path identifier and / or the service label identifier monitoring field between the MPLS network node devices in the monitoring field is updated.

[0170] In some embodiments, the VPN service traffic flow direction monitoring device in the MPLS network provided in the embodiments of the present disclosure may also include: a second monitoring field update module 907, which is used to monitor whether the MPLS network signaling message and / or the VPN service routing signaling message changes; if the MPLS network signaling message and / or the VPN service routing signaling message changes, then according to the changed MPLS network signaling message and / or the VPN service routing signaling message, the field information of the label exchange path identifier and / or the service label identifier monitoring field between the MPLS network node devices in the monitoring field is updated.

[0171] In some embodiments, the VPN service traffic flow direction monitoring device in the MPLS network provided in the embodiments of the present disclosure may also include: a data reporting module 908, which is used to: obtain a customized data reporting model, the data reporting model uses on-demand collection and active push to report data; use the data reporting model to encapsulate and report the VPN service traffic flow direction monitoring results of the MPLS network.

[0172] In some embodiments, the data reporting module 908 is further used to: collect and encapsulate the VPN service traffic flow monitoring results of the MPLS network using the YANG data model; and report the encapsulated data based on the Telemetry data reporting mechanism.

[0173] In some embodiments, the VPN service flow data monitoring module 901 is further used for: if the VPN service flow data is the service flow data of a single VPN service instance in a single traffic flow direction, then the inbound routing configuration parameters configured for the VPN service instance are used to obtain the Loopback address of a single destination device involved in the VPN service instance and the VPN service routing information in the BGP message as the VPN label information in the traffic flow classification information; through the Loopback address of a single destination device involved in the VPN service instance, the LSP label information of the destination device is obtained in the LDP message as the LSP label information in the traffic flow classification information; if the VPN service flow data is the service flow data of a single VPN service instance in multiple traffic flow directions, then the Loopback addresses and VPNs of multiple destination devices involved in the VPN service instance are obtained in the BGP message through the inbound routing configuration parameters configured for the VPN service instance. The service routing information is used as the VPN label information in the traffic flow classification information; the LSP label information of the multiple destination devices involved in the VPN service instance is obtained in the LDP message through the Loopback addresses of the multiple destination devices involved in the VPN service instance, as the LSP label information in the traffic flow classification information; if the VPN service flow data is the service flow data of multiple VPN service instances in multiple traffic flow directions, the Loopback addresses of the multiple destination devices involved in each VPN service instance and the VPN service routing information are obtained in the BGP message through the inbound routing configuration parameters configured for each VPN service instance, as the VPN label information in the traffic flow classification information; the LSP label information of the multiple destination devices involved in each VPN service instance is obtained in the LDP message through the Loopback addresses of the multiple destination devices involved in each VPN service instance, as the LSP label information in the traffic flow classification information.

[0174] In some embodiments, the VPN service flow data monitoring module 901 is also used to: update the VPN label information in the traffic flow classification information if the VPN service routing signaling message changes; and update the LSP label information in the traffic flow classification information if the MPLS network signaling message changes.

[0175] It should be noted that the examples and application scenarios implemented by the modules in the above-mentioned device embodiment are the same as those of the corresponding steps in the method embodiment, but are not limited to the contents disclosed in the above-mentioned method embodiment. It should be noted that the above-mentioned modules as part of the device can be executed in a computer system such as a set of computer executable instructions.

[0176] Based on the same inventive concept, the embodiments of the present disclosure also provide a system for monitoring the flow direction of VPN service traffic in an MPLS network, as described in the following embodiments. Since the principle of solving the problem in the system embodiment is similar to that in the above method embodiment, the implementation of the system embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0177] Fig.10 A schematic diagram of a VPN service flow direction monitoring system in an MPLS network according to an embodiment of the present disclosure is shown. Fig.10 As shown, the system includes: a source router 10 , a destination router 20 and a monitoring controller 30 .

[0178] Among them, the source router 10 is used to generate traffic flow classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network after receiving the VPN service flow data, and dispatch different VPN service flow data to the monitoring queue of the corresponding traffic flow direction according to the traffic flow classification information of different VPN service flow data, wherein the traffic flow classification information is used to mark each traffic flow direction of different VPN service flow data from the source router 10 to the destination router 20, and each traffic flow direction corresponds to a monitoring queue; the monitoring controller 30 is used to count the VPN service flow data transmitted in each monitoring queue to obtain the VPN service traffic flow direction monitoring result of the MPLS network.

[0179] It should be noted that, in the disclosed embodiment, the traffic flow classification information generated for different VPN service flow data in the MPLS network includes: LSP label information and VPN label information, the LSP label information is the LSP label information used to identify the label switching path LSP in the MPLS network, and the VPN label information is the VPN service label information used to identify the VPN service instance in the VPN network. Among them, the LSP label information in the traffic flow classification information is obtained through the label distribution protocol LDP message; the VPN label information in the traffic flow classification information is obtained through the border gateway protocol BGP message.

[0180] In some embodiments, the VPN service traffic flow direction monitoring system in the MPLS network provided in the embodiments of the present disclosure may also include: a user terminal device 40, which communicates with the monitoring controller 30, and is used to receive the VPN service traffic flow direction monitoring results of the MPLS network reported by the monitoring controller 30; wherein the monitoring controller 30 is also used to use a customized data reporting model to encapsulate and report the VPN service traffic flow direction monitoring results of the MPLS network.

[0181] In some embodiments, the above-mentioned source router 10 is also used to: obtain VPN service flow monitoring configuration information, wherein the service flow monitoring configuration information is used to configure the service information to be monitored and / or the traffic flow direction information to be monitored; determine the field information of the label switching path identifier and / or the service label identifier monitoring field between the MPLS network node devices in the monitoring field according to the VPN service flow monitoring configuration information, and generate LSP label information and VPN label information for traffic flow direction classification, wherein the service label identifier monitoring field is used to monitor the path identifier and network node device; generate LSP label information and VPN label information for traffic flow direction classification according to the field information of the label switching path identifier and / or the service label identifier monitoring field between the MPLS network node devices in the monitoring field, and generate traffic flow direction classification information containing LSP label information and VPN label information.

[0182] In some embodiments, the monitoring controller 30 is also used to monitor whether the service flow monitoring configuration information has changed; if the service flow monitoring configuration information has changed, the source router 10 is also used to update the field information of the label exchange path identifier and / or service label identifier monitoring field between the MPLS network node devices in the monitoring field according to the changed service flow monitoring configuration information, and generate LSP label information and VPN label information for traffic flow classification.

[0183] In some embodiments, the monitoring controller 30 is also used to monitor whether the MPLS network signaling message and / or the VPN service routing signaling message changes; if the MPLS network signaling message and / or the VPN service routing signaling message changes, the source router 10 is also used to update the field information of the label exchange path identifier and / or the service label identifier monitoring field between the MPLS network node devices in the monitoring field according to the changed MPLS network signaling message and / or the VPN service routing signaling message, and generate LSP label information and VPN label information for traffic flow classification.

[0184] In some embodiments, the VPN service traffic flow monitoring results of the MPLS network obtained by monitoring the controller 30 may include but are not limited to at least one of the following: service traffic flow byte statistics, service traffic flow data packet statistics, and service traffic flow velocity statistics.

[0185] In some embodiments, the monitoring controller 30 is further used to: collect and encapsulate the VPN service traffic flow monitoring results of the MPLS network using the YANG data model; and report the encapsulated data based on the Telemetry data reporting mechanism.

[0186] In some embodiments, the VPN service traffic flow direction monitoring system in the MPLS network provided in the embodiments of the present disclosure can be used for but is not limited to monitoring the following service flow data: service flow data of a single VPN service in a single traffic flow direction; service flow data of a single VPN service in multiple traffic flows; service flow data of multiple VPN services in multiple traffic directions.

[0187] Based on the above embodiments, in some embodiments, the above source router 10 is further used for: if the VPN service flow data is the service flow data of a single VPN service instance in a single traffic flow direction, then the inbound routing configuration parameters configured by the VPN service instance are used to obtain the Loopback address of a single destination device involved in the VPN service instance and the VPN service routing information in the BGP message as the VPN label information in the traffic flow classification information; through the Loopback address of a single destination device involved in the VPN service instance, the LSP label information of the destination device is obtained in the LDP message as the LSP label information in the traffic flow classification information; if the VPN service flow data is the service flow data of a single VPN service instance in multiple traffic flow directions, then the Loopback addresses and VPNs of multiple destination devices involved in the VPN service instance are obtained in the BGP message through the inbound routing configuration parameters configured by the VPN service instance. The service routing information is used as the VPN label information in the traffic flow classification information; the LSP label information of the multiple destination devices involved in the VPN service instance is obtained in the LDP message through the Loopback addresses of the multiple destination devices involved in the VPN service instance, as the LSP label information in the traffic flow classification information; if the VPN service flow data is the service flow data of multiple VPN service instances in multiple traffic flow directions, the Loopback addresses of the multiple destination devices involved in each VPN service instance and the VPN service routing information are obtained in the BGP message through the inbound routing configuration parameters configured for each VPN service instance, as the VPN label information in the traffic flow classification information; the LSP label information of the multiple destination devices involved in each VPN service instance is obtained in the LDP message through the Loopback addresses of the multiple destination devices involved in each VPN service instance, as the LSP label information in the traffic flow classification information.

[0188] In some embodiments, the source router 10 is further configured to: update the VPN label information in the traffic flow classification information if the VPN service routing signaling message changes; and update the LSP label information in the traffic flow classification information if the MPLS network signaling message changes.

[0189] In summary, the VPN service traffic flow direction monitoring solution in the MPLS network provided in the embodiments of the present disclosure can achieve but is not limited to the following technical effects: ① By newly defining the path identifier (L+V) between network node devices, the traffic direction of VPN service flow data can be marked to achieve accurate monitoring of the service traffic direction; ② The destination routing of multiple links can be unified, and the accurate information of VPN traffic flow direction of different links can be monitored, which gets rid of the current port monitoring of multiple path identifiers between network node devices and complex mechanisms; ③ The traffic flow direction information of the existing network links can be updated in real time to achieve remote traffic flow monitoring, providing VPN service customers with more intuitive traffic information; ④ In terms of network supervision, network management personnel can know the source and destination of the packet, the type of network service and the cause of network congestion.

[0190] The VPN service traffic flow direction monitoring solution in the MPLS network provided in the embodiments of the present disclosure can be applied to but not limited to the precise monitoring of the VPN service traffic flow direction of government, enterprise or cloud private networks, and can provide value-added services for user service monitoring, which is beneficial to user network optimization and adjustment and improves the user service quality experience; it can also be applied to the VPN service traffic flow direction monitoring in self-operated key MPLS networks, and can monitor the traffic size and trend of key bureaus, implement effective network bandwidth planning, and meet the needs of business development; currently, the MPLS VPN business is developing rapidly, and the VPN service traffic flow direction monitoring method in the MPLS network provided in the embodiments of the present disclosure can be applied to the precise monitoring of the MPLS VPN service traffic flow direction, and has broad application prospects.

[0191] Those skilled in the art will appreciate that various aspects of the present disclosure may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or an implementation that combines hardware and software aspects, which may be collectively referred to herein as a "circuit", "module" or "system".

[0192] Based on the same inventive concept, an electronic device is also provided in an embodiment of the present disclosure, the electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the above methods for monitoring the flow direction of VPN service traffic in an MPLS network by executing the executable instructions. Since the principle of solving the problem in the electronic device embodiment is similar to that in the above method embodiment, the implementation of the electronic device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0193] Refer to the following Fig.11 1100 according to this embodiment of the present disclosure is described. Fig.11 The electronic device 1100 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0194] like Fig.11 As shown, the electronic device 1100 is in the form of a general computing device. The components of the electronic device 1100 may include but are not limited to: at least one processing unit 1110, at least one storage unit 1120, and a bus 1130 connecting different system components (including the storage unit 1120 and the processing unit 1110).

[0195] The storage unit stores a program code, and the program code can be executed by the processing unit 1110, so that the processing unit 1110 executes the steps described in the "Exemplary Method" section of the specification according to various exemplary embodiments of the present disclosure. For example, the processing unit 1110 can execute the following steps of the above method embodiment: generating traffic flow direction classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network, wherein the traffic flow direction classification information is used to mark each traffic flow direction of different VPN service flow data, and each traffic flow direction corresponds to a monitoring queue; according to the traffic flow direction classification information of different VPN service flow data, different VPN service flow data are dispatched to the monitoring queue of the corresponding traffic flow direction; and the VPN service flow data transmitted in each monitoring queue are counted to obtain the VPN service flow direction monitoring result of the MPLS network.

[0196] The storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 11201 and / or a cache storage unit 11202 , and may further include a read-only storage unit (ROM) 11203 .

[0197] The storage unit 1120 may also include a program / utility 11204 having a set (at least one) of program modules 11205, such program modules 11205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0198] Bus 1130 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0199] The electronic device 1100 may also communicate with one or more external devices 1140 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 1100, and / or communicate with any device that enables the electronic device 1100 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 1150. Furthermore, the electronic device 1100 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 1160. As shown, the network adapter 1160 communicates with other modules of the electronic device 1100 via a bus 1130. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1100, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0200] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0201] Based on the same inventive concept, a computer-readable storage medium is also provided in the embodiment of the present disclosure, on which a computer program is stored, and when the computer program is executed by a processor, any of the above methods for monitoring the flow direction of VPN service traffic in an MPLS network is implemented. Since the principle of solving the problem in the embodiment of the computer-readable storage medium is similar to that in the above method embodiment, the implementation of the embodiment of the computer-readable storage medium can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0202] More specific examples of computer-readable storage media in the present disclosure may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0203] In the present disclosure, a computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, wherein a readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A readable signal medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0204] Alternatively, the program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0205] In specific implementations, program codes for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages, such as Java, C++, etc., and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device, partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0206] Based on the same inventive concept, a computer program product is also provided in the embodiments of the present disclosure, including a computer program product, including: a computer program or an instruction, wherein when the computer program or the instruction is executed by a processor, the method for monitoring the flow direction of VPN service traffic in an MPLS network of any one of the above method embodiments is implemented. Since the principle of solving the problem in the computer program product embodiment is similar to that in the above method embodiment, the implementation of the computer program product embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0207] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0208] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0209] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0210] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.< / x> < / n>

Claims

1. A method for monitoring the flow direction of virtual private network (VPN) service traffic in a multi-protocol label switching (MPLS) network, characterized in that: include: Generate traffic flow direction classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network, wherein the traffic flow direction classification information is used to mark each traffic flow direction of different VPN service flow data, and each traffic flow direction corresponds to a monitoring queue; According to the flow direction classification information of different VPN service flow data, different VPN service flow data are dispatched to the monitoring queue of the corresponding flow direction; Count the VPN service flow data transmitted in each monitoring queue to obtain the VPN service flow direction monitoring results of the MPLS network; The LSP label information is LSP label information used to identify the label switching path LSP in the MPLS network obtained through the label distribution protocol LDP message; the VPN label information is VPN service label information used to identify the VPN service instance in the VPN network obtained through the border gateway protocol BGP message.

2. The method for monitoring VPN service flow direction in an MPLS network according to claim 1, characterized in that: Generate traffic flow classification information containing LSP label information and VPN label information for different VPN service flow data in the MPLS network, including: Acquire VPN service flow monitoring configuration information, wherein the VPN service flow monitoring configuration information is used to configure VPN service information to be monitored and / or traffic flow direction information to be monitored; According to the service flow monitoring configuration information, the field information of the label exchange path identifier and / or service label identifier monitoring field between MPLS network node devices in the monitoring field is determined, and LSP label information and VPN label information are generated for traffic flow classification.

3. The method for monitoring VPN service flow direction in an MPLS network according to claim 2, characterized in that: After determining the field information of the MPLS network node device-to-device label switching path identifier and / or the VPN service label identifier monitoring field in the monitoring field according to the service flow monitoring configuration information, the method further includes: Monitoring whether the VPN service flow monitoring configuration information has changed; If the VPN service flow monitoring configuration information is changed, the field information of the MPLS network node device-to-device label switching path identifier and / or the VPN service label identifier monitoring field in the monitoring field is updated according to the changed service flow monitoring configuration information.

4. The method for monitoring VPN service flow direction in an MPLS network according to claim 2, characterized in that: After determining the field information of the network node device label exchange path identifier and / or the service label identifier monitoring field in the monitoring field according to the service flow monitoring configuration information, the method further includes: Monitor whether MPLS network signaling messages and / or VPN service routing signaling messages have changed; If the MPLS network signaling message and / or VPN service routing signaling message changes, the field information of the MPLS network node device path identifier and / or VPN service identifier monitoring field in the monitoring field is updated according to the changed MPLS network signaling message and / or VPN service routing signaling message.

5. The method for monitoring VPN service flow direction in an MPLS network according to claim 1, characterized in that: The VPN service traffic flow direction monitoring result of the MPLS network includes at least one of the following: VPN service traffic flow direction byte count statistics result, VPN service traffic flow direction data packet count statistics result, VPN service traffic flow direction flow velocity statistics result.

6. The method for monitoring VPN service flow direction in an MPLS network according to claim 1, characterized in that: After counting the VPN service flow data transmitted in each monitoring queue to obtain the VPN service flow direction monitoring result of the MPLS network, the method further includes: Obtain a custom data reporting model, wherein the data reporting model reports data in an on-demand collection and active push manner; The data reporting model is used to encapsulate and report the VPN service traffic flow direction monitoring result of the MPLS network.

7. The method for monitoring VPN service flow direction in an MPLS network according to claim 6, characterized in that: Using the data reporting model, encapsulating and reporting the VPN service traffic flow direction monitoring result of the MPLS network, including: Use the YANG data model to encapsulate the VPN service traffic flow monitoring results collected on the MPLS network; Based on the Telemetry data reporting mechanism, the encapsulated data is reported.

8. The method for monitoring VPN service flow direction in an MPLS network according to claim 1, characterized in that: The VPN service flow data includes at least one of the following: Service flow data of a single VPN service in a single traffic direction; Service flow data of a single VPN service in multiple traffic directions; Service flow data of multiple VPN services in multiple traffic directions.

9. The method for monitoring VPN service flow direction in an MPLS network according to claim 1, characterized in that: Before generating traffic flow classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network, the method further includes: If the VPN service flow data is service flow data of a single VPN service instance in a single traffic flow direction, the loopback address of a single destination device involved in the VPN service instance and the VPN service routing information are obtained in the BGP message through the inbound routing configuration parameters configured for the VPN service instance, as the VPN label information in the traffic flow direction classification information; the LSP label information of the destination device involved in the VPN service instance is obtained in the LDP message through the loopback address of the single destination device involved in the VPN service instance, as the LSP label information in the traffic flow direction classification information; If the VPN service flow data is service flow data of a single VPN service instance in multiple traffic flow directions, the Loopback addresses of multiple destination devices involved in the VPN service instance and the VPN service routing information are obtained in the BGP message through the inbound routing configuration parameters configured for the VPN service instance, as the VPN label information in the traffic flow direction classification information; the LSP label information of multiple destination devices involved in the VPN service instance is obtained in the LDP message through the Loopback addresses of the multiple destination devices involved in the VPN service instance, as the LSP label information in the traffic flow direction classification information; If the VPN service flow data is service flow data of multiple VPN service instances in multiple traffic flow directions, the Loopback addresses of multiple destination devices involved in each VPN service instance and the VPN service routing information are obtained in the BGP message through the inbound routing configuration parameters configured for each VPN service instance, as the VPN label information in the traffic flow direction classification information; the LSP label information of the multiple destination devices involved in each VPN service instance is obtained in the LDP message through the Loopback addresses of the multiple destination devices involved in each VPN service instance, as the LSP label information in the traffic flow direction classification information.

10. The method for monitoring VPN service flow direction in an MPLS network according to claim 1, characterized in that: Before generating traffic flow classification information including LSP label information and VPN label information for different VPN service flow data in the MPLS network, the method further includes: If the VPN service routing signaling message changes, the VPN label information in the traffic flow classification information is updated; If the MPLS network signaling message changes, the LSP label information in the traffic flow classification information is updated.

11. A device for monitoring VPN service flow direction in an MPLS network, characterized in that: include: A VPNVPN business flow data monitoring module is used to generate traffic flow direction classification information including LSP label information and VPN label information for different VPN business flow data in the MPLS network, wherein the traffic flow direction classification information is used to mark each traffic flow direction of different VPN business flow data, and each traffic flow direction corresponds to a monitoring queue; VPNVPN business flow data scheduling module, used for scheduling different VPN business flow data to the monitoring queue of the corresponding flow direction according to the flow direction classification information of different VPN business flow data; VPNVPN business flow data statistics module is used to count the VPN business flow data transmitted in each monitoring queue to obtain the VPN business flow direction monitoring result of the MPLS network; The LSP label information is LSP label information used to identify the label switching path LSP in the MPLS network obtained through the label distribution protocol LDP message; the VPN label information is VPN service label information used to identify the VPN service instance in the VPN network obtained through the border gateway protocol BGP message.

12. A VPN service flow direction monitoring system in an MPLS network, characterized in that: include: Source router, destination router and monitoring controller; The source router is used to generate traffic flow classification information including LSP label information and VPN label information for different VPN traffic flow data in the MPLS network after receiving the VPN traffic flow data in the MPLS network, and dispatch different VPN traffic flow data to the monitoring queue of the corresponding traffic flow direction according to the traffic flow classification information of different VPN traffic flow data, wherein the traffic flow classification information is used to mark each traffic flow direction of different VPN traffic flow data, and each traffic flow direction corresponds to a monitoring queue; The monitoring controller is used to count the VPN service flow data transmitted in each monitoring queue to obtain the VPN service flow direction monitoring result of the MPLS network; The LSP label information is LSP label information used to identify the label switching path LSP in the MPLS network obtained through the label distribution protocol LDP message; the VPN label information is VPN service label information used to identify the VPN service instance in the VPN network obtained through the border gateway protocol BGP message.

13. The VPN service flow direction monitoring system in the MPLS network according to claim 12, characterized in that: The system further comprises: A user terminal device, communicating with the monitoring controller, for receiving a VPN service flow direction monitoring result of the MPLS network reported by the monitoring controller; The monitoring controller is further used to encapsulate and report the VPN service traffic flow direction monitoring result of the MPLS network using a custom data reporting model.

14. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the method for monitoring VPN service traffic flow direction in an MPLS network as described in any one of claims 1 to 10 by executing the executable instructions.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for monitoring the flow direction of VPN service traffic in an MPLS network according to any one of claims 1 to 10 is implemented.

16. A computer program product comprising: A computer program or instruction, characterized in that when the computer program or instruction is executed by a processor, it implements the method for monitoring the flow direction of VPN service traffic in an MPLS network as described in any one of claims 1 to 10.

Images