A method and application of measuring xFlow indicators based on FMP protocol
Through the client-server communication mode and TCP connection of the FMP protocol, the problem of inaccurate xFlow traffic monitoring is solved, the standardized export of traffic indicators and troubleshooting is realized, and the operation and maintenance efficiency and the integrity of statistical information are improved.
Patent Information
- Application Number
- CN202211482576.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-11-24
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2042-11-24
AI Technical Summary
In the xFlow-based traffic monitoring scenario, the lack of standardized protocols leads to inaccurate traffic calculations and makes it difficult to troubleshoot problems, especially in the multi-network device scenarios, and existing devices cannot effectively export packets for monitoring.
Adopt the client-server communication mode based on the FMP protocol, and define four logical roles: control the client, session sending, server and session reflection, and realize the establishment, start and stop of traffic measurement sessions through TCP connection to ensure the completeness of statistical information. Sex and accuracy.
It has realized the standardized export of various traffic monitoring indicators, improved interoperability and operation and maintenance efficiency of multiple manufacturers, simplified large-scale traffic statistics and troubleshooting, and ensured the integrity of statistical information.
Smart Images

Figure CN115834719B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of measuring xFlow (network flow protocol, such as NetFlow and NetStream, etc.) indicators, and in particular to an FMP (Flow Measure Protocol) protocol and application thereof for measuring xFlow indicators. Background Art
[0002] In the scenario of xFlow-based traffic monitoring, there is a lack of a standardized protocol for measuring various traffic monitoring protocols.
[0003] Generally, when xFlow traffic calculation is inaccurate or does not come out, it may be necessary to check whether there are configuration errors, omissions, and regulatory issues in each network element device. Existing network element devices that process xFlow do not have standard export of various operating configurations. When xFlow traffic calculation is inaccurate, it is impossible to timely and effectively troubleshoot the fault point. Especially when there are many xFlow network element devices, troubleshooting is more time-consuming.
[0004] Existing network element devices that process xFlow have no standard for exporting xFlow messages for effective monitoring, and inaccurate flow calculations caused by packet loss or delays are difficult to troubleshoot. Summary of the invention
[0005] In order to solve the above-mentioned problems existing in the prior art, the present invention provides a method and application for measuring xFlow indicators based on the FMP protocol, which standardizes the export of various monitoring indicator information of each network element device that processes xFlow when processing xFlow messages, can realize intercommunication among multiple manufacturers, and greatly improve the operation and maintenance efficiency in large-scale deployment scenarios.
[0006] To achieve the above object, the present invention adopts the following technical solutions:
[0007] In one embodiment of the present invention, a method for measuring xFlow indicators based on the FMP protocol is proposed. The FMP protocol adopts a client-server communication mode and defines four logical roles, namely, the control client, session sending, server and session reflection. The control client / server is responsible for negotiating the establishment and startup of the FMP session. Once the session is started, the control client and server respectively notify the session sending and session reflection modules of the relevant session information, so that they have the ability to send and respond to probe frames for this session.
[0008] Furthermore, the control client is responsible for establishing, starting, and stopping FMP sessions, and collecting statistics;
[0009] The session transmission is scheduled by the control client, which actively sends out probe frames for performance statistics;
[0010] The server is responsible for responding to requests from the control client to establish, start, and stop FMP sessions;
[0011] The session reflection is scheduled by the server, which responds to the probe frames sent by the session sending module.
[0012] Furthermore, the FMP protocol defines four stages, namely control session establishment, measurement session establishment, measurement session startup and measurement session stop. The control client and server establish a control session based on a TCP connection. After the control session is established, the control client specifies the IP address and TCP port to initiate the establishment of a measurement session. After the measurement session is established, the control client initiates a startup message for the measurement session. When the control session receives the startup message, it starts all measurement sessions under the control session. When data collection is completed, the measurement session stops.
[0013] Furthermore, the control session establishment includes:
[0014] The server opens the TCP port listening, and the control client initiates the TCP connection;
[0015] The server actively sends an initiation message to notify the control client of the server's parameter configuration;
[0016] After receiving the initiation message from the server, the control client sends an establishment response message to initiate the establishment of the control session;
[0017] The server verifies the establishment response message and responds with a service start message;
[0018] The control session between the control client and the server is established.
[0019] Furthermore, the measurement session establishment includes:
[0020] The control client sends a measurement session request message carrying IP address and TCP port information to the server through a TCP connection;
[0021] After receiving the measurement session request message, the server establishes a measurement session according to the IP address and TCP port specified by the control client, and replies with a session acceptance message to the control client;
[0022] The measurement session between the control client and the server is established.
[0023] Further, the measurement session initiation includes:
[0024] Control the client to send a start session message;
[0025] After receiving the start session message, the server notifies the session reflection module of the relevant measurement session information so that it has the ability to respond;
[0026] After the server responds to the start confirmation message, it starts the test session;
[0027] After receiving the start confirmation message, the control client notifies the session sending module to measure the session information so that it has the ability to send probe frames.
[0028] The measurement session is started and the session reflection module begins to respond to FMP detection messages.
[0029] Further, the measurement session stopping includes:
[0030] Control the client to send a stop session message to notify the server to stop performance statistics;
[0031] After receiving the stop session message, the server notifies the session reflection module to close the answering function of the corresponding measurement session.
[0032] Furthermore, the xFlow indicator measurement method based on the FMP protocol is applied in the traffic, operation configuration and statistics of xFlow network element devices.
[0033] Beneficial effects:
[0034] 1. The present invention defines a unified FMP protocol framework to facilitate subsequent xFlow-based management and control expansion needs.
[0035] 2. After the present invention realizes the unified protocol, it can be convenient for various manufacturers to uniformly realize the export of relevant indicators, which is convenient for the unified operation and maintenance of the entire network.
[0036] 3. The present invention implements the FMP protocol based on TCP as the transmission protocol, which can ensure the integrity of statistical information.
[0037] 4. The present invention can process large-scale traffic statistics of xFlow network element devices based on the FMP protocol, accurately compare and troubleshoot, etc., to improve deployment and operation and maintenance efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] Figure 1 It is a diagram of the interrelationships of the four logical roles defined by the FMP protocol of the present invention;
[0039] Figure 2 It is a schematic diagram of the process of establishing a control session of the present invention;
[0040] Figure 3 It is a schematic diagram of the measurement session establishment process of the present invention;
[0041] Figure 4 It is a schematic diagram of the measurement session startup process of the present invention;
[0042] Figure 5It is a schematic diagram of the measurement session stop flow of the present invention;
[0043] Figure 6 It is a schematic diagram of the information interaction data flow based on the FMP protocol according to an embodiment of the present invention. DETAILED DESCRIPTION
[0044] The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.
[0045] Those skilled in the art will appreciate that the embodiments of the present invention may be implemented as a system, device, apparatus, method or computer program product. Therefore, the present disclosure may be specifically implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.
[0046] According to an embodiment of the present invention, a method and application for measuring xFlow indicators based on the FMP protocol are proposed. The FMP protocol defines a method for measuring the accuracy of xFlow indicators between any two network element devices supporting the protocol in an IP network.
[0047] The principle and spirit of the present invention are explained in detail below with reference to several representative embodiments of the present invention.
[0048] The newly defined xFlow indicator measurement method based on the FMP protocol (based on TCP) of the present invention is described as follows:
[0049] Terminology Introduction:
[0050] The FMP protocol uses a client-server communication model and defines the following four logical roles, which are related to each other as follows: Figure 1 As shown:
[0051] Control-Client: Responsible for establishing, starting and stopping FMP sessions and collecting statistics.
[0052] Session-Sender: Scheduled by Control-Client, actively sends out probe frames for performance statistics.
[0053] Server: Responsible for responding to requests from Control-Client to establish, start, and stop FMP sessions.
[0054] Session-Reflector: Scheduled by the Server, responds to the probe frames sent by the Session-Sender.
[0055] Basic principle:
[0056] The control client / server is responsible for negotiating the establishment and start of the FMP session. Once the session is started, the control client and server will notify the session sending and session reflection modules of the relevant session information (including the IP address and port number used in the session), so that they can respectively have the ability to send and respond to probe frames for this session. The process is divided into four stages: control session establishment, measurement session establishment, measurement session start and measurement session stop.
[0057] 1. Control session establishment:
[0058] The establishment of a control session is mainly used to determine the legitimacy and parameter verification of the control layer. The two establish a control session based on a TCP connection. The control session is the prerequisite for establishing a measurement session. The process is as follows: Figure 2 As shown:
[0059] 1. The server opens the TCP port listening, and the control client initiates the TCP connection.
[0060] 2. The server actively sends an initiation message to notify the control client of the server's parameter configuration.
[0061] 3. After receiving the initiation message from the server, the control client sends an establishment response message to initiate the establishment of the control session.
[0062] 4. The server verifies the establishment response message and responds with a service startup message.
[0063] 5. At this point, the control session between the client and the server is established.
[0064] 2. Measurement session establishment:
[0065] After the control session is established, the client can be controlled to specify the IP address and TCP port to initiate the establishment of the measurement session. The process is as follows: Figure 3 As shown:
[0066] 1. The control client sends a measurement session request message carrying IP address and TCP port information to the server through a TCP connection.
[0067] 2. After receiving the measurement session request message, the server establishes a measurement session according to the IP address and TCP port specified by the control client, and replies with a session acceptance message to the control client.
[0068] 3. At this point, the measurement session between the control client and the server is established.
[0069] 3. Measurement session start:
[0070] The measurement session is initiated based on the control session. When the control session receives the start message, it will start all measurement sessions under the control session. After the measurement session is established, the control client can initiate a measurement session start message. The process is as follows: Figure 4 As shown:
[0071] 1. Control the client to send a start session message.
[0072] 2. After receiving the start session message, the server notifies the session reflection module of relevant measurement session information (including information such as the IP and port number used in the session) so that the session reflection module has the ability to respond.
[0073] 3. After the server replies with a start confirmation message, it starts the test session.
[0074] 4. After receiving the start confirmation message, the control client notifies the session sending module to measure the session information (including the IP and port number used in the session, etc.) so that the session sending module has the ability to send probe frames.
[0075] 5. At this point, the measurement session is started and the session reflection module can begin to respond to FMP measurement messages.
[0076] A measurement session can support multiple subclasses, such as data measurement sessions and fault detection sessions.
[0077] 4. Measurement session stop:
[0078] When data collection is complete, the measurement session can be stopped by Figure 5 As shown:
[0079] 1. Control the client to send a stop session message to notify the server to stop performance statistics.
[0080] 2. After receiving the stop session message, the server notifies the session reflection module to close the response function of the corresponding measurement session.
[0081] The FMP message format is described in Table 1:
[0082] 1. Public message header:
[0083] It is used to define the unified common part of the FMP protocol carried on the TCP protocol. The main fields include the protocol version, the purpose type of the message and the specific message body (such as control and session message bodies, etc.).
[0084] 2. Control message:
[0085] It is used to define the basic information of control messages and guide the interaction process of control sessions. The main fields include version, message usage type and specific message body.
[0086] 3. Request / start session message body:
[0087] It is used to define the basic information of various types of session messages and guide the establishment of the session process. The main fields include sequence number, session type, session statistics, scheduling interval, etc.
[0088] Table 1
[0089]
[0090] The following is an example of a specific measurement session message, as shown in Table 2 below, which describes the indicator content exported by the router during measurement, where the measurement report is the overall measurement record structure, the measurement record header is the structure of each measurement record, and the measurement record body is the definition of the specific measurement record structure.
[0091] Table 2
[0092]
[0093] It should be noted that, although the operations of the method of the present invention are described in a specific order in the above embodiments and the accompanying drawings, this does not require or imply that the operations must be performed in the specific order, or that all the operations 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.
[0094] In order to explain the above-mentioned method for measuring xFlow indicators based on the FMP protocol more clearly, a specific embodiment is used for illustration below. However, it should be noted that this embodiment is only for better illustrating the present invention and does not constitute an improper limitation to the present invention.
[0095] Embodiment 1: An FMP session is established between NDC and network element devices such as Router through the newly defined FMP protocol (based on TCP), and Router and NDC periodically or actively trigger the interaction of statistics and configuration data according to business needs.
[0096] Figure 6 FIG. 1 is a schematic diagram of the information exchange data flow based on the FMP protocol according to an embodiment of the present invention. Figure 6 As shown, the overall interaction process is as follows:
[0097] 1. Establish an FMP protocol session between the Router and NDC;
[0098] 2. The Router performs statistics based on flow characteristics periodically or according to business needs;
[0099] 3. The Router reports statistical information to the NDC or third-party collector periodically or according to business needs based on the FMP protocol. The information can carry information such as xFlow traffic and xFlow configuration;
[0100] 4. NDC or third-party collectors locally save xFlow traffic (obtained by summing the number of xFlow messages and bytes) and xFlow configuration information according to the FMP protocol;
[0101] 5. The user can intuitively compare the xFlow configuration in step 4 with the standard configuration data of the Router to determine whether there are any differences, thereby determining whether the Router has configuration problems such as errors, omissions, or non-standardization;
[0102] 6. Users can intuitively compare the xFlow traffic in step 4 with the xFlow traffic data received by NDC or a third-party collector to determine whether there is a deviation, thereby determining the accuracy of traffic restoration based on the xFlow protocol.
[0103] The specific implementation instructions are as follows:
[0104] router:
[0105] 1. Enable FMP protocol;
[0106] 2. Configure the local IP of the FMP control client, the IP of the NDC and the FMP port;
[0107] 3. Configure FMP to control the collection time, collection dimension and collection interval of client services;
[0108] 4. Start FMP to control client service scheduling.
[0109] NDC / third-party collector:
[0110] 1. Enable FMP protocol;
[0111] 2. Configure the local IP of the FMP server, the IP of the router and the FMP port;
[0112] 3. Configure FMP session service types (such as traffic, operation configuration and statistics, etc.) as needed;
[0113] 4. Start the FMP server service.
[0114] The xFlow indicator measurement method and application based on the FMP protocol proposed in the present invention define a unified FMP protocol framework, which is convenient for subsequent various management and control expansion needs based on xFlow; after the unified protocol is implemented, it is convenient for various manufacturers to uniformly export relevant indicators, which is convenient for unified operation and maintenance of the entire network; the FMP protocol is implemented based on TCP as the transmission protocol to ensure the integrity of statistical information; large-scale traffic statistics of network element devices of xFlow can be processed based on the FMP protocol, and accurate comparison and troubleshooting can be performed, etc., thereby improving deployment and operation and maintenance efficiency.
[0115] Although the spirit and principle of the present invention have been described with reference to several specific embodiments, it should be understood that the present invention is not limited to the disclosed specific embodiments, and the division of various aspects does not mean that the features in these aspects cannot be combined to benefit, and such division is only for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements contained in the spirit and scope of the attached claims.
[0116] Regarding the limitation of the protection scope of the present invention, those skilled in the art should understand that, based on the technical solution of the present invention, various modifications or variations that can be made by those skilled in the art without creative work are still within the protection scope of the present invention.
Claims
1. A method for measuring xFlow indicators based on the FMP protocol, characterized in that: The method includes: Step 1: Establish an FMP protocol session between the Router and NDC; Step 2: The Router performs statistics based on flow characteristics periodically or as required by the service. Step 3: The Router reports statistical information to the NDC or a third-party collector periodically or according to business needs based on the FMP protocol. The information carries xFlow traffic and xFlow configuration information. Step 4: NDC or third-party collector locally saves xFlow traffic and xFlow configuration information according to the FMP protocol; Step 5: Compare the xFlow configuration in step 4 with the standard configuration data of the Router to determine whether there are any differences, thereby determining whether the Router has any errors, omissions, or non-standard configuration problems; Step 6: Based on the xFlow traffic in step 4, compare it with the xFlow traffic data received by NDC or a third-party collector to determine whether there is a deviation, thereby determining the accuracy of traffic restoration based on the xFlow protocol; The FMP protocol adopts the client-server communication mode and defines four logical roles, namely, the control client, session sending, server and session reflection. The control client / server is responsible for negotiating the establishment and start of the FMP session. Once the session is started, the control client and server notify the session sending and session reflection modules of the relevant session information, so that they have the ability to send and respond to probe frames for this session. The FMP protocol message format includes: Common message header: used to define the unified common part of the FMP protocol carried on the TCP protocol. The main fields include the protocol version, the purpose type of the message and the specific message body. Control message: used to define the basic information of control messages and guide the interaction process of control sessions. The main fields include version, message usage type and specific message body. Request / start session message body: used to define the basic information of various types of session messages and guide the establishment of the session process. The main fields include sequence number, session type, session statistics items, and scheduling interval.
2. The method for measuring xFlow indicators based on the FMP protocol according to claim 1, characterized in that: The control client is responsible for establishing, starting and stopping FMP sessions and collecting statistical results; The session transmission is scheduled by the control client, which actively sends out probe frames for performance statistics; The server is responsible for responding to requests initiated by the control client to establish, start and stop FMP sessions; The session reflection is scheduled by the server to respond to the probe frame sent by the session sending module.
3. The method for measuring xFlow indicators based on the FMP protocol according to claim 1, characterized in that: The FMP protocol defines four stages, namely control session establishment, measurement session establishment, measurement session start and measurement session stop. The control client and the server establish a control session based on a TCP connection. After the control session is established, the control client specifies an IP address and a TCP port to initiate the establishment of a measurement session. After the measurement session is established, the control client initiates a start message for the measurement session. When the control session receives the start message, all measurement sessions under the control session are started. When data collection is completed, the measurement session stops.
4. The method for measuring xFlow indicators based on the FMP protocol according to claim 3 is characterized in that: The control session establishment includes: The server opens the TCP port listening, and the control client initiates the TCP connection; The server actively sends an initiation message to notify the control client of the server's parameter configuration; After receiving the initiation message from the server, the control client sends an establishment response message to initiate the establishment of the control session; The server verifies the establishment response message and responds with a service start message; The control session between the control client and the server is established.
5. The method for measuring xFlow indicators based on the FMP protocol according to claim 3, characterized in that: The measurement session establishment includes: The control client sends a measurement session request message carrying IP address and TCP port information to the server through a TCP connection; After receiving the measurement session request message, the server establishes a measurement session according to the IP address and TCP port specified by the control client, and replies with a session acceptance message to the control client; The measurement session between the control client and the server is established.
6. The method for measuring xFlow indicators based on the FMP protocol according to claim 3, characterized in that: The measurement session initiation includes: Control the client to send a start session message; After receiving the start session message, the server notifies the session reflection module of the relevant measurement session information so that it has the ability to respond; After the server responds to the start confirmation message, it starts the test session; After receiving the start confirmation message, the control client notifies the session sending module to measure the session information so that it has the ability to send probe frames; The measurement session is started and the session reflection module begins to respond to FMP detection messages.
7. The method for measuring xFlow indicators based on the FMP protocol according to claim 3, characterized in that: The measurement session stopping includes: Control the client to send a stop session message to notify the server to stop performance statistics; After receiving the stop session message, the server notifies the session reflection module to close the answering function of the corresponding measurement session.
8. Application of the method for measuring xFlow indicators based on the FMP protocol according to any one of claims 1 to 7 in the traffic, operation configuration and statistics of xFlow network element devices.
